Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Regarding omx h264 decoder delay in live video streaming
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
B U J J I  
View profile  
 More options Aug 3 2011, 6:39 am
From: B U J J I <sivait...@gmail.com>
Date: Wed, 3 Aug 2011 16:09:48 +0530
Local: Wed, Aug 3 2011 6:39 am
Subject: Re: [pandaboard] Re: Regarding omx h264 decoder delay in live video streaming

Hi Vijay,

Thanks for your reply.

I tried as you said. but no luck

my steps for running:

*syslink_daemon Notify_MPUSYS_reroute_Test_Core0.xem3 dce_app_m3.xem3 *
Spawning SysLink Daemon...
root@vu-desktop:/home/vu/ducati# 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
  state [0x0]
MultiProc_getId procId: [0x1]
ProcMgr_open Status [0xca11000]
ProcMgr_attach status: [0x0]
After attach: ProcMgr_getState
  state [0x0]
SysM3 Load: loading the SysM3 image 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 [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]
*** DLoad4430_load: Failed to open file!
Error [0x8fade003] at Line no: 597 in file elfload/dload4430.c
*** ProcMgr_load: DLoad4430_load failed.
Error [0x8f2ba003] at Line no: 1544 in file ProcMgr.c
Error in ProcMgr_load, status [0x8f2ba003]
ipcSetup failed!

and

ps -A | grep syslink
gives nothing

So I am again confirming that syslink_dameon is not running already.

Let me share my setup steps also as well as you said like your setup is
working so i can get help from you:

1. downloaded ubuntu-netbook-10.10-preinstalled-netbook-armel+omap4.img.gz
and installed into sdcard and finished installtion. y

i didn't install ubuntu-omap4-extras so i didn't install any syslink related
componets so i don't have any syslink now.

2. Now i downloaded kernel from rob clark git
    git clone https://github.com/robclark/kernel-omap4.git
    cd kernel-omap4
    git checkout remotes/origin/ti-omap4-drm
   ( checked out remotes/origin/ti-omap4-drm version branch)

appiled patch also from http://review.omapzoom.org/#change,13113 ( i tried
both with/without patch)

   from this kernel with omap4_defconfig i got uImage after make.

3.Now I am created

Building Ducati/M3 Side Install TMS470/ARM Compiler
TMS470/ARM Code Generation Tools (CGT) - 4.6.1

Install Code Generation Tools (CGT) from:

   - https://www-a.ti.com/downloads/sds_support/CodeGenerationTools.htm

Install to *$HOME/ducati/ti_cgt_tms470_<version>*
 Install XDC tools

Download XDC tools from:

XDC tools - 3.20.07.86

   - http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc

Install to *$HOME/ducati/xdctools_<version>*
Install BIOS
BIOS (the RTOS) - 6.31.03.25

Download BIOS (the RTOS) from:

   -
   http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bi...

Install to *$HOME/ducati/bios_<version>*
Install Codec Engine
Codec Engine (CE) - 3.20.00.16

Download Codec Engine (CE) from:

   - http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/ce/

The lite version is fine. Install to *$HOME/ducati/codec_engine_<version>*
 Install Framework Components
Framework Component (FC) - 3.20.00.22

Download Framework Components (FC) from:

   - http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc

The lite version without fctools is fine. Install to *
$HOME/ducati/framework_components_<version>*
 Install XDAIS
XDAIS - 7.20.00.07

Download XDAIS from:

   -
   http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xd...

Untar to *$HOME/ducati/xdais_<version>*
Install HDVICP2 library codecs
HDVICP2 API and HDVICP2_CODECS - 1.00.000

Install HDCICP2 plus desired codecs from:

   -
   http://software-dl.ti.com/dsps/dsps_public_sw/codecs/HDVICP2/index_FD...

then

