Bootloop after update to 6.4.3 (again and again and again and ......)

MOX hardware [CZ]
1

I reported bootloop after updating to 5.3.6 here Bootloop after update to 5.3.6 (again). Same after update to 6.0.1 .

Today i tried to update to fresh 6.4.3, same story.
Wtf is going on with this hardware? Realy not any succesful update possible?

I realy have to setup the whole system every single time you put an update online?
It’s the worst experience i’ve ever had with hardware. I have held children’s toys in my hands that are more stable than a turris mox.

Come on guys, can’t you do it better?

Here is the log from UART:
CZ.NIC’s Armada 3720 Secure Firmware v2021.09.07 (Sep 7 2021 18:16:52)
Running on Turris MOX
Initializing DDR… done
NOTICE: Booting Trusted Firmware
NOTICE: BL1: v2.5(release):v2.5-396-gb3fa4e461
NOTICE: BL1: Built : 18:17:49, Sep 7 2021
NOTICE: BL1: Booting BL2
NOTICE: BL2: v2.5(release):v2.5-396-gb3fa4e461
NOTICE: BL2: Built : 18:17:50, Sep 7 2021
NOTICE: BL1: Booting BL31
NOTICE: BL31: v2.5(release):v2.5-396-gb3fa4e461
NOTICE: BL31: Built : 18:17:53, Sep 7 2021

U-Boot 2021.10-rc3-00050-g7d3fea2c7f (Sep 07 2021 - 18:16:56 +0200)

DRAM: 1 GiB
WDT: Started with servicing (60s timeout)
Comphy chip #0:
Comphy-0: SGMII1 3.125 Gbps
Comphy-1: PEX0 5 Gbps
Comphy-2: USB3_HOST0 5 Gbps
PCIE-0: Link up
MMC: sdhci@d8000: 0
Loading Environment from SPIFlash… SF: Detected w25q64dw with page size 256 Bytes, erase size 4 KiB, total 8 MiB
OK
Model: CZ.NIC Turris Mox Board
Net: eth0: neta@30000
Turris Mox:
Board version: 22
RAM size: 1024 MiB
Serial Number: 12345…
ECDSA Public Key: xyz…
SD/eMMC version: SD
Module Topology:
1: Mini-PCIe Module
2: Peridot Switch Module (8-port)
3: Topaz Switch Module (4-port)

Hit any key to stop autoboot: 2 1 0
gpio: pin GPIO221 (gpio 57) value is 0
gpio: pin GPIO220 (gpio 56) value is 1
SF: Detected w25q64dw with page size 256 Bytes, erase size 4 KiB, total 8 MiB
device 0 offset 0x7f0000, size 0x10000
SF: 65536 bytes @ 0x7f0000 Read: OK
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1…
Found U-Boot script /boot.scr
2455 bytes read in 96 ms (24.4 KiB/s)

Executing script at 04d00000

20499 bytes read in 102 ms (195.3 KiB/s)
crc32 for 04100000 … 041d062f ==> 4b6c6c83
word at 0x04effff8 (0x836c6c4b) != word at 0x04effffc (0xff325d6a)
Total of 0 word(s) were the same
14221320 bytes read in 747 ms (18.2 MiB/s)

Flattened Device Tree blob at 04f00000

Booting using the fdt blob at 0x4f00000
Loading Device Tree to 000000003faf5000, end 000000003fafd012 … OK

Starting kernel …

“Synchronous Abort” handler, esr 0x96000040
elr: ffffffffc5cfd024 lr : 0000000000003234 (reloc)
elr: 0000000005c10024 lr : 000000003ff16234
x0 : eb00005f910262a0 x1 : 0000000000000428
x2 : 0000000000000000 x3 : 0000000000000428
x4 : 000000003ffe4d48 x5 : 0000000000000001
x6 : 0000000000000008 x7 : 0000000000000000
x8 : 0000000005000000 x9 : 0000000000000002
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 000000003faf8fff
x14: 000000003faf5000 x15: 000000003ff14f84
x16: 000000003ff5a230 x17: 0000000000000000
x18: 000000003fb02dc0 x19: 000000003ffe3f80
x20: 0000000000000000 x21: 0000000000000400
x22: 0000000000000003 x23: 000000003fbfbc18
x24: 000000003fbfbc18 x25: 000000003ffcdae8
x26: 0000000000000000 x27: 000000003ff1625c
x28: 000000003fbfbc40 x29: 000000003fafe480

Code: f900c460 8b020023 b4000060 91372264 (f9000404)
Resetting CPU …

resetting …

CZ.NIC’s Armada 3720 Secure Firmware v2021.09.07 (Sep 7 2021 18:16:52)
Running on Turris MOX
Initializing DDR… done
NOTICE: Booting Trusted Firmware
NOTICE: BL1: v2.5(release):v2.5-396-gb3fa4e461
NOTICE: BL1: Built : 18:17:49, Sep 7 2021
NOTICE: BL1: Booting BL2
NOTICE: BL2: v2.5(release):v2.5-396-gb3fa4e461
NOTICE: BL2: Built : 18:17:50, Sep 7 2021
NOTICE: BL1: Booting BL31
NOTICE: BL31: v2.5(release):v2.5-396-gb3fa4e461
NOTICE: BL31: Built : 18:17:53, Sep 7 2021

