Thanks, but isn't the FR365 the exact same hardware as the ER706W? If so why two separate OpenWrt projects? If not, what are the differences?
Only someone who owns them can answer that question.
yup got openwrt working on the ER706W iām pretty sure you can revert it via uboot.
No partition changes in it.
I agree but the commit has 2 extra partitions they are not in the gpl code of either the er706w or the fr365. id say the flash ram wont take it at least in the er706w. wifi needs the kmod-mt76 driver as well.
for a commit its lacking and should give boot loops.
I think they are the same atleast going by the source code.
if you can get uboot going try.
mtd list.
im guessing no panic oops and no log recovery partitions. (i copyed my mtd partitions with uboot and a hex calculator)
see how you go those partitions are in the er605
Hi,
Iām thinking of buying this router, and Iāve just learnt it is (kind of) supported by OpenWrt.
What I canāt find any information about is that if the SFP port is supported also. I plan to use a TP-SM331T to get another wan/lan port.
Any hints?
I finally bought this router and the SFP module. 
I've gained serial access, backed up all partitions, and flashed the latest FR365 firmware (25.12.2). Everything is working properly, including the SFP port.
However, there is a cosmetic (?) error: it says the device is an FR365, not an ER706w (no surprise...).
- Does this matter at all?
- What should be done in order to display the correct board name?
- What should be done in order to list this router as supported in the ToH?
However, there is a cosmetic (?) error: it says the device is an FR365, not an ER706w (no surprise...).
-
Does this matter at all?
Donāt think so.
-
What should be done in order to display the correct board name?
Edit the FR365 files from the fr365 addition to openwrt here is where to look. https://git.openwrt.org/openwrt/openwrt/commit/?id=e507398b88322a69417de47b94942ab53dae4603
-
What should be done in order to list this router as supported in the ToH?
I stuck with factory mtd so i edited the dts file the FR365 has 2 extra Partitions than the TP Link ER706w and renamed it. No errors in mine displays ER706W where it should.
Whether that is enough to add it to the toh or keep it as a variation of the FR365.
frollic should know.
I can't find any difference in the partition scheme.
This is the mtd list in the factory u-boot console.
mtd list
MT7981>
List of MTD devices:
* spi-nand0
- device: spi_nand@0
- parent: spi@1100a000
- driver: spi_nand
- path: /spi@1100a000/spi_nand@0
- type: NAND flash
- block size: 0x20000 bytes
- min I/O: 0x800 bytes
- OOB size: 64 bytes
- OOB available: 24 bytes
- 0x000000000000-0x000008000000 : "spi-nand0"
* nmbm0
- type: Unknown
- block size: 0x20000 bytes
- min I/O: 0x800 bytes
- OOB size: 64 bytes
- OOB available: 24 bytes
- 0x000000000000-0x000007c00000 : "nmbm0"
- 0x000000000000-0x000000100000 : "bl2"
- 0x000000100000-0x000000180000 : "u-boot-env"
- 0x000000180000-0x000000380000 : "factory"
- 0x000000380000-0x000000580000 : "fip"
- 0x000000580000-0x000002980000 : "ubi"
- 0x000002980000-0x000004d80000 : "ubi.b"
- 0x000004d80000-0x000004da0000 : "support-list"
- 0x000004da0000-0x0000057a0000 : "user-config"
- 0x0000057a0000-0x0000057c0000 : "partition-table"
- 0x0000057c0000-0x0000057e0000 : "device-info"
- 0x0000057e0000-0x000005800000 : "device-info.b"
- 0x000005800000-0x000005820000 : "tddp"
- 0x000005820000-0x000005840000 : "tddp.b"
- 0x000005840000-0x000005a40000 : "extra-para-ubi"
- 0x000005a40000-0x000005a60000 : "firmware-info"
- 0x000005a60000-0x000005a80000 : "firmware-info.b"
- 0x000005a80000-0x000005c80000 : "log"
- 0x000005c80000-0x000005e80000 : "log.b"
- 0x000005e80000-0x000006380000 : "wlan"
- 0x000006380000-0x000006880000 : "wlan.b"
- 0x000006880000-0x000007980000 : "database"
- 0x000007980000-0x000007a00000 : "log_recovery"
- 0x000007a00000-0x000007a80000 : "panic-oops"
MT7981>
The last two partitions are not referenced in mtd9 (partition-table). This partition is read during the boot process.
disk size
"disk-size": "0x08000000",
"partition-table": [{
"name": "BL2",
"base": "0x00000000",
"size": "0x00100000",
"attr": "0x11111111"
}, {
"name": "u-boot-env",
"base": "0x00100000",
"size": "0x00080000",
"attr": "0x44444444"
}, {
"name": "Factory",
"base": "0x00180000",
"size": "0x00200000",
"attr": "0x55555555"
}, {
"name": "FIP",
"base": "0x00380000",
"size": "0x00200000",
"attr": "0x66666666"
}, {
"name": "ubi",
"base": "0x00580000",
"size": "0x02400000",
"attr": "0x77777777"
}, {
"name": "ubi.b",
"base": "0x02980000",
"size": "0x02400000",
"attr": "0x88888888"
}, {
"name": "support-list",
"base": "0x04D80000",
"size": "0x00020000",
"attr": "0x99999999"
}, {
"name": "user-config",
"base": "0x04DA0000",
"size": "0x00A00000",
"attr": "0xAAAAAAAA"
}, {
"name": "partition-table",
"base": "0x057A0000",
"size": "0x00020000",
"attr": "0xAAAAAAAB"
}, {
"name": "device-info",
"base": "0x057C0000",
"size": "0x00020000",
"attr": "0xAAAAAAAC"
}, {
"name": "device-info.b",
"base": "0x057E0000",
"size": "0x00020000",
"attr": "0xAAAAAAAD"
}, {
"name": "tddp",
"base": "0x05800000",
"size": "0x00020000",
"attr": "0xAAAAAAAE"
}, {
"name": "tddp.b",
"base": "0x05820000",
"size": "0x00020000",
"attr": "0xAAAAAAAF"
}, {
"name": "extra-para-ubi",
"base": "0x05840000",
"size": "0x00200000",
"attr": "0xAAAAAABA"
}, {
"name": "firmware-info",
"base": "0x05A40000",
"size": "0x00020000",
"attr": "0xAAAAAADA"
}, {
"name": "firmware-info.b",
"base": "0x05A60000",
"size": "0x00020000",
"attr": "0xAAAAAAEA"
}, {
"name": "wlan",
"base": "0x05E80000",
"size": "0x00500000",
"attr": "0xAAAAACAA"
}, {
"name": "wlan.b",
"base": "0x06380000",
"size": "0x00500000",
"attr": "0xAAAAADAA"
}, {
"name": "database",
"base": "0x06880000",
"size": "0x01100000",
"attr": "0xAAACADAA"
}]
}
But I think it only means that these partitions are not in use in any way (even by the factory firmware).
The board name really seems to be a cosmetic error, it doesn't affect the operation of ER706W, everything is working properly for a week now.
I'm pretty sure it's dual boot. My device has been updated from factory firmware 1.21 -> 1.28, and the *.b partitions contain the old firmware. I just don't know how to select A/B boot sources.
Another interesting thing: the mtd7 / support-list partition contains a list of devices as follows:
support-list
"support-list":[
{"model_name": "ER706W", "model_version": "1.0", "special_id": "55530000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.0", "special_id": "43410000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.0", "special_id": "45550000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.0", "special_id": "00000000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.20", "special_id": "55530000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.20", "special_id": "43410000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.20", "special_id": "45550000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.20", "special_id": "00000000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.20", "special_id": "4B520000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.20", "special_id": "45470000", "flash_version": "00000000"},
{"model_name": "Festa FR365", "model_version": "1.0", "special_id": "55530000", "flash_version": "00000000"},
{"model_name": "Festa FR365", "model_version": "1.0", "special_id": "43410000", "flash_version": "00000000"},
{"model_name": "Festa FR365", "model_version": "1.0", "special_id": "45550000", "flash_version": "00000000"},
{"model_name": "Festa FR365", "model_version": "1.20", "special_id": "55530000", "flash_version": "00000000"},
{"model_name": "Festa FR365", "model_version": "1.20", "special_id": "43410000", "flash_version": "00000000"},
{"model_name": "Festa FR365", "model_version": "1.20", "special_id": "45550000", "flash_version": "00000000"},
{"model_name": "Festa FR365", "model_version": "1.20", "special_id": "45470000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.0", "special_id": "45550000", "flash_version": "00000001"},
{"model_name": "ER706W", "model_version": "1.20", "special_id": "45550000", "flash_version": "00000001"},
{"model_name": "ER706W", "model_version": "1.20", "special_id": "45470000", "flash_version": "00000001"},
{"model_name": "ER706W", "model_version": "1.30", "special_id": "45470000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.30", "special_id": "55530000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.30", "special_id": "43410000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.30", "special_id": "45550000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.30", "special_id": "00000000", "flash_version": "00000000"},
{"model_name": "ER706W", "model_version": "1.30", "special_id": "4B520000", "flash_version": "00000000"},
{"model_name": "Festa FR365", "model_version": "1.0", "special_id": "45550000", "flash_version": "00000001"},
{"model_name": "Festa FR365", "model_version": "1.20", "special_id": "45550000", "flash_version": "00000001"},
{"model_name": "Festa FR365", "model_version": "1.20", "special_id": "45470000", "flash_version": "00000001"}
I don't know the purpose of this list, but the two device (FR365 and ER706W) seem to be very closely related. Maybe the firmwares are the same, and some kind of hardware id shows which one is the current device.