Table of Contents
Advertisement
Example 4-1. Configuration items for timer/counter - extract from the driver header file
/*******************************************************************************
Defines for appconfig.h for each timer/counter
********************************************************************************
void qtxxISR(void);
#define INT_VECTOR_ADDR_yy qtxxISR
#define INT_PRIORITY_LEVEL_yy one of INTC_DISABLED, INTC_LEVEL0,
#define QT_xx_CTRL_INIT 0x0000
#define QT_xx_SCR_INIT
#define QT_xx_CMP1_INIT 0x0000
#define QT_xx_CMP2_INIT 0x0000
#define QT_xx_LOAD_INIT 0x0000
#define QT_xx_CNTR_INIT 0x0000
where:
xx is timer/counter:
yy is corresponding interrupt vector
*/
4.3
On-chip drivers - interface description
The DSP56800E_Quick_Start includes a set of on-chip drivers which are used to initialize, to
configure and to access the on-chip peripherals. The on-chip drivers provide a C language
Application Programming Interface (API) to the peripheral module (see Figure 4-1). This
interface is common for all input/output operations.
This interface provides the following API statements:
ioctl - to initialize and to access peripheral module
read - e.g. to receive data
write - e.g. to transmit data
The philosophy of all input/output operations resides in these three statements (commands).
These commands provide better code portability between the processors from the same family,
where the base addresses of the peripheral modules are different. Therefore it is preferred to use
FREESCALE SEMICONDUCTOR
INTC_LEVEL1, INTC_LEVEL2 or INTC_LEVEL3
0x0000
D0,D1,D2,D3,C0,C1,C2,C3,B0,B1,B2,B3,A0,A1,A2,A3
e.g. on MC56F8346:
D: 52,53,54,55
C: 56,57,58,59
B: 60,61,62,63
A: 64,65,66,67
User Application
On-chip Driver API
Peripheral Module
Figure 4-1. User Interface
Targeting 56F8xxx Platform
On-chip drivers - interface description
4-3
Advertisement
Chapters
Table of Contents
