I don't have a functional state to create a patch, but it appears to work a little better now. The "reg" command is returning values which make sense instead all 0 as before.
I just change it: # Per ARM: DDI0211J_arm1136_r1p5_trm.pdf - the ARM 1136 as a 5 bit IR register jtag newtap $_CHIPNAME cpu -irlen 5 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID # No IDCODE for this TAP jtag newtap $_CHIPNAME whatchacallit -irlen 4 -ircapture 0 -irmask 0xf -expected-id 0x0 # Per section 40.17.1, table 40-85 the IR register is 4 bits # But this conflicts with Diagram 6-13, "3bits ir and drs" jtag newtap $_CHIPNAME smda -irlen 5 -ircapture 0x1 -irmask 0xf -expected-id $_SDMATAPID But there is a problem during IR valitation: # openocd -f dicarlo.cfg -f imx31.cfg Open On-Chip Debugger 1.0 (2009-01-10-15:42) svn:1312 BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ jtag_speed: 10 Info : JTAG tap: imx31.sjc tap/device found: 0x2b900f0f (Manufacturer: 0x787, Part: 0xb900, Version: 0x2) Info : JTAG Tap/device matched Info : JTAG tap: imx31.cpu tap/device found: 0x07b3601d (Manufacturer: 0x00e, Part: 0x7b36, Version: 0x0) Info : JTAG Tap/device matched Warn : Tap/Device does not have IDCODE Info : JTAG Tap/device matched Info : JTAG tap: imx31.smda tap/device found: 0x2190101d (Manufacturer: 0x00e, Part: 0x1901, Version: 0x2) Info : JTAG Tap/device matched Error: Error validating JTAG scan chain, IR mismatch, scan returned 0x0c2011 Error: Could not validate JTAG chain, continuing anyway... Info : found ARM1136 Warn : no tcl port specified, using default port 6666 Info : Debug entry: JTAG HALT Info : r0 004058d8 (INVALID) Info : r1 0000f803 (INVALID) Info : r2 000000a1 (INVALID) Info : r3 1fffff4c (INVALID) Info : r4 00000001 (INVALID) Info : r5 000186a0 (INVALID) Info : r6 00000000 (INVALID) Info : r7 1fffc834 (INVALID) Info : r8 00000000 (INVALID) Info : r9 00000001 (INVALID) Info : r10 00000002 (INVALID) Info : r11 000000f0 (INVALID) Info : r12 000000a1 (INVALID) Info : sp 1fffff3c (INVALID) Info : lr 000186a0 (INVALID) Info : pc 004058d0 (INVALID) Info : cpsr 200001d3 (INVALID) Info : dscr 00006003 (INVALID) target state: halted Best Regards, Alan On Tue, Jan 13, 2009 at 9:07 PM, Øyvind Harboe <oyvind.har...@zylin.com> wrote: > patch? > > On Tue, Jan 13, 2009 at 9:53 PM, Alan Carvalho de Assis > <acas...@gmail.com> wrote: >> Hi Oyvind, >> >> On Mon, Jan 12, 2009 at 8:18 PM, Øyvind Harboe <oyvind.har...@zylin.com> >> wrote: >>>> I am not familiar to BSDL file, then I need to study more about it to >>>> verify if our imx31.cfg file is correct. >>>> Any material about how to decode this kind of file is welcome. >>> >>> The primary information I need at this point is a crisp explanation >>> of what the JTAG chain contains. Of course I could read this up >>> in the datasheets, but I'd rather concentrate the time I have available >>> on OpenOCD specific problems rather than becoming an imx31 expert. >>> >> >> I am searching it, but it is not easy to find. I can validate one >> device from BSDL: >> >> "0010" & -- Version >> "000110" & -- Design Center Number >> "0100000001" & -- Sequence Number >> "00000001110" & -- Manufacturer Identity >> "1"; -- IEEE 1149.1 Requirement >> >> It is exactly the SDMATAPID 0x2190101d. But I think there is some >> error in your imx31.cfg because the IR Length for this device is 5 not >> 4 as defined in config file. >> >>> Thanks! >>> >> >> Best Regards, >> >>> -- >>> Øyvind Harboe >>> http://www.zylin.com/zy1000.html >>> ARM7 ARM9 XScale Cortex >>> JTAG debugger and flash programmer >>> >> >> Alan >> > > > > -- > Øyvind Harboe > http://www.zylin.com/zy1000.html > ARM7 ARM9 XScale Cortex > JTAG debugger and flash programmer > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
