FC Config Updates
From Texas Instruments Embedded Processors Wiki
Translate this page to
Framework component configuration updates
Contents |
Introduction
Using Framework Components (FC) requires configuring it to match your application's needs. Over time, old configuration options have evolved and new configuration options have been added. This page summarizes the changes to FC configuration that have occurred over the history of the Framework Components product.
Debug and Trace settings
| FC version where a change was introduced | Change | Example configuration |
|---|---|---|
| 1.20 | Initial implementation | You can configure DSKT2.debug=true or DMAN3.debug=true during development to enable obtain some tracing information and to insert debug symbols for the module of interest. |
| 2.0 | Decoupled tracing vs. debug build |
The available options are:
By setting these in your .cfg file, you can choose whether to enable the debug build profile or to enable tracing on a per-module basis. |
| 2.23 | Addition of a global setting to control tracing and debug build profile on all modules. Also changed the syntax to enable these on a per-module basis | E.g.
//Use all FC libraries with debug profile and no trace xdc.useModule('ti.sdo.fc.global.Settings').profile = "debug"; or //Use the DSKT2 library built with debug profile and no trace xdc.loadPackage('ti.sdo.fc.dskt2').profile = "debug"; The common options for 'profiles' are
|
Event Queue priorities in DMAN3
| FC version where a change was introduced | Change | Example configuration |
|---|---|---|
| 1.0 | Initial implementation - no option available | /* n/a */ |
| 2.0 | Added configuration parameter queuePri |
var DMAN3 = xdc.useModule('ti.sdo.fc.dman3.DMAN3'); DMAN3.queuePri = [3, 7, 0, 0, 0, 0, 0, 0]; |
See also
- Codec Engine configuration en breve
- Using createFromServer()
- Codec Engine Group IDs
- Changing the DVEVM memory map
- Codec Engine Configuration Updates
