Trouble with Luminary LM3S811 Eval on Linux

Development Boards MicroMod
1

Board: Luminary (pre-TI) LM3S811 eval board

OS: Ubuntu Linux Karmic Koala

OpenOCD: the version that comes with Karmic – says its “Open On-Chip Debugger 0.2.0-in-development (2009-06-30-01:11) svn:r2403”

Problem: I run

openocd -f /usr/share/openocd/scripts/target/lm3s811.cfg -f /usr/share/openocd/scripts/interface/luminary.cfg

and it says:

Open On-Chip Debugger 0.2.0-in-development (2009-06-30-01:11) svn:r2403

BUGS? Read /usr/share/doc/openocd/BUGS

$URL: http://svn.berlios.de/svnroot/repos/ope … /openocd.c $

500 kHz

jtag_nsrst_delay: 100

jtag_ntrst_delay: 100

Error: unable to open ftdi device: device not found

Runtime error, file “command.c”, line 469:

Web searches on “unable to open ftdi device: device not found” don’t seem to find anything to the point.

The device shows up when I do ‘lsusb’, the config file has PID and VID that matches what shows up in lsusb, but openocd can’t seem to see it.

Running openocd under ‘sudo’ doesn’t help.

Putting a file under ‘rules.d’ to give permissions to the port don’t seem to make a difference.

Clues? Clues? Clues for the clueless?

2

Fixed!

The processor is an old one – processor version 2 instead of 3, and the FTDI chip appears to have a different tag line than OpenOCD expects. In interface/luminary-lm3s811.cfg I changed

ft2232_device_desc “LM3S811 Evaluation Board A”

to

#ft2232_device_desc “LM3S811 Evaluation Board A”

then in target/lm3s811.cfg I changed

set _CPUTAPID 0x3ba00477

to

set _CPUTAPID 0x2ba00477

And it talks!

Now I need to obtain a Gdb/insight pair that works…