Openmax/syslink error in RDK 00.07.00.01 of 816x DVR reference.

Maybe you are using the wrong version of syslink. As I can only see syslinkipc_ device files in /dev. (Version 2.00.02.80 or .00.78) on DM8148.
If you are using the current Beta EZSDK for Netra you'll have to use a syslink version like .00.68 or so, I think. Since the newer versions are not compatible anymore.

Regards

Markus

Thanks Markus.

I used rdk version00.07.00.01 and the syslink_02_00_00_67. All those are provided by ti.

You mean my version of  syslink is older? The problem cause by syslink.ko?

I try the default syslink.ko  and  app_m3video.xem3, app_m3vpss.xem3 in RDK( udworks), it is still error. The tstEncoder can work in ti offical image.  But it can no work in the rootfs that i built. So there maybe something wrong in syslink.ko or app_m3video.xem3, app_m3vpss.xem3.

Maybe I think:

(1)  The *.ko or *.xm3 are wrong. That  maybe the versions are not   compatible anymore;

(2)  I do not use udev.  I insmod syslink.ko and ti81xx_hdmi.ko directly. Did it need other kernel modules?

Besides the version, is my process is ok?

Yes, Markus you are right. The function call like this:

LIB816x_StartSystem()

  \___ DVR_Init()

          \___ DVR_start_front_if() ==> It depend on /dev/input/uinput.

The kernel has built in the uinput driver. Becase I use mdev, the /dev/input/uinput was not created auto.

I tar the normal nodes in /dev of offical image, and tar xf it under /dev in my rootfs.  But this only fix "err: Error create uinput device -1.". The syslink error is still.

Maybe it seems 2 things.

(1) The kernel driver of syslink is error, Maybe the version problem;

(2) The major and minor I created using the load_moules are wrong.

Anything else you think? Thanks.

Regards

Yaming

Log like this:

/opt- # ./load_module.sh
SysLink version : 02.00.00.67_alpha2
SysLink module created on Date:May  9 2011 Time:07:39:43
Entered KnlUtilsDrv_initializeModule
Trace enabled
Trace SetFailureReason enabled
Trace class 3
traceMask value: 0x30101
DM8168DUCATIPWR Module already initialized!
Leaving KnlUtilsDrv_initializeModule 0x0
[module] ti81xx_hdmi init done
load module completed

/opt- # lsmod
TI81xx_hdmi 11306 0 - Live 0xbf181000
syslink 1074625 0 - Live 0xbf049000
ipv6 209879 10 - Live 0xbf000000

/opt- # ./start_app.sh
start application
tstEncoder 18:12:04
input: dvr-keypad as /devices/virtual/input/input0
front_interface start
OsalDrv driver open: /dev/syslinkipc/Osal: No such device or address
OsalDrv driver close: /dev/syslinkipc/Osal: Bad file descriptor
/dev/syslinkipc/MultiProc: No such device or address
MultiProc driver close: : Bad file descriptor
SharedRegion driver open: : No such device or address
SharedRegion driver close: : Bad file descriptor
/dev/syslinkipc/GateMP: No such device or address
/dev/syslinkipc/MessageQ: No such device or address
MessageQ driver close: : Bad file descriptor
Notify driver open: /dev/syslinkipc/Notify: No such device or address
Notify driver close: /dev/syslinkipc/Notify: Bad file descriptor
/dev/syslinkipc/HeapBufMP: No such device or address
/dev/syslinkipc/HeapMemMP: No such device or address
/dev/syslinkipc/ListMP: No such device or address
/dev/syslinkipc/RingIO: No such device or address
RingIO driver close: : Bad file descriptor
/dev/syslinkipc/ClientNotifyMgr: No such device or address
ClientNotifyMgr driver close: : Bad file descriptor
/dev/syslinkipc/FrameQBufMgr: No such device or address
FrameQBufMgr driver close: : Bad file descriptor
/dev/syslinkipc/FrameQ: No such device or address
FrameQ driver close: : Bad file descriptor
/dev/syslinkipc/Ipc: No such device or address
Assertion at Line no: 231 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/procMgr/hlos/usr/Linux/ProcMgrDrvUsr.c: (ProcMgrDrvUsr_refCount > 0) : failed
[t=0x00000002] [tid=0x400692d0] xdc.runtime.Main: ERROR: "IpcSupport.c", line 222: ipc_initialize(), error in ProcMgr_open()
xdc.runtime.Main: "IpcSupport.c", line 222: ipc_initialize(), error in ProcMgr_open()
[t=0x00000103] [tid=0x400692d0] xdc.runtime.Main: ERROR: "IpcSupport.c", line 313: ipc_initialize() failed
xdc.runtime.Main: "IpcSupport.c", line 313: ipc_initialize() failed
Assertion at Line no: 1080 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/ipc/hlos/usr/SharedRegion.c: (id < SharedRegion_module->cfg.numEntries) : failed
Assertion at Line no: 1064 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/ipc/hlos/usr/MessageQ.c: (heap != NULL) : failed
Assertion at Line no: 231 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/procMgr/hlos/usr/Linux/ProcMgrDrvUsr.c: (ProcMgrDrvUsr_refCount > 0) : failed
[t=0x000001ee] [tid=0x400692d0] xdc.runtime.Main: ERROR: "IpcSupport.c", line 222: ipc_initialize(), error in ProcMgr_open()
xdc.runtime.Main: "IpcSupport.c", line 222: ipc_initialize(), error in ProcMgr_open()
[t=0x00000251] [tid=0x400692d0] xdc.runtime.Main: ERROR: "IpcSupport.c", line 313: ipc_initialize() failed
xdc.runtime.Main: "IpcSupport.c", line 313: ipc_initialize() failed
Assertion at Line no: 1080 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/ipc/hlos/usr/SharedRegion.c: (id < SharedRegion_module->cfg.numEntries) : failed
Assertion at Line no: 1064 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/ipc/hlos/usr/MessageQ.c: (heap != NULL) : failed
app: dvr_init() ... done
enc: bitrate ... 1200000

