Motorola DSP56602 Manuel d'utilisateur

DSPS56TOOLSUM/DDocument Rev. 1.0, 07/1999Suite56™ DSP ToolsUser’s Manual, Release 6.3

x Suite56 DSP Tools User’s Manual Motorola

Motorola About this Book xiAbout this BookThis manual is aguide toMotorola code-development tools, such assimulators of digitalsignalprocessors,hardwa

xii DSP Tools User’s Manual MotorolaWe also assume that you are fluent in the programming language—whether C orassembly language—for your project, and

Motorola About this Book xiiiConventionsThis manual uses the following notation conventions:• Courier monospaced type indicates commands,command param

xiv DSP Tools User’s Manual MotorolaGSM global system for mobile communicationGUI graphic user interfaceIIR infinite impulse response (a type of filte

Motorola Selecting Tools 1-1Chapter 1Selecting ToolsThis chapter explains which Motorola Suite56 tools will enable you to accomplish whichtasks; it de

1-2 Suite56 DSP Tools User’s Manual MotorolaCompilers1.1 CompilersMotorola recommends purchase of the Tasking C compiler for the DSP56300 andDSP56600

AssemblersMotorola Selecting Tools 1-3This option to link explicitly is obviously a good choice under several different conditions:• if your project c

1-4 Suite56 DSP Tools User’s Manual MotorolaLinkersFigure 1-3. Input and Output of the Assembler1.3 LinkersA linker combines relocatable object files

LinkersMotorola Selecting Tools 1-5You can control the Suite56 linker by means of command files. With the option -f, youcan control the linker through

Suite56, OnCe, and MFAX are trademarks of Motorola, Inc.Motorola reserves the right to make changes without further notice to any products herein. Mot

1-6 Suite56 DSP Tools User’s Manual MotorolaSimulators1.4 SimulatorsA Suite56 simulator is a software implementation of a hardware device, such as a d

SimulatorsMotorola Selecting Tools 1-71.4.1 Data Streams and the SimulatorA simulator is also a reasonable choice when you frequently have to download

1-8 Suite56 DSP Tools User’s Manual MotorolaSimulators1.4.2 User Interfaces to the SimulatorThe Suite56 simulator offers a graphic user interface with

SimulatorsMotorola Selecting Tools 1-9The Motorola DSP Simulator Reference Manual documents options available for bothinterfaces of the simulator. In

1-10 Suite56 DSP Tools User’s Manual MotorolaHardware Debugger: ADSFigure 1-7. Text-Based Interface of the Simulator1.5 Hardware Debugger: ADSLike a s

Hardware Debugger: ADSMotorola Selecting Tools 1-11Figure 1-8. Parts of the Hardware Debugger (ADS)Motorola DSP37-pinhost-businterface cardhost comput

1-12 Suite56 DSP Tools User’s Manual MotorolaHardware Debugger: ADS1.5.1 User Interfaces to the DebuggerThe Suite56 debugger offers a graphic user int

Hardware Debugger: ADSMotorola Selecting Tools 1-13Figure 1-9. Graphic User Interface of the Hardware DebuggerIn the text-based, command-line interfac

1-14 Suite56 DSP Tools User’s Manual MotorolaHardware Debugger: ADS

Motorola Testing Your Hardware Installation 2-1Chapter 2Testing Your Hardware InstallationThe manual for each Motorola Suite56 tool (such as a compile

Motorola Table of Contents iiiTable of ContentsAbout this BookAudience ... xiPrerequisites...

2-2 Suite56 DSP Tools User’s Manual MotorolaFigure 2-1. Setting up a Suite56 ADS with its ADMMotorola DSP37-pinhost-businterface cardhost computercomm

Testing Your Installation of the Command ConverterMotorola Testing Your Hardware Installation 2-32.1 Testing Your Installation of the Command Converte

2-4 Suite56 DSP Tools User’s Manual MotorolaTesting Your Installation of the Command Converter2.1.2 Testing through the Command-Line InterfaceIf you p

Testing a Low-Frequency Target DeviceMotorola Testing Your Hardware Installation 2-52.2 Testing Your Installation of a Target BoardIf you have success

2-6 Suite56 DSP Tools User’s Manual MotorolaChoosing a Connector for the EVM Power Supply2.4 Choosing a Connector for the EVM Power SupplyMost Suite56

Motorola Debugging C and Assembly Code 3-1Chapter 3Debugging C and Assembly CodeThis chapter walks you through sample programs in both C and assembly

3-2 Suite56 DSP Tools User’s Manual MotorolaInitializing a Debugging Environment3.1.2 Defining Paths and Working DirectoriesA Suite56 tool, by default

Initializing a Debugging EnvironmentMotorola Debugging C and Assembly Code 3-3Anytime you want to repeat that sequence of logged commands, from the Fi

3-4 Suite56 DSP Tools User’s Manual MotorolaInitializing a Debugging Environment3.1.5 Setting the RadixWhether you are using the graphic user interfac

Source-Level Debugging in CMotorola Debugging C and Assembly Code 3-53.1.7 Displaying MemoryTo display blocks of memory in the graphic user interface,

iv Suite56 DSP Tools User’s Manual MotorolaChapter 3Debugging C and Assembly Code3.1 Initializing a Debugging Environment ...

3-6 Suite56 DSP Tools User’s Manual MotorolaSource-Level Debugging in C3.2.1 Compiling to DebugWhen you are preparing to debug a C program with Suite5

Source-Level Debugging in CMotorola Debugging C and Assembly Code 3-7Example 3 -2. A Sample C Program: ltp.cint signal_lin[40], signal_dpri[120], nc;v

3-8 Suite56 DSP Tools User’s Manual MotorolaSource-Level Debugging in C3.2.2 About Software Breakpoints in a C ProgramThis section discusses software

Source-Level Debugging in CMotorola Debugging C and Assembly Code 3-93.2.3 Setting Software Breakpoints in a C ProgramThe following procedure details

3-10 Suite56 DSP Tools User’s Manual MotorolaSource-Level Debugging in C3. Under Count secify how many times the Debugger should encounter thebreakpoi

Source-Level Debugging in CMotorola Debugging C and Assembly Code 3-119. If the action specified is to execute a command, under Command type theDebugg

3-12 Suite56 DSP Tools User’s Manual MotorolaSource-Level Debugging in C3. Click OK.The breakpoints you selected are now deleted.Breakpoints will not

Source-Level Debugging in CMotorola Debugging C and Assembly Code 3-133.2.6 To Set a Hardware Breakpoint1. From the Execute menu, choose Breakpoints,

3-14 Suite56 DSP Tools User’s Manual MotorolaSource-Level Debugging in C5. Under Option, indicate whether a second condition should be considered. And

Source-Level Debugging in CMotorola Debugging C and Assembly Code 3-153.2.7 To Clear a Hardware Breakpoint1. From the Execute menu, choose Breakpoints

Motorola Table of Contents vChapter 4Tips about Special Projects4.1 Managing Projects with Multiple Devices . ... 4-14.1.1 Co

3-16 Suite56 DSP Tools User’s Manual MotorolaSource-Level Debugging in CIn the text-based interface, to define a watch list, use the watch command, as

Source-Level Debugging in CMotorola Debugging C and Assembly Code 3-173.2.10 Casting in a C ProgramSuite56 tools support these kinds of casts for both

3-18 Suite56 DSP Tools User’s Manual MotorolaSource-Level Debugging in CThese are the C-specific debugging commands:•down moves down the C function ca

Symbolic Debugging in Assembly CodeMotorola Debugging C and Assembly Code 3-19again and choose Close. A dialogue box opens for you to indicate that yo

3-20 Suite56 DSP Tools User’s Manual MotorolaSymbolic Debugging in Assembly CodeExample 3 -5. A Finite Impulse Response Filter in Assembly Code: fir.a

Symbolic Debugging in Assembly CodeMotorola Debugging C and Assembly Code 3-21rep #data_pointsmove x0,x:(r6)+ ;clear data points.loopdo #data_points,e

3-22 Suite56 DSP Tools User’s Manual MotorolaSymbolic Debugging in Assembly Code3.3.1 Setting Breakpoints in Assembly CodeThis section discusses softw

Symbolic Debugging in Assembly CodeMotorola Debugging C and Assembly Code 3-23To disable a breakpoint, in the graphic user interface, double-click on

3-24 Suite56 DSP Tools User’s Manual MotorolaCalling Assembly Code from C Code3.4 Calling Assembly Code from C CodeC compilers—whether distributed by

Exploiting Memory Control FilesMotorola Debugging C and Assembly Code 3-25Example 3 -8. An Assembly Routine Called by a C Programsection norm_routine_

vi Suite56 DSP Tools User’s Manual Motorola

3-26 Suite56 DSP Tools User’s Manual MotorolaExploiting Memory Control FilesExample 3 -11. Assembling Two Relocatable Object Files> asm56300 -b sec

Exploiting Memory Control FilesMotorola Debugging C and Assembly Code 3-27Example 3 -14. A Memory Map File: out.mapMotorola DSP Linker Version 6.2.1 9

3-28 Suite56 DSP Tools User’s Manual MotorolaExploiting Memory Control Files

Motorola Tips about Special Projects 4-1Chapter 4Tips about Special ProjectsThe tips about special projects in this chapter were collected from Motoro

4-2 Suite56 DSP Tools User’s Manual MotorolaManaging Projects with Multiple DevicesIn contrast, if all the digital signal processors in your project h

Managing Projects with Multiple DevicesMotorola Tips about Special Projects 4-3As long as a simulated device is configured ON, it is active during exe

4-4 Suite56 DSP Tools User’s Manual MotorolaDeveloping Real-Time Applications4.1.3 Simulating Communication between Multiple DevicesUse simulated inpu

Developing Real-Time ApplicationsMotorola Tips about Special Projects 4-5To apply a pin file, in the File menu, choose Input,andthenselect Open. A dia

4-6 Suite56 DSP Tools User’s Manual MotorolaDeveloping Real-Time Applications4.2.3 Generating Output with Time-Critical InformationSimulated output ca

Finding Well Hidden BugsMotorola Tips about Special Projects 4-74. Tie the output of the second device to the SSI input pin of the first simulateddevi

Motorola List of Figures vii1-1 Simple Code Development Cycle:Compile,Link,ExecutetoDebug... 1-11-2 Compiling by Default or with

4-8 Suite56 DSP Tools User’s Manual MotorolaFinding Well Hidden BugsTo set a breakpoint on an address in memory, follow these steps:1. Set the default

Finding Well Hidden BugsMotorola Tips about Special Projects 4-9Figure 4-3. Dialogue Box to Set a Breakpoint in Memory4.3.2 Setting Breakpoints on Reg

4-10 Suite56 DSP Tools User’s Manual MotorolaFinding Well Hidden Bugs

Motorola Answers to Frequently Asked Questions 5-1Chapter 5Answers to Frequently AskedQuestionsThe answers to frequently asked questions that appear i

5-2 Suite56 DSP Tools User’s Manual MotorolaI’m tired of initializing my development environment every time I start work. Is there any way to save my•

I’m having trouble debugging at low frequencies.Motorola Answers to Frequently Asked Questions 5-3You can create a startup.cmd file either by logging

5-4 Suite56 DSP Tools User’s Manual MotorolaHow do I halt in mid-cycle in a Suite56 simulator?Example 5 -1. Setting Low Frequencies in Suite56 Tools&g

How do I plot memory use?Motorola Answers to Frequently Asked Questions 5-55.7 Can I link my customized libraries to a Suite56simulator?Yes, you can l

5-6 Suite56 DSP Tools User’s Manual MotorolaHow do I get a listing with cycle counts?When you assemble your application, use the option -mu to report

What does this error message mean?Motorola Answers to Frequently Asked Questions 5-75.12 My program runs, but it is too big.Assemble your application

viii Suite56 DSP Tools User’s Manual Motorola

5-8 Suite56 DSP Tools User’s Manual MotorolaWhat does this error message mean?

Motorola Glossary-1absolute executable file is an object file in which the assembler and linker have filled in,for every symbol, its ultimate location

Glossary-2 DSP Tools User’s Manual Motorolaoverlaying is a strategy of repeatedly using the same location in memory for theexecution of different piec

Motorola Index-1Aabbreviations xiiiabsolute executable file 1-4, Glossary-1acronyms xiiiADM application development module Glossary-1setting up 2-1tes

Index-2 DSP Tools User’s Manual Motorolalong-term predictor (LTP) 3-5map file 3-26memory control file 3-25test command converter 2-4test target device

Motorola Index-3multiple devices 4-1JTAG interface 4-2no JTAG interface 4-1separate directories for 5-1simulating communication 4-4Nnotation xiiicasts

Index-4 DSP Tools User’s Manual Motoroladisplaying source code 4-3function calls 4-3preferences 3-1, 5-2session 4-3simulated input 4-3simulated output

Motorola List of Examples ixList of Examples2-1 Start the Debugger ........... 2-42-2 Test Commands for the Command Con