I’ve been trying to get the Olimex USB JTAG pod and OpenOCD v0.1.0 to work with the TI DM355 eval board.
I had been using this wiki page as a guide…
http://wiki.davincidsp.com/index.php?ti … mex_dongle
Likewise, I was using this page for advice on installing OpenOCD on Ubuntu v8.10:
http://openhardware.net/Embedded_ARM/OpenOCD_JTAG/
However, the problem appears to be that the DM355.cfg offered on davincidsp.com uses obsolete syntax. In particular, this is what I get using the DM355.cfg data provided with OpenOCD v0.1,0. Might anyone have tips for updating DM355.cfg syntax?
$ sudo openocd -f DM355.cfg
Open On-Chip Debugger 0.1.0 (2009-01-24-18:18) Release
BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
$URL: https://kc8apf@svn.berlios.de/svnroot/r … /openocd.c $
OLD SYNTAX: DEPRECATED - translating to new syntax
jtag newtap CHIP TAP -irlen 4 -ircapture 0x1 -irvalue 0x0
Example: STM32 has 2 taps, the cortexM3(len4) + boundryscan(len5)
jtag newtap stm32 cortexm3 …, thus creating the tap: “stm32.cortexm3”
jtag newtap stm32 boundry …, and the tap: “stm32.boundery”
And then refer to the taps by the dotted name.
NEW COMMAND:
OLD SYNTAX: DEPRECATED - translating to new syntax
jtag newtap CHIP TAP -irlen 4 -ircapture 0x1 -irvalue 0x0
Example: STM32 has 2 taps, the cortexM3(len4) + boundryscan(len5)
jtag newtap stm32 cortexm3 …, thus creating the tap: “stm32.cortexm3”
jtag newtap stm32 boundry …, and the tap: “stm32.boundery”
And then refer to the taps by the dotted name.
NEW COMMAND:
OLD SYNTAX: DEPRECATED - translating to new syntax
jtag newtap CHIP TAP -irlen 6 -ircapture 0x1 -irvalue 0x0
Example: STM32 has 2 taps, the cortexM3(len4) + boundryscan(len5)
jtag newtap stm32 cortexm3 …, thus creating the tap: “stm32.cortexm3”
jtag newtap stm32 boundry …, and the tap: “stm32.boundery”
And then refer to the taps by the dotted name.
NEW COMMAND:
Runtime error, file “DM355.cfg”, line 24:
bad option “arm926ejs”: must be one of count, create, current, names, number, or types