correct .. you can flash back and forth at will, using the respective webui's and .img files
correct .. the uboot functionality is part of the firmware, its always there and accessible, the glinet-uboot-scr package merely provides this same functionality in openwrt, to put it simple, this allows you to flash from oem to openwrt using uboot, and recover via uboot using an openwrt image. Without this package, you must use the webui or sysupgrade via cli to upgrade to openwrt. And if you need to use uboot for recovery, you would have to use the oem file, so in other words, revert to oem in uboot, and then use webui to reflash to openwrt.
with that, the glinet-uboot-scr package is included by default, so you have all the functionally as above
@Hostle What kind of throughput are you seeing on your latest build? My GL-B3000 does 650 Mbit/s (ie. capped by upstream) on the GL.iNet ROM, but varies wildly on OpenWRT.
I see around 650-700 on 5Ghz under ideal contiions ..topped out. Seems to be about the average rate so far. Some report 450-600 but i consistently run right around 600
Thank you so much for your work on this device, and for keeping the PR alive and up-to-date.
I've used your dev branch to build a custom image, and everything seems to work fine.
However, when I try to upgrade the image using sysupgrade and the factory image (sysupgrade -v -n /tmp/openwrt-qualcommax-ipq50xx-glinet_gl-b3000-squashfs-factory.img), I have the following error:
Validating Firmware ... [ OK ]
fit-main: Firmware is Valid: fit
fit-main: Upgrading Firmware via [ FIT IMAGE ]
fit: Extract [ FIT IMAGE ] -x-x-> [ ubi.bin ] ... /lib/upgrade/do_stage2: line 112: dumpimage: not found
Looking at the /lib/upgrade/platform.sh file, I guess I should use a different image which would be detected as a sysupgrade-tar one: does it mean I should generate a openwrt-qualcommax-ipq50xx-glinet_gl-b3000-squashfs-sysupgrade.bin file to use it with sysupgrade?
seems you're missing the dumpimage package or the reference to it. can you post the output of the following
cat /lib/upgrade/platform.sh
and the output of this aswell
apk info dumpimage
EDIT
Ok so its my bad, i never included it in platform.sh in the dev repo. You'll need to edit the line at the top of platform.sh to include dumpimage like so.
/lib/upgrade/platform.sh
line 4: RAMFS_COPY_BIN='fw_printenv fw_setenv head'
add dumpimage like this
line 4: RAMFS_COPY_BIN='dumpimage fw_printenv fw_setenv head'
save and exit, then rerun the update and it should update fine.
I have fixed it and pushed it to the dev repo already, but you'll need to fix it manually as above OR just use uboot to upgrade after you make a fresh image.You need to do a pull from the repo to get the fix first before recompiling new image to flash
Is it possible to wipe off completely the custom GLiNET firmware and ONLY install that OpenWRT build? Or do they have to run alongside another as it's with factory default?
not sure what you mean here? when openwrt is installed, the oem is wiped. And vice versa when oem is installed. They are 2 totally separate firmware's.
As for the repo, thats my development branch. Its updated every night to stay inline with main. Then support for gl-b3000 and gl-x2000 patched on top on the fresh main.
If you are looking for the pr for the b3000 only, simply use that branch "add_glinet_gl-b3000_support" or just apply it as a patch to what ever tree you wish.
As of latest commits to thye pr, the uboot script is now included, and no external package is needed. That means, the pr can be built directly without cherry picking the glinet-uboot-scr package.
I had noticed that your branch was not up-to-date with the PR, and I tried adding dumpimage. I then stopped when I had an error about a /tmp/firmware.bin missing file. I realize now that it was the expected name of the update file, I have left a comment on your PR for this.