Difference between revisions of "Marvell EBU:Armada 38x"

From eLinux.org
Jump to: navigation, search
(Add a38x-ap recovery steps)
 
m (Armada-38x-AP)
Line 1: Line 1:
=== Armada-38x-AP ===
 
 
 
==== Recovery ====
 
==== Recovery ====
  

Revision as of 06:17, 17 July 2018

Recovery

Users that have messed up with the NAND storage can face an empty console after a reboot, meaning that a recovery is now needed.

Two situations: either the BootROM finds something and runs a bootloader (probably U-Boot) that fails to reach the command prompt; or the BootROM will loop over a few NAND blocks, try to boot from each of them and finally give up and display a message like "Trying UART".

Note: While the UART-to-USB FTDI chip is wired on UART1, the BootROM only interacts on UART0. Both UARTs are available on the top side of the board through two horizontal 3-pin male headers, the one directer towards the mini-USB connector is UART1.

Once connected on the right UART, one should send (at 115200b) the xmodem boot pattern (0xbb 0x11 0x22 0x33 0x44 0x55 0x66 0x77) right after resetting the SoC. Then "NACK" characters should be sent by the BootROM (one per second). This means that the BootROM is ready to receive a recovery image (a U-Boot image flagged "-uart.bin" at the end) that it will load in RAM and run. The loading is achieved by the sx-at91 binary. Once in a "live" U-Boot, one can burn another one with the bubt command.