• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 120 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM67A: AM67A storage-specific odd boot behavior

Raymond Healy
Prodigy 60 points

Part Number: AM67A

I am working with a custom AM67A-based board, running the processor sdk linux for am67a. I am currently booting off of SD cards (using an MMC user data area boot mode), and (for most cards), will boot directly from u-boot into linux, loading their device tree path from a modified UEnv.txt.

However, certain cards will fail to load my intended device tree (failure to find a path), and will then fallback to what seems to be a grub EFI app which uses the device tree contained in the binman-generated boot image.

I have checked the user data area contents of a disk image of a working card, a faulting card, and the common yocto-generated image used to flash them both, and have found no major differences.

My questions are:

1. Am I correct in assuming that this grub EFI image pulls its device tree from the boot binary, rather than from the linux image

2. Does the u-boot image generated by the ti-u-boot-staging recipe make use of the boot areas of the sd card (e.g. to store environment variables), since I have been unable to find glaring differences in the user data area.

  • 0
    TI__Guru* 86181 points

    Hello,

    Raymond Healy said:
    1. Am I correct in assuming that this grub EFI image pulls its device tree from the boot binary, rather than from the linux image

    I will have to check on this.

    Raymond Healy said:
    2. Does the u-boot image generated by the ti-u-boot-staging recipe make use of the boot areas of the sd card (e.g. to store environment variables), since I have been unable to find glaring differences in the user data area.

    The default environment is built into the U-Boot image itself. If you have modified the environment variables and saved them with `saveenv` then the environment location depends on the location you have configured in the source code.

    Raymond Healy said:
    However, certain cards will fail to load my intended device tree (failure to find a path), and will then fallback to what seems to be a grub EFI app which uses the device tree contained in the binman-generated boot image.

    Could you please share the failure boot logs?

    Regards,

    Prashant