On 08/07/13 19:45, Laszlo Papp wrote: > Forgot to mention, but the previous error occured with 0.7.0. This is > what I am getting with 0.6.1 and 0.5.0 while having the same set up and > configuring with --enable-ft2232_libftdi: > > >>>>>> > Info : 281 63 core.c:951 jtag_examine_chain_display(): JTAG tap: > omapl138.jrc tap/device found: 0x1b7d102f (mfg: 0x017, part: 0xb7d1, > ver: 0x1) > Warn : 282 63 core.c:951 jtag_examine_chain_display(): JTAG tap: > omapl138.jrc UNEXPECTED: 0x1b7d102f (mfg: 0x017, part: 0xb7d1, > ver: 0x1) > Error: 283 63 core.c:951 jtag_examine_chain_display(): JTAG tap: > omapl138.jrc expected 1 of 1: 0x0b7d102f (mfg: 0x017, part: 0xb7d1, > ver: 0x0) > Error: 284 63 core.c:1457 jtag_init_inner(): Trying to use configured > scan chain anyway... > Debug: 285 63 core.c:1208 jtag_validate_ircapture(): IR capture > validation scan > Debug: 286 65 core.c:1267 jtag_validate_ircapture(): omapl138.jrc: IR > capture 0x01 > Warn : 287 65 core.c:1480 jtag_init_inner(): Bypassing JTAG setup events > due to errors > <<<<<< > > Got a clue how to proceed? >
This is fixed in newer versions of OpenOCD, note added -ignore-version to tap declaration. jtag newtap $_CHIPNAME jrc -irlen 6 -irmask 0x3f -expected-id $_JRC_TAPID -ignore-version Cheers Spen ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
