David Brownell wrote:
On Wednesday 24 March 2010, Øyvind Harboe wrote:
I think it makes sense that target scripts now
have to work on SWD *and* JTAG and that they shouldn't really
contain anything jtag or swd specific unless there is a reason to.
Exactly where I'm coming from...
plus, we should avoid creating such reasons
Right if OpenOCD see JTAG as ARM debug port only AND if you exclude JTAG
daisy chain ( multiple JTAG target in the same chain ) !
This makes many conditions !
SWD is specific to ARM core
SWD port is dedicated for one device only.
SWD port can not do board level connection test (boundary scan)
JTAG is generic and integrated by the major part of smart targets (CPU /
FPGA / CPLD / some memory ...)
JTAG port can be chained.
JTAG port can provide board level connection test.
If we see OpenOCD at long term:
- The openocd target script should be the same for JTAG and SWD
- But the only variation will be the max frequency of each port (function).
Regards,
Laurent
http://www.amontec.com
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
