[U-Boot] Question regarding MLO size

[Arun Bharadwaj]

Hi all,

I am using a Gumstix Overo (omap3), running the u-boot v2015.04 and have
the following issue:

I have made a few modifications to the misc_init_r() routine in the
board/overo/overo.c file; the resulting MLO file is 61,220 bytes and the
console hangs at "reading u-boot.img" during the boot process. In the
absence of those changes to the misc_init_r() the MLO size is 61,212 bytes
and the u-boot is loaded without any issues.

misc_init_r() is not even called from any SPL related code, so I am not
sure why changes to this routine is causing MLO size to change. I verified
this by doing the following: I put a few debug statements in misc_init_r()
and rebuilt both u-boot.img and MLO. First, I replaced only the new MLO in
my target and the debug statement did not appear while it appeared when I
replaced the u-boot.img in the target.

If anybody has an idea what is going on, it would be very helpful. Thanks!

FYI: The change I am trying to make in misc_init_r() :
@@ -295,6 +295,7 @@ int misc_init_r(void)
                        expansion_config.fab_revision);
                MUX_GUMSTIX();
                setenv("defaultdisplay", "lcd35");
+               setenv("expansionname", "palo35");
                break;
        case GUMSTIX_PALO43:
                printf("Recognized Palo43 expansion board (rev %d %s)\n",


-Arun