ARM-USB-OCD, SAM7-P256, Windows 7,

Development Boards MicroMod
1

I’m getting the following error:

Error: unable to open ftdi device: device not found

I’ve looked but if this topic is resolved elsewhere, a pointer is appreciated.

Here is my hardware

o Olimex SAM7-P256 development board, it has one AT91SAM7S256 processor

o Olimex ARM-USB-OCD JTAG adapter

I used the CD provided with the ARM-USB-OCD and followed the howto

document from Olimex to install the drivers and did so on 32 bit Windows 7

as well as 64 bit Windows 7. I checked the device manager and it appears

that the drivers are all properly installed.

I’m using Freddie Chopin’s builds of openocd version 0.4 on 32 bit Windows 7

and openocd version 0.5 on 64 bit Windows 7. I entered the given example

autoprobe configuration code as ‘probe.cfg’.

source [find interface/olimex-arm-usb-ocd.cfg]

reset_config trst_and_srst

jtag_rclk 8

I get the error on both the Windows 7 platforms. On a Windows XP machine

the board is detected.

Thanks;

2

hello?

3

The kind folks at Olimex told me to get the latest online. I’m not sure what happened, but I was able to update the drivers using the Drivers provided, and now Freddie’s 0.5.0 build of openocd can access the ARM-USB-OCD JTAG device and the COM port is still there.

http://olimex.com/dev/soft/arm/JTAG/Ope … e_v1.1.zip

Onto the next hurdle…

Jonathan

4

Things did go well with the 64 Bit Windows 7 machine, but not the 32 Bit Windows 7 machine. The symptoms? In the device manager I see an entry for “libusb-win32 devices” which contains two “Olimex OpenOCD ARM-USB-USB” devices. This is a different situation. I’m guessing that libusb was installed. I’m not sure what to do next…