                                                                                                                                                                                                                                                                
Received-SPF: pass (google.com: domain of robdcl...@gmail.com designates 209.85.161.46 as permitted sender) client-ip=209.85.161.46;
MIME-Version: 1.0
In-Reply-To: <CAMYiwi9YvZWESuN0_3UGOuubZ8Y9wVVKg8t_tUCnDUPS+0N1Lw@mail.gmail.com>
References: <31063078.758.1311556825153.JavaMail.geo-discussion-forums@yqu12>
	<4233169.704.1311558723462.JavaMail.geo-discussion-forums@yqkc21>
	<CAMYiwi9YvZWESuN0_3UGOuubZ8Y9wVVKg8t_tUCnDUPS+0N...@mail.gmail.com>
Date: Fri, 29 Jul 2011 16:03:28 -0500
Message-ID: <CAF6AEGtjofrFR2qT7fYf=rnfz_Bs6B5+Ae8BuxYhg+NFiFz...@mail.gmail.com>
Subject: Re: [pandaboard] Regarding omx h264 decoder delay in live video streaming
From: Rob Clark <robdcl...@gmail.com>
To: pandaboard@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I believe you need to run syslink_daemon in one shot w/ both xem3's, ie:

syslink_daemon /home/vu/ducati/Notify_MPUSYS_reroute_Test_Core0.xem3
/home/vu/ducati/dce_app_m3.xem3

(note that in syslink v3.0, the xem3 images actually get combined into
a single firmware binary..)

BR,
-R

On Thu, Jul 28, 2011 at 6:11 AM, B U J J I <sivait...@gmail.com> wrote:
> Hi all,
> I tried the setup from the given instructions
> =A0http://www.omappedia.org/wiki/DistributedCodecEngine=A0=A0and i am abl=
e to
> create .xem3 files successfully as well.
> Now I ran the .xem3 files using syslink_dameon i got the following errors=
...
> sudo ./syslink_daemon /home/vu/ducati/Notify_MPUSYS_reroute_Test_Core0.xe=
m3
> Spawning SysLink Daemon...
> vu@vu-desktop:~/ducati/syslink/syslink/daemons/syslink$ MultiProc_getId
> remoteId: [0x2]
> MultiProc_getId remoteId: [0x1]
> MultiProc_getId remoteId: [0x0]
> MultiProc_getId procId: [0x2]
> ProcMgr_open Status [0xca11000]
> ProcMgr_attach status: [0x0]
> After attach: ProcMgr_getState
> =A0 state [0x0]
> SysM3 Load: loading the SysM3 image
> /home/vu/ducati/Notify_MPUSYS_reroute_Test_Core0.xem3
> =A0 Programming proc 2 MMU using linear address
> =A0 Programming SysM3 memory regions
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> VA =3D [0xa0000000] of size [0x100000] at PA =3D [0x9cf00000]
> VA =3D [0x0] of size [0x1000000] at PA =3D [0x9d000000]
> VA =3D [0x80000000] of size [0x1000000] at PA =3D [0x9e000000]
> VA =3D [0x81000000] of size [0x1000000] at PA =3D [0x9f000000]
> =A0 Programming SysM3 L4 peripherals
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> PA [0x60000000] VA [0x60000000] size [0x10000000]
> PA [0x70000000] VA [0x70000000] size [0x8000000]
> 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]
> PA [0x54000000] VA [0xb4000000] size [0x1000000]
> SysM3: Creating Ducati DMM pool of size 0x10000000
> Starting ProcMgr for procID =3D 2
> *** ProcMgrDrvUsr_ioctl: Driver ioctl failed!
> Error [0x8f2ba006] at Line no: 425 in file ProcMgrDrvUsr.c
> *** ProcMgr_start: API (through IOCTL) failed on kernel-side!
> Error [0x8f2ba006] at Line no: 1820 in file ProcMgr.c
> Error in ProcMgr_start, status [0x8f2ba006]
> ipcSetup failed!
>
>
> sudo ./syslink_daemon /home/vu/ducati/dce_app_m3.xem3
> Spawning SysLink Daemon...
> vu@vu-desktop:~/ducati/syslink/syslink/daemons/syslink$ MultiProc_getId
> remoteId: [0x2]
> MultiProc_getId remoteId: [0x1]
> MultiProc_getId remoteId: [0x0]
> MultiProc_getId procId: [0x2]
> ProcMgr_open Status [0xca11000]
> ProcMgr_attach status: [0x0]
> After attach: ProcMgr_getState
> =A0 state [0x0]
> SysM3 Load: loading the SysM3 image /home/vu/ducati/dce_app_m3.xem3
> =A0 Programming proc 2 MMU using linear address
> =A0 Programming SysM3 memory regions
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> VA =3D [0xa0000000] of size [0x100000] at PA =3D [0x9cf00000]
> VA =3D [0x0] of size [0x1000000] at PA =3D [0x9d000000]
> VA =3D [0x80000000] of size [0x1000000] at PA =3D [0x9e000000]
> VA =3D [0x81000000] of size [0x1000000] at PA =3D [0x9f000000]
> =A0 Programming SysM3 L4 peripherals
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> PA [0x60000000] VA [0x60000000] size [0x10000000]
> PA [0x70000000] VA [0x70000000] size [0x8000000]
> 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]
> PA [0x54000000] VA [0xb4000000] size [0x1000000]
> SysM3: Creating Ducati DMM pool of size 0x10000000
> Starting ProcMgr for procID =3D 2
> *** ProcMgrDrvUsr_ioctl: Driver ioctl failed!
> Error [0x8f2ba006] at Line no: 425 in file ProcMgrDrvUsr.c
> *** ProcMgr_start: API (through IOCTL) failed on kernel-side!
> Error [0x8f2ba006] at Line no: 1820 in file ProcMgr.c
> Error in ProcMgr_start, status [0x8f2ba006]
> ipcSetup failed!
>
> please give some inputs...
>
> Thanks,
> Bujji
>
>
>
> On Mon, Jul 25, 2011 at 7:22 AM, kozak | Subbu <c.a.subraman...@gmail.com=
>
> wrote:
>>
>> Also like Rob mentioned, k-2.6.35 and memmgr-2.0 wont fly. You have to
>> have a couple of patches taken in for k35 to work with memmgr-2.0 I gues=
s.
>> You should be good on the user space side though.
>
>