SPL not booting into main u-boot when loading using NXPs UUU tool and mender-uboot is enabled

General Discussions
, , , ,
6

I’m just providing a solution for those that encounter a similar issue and are looking for a good solution. I found that the best thing to do to solve the the issue mentioned in this post was to patch the Mender recipes to accept CONFIG_ENV_IS_NOWHERE as a valid configuration along with CONFIG_ENV_IS_MMC. The final solution is very easy to fix, by patching/updating two files. The affected files are: recipes-bsp/u-boot/patches/0002-Generic-boot-code-for-Mender.patch and recipes-bsp/u-boot/files/uboot_auto_configure.sh

Make the following modification in recipes-bsp/u-boot/patches/0002-Generic-boot-code-for-Mender.patch:

+#ifndef MENDER_AUTO_PROBING
+
+#include <config_mender_defines.h>
+/* Ossian: CONFIG_ENV_IS_NOWHERE is needed to boot using the UUU tool was: #ifdef CONFIG_ENV_IS_NOWHERE */
+#if !defined(CONFIG_ENV_IS_IN_MMC) && !defined(CONFIG_ENV_IS_IN_UBI)
+# error A CONFIG_ENV_IS_IN_<storage-type> define is required for Mender to work. For standard Mender setups this should be CONFIG_ENV_IS_IN_MMC for HD/SSD/MMC/SD storage setup, and CONFIG_ENV_IS_IN_UBI for Flash/UBI storage.
+#endif
+
+#ifndef CONFIG_BOOTCOUNT_LIMIT

Make the following modification in recipes-bsp/u-boot/files/uboot_auto_configure.sh:

    # Make sure the environment is in MMC.
    replace_definition \
        'CONFIG_ENV_IS_(NOWHERE|IN_[^ ]*)' \
        'CONFIG_ENV_IS_IN_MMC'
    
    # Ossian: Need to have CONFIG_ENV_IS_NOWHERE defined for the UUU tool. 
    #         Mender still works as designed with this config enabled.
    add_definition \
        'CONFIG_ENV_IS_NOWHERE'
        
    add_definition \
        'CONFIG_CMD_EXT4'
    add_definition \
        'CONFIG_CMD_FS_GENERIC'
    add_definition \
        'CONFIG_MMC'
}

With these two modifications and MENDER_UBOOT_AUTO_CONFIGURE = “1” enabled u-boot should be setup to work with the UUU tool, and will continue to work as expected for Mender updates.