Debugging for ARM target, "invalid command name "fast""

Development Boards MicroMod
1

Hello!

I am able to debug using OpenOCD and GDB, but it is a bit slow, and the debugger advises me as follows:

NOTE! DCC downloads have not been enabled, defaulting to slow memory writes. Type 'help dcc'.
NOTE! Severe performance degradation without fast memory access enabled. Type 'help fast'.

I checked with the OpenOCD user’s guide, and altered my call to OpenOCD as per instructions from the manual:

openocd -c "fast enable" -c "interface dummy" -f interface/jtagkey.cfg -f target/lpc2378.cfg

This does not work, I get the error message:

Runtime error, file "command.c", line 650:
    invalid command name "fast"

Does anybody have any idea why this is happening?

–j.l.

2

Additional information:

I’m using OpenOCD v0.4.0 on a Windows XP system.

–j.l.

3

Just tested on my install.

fast enable is not recognized, but:

help fast

arm7_9 fast_memory_access [‘enable’|‘disable’]

use fast memory accesses instead of slower but potentially safer

accesses (command valid any time)

fast_load

loads active fast load image to current target - mainly for profiling

purposes

fast_load_image filename address [‘bin’|‘ihex’|‘elf’|‘s19’] [min_address [max_length]]

Load image into server memory for later use by fast_load; primarily

for profiling (command valid any time)

so I guess you should try

arm7_9 fast_memory_access enable

4

Ah yes, thank you Mox, I will try it. But it looks as though the manual needs updating on this point…

5

Yep, adding

monitor arm7_9 fast_memory_access enable

to the gdb init script solved the issue. Thanks!

6

:smiley:

7

Hi ,

Also you could try to install the updated Amontec JTAGkey Driver for Windows.

http://www.amontec.com/download/amontec … 091124.zip

http://www.amontec.com/download/amontec … 091124.zip

This new JTAGkey driver is certified and signed by Microsoft WHQL program.

Microsoft Windows 2000

Microsoft XP 32 bits and 64 bits

Microsoft VISTA 32 bits and 64 bits

Microsoft WINDOWS 7 32 bits and 64 bits

Microsoft serveur 2008 64 bits

It could help you to reach better performance.

Regards,

Laurent Gauch

http://www.amontec.com

http://www.amontec.com

8

Thank you Laurent for your reply!

I did use the Amontec drivers, but I kept getting an error message from OpenOCD saying, in essence, that it can’t connect to the device. The driver supplied with OpenOCD 0.4.0 from freddiechopin works without trouble. I’m assuming this problem stems from something amiss with my setup, but I have not been successful in sorting it out. Shouldn’t it just be a case of installing the driver and go? Would there be a difference between JTAG key and JTAG key 2? There could, I suppose, be a speed advantage with using the Amontec driver, but rather a slow driver over one that doesn’t work…

Cheers!

–j.l.

9

It’s said in milions of places - OpenOCD can be compiled for libusb-win32 or for ftd2xx. My compilation uses libusb-win32 drivers, amontec drivers use ftd2xx - it’s just impossible to “match” those. You need to recompile OpenOCD yourself to use that drivers. The flashing will be a_bit - 2x faster (depending on lots of factors), so if the flashing takes less than 10s and you don’t flash chips for a living there’s no point in trying to recompile OpenOCD if you don’t know how…

It’s a pity Amontec didn’t certify libusb-win32 drivers, knowing that currently OpenOCD cannot be distributed with ftd2xx…

4/3!!

10

Mmm, yes quite. I suppose one could use the package of OpenOCD that Amontec supplies to their customers (I’m talking about the sdk4arm package here), but it hasn’t been updated for over three years?