Termination; Device Driver Directory And File Structure - Analog Devices VisualDSP++ 5.0 Service Manual

Device Driver Overview

Termination

The API of the device driver model includes a termination function that
may be called by the application if the device drivers are no longer
required. The termination function,
free up the resources used by the device manager and any open physical
drivers. Many embedded systems run in an endless operating loop and
never call the termination function of the device manager. An application
that operates in an endless loop can save program memory by not calling
the terminate function.
As part of the termination function processing, the device manager closes
all open physical drivers. The physical drivers are closed in an abrupt man-
ner. If a more graceful shutdown is needed, the application may prefer to
close any open physical drivers first, and then call the termination
function.
Note that because of the reliance on the system services, the termination
function of the device manager should be called prior to any termination
functions of the system services. This ensures that the system services can
be called by the device manager and/or physical drivers as part of their
shutdown procedure.
After the device manager has been terminated, it must be reinitialized
before any of its functionality can be accessed again.

Device Driver Directory and File Structure

All files for the device driver model are contained within the
directory tree. In VisualDSP++ installations, this is the directory that
stores the core development tools. Other development toolsets may use
other directory names for their toolkits, but the device driver files can
always be found within the
1-24
adi_dev_Terminate()
directory tree.
Blackfin
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors
, is called to
Blackfin