USB superspeed peripherals Forum Discussions

If you have been running into incessant DMA Reset Event: Frame Timer Overflow problems no matter what the frame-rate your device is reporting to the FX3 then - YOU HAVE A PURELY ELECTRICAL CONNECTIVITY PROBLEM. I have seen multiple users report this problem and spend an inordinate amount of time debugging their FX3 firmware or resoldering their pins or replacing their cards. The problem lies in the fact that either FRAME_VALID or LINE_VALID or PCLK are not reaching their pins on the FX3. Use a scope to isolate the absent signals. It has taken me 3 months and two FX3 cards to work this out. I hope this post will help others who come after me to quickly find a solution to their problem.

Hello

Q1-1) Regarding the Tx de-emphasis setting of Fx3, I think that the default setting (SDK) of FX-3 is set to -3.5dB in line with the normal USB 3.2 standard. Is it possible to change this setting to 0dB? Please tell me how if possible.

Q1-2)

https://community.infineon.com/t5/USB-superspeed-peripherals/FX3-TX-de-emphasis-value/td-p/290348

For example, is it possible to set the value of Tx de-emphasis (dB) to 0x00 for the following calculation of Tx de-emphasis described in the above community?

Tx de-emphasis (dB) = 20 *log10 [(128 − 2 * tx_deemphasis value) /128]

Best Regards

NoAr

Hi all,

I am trying to program a PCB with the CYUSB3064 CX3 controller. I have obtained a development board from e-con, using the CYUSB3064 and the OV5640 image sensor, and am able to update the drivers in Device Manager, and program the device through the Control Center as outlined in the CyUSB.pdf guide. The dev board VID and PID is USB\VID_04B4&PID_00F3&REV_0100.

However, when I try to do the same process with my custom PCB, I am unable to update the drivers. Here is my exact configuration and error message: The PCB gets recognized as a USB Root Hub (USB 3.0) device and uses the C:\Windows\system32\DRIVERS\USBHUB3.sys driver by default. When I click Update Driver and point it to the Cypress\EZ-USB FX3 SDK\1.3\driver\bin\Win10\x64\cyusb3.inf, I select Cypress FX3 USB BootLoader Device from the list of models, but get the 'This device cannot start. (Code 10) An invalid parameter was passed to a service or function.' error. You can see this in the attached screenshot as well.

I'm assuming that the VID and PID for the controller on my PCB should be the same as the dev board, since they're the same controller, and thus I made no changes to the cyusb.inf, as the VID 04B4 - PID 00F3 is already in the list. Additionally, any attempts I made to edit the .inf were unsuccessful anyways, as I was unable to complete the force unsigned driver step. Is this correct? What could possibly be the cause of the error? Any help would be greatly appreciated. Thank you.

System info: Windows 10 22H2 running on Macbook Pro 16" 2019 via Bootcamp.

Hi!

Is there some source code example for SD-card support with CYUSB3035?

In Application Note AN89661_USB_RAID_1_Disk_Design_Using_EZ-USB_FX3S-ApplicationNotes-v03_00-EN all the links lead to a dead ends.

I am using ezusbfx3sdk_1.3.5_Windows_x32-x64.exe,  with cyusb3065/cyusb3014; 

I download AN75779 the lastest release from your website and compiles. it works with default configuration, an UVC device enumerate automatically.

However, when I uncomment USB_DEBUG_INTERFACE  macro, (actually, there compile errors, with an extra "," ), fix bugs I flash image to RAM, there is only one unrecognized device, no UVC device. when I follow 5.9 to install driver, the only unknown device is not working. there is error "yellow mark" on device.  double click the device, we get " USB device return usb config descriptor invalid (translate from Chinese) ".

I tried another debug solution : https://community.infineon.com/t5/Knowledge-Base-Articles/Using-CyU3PDebugPrint-API-to-Send-Debug-Messages-over-USB-CDC-Interface-from-FX3/ta-p/251458, it works.

