USB superspeed peripherals Forum Discussions

Hi,

I am currently working in a project based on CX3. We have developed both an own hardware which embedded it, and a host application.

Our product works as a bridge between MIPI and USB protocols, in order to drive the pixel information from a CMOS Image Sensor to a host.
A complex softwere layer, inside the host, will run after it applying image processing algorithms.

After this overview, I want to explain my doubt. I have been working in both hardware and firmware layers, for this reason I have EZ-USB Suit
installed in my laptop, because I use it to complile the firmware image, which it will be store inside the embedded SPI-Flash memory in the PCB. So, as I have installed the EZ-USB Suite, my laptop has the cypress custom driver which achieve recognize the CX3 as Cypress USB BootLoader. Finally I store the firmware in our hardware design via Control Center tool.

But We need to update the firmware image in whatever laptor, including all of them which do not have the EZ-USB Suite installed. For this reason I would like to know which are the minimum necessary files (contemplated in the SDK EZ-USB Suite) that We need to add in our software layer in order to be able to upload the firmware, discarding the rest of the files of the SDK EZ-USB Suite.

Thanks so much.

Hi,

Last time I change cypress bulk to isochronous mode.  Detail refer to  https://community.cypress.com/t5/USB-Superspeed-Peripherals/how-to-change-bulk-to-isochronous-mode-in-uvc-project/m-p/89823#M7126

I find ubuntu16.04 + cypress(Isochronous ) can only open single camera. if open multiple cameras simultaneously, the first camera works well, but next camera will report "VIDIOC_STREAMON failed 28, No space left on device."

kernlog shows:

Apr 20 12:31:52 ecu kernel: [66731.190810] usb 10-3: Not enough bandwidth for new device state.
Apr 20 12:31:52 ecu kernel: [66731.190831] usb 10-3: Not enough bandwidth for altsetting 1

Is the cypress code needs some changes for bandwitdth setting?

Could you help to check the attach file and help to fix it ?

Appreciate for your help!

Jun

Sample firmware " USBBulkSourceSinkLED.img"  is downloaded to RAM of FX3 on CYUSB3KIT-003 demo board. In normal working, after downloading, the device enumerates as device"Cypress FX3 USB StreamerExample Device".  But sometimes, after downloading , the device can't enumerate.  It has to recycle the power by unplug USB cable and download it again. I need some help on  why and how to avoid it

Hello,

I have several demo setups available to me.I have a Denebola CX3 RDK board (with 0v5640 camera, a CYUSB3KIT (FX3 Superspeed explorer), a CYUSB3ACC-004A ON Semi interconnect board and finally an AS0260 DEMO3HEAD board. I  need to prototype a AS0260 camera on etither the CX3 development board or preferably the FX3 version.  This has been done in the past as firmware examples exist in the FX3 SDK directory.  The interconnect board gives details to setup an obsolete MT9M114  DEMO3 board only. While the pinouts of the interconnect board appear compatible, I dont really know if this hardware setup is appropriate.  Is there a good example of configuring a CX3 or FX3  to AS0260 camera with all off the shelf hardware as I described with jumper settings etc?  Thank you for your help.

What firmware and configuration is installed on CYUSB3013 parts that come directly from Infineon?

While bringing up a board with a new CYUSB3013:

1. It appears that CYUSB golden firmware is only enumerating as a USB2 device. Is there any way to force it to use USB3?

2. Is there a list of what might put or keep an FX3 in USB2 mode?

3. When an FX3 is in USB2 mode, is there any log data stored in the FX3 of attempted USB3 connections? (Step 3.e.ii in Section 6.8 of the TRM indicates a count is maintained for the number of times 3.0 receiver detection failed. Is that count readable externally?)

4. Could there be a Hardware issue? It appears that CYUSB golden firmware does not react properly to cable disconnect. We have a self-powered board that keeps the device powered regardless of USB connection. The behavior is as follows: if the USB cable is connected on power up, the device enumerates as USB2 "Cypress FX3 USB BootLoader Device", as expected. However if I unplug and re-plug the USB cable, I see setup packet timeouts on the bus, as if the device didn't reset its bus address and as a result is not responding to broadcasts... The same happens if I power up the board with the cable disconnected and then connect the cable a few seconds later. Is this by design or did we do something weird with our board? SuperSpeed explorer board is bus-powered so it doesn't have these issues...

5. Is there an Application Note or Best Practices for self-powered devices?

6. Other than PMODE pins, is there a way to control behavior of a new CYUSB3013 device? 

7. Even with PMODE pins, are there combinations that are not documented? Reference Table 1-4 in the TRM.