app: dvr_startsystem ... start
OsalDrv driver open: /dev/syslinkipc/Osal: No such device or address
OsalDrv driver close: /dev/syslinkipc/Osal: Bad file descriptor
/dev/syslinkipc/MultiProc: No such device or address
MultiProc driver close: : Bad file descriptor
SharedRegion driver open: : No such device or address
SharedRegion driver close: : Bad file descriptor
Assertion at Line no: 217 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/ipc/hlos/usr/Linux/GateMPDrv.c: (GateMPDrv_refCount > 0) : failed
/dev/syslinkipc/MessageQ: No such device or address
MessageQ driver close: : Bad file descriptor
Notify driver open: /dev/syslinkipc/Notify: No such device or address
Notify driver close: /dev/syslinkipc/Notify: Bad file descriptor
Assertion at Line no: 222 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/ipc/hlos/usr/Linux/HeapBufMPDrv.c: (HeapBufMPDrv_refCount > 0) : failed
Assertion at Line no: 221 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/ipc/hlos/usr/Linux/HeapMemMPDrv.c: (HeapMemMPDrv_refCount > 0) : failed
Assertion at Line no: 225 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/ipc/hlos/usr/Linux/ListMPDrv.c: (ListMPDrv_refCount > 0) : failed
/dev/syslinkipc/RingIO: No such device or address
RingIO driver close: : Bad file descriptor
/dev/syslinkipc/ClientNotifyMgr: No such device or address
ClientNotifyMgr driver close: : Bad file descriptor
/dev/syslinkipc/FrameQBufMgr: No such device or address
FrameQBufMgr driver close: : Bad file descriptor
/dev/syslinkipc/FrameQ: No such device or address
FrameQ driver close: : Bad file descriptor
Notify driver open: /dev/syslinkipc/Notify: No such device or address
Assertion at Line no: 231 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/procMgr/hlos/usr/Linux/ProcMgrDrvUsr.c: (ProcMgrDrvUsr_refCount > 0) : failed
[t=0x0001a03d] [tid=0x400692d0] xdc.runtime.Main: ERROR: "IpcSupport.c", line 222: ipc_initialize(), error in ProcMgr_open()
xdc.runtime.Main: "IpcSupport.c", line 222: ipc_initialize(), error in ProcMgr_open()
[t=0x0001a113] [tid=0x400692d0] xdc.runtime.Main: ERROR: "IpcSupport.c", line 313: ipc_initialize() failed
xdc.runtime.Main: "IpcSupport.c", line 313: ipc_initialize() failed
Assertion at Line no: 1080 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/ipc/hlos/usr/SharedRegion.c: (id < SharedRegion_module->cfg.numEntries) : failed
Assertion at Line no: 1064 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/ipc/hlos/usr/MessageQ.c: (heap != NULL) : failed
Assertion at Line no: 231 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/procMgr/hlos/usr/Linux/ProcMgrDrvUsr.c: (ProcMgrDrvUsr_refCount > 0) : failed
[t=0x0001a1bf] [tid=0x400692d0] xdc.runtime.Main: ERROR: "IpcSupport.c", line 222: ipc_initialize(), error in ProcMgr_open()
xdc.runtime.Main: "IpcSupport.c", line 222: ipc_initialize(), error in ProcMgr_open()
[t=0x0001a223] [tid=0x400692d0] xdc.runtime.Main: ERROR: "IpcSupport.c", line 313: ipc_initialize() failed
xdc.runtime.Main: "IpcSupport.c", line 313: ipc_initialize() failed
Assertion at Line no: 1080 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/ipc/hlos/usr/SharedRegion.c: (id < SharedRegion_module->cfg.numEntries) : failed
Assertion at Line no: 1064 in /home/idaroa/proj/src/20110527/00.07.00.01/dvr/../ti_tools/syslink_02_00_00_67/ti/syslink/ipc/hlos/usr/MessageQ.c: (heap != NULL) : failed
err: Line number: 201
app: lib816x_statsystem ... done

