Linking In The Device Driver Library - Analog Devices VisualDSP++ 5.0 Service Manual

Device Driver Overview

Linking in the Device Driver Library

All object code for the device manager and Analog Devices-supplied phys-
ical drivers is included in the device driver library file. This file is found in
the
Blackfin/lib
for each supported processor variant. You should ensure that the appropri-
ate library is included in the list of object files for the linker.
The device driver library file is of the form
• represents the processor variant – This is typically a three-digit
xxx
number that identifies the processor variant, such as
ADSP-BF532 processor,
so on.
• represents any special conditions for the library – The following
z
combinations are used:
•
y
revisions of silicon.
• blank – A library without an additional suffix does not con-
tain workarounds to any anomalies.
Located within the
individual silicon revisions. The libraries in these subdirectories are built
for specific silicon revisions of the processors.
One device driver library file should be included for the linker to process.
Choose the correct library based on the processor variant for your system.
For example, an application developer targeting silicon revision 0.2 of the
ADSP-BF532 processor should link with the
Blackfin/lib/bf532_rev_0.2
1-28
directory. In this directory is a device driver library file
534
– The library is built to avoid all known anomalies for all
Blackfin/library
subdirectory. As another example, the
VisualDSP++ 5.0 Device Drivers and System
libdrvxxxz.dlb
for the ADSP-BF534 processor, and
directory are subdirectories for
libdrv532.dlb
Services Manual for Blackfin Processors
where:
for the
532
file from the