USB superspeed peripherals Forum Discussions

Hi,

I need to change the GPIF config during a runtime. I've read about sequence:
1. GpifDisable()
2. De initialize all the peripheral blocks.
3. Reconfigure IO Matrix.
4. Initialize the respective peripheral blocks.
5. New GpifLoad().

In my GPIFs I only do modifications in struct "CyU3PGpifConfig_t CyFxGpifConfig" that are not related to other peripherals (I'm not switching IO from 16 to 32b, not disabling I2C/SPi, etc).  I have I2C, SPI, UartDebug initialized in my project, and I do override some GPIOs. 

Do I still need to do that routine with De-init and Init ALL periph blocks anyways? Or I can skip the steps with peripherals that I use but do not change?

Thanks

 

Show Less

1. I am creating a custom card for a project. Does the term "FX3 RAM" in the CyControlCenter.pdf refer to RAM inside the FX3 or does it refer to the CY7C1062DV33 on Explorer Kit Board? I use the PMODE code F11 where (F stands for Floating and 1 is signal high).

 

2. My card has a lot of components on it. It does have a contiguous ground layer right across the card. However, there are signal traces that cross underneath the SS wires because of space constraints. Will this be a deal breaker?

Show Less

The updated Windows driver in the 1.3.5 SDK is behaving quite differently to the one in 1.3.4:

1. it causes lots of suspend+resume events while transferring data,
2. these seem to also cause XferData() to return error, whereas previously XferData() would happily run in a loop forever.

It's easy to reproduce point 1 using an example program + Streamer:

• Put the cyfxgpiftousb basic example onto the eval board.
• Attach the debug USB lead so can view the debug output.
• Run Streamer with PacketsPerXfer=1 and XfersToQueue=1
• The debug log shows lots of lines saying "USB event: 2 0" where 2 = CY_U3P_USB_EVENT_SUSPEND.

Now uninstall the newer driver and put on the older one, and do the same as above. No debug lines appear while transferring data, and it works perfectly.

This continual suspend+resume is causing problems as it takes several milliseconds during which GPIF data is lost.

Is this new behaviour in the new driver intentional? Or is it a bug?

Many thanks

Show Less

I need some help selecting the correct voltage level for the MIPI Signals on the Image Sensor side, as described below: am interfacing the CX3 with a new Image Sensor that uses/requires 1.00 V to 1.1 V (Typical 1.05 V) for MIPI Signals; The CX3 uses/requires a voltage of 1.2 V for the MIPI Signals. I am concerned about this mismatch of voltage levels. The supplier of the image sensor says that I can power their image sensor using 1.05 V and at the same time power the CX3 using 1.2 V because the "low" and "high" levels of the MIPI Signal from the sensor are within the acceptable range of the CX3. Is it OK to use these different voltages for the MIPI Signals? Thanks, Mo Show Less

Do you have a new GX3 driver in the works which is compatible with OSX Sonoma? The latest I see is for Monterey and they were working great until moving to Sonoma.

Driver page:

https://www.infineon.com/cms/en/design-support/software/device-driver-libraries/usb-controllers-ez-usb-gx3-software-and-drivers/

Thank you for continuing to produce drivers for the GX3 chip and "doing the dance" to keep things up to date with the ever changing OSX requirements.

References:

https://community.infineon.com/t5/USB-superspeed-peripherals/EZ-USB-GX3-CYUSB3610-M1-Mac-Drivers/td-p/360487
https://community.infineon.com/t5/USB-superspeed-peripherals/EZ-USB-GX3-CYUSB3610-M1-Mac-Drivers/m-p/281767

 

Show Less