We're having reports of problems with our products using the FX2LP not being recognized by PCs with USB3.1.  USB3.0 seems to work.  Are there any known compatibility issues?

hello，

Is the driver of CY7C68013A for windows 10 supported now？and how to get it ？

thanks so much.

Dear,

     I'm following this link: Interfacing FX2LP™ with Image Sensor – KBA95736

    The firmware is exactly the same,  image sensor and the connection wires are the same;

    (1) with my custom board and cy7c68013A-128AXC, the results are perfect,

    (2) but when I change to another cy7c68013a-56PAXC, as below (the schematic is given as attached.), I can get nothing. why?????

    for the failed case, the oscilloscope shows that the signals are OK, and when I use a intermediate FPGA to check the signals, the data are also OK, as below,

I really don't know what happened, why this test board cannot get any data from the image sensor ? do I need to do any extra setting for this board?

Is there any way to reduce the USB-->SPI latency on CY7C65211A on a Windows platform?  When I perform GPIO toggles they take place in about 1 msec but when I perform an SPI transaction of 2 bytes it takes about 15 msec.  So, there's going to be some Windows latency due to USB polling interval, but for USB2 that seems to be 1 msec so I should see 1msec + SPI transaction time for the SPI transaction as well???  This leads me to believe that there is some latency in the IC itself...?

Hi,

I'm testing the new USB Bridge board FX2LP18 based. We do not have the FPGA board yet to connect it onto. This if the final usage of this FX2LP18 USB Bridge board (download and communicate with a FPGA and also communcate with several I2C components).

On the board we have a MICTOR connector to connect Agilent Logic Analyzer with 16bits DATA BUS and CTRLs (IFCLK etc), SCL and SDA.

I notived that if the probes (E5346A) are plugged (to analyze the DATA/CTRL GPIF traffic), then the FX2LP18 resets during a GPIF exchange (Windows Sound and Device return to be a "No EEPROM Device").

It does not Reset if i do not plug the probes. And the GPIF datas is correctly sent to the DATA/CTRL bus.

The E5346A probes have termination like this :

I suspect an analog issue (overconsummtion ?) but unable to see any RESET low pulse or VCC drop.

I tried to lower the GPIF freq => 48MHZ downto 30MHZ. It seems better. No RESET occurs. But this is not a valuable solution cause we lost in performance.

Can i monitor something else to see what's the source of the RESET ? Is it possible to retrieve it in the firmware for instance using a FX2LP18 register ?

Regards.

Hi,

is there any EZ-USB® FX1™ , FX2LP™ , and FX3 Driver for Arm64 based CPU?

I've installed windows 10 on arm64 CPU and I need this driver.

Hi Cypress Team,

Good day!

I have two problems need your help.

1. My customer need 3 JTAG ports and 1 Uart port. Does cypress have 4 port USB bridge?

2. Can CY7C65215 support 2 JTAG ports now?

Appreciate &Thanks

Sophie

Hi, i need few details for the part CY7C68013A-56PVXC.

1. Currently this part is active, may i know how long it will be supported?

2. Is there any EOL issued for this part?

Consider this as priority and respond as soon as possible.

Regards

Bhuvaneswari

Hi, We've received our new board with a FX2LP18 inside.

We have a large EEPROM inside to store the "Connect" Firmware (and perhaps the true firmware one day).

The I2C bus is 1.8V. The communication is OK with the EEPROM. I was able to program it (using a didicated master - a promira)  from adress 0x0000 with the following DATAs :

C2 B4 04 14 86 00 00 00 00 07 00 00 90 e6 80 e4 f0 80 fe 80 01 e6 00 00

Theses DATAs are the .IIC file (LP18_safe) available in the \CY3687_MOBL-USB_FX2LP18_DVK\1.0\Firmware\Connect folder.

The EEPROM is correctly written. After a RESET, i can see the I2C communication of the FX2LP18 onto this EEPROM. All seems OK.

But after that the FX2LP18 does not enumerate.  What i'm doing wrong ?

** NEWS ** IN fact it enumerates. USB sound can be heard.

But Drivers not found. I tried another .IIC to use same PID/VID than FX2LP.

USB\VID_B404&PID_8613\6&12BE8945&0&3

What i need to do ?

I would like to see my device in the USB control Center to be able to do a RAM download.

*** LAST MINUTE ** : It is OK. I've made an inversion in the PID/VID

Thanks.

Windows7

Cypress Windows Driver Package v3.13.0.84

Renesas Electronics USB 3.0 Host Controller Driver v3.0.23.0

Tera Term v4.99

Equipment to simulate system interconnect:

     - StarTech PEXUSB3S4V PCIe  USB 3.0 4 port Card

     - C2G 29525 2-Port USB Hub (required to simulate USB 2.0 environment)

     - Cypress CYUSBS236 DVK Board (2x)

Problem:

Re-connect of Cypress USB device on USB 2.0 hub after opening a session to all COM ports of each device results in Windows "USB Device Not Recognized" message.  Requires (minimum) restart of USB 3.0 Root Hub device to remedy.

Initial connection:  USB Serial Composite Devices on USB 2.0 Hub

Connection after opening & closing session to all COM ports:  Unknown Devices on USB 2.0 Hub

Steps (repeat as necessary):

1. Connect Cypress A (CYUSBS236 SW1)
2. Connect to Cypress A COM port 0 (Tera Term "New Connection")
3. Connect to Cypress A COM port 1 (Tera Term "New Connection")
4. Connect Cypress B (CYUSBS236 SW1)
5. Connect to Cypress B COM port 0 (Tera Term "New Connection")
6. Connect to Cypress B COM port 1 (Tera Term "New Connection")
7. Disconnect Cypress B COM port 1 (Tera Term "Disconnect")
8. Disconnect Cypress B COM port 0 (Tera Term "Disconnect")
9. Disconnect Cypress B (CYUSBS236 SW1)
10. Disconnect Cypress A COM port 1 (Tera Term "Disconnect")
11. Disconnect Cypress A COM port 0 (Tera Term "Disconnect")
12. Disconnect Cypress A (CYUSBS236 SW1)