I have a weird situation right now that I thought I'd reach out and see if anyone has an idea what is wrong here. I have an AM3517 SOM where the MLO and u-boot are stored in NAND. I have the AM3517 Eval Kit and my own custom hardware. On the Eval Kit, u-boot will start up and start doing the autoboot countdown. On my custom hardware, the autoboot countdown never starts and u-boot just drops into the command line and therefore cannot autoboot. The ONLY difference between these two is the hardware, and I've already ruled out the boot strapping pins as the cause. They are identical (EMAC, USB, MMC1, NAND so SYS_BOOT 5,2,0 = 0b110). There is no SD card installed in either device as well and all of the u-boot environment variables are stored in NAND, so there isn't some conflict with the bootdelay variable which is currently set to 10 seconds.
I am using the ti-u-boot. The MLO I am using is based off of the 2015.04 branch and the u-boot I am using is based off of the 2016.05 branch. Again, this is the same module with the same MLO and u-boot in NAND, but different hardware. Is there anywhere a hardware difference could cause u-boot to stop autobooting before the autoboot countdown even comes up?
