Texas Intruments' DAVINCI DM355 and open OCD

Development Boards MicroMod
1

Hello everybody,

I’m working with the DM355 evaluation board and my code is already finished. Now I would like to debug it using a graphical interface. I think that OLIMEX-JTAG+OPENOCD+ECLIPSE+TI’s tools could work.

At this step I’m trying to configure openOCD. Let me show you my config. script:

#daemon configuration
telnet_port 4444
gdb_port 3333
#interface
interface parport
parport_port 0x378
parport_cable wiggler
jtag_speed 10
#use combined on interfaces or targets that can’t set TRST/SRST separately
reset_config trst_and_srst
#jtag scan chain
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag_device 4 0x1 0xf 0x0e
jtag_device 4 0x1 0xf 0x0e
jtag_device 6 0x1 0x03C 0x0e
#target configuration
daemon_startup reset
#target
target arm926ejs little reset_halt 1 arm926ejs
working_area 0 0x200000 0x4000 backup
#run_and_halt_time 0 5000
#flash configuration
#flash bank <chip_width> <bus_width> [driver_options …]
flash bank cfi 0x10000000 0x800000 2 2 0

Do you have a good config script for this processor in ICE mode or ETB+ARM+ICE mode?

I apologize for my English but I do not use to use it.

2

Have you had any success getting the DM355 eval board to work with the Olimex JTAG dongle and OpenOCD?

I’ve been trying to get the Olimex USB JTAG pod and OpenOCD v0.1.0 to work with the DM355 eval board.

I had been using this wiki page as a guide…

http://wiki.davincidsp.com/index.php?ti … mex_dongle

Likewise, I was using this page for advice on installing OpenOCD on Ubuntu v8.10:

http://openhardware.net/Embedded_ARM/OpenOCD_JTAG/

However, the problem appears to be that the DM355.cfg offered on davincidsp.com uses obsolete syntax. In particular, this is what I get using the DM355.cfg data provided with OpenOCD v0.1,0. Might anyone have tips for updating DM355.cfg syntax?

$ sudo openocd -f DM355.cfg

Open On-Chip Debugger 0.1.0 (2009-01-24-18:18) Release

BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS

$URL: https://kc8apf@svn.berlios.de/svnroot/r … /openocd.c $

OLD SYNTAX: DEPRECATED - translating to new syntax

jtag newtap CHIP TAP -irlen 4 -ircapture 0x1 -irvalue 0x0

Example: STM32 has 2 taps, the cortexM3(len4) + boundryscan(len5)

jtag newtap stm32 cortexm3 …, thus creating the tap: “stm32.cortexm3”

jtag newtap stm32 boundry …, and the tap: “stm32.boundery”

And then refer to the taps by the dotted name.

NEW COMMAND:

OLD SYNTAX: DEPRECATED - translating to new syntax

jtag newtap CHIP TAP -irlen 4 -ircapture 0x1 -irvalue 0x0

Example: STM32 has 2 taps, the cortexM3(len4) + boundryscan(len5)

jtag newtap stm32 cortexm3 …, thus creating the tap: “stm32.cortexm3”

jtag newtap stm32 boundry …, and the tap: “stm32.boundery”

And then refer to the taps by the dotted name.

NEW COMMAND:

OLD SYNTAX: DEPRECATED - translating to new syntax

jtag newtap CHIP TAP -irlen 6 -ircapture 0x1 -irvalue 0x0

Example: STM32 has 2 taps, the cortexM3(len4) + boundryscan(len5)

jtag newtap stm32 cortexm3 …, thus creating the tap: “stm32.cortexm3”

jtag newtap stm32 boundry …, and the tap: “stm32.boundery”

And then refer to the taps by the dotted name.

NEW COMMAND:

Runtime error, file “DM355.cfg”, line 24:

bad option “arm926ejs”: must be one of count, create, current, names, number, or types