path: root/Documentation
diff options
authorAndrey Smirnov <>2018-12-07 00:13:22 -0800
committerSascha Hauer <>2018-12-10 10:04:39 +0100
commit392ae40c2c10e0bf657723bc3fdd8a9a7fa54b77 (patch)
tree954c83d77d8c1edd7e2875c0e1bbac9e2ad3e405 /Documentation
parent32c01aa6c8a6310d09b706fd634f439cc3d115e3 (diff)
Documentation: i.MX: Document how to use GPT
Document a way to avoid clashes between i.MX boot info/Barebox and GPT's Partition Entry Array. Signed-off-by: Andrey Smirnov <> Signed-off-by: Sascha Hauer <>
Diffstat (limited to 'Documentation')
1 files changed, 19 insertions, 0 deletions
diff --git a/Documentation/boards/imx.rst b/Documentation/boards/imx.rst
index 99ca10b..35a180b 100644
--- a/Documentation/boards/imx.rst
+++ b/Documentation/boards/imx.rst
@@ -60,6 +60,25 @@ The images can also always be started second stage::
bootm /mnt/tftp/barebox-freescale-imx51-babbage.img
+Using GPT on i.MX
+For i.MX SoCs that place vendor specific header at +1KiB mark of a
+boot medium, special care needs to be taken when parition that medium
+with GPT. In order to make room for i.MX boot header GPT Partition
+Entry Array needs to be moved from its typical location, LBA 2, to an
+offset past vendor specific information. One way to do this would be
+to use ``-j`` or ``--adjust-main-table`` option of ``sgdisk``. For
+example, the following sequence:
+ sgdisk -Z <block device>
+ sgdisk -o -j 2048 -n 1:8192:+100M <block device>
+will create a single GPT partition starting at LBA 8192 and would
+place Partition Entry Array starting at LBA 2048 which should leave
+enough room for Barebox/i.MX boot header. Once that is done ``dd``
+command above can be used to place Barebox on the same medium.
Information about the ``imx-image`` tool