<  h> : help.
<  q> : quit.
<  1> : encoder            test.

input cmd:
 

Hi Yaming,

Looks like the syslink module insertion has not succeeded for you. We can check it by looking at the log. Can you share the log of insmod syslink.ko also? You have not shared in last post.

BTW, to confirm if it is syslink.ko problem, can you use the syslink.ko and the uImage from the TI DVR RDK release and only replace your .xem3 binaries and test.

Also, can you confirm if you are using the right paths for the syslink that you have used in the Rules.make to build the .xem3 binaries.

Regards,

Anshuman

PS: Please mark this post as verified, if you think it has answered your question. Thanks.

Hi guys,

I'm sure the driver of syslink for linux kernel is ok now. Now  I traced that tstEncoder came to DVR_StartSystem().

I use mdev for manage the node under /dev, the device node for uinput and  syslinkipc could not be created very for DVR lib.

I was cheated by "/opt/load_modules.sh", it create the wrong major. I check every major, minor and path of every node and recreated them manually. Now we can see "Starting Streaming Server...DONE".

But tstEncoder hung at this stage. I'm sure tstEncoder hung in DVR_StartSystem(). And  I put the tstEncoder in offical DVR image it act likely. So the .xem3 maybe are right.

This moment, I just depend on trace the DVR_StartSystem(). Any ideas? The run log like this:

[root@/opt-]# ./start_app.sh
start application
[root@/opt-]# tstEncoder 03:50:39
front_interface start
Wait for VM3 to to create the server first
app: dvr_init() ... done
enc: bitrate ... 1200000

app: dvr_startsystem ... start
Entering: OMX_TI_CMUX_ComponentInit
Entering: OMX_TI_DMUX_ComponentInit
 AVSERVER UI: Starting Streaming Server...
Entering: _OMX_TI_DMUX_DataProcPrdTaskFcn
Entering: _OMX_CMUXDataProcPrdTaskFcn
NetraDrvInit: 6
queue id:0
Initializing...
...done initializing
NetraDrvInit: 2
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.125:8557/h264_ch7
NetraDrvInit: 2
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.125:8556/h264_ch6
NetraDrvInit: 10
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.125:8555/h264_ch5
NetraDrvInit: 9
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.125:8554/h264_ch4
NetraDrvInit: 8
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.125:8553/h264_ch3
NetraDrvInit: 6
NetraDrvInit: 2
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.125:8551/h264_ch1
Play this stream using the URL:
        rtsp://10.51.252.125:8558/h264_ch8
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.125:8552/h264_ch2
 AVSERVER UI: Starting Streaming Server...DONE

I use the "insmod ./$moudle_dir/syslink.ko TRACE=1 TRACEFAILURE=1" for debug. And the log as following. Is the tstEncoder depend on record enable?

input: dvr-keypad as /devices/virtual/input/input0
*** DM8168VIDEOM3PROC_translate: srcAddr not found in slave address space
        Error [0x86a85001] at Line no: 1471 in file /home/phoong/work/netra/dvr/sdk_5011/syslink_02_00_00_67/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/ti81xx/ti81xxducati/ti81xxvideom3/Dm8168M3VideoProc.c
