> If you like you can try it your own: Configure recent trunk (1875) with > --enable-dummy and then > > openocd -s lib/openocd/ -f interface/dummy.cfg -f board/ti_beagleboard.cfg > > This will result in > > -- cut -- > Open On-Chip Debugger 0.2.0-in-development (2009-05-21-19:06) svn:1875 > > BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS > > $URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $ > Warn : JTAG command queued, while TRST is low (TAP in reset) > current endstate: RUN/IDLE > Warn : Tap/Device does not have IDCODE > Error: JTAG tap: omap3.jrc got: 0x00000000 (mfg: 0x000, part: > 0x0000, ver: 0x0) > Error: JTAG tap: omap3.jrc expected 1 of 1: 0x0b7ae02f (mfg: 0x017, part: > 0xb7ae, ver: 0x0) > Error: trying to validate configured JTAG chain anyway... > Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0xFF. > tap=omap3.jrc pos=0 expected 0x1 got 3 > Warn : Could not validate JTAG chain, continuing anyway... > openocd: jtag.c:889: interface_jtag_add_dr_scan: Assertion `field == > out_fields + scan->num_fields' failed. > -- cut -- >
From what I can tell this fails because at the point of the call omap3.jrc is enabled but not omap3.cpu. The old code in jtag.c will silently ignore this. If this is indeed the error then this underscores the need to even further strengthen the checks because the error should have been caught in the earlier jtag_add_ir_scan() which also tried to address a TAP that is not enabled. Michael _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
