Re: [Fx2lib-devel] Trouble running speed.py

[Dennis M. <de...@ub...>]

Chris McClelland wrote:
> Hi guys,
>
> At the weekend I built a little board with a 7C68014A-56PVXC on it. It 
> works fine from Windows using the Keil toolchain and all the Cypress 
> tools. But on Linux/fx2lib I'm having trouble.
>   
Is that a Typo?  7c68014a.  I'm not sure if there are differences 
between parts or if you have the 7c68013a.
> I got the latest fx2lib and libusb code via git, the sdcc toolchain 
> yesterday, and the CyStream firmware (from 
> http://allmybrain.com/2009/04/14/fx2-cystream-throughput-test-with-sdcc-and-fx2lib/).
>
> I attached an example session, from the time I plug in the board. It 
> looks like it enumerates correctly as the bootloader and renumerates 
> correctly as the CyStream firmware. But once speed.py has failed, 
> subsequent lsusb listings fails with "can't get device qualifier: 
> Connection timed out".
>
> Can anyone see if I'm doing anything silly?
>   
I think what is happening is when you run speed.py, the device is 
getting into a state where it is no longer handling vendor commands.  
Any type of loop that doesn't ever exit back to the main loop can cause 
this.  I'm not sure what could be causing that in the stream firmware 
but there is some chance the code I posted had a flaw in it.  You're 
welcome to zip up your firmware and I could try it on my board to see if 
I get a different result. 

Have you tried CyStream.exe on Windows but with the SDCC compiled 
firmware?  To do that I either had to load the firmware with the device 
on windows, load the firmware onto a prom, or use a virtual machine. 
(VMware handles USB devices pretty reasonably.)

One last thing, on my machine, with libusb-1.0, I had to use a version 
from source.  I don't know what version Gentoo is at, but their 1.0 
released code had a pretty big bug that was fixed later on in the git 
version.

-Dennis