TDA4VM: TDA4 live tuning error question

Hi, thank you for your reply.

No more errors are displayed in DCC Tool. Your steps are very effective. Thank you.

Now I have another problem.

When I use single_cam to light up the camera, I use DCC Tool to transfer the changed content to TDA4. But I don't see any change in the picture on the monitor. From the software I see the following error:

Enter Choice:     57.244754 s: ISS: Starting sensor [IMX390-UB953_D3] ... Done !!!
get_dcc_dir_size : Could not open directory or directory is empty /opt/vision_apps/dcc/IMX390-UB953_D3/wdr
[MCU2_0]     57.279390 s: IMX390_GetWBPrgFxn: sensor_pre_gain = 0
   115.135522 s:  VX_ZONE_ERROR:[ownContextSendControlCmd:751] Command ack message returned failure cmd_status: -1
[MCU2_0]    115.135265 s:  Invalid Camera Id 390
[MCU2_0]    115.135337 s:  VX_ZONE_ERROR:[tivxVpacVissSetParamsFromDcc:213] dcc_update Failed !!!
[MCU2_0]    115.135390 s:  VX_ZONE_ERROR:[ownTargetNodeDescNodeControl:1037] SendCommand Failed
   125.923338 s:  VX_ZONE_ERROR:[ownContextSendControlCmd:751] Command ack message returned failure cmd_status: -1
[MCU2_0]    125.923102 s:  Invalid Camera Id 390
[MCU2_0]    125.923169 s:  VX_ZONE_ERROR:[tivxVpacVissSetParamsFromDcc:213] dcc_update Failed !!!
[MCU2_0]    125.923225 s:  VX_ZONE_ERROR:[ownTargetNodeDescNodeControl:1037] SendCommand Failed

Please help me solve this problem, thank you.

Zhang Jia Rong said:

Invalid Camera Id 390

It suggests that your camera ID (DCC ID) is not 390.

Do you have 390 on both your tuning tool side and EVM side?

If you use the tuning tool output xml in SDK, does it work without any issue?

Hi, thank you for your reply.
My camera is otobrite IMX390.
I can use your single_cam code to light up my camera without changing any programs.
I would like to ask, does IMX390 have to be D3?

''Do you have 390 on both your tuning tool side and EVM side?''What does this mean?

''If you use the tuning tool output xml in SDK, does it work without any issue?'' I'm not sure if I did this, but I used python scripts to make adjustments and throw the output files into SDK card, and then light up the camera, the picture will change.

Zhang Jia Rong said:

''Do you have 390 on both your tuning tool side and EVM side?''What does this mean?

Both tuning tool and EVM have to use 390 as DCC ID to avoid this invalid camera id issue.

Zhang Jia Rong said:

I used python scripts to make adjustments and throw the output files into SDK card, and then light up the camera, the picture will change.

If you use 390 as DCC ID in python script, it should work.
I am not sure why you get the error message saying 390 is invalid.
We have never seen this problem while sensor driver use 390 and tuning tool uses 390 as well.

Zhang Jia Rong said:

I would like to ask, does IMX390 have to be D3?

As long as the driver works, your otobrite camera has same electrical design as D3's.
Tuning has to be done as optical stuff (lens etc.) should be different.

BTW, previously there was some network issue at Foxxonn for tuning tool to work properly with EVM.
I am not sure if that can cause the issue you have.

From the message, 390 is the correct DCC ID we use for IMX390.

Hi, thank you for your reply.

Is this the DCC ID you are talking about? But when I set the name to 390 and then transferred the data to the EVM, the image still did not change, and the error message was the same as the EVM content above.

The operation manual mentions that I need to use Ethernet to set the IP addresses of the EVM and PC to be the same. I am using a WIFI machine to do this, so I guess it has nothing to do with the company network?

Zhang Jia Rong said:

Is this the DCC ID you are talking about?

No, that is the sensor name.

DCC ID is the "Sensor ID" below that.

Hi, thank you for your reply.

You are right, sorry I didn't see it clearly. After I changed the sensor ID to 390, the screen changed.

Here are my steps

1. Open DCC Tool and set the parameters value (sensor ID needs to be changed to 390)
2. Open BLC
3. Set EVM address
4. Set data pedestal value
5. Use EVM to light up the lens
6. Press process plugin
7. Press update the current plugin dcc file
8. EVM screen changes

Above are my steps.

Currently there is another problem.

The screen changed when I sent data to EVM for the first time, but the second time the screen didn’t change . What could be the problem?

Because when I changed the data pedestal value to 1 and 100, according to my understanding, the two pictures should be different, but from the picture, I can't see any difference. The following is when I changed the data pedestal value to 1 and 100 images.

The last picture is the response after I used single_cam to open the lens. However, after I did steps 6 and 7, although the image changed on the EVM, there was no response that I transferred the data from DCC to EVM. Is this correct?

Zhang Jia Rong said:

Because when I changed the data pedestal value to 1 and 100, according to my understanding, the two pictures should be different, but from the picture, I can't see any difference.

Did you press all the 3 buttons after you change the value?

Hi, thank you for your reply.

In this sentence, "Did you press all the 3 buttons after you change the value?", does the 3 buttons refer to these 3 buttons?

Is the order of usage from left to right correct?

Zhang Jia Rong said:

Is the order of usage from left to right correct?

Yes, in that order after you update any parameter in the GUI.