USB superspeed peripherals Forum Discussions
Hello,
I am currently designing a PCB with the CX3 processor.
the board is powered by an external power supply V5V_EXT.
Could you please tell me how to connect the USB connector that comes on the board?
I thought of connecting VUSB from the connector to the VUSB pin of the CX3.
As for the other power supplies of the core, they will be generated from the V5V_EXT power supply.
The problem is that in this case we can not respect the sequence of POWER ON
because if the USB cable is not connected and we are only supplied with external power the sequence described in this graphic is not respected!
Could you please tell me how to power the board to respect the power sequence of the CX3.
For information we are in USB 3.0.
Thank you @
Show LessGreetings,
I want to use the CYUSB3065 chip to get an image from the OG02B1B OVT sensor on a PC via the USB3 interface. I drew a printed circuit board for the OG02B1B sensor and connected it to the CYUSB3065 starter kit using the mipi csi-2 interface. After that, I modified the code for CYUSB3065. Now I'm running a CLASSIC MEDIA PLAYER in Windows10 and the Wireshark program outputs the log shown on the printscreen. There is data, but they are all equal to 0xFF03. What does it mean? and how to solve the problem?
Show LessIn testing I came across a strange result. I have an FX3 application where data is streamed at a fixed rate from an ADC. While overall the application is reliable and can transfer data for a day or more without corruption, changing the size of the CyDmaBuffer to certain values will reliably cause less data to be received than requested. For example, using the modified driver that enables transfers > 4 MB, if I configure 5111808 bytes per buffer (4992 1024 byte USB packets), then transfer 12 buffers, buffer 11 is always smaller by 12288 bytes:
[Device 0, Thread 0] 0: Got 5111808 bytes (128.000000 FX3 DMA buffers) in buffer 0! (hEvent: 1176) start: 1 (expected: 1) end: 128
[Device 0, Thread 1] 1: Got 5111808 bytes (128.000000 FX3 DMA buffers) in buffer 1! (hEvent: 1232) start: 129 (expected: 129) end: 256
[Device 0, Thread 0] 2: Got 5111808 bytes (128.000000 FX3 DMA buffers) in buffer 2! (hEvent: 1248) start: 257 (expected: 257) end: 384
[Device 0, Thread 1] 3: Got 5111808 bytes (128.000000 FX3 DMA buffers) in buffer 3! (hEvent: 1244) start: 385 (expected: 385) end: 512
[Device 0, Thread 0] 4: Got 5111808 bytes (128.000000 FX3 DMA buffers) in buffer 4! (hEvent: 1236) start: 513 (expected: 513) end: 640
[Device 0, Thread 1] 5: Got 5111808 bytes (128.000000 FX3 DMA buffers) in buffer 5! (hEvent: 1260) start: 641 (expected: 641) end: 768
[Device 0, Thread 0] 6: Got 5111808 bytes (128.000000 FX3 DMA buffers) in buffer 6! (hEvent: 1268) start: 769 (expected: 769) end: 896
[Device 0, Thread 1] 7: Got 5111808 bytes (128.000000 FX3 DMA buffers) in buffer 7! (hEvent: 1272) start: 897 (expected: 897) end: 1024
[Device 0, Thread 0] 8: Got 5111808 bytes (128.000000 FX3 DMA buffers) in buffer 8! (hEvent: 1276) start: 1025 (expected: 1025) end: 1152
[Device 0, Thread 1] 9: Got 5111808 bytes (128.000000 FX3 DMA buffers) in buffer 9! (hEvent: 1280) start: 1153 (expected: 1153) end: 1280
ERROR: [Device 0, Thread 0] 10 SMALL BUFFER RECIEVED (missing 12288 bytes) !!!
[Device 0, Thread 0] 10: Got 5099520 bytes (127.692308 FX3 DMA buffers) in buffer 10! (hEvent: 1220) start: 1281 (expected: 1281) end: 34516
DMA buffer wrong end
[Device 0, Thread 1] 11: Got 5111808 bytes (128.000000 FX3 DMA buffers) in buffer 11! (hEvent: 1252) start: 30421 (expected: 1409) end: 34517
DMA BUFFERS DESYNCED!
DMA buffer wrong end
Overflows: 0
Total FX3 DMA transfers Produced: 1536
In this test, the hardware was attempting to generate 128*12 = 1536 DMA transfers, and the hardware reports sending exactly that many with zero overflows. However, buffer 10 is inexplicably missing 12288 bytes, which is about 31% of one DMA buffer, which causes all subsequent frames to be misaligned (the "BUFFERS DESYNCED" error). Buffer 11, although shifted 12288 bytes, is the correct size. This will happen every time when the CyUSB buffer is this size, but goes away if I change it.
Wireshark shows that the missing bytes are only sent after the transfer has been aborted:
My understanding is that CyUSB buffers need to be an integer number of USB packets (in this case 4992) and should hold an integer number of FX3 DMA buffers (in this case 128), but otherwise can be adjusted as makes sense for the application. I'm not sure how to interpret the smaller returned number of bytes. Is there a way to check why the device sent less than expected?
Show LessWe developed a custom board that utilized portions of the CYUSB3KIT-003 dev kit schematic. Unfortunately the need to connect the OTG_ID pin to ground for dual role USB operation was missed so it was left unconnected. The entire reason for including the FX3 was so our board could act as a USB host, so this omission is a big problem. Is there any way to enable the USB host operation from software without having to do a respin of the board?
Show LessHi team,
I am trying to get 13MP MJPEG video stream with HS USB 2.0. I have set the resolution successfully but I am getting white screen in directshow based app. In AMCap I was getting "Unable to render video preview screen".
May I know why it is happening so?
Does USB 2.0 support 13MP MJPEG video stream?
Thank you.
Show Less
Hello,
I am testing the CX3 mipi interface that uses only 2 data lanes.
My board was created with unsed data lane floating.
I just found out that the data sheet says to connect to the ground, but i cannot modify it now...
What are the results in this case? What are the expected problems?
Is it unstable? Or Is it not working?
Please,, we are praying it is working...
Show LessI need to use the cyusb3kit-003 SuperSpeed Explorer kit to develop a "logic analyzer" that writes from 16 bit parallel input to windows disk through USB3. I have a USB2 device that takes data to a buffer, but the readout won't keep up with input.
It is simple. I need an EXE file for execution under windows command prompt that takes data and writes to binary disk like my current unit. I am not a programmer, so I need to find someone to do the programming. I use a high level language to read the binary file and process it.
The web pages lead me in endless circles, and the associates list does not seem to know about the SuperSpeed device. Short of learning binary coding which I do not have enough time to do, I see no help.
Show Less
Hi team,
I added different resolutions to my custom camera board with the help of this link .
I have taken care of probe control settings and descriptor settings while adding different resolutions.
Currently I am facing some issues and I would like to have a help from you.
1. I can able to stream 13MP resolution over USB 2.0 but for some lower resolutions like VGA I'm getting black screen in AMCap. But I am getting image in windows camera app, why is this happen ? Did I miss anything?
2. 13MP resolution streaming is perfectly being done and I have added still capture capability to it. When I try to capture image, the streaming is getting interrupted and on to UART log side I'm getting DMA_RESET(continuously starting and stopping the App). May I know why this happening?
Your help is most appreciated.
Thank you,
Abdul.
Show Less
Infineon's EZ-USB FX3S and SD3 support both support RAID 0 and RAID 1. Do any products support other RAID levels, specifically RAID 5?
RAID 0 is Block-level striping without parity or mirroring
RAID 1 is Mirroring without parity or striping
RAID 5 is Block-level striping with distributed parity
Greg
Show LessMy hardware is a sensor connected to 3014 via DVP. The problem is the DVP signals are good(frame/line valid and the pixel clock). And we can see the firmware enter the CyFxUvcApplnDmaCallback(), however, then get the buffer from CyU3PDmaMultiChannelGetBuffer(), we found the dmaBuffer.count is zero for every callback. The consequence is that the USB host receives many empty USB packages, and no image is presented.
The interesting thing is if we try to reset 3014(may need a few times), it is probably recovering from the exception state.
Any idea for what's going on under this phenomenon? Many thanks
Rossi
Show Less