TDA4VH-Q1: Vision Apps > App Single Cam IMX390

Hi Berke,

We have not seen similar issues previously.
Could you please share some raw/yuv images showing the problem?

Kaan Berke Ulusoy said:

However, we thought that the sensor itself is same that is why we were not expecting to see any problem while using the built in registers and isp bins.

TDA4 needs to control sensor exposure through i2c.
Do you see that is working properly with gmsl serdes?

Hi Gang,

I don't know why but I cannot upload captured images to this message. Is there any other way to do it? 

Actually yes, we activated the auto exposure and depending on the lightning condition of the environment we observed that there are some settings changing through i2c bus on the command window.

In addition to all of this, I would like to share one more information. We get this error "[MCU2_0] 95.198346 s: VX_ZONE_ERROR:[tivxCaptureDequeueFrameFromDriver:885] CAPTURE: ERROR: Incomplete Frame for Ch0 !!!" continuously, could it be related to our issue somehow or what could be the reason for that?

Thanks,

Berke

Kaan Berke Ulusoy said:

I don't know why but I cannot upload captured images to this message. Is there any other way to do it? 

Hi Berke,

You may zip your files first and then upload the zip file.

Kaan Berke Ulusoy said:

We get this error "[MCU2_0] 95.198346 s: VX_ZONE_ERROR:[tivxCaptureDequeueFrameFromDriver:885] CAPTURE: ERROR: Incomplete Frame for Ch0 !!!" continuously, could it be related to our issue somehow or what could be the reason for that?

Yes, this might suggest that some issue is present in transferring sensor raw images via serdes to TDA4.

In the video, there seems some broken raw image frames, e.g., green on the top and red at the bottom.

8637.yuv.zip

Thank you for the first diagnosis, Is there a way to find exactly which setting is problematic or what would you suggest at this point?

Hi Berke,

Kaan Berke Ulusoy said:

8637.yuv.zip

Thanks for sharing!

The raw image is broken and the bottom ~100 rows of pixels are garbage.
There should be some issue in transferring sensor raw image from IMX390 to TDA4.

What is the actual color of these letters?
I am not sure if the raw image is in the right color pattern (IMX390 by default is RGGB).

Kaan Berke Ulusoy said:

Is there a way to find exactly which setting is problematic or what would you suggest at this point?

I am not familiar with serdes and CSI details.
You may need to check if there is any error flags in serdes first.

Hi Gang,

Thank you for this information. The actual color of the letters is red. You are right, I will check the relevant parts in the code.

Berke

Hi Gang,

Sorry for my late reply, it was due to bank holiday last week. 

We tried to understand the problem here and came with a few questions. 

1. First of all, thank you for your feedback yes according to the data sheet, recommended pixels to be used is in the format of GBRG even though the effective pixels start with RGGB, it seems there is a 1 pixel shift. We found a register in IMX390 to shift the pixels would that help to correct color format in YUV image?
2. Regarding the garbage pixel you are right there is a problem with serdes or CSI, should we create a new problem report for that? Because it seems like we correctly set ser/des and CSI as we already used this ser/des with another Image sensor which as built in ISP without any problem. Do you know which settings should be configured through serialized for Imaging sensor? Like INCK clock?
3. We found another thread in the forum about this Error message "[MCU2_0] 95.198346 s: VX_ZONE_ERROR:[tivxCaptureDequeueFrameFromDriver:885] CAPTURE: ERROR: Incomplete Frame for Ch0 !!!". Acording to this thread this message pops up if the size of recieved image and defined settings are not compatible. Even though we used correct pixel sizes, we still get this error. Could it be because of the same problem explained in the previous item? 
4. Apart from that, we didn't observe any other error or warning messages in the log while running the vision apps single cam app. Is there any other way to debug this issue?

Thanks a lot.

Kind Regards,

Berke

Hi Berke,

Kaan Berke Ulusoy said:

First of all, thank you for your feedback yes according to the data sheet, recommended pixels to be used is in the format of GBRG even though the effective pixels start with RGGB, it seems there is a 1 pixel shift. We found a register in IMX390 to shift the pixels would that help to correct color format in YUV image?

You may either change the color format of the sensor output to RGGB or change the VISS settings to GRBG.
Both should be fine.

Kaan Berke Ulusoy said:

Regarding the garbage pixel you are right there is a problem with serdes or CSI, should we create a new problem report for that? Because it seems like we correctly set ser/des and CSI as we already used this ser/des with another Image sensor which as built in ISP without any problem. Do you know which settings should be configured through serialized for Imaging sensor? Like INCK clock?

I am not familiar with SerDes details.
The raw camera output in 12-bit raw image format and the other should be in some YUV format.
I am not sure if SerDes settings need to be done differently or not.

You may refer to existing IMX390 drivers in SDK to see if you can find anything.

On Q3 and Q4, I am copying my friend Brijesh Jadav for his comments

Gang Hua said:

change the VISS settings to GRBG.

To be clear, you may set up VISS settings for GRBG following the link below.

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1275034/faq-default-dcc-profile-generation-tool-for-tda4-am6xa-isp-vpac?tisearch=e2e-sitesearch&keymatch=%20user%3A35541

Hi Berke,

Kaan Berke Ulusoy said:

Please see attached captures.

The raw image looks Ok to me.

Kaan Berke Ulusoy said:

Could it be because of the green gain or Auto white balance?

AWB has to be calibrated for your camera.

https://www.ti.com/lit/pdf/sprad86

https://www.ti.com/lit/pdf/spracu7

Hello  Gang,

Thanks a lot for your support. 

I went through the shared links now it is a bit more clear. 

Allow me to ask one thing to understand correctly. You have said that the raw image looks okay, so greenish like visual is okay for a raw image of RGGB sensor? Since we also see the same thing in the display screen while running the app, I am assuming the raw image is displayed on the monitor not viss.yuv, is that correct understanding? Further steps is actually relevant to isp tuning itself.

Also, since the initial problems are resolved, I will close this thread. Thanks again.

Berke