• State
  • Replies 2 replies
  • Subscribers 32 subscribers
  • Views 24 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AM3351: u-boot 2026.04 defconfig Build Issues

Bob Groves
Prodigy 10 points

Part Number: AM3351

Using the U-Boot 2026.04 release, I built a MLO file based on the am335x_evm_defconfig file.

Redoing the u-boot build using the 2017 Linux 4.9 product baseline ‘devel_am335x_defconfig’ file, the build fails with various ‘make’ pre-script check errors.

Reviewing the 2017 Linux 4.9 product baseline ‘devel_am335x_defconfig’ file, I also found missing ‘oMap’ configuration statements.

Need TI help in addressing the 2017 Linux 4.9 product baseline ‘devel_am335x_defconfig’ file u-boot build issues.

I see two paths forward to resolve the u-boot build issues:

  1. Modify the U-Boot 2026.04 release am335x_evm_defconfig file --
  • Using u-boot menuconfig, modify the ‘am335’ configuration statements for our product hardware.
  1. Modify the 2017 Linux 4.9 product baseline ‘devel_am335x_defconfig’ file --
  • Add the missing ‘oMap’ configuration statements.
  • Resolve the 2026.04 MLO build issues by updating the defconfig file.

 

 

  • 0
    TI__Intellectual 1050 points

    Hi ,

    The owner is on leave today; he will address this once back,
    Thanks,
    JOMY
  • 0 in reply to Jomy Paul P S
    TI__Guru**** 179531 points

    Hi Bob,

    Before the assigned engineer looking into your query, can you please clarify on what you are trying to do with both u-boot 2026.04 and 2017 sdk u-boot? I am a bit confused by your description. It seems you are trying to use the u-boot defconfig from 2017 to build 2026.04, is this correct?

    Regardless the u-boot version, it already provides configs/am335x_evm_defconfig. You'd better to use it as the baseline but please do not take the defconfig file across u-boot versions.

    Please also note, for latest u-boot, the TI officially supported version is 2026.01, not 2026.04 and any other 2026 versions.