Hi,
I was wondering if anyone had tried the above combination; using an Altera USB-Blaster to talk to a Freescale i.MX27 MCU using OpenOCD?
We’re looking to use the above to debug some issues with the Linux kernel… the USB JTAG device of choice is largely due to the fact that it’s there, and allegedly supported by OpenOCD.
Target board is a Ka-Ro TX27 module on their “StarterKit 5” development board. We’ve made a wiring adapter to convert between the Altera wiring standard, and the ARM JTAG used on the StarterKit 5. (AFAIK it’s the standard ARM JTAG wiring.) OpenOCD is built from a git clone done yesterday.
vk4mslp2 tmp # openocd -f interface/altera-usb-blaster.cfg -f target/imx27.cfg
Open On-Chip Debugger 0.5.0-dev-00391-g2986320 (2010-06-29-16:23)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
3000 kHz
trst_and_srst srst_pulls_trst srst_gates_jtag trst_push_pull srst_open_drain
dcc downloads are enabled
Error: Translation from khz to jtag_speed not implemented
Error: Translation from khz to jtag_speed not implemented
Error: Translation from jtag_speed to khz not implemented
Error: Translation from khz to jtag_speed not implemented
Info : adapter-specific clock speed value 3000
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Command handler execution failed
in procedure 'jtag'
Warn : jtag initialization failed; try 'jtag init' again.
^C
Evidently; there is a bug relating to the “jtag init” command … in so far as either in the documentation and in the message above suggesting that it can be run multiple times, or in the “jtag init” command itself, as running it yields a message telling me that it has already been run.
> jtag init
'jtag init' has already been called
Update: Tried it with a board based on the Altera EPM7064SLC44… Altera’s software and the same hardware successfully scans the JTAG chain… however under Linux:
vk4mslp2 scripts # openocd -f interface/altera-usb-blaster.cfg
Open On-Chip Debugger 0.5.0-dev-00391-g2986320 (2010-06-29-16:23)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
3000 kHz
Error: Translation from khz to jtag_speed not implemented
Error: Translation from khz to jtag_speed not implemented
Error: Translation from jtag_speed to khz not implemented
Error: Translation from khz to jtag_speed not implemented
Info : adapter-specific clock speed value 3000
Warn : There are no enabled taps. AUTO PROBING MIGHT NOT WORK!!
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Warn : There are no enabled taps. AUTO PROBING MIGHT NOT WORK!!
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Command handler execution failed
in procedure 'jtag'
Warn : jtag initialization failed; try 'jtag init' again.
Warn : gdb services need one or more targets defined
On a related note, has anyone tried using OpenOCD with this particular microcontroller (1.8V logic)? If so, what JTAG devices do you use/recommend? We’d prefer something that can handle 1.8V logic (the USB Blaster allegedly does), as while the starterkit board incorporates a level converter, this is something we’ll probably omit on our own boards.
Regards,