Table of Contents
Advertisement
For example, to create an upgrade Binary image for a -UA system, from the v4.0.0 Release Package
use the following command:
xflash --no-compression --noinq --factory-version 14.3
--upgrade 0x0400 app_xvf3510_ua_v4.0.0.xe -o app_xvf3510_ua_v4.0.0.bin
ADDITION OF DFU SUFFIX TO BINARY FILES
To prevent accidental upgrade of an incompatible image both the binary Upgrade image and the Data
Partition binary must be signed using the provided dfu_suffix_generator which can be found
pre-compiled in the host platform directory of the release package eg. \host\MAC\bin.
This mechanism embeds a structure into the binary files which can be read by the DFU tool to check
that the binary data is appropriate for the connected device, prior to executing.
The general form of usage for the dfu_suffix_generator is as follows:
dfu_suffix_generator VENDOR_ID PRODUCT_ID [BCD_DEVICE] BINARY_INPUT_FILE BINARY_OUTPUT_FILE
VENDOR_ID, PRODUCT_ID and BCD_DEVICE are non-zero 16bit values decimal or hexadecimal
format, 0xFFFF bypassing verification of this field.
When building Upgrade images for XVF3510-UA devices, the USB Vendor Identifier (VID) and USB
Product Identifier (PID) are added to the header and then checked by the DFU utility that the
connected device matches. An error is reported by the tool if there is no match with the connected
device.
For XVF3510-INT devices both Vendor and Product ID fields should be set to 0xFFFF for the
generation. This instructs the DFU to bypass the checking as there is no equivalent to the USB
identifiers for I2C systems. However, even though the checking is bypassed for the XVF3510-INT the
suffix must be added to both Upgrade and Data partition files as the DFU utility checks the integrity of
the binaries based on this information.
The following examples show how to add DFU Suffix to Update binaries for both XVF3510-INT and
XVF3510-UA products.
For XVF3510-UA (default XMOS Vendor and XVF3510-UA product identifiers are used for illustration):
dfu_suffix_generator.exe 0x20B1 0x0014 app_xvf3510_ua_v4.0.0.bin boot.dfu
dfu_suffix_generator.exe 0x20B1 0x0014 data_partition_upgrade_ua_v4_0_0.bin data.dfu
For XVF3510-INT:
dfu_suffix_generator.exe 0xFFFF 0xFFFF app_xvf3510_int_v4.0.0.bin boot.dfu
dfu_suffix_generator.exe 0xFFFF 0xFFFF data_partition_upgrade_int_v4_0_0.bin data.dfu
NOTE: Extreme care must be taken if modifying the default Vendor and Product IDs through a Data
Partition. If configuration from Data Partition fails the USB VID and PID will remain at their default values
(VID=0x20B1, PID=0x0014) and DFU requests for signed files with modified will not be allowed.
PERFORMING DFU
The pre-compiled DFU utility is provided in the Release Package in the host architecture directory eg.
\host\Linux\bin. For MAC, Linux and Windows the DFU_USB is provided, and for PI DFU_I2C is
provided. The source code can be used to rebuild either version on the required platform.
The general form of dfu_usb utility is as follows:
dfu_usb [OPTIONS] write_upgrade BOOT_IMAGE_BINARY DATA_PARTITION_BIN
OPTIONS:
--quiet
--vendor-id 0x20B1 (default)
--product-id 0x0014 (default)
--bcd-device 0xFFFF (default)
--block-size 128 (default)
and the general form of the dfu_i2c utility is shown below:
XM-014232-PC
26
Advertisement
Table of Contents
