Hi, I pulled out trunk 2604 and applied 4 patches. On my system, OpenOCD works the way Dirk email has described.
Best regards, James --- On Sun, 8/23/09, Dirk Behme <[email protected]> wrote: > From: Dirk Behme <[email protected]> > Subject: Re: [Openocd-development] OpenOCD + beagle > To: "David Brownell" <[email protected]>, > [email protected], "James Lin" <[email protected]> > Date: Sunday, August 23, 2009, 5:52 AM > David Brownell wrote: > > On Wednesday 19 August 2009, James Lin wrote: > > > >> Then I tried to apply the patch described in > >> http://lists.berlios.de/pipermail/openocd-development/2009-June/008256.html > >> > >> I don't know if this additional step was necessary > but it seemed > >> to get correct mfg, part, ver. > > > > So it *was* necessary. You seem to have had > better luck than I > > did, way back when I did that, in that you got that > without first > > forcing a reset. Right? > > > > Maybe an updated version of that patch should > merge... > > With the four patches in attachment (from [1] [2] [3]) on > top of recent OpenOCD r2604 with BeagleBoard: > > -- cut -- > > openocd -s lib/openocd/ -f interface/flyswatter.cfg -f > board/ti_beagleboard.cfg > Open On-Chip Debugger 0.3.0-in-development > (2009-08-22-08:37) svn:2604M > $URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $ > For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS > OLD SYNTAX: DEPRECATED - use jtag_khz, not jtag_speed > jtag_speed: 1 > Warn : huge IR length 38 > Info : clock speed 3000 kHz > Info : JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f > (mfg: 0x017, part: 0xb7ae, ver: 0x0) > Info : JTAG Tap/device matched > -- cut -- > > -- cut -- > > telnet localhost 4444 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > Open On-Chip Debugger > > omap3_dbginit > JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: > 0x017, part: 0xb7ae, ver: 0x0) > JTAG Tap/device matched > AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, > ap_tar 0x54011080 > SWJ-DP STICKY ERROR > Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080 > TargetName > Type Endian > TapName State > -- ------------------ ---------- ------ > ------------------ ------------ > 0* omap3.cpu > cortex_a8 little omap3530.dap > unknown > 0x54011314 00000003 > > .... > 0x54011314 00000001 > > .... > > scan_chain > TapName > | Enabled | IdCode > Expected IrLen IrCap IrMask > Instr > ---|--------------------|---------|------------|------------|------|------|------|--------- > 0 | omap3530.dsp | > n | 0x00000000 | 0x00000000 | 0x26 | > 0x25 | 0x3f | 0xffffffff > 1 | omap3530.dap | > Y | 0x00000000 | 0x0b6d602f | 0x04 | > 0x01 | 0x0f | 0x0a > 2 | omap3530.jrc | > Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 | > 0x01 | 0x3f | 0x3f > > halt > invalid mode value encountered > ... > invalid mode value encountered > target state: halted > invalid mode value encountered > ... > target halted in ARM state due to debug-request, current > mode: Illegal mode value > r0: 0xfffffff8 pc: 0x00000000 > MMU: disabled, D-Cache: disabled, I-Cache: disabled > > poll > background polling: on > TAP: omap3530.dap (enabled) > target state: halted > invalid mode value encountered > ... > target halted in ARM state due to debug-request, current > mode: Illegal mode value > r0: 0xfffffff8 pc: 0x00000000 > MMU: disabled, D-Cache: disabled, I-Cache: disabled > > resume > invalid mode value encountered > ... > > poll > background polling: on > TAP: omap3530.dap (enabled) > target state: running > > > > -- cut -- > > Having U-Boot running, halt and resume seem to work (but a > lot of invalid mode warnings). And yes, "soft_reset_halt" > still gives a segfault. > > What are the next steps which could be done with > BeagleBoard? I never attached gdb yet, so if anybody has > hints for this ... ;) > > I'd vote to apply the four patches in attachment. > > Then, the next steps would be to find the reason for > invalid mode message, the segfault and maybe fix the "OLD > SYNTAX: DEPRECATED - use jtag_khz, not jtag_speed" message > above? > > I would be happy to test all this ;) > > Best regards > > Dirk > > [1] > https://lists.berlios.de/pipermail/openocd-development/2009-June/008256.html > > [2] > http://lists.berlios.de/pipermail/openocd-development/2009-July/009652.html > > [3] > https://lists.berlios.de/pipermail/openocd-development/2009-August/010004.html > > -----Inline Attachment Follows----- > > > -----Inline Attachment Follows----- > > > -----Inline Attachment Follows----- > > > -----Inline Attachment Follows----- > > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
