This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

ARM-DSP Bridge

I am writing a new application using the DSP side of the DM6446 processor and was hoping to get some help as to where to start.  I am going to write a test app on the DVEVM board with a DM6446 processor to start with to make it easy and then I will transfer the code to our custom board.  Can anyone help point me in the right direction to get started?  I would like to run a very simple application on the DSP using the ARM.  I'd like to make use of the DSPLINK stuff (if possible) and CMEM.

Thanks,

Brian

  • Brian,

    Do you want to bypass (not use) the codec engine framework?  We have examples with source code under DVSDK codec engine directory that show you how to write your DSP algorithm, build a DSP server, and have an ARM side application use this server; of course, these examples use codec engine framework. 

  • I suppose that would be fine.  I don't know much about codec engine framework.  We are trying to port some existing fixed point code to the DSP, so perhaps this is the way to go.

  • codec engine framework also provides a way for DSP algorithms written by different third parties to work well together.  There is documentation included in the DVSDK under codec engine directory which should help you get familiar with codec engine.

  • For the DM6446 DVEVM, which tools do I use for the linux platform to compile the dsp software?  I went on the upgrade advisor on my code composer 3.3 tool and thought it was the c54x+, but then I don't see that option when trying to compile the dsp software.  I'd appreciate any help I could get with this.

    Thanks.

  • There are basically three software components that need building (dsp algorithm(s), dsp server, linux application).  You could build all of them in Linux host as the codec engine examples included in the DVSDK show and I would argue that this is probrably the preferred method; the DSP toolchain (compiler, linker...) are installed as part of DVSDK per Getting Started Guide.

    That said, bulding DSP software on windows via CCS, although possible can become quite complex; you see there are many header files (e.g. codec engine, xdm, xdais...) that may not be present on CCS enviroment; sometimes an incompatible version is present; this means you will need to read dsp algorithm release notes and make sure you download all necessary software components via update advisor and setup necessary paths and or environment variables, config files... Whereas an official DVSDK release makes sure you have all compatible versions of software components present.