DS90UB960-Q1: Pattern Generator testing in vison apps

Hi Christopher,

Thanks for reaching out with this question. From the FPD-Link side, these patterns are different than are generated by the ser/des. There is a pattern generator both on the UB953 serializer, and the UB960 deserializer hub, but these patterns will more closely match the patterns below.

The TDA team may be able to provide some additional background here on this TDA4VM - sensor fusion board platform, let me try to check with their team.

Best,

Thomas

Hi Thomas,

Thanks for the reply.

And looking forward to the further information.

Best,

Christopher

Hi Thomas,

Here are additional information:

The version of rtos sdk I used is "ti-processor-sdk-rtos-j721e-evm-08_06_01_03"
The sensor fusion board is "TIDA-01413"

Thanks

Hi Christopher,

I'm seeing the same as you are seeing on SDK 8.6.

The raw pattern looks correct, but the YUV is incorrect somehow. I see correct pattern on SDK 8.5.

Let me check internally what changes went in regarding this on SDK 8.6.

Meanwhile, can you tell me your usecase here? Is there anything in particular you are looking for?

Regards,

Nikhil

Hi Nikhil,

Thanks for the information.

We are preparing to port new yuv sensor on TDA4, and just try to get image data from pattern generator first since the camera module still not received yet..

It's good to hear that the raw test pattern of sensor d:UB9xxx_RAW12_TESTPATTERN looks correct.

I have some update for sensor e:UB96x_UYVY_TESTPATTERN:

Below image shows the result of cap_0000.yuv in uyvy422 format:

For the same test pattern configuration except changing data type from YUV422_8B to RAW12:

//{0xB2, 0x1E, 0x1}, // PGEN_CSI_DI:MIPI_CSI2_DT_YUV422_8B
{0xB2, 0x2C, 0x1}, // PGEN_CSI_DI:RAW

//{VX_DF_IMAGE_UYVY, 7}, /*dataFormat and MSB [0]*/
{TIVX_RAW_IMAGE_16_BIT, 11}, /*dataFormat and MSB [0]*/

I got different result as below (img_viss_0000.yuv with nv12 format):

F.Y.I.

Thanks again for looking into this.

Regards,
Christopher

Hi Nikhil,

Here are some information updated.

We got the camera module and already integrated it with imaging sensor framework in rtos sdk.

It is a YUV422-8bit sensor.

Below shows the output of app_single_cam on both SDK 8.5 and 8.6.

SDK 8.5 (looks correct)

SDK 8.6 (incorrect, some noise on dark green background)

F.Y.I.

Since all of our implementations were based on SDK 8.6, still look forward to the solution on SDK 8.6.

Thanks.

Best,
Christopher

Hi Christopher,

I had raised this issue internally.

Placing the JIRA here for TI's internal tracking purpose.

[ADASVISION-6078] UB96x_UYVY_TESTPATTERN not working with the vision_apps single and multicam demo - Texas Instruments JIRA

The issue seems to be fixed in SDK 9.0 and the issue is not seen in SDK 8.5

I'm checking with the experts internally regarding the changes that resolved this issue.

Meanwhile, could you let me know if you have plans to migrate to SDK 9.0?

Regards,

Nikhil

Hi Nikhil,

Thanks for tracking this issue.

Regarding SDK 9.0 migration, it is an option, and we will review the changes, evaluate the effort and schedule first.

Currently we move our development to SDK 8.5 and it goes well so far.

Regards,

Christopher

Sure. Thank you for the update

My first guess was that the issue was caused by some changes under "imaging/sensor_drv/" for serdes/fusion-2.

I reviewed the changes there between "8.5 and 8.6" and "8.6 and 9.0" and merged 9.0 changes back into 8.6, but it does not make any difference for UYVY test pattern.
Therefore, the issue is probably caused by other changes out of "imaging/sensor_drv/" (e.g., CSIRX).

Hi Christopher,

Christopher said:

I got different result as below (img_viss_0000.yuv with nv12 format):

Could you please share this "img_viss_0000.yuv"?
Your gray picture above looks correct to me for the UYVY test pattern.

Hi Gang, 

The file was attached here for your reference.

Thanks.

Regards,

Christopher

Christopher said:

The file was attached

Thanks for sharing!

Christopher said:

//{0xB2, 0x1E, 0x1}, // PGEN_CSI_DI:MIPI_CSI2_DT_YUV422_8B
{0xB2, 0x2C, 0x1}, // PGEN_CSI_DI:RAW

//{VX_DF_IMAGE_UYVY, 7}, /*dataFormat and MSB [0]*/
{TIVX_RAW_IMAGE_16_BIT, 11}, /*dataFormat and MSB [0]*/

The pattern is changed to RAW from YUV already I suppose.

Hi Gang,

Yes, it is the output with modification which changed to RAW from YUV.

The saved file name is img_viss_0000.yuv (nv12 format) because it is the the result from VISS node.

And cap_0000.zip (uyvy422 format) is the output of original uyuv test pattern without any modification.

F.Y.I.

Thanks.

Christophser

Hi Gang,

Thanks for status update.

We had moved our development to SDK 8.5, and SDK 9.0 is still under evaluation.

Regards,

Kris

Christopher said:

We had moved our development to SDK 8.5, and SDK 9.0 is still under evaluation.

Thanks for the confirmation!

Please feel free to open a new thread if you have any further questions.

Hi Gang,

Sure!

And thanks for all of your great support!

Best,

Christopher

Hi Gang,

Thanks for providing the information of this issue.

I will try to compare csirx_drvUdma.c between 8.5, 8.6, and 9.0.

I think this issue could be marked as resolved.

Thank again for the great support.

Regards,

Christopher