RE: CMEM/DSPLink and 2.6.28 kernel?

The wiki page below has been updated with patches/changes required (over DSPLink 1.6x) for building with 2.6.28 kernel http://tiexpressdsp.com/wiki/index.php?title=Building_DSPLink_with_kbuild Regards, Mugdha -Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com

RE: sample dsplink appl.

Ramesh, What bootargs are you using? Are you reserving memory from Linux for DSPLink shared memory using mem= command? http://tiexpressdsp.com/wiki/index.php?title=Changing_DSPLink_Memory_Map Regards, Mugdha From: davinci-linux-open-source-bounces+mugdha=ti

RE: Debugging Message.out sample application in DSP/BIOS Link

Suhas, There are a few ways: 1. On GPP-side, use trace to see what's happening. http://tiexpressdsp.com/wiki/index.php?title=Enabling_trace_in_DSPLink Here, since you know MSGQ_locate is stuck, that likely won't help. Is MSGQ_locate hung such that it exits with Ctrl C (i.e. pending on a semaphore

RE: Problem with decode demo application

Suhas, Please see here: http://tiexpressdsp.com/index.php?title=Troubleshooting_DSPLink_configuration_issues#Problem:_PROC_start_failed_with_configuration_mismatch.2Ffailure_showing_some_modules_with_0_and_others_with_0x Regards, Mugdha -Original Message- From: davinci-linux-op

RE: Problem with decode demo application

at both GPP-side and DSP-side are using the same configuration, otherwise there may be mismatches in shared memory, resulting in run-time issues. Regards, Mugdha -Original Message- From: suhas [mailto:suh...@aftek.com] Sent: Thursday, March 26, 2009 8:03 PM To: Kamoolkar, Mugdha; davinc

RE: moved on to a kernel cmem problem

Mat, We have verified DSPLink with 2.6.18+ versions (notably 2.6.22 and 2.6.23, and later even latest GIT versions). There is no issue of the sort that you have mentioned below. The folder says 2.6.18 because there's no difference as far as DSPLink is concerned between 2.6.18 and later versions

RE: DSPLINK: MSGQ_get() with WAIT_NONE arg causes freeze

Kelby, We found this issue recently, and it needs a fix in sync.c file. I will send it separately to you. Regards, Mugdha -Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Kelby

RE: Exact DSP on the OMAP3530

Hi, Please see here: http://wiki.davincidsp.com/index.php?title=Changing_DSPLink_Memory_Map At the bottom of the page, we mention that SPRU871.pdf (http://focus.ti.com/general/docs/techdocsabstract.tsp?abstractName=spru871) has the required MAR address ranges. Regards, Mugdha -Original M

RE: Exact DSP on the OMAP3530

/* SYNCD }, Which document tells me, that L1P RAM starts at 0x5cE0 or 0x10E0 respectively? Regards, Ingo Quoting "Kamoolkar, Mugdha" : > Hi, > > Please see here: > http://wiki.davincidsp.com/index.php?title=Changing_DSPLink_Memory_Map > > At the bottom of

RE: OMAP Intercore locking

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

RE: Engine Open() from multiple DLL/SO libraries same process

Steve, Check out: http://wiki.davincidsp.com/index.php?title=Codec_Engine_Roadmap This page mentions that CE 2.00 adds multi-process support. Regards, Mugdha From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve MacLean Sent: Saturday, April 26, 2

RE: How to debug dsp side program using CCS

Hi, It looks like you may not have created TCF configuration file for your program. You can refer to any DSP/BIOS example application for this (available within CCS). If you don't have TCF file, then you will not get any linker command file, which would otherwise have been generated by the TCON

Linux based tools for DSP-side build

Hi, There have been some questions in the past on this list about whether DSP-side development can be done on Linux. This is FYI for those who may not be aware ... DSP-side development tools are available on Windows (as part of CCS) and also on Linux (as standalone downloads). * DSP/BIOS: https

RE: LOOP sample in DSPLINK

Mike, LOOP is just a DSPLink sample application. It is self-contained and generates its own DSP executable that works alongwith the corresponding GPP-side LOOP application. Hence it needs to have its own configuration information. When you write your own application, you can simply use the DSPL

RE: why request_irq() return -16 on Davinci EVM?

Mike, This code is part of DSPLink isr.c. Are you trying to register an ISR for shared or non-shared interrupt? If you are registering for shared interrupt (such as PCI), you should use the SA_SHIRQ version, otherwise use 0. But the define for DM642_PCI is very DSPLink-specific, so you should r

RE: problem with memory map in dsplink_1_50

Can you check your DSP map file and see if anything in that map file falls outside the range: 0x87A0 to 0x87E0? Regards, Mugdha -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of SergA Sent: Monday, June 09, 2008 1:32 PM To: Ring, Chris Cc: davinc

RE: Failed while insert dsplinkk on EVM 1.30 release

Looks like the kernel version with which DSPLink was built in the evm_1_30 release does not match the version that you have on your target board. Can you check the documentation to ensure that you have the required matching kernel version? Regards, Mugdha -Original Message- From: [EMAI

RE: Failed while insert dsplinkk on EVM 1.30 release

EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 10:31 AM To: Kamoolkar, Mugdha Cc: davinci; [EMAIL PROTECTED] Subject: RE: Failed while insert dsplinkk on EVM 1.30 release Thanks for your reply. The kernel version in my board is 2.6.23. DSPLink built in evm_1_30 does not support for 2.6.23? I can not fin

RE: Failed while insert dsplinkk on EVM 1.30 release

0:51 AM To: Kamoolkar, Mugdha Cc: davinci; [EMAIL PROTECTED] Subject: RE: Failed while insert dsplinkk on EVM 1.30 release Yeah, it seems that new version of EVM does not recompile DSPLINK when try to compile whole EVM packages. Why not?Thanks. On Tue, 2008-06-10 at 10:44 +0530, Kamoolkar, Mugdha wrote:

RE: Failed while insert dsplinkk on EVM 1.30 release

had this working. Regards, Mugdha -Original Message- From: steven.zhang [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 1:07 PM To: Kamoolkar, Mugdha Cc: davinci; [EMAIL PROTECTED] Subject: RE: Failed while insert dsplinkk on EVM 1.30 release When I try to compile the dsplink, it

RE: Failed while insert dsplinkk on EVM 1.30 release

stead. Regards, Mugdha -Original Message- From: steven.zhang [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 1:52 PM To: Kamoolkar, Mugdha Cc: davinci; [EMAIL PROTECTED] Subject: RE: Failed while insert dsplinkk on EVM 1.30 release Thanks Mugdha. http://tiexpressdsp.com still can n

RE: Failed while insert dsplinkk on EVM 1.30 release

ne 10, 2008 2:20 PM To: Kamoolkar, Mugdha Cc: davinci; [EMAIL PROTECTED] Subject: RE: Failed while insert dsplinkk on EVM 1.30 release Thanks. Mugdha. I will try to remove the sys_open etc from DSPLINK_140-05PL by comparing DSPLINK_1_50. Regards, Steven On Tue, 2008-06-10 at 14:06 +0530, Kamo

RE: building dsplink

Brian, You may have an incompatible version of Linux kernel. DSPLink versions prior to DSPLink 1.50 did not inherently support linux kernel versions 2.6.18 onwards. If you need to build DSPLink on a linux kernel version 2.6.18+, you'll need to either: 1. Use DSPLink 1.50 (but note that you need

RE: building dsplink

rnel version has something different? Regards, Mugdha -Original Message- From: Brian Rhodes [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2008 12:32 PM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source@linux.davincidsp.com Subject: Re: building dsplink Thanks for responding. I am t

RE: Porting OpenCV to DM6446

Andre, Sorry to have missed your very first e-mail where you mentioned your issues with DSPLink POOL & CMEM; I look for DSPLink or similar in the title to see if I need to reply. :-) DSPLink does not use CMEM internally, it just uses the POOL module, which is independent and not based off CMEM.

RE: CERuntime_init/exit + threads

David, DSPLink installs a signal handler by default to cleanup its own resources. But you can disable it by updating in the DSPLink dynamic configuration file CFG_Linux.c. Set HANDLESIGNALS to FALSE. FALSE, /* HANDLESIGNALS : Should signals be handled for cleanup

RE: CERuntime_init/exit + threads

nt: Friday, July 25, 2008 12:17 PM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source@linux.davincidsp.com Subject: RE: CERuntime_init/exit + threads Mugdha, Thanks for the info... do I need to edit any code in the IPC also? I think a better policy would be to check the signalhandler_t val

RE: CERuntime_init/exit + threads

EMAIL PROTECTED] Sent: Friday, July 25, 2008 1:41 PM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source@linux.davincidsp.com Subject: RE: CERuntime_init/exit + threads Thanks again! I was looking that the sources for dsplink and noticed what think is a bug: dsplink/gpp/src/api/Linux/drv_api.c

RE: dsplink on Lyrtech SFF SDR board

Philip, Do you have a log without trace enabled? It's easier to see success/failure with that. In RingIO, the behavior is such that acquire failure is ok (it will then go and wait for buffer to be available). So the failure in the API doesn't necessarily mean failure in the test-case. For memo

RE: cannot run the decode demo on the 6446EVM

Panchy, Have you reserved the right amount of memory for DSP (and shared memory) in bootargs? Refer to: http://wiki.davincidsp.com/index.php?title=Changing_the_DVEVM_memory_map#Changing_the_boot_argument_in_your_Linux_bootloader Regards, Mugdha From: [EMAIL PROT

RE: Davinci-linux-open-source Digest, Vol 33, Issue 33

Deep, This can happen if you have not built the Linux kernel (LSP) before building DSPLink. Regards, Mugdha From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of deep bera Sent: Wednesday, September 10, 2008 4:08 PM To: davinci-linux-open-source@linux.

RE: readwrite sample

Nicolas, Please refer to: http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_build_issues#Problem:_Build_error_.22The_system_cannot_find_the_path_specified..22 Regards, Mugdha From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nicol

RE: Dsplink driver problem...?

John, This may be related to the following FAQ: http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_configuration_issues#Problem:_Getting_error_when_running_sample_applications_on_Linux Regards, Mugdha -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTE

RE: Expected DspLink Message Example Rates?

Brett, On DM6446 Linux release build, we have seen ~120 microseconds for a round-trip message: GPP->DSP->GPP. Note that this includes any context switching time on the Operating System. Our measurements are on a lightly loaded system, so you will likely see different numbers depending on the l

RE: To boot DSP and run DSP application from ARM.

Naveena, You can look into the hal (hardware abstraction layer) code within DSPLink sources as a reference for what you are attempting to do. It will have the right sequence of register settings. Regards, Mugdha From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED

RE: To boot DSP and run DSP application from ARM.

PROTECTED] Sent: Friday, September 26, 2008 12:50 PM To: Kamoolkar, Mugdha; davinci-linux-open-source@linux.davincidsp.com Subject: RE: To boot DSP and run DSP application from ARM. Thank you. If I am to use PROC section alone (to load and run)and no other communication mechanism (MSGQ, POOL ,CHL...), is

RE: To boot DSP and run DSP application from ARM.

: Kamoolkar, Mugdha; davinci-linux-open-source@linux.davincidsp.com Subject: RE: To boot DSP and run DSP application from ARM. So what is a possible way to run a non-DSPLink DSP executable from ARM? It will be more helpful if I get a sample program(firmware appln) or linux driver to do the same. Thanks

RE: writing compiling executing arm-dsp hello world program

Deepak, What error did you get while running? Have you looked at this to see if your error matches any of the ones listed here: http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_configuration_issues Regards, Mugdha From: [EMAIL PROTECTED] [ma

RE: writing compiling executing arm-dsp hello world program

You can rebuild DSP-side: http://tiexpressdsp.com/wiki/index.php?title=Building_DSPLink Regards, Mugdha From: Deepak Mundra [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 11:38 AM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source

RE: writing compiling executing arm-dsp hello world program

[mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 11:54 AM To: Kamoolkar, Mugdha Subject: Re: writing compiling executing arm-dsp hello world program Hi can you please tel me how to solve this problem? dsplinkk: no version for "struct_module" found: kernel tainted. dsplinkk: modu

RE: writing compiling executing arm-dsp hello world program

ds, Mugdha From: Deepak Mundra [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 12:31 PM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source@linux.davincidsp.com Subject: Re: writing compiling executing arm-dsp hello world program Hi this code is to print h

RE: writing compiling executing arm-dsp hello world program

undra [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 2:30 PM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source@linux.davincidsp.com Subject: Re: writing compiling executing arm-dsp hello world program Hi .. As mentioned in the site .. i compiled both dsp and gpp side .. and copied

RE: writing compiling executing arm-dsp hello world program

PROTECTED] Sent: Tuesday, October 21, 2008 3:57 PM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source@linux.davincidsp.com Subject: Re: writing compiling executing arm-dsp hello world program Hi thanks for the reply enabled only proc and in hello.c file i have set #define NUM_ARGS 0 and using in

RE: writing compiling executing arm-dsp hello world program

, Mugdha From: Deepak Mundra [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2008 7:47 PM To: Kamoolkar, Mugdha Subject: Re: writing compiling executing arm-dsp hello world program Hi Mugdha, I am trying to implement or run blit function on dsp (provided by

RE: basic question(s)...

To add to that, all tools you need for building DSP-side are available standalone as well (outside of CCS): Target Content: https://www-a.ti.com/downloads/sds_support/targetcontent/index.html CodeGen tools: https://www-a.ti.com/downloads/sds_support/CodeGenerationTools.htm Generally good to loo

RE: writing compiling executing arm-dsp hello world program

ation is used. This release will be available very soon (before the end of this month). Regards, Mugdha From: Deepak Mundra [mailto:[EMAIL PROTECTED] Sent: Thursday, October 23, 2008 5:08 PM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source@linux.davincids

RE: writing compiling executing arm-dsp hello world program

Can you also disable PROBE and try once more? PROBE is not supported anymore, and we have even removed it from the configurations in recent releases. Regards, Mugdha From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kamoolkar, Mugdha Sent: Thursday

RE: Encodedecode: Failed to open codec engine

Jose, The error prints that you got in debug build are from DSPLink. For example, look at the first error: Failure: Status:[0x80008008] File:[0x50c] Line:[216] Look at the following wiki page for an interpretation of this: http://tiexpressdsp.com/wiki/index.php?title=Debugging_DSPLink_using_SET_

RE: Encodedecode: Failed to open codec engine

ake sense to you? Is a goog idea to recompile dsplink introducing more traces? dsplink and cmem modules appear when I lsmod in the target. And you're right, my dsplink version is 1.30.08.02. Thanks and regards, Jose. -- RE: Encodedecode: Failed to open codec engine

RE: Encodedecode: Failed to open codec engine

0 and rebuilt dsplink, and still the same error. I'm thinking about reinstall everything or upgrade dsplink to 1.40... I keep on searching... Thanks. Jose -- RE: Encodedecode: Failed to open codec engine Kamoolkar, Mugdha Mon, 03 Nov 2008 20:13:49 -0800 Jose, I recall

RE: LSP 01.20.00.014 compatibility issue

Hi, With DSPLink, you would have got a warning (not error) about version of struct_module not found. That can be ignored. You will need to rebuild cmem on your kernel to remove the struct_module error. Regards, Mugdha From: [EMAIL PROTECTED] [mailto:[EMAIL PROT

RE: To boot DSP and run DSP application from ARM.

] [mailto:[EMAIL PROTECTED] On Behalf Of Kamoolkar, Mugdha Sent: Friday, September 26, 2008 3:48 PM To: Naveena M.; davinci-linux-open-source@linux.davincidsp.com Subject: RE: To boot DSP and run DSP application from ARM. Naveena, There is nothing of that sort currently available (as far as I know). You

RE: DSP-side configuration mismatch/failure

Craig, On DM6467, if this happens intermittently, then it is likely to be the known issue we have documented in the Release Notes for this platform. We have seen that if the DSP is reset/released very fast, then this problem is seen. We have not been able to root-cause it so far, so we release

RE: DSP-side configuration mismatch/failure (Help!)

Sameer, Please look here: http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_configuration_issues Regards, Mugdha From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sameer Naik Sent: Sunday, December 07, 2008 9:55 PM To: davinci-lin

RE: DSP-side configuration mismatch/failure (Help!)

Sameer, This wouldn't be the same issue ... this is relevant only for DM6467. We have never seen this with DM6446. Regards, Mugdha From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sameer Naik Sent: Sunday, December 07, 2008 10:06 PM To: davinci-li

RE: Build dsplinkk.ko

Andre, Can you try a VERBOSE build and check if you get any pointers: http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_build_issues#Problem:_Build_fails._Paths_are_set_correctly By the way, using 1.60 is probably the best option. 1.30.08 did not support 2.6.18+ kernels, so yo

RE: Changing the default memory map on DM6446

Hi, Have you done this: * Ensure that the RESETVECTOR field in LINKCFG_dspObjects structure is also changed to point to the right place. STATIC CONST LINKCFG_Dsp LINKCFG_dspObjects [] = { { ... 0x8410,/* RESETVECTOR: Reset Vector for the DSP */

RE: dsplink and cmem

Hi, DSPLink is available for free download at: https://www-a.ti.com/downloads/sds_support/targetcontent/link/index.html Latest versions (1.50 onwards) support 2.6.18+ kernels. I would advise using DSPLink 1.60, which is the latest release available. You can look here for version compatibility

RE: starting DSP server './decodeCombo.x64P' FAILED

DSPLink 1.60 (available here: https://www-a.ti.com/downloads/sds_support/targetcontent/link/index.html) fixes this defect: SDOCM00036048: DSP executable load fails when a yaffs2 file system is used Description: If any Linux file system does not implement some operations as members of file_opera

RE: SFFSDR DSPLink Hello world

Alden, Which version of DSPLink are you using? The DSPLink build mechanism does not use CCS, but that does not mean that the IDE cannot be used for debugging purposes.That's still possible to do by loading symbols on the DSP-side CCS once you connect CCS to the DSP after it's running. I would

RE: starting DSP server './decodeCombo.x64P' FAILED

PM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source@linux.davincidsp.com Subject: Re: starting DSP server './decodeCombo.x64P' FAILED HI! Thanks for the inputs.Bringing the fix from 1.60 to 1.50 worked for us. Is there a list of constraints or bugs related to all these software modules i

RE: SFFSDR DSPLink Hello world

nesday, January 07, 2009 8:35 PM To: Kamoolkar, Mugdha; davinci-linux-open-source@linux.davincidsp.com Cc: 'shehr...@gmail.com'; Abhijit Navalekar; John Roberts Subject: RE: SFFSDR DSPLink Hello world Hi Mugdha Thank you, for the response, I will have John look into the build to see if he use

RE: dsplink and cmem

David Brownell [mailto:davi...@pacbell.net] Sent: Tuesday, January 06, 2009 4:00 PM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source@linux.davincidsp.com; Liu Hua Subject: Re: dsplink and cmem On Monday 05 January 2009, Kamoolkar, Mugdha wrote: > DSPLink is available for free download at: >

RE: dsplink and cmem

ll [mailto:davi...@pacbell.net] Sent: Tuesday, January 13, 2009 4:20 AM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source@linux.davincidsp.com; Liu Hua Subject: Re: dsplink and cmem On Thursday 08 January 2009, Kamoolkar, Mugdha wrote: > However, in the current DSPLink 1.xx versions, we are not

RE: Mixing DSP/BIOS Link and Codec Engine

Bernard, The issue with MSGQ_transportOpen that you are facing is likely because Codec Engine already opens it for you. So you cannot open it again (you are getting DSP_EACCSESDENIED error). However, since CE has already opened it, you can directly use the MSGQ module from your application for usi

RE: regarding dsplink modules

Ashok, DSP/BIOS LINK does not support real-time preemption mode. Can you confirm that your kernel configuration is correct? In future releases, we will be supporting later versions of Linux (than the current 2.6.10), so users will find it easier to use without applying Kevin's patch. Till then, I

RE: building dsplink problem with GIT 2.6.23 kernel

Hi, For now, please try instructions at: http://www.mail-archive.com/[EMAIL PROTECTED] om/msg03002.html Future releases of DSP/BIOS LINK will support kernel versions 2.6.18 and higher. Regards, Mugdha -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of JAEH

RE: DSPLINK building problems with GIT 2.6.23 kernel

Hi, We saw something else on 2.6.18+ kernel versions, related to the modpost utility not including the required header files into the generated .c file. That is likely the cause of the problem you are seeing. To workaround this issue, can you try the following: In file /dsplink/make/Linux/Davinc

RE: Need Materials for "Multi-core data/information exchange methods"

Ujjal, The DSP/BIOS(tm) LINK software available for TI multi-core processors including DM6446 is available for download at: https://www-a.ti.com/downloads/sds_support/targetcontent/link/index.html This software provides different mechanisms for inter-processor communication between the ARM

RE: How to use DSPLink

Gajendra, You can develop and build DSP applications on Montavista Linux and communicate between the ARM and DSP using DSP/BIOS LINK product available for DM6446. For developing applications on DSP, you can refer to the DSP/BIOS documentation. DSP/BIOS is available as part of CCS, and also availa

RE: DSP link license

Philip, I am also not a lawyer, but to my limited understanding, the license mainly says: 1. Do not use this, or attempt to port this software to any non-TI chip. It must be used only on TI hardware. 2. Do not use this software for assisting in design, development or verification of a non-TI devic

RE: IPS name error

Josh, Within DSP/BIOS LINK, the issue is in the configuration file (CFG_Davinci.c). The IPS name is the following: "IPS" in the below ... /** * @name LINKCFG_ipsTable_00 * * @desc IPS table ID 0. * =

RE: simple data exchange between ARM and DSP

Robert, DSP/BIOS Link product may be useful for you. It is intended for exactly this purpose, and 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

RE: simple data exchange between ARM and DSP

d DSP Am Wed, 6 Feb 2008 16:04:00 +0530 schrieb Kamoolkar, Mugdha: > Robert, > > DSP/BIOS Link product may be useful for you. Thank you for the hint! I am just try to compile the samples. But cc does not find 'std.h' (but it is in the include-folder: -I/opt/ti-tools/bios/pack

RE: simple data exchange between ARM and DSP

W. Kuhn Sent: Wednesday, February 06, 2008 7:36 PM To: davinci-linux-open-source@linux.davincidsp.com Subject: Re: simple data exchange between ARM and DSP Am Wed, 6 Feb 2008 17:53:29 +0530 schrieb Kamoolkar, Mugdha: > Also, 1.30 is a very old release. I just downloaded the newest version 1

RE: simple data exchange between ARM and DSP

Robert, It appears that you are using mvcyg4.0 on Windows. We have seen issues when attempting to build DSP-side code using TI tools from mvcyg4.0. The TI tools (CGTOOLS) for Windows were not taking in the forward slashes correctly. Have you installed the Linux version or the CCS version of CGTOOL

RE: simple data exchange between ARM and DSP

schrieb Kamoolkar, Mugdha: > For DSP-side on a Windows PC, can you try to build using a dos shell > instead? Choose Windows-based distribution for DSP-side build when > running the dsplinkcfg script, and build DSP-side separately from dos > shell. I am just doing it. I installed perl in

RE: simple data exchange between ARM and DSP

ary 07, 2008 5:41 PM To: davinci-linux-open-source@linux.davincidsp.com Subject: Re: simple data exchange between ARM and DSP Am Thu, 7 Feb 2008 16:43:10 +0530 schrieb Kamoolkar, Mugdha: > Please remove cygwin from the path for dos shell usage, otherwise it > interferes with the directory

RE: simple data exchange between ARM and DSP

pen-source@linux.davincidsp.com Subject: Re: simple data exchange between ARM and DSP Am Thu, 7 Feb 2008 23:06:50 +0530 schrieb Kamoolkar, Mugdha: > file: \dsplink\make\DspBios\c64xxp_5.xx_windows.mk > BASE_INSTALL:= C:\ti-tools > BASE_SABIOS := $(BASE_INSTALL)\bios > BASE_CGTOOLS:=

RE: simple data exchange between ARM and DSP

ARM and DSP Am Fri, 8 Feb 2008 13:14:49 +0530 schrieb Kamoolkar, Mugdha: > - Use mvcyg4.0 shell to build GPP-side. Thank you for your summary. I do have (I hope only simple) problems with the gpp-side. I compiled dsplink_1_50 (with the recent bios_5_32_01) and it works. So I got the necess

RE: simple data exchange between ARM and DSP

PM To: davinci-linux-open-source@linux.davincidsp.com Subject: Re: simple data exchange between ARM and DSP Am Fri, 8 Feb 2008 13:53:49 +0530 schrieb Kamoolkar, Mugdha: > Is your LSP built for Davinci? Basically, are all the soft links in > place for the davinci config? Do you mean: /

RE: simple data exchange between ARM and DSP

No ... You can't just make soft links this way. You can refer to the InstallGuide_Davinci.pdf in the DSPLink package for instructions on building the kernel for Davinci. Regards, Mugdha -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] .com] On Behalf Of Robert W. Kuhn

RE: Building DSP link with DaVinci git kernel, was:DaVinci git kernel

Troy, Dirk, DSPLink v1.50 fixes most of the issues with running on 2.6.18+ kernel versions, since it supports 2.6.18 kernel. It is still not GPL, and we are trying to sort out issues towards getting it done in future releases. Regards, Mugdha -Original Message- From: [EMAIL PROTECTED] [

RE: dsp-link - readwrite-example: DSP address>

Robert, Please refer to the InstallGuide_Davinci.pdf for platform-specific instructions on running the sample applications. This is especially applicable for readwrite sample, because the memory addresses will differ for different platforms. The instructions apply to the default memory configurati

RE: dsp-link - readwrite-example: DSP address>

-open-source@linux.davincidsp.com Subject: Re: dsp-link - readwrite-example: DSP address> Am Mon, 11 Feb 2008 18:56:38 +0530 schrieb Kamoolkar, Mugdha: > Please refer to the InstallGuide_Davinci.pdf for platform-specific > instructions on running the sample applications. > This is especi

RE: dsp-link - readwrite-example: DSP address>

Robert, The issue seems to be here: 1048577 = 0x11 ./readwritegpp readwrite.out 2409627648 1048577 1 The readwrite sample internally does the following: Passed address is used for write (ARM->DSP): 2409627648 = 0x8FA0 For read (DSP->ARM), the address used is: (Write address + buffer size)

RE: Porting dsplink_1_30_08_02

SARA, The problem indicates that data transfer is not working. If you are porting to a different shared memory platform and DSP has started correctly, it's most likely that your ported code for sending & receiving interrupts between the GPP & DSP is not correct, and interrupts are not being sent

RE: DSP-Heap

Robert, You will need to go through DSP/BIOS documentation for DSP-side to create a heap on DSP-side. It cannot be done as part of DSPLink. It needs to be done in DSP-side TCF file. There is a field called createHeap, which you need to set to TRUE and specify the size. E.g., in default DSPLink con

RE: DSP-Heap

rieb Kamoolkar, Mugdha: > You will need to go through DSP/BIOS documentation for DSP-side to > create a heap on DSP-side. It cannot be done as part of DSPLink. I thought this is done through a run of gmake. "gmake" is making a BIOS from the entries of readwrite.tcf in the DspBios\Davin

RE: building dsplink with non-Montavista toolchain

Kai, We have verified DSPLink with upto 2.6.22 kernel. In our internal development for this since 1.50, we have made the following changes: /dsplink/gpp/src/osal/Linux/prcs.c: Add #include /dsplink/gpp/src/osal/Linux/2.6.18/mem.c: Add #include /dsplink/gpp/src/osal/Linux/2.6.18/isr.c Change:

RE: DSP-Heap

Robert W. Kuhn Sent: Friday, February 15, 2008 12:34 PM To: davinci-linux-open-source@linux.davincidsp.com Subject: Re: DSP-Heap Am Thu, 14 Feb 2008 20:51:20 +0530 schrieb Kamoolkar, Mugdha: > Yes, I meant that you need to refer to DSP/BIOS documentation on how > to create heaps (syntax) withi

RE: DSP-Heap

1:58 +0530 schrieb Kamoolkar, Mugdha: > For example: > Assume that you have 256 MB on your board. You want to split this as: > > ARM: 64MB (400), > DSP: 192MB (C00) > > Now, you do the following: > 1. Specify mem=64M on your Linux bootargs. This means you are sayi

RE: a quesion about using dsp/bios link

Kashin lin, I assume you are trying to communicate between ARM & DSP using DSPLink. You can refer to sample applications provided with the DSPLink release as a reference for how the APIs can be used. The sample applications are available within the /dsplink/gpp/src/samples and /dsplink/dsp/src/sa

RE: error duning building dsp/bios link

Can you build with VERBOSE=1 gmake debug VERBOSE=1 With this, you will get prints of all the commands during make, and will know exactly which one is failing. Regards, Mugdha From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of kashin Lin Sent: Mon

RE: a quesion about using dsp/bios link

s, Mugdha From: kashin Lin [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 9:50 PM To: Kamoolkar, Mugdha Cc: davinci-linux-open-source@linux.davincidsp.com Subject: Re: a quesion about using dsp/bios link Hi, thanks for your reply. i still have some ques

RE: help

Siva, Please make sure you have followed all instructions for creating a different memory map as described in: http://www.mail-archive.com/[EMAIL PROTECTED] om/msg04442.html and http://www.mail-archive.com/[EMAIL PROTECTED] om/msg0

RE: dsplink_1_40_05: sample application failed

Saravanan, At what point do you get segmentation fault? Basically what do you see on the console prints before the fault? Can you also share the segmentation fault dump (if any)? We have verified with uclibc to some extent in earlier releases (more in later releases). Regards, Mugdha __

RE: help with DSPLink

)" always be 0 (can JTAG debug interrupt?) (kashin Lin) 2. RE: DM355 FB DLCD Chroma Pins Are Not Active? ([EMAIL PROTECTED]) 3. how to assigned an ISR to a interrupt in DSP/BIOS? (kashin Lin) 4. RE: help (Kamoolkar, Mugdha) ---

RE: DSPLINK: Change output dir of build process

Robert, Currently this is not configurable. The binaries are automatically generated in: $(DSPLINK)/dsp/export/BIN/$(DSPOS)/$(PLATFORM)/$(VARIANT)/[DEBUG | RELEASE] This is to ensure generic make-system for different platforms & builds. What exactly are you looking for? Regards, Mugdha -O

RE: DSPLINK: Change output dir of build process

t: Re: DSPLINK: Change output dir of build process Am Fri, 22 Feb 2008 12:15:26 +0530 schrieb Kamoolkar, Mugdha: > Currently this is not configurable. The binaries are automatically > generated in: > $(DSPLINK)/dsp/export/BIN/$(DSPOS)/$(PLATFORM)/$(VARIANT)/[DEBUG | > RELEASE] >

  1   2   >