Looking for info and possibility of (future) support of TP-Link Omada er605 Router

This device has two sets of volumes: main ones (`kernel`, `rootfs`, etc) and 'ba…ckup' (`kernel.b`, `rootfs.b`, etc). Bootloader tries to determine which set of volumes to use by looking at contens of `extra-para` and `extra-para.b` volumes. These volumes contain JSON that looks like this: ``` { "dbootFlag": "1", "integerFlag": "1", "fwFlag": "GOOD", "score":1 } ``` It looks like the bootloader looks for `"fwFlag": "GOOD"` (as opposed to `BAD`) then it compares `score` field - whichever 'good' volume has bigger score wins. This determines which set of volumes to use to boot. So for example if `extra-para` is good and has bigger score then `kernel`, `rootfs`, etc volumes are used. This means bootloader needs to explain to the kernel which volume to use for the rootfs. After looking at bootloader code with disassembler I think it contains a bug. Relevant part of code looks something like this: ``` if (image_id == 0) { rootfs_volume_id = 8; rootfs_volume_name = "rootfs"; } else { rootfs_volume_id = 0xf; rootfs_volume_name = "rootfs.b"; } sprintf( &buffer, 0x800, "console=ttyS0,115200 noinitrd ubi.mtd=3,2048 ubi.block=0,%s root=/dev/ubiblock0_%d DKMGT_IMAGE_ID=%d DKMGT_IMAGE_TYPE=ubi", rootfs_volume_name, rootfs_volume_id, image_id ); ``` Where `image_id == 0` if 'normal' (not '*.b' set of volumes is used). However from device dumps we know that from the factory `rootfs.b` has id 8 and `rootfs` has id 15. So from above we can see that ids and names of rootfs volumes do not match. More over - they are hardcoded in the bootloader. Both things are problematic for OpwnWRT which completely removes volumes on update meaning that volume ids may actually change. So instead of relying on bootloader to provide the kernel with root device this patch forces kernel to determine root automatically - and it defaults to `rootfs` volume which is correct for our purposes. Overall this makes image boot fine from flash after sysupgrade from inirams. assuming `extra-para*` volumes make bootloader use non-'*.b' set of volumes. Signed-off-by: Nikolay Martynov <mar.kolya@gmail.com>

and

github.com/openwrt/openwrt

ramips: Fix boot volume selection for TPLink ER605 v2

openwrt:master ← mar-kolya:tp-link-er605-v2-fix-boot-volume-selection-pr

opened 01:52AM - 09 Jan 23 UTC

mar-kolya

+63 -0

TPLink ER605 v2 uses two ubi volumes: `extra-para` and `extra-para.b` to determi…ne which set of volumes to use for booting. OpenWrt doesn't really support this concept of 'backup' volumes. So in order to avoid selecting wrog set of volumes this patch makes `sysupgrade` process update `extra-para` and `extra-para.b` to force useage of 'first' set of volumes regardless of previous state.

OranguTech · January 16, 2023, 11:12pm

Thanks Everyone for the work that's been accomplished so far.

My understanding is we don't have much traction for v1 hardware yet, correct?

I'm new to building OpenWRT and hardware support, so I'll state/ask again:

What steps, if any, would be valuable for moving that along? I have an unused, unupgraded (will need to check the version), v1 ready to go, I (should) have the ability to root login and UART connect, I just need a bit of orientation/pointing in the right direction. (Full image dump? Partition layout, etc.)

mojolacerator2 · January 18, 2023, 2:09pm

How do we get past this to a working image?

hecatae · January 18, 2023, 2:39pm

If you login as root does the above work to give UBI partition information on all partitions?

Klingon · January 18, 2023, 2:59pm

Here you have the info Looking for info and possibility of (future) support of TP-Link Omada er605 Router - #59 by Klingon

hecatae · January 18, 2023, 3:01pm

@Klingon is that the V2 as @OranguTech is asking about the V1, which is what this thread was originally about.

Klingon · January 18, 2023, 4:09pm

My device is a V2, not a V1. The info shown is for an V2.

Klingon · January 19, 2023, 7:30am

In the thread there is no specification whether V1 or V2, is about ER605

