Hi Fabio,
On Sun, Feb 18, 2018 at 3:14 AM, Fabio Estevam festevam@gmail.com wrote:
From: Fabio Estevam fabio.estevam@nxp.com
With fastboot support enabled, it is useful to be able to list the eMMC EFI partitions, so select the CONFIG_EFI_PARTITION option.
Signed-off-by: Fabio Estevam fabio.estevam@nxp.com
Hi Stefano,
It seems you picked the v1 of my fastboot patch instead of v2.
Hence I am sending a new patch that only selects CONFIG_EFI_PARTITION.
configs/mx6sabresd_defconfig | 1 + 1 file changed, 1 insertion(+)
diff --git a/configs/mx6sabresd_defconfig b/configs/mx6sabresd_defconfig index feb385d..55709e8 100644 --- a/configs/mx6sabresd_defconfig +++ b/configs/mx6sabresd_defconfig @@ -48,6 +48,7 @@ CONFIG_CMD_EXT4=y CONFIG_CMD_EXT4_WRITE=y CONFIG_CMD_FAT=y CONFIG_CMD_FS_GENERIC=y +CONFIG_EFI_PARTITION=y
Do you have a partition table details, I'm trying GPT as below
+#define ROOT_UUID "69dad710-2ce4-4e3c-b16c-21a1d49abed3" +#define PARTS_DEFAULT \ + "name=loader1,start=1k,size=64K,uuid=${uuid_gpt_loader1};" \ + "name=loader2,start=69K,size=827K,uuid=${uuid_gpt_loader2};" \ + "name=uEnv,start=896K,size=128K,uuid=${uuid_gpt_uenv};" \ + "name=rootfs,size=-,uuid="ROOT_UUID
=> gpt write mmc 0 $partitions Writing GPT: Partition overlap error!
Look like loader1 start=1k wont working, it 's always starting 0x00000022 offset if we unspecify start but SPL wont start there right?
Jagan.