ARM-USB-OCD-H and OS/X

[Torsten Robitzki]

Hello,
currently I try to use my shiny new Olimex to program a cc2560 using JTAG. I'm using openocd 0.10. I try to flash a binary with the following command:

openocd -d 3 -f ./interface/olimex-arm-usb-ocd-h.cfg -f ./target/cc26xx.cfg -c "program ${TARGETNAME}.elf verify reset exit"

The flashing attempt fails and now I'm trying to figure out, why it fails and could use some help. The most interesting part of the produced log might be this part:


...
Info : 326 225 core.c:958 jtag_examine_chain_display(): JTAG tap: cc26xx.jrc tap/device found: 0xffffffff (mfg: 0x7ff, part: 0xffff, ver: 0xf)
Warn : 327 225 core.c:958 jtag_examine_chain_display(): JTAG tap: cc26xx.jrc       UNEXPECTED: 0xffffffff (mfg: 0x7ff, part: 0xffff, ver: 0xf)
Error: 328 225 core.c:958 jtag_examine_chain_display(): JTAG tap: cc26xx.jrc  expected 1 of 1: 0x1b99a02f (mfg: 0x017, part: 0xb99a, ver: 0x1)
Warn : 329 225 core.c:995 jtag_examine_chain_end(): Unexpected idcode after end of chain: 352 0xffbfffff
Warn : 330 225 core.c:995 jtag_examine_chain_end(): Unexpected idcode after end of chain: 480 0x00ffffff
Warn : 331 225 core.c:995 jtag_examine_chain_end(): Unexpected idcode after end of chain: 512 0x001fffe0
Warn : 332 225 core.c:995 jtag_examine_chain_end(): Unexpected idcode after end of chain: 544 0xe0007ffc
Warn : 333 225 core.c:995 jtag_examine_chain_end(): Unexpected idcode after end of chain: 576 0xf00001ff
Warn : 334 225 core.c:995 jtag_examine_chain_end(): Unexpected idcode after end of chain: 608 0xc000003f
Warn : 335 225 core.c:995 jtag_examine_chain_end(): Unexpected idcode after end of chain: 640 0xe000000f
Error: 336 225 core.c:1133 jtag_examine_chain(): double-check your JTAG setup (interface, speed, ...)
Error: 337 225 core.c:1442 jtag_init_inner(): Trying to use configured scan chain anyway...
...


In the end it results in:


User : 658 673 command.c:764 jim_echo(): ** Programming Started **
Debug: 659 673 command.c:145 script_debug(): command - ocd_command ocd_command type ocd_flash write_image erase rc_server.elf
Debug: 660 673 command.c:145 script_debug(): command - ocd_command ocd_command type ocd_echo ** Programming Failed **
Debug: 661 673 command.c:145 script_debug(): command - echo ocd_echo ** Programming Failed **
User : 663 677 command.c:764 jim_echo(): ** Programming Failed **
Debug: 664 677 command.c:145 script_debug(): command - ocd_command ocd_command type ocd_shutdown error
Debug: 665 677 command.c:145 script_debug(): command - shutdown ocd_shutdown error
User : 667 681 server.c:611 handle_shutdown_command(): shutdown command invoked
Debug: 668 681 command.c:628 run_command(): Command failed with error code -4
User : 669 681 command.c:689 command_run_line(): embedded:startup.tcl:490: Error:
in procedure 'flash' called at file "embedded:startup.tcl", line 490


When I repeat the call, the openocd does not contain the Error message from above, but the Program Failed message stays the same.

I've installed the Drivers using the instruction from the manual: 3.3.5 Driver installation in MAC OS X
There it says that I should be able to see some kind of device under /dev. But I don't see that device.

Could it be that I do have some kind of driver installation problem here? How can I track this down to find the cause of the problem?

Thank you very much in advance for any help.

Kind regards,
Torsten

[JohnS]

In case no-one here uses OS/X etc then try oocd ML.

They will want to know full -d3 output & exact OS as well as the tool.

John

[Torsten Robitzki]

Hi John,
thanks for the hint, I've forwarded my question to the openocd mailing list.

cheers,
Torsten