hecatae · January 19, 2023, 9:06am

Because when the thread began, V2 did not exist.

Klingon · January 19, 2023, 10:57am

And what do you suggest, create another thread for V2?

hecatae · January 19, 2023, 12:45pm

No Idea, I was replying to @OranguTech when you started replying to me.

Klingon · January 19, 2023, 3:58pm

That's true!!

OranguTech · January 21, 2023, 8:16am

I now have an mtd_backup of a 99% stock v1.0/1.6 (running Firmware 1.1.1).

Let me know if anyone needs a copy or some other command/output.

root@ER605:~# uname -a
Linux ER605 3.10.108 #1 SMP Fri Jul 23 17:56:17 CST 2021 mips GNU/Linux

cat /proc/cpuinfo
system type             : MT7621
machine                 : Unknown
processor               : 0
cpu model               : MIPS 1004Kc V2.15
BogoMIPS                : 583.68
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 32
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa                     : mips1 mips2 mips32r1 mips32r2
ASEs implemented        : mips16 dsp mt
shadow register sets    : 1
kscratch registers      : 0
core                    : 0
VPE                     : 0
VCED exceptions         : not available
VCEI exceptions         : not available

processor               : 1
cpu model               : MIPS 1004Kc V2.15
BogoMIPS                : 583.68
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 32
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa                     : mips1 mips2 mips32r1 mips32r2
ASEs implemented        : mips16 dsp mt
shadow register sets    : 1
kscratch registers      : 0
core                    : 0
VPE                     : 1
VCED exceptions         : not available
VCEI exceptions         : not available

processor               : 2
cpu model               : MIPS 1004Kc V2.15
BogoMIPS                : 583.68
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 32
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa                     : mips1 mips2 mips32r1 mips32r2
ASEs implemented        : mips16 dsp mt
shadow register sets    : 1
kscratch registers      : 0
core                    : 1
VPE                     : 0
VCED exceptions         : not available
VCEI exceptions         : not available

processor               : 3
cpu model               : MIPS 1004Kc V2.15
BogoMIPS                : 583.68
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 32
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa                     : mips1 mips2 mips32r1 mips32r2
ASEs implemented        : mips16 dsp mt
shadow register sets    : 1
kscratch registers      : 0
core                    : 1
VPE                     : 1
VCED exceptions         : not available
VCEI exceptions         : not available

===
cat /proc/partitions
major minor  #blocks  name

  31        0        256 mtdblock0
  31        1        192 mtdblock1
  31        2         64 mtdblock2
  31        3       1536 mtdblock3
  31        4      12224 mtdblock4
  31        5        128 mtdblock5
  31        6         64 mtdblock6
  31        7         64 mtdblock7
  31        8         64 mtdblock8
  31        9         64 mtdblock9
  31       10         64 mtdblock10
  31       11        128 mtdblock11
  31       12       1536 mtdblock12
  31       13      16384 mtdblock13
  
  ===
  
  root@ER605:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00040000 00010000 "bootloader"
mtd1: 00030000 00010000 "bootloader-fs"
mtd2: 00010000 00010000 "extra-para"
mtd3: 00180000 00010000 "kernel"
mtd4: 00bf0000 00010000 "rootfs"
mtd5: 00020000 00010000 "panic-oops"
mtd6: 00010000 00010000 "partition-table"
mtd7: 00010000 00010000 "device-info"
mtd8: 00010000 00010000 "support-list"
mtd9: 00010000 00010000 "firmware-info"
mtd10: 00010000 00010000 "tddp"
mtd11: 00020000 00010000 "log"
mtd12: 00180000 00010000 "rootfs_data"
mtd13: 01000000 00010000 "firmware"

cat /proc/version
Linux version 3.10.108 (jenkins_router@sohoilinuxbuild) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 unknown) ) #1 SMP Fri Jul 23 17:56:17 CST 2021

hecatae · January 21, 2023, 1:14pm

what do you see from ubinfo -a

TMTRTLP · January 21, 2023, 11:08pm

Well I'm probably not going to be much help but this is what I get when I run that command on my V1.6.

root@ER605:~# ubinfo -a
-ash: ubinfo: not found