*** Processor_translateAddr: Processor address translation failed!
        Error [0x86a85001] at Line no: 600 in file /home/phoong/work/netra/dvr/sdk_5011/syslink_02_00_00_67/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/hlos/knl/Processor.c
*** ElfLoaderTrgWrite_copy: Processor_translateAddr failed!
        Error [0x86a85001] at Line no: 521 in file /home/phoong/work/netra/dvr/sdk_5011/syslink_02_00_00_67/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/hlos/knl/loaders/Elf/ElfLoader.c
*** DM8168VPSSM3PROC_translate: srcAddr not found in slave address space
        Error [0x86a85001] at Line no: 1475 in file /home/phoong/work/netra/dvr/sdk_5011/syslink_02_00_00_67/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/ti81xx/ti81xxducati/ti81xxvpssm3/Dm8168M3DssProc.c
*** Processor_translateAddr: Processor address translation failed!
        Error [0x86a85001] at Line no: 600 in file /home/phoong/work/netra/dvr/sdk_5011/syslink_02_00_00_67/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/hlos/knl/Processor.c
*** ElfLoaderTrgWrite_copy: Processor_translateAddr failed!
        Error [0x86a85001] at Line no: 521 in file /home/phoong/work/netra/dvr/sdk_5011/syslink_02_00_00_67/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/hlos/knl/loaders/Elf/ElfLoader.c
*** DM8168VPSSM3PROC_translate: srcAddr not found in slave address space
        Error [0x86a85001] at Line no: 1475 in file /home/phoong/work/netra/dvr/sdk_5011/syslink_02_00_00_67/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/ti81xx/ti81xxducati/ti81xxvpssm3/Dm8168M3DssProc.c
*** Processor_translateAddr: Processor address translation failed!
        Error [0x86a85001] at Line no: 600 in file /home/phoong/work/netra/dvr/sdk_5011/syslink_02_00_00_67/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/hlos/knl/Processor.c
*** ElfLoaderTrgWrite_copy: Processor_translateAddr failed!
        Error [0x86a85001] at Line no: 521 in file /home/phoong/work/netra/dvr/sdk_5011/syslink_02_00_00_67/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/hlos/knl/loaders/Elf/ElfLoader.c

I just put tstEncoder on the TI DVR RDK release and  it hung at " AVSERVER UI: Starting Streaming Server...DONE", the seem as in my rootfs.

The rtsp server can run now, but tstEncoder is hunged.

 According the trace tstEncoder was hung in 00.07.00.01/dvr/app/src/omx_il_tunnel.c function: omx_ilclient_connect_VFPCSC_VFDC() @ line 974;

