PROCESSOR-SDK-AM62X: SK-AM62x EVM eMMC GPT Partition (UDA) boot failed

Hello Jason.

Upon first glace, your boot mode pin settings might be wrong.

For eMMC boot  from UDA (raw mode) B3=0, B4=0, B5=0, B6=1, B7=1, B8=0, B9=0

regards,

Judith

For more information, you could look at the TRM Table 5-4. Primary Boot Mode Selection

Hi Judith,

Thanks so much for your reply!

But it seems that the problem cannot be solved, B7 is set to 0 is the FS mode, what I want to know is the FS mode instead of the RAW mode

Thanks and regards,

Jason

Hi Judith,

        I test MBR and GPT in eMMC UDA(raw mode), both them can boot up. But it seems just MBR can boot up EVM in FS(filesystem) mode, GPT not work.

        I think the problem may occur in ROM boot or GPT boot setting.

Hi Yufeng,

Judith is out of office for the next few days. Please expect delayed response.

Hello Jason,

Ok, I understand now you are using eMMC boot in FS mode. Then please verify the boot pin setting:

B3:0, B4:0, B5:0, B6:1, B7:0, B8:0, B9:1

regards,

Judith

Hello Judith,

For eMMC UDA boot B9 should be set to 1.

I find CONFIG_EFI_LOADER in config_distro_bootcmd.h it support CONFIG_X86_RUN_64BIT, if I use GPT partition for FS boot need enable it (GPT + UEFI)? No more information in SDK.

Hello wei,

Just double checked and the  B9 should be set to 0 correct? MMCSD Port 0 (8 bit width). This bit must be set to 0

I think we have mistyped.

Hello wei,

It seems like boot from eMMC (fs mode) has not been validated and therefore is not supported by TI. Is there a reason why you are not using eMMC boot from boot0 or boot1?

regards,

Judith

Hello Judith,

       I tested eMMC UDA FS boot with MBR partition（B3 B7 B9 is 0）.

       During industrial production, if boot image in eMMC boot0 or boot1, rootfs in eMMC UDA, it seems  to burn them separately（boot.img and rootfs.img）.

       The better way is one burn image contains boot and rootfs, there are 10 partitions in my eMMC and the last few partitions have no actual content, if I use 

       MBR must include those logical partition table (MBR store logical partition table at the previous sector of each logical partition), if image not include no

       actual content partitions the partition information will be lost, so the burn image is too  large for me (about 5GB).

       GPT can stores the partition table in the previous sector of image, partition information not lose, the burn image just 1.7GB

       my partition:

       1. boot

       2. kernel

       3. rootfs

       4. p4

       5. p5

       6. p6

       7. p7

       8. p8

       9. p9

       10. p10

       In MBR, the burn image must include 'boot' to the previous sector of 'p10'.

       In GPT, the burn image just include 'boot', 'kernel' and 'rootfs'.

Hello Judith,

        thanks for your reply.

        now I used raw boot from eMMC UDA.