USB Forum Discussions
Browse the Community
USB low-full-high speed peripherals
Discussion forum regarding USB low-full-high speed peripherals topics.
USB hosts hubs transceivers
Discussion forum regarding USB hosts hubs and transceivers topics.
USB superspeed peripherals
Discussion forum regarding USB superspeed peripherals topics.
Featured Discussions
Hello,
I tested the video output on the custom board with the firmware provided by the kba below.
In order to exclude and test the image sensor, we tested it with data from fpga, which outputs a virtual pseudo image, and it worked well on the existing AN75779 project.
Problem:
In a project with that CDC interface, we found that the image did not come up until we opened the COM port on the CDC interface.
(Image1 : without open com port)
(image2 : video capture with opening com port)
Can you tell me why this happens, and how to fix it?
Below is a log that is output when I open a port without video output, as in Image 1.
Additionally) When the DebugInit() function is annotated, video is output immediately without the issue.
It seems to be related to the code below.
Thanks.
Show Less
I am using the FX3 KIT to implement a camera interface using the code found in AN75779. Can someone explain what it means to be told that a "DMA Reset Event: Frame Timer Overflow" has occured? Does it mean I should increase the Frame rate or reduce the frame rate?
Show LessThe 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 ?
Show LessHello.
I'd like to know detail HPI register about BCR-Plus.
Below is HPI register in BCR HPI Utility user guide.
I don't find detail document. Let me know if anyone know link or data.
Regards.
Robert.
Show Less
Hi,
the datasheet reads:
> After TetraHub is configured in a high speed system, it is in single TT mode. The host may then set the hub into multiple TT mode by sending a SetInterface command.
- is there a way to flip this behaviour on the hub itself?
i.e. by adding an eeprom or setting it via i2c? - Easiest would of course be to let the host reconfigure it to multi-TT
I haven't found how to do this under Linux, any tips?
Hello Infineon!
I've implemented a FIDO CTAP 2.1 interface on an FX3s but I am getting very strange behaviour with it... I've posted in the FIDO community google group but I don't think I'll get a response there... Any thoughts/ideas would be most appreciated!
To summarize:
1. Driver and report descriptors work as expected
2. HID Communication works
The wierdness:
Situation 1 (working situation)
1. Load up a test page for FIDO (Chrome browser, webauthn.io or other tool, all have same behaviour)
2. Start a FIDO registration process, browser says "insert FIDO device"
3. Program FX3s with FIDO firmware, it registers and handles INIT and GETINFO steps correctly, and sends registration info
Situation 2 (not working situation)
1. Program FX3s with FIDO firmware
2. Load up test page
3. Start FIDO registration, gets stuck in a loop performing INIT and GETINFO until "device fail" message
The part that is really confusing me is during INIT stage, the FX3s must send a new CID value, which the webpage/host must use for future responses, which it DOES use for the getinfo request... This confirms that FX3s -> FIDO HID -> browser and back communication is working successfully in situation 2.....
Is this potentially an issue with chromes implementation of FIDO HID? Is there a way I can "trick" the host with the FX3s to do a reset on a specific USB interface? I do not want to disconnect USB via CyU3PConnectState since it is a composite device and other interfaces may be doing something.
I should also point out there's shouldn't be any real difference in timing between messages sent and received (approx 10~50ms), nor is the content of the replies different. I will be investigating this with wireshark shortly but I am doubtful that a message timeout is the problem since the host should be sending an error if there is one as well.
Regards!
Fujimi
Edit: This only happens on USB3, works as expected on USB2 (Both scenario 1 and 2 work USB2), further edit, responses are always 64 byte in size which is the buffer size so there should be no issues with set wrap up (I think)
Show Less
I am learning the 3014 chip. And when I use USB Control Center, I found three burning methods. Could someone explain the difference between RAM mode and SPI FLASH mode? And when I choose RAM method or SPI FLASH method, how does the IMG program load and run?
Best wishes.
Show LessI am using the GPIF2 function of FX3 to receive large amounts of data from an FPGA, and then I am transmitting this data to a PC via USB using the Bulk-in path.
During USB Bulk transfers, I am experiencing a delay between I2C packets when using FX3's I2C Master to communicate with the FPGA's I2C Slave.
When not performing data transmission via Bulk, the operation works correctly with very short delays.
However, when using Bulk transfers consecutively, there is a significant delay between I2C packets.
I used FX3's SDK version 1.3.4, and here are the settings for the I2C:
void AppInit() { AppDebugInit(); AppPibInit(); AppGpifInit(); AppGpioInit(); AppI2cInit(400); AppUsbInit(); } |
void AppI2cInit(uint32_t i2cSpeed_KHz)
{
CyU3PReturnStatus_t apiRetStatus = CY_U3P_SUCCESS;
CyU3PI2cConfig_t i2cConfig;
/* Initialize and configure the I2C master module. */
apiRetStatus = CyU3PI2cInit();
AppErrorHandler(apiRetStatus,"CyU3PI2c failed", CyTrue);
/* Start the I2C master block. The bit rate is set at 100KHz.
* The data transfer is done via DMA. */
CyU3PMemSet((uint8_t *) &i2cConfig, 0, sizeof(i2cConfig));
i2cConfig.bitRate = i2cSpeed_KHz * 1000;
i2cConfig.busTimeout = 0xFFFFFFFF;
i2cConfig.dmaTimeout = 0xFFFF;
i2cConfig.isDma = CyFalse;
apiRetStatus = CyU3PI2cSetConfig(&i2cConfig, NULL);
AppErrorHandler(apiRetStatus,"CyU3PI2cSetConfig failed", CyTrue);
}
|
CyU3PReturnStatus_t I2C_Write(uint8_t SlaveAddr, uint8_t* addr, uint16_t addrLen, uint8_t* data, uint16_t dataLen)
{
CyU3PReturnStatus_t apiRetStatus = CY_U3P_SUCCESS;
CyU3PI2cPreamble_t preamble;
uint8_t* dataBuf = (uint8_t*)CyU3PMemAlloc(dataLen * sizeof(uint8_t));
CyU3PMemCopy(dataBuf, data, dataLen);
preamble.length = addrLen + 1 ;
preamble.buffer[0] = SlaveAddr; /* Slave address: Write operation */
CyU3PMemCopy(&(preamble.buffer[1]), addr, addrLen);
preamble.ctrlMask = 0x0000;
apiRetStatus = CyU3PI2cTransmitBytes(&preamble, dataBuf, dataLen, I2C_RETRY_COUNT);
AppErrorHandler(apiRetStatus, "CyU3PI2cTransmitBytes Fail", CyFalse);
CyU3PMemFree(dataBuf);
return apiRetStatus;
}
|
CyU3PReturnStatus_t I2C_Read(uint8_t SlaveAddr, uint8_t* addr, uint16_t addrLen, uint8_t* data, uint16_t dataLen)
{
CyU3PReturnStatus_t apiRetStatus = CY_U3P_SUCCESS;
CyU3PI2cPreamble_t preamble;
preamble.length = addrLen + 2;
preamble.buffer[0] = SlaveAddr;
CyU3PMemCopy(&(preamble.buffer[1]), addr, addrLen);
preamble.buffer[addrLen + 1] = (SlaveAddr | 0x01);
preamble.ctrlMask = 0x0004;
apiRetStatus = CyU3PI2cReceiveBytes(&preamble, data, dataLen, I2C_RETRY_COUNT);
AppErrorHandler(apiRetStatus, "CyU3PI2cReceiveBytes Fail", CyFalse);
return apiRetStatus;
}
|
Are there any settings required to simultaneously use GPIF2 and I2C, or if not, please explain what is causing the delay?
Hi,
I am not able to use the CY4500 PD software on MacOS. The software launches but in some sort of corrupted state that leaves it non-functional. It does not detect the analyzer hardware and clicking "Start" from status bar does nothing. I have attached a screenshot.
I am on M1 MacBook Pro, MacOS 13.5.2.
I posted previously about the software not launching at all and was told to install Java 8. I edited the program's Info.plist to force it to use JDK 1.8.0_181 because it was trying to use JDK 10 before, despite using jenv to switch my default Java to 8. This enabled the software to launch but it is still non-functional as described above.
I have also attached log file.
Show Less