USB superspeed peripherals

Hi,

I've written a custom bootloader for the CYUSB3014-BZXC using the Cypress Boot API. We've been using this bootloader without issue for the past couple of months. However, someone recently plugged the board into a USB 3.1 host controller using a USB 2.0 cable. Upon doing so we discovered that in USB 2.0 mode the device stops responding to standard requests after being suspended and then resumed. The traffic on the USB bus was captured with an Ellisys EX350 and shows the following transactions:

1. get device descriptor (success)
2. set address (success)
3. get device descriptor (success)
4. get configuration descriptor (success)
5. get BOS ddescriptor (success)
6. get serial number descriptor (success)
7. get language ID descriptor (success)
8. get product descriptor (success)
9. set configuration 1 (success)
10. LPM transaction (success)
11. Suspended
12. Resume
13. get language ID descriptor x 6 (failure)
14. get manufacturer descriptor x 6 (failure)
15. get product descriptor x 6 (failure)

UART Debug message prints from the firmware show the following:

Initializing FX3 Boot Firmware 1.6
Boot FW Event: CY_FX3_BOOT_USB_IN_SS_DISCONNECT
Boot FW Event: CY_FX3_BOOT_USB_SUSPEND
Boot FW Event: CY_FX3_BOOT_USB_RESET
Boot FW Event: CY_FX3_BOOT_USB_RESET
Boot FW Event: CY_FX3_BOOT_USB_RESUME

Are there any special actions that the firmware must take when it receives CY_FX3_BOOT_USB_SUSPEND or CY_FX3_BOOT_USB_RESUME in order to get the FX3 to ACK the control requests that take place after the the suspend and resume operations?

We also seem to experience the same problem when running the application firmware (uses Cypress full API) when the device is plugged in with a USB 2.0 cable. The bus activity is similar:

1. get device descriptor (success)
2. set address (success)
3. get device descriptor (success)
4. get configuration descriptor (success)
5. get BOS ddescriptor (success)
6. get serial number descriptor (success)
7. get language ID descriptor (success)
8. get product descriptor (success)
9. LPM transaction (success)
10. Suspended
11. Resume
12. set configuration 1 x 3 (failure)
13. Suspended

So the same question applies for the application firmware: what steps must we take in firmware in order for control transfers to succeed after the device has been suspended and then resumed?

Some other information that you may find useful:

Operating system: Windows 10
Host Controller: Asmedia ASM3142
Hub: none

I appreciate any help you can provide.

Thanks,
Michael

Hi,

    within the  AN75779 firmware i have already make it work well in win10(not work well when transfer video 2560*1024@25fps) and it can't work in linux.

    I want to know what else should be changed to make sure the firmware work well in both windows and linux. and it seems I didn't use the full bandwidth in win10(350MBps),what should i do to transfer video(2560*1024@25fps) in SS mode? 

(https://community.infineon.com/t5/Knowledge-Base-Articles/Change-Bulk-endpoint-to-Isochronous-in-FX3-firmware-KBA231897/ta-p/251816)

Hi: I used the solution provided by this link. After download the img, two FX3 unknown devices appears in device manager.

But when I update the driver , pop the message" i can't find the driver".

Is the program is tested?

https://community.infineon.com/t5/USB-superspeed-peripherals/USB3014%E5%90%8C%E6%97%B6%E4%BD%BF%E7%94%A8GPIF%E5%92%8CUART/m-p/339272/thread-id/30093

When I use cyfxuartlpregmode.c to test UART send and receive, I found if I do not use "CyU3PUartSetTimeout (1, 50000);" :

1. the SuperSpeed Explorer Kit still works but slower (ok to me)

2. the program should send "VRS" and receive "20181114" about two times a second, but sometimes, it loses "1114" (about 200 - 3000 times, it will happen once)

So, my question is, why did this happen? and more importantly, how to choose the readLoopCnt and writeLoopCnt value?

-------------------------------------------------

uartConfig.baudRate = CY_U3P_UART_BAUDRATE_9600;

uartConfig.isDma = CyFalse; 

io_cfg.isDQ32Bit = CyTrue;

io_cfg.lppMode = CY_U3P_IO_MATRIX_LPP_DEFAULT;

-------------------------------------------------

Hi infineon team, 

I port my source code ( build using 1.3.1) to 1.3.4 SDK. Upon compiling my code, I get an error message such as SYS_MEM overflowed by 37624 bytes. For this issue, I have modified the fx.ld and cyfxtx.c files. Due to this modification, I need to reduce the UVC_STREAM_BUFF size (previously we used 36KB). But if i reduced the UVC_STREAM_BUFF size, i am facing GET_BUFF_FAILED issue as mentioned in this community link.

As all of our products use 36KB as the standard UVC_STREAM_BUFF size. Currently we are unable to port our code to 1.3.4 SDK.

Our expectation for SDK 1.3.5 is to have some lesser library size. So that I can maintain 36 KB as UVC_STREAM_BUFF size when I port from SDK 1.3.1 to SDK 1.3.5. Please comment on this.

Reagrds ,

Rakesh

@AliAsgar @Rashi_Vatsa @KandlaguntaR_36 

hi

my application need to add new feature that device should enumerate as CDROM device that can autorun our software when device plug in.

Is there any example of cdrom device that i can reference?

and due my application already used i2c/gpif/uart peripheral. can i put our software(few kb) in ram that fx3 will load the software when start up without communication peripheral 

Hi,

I am working on cyclone 10 gx development board and cypress cyusb3kit-003. I have programmed cypress superspeed board with SF_loopback.img file which was given in AN65974 folder. I have programmed fpga with below file slaveFIFO2b_loopback.sof and may find setting file regarding fpga slaveFIFO2b_loopback.qsf in below file. I am not able to send bulk file to the fpga. 

The problem for the Intel PCH out of the USB3.0 device connected to this device,in the first link can be normal link on,

when the PCH closed the USB3.0 port and then open again, can not identify the device, only re-hardware reset can be,

we want to know there are other ways to solve this problem

CPU: Intel's  EAGLE STREAM

Operating system: Linux 7.8