Skip to content

Commit

Permalink
Recommend usage of partition type GUIDs to find firmware
Browse files Browse the repository at this point in the history
If the firmware is loaded from a GPT partitioned medium, it should use
the partition type GUID (and not sector number or partition number) to
identify the relevant partition. This GUID should be unique for each
board type.

Signed-off-by: Heinrich Schuchardt <[email protected]>
  • Loading branch information
xypron committed May 5, 2023
1 parent 552fe5a commit b5a3315
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions source/chapter4-firmware-media.rst
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,13 @@ non-protective partitions).
There are no requirements on the contents or layout of the firmware
protective partition.

Devices should use the partition type GUID to identify the partition with
the firmware to load. This is preferable over fixed sector or partition
numbers as it imposes the least restrictions on the partitioning scheme.

Firmware partition type GUIDs should be unique for a board type. This
allows creating media that can be booted on a multitude of boards.

Placing GPT data structures away from firmware images can be accomplished by
adjusting the GUID Partition Entry array location
(adjusting the values of `PartitionEntryLBA` and `NumberOfPartitionEntries`,
Expand Down

0 comments on commit b5a3315

Please sign in to comment.