USB superspeed peripherals Forum Discussions

Hello,

Board : CYUSB3KIT - 003

I'm trying to test my DUT(Device under test) machine with lower packet size then 1024 with the FX3 board and the "USBIntrSourceSink" firmware example.

I want to change the parameters inside the "USBIntrSourceSink" firmware example according to the USB 3.2 Specification limit.

1. maximum packet size.   (USB 3.2 Specification 4.4.7.1, 9.6.6)
2. BURST SIZE.

Inside the "USBIntrSourceSink" example there are

• cyfxintrsrcsink.c
• cyfxintrsrcsink.h
• cyfxintrdscr.c

In "cyfxintrsrcsink.h" I changed the "CY_FX_INTR_BURST_SIZE" param to 1

And inside "cyfxintrsrcsink.c"

 I changed size to 8

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

case  CY_U3P_SUPER_SPEED:

            size = 8;

            break;

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

Also inside "cyfxintrdscr.c" in section

/* Standard super speed configuration descriptor */

 I change it to

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

    0x08,0x00,                      /* Max packet size = 1024 bytes */

    0x08,(0x00 * CY_FX_INTR_BURST_SIZE), /* Bytes per interval : 1024 * burst */

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

the FX3 board don’t pass the enumeration and fail in the Descriptor hand shake.

But when I change the number to 16 in all the files it works And the streamer can test the FX3 board with the interrupt firmware test.

Thanke for your help.

Hello,

I am developing a firmware for a Cypress CX3 that control multiple sensor on top of streaming a camera sensor.

After integrating the last sensors, my code is now too big to fit in the SYS_MEM segment:

I tried to increase its size as proposed on other topics but I cannot change "CY_U3P_SYS_MEM_TOP" as my firmware also requires a 2-stage bootloader. Increasing the SYS_MEM segment size reduced the other segments and the DMA streaming is not functioning anymore.

I need to increase the SYS_MEM length to at least 0x34000 to fit all my code. How can I increase it while keeping the DMA video streaming functional ?

Thank you for your help,

SimonP

Hello,i used project of USBVideoClassBulk and work on Windows10,and download firmware to ram of FX3 development board,windows10 camera could displays FX3 output image,but i download the same firmware to EEPROM of FX3 development board,then attached FX3 to ubuntu18.04,camera(cheese) couldn't identified device.

ubuntu18.04 dmesg dispaly as follows:

usb 4-4:new SuperSpeed USB device number 9 using xhci_hcd

usb 4-4:LPM exit latency is zeroed, disabling LPM.

usb 4-4:New USB device found, idVendor = 04b4, idProduct = 4722

usb 4-4:New USB device strings: Mfr = 1, Product = 2, SerialNimber = 0

usb 4-4:Product: FX3

usb 4-4:Manufacturer: Cypress

uvcvideo: Found UVC 1.10 device FX3 (04b4:4722)

input： FX3  as /devices/pci0000:00/0000:00:14.0/usb4/4-4/4-4:1.0/input/input22

Hi,

I am currently working with a CX3 in order to transfer data frame from a CIS sensor to the host. 

I need  to send some custom information with each frame for, but I don't know if it is possible to modify or add byte information into Payload Header or to the end of the frame.

Please could you give me same advice about how to do that? I guess I will have to modify the DMA buffer size in order to add byte information. But I would like to know if there are already some bytes that I can modify without to change the DMA buffer size.

Thanks.

Hi,

I have a FX3 firmware project with a working GPIF state machine configured with a manual DMA channel for GPIF to USB transfer (based on the sample cyfxgpiftousb).
The GPIF is able to produce  a data package (1030 byte) up to every 60 microseconds. The interval time is configurable by the firmware.
If the data is ready, the DMA callback function is called, where I change some bytes from the buffer (add a counter) and then commit it with CyU3PDmaChannelCommitBuffer.

Now I want to commit the data only when a special firmware flag is set, otherwise I want to discard the buffer with CyU3PDmaChannelDiscardBuffer and not transfer it to the PC.
But this is working only if the interval is set to several milliseconds.
If the interval is set to lower values, so that e.g. the DMA callback is called every 1 millisecond, the buffer discarding seems to take too long, and the callback will not be called after some passes.

My question, does the discarding really takes so long or is there is something wrong on my thoughts.

