Coma FW-C2800 User's Guide Page 38

  • Download
  • Add to my manuals
  • Print
  • Page
    / 276
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 37
Using the Configuration Tool
2-4
8) In the Save as type box choose Seed files (*.cdb) and click Save.
9) In the Set Description dialog type a description and click OK.
10) In the Configuration Tool, choose File
Exit.
2.2.3 Setting Global Properties for a Module
1) When you choose a module (by clicking on it), the right side of the
window shows the current properties for the module. (If you see a list of
priorities instead of a property list, right-click on the module and choose
Property/value view. If the right side of the window is gray, this module
has no global properties.)
For help about a module, click and then click on the module.
2) Right-click the icon next to the module and choose Properties from the
pop-up menu. This opens the property dialog.
3) Change properties as needed. For help on the module’s properties, click
Help in the property dialog.
2.2.4 Creating Objects Using the Configuration Tool
Most objects can be created either statically using the Configuration Tool or
dynamically by calling the function XXX_create. This section describes
objects created using the Configuration Tool. To create objects dynamically
see section 2.2.8, Creating, Referencing, and Deleting Dynamically-Created
DSP/BIOS Objects, page 2-10.
For typical DSP applications, most objects should be created with the
Configuration Tool because they are used throughout program execution. A
number of default objects are automatically defined in the configuration
template. Creating objects with the Configuration Tool provides the following
benefits:
Improved access within DSP/BIOS Analysis Tools. The Execution Graph
shows the names of objects created with the Configuration Tool. In
addition, you can view statistics only for objects created with the
Configuration Tool.
Reduced code size. For a typical module, the XXX_create and
XXX_delete functions contain 50% of the code required to implement the
module. If you avoid using any calls to TSK_create and TSK_delete, the
underlying code for these functions is not included in the application
program. The same is true for other modules. By creating objects with the
Configuration Tool you can dramatically reduce the size of your
application program.
Page view 37
1 2 ... 33 34 35 36 37 38 39 40 41 42 43 ... 275 276

Comments to this Manuals

No comments