TDA4VM: DECODER hardware

xueming tian

Part Number: TDA4VM

HI, TI

Is there a hardware or SDK restriction on 64k pages and corresponding scenarios for tda4? 64k must be used ?

The specific information is as follows：

In Processor SDK Linux J721e, DECODER hardware supports the following codecs:
• Video Decode: H.264, HEVC/H.265, MPEG4/H.263, WMV9, VC-1, MPEG2, DivX, AVS, RealVideo, VP8, VP6, Sorenson
• Image Decode: MJPEG

Support for H264 format files as described on the web page. Actually input H264 video, decoding error.

Tidec_decode supported format information is not displayed.

Tienc_encode supported formats are displayed in the help message.

Whether TI can provide relevant video footage ?

Thanks and Regards

over 4 years ago

0 Prashanth Kumar15 over 4 years ago

Mastermind 8775 points

Hi,

xueming tian said:
Is there a hardware or SDK restriction on 64k pages and corresponding scenarios for tda4? 64k must be used ?

Can you elaborate more on this?

Along with:

SDK version?
Linux or RTOS?
The command you used to decode.

xueming tian said:
Support for H264 format files as described on the web page. Actually input H264 video, decoding error.

Tidec_decode supported format information is not displayed.

Tienc_encode supported formats are displayed in the help message.

The COdec driver in Latest SDKs Support:

Decoder: H.264, H.265(HEVC) and JPEG as of now.
Encoder: H.264 only.

More information can be found in Documentation section in SDK download page: www.ti.com/.../PROCESSOR-SDK-LINUX-J721E

0 xueming tian over 4 years ago in reply to Prashanth Kumar15

Intellectual 631 points

Thanks, Prashanth Kumar15:

we want to run the video framework on the A72 core.

1、SDK Linux for J721e 08_01_00

2、Linux

0 Prashanth Kumar15 over 4 years ago in reply to xueming tian

Mastermind 8775 points

Hi,

As Mentioned above,

The Codec driver in Latest SDKs Support:

Decoder: H.264, H.265(HEVC) and JPEG as of now.
Encoder: H.264 only.

More information can be found in Documentation section in SDK download page: www.ti.com/.../PROCESSOR-SDK-LINUX-J721E

You can use gstreamer to get the video demo running at your setup.

0 xueming tian over 4 years ago in reply to Prashanth Kumar15

Intellectual 631 points

When new multimedia materials are used, the OS panic occurs due to H.264 decoding.
The exception occurs in the firmware response process. An exception occurs in accessing the memory. The memory pointer points to an invalid address. After checking the driver code, I did not find the value assignment and suspected that the problem was related to the firmware.

calltrace:

