TDA4VH-Q1: Use Video Codec chip for H264 encoding occasional device opening failure problem.

Hello, 

Are you only finding this error on Linux+RTOS? Have you experienced this on the Linux Processor SDK?

Thanks,
Sarabesh S.

Hi, 

I don't understand what you mean, do you mean to run Linux only with A72 core and not start with R core? this is a situation I have not tried.

Yes, exactly. Or you could try running a decode pipeline on the Vision Apps SDK command line like shown below:

• gst-launch-1.0 filesrc location=<h264_input_path> ! queue ! h264parse ! v4l2h264dec ! videoconvert ! video/x-raw,format=NV12 ! fakesink

You can find the Linux 9.01 Processor SDK here: https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-J784S4/09.01.00.06

Let me know your results.

Thanks,
Sarabesh S.

Hi

Is this error related to gsteamer? I was not using gsteamer when this problem occurred.

I found that this error appeared after the system started, even if I didn't do anything.

Hi,

I find that the error occurs when wave5_pm_suspend is called.

Hello

jin zhu said:

Is this error related to gsteamer? I was not using gsteamer when this problem occurred.

I was trying to understand in what scenario are you seeing this error? Such as a GStreamer pipeline, a TI demo, etc.

Did you make any modifications to the CODEC driver or the Linux+RTOS SDK? 

BR,
Sarabesh S.

Hi

I didn't make any changes to the CODEC driver

Hi,

The error occurred on the  wave5_vpu_open_enc  and  wave5_vpu_open_dec interface.

Code path:

drivers\media\platform\chips-media\wave5\wave5-vpu-enc.c

drivers\media\platform\chips-media\wave5\wave5-vpu-dec.c

Hello, 

I will test this early next week and come back to you with my results. Thank you for your patience.

BR,
Sarabesh S.

Hello,
Is there any progress?

BR.

Hello

I tested it on the TI evm board and didn't find this problem. The problem came up on our custom board.

The drivers are exactly the same on both devices, but the phenomena are different.

H264/265 chip is the chip inside the SOC, will the external circuit Settings affect it?

We checked the power supply, but we found nothing wrong.

This problem occurs occasionally. Can you help me analyze the cause of this problem?

thank you.

That is interesting, I am not sure what the problem could be since the driver is working successfully on our EVM. I will think on this and let you know if I come up with anything.

Thanks,
Sarabesh S.

Hello,

Were you able to identify the problem on your custom board? The external circuit settings should not effect it. I don't have a TDA4VH with me currently, but could you run k3conf dump clock and identify the CODEC clocks- there should be 2 (CODEC0 and CODEC1). Once you identify the CODEC clocks, please check what the frequency they are running at. ACLK, CCLK, and PCLK should be running at 600MHz and BCLK should be running at 400MHZ for each CODEC clock.

BR,
Sarabesh S.

Glad to hear you were able to find a solution by delaying the Board_init function on MCU2_0. Let me know if anything else comes up.

BR,
Sarabesh S.