File System Service Api Reference; Notation And Naming Conventions - Analog Devices VisualDSP++ 5.0 Service Manual

File System Service API Reference

file. The number of cache blocks to use defaults to four (4), but can be
overridden upon initialization of the FSS with the inclusion of the follow-
ing command-value pair in the FSS configuration table:
{ ADI_FSS_CMD_SET_NUMBER_CACHE_BLOCKS,
(void*)<number-cache-blocks> },
When a file is opened, the file cache is dynamically allocated from the FSS
cache heap; when the file is closed, the memory is freed.
Please note that for the default format of the hard disk of the
ADSP-BF548 EZ-KIT Lite, a cluster—and hence each cache block—is
16 KB in size.
File System Service API Reference
This section provides the details of the data structures and functions
within the FSS or file system service application program interface (API).
It is usually intended that the API be used via intermediate code such as
the extensible. Its use may provide marginal benefits in terms of through-
put speed and code size, but this is offset by its lack of portability between
development environments.

Notation and Naming Conventions

To safeguard against conflicts with other software libraries provided by
Analog Devices, or other sources, the file system service uses an unambig-
uous naming convention in which enumeration values and
statements use the
lowercase
adi_fss_
Each function within the file system service API returns an error code of
type
ADI_FSS_RESULT
(
ADI_FSS_RESULT_SUCCESS
function call. Any nonzero value indicates the specific type of error that
12-18
prefix. Functions and global variables use the
ADI_FSS_
equivalent.
. Like the other system services, a return value of zero
) indicates that no error has occurred during the
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors
typedef