cancel
Showing results for 
Search instead for 
Did you mean: 

USB Superspeed Peripherals

wayu_4276666
New Contributor II

Hi Sir,

I have an application to use the sensor(IMX390).

The sensor output data format are 1936*1114@40FPS, RAW12.

I use E-CAM to receive the DATA from CX3.

The CX3 Descriptor as below:

    /* Class specific Uncompressed VS Frame Descriptor 1 - 1080p */

    0x1E,                               /* Descriptor size */

    CX3_CS_INTRFC_DESCR,                /* Descriptor type*/

    0x05,                               /* Subtype:  frame interface*/

    0x01,                               /* Frame Descriptor Index: 1 */

    0x00,                               /* No Still image capture method supported */

    0xAC,0x05,                          /* Width in pixel:  1452 */

    0x58,0x04,                          /* Height in pixel: 1112 */

    0x00,0xD0,0x97,0x3D,                /* Min bit rate (bits/s): 1452 x 1112 x No Of Bits per Pixel x FrameRate = 1033359360  */

    0x00,0xD0,0x97,0x3D,                /* Max bit rate (bits/s): Fixed rate so same as Min */

    0x40,0x46,0x31,0x00,                /* Maximum video or still frame size in bytes(Deprecated): 1452 x 1112 x 2 */

    0x90,0xD0,0x03,0x00,                /* Default frame interval (in 100ns units): (1/40)x10^7 */

    0x01,                               /* Frame interval type : No of discrete intervals */

    0x90,0xD0,0x03,0x00,                /* Frame interval 3: Same as Default frame interval */

The E-CAM Resolution is 1452*1112@40FPS, UYVY this parameter can see the image on E-CAM,

if I use the 1452*1114@40FPS, UYVY the E-CAM show the black frame.

Q1: Is the IP(MIPI-CSI2) of CX3 has a filter to drop the line with some data type?

       Please reference the attachment files to check the data type and frame architecture.

BR

Ben

0 Likes
1 Solution
wayu_4276666
New Contributor II

Hi Sir,

According to this description"The data types 0x10 and 0x2F are not supported by CX3."

The Ignored OB's data type is 0x10 and ignored OB is 2 lines.

So. this is the reason why my sensor SPEC is 1936*1114, but the CX3 received the data is 1936*1112.

Thank you for your help.

BR

Ben

pastedImage_0.png

View solution in original post

0 Likes
24 Replies
wayu_4276666
New Contributor II

Hi Sir,

If you need more information,

Please let me know.

0 Likes
AlbertB_56
Employee

Hello,

Thank you for contacting Cypress Semiconductor

I will need to transfer this thread to the EZ_USB team for further technical support

Best regards,

Albert

Cypress Semiconductor Corp.

An Infineon Technologies Company

0 Likes
wayu_4276666
New Contributor II

Hi Albert,

Do you have any further information?

Or need some Information from me?

BR

Ben

0 Likes
JayakrishnaT_76
Moderator
Moderator

Hello Ben,

Apologies for the delayed response.

As per your original description I find that you want to stream the resolution 1936x1114 RAW12 format @40FPS. Please share the snapshot of the MIPI configuration utility for this resolution so that I can evaluate it at my end. Also, please let me know if you are padding or packing the incoming data. According to my understanding, you are packing the incoming data into 16 bits. Please correct me if Iam wrong.

Best Regards,

Jayakrishna

Best Regards,
Jayakrishna
0 Likes
wayu_4276666
New Contributor II

Hi Sir,

thank you for your reply.

MIPI Configuration and USB descriptor in the attachment.

The GPIF bus width config as 24-bit.

According to my understanding, you are packing the incoming data into 16 bits.

-> I packing the income data into 24 bits.

0 Likes
JayakrishnaT_76
Moderator
Moderator

Hello,

In the original description I found that 1936*1112 in RAW12 @40fps was correctly streamed by E-Cam view. Please let me know if the problem exists while streaming 1936*1114 in RAW12 @40fps using E-Cam View or not.

Please share the snapshot of CX3 Receiver Configuration Tab of the MIPI configuration utility for the failing configuration as is done under step 7 of the following KBA.

Steps to Setup up MIPI CSI Camera Solution with CX3 – KBA225748

Best Regards,

Jayakrishna

Best Regards,
Jayakrishna
0 Likes
wayu_4276666
New Contributor II

Hi Sir,

