On Feb 6, 2009, at 1:08 AM, Martin Haeberli wrote:

Hello!


Debug: 45 31 command.c:91 script_command(): script_command - jtag_device Debug: 46 31 command.c:108 script_command(): script_command - jtag_device, arg
v[0]=ocd_jtag_device
Debug: 47 31 command.c:108 script_command(): script_command - jtag_device, arg
v[1]=5
Debug: 48 31 command.c:108 script_command(): script_command - jtag_device, arg
v[2]=0x1
Debug: 49 31 command.c:108 script_command(): script_command - jtag_device, arg
v[3]=0x1
Debug: 50 31 command.c:108 script_command(): script_command - jtag_device, arg
v[4]=0x1e

This looks like an old-style jtag_device command. You'll want to convert it to the new-style jtag newtap command.


Debug:   51 31 target.c:3990 jim_target(): Target command params:
Debug: 52 31 target.c:3991 jim_target(): target create target0 mips_m4k -endia
n big -chain-position 0

And then the argument to -chain-position will change.

Debug: 76 266 openocd.c:150 handle_init_command(): jtag interface init complet
e
Debug:   77 266 jtag.c:1621 jtag_init_inner(): Init JTAG chain
Debug: 78 266 jtag.c:327 jtag_call_event_callbacks(): jtag event: JTAG control
ler reset (TLR or TRST)
Debug:   79 266 jtag.c:1301 jtag_reset_callback(): -
Debug: 80 266 jtag.c:327 jtag_call_event_callbacks(): jtag event: JTAG control
ler reset (TLR or TRST)
Debug:   81 266 jtag.c:1301 jtag_reset_callback(): -
Error: 82 281 jtag.c:1357 jtag_examine_chain(): JTAG communication failure, ch
eck connection, JTAG interface, target power etc.
Error: 83 281 jtag.c:1640 jtag_init_inner(): trying to validate configured JTA
G chain anyway...
Debug: 84 281 jtag.c:327 jtag_call_event_callbacks(): jtag event: JTAG control
ler reset (TLR or TRST)
Debug:   85 281 jtag.c:1301 jtag_reset_callback(): -
Error: 86 281 jtag.c:1471 jtag_validate_chain(): Error validating JTAG scan ch
ain, IR mismatch, scan returned 0x7f
Error: 87 281 jtag.c:1645 jtag_init_inner(): Could not validate JTAG chain, co
ntinuing anyway...
Debug: 88 281 openocd.c:156 handle_init_command(): jtag init complete

Looks like the JTAG hardware failed to communicate at all. Both the examine and validate failed which means OpenOCD cannot talk to anything on the JTAG chain. I'm not sure why we bothered to continued after this point. Something is wrong with either the JTAG chain configuration or the JTAG hardware.

----
openocd.cfg:
----
telnet_port 4444
gdb_port 3333

interface ft2232
ft2232_device_desc "Signalyzer A"
ft2232_layout signalyzer
ft2232_vid_pid 0x0403 0xbca0

jtag_nsrst_delay 100
jtag_ntrst_delay 100

reset_config trst_and_srst separate

jtag_device 5 0x1 0x1 0x1e

Change this to a jtag newtap command.



target create target0 mips_m4k -endian big -chain-position 0

jtag_khz 1000
flash bank cfi 0x90000000 0x200000 2 2 0
----

I welcome any guidance y'all can offer; this is in a TI TNETC4401
cable modem chip.

Best,

Martin

--
Rick Altherr
kc8...@kc8apf.net

"He said he hadn't had a byte in three days. I had a short, so I split it with him."
 -- Unsigned



Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to