Steve Dean <[email protected]> writes: > What tools are used for 1st-time programming of the STM32 on TeleMega, > CC1111 on TeleBT, and the NXP LPC11U14 on TeleDongle? I'm assuming that > these uC devices do not come from the manufacturers with USB bootloaders > already flased on the part. I have boards and parts for swdadapter, but > I'm certain about all the physical connections.
For the cc1111, we built our own debugging system using another cc1111
(usually in another teledongle). That hooks up to the sdcc debugger so
you get source-level debugging as well.
For the STM32 and LPC11U14, we're using the ST-linkv2 dongles, which
digikey (and others) sell. We started by using an STM32L discovery
board, which has the STlinkv2 device on-board, with jumpers that let you
use it with other boards.
For the STlinkv2 devices, we've got a little PCB which plugs in to the
STlinkv2 20-pin header and offers 4 and pin MicroMaTch connectors
compatible with our debug headers. You can find schematic and layout
information for that board here:
http://git.gag.com/?p=hw/swdadapter
I've got the st-link tools packaged for debian, but the actual bits are
just the upstream ones at this point. We use this for talking to the
STM32 variants:
deb http://keithp.com/archive/ unstable/
deb-src http://keithp.com/archive/ unstable/
For LPC11U14, we're using openocd; there are patches available for the
LPC series on the net. They also use the STlinkv2 dongle. The bits that
we're using are here:
http://git.gag.com/?p=fw/openocd
I haven't checked to see how much of the stuff we've merged from around
the net has made it upstream in a while; it's quite possible that bare
upstream will 'just work' at this point.
I'd love to switch to using openocd everywhere, but I haven't managed to
get it working with the STM32 processors.
--
-keith
signature.asc
Description: PGP signature
_______________________________________________ altusmetrum mailing list [email protected] http://lists.gag.com/mailman/listinfo/altusmetrum
