OpenOCD and DM365

Hello,

This post has already been posted on TI’s website but I think it equally concerns an openOCD issue.

I have just built my custom DM365 (300Mhz with same DDR and NAND Flash as the EVDM) board and I’m at the point where I need to debug it. I am using Olimex ARM-USB-OCD debugger connected trough USB to my Mac computer (runs like Linux with the latest OCD version).

When I run openocd command, here is an error I get:

Open On-Chip Debugger 0.4.0-rc2-dev-00005-gfa1cfc2 (2010-02-16-17:32)
Licensed under GNU GPL v2
For bug reports, read
    http://openocd.berlios.de/doc/doxygen/bugs.html
1500 kHz
RCLK - adaptive
fast memory access is enabled
dcc downloads are enabled
trst_only separate trst_push_pull
CS0 NAND
Info : device: 4 "2232C"
Info : deviceID: 364511235
Info : SerialNumber: ? A
Info : Description: Olimex OpenOCD JTAG A
Info : RCLK (adaptive clock speed) not supported - fallback to 1500 kHz
Info : JTAG tap: dm365.jrc tap/device found: 0x8b83e02f (mfg: 0x017, part: 0xb83e, ver: 0x8)
Info : JTAG tap: dm365.etb enabled
Info : JTAG tap: dm365.arm enabled
Info : Embedded ICE version 15
Error: unknown EmbeddedICE version (comms ctrl: 0xffffffff)
Info : dm365.arm: hardware has 2 breakpoint/watchpoint units
Warn : ETMv2+ support is incomplete
Info : ETM v16.15
Segmentation fault

I was wondering how to debug that thing?

I checked the connections and the voltage seem alright: EMU0 and EMU1 are pulled up at 3.3V, RST is pulled up too and TRST is pulled down.

Thanks,

Mike

hey,

I am out of my depth with openOCD, debugging, and probably that device you’re using, but I’ll give it a whirl whilst I finish my coffee.

The error ‘embedded ICE version 15’ Is there any way you can find out exactly what version of the embedded ICE that chip is using? I know it sounds obvious, but as that is the first error… as it picks up the tap ID, I assume your hardware can happily read bits from your target at the jtag speed you are using. Although, since I’m a hardware guy, I’m always suspicious of clock skew, so I tend to slow things down to a crawl for testing.

What is your config file your using? And are you using a specific target config file for this device?

As I said, I’m pretty much out of my depth, but who knows, maybe you can bounce idea’s off a noob and find the solution?