On Wed, May 9, 2012 at 10:06 AM, Xiaofan Chen <[email protected]> wrote:
>> Just a check... You're using the same board config file both times.
>> Are you changing it to use the ftdi driver instead of the old ft2232?
>> Both can be configured in the same OpenOCD binary and only the
>> configuration files select which one to use. There's a complete new
>> set of files in the interface/ftdi/ subdir that selects my driver
>> instead of the old one.
>
> I installed the official version to /usr/local and the mpsse version
> to ~/bin so that I can compared the two. But now I know the problem.
> I thought I edited the configure file to add --enable-ftdi for the mpsse
> version but I just checked and I did not. And then I was using the same
> board file without creating a version of the board file for the mpsse
> (use interface/ftdi/luminary.cfg instead of interface/luminary.cfg).
>
> So I need to redo the build and the test. Sorry about the noise.
>
I just tested with TI/Luminary EK-LM3S1968 and here
are the results.
There are actually no differences at all.
mymacmini:build_mpsse xiaofanc$ cat myconfig_git.sh
LDFLAGS="-L/usr/local/lib -lusb-1.0" ../configure
--enable-maintainer-mode --prefix=/Users/xiaofanc/bin --enable-jlink
--enable-ftdi --enable-ft2232_libftdi --enable-stlink --disable-werror
mymacmini:board xiaofanc$ cp ek-lm3s1968.cfg ek-lm3s1968_mpsse.cfg
mymacmini:board xiaofanc$ nano ek-lm3s1968.cfg
mymacmini:board xiaofanc$ pwd
/Users/xiaofanc/bin/share/openocd/scripts/board
mymacmini:board xiaofanc$ diff ek-lm3s1968.cfg ek-lm3s1968_mpsse.cfg
13c13
< source [find interface/ftdi/luminary.cfg]
---
> source [find interface/luminary.cfg]
+++++++++
MPSSE version:
mymacmini:lm3s1968 xiaofanc$ ~/bin/bin/openocd -f board/ek-lm3s1968_mpsse.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: couldn't read enough bytes from FT2232 device (78 < 81)
Error: couldn't read from FT2232
Error: Trying to use configured scan chain anyway...
Warn : Bypassing JTAG setup events due to errors
Info : lm3s1968.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'telnet' connection from 4444
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x81000000 pc: 0x000011a8 msp: 0x200000f0
500 kHz
auto erase enabled
wrote 262144 bytes from file demo4.bin in 8.335512s (30.712 KiB/s)
1000 kHz
flash 'stellaris' found at 0x00000000
auto erase enabled
wrote 262144 bytes from file demo4.bin in 5.256349s (48.703 KiB/s)
2000 kHz
auto erase enabled
wrote 262144 bytes from file demo4.bin in 4.357144s (58.754 KiB/s)
3000 kHz
auto erase enabled
wrote 262144 bytes from file demo4.bin in 4.348687s (58.868 KiB/s)
++++++++++++++
Non-MPSSE version
mymacmini:lm3s1968 xiaofanc$ openocd -f board/ek-lm3s1968.cfg
Open On-Chip Debugger 0.6.0-dev-00543-g908ee4d (2012-05-05-20:28)
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: couldn't read enough bytes from FT2232 device (51 < 81)
Error: couldn't read from FT2232
Error: Trying to use configured scan chain anyway...
Warn : Bypassing JTAG setup events due to errors
Info : lm3s1968.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'telnet' connection from 4444
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x000011ae msp: 0x200000f0
flash 'stellaris' found at 0x00000000
500 kHz
auto erase enabled
wrote 262144 bytes from file demo4.bin in 8.341610s (30.690 KiB/s)
1000 kHz
auto erase enabled
wrote 262144 bytes from file demo4.bin in 5.227277s (48.974 KiB/s)
2000 kHz
auto erase enabled
wrote 262144 bytes from file demo4.bin in 4.353256s (58.807 KiB/s)
3000 kHz
auto erase enabled
wrote 262144 bytes from file demo4.bin in 4.346641s (58.896 KiB/s)
^C
>> mymacmini:lm3s1968 xiaofanc$ openocd -f board/ek-lm3s1968.cfg
>> Open On-Chip Debugger 0.6.0-dev-00543-g908ee4d (2012-05-05-20:28)
>> 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: couldn't read enough bytes from FT2232 device (70 < 81)
>> Error: couldn't read from FT2232
>> Error: Trying to use configured scan chain anyway...
>
> These errors highlight the need for a new driver. It's not
> about performance.
Unfortunately both have the same problem.
BTW, I encountered quite some stability issue with
0.6.0-dev-00543-g908ee4d (program hang) which
the later 0.6.0-dev-00543-g908ee4d and current git
do not have. Maybe you want to rebase the patches
on current git.
--
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