TMS320DM8168: Upgrading H.264 Decoder

Lawrence Wong

Part Number: TMS320DM8168

Customer using EZSDK with IVAHD_H264vdec_02_00_07_00 decoder. They are trying to update to H.264 GA2.0 Decoder object executable for linux V02.00.22.01-02.00.22.01 but was unclear how to properly integrated it into the EZSDK. Included documentation did not provide any details on how to integrate into the EZSDK environment

over 6 years ago

0 Pavel Botev over 6 years ago

TI__Guru**** 170625 points

Hi Lawrence,

I am only able to find below e2e threads for reference:

e2e.ti.com/.../474977
e2e.ti.com/.../346183

For any detailed software support, bug fixes, or enhancements to TI software, please contact any of the select partners recommended below.

e2e.ti.com/.../622094

Regards,
Pavel

0 Lawrence Wong over 6 years ago in reply to Pavel Botev

TI__Genius 15790 points

Customer have tried to compile provided h264 library with our EZSDK environment but get errors at linking when building overlay packages (please see attached file for more details). They have replaced current h264vdec_ti.lib with never version and change header files as well but is seems like this library is not compatible with some other overlay modules (media-controller-devkit):

-l/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/media-controller-devkit/cgt470_4_9_2/lib/rtsv7M3_T_le_eabi.lib

fatal error: file

"/home/bob/in40IPdevelopment-ver1_0_93/Baltimore_Firmware/Baltimore/IN40IPDe

velopment/branch_dev/TI/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/iva

hd_h264vdec_02_00_07_00_production/packages/ti/sdo/codecs/h264vdec/lib/h264v

dec_ti.lib<h264vdec_ti_ires.obj>" has a Tag_ABI_PCS_wchar_t attribute value

of "4" that is different than one previously seen ("2"); combining

incompatible files

make[2]: *** [/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/bin/ti816x-evm/dm816xbm_m3video_whole_program_debug.xem3] Error 1

make[2]: Leaving directory `/home/bob/in40IPdevelopment-ver1_0_93/Baltimore_Firmware/Baltimore/IN40IPDevelopment/branch_dev/TI/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/examples/ti/omx/demos/dm816xbm'

make[1]: *** [dm816xbmvm3] Error 2

make[1]: Leaving directory `/home/bob/in40IPdevelopment-ver1_0_93/Baltimore_Firmware/Baltimore/IN40IPDevelopment/branch_dev/TI/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/src'

make: *** [omx] Error 2

Is the H264 library REL.500.V.H264AVC.D.HP.IVAHD.02.00.22.01.bin is for DVRRDK environment and not for EZSDK overlay environment as libraries in EZSDK overlay package are named as: ivahd_h264vdec_<version>_production.

How to integrate the new H264 library version 02.00.22.01 as an overlay production packet (ivahd_h264vdec_02.00.22.01 production) into EZSDK environment?

Any suggestion how to resolve incompatibilities with our EZSDK modules as in linking error above.

Fullscreen H264-linker-error.txt Download

# Linking into /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/bin/ti816x-evm/dm816xbm_m3video_whole_program_debug.xem3
#
cd /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug && /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/media-controller-devkit/cgt470_4_9_2/bin/lnk470 -w -q -u _c_int00 --silicon_version=7M3 -c --dynamic  --opt='--endian=little -mv7M3 --abi=eabi -qq -pdsw225 -g -ms --gcc -D___DSPBIOS___ -D___DUCATI_FW___ -DSYSLINK_USE_TILER -DMULTICHANNEL_OPT=1  -oe --symdebug:dwarf -ms -op2 -O3 -k -os --optimize_with_debug --inline_recursion_limit=20 --diag_suppress=23000' --strict_compatibility=on  -x --zero_init=off --retain=_Ipc_ResetVector      /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/ducati_mmsw_main_vidm3.oem3  /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/mmsw_platform_vidm3.oem3  /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/load_update.oem3  /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/configureUiaLogger.oem3  /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/sys_top_slave.oem3  /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/omxbase_cfg.oem3  /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/domx_cfg.oem3  /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/domxProxyWrappers.oem3  /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/domx_delegates_shmem_cfg.oem3  /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/omxcore_cfg.oem3  /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/memtbl_cfg.oem3  /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/VpsAppMain_pem3.oem3 /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/obj/ti816x-evm/m3video/whole_program_debug/dm816xbm_configuro/linker_mod.cmd -o /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/bin/ti816x-evm/dm816xbm_m3video_whole_program_debug.xem3 -m /home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/bin/ti816x-evm/dm816xbm_m3video_whole_program_debug.xem3.map -l/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/ti/omx/comp/omxbase/lib/m3video/whole_program_debug/omxbase.aem3 -l/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/ti/omx/comp/venc/lib/ti816x-evm/m3/whole_program_debug/venc.aem3 -l/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/ti/omx/comp/vdec/lib/ti816x-evm/m3/whole_program_debug/vdec.aem3 -l/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/ti/omx/comp/server/lib/ti816x-evm/m3/whole_program_debug/server.aem3 -l/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/ti/omx/comp/scheduler/lib/ti816x-evm/m3/whole_program_debug/scheduler.aem3 -l/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/ti/omx/domx/lib/m3video/whole_program_debug/domx.aem3 -l/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/ti/omx/domx/delegates/shmem/lib/m3video/whole_program_debug/domx_delegates_shmem.aem3 -l/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/ti/omx/omxcore/lib/m3video/whole_program_debug/omxcore.aem3 -l/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/ti/omx/memcfg/lib/m3video/whole_program_debug/memcfg.aem3 -l/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/utilities/firmware_loader/ldrmemcfg/lib/m3/whole_program_debug/ldrmemcfg.aem3 -l/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/media-controller-devkit/cgt470_4_9_2/lib/rtsv7M3_T_le_eabi.lib
fatal error: file
   "/home/bob/in40IPdevelopment-ver1_0_93/Baltimore_Firmware/Baltimore/IN40IPDe
   velopment/branch_dev/TI/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/iva
   hd_h264vdec_02_00_07_00_production/packages/ti/sdo/codecs/h264vdec/lib/h264v
   dec_ti.lib<h264vdec_ti_ires.obj>" has a Tag_ABI_PCS_wchar_t attribute value
   of "4" that is different than one previously seen ("2"); combining
   incompatible files
