Belkin RT3200/Linksys E8450 WiFi AX discussion

Mhisani · April 24, 2024, 2:18pm

Thankyou both for your replies. Whilst I didn't blindly restore a config I did compare the stock configs with my config files and copied over lines where things made sense. But clever me did indeed wipe out the compat version 2.0 it seems. I went back and looked at the stock config files as I backed them up too thankfully and there it was. Therefore.. All updated and working well. Feel a bit silly!

grauerfuchs · April 24, 2024, 2:24pm

No worries! We all make mistakes, and it's all too easy to overlook something when you're in a rush. As long as things worked out all right in the end, it's all good.

Yorper · April 25, 2024, 3:56am

Well it’s taken about 3 weeks… I’ve now had the time to recover my e8450. No issues with recovery and device running as good as before.

darekxan · April 25, 2024, 12:36pm

Jumped today on the same bandwagon, yet to be recovered though. No sign of life.

After 15 mins spent in freezer - boot successful.

hnyman · April 25, 2024, 2:14pm

After similar "boots after cooling in freezer" issue with my RT3200 I reflashed the fip partition (that is located inside the UBI after the new 1.1.0 installers) from the live OpenWrt to hopefully prevent further recovery needs.

darekxan · April 25, 2024, 5:18pm

Thanks for pointing me in that direction, I've recovered the device without needing to attach a serial console.

root@OpenWrt:~# ubinfo -d 0 -n 0
Volume ID:   0 (on ubi0)
Type:        static
Alignment:   1
Size:        9 LEBs (1142784 bytes, 1.0 MiB)
Data bytes:  1019796 bytes (995.8 KiB)
State:       OK
Name:        fip
Character device major/minor: 250:1

root@OpenWrt:~# ubinfo -d 0 | grep physical
Count of bad physical eraseblocks:       0
Count of reserved physical eraseblocks:  20

root@OpenWrt:~# ls -l openwrt-mediatek-mt7622-linksys_e8450-ubi-bl31-uboot.fip
-rw-r--r--    1 root     root       1012564 Apr 25 19:08 openwrt-mediatek-mt7622-linksys_e8450-ubi-bl31-uboot.fip

root@OpenWrt:~# md5sum openwrt-mediatek-mt7622-linksys_e8450-ubi-bl31-uboot.fip 
74438e269be0c03049b40fdead43d6dc  openwrt-mediatek-mt7622-linksys_e8450-ubi-bl31-uboot.fip

root@OpenWrt:~# ubiupdatevol /dev/ubi0_0 openwrt-mediatek-mt7622-linksys_e8450-ubi-bl31-uboot.fip

root@OpenWrt:~# ubinfo -d 0 | grep physical
Count of bad physical eraseblocks:       0
Count of reserved physical eraseblocks:  20
root@OpenWrt:~# ubinfo -d 0 -n 0
Volume ID:   0 (on ubi0)
Type:        static
Alignment:   1
Size:        9 LEBs (1142784 bytes, 1.0 MiB)
Data bytes:  1012564 bytes (988.8 KiB)
State:       OK
Name:        fip
Character device major/minor: 250:1

Rebooted fine, without being held captive in a freezer

Yorper · April 25, 2024, 8:47pm

The freezer trick didn’t work for me… Whilst I was in the unit though I decided to remove the header and solder 3 wires in. They now come out the bottom of the case for easy access to serial if needed again in the future. You can’t even notice unless you pick the unit up and turn it over

Lynx · April 25, 2024, 9:13pm

What’s the best technical explanation for why the freezer trick works? What’s the technical problem solved and why is it solved?

Also seriously how was it discovered in the first place? The trick itself and discovery seems kinda amusing. Concerning the latter:

Dash. My router won’t boot. Did it overheat? Well, I’ll try sticking it in the freezer. Oh, by George, it works now!

grauerfuchs · April 25, 2024, 9:30pm

The best guess that I've heard regarding the freezer trick revolves around heat making it harder to read data that was poorly but still correctly written. The lower temperature coming from the freezer "may" be enough to stabilize things and/or pull the noise floor down long enough for it to correctly read the section of flash in question. However, I have yet to see any hard evidence directly and provably explaining the cause of the issue. It could all very well be a strange set of coincidences.

