TI DSP/BIOS 5.42 用户手册：实时应用开发指南

DSPbios

需积分: 33 44 浏览量更新于2024-07-21 收藏 1.49MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

资源详情

资源推荐

16 About DSP/BIOS SPRU423I—August 2012

Submit Documentation Feedback

DSP/BIOS Components www.ti.com

1.2.2 DSP/BIOS Configuration Tool

A DSP/BIOS configuration allows you to optimize your application by creating objects and setting their

properties statically, rather than at run-time. This both improves run-time performance and reduces the

application footprint.

The source file for a configuration is a DSP/BIOS Tconf script, which has a file extension of .tcf. There

are two ways to access a DSP/BIOS configuration:

•

Textually. You can edit the text of the script using Code

Composer Studio or a separate text editor. You code the

configuration using JavaScript syntax. See the DSP/BIOS

Textual Configuration (Tconf) User’s Guide (SPRU007) for details.

•

Graphically. You can view configurations in read-only mode

with the DSP/BIOS Configuration Tool, a graphical editor that

functions as a macro recorder for scripts. The interface is

similar to that of the Windows Explorer. The script is shown

in the right pane as you create it.

You can set a wide range of parameters used by DSP/BIOS at run time. The objects you create are used

by the application’s DSP/BIOS API calls. These objects include software interrupts, tasks, I/O streams,

and event logs.

SYS System services manager

TRC Trace manager

TSK Multitasking manager

Module Description

SPRU423I—August 2012 About DSP/BIOS 19

Submit Documentation Feedback

www.ti.com Naming Conventions

Unlike traditional debugging, which is external to the executing program, program analysis requires the

target program contain real-time instrumentation services. By using DSP/BIOS APIs and objects,

developers automatically instrument the target for capturing and uploading real-time information to the host

through the Code Composer Studio DSP/BIOS analysis tools.

Several broad real-time program analysis capabilities are provided:

•

Program tracing. Displaying events written to target logs, reflecting dynamic control flow during

program execution

•

Performance monitoring. Tracking summary statistics that reflect use of target resources, such as

processor load and timing

•

File streaming. Binding target-resident I/O objects to host files

When used in tandem with other debugging capabilities of Code Composer Studio, the DSP/BIOS real-

time analysis tools provide critical views into target program behavior during program execution—where

traditional debugging techniques that stop the target offer little insight. Even after the debugger halts the

program, information already captured by the host with the DSP/BIOS analysis tools can provide insight

into the sequence of events that led up to the current point of execution

Later in the software development cycle, when regular debugging techniques become ineffective for

attacking problems arising from time-dependent interactions, the DSP/BIOS analysis tools have an

expanded role as the software counterpart of the hardware logic analyzer.

1.3 Naming Conventions

Each DSP/BIOS module has a unique name that is used as a prefix for operations (functions), header

files, and objects for the module. This name is comprised of 3 or more uppercase alphanumerics.

Throughout this manual, 64 represents the two-digit numeric appropriate to your specific DSP platform.

If your DSP platform is C6200 based, substitute 62 each time you see the designation 64. For example,

DSP/BIOS assembly language API header files for the C6000 platform will have a suffix of .h62. For a

C55x DSP platform, substitute 55 for each occurrence of 64. Also, each reference to Code Composer

Studio C5000 can be substituted with Code Composer Studio C6000.

All identifiers beginning with upper-case letters followed by an underscore (XXX_*) should be treated as

reserved words.

1.3.1 Module Header Names

Each DSP/BIOS module has two header files containing declarations of all constants, types, and

functions made available through that module’s interface.

•

xxx.h. DSP/BIOS API header files for C programs. Your C source files should include std.h and the

header files for any modules the C functions use.

•

xxx.h##. DSP/BIOS API header files for assembly programs. Assembly source files should include

the appropriate xxx.h## header file for any module the assembly source uses. For example, hwi.h62.

This file contains macro definitions specific to this device.

20 About DSP/BIOS SPRU423I—August 2012

Submit Documentation Feedback

Naming Conventions www.ti.com

Your program must include the header file for each module used in a particular program source file. In

addition, C source files must include std.h before any module header files. (See Section 1.3.4, Data Type

Names, page 1-21, for more information.) The std.h file contains definitions for standard types and

constants. After including std.h, you can include the other header files in any sequence. For example:

#include <std.h>

#include <tsk.h>

#include <sem.h>

#include <prd.h>

#include <swi.h>

DSP/BIOS includes a number of modules that are used internally. These modules are undocumented

and subject to change at any time. Header files for these internal modules are distributed as part of

DSP/BIOS and must be present on your system when compiling and linking DSP/BIOS programs.

1.3.2 Object Names

System objects included in the configuration by default typically have names beginning with a 3- or 4-

letter code for the module that defines or uses the object. For example, the default configuration includes

a LOG object called LOG_system.

Note: Objects you create statically should use a common naming convention of your

choosing. You might want to use the module name as a suffix in object names. For

example, a TSK object that encodes data might be called encoderTsk.

1.3.3 Operation Names

The format for a DSP/BIOS API operation name is MOD_action where MOD is the letter code for the

module that contains the operation, and action is the action performed by the operation. For example,

the SWI_post function is defined by the SWI module; it posts a software interrupt.

This implementation of the DSP/BIOS API also includes several built-in functions that are run by various

built-in objects. Here are some examples:

•

CLK_F_isr. Run by an HWI object to provide the low-resolution CLK tick.

•

PRD_F_tick. Run by the PRD_clock CLK object to manage PRD_SWI and system tick.

•

PRD_F_swi. Triggered by PRD_tick to run the PRD functions.

•

_KNL_run. Run by the lowest priority SWI object, KNL_swi, to run the task scheduler if it is enabled.

This is a C function called KNL_run. An underscore is used as a prefix because the function is called

from assembly code.

•

_IDL_loop. Run by the lowest priority TSK object, TSK_idle, to run the IDL functions.

•

IDL_F_busy. Run by the IDL_cpuLoad IDL object to compute the current CPU load.

•

RTA_F_dispatch. Run by the RTA_dispatcher IDL object to gather real-time analysis data.

•

LNK_F_dataPump. Run by the LNK_dataPump IDL object to manage the transfer of real-time

analysis and HST channel data to the host.

•

HWI_unused. Not actually a function name. This string is used in the configuration to mark unused

HWI objects.

剩余224页未读，继续阅读

lz820210

粉丝: 0
资源: 4

TI DSP/BIOS 5.42 用户手册：实时应用开发指南

完全bios手册（很全面的bios文档）

TI DSP-BIOS用户手册与驱动开发（完整）

TMS320 DSP BIOS 5.42 用户指南：嵌入式实时开发基石

DSP/BIOS用户手册

dsp28335数据手册

dsp28335中文手册

dsp6713技术手册

dsp芯片数据手册28335下载

dsp280039中文手册

dsp6674sysbios

stm32f10x_dsp库中文手册(fft)

dsp2803x参考手册中文

dsp28377s学习手册

dsp28335中文手册 定时器

stm32dsp库函数手册中文

dsp2803x中文数据手册

FT-M6678 DSP低速接口使用手册

TMIS320 DSP/BIOS

f2812 dsp/bios csl

最新资源

dsp28335中文手册定时器