On Wed, May 9, 2012 at 1:36 PM, Xiaofan Chen <[email protected]> wrote:
> 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
>
> ++++++++++++++
> 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
>>
>> These errors highlight the need for a new driver. It's not
>> about performance.
>
> Unfortunately both have the same problem.
>
Impossible. My driver doesn't print that message, it's only in ft2232.c.
andreas@naven:~/develop/openocd$ grep -r "read enough bytes" .
../src/jtag/drivers/ft2232.c: LOG_ERROR("couldn't read enough bytes
from "
I'm not sure what's happening, but you're still using the old driver.
/Andreas
------------------------------------------------------------------------------
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
