Ok, I’ve got an AT91SAM7S256 device and an Xverve Signalyzer. Things are working with some older versions of openocd that we had lying around, so I trust that the device and the Signalyzer are working (I’m able to flash with an older SVN version). I need to move up to the 0.1.0 release for various reasons and to do so I had to redo the config file since the syntax was all different. But it can’t open the FTDI device now.
Command line output:
$ openocd -f ~/dev/at91sam7s256-signalyzer.cfg
Open On-Chip Debugger 0.1.0 (2009-01-22-11:22) Release
BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
$URL: https://kc8apf@svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.1.0/src/openocd.c $
Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 456:
My config file (taken directly from http://openocd.berlios.de/doc/Simple-Co … tion-Files)
source [find interface/signalyzer.cfg]
# Change the default telnet port...
telnet_port 4444
# GDB connects here
gdb_port 3333
# GDB can also flash my flash!
gdb_memory_map enable
gdb_flash_program enable
source [find target/sam7x256.cfg]
Looking at openocd running in strace it seems that it is trying to open each of the USB devices on my system, including the correct one, and then saying it can’t find the device. Is my config file ok? I’m I invoking openocd correctly? Thanks.