WolfSSL
/
wolfBoot
mirror of https://github.com/wolfSSL/wolfBoot.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Fixed documentation relative paths

pull/1/head
Daniele Lacamera 2018-10-15 07:43:54 +02:00
parent 836cfbc608
commit b9fca1d79a
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/firmware_image.md
View File

@ -20,7 +20,7 @@ to guarantee that the entry point of the actual firmware is stored on the flash
a 256-Bytes aligned address. This ensures that the bootloader can relocate the vector table before a 256-Bytes aligned address. This ensures that the bootloader can relocate the vector table before
chain-loading the firmware the interrupt continue to work properly after the boot is complete. chain-loading the firmware the interrupt continue to work properly after the boot is complete.
![Image header](docs/png/image_header.png) ![Image header](png/image_header.png)
*The image header is stored at the beginning of the slot and the actual firmware image starts 256 Bytes after it* *The image header is stored at the beginning of the slot and the actual firmware image starts 256 Bytes after it*
@ -35,7 +35,7 @@ respectively containing:
These three fields are required by the bootloader to verify the integrity and the origin of the firmware image. These three fields are required by the bootloader to verify the integrity and the origin of the firmware image.
![Image trailers](docs/png/image_tlv.png) ![Image trailers](png/image_tlv.png)
*The trailer of a signed firmware contains a TLV header and three TLV records that are used by the bootloader to verify the image* *The trailer of a signed firmware contains a TLV header and three TLV records that are used by the bootloader to verify the image*

6
docs/flash_partitions.md
View File

@ -17,7 +17,7 @@ The flash memory of the target is partitioned into the following areas:
- Scratch space (swap partition) starting at address `FLASH_AREA_IMAGE_SCRATCH_OFFSET` - Scratch space (swap partition) starting at address `FLASH_AREA_IMAGE_SCRATCH_OFFSET`
A proper partitioning configuration must be set up for the specific use, by setting A proper partitioning configuration must be set up for the specific use, by setting
the values for offsets and sizes in [include/target.h](include/target.h). the values for offsets and sizes in [include/target.h](../include/target.h).
### Bootloader partition ### Bootloader partition
@ -54,7 +54,7 @@ configuration in `target.h`:
which results in the following partition configuration: which results in the following partition configuration:
![example partitions](docs/png/example_partitions.png) ![example partitions](png/example_partitions.png)
This configuration demonstrates one of the possible layouts, with the slots This configuration demonstrates one of the possible layouts, with the slots
aligned to the beginning of the physical sector on the flash. aligned to the beginning of the physical sector on the flash.
@ -62,6 +62,6 @@ aligned to the beginning of the physical sector on the flash.
The entry point for all the runnable firmware images on this target will be `0x20100`, The entry point for all the runnable firmware images on this target will be `0x20100`,
256 Bytes after the beginning of the first flash partition. This is due to the presence 256 Bytes after the beginning of the first flash partition. This is due to the presence
of the firmware image header at the beginning of the partition, as explained more in details of the firmware image header at the beginning of the partition, as explained more in details
in [Firmware image](docs/firmware_image.md) in [Firmware image](firmware_image.md)