> THat MCR thing looks odd, but also:
Hmm ... Why odd?

> > Open On-Chip Debugger 0.4.0-rc1-dev-00118-gdab9297-dirty (2010-01-26-09:08)
> 
> "git show dab9297" says more or less "what????" ... looks like you have some
> nostandard patches in your git tree.
Nothing interesting. My local commit with changes in the NAND-flash driver.

> Does this problem reproduce with mainline code?
Yes:
---
[imp...@kb33 openocd]$ src/openocd -f /home/impatt/openocd.cfg
Open On-Chip Debugger 0.4.0-rc1-dev-00151-g3036588 (2010-01-27-09:33)
For bug reports, read
        http://openocd.berlios.de/doc/doxygen/bugs.html
jtag_nsrst_assert_width: 10
jtag_nsrst_delay: 50
jtag_ntrst_assert_width: 10
jtag_ntrst_delay: 10
Warn : imx35.sdma: nonstandard IR value
Warn : imx35.sdma: nonstandard IR mask
trst_and_srst separate srst_gates_jtag trst_open_drain srst_open_drain
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.sdma does not have IDCODE
Info : JTAG tap: imx35.sjc 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
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.sdma does not have IDCODE
Info : JTAG tap: imx35.sjc tap/device found: 0x0882601d (mfg: 0x00e, part: 
0x8826, ver: 0x0)
Info : found ARM1136
Warn : imx35.cpu: ran after reset and before halt ...
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000001d3 pc: 0xa006c930
Error: jim_mcrmrc: no command context
---


-- 
Regards,
Alexei Babich, circuit design engineer, Rezonans plc., Chelyabinsk, Russia
http://www.rez.ru
Jabber ID: [email protected]
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to