[?] Enabling Brume U-Boot Recovery

jeffsf · 2019-12-04T15:43:44.972Z

Does the Brume have a way to trigger a U-Boot recovery process?

I’ve tried the typical hold down the button while powering on approach and haven’t seen any changes in the LED sequence, nor any packets on either of the LAN ports or the WAN port. I’ve tried with just one cable connected.

The Ethernet ports are electrically functional as they show as link up on the connected host.

It’s soft bricked right now, so I can’t easily get any information about the U-Boot version or modify any parameters.

JCool · 2019-12-04T18:08:23.637Z

I bricked it mine trying to install a custom OpenWrt image, I was able to get in the U-Boot Web UI pressing and holding the reset button all the time, although I don’t know if it’s the right way.
Righ now I connected via serial port pressing " gl " to stop the booting.

U-Boot 2017.03-armada-17.10.2-gc5a0d2c (Sep 01 2019 - 18:20:09 +0800)

Model: GL.iNet GL-MV1000
       CPU    @ 1000 [MHz]
       L2     @ 80  [MHz]
       TClock @ 200 [MHz]
       DDR    @ 800 [MHz]
DRAM:  1 GiB
U-Boot DT blob at : 000000003f715098
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 down
MMC:   sdhci@d8000: 0, sdhci@d0000: q
SF: Detected w25q128fw with page size 256 Bytes, erase size 4 KiB, total 16 MiB
Net:
Warning: neta@30000 (eth0) using random MAC address - 66:40:17:d9:17:6e
eth0: neta@30000 [PRIME]
Hit "gl" key to stop booting in 2 seconds

jeffsf · 2019-12-04T20:27:25.262Z

On 192.168.1.1?

After holding down the button next to the MODE switch while powering on, I don’t see any evidence of “life” on any of the three Ethernet ports.

I may have to break it open and find the serial leads.

JCool · 2019-12-05T07:39:36.755Z

If none of the leds flash you probably will need serial access.
I think I found the sequence when the LED lights up:
Set your computer’s IP address to 192.168.1.2
Press and hold the Reset button and power the device
. the 3 LED will light up then
. the power LED will light up
. when WAN LED light up release the reset button, power LED and WAN LED will light up, connect the LAN cable and go to http://192.168.1.1

U-Boot 2017.03-armada-17.10.2-gc5a0d2c (Sep 01 2019 - 18:20:09 +0800)

Model: GL.iNet GL-MV1000
       CPU    @ 1000 [MHz]
       L2     @ 800 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 800 [MHz]
DRAM:  1 GiB
U-Boot DT blob at : 000000003f715098
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 down
MMC:   sdhci@d8000: 0, sdhci@d0000: 1
SF: Detected w25q128fw with page size 256 Bytes, erase size 4 KiB, total 16 MiB
Net:   
Warning: neta@30000 (eth0) using random MAC address - 06:43:50:90:dc:9d
eth0: neta@30000 [PRIME]
Reset button is pressed for:  7 HTTP server is starting at IP: 192.168.1.1
done set host addr 0xa8c0 0x101
HTTP server is ready!

alzhao · 2019-12-05T09:07:57.805Z

Hold the reset while powering on, until the middle LED light up. You will enter uboot failsafe as other routers do.

jeffsf · 2019-12-13T05:14:54.204Z

U-Boot 2017.03-armada-17.10.2-g7bd38cd-dirty (Aug 14 2019 - 17:11:54 +0800)

does not respond to holding reset while powering up. Serial indicates that it continues directly into running the bootscript and then the kernel.

Firmware was flashed through U-Boot

openwrt-gl-mv1000.bin -> openwrt-mv1000-emmc-3.027-0924.img

which reports as

 OpenWrt 19.07-SNAPSHOT, r10273-2b88d02

TIM-1.0
WTMI-armada-17.10.5-7bd38cd
WTMI: system early-init

DDR topology parameters:
========================
ddr type               DDR4
ddr speedbin           10
bus width              16-bits
cs num                 1
  cs[0] - group num    0
  cs[0] - bank num     8
  cs[0] - capacity     1024MiB
SVC REV: 5, CPU VDD voltage: 1.085V

DRAM windows:
=============
WIN[0] - base addr     0x60000000
WIN[0] - size          0x40000000

memory test region:
===================
CS[0]                  0x60000000 - 0x9fffffff

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 0x0000001F

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

DLL TUNING
==============
   DLL 0xc0001050[21:16]: [9,31,1d]
   DLL 0xc0001050[29:24]: [b,30,1d]
   DLL 0xc0001054[21:16]: [9,32,1d]
   DLL 0xc0001054[29:24]: [d,31,1f]
   DLL 0xc0001074[21:16]: [0,3f,1f]
   DLL 0xc0001074NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v1.3(debug):armada-17.10.7:7bd38cd
NOTICE:  BL1: Built : 17:12:19, Aug 14 2NOTICE:  BL2: v1.3(debug):armada-17.10.7:7bd38cd
NOTICE:  BL2: Built : 17:12:20, Aug 14 2019NOTICE:  BL31: v1.3(debug):armada-17.10.7:7bd38cd
NOTICE:  BL31:

U-Boot 2017.03-armada-17.10.2-g7bd38cd-dirty (Aug 14 2019 - 17:11:54 +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 : 000000003f71b078
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 down
MMC:   sdhci@d8000: 0, sdhci@d0000: 1
SF: Detected w25q128fw with page size 256 Bytes, erase size 4 KiB, total 16 MiB
Net:   
Warning: neta@30000 (eth0) using random MAC address - ba:f3:98:0a:50:18
eth0: neta@30000 [PRIME]
Hit any key to stop autoboot:  0 
353 bytes read in 6 ms (56.6 KiB/s)
   Running bootscript from mmc ...
## Executing script at 05000000
8834 bytes read in 6 ms (1.4 MiB/s)
7641096 bytes read in 176 ms (41.4 MiB/s)
## Flattened Device Tree blob at 04ff0000
   Booting using the fdt blob at 0x4ff0000
   Using Device Tree in place at 0000000004ff0000, end 0000000004ff5281

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.131 (zl@glinet) (gcc version 7.4.0 (OpenWrt GCC 7.4.0 r10260-04f03e7)) #0 SMP Sun Sep 15 09:52:59 2019
[    0.000000] Boot CPU: AArch64 Processor [410fd034]
[    0.000000] Machine model: GL.inet GL-MV1000 (Marvell)

rp201rp · 2019-12-13T06:34:17.607Z

not sure if you did “switch_system ubuntu”
I did that when i got my mv1000 and there was no ubuntu installed to alternate boot partition. but it did boot into a luci-gui of openwrt with 192.168.1.1 I did some reading and kept missing the option of waiting for middle light and then waiting for 3rd light to go on. when 3rd light goes on it defaults back to first Os boot of openwrt.