Forum Post: RE: DM8168 Decoding External Display

Thanks for your timely help.
 
With you help, I have modified the load address and entry point of Linux to 0xD0008000, and then ./run_make.sh ti816x-etv sys_all.
 
There is some errors in the running result:
 
dm816x login: root
root@dm816x:~# ./demo.sh
 
Beginning streaming...
*** Bootargs Validated for mem param ***
*** Bootargs Validated for notifyk.vpssm3 params ***
Kernel bootargs validated
numid=1,iface=MIXER,name='PCM Playback Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=127,step=0
  : values=127,127
  | dBscale-min=-63.50dB,step=0.50dB,mute=0
 [c6xdsp ] Remote Debug Shared Memory @ 0xbf000000
 [m3video] Remote Debug Shared Memory @ 0xbf005020
 [m3vpss ] Remote Debug Shared Memory @ 0xbf00a040
SysLink version : 2.10.02.17
SysLink module created on Date:Nov 29 2013 Time:16:04:07
Trace enabled
Trace SetFailureReason enabled
 Setting DMM priority for [DUCATI  ] to [0] ( 0x4e000624 = 0x08000000 )
 Setting DMM priority for [HDVICP0 ] to [2] ( 0x4e000634 = 0x0000000a )
 Setting DMM priority for [HDVICP1 ] to [2] ( 0x4e000634 = 0x000a0000 )
 Setting DMM priority for [HDVICP2 ] to [2] ( 0x4e000634 = 0x00a00000 )
Attached to slave procId 2.
Loaded file ../firmware/dvr_rdk_BUG: Your driver calls ioremap() on system memory.  This leads
to architecturally unpredictable behaviour on ARMv6+, and ioremap()
will fail in the next kernel release.  Please fix your driver.
fw_m3vpss.xem3 o------------[ cut here ]------------
n slave procId 2WARNING: at arch/arm/mm/ioremap.c:211 __arm_ioremap_pfn_caller+0x58/0x190()
.
Started slaveModules linked in: procId 2.
 syslink
Backtrace:
[<c0049bdc>] (dump_backtrace+0x0/0x110) from [<c03c597c>] (dump_stack+0x18/0x1c)
 r7:00000000 r6:c004d78c r5:c0493423 r4:000000d3
[<c03c5964>] (dump_stack+0x0/0x1c) from [<c006d1c8>] (warn_slowpath_common+0x54/0x6c)
[<c006d174>] (warn_slowpath_common+0x0/0x6c) from [<c006d204>] (warn_slowpath_null+0x24/0x2c)
 r9:00000002 r8:00000000 r7:bf036094 r6:00080000 r5:15080000
r4:00000002
[<c006d1e0>] (warn_slowpath_null+0x0/0x2c) from [<c004d78c>] (__arm_ioremap_pfn_caller+0x58/0x190)
[<c004d734>] (__arm_ioremap_pfn_caller+0x0/0x190) from [<c004d948>] (__arm_ioremap_caller+0x64/0x6c)
[<c004d8e4>] (__arm_ioremap_caller+0x0/0x6c) from [<c005fdbc>] (omap_ioremap+0x60/0x64)
 r6:00000002 r5:15080000 r4:80000000
[<c005fd5c>] (omap_ioremap+0x0/0x64) from [<bf036094>] (MemoryOS_map+0x1f0/0x3a8 [syslink])
 r7:ce795e28 r6:00000001 r5:ce795d48 r4:d0891000
[<bf035ea4>] (MemoryOS_map+0x0/0x3a8 [syslink]) from [<bf004594>] (_ProcMgr_map+0x1cc/0x4ac [syslink])
 r8:ce795e28 r7:ce795e28 r6:00000001 r5:d302e000 r4:d0abb000
[<bf0043c8>] (_ProcMgr_map+0x0/0x4ac [syslink]) from [<bf004990>] (ProcMgr_map+0x11c/0x1b4 [syslink])
[<bf004874>] (ProcMgr_map+0x0/0x1b4 [syslink]) from [<bf019954>] (Platform_loadCallback+0x4a0/0x7a0 [syslink])
[<bf0194b4>] (Platform_loadCallback+0x0/0x7a0 [syslink]) from [<bf04d42c>] (Ipc_control+0x68/0x14c [syslink])
[<bf04d3c4>] (Ipc_control+0x0/0x14c [syslink]) from [<bf086958>] (IpcDrv_drvioctl+0x68/0x298 [syslink])
 r7:00000004 r6:bf0facd0 r5:c014f497 r4:bedb7adc
[<bf0868f0>] (IpcDrv_drvioctl+0x0/0x298 [syslink]) from [<c00d27e8>] (vfs_ioctl+0x28/0x44)
 r6:00000004 r5:cdd45c00 r4:00000000
[<c00d27c0>] (vfs_ioctl+0x0/0x44) from [<c00d2ef8>] (do_vfs_ioctl+0x500/0x540)
[<c00d29f8>] (do_vfs_ioctl+0x0/0x540) from [<c00d2f90>] (sys_ioctl+0x58/0x7c)
[<c00d2f38>] (sys_ioctl+0x0/0x7c) from [<c0045e00>] (ret_fast_syscall+0x0/0x30)
 r8:c0045fa8 r7:00000036 r6:0007e2b4 r5:c014f497 r4:bedb7adc
---[ end trace 4f025b7048c3521b ]---
 [m3vpss ] ***** SYSTEM  : Frequency <ORG> - 250000000, <NEW> - 280000000
 [m3vpss ] notify_attach  rtnVal  0
 [m3vpss ] initProxyServer  rtnVal  0
 
It indicates that  syslink is not compatible with the memroy map? what causes the bug?