[123717.848904] decoder_service_firmware_response failed
[123717.853947] [TID=0x0295001B] [DECODE_FAILED]
[123717.858304] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000034
[123717.867159] Mem abort info:
[123717.870032] ESR = 0x96000007
[123717.873166] EC = 0x25: DABT (current EL), IL = 32 bits
[123717.878551] SET = 0, FnV = 0
[123717.881684] EA = 0, S1PTW = 0
[123717.884903] Data abort info:
[123717.887858] ISV = 0, ISS = 0x00000007
[123717.891768] CM = 0, WnR = 0
[123717.894815] user pgtable: 64k pages, 48-bit VAs, pgdp=00000008bcec4c00
[123717.901415] [0000000000000034] pgd=0000000092400003, p4d=0000000092400003, pud=0000000092400003, pmd=0000000092410003, pte=00000
00000000000
[123717.914009] Internal error: Oops: 96000007 [#1] PREEMPT SMP
[123717.919653] CPU: 0 PID: 116 Comm: kworker/0:15 Tainted: G W O 5.10.0+ #51
[123717.927636] Hardware name: Texas Instruments K3 J721E SoC (DT)
[123717.933551] Workqueue: events stream_worker [vxd_dec]
[123717.938676] pstate: 00000005 (nzcv daif -PAN -UAO -TCO BTYPE=--)
[123717.944763] pc : vdeckm_get_core_state+0x1ac/0x1e0 [vxd_dec]
[123717.950502] lr : hwctrl_get_core_status+0x54/0x68 [vxd_dec]
[123717.956144] sp : ffff80001398f890
[123717.959533] x29: ffff80001398f890 x28: 0000000000000000
[123717.964917] x27: ffff000001776c68 x26: 000000000295001b
[123717.970301] x25: ffff00083ec8f8a4 x24: 0000000000000089
[123717.975685] x23: 0000000000000040 x22: ffff0000016cc400
[123717.981069] x21: ffff80001398fd28 x20: ffff000001776c00
[123717.986453] x19: ffff000001776c00 x18: 0000000000000010
[123717.991837] x17: ffffffdfffe07548 x16: ffff8000115d2340
[123717.997221] x15: ffffffffffffffff x14: 0720072007200720
[123718.002605] x13: ffff800010eb2e58 x12: ffff8000114e83e8
[123718.007989] x11: 0000000000000003 x10: ffff8000114d03a8
[123718.013373] x9 : ffff800008e90f94 x8 : ffff80001398fc5c
[123718.018757] x7 : 0000000000000000 x6 : 000000000000003f
[123718.024141] x5 : 0000000000000040 x4 : fffffffffffffff0
[123718.029525] x3 : 0000000000000000 x2 : 0000000000000000
[123718.034909] x1 : ffff80001398fb08 x0 : ffff800008ee5210
[123718.040293] Call trace:
[123718.042827] hwctrl_get_core_status+0x1ac/0x1e0 [vxd_dec]
[123718.048220] hwctrl_get_core_status+0x54/0x68 [vxd_dec]
[123718.053526] hwctrl_process_msg+0x214/0x688 [vxd_dec]
[123718.058659] decoder_service_firmware_response+0x78/0x1460 [vxd_dec]
[123718.065092] core_fw_response_cb+0x84/0xc8 [vxd_dec]
[123718.070139] stream_worker+0x6c/0xa8 [vxd_dec]
[123718.074655] process_one_work+0x1f4/0x4d0
[123718.078738] worker_thread+0x50/0x478
[123718.082473] kthread+0x164/0x168
[123718.085776] ret_from_fork+0x10/0x18
[123718.089427] Code: b5000181 a8d97bfd d50323bf d65f03c0 (b9403444)
[123718.095591] Modules linked in: ti_am65_cpsw_nuss(O) sdhci_am654(O) am65_cpts(O) phy_gmii_sel(O) davinci_mdio(O) vxe_enc(O) vxd_d
ec(O) videobuf2_dma_sg v4l2_mem2mem videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common v4l2_fwnode videodev mc
[123718.118429] ---[ end trace 98f3058c9c95ff53 ]---

0 Prashanth Kumar15 over 4 years ago in reply to xueming tian

Mastermind 8775 points

Hi,

Can you please let us know how did you run your usecase? The decoders are working fine here.

0 xueming tian over 4 years ago in reply to Prashanth Kumar15

Intellectual 631 points

Hi,

The decode test is re-executed using the unmodified OS. The OS panic occurs again. The necessary log and h264 file are uploaded by the attachment.
OS: SDK Linux for J721e 08_01_00
tidec_decode: download src from "">git.ti.com/.../" and the binary is attached.
video file: switch_1080p_720p_240frames.h264 which is uploaded by the attachment.
error log: "2022-02-15-tidec_decode-kernel-panic.log" which is obtained by "dmesg" command.

command line:
"./tidec_decode -i switch_1080p_720p_240frames.h264 -v /dev/video0 -b -o abc"

execution phenomenon:
The tidec_decode process executed normally in the beginning, and some log is printed:
"
TI DEC V4L2 Codec decoding example application
Copyright (c) 2018 Texas Instruments, Inc.

Using v4l2 for capture buffers
Input #0, h264, from 'switch_1080p_720p_240frames.h264':
Duration: N/A, bitrate: N/A
Stream #0:0: Video: h264 (High), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 24 fps, 24 tbr, 1200k tbn, 48 tbc
"

The tidec_decode process executed for some time. But then error messages are outputed from the serial port, such as:
"
[ 476.530283] [USERSID=0x00000005] [TID 0x005A0019] Some macroblocks were dropped when processing the current frame. May have corruption
...
[ 509.869028] decoder_service_firmware_response failed
"

While the tidec_decode process didn't exit automatically. We had to try to exit it by pressing ctrl+c, and more error messages are outputed from the serial port such as:
"[ 858.019802] img_dec 4300000.video-decoder: img_mmu_unmap: buffer id 2 not found
...
"[ 858.823195] Fixing recursive fault but reboot is needed!
"

The whole kernel log is attached as "2022-02-15-tidec_decode-kernel-panic.log" which is obtained by "dmesg" command.

Ti-08-01-SDK-tidec_decode-kernel_panic-20220215.zip

0 Prashanth Kumar15 over 4 years ago in reply to xueming tian

Mastermind 8775 points

Hi,

We did not see this issue on latest SDK. Can you share the bitstream switch_1080p_720p_240frames.h264?

0 xueming tian over 4 years ago in reply to Prashanth Kumar15

Intellectual 631 points

Hi，

The video file switch_1080p_720p_240frames.h264 is shared insided the zip file which was uplaoded in last reply. If the zip cannot be downloaded this video switch_1080p_720p_240frames.h264 can also be downloaded from https://chromium.googlesource.com/chromium/src/media/+/refs/heads/main/test/data/switch_1080p_720p_240frames.h264

Thanks and Regards

0 Prashanth Kumar15 over 4 years ago in reply to xueming tian

Mastermind 8775 points

Hi,

The stream seems to be faulty. ffmpeg is not able to decode it. It threw the below error:

[h264 @ 0x7f9e440022c0] missing picture in access unit with size 2580
[AVBSFContext @ 0x7f9e44002820] No start code is found.

Can you try any other valid stream?

0 xueming tian over 4 years ago in reply to Prashanth Kumar15

Intellectual 631 points

Hi,

At our PC environment, the stream switch_1080p_720p_240frames.h264 seems to be good. it can be decoded by ffmpeg which is shown as following screenshot.

I upload the video file again in this reply. Please download the zip and decompress it. This file's md5 is 7762f132efbd8aeb2d18f79453d829ad. Please try again, thanks very much.

switch_1080p_720p_240frames.zip

0 Prashanth Kumar15 over 4 years ago in reply to xueming tian

Mastermind 8775 points

Hi,

Thanks. This stream works fine with ffmpeg. I am able to reproduce the issue at my side. I will investigate this further and provide an update.

0 xueming tian over 4 years ago in reply to Prashanth Kumar15

Intellectual 631 points

Hi,

Has there been any progress on this issue?

0 Prashanth Kumar15 over 4 years ago in reply to xueming tian

Mastermind 8775 points

Hi,

Sorry for delayed response.

The codec driver doesn't support B-frame decoding. The bitstream shared has B-frames in it and there is data loss in B-frames too, which makes the stream as erroneous stream. It can be decoded by the software decoders.

If we provide a bitstream with B-frame the driver throws proper error messages and exits clean. The issue is seen only with stream which has B-frame and erroneous.

Will provide more updates when I have them ready.

Processors

Processors forum

TDA4VM: DECODER hardware