Dhaval,
We have a custom board with DM6441 on it and running MV 2.6.10.
When I got rid of the crippled I2C speed and delay for the MSP430 (we don't
use it), I was getting those errors in addition to "AL detected".
At least for the clunky driver in MV 2.6.10, the max bus speed I was able
to achieve was 60 KHz...
inter-transfer delay didn't seem to help at all so I dropped it.
So, try a bus speed of 50 to 60 KHz and see it that helps... it's better
than running at 20 KHz with a huge delay.
Regards,
David
--
DAVID A. KONDRAD
Software Design Engineer
On-Q/Legrand
Telephone (800) 321-2343 x311
www.onqlegrand.com
davinci-linux-ope
n-source-request@
linux.davincidsp. To
com davinci-linux-open-sou...@linux.dav
Sent by: incidsp.com
davinci-linux-ope cc
n-source-bounces@
linux.davincidsp. Subject
com Davinci-linux-open-source Digest,
Vol 37, Issue 83
01/20/2009 10:05
AM
Please respond to
davinci-linux-ope
n-sou...@linux.da
vincidsp.com
Send Davinci-linux-open-source mailing list submissions to
davinci-linux-open-source@linux.davincidsp.com
To subscribe or unsubscribe via the World Wide Web, visit
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
or, via email, send a message with subject or body 'help' to
davinci-linux-open-source-requ...@linux.davincidsp.com
You can reach the person managing the list at
davinci-linux-open-source-ow...@linux.davincidsp.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Davinci-linux-open-source digest..."
Today's Topics:
1. RE: Davinci i2c warning : command completely failed
(Rajashekhara, Sudhakar)
2. Re: [patch 0/6] EDMA interface updates (Sergei Shtylyov)
3. Re: [patch 0/6] EDMA interface updates (Sergei Shtylyov)
4. RE: Davinci i2c warning : command completely failed
(DHAVAL LAKKAD)
5. Query reg generating an event in DM6467 for every 5 min
(kirthika varadarajan)
6. disable linking xdc.runtime libraries (Viraj Karandikar)
----------------------------------------------------------------------
Message: 1
Date: Tue, 20 Jan 2009 19:06:37 +0530
From: "Rajashekhara, Sudhakar" <sudhakar....@ti.com>
Subject: RE: Davinci i2c warning : command completely failed
To: DHAVAL LAKKAD <dhaval.lak...@einfochips.com>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>
Message-ID:
<ff55437e1f14da4baeb721a458b67017068a375...@dbde02.ent.ti.com>
Content-Type: text/plain; charset="us-ascii"
Dhaval,
Try modifying the I2C bus frequency in the drivers/i2c/busses/i2c-davinci.c
file and see what happens.
Regards, Sudhakar
________________________________________
From: davinci-linux-open-source-boun...@linux.davincidsp.com
[davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of
DHAVAL LAKKAD [dhaval.lak...@einfochips.com]
Sent: Tuesday, January 20, 2009 6:37 PM
To: davinci-linux-open-source@linux.davincidsp.com
Subject: Davinci i2c warning : command completely failed
Hi ,
We are working on TI's DVEVM6467 processor. When we run any video
application
(eg. Capture, Display or Loopback ) continuously for more than 6 to 7
times,
then board gets hanged with the message "DaVinci I2C WARNING: i2c: cmd
complete
failed: complete = 0x0, icstr = 0x410". After getting this problem we have
to
just reboot the board. So can any one suggest the solution to resolve this
problem?
Regards,
Dhaval Lakkad
--
_____________________________________________________________________
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.
__________________________________________________________________________
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
------------------------------
Message: 2
Date: Tue, 20 Jan 2009 16:42:18 +0300
From: Sergei Shtylyov <sshtyl...@ru.mvista.com>
Subject: Re: [patch 0/6] EDMA interface updates
To: Kevin Hilman <khil...@deeprootsystems.com>
Cc: DaVinci <davinci-linux-open-source@linux.davincidsp.com>
Message-ID: <4975d4ba.40...@ru.mvista.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Hello.
Kevin Hilman wrote:
>>>>>>>>>Some of the comments about my earlier EDMA patches touched on
issues
>>>>>>>>>in that programming interface, like:
>>>>>>>>>- The single call to allocate DMA resources is overly complex.
>>>>>>>>>- Its programming model doesn't match the hardware well: talking
>>>>>>>>>about master vs. slave, not channels and parameter RAM; confusing
>>>>>>>>>those two resource types (especially when allocating); etc.
>>>>>>>>>- Since the calls used a "davinci_" prefix, they wouldn't be very
>>>>>>>>>appropriate for the DMA in the OMAP-L137 chip.
>>>>>>>>We were going to move the generic part of
>>>>>>>>arch/arm/mach-davinci/dma.c (alomg with other common code b/w so
>>>>>>>>called OMAP-L1x and DaVinci) to arch/arm/plat-davinci/ but the
rename
>>>>>>>>seems reasonable anyway.
>>>>>>>I keep hearing things like this, but have not yet seen any patches,
or
>>>>>>>technical arguments for doing so.
>>>>>> The technical argument is simple: sharing the code for two similar
>>>>>>platforms, the EDMA code in particular.
>>>>>The code already is shared.
>>>> How? You're not supposed to looks for the shared code in other
>>>>mach-*/ dirs, are you?
>>>I'm talking about DaVinci git tree here, not TI/MV trees. There is
>>>no plat-davinci, only a mach-davinci.
>>>The current DMA code is shared across the various devices currently
>>>supported in DaVinci git.
>>>The point I'm trying to make is that I still do not agree with the
>>>need to create a plat-davinci for "common" code. The reasons I've
>>>heard so far have not been convincing.
>> So, you want e.g. EDMA code duplicated, right?
> Um, no. You are the one who seems to be implying a new mach-*
> directory for a new platform which would require duplication.
> The way I currently see things is a single mach-davinci with support
> for dm644x, dm355, dm646x, omapl1x7, etc.
MV too have clinged to the idea of "parasitising" on the DaVinci code
till
the last possibility but then finally ditched it.
> Until technical reasons for the creation of a new mach-* directory are
> proposed and discussed on the list, that's the way I plan to continue
> things.
If completely different interrupt controller doesn't sound as
sufficient
technical reason, I think I won't be wasting any more time on this
argument.
Hopefully others will be able to provide better arguments. I've been tired
enough by the internal discussion already.
> Kevin
WBR, Sergei
------------------------------
Message: 3
Date: Tue, 20 Jan 2009 16:55:27 +0300
From: Sergei Shtylyov <sshtyl...@ru.mvista.com>
Subject: Re: [patch 0/6] EDMA interface updates
To: Sergei Shtylyov <sshtyl...@ru.mvista.com>
Cc: DaVinci <davinci-linux-open-source@linux.davincidsp.com>
Message-ID: <4975d7cf.3090...@ru.mvista.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Hello, I wrote:
>>>>>>>>>> Some of the comments about my earlier EDMA patches touched on
>>>>>>>>>> issues
>>>>>>>>>> in that programming interface, like:
>>>>>>>>>> - The single call to allocate DMA resources is overly complex.
>>>>>>>>>> - Its programming model doesn't match the hardware well:
talking
>>>>>>>>>> about master vs. slave, not channels and parameter RAM;
confusing
>>>>>>>>>> those two resource types (especially when allocating); etc.
>>>>>>>>>> - Since the calls used a "davinci_" prefix, they wouldn't be
very
>>>>>>>>>> appropriate for the DMA in the OMAP-L137 chip.
>
>
>>>>>>>>> We were going to move the generic part of
>>>>>>>>> arch/arm/mach-davinci/dma.c (alomg with other common code b/w so
>>>>>>>>> called OMAP-L1x and DaVinci) to arch/arm/plat-davinci/ but the
>>>>>>>>> rename
>>>>>>>>> seems reasonable anyway.
>
>
>>>>>>>> I keep hearing things like this, but have not yet seen any
>>>>>>>> patches, or
>>>>>>>> technical arguments for doing so.
>
>
>>>>>>> The technical argument is simple: sharing the code for two similar
>>>>>>> platforms, the EDMA code in particular.
>>>>>> The code already is shared.
>>>>> How? You're not supposed to looks for the shared code in other
>>>>> mach-*/ dirs, are you?
>>>> I'm talking about DaVinci git tree here, not TI/MV trees. There is
>>>> no plat-davinci, only a mach-davinci.
>>>> The current DMA code is shared across the various devices currently
>>>> supported in DaVinci git.
>>>> The point I'm trying to make is that I still do not agree with the
>>>> need to create a plat-davinci for "common" code. The reasons I've
>>>> heard so far have not been convincing.
>>> So, you want e.g. EDMA code duplicated, right?
>> Um, no. You are the one who seems to be implying a new mach-*
>> directory for a new platform which would require duplication.
>> The way I currently see things is a single mach-davinci with support
>> for dm644x, dm355, dm646x, omapl1x7, etc.
> MV too have clinged to the idea of "parasitising" on the DaVinci code
> till the last possibility but then finally ditched it.
>> Until technical reasons for the creation of a new mach-* directory are
>> proposed and discussed on the list, that's the way I plan to continue
>> things.
> If completely different interrupt controller doesn't sound as
> sufficient technical reason, I think I won't be wasting any more time on
> this argument. Hopefully others will be able to provide better
> arguments. I've been tired enough by the internal discussion already.
Just one last argument, to be as technical as possible: entry-macro.S
will
need either #ifdef'ery (thus defying your presumed idea of having the
single
binary to boot on all DaVinci like platfroms) or some kind of runtime check
(at one point we did implement that) in order to function on both
platfroms.
Are you sure we need all that?
>> Kevin
WBR, Sergei
------------------------------
Message: 4
Date: Tue, 20 Jan 2009 19:34:20 +0530 (IST)
From: "DHAVAL LAKKAD" <dhaval.lak...@einfochips.com>
Subject: RE: Davinci i2c warning : command completely failed
To: "Rajashekhara, Sudhakar" <sudhakar....@ti.com>
Cc: "davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>
Message-ID:
<1539.10.100.3.96.1232460260.squir...@india.einfochips.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Sudhakar,
Thanks a lot for your response.
I have tried as per your suggestion. Previously i was using 400 KHz as I2C
bus
frequency. Then i changed it to 100 KHz which is standard. But still i am
facing
the same problem.
It seems that when we try to access "TVP7002 HD Video Decoder" or "THS7353
Video
buffer", this problem occur.
I have attached the snap of the error for your reference.
Regards,
Dhaval Lakkad
> Dhaval,
>
> Try modifying the I2C bus frequency in the
drivers/i2c/busses/i2c-davinci.c file
> and see what happens.
>
> Regards, Sudhakar
> ________________________________________
> From: davinci-linux-open-source-boun...@linux.davincidsp.com
> [davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of
DHAVAL
> LAKKAD [dhaval.lak...@einfochips.com]
> Sent: Tuesday, January 20, 2009 6:37 PM
> To: davinci-linux-open-source@linux.davincidsp.com
> Subject: Davinci i2c warning : command completely failed
>
> Hi ,
>
> We are working on TI's DVEVM6467 processor. When we run any video
application
> (eg. Capture, Display or Loopback ) continuously for more than 6 to 7
times,
> then board gets hanged with the message "DaVinci I2C WARNING: i2c: cmd
complete
> failed: complete = 0x0, icstr = 0x410". After getting this problem we
have to
> just reboot the board. So can any one suggest the solution to resolve
this
> problem?
>
> Regards,
>
> Dhaval Lakkad
>
>
>
>
>
> --
> _____________________________________________________________________
> 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 otherwis
--
_____________________________________________________________________
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.
__________________________________________________________________________
-------------- next part --------------
r...@10.100.3.61:/opt/Codecs# ./CaptureEncode
DBG->videocapture_API.c:108: Evaluation version
DBG->videocapture_API.c:123: Memory is successfully allocated for params
structure
DBG->videocapture.c:364: /dev/DavinciHD_vdce device opened
DBG->videocapture.c:436: VDCE device closed successfuly
DaVinci I2C WARNING: i2c: cmd complete failed: complete = 0x0,
icstr = 0x410
DaVinci I2C WARNING: i2c: cmd complete failed: complete = 0x0,
icstr = 0x410
DaVinci I2C WARNING: i2c: cmd complete failed: complete = 0x0,
icstr = 0x410
DaVinci I2C WARNING: i2c: cmd complete failed: complete = 0x0,
icstr = 0x410
------------------------------
Message: 5
Date: Tue, 20 Jan 2009 23:33:30 +0900
From: kirthika varadarajan <kirthikai...@gmail.com>
Subject: Query reg generating an event in DM6467 for every 5 min
To: Davinci-linux-open-source@linux.davincidsp.com
Message-ID:
<13bd74410901200633w14d217c3wee764dfb1cac2...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
I am writing a simple application in which i need to generate an event for
every 5 min.
I just created a thread inside the thread i need to create an event for
every 5 min.
I refered to DM6467, there the timers are in kernel and i am not able to
link it in my application.
Suggest me how to generate events for every 5 min .
Regards
Kiruthika
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20090120/05dcf22a/attachment-0001.htm
------------------------------
Message: 6
Date: Tue, 20 Jan 2009 20:26:55 +0530
From: "Viraj Karandikar" <viraj.karandi...@ittiam.com>
Subject: disable linking xdc.runtime libraries
To: <davinci-linux-open-source@linux.davincidsp.com>
Message-ID:
<904dec693be1ab429622c6f5aba7e0b8057e3...@is01ex02.ittiam.com>
Content-Type: text/plain; charset="us-ascii"
Hi,
I am using TI XDC tools to build a archive instead of executable. I do
not want to link xdc.runtime libraries. But by default it gets linked
into the final archive.
Is there any way to disable this linking of xdc.runtime libraries?
Regards,
Viraj
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20090120/ede86a43/attachment.htm
------------------------------
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
End of Davinci-linux-open-source Digest, Vol 37, Issue 83
*********************************************************
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