In the original description I found that 1936*1112 in RAW12 @40fps was correctly streamed by E-Cam view. Please let me know if the problem exists while streaming 1936*1114 in RAW12 @40fps using E-Cam View or not.

->The 1936*1114@40FPS Raw12 the E-CAM was show black frame. Letter I will upload my test result(1936*1114).Please see the attachment.

Please share the snapshot of CX3 Receiver Configuration Tab of the MIPI configuration utility for the failing configuration as is done under step 7 of the following KBA.

->I did not use CX3 Receiver Configuration to generate the 4 files, I use the old project and modify the frame parameters by myself.

-> I compared 2 resolutions, where is the different fields in the 4 files.

-> I will use the  CX3 Receiver Configuration to generate the files and check the E-CAM working status.

0 Likes
JayakrishnaT_76
Moderator
Moderator

Hello,

For supporting a new resolution using CX3, the following needs to be done:

1. Add the details for the new resolution in the Image sensor configuration tab of MIPI configuration Utility.

2. Go to the CX3 Receiver Configuration tab of the MIPI configuration utility and adjust the parameters so that errors are not shown.

3. Save the generated files.

4. For packing the incoming data from the image sensor, modifications are to be done on the generated files. Please refer to the following KBA to understand more on the modifications:

Streaming RAW10 Format Input Data to 16/24-bit Output Format in CX3 MIPI CSI-2 - KBA224387

5. The image sensor needs to be configured to send out frames with the new resolution. For this, the image sensor configuration settings (register settings for the new resolution) also need to be added to the project.

Please let me know if you have any queries on this.

Best Regards,

Jayakrishna

Best Regards,
Jayakrishna
0 Likes
JayakrishnaT_76
Moderator
Moderator

Hello,

Please confirm that you have done all the steps correctly and in order as mentioned in my previous response for streaming 1936*1114 RAW 12 @ 40fps. Please share a snapshot of the MIPI configuration utility for this resolution as requested in my response 6. In addition to this, please share the descriptor file for us to check at our end.

Best Regards,

Jayakrishna

Best Regards,
Jayakrishna
0 Likes
wayu_4276666
New Contributor II

Hi Jayakrishna,

in the attachment is 1936*1114 &1936*1112 relation files.

I did not use the CX3 Receiver to configuration, so I can not offer you the snapshot.

But now, I re-do the project need some time.

I decided to use the method which you mention.

BR

Ben

0 Likes
JayakrishnaT_76
Moderator
Moderator

Hello Ben,

Sure, please take your time to create the project again from scratch. Please share the snapshots and files that I requested in my previous response once it is ready.

Best Regards,

Jayakrishna

Best Regards,
Jayakrishna
0 Likes
wayu_4276666
New Contributor II

hi Sir,

All of my setting files and snapshot are in the attachment.

BR

Ben

0 Likes
JayakrishnaT_76
Moderator
Moderator

Hello,

Thank you for sharing the requested files and snapshots. I referred to the files corresponding to 1452*1114. Please find my comments on the same below:

1. Please confirm that the Input video format from the image sensor is RAW12 itself. This is because, in the snapshot of the MIPI configuration utility, I saw that you are using UYVY instead of RAW12 for the input video format. Also, please confirm that the sensor is configured to send data in RAW12 format itself.

2. Inside the descriptor file, the calculations for Min and Max bit rates seems to have a mistake. The correct calculation for bit rate is shown below:

bit rate = 1452*1114*16*30 = 776,413,440 (0x2E47 2100)

Please use this setting for the min and max bit rates in the descriptor file.

3. Please provide the UART debug logs for debugging the issue.

Best Regards,

Jayakrishna

Best Regards,
Jayakrishna
0 Likes
wayu_4276666
New Contributor II

Hi Sir,

1. Please confirm that the Input video format from the image sensor is RAW12 itself. This is because, in the snapshot of the MIPI configuration utility, I saw that you are using UYVY instead of RAW12 for the input video format. Also, please confirm that the sensor is configured to send data in RAW12 format itself.

->The sensor output format is raw12.

->Do I have to change the configuration of input video format from UYVY to RAW12?

2. Inside the descriptor file, the calculations for Min and Max bit rates seems to have a mistake. The correct calculation for bit rate is shown below:

bit rate = 1452*1114*16*30 = 776,413,440 (0x2E47 2100)

-> The FPS is 40 not 30.

Please use this setting for the min and max bit rates in the descriptor file.

3. Please provide the UART debug logs for debugging the issue.

->In the log, the Frm_sz=3229248

