I committed the "transport" framework patch; you've
seen it on the list before, the main difference ince
the last post was adding user's guide docs.

(This has been ready for some time, and I got tired of just carrying it 
privately.  It's groundwork, and shouldn't affect anyone's work; but if it 
does, we should learn about it, and fix that soonish.)

To recap:  debug-capable transports are JTAG or SWD
... with SWD (still) on the way.  JTAG init changed just a bit.

Programming-capable transport examples can include SPI and UART -- someone 
wanting to contribute to the OpenOCD project might want to look at those.

You could for example update the AVR ISP programming support to use a 
to-be-written SPI
transport, hooking up to the current  skeletal AVR8 support.  Similarly, both 
TI/Luminary and NXP versions of Cortex-M3 support SPI for initial flashing of 
firmware, and a good "SPI" transport should be able to work on those chips too. 
 (I know some of the swiss-army-knife style debug adapters can do SPI easily.)


_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to