[espressobin latest u-boot bricks board]

@ebin-dev confirmed the new image works great. Thanks again! 

[espressobin latest u-boot bricks board]

@ebin-dev, @Rainbaby Many thanks. I will try to flash the new image tonight and update this thread on how it goes.

[espressobin latest u-boot bricks board]

After further experimentation, I am able to flash the flash-image-ddr4-1g-2cs-1000_800.bin image and everything is back to normal, though I am restricted to 1GiB of RAM. Interesting since the official 2g image from espressobin.net works fine 

[espressobin latest u-boot bricks board]

I just got a new espressobin v7 with 2gb of ram. Output from working u-boot:

U-Boot 2017.03-armada-17.10.2-g255b9cc (Nov 07 2018 - 09:48:30 +0800)

Model: Marvell Armada 3720 Community Board ESPRESSOBin
       CPU    @ 1000 [MHz]
       L2     @ 800 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 800 [MHz]
DRAM:  2 GiB
U-Boot DT blob at : 000000007f7161b8
Comphy-0: USB3          5 Gbps
Comphy-1: PEX0          2.5 Gbps
Comphy-2: SATA0         6 Gbps

...

Marvell>> sspi
SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB

Marvell>> version

U-Boot 2017.03-armada-17.10.2-g255b9cc (Nov 07 2018 - 09:48:30 +0800)
aarch64-linux-gnu-gcc (Linaro GCC 5.3-2016.05) 5.3.1 20160412
GNU ld (Linaro_Binutils-2016.05) 2.25.0 Linaro 2016_02

I'm trying to update to the latest u-boot version from here https://dl.armbian.com/espressobin/u-boot/  flash-image-ddr4-2g-2cs-1000_800.bin

 

Marvell>> bubt flash-image-ddr4-2g-2cs-1000_800.bin spi usb
Burning U-BOOT image "flash-image-ddr4-2g-2cs-1000_800.bin" from "usb" to "spi"
USB0:   Register 2000104 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB1:   USB EHCI 1.00
scanning bus 0 for devices... ** First descriptor is NOT a primary desc on 0:1 **
2 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
Image checksum...OK!
823492 bytes written, 65536 bytes skipped in 7.538s, speed 120754 B/s
Done!

So everything seems to go ok. From here, I reset the board and I get nothing at all. No serial console, nothing. I need to go into uart just to get any kind of a sign that the board is still alive. From uart I can recover using the following image from http://espressobin.net/tech-spec/ (U-Boot 2017.03-armada-17.10):

espressobin-bootloader-cpu-1000-ddr4-2cs-2g-atf-g39a62a1-uboot-g255b9cc-20181107-REL.bin

which brings me back to the initial state at the start of this post. Any ideas why flashing the latest u-boot image from armbian seems to completely bricks my board?

 

Thanks!