Accessing The Device Driver Api - Analog Devices VisualDSP++ 5.0 Service Manual

To use the device drivers, applications need only to use include files in
their source code, and link with a device driver library and a system ser-
vices library module.

Accessing the Device Driver API

User source files accessing the device manager API should include the files
and
services.h
and
Blackfin/include/drivers
source file should use the include file of the physical driver that will be
accessed.
For example, user code that accesses the Analog Devices parallel peripheral
interface (PPI) driver would include the following lines in their source file
(in order):
#include <services/services.h>
#include <drivers/adi_dev.h>
#include <drivers/ppi/adi_ppi.h>
The device driver API and functionality is uniform and consistent across
all Blackfin processors, including all single- and multi-core devices.
Regardless of the Blackfin processor being targeted, application software
does not change. For example, application software running on a sin-
gle-core ADSP-BF533 processor can operate unchanged on a multi-core
ADSP-BF561 processor.
In order to provide this consistent API to the application, the system ser-
vices, device manager, and physical drivers need to be aware of the specific
processor variant being targeted. You must ensure that the processor defi-
nition macro for the processor variant being targeted is defined when
including the system services (
and physical driver include files.
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors
, located in the
adi_dev.h
directories, respectively. In addition, your
services.h
Introduction
Blackfin/include/services
// system services
// device manager
// PPI physical driver
), device manager ( ),
adi_dev.h
1-25