The November 14th glinet_gl-ar300m-nand images do not include these changes and should not be flashed at this time.
If you want "release" images, you will likely need to wait for "20.01" as the SPI-NAND drivers depend on Linux 4.19 and later, as well as that 19.07 "has left the dock" at this time.
NB: The glinet_gl-ar750s-nor-nand-squashfs-factory.img cannot be flashed with U-Boot at this time.
The glinet_gl-ar750s-nor-squashfs-sysupgrade.bin "NOR" images can be flashed through U-Boot.
- Do not use "force" with
sysupgrade-- If need be, use "serial-less" U-Boot to flash, see below
- The OEM config is not directly compatible with the OpenWrt config. Preserving config is not recommended when upgrading from OEM firmware.
- NOR boot can be selected by
fw_setenv bootcount 3
NAND boot can be selected by
fw_setenv bootcount 0
Flashing with U-Boot does not seem to "automatically" change the boot mode.
See also https://docs.gl-inet.com/en/2/hardware/ar300m/#using-firmware
From a NOR-based image on a device with NAND flash
(See later section for the GL-AR300M16, GL-AR300M-Lite, and other GL-AR300M-series devices without NAND)
Flash the NAND-aware, NOR-resident image first
sysupgradeshould work in most cases with the -sysupgrade.bin image (do not "force")
When running the new NAND-aware, NOR-resident image, you can then
sysupgradeto the NAND-aware, NAND image
From an OEM image on GL-AR300M that has NAND flash
- Use U-Boot to flash glinet_gl-ar300m-nand-squashfs-factory.img using the "NAND Firmware" option -- Serial is not required, see https://docs.gl-inet.com/en/3/troubleshooting/debrick/
NB: If your GL-AR300M U-Boot does not have an option of NOR vs. NAND firmware presented
At this time please flash glinet_gl-ar300m-nor-squashfs-sysupgrade.bin and
sysupgradeto the NAND version, if desired.
From an OEM image on GL-AR750S
- Use U-Boot to flash glinet_gl-ar750s-nor-squashfs-sysupgrade.bin using the "NOR Firmware" option (if given a choice) -- Serial is not required, see https://docs.gl-inet.com/en/3/troubleshooting/debrick/
sysupgrademay then be used to flash glinet_gl-ar750s-nor-nand-squashfs-sysupgrade.bin
For GL-AR300M16, GL-AR300M-Lite, and other GL-AR300M devices without NAND flash
NB: These two images do not yet include [OpenWrt-Devel] ath79: fix merge/rebase omission for GL-AR300M16 and GL-AR300M-Lite
- There (shortly will be) ath79 images for both of these that do not include the NAND-aware kernel and UBI utilities.
WARNING – Do not upgrade pre-November 15, 2019 versions of ath79 firmware directly to GL-AR300M (NAND) images
Versions of ath79 firmware for the GL-AR300M prior to November 15, 2019 are not capable of reliably upgrading directly to the new GL-AR300M (NAND) images.
Upgrade with U-Boot in these cases is recommended. U-Boot can be accessed without a serial connection. See https://docs.gl-inet.com/en/3/troubleshooting/debrick/
Direct upgrades may result in the device unexpectedly booting into the “old” NAND-resident system and its configuration. If this is a “stock” OEM system, its default LAN IP is 192.168.8.1.
If the NAND-resident system fails to boot, use U-Boot to install a fresh image.
What is "GL-AR750S (NOR/NAND)" and glinet_gl-ar750s-nor-nand?
The GL-AR750S boots its kernel off NOR flash, even when NAND is used for the file systems. This is how the OEM firmware behaves as well. The plain "NAND" name was reserved in case someone writes a new boot loader that boots the kernel from NAND flash.
Commits of interest: