I'm new to OpenOCD and had it debugging out of RAM beautifully. I've
been getting sporadic errors verifying binary images I write to flash. This
got me interested in OpenOCD and its code. The rest of this email is a
long list of issues I encountered, some of which are probably due to
my own misunde
Answering some of your questions here. Please keep tabs on your problems
and keep sending patches/bringing them up one by one :-)
There was a lot of good feedback in this email, but of course with so
many things in a single posting, there is the danger(certainty actually)
that some things will dr
>
> > 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
>
> > 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
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
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
> 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
>
> > 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
> 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