void GpifToUsbDmaCallback(CyU3PDmaChannel *chHandle, CyU3PDmaCbType_t type,
CyU3PDmaCBInput_t *input) {
int i;
CyU3PReturnStatus_t status;

if (type == CY_U3P_DMA_CB_PROD_EVENT)
{
if(input != NULL && input->buffer_p.count > 0)
{
if (boTintChanged)
{
comm_PutChar (ACK);
CyU3PDmaChannelDiscardBuffer (chHandle);
boTintChanged = CyFalse;
}
else if (boFetch)
{
// The first six byte contains data garbage from the ADC pipe
// so we can change the first 4 byte and include a counter...
input->buffer_p.buffer[0] = uiDataSignature;
input->buffer_p.buffer[1] = uiDataSignature>>8;
input->buffer_p.buffer[2] = uiDataSignature>>16;
input->buffer_p.buffer[3] = uiDataSignature>>24;
uiDataSignature++;

// ...and set the next two byte to zero (preserved for future usage)
input->buffer_p.buffer[4] = 0;
input->buffer_p.buffer[5] = 0;

CyU3PReturnStatus_t status = CyU3PDmaChannelCommitBuffer (chHandle, input->buffer_p.count, 0);
CyU3PDebugPrint(4, "GpifToUsbDmaCallback CyU3PDmaChannelCommitBuffer %d \r\n", status);
boFetch = CyFalse;
}
else
status = CyU3PDmaChannelDiscardBuffer (chHandle);
}
else
status = CyU3PDmaChannelDiscardBuffer (chHandle);
}

if (type == CY_U3P_DMA_CB_CONS_EVENT)
{
/* Data transfer has been started. Enable the LPM disable loop. */

}

CyU3PDebugPrint(4, "GpifToUsbDmaCallback Event %d empfangen \r\n", type);

return;
}

Dear all,     (and @YatheeshD_36)

Almost 18 months ago I was having some issues in using the .Net Api for Cypress EZ-USB FX3 SDK.

However I got some really nice help in this thread:
https://community.infineon.com/t5/USB-Low-Full-High-Speed/SuiteUSB-using-NET-API-for-PassMark-USB-3-0-plug/m-p/76716#233780

The issue was resolved and everything has been running smoothly for the last 18 months until the other day.
What has changed? Nothing obvious that I'm aware of, but our IT department has updated machines with Windows security patches if that could make a difference. 

What seems to happen is the following:

1. The device (Passmark USB3.0) inserted into the machine.
2. My code is using the CyUSB  .Net interface for the CyUsb3.sys driver.
   
3. My code checks that the endpoints are USB 3.0 by checking the size of the MaxPktSize of the endpoint and making sure that it is not below 0x4000.
   

    

4. This is all good. Then my program creates an arbitrary buffer of 65k data and calls the
   endpoint function XferData.
   
5. This fails and if I debug fairly deep down in CyEndPoints.cs (at line 367 in function BeginDataXfer) I can see that _lastError is set to 997. The function returns a true so this might be as expected.
6. After this the function FinishDataXfer is called to get the overlapped result.  However the rResult from the GetOverlappedResult function returns false and the len is set to 0 bytes.
7. No bytes are being transmitted.
8. One observation is that after the device was inserted the Cypress Control Center reports a descriptor info with a Bulk channel with MaxPktSize of 16384.
   
9. After the transmittal failure the device info reports just a bulk channel of 1024 bytes (which is what I interpret as HS instead of SS)
   
10. However the device still seems to be enumerated at SS from what it will let you know through its display.
    

    (The Passmark testprogram does not show any errors and happily runs at SuperSpeed (USB3.0))

• There have been no code changes for my code. 
• From what I can tell there are no updates to the Cypress / Infineon SDK (EZ-USB FX3 SDK 1.3.4 for Windows)
• There are no updates to the FW of the Passmark adapter nor to their driver during the last 18 months.

If someone has any idea what I should try to look further into, or has any advice on how to move forward,  it would be greatly appreciated.

King regards
Magnus

We are seeking paid assistance to solve a communication problem between the Cypress FX3 and computers using USB 3.0. We have written some custom code that gets the buffer contents in a loop. We have installed Cypress driver CYUSB3.SYS version 1.2.3.20

With this code, we are able to transfer 1GB data in about 8 sec on an HP Z440 computer running Windows 7 running CYUSB3.SYS 1.2.3.3, and on several other computers running Windows 10.

However, when we try to run on our Lab computer, a Dell Xeon W-2125 4GHz with 64GB RAM, x64-based processor, communication times out above 512K data, and inserts a 10 sec delay. This delay is inserted multiple times depending on the data size. We can affect this problem by slowing down the capture loop by inserting internal looping to take up processing time, but this isn't a solution

We are requesting assistance in a proper solution to this problem