OMTB / "decode" demo / "decode_display" demo on 8168 Netra EVM without Daughtercard

Hi Stegre

I believe decode_display example does not need a daughter to work.I have let it worked, and I have the Dcard, but it really do nothing in this example.

It will decode the video file in your file system and display on the LCD via HDMI connector.

Jun

Thanks Jun, in that case I'm going to try to get that compiled & running.

Well, anything I try just hangs. I've made the suggested mods to enable the "decoder input port" and I've set DOMX_CORE_DOPROCINIT  to zero so the firmware doesn't get loaded twice. I've modified rc5.d so neither "matrix-gui-e" nor "pvr-init" runs on startup.  The insmod's of syslink.ko and TI81xx_HDMI.ko are being run on startup. Nonetheless, the decode_display demo hangs as follows:

root@dm816x-evm:~/decode_display# ./decode_display_a8host_debug_extra_init.xv5T 1920 1080 60 /usr/share/ti/data/videos/dm816x_1080p_demo.264

Entered Frame Width: 1920
Entered Frame Height: 1080
Entered Frame Rate: 60
Entered File name: /usr/share/ti/data/videos/dm816x_1080p_demo.264
 Decoder-Display example 

===============================

Starting threads

Threads started. Starting platform init
Wait for VM3 to to create the server first
Platform initialized
 openeing file 
 OMX_Init completed 
  decoder compoenent is created 
enable decoder input port 
got eventEnable/Disable Event 
enable scalar output port 
got eventEnable/Disable Event 
 scalar compoenent is created 

< -- O/S hangs here; requires reboot -- >

I also can't run any of the OMTB scripts, even "fread_dec_fwrite" which shouldn't require any video inputs or outputs at all. The scripts all seem to hang on "gethandle" of the H.264 decoder. Below is a typical log with the debug flags set:

root@dm816x-evm:~# ./omtb_dm816xbm_a8host.xv5T fread_vdec_fwrite.oms 

Wait for VM3 to to create the server first
OMTB> Processing : omx -s fread_vdec_fwrite.oms
OMTB> #omx omtb_dbg_lvl 0x10
OMTB> omx omtb_dbg_lvl 0xff
OK
OMTB> omx api init
OMTB-OMX_ErrorNone
OK

< -- a bunch of other "OK"'s in here -- > 

OMTB> omx api gethandle h264vdec 0 0
OMTB-Entering <Function , instance #> : <H264VDEC_GetHandle , 0>
OMTB-Component Name is:OMX.TI.DUCATI.VIDDEC
OMTB-Input File is:/usr/share/ti/data/videos/dm816x_1080p_demo.264
OMTB-Output File is:/usr/share/ti/data/videos/dm816x_1080p_420sp.yuv
OMTB-Frame Size File is:frame_data.txt
OMTB-Entering <Function , instance #> : <H264VDEC_AllocateMemory , 0>
OMTB-Leaving <Function , instance #> : <H264VDEC_AllocateMemory , 0>

< -- O/S hangs here; requires reboot -- >

Am I doing something wrong, or is there truly no support for the EVM without a daugtercard? Could someone from TI please advise?

I have just run the decode_display example from the EVM main board without the daughtercard attached. I was having similar issues to what you list above (with the daughtercard attached) but when i removed the pvr script from boot-time init it solved my problem (which you reference above that you are already doing.)

I am using the standard boot scripts from SDK5_01_01_80 (nfs boot from /home/<user>/targetfs as set up by EzSDK install), except that I removed the matrix-gui and pvr-init links from /etc/rc5.d/.  I do nothing to reconfigure after the boot scripts run (i.e. I do not re-run prcm_config_app or insmod syslink.ko or TI81xx_hdmi.ko). I also had to make the change to set DOMX_CORE_DOPROCINIT to zero. I know you said you've already done thse things, just wanted to summarize. There are no other changes that I have made. I execute with:

# ./decode_display_a8host_debug.xv5T -w 1920 -h 1080 -f 60 -i /usr/share/ti/data/videos/dm816x_1080p_demo.264

I am also able to run the decode_scale_display.oms example with this setup:

# ./omtb_dm816xbm_a8host.xv5T decode_scale_display.oms

BTW, locking up as you describe is not necessarily an indication of something going wrong. At lease with my version of SDK, the OMX teardown is not yet implemented, so every time I run one of these demos, I can't stop it, even if it is running correctly. Each time I have to power-cycle the board and reboot. I have seen other postings that describe the same experience.

Unfortunately, I am not the person to help you diagnose your problem - I am just getting up and running myself. But I wanted to let you know that it can be done to run these examples without the daughtercard.

Regards,

Steve

Thank you very much for your response. The EVM board is off my desk at the moment, but as soon as I get it back I'm going to re-try the experiments carefully as you describe, taking into account everything you've pointed out, since your post is giving me the confidence that this *should* work. I prob just missed something somewhere. Thanks again.