CX3 CB failure in high speed mode

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
lock attach
Attachments are accessible only for community members.
BeCh_1049336
Level 1
Level 1
10 replies posted 5 replies posted 5 sign-ins

Hi,

I used CX3 to get image sensor with 328 x 744 x 2 (16bit) x 10 (fps) = 4.6MBps bandwidth.

For super speed mode, the result is correct and no image issue.

The correct frame info is as below.

BeCh_1049336_0-1613611264139.png

 

But, when I used high speed mode to get images, I got "CB failure" with these logs.

BeCh_1049336_1-1613612009324.png

And sometimes, I got the frame info as below.

BeCh_1049336_2-1613612396449.png

 

The sensor settings are the same in super speed and high speed mode, I only changed the descriptors in super speed and high speed.

Attached the "cycx3_uvcdscr.c" as well, could you please help me figure out what root cause might be?

Thank you.

Bert

0 Likes
1 Solution
lock attach
Attachments are accessible only for community members.

Edited:

Hello,

Thank you for the details.

From the Wireshark traces, I didn't see the USB errors. Can you try streaming (36 KB) on some other  Host PC and  host application like MPC- HC / eCamView. You can try streaming as YUY2 format (change GUID in descriptor file) for the other application

Please let me know if SDK1.3.4 is used. Please check the build variable (snippet attached) of the project.

For 42 KB, I missed out one point

Please try this configuration

CX3_UVC_DATA_BUF_SIZE (0xA800)
CX3_UVC_STREAM_BUF_COUNT (2)
0x10, 0xA8, 0x00, 0x00, /* No. of bytes device can rx in single payload: 42KB + 16*/

In addition to my previous response, please try Configuring horizontal blanking of the image sensor as high as possible (to do this vertical blanking can be reduced thereby maintaining same frame rate). While doing this make sure that vertical blanking does not go below ~350 us.

Please try this and let me know the results

Regards,
Rashi

View solution in original post

0 Likes
10 Replies