USB superspeed peripherals Forum Discussions

My device is fx3.

- I tried read UVC header via v4l2(https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/pixfmt-meta-uvc.html)

- The procedure is something like that in librealsense(https://github.com/IntelRealSense/librealsense/blob/master/src/linux/backend-v4l2.h). Open the video capture and meta device synchronously, after streamon, read video capture and meta one by one.

- In my experiment, the meta buffer is zero length as below shown

vidcap, buf: index: 0, byteused: 1843200, length: 1843200, ts: 90818755
meta, buf: index: 0, bytesused: 0, length: 1024, flags: 12000, ts: 90818755
vidcap, buf: index: 1, byteused: 1843200, length: 1843200, ts: 90818787
meta, buf: index: 1, bytesused: 0, length: 1024, flags: 12000, ts: 90818787
vidcap, buf: index: 2, byteused: 1843200, length: 1843200, ts: 90818823
meta, buf: index: 2, bytesused: 0, length: 1024, flags: 12000, ts: 90818823
vidcap, buf: index: 0, byteused: 1843200, length: 1843200, ts: 90818855
meta, buf: index: 0, bytesused: 0, length: 1024, flags: 12000, ts: 90818855
vidcap, buf: index: 1, byteused: 1843200, length: 1843200, ts: 90818891
meta, buf: index: 1, bytesused: 0, length: 1024, flags: 12000, ts: 90818891
vidcap, buf: index: 2, byteused: 1843200, length: 1843200, ts: 90818923
meta, buf: index: 2, bytesused: 0, length: 1024, flags: 12000, ts: 90818923
vidcap, buf: index: 0, byteused: 1843200, length: 1843200, ts: 90818955
meta, buf: index: 0, bytesused: 0, length: 1024, flags: 12000, ts: 90818955
vidcap, buf: index: 1, byteused: 1843200, length: 1843200, ts: 90818991
meta, buf: index: 1, bytesused: 0, length: 1024, flags: 12000, ts: 90818991
vidcap, buf: index: 2, byteused: 1843200, length: 1843200, ts: 90819023
meta, buf: index: 2, bytesused: 0, length: 1024, flags: 12000, ts: 90819023
vidcap, buf: index: 0, byteused: 1843200, length: 1843200, ts: 90819059
meta, buf: index: 0, bytesused: 0, length: 1024, flags: 12000, ts: 90819059

Any suggestions, Thanks in advance.

Regards

Rossi

Hi

I'm developing UVC 2.0 host firmware which receives mjpeg video stream from the webcam. The video is 640x480 30fps in mjpeg format.

When I analyze the stream received from the webcam, I found that SOI(Start of Image, 0xff 0xd8) and EOI(End of Image, 0xff 0xd9) does not match exactly.  When a SOI is found then there should be a matching EOI to complete a picture. But in my case it was not.  (See below)

As a result, when I played the stream received in the host firmware, video generated by VLC player resulted in broken images like below. (Camera is showing the ceiling of my office, btw)

I think this could be resulted from the bandwidth issue but I don't know what to tune at this moment. I tried to change DMA buffer size etc but ends up same results so far.

The host firmware handles mjpeg stream in manual mode (by dedicated receiving thread). I'm curious whether this is fast enough to handle the video(640x480 30fps mjpeg) or not.

Any comments will be highly appreciated.

Regards,

Rossi

Hello, I am designing a MIPI to USB3SS interface with the CX3 CYUSB3065-BZXC. The CX3 needs 3 clocks (to use watch dog). The MIPI sensor we are using uses a 37.125MHz clock, and so expecting that this will feed into REFCLK. Also a 19.2MHz clock is needed, and the 32kHz clock. I am thinking of using the Si5351A-B-GT with a single xtal to generate these 3 clocks, but concerned about the phase noise spec requirement on the CX3. Will the Si5351A and a crystal meet the CX3 phase noise requirement?

Here is the Si5351A jitter spec of 155ps pk-pk worst case.

And the CX3 phase noise spec.

Im not too sure how to reconcile if this part is okay to use or not.

It would be nice, as a single xtal can be used and then the output frequencies changed easily on a design.

Help on understanding if the Si5351A is suitable or not with the CX3 is appreciated.

I need to use both the USB Uart and SlaveFIFO, so I added the CDC interface to the FX3 device following the knowledge base article：Adding Communication Device Class Interface to FX3... - Infineon Developer Community

But when I  program the FX3, the device manager could not recognize the device correctly, as shown in the figure

According to the article description, I need to delete the original driver and reprogram it, the original description is

But after I delete the driver, the device is recognized as "WestBridge", so I can't burn the img file to it anymore.

What can I do to recognize the device correctly?

Hi,

I'm working with a product that will have multiple FX3 based devices connected and we need to distinguish between them reliably. I understand that every chip has a unique 64 bit ID at address 0xE0055010 and that the correct order to read the two registers is 0xE0055014 and then 0xE0055010. I have found this much info in the forum.

So I can read the ID like

uint64_t id;
CyU3PReadDeviceRegisters((uint32_t*)0xe0055010, 2, (uint32_t*)&id);

And I have two questions regarding this;

1. Will CyU3PReadDeviceRegisters() read the data in the correct order as stated above, or will I need to flip the 32-bit values around?
2. Is there a preferred interpretation of this 64 bit ID? Is it an ascii string? A unicode string? An integer? Signed? Hex characters? Does it have an expected format?

Regards,
Georgios

I need to use both UART and SPI interface, FX3's SPI interface and UART interface are shared, now my SPI is connected to FLASH, I need to power on through SPI FLASH, so I can't use its UART function, but FX3 has "16-bit data bus + UART + SPI + I2S " mode. In this mode, UART is mapped to GPIO46~49. Can I use the following settings to enable me to use both UART and SPI FLASH BOOT?

io_cfg.isDQ32Bit = CyFalse;

io_cfg.s0Mode = CY_U3P_SPORT_INACTIVE;
io_cfg.s1Mode = CY_U3P_SPORT_INACTIVE;
io_cfg.useUart = CyTrue;
io_cfg.useI2C = CyFalse;
io_cfg.useI2S = CyFalse;
io_cfg.useSpi = CyTure;
io_cfg.lppMode = CY_U3P_IO_MATRIX_LPP_DEFAULT;
/* No GPIOs are enabled. */
io_cfg.gpioSimpleEn[0] = 0;
io_cfg.gpioSimpleEn[1] = 0x08000000;
io_cfg.gpioComplexEn[0] = 0;
io_cfg.gpioComplexEn[1] = 0;

And, can I still use the virtual COM port function of the UART in this mode?

Hi,

I am using a CX3 Dev Kit to interface to an Omnivision OCSHA10 image sensor. I had asked earlier if there was an API to get the frame buffer data returned by the image sensor via Solved: Re: How to get image frame content in CX3 - Infineon Developer Community.

Even if there is no API to get the frame buffer, are there any UVC related data structures which I can check to see the data that is being sent to the connected PC?

Thanks and Regards,

Subramanyan

Hi infineon team,

we are planning to replace 19.2 MHz external crystal from our FX3 board  to 26 MHz crystal. we have few queries regarding change in the external crystal

1) will it affect any kind of internal operations?

2) will the prescaler outputs value will be same as 19.2 MHz? 

kindly give us suggestions / note points to be taken care while changing to 26 MHz . 

Thanks and regards, 

Rakesh rajan

@AliAsgar @JayakrishnaT_76 @Rashi_Vatsa