USB superspeed peripherals Forum Discussions

Dears

USB Video Class 1_5的USB_Video_Payload_Frame_Based_1.5.pdf文档中定义了PAL 隔行的描述符，但是在AN75779的固件中没找到 bmInterlaceFlags 这个描述符，请问怎么修改成隔行呢？

Hello

Regarding the USB driver sugnature for FX3, We are planning to get the signature based on the Part3 Driver Ressell of CyUSB.pdf.

SO, I will attache the planning document to get the USB driver signature.Also, they have already get their PID/VID.

[Current their Progress]

- They have finished up to ② in step 1.

- They are asking to create a global account for Azure AD.

- They donot have an EV code signing certification, sp they are considering purchasinf it.

[Question]

Q1> For attached procedure, Is this kind of recognition for the procedure>?

Q2-1> What should ther do if the EV code signing certificate expires ?

Q2-2> What should ther do if the OS is updating during period?

Q3> If they sign using the time stamp function , Is it possible to use it without probleams even if it expires. If no, Please tell me the workaround more details.

Best Regards

Arai

Hi Cypress,

I am using CX3 to get data from ToF image sensor over USB to host PC,

i used the e-CON Denebola EVB to develop it, i could get the image data and proper Descriptor Info from Control Center also in device management as following,

but now i am using the same FW on our CX3 board designed from us, but CX3 cannot be recognized properly in device management and it's show empty in control center as following pic.

i try to trace the log different from pass and fail, as above left bottom red, i found there is no callback as CyCx3UvcApplnUSBSetupCB from host driver,

but the code did register it in CyU3PUsbRegisterSetupCallback as following snapshot.

i don't know why host driver didn't trigger the callback "CyCx3UvcApplnUSBSetupCB ", may i have your suggestion for the issue ?

What kind of signal or debug code i can do more test to verify ? thanks ~

B/R

Kyle

Hi all,

I'm trying to sample a signal for a long period of time and stream to the system host using the FX3 GPIF2 interface. If I use a high sampling rate and I keep the bus active, there is no problem. However if the sampling rate (or the bus activity is low), the FX3 seems to not respond after some time, by not asserting the DMA ready flags.

For our system, GPIF2 data is sent in burst of 1KB. An internal FIFO buffers data and a state machine waits for the buffer to fill up before sending the next burst. For this example, the amount of data to transfer is about 30M 32 bit words and the input data rate is about 92MBps. The FX3 uses a multi-channel DMA with FLAGA and FLAGB as ready flags. DMA buffers are 2x16KB for each channel and USB burst length is 8KB. As can it seen in the image below, after sending a complete 16KB buffer to the FX3, FLAGA and FLAGB don't get asserted any more and the system fails due to a FIFO overflow.

So here is my question: Is there something I am missing that can justify this behaviour? Something like a timeout at the GPIF2 level. This doesn't happen with higher sample rates.

Kind regards

JayakrishnaT_76​

Hello, I want to add another PWM based on the project you provided last time to transmit data through gpif, but the project does not respond after I added it. Can you give me some suggestions?

Here are the functions I need to implement:

1. After power on, first configure 78365 through gpio to simulate spi

2. Generate a PWM to drive external mems

3. Send data to 78365 cyclically through gpif

The following code from line 745 is the part I added

I look forward to your answer

Hi

    There is a CYUSB3014 & MT9V034 camera programming, follow the application AN75779 instructions: according to Aptina MT9V034 data sheet changed sensor.c. Update the length of the high-speed and super-speed USB configuration descriptor and the length of the video stream input header descriptor. At the same time, through the GPIF II Designer, modify the "data bus width" field to select "16 bits", recompile the GPIF project, and use the newly generated file "cyfxgpif2config.h" Replace the original file. After all the files are modified, compile the CYUSB3014 project, use the IMG file in the DEBUG directory to write CYUSB3014. insert the host, the host USB can enumerate the camera correctly. It seems to be correct to capture the USB data between the camera and the host.  See attachment USB.TXT.

     But when I open the camera with the host application, I cannot capture the image of the camera. To capture the USB data between the camera and the host, the host is always in the "SET INTERFACE" command loop. For the captured data, see Annex 9V034.TXT.

The search data "SET INTERFACE" is a command of USB2.0, but the returned data does not know what it means. In this case, where should I look in the firmware to find the problem?

     Any help you can provide would be greatly appreciated!

   Qimin Liu

Hi,

in FX3, can we pause the DMA transfer deliberately at some point of DMA(by a flag or an external event)?
Base on my understanding, we can do it by DR_DRQ and DACK , if we use assert DRQ on "dma-rdy" it happens at the end of DAM. but by using DAK, we can controlling that. right?

Is there is any example for drq/dack mechanism?
I have read the user guide but there are some ambiguities for me.
For example, dr_drq assert or de-assert by "bystatemachine" , is not clear for me.
Also I couldn't find any description about drq/dack timing mechanism.

Thanks in advance

I have 1.2.3.20.  With the last Windows 10 Update 2004 our USB communication has degraded on certain hardware.  Anyone else have similar issues?  If there is a newer version where would I find it?

Thank you.

Our system  is working well with  FX3     - it is a C#.net application that we are migrating to USB3.

We have found that when USB cable is pulled  bulkendpt XferData call never exits or throws an exception, even though timeout is set.

...

try{

                BulkOutEndPt.TimeOut = 500;

                bResult = BulkOutEndPt.XferData(ref outData, ref numberOfBytesToWrite_CommandRead);  // this line never exits !!

            }

            catch(Exception ex) {....

...

   Adding support for .DeviceRemoved event, allows to at least know this has happened but  the thread executing the Xfer remains blocked.

Has anyone had a similar experience ?   any known workarounds ?  -  I presume we could move to asynchronous transfer but that seems a lot of work to deal with a rare fault condition, and I certainly wouldn't want to do that if I didn't know it would work.