Hello,
I have a Blaze platform running Ubuntu 10.10. I am unable to get video captured from any of the cameras. This is most likely due to sylink errors that I have been getting.
For example, If I try to load ducati multimedia firmware , I get following errors. (message log is attached below). Below , I also logged the errors we get when running gst-pipeline (due to syslink errors).
Can someone help ? Thank you very much. Miko
root@blaze:~# omap-ducati-setup
Apparently ducati setup has already been done!
root@blazeC:~#
root@blaze:~# syslink_daemon.out /lib/firmware/omap4/Notify_MPUSYS_reroute_Test_Core0.xem3 /lib/firmware/omap4/base_image_app_m3.xem3
Spawning TILER server daemon...
root@blazeC:~# MultiProc_getId remoteId: [0x2]
MultiProc_getId remoteId: [0x1]
MultiProc_getId procId: [0x2]
RCM procId= 2
ProcMgr_open Status [0xbabe000]
ProcMgr_attach status: [0xf2ba000]
After attach: ProcMgr_getState
state [0xf2ba000]
MultiProc_getId procId: [0x1]
ProcMgr_open Status [0xbabe000]
ProcMgr_attach status: [0xf2ba000]
After attach: ProcMgr_getState
state [0xf2ba000]
SYSM3 Load: loading the SYSM3 image /lib/firmware/omap4/Notify_MPUSYS_reroute_Test_Core0.xem3
Programming proc 2 MMU using linear address
Programming SysM3 memory regions
=========================================
VA = [0xa0000000] of size [0x100000] at PA = [0x9cf00000]
VA = [0x0] of size [0x1000000] at PA = [0x9d000000]
VA = [0x80000000] of size [0x1000000] at PA = [0x9e000000]
VA = [0x81000000] of size [0x1000000] at PA = [0x9f000000]
Programming SysM3 L4 peripherals
=========================================
PA [0x60000000] VA [0x60000000] size [0x10000000]
PA [0x78000000] VA [0x78000000] size [0x8000000]
PA [0x4a000000] VA [0xaa000000] size [0x1000000]
PA [0x48000000] VA [0xa8000000] size [0x1000000]
PA [0x5a000000] VA [0xba000000] size [0x1000000]
PA [0x5b000000] VA [0xbb000000] size [0x1000000]
Starting ProcMgr for procID = 2
ProcMgrDrvUsr_ioctl 403 proc id = 2
*** ProcMgrDrvUsr_ioctl: Driver ioctl failed!
Error [0x8f2ba006] at Line no: 418 in file ProcMgrDrvUsr.c
*** ProcMgr_start: API (through IOCTL) failed on kernel-side!
Error [0x8f2ba006] at Line no: 1757 in file ProcMgr.c
Error in ProcMgr_start, status [0x8f2ba006]
ipcSetup failed!
Following is the syslog that is generated
Jun 7 13:59:46 blaze kernel: [ 79.207183] omap-remoteproc omap-remoteproc.0: omap_rproc_open: dev num 0, name tesla, count 2
Jun 7 13:59:46 blaze kernel: [ 79.216217] omap-remoteproc omap-remoteproc.1: omap_rproc_open: dev num 1, name ducati-proc0, count 2
Jun 7 13:59:46 blaze kernel: [ 79.225891] omap-remoteproc omap-remoteproc.2: omap_rproc_open: dev num 2, name ducati-proc1, count 2
Jun 7 13:59:46 blaze kernel: [ 79.236938] omap-remoteproc omap-remoteproc.0: omap_rproc_open: dev num 0, name tesla, count 2
Jun 7 13:59:46 blaze kernel: [ 79.245941] omap-remoteproc omap-remoteproc.1: omap_rproc_open: dev num 1, name ducati-proc0, count 2
Jun 7 13:59:46 blaze kernel: [ 79.255584] omap-remoteproc omap-remoteproc.2: omap_rproc_open: dev num 2, name ducati-proc1, count 2
Jun 7 13:59:46 blaze kernel: [ 79.270843] proc_mgr_attach:proc_mgr_handle->num_mem_entries = 0
Jun 7 13:59:46 blaze kernel: [ 79.282226] proc_mgr_attach:proc_mgr_handle->num_mem_entries = 0
Jun 7 13:59:46 blaze kernel: [ 79.327331] omap-remoteproc omap-remoteproc.1: omap_rproc_ioctl
Jun 7 13:59:46 blaze kernel: [ 79.333709] ------------[ cut here ]------------
Jun 7 13:59:46 blaze kernel: [ 79.338562] WARNING: at /build/buildd/linux-ti-omap4-2.6.35/arch/arm/plat-omap/omap_device.c:503 omap_device_enable+0x3c/0x88()
Jun 7 13:59:46 blaze kernel: [ 79.350524] omap_device: omap-remoteproc.1: omap_device_enable() called from invalid state 1
Jun 7 13:59:46 blaze kernel: [ 79.359344] Modules linked in: bt_drv(C) st_drv(C) dm_crypt rfcomm l2cap sco bluetooth rfkill joydev twl4030_pwrbutton dm_mirror dm_region_hash dm_log btrfs ohci_hcd
Jun 7 13:59:46 blaze kernel: [ 79.374847] [<80046788>] (unwind_backtrace+0x0/0xe4) from [<8007c3c0>] (warn_slowpath_common+0x4c/0x64)
Jun 7 13:59:46 blaze kernel: [ 79.384643] [<8007c3c0>] (warn_slowpath_common+0x4c/0x64) from [<8007c458>] (warn_slowpath_fmt+0x2c/0x3c)
Jun 7 13:59:46 blaze kernel: [ 79.394653] [<8007c458>] (warn_slowpath_fmt+0x2c/0x3c) from [<8005ace8>] (omap_device_enable+0x3c/0x88)
Jun 7 13:59:46 blaze kernel: [ 79.404449] [<8005ace8>] (omap_device_enable+0x3c/0x88) from [<8005427c>] (proc44x_start+0x5c/0xa4)
Jun 7 13:59:46 blaze kernel: [ 79.413909] [<8005427c>] (proc44x_start+0x5c/0xa4) from [<80061f88>] (rproc_start+0x4c/0x7c)
Jun 7 13:59:46 blaze kernel: [ 79.422729] [<80061f88>] (rproc_start+0x4c/0x7c) from [<80122c1c>] (vfs_ioctl+0x7c/0xac)
Jun 7 13:59:46 blaze kernel: [ 79.431182] [<80122c1c>] (vfs_ioctl+0x7c/0xac) from [<80122fa8>] (do_vfs_ioctl+0x1b4/0x1cc)
Jun 7 13:59:46 blaze kernel: [ 79.439910] [<80122fa8>] (do_vfs_ioctl+0x1b4/0x1cc) from [<8012300c>] (sys_ioctl+0x4c/0x6c)
Jun 7 13:59:47 blaze kernel: [ 79.448638] [<8012300c>] (sys_ioctl+0x4c/0x6c) from [<8003faa0>] (ret_fast_syscall+0x0/0x30)
Jun 7 13:59:47 blaze kernel: [ 79.457427] ---[ end trace 4aa69bd3c15a4bd5 ]---
Jun 7 13:59:57 blaze kernel: [ 89.470336] ------------[ cut here ]------------
Jun 7 13:59:57 blaze kernel: [ 89.475189] WARNING: at /build/buildd/linux-ti-omap4-2.6.35/drivers/dsp/syslink/multicore_ipc/../ipu_pm/ipu_pm.c:702 ipu_pm_notifications+0x178/0x304()
Jun 7 13:59:57 blaze kernel: [ 89.489318] Modules linked in: bt_drv(C) st_drv(C) dm_crypt rfcomm l2cap sco bluetooth rfkill joydev twl4030_pwrbutton dm_mirror dm_region_hash dm_log btrfs ohci_hcd
Jun 7 13:59:57 blaze kernel: [ 89.504821] [<80046788>] (unwind_backtrace+0x0/0xe4) from [<8007c3c0>] (warn_slowpath_common+0x4c/0x64)
Jun 7 13:59:57 blaze kernel: [ 89.514648] [<8007c3c0>] (warn_slowpath_common+0x4c/0x64) from [<8007c3f0>] (warn_slowpath_null+0x18/0x1c)
Jun 7 13:59:57 blaze kernel: [ 89.524719] [<8007c3f0>] (warn_slowpath_null+0x18/0x1c) from [<80404734>] (ipu_pm_notifications+0x178/0x304)
Jun 7 13:59:57 blaze kernel: [ 89.535003] [<80404734>] (ipu_pm_notifications+0x178/0x304) from [<804090f0>] (devh44xx_notifier_call+0x54/0xa8)
Jun 7 13:59:57 blaze kernel: [ 89.545623] [<804090f0>] (devh44xx_notifier_call+0x54/0xa8) from [<8054c5ac>] (notifier_call_chain+0x38/0x68)
Jun 7 13:59:57 blaze kernel: [ 89.555999] [<8054c5ac>] (notifier_call_chain+0x38/0x68) from [<8009bdd0>] (__blocking_notifier_call_chain+0x48/0x5c)
Jun 7 13:59:57 blaze kernel: [ 89.567077] [<8009bdd0>] (__blocking_notifier_call_chain+0x48/0x5c) from [<8009bdf8>] (blocking_notifier_call_chain+0x14/0x18)
Jun 7 13:59:57 blaze kernel: [ 89.578948] [<8009bdf8>] (blocking_notifier_call_chain+0x14/0x18) from [<803fcf3c>] (ipc_release+0x28/0xdc)
Jun 7 13:59:57 blaze kernel: [ 89.589141] [<803fcf3c>] (ipc_release+0x28/0xdc) from [<801161ec>] (__fput+0x104/0x1d0)
Jun 7 13:59:57 blaze kernel: [ 89.597473] [<801161ec>] (__fput+0x104/0x1d0) from [<8011311c>] (filp_close+0x6c/0x78)
Jun 7 13:59:57 blaze kernel: [ 89.605743] [<8011311c>] (filp_close+0x6c/0x78) from [<801131b4>] (sys_close+0x8c/0xcc)
Jun 7 13:59:57 blaze kernel: [ 89.614105] [<801131b4>] (sys_close+0x8c/0xcc) from [<8003faa0>] (ret_fast_syscall+0x0/0x30)
Jun 7 13:59:57 blaze kernel: [ 89.622894] ---[ end trace 4aa69bd3c15a4bd6 ]---
When gst pipeline is launched , following errors happen :
st-auto-launch omx_camera mode=1 focus=2 exposure=1 awb=1 vstab=false vnf=off name=cam cam.src ! "video/x-raw-yuv-strided, format=(fourcc)NV12, width=640, height=480, framerate=30/2, buffer-count-requested=4" ! queue name=q1 ! v4l2sink min-queued-bufs=2 sync=false crop-top=0 crop-left=0 crop-width=640 crop-height=480 device=/dev/video1 cam.vidsrc ! "video/x-raw-yuv-strided, format=(fourcc)NV12, width=640, height=480, framerate=30/2" ! queue name=q2 ! omx_h264enc input-buffers=2 output-buffers=2 bitrate=1000000 profile=2 level=2048 ! queue name=q3 ! qtmux ! filesink location=~/Videos/record_h264.mp4 0:play 60:eos
console log is as follows :
omx_proxy_common.c:1819 OMX_ProxyCommonInit() ERROR: ERROR executing OMX_GetHandle remotely
** (gst-auto-launch:1397): CRITICAL **: g_omx_core_init: assertion `core->omx_handle' failed
** (gst-auto-launch:1397): CRITICAL **: g_omx_core_get_handle: assertion `core->omx_handle' failed
Segmentation fault
syslog is as follows :
[ 3065.582519] omap-remoteproc omap-remoteproc.0: omap_rproc_open: dev num 0, name tesla, count 2
[ 3065.592498] omap-remoteproc omap-remoteproc.1: omap_rproc_open: dev num 1, name ducati-proc0, count 2
[ 3065.602905] omap-remoteproc omap-remoteproc.2: omap_rproc_open: dev num 2, name ducati-proc1, count 2
[ 3065.615295] omap-remoteproc omap-remoteproc.0: omap_rproc_open: dev num 0, name tesla, count 2
[ 3065.624969] omap-remoteproc omap-remoteproc.1: omap_rproc_open: dev num 1, name ducati-proc0, count 2
[ 3065.635162] omap-remoteproc omap-remoteproc.2: omap_rproc_open: dev num 2, name ducati-proc1, count 2
[ 3065.646514] proc4430_attach num_mem_entries = 6
[ 3065.651123] proc_mgr_attach:proc_mgr_handle->num_mem_entries = 0
[ 3065.658264] proc4430_attach num_mem_entries = 6
[ 3065.662841] proc_mgr_attach:proc_mgr_handle->num_mem_entries = 0
[ 3065.669921] nameserver_get_local entry not found!