->Frame_Height * Frame_Width * Bytes_Per_Pixel = Frm_sz

->1112*1452*2=3229248

->So, according to above description

->the Frame_Height=1112 not 1114,

->but my sensor frame_height is 1114,

->this situation make me confusing.

Ben

0 Likes
JayakrishnaT_76
Moderator
Moderator

Hello,

Apologies for making the mistake in data rate calculations in my previous response.

I tested the resolutions 1916*1080, 1916*1079, 1916*1078 and 1916*1077 in YUY2 format at 30fps using Denebola kit and could not reproduce your issue. I did not see loss of any lines as you reported. It seems like the sensor is not configured correctly. Please check and confirm that the sensor configurations are correct.

As a test, can you please try streaming 1936*1110 in Raw 12 at 40fps and let us know the result.

Best Regards,

Jayakrishna

Best Regards,
Jayakrishna
0 Likes
wayu_4276666
New Contributor II

Hi Sir,

As a test, can you please try streaming 1936*1110 in Raw 12 at 40fps and let us know the result.

->I use above parameters to test. Please see the attachment files.

->"In Raw12", do you mean the Input data format configuration as below

pastedImage_0.png

0 Likes
JayakrishnaT_76
Moderator
Moderator

Hello,

Yes, by RAW 12 I mean to say that the input format needs to be set to 12 in the MIPI configuration utility and the sensor needs to be configured to output pixels in RAW 12 format. I find that you are able to stream 1936*1110 in RAW12 format at 40fps from the files shared in your last response. So, please double check the configurations settings for 1936*1114 in RAW12 format at 40fps from the sensor vendor. We haven't seen any limitations on the number of lines (V-Active) for CX3.

Best Regards,

Jayakrishna

Best Regards,
Jayakrishna
0 Likes
wayu_4276666
New Contributor II

Hi Sir,

This time, i config the Input Data format as RAW12.

The test result as below:

1.1936*1114@40fps, RAW12, the ECAM show black frame, the fps=0

in the number of bits per pixel field, input format was raw12 ,the value was 0xc, show black frame

I change the field from 0xc to 0x10, show black frame.

2.1936*1112@40fps, RAW12, the ECAM can show the image.

please reference the attachment.

0 Likes
JayakrishnaT_76
Moderator
Moderator

Hello,

You need not change the number of bits per pixel field in the descriptors. It can be set to 0x10 (16) itself. As mentioned in my previous response, it seems like the image sensor configuration settings (sensor's register settings that are configured using I2C interface of FX3) are not proper for the frame 1936*1114 in Raw12 at 40fps. As you were able to stream the resolution 1936*1110 in Raw12 at 40fps, we can understand that there is no limitation on the number of lines (V-Active) for CX3. We tested the following resolutions at our end and did not find any issue as mentioned:

1. 1916*1080 YUY2 at 30fps

2. 1916*1079 YUY2 at 30fps.

3. 1916*1078 YUY2 at 30fps

4. 1916*1077 YUY2 at 30fps

This further proves that there is no limitation on the number of lines or V-Active for CX3. Please verify that the image sensor registers are configured correctly to output 1936*1114 in Raw12 at 40fps. Please verify these configuration settings (sensor's register settings that are configured using I2C interface of FX3) from the sensor vendor.

Best Regards,

Jayakrishna

Best Regards,
Jayakrishna
0 Likes
wayu_4276666
New Contributor II

Hi Sir,

Thank you for your help.

I will check the sensor setting, which parameter is correct or not.

Ben

0 Likes
wayu_4276666
New Contributor II

Hi Sir,

I have a question about raw sensor data type

According to your reply, "we can understand that there is no limitation on the number of lines (V-Active) for CX3".

Q:Is any data type that CX3 can received?

My sensor used data type as below

pastedImage_0.png

0 Likes
JayakrishnaT_76
Moderator
Moderator

Hello,

The data types 0x10 and 0x2F are not supported by CX3.

Best Regards,

Jayakrishna

Best Regards,
Jayakrishna
0 Likes
wayu_4276666
New Contributor II

Hi Sir,

According to this description"The data types 0x10 and 0x2F are not supported by CX3."

The Ignored OB's data type is 0x10 and ignored OB is 2 lines.

So. this is the reason why my sensor SPEC is 1936*1114, but the CX3 received the data is 1936*1112.

Thank you for your help.

BR

Ben

pastedImage_0.png

View solution in original post

0 Likes