Disclaimer. Purpose of This Document. Intended Audience. Technical or Customer Support. Online Technical Documentation

This chapter describes the new features and enhancements introduced in environment, tools, and documentation.

The information is presented as follows.

•  “Integrated Development and Debugging Environment (IDDE)” on page 2-2

•  “Simulator” on page 2-8

•  “Assemblers” on page 2-10

•  “Compiler and Library” on page 2-14

•  “Linker” on page 2-18

•  “Documentation” on page 2-20

•  “VisualDSP++ Component Software Engineering (VCSE)” on page 2-23

•  “VisualDSP++ Kernel” on page 2-25

•  “Object Protection” on page 2-27

Integrated Development and

Debugging Environment (IDDE)

The IDDE provides these new features and enhancements:

•  “External Makefile Execution” on page 2-2

•  “New Profiler Interface” on page 2-3

•  “New Streams Interface” on page 2-4

•  “Image Viewer” on page 2-5

•  “Flash Programmer” on page 2-7

•  “Editor Enhancements” on page 2-7

For more information, refer to the VisualDSP++ 3.0 User’s Guide for ADSP-21xx DSPs and online Help.

External Makefile Execution

The IDDE has been enhanced to support the loading and building of external gmake-compatible makefiles. This feature enables you to develop, maintain, and use your own external makefile without having to leave the IDDE. When you open a makefile, it is displayed in the Project window as a single file node. Double-clicking on the makefile icon in the Project window opens the makefile in the editor window. A syntax highlighting file is provided for easier makefile editing.

The IDDE does not consume, parse, or perform any type of syntax checking on the makefile and does not modify the loaded makefile in any way. While a makefile is opened, all project related commands with the exception of Build and Build All are disabled. When a Build or Build All command is issued, the gmake engine is executed and all output is displayed on the Build page of the Output window.

If an error occurs, the error text, which includes the line number and name of the file, appears on the Build page of the Output window. The error text conforms to the syntax described in the section “Error Message Numbering and Help” on page 2-20. Double-clicking the text opens the specified file and places the cursor on the line that has the error.

New Profiler Interface

The legacy profiling tool supported by simulators has been merged with the new statistical/linear profiler.

The Profile option has been removed from the Tools menu and from the View/Debug Windows menu since the legacy profiler is no longer supported.

Linear Profiling

A new linear profiling interface is available for the ADSP-219x DSP simulator only. Emulators continue to use the statistical profiling interface. A new menu option (New Profile) under Tools and Linear Profiling opens the Linear Profiling Results window.

Settings in the Profile Window Properties dialog box control which and how data items are utilized in the profiling interface. To open the properties dialog box, right-click in the Linear Profiling Results window.

From the Display tab, select the profiling data items to display. The linear profiling interface enables the simulator to pass additional profiling data, such as cache hits and misses, which can be displayed in additional columns.

From the Filter tab, choose one of the following items to profile.

•  Entire memory space. The linear and statistical profilers have the same behavior as in VisualDSP++ 2.0.

•  C/C++ functions. Choose functions to profile from a list of available functions. The profiler discards any collected PC samples that are not within the selected functions.

•  Memory ranges. Specify the start and end addresses of the memory ranges to profile. The profiler discards any collected program counter (PC) samples that are not within the selected memory ranges.

Most of the time, when building debug versions of the code, you profile