Brian,
There are several changes from DSPLink 1.3x to 1.6x.
Can you refer to the links at
http://processors.wiki.ti.com/index.php/Category:DSPLink
Specifically
http://processors.wiki.ti.com/index.php/Migrating_between_DSPLink_versions
In your email you have said that you have already looked
DSPLink expects the Linux kernel to be booted and available. To use any DSPLink
API’s the DSPLink kernel module needs to be “insmod”-ed.
You will have to write custom code to boot load the DSP from your ubl.
Deepali
From:
Yes,
Support for DM6446 with git kernel has been added in DSPLink release 1.65.00.02
available at
http://software-dl.ti.com/dsps/dsps_public_sw/DSPLink/1_65/index.html
Deepali
From: davinci-linux-open-source-bounces+deepali=ti@linux.davincidsp.com
Mike,
DSPLink does not use CMEM internally.
Deepali
-Original Message-
From: davinci-linux-open-source-bounces+deepali=ti@linux.davincidsp.com
[mailto:davinci-linux-open-source-bounces+deepali=ti@linux.davincidsp.com]
On Behalf Of Mike Williamson
Sent: Friday, May 28, 2010
Nick
For which use case do you require the DSP-ARM signal?
Are you using DSPLink? DSPLink which is IPC software primarily uses the
DSP-Arm and ARM-DSP interrupts for communication.
See further comments inline:
-Original Message-
From:
Hello,
Please check here:
http://wiki.davincidsp.com/index.php/DSPLink_FAQs#Why_does_the_MSGQ_get_API_call_in_my_application_crash.3F
Does this FAQ apply to your scenario?
Thanks and Regards,
Deepali Uppal
DSP/BIOS Link
From:
Vinayagam,
Please look through below link to understand changing memory map along with the
link.cmd changes that you have done.
http://wiki.davincidsp.com/index.php/Changing_the_DVEVM_memory_map
Thanks and Regards,
Deepali Uppal
DSP/BIOS Link
Platform Support Products
Arnaud,
The official DSPLink release supports Linux releases from Montavista and not
open source. However, there are multiple email resources available in order to
enable you to do a build. Kindly do a search on the list.
One relevant link:
RT,
You can download DSPLink from external web
http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/targetcontent/link/index.html
and use it.
FAQ's and other relevant How to material can be obtained from
http://wiki.davincidsp.com/index.php?title=Main_Page
The default support for DM6446
Jayakrishnan,
Please check this:
http://wiki.davincidsp.com/index.php/Troubleshooting_DSPLink_configuration_issues#Problem:_PROC_attach_failed_with_DSP_EALREADYCONNECTED_error
Thanks and Regards,
Deepali Uppal
DSP/BIOS Link
Platform Support Products
-Original Message-
From:
Caglar,
I need some more clarification before I can answer the questions that you have
asked.
1) Does your application ensure that all the DSPLink shut down API's like
MSGQ_close, POOL_close, etc are being called in the various components when you
stop your application?
2) Are you seeing
-Original Message-
From: Caglar Akyuz [mailto:caglarak...@gmail.com]
Sent: Thursday, September 24, 2009 12:09 PM
To: Uppal, Deepali
Cc: davinci-linux-open-sou...@linux.
Subject: Re: Dsplink Memory Leak Problem
On Thursday 24 September 2009 09:34:48 Uppal, Deepali wrote:
Caglar,
I need
Hello,
I do not know why the DSP is hanging.
But I can give an explanation for the crash dump seen after CTRL C.
DSPLink has a signal handler registered by default which clean up the DSPLink
driver when process termination signals are sent to any process/thread which is
using the driver on
...@gmail.com]
Sent: Wednesday, September 23, 2009 1:50 PM
To: Uppal, Deepali; 'davinci-linux-open-source@linux.davincidsp.com'
Subject: RE: DSP hang when run DVSDK Demo in DM6446
Hi Deepali Uppal:
You are right, each time when the DSP hanging, it run at:
@6,001,216us: [+0 T:0x41baf490 S:0x41baea84
Sameer,
This error is indicating patch has not been applied correctly.
Older support mails indicate this patch is for an older DVSDK version (1.00
series). Looking at the patch code, you should be able to patch the DSPLink
files manually.
Thanks and Regards,
Deepali Uppal
DSP/BIOS Link
To: Uppal, Deepali
Cc: davinci-linux-open-source@linux.davincidsp.com
Subject: Re: Compiling dsplink_140-05p1 for linux-davinci-2.6.23 kernel
That is exactly what i have done, i.e. applied the patches manually.
Attached are my patched files.
Regards
~Sameer
On Mon, Sep 21, 2009 at 3:14 PM, Uppal
-source@linux.davincidsp.com; Uppal, Deepali
Subject: RE: [DSPLINK on DM6467] with PREEMPT_RT mode on MVL Pro 4
Deepali,
Thank you for the suggested changes.
I am able to port the DSPLINK 1.6x for 2.6.10 RT kernel with the changes
you suggested. It is able to get insmoded into 2.6.10 RT kernel
@linux.davincidsp.com; Uppal, Deepali
Subject: RE: [DSPLINK on DM6467] with PREEMPT_RT mode on MVL Pro 4
Hi Deepali,
I tried merging the DSPLINK 1.6x into 2.6.10 kernel. But some of the
mutex functions and files are not present in the 2.6.10 kernel.
(Attached file gives the compilation errors, when I try
Santosh,
There isn't a DSPLink available with support for 2.6.10 kernel and real-time
kernel. Support for RT mode was added in DSPLink 1.6x, and in this version, MVL
Pro 4 support was removed. One thing that the you could try is to merge support
for 2.6.10 kernel into DSPLink 1.6x.
Thanks and
Yang,
Please check this FAQ on DSPLink wiki:
http://wiki.davincidsp.com/index.php/DSPLink_FAQs#Why_does_signal_handler_registered_in_my_application_stop_working_when_I_integrate_DSPLink_.3F
Thanks and Regards,
Deepali Uppal
DSP/BIOS Link
Platform Support Products
-Original Message-
Kirthika,
Can you check this link:
http://wiki.davincidsp.com/index.php/Changing_the_DVEVM_memory_map
Thanks and Regards,
Deepali Uppal
DSP/BIOS Link
Platform Support Products
From: davinci-linux-open-source-bounces+deepali=ti@linux.davincidsp.com
Hello,
Are you seeing type clash errors? You need to include xdc/std.h before DSPLink
headers to avoid type clash.
Also, you can edit file $dsplink\gpp\src\samples\readwrite\Linux\COMPONENT to
add your specific compiler flags, defines etc.
Thanks and Regards,
Deepali Uppal
DSP/BIOS Link
Matthias,
Codec Engine ships with the DATA i.e. CHNL component disabled.
Could there be a mismatch between the GPP and DSP components DSPLink
configuration?
You can also look at
http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_configuration_issues
for further pointers.
David,
Please can you look at the patch that Kevin Hilman had provided in the past and
see if
That helps.
http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg03002.html
Regards,
Deepali
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
Shivdas,
DSP/BIOS Link product provides DSP bootloading and data transfer services. It
is available standalone, as well as within Codec Engine. If used standalone,
you can choose one of the several data transfer protocols available between the
ARM DSP, depending on your specific needs.
The
Platform Support Products
[http://dbdwss01.india.ti.com/pspproducts/default.aspx]
-Original Message-
From: shivdas.gujare [mailto:[EMAIL PROTECTED]
Sent: Monday, June 23, 2008 4:18 PM
To: Uppal, Deepali
Cc: Davinci linux open source
Subject: RE: Needs reference to documents
Hi
Hello,
My answers inline.
Regards
Deepali
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of kashin Lin
Sent: Sunday, March 02, 2008 4:31 PM
To: davinci-linux-open-source@linux.davincidsp.com
Subject: DSPLink samples failure
Hi,
i try
RyanYee,
I can answer your question from the perspective of DSP/BIOS Link.
The loading of the DSP executable occurs when the GPP side application calls
the API PROC_load. When the GPP side application calls the API PROC_start, the
already loaded DSP/BIOS application starts up.
This triggers
Yan Ming,
Codec Engine is a codec execution framework that automates the
invocation and instantiation of eXpressDSP-compliant codecs and
algorithms. TI Codec Engine is provided as part of the TMS320DM644x
Digital Video Evaluation Module (DVEVM). Codec engine can execute in
ARM-only, ARM-DSP,
]
Sent: Wednesday, November 14, 2007 8:52 PM
To: Uppal, Deepali
Cc: Kamoolkar, Mugdha
Subject: Re: SV: turn on/off the DSP
Hi Deepali,
We have a very small DM6446 low power device (2 inches by 1/2 inch)
where the ARM needs to be running most of the time. My thought was to
turn off the DSP clock
Tim,
You can download the latest version of Link from
https://www-a.ti.com/downloads/sds_support/targetcontent/link/index.html
Regards,
Deepali
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: Thursday, November
Euan,
This message is just a warning and will not have any effect of
execution.
The warning is coming because DSP/BIOS Link does not use the kernel
build system and also it is not under the same license as the kernel
itself.
Regards,
Deepali
-Original Message-
From: [EMAIL PROTECTED]
Bernard,
LAD can be used to connect to start the DSP, but apart from that, you
can use DSPLINK standard APIs by making calls directly to DSPLINK
protocols.
MSGQ and other protocols can be used for inter-processor communication
via CE. Please look at the samples shipped with the Link release at
Jeremy,
Regarding issue 1:
This message is just a warning and will not have any effect of
execution.
The warning is coming because DSP/BIOS Link does not use the kernel
build system and also it is not under the same license as the kernel
itself.
Regards,
Deepali
-Original Message-
Hello,
The possible causes for PROC_start failure:
* DSP has not been loaded correctly, and hence is not executing
correctly to reach the point where the driver completes the handshake
between GPP and DSP for PROC_Start.
* There is a memory configuration mismatch in memory
35 matches
Mail list logo