eError = OMX_SendCommand ( pContext->hVFDC[H_VFDC_PB_OFFSET], OMX_CommandPortEnable, nVFDCPortIndex, NULL );

 The function call maybe like this:

 LIB816x_StartSystem()

        `|

          DVR_StartSystem()

             \___ omx_ilclient_connect_VFPCSC_VFDC()

                        \___ OMX_SendCommand () ==>hunged here.

Maybe the normal following  prcoss will proble kernel module ti8x6x_fb.ko and vpss.ko. But it is hunged here. Any idiea?

Hi,

Did you check the standard DVR RDK application? Was that also giving the same problem? If yes, then we can debug from that direction.

Regards,

Anshuman

Hi,

I check the standard DVR RDK application using nfs ../target/rfs. When I run tstEncoder under it, tstEncoder is still hunged at "AVSERVER UI: Starting Streaming Server...DONE". But "dvrmain"  can come to "app: lib816x_statsystem ... done".

We just want to check RTSP and Encoder in DVR reference. Is my test method using tstEncoder is wrong? Can you give some advice for this? Log and /opt/netra/start.sh as following.

Log:

root@dvr:~# cat /opt/netra/start.sh
#! /bin/sh

export LD_LIBRARY_PATH=/usr/lib
export QT_QWS_FONTDIR=/usr/lib/fonts

if [ ! -e ./app_m3video.xem3 ]; then
        echo "not found app_m3video.xem3"
        exit 0
fi

if [ ! -e ./app_m3vpss.xem3 ]; then
        echo "not found app_m3vpss.xem3"
        exit 0
fi

./tstEncoder&
if [ -x ./dvrmain ]; then
#       ./dvrmain -qws hdmi ntsc &
#       ./dvrmain -qws hdmi pal &
#       ./dvrmain -qws vga ntsc &
#       ./dvrmain -qws vga pal &
else
        echo "not found dvrmain"
fi

INIT: version 2.86 booting
Error opening /dev/fb0: No such file or directory
Please wait: booting...
Starting udev
udevd (76): /proc/76/oom_adj is deprecated, please use /proc/76/oom_score_adj instead.
udev: starting version 141
udev: renamed network interface eth1 to eth3
udevd-event[122]: error changing netif name eth0 to eth2: Device or resource busy

Root filesystem already rw, not remounting
Caching udev devnodes
Populating dev cachemv: cannot rename '/tmp/devices': No such file or directory
ALSA: Restoring mixer settings...
NOT configuring network interfaces: / is an NFS mount
No state is present for card DVR
Found hardware: "" "" "" "" ""
Hardware is initialized using a generic method
No state is present for card DVR
INIT: Entering runlevel: 5
Starting system message bus: dbus.
Starting telnet daemon.
Starting syslogd/klogd: NET: Registered protocol family 10
done
Starting thttpd.
SysLink version : 02.00.00.67_alpha2
SysLink module created on Date:May  9 2011 Time:07:39:43
Entered KnlUtilsDrv_initializeModule
traceMask value: 0x0
Leaving KnlUtilsDrv_initializeModule 0x0
[module] ti81xx_hdmi init done
load module completed
start application
./start.sh: line 22: syntax error: "else" unexpected
tstEncoder 00:23:54
input: dvr-keypad as /devices/virtual/input/input0
front_interface start

Wait for VM3 to to create the server first
app: dvr_init() ... done
enc: bitrate ... 1200000

app: dvr_startsystem ... start
 _   _ ___  _   _         _
| | | |    | ||| |___ ___| | _ ___
| |_| | |) |  ~  | . |  _| |/_|  -|
|_____|___ /____/ ___|_| |_| _|-__|

DVR_Netra Board (2011.04)

dvr login: Entering: OMX_TI_CMUX_ComponentInit
Entering: OMX_TI_DMUX_ComponentInit
 AVSERVER UI: Starting Streaming Server...
Entering: _OMX_TI_DMUX_DataProcPrdTaskFcn
Entering: _OMX_CMUXDataProcPrdTaskFcn
NetraDrvInit: 2
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.76:8556/h264_ch6
NetraDrvInit: 10
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.76:8555/h264_ch5
NetraDrvInit: 9
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.76:8554/h264_ch4
NetraDrvInit: 8
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.76:8553/h264_ch3
NetraDrvInit: 6
queue id:0
Initializing...
...done initializing
NetraDrvInit: 2
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.76:8551/h264_ch1
NetraDrvInit: 2
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.76:8557/h264_ch7
NetraDrvInit: 6
queue id:0
Initializing...
...done initializing
Play this stream using the URL:
        rtsp://10.51.252.76:8558/h264_ch8
Play this stream using the URL:
        rtsp://10.51.252.76:8552/h264_ch2
 AVSERVER UI: Starting Streaming Server...DONE

 _   _ ___  _   _         _
| | | |    | ||| |___ ___| | _ ___
| |_| | |) |  ~  | . |  _| |/_|  -|
|_____|___ /____/ ___|_| |_| _|-__|

DVR_Netra Board (2011.04)

dvr login: root
root@dvr:~# cat /opt/netra/
/opt/netra/app_m3video.xem3  /opt/netra/skin/
/opt/netra/app_m3vpss.xem3   /opt/netra/start.sh
/opt/netra/dvrmain           /opt/netra/tstEncoder
/opt/netra/prep-sdd.sh       /opt/netra/wis-streamer
root@dvr:~#

The root cause of tstEncoder hunged at "AVSERVER UI: Starting Streaming Server...DONE" maybe the code of tstEncoder.c line 292 of 00.07.00.01.

   288  int main(void)
   289  {
   290          printf("tstEncoder %s\n",__TIME__);
   291
   292          LIB816x_startSystem(0, 2);   --> The wrong val.
   293          testThread();
   294
   295          return 0;
   296  }

According the video source(PAL) we use,  modify LIB816x_startSystem(2, 0). tstEncoder runs ok now.

Hi,

Good catch. Yes, the PAL input mode is supported as input selection only on the dvrmain application. For the test applications, it was assumed to have NTSC input.

But did you mention that your dvrmain application was also not working. That is strange, if you selected PAL input in start.sh script.

Regards,

Anshuman

PS: Please mark this post as verified, if you think it has answered your question. Thanks.