On Mon, Sep 19, 2011 at 10:13 AM, Matt Reimer <mrei...@sdgsystems.com> wrote: > On Tue, Sep 13, 2011 at 9:28 AM, Oliver Döring <o.doer...@tu-bs.de> wrote: >> Hi, >> >> I'm having lots of problems with this Toradex board. >> >> I use a custom carrier board without JTAG buffers, so I connected my >> JTAG-USB directly to the Colibri FFC JTAG connector. My JTAG adapter is >> FT2232 based and uses the OOCDLink layout, which means it has NTRST and >> NSRST buffers with OE. I traced all the signals from the Colibri board to >> the JTAG adapters, everything looks ok. I looked at the signals with an >> (analogue) oscilloscope and saw the reset signals and pulses on TMS, TCK, >> TDI and TDO. >> >> However, here is what I get: >> >> OpenOCD startup: >>> >>> Open On-Chip Debugger 0.6.0-dev-00079-g4017af8-dirty (2011-09-11-23:08) >>> Licensed under GNU GPL v2 >>> For bug reports, read >>> http://openocd.berlios.de/doc/doxygen/bugs.html >>> Info : only one transport option; autoselect 'jtag' >>> 100 kHz >>> adapter_nsrst_delay: 260 >>> jtag_ntrst_delay: 250 >>> Info : colibri_pxa320.cpu: hardware has 2 breakpoints and 2 watchpoints >>> trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain >>> adapter_nsrst_delay: 800 >>> Info : clock speed 100 kHz >>> Info : JTAG tap: colibri_pxa320.cpu tap/device found: 0x7e642013 (mfg: >>> 0x009, part: 0xe642, ver: 0x7) >> >> Trying to halt the CPU: >>>> >>>> reset halt >>> >>> JTAG tap: colibri_pxa320.cpu tap/device found: 0x7e642013 (mfg: 0x009, >>> part: 0xe642, ver: 0x7) >>> Bad value '00' captured during DR or IR scan: >>> check_value: 0x02 >>> check_mask: 0x07 >>> JTAG error while writing DCSR >>> Bad value '00' captured during DR or IR scan: >>> check_value: 0x02 >>> check_mask: 0x06 >>> JTAG error while reading TX >>> error while polling TX register, reset CPU >>> target state: halted >>> target halted in ARM state due to undefined, current mode: User >>> cpsr: 0x00000000 pc: 0x00000000 >>> MMU: disabled, D-Cache: disabled, I-Cache: disabled >>>> >> >> When I try to resume, I get lots of those "Bad value '00' captured..." >> messages and eventually a "time out writing RX register". > > Is it a bug that xscale_read_dcsr() exits with the TAP in state > TAP_DRPAUSE? The attached patch seems to make the "Bad value '00'" > messages go away. > > If this patch looks correct I'll submit a proper patch to commit. > > Matt
Oops, forgot the patch. Matt
read_dcsr.patch
Description: Binary data
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
