For the last few days, I'm trying failsafe firmware update as explained here , I'm using the same code and followed the same steps as mentioned, first I merged 2nd stage boot loader and UsbBulkSrcSink and then flashed to my Denebola Kit, and It successfully shows itself as a device in the control center, but later when I try to update new firmware(USBBulkloopAutoEnum from examples) with given Firmware Updater, I flashed new firmware with given Firmware updater, but It didn't execute in Denebola Kit. Even in the control center, I didn't get anything to see.Show Less
I want to interface two 800x800, 60 fps sensors with MIPI output in stereo mode and convert it to USB 3.0. Kindly let me know whether it's possible to do it with CX3. If not suggest me a way to do it. Thanks in advance.Show Less
Dear infineon team,
I am trying to port my old code build using 1.3.1 SDK to 1.3.4 SDK. I faced a problem during I2C communication. I was sending some data through I2C before the CyU3PConnectState() API in my previous code. But while using 1.3.4 SDK the data transmitted over I2C was not written properly in registers. This is happening randomly (out of 5 times 2 or 3 times this issue occurs) . But in 1.3.4 SDK when I transmit I2C data after the CyU3PConnectState() API it is working properly.
kindly provide a solution to sort out this issue.
I am currently learning to work with the EZ-USB FX3 kit and trying to implement some UART messages to follow the execution of my programs with a puTTy terminal.
The CyU3PDebugPrint() function, frome the cyu3system.h library, seems to be made for that purpose, however I have not been able to make it work so far, even though the subject has been discussed many times on this forum.
In particular, I am confused by the fact that there are entire blocks of code dedicated to initializing the UART in the UsbUart example firmware that are not mentioned in this article on how to use the function.
I also tried to import and run the edited Debug firmware provided in this previous discussion about a similar issue, yet cannot read anything in my terminal.
For your information, PuTTy scans the COM port on the USB 2.0 connector, since it is linked with the UART interface, with the default settings (115200 bauds, 8 data bits, no Parity bit, 1 stop bit, no Flow control). Could I be doing this wrong ?
>Do you happen to have a template on how to use this DebugPrint function for a basic application? My next test would be to print a message when the on-board user button is pressed.
>Is there another message-printing function I might have missed and that could be easier to use?
Thanks very muchShow Less
Can anyone tell me what is the starting address of CX3 and what its size, I searched in Technical reference and Datasheet, but I could not found?Show Less
Hi I am using FX3 USB superspeed hardware. I am trying to do file transfer from Master to Slave using cyusb_linux application. I have downloaded the latest application from your website. My OS is Ubuntu. I am getting the below errors LIBUSB_ERROR_TIMEOUT , LIBUSB_ERROR_OTHER and unable to clear halt data pipe. I want to transfer bulk files from master to slave. Kindly help me out in this. I have attached the screen shot. Thanks in advance.Show Less
Most of the data I'm trying to transmit seems to be going between the FX3 and the other chip just fine, but I'm periodically getting zero length packets seemingly coming from nowhere. I've been trying to debug this, but everything I've tried has been a dead end so far.
I'm trying to use the FX3 to connect an 8051 on our board with a host application on a windows PC. My setup is as follows:
Now the problem I'm seeing is that, the 8051 sends a keepalive signal periodically to the host app, and every once in a while, we get a zero length packet as well.
Here's what I've tried in my investigation:
I suspected that maybe there's noise or something changing the PKTEND pin long enough to trick the state machine into sending a ZLP, but my coworker has already dismissed that notion. He's the hardware guy, so I can't really make him check it, and he didn't leave a way to attach a scope or anything to the pin, so wouldn't be easy.
If anyone has any suggestions of what might be going wrong, or ideas for other things I could test, I'd love to hear them.Show Less
I am working with a sensor at 1280x720@30fps YUV422_8 output, I want to use 24bit-bus to transfer data. But when I set up this project, I found there was data padded to the frame, and I can't preview the frame directly by Amcap. I understand it is because the line size can't be divided by 24bit, then there is data padding. So I want to know how the data is padded to each frame, and how to get rid of the padded data on each frame?
If I need to use multiple endpoints of fx3, should I use them in order? That means I should use ep1, then ep2, ep3, and so on.
Can I not use ep2, instead, I use ep3 or ep4, for example?
I found when I used ep1, ep2, ep3, my project can work; But if I used ep1, ep2, ep4, the project will go wrong.
Is this the rule for using the endpoints of fx3? But I have not found the rule in any reference documents of fx3.
Or I have something else wrong?
Thanks a lot.Show Less