USB low-full-high speed peripherals Forum Discussions

Hi,

I've a similar issue as described in thread:
https://community.infineon.com/t5/USB-superspeed-peripherals/CYUSB3-sys-driver/m-p/344343#M30543

Our Application/device is productive for several years now and running without any major issues using driver version 3.4.7.
We recently tried upgrading to the latest driver version(s) and run into connectivity problems:
The USB communication (mainly bulk transfer EP1) between uC and PC is working for several minutes upto a few hours with out any issues. Suddenly the device is removed and reattached within the same second, but of course the previous CyFX2Device object got invalid and the PC software stops/hangs. Debugging my software, it looks like the CyUSBEndpoint.XFerData routine never ends, waiting for the transfer to finish/abort. (More precisely: the thread is waiting in CyUSBEndpoint.WaitForIO)
Sometimes the device is also missing in the CyUSB.USBDeviceList after these "reenumeration events".

 We tested several combinations of cyusb.sys and cyusb.dll with the same harware, firmware and PC-Software:
3.4.7 (sys) 3.4.7 (dll) -> working
1.2.3.20 (sys) 1.2.3.0 (dll) -> working
1.3.0.3 (sys) 1.2.3.0 (dll) -> fail

Since the above thread mentions a similar issue I was wondering if there
a) is a newer version of the cyusb.dll which should be used with 1.3.0.x version of the driver?
b) is there a newer version of the cyusb3.sys file?

Best
Marcus

Hello, now I test the SPI communication rate of cy7c65211A chip in the linux virtual machine environment. SPI has been adapted to 3Mhz, Master and Mode2 modes. It is found that the CySpiReadWrite function is used to read the time interval of 1-byte sensor data each time. The time required for payment is about 8ms, I am not sure why it takes so long. The CS chip selection signals here are all GPIO2. Please reply when you are free, thank you

Hi, Guys,

I am using a Android Stuio to program a USB to I2C. in fact, some body has help me.  But he gave me an libs for armeabi(6t bit). 

I need a a libCYUSBSerial.so for 32 bit  ARMEABI-7a.      can you urgent give me a reply and a lowver version?

Thanks 

Hi,

I'm using CY7C65215-32LTXI in our design.

I have changed the configuration like following by using USB-Serial Configuration Utility.

Before:

SCB0

Mode:I2C

Protocol:Vendor

SCB1

Mode:SPI

Protocol:Vendor

After:

SCB0

Mode:UART

Protocol:CDC

SCB1

Mode:UART

Protocol:CDC

After this change, there have been no device detected by usb-serial configurariton utility. And also device manager could not detect com port.

Please tell me the way to back the configuration under this circumstance.

Thanks.

we use the EP6 transfer data from FPGA to PC (  IN  )
set EP6CFG = 0xE0; // IN, 512-bytes, 4x, bulk
After the data update in FPGA device，read the data package，There are 4 * 512 bytes in front and are not valid data；

set the 2x, bulk
After the data update in FPGA device，read the data package，There are 2 * 512 bytes in front and are not valid data；

What is the cause of this problem ？

Hi, I have Cypress CY7C65215-32LTXIT device. I would like to configure my device communication as I2C on GNU/LINUX. But I don't do this. There is "USB-Serial Configuration Utility" for Windows but not Linux.  Do you know "Configuration API" or software(utility) on Linux  for CY7C65215-32LTXIT?

I download the firmware by the control center on Win7, and the board can work normally.  I move the same firmware + sw + hardware to a windows 10 machine. After downloading firmware, the board does not work.

anyone have suggestion? thanks

Hi,

I use the CY7C68013A in Slave FIFO mode with external clock.

When the externally supplied IFCLK fails due to some reason, the FIFO becomes stuck, even if the external clock is revived.

Currently, the only remedy I know of is pulling the USB plug.

I know that the external IFCLK must be present before switching to external clock, but bad things happen sometimes.

What can I do if the external clock starts too late or has been off or below the minimum frequency temporarily (other than pulling and re-seating the USB plug)?

Thanks!

P.S.:

Disabling and re-enabling the device or the USB root hub in the Windows Device Manager (-> new enumeration) does not solve the problem.