One thing I need to point out is that, I do not connect any cameras, and I don't think this will affect the enumeration of devices. 

@ChaitanyaV_61  @narolkarvarun 

CYUSB3014-BZXIT CYUSB3065-BZXC 

Hi everyone! Regarding CYUSB3035-BZXI's datasheet (001-84160 Rev. *K) S0-port consist of GPIOs from GPIO34 to GPIO45. In a parent version of the device (CYUSB3064-BZXI) SO-port also include a GPIO33. What is function of GPIO33 (pin K2) in CYUSB3035 ?

11:21:23 **** Incremental Build of configuration Debug for project SRAM_FX3 ****
cs-make all
'Building file: ../cyfx_gcc_startup.S'
'Invoking: ARM Sourcery Windows GCC Assembler'
arm-none-eabi-gcc -x assembler-with-cpp -I"C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\\firmware\u3p_firmware\inc" -Wall -Wa,-adhlns="cyfx_gcc_startup.o.lst" -c -fmessage-length=0 -MMD -MP -MF"cyfx_gcc_startup.d" -MT"cyfx_gcc_startup.d" -mcpu=arm926ej-s -mthumb-interwork -g -gdwarf-2 -o "cyfx_gcc_startup.o" "../cyfx_gcc_startup.S"
Access is denied.
cs-make: *** [cyfx_gcc_startup.o] Error 1

11:21:23 Build Finished (took 569ms)

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

请教下编译错误可能什么原因

Hello there !

As my team and I are currently developing a system based around one of your FX3 EZ-USB controllers, some concerns arose due to the fact that these products have been on the market for more than 10 years, according to the original documentation from Cypress.

Though the USB controller works fine, we might have to reconsider our hardware choices if there are any chances for the production to be discontinued or for the chip to become obsolete due to a new generation of USB controllers in the next few years.

Do you have any guarantees on production and support continuity, specifically for CYUSB3014-BZXC ? If so, for how long should we expect it to be available still ? 

Also, should we expect a new  series of USB controllers to make the FX3 series obsolete any time soon ?

I am not entirely sure that the technical support forum is the right place to ask this ; if it's not, could you please redirect me to the adequate platform / forum, or to a direct contact?

Best regards,

Enzo 

Is there a latest GPIF II Designer software that has bug fix regarding the Error that DR_DATA need to be same as Thread number to the next state? Multi-channel DR_DATA Thread0 goes to DR_DATA Thread1 is needed to perform Continuous FX3 Stream Out. The Multi-channel IN_DATA Thread0 goes to IN_DATA Thread1 is needed to perform Continuous FX3 Stream In. An idea that it is bug in the GPIF II Designer software GUI because it prevent the Multi-channel DR_DATA to happen, but by editing the generated cyfxgpif2config.h in the CyFxGpifWavedata, the multi-channel DR_DATA can be force to work. One of the forum did the manually editing of the CyFxGpifWavedata in this link:
https://community.infineon.com/t5/USB-superspeed-peripherals/Continuous-FX3-GPIF-Write-doesn-t-work-GPIF-Designer-bug-GPIF-State-Machine-bug/td-p/290776
Question is there a GPIF II Designer release that allow the Multi-channel DR_DATA to happen in the GUI State machine?

Hello,

I apologize if this question has already been asked. In my project I use some pins as tristate pins. I need to set the pin to 1 or 0. When I set it to 1, the external device can set it to 0 (its pin is also tristable). So I need to read the state of the pin itself (not register bit). I configure the output (CyU3PGpioSetSimpleConfig() function) as follows:

gpioConfig.outValue = CyTrue; // Initially HIGH value
gpioConfig.driveLowEn  = CyTrue;
gpioConfig.driveHighEn = CyFalse;

If I set:

gpioConfig.inputEn = CyTrue;

Will the value be read from the pin, or from the internal register of the port? How to do this correctly?

Thank you!