ARM-USB-OCD and Atmel AT91RM9200

Development Boards MicroMod
1

Hello list,

i just installed my new ARM-USB-OCD.

I connected it to an Atmel AT91RM9200-EK Evaluation Board and tried to debug the sample application.

It thought it must be possible to get a memory or register view although the Hardware mismatches, it’s an ARM9 too.

If i try to debug, this message appears:

Info: openocd.c:73 main(): Open On-Chip Debugger (Revision 62)

Warning: arm7_9_common.c:669 arm7_9_assert_reset(): srst resets test logic, too

And if i click the “Bug” Button the launch stops at 55% and a timeout appears.

What can i do to get this working ?

THX

Thomas

2

Hello Thomas,

the OpenOCD should work with an AT91RM9200 without problems. Could you please post the .cfg file you’re using?

Regards,

Dominic

3

Dominic:
Hello Thomas,

the OpenOCD should work with an AT91RM9200 without problems. Could you please post the .cfg file you’re using?

Regards,

Dominic

Here is my .cfg file, based on the lpc demo configuration:

#daemon configuration

telnet_port 4444

gdb_port 3333

#interface

interface ftd2xx

ftd2xx_device_desc “Olimex OpenOCD JTAG A”

ftd2xx_layout olimex_jtag

#ftd2xx_vid_pid 0x0403 0xcff8

ftd2xx_vid_pid 0x15ba 0x0003

jtag_speed 2

#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 0xe

#target configuration

daemon_startup reset

#target

#target arm7tdmi

#target arm7tdmi little run_and_halt 0 arm7tdmi-s_r4

target arm920t little reset_halt arm920t

4

Hello Thomas,

The log lines you’ve sent me “…srst resets test logic, too…” indicate that you had “reset_config … srst_pulls_trst” - guess you removed that, which is fine for an AT91RM9200.

The revision 62 distributed by Olimex is almost ancient - it got committed to SVN on May 22nd. You should upgrade to a more recent version, either compiling it yourself, or by using the binary package kindly provided by Michael Fischer at www.yagarto.de.

If your problem persists, please run the OpenOCD “-d -l ”, and send me the resulting log file together with the exact config file used (Dominic.Rath gmx.de).

Regards,

Dominic

5

Hi,

OpenOCD revisions still change too often (can’t be otherwise with so much different ARM cores and vendor specific implementations for the flash loading etc) and every time we run ARM-USB-OCD we put in the CD most recent version.

I’m thinking now for something like “dynamic” installation. i.e. somewhere at our server to place always up to date compiled OpenOCD and to make Upgrade program which when run to check the installed openOCD version against the most recent and to upgrade the OpenOCD automatically.

Do you guys ever did something like this?

Tsvetan

6

Or even try http://www.yagarto.de/ instead. It works better without the trailing full stop :wink:

All the best to one and all.