make[2]: *** [/home/bob/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/bin/dm816xbm/bin/ti816x-evm/dm816xbm_m3video_whole_program_debug.xem3] Error 1
make[2]: Leaving directory `/home/bob/in40IPdevelopment-ver1_0_93/Baltimore_Firmware/Baltimore/IN40IPDevelopment/branch_dev/TI/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/examples/ti/omx/demos/dm816xbm'
make[1]: *** [dm816xbmvm3] Error 2
make[1]: Leaving directory `/home/bob/in40IPdevelopment-ver1_0_93/Baltimore_Firmware/Baltimore/IN40IPDevelopment/branch_dev/TI/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx-ti81xx-src_05_02_00_48/src'
make: *** [omx] Error 2

0 Margarita Gashova over 6 years ago in reply to Lawrence Wong

TI__Guru* 80190 points

Hello Lawrence,

I will give you an example with older version of decoder.
As you see we have 2 versions .00 and .01
ivahd_h264vdec_02_00_17_00_production
ivahd_h264vdec_02_00_17_01_production
The difference is that the .00 version has wchar_t parameter set to 2(Tag_ABI_PCS_wchar_t: 2) and the .01 version has the parameter set to 4.
This is the fatal error that you are seeing.
The reason that we have two h264dec versions is that the 00 require lower cgt470 tool version and it is for SDKs(EZSDK). The .01 require higher cgt tool version and it is for RDKs(DVRRDK etc.). I guess if you update the codec generation tools you will be able to compile .01(search in the datasheet for the version). You could check is there ivahd_h264vdec_02.00.22.00.
On other hand, please check the datasheet of the codec. There, you could find the HDVICP2 API version that h264 decoder requires. Compare this with the version in EZSDK.
May be some changes will be require in the overlay package for h264 decoder(search for changes in params).

Please refer this:
e2e.ti.com/.../622094

Hope this helps.

Best Regards,
Margarita

0 Margarita Gashova over 6 years ago in reply to Margarita Gashova

TI__Guru* 80190 points

Hello,

Please if this answers your question click the "This resolved my issue" button.
Thank you!

Best Regards,
Margarita

0 Lawrence Wong over 6 years ago in reply to Margarita Gashova

TI__Genius 15790 points

Margarita,

Where can I get different releases of the HDVICP2 API? Customer tried using REL.500.V.H264AVC.D.HP.IVAHD.02.00.14.00.bin but got the same error:

has a Tag_ABI_PCS_wchar_t attribute value of "4" that is different than one previously seen ("2"); combining incompatible files

Regards,

Lawrence

0 Margarita Gashova over 6 years ago in reply to Lawrence Wong

TI__Guru* 80190 points

Hello,

They need to check the codec datasheet for what it requires(like codec generation tools etc).
If I remember right the latest tested version of h264dec in EZSDK was ivahd_h264vdec_02_00_15_00_production.
"Where can I get different releases of the HDVICP2 API?"
Unfortunately, I am not the right person to answer this.

Best Regards,
Margarita

Processors

Processors forum

TMS320DM8168: Upgrading H.264 Decoder