USB superspeed peripherals Forum Discussions
Hi,
I am currently working with CX3 device getting frames from a CMOS Image Sensor(CIS). I have configured the MIPI information to get the data raw in RGB888 format, because I know that it is the only way for getting the maximum bandwidth. I have configured the PLL registers in order to set the PCLK in 100MHz(so CX3's data rate is 2.4Gbps).
On the other hand, I have done the same thing in the CIS, I mean, I have configured the PLLs for getting a similar bandwidth, all good for now. When I run a host application,from Laptop, which works directly with CX3 device. I have got a correct image, but if I open the debug port I can see how it appears the following issues:
- CB Failure.
- Video Timer.
So, I would like to know which is the cause or causes of both issues, and how try to fix them.
Thanks.
Show LessI apologize if this question is remedial... I'm brand-new to the EZ-USB product line. I've developed a custom PCB that contains three EZ-USB CX3 ICs, all connected through a USB Hub. Let me start by telling you what works:
- All three EZ-USB devices show up in "USB Control Center" (as "Cypress FX3 USB BootLoader Device")
- I've successfully installed and compiled a number of default firmware projects (to IMG files in Release mode), including:
- cyfxbulklpauto
- cyfxbulklpauto_cpp
- cyfxuvcinmem
- cycx3_uvc_ov5640
- I can select one of the devices in "USB Control Center" and run: "Program" - "FX3" - "RAM"
- I get the message "Programing Succeeded" and the device reboots (disconnects)
However, that's all that happens. The device never seems to come back online with the new firmware... irrespective of which demo I've tried. The only thing I can think of is that there's some compile file I need to set to specify CX3... but haven't found reference to any such flag in the documentation. Beyond that, I'm at a total loss..
Any suggestions you may have would be most appreciated!
Show LessHello,
Using the UAC1.0 example I am attempting to create a version that supports UAC2.0.
I have edited the descriptors but I am unable to get the device to enumerate. Windows reports error code 10 "A device which does not exist was specified."
As part of the descriptors I have included a clock source and clock selector entity but I have not yet created the code to handle requests to these. Could this be the reason for the error code I am getting? I am trying to check that the descriptors are correct before I move on to other parts of the code to avoid confusion later.
Show LessHi, I've studied the doc and knew how to modify the
C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\fw_build\fx3_fw\fx3.ld
to reallocate the memory mapping. It works!
However, it could affect other projects which don't need to modify the fx3.ld.
How to designate the fx3.ld path by some project's setting?
PS. I've searched that in Project Explorer -> click right button on designated project -> Properties -> C/C++ General -> Paths and Symbols, but still cannot find it yet...
Any help will be highly appreciated!
Hughes
my program works fine on USB3.0 connect
when i try to use 2.0, cant get any image
capture data by bushound get correct data length 15372*170+10252 ==> 15360*170+10240(without uvc head) == 1280*1024*2
use e-CAMView show correct resultion and format(1280*1024 Y16)
i think it should be description problem? but dont know how to fix it
zip file is my SS and HS description function too large to post here
Show Less
Hello,
we are developing products based on EZ-USB FX3. My question is, can we use the cypress VID and PID. I read that: "Cypress VID can be used only for development purposes", the Cypress VID/ PIDs can be used for testing purposes and when the end product is to be released, it is essential to use a different VID issued by USB.org. ".
I am asking to know if you have any updates or changes on that topic.
Thanks in advance.
Regards
Ghani
Show LessHi!
I wanted to utilize the space remaining in the EEPROM for storing some data. However, with the I2C boot mode, it seems to fail.
I've set the PMODE settings to Z1Z (for I2C -> USB boot).
My IMG file size is 165 KB. I'm trying to use the last 1024 bytes for storing some custom data.
Whenever I try to do that with this boot mode, the boot from EEPROM fails and it falls back to the USB boot mode.
On reading back after programming the EEPROM, it seems that the full 256 KB is being utilized.
However from https://www.cypress.com/file/201991/download, it doesn't seem that the EEPROM should be full, as the EEPROM write should end with the checksum in the end.
Currently, Control Center is being used to program the I2C EEPROM (with the PMODE settings being changed accordingly).
Show LessHello,
When I was debugging the CX3 UVC project, I found that CyU3PI2cTransmitBytes in I2C_SensorWrite returned the error value 0x4a
The error represented by 0x4a is CY_U3P_ERROR_FAILURE - When a transfer fails with an error defined in CyU3PI2cError_t
I found the mistake, but what I have to do next to correct the mistake I have no idea,I hope you can give me some advice to help me, thank you very much!
Best Regards,
Yaqi
Show Less