For EFR32MG21 also firmware with Thread support is needed: https://github.com/openthread/ot-efr32
If anyone would like to check Bluetooth operation for MX4200, I wrote something about it here: OpenWrt support for Linksys MX4200 - #363 by lytr
1 Like
These can be used further for Open Thread support on this chip.
I am able to switch the chip to programming mode, connect via ser2net and read the memory via dk6prog:
dk6prog -b PYSERIAL -d /dev/ttyMSM1 info
This is an experimental utility. Use with caution!
ERROR:spsdk.dk6.driver:Selected backend does not have method for ISP sequence (62ms since start, driver.py:147)
Chip ID: 0x88888888
ROM Version: 0x140000cc
MAC Address: xx:xx:xx:xx:xx:xx:15:00
Detected DEVICE: K32W041
Memory Memory ID Base Address Length Sector Size Memory Type Access
----------------------------------------------------------------------------------------------
FLASH 0 0x0 0x9de00 0x200 FLASH All is available
PSECT 1 0x0 0x1e0 0x10 FLASH All is available
pFLASH 2 0x0 0x1e0 0x10 FLASH All is available
Config 3 0x9fc00 0x200 0x200 FLASH All is available
EFUSE 4 0x0 0x80 0x2 EFUSE (OTP) Write Enabled
ROM 5 0x3000000 0x20000 0x1 ROM Write Enabled
RAM0 6 0x4000000 0x16000 0x1 RAM Write Enabled
RAM1 7 0x4020000 0x10000 0x1 RAM Write Enabled
1 Like
I paid more for my single one than you paid for 3. Hopefully some of the woot buyers will find their way here.
so i tried flashing the latest 24.10 and the nss fork onto my 8500 and it appears that neither works.
there's clearly a panic happening and it resets 3 times and got back to stock fw.
i am too lazy to take it apart at this moment to get serial, any insight would be helpful
Can confirm that 24.10 works fine and never had to use serial.
Are you doing it this way? [OpenWrt Wiki] Linksys MX8500 installation
Just wanted to share some input here. I'm a fellow Woot purchaser and an OpenWRT newbie. I used the latest NSS build from this repository, but I had trouble getting the WAN port to work—my fault for not reading the guide. Be sure to follow the installation guide on the page—Steps 5 and 13 are crucial if the WAN port isn't working.
It's not necessary for testing, but if you want to update the firmware without losing your configuration settings, you'll need to flash both partitions. So far, I've flashed 2 out of the 3—just need to get the last one done.
1 Like
Be sure to follow the installation guide on the page—Steps 5 and 13 are crucial if the WAN port isn't working.
Step 5 (updating OEM firmware) does not actually do anything and has been removed. Step 12 (formerly 13) is required for the WAN port to work.
I've also added a part 3 section to update the AQR firmware but it has been some time since I have done it, so please give some feedback or edit the wiki if you've recently done this.
2 Likes
I flashed my own build first that probably messed up the partition since my own build was too big to fit in the correct kernel size for some reason; reflashed stock and nss build over it now we are all good!
i didnt do anything besides adding aq_load_fw to bootenv and it just works
i guess its only needed if you want more up to date fw with no clear indication of what is being changed by the AQR guys.
I ordered 3 sets of MX8500 from the woot sale. I flashed 4 so far and they all required updating the AQR firmware to get the 5gbe port to work at all.
Possibly Linksys made changes to the AQR firmware in uboot even though it apparently doesn't use the uboot firmware through the product's life. I did notice in the picture you posted earlier your routers have the new Linksys logo while all of mine have the old Linksys logo so your units likely have a later production date.
You can check what AQR firmware version is on the partition by checking the checksum:
sha256sum /dev/mtd26
3677ba4ca7b3e09d7605d762c91d353f98df590650f55f9fae0d4bff178e4049 *v5.4.B
4e11bbbc1bf25460ef696d0fc43bce7a5a5fd34bd84ff899890409df0bce1d0d *v5.5.B
0e0374d3824c925ebcdc7e8be39d2348083acbd16f69c6f9a029513d6c45c8d5 *v5.5.F
737119ef56264c94fb9ca2a7da5530faae2525664f03252c02ecfc2f5806caaa *v5.6.5
2 Likes
sha256sum /dev/mtd26
3677ba4ca7b3e09d7605d762c91d353f98df590650f55f9fae0d4bff178e4049 /dev/mtd26
huh, weird that it just works then
it does come with the last stock fw dk if that rly says anything
you really do know everything there is to know about this device
Updated https://openwrt.org/toh/linksys/mx8500 with more detailed instructions on installing AQR firmware.
Thanks @atomsho045 @lytr @OpenWRT-fanboy for correcting and clarifying the installation steps and that there's differences in stock OEM firmware and some routers already have AQR firmware installed and some don't.
1 Like
Okay I got around to doing some more testing and my issue is that the old firmware is somehow incompatible with my ISP's ONT. If you don't have any compatibility issues you probably don't need to flash to the latest AQR firmware.
MX8500 with freshly installed openwrt and modified uboot shows
sha256sum /dev/mtd26
3677ba4ca7b3e09d7605d762c91d353f98df590650f55f9fae0d4bff178e4049
So firmware v5.4.B
Connecting MX8500 directly to ONT throws the following message on serial
ONT<--->MX8500(old AQR firmware)
Aquantia AQR114C 90000.mdio-1:08: Downshift occurred from negotiated speed 1Gbps to actual speed 100Mbps, check cabling!
nss-dp 3a007000.dp6-syn wan: PHY Link up speed: 100
Cannot ping out. But if I connect a MX8500 with new AQR firmware in between like:
ONT<--->MX8500(new AQR firmware)<--->MX8500(old AQR firmware)
The downshift message no longer pops and I can ping out on MX8500 with the old firmware. So the old AQR firmware technically works, it's just doesn't play nice with my ONT. Whatever changes were made in the new AQR firmware fixed it.
Hi @BrainSlayer,
According to DD-WRT :: View topic - Freshly Flashed MX8500 Issues, dd-wrt is able to load the AQR firmware from kernel, which openwrt can't do. Do you happen to know why?
Maybe this will help. It's for the MR7500 but it's the same WAN interface:
https://svn.dd-wrt.com/changeset/59402
I bricked my router after " modify the router's U-Boot bootloader to load the Marvell AQR firmware before booting OpenWrt." and reboot. can anyone help me recover it? I have a serial ttl adapter and can open the router.