Symphony SoundBite Demo User’s Guide
10
Freescale
Semiconductor
Chapter 4
Building the Demonstration Application
The demonstration application source consists of a collection of assembly code and include files that are individually
assembled and then linked together into an executable object for the DSP. The detailed function of the code within the
source is beyond the scope of this document. For more information about the internal workings of the demonstration
application, please refer to Symphony SoundBite: Assembly Project Template document.
This chapter details the procedure to build the demonstration application from the source. Some working knowledge of
Symphony Studio is assumed.
4.1
Importing and Preparing the Project
The source of the demonstration application is included in the accompanying zip file archive within a compressed
workspace file (Symphony Studio can directly import the source project from the compressed archive). To import the
demonstration application source into a Symphony Studio project:
1)
Launch Symphony Studio.
2)
In the C/C++ perspective, right-click in the Projects pane (or use the File menu to select Import) and choose
Import.
3)
In the pop-up dialog box, select General > Existing Projects into Workspace. Click Next.
4)
Choose the Select archive file radio button, browse to the demonstration application workspace archive, and Open
it.
5)
Make sure that the check box next to the Symphony SoundBite board test project is checked.
6)
Check “Copy projects into workspace.”
7)
Click Finish.
8)
Right-click on the project and select Properties.
9)
Select C/C++ Build > Tool Settings.
10)
Select 56k ASM Assembler > Options. Verify that the Debug option is checked and that there is a “%” in the List
File field.
The checkbox tells the assembler to place symbolic information for debugging into the intermediate object files.
The “%” tells the assembler to generate a listing file for each input source file (the make file assembles each .asm
file separately and the %” is a placeholder for the filename being acted upon).
11)
Select 56k ASM Linker > Options. Verify that the Debug option is checked. In the Map File field, there should be
a filename “mapfile.txt,” which is what was used in the original project (although this name is arbitrary). The text
in the Memory Control File field should be “..\sb_boardtest_lnk.ctl,” which points to an existing file in the project
folder.
The checkbox directs the linker to include the symbolic debugging information in the object output file.
The map file name specifies the filename to use for saving the map file (which contains textual information about
the symbolics in the object file, where the labels are located and so on).