USB superspeed peripherals Forum Discussions

Hi, 

We are using the DS90UB954TRGZTQ1 and DS90UB953 from TI for serializing and Deserializing MIPI data from a High-speed camera. To send the data to the computer we are using the CYUSB3065-BZXC from Cypress Semi because it has UVC drivers support. The CYUSB3065-BZXC supports only MIPI CSI-2 V1.01 whereas the DS90UB954 chip support MIPI-CSI 2 V1.3.

Is the MIPI CSI-2 V1.3 backward compatible with MIPI CSI-2 V1.01 ? Do I have to do any special configuration for this on the USB Super Speed Phy? Would I face any issues?

Tony 

Hello,

We want to certificate driver by resell process.
Could you please confirm below information?

publisher display name : INCAA Computers
os : win 10 x64, win 10 x86
driver version : 1.2.3.20
chip : fx3s

Thank you

Hello.

I am using the Streamer Application  from SDK1.3.4 with the SuperSpeed Explorer Kit.  When I plug the setup into a USB3 port that is part of the motherboard, all is fine and I can get transfers approximately 4.3Gbps.  There are no failures.  I am just using the default settings that the Streamer Application starts with.  All looks good and is okay.

However, when I try to use a RocketU 1244A USB3 add-in card with the default settings,  I get approximately 200 Successes and then it just keeps failing.  The transfer rate just decreases to 0 if I let it run over time.  After the initial successes, everything is failure.

The settings are BULK IN, packets per xfer=32, xfers to queue=16.  Which is the default.

After trying numerous different things, it appears that the 1244A card cannot queue up any more than one DeviceIoControl() buffer at a time?  Other cards, in addition to the motherboard usb ports, appear to allow queuing up multiple buffers simultaneously via DeviceIoControl().

If I make the packets per xfer=1 and xfers to queue=1 in the Streamer Application with the 1244A card, I can get no failures but the transfer rate is 0.043Gbps (much slower).  Are you aware of any limitations in using DeviceIoControl() with the 1244A USB3 PCIe card?

Frank

My FX3 development board is CYUSB3014. It directly connect to host. I want to implement a function. Development board is running Slave FIFO application that's from SPI flash, PC send a signal development board through control endpoint, development board reboot into BootLoader and wait for PC update SPI flash. I've tried to call CyFx3BootDeviceReset, but my project link failed. 

How can I do it? Please help me.

Hi everyone,

I have a new sensor with YUV422-8bit need to connect to CX3, I have made CX3 MIPI receiver configuration accroding to CX3 SDK, but I can't get image from CX3. And I have confirmed that the CX3 hardware is OK because I have got image from a raw sensor already, and the new YUV2 sensor is streaming correctly because I have measured the MIPI signal, I suspect there may be something throng with CX3 MIPI configuration, but I can't find it, is there anyone could help me? Below is my configuration:

I have measured HSYNC and VSYNC on CX3 board, but they are always low.

Anyone could help to generate a correct CX3 MIPI configuration for me?

Hi,

How to calculate FIFO Delay Time as CX3 MIPI Interface Confiduration show. Could you give me any formula to calculate this value? Thanks!

Hello,
I am working on a YUV422-10bit sensor connecting to CX3 with YUV2 output. The sensor resolution is 1280x720@30fps, I find that MIPI CSI-2 transfer YUV422-10 as 2 pixel with 5 bytes, so I think I could still configure CX3 as YUV422-8 input, but configure resolution to 1600x720. In this way, CX3 still can receive complete sensor data I think(if this is wrong, please correct me). And I actually done a test, but the result is quite abnormal. I print CX3 debug log, and found CX3 have received sensor data with different frame size, the frequency is also unequal, and preview all black image with AMcap. So if anybody could help me?

Attachment is MIPI interface configuration and debug log.

Hi. For a few proto PCBAs, we are sourcing CYUSB3014-BZXI devices but the datecode is '12xx'. Concerned about the 'ES' devices which had some erratas. Specifically, unable to soft-enumerate on the 'ES' version of the component.

Have some questions:

1) Will the engineering samples of the CYUSB3014-BZXI devices have the 'ES' laser markings ? This datecode does not but wish to understand the markings.

2) Which datecode of the CYUSB3014-BZXI is considered to be bug free silicon ? Saw some mention of Rev B and Rev C silicon but how can we determine if our device is one of these iterations with erratas ?

Please assist asap as so far, unable to locate any document with these details.

Thanks.