USB superspeed peripherals Forum Discussions
Hi,
I have generated my own config. file from the Image sensor configuration. I got the below errors when connecting to PC(Windows 10).
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
For your reference, pls find the attached file and device descriptor(.zip file)CX3 Connectivity error
I am developing real-time data transmission using fx3 (USB\VID_04B4&PID_00F3).
The number of modules is a system that receives data at the same time using 7 to 8 modules.
But
Errors often occur in FinishDataXfer(), and the error codes are as
The source is roughly as follows. follows:
lease check the attached file for the approximate source and situation.
Show Less
Dear All,
I am implementing FX3 U3V device with the demo provided in this link. (https://community.infineon.com/t5/USB-superspeed-peripherals/FX3-application-note-for-USB3-Vision/td-p/52071#comment-293031)
And I refer the following discussions and make some modification to the demo as well as the xml file to make it enumerated but the eBUS palyer then shows XML_ERROR while the xml file contained in the device has been read by the host app. I change the xml files and adjust the size of the xml file, but the error remains. Is there any step i missed? Any help would be appreciated!
Thank you!
Show Less
- I have a CYUSB303X with the GPIF-II interface connected to AD7381-4 ADC. The CYUSB is running the attached AD7381-4_cyfxgpiftousb project.
- When applying constant voltage on the GPIF pins, I'm able to read them properly at the USB port (on the host PC).
- When the AD7381-4 digital signals are applied, the readings are always zero (which doesn't correspond to the real data being transmitting). What is the reason for that?
Please see the schematic below:
Here are the signals captured by a logic analyzer, they are always read as zeros, if a DC (Zero or 1) is applied on the GPIF input lines, it is read properly at the USB:
Here is the USB read:
Show Less
I am trying to view the status of a DMA channel but the `CyU3PDmaChannelGetStatus` API is returning a status of `CY_U3P_ERROR_BAD_ARGUMENT` and I am unsure why. I have the following code:
CyU3PReturnStatus_t apiRetStatus = CY_U3P_SUCCESS;
CyU3PDmaState_t dmaState;
uint32_t prodCount, consCount;
apiRetStatus = CyU3PDmaChannelGetStatus(&glChHandleUVCStream, &dmaState, &prodCount, &consCount);
if (apiRetStatus != CY_U3P_SUCCESS)
{
CyU3PDebugPrint(4, "DMA Channel Get Error: 0x%x\r\n", apiRetStatus);
}
`glChHandleUVCStream` is initialized with `CyU3PDmaChannelCreate` API as `CY_U3P_DMA_TYPE_MANUAL` in my application initialization function. Looking at the documentation on `CyU3PDmaChannelGetStatus`, all arguments are of the proper type. Any help would be appreciated. The variables passed to this function do get values filled out, including CY_U3P_DMA_ERROR as the status. Could this be related? How can I see the reason of the DMA channel's error status?
Show LessHi,
I tried modifying the SuperSpeed Design Examples V1.2.1 CollectData program and changing:
// Start with modest buffering 8 x 8 x 16KB = 1MB
// Can go up to 256 x 64 x 16KB = 256MB but this will mask some effects
#define PACKETS_PER_TRANSFER 8 // 256
#define NUM_TRANSFER_PER_TRANSACTION 8 // 64
to:
#define PACKETS_PER_TRANSFER 256 // 256 * 64 * 16KB = 256MB
#define NUM_TRANSFER_PER_TRANSACTION 64
The FX3 is continually streaming ~200MB/s of data. The above change worked well on my computer, but on another computer it silently dropped packets after about 512MB of received data.
What are good settings for the above two values that should work on any computer for a 200MB/s transfer rate? Also, is the CollectData example source code missing something that would show dropped packet errors?
Thanks,
Will
Show Less
We've been looking through the EZ-USB FX3 SDK and cannot find any VHDL or Verilog files.
The application notes seem to refer to them, but there doesn't appear to be any other downloads.
The main file in question is "Fx3_slaveFIFO2b_altera".
Is there any way to get this file?
Thanks,
Sam
Show LessI am running into strange issues where if I insert Type C USB3.0 on one side CX3-UVC camera is detected. But if a change in the orientation of the cable device is not detected. Please find below sch for reference. Also in older PCB with the same design, we are not facing issues. We have followed guidelines with each PCB. We are not sure what could be the reason.
Show Less
Hi,
I have read the document"Designing with the EZ-USB® FX3 Slave FIFO Interface".
It writes"Flags may be configured by EZ-USB FX3 firmware as empty, full, partially empty, or partially full signals. These are not
controlled by GPIF II states, but, rather, by the DMA hardware engine internal to FX3."
But in the fireware's API,I can't find any apis to config that.
Could you tell me how to config that?thank you.
Show LessDev Board: CYUSB3KIT-003
I am currently working with the example "cyfxusbi2cregmode.c"
I understand that communications can be sent through the I2C pins SDA and SCL using the function:
CyFxUsbI2cTransfer (
uint16_t byteAddress,
uint8_t devAddr,
uint16_t byteCount,
uint8_t *buffer,
CyBool_t isRead)
Could someone please provide a quick example of how these parameters would be filled out when this function is called to communicate with a slave peripheral? Assume we want to send a simple 16 bit (2 byte) write communication. What would this look like? I also do not understand the difference between byteAddress and devAddr.
Thank you
Show Less