Jump to content
  • 0

Atlys EZ-USB with cyusb.inf


willienpboys

Question

I am using my Atlys board as prototyping platform for EZ-USB2.0 upload/download using the slave fifos. The Adept2 API has problems for the streamioex example that's provided on the upload speed test side, i.e.

>StreamIOEx.exe -ds -us
Opened device: Atlys
Download speed test:
        512.00 Bytes    in 729.53 us    with 685.38 kBps
        1.00 kBytes     in 629.03 us    with 1.55 MBps
        2.00 kBytes     in 750.91 us    with 2.60 MBps
        4.00 kBytes     in 767.16 us    with 5.09 MBps
        8.00 kBytes     in 910.41 us    with 8.58 MBps
        16.00 kBytes    in 1.25 ms      with 12.50 MBps
        32.00 kBytes    in 1.75 ms      with 17.82 MBps
        64.00 kBytes    in 2.88 ms      with 21.73 MBps
        128.00 kBytes   in 5.26 ms      with 23.78 MBps
        256.00 kBytes   in 9.75 ms      with 25.64 MBps
        512.00 kBytes   in 19.99 ms     with 25.01 MBps
        1.00 MBytes     in 40.15 ms     with 24.90 MBps
        2.00 MBytes     in 77.69 ms     with 25.74 MBps
        4.00 MBytes     in 157.78 ms    with 25.35 MBps
        8.00 MBytes     in 305.69 ms    with 26.17 MBps
        16.00 MBytes    in 614.26 ms    with 26.05 MBps
        32.00 MBytes    in 1.24 sec     with 25.86 MBps
Upload speed test:
        512.00 Bytes    in 648.71 us    with 770.77 kBps
        1.00 kBytes     in 629.03 us    with 1.55 MBps
        2.00 kBytes     in 622.19 us    with 3.14 MBps
DstmIOEx API failed

I tried providing the (Vendor ID, Product ID) = (0x1443, 0x0007) for the Digilent USB interface to the USB chip manufacturer Cypress's cyusb.inf, but Windows 7 does not recognize the device. Is it possible to run the Digilent USB interface using the Cypress API?

Link to comment
Share on other sites

1 answer to this question

Recommended Posts

Hi Willienpboys,

There is a way to have it use the Cypress API but to do this could result in issues for you later on. Underneath where PROG is written on the silk screen is JP9. You would need to cut the trace at JP9. Doing this would eliminate the eeprom from communicating and the default Vendor ID, Product ID would be what is communicated. This would allow you to use the Cypress API. When you want to go back to having the eeprom you would need to jumper JP9. You would need to be aware that there is a potential for you to damage the eeprom using the board this way. 

cheers,

Jon

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...