Does anyone have an s3c6410 PCB out there they
could donate to us?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios
Duane Ellis wrote on 2009-09-07 21:29:50:
> Jonas Horberg wrote:
> > Note that configuration files with jtag_khz or jtag_rclk can not be
> > used with the parport interfaces until a fix is created.
> >
> Huh? Sorry I'm late to this thread but I have a question.
jtag_khz and jtag_rclk require t
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Tue, Sep 8, 2009 at 2:31 AM, Duane Ellis wrote:
> david> Having a hundred or so chip-specific config files is
> david> a messy concept...
>
> Yes, but that is exactly what is needed.
>
> If there are 100 chips - you need 100 files, with 100 names.
I guess I have to agree with you on this one.
Provide an "armv7a disassemble" command. Current omissions include
VFP (except as coprocessor instructions), Neon, and various Thumb2
opcodes that are not available in ARMv7-M processors.
---
doc/openocd.texi| 17 +
src/target/armv7a.c | 86
Clean up some loose ends with the ARM disassembler
- Add a header comment describing its current state and uses
and referencing the now-generally-available V7 arch spec
- Support some mode switch instructions:
* Thumb to Jazelle (BXJ)
* Thumb to ThumbEE (ENTERX)
* ThumbEE to Thum
Hi!
I just like to report that there is a regression in the s3c6410 support
of OpenOCD. Release 0.2 is working fine with my SMDK6410 here, using
jtagkey-tiny with libftdi.
The command I use to start is:
cd tcl
../src/openocd -s . -f ./interface/jtagkey-tiny.cfg -f
./target/samsung_s3c6410.cfg
david> Having a hundred or so chip-specific config files is
david> a messy concept...
Yes, but that is exactly what is needed.
If there are 100 chips - you need 100 files, with 100 names.
Take the "openocd-developer-hat" off for a little bit and think about this.
Configure files are something *
Here are two very small patches.
The first one fixes the reporting of instruction state.
The second one makes sure the processor stays in Thumb state when
restoring the PC.
After this it is possible to single step Thumb code.
Best regards,
Magnus
Index: src/target/armv7a.c
==
Øyvind Harboe wrote:
> The only way we get a decent amount of regression testing is
> to commit.
>
> If you are reasonably confident about that this is the right direction
> and there appears to be no regressions, then it should be
> committed for testing.
>
>
>
Commited
__
The only way we get a decent amount of regression testing is
to commit.
If you are reasonably confident about that this is the right direction
and there appears to be no regressions, then it should be
committed for testing.
--
Øyvind Harboe
Embedded software and hardware consulting services
ht
On Monday 07 September 2009, Duane Ellis wrote:
> I would have put *ALL* sets in the CHIP_SPECIFIC file
> And some type of validation in the CHIP_INTERNALS file.
Wasn't the key part of Freddie's idea to git rid of
the need for a plethora of chip-specific files?
NXP has 90-odd lpc2xxx chips (most
Duane Ellis pisze:
Freddie Chopin wrote:
I got the second version - it implements ideas from Duane and David.
comments...
-Duane.
===
1) Seems to be missing proc _SET_DEFAULT..
2) There are numerous syntax errors ... example:
# check for VARIANT - it has to be defined
if {
Jonas Horberg wrote:
> Note that configuration files with jtag_khz or jtag_rclk can not be
> used with the parport interfaces until a fix is created.
>
Huh? Sorry I'm late to this thread but I have a question.
The idea here is: "jtag_khz 1000" - should mean no faster then 1mhz
There is no "mi
Freddie Chopin wrote:
> I got the second version - it implements ideas from Duane and David.
comments...
-Duane.
===
1) Seems to be missing proc _SET_DEFAULT..
2) There are numerous syntax errors ... example:
# check for VARIANT - it has to be defined
if { [info exists VARIAN
Magnus Lundin wrote:
> Hello,
>
> If there are no known regressions then perhaps this patch should be
> commited ?
>
> http://lists.berlios.de/pipermail/openocd-development/2009-September/010335.html
>
> There are more thumb handling stuff to be fixed so I think this should
> go first.
Acked-
Hello,
If there are no known regressions then perhaps this patch should be
commited ?
http://lists.berlios.de/pipermail/openocd-development/2009-September/010335.html
There are more thumb handling stuff to be fixed so I think this should
go first.
Regards,
Magnus
I got the second version - it implements ideas from Duane and David.
Take a look and tell me what do you think about it. Should I create a patch?
I attach 2 files - lpc2xxx_internals.tcl and lpc2103.cfg as an example.
Notice that now ALL the magic is completely hidden inside
lpc2xxx_internals.
Matt Hsu wrote:
> Magnus Lundin wrote:
>> Hello list.
>>
>> For those of you who has not yet had the time to read all the TRM's
>> covering Cortex-A8 and ARM ADIv5, I have started to write up an easy
>> introduction to the debug components in a Cortex-A8 system.
>>
> It's great. The first
Example of use:
jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf
-expected-id $_CPUTAPID
jtag configure $_CHIPNAME.cpu -event post-reset {
puts hello!
}
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
__
Beagleboard needs 100 clocks after reset.
The attached patch adds support for a generic post-reset
event.
Testing & comments needed before committing:
1. test that a robust post reset event can be written for Beagleboard
that handles the "100 clocks after reset" problems.
2. test for regression
David Brownell wrote on 2009-09-04 17:17:14:
> On Friday 04 September 2009, Jonas Horberg wrote:
> > Automatic detection of the toogle speed is of course the next step.
> > Do we have something platform independent that can measure
> > with the required precision?
I did some research and found t
23 matches
Mail list logo