Holger Freyther wrote: > On Thursday 27 August 2009 07:04:22 you wrote: >> Holger Freyther wrote: >>> Hey, >>> >>> today Matt Hsu and me sat together to look into why OpenOCD does not work >>> on the beagle board. We have found and fixed some issues with the code, >>> it should make it more robust and we have fixed the root cause for us. >>> >>> cortex_a8_dap_read_coreregister_u32 only returned 0x0 for the registers, >>> this was due the instruction written to the ITR register was not >>> executed. We will have to enable bit 13 of DSCR to enable the execution >>> of ITR. >>> >>> The attached patch series fixes the problem for me and matt. The patches >>> were done in teamwork.. >> Have you done this with or without Dave's tck_100 patch applied? That >> is, to test this (now applied, thanks!) patch series, do we have to >> additionally apply Dave's tck_100 patch? > > All the patches were developed on top of the latest svn version, so I think > we > were running without Dave's patch.
Ok. So short status update (and a question, see below): Status: Using r2643 without any additional patches, it basically seems to work :) -- 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-27-16:18) svn:2643 $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 Error: JTAG communication failure: check connection, JTAG interface, target power etc. Error: trying to validate configured JTAG chain anyway... ... -- cut -- -- cut -- > telnet localhost 4444 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger > omap3_dbginit JTAG communication failure: check connection, JTAG interface, target power etc. trying to validate configured JTAG chain anyway... 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 | 0x00000000 | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f > halt target state: halted target halted in ARM state due to debug-request, current mode: Supervisor spsr_svc: 0x400001d3 pc: 0x80e87dcc MMU: disabled, D-Cache: disabled, I-Cache: enabled > poll background polling: on TAP: omap3530.dap (enabled) target state: halted target halted in ARM state due to debug-request, current mode: Supervisor spsr_svc: 0x400001d3 pc: 0x80e87dcc MMU: disabled, D-Cache: disabled, I-Cache: enabled > resume > poll background polling: on TAP: omap3530.dap (enabled) target state: running > soft_reset_halt requesting target halt and executing a soft reset Target omap3.cpu does not support soft_reset_halt > -- cut -- -> "soft_reset_halt" does give a reasonable error message now, doesn't crash any more -> "invalid mode value encountered" is gone now -> It seems to work without Dave's tck100 patch [1], but this results in "JTAG communication failure ...". So we still need anything like this. One question (request?): Everybody already working with this, could you please send working stuff (commands) in format like above (i.e. exact command syntax and output). I'd like to update the documentation [2] and for this collect what is working how. Having a short intro (log?) using this with gdb (and Eclipse??) would be nice, too! Many thanks and best regards Dirk [1] https://lists.berlios.de/pipermail/openocd-development/2009-August/010110.html [2] http://elinux.org/BeagleBoardOpenOCD _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
