You definitely need the 12v adapter to get the console to work. Now that I have it the UBoot image is starting and reporting issues with the onboard image load. I have not added any USB or micro-sd cards to the device at this point. I was just trying to follow the “Getting Started” information prior to adding or performing any activities. If you look at the information below you will see the errors.
Booting Trusted Firmware
BL1: v1.2(release):armada-17.02.0:
BL1: Built : 17:28:05, May 18 2NOTICE: BL2: v1.2(release):armada-17.02.0:
NOTICE: BL2: Built : 17:28:06, May 18 20NOTICE: BL31: v1.2(release):armada-17.02.0:
NOTICE: BL31:
U-Boot 2015.01-armada-17.02.0-g48dc978 (May 18 2017 – 17:28:01)
I2C: ready
DRAM: 1 GiB
Board: DB-88F3720-ESPRESSOBin
CPU @ 1000 [MHz]
L2 @ 800 [MHz]
TClock @ 200 [MHz]
DDR @ 800 [MHz]
Comphy-0: PEX0 2.5 Gbps
Comphy-1: USB3 5 Gbps
Comphy-2: SATA0 5 Gbps
Now running in RAM – U-Boot at: 3ff2b000
U-Boot DT blob at : 000000003fa18168
MMC: XENON-SDHCI: 0
SF: Detected W25Q32DW with page size 256 Bytes, erase size 4 KiB, total 4 MiB
PCIE-0: Link down
SCSI: SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
flags: ncq led only pmp fbss pio slum part sxs
Net: neta0
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
Card did not respond to voltage select!
** Bad device mmc 0 **
Card did not respond to voltage select!
** Bad device mmc 0 **
Bad Linux ARM64 Image magic!
Marvell>>
Can the internal firmware image be reloaded?
