USB superspeed peripherals Forum Discussions

Hi, everyone!

Currently, my development board uses the cypress 3014 chip and uses UVC output.  However, after the program runs, the device can be recognized on Windows systems, but it can't be recognized on Linux systems. And I am using Ubuntu as my Linux system. What could be the problem? Do I need to modify the cyfxdscr. c file? Could anyone provide some suggestions?

Best wishes.

wind13

Hello,

Now I am using the cyfxusbhost sample program to test the function of cyusb3014 as a host. When I connected the USB flash drive and typec port, I failed to enumerate the USB flash drive device successfully. May I ask what the reason may be? (I also tried to connect the mouse to the host port, but failed to enumerate the mouse device successfully)

Thanks.

Hello

I have a custom CX3 control board (CYUSB3065 chip) that connects to the OV5460 camera using an I2C EEPROM (ST M24M02).
This test uses the routine "cycx3_uvc_ov5640" from FX3 SDK 1.3.4 as is. After compiling and downloading to RAM, the camera image can be obtained successfully. However, if you download the compiled image file to the EEPROM, the system will not be able to boot from I2C, regardless of whether the PMOD is set to Z1Z or 1ZZ.
Use a logic analyzer to test the I2C signal. You can read the data of the first frame at the start. Compared to AN76405, the read data is correct. But oddly enough, the I2C interface stopped working after that.
The logic analyzer tests the I2C signal as shown in the attached figure.
Are there any settings in the routine that affect I2C activation? Does it affect the launch of I2C?

Best regards!
Liu Qimin

smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/USB-superspeed-peripherals/CX3-I2C-startup-failed/td-p/630162

smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/USB-superspeed%E3%83%9A%E3%83%AA%E3%83%95%E3%82%A7%E3%83%A9%E3%83%AB/CX3-I2C%E3%81%AE%E8%B5%B7%E5%8B%95%E3%81%AB%E5%A4%B1%E6%95%97%E3%81%97%E3%81%BE%E3%81%97%E3%81%9F/td-p/630171

I was happy to see that FX3 SDK v1.3.5 have finally been released, only to find out that the reason for not being able to run 1.3.4 are still there 😞 

I wrote about this almost a year ago, and the bug has of course been around much longer than this.
Solved: FX3 SDK 1.3.5 updated release schedule - Infineon Developer Community

I do not remember the details with 1.3.4, but with 1.3.5 I can't use breakpoint or halt the execution, since the tool will loose connection with the CPU. i.e. if I press the pause button, nothing will happen except that the pause button gets disabled.

I really hoped that this was fixed since I have constant issues with version 1.3.3 as well, in this version I can set breakpoints and step a few lines, but it is more or less impossible to press run and expect that it will work again.

I'm using a Segger J-link debugger.

I am trying to stream 1080p60 video through a MultiChannel DMA buffer however we are running into a problem where after writing some amount of buffers to the FX3, we are seeing the current thread WATERMARK and READY flags stay asserted. This causes video data to backup on the FPGA side (because it cannot write due to buffers reporting as full) and then the system breaks. This issue is not present when streaming 480p60, 720p60 or 1080p30. I tried increasing the number of buffers in the  MultiChannel DMA from 4 to 8 to try and increase the number of available buffers but I saw no difference. If I switch to a single channel DMA, video can be sent out as expected however I am unsure if it is truly 1080p60 because the docs say I need to use a MultiChannel DMA to get the FX3 data bandwidth required to output 1080p60.

In the included photo, You can see multiple writes and then suddenly both WATERMARK and READY assert at the same time.

Is there any way to check if buffers are getting stuck or are full through the FX3 firmware? Could I attach a UART debug print to when this is occuring?

The BT601 format data of the f 5640 module has been successfully debugged according to the 《Infineon-AN75779 _How_to_Implement_an_Image_Sensor_Interface_with_EZ-USB_FX3 _in_a_USB_Video_Class_(UVC)_Framework-ApplicationNotes-v13_00-CN.pdf》document and the "cyfxuvc_an75779.zip" code. Is there any reference material for the f 5640 module BT656 format data to fx3 ?

Hi,

Following this thread Looking-for-FX3-descriptors-that-work-with-WinUSB/td-p/101661 , we are using the WinUSB driver to communicate with our FX3 chip (CYUSB3011). 

Now, we are at a point where we would want to be able to reprogram the chip without using the Control Center given in the SDK.

We saw that the code for the Control Center was also in the SDK so we took a look into it. It seems like the DownloadFw is used with a CCyFX3Device. However, we don't directly use the CyAPI since we use the libusb functions in our code.

So my questions are, is it possible to reprogram the device even tough we are using the WinUSB driver? And if so, is there any example or a document that could help us with it?

Thank you and have a nice day,

Keven

Hello, 

I have developed my firmware program and now I want it to be freely named in the device manager, how do I change it?
Thanks.

Sir / Madam,

Could you please help me in fixing:  "sudo ./install.sh" reports " ../include/controlcenter.h:9:10: fatal error: ui_controlcenter.h: No such file or directory " ?

Sincerely,

Liu

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

liuw@liuw-SYS-E100-12T-H:/home/Cypress/cyusb_linux_1.0.5$ sudo ./install.sh
Your current directory is /home/Cypress/cyusb_linux_1.0.5. This is where the cyusb_suite software will be installed...
g++ -fPIC -o lib/libcyusb.o -c lib/libcyusb.cpp
g++ -shared -Wl,-soname,libcyusb.so -o lib/libcyusb.so.1 lib/libcyusb.o -l usb-1.0 -l rt
cd lib; ln -sf libcyusb.so.1 libcyusb.so
rm -f lib/libcyusb.o
rm -f moc_predefs.h
rm -f moc_controlcenter.cpp
rm -f controlcenter.o main.o fx2_download.o fx3_download.o streamer.o moc_controlcenter.o
rm -f *~ core *.core
g++ -c -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -I/usr/local/Qt-5.12.12/include -I/usr/local/Qt-5.12.12/include/QtGui -I/usr/local/Qt-5.12.12/include/QtNetwork -I/usr/local/Qt-5.12.12/include/QtCore -I. -I/usr/local/Qt-5.12.12/mkspecs/linux-g++ -o controlcenter.o controlcenter.cpp
In file included from controlcenter.cpp:7:
../include/controlcenter.h:9:10: fatal error: ui_controlcenter.h: No such file or directory
9 | #include "ui_controlcenter.h"
| ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [Makefile:1183: controlcenter.o] Error 1