On Tuesday 19 January 2010, Alexei Babich wrote: > [imp...@kb33 openocd]$ src/openocd -f /home/impatt/openocd.cfg > Open On-Chip Debugger 0.4.0-rc1-dev-00118-gdab9297-dirty (2010-01-20-10:20) > 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 > Warn : imx35.whatchacallit: nonstandard IR value > Warn : imx35.whatchacallit: nonstandard IR mask > Error: Target not examined yet
You didn't provide your "openocd.cfg", but the usual case here is that you tried to do something too early. Like "nand probe" before "init", for example; that's something best done at the end of a reset-init event handler. > Info : clock speed 500 kHz > Info : JTAG tap: imx35.etb tap/device found: 0x2b900f0f (mfg: 0x787, part: > 0xb900, ver: 0x2) > Info : JTAG tap: imx35.cpu tap/device found: 0x07b3601d (mfg: 0x00e, part: > 0x7b36, ver: 0x0) > Info : TAP imx35.whatchacallit does not have IDCODE > Info : JTAG tap: imx35.sdma tap/device found: 0x0882601d (mfg: 0x00e, part: > 0x8826, ver: 0x0) > Info : found ARM1136 > Info : imx35.cpu: hardware has 6 breakpoints, 2 watchpoints > Warn : ETMv2+ support is incomplete > Info : ETM v3.1 That stuff is what happens with "init". So whatever you were doing too-early ... do it later. You can invoke "init" explicitly, if you like. - Dave > --- > > When I try to invoke target_read_u32(), I get a message in the log: Error: > 131 6 target.c: 1477 target_read_u32(): Target not examined yet > Can anyone suggest how to try to get rid of the error? > > Thank you. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
