It might have accidentally unplugged while was booting up.
u - boot >> boot
The AP hangs at the u-boot and doesn't proceed. It will fail as it can't find the recovery image.
Showing the environment variables and the faulty bootcmd.
u - boot >> printenv BOOT = part1 CASset = max ENABLE_BREAK = 1 FACTORY_RESET = 0 MALLOC_len = 5 MANUAL_BOOT = 0 MEMORY_DEBUG = 0 MPmode = SMP autoload = yes baudrate = 9600 bootcmd = boardinit <<<<< bootdelay = 3 bootfile = board_init_barbados2k . img cacheShare = no disaMvPnp = no eeeEnable = no enaClockGating = no enaCpuStream = no enaFPU = yes enaMonExt = no enaWrAllo = no eth1addr = 00 : 50 : 43 : xx : xx : xx eth1mtu = 1500 eth2addr = 00 : 50 : 43 : xx : xx : xx eth2mtu = 1500 ethact = egiga2 ethaddr = 00 : 50 : 43 : xx : xx : xx ethmtu = 1500 ethprime = egiga2 image_name = part . bin initrd_high = 0xffffffff limit_dram_size = yes loadaddr = 0x02000000 loads_echo = 0 mtddevname = fs mtdids = nand0 = armada - nand mtdparts = mtdparts = armada - nand : 1m ( oops ), 1m ( reserved ),-( fs ) nandEcc = nfcConfig = 4bitecc netretry = yes partition = nand0 , 2 pcieTune = no pexMode = RC stderr = serial stdin = serial stdout = serial yuk_ethaddr = 00 : 00 : 00 : xx : xx : xx Environment size : 894 / 65532 bytes
Correcting the false bootcmd and saving and rebooting.
u - boot >> setenv bootcmd nandboot u - boot >> saveenv u - boot >> boot
This info was found on some website. Don't remember where, but it helped in a similar case.
... View more