Hi!
I'm trying to run openocd on an ARM9/uClibc system to access some
"client" ARMs and configure them. Therefore, I adapted the at91rm9200
interface to my hardware situation. I could verify with a Scope that the
signals are there (TCK, TDI, TDO, TMS). Only the openocd gives me some
headache. For some reasons I got this output when running from gdb:
Info: JTAG device found: 0x0792603f (Manufacturer: 0x01f, Part:0x7926,
Version: 0x0)
Warning:Unexpected idcode after end of chain! 256 0x000000fe
Warning:Unexpected idcode after end of chain! 288 0x0000007f
Warning:Unexpected idcode after end of chain! 320 0x000000ff
Warning:Unexpected idcode after end of chain! 352 0x0000007f
Warning:Unexpected idcode after end of chain! 384 0x800000ff
Warning:Unexpected idcode after end of chain! 416 0x000001ff
Warning:Unexpected idcode after end of chain! 448 0x800000ff
Warning:Unexpected idcode after end of chain! 480 0x000001ff
Warning:Unexpected idcode after end of chain! 512 0x000000ff
Warning:Unexpected idcode after end of chain! 544 0x800000ff
Warning:Unexpected idcode after end of chain! 576 0x000000ff
Warning:Unexpected idcode after end of chain! 608 0x800000ff
Program received signal SIGSEGV, Segmentation fault.
0x00051a3c in interface_jtag_add_dr_out (device_num=0, num_fields=0,
num_bits=0x2, value=0xeead8, end_state=TAP_RTI) at jtag.c:732
732 in jtag.c
What is the reason for this behavior.
a.) Why do I receive "Unexpected idcode"?
b.) Why is that command chain failing?
I use openocd svn revision 1191.
Regards
akuehn
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
