laiyp/lib_xua
1
0
Fork 0
forked from PAWPAW-Mirror/lib_xua
Code Pull Requests Activity

Added explanation of values passed to xflash in example

Browse Source
This commit is contained in:
Sam Chesney
2014-06-11 17:32:33 +01:00
parent f1cb1828d1
commit 7d13492597
1 changed files with 19 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
module_dfu/doc/factory_image.rst
View File

@@ -16,6 +16,25 @@ Use the XMOS Development Tools to run the command:
in bytes the minimum size required to store the boot loader, factory image and in bytes the minimum size required to store the boot loader, factory image and
any upgrade images. any upgrade images.
The following can be used as a guide to help calculate the required boot
partition size for a design:
- boot partition size = loader size + maximum size of factory image +
maximum size of upgrade images + padding to sector boundaries
Where:
- loader size = 0x1000 bytes, or 0x4000 bytes if secure boot functionality is
used
- maximum size of factory image = number of xCORE tiles *
xCORE SRAM size
- maximum size of upgrade images = (number of xCORE tiles *
xCORE SRAM size) * number of concurrent images to be held in flash
The above example sets the boot partition to a size appropriate for designs
based on a single xCORE tile, where a single upgrade image is required
in flash at any one time.
This programs the factory default firmware image into the flash device. This programs the factory default firmware image into the flash device.
The device will now support the DFU mechanism, and can use it to safely receive The device will now support the DFU mechanism, and can use it to safely receive
firmware updates, as well as revert to the factory firmware image when required, firmware updates, as well as revert to the factory firmware image when required,