I've built syslink including the kernel module, then built my kernel and its modules against syslink. I boot up my board and manually run the steps of the TI init script "S50load-firmware.sh". This is what happens:
# PATH=$PATH:/usr/share/ti/ti-hdvpss-display-utils
# modprobe syslink
SysLink module created on Date:Mar 29 2011 Time:14:15:57
Entered KnlUtilsDrv_initializeModule
traceMask value: 0x0
Leaving KnlUtilsDrv_initializeModule 0x0
# procmgrapp.exe 2 /usr/share/ti/ti-hdvpss-display-utils/ti816x_hdvpss.xem3 &
# ProcMgrApp sample application
Entered ProcMgrApp_startup
ProcMgr_attach status: [0x0]
After attach: ProcMgr_getState
state [0x1]
ProcMgr_load status: [0x3046000]
After load: ProcMgr_getState
state [0x3]
ProcMgr_start passed [0x6a85000]
# modprobe vpss mode=hdmi:1080p-60,dvo2:1080p-60 debug=1
and then it hangs. I can't use Ctrl-C or anything else. The same happens without the debug argument and also with just "modprobe vpss".
I don't know if it's relevant or not but occasionally ProcMgrApp fails with this:
ProcMgrApp sample application
Entered ProcMgrApp_startup
ProcMgr_attach status: [0x0]
After attach: ProcMgr_getState
state [0x1]
Error in ProcMgr_load [0x83046005]
Leaving ProcMgrApp_startup
Press enter to continue and perform shutdown ...
Assertion at Line no: 127 in /home/user/ezsdk/ti-ezsdk_c6a816x-evm_5_00_00_56/s
yslink_02_00_00_56/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/
utils/hlos/Memory.c: (size > 0) : failed
Entered ProcMgrApp_shutdown
Assertion at Line no: 261 in /home/user/ezsdk/ti-ezsdk_c6a816x-evm_5_00_00_56/s
yslink_02_00_00_56/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/
utils/hlos/knl/osal/Linux/MemoryOS.c: (size > 0) : failed
Assertion at Line no: 304 in /home/user/ezsdk/ti-ezsdk_c6a816x-evm_5_00_00_56/s
yslink_02_00_00_56/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/
ipc/hlos/knl/Linux/IpcDrv.c: (status >= 0) : failed
Ipc_control Ipc_CONTROLCMD_STOPCALLBACK status: [0xffffffff]
ProcMgr_stop status: [0x6a85000]
After stop: ProcMgr_getState
state [0x2]
ProcMgr_unload status: [0x8485f003]
After unload: ProcMgr_getState
state [0x2]
ProcMgr_detach status: [0x0]
After detach: ProcMgr_getState
state [0x0]
ProcMgr_close status: [0x0]
Leaving ProcMgrApp_shutdown
If I just load VPSS without loading syslink and running ProcMgrApp first it seems to load the module but with this error message:
# modprobe vpss mode=hdmi:1080p-60,dvo2:1080p-60 debug=1
SysLink module created on Date:Mar 29 2011 Time:14:15:57
Entered KnlUtilsDrv_initializeModule
traceMask value: 0x0
Leaving KnlUtilsDrv_initializeModule 0x0
VPSS_FVID2: Failed to send version command to M3 0xfffffff9.
VPSS_CORE : Failed to init fvid2 interface,
vpss: probe of vpss failed with error -22
So, does anyone know why my VPSS module is failing to load?
Thanks,
Ralph