Douglas Bertelsen <[email protected]> writes: > I am in the process of attempting to flash an empty (except for the > preloaded ROM) LPC11U14 in the TeleGPS I soldered together several days ago > (the saw filter was about as fun as the 0402 components). I'm using > openocd built from the git.gag.com repository but come up against a brick > wall at that point. using ao-flash-lpc results in an error of "program" > not being a valid command and 'lpc200' driver usage field missing.
That's a bit odd; Bdale has been happily flashing TeleGPS boards, and I
assume he's using those openocd bits with the 'turnon_telegps' script in
ao-bringup.
I've just flashed a couple dozen EasyMini boards, but I'm using slightly
different openocd bits. I've pushed those to the lpc11uxx branch on
gag.com; you may want to try those and see if they work better.
> Trying to dig deeper, I have been mucking about in the openocd telnet
> client with limited success. Even when I get the target halted, the flash
> never takes, complaining about jtag errors. Openocd seems a lot less scary
> than it did on Wednesday, but I'm still far from picking everything
> up.
Yeah, it's not my favorite piece of code either; the scripts certainly
make it flexible, but getting it to work reliably hasn't been easy for us.
> Keith, you mentioned some tcl scripts for the LPC11U14 in a blog post, are
> those now used in the ao-flash-lpc script or posted elsewhere? I've
> searched around and looked at a lot of source code and cfg files, but don't
> seem to be finding what I'm looking for.
The TCL scripts needed for openocd are all in the repository. If you
look at the ao-flash-lpc script. That script just references the
configuration provided with the openocd build itself:
echo "program $file verify reset" > $cmds
openocd \
-f interface/stlink-v2.cfg \
-f target/lpc11u14.cfg \
-f $cmds \
-c shutdown
You should see both the interface/stlink-v2.cfg and target/lpc11u14.cfg
files in openocd's tcl directory.
> I do have a stlink-v2 dongle (currently used with openocd) and ftdi ft232rl
> breakout board if needed. Any insight would be appreciated.
One trick with the stlink-v2 dongle is that all of its outputs are
driven by voltage coming from the target system (pin 1 and 2 on the
20-pin header). Our boards don't provide that on their debug connectors,
but the stlink-v2 dongle conveniently provides 3.3V on pin 19.
If you look at the 'swdadapter' schematic, you'll see how we hook the
four debug pins on all of our ARM boards to the programming dongle. I
think Bdale has a pile of those adapters built if you want to buy one. I
don't see them in the shop at present though.
-keith
pgpgof43LKIOq.pgp
Description: PGP signature
_______________________________________________ altusmetrum mailing list [email protected] http://lists.gag.com/mailman/listinfo/altusmetrum
