Table of Contents
Advertisement
dfu_i2c [OPTIONS] write_upgrade BOOT_IMAGE_BINARY DATA_PARTITION_BIN
OPTIONS:
--quiet
--i2c-address 0x2c (default)
--block-size 128 (default)
The two binary files passed to the utility, the boot image and data partition, must have the DFU suffix
present otherwise the DFU utility will generate an error. Example DFU utility usage is shown for both
XVF3510-UA and XVF3510-INT below.
For XVF3510-UA:
dfu_usb --vendor-id 0x20B1 --product-id 0x0014 write_upgrade boot.dfu data.dfu
and for XVF3510-INT:
dfu_i2c write_upgrade boot.dfu data.dfu
Once complete the following message will be returned and the device will reboot. In the case of
XVF3510-UA the device will re-enumerate.
write upgrade successful
For verification that DFU has succeeded as planned, the vfctrl utility can be used to query the firmware
version before and after update. For example, to query the version of XVF3510-UA the following
command is used:
vfctrl_usb GET_VERSION
NOTE: The vfctrl utilities check the version number of the connected device to ensure correct
operation. To suppress an error caused by a disparity in the version of vfctrl and upgraded firmware
the --no-check-version option can be used with the utility.
4.1.4. FACTORY RESTORE
To restore the device to its factory configuration, effectively discarding any upgrades made, the same
process as outlined above is followed but using a blank Boot Image and Data Partition.
This is the only way a restore can be initiated as the device does not have the ability to restore itself.
The same blank file can be used for both Boot Image and Data partition and can be generated using
dd on MAC and Linux, and fsuils in windows as shown below:
An blank image can be created with a file of zeroes the size of one flash sector. In the normal case of
4KB sectors on a UNIX-compatible platform, this can be created as follows:
dd bs=4096 count=1 < /dev/zero 2>/dev/null blank.dfu
and for Windows systems:
fsutil file createNew blank.dfu 4096
The process outlined in the
can now be followed using the blank.dfu file for both Boot Image and Data Partition.
4.1.5. BOOT IMAGE AND DATA PARTITION COMPATIBILITY CHECKS
The format of Data Partitions and Boot Images may change between version increments. Therefore to
prevent incompatible Boot and Data Partitions from running and causing undefined behaviour, a field
called compatibility version is embedded into the Data Partition. A running Boot Image checks
its own version, against the compatibility version in the Data Partition before reading the
partition data.
XM-014232-PC
Generation and application of Upgrade Image and Data Partition
section
27
Advertisement
Table of Contents
