OMAPL138 Audio Soc Example

Christian,

Please refer to the dependencies for the demo in the release notes.

http://software-dl.ti.com/dsps/dsps_public_sw/apps_processors/Audio_soc_example/1_00/exports/audio_soc_ReleaseNotes.txt

From the linking error, it appears that you may not have your DSPLINK package built. The DVSDK which is the linux SDK for the OMAPL138 platform integrates all the needed components so it might be easier for you to build the example there.

Regards,

Rahul

Thank you Rahul,

now i have installed CCSv5 and i am wondering how i can import the audio soc example into the CCS.

In the OMAP-L138_EXP_User_Guide.pdf is described how to import GEL/BSL Files into CCS but the audio soc example isnt of that type.

Do you know how i can convert this?

edit: I followed the instructions on http://processors.wiki.ti.com/index.php/Debugging_the_DSP_side_of_a_DSPLink_application_on_OMAP-L138_using_CCS but when i try to load symbols (the audio_soc.out file) nothing happens, just a message occurs "No source available for 0x8000000", and the DSP still writes "no symbols defined at 0x8000000"

Have you any idea?

Best regards

Christian

any suggestions?

really, i need help in using the audio soc example with ccs5. There is still the "No source avaible for "0x80000000" " window and i dont know how i can load the symbols.

Hi Christian,

Sorry for the delayed response. The audio SoC needs to be built in the linux environment as its build has been setup for the make environment and not the CCS environment. This example is intagrated into the linux software development kit for the platform, which is a self contained packaged with integrated build environment(make based not CCS based). In order to build this demo follow the steps below :

1. Download DVSDK 4.03 from here on Ubuntu 10.04

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_4_00/latest/index_FDS.html

2. Disable ALSA driver from the kernel.

3. Build the linux kernel, DSPlink, CMEM  (instructions software developers guide in doc folder of SDK)

4. Build the Audio soc example and install binaries to filesystem.

5. Flash ubl and uboot on the platfrom. Run setup.sh from DVSDK to setup linux boot

6. To run the example look at the instructions in the software designers guide

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_4_00/latest/exports/OMAPL138_Software_Developers_Guide.pdf

Hope this helps

Regards,

Rahul

thank you for your reply.

all the steps you described i already made, but i do not want just to run the example, i want to debug it, so i can understand it. is there a way to do this in ccs?

When are you loading the symbols in CCS? You need to execute the ARM side App on the target first which will load the DSP application using DSPLINK . When the the code executes the while(i) statement, connect to DSP and load the symbols. If you have the source associated with it open in the editor you should be able to single strp through the code.

Let us know if you have any followup questions.

Regards,

Rahul

I have attached a screenshot of my environment and the failure i receive.

Following things i have done:

1) I logged into the experimenter Kit with Cutecom, a ssh terminal

2) I started the audio soc example with ./audioSoc_gpp audioSoc_dsp.out ../davincieffect_clip.pcm

3) I launched CCS and launched target configuration and then i connected to Target (error "C674X_0: Error connecting to the target: (Error -1180 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 5.0.747.0) " dissappeared after clicking several times on the retry button)

4) Loaded Symbols audio_soc_Example.out

5) see screenshot

What am i missing?

thanks, christian

edit: just for info, i used the correct settings described in the Software Developers Guide - Chapter Audio Soc Example, like booting from uImage_Soc without the Linux Audio Part. I am using VMware player with Xubuntu.

Christian,

It appears that you are using a GEL file when connecting to the device, please remove the GEL file as the device initialization has been done for you through the ubl and uboot code. The other thing you will need to figure out from the code is when the ARM application is bringing the DSP out of reset and loads the executable on it..If you find this, you can add a user input statement as demonstrated below:

http://processors.wiki.ti.com/index.php/Debugging_the_DSP_side_of_a_CE_application_using_CCS#Algorithm_Debugging

This will give you time to connect to the DSP and then load symbols and set break points before letting the rest of the application run.

Regards,

Rahul

Hy

I removed the Gel File via CCS after i booted the device. I hope this is correct. Also, i added the getchar() function to the line where the DSP application will be executed. After i pressed the button "Connect Target" and "Load Symbols" i was able to step trough the assembly code, but the c-Code was not there. How can i achieve this to step trough the c-Code?

regards christian

Hi Rahul

i am able to step trough the source code! I dont know how exactly i accomplished this, but one time i used the Load Program button instead of the Load Symbol and from now on i can see the source code.

The most important steps i think is to delete the GEL File which is created at every target configuration launch and then do the Load Symbols (!) after connecting to the target. Load Program must only be done once i think.

anyway thank you for your support!

regards christian