Even assuming the above is correct, it's only a temporary measure. The steps listed in the wiki for recovering the device are still recommended. So far, there have been multiple reports from people that have successfully used the "freezer trick" in the past, but it became less and less reliable over time until it wouldn't work at all anymore.

quarky · April 25, 2024, 10:36pm

Maybe the bootloader is configuring the spi-nand flash clock(s) too fast? Colder temp tends to work better for fast clocks due to lower resistance and therefore allowing signals to stabilize faster.

perceival · April 26, 2024, 3:13pm

I've managed to brick that otherwise decent router. Either I am doing something wrong or it is broken beyond repair. Any hints?

serial log

Connected.

F0: 102B 0000
F6: 0000 0000
V0: 0000 0000 [0001]
00: 0000 0000
BP: 0400 0041 [0000]
G0: 1190 0000
T0: 0000 02AE [000F]
Jump to BL

NOTICE:  BL2: v2.4(release):OpenWrt v2021-05-08-d2c75b21-3 (mt7622-snand-1ddr)
NOTICE:  BL2: Built : 23:34:56, Oct  7 2022
NOTICE:  SPI-NAND: FM35Q1GA (128MB)
ERROR:   BL2: Failed to load image id 3 (-2)
F0: 102B 0000
F6: 0000 0000
V0: 0000 0000 [0001]
00: 0000 0000
BP: 0400 0041 [0000]
G0: 1190 0000
T0: 0000 02AE [000F]
Jump to BL

NOTICE:  BL2: v2.4(release):OpenWrt v2021-05-08-d2c75b21-3 (mt7622-snand-1ddr)
NOTICE:  BL2: Built : 23:34:56, Oct  7 2022
NOTICE:  SPI-NAND: FM35Q1GA (128MB)
ERROR:   BL2: Failed to load image id 3 (-2)

F0: 102B 0000
F6: 0000 0000
V0: 0000 0000 [0001]
00: 0000 0000
BP: 0400 0041 [0000]
G0: 1190 0000
T0: 0000 02AE [000F]
Jump to BL

NOTICE:  BL2: v2.4(release):OpenWrt v2021-05-08-d2c75b21-3 (mt7622-snand-1ddr)
NOTICE:  BL2: Built : 23:34:56, Oct  7 2022
NOTICE:  SPI-NAND: FM35Q1GA (128MB)
ERROR:   BL2: Failed to load image id 3 (-2)

F0: 102B 0000
F1: 5000 1006
F3: 4000 0036
F5: 480A 0031
F5: 480A 0031
00: 1005 0000
F1: 5000 1006
F3: 4000 0036
F5: 480A 0031
F5: 480A 0031
01: 102A 0001
02: 1005 0000
BP: 0000 00C0 [0001]
T0: 0000 0350 [000F]
System halt!

NOTICE:  BL2: v2.4(release):516c195bf-dirty
NOTICE:  BL2: Built : 18:53:46, Feb  2 2021
INFO:    BL2: Doing platform setup
INFO:    PMIC: MediaTek MT6380 E3
INFO:    EMI: DRAMC calibration done
INFO:    EMI: Rank size auto detect
INFO:    EMI: Rank size: 0x20000000
INFO:    EMI: complex R/W mem test passed

Telnet log

> halt
target halted in Thumb state due to debug-request, current mode: Supervisor
cpsr: 0x600001f3 pc: 0x00201000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
> mww 0x10212000 0x22000000
> mt7622.cpu0 configure -work-area-phys 0x101000 -work-area-size 8096
8096
>  set cp [aarch64 mrc 15 0 1 0 0]
0xc50838
> set cp [expr {$cp & ~1}]
12912696
> aarch64 mcr 15 0 1 0 0 $cp
> reg cpsr 0x1d3
cpsr (/32): 0x000001d3
> load_image switch_mode_32_64.bin 0x100000 bin
68 bytes written at address 0x00100000
downloaded 68 bytes in 0.000995s (66.740 KiB/s)
> load_image aarch64_stall.bin 0x100100 bin
4 bytes written at address 0x00100100
downloaded 4 bytes in 0.001984s (1.969 KiB/s)
> reg pc 0x100000
pc (/64): 0x0000000000100000
> resume
mt7622.cpu0: Timeout waiting for resumex

