On Tue, Aug 19, 2008 at 4:41 AM, Daniel Gimpelevich
<[EMAIL PROTECTED]> wrote:
> Hello. Before I get into the subject of my message, let me mention the
> following mini-patch:
>
> Index: src/jtag/parport.c
> ===
> --- src/jtag/parport.
Can you resubmit using svn diff?
I wasn't able to apply this patch.
Also svn diff has the added bonus that it will ignore all the automake files
for you...
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
> Are you doing some special pre-processing before passing it to TCL so that
> openocd-specific commands don't need the semicolon (to maintain backward
> compatibility?)
Essentially. Though *after* I get it back from Tcl and before I pass it to the
openocd commands, I strip all args after the arg
>
> > My old command-line from r717:
> >
> > ./openocd -f interface/olimex-arm-usb-ocd.cfg -f target/sam7x256.cfg -c
> init
> > -c reset
> >
> > This quits. If I leave off the "-c reset", the program stays alive and I
> can
> > telnet to it. This is different than how r717 behaved. I'm not sure why
> I would have kept the sam7s config files since all variants can use this
> base configuration.
>
On secong thought, I would rename it just sam7 or at91sam7 because all of
the following can share the same config file:
at91sam7S
at91sam7SE
at91sam7X
at91sam7XC
at91sam7A
at91sam7L
The flash look
I noticed you are using the AT91SAM7 -
You might want to check out some of the things I wrote for the SAM7 also.
https://lists.berlios.de/pipermail/openocd-development/2008-July/002378.html
try this from GDB [from the above email]
Step 1:
(gdb) mon source [find tcl/chip/atmel/at91/at91sam
Hello. Before I get into the subject of my message, let me mention the
following mini-patch:
Index: src/jtag/parport.c
===
--- src/jtag/parport.c (revision 929)
+++ src/jtag/parport.c (working copy)
@@ -101,6 +101,7 @@
{ "w
Jason Gallicchio wrote: [lots of comments about tcl ish things]
First, remember this: OpenOCD uses JIM TCL - which is not "Main Stream
Tcl/Tk".
JimTCL can be embedded in a "rom" target - something main stream Tcl/TK
cannot do.
This 'embedded feature' is some what helpful for some users of OpenO
>
> > The sam7x and sam7s configurations are identical except for calling
> > different reset scripts. But the reset scripts are identical except for
> > extra
> > spaces at the end of some lines (violating your style rules.)
>
> I've deleted the sam7s files from subversion.
>
This may have been t
Attached is Patch #1 of the target trigger stuff.
This patch introduces 2 new things to Jim
(A) a new concept called "Name Value Pair" or NVP, in simple terms:
Think: "String" and "Value". There can be many strings - all related to
a single value, for examle: "T", "t", "y", "1", "yes", all can
>
> > Comments at the end of lines do not work in telnet, which makes
> > pasting pieces of .cfg files in difficult.
>
> OpenOCD uses TCL now, but I did add support for # comments
> at the end of openocd commands a while back.
>
> Which subversion version are you running?
>
> If you add "; # commen
Johannes> PS: IMHO --enable-gccwarnings should be the default.
I agree, that was the way I originally submitted the patch.
I don't know why it got flipped.
-Duane.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists
Committed.
Thanks!
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-
On Wed, Aug 06, 2008, Spen wrote:
>
> I have committed the attached patch.
> It removes a few more build warnings.
> fixes broken mips build - unsure when this happened.
>
> fixes non working --enable-gccwarnings configure option.
> added --enable-gccwarnings to docs.
Attached is another warning
Please include a debug_level 3 log. This will tell me the origin of the error.
>
> And then retry.
>
> > flash erase_address 0x 0x0007
> error erasing flash bank, status: 0xa2
> failed erasing sectors 0 to 6 (-902)
> Runtime error, file "?", line 1:
>error erasing flash bank, sta
Hello
I'm connecting an Olimex arm-usb-tiny to a STEVAL IFD001V1 with
STR912FAW44 cpu. I run openocd (SVN revision 895 and/or 902) and then
connect with gdb someimage.elf, then run:
(gdb) load
Error erasing flash with vFlashErase packet
Error: error erasing flash bank, status: 0xa2
Error: fai
16 matches
Mail list logo
