Jump to content

Recommended Posts

Posted

I purchased a V7 version of ebin
But after updating uboot, the reboot is still in stock uboot.

Marvell>> bubt flash-image-1g-1cs-1000_800.bin spi usb
Burning U-BOOT image "flash-image-1g-1cs-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... 1 USB Device(s) found
scanning bus 1 for devices... 2 USB Device(s) found
reading flash-image-1g-1cs-1000_800.bin
Image checksum...OK!
SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB
262144 bytes written, 593344 bytes skipped in 2.65s, speed 424017 B/s
Done!
Marvell>> TIM-1.0
TIM-1.0
TIM-1.0
WTMI-armada-17.10.5-bb8f823
WTMI: system early-init
SVC REV: 4, CPU VDD voltage: 1.120V

Fill memory before self refresh...done

Now in Self-refresh Mode
Exited self-refresh ...


Self refresh Pass.
DDR self test mode test done!!
Vref read training
===================
Final vdac_value 0x00000020

Vref write training
===================
Final vref_value 0x0000001F

DLL TUNING
==============
   DLL 0xc0001050[21:16]: [8,35,1e]
   DLL 0xc0001050[29:24]: [8,2b,19]
   DLL 0xc0001054[21:16]: [b,31,1e]
   DLL 0xc0001054[29:24]: [e,30,1f]
   DLL 0xc0001074[21:16]: [0,3f,1f]
   DLL 0xc0001074NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v1.3(release):armada-17.10.3:39a62a1
NOTICE:  BL1: Built : 15:40:57, Jun  1 2NOTICE:  BL2: v1.3(release):armada-17.10.3:39a62a1
NOTICE:  BL2: Built : 15:40:59, Jun  1 201NOTICE:  BL31: v1.3(release):armada-17.10.3:39a62a1
NOTICE:  BL31:

U-Boot 2017.03-armada-17.10.2-g14aeedc (Jun 01 2018 - 15:39:10 +0800)

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

5bbf40e79a3be.jpg

5bbf40f54eff6.jpg

Posted
3 hours ago, nasbdh9 said:

U-Boot 2017.03-armada-17.10.2-g14aeedc (Jun 01 2018 - 15:39:10 +0800)

 

Your u-boot was not provided by Armbian - you can convince yourself by comparing it to the ones in the Archive (yours was compiled on June 1st, in timezone GMT +8 ...).

 

Your EspressoBin is equipped with a Macronix SPI - if you need to rescue it start from here or here.

Posted
1 hour ago, ebin-dev said:

Your EspressoBin is equipped with a Macronix SPI


Last u-boot builds should have support for Macronix OOTB, right? 

Posted
22 minutes ago, Igor said:

Last u-boot builds should have support for Macronix OOTB, right? 

 

That's what I tested, but to be completely sure I'll check the test logs I published in the other thread to make sure the printed build date got updated.

 

If the flashed file turns out to be Armbian's, my only theory is that the factory bootloader recognises the Macronix chip but somehow fails to update its contents (so that the factory bootloader remains unchanged).

 

That could be fixed by reflashing from an UART-downloaded image.

Posted
1 hour ago, Igor said:

Last u-boot builds should have support for Macronix OOTB, right?  

 

  Yes - it was confirmed at least by FoodGenius in the parallel thread (see here - below the EDIT).

Posted

Yeah, I also got versions/dates like the ones here after I successfully flashed via UART download + bubt:

TIM-1.0
WTMI-devel-18.07.0-6050fd5
WTMI: system early-init
SVC REV: 5, CPU VDD voltage: 1.155V
NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v1.5(release):711ecd3 (Marvell-armada-18.09.4)
NOTICE:  BL1: Built : 15:13:47, Sep  7 2018
NOTICE:  BL1: Booting BL2
NOTICE:  BL2: v1.5(release):711ecd3 (Marvell-armada-18.09.4)
NOTICE:  BL2: Built : 15:13:50, Sep  7 2018
NOTICE:  BL1: Booting BL31
NOTICE:  BL31: v1.5(release):711ecd3 (Marvell-armada-18.09.4)
NOTICE:  BL31: Built : 15:1

U-Boot 2017.03-armada-18.09.1-ga92bd86-armbian (Sep 05 2018 - 21:49:34 +0200)

Model: Marvell Armada 3720 Community Board ESPRESSOBin
       CPU     1000 [MHz]
       L2      1000 [MHz]
       NB AXI  250 [MHz]
       SB AXI  250 [MHz]
       DDR     800 [MHz]
DRAM:  2 GiB
U-Boot DT blob at : 000000007f7142d8
Comphy chip #0:
Comphy-0: USB3          5 Gbps    
Comphy-1: PEX0          2.5 Gbps  
Comphy-2: SATA0         6 Gbps    
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 
PCIE-0: Link up
MMC:   sdhci@d0000: 0
SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB
Net:   eth0: neta@30000 [PRIME]
Hit any key to stop autoboot:  0 
Marvell>> 

 

Posted
32 minutes ago, ebin-dev said:

@nasbdh9 It would appear that your 1g-1cs EspressoBin (V7_0-2) is equipped with DDR4 RAM. Could you post an image of the RAM chip ?

 

5bc313d3caef0.jpg

 

Samsung K4A8G165WB-BCRC

Posted

There are some nice upgrades in this v7 board design, like the new SATA connector. However the FW image is based on old Marvell 17.10 LSP. Since the new DDR4 layout is only included in Globalscale in-house FW images, the official Marvell LSP has no support for the new DDDR4 layouts yet. Marvell asked Globalscale team to upgrade their base to 18.09. If it happens, it will be much easier to add these new layouts to the official LSP and to the mainline sources.

FYI - the A3700 support pull request is under review @ TF-A right now. Once it gets merged, you will be able to try the new TF-A v2.0. Unfortunately this PR code supports only DDR3-based EspressoBin for now. 

Posted

I also have a ESPRESSObin v7 board, but I can't find any OS image to use for even basic testing. Does anyone know where I can get this? GlobalScale is not responding to emails. 

Posted

GlobalScale has published some stuff for the V7 EspressoBin here and here (based on the version 17.x bootloader). May be that is useful for you.

 

Armbian uses the 18.x branch of the bootloader and the environment settings are adapted to it.

Updated sources of the 18.x bootloader with support for the V7 EspressoBin are expected to be published by Marvell some time soon and updated versions of Armbian and the corresponding bootloader images for V7 EspressoBins will follow.

 

Posted

Yes, I noticed that. I have the board up with their rootfs on 4.4.52 so I can at least test some things. 

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines