U-Boot: CONFIG_DEFAULT_DEVICE_TREE is not effective

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Urgent
    • Linux Core SDK
    • LCPD-45546
    • 11.00
    • 11.02
    • Hide
      am64xx-evm
      am64xx-hsevm
      am64xx_sk-fs
      Show
      am64xx-evm am64xx-hsevm am64xx_sk-fs

      The devicetree file name set in CONFIG_DEFAULT_DEVICE_TREE is not effective.

      When porting U-Boot to a custom board, the board devicetree filename would be set in CONFIG_DEFAULT_DEVICE_TREE in defconfig. However, U-Boot would ignore this setting and still use ti/k3-am642-evm.dtb.

      The reason is that the board name is predefined as "am64x_gpevm" in setup_board_eeprom_env() when i2c eeprom detect failed, which leads to function ti_set_fdt_env() ignoring CONFIG_DEFAULT_DEVICE_TREE and using ti/k3-am642-evm.dtb instead.

      Fix:
      Merged in ti-u-boot at https://github.com/TexasInstruments/ti-u-boot/commit/1ea5958721b24ee7d364f11737844a6f15aebf98
      A similar fix will be posted upstream as well with a significant refactor to ti_fdt_map.

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-6369 - U-Boot: CONFIG_DEFAULT_DEVICE_TREE ...
                SYNCHRONIZED
                • Last Sync Date: