Full openocd support for L138 ARM-side

Thanks for this work - it's very timely for me - I'm new to openocd, but I'm just about to start debugging a new l138 board which is modeled after the zoom evm board.

Is your latest work in the sourceforge git? I just did a clone, but when I run it against my zoom evm board and run "scan_chain" I get the following output - I'm assuming the zeroes for idcode on the omapl138.arm line are not good.  I'd appreciate any hints about how to get started.

(using a flyswatter interface via ft2232_libftdi, by the way)

Thanks,

Pace

Open On-Chip Debugger 0.5.0-dev-00583-ge7b2958 (2010-11-09-08:18)
Licensed under GNU GPL v2
For bug reports, read
    http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
RCLK - adaptive
fast memory access is enabled
dcc downloads are enabled
force hard breakpoints
use of EmbeddedICE dbgrq instead of breakpoint for target halt enabled
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
Info : RCLK (adaptive clock speed) not supported - fallback to 1500 kHz
Info : JTAG tap: omapl138.jrc tap/device found: 0x0b7d102f (mfg: 0x017, part: 0xb7d1, ver: 0x0)
Info : JTAG tap: omapl138.etb enabled
Info : JTAG tap: omapl138.arm enabled
Info : Embedded ICE version 6
Info : omapl138.arm: hardware has 2 breakpoint/watchpoint units
Info : ETM v1.3
Info : accepting 'telnet' connection from 4444
   TapName             Enabled  IdCode     Expected   IrLen IrCap IrMask
-- ------------------- -------- ---------- ---------- ----- ----- ------
 0 omapl138.etb           Y     0x00000000 0x2b900f0f     4 0x01  0x0f
 1 omapl138.arm           Y     0x00000000 0x07926001     4 0x01  0x0f
 2 omapl138.jrc           Y     0x0b7d102f 0x0b7d102f     6 0x01  0x3f

You're very welcome. 

I haven't tried to use those da850 board scripts with a recent git version. What I have done is checkout from the git repo and point a released version of openocd at the scripts from the repo. 

The da850 board script should be available in that repo as of the 9th of August 2009 [1].

$openocd -v

Open On-Chip Debugger 0.3.1 (2010-01-18-18:43)
[...]
$cd ~/src
$git clone git://repo.or.cz/openocd.git
$openocd -s ~/src/openocd/tcl -f /usr/share/openocd/scripts/interface/olimex-jtag-tiny.cfg -f ~/src/openocd/tcl/board/da850evm.cfg -f ~/src/openocd-local.cfg
Open On-Chip Debugger 0.3.1 (2010-01-18-18:43)
$URL$
For bug reports, read
        http://openocd.berlios.de/doc/doxygen/bugs.html
RCLK - adaptive
fast memory access is enabled
dcc downloads are enabled
force hard breakpoints
use of EmbeddedICE dbgrq instead of breakpoint for target halt enabled
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
Info : RCLK (adaptive clock speed) not supported - fallback to 1500 kHz
Info : JTAG tap: omapl138.jrc tap/device found: 0x0b7d102f (mfg: 0x017, part: 0xb7d1, ver: 0x0)
Info : JTAG tap: omapl138.etb enabled
Info : JTAG tap: omapl138.arm enabled
Info : Embedded ICE version 6
Info : ETM v1.3
[...]
Info : accepting 'telnet' connection from 0
     TapName            | Enabled |   IdCode      Expected    IrLen IrCap  IrMask Instr     
---|--------------------|---------|------------|------------|------|------|------|---------
 0 | omapl138.etb       |    Y    | 0x00000000 | 0x2b900f0f | 0x04 | 0x01 | 0x0f | 0x0f
 1 | omapl138.arm       |    Y    | 0x00000000 | 0x07926001 | 0x04 | 0x01 | 0x0f | 0x0c
 2 | omapl138.jrc       |    Y    | 0x0b7d102f | 0x0b7d102f | 0x06 | 0x01 | 0x3f | 0x3f 

Where ~/src/openocd-local.cfg contains only 'gdb_memory_map disable' [2].

I also have the zeroes for IdCode and I am able to successfully debug u-boot and the linux kernel using the olimex-jtag debugger.

If you have further problems or questions about openocd I reccomend using the openocd mailing list; there are people there that know much more about openocd than I do. 

Best Regards,

Ben Gardiner

[1] http://repo.or.cz/w/openocd.git/commit/91305bfa7f550c96b967008c1512864cffdaa52a
[2] http://comments.gmane.org/gmane.comp.debugging.openocd.devel/13873

Ben Gardiner said:

Can someone confirm that the cfg files in the patch are correct?

How should I proceed to get full configuration-on-reset support for the da850 like that which already exists for the dm365evm [2] ? Can someone provide existing openocd cfg files or procedures in another format from which I can base further work?

TI Support, 

Any chance of getting help regarding my queries in the original post?

Hi Ben,

I'm finding myself embarking on an effort to bring this kind of functionality to the OMAP-L138 target.  I know this post is kind of old, but did you already go down this road yourself?  Maybe we can combine efforts?

Ben and Benjamin,

did you get this topic any forward?