Adsp device drivers and system services

Address: http://blog.csdn.net/gaoling179/article/details/6284770

 

In the process of developing a DSP using Visual DSP ++, you can quickly develop applications by applying the device drivers and system service programs that come with the system software without writing the underlying drivers.

 

(1) Adi has constructed all the drivers and services related to DSP Chips. As long as you understand the framework, writing applications is as simple as building blocks, first, let's briefly introduce the composition of the file:

":/Program files/analog devices/visualdsp 5.0/Blackfin/include/services" is the location of all system service header files, add "# include <services/services. h>.

":/Program files/analog devices/visualdsp 5.0/Blackfin/lib/src/services" is where all system service source files are located, if the debugging program can copy the corresponding service program to the project file, and then join the project to enter the service for internal debugging.

":/Program files/analog devices/visualdsp 5.0/Blackfin/include/drivers" is the location of all driver headers, add "# include <services/services. h> "and the corresponding driver header file, such as" # include <Drivers/sport/adi_sport.h> ", you can add the sport driver to the project.

":/Program files/analog devices/visualdsp 5.0/Blackfin/lib/src/drivers" is the location of all device driver source files, if the debugging program can copy the corresponding driver to the project file, and then add the project to the driver for debugging.

 

 

(2) The following is a brief introduction to system services:

System services provide unified interfaces for different chips, which are located at the underlying layer of applications and implement the underlying functions of chips, for example, you only need to call the flag system service function adi_flag_setdirection to set the IO port as the output, which is very simple. Different service programs are associated with each other and initialized in sequence.

Contact:

 

Initialization sequence:

1. Interrupt Control Service
2. External Bus Interface Unit
3. Power Management Service
4. Port Control (if applicable)
5. Deferred callback service
6. DMA Manager Service
7. Programmable flag Service
8. Timer Service
9. Real-time clock service
10. semaphore Service

The initialization program can use the system service layer Initialization Files (adi_ssl_init.c and adi_ssl_init.h) provided by ADI to set macro definitions in the header file.

 

(3) The following describes the device drivers:

The device driver also provides a unified interface, which is as simple as file operations. You can also control the device driver by calling the following functions,

Adi_dev_close
Adi_dev_control adi_dev_init
Adi_dev_open adi_dev_read
Adi_dev_terminate
Adi_dev_write.

The location of the device driver in the program is shown in:

 

 

(4) Read Device Drivers and system servicesmanual for XXX processors in detail.