David Brownell a écrit : > On Tuesday 24 November 2009, Albert ARIBAUD wrote: >>> Error: feroceon.cpu: IR capture error; saw 0x09 not 0x01 > > jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id > $_CPUTAPID > ^^^^^^^^^^^ > Does "0x03" behave?
I did investigate by fixing 0x3 directly in feroceon.cfg, and it does not improve: > Error: IR capture error at bit 4, saw 0x09 not 0x...3 (and it does not change anything else -- this is consistent with the OpenOCD docs, which state that IR capture is for information only and has no functional impact.) Actually, a combination that works (i.e., shows no IR capture error) is obtained by using -irlen 32 -ircapture 0x1 -irmask 0x3, but an IR length of 32 is inconsistent with the ARM/feroceon literature available (in which IR length is 4 bits). Besides, other OpenOCD users have working configs with feroceon.cfg as it is (on another board type and/or another JTAG probe type). With that abnormal -irlen 32 -ircapture 0x1 -irmask 0x3, the behavior is different: > $ src/openocd -f o.cfg > Open On-Chip Debugger 0.4.0-dev-00171-gfd2c9fd (2009-11-24-08:48) > For bug reports, read > http://openocd.berlios.de/doc/doxygen/bugs.html > trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain > jtag_nsrst_delay: 200 > jtag_ntrst_delay: 200 > none separate > Info : clock speed 6000 kHz > Info : JTAG tap: feroceon.cpu tap/device found: 0x49602093 (mfg: 0x049, part: > 0x9602, ver: 0x4) > Info : Embedded ICE version 12 > Error: unexpected Feroceon EICE version signature And the target seems to halt (no reaction on the U-boot serial console) but still appears running in the telnet interface, and still cannot be halted Note that if I then do a ^C and launch openOCD again, the "Unexpected Feroceon EICE version signature" message does not appear again. Amicalement, -- Albert. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