export TMS470_C_DIR="$HOME/ducati/ti_cgt_tms470_4_6_1/include;$HOME/ducati/ti_cgt_ tms470_4_6_1/lib"
export TMS470CGTOOLPATH="$HOME/ducati/ti_cgt_tms470_4_6_1"
XDCPATH=""
for f in $HOME/ducati/*/packages; do
  XDCPATH="$XDCPATH$f;"
done
export XDCPATH
export XDCROOT="$HOME/ducati/xdctools_3_20_07_86"
export XDCARGS="profile=release"

then

cd $HOME/ducati
git clone git://gitorious.org/bios-syslink/bios-syslink.git
cd bios-syslink/packages
git checkout 48e98007e21e311c126f89ff51616bf6d7067b9d

then

diff --git a/packages/config.bld b/packages/config.bld
index 01113a1..17e9862 100644
--- a/packages/config.bld
+++ b/packages/config.bld
@@ -228,6 +228,5 @@ M3.platform = M3.platforms[0];

 //Uncomment the require targets
 Build.targets = [
-                    C64T,
                     M3,
                 ];

next

export XDCBUILDCFG="`pwd`/config.bld"
$XDCROOT/xdc clean -PR ./ti
$XDCROOT/xdc -PR ./ti/sdo ./ti/omap/uart/ ./ti/omap/mem/
./ti/omap/platform/ ./ti/omap/slpm/ ./ti/omap/deh ./ti/omap/hdmiwa
$XDCROOT/xdc -PR ./ti/omap/samples/notify

this has given me
*
ti/omap/samples/notify/ti_omap_platform_core0/release/Notify_MPUSYS_reroute _Test_Core0.xem3
*.

Build DCE

cd $HOME/ducati
git clone git://github.com/robclark/libdce.git
cd libdce

export XDCBUILDCFG="`pwd`/ducati/build/config.bld"
cd ducati/platform/base_image
$XDCROOT/xdc -j4 -PD .

now i got *out/app_m3/release/dce_app_m3.xem3*.

$TMS470CGTOOLPATH/bin/strip470 Notify_MPUSYS_reroute_Test_Core0.xem3
$TMS470CGTOOLPATH/bin/strip470 dce_app_m3.xem3

with this i got my *Notify_MPUSYS_reroute_Test_Core0.xem3 and **dce_app_m3.xem3
and i have these two binaries.*
*
*
*Now I changed took the uImage to boot partion of my sdcard from
kernel-omap4 (from rob clark)  and booted with this.*
*
*
*Now On Pandaboard i compiled and installed following things*
* TILER userspace

git clone git://git.omapzoom.org/platform/hardware/ti/tiler.git
cd tiler
git checkout origin/memmgr_2.0
./bootstrap.sh
./configure --prefix=/usr
make -j4
sudo make install

*
*
*
* Build Syslink userspace

git clone git://git.omapzoom.org/platform/hardware/ti/syslink.git
cd syslink/syslink
git checkout origin/syslink-2.0
./bootstrap.sh
./configure --prefix=/usr
make -j4
sudo make install

[edit<http://www.omappedia.org/index.php?title=DistributedCodecEngine&actio...>
]Build DCE userspace

cd libdce
./autogen --prefix=/usr
make -j4
sudo make install

*

now I took *Notify_MPUSYS_reroute_Test_Core0.xem3 and **dce_app_m3.xem3  from
my system where they got created and copied to *
*Pandaboard.*
*and ran like this*
*sudo syslink_daemon Notify_MPUSYS_reroute_Test_Core0.xem3 dce_app_m3.xem3 *
*
*
this has failed ofcourse starting of this i have put the log that I got.

Now tell me where I am going wrong Is this the correct procedure with all
versions if not tell me what u did ?

*please reply back to me with all the software u used and tried that is
working successfully...*

Thanks and Regards,
Bujji

*
*
*
*
*
*

On Tue, Aug 2, 2011 at 2:39 PM, Vijay <kadambi.vi...@gmail.com> wrote:
> Hi Bujji,
> Even I have faced similar issue. But As Kozak pointed out, I already
> had a syslink.out running. I had killed that process and loaded the
> binaries again. And it worked. May be you kill as a normal user and
> not as root.. This should help.

> try the commands as given below
> ps –A | grep syslink*
> kill <pid>

> After this if u type
> ps –A | grep syslink* you will get the syslink daemon de-functioning.

> Again you load the binaries. This should help.

> Regards,
> VIjay

> On Jul 28, 4:11 pm, B U J J I <sivait...@gmail.com> wrote:
> > Hi all,
> > I tried the setup from the given instructionshttp://
> www.omappedia.org/wiki/DistributedCodecEngine and i am able 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.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
> >   state [0x0]
> > SysM3 Load: loading the SysM3 image
> > /home/vu/ducati/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 [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 = 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
> >   state [0x0]
> > SysM3 Load: loading the SysM3 image /home/vu/ducati/dce_app_m3.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 [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 = 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 guess.
> You
> > > should be good on the user space side though.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.