USB superspeed peripherals Forum Discussions
We were testing of the Designing A GPIF™ II Master Interface concept using CYUSB3KIT-003 kit and try to send data from Slave to Master and Master to Slave in line with the document AN87216. We observed that the transmission is happening in same PC having two USB 3.0 port.
But when we are connecting between two PC (One PC ->Host ,Second PC->Slave), the Slave USB device is not able to transfer data to Master USB and only master to slave data transfer is working.
How to transfer data from Slave to Host using CYUSB3KIT-003 kit between two PC?
Show Less
Hello,
I'm using a Denebola board to receive data from an image sensor. I have developed a passive adapter board that simply routes the MIPI lanes and I2C from the Denebola daughter board connector to the image sensor connector.
The image dimensions are 4056x3040=12330240 B at 10 fps. RAW8. And the MIPI configuration is:
CY_U3P_CSI_DF_YUV422_8_2, /* CyU3PMipicsiDataFormat_t dataFormat */
2, /* uint8_t numDataLanes */
2, /* uint8_t pllPrd */
119, /* uint16_t pllFbd */
CY_U3P_CSI_PLL_FRS_250_500M, /* CyU3PMipicsiPllClkFrs_t pllFrs */
CY_U3P_CSI_PLL_CLK_DIV_4, /* CyU3PMipicsiPllClkDiv_t csiRxClkDiv */
CY_U3P_CSI_PLL_CLK_DIV_4, /* CyU3PMipicsiPllClkDiv_t parClkDiv */
0, /* uint16_t mClkCtl */
CY_U3P_CSI_PLL_CLK_DIV_2, /* CyU3PMipicsiPllClkDiv_t mClkRefDiv */
4056, /* uint16_t hResolution */
0 /* uint16_t fifoDelay */
I have 3 setups (denebola board + adapter board + image sensor):
- 1st: Works well, the frame size received is 12330240 B, 0 MIPI errors, and the host application receives the image correctly.
- 2nd: Frame size shown is wrong (sometimes 30000000 or 8000000), many recrErrCnt, and the host application receives a frame with the wrong size.
- 3rd: Frame size shown is wrong (sometimes 30000000 or 8000000), manyctlErrCnt, and the host application receives a frame with the wrong size.
We are checking the hardware of 2nd and 3rd setups. However, so far we can't find any issue with them.
The firmware applied on all setups is the same. Is there any custom configuration that should be done to different CX3s? This would explain the different behavior from CX3 to the other.
I appreciate any insight you can provide.
Best regards,
Hi,
I am trying to integrate camera AR0522 with a Cypress CX3 custom board but failing to configure the MIPI interface correctly.
I noticed that there is existing devkits with camera AR0521 but the EZ-USB FX3 SDK only provide libraries and examples for the cameras AS0260 and OV5640.
Do you know if there is a project example or at least a MIPI configuration example available for the AR0521 (or AR0522) ?
Best regards,
SimonP
Show LessCYUSB3610 wondering if there is an updated Mac OS driver for the latest operating system which is Big Sur. Please provide driver if available. If not available do you have an ETA on when it will be?
Show LessHi,
We are getting CY_U3P_USB_EVENT_SETCONF event in some CX3 chips while switching between resolutions inconsistently so that USB reset occurs. We have added CyU3PUsbLPMDisable () API in CyCx3UvcAppInit(), even after this we are getting a USB reset issue, however, the number of occurrences is low. Please guide us to overcome this issue as earlier as possible.
Reagrds,
Vignesh Kumar R.
Show LessHello
For the subject ,usb and mass storage peripheral controller, is it possible to interface the part with the host controller over uart also in addition to the SDIO interface (i.e in addition to sdio interface with the microcontroller, can it be connected to microcontroller with uart also for command and control purpose?)
Please advice.
Show Less
hi, I want to transfer data from the gpif to PC. the fx3 was working dma auto mode, gpif width=16bits,I want reset the DMA buffer before every transfer to clear the DMA buffer data。How should I do,thx
Show LessHi,
We have a custom board with FX3 + EEPROM. This setup is already working and has been programmed multiple times with "control center". Now, we are thinking of adding some modifications to our custom board, for which we will need to modify "CyBootProgrammer.img".
The problem comes when we build the project named "cyfxflashprog", rename the generated .img to "CyBootProgrammer.img" and overwrite "...\EZ-USB FX3 SDK\1.3\bin\CyBootProgrammer.img" with the newly created file. By doing this, when we try to program our EEPROM as we always do, "Control Center" shows the message: "Programming of I2C EEPROM Failed".
Just as a note: our device is correctly detected by Control Center, and only fails when trying to program a .img file to the I2C EEPROM. In addition to that, we have this system properly working when not building "CyBootProgrammer.img" ourselves.
So, is there any modification to be included to "cyfxflashprog" project that can solve our issues?
Thank you,
Hello,
In configuring the DMA channels, the size and count parameters dictate the amount of data that can be stored within the DMA channel:
What I understood from this is that there would be CY_FX_BULKLP_DMA_BUF_COUNT buffers with size of size * 8 where data can be stored etc. in the DMA channel i.e. size = 8192, count = 2 means 2x8192 buffer size total.
Is there a way that I can fill up the two buffers consecutively before committing them for sending? What I currently tried is filling up one whole buffer and then committing it before filling up the next buffer for another commit. I would like to try filling up both or all available buffers first before committing to minimize the commit buffer call.
Thanks,
jl46
Hello,
I'm using the CYUSB3014 GPIF feature to capture data from an ADC. I have read from a forum inquiry here that there is a tendency for data loss when using the GPIF but can be resolved by using multiple socket and thread: https://community.cypress.com/t5/USB-Superspeed-Peripherals/FX3-lose-data-from-GPIF-II-to-USB-3-0-even-with-2-threads/m-p/86040#M6686
I've also looked at the UVC example that incorporates the multiple GPIF socket but applying it to my code results in an IN transfer error every time I try getting data from the GPIF endpoint:
The ADC that I'm using has a corresponding timing diagram:
*ADC = master, FX3 = Slave.
The DOUTx pins are from 4 pins of the ADC outputting data in parallel. I connected the DCLK to GPIO16, DRDY to GPIO17 and the DOUTx pins to GPIO0 to 4.
Thanks,
rs2123