Re: dm6437 resizer problem, source is from ccdc ,not sdram
Il 24/12/10 11.04, ha scritto: > hi > these days , i've been working on VPFE resizer . and my platform is dm6437. are you using linux on 6437? Which version? Virtuallogix? Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Linux + CE + POSIX interval timers
On 02/04/2011 06:45 PM, Danny Marsh wrote: Hello, We are developing a DM6446 platform with linux and the dvsdk_2_00_00_22. We have created several iUniversal Codec Engine algorithms and can get them to run independently. We then tried to integrate the algorithms into another application that was using interval timers (setitimer and timer_create), and ALSA. This is where we started running into issues. First when we started the interval timers before opening the DSP server, the server wouldn't even open. When we opened the handles to the DSP server before starting the interval timers it opened, but the interval timers weren't working correctly. I used timers in a previous project, and the worked fine with kernel 2.6.18. But I did not use alsa, only video. Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: [PATCH 0/9] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver
On Fri, May 15, 2009 at 02:35:19PM -0400, m-kariche...@ti.com wrote: > From: Muralidharan Karicheri > > VPFE Capture driver for DaVinci Media SOCs :- DM355 and DM6446 maybe the question is silly, but how do these patches relate to the merge with Linus' tree? I mean, will it be merged for 2.6.30 or what? Ottavio -- Non c'è più forza nella normalità, c'è solo monotonia. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Status of the vlynq driver
Hi, I'm trying to understand the status of the vlynq driver. Last time (01/15/2009) I saw a patch from Hugo Vileneuve, which was based on on a previous driver coming out from openwrt. At that time, Kevin Hilman said it was going to push it to the repository, but I'm not able to find it any more. Were is it? Will it be merged into 2.6.30? Thanks, Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: [PATCH 0/9] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver
Kevin Hilman wrote: FYI I've added this series to a staging branch of DaVinci git after some minor compile updates for the new kernel. See branch 'staging/vpfe'. cool. I think I'll try it in a few days. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Status of the vlynq driver
Kevin Hilman wrote: Ottavio Campana writes: Hi, I'm trying to understand the status of the vlynq driver. Last time (01/15/2009) I saw a patch from Hugo Vileneuve, which was based on on a previous driver coming out from openwrt. At that time, Kevin Hilman said it was going to push it to the repository, but I'm not able to find it any more. Can you send a link for the post you're referring to? If there was such a driver submitted, I have forgotten about it and it has fallen through the cracks. The VLYNQ patches submitted by Hugo in January that I know of[1,2] were just some preliminary patches to allow VLYNQ to work and were merged at that time. That being said, the PSC changes made by [1] have been removed since we decoupled PSC and muxing. VLYNQ muxing should be done in board init files as necessary. Kevin [1] http://linux.omap.com/pipermail/davinci-linux-open-source/2009-January/010273.html [2] http://linux.omap.com/pipermail/davinci-linux-open-source/2009-January/010275.html yeah, that was the code I was referring to. But today, casually, I found this: http://lkml.indiana.edu/hypermail/linux/kernel/0906.0/00155.html Did you see it? ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
builing CE with latest kernel
Hi, I tried compiling CE 2.23.01 using 2.6.30-rc7 but I failed. Did anyone of you succeded? -- Non c'è più forza nella normalità, c'è solo monotonia. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: [PATCH 0/10 - v2] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver
m-kariche...@ti.com wrote:
From: Muralidharan Karicheri
VPFE Capture driver for DaVinci Media SOCs :- DM355 and DM6446
is this the same set of patches present in the branch staging/vpfe ?
I'm having a doubt with that set of patches. Particularly, I'm having
problems when detecting the video format, because I don't find the
define VPFE_STD_AUTO any more.
My code is
std = VPFE_STD_AUTO;
if (ioctl (worker_acquire->fd, VIDIOC_S_STD, &std) == -1)
{
fprintf (stderr, "set_data_format: ioctl VIDIOC_S_STD failed\n");
return -1;
}
/* wait until decoder is fully locked */
sleep (1);
if (ioctl (worker_acquire->fd, VIDIOC_QUERYSTD, &std) == -1)
{
fprintf (stderr, "set_data_format: ioctl VIDIOC_QUERYSTD failed\n");
return -1;
}
if (std == V4L2_STD_NTSC)
{
fprintf (stdout, "NTSC camera detected\n");
}
else if (std == V4L2_STD_PAL)
{
fprintf (stdout, "PAL camera detected\n");
}
else
{
fprintf (stdout, "Unknown video input standard\n");
return -1;
}
But VPFE_STD_AUTO does not exist:
otta...@debian2:~$ grep -r VPFE_STD_AUTO
/home/ottavio/Projects/stuff/openembedded/tmp/work/dm6446-evm-angstrom-linux-gnueabi/linux-davinci-2.6.29+2.6.30-rc7-r8+gitr03022e38318bef016836dae71c70b9ea975723e7-r8/git/*
otta...@debian2:~$
So the question is: how do I autodetect the video format? Do you have
some reference code?
Thank you,
Ottavio
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: [PATCH 0/9] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver
Ottavio Campana wrote: Kevin Hilman wrote: FYI I've added this series to a staging branch of DaVinci git after some minor compile updates for the new kernel. See branch 'staging/vpfe'. cool. I think I'll try it in a few days. I tried it today. It seems not to work, let me explain what I did. I checked out today openembedded (I had to modify the defconfig because it lacked vpfe support) and tried to build angstrom. With the exception of dsplik that does not build against the 2.6.30-rc7 kernel, everything seemed to be in good shape. But with udev I only see /dev/fb[0123], no /dev/video0 . The VIDIOC_QUERYCAP ioctl does not work on any of the /dev/fb* devices, but I think it's for /dev/video0, though I'm not sure. TVP5146 does not compile. So, basically, it does not work :-( I attach the dmesg and the kernel config. Please give me feedback and/or a hint to check if it works. Thank you, Ottavio Linux version 2.6.30-rc7-davinci1 (otta...@debian2) (gcc version 4.3.3 (GCC) ) #1 PREEMPT Wed Jun 10 18:00:36 CEST 2009 CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177 CPU: VIVT data cache, VIVT instruction cache Machine: DaVinci DM644x EVM Memory policy: ECC disabled, Data cache writeback On node 0 totalpages: 17920 free_area_init_node: node 0, pgdat c02f43c4, node_mem_map c0321000 DMA zone: 140 pages used for memmap DMA zone: 0 pages reserved DMA zone: 17780 pages, LIFO batch:3 DaVinci dm6446 variant 0x0 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17780 Kernel command line: console=ttyS0,115200n8 root/dev/nfs rw noinitrd ip=dhcp nf sroot=192.168.0.1:/srv/nfs/rootfs mem=70M NR_IRQS:168 PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 70MB = 70MB total Memory: 67740KB available (2696K code, 276K data, 108K init, 0K highmem) Calibrating delay loop... 147.86 BogoMIPS (lpj=739328) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok DaVinci: 71 gpio irqs net_namespace: 928 bytes NET: Registered protocol family 16 WARNING: both IDE and Flash are enabled, but they share AEMIF pins. Disable IDE for NAND/NOR support. bio: create slab at 0 Switched to high resolution mode on CPU 0 NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered NET: Registered protocol family 1 msgmni has been set to 132 io scheduler noop registered io scheduler anticipatory registered (default) Setting Up Clocks for DM420 OSD Console: switching to colour frame buffer device 90x30 fb0: dm_osd0_fb frame buffer device fb1: dm_vid0_fb frame buffer device fb2: dm_osd1_fb frame buffer device fb3: dm_vid1_fb frame buffer device Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0x1c2 (irq = 40) is a 16550A console [ttyS0] enabled serial8250 serial8250.0: unable to register port at index 1 (IO0 MEM1c20400 IRQ 41): -22 serial8250 serial8250.0: unable to register port at index 2 (IO0 MEM1c20800 IRQ 42): -22 brd: module loaded davinci_emac_probe: using random MAC addr: 36:38:ea:09:4d:ba emac-mii: probed console [netcon0] enabled netconsole: network logging started i2c /dev entries driver Linux video capture interface: v2.00 vpfe_init vpfe-capture: vpfe vpss master clock enabled vpfe-capture: vpfe vpss slave clock enabled vpfe-capture vpfe-capture: v4l2 device registered vpfe-capture vpfe-capture: video device registered vpfe-capture vpfe-capture: No Subdevice or platform client data dm644x_ccdc_init vpfe_register_ccdc_device: DM6446 CCDC TCP cubic registered NET: Registered protocol family 17 RPC: Registered udp transport module. RPC: Registered tcp transport module. eth0: attached PHY driver [LXT971] (mii_bus:phy_addr=1:01, id=1378e2) Sending DHCP requests .<6>PHY: 1:01 - Link is Up - 100/Full ., OK IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.0.104 IP-Config: Complete: device=eth0, addr=192.168.0.104, mask=255.255.255.0, gw=255.255.255.255, host=192.168.0.104, domain=example.org, nis-domain=(none), bootserver=0.0.0.0, rootserver=192.168.0.1, rootpath= Looking up port of RPC 13/2 on 192.168.0.1 Looking up port of RPC 15/1 on 192.168.0.1 VFS: Mounted root (nfs filesystem) on device 0:13. Freeing init memory: 108K watchdog watchdog: heartbeat 60 sec Uniform Multi-Platform E-IDE driver pcf857x 1-0038: gpios 104..111 on a pcf8574 pcf857x 1-0039: gpios 112..119 on a pcf8574 pcf857x 1-003a: gpios 120..127 on a pcf8574 ide0: MMIO-DMA Probing IDE interface ide0... ide0 at 0xfec661f0-0xfec661f7,0xfec663f6 on irq 22 musb_hdrc: version 6.0
Re: [PATCH 0/9] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver
Ottavio Campana wrote: Ottavio Campana wrote: Kevin Hilman wrote: FYI I've added this series to a staging branch of DaVinci git after some minor compile updates for the new kernel. See branch 'staging/vpfe'. cool. I think I'll try it in a few days. I tried it today. It seems not to work, let me explain what I did. I checked out today openembedded (I had to modify the defconfig because it lacked vpfe support) and tried to build angstrom. With the exception of dsplik that does not build against the 2.6.30-rc7 kernel, everything seemed to be in good shape. But with udev I only see /dev/fb[0123], no /dev/video0 . The VIDIOC_QUERYCAP ioctl does not work on any of the /dev/fb* devices, but I think it's for /dev/video0, though I'm not sure. TVP5146 does not compile. I investigated a bit more why tvp5146 does not compilare in staging/vpfe. I found out that drivers/media/video/tvp5146.c uses the constant I2C_DRIVERID_TVP5150 in line 604. Such constant does not exist and it fails compiling. I have a couple of questions: * what must the value of I2C_DRIVERID_TVP5150 be? * is the tvp5146 driver necessary to get the /dev/video0 device? Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Question about dvsdk 2.00.00.18 examples
Hi, I'd like to use a dm6446 to grab video from a camera and to encode it by using h264. By reading some emails that passed on this mailing list, I understood that with MVL5.0 I need to allocate buffers with CMEM and enqueue them to the video driver using user pointers. Successively I have to pass the dequeued buffer to the TI H.264 encoder. I downloaded the dvsdk 2.00.00.18, but I got confused by all the examples. Where do I find the examples of memory allocation with CMEM? And for encoding? Do I have to use dmai examples? Thank you for the help, Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
problem including xdc/std.h
I am following the codec engine application developer user's guide to develop a custom application using TI h264 HD encoder. The first required step is to #include But when I do it and try to compile I get ../../xdc/std.h:128: error: expected specifier-qualifier-list before 'xdc_IArg' ../../xdc/std.h:131: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'xdc_floatToArg' ../../xdc/std.h:139: error: expected ')' before 'a' ../../xdc/std.h:181: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'IArg' ../../xdc/std.h:182: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'UArg' ../../xdc/std.h:184: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'Int8' ../../xdc/std.h:185: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'Int16' ../../xdc/std.h:186: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'Int32' ../../xdc/std.h:191: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'UInt8' ../../xdc/std.h:192: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'UInt16' ../../xdc/std.h:193: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'UInt32' ../../xdc/std.h:204: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'Uint8' ../../xdc/std.h:205: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'Uint16' ../../xdc/std.h:206: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'Uint32' By reading xdc/std.h, it seems that the file is wrong because the order of declarations is incorrect. There must be something really stupid that I'm missing, but I cannot find it. -- Non c'è più forza nella normalità, c'è solo monotonia. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: problem including xdc/std.h
Hi, you answer makes me think that building a library without XDC package.bld is possibile. It it true? Considering that I just want to develop an application, is there a (more or less) official way to use just standard autotools? Ottavio On Tue, Jun 16, 2009 at 02:42:44PM -0500, Ring, Chris wrote: > This comes up a lot, I'll add this to the CE FAQ. > > If you're building a _library_: >* If you're not using XDC's package.bld-based build, you'll have to > explicitly define your 'target' via the -Dxdc_target__= option. >* If you're using XDC's package.bld-based build, the appropriate > xdc_target__ will be defined for you. > > If you're building an _executable_, you should run the config step prior to > building your application. >* If you're not using package.bld to build your app, you'll use > "configuro" to configure your app - which will generate a compiler.opt file > you should 'cat' into your CFLAGS (this will include the > -Dxdc_target__= define). (The CE Examples include a configuro > example makefile which does this - likely in > examples/ti/sdo/ce/examples/video_copy/*, but may vary based on your CE > version.) >* If you're using package.bld, similar to the lib build, this happens for > free. > > This all stems from 's extensibility support; the late binding to > a 'target' via the -D option lets both your .c code and remain > unchanged, and yet system integrators can integrate new 'targets' that > neither your .c files nor have seen into the system. > > Some more background docs: >* http://rtsc.eclipse.org/docs-tip/Consuming_Configurable_Content >* http://wiki.davincidsp.com/index.php/StdDotH > > Chris > > > -Original Message- > > From: > > davinci-linux-open-source-bounces+cring=ti@linux.davincids > > p.com > > [mailto:davinci-linux-open-source-bounces+cring=ti@linux.d > > avincidsp.com] On Behalf Of Ottavio Campana > > Sent: Tuesday, June 16, 2009 1:01 AM > > To: davinci-linux-open-source@linux.davincidsp.com > > Subject: problem including xdc/std.h > > > > I am following the codec engine application developer > > user's guide to > > develop a custom application using TI h264 HD encoder. > > > > The first required step is to > > > > #include > > > > But when I do it and try to compile I get > > > > ../../xdc/std.h:128: error: expected specifier-qualifier-list > > before 'xdc_IArg' > > ../../xdc/std.h:131: error: expected '=', ',', ';', 'asm' or > > '__attribute__' before 'xdc_floatToArg' > > ../../xdc/std.h:139: error: expected ')' before 'a' > > ../../xdc/std.h:181: error: expected '=', ',', ';', 'asm' or > > '__attribute__' before 'IArg' > > ../../xdc/std.h:182: error: expected '=', ',', ';', 'asm' or > > '__attribute__' before 'UArg' > > ../../xdc/std.h:184: error: expected '=', ',', ';', 'asm' or > > '__attribute__' before 'Int8' > > ../../xdc/std.h:185: error: expected '=', ',', ';', 'asm' or > > '__attribute__' before 'Int16' > > ../../xdc/std.h:186: error: expected '=', ',', ';', 'asm' or > > '__attribute__' before 'Int32' > > ../../xdc/std.h:191: error: expected '=', ',', ';', 'asm' or > > '__attribute__' before 'UInt8' > > ../../xdc/std.h:192: error: expected '=', ',', ';', 'asm' or > > '__attribute__' before 'UInt16' > > ../../xdc/std.h:193: error: expected '=', ',', ';', 'asm' or > > '__attribute__' before 'UInt32' > > ../../xdc/std.h:204: error: expected '=', ',', ';', 'asm' or > > '__attribute__' before 'Uint8' > > ../../xdc/std.h:205: error: expected '=', ',', ';', 'asm' or > > '__attribute__' before 'Uint16' > > ../../xdc/std.h:206: error: expected '=', ',', ';', 'asm' or > > '__attribute__' before 'Uint32' > > > > By reading xdc/std.h, it seems that the file is wrong > > because the order > > of declarations is incorrect. > > > > There must be something really stupid that I'm missing, but I cannot > > find it. > > > > -- > > Non c'è più forza nella normalità, c'è solo monotonia. > > > > ___ > > Davinci-linux-open-source mailing list > > Davinci-linux-open-source@linux.davincidsp.com > > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > > -- Non c'è più forza nella normalità, c'è solo monotonia. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
have you ever seen this error?
I'm trying to develop my application based on encodeCombo on a dm6446.
When I try to open codec engine I get this error:
Processor_create: execv failed: Permission denied
Comm_locate:msgget: No such file or directory
error: could not open engine encode : Unable to locate the server on the DSP
By looking in google, I didn't find anything. Do you have ideas?
The code that triggers the error is
static String video_enc_name = "encode";
...
CERuntime_init ();
Engine_Error error_code;
ce = Engine_open(video_enc_name, NULL, &error_code);
if (ce == NULL)
{
fprintf (stderr, "error: could not open engine %s :",
video_enc_name);
switch (error_code)
...
Ottavio
--
Non c'è più forza nella normalità, c'è solo monotonia.
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: have you ever seen this error?
On Thu, Jun 18, 2009 at 10:53:15AM +0200, Vladimir Pantelic wrote:
> Ottavio Campana wrote:
> >I'm trying to develop my application based on encodeCombo on a dm6446.
> >
> >When I try to open codec engine I get this error:
> >
> >Processor_create: execv failed: Permission denied
> >Comm_locate:msgget: No such file or directory
> >error: could not open engine encode : Unable to locate the server on the
> >DSP
>
> well, where is your DSP file? CE tries to find the DSP server file and
> fails.
> most demo setups expect it in the same folder as the app, so check.
I do have encodeCombo.x64P in the same directory. While looking in
google, I found how to get more debug information, so, by setting
CE_DEBUG=2 here is what I get:
@0,560,910us: [+6 T:0x4001eb80] CE - Engine_init> CE debugging on (CE_DEBUG=2;
allowed CE_DEBUG levels: 1=min, 2=good, 3=max)
@0,561,232us: [+0 T:0x4001eb80] CS - Server_init()
@0,561,382us: [+0 T:0x4001eb80] CS - Server_init> Global_useLinkArbiter = 0
@0,561,767us: [+0 T:0x4001eb80] CE - Engine_open> Enter('encode', 0x0,
0xbe81fb8c)
@0,562,047us: [+0 T:0x4001eb80] CE - rserverOpen('encodeCombo.x64P'), count = 0
@0,562,207us: [+0 T:0x4001eb80] OP - Processor_create>
Enter(imageName='encodeCombo.x64P', attrs=0xbe81fb40)
@0,565,950us: [+0 T:0x4001eb80] OP - Processor_create> return (0x37c50)
@0,566,243us: [+0 T:0x4001eb80] CE - rserverOpen('encodeCombo.x64P'): 0x2da78
done.
Processor_create: execv failed: Permission denied
@0,571,824us: [+0 T:0x4001eb80] OP - Processor_create> return (0x37c50)
@0,573,300us: [+0 T:0x4001eb80] CE - rserverOpen('encodeCombo.x64P'): 0x2da78
done.
Comm_locate:msgget: No such file or directory
@10,569,223us: [+0 T:0x4001eb80] CE - Engine_close(0x37d48)
Comm_put: Invalid argument
@10,571,436us: [+0 T:0x4001eb80] CE - rserverClose(0x2da78), count = 1
@10,571,624us: [+0 T:0x4001eb80] OP - Processor_delete> Enter(proc=0x37c50)
@10,571,880us: [+1 T:0x4001eb80] OP - Processor_delete(0x37c50) freeing object
...
@10,572,052us: [+0 T:0x4001eb80] OP - Processor_delete> return.
@10,572,184us: [+0 T:0x4001eb80] CE - rserverClose(0x2da78) done.
@10,572,318us: [+0 T:0x4001eb80] CE - Engine_open> return(0)
error: could not open engine encode : Unable to locate the server on the DSP
So, "rserverOpen('encodeCombo.x64P'): 0x2da78 done" gives me the
idea that it works correctly. But immediately after that I get
"Processor_create: execv failed: Permission denied"
What can it be? Anything DSP related?
--
Non c'è più forza nella normalità, c'è solo monotonia.
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: have you ever seen this error?
(again, it seems the first time it did not have the list as
destination).
It seems to be correct, I'll paste it so that you can check, do you have
any other idea?
var osalGlobal = xdc.useModule( 'ti.sdo.ce.osal.Global' );
osalGlobal.runtimeEnv = osalGlobal.DSPLINK_LINUX;
var TraceUtil = xdc.useModule('ti.sdo.ce.utils.trace.TraceUtil');
TraceUtil.attrs = TraceUtil.FULL_TRACING;
xdc.loadPackage("ti.sdo.ce.video2");
xdc.loadPackage("ti.sdo.ce.video1");
xdc.loadPackage("ti.sdo.ce.video");
xdc.loadPackage("ti.sdo.ce.image1");
xdc.loadPackage("ti.sdo.ce.audio1");
xdc.loadPackage("ti.sdo.ce.audio");
xdc.loadPackage("ti.sdo.ce.speech1");
xdc.loadPackage("ti.sdo.ce.speech");
var Engine = xdc.useModule('ti.sdo.ce.Engine');
var encode = Engine.createFromServer(
"encode",
"./encodeCombo.x64P",
"ti.sdo.servers.encode"
);
On Thu, Jun 18, 2009 at 08:04:55AM -0500, Ring, Chris wrote:
> Double check that your ARM-side .cfg script is correctly setting the OSAL
> .runtimeEnv to "DSPLINK_LINUX". Something like this:
>
> ==
> /* Load support for the Codec Engine OSAL */
> var osalGlobal = xdc.useModule('ti.sdo.ce.osal.Global');
>
> /* Configure CE to use it's DSP Link Linux version */
> osalGlobal.runtimeEnv = osalGlobal.DSPLINK_LINUX;
> ==
>
> If it's [incorrectly] set to "osalGlobal.LINUX", you may get that error.
>
> Chris
>
> > -Original Message-
> > From: davinci-linux-open-source-boun...@linux.davincidsp.com
> > [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com
> > ] On Behalf Of Ottavio Campana
> > Sent: Thursday, June 18, 2009 2:19 AM
> > To: davinci-linux-open-source@linux.davincidsp.com
> > Subject: Re: have you ever seen this error?
> >
> > On Thu, Jun 18, 2009 at 10:53:15AM +0200, Vladimir Pantelic wrote:
> > > Ottavio Campana wrote:
> > > >I'm trying to develop my application based on encodeCombo
> > on a dm6446.
> > > >
> > > >When I try to open codec engine I get this error:
> > > >
> > > >Processor_create: execv failed: Permission denied
> > > >Comm_locate:msgget: No such file or directory
> > > >error: could not open engine encode : Unable to locate the
> > server on the
> > > >DSP
> > >
> > > well, where is your DSP file? CE tries to find the DSP
> > server file and
> > > fails.
> > > most demo setups expect it in the same folder as the app, so check.
> >
> > I do have encodeCombo.x64P in the same directory. While
> > looking in
> > google, I found how to get more debug information, so,
> > by setting
> > CE_DEBUG=2 here is what I get:
> >
> > @0,560,910us: [+6 T:0x4001eb80] CE - Engine_init> CE
> > debugging on (CE_DEBUG=2; allowed CE_DEBUG levels: 1=min,
> > 2=good, 3=max)
> > @0,561,232us: [+0 T:0x4001eb80] CS - Server_init()
> > @0,561,382us: [+0 T:0x4001eb80] CS - Server_init>
> > Global_useLinkArbiter = 0
> > @0,561,767us: [+0 T:0x4001eb80] CE - Engine_open>
> > Enter('encode', 0x0, 0xbe81fb8c)
> > @0,562,047us: [+0 T:0x4001eb80] CE -
> > rserverOpen('encodeCombo.x64P'), count = 0
> > @0,562,207us: [+0 T:0x4001eb80] OP - Processor_create>
> > Enter(imageName='encodeCombo.x64P', attrs=0xbe81fb40)
> > @0,565,950us: [+0 T:0x4001eb80] OP - Processor_create> return
> > (0x37c50)
> > @0,566,243us: [+0 T:0x4001eb80] CE -
> > rserverOpen('encodeCombo.x64P'): 0x2da78 done.
> > Processor_create: execv failed: Permission denied
> > @0,571,824us: [+0 T:0x4001eb80] OP - Processor_create> return
> > (0x37c50)
> > @0,573,300us: [+0 T:0x4001eb80] CE -
> > rserverOpen('encodeCombo.x64P'): 0x2da78 done.
> > Comm_locate:msgget: No such file or directory
> > @10,569,223us: [+0 T:0x4001eb80] CE - Engine_close(0x37d48)
> > Comm_put: Invalid argument
> > @10,571,436us: [+0 T:0x4001eb80] CE - rserverClose(0x2da78), count = 1
> > @10,571,624us: [+0 T:0x4001eb80] OP - Processor_delete>
> > Enter(proc=0x37c50)
> > @10,571,880us: [+1 T:0x4001eb80] OP -
> > Processor_delete(0x37c50) freeing object ...
> > @10,572,052us: [+0 T:0x4001eb80] OP - Processor_delete> return.
> > @10,572,184us: [+0 T:0x4001eb80] CE - rserverClose(0x2da78) done.
> > @10,572,318us: [+0 T:0x4001eb80] CE - Engine_open> return(0)
> > error: could
Re: have you ever seen this error?
001eb80] CE - Engine_setTrace> return(0)
@0x000a70b8:[T:0x4001eb80] CE - Engine_open> return(322752)
@0x000a7635:[T:0x4001eb80] ti.sdo.ce.video1.VIDENC1 - VIDENC1_create> Enter
(engine=0x4ecc0, name='h264enc', params=0x0)
@0x000a7ba6:[T:0x4001eb80] CV - VISA_create(0x4ecc0, 'h264enc', 0x0, 0x2496,
'ti.sdo.ce.video1.IVIDENC1')
@0x000a80dd:[T:0x4001eb80] CV - VISA_create2(0x4ecc0, 'h264enc', 0x0, 0x0,
0x2496, 'ti.sdo.ce.video1.IVIDENC1')
@0x000a8642:[T:0x4001eb80] OM - Memory_alloc> Enter(0x30)
@0x000a8856:[T:0x4001eb80] OM - Memory_alloc> return (0x4ed78)
@0x000a8921:[T:0x4001eb80] CE - Engine_createNode(0x4ecc0, 'h264enc', 2496,
0x0, 0x0, 0xbee67aec)
@0x000a89bd:[T:0x4001eb80] CE - Engine> allocNode Enter(engine=0x4ecc0,
impId='h264enc')
@0x000a8a3c:[T:0x4001eb80] OM - Memory_alloc> Enter(0x20)
@0x000a8ab6:[T:0x4001eb80] OM - Memory_alloc> return (0x4c580)
@0x000a8b43:[T:0x4001eb80] CE - Engine> allocNode(). Calling
Comm_create(gppfromnode_4218_1, 0x4c588, NULL)
@0x000a8bc5:[T:0x4001eb80] OC - Comm_create>
Enter(queueName='gppfromnode_4218_1', queue=0x4c588, attrs=0x0)
@0x000a8c42:[T:0x4001eb80] OM - Memory_alloc> Enter(0x4)
@0x000a8cba:[T:0x4001eb80] OM - Memory_alloc> return (0x4e8a0)
@0x000a8f27:[T:0x4001eb80] OC - Comm_create> return (0x4e8a0)
@0x000a8fe4:[T:0x4001eb80] OC - Comm_put> Enter(queue=0x0, msg=0x415eec80)
@0x000a90bd:[T:0x4001eb80] OC - Comm_put> return (0)
@0x000a9148:[T:0x4001eb80] OC - Comm_get> Enter(queue=0x1, msg=0xbee67a04,
timeout=-1)
@0x000af2f1:[T:0x4001eb80] OC - Comm_get> MSGQ_get() status=0x8000, return (0)
@0x000af3cb:[T:0x4001eb80] OC - Comm_put> Enter(queue=0x0, msg=0x415eec80)
@0x000af4aa:[T:0x4001eb80] OC - Comm_put> return (0)
@0x000af56c:[T:0x4001eb80] OC - Comm_get> Enter(queue=0x1, msg=0xbee67a04,
timeout=-1)
@0x000afb2d:[T:0x4001eb80] OC - Comm_get> MSGQ_get() status=0x8000, return (0)
@0x000afc02:[T:0x4001eb80] CE - Engine_createNode> created node(stdIn=0x2,
stdOut=0x10001, msgq=0x4e8a0, algName='h264enc', rmsNode=0x8fa46f48,
algHandle=0x8fa47030)
@0x000b0151:[T:0x4001eb80] CE - Engine_createNode> Returning 0x4c580
@0x000b01e3:[T:0x4001eb80] OM - Memory_alloc> Enter(0x4)
@0x000b026d:[T:0x4001eb80] OM - Memory_alloc> return (0x4e8b0)
@0x000b02f0:[T:0x4001eb80] OC - Comm_alloc> Enter(poolId=0x0, msg=0x4e8b0,
size=2496)
@0x000b03a6:[T:0x4001eb80] OC - Comm_alloc> msg=0x415efc80, returning (0)
@0x000b044a:[T:0x4001eb80] CV - VISA_create> remote codec created
(name='h264enc', localQueueID=0x10001, remoteQueueID=0x0002)
@0x000b04e5:[T:0x4001eb80] ti.sdo.ce.video1.VIDENC1 - VIDENC1_create> return
(0x4ed78)
On Thu, Jun 18, 2009 at 09:40:50AM -0500, Ring, Chris wrote:
> Which version of CE are you using? I want to cross-check your trace output
> below against the actual sources.
>
> Your .cfg script below looks right, but the trace output [way] below
> indicates that the wrong .runtimeEnv is being pulled in. Namely, the trace
> indicates that the "LINUX" runtimeEnv rather than the "DSPLINK_LINUX"
> runtimeEnv is being used. Hmmm...
>
> Maybe your build is broken - can you provide a dump of your build log (should
> include a bunch of "will link with :" output - I'm
> curious to see which libs are getting linked in.
>
> Chris
>
> > -Original Message-
> > From: Ottavio Campana [mailto:ottavio.camp...@dei.unipd.it]
> > Sent: Thursday, June 18, 2009 7:01 AM
> > To: Ring, Chris
> > Cc: Ottavio Campana; davinci-linux-open-source@linux.davincidsp.com
> > Subject: Re: have you ever seen this error?
> >
> > (again, it seems the first time it did not have the list as
> > destination).
> >
> > It seems to be correct, I'll paste it so that you can check,
> > do you have
> > any other idea?
> >
> > var osalGlobal = xdc.useModule( 'ti.sdo.ce.osal.Global' );
> > osalGlobal.runtimeEnv = osalGlobal.DSPLINK_LINUX;
> >
> > var TraceUtil = xdc.useModule('ti.sdo.ce.utils.trace.TraceUtil');
> > TraceUtil.attrs = TraceUtil.FULL_TRACING;
> >
> > xdc.loadPackage("ti.sdo.ce.video2");
> > xdc.loadPackage("ti.sdo.ce.video1");
> > xdc.loadPackage("ti.sdo.ce.video");
> > xdc.loadPackage("ti.sdo.ce.image1");
> > xdc.loadPackage("ti.sdo.ce.audio1");
> > xdc.loadPackage("ti.sdo.ce.audio");
> > xdc.loadPackage("ti.sdo.ce.speech1");
> > xdc.loadPackage("ti.sdo.ce.speech");
> >
> > var Engine = xdc.useModule('ti.sdo.ce.Engine');
> >
> > var encode = Engine.createFromServer(
> >
video capture and USERPTR
Hello, I'm trying to acquire video using user pointers, following the idea explained in http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg12884.html I am using MVL 5.0 and I want to use buffers allocated with codec engine to exchange data quickly between arm and dsp. Since the VIDIOC_DQBUF ioctl gives me an error whren I try to pass buffers to he driver, I just would like to know if USERPTR is supported for video capture by MVL5.0 kernel or not. Thank you, Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
looking for h264 encoder examples
Hi,
I'm having some problems with the h264 encoder on a dm6446.
If I call
video_enc = VIDENC1_create (ce, "h264enc", NULL);
it creates the encoder, but if I call
memset (&video_params, 0, sizeof (IVIDENC1_Params));
video_params.size = sizeof(IVIDENC1_Params);
video_params.encodingPreset = XDM_DEFAULT;
video_params.rateControlPreset = IVIDEO_LOW_DELAY;
video_params.dataEndianness = XDM_BYTE;
video_params.maxInterFrameInterval = 1;
video_params.inputContentType = IVIDEO_PROGRESSIVE;
video_params.reconChromaFormat = XDM_YUV_422ILE;
video_enc = VIDENC1_create (ce, "h264enc", &video_params);
I get the following error and I think it should be a configuration
error, but I cannot understand what it is.
So I am looking for some examples to use as trace to implement my h264
encoder. Where can I find them?
Ottavio.
@0,542,540us: [+0 T:0x4001eb80] CE - Engine_fwriteTrace> returning count [7152]
@0,542,713us: [+0 T:0x4001eb80] CE - Engine_open> return(322888)
@0,542,965us: [+0 T:0x4001eb80] ti.sdo.ce.video1.VIDENC1 - VIDENC1_create>
Enter (engine=0x4ed48, name='h264enc', params=0x43574)
@0,543,202us: [+0 T:0x4001eb80] CV - VISA_create(0x4ed48, 'h264enc', 0x43574,
0x2496, 'ti.sdo.ce.video1.IVIDENC1')
@0,543,371us: [+0 T:0x4001eb80] CV - VISA_create2(0x4ed48, 'h264enc', 0x43574,
0x30, 0x2496, 'ti.sdo.ce.video1.IVIDENC1')
@0,543,553us: [+0 T:0x4001eb80] CE - Engine_createNode(0x4ed48, 'h264enc',
2496, 0x43574, 0x30, 0xbedc5adc)
@0,543,716us: [+0 T:0x4001eb80] CE - Engine> allocNode Enter(engine=0x4ed48,
impId='h264enc')
@0,543,894us: [+0 T:0x4001eb80] CE - Engine> allocNode(). Calling
Comm_create(gppfromnode_1738_1, 0x4c588, NULL)
@0,547,482us: [+6 T:0x4001eb80] CE - Engine_createNode> Remote node creation
FAILED (0x80008008).
[DSP] @0,110,429tk: [+0 T:0x8fa424cc] OM - Memory_alloc> Enter(size=0x18)
[DSP] @0,110,477tk: [+0 T:0x8fa424cc] OM - Memory_alloc> return (0x8fa46f88)
[DSP] @0,110,526tk: [+0 T:0x8fa424cc] OM - Memory_alloc> Enter(size=0xa)
[DSP] @0,110,571tk: [+0 T:0x8fa424cc] OM - Memory_alloc> return (0x8fa46fa0)
[DSP] @0,110,626tk: [+0 T:0x8fa424cc] OM - Memory_alloc> Enter(size=0x20)
[DSP] @0,110,671tk: [+0 T:0x8fa424cc] OM - Memory_alloc> return (0x8fa46fb0)
[DSP] @0,110,721tk: [+0 T:0x8fa424cc] OM - Memory_alloc> Enter(size=0x24)
[DSP] @0,110,766tk: [+0 T:0x8fa424cc] OM - Memory_alloc> return (0x8fa46fd0)
[DSP] @0,110,835tk: [+0 T:0x8fa424cc] ti.sdo.ce.video1.VIDENC1 -
VIDENC1_create> Enter (engine=0x0, name='h264enc', params=0x8fe05cc0)
[DSP] @0,110,924tk: [+0 T:0x8fa424cc] CV - VISA_create(0x0, 'h264enc',
0x8fe05cc0, 0x2496, 'ti.sdo.ce.video1.IVIDENC1')
[DSP] @0,111,001tk: [+0 T:0x8fa424cc] CV - VISA_create2(0x0, 'h264enc',
0x8fe05cc0, 0x30, 0x2496, 'ti.sdo.ce.video1.IVIDENC1')
[DSP] @0,111,097tk: [+0 T:0x8fa424cc] CE - Engine_open> Enter('local',
0x8fa461cc, 0x9c0)
[DSP] @0,111,157tk: [+0 T:0x8fa424cc] OM - Memory_alloc> Enter(size=0x2c)
[DSP] @0,111,207tk: [+0 T:0x8fa424cc] OM - Memory_alloc> return (0x8fa47040)
[DSP] @0,111,264tk: [+0 T:0x8fa424cc] CE - Engine_open> return(-1885048768)
[DSP] @0,111,328tk: [+0 T:0x8fa424cc] OM - Memory_alloc> Enter(size=0x30)
[DSP] @0,111,373tk: [+0 T:0x8fa424cc] OM - Memory_alloc> return (0x8fa47070)
[DSP] @0,111,427tk: [+0 T:0x8fa424cc] ti.sdo.ce.alg.Algorithm -
Algorithm_create> Enter(fxns=0x8fac4fb8, idma3Fxns=0x8fac4fe4, iresFxns=0x0,
params=0x8fe05cc0, attrs=0x8fa462e0)
[DSP] @0,111,535tk: [+0 T:0x8fa424cc] OM - Memory_alloc> Enter(size=0x10)
[DSP] @0,111,580tk: [+0 T:0x8fa424cc] OM - Memory_alloc> return (0x8fa470a0)
[DSP] @0,111,947tk: [+7 T:0x8fa424cc] ti.sdo.ce.alg.Algorithm -
Algorithm_create> Algorithm creation FAILED; make sure that 1) alg params are
correct/appropriate, 2) there is enough internal and external algorithm memory
available -- check DSKT2 settings for heap assignments and scratch allocation
[DSP] @0,112,107tk: [+0 T:0x8fa424cc] ti.sdo.ce.alg.Algorithm -
Algorithm_delete> Enter(alg=0x8fa470a0)
[DSP] @0,112,170tk: [+0 T:0x8fa424cc] OM - Memory_free> Enter(addr=0x8fa470a0,
size=16)
[DSP] @0,112,226tk: [+0 T:0x8fa424cc] OM - Memory_free> return (0x1)
[DSP] @0,112,269tk: [+0 T:0x8fa424cc] ti.sdo.ce.alg.Algorithm -
Algorithm_delete> Exit
[DSP] @0,112,322tk: [+0 T:0x8fa424cc] ti.sdo.ce.alg.Algorithm -
Algorithm_create> return (0x0)
[DSP] @0,112,379tk: [+2 T:0x8fa424cc] CV - VISA_create2> FAILED to create local
codec.
[DSP] @0,112,430tk: [+0 T:0x8fa424cc] CV - VISA_delete(0x8fa47070)
[DSP] @0,112,476tk: [+5 T:0x8fa424cc] CV - VISA_delete> deleting codec
(localQueue=0x, remoteQueue=0x)
[DSP] @0,112,544tk: [+0 T:0x8fa424cc] OM - Me
Re: video capture and USERPTR
On Mon, Jun 22, 2009 at 04:14:15PM -0400, Ryan Talbot wrote: > > Since the VIDIOC_DQBUF ioctl gives me an error whren I try to > > pass buffers to he driver, I just would like to know if > > USERPTR is supported for video capture by MVL5.0 kernel or not. > > > > Which error is DQBUF giving you? Did you give the driver a REQBUF first > to switch it into USERPTR I/O mode? EINVAL. I studied the kernel code, only MMAP works, USERPTR ins't implemented. -- Non c'è più forza nella normalità, c'è solo monotonia. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
question about changing the NAND memory
Hi,
I'm developing a new board based on dm6446. I would like to change the
NAND memory, and I'm wondering how this would impact the kernel.
I mean, I saw in arch/arm/mach-davinci/board-dm644x-evm.c that the nand
partitioning is defined in the array davinci_evm_nandflash_partition .
My question is: if I change the NAND memory, what do I have to change?
Further more, I don't underdstand how the total size of the memory is
specified:
The code is
123 struct mtd_partition davinci_evm_nandflash_partition[] = {
124 /* Bootloader layout depends on whose u-boot is installed, but we
125 * can hide all the details.
126 * - block 0 for u-boot environment ... in mainline u-boot
127 * - block 1 for UBL (plus up to four backup copies in blocks 2..5)
128 * - blocks 6...? for u-boot
129 * - blocks 16..23 for u-boot environment ... in TI's u-boot
130 */
131 {
132 .name = "bootloader",
133 .offset = 0,
134 .size = SZ_256K + SZ_128K,
135 .mask_flags = MTD_WRITEABLE,/* force read-only
*/
136 },
137 /* Kernel */
138 {
139 .name = "kernel",
140 .offset = MTDPART_OFS_APPEND,
141 .size = SZ_4M,
142 .mask_flags = 0,
143 },
144 /* File system (older GIT kernels started this on the 5MB mark) */
145 {
146 .name = "filesystem",
147 .offset = MTDPART_OFS_APPEND,
148 .size = MTDPART_SIZ_FULL,
149 .mask_flags = 0,
150 }
151 /* A few blocks at end hold a flash BBT ... created by TI's CCS
152 * using flashwriter_nand.out, but ignored by TI's versions of
153 * Linux and u-boot. We boot faster by using them.
154 */
155 };
so, what is MTDPART_SIZ_FULL? Does it autodetect the size of the memory?
Thank you for your help,
Ottavio
--
Non c'è più forza nella normalità, c'è solo monotonia.
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
problem while experimenting with g711enc
Hi, I'm trying to use g711enc to make some experiments. Everything seems to work fine, but I don't know how I can play the compressed file I get from the application. How do you play it? -- Non c'è più forza nella normalità, c'è solo monotonia. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: problem while experimenting with g711enc
mmm... vlc output is [0287] main playlist: nothing to play so I suspect I'm missing an header or something similar... Do you add something at the beginning of the file? I currently just save the encoded output. Ottavio On Wed, Jul 22, 2009 at 01:47:02PM +0530, bhushan wrote: > Hi, > You may have to download the g711 codec lib for a player such as winamp/ > vlc then play it. > > Bhushan > > On Wed, Jul 22, 2009 at 12:48 PM, Ottavio Campana < > ottavio.camp...@dei.unipd.it> wrote: > > > Hi, > > > > I'm trying to use g711enc to make some experiments. Everything seems to > > work fine, but I don't know how I can play the compressed file I get > > from the application. > > > > How do you play it? > > > > -- > > Non c'è più forza nella normalità, c'è solo monotonia. > > > > ___ > > Davinci-linux-open-source mailing list > > Davinci-linux-open-source@linux.davincidsp.com > > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > > > > > > -- > Bhushan -- Non c'è più forza nella normalità, c'è solo monotonia. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: problem while experimenting with g711enc
would you mind posting the header you're using? On Wed, Jul 22, 2009 at 02:43:12PM +0530, Zuber wrote: > One quick solution is to put 44 bytes wav header at the beginning of the > G711 encoded file. > VLC will then recognize your clip and play it successfully. We have > tested it here. It works with vlc player. > > Zuber Saiyed > Embedded Engineer > eInfochips Ltd. > Tel. No. +91 79 26563705 Ext. 126 > Cell. No. +91 96621 33369 > www.einfochips.com > > > > Ottavio Campana wrote: > >mmm... > > > >vlc output is > >[0287] main playlist: nothing to play > >so I suspect I'm missing an header or something similar... > > > >Do you add something at the beginning of the file? I currently just save > >the encoded output. > > > >Ottavio > > > >On Wed, Jul 22, 2009 at 01:47:02PM +0530, bhushan wrote: > > > >>Hi, > >> You may have to download the g711 codec lib for a player such as winamp/ > >>vlc then play it. > >> > >>Bhushan > >> > >>On Wed, Jul 22, 2009 at 12:48 PM, Ottavio Campana < > >>ottavio.camp...@dei.unipd.it> wrote: > >> > >> > >>>Hi, > >>> > >>>I'm trying to use g711enc to make some experiments. Everything seems to > >>>work fine, but I don't know how I can play the compressed file I get > >>>from the application. > >>> > >>>How do you play it? > >>> > >>>-- > >>>Non c'è più forza nella normalità, c'è solo monotonia. > >>> > >>>___ > >>>Davinci-linux-open-source mailing list > >>>Davinci-linux-open-source@linux.davincidsp.com > >>>http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > >>> > >>> > >> > >>-- > >>Bhushan > >> > > > > > -- > _ > Disclaimer: This e-mail message and all attachments transmitted with it > are intended solely for the use of the addressee and may contain legally > privileged and confidential information. If the reader of this message > is not the intended recipient, or an employee or agent responsible for > delivering this message to the intended recipient, you are hereby > notified that any dissemination, distribution, copying, or other use of > this message or its attachments is strictly prohibited. If you have > received this message in error, please notify the sender immediately by > replying to this message and please delete it from your computer. Any > views expressed in this message are those of the individual sender > unless otherwise stated.Company has taken enough precautions to prevent > the spread of viruses. However the company accepts no liability for any > damage caused by any virus transmitted by this email. > _ > -- Non c'è più forza nella normalità, c'è solo monotonia. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Regarding Support from TI
On Thu, Sep 17, 2009 at 12:13:43PM +0530, Sandeep YEDIRE wrote: > Thank you for reply. > I posted my problem on E2E but no reply. May be my info might not be > clear for them to comment on that. So What I want is solution/advice, > I can provide my code for simulating. Can I provide my code for > simulation to TI for help? If its paid, please let me know. I would like to know if there's the possibility of getting paid support, because I have companies asking for it when development hangs. I also have an unanswered question on E2E and I would like to have a help. You can see it here http://e2e.ti.com/forums/p/9628/37449.aspx -- Non c'è più forza nella normalità, c'è solo monotonia. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
what about /dev/ttyS2 in dm6446?
I'm trying MVL 5.0 downloaded from the website of TI. I only see /dev/ttyS0 and /dev/ttyS1, but the dm6446 has three UARTs. Why is /dev/ttyS2 not present? Do I just have to create the device? Or is support missing? Thanks, Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: I want to acquire VLYNQ protocol's specification
On Fri, Oct 16, 2009 at 01:57:32AM +, 임충권 wrote: > Hello > > I want to make a device that communicates with davinci through VLYNQ > but I don't really know how VLYNQ works, specially how the link is > stablished. > > SPRUE36.pdf seems to have an incomplete VLYNQ protocol specification. In sprue36a.pdf §2.6 they say Since VLYNQ devices can be controlled solely over the serial interface (that is, no local CPU exists), an automatic reliable initialization sequence (without user configuration) establishes a connection between two VLYNQ devices, just after a VLYNQ module is enabled and auto-negotiation occurs. Thus once you set up the vlynq registers, it will automatically set up the link with the other device. As far as I know, the low-level details of vlynq are not available. If you plan to develop a custom device then you have either to use a device from TI with a vlynq port or to buy an ip core from Xilinx to add the vlynq port to an fpga. Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
dm 357 status
Hi, I'd like to buy the evaluation board of DM357. In http://focus.ti.com/docs/toolsw/folders/print/tmdsevm357.html they say that it's supported by Montavista 2.6.18. Do you know how DM357 is supported in more recent versions of the kernel? I tried browsing http://git.kernel.org/?p=linux/kernel/git/khilman/linux-davinci.git for it but I didn't find anything... Thanks for your help, Ottavio -- Non c'è più forza nella normalità, c'è solo monotonia. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
status of Video Capture in git kernel?
Can you please tell me the status of video capture for the git kernel? I'd like to used it, but in http://wiki.davincidsp.com/index.php?title=DaVinci_GIT_Linux_Kernel it is said not to be available. Thank you, Ottavio -- Non c'è più forza nella normalità, c'è solo monotonia. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
problem with u-boot on NAND memory with dm6446
I'm trying to put u-boot on a custom board based on dm6446 in a NAND memory. I find some mismatches between the montavista linux kernel and u-boot 2009.11 . Particularly, in linux-2.6.18_pro500/arch/arm/mach-davinci/board-evm.c the variable davinci_nand_partitions has 4 elements bootloader of 265KB, params 128K, kernel 4M and filesystem the rest of the memory. But u-boot 2009.11 has a different partitions layout specified by mtdparts=davinci_nand.0:384k(bootloader)ro,4m(kernel),-(filesystem) In any case I would assume that after 0x6 (i.e. 384k) no data would be present, and by erasing it nothing would happen. But By erasing it u-boot stops working. The commands I give are: nand erase 0x0006 0x0040 nand write 0x8070 0x0006 0x0040 reset and u-boot does not work any more and I have to reinstall it with sfh. If I try to write to 0x0206 instead of 0x0006 it works, but I think it is wrong because when I to flash_eraseall -j /dev/mtdblock3 from linux I delete the kernel from the NAND and also because the correct address seems to be 0x0006 in this post: http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg06694.html So, I think that the position of u-boot at the beginning of the nand memory does not start at 0x0 and does not finish at 0x0005 . Thus, my questions are; 1) what is the correct place for u-boot in the NAND memory? 2) is it due to sfh? 3) how should I change mtdparts? how? Did you experience something similar? Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: problem with u-boot on NAND memory with dm6446
On Tue, Jan 26, 2010 at 09:42:43AM +0200, Caglar Akyuz wrote: > On Monday 25 January 2010 06:49:23 pm Ottavio Campana wrote: > > I'm trying to put u-boot on a custom board based on dm6446 in a NAND > > memory. > > > > I find some mismatches between the montavista linux kernel and u-boot > > 2009.11 . > > > > Are they using the same ecc/oob layout? In the past(2.6.10 era), it is known > that u-boot montavista linux kernel do not use the same layout. Does > montavista linux kernel suppose to work with u-boot 2009.11? mmm.. I don't know. By the way, I find a solution, I discovered that u-boot 2009.11 and bootargs "live" in the first MB of the nand, thus as a workaround I consider my nand divided into three parts: 1m of bootloader, 4m for the kernel and the rest for the rootfs. But I still dont' know where u-boot puts its stuf... > > Particularly, in linux-2.6.18_pro500/arch/arm/mach-davinci/board-evm.c > > the variable davinci_nand_partitions has 4 elements bootloader of 265KB, > > params 128K, kernel 4M and filesystem the rest of the memory. > > > > But u-boot 2009.11 has a different partitions layout specified by > > mtdparts=davinci_nand.0:384k(bootloader)ro,4m(kernel),-(filesystem) > > > > Correct me if I'm wrong but this is a kernel command line parameter. It has > nothing to do with u-boot partitions. does u-boot even support nand > partitions? By looking at the documentation at [1] I see it is just an > interface to use dynamic partitioning feature of Linux. well, mtdparts seems to be hardcoded in the kernel. By passing the variable nothing changes. > > In any case I would assume that after 0x6 (i.e. 384k) no data would > > be present, and by erasing it nothing would happen. But By erasing it > > u-boot stops working. > > > > The commands I give are: > > > > nand erase 0x0006 0x0040 > > nand write 0x8070 0x0006 0x0040 > > reset > > > > Do you want to update u-boot from u-boot? I never tried that, I thought ubl > obb layout and u-boot layout are not compatiple. no, just putting kernel and rootfs on the nand. In any case, it somehow works, I just would like now to understand what u-boot 2009.11 really does. Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: question on RAMDISK
Il 01/02/10 22.49, Naresh Kansara ha scritto: Hello All, I have two questions. 1. Is there a limit of 32MB on Ramdisk? I tried to use 64MB size and I got some errors I don't know, but maybe you're running out of memory 2. Has anybody tried to use two RAMDISK? If yes how to use two ramdisk? what I do is booting and mounting the rootfs on a ramdisk and successively I can mount in tmp a tmpfs volume. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
ogg vorbis encoder for dm6446
is there an encoder for dm6446 for ogg vorbis? Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: ogg vorbis encoder for dm6446
On Thu, Feb 04, 2010 at 07:43:24AM +0100, Bjørn Forsman wrote: > Hi Ottavio, > > On 2 February 2010 17:33, Ottavio Campana > wrote: > > is there an encoder for dm6446 for ogg vorbis? > > Yes, you can use GStreamer to get ogg/vorbis support on the DM6446. > This codec only runs on the ARM GPP, no DSP. what is the performance running on the GPP? I mean, can I get PAL or NTSC? ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: ogg vorbis encoder for dm6446
On Fri, Feb 05, 2010 at 09:12:12AM +0100, Vladimir Pantelic wrote: > Ottavio Campana wrote: >> On Thu, Feb 04, 2010 at 07:43:24AM +0100, Bjørn Forsman wrote: >>> Hi Ottavio, >>> >>> On 2 February 2010 17:33, Ottavio Campana >>> wrote: >>> > is there an encoder for dm6446 for ogg vorbis? >>> >>> Yes, you can use GStreamer to get ogg/vorbis support on the DM6446. >>> This codec only runs on the ARM GPP, no DSP. >> >> what is the performance running on the GPP? I mean, can I get PAL or NTSC? > > err, vorbis is an audio codec, no? well, vorbis is for audio and theora is for video and they are both part of ogg. I made a mistake, I ment the video encoder, not the audio. Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: DM6446 HELP:GPIO
Il 25/02/10 11.23, rohan tabish ha scritto: Hello everyine i want to know how to acess lets say an LED which is connected to GPIO. any help regarding it will be useful.I have seen the gpio.h file there are MACROS defined do i just need to use those MACROS if on the dvevm http://tiexpressdsp.com/index.php/LED_usage_on_DVEVM otherwise read Documentation/gpio.txt in the kernel sources. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: SPI with DM6446
Il 25/02/10 10.22, Alex Tarter ha scritto: I have trying to get my dm6446 running SDK2.0 to output on the SPI bus. I was grateful to Josh Hintze who posted a driver on this forum a few years ago (thank god for archives!), however I can’t seem to get it to work. When I send a write command to the driver it sends the SPI_CLK, SPI_D0 and SPI_EN0 pins high but doesn’t change their voltage. How do I get the clock to start cycling and data to come out? check the value of PINMUX1 (or PINMUX0, I don't perfectly remember) to see if the SPI controller is connected to the output pins. There's a bit that has to be set to 1. Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: arago next and gstreamer-ti and dm365
On Wed, Mar 17, 2010 at 06:05:39PM +0100, Raffaele Recalcati wrote: > I'm looking at gstreamer-ti, and seems really nice. > But the compilation stops due to the error below. > I'm not sure that I can ask something to this mailing list, but please > answer me where is the best place to go on with git kernel and DM365 codecs. > Thanks. Ciao! Even though it's related to TI products, I don't think this is the best place, since it's a problem related to OE. > NOTE: Task failed: Fetch failed: http://install.source.dir.local > /ti_cgt_c6000_6.1.9_setup_linux_x86.bin;name=cgt6xbin you need to download the c6000 compiler, put the tarball in your source directory and successively remove that line from the receipe. It has been a while since last time I checked the receipe, but I don't think things changed that much. Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: linux emif driver
Il 24/04/10 04.10, liuyue18301 ha scritto: > >hello everyone >in dm6446 we want to expand the seven uart devices by the emif > bus.but i can not find the emif bus driver in the Linux,if i want to > write/read data to the uart which expanded by the emif bus how can do it? now > i have no idea.who can give me a guideline > if you have a regular uart, just connect it to the emif. Then, add the serial port to arch/arm/mach-davinci/board-evm.c . This should work. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Running a Web Browser on DM6446
On Thu, Jun 03, 2010 at 09:35:01AM +0300, amr ali wrote: > > Hi, > I want to run a Web Browser on DM6446. Any head starts? > > Did anyone manage to run Ubuntu Desktop on any Davinci Boards? basically you need X working on the framebuffer or something like directfb + gtk + browser. I think having X running is the easiest solution and should be available in the evaluation version of montavista. Once you have X, you can do what you want. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Is populating /dev devices????
On 07/07/2010 08:54 AM, rohan tabish wrote: Is populating /dev devices required at each bootup .It takes about 5sec to populate all the devices how to ignore this? no, you can always provide a static /dev ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Prefered web server fo Davinci
On Wed, Sep 15, 2010 at 09:35:18AM -0400, Mark Deneen wrote: > On Wed, 2010-09-15 at 03:06 +0100, Jon Povey wrote: > > davinci-linux-open-source-boun...@linux.davincidsp.com wrote: > > > Could someone please tell me if there is a better, smaller, > > > easier to cross compile, and secure web server that you would > > > recommend? > > > > http://www.acme.com/software/thttpd/ looks promising at a glance. > > I haven't tried it, but it's small and uses GNU configure so may > > not be painful to cross-compile. > > > > I'd be interested to know your results - I may need to do something > > similar soon. > > > > As for security.. always a crapshoot. > > Perhaps you gain a little security through obscurity not using Apache. > > > Depending on what you need the web server to do, here's a few more > options: > > 1. lighttpd http://www.lighttpd.net/ > 2. uhttpd https://dev.openwrt.org/browser/trunk/package/uhttpd?rev=20573 > 3. publicfile http://cr.yp.to/publicfile.html > > lighttpd is the most advanced of the three, but it has fewer bells and > whistles than apache. if the task is just serving a few pages also busybox comes with a minimal webserver. You can do cgi with it, but you need to write shell scripts. Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
what about DM368 and TMS320C6A8167?
how are they supported by the git tree? Ottavio ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