> halt
mt7622.cpu0 halted in AArch64 state due to debug-request, current mode: EL3H
cpsr: 0x000003cd pc: 0x100100
MMU: disabled, D-Cache: disabled, I-Cache: disabled
> load_image bl2-1c.bin 0x201000 bin
46133 bytes written at address 0x00201000
downloaded 46133 bytes in 0.190049s (237.053 KiB/s)
> reg pc 0x201000
pc (/64): 0x0000000000201000
> resume
> 
> halt
mt7622.cpu0 halted in AArch64 state due to debug-request, current mode: EL3T
cpsr: 0x800002cc pc: 0x2012d8
MMU: disabled, D-Cache: disabled, I-Cache: enabled
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 2.060810s (292.193 KiB/s)
> 
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
Invalid ACK (6) in DAP response
Could not read DSCR register
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 0.995608s (604.811 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 0.970101s (620.713 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (3) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 1.014512s (593.541 KiB/s)
> 
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 0.972982s (618.875 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 2.017217s (298.507 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 0.970069s (620.733 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 1.980045s (304.111 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 0.972753s (619.021 KiB/s)
> 
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 1.995656s (301.733 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 1.955213s (307.974 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 2.294049s (262.485 KiB/s)
Invalid ACK (6) in DAP response
Polling target mt7622.cpu0 failed, trying to reexamine
mt7622.cpu0: hardware has 6 breakpoints, 4 watchpoints
mt7622.cpu0 halted in AArch64 state due to debug-request, current mode: EL3T
cpsr: 0x800002cc pc: 0x2012d8
MMU: disabled, D-Cache: disabled, I-Cache: enabled
[mt7622.cpu0] Examination succeed
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 2.324999s (258.991 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
Invalid ACK (6) in DAP response
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 0.974809s (617.715 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 2.001473s (300.856 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 2.310926s (260.568 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 0.994751s (605.332 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 0.990418s (607.980 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 1.969404s (305.755 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 1.025141s (587.387 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 1.956895s (307.709 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 0.969610s (621.027 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 1.955311s (307.958 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 0.986712s (610.263 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
Invalid ACK (6) in DAP response
Failed to write memory at 0x80810080
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 0.970590s (620.400 KiB/s)
> load_image fip-snand-no-bmt.bin 0x40020000 bin
616606 bytes written at address 0x40020000
downloaded 616606 bytes in 2.311132s (260.545 KiB/s)
> mww 0x100200 1                                
> resume
>

OpenOCD log

Open On-Chip Debugger 0.12.0+dev-00561-g0ab39cea2 (2024-04-23-05:10)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Warn : TMS/SWDIO moved to GPIO 8 (pin 24). Check the wiring please!
trst_and_srst separate srst_gates_jtag trst_push_pull srst_push_pull connect_deassert_srst
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : BCM2835 GPIO JTAG/SWD bitbang driver
Info : clock speed 7353 kHz
Info : JTAG tap: mt7622.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver: 0x4)
Info : mt7622.cpu0: hardware has 6 breakpoints, 4 watchpoints
Info : [mt7622.cpu0] Examination succeed
Info : starting gdb server for mt7622.cpu0 on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'telnet' connection on tcp/4444
	halt
mww 0x10212000 0x22000000
mt7622.cpu0 configure -work-area-phys 0x101000 -work-area-size 8096
 set cp [aarch64 mrc 15 0 1 0 0]
set cp [expr {$cp & ~1}]
aarch64 mcr 15 0 1 0 0 $cp
reg cpsr 0x1d3
load_image switch_mode_32_64.bin 0x100000 bin
Info : mt7622.cpu0 cluster 0 core 0 multi core
mt7622.cpu0 halted in AArch64 state due to debug-request, current mode: EL3T
cpsr: 0x200002cc pc: 0x2053cc
MMU: disabled, D-Cache: disabled, I-Cache: enabled
mt7622.cpu0: not 32-bit arm target
can't read "cp": no such variable
can't read "cp": no such variable
Error: Opcode 0xee100e15, DSCR.ERR=1, DSCR.EL=3
Info : Cannot reach EL 1, SPSR corrupted?

Error: Opcode 0xee100e15, DSCR.ERR=1, DSCR.EL=3
Info : Cannot reach EL 1, SPSR corrupted?

Error: DSCR_DTR_RX_FULL, dscr 0x43006313
Info : Cannot reach EL 1, SPSR corrupted?
Error: Opcode 0xd5330401, DSCR.ERR=1, DSCR.EL=3
Info : Cannot reach EL 1, SPSR corrupted?
Error: Failed to write x1 register

Error: Opcode 0xee100e15, DSCR.ERR=1, DSCR.EL=3
Info : Cannot reach EL 1, SPSR corrupted?

Error: DSCR_DTR_RX_FULL, dscr 0x43006313
Info : Cannot reach EL 1, SPSR corrupted?
Error: Opcode 0xd5330401, DSCR.ERR=1, DSCR.EL=3
Info : Cannot reach EL 1, SPSR corrupted?
Error: Failed to write x1 register

Error: Opcode 0xee100e15, DSCR.ERR=1, DSCR.EL=3
Info : Cannot reach EL 1, SPSR corrupted?

Error: Opcode 0xee100e15, DSCR.ERR=1, DSCR.EL=3
Info : Cannot reach EL 1, SPSR corrupted?

Error: DSCR_DTR_RX_FULL, dscr 0x43006313
Info : Cannot reach EL 1, SPSR corrupted?
Error: Opcode 0xd5330401, DSCR.ERR=1, DSCR.EL=3
Info : Cannot reach EL 1, SPSR corrupted?
Error: Failed to write x1 register

Error: Invalid ACK (0) in DAP response
Polling target mt7622.cpu0 failed, trying to reexamine
Error: Invalid ACK (0) in DAP response
Error: Could not initialize the APB-AP
Error: [mt7622.cpu0] Examination failed
Examination failed, GDB will be halted. Polling again in 100ms
Error: Invalid ACK (0) in DAP response
Polling target mt7622.cpu0 failed, trying to reexamine
Error: Invalid ACK (0) in DAP response
Error: Could not initialize the APB-AP
Error: [mt7622.cpu0] Examination failed
Examination failed, GDB will be halted. Polling again in 300ms
Error: Invalid ACK (0) in DAP response
Polling target mt7622.cpu0 failed, trying to reexamine
Error: Invalid ACK (0) in DAP response
Error: Could not initialize the APB-AP
Error: [mt7622.cpu0] Examination failed
Examination failed, GDB will be halted. Polling again in 700ms
Error: Invalid ACK (0) in DAP response
Polling target mt7622.cpu0 failed, trying to reexamine
Error: Invalid ACK (0) in DAP response
Error: Could not initialize the APB-AP
Error: [mt7622.cpu0] Examination failed
Examination failed, GDB will be halted. Polling again in 1500ms
Error: Invalid ACK (7) in DAP response
Polling target mt7622.cpu0 failed, trying to reexamine
Error: Debug regions are unpowered, an unexpected reset might have happened
Error: JTAG-DP STICKY ERROR
Error: Could not initialize the APB-AP
Error: [mt7622.cpu0] Examination failed
Examination failed, GDB will be halted. Polling again in 3100ms
Polling target mt7622.cpu0 failed, trying to reexamine
Info : mt7622.cpu0: hardware has 6 breakpoints, 4 watchpoints
Info : [mt7622.cpu0] Examination succeed
target halted in Thumb state due to debug-request, current mode: Supervisor
cpsr: 0x600001f3 pc: 0x00201000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
Error: mt7622.cpu0: Timeout waiting for resumex

mt7622.cpu0 halted in AArch64 state due to debug-request, current mode: EL3H
cpsr: 0x000003cd pc: 0x100100
MMU: disabled, D-Cache: disabled, I-Cache: disabled
mt7622.cpu0 halted in AArch64 state due to debug-request, current mode: EL3T
cpsr: 0x800002cc pc: 0x2012d8
MMU: disabled, D-Cache: disabled, I-Cache: enabled
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Could not read DSCR register
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (3) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Polling target mt7622.cpu0 failed, trying to reexamine
Info : mt7622.cpu0: hardware has 6 breakpoints, 4 watchpoints
mt7622.cpu0 halted in AArch64 state due to debug-request, current mode: EL3T
cpsr: 0x800002cc pc: 0x2012d8
MMU: disabled, D-Cache: disabled, I-Cache: enabled
Info : [mt7622.cpu0] Examination succeed
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080
Error: Invalid ACK (6) in DAP response
Error: Failed to write memory at 0x80810080

Update: logs synchronized and with previously missing serial console output

grauerfuchs · April 26, 2024, 3:26pm

Have you tried using the serial console with mtk_uartboot yet? JTAG can certainly get the job done, but it's far more technical and temperamental. Many people have reported extraordinary success right from the serial console thanks to the mtk_uartboot tool.

perceival · April 26, 2024, 3:33pm

Yeah, handshaking into infinity

grauerfuchs · April 26, 2024, 3:58pm

Drat. I'm far from an expert with OpenOCD, but your logs look to me like either there's an issue with the software, or the router might truly be kaput from hardware issues. It looks like you're reading the CPU ID successfully, but anything after that goes down the drain. Without a logic analyzer watching the signals to see if the problem is computer-side or device-side, this one is out of my league. Hopefully someone with significantly more experience with OpenOCD is watching this topic. My last experience on JTAG was way back on the bit-bang via parallel port days.

I know it's unlikely at this point, but is it possible you have a bad solder joint or a bridge somewhere on the JTAG pad or on the serial connector? The only reason I'm asking is to see if something might be holding one of the power, reset, or data lines and it's preventing the chip from booting far enough to respond on the UART.

perceival · April 26, 2024, 4:04pm

Good hint. Will try to reconnect everything. On the router board side I am using proper clamp but on the Raspberry pins are just inserted into the board.

FanOfOpenWRT · April 26, 2024, 10:13pm

I was stuck at handshake until I confirmed the wires were solidly in place and correctly connected, then it worked perfectly.

grauerfuchs · April 27, 2024, 12:33am

Very good point. Even I had trouble keeping a solid serial connection until I acquired a proper, matching plug for that connector. Most of the leads and clips that ship with the USB to serial adapters are designed for a wider pitch with a longer male end, so they make very poor connections to the smaller connector on this router.

ka2107 · April 27, 2024, 1:24am

Can you please provide instructions on how to do that? Is this from a normal running OpenWrt or the did you have to reboot into recovery to re-flash fip inside the UBI?

I have 2 RT3200's that do not turn ON at room temp but only after being in freezer for some time and when they are still cold.

The devices are in a remote location so I can't connect Serial wires to them, but I can ask someone to connect the RT3200 using ethernet cable to a laptop (running Windows 11 or Linux) and try to bring them back to working condition.

I can also try to reflash the OEM firmware and then try the UBI installers again (if I can do so without serial cable) if that might fix the issue. However from what I read the latest UBI installer v1.1.1 still does not have the higher drive current fix on the u-boot side.

hnyman · April 27, 2024, 4:04am

All was explained and command shown in the earlier message that I linked in the message you quoted...
And repeated in next message from darekxan who did the action himself based on my example.

iyousif · April 27, 2024, 4:45am

Mine reads like this, shall I proceed to the next command?

 -----------------------------------------------------
 OpenWrt 23.05.3, r23809-234f1a2efa
 -----------------------------------------------------
root@OpenWrt:~# ubinfo -d 0 -n 0
Volume ID:   0 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        9 LEBs (1142784 bytes, 1.0 MiB)
State:       OK
Name:        ubootenv
Character device major/minor: 249:1

Thank you for your feedback.