Table of Contents
Advertisement
4.
XVF3510 FEATURES AND CONFIGURATION
This section describes in detail the features and configuration of the XVF3510 processor. It is
organised into four sections which cover the main aspects of usage and configuration:
}
Booting;
}
Configuration and the Data Partition;
}
Interfaces, Audio Routing and filtering;
}
Far-field voice processing.
4.1. BOOTING
As demonstrated with the VocalFusion development kits the standard mechanism for booting is from
an attached QSPI Flash device. This provides standalone operation, and persistent storage for
configuration dataa. VocalFusion XVF3510 supports device firmware upgrade (DFU) over USB (-UA
product variant) and I
2
C (-INT product variant). Pre-compiled host utilities, and source code for
reference, are supplied for performing DFU operations. The Pre-compiled utilities can be found in the
release package in one of the host architecture directories eg. host\Win32\bin\dfu_usb.exe,
and the source code in host\src\dfu.
NOTE: While the functionality of the DFU is similar to the USB DFU specification, it has diverged to
accommodate both USB and I2C operation and therefore is not compatible with compliant USB DFU
tools.
The following sections discuss the structure of data within the flash memory, and operation of DFU.
4.1.1. FLASH STORAGE STRUCTURE
The structure of data within the VocalFusion XVF3510 is arranged to contain a factory image, a single
upgrade image, device serial numbers and data partitions for both the factory and upgrade image.
This is shown below.
Figure 4-1 Flash data structure for VocalFusion XVF3510
}
The Factory boot image is the executable code for VocalFusion, and is supplied in the Release
Package in the bin directory. The file format is xe, which refers to XMOS Executable. This is
written to the device via the XTAG debugger or through a bulk flash programming operation.
}
The Upgrade boot image , if present, is the executable code written to the flash memory via a
DFU operation. Generation of the Upgrade boot image is covered below.
}
The HW build info is specified in the .json Data Partition file for the factory image and is written
at the same time as the factory image and Data Partition. It is a unique identifier which is
unaffected by subsequent DFU upgrade operations.
XM-014232-PC
24
Advertisement
Table of Contents
