My GL-AR300M has a very old Firmware on the NOR flash (2.7) and the latest on the NAND side. However, sometime it is booting the NOR flash.
Now I wanted to update the NOR flash. To do this, I first tried to update uboot with the bin file uboot-gl-ar300m-20220216-md5-97ff7bb80cbf129fa21f34ded1559ff8.bin from github. Unfortunately, I tried this on the normal update page (http://192.168.1.1/).
Nevertheless, I can still reach the uboot update page, even the http://192.168.1.1/uboot.html page. However, I I now try to update with the above named file (downloaded as raw) I get the message: " UPDATE FAILED Something went wrong during updateProbably you have chosen wrong file (too big or too small) or you were trying to update ART on device with unknown FLASH type (and size) which is not allowed. Please, try again or contact with the author of this modification. You can also get more information during update in U-Boot console."
Please, what can I do to update uboot and get the device running with latest firmware on each flash memory?
PS: Device can still boot up, at least on NAND flash.
The switch button in disabled is NAND in the default, even you have not upgrade the uboot, the older uboot does not support the switch button, and it supposed to NAND boot in the default.
Hello,
Thank you for your support!
I have the GL-AR300M-ext. A pretty old (or early) version. I used exactly the uboot file, you propose. I downloaded it as raw, several times - no change. I use a windows 11 PC. Used both ethernet ports (a USB and an internal one). I also reduced MTU. No change.
Any other ideas, please?
May try to login the ssh and enter the following instructions, note your uboot is not the latest version, probably it does not take effect, but just try. If not take effect, it also will not have any impact.
##Enable
fw_printenv
fw_setenv boot_dev on
reboot
##Reset to default
fw_printenv
fw_setenv boot_dev
reboot
By default, uboot boot-up the firmware of the NAND first, and if it fails, then it boot-up the NOR.
thanks for the hint. I believe that NAND has preference. What I encounter is, that maybe 1 out of three times it boots from NOR, using V2.7 which is really annoying. Why it is behaving like this, I don't know. I don't observe any crashes or instabilities on either system.
I would really prefer to update uboot, if I knew how? TFTP Server would be no problem. Would I need UART access? If I manage to open the case, I can do this, too.
However, simply using the uboot menu would be great, it just won't let me ...
Would booting from NOR, flashing openwrt, booting again from NOR and updating to latest gl-inet firmware with luci be a painless option?
I read it on the forum.
Direct update from gl-inet firmware to later gl-inet version does not seem possible, too
I tried to flash old versions of uboot from the github link you gave me.
Up to five years old, since this was slightly smaller. However, so success. The webGUI of uboot keeps complaining.
There is a tool in OpenWrt that used to be shipped with GL iNet firmware called mtd but was missing in 4.7.8 firmware. It can write data to the partitions on the mtd device. Looking at my ar300m, here is the layout of my mtd device:
