USB Audio Design Guide
5.4
Validated Build Configurations
It is not possible for all build configuration permutations to be exhaustively tested.
XMOS therefore test a subset of build configurations for proper behaviour, these
are based on popular device configurations.
The presence of a build configuration in an application signifies it as a Validated
Build Configuration and should be considered supported.
5.5
Configuration Naming Scheme
This section describes the naming scheme for the provided build configurations
(and therefore binaries) generated for each build configuration
Each relevant build option is assigned a position in the configuration name, with
a character denoting the options value (normally ‘x’ is used to denote “off” or
“disabled”)
For example, Figure
lists the build options for the single tile L-Series Reference
Design.
Build Option Name
Options
Denoted by
Audio Class Version
1 or 2
1 or 2
Audio Input
on or off
i or x
Audio Output
on or off
o or x
MIDI
on or off
m or x
S/PDIF Output
on or off
s or x
Figure 31:
Single tile
L-Series build
options
For example a binary named 2ioxs would indicate Audio Class 2.0 with input and
output enabled, MIDI disabled, SPDIF output enabled.
5.6
A USB Audio Application
This section provides a walk through of the single tile USB Audio Reference Design
(L-Series) example, which can be found in the
app_usb_aud_l1
directory.
In each application directory the
src
directory is arranged into two folders:
#. An
core
directory containing source items that must be made available to the
USB Audio framework
1. An
extensions
directory that includes extensions to the framework such as
CODEC config etc
The
core
folder for each application contains:
1. A
.xn
file to describe the hardware platform the app will run on
2. A custom defines file:
customdefines.h
for framework configuration
XM0088546.1
Содержание xCORE-200 Multi-channel Audio board
Страница 6: ...1 Overview XM0088546 1...
