On Thu, May 10, 2012 at 4:18 AM, Andreas Fritiofson
<[email protected]> wrote:
> Using the built-in adapter, you only get ones, but with the external
> adapter you can at least read the idcode correctly. I've taken a look
> at the schematics of the EK-LM3S1968 board and it seems like the I/O
> config and init in interface/ftdi/luminary{,_icdi}.cfg is wrong. It
> initializes SRSTN (FT2232 ADBUS5) as an input which
> makes the internal signal between the FT2232 and the
> CPLD floating. Also, it uses the
> FTDI pin as an open-drain output as if it directly controls target
> nSRST even though it's buffered with a CPLD. Strangely, the layout
> code in the old driver does the same thing, that's where I copied the
> info from. Can you try the attached luminary.cfg to see if you can at
> least read the idcode?
Now it actually generate a segfault. But I think you are getting
closer.
mymacmini:lm3s1968 xiaofanc$ ~/bin/bin/openocd -f
~/bin/share/openocd/scripts/board/ek-lm3s1968_mpsse_icdi.cfg
Open On-Chip Debugger 0.6.0-dev-00448-gac053a2 (2012-05-09-19:01)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
500 kHz
Info : clock speed 500 kHz
Error: interface can't tri-state 'nSRST'
Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg:
0x23b, part: 0xba00, ver: 0x3)
Segmentation fault: 11
--
Xiaofan
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