U-Boot 2021.10-rc3-00050-g7d3fea2c7f (Sep 07 2021 - 18:16:56 +0200)

DRAM: 1 GiB
WDT: Started with servicing (60s timeout)
Comphy chip #0:
Comphy-0: SGMII1 3.125 Gbps
Comphy-1: PEX0 5 Gbps
Comphy-2: USB3_HOST0 5 Gbps
PCIE-0: Link up
MMC: sdhci@d8000: 0
Loading Environment from SPIFlash… SF: Detected w25q64dw with page size 256 Bytes, erase size 4 KiB, total 8 MiB
OK
Model: CZ.NIC Turris Mox Board
Net: eth0: neta@30000
Turris Mox:
Board version: 22
RAM size: 1024 MiB
Serial Number: 12345…
ECDSA Public Key: xyz…
SD/eMMC version: SD
Module Topology:
1: Mini-PCIe Module
2: Peridot Switch Module (8-port)
3: Topaz Switch Module (4-port)

Hit any key to stop autoboot: 2 1 0
gpio: pin GPIO221 (gpio 57) value is 0
gpio: pin GPIO220 (gpio 56) value is 1
SF: Detected w25q64dw with page size 256 Bytes, erase size 4 KiB, total 8 MiB
device 0 offset 0x7f0000, size 0x10000
SF: 65536 bytes @ 0x7f0000 Read: OK
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1…
Found U-Boot script /boot.scr
2455 bytes read in 89 ms (26.4 KiB/s)

Executing script at 04d00000

20499 bytes read in 102 ms (195.3 KiB/s)
crc32 for 04100000 … 041d062f ==> 4b6c6c83
word at 0x04effff8 (0x836c6c4b) != word at 0x04effffc (0xff325d6a)
Total of 0 word(s) were the same
14221320 bytes read in 730 ms (18.6 MiB/s)

Flattened Device Tree blob at 04f00000

Booting using the fdt blob at 0x4f00000
Loading Device Tree to 000000003faf5000, end 000000003fafd012 … OK

Starting kernel …

“Synchronous Abort” handler, esr 0x96000040
elr: ffffffffc5cfd024 lr : 0000000000003234 (reloc)
elr: 0000000005c10024 lr : 000000003ff16234
x0 : eb00005f910262a0 x1 : 0000000000000428
x2 : 0000000000000000 x3 : 0000000000000428
x4 : 000000003ffe4d48 x5 : 0000000000000001
x6 : 0000000000000008 x7 : 0000000000000000
x8 : 0000000005000000 x9 : 0000000000000002
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 000000003faf8fff
x14: 000000003faf5000 x15: 000000003ff14f84
x16: 000000003ff5a230 x17: 0000000000000000
x18: 000000003fb02dc0 x19: 000000003ffe3f80
x20: 0000000000000000 x21: 0000000000000400
x22: 0000000000000003 x23: 000000003fbfbc18
x24: 000000003fbfbc18 x25: 000000003ffcdae8
x26: 0000000000000000 x27: 000000003ff1625c
x28: 000000003fbfbc40 x29: 000000003fafe480

Code: f900c460 8b020023 b4000060 91372264 (f9000404)
Resetting CPU …

resetting …

and again … and again …

2

Are you running a recent bootloader version? You may try

opkg update
opkg install turris-nor-update
nor-update
3

=> version
U-Boot 2021.10-rc3-00050-g7d3fea2c7f (Sep 07 2021 - 18:16:56 +0200)

aarch64-unknown-linux-gnu-gcc (Gentoo Hardened 10.3.0-r2 p3) 10.3.0
GNU ld (Gentoo 2.36.1 p5) 2.36.1

Don’t know if that version matches “recent”.

4

:rofl: Best comment of the day!

1 Like
6

I don’t agree. There are some problems, but it’s in many cases useful solution.

7
off topic / MOX usability

Turris MOX (configuration ABD) is a working and usable solution for (WiFi 6) access points if you are fine with DIY-modding. Even though it is not really cheaper than Turris Omnia while at the same time far less powerful and user friendly. So if one can get a cheap TO on eBay or here in the market place, better go for this option (in case you need a TOS based access point).

The advertised adaptability fails in my eyes just like the material (ugly plastic)/inappropriate design (for passive cooling) and the other options (SDIO WiFi, nextcloud hub, switch,…). But everyone fit in doing basic calculations should be aware of that when looking at the hardware specs, which allow no more than basic functionality.

But all in all I second Victor’s opinion this time. You (CZ.NIC) shouldn’t advertise what you cannot comply with.

@Dr.D.Bakel : better open a gitlab issue or write Turris support directly. That way you get real help - complaints in this forum seldom get you any further.

1 Like
8

Strange, i just updated the bootloader via usb (uart / ymodem doesn’t work for me) and the device just start without any problem,

=> version
U-Boot 2022.07 (Aug 15 2022 - 12:25:08 +0000), Build: jenkins-turris-os-packages5

aarch64-openwrt-linux-musl-gcc (OpenWrt GCC 8.4.0 r16627+119-b93327c469) 8.4.0
GNU ld (GNU Binutils) 2.34

9

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.