Table of Contents
Advertisement
The version of the firmware should also be specified in the --upgrade argument of xflash when
generating the Upgrade Image as described previously.
If the compatibility check fails, the booted image, which could be a factory image or an upgrade image
will not read the Data Partition and will operate with its default settings (described in Default Operation
section above). The Boot status is reported in the RUN_STATUS register which can be accessed via
the vfctrl utility, for example:
vfctrl_usb GET_RUN_STATUS
Successful Boot status is reported by either FACTORY_DATA_SUCCESS or UPGRADE_DATA_SUCCESS
depending on which Boot Image was executed.
If unsuccessful the device will revert to a fail-safe mode of operation. The RUN_STATUS register can
be queried for further debug information. The full list of RUN_STATUS codes are described in the
Appendix B: Boot Status codes (RUN_STATUS).
NOTE: Fail safe mode uses default vendor ID of 0x20B1 (XMOS) and product ID of 0x14. In this event,
host needs to be equipped with the ability to locate USB device under different IDs.
4.1.6. CUSTOM FLASH MEMORY DEVICES
The majority of QSPI flash devices conform to the same set of parameters which define the access
and usage of flash devices. However, to support instances when the flash interface parameters are
different, the following section explains how to define a custom flash interface.
Details of the flash device used to store the Boot Image and Data Partition data must be specified in
two locations to ensure successful Factory programming and the ability to execute DFU to Upgrade
the firmware. The Development kit uses a standard QSPI flash device which is representative of most
2MByte QSPI devices.
CUSTOM FLASH DEFINITION FOR FACTORY PROGRAMMING
During the Factory programming procedure, using the XMOS XTAG debugger, the specification of the
flash device is used to create the loader which is responsible for downloading the Boot Image from
flash and to the device. The flash specification is provided to XFLASH, as described in the
Updating
the Firmware
section, using a SPISPEC file. A representative SPISPEC file, which supports the majority
of QSPI flash devices and the Development Kits is provided in the Release Package here:
\data-partition\16mbit_12.5mhz_sector_4kb.spispec
This is a text file and must be modified with any differing parameters. An example .spispec file is shown
Appendix C: Example .SPISPEC File Format
in
section.
CUSTOM FLASH DEFINITION FOR DATA PARTITION GENERATION
The SPISPEC file must also be included in the Data Partition, along with the Sector size so that DFU
operations can be executed correctly.
NOTE: Due to the nature of the DFU function, it is critically important to test the execution of the DFU
process in a target system prior to production manufacturing.
XM-014232-PC
28
Advertisement
Table of Contents
