Hi,
You can look at DSPLink MPCS module. It provides a two-processor software
spinlock. We also have a MPLIST module, which is a shared memory list protected
with this MPCS lock.
http://wiki.davincidsp.com/index.php/DSPLink_Overview
Regards,
Mugdha
-Original Message-
From: davinci-l
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
Thanks guys!
The EABI configuration was the problem. My busybox was not compiled with AEABI,
so I disabled it in the compiler config, and now I get to the shell prompt.
However, there seems to be a problem with the serial interrupt now. While
pressing keys generates a serial interrupt, no tex
Hi Hemant :
i tried to use your patch with 2.6.10 kernel,
I have a PCI backplane with minimum 2 slots .
The DM646x EVM (without h/w modification ) is put in one of the slots and a
10/100 Mbps Ethernet PCI Adapter was used in other slot.
when my linux kenerl run to this function
void dm646xevm
Hi Hemant :
i tried to use your patch with 2.6.10 kernel,
I have a PCI backplane with minimum 2 slots .
The DM646x EVM (without h/w modification ) is put in one of the slots and a
10/100 Mbps Ethernet PCI Adapter was used in other slot.
when my linux kenerl run to this function
void dm646xevm
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
Hi Lingyun,
It is strange that you are hitting that code, because on unmodified EVMs, the
code inside 'if' block in dm646xevm_pci_setup is not supposed to be executed.
The reason is, when the (unmodified) EVM is put into PCI slot, the on-board
logic automatically enables PCI (EMIF disabled).
C
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:msgg
Hi,
sorry not to have answered sooner.
On Tuesday 09 June 2009 00:05:10 Karicheri, Muralidharan wrote:
> > > +
> > > +/* register access routines */
> > > +static inline u32 regr(u32 offset)
> > > +{
> > > + if (offset <= ccdc_addr_size)
> >
> > This should be <.
> >
> > > + return __raw_
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'
On Thu, Jun 18, 2009 at 03:08:54, Krzysztof Helt wrote:
> On Wed, 17 Jun 2009 10:01:10 -0400
> "Rajashekhara, Sudhakar" wrote:
>
> > Resending the same patch with additional Signed-off information.
> >
> > Adds LCD controller (LCDC) driver for TI's DA8xx/OMAP-L1xx architecture.
> > LCDC specific
(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.useM
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 ra
Hi,
I am using a custom board with dm355 and I have some questions about RAM
memory.
Booting my board from NFS and using the "free" command I get:
# free
total used free shared
buffers
Mem:7794034864430760
Adds LCD controller (LCDC) driver for TI's DA8xx/OMAP-L1xx architecture.
LCDC specifications can be found at http://www.ti.com/litv/pdf/sprufm0a.
LCDC on DA8xx consists of two independent controllers, the Raster Controller
and the LCD Interface Display Driver (LIDD) controller. LIDD further suppor
Dear Chris,
I think I found the problem while I was writing a long response to your
email with all the details. I found out that I linked to some wrong
libraries. Let me explain a bit.
I am compiling my program directly on the arm board, I have the rootfs
mounted on nfs. The only thing I
I modified 2.6.30-rc7 which was pulled from davinci git last week to
support our dm6446 board. In order to get i2s configured properly I had
to make some changes. There was no longer a definition for the CLKSM
bit. hwparams does not read the SRGR register, but instead simply sets
FSGM which
Hi all,
I want to restore the NAND flash file system on DM365 EVM, so I
followed the document of DM365 "getting started guide" on A.5.2.
1. Flash_eraseall /dev/mtd3
2. Mount -t yaffs2 /dev/mtdblock3 /mnt/nand
3. tar xf /target-reduced-dm365.tar
But for 1. Flash_eraseall, I saw
s-paul...@ti.com wrote:
> From: Sandeep Paulraj
>
> The patch applies to linux-mtd GIT tree
>
> This patch adds 4-bit ECC support for large page NAND chips using the new ECC
> mode NAND_ECC_HW_OOB_FIRST. The platform data from board-dm355-evm has been
> adjusted to use this mode.
>
> The patche
> -Original Message-
> From: Troy Kisky [mailto:troy.ki...@boundarydevices.com]
> Sent: Thursday, June 18, 2009 5:16 PM
> To: Paulraj, Sandeep
> Cc: davinci-linux-open-source@linux.davincidsp.com; linux-
> m...@lists.infradead.org; dw...@infradead.org; t...@linutronix.de;
> a...@linux-fou
Paulraj, Sandeep wrote:
>
>> -Original Message-
>> From: Troy Kisky [mailto:troy.ki...@boundarydevices.com]
>> Sent: Thursday, June 18, 2009 5:16 PM
>> To: Paulraj, Sandeep
>> Cc: davinci-linux-open-source@linux.davincidsp.com; linux-
>> m...@lists.infradead.org; dw...@infradead.org; t...@
On Thursday 18 June 2009, Troy Kisky wrote:
> > To answer your question, yes it can be at the end but I do not
> > see any reason why it has to be at the end
> > Any reason why you insist that it should be at the end.
>
> Well, for one, it is nice to have oobfree contiguous. But mainly, I hope
>
Hi Hemant,
i had add a spiflash chip to the EVM use the SPI CS1
i had modified the UBL to load u-boot image from the SPI flash
so i can boot the kenel , but i have not modify the CPLD logic.
lingyun
2009-06-19
发件人: Pedanekar, Hemant
发送时间: 2009-06-18 17:36:53
收件人: lingyun
抄送: davinci-linu
23 matches
Mail list logo