SmartServer IoT doesn't boot up, stuck in U-Boot prompt (KB1387)   

We have seen some cases in which the SmartServer may constantly reboot in the U-boot prompt or never complete booting up. This may be due to corruption in the SmartServer environmental variables or software corruption. 

On older SmartServer IoT software versions (2.41 and 2.50), or upgrading from an older software version to newer software we have seen a couple of cases in which the SmartServer doesn't boot up properly.  The SmartServer appears to constantly reboot. You shouldn't see this upgrade issue with SmartServer 2.61+ though we have seen some issues downgrading to older versions.

When the SmartServer constantly reboots in the U-boot prompt you can't access the SmartServer CMS and may have problems accessing the SmartServer configuration Web page.

For example, if you connect to the SmartServer serial console and see the following messages due to constant rebooting then you will need to run the workaround below.

U-Boot 2015.04 (Aug 08 2018 - 02:20:16)
CPU:   Freescale i.MX6DL rev1.3 at 792 MHz
CPU:   Temperature 34 C
Reset cause: WDOG
Board: Echelon Lumewave Apollo 2
Boot Device: SPI-NOR
I2C:   ready
DRAM:  2 GiB
PMIC:  PFUZE100 ID=0x10
SF: Detected MX25L3205D with page size 256 Bytes, erase size 64 KiB, total 4 MiB
In:    serial
Out:   serial
Err:   serial
Normal Boot



You will need to stop the constant rebooting process by accessing the SmartServer console port and pressing any key on the keyboard (for example, the space key) when prompted with "Hit any key to stop autoboot".


You must use a Linux PC or a second SmartServer (used as a host SmartServer running minicom) to stop the boot process in the U-boot prompt. Window PC can't be used as its USB driver does not connect fast enough to the SmartServer console to allow you to press any key.

After you have stopped the problem SmartServer in the U-boot prompt,  you can try and fix it or re-image it.


1. Stop the boot process temporarily in the U-boot prompt using the problem SmartServer console port.

  - See KB1437 on how to use a second SmartServer as a host SmartServer.  

  - press any key when you see "Hit any key to stop autoboot", and make sure stays in the U-boot prompt.

2. Re-save the environmental variable

env default -a

The Smartserver will automatically boot up after a short period of time.

3. Try to re-image the SmartServer from the U-boot prompt

    - see KB1438 for details



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk