IPQ5018: GLiNET B3000 info

Hostle · 2025-02-04T14:41:13.012Z

shi05275:

Thanks for your work, can you provide me the address of your repo? I am also working on running vanilla openwrt on GL-B3000, but I encountered some problems. Maybe your work can reduce a lot of my repetitive work. Thanks again.

I haven't pushed anything since 6.6.54, just haven't had the time. The pr is ready, I'm just waiting for the initial add 5018 target pr to go through, then I'll send it

MiguelOlmos · 2025-02-04T14:55:39.503Z

Yeah, my mistake, tried to flash the zip, need to take my coffee before try to play with firmwares...

Hostle · 2025-02-04T14:57:24.311Z

MiguelOlmos:

take my coffee before try to play with firmwares

the first rule of any sensible programming

MiguelOlmos · 2025-02-05T08:04:53.607Z

Hey there, it's me again, not sure if is just me, they are working great after flash all of them, now is way more stable, but I have problems with the DHCP server, it just give IPs for 5 hours and after acts like a dumb AP

slh · 2025-02-06T15:30:21.586Z

Hostle:

I've been really busy and haven't had time to prep the pr. I think ipq50xx has now been officially merged.

Now it's show time:

github.com/openwrt/openwrt

qualcommax: add ipq50xx target

committed 08:51AM - 06 Feb 25 UTC

georgemoussalem

+13689 -1

Introduce support for the Qualcomm IPQ50xx SoC. This series adds support for the… following components: - minimal boot support: GCC/pinctrl/watchdog/CPUFreq/SDI (upstreamed) - USB2 (upstreamed) - Thermal/Tsens - PCIe gen2 1&2-lane PHY and controller - PWM and PWM LED - QPIC SPI NAND controller - CMN PLL Block (provider of fixed rate clocks to GCC/ethernet/more.) - Ethernet: IPQ5018 Internal GE PHY (1 gbps) - Remoteproc MPD driver for IPQ5018 (2.4G) & QCN6122 (5/6G) Wifi Co-developed-by: Ziyang Huang <hzyitc@outlook.com> Signed-off-by: Ziyang Huang <hzyitc@outlook.com> Signed-off-by: George Moussalem <george.moussalem@outlook.com> Link: https://github.com/openwrt/openwrt/pull/17182 Signed-off-by: Robert Marko <robimarko@gmail.com>

github.com/openwrt/openwrt

qualcommax: ipq50xx: add support for Linksys MX2000 and MX5500

committed 08:51AM - 06 Feb 25 UTC

georgemoussalem

+1072 -0

Add support for Linksys MX2000 (Atlas 6) and MX5500 (Atlas 6 Pro). These devices… are completely identical except for the secondary wifi chip used for 5Ghz: QCN6102 is used on MX2000 while QCN9024 is used on MX5500 Speficiations: * SoC: Qualcomm IPQ5018 (64-bit dual-core ARM Cortex-A53 @ 1.0Ghz) * Memory: Winbond W634GU6NB-11 (512 MiB DDR3-933) * Serial Port: 3v3 TTL 115200n8 * Wi-Fi: IPQ5018 (2x2 2.4 Ghz 802.11b/g/n/ax) * Wi-Fi: MX2000: QCN6102 (2x2:2 5 Ghz 802.11an/ac/ax) MX5500: QCN9024 (4x4:4 5 Ghz 802.11an/ac/ax) * Ethernet: IPQ5018 integrated virtual switch connected to an external QCA8337 switch (4 Ports 10/100/1000 GBASE-T) * Flash: Macronix MX35UF2GE4AD (256 MiB) * LEDs: 1x multi-color PWM LED * Buttons: 1x WPS (GPIO 27 Active Low) 1x Reset (GPIO 28 Acive Low) Flash instructions (in case of MX2000, else replace with MX5500 images): 1. On OEM firmware, login to the device (typically at http://192.168.1.1) and click 'CA' in the bottom right corner -> Connectivity -> Manual Upgrade. Alternatively, browse to http://<router IP>/fwupdate.html. Upgrade firmware using openwrt-qualcommax-ipq50xx-linksys_mx2000-squashfs-factory.bin image. Optionally install on second partition, after first boot check actual partition: fw_printenv -n boot_part and install firmware on second partition using command in case of 2: mtd -r -e kernel -n write openwrt-qualcommax-ipq50xx-linksys_mx2000-squashfs-factory.bin kernel and in case of 1: mtd -r -e alt_kernel -n write openwrt-qualcommax-ipq50xx-linksys_mx2000-squashfs-factory.bin alt_kernel 2. Installation using serial connection from OEM firmware (default login: root, password: admin): fw_printenv -n boot_part In case of 2: flash_erase /dev/mtd12 0 0 nandwrite -p /dev/mtd12 openwrt-qualcommax-ipq50xx-linksys_mx2000-squashfs-factory.bin or in case of 1: flash_erase /dev/mtd14 0 0 nandwrite -p /dev/mtd14 openwrt-qualcommax-ipq50xx-linksys_mx2000-squashfs-factory.bin After first boot install firmware on second partition: mtd -r -e kernel -n write openwrt-qualcommax-ipq50xx-linksys_mx2000-squashfs-factory.bin kernel or: mtd -r -e alt_kernel -n write openwrt-qualcommax-ipq50xx-linksys_mx2000-squashfs-factory.bin alt_kernel 3. Back to the OEM firmware. Download firmware from OEM website: MX2000: https://support.linksys.com/kb/article/585-en/ MX5500: https://support.linksys.com/kb/article/587-en/ From serial or SSH: fw_printenv boot_part in case of 1: mtd -r -e alt_kernel -n write FW_MX2000_1.1.7.210469_prod.img alt_kernel else in case of 2: mtd -r -e kernel -n write FW_MX2000_1.1.7.210469_prod.img kernel Signed-off-by: George Moussalem <george.moussalem@outlook.com> Link: https://github.com/openwrt/openwrt/pull/17182 Signed-off-by: Robert Marko <robimarko@gmail.com>

Hostle · 2025-02-06T18:04:59.166Z

yes i received a message informing me of the good news. Great work @georgem83 , @hzyitc and everyone who made this possible.

I just have one last thing to work out,

Hostle:

I need to come up with a clean solution to the glinet image check... in short the glinet upgrade check for supported devices = b3000. Openwrt uses a slightly different format glinet,gl-B3000. So i have to check for both board names in multiple places, ontop of that the supported devices param only allow for 1 device, so that require having 2 sets of bdfs for ipq-wifi, one for gl-b3000 and another set for b3000 ... its icky.

I think the final solution is to make a proper .bin file and flash from luci via glinet --> advanced settings but i haven't had much time to go over it lately. I will figure something out by the time the pr is necessary. For the time being I will just host the .img file for 6.6.54 and remove the ickyness from 6.6.72 for the most part.

Currently, i have for the most part solved this issue.

Hostle:

ontop of that the supported devices param only allow for 1 device

this is incorrect, or at least as of 6.6.74, I simply added the second entry "b3000" and the glinet stock firmware upgrade now will accept it, furthermore, openwrt uses the first entry "glinet_gl-b3000" (or board-name), in turn ipq-wifi then correctly identifies the board bdfs and all is well.

The only issue i see with this approach is that 3 different image types are generated in the build. An .img file, .ubi file, and sysupgrade tar. The .img file is only used for the initial switch to openwrt. Generally, the sysupgrade tar is used to upgrade moving forward.However, in some cases ( in development anyway) a .ubi or .bin file was needed to reflect all changes, depending on the type of change ie board bdf's or changes to ath11k script etc. As mention, the .ubi can be used in these occasions, but to the best of my knowledge, a ubi file cannot have metadata attached. This results in having to use the force option, which imo seems incomplete.

So my question is, should i do something in the makefile, that would allow to build the .img file for the initial upgrade. And a second option for the sysupgrade and ubi.

which bring me to the final question, is the .ubi even needed ?

define Device/glinet_gl-b3000
  $(call Device/FitImage)
  DEVICE_VENDOR := GL.iNET
  DEVICE_MODEL := GL-B3000
  BLOCKSIZE := 128k
  PAGESIZE := 2048
  SOC := ipq5018
  DEVICE_DTS_CONFIG := config@mp03.5-c1
  SUPPORTED_DEVICES:=glinet,gl-b3000, b3000
  UBINIZE_OPTS := -E 5
  IMAGES := sysupgrade.tar nand-factory.img factory.ubi
  IMAGE/sysupgrade.tar := sysupgrade-tar | append-metadata
  IMAGE/nand-factory.img := append-ubi | qsdk-ipq-factory-nand | append-metadata
  IMAGE/factory.ubi := append-ubi
  DEVICE_PACKAGES := ath11k-firmware-qcn6122 ipq-wifi-glinet_gl-b3000
endef
TARGET_DEVICES += glinet_gl-b3000

hecatae · 2025-02-06T19:10:29.192Z

@brada4 @frollic @NC1 thoughts?

bluewavenet · 2025-02-06T19:10:59.814Z

Well done and thanks for all your hard work on this!

Hostle:

I have not tried to flash the openwrt .img file using uboot, I suspect it would fail the partition check as the wifi partition is not present,

You may remember our brief discussions in this thread last November.

All current official Openwrt firmwares for Gl-inet routers can be flashed from the uboot web-ui. Currently this one will be the exception. (unless you added this and I missed it)

If I remember correctly, you had excluded uboot web-ui flashing because in your opinion it should only be used for recovery.

I assume this was to simplify the early development phase.
Now is probably the time to revisit this, as currently "recovering" back to stock firmware will be the only option for most users for a soft brick situation, something many people will want to avoid.

There are other reasons/uses for uboot web-ui flashing of official Openwrt. One that I mentioned is, for example, roll out of a number of devices in say a mesh network where the uboot web-ui is a much more efficient method allowing batch re-flashing. This is currently doable with every other gl-inet router.

Hostle · 2025-02-06T19:31:09.650Z

as i have said before ..uboot webui works as usual. And again, I see no advantage to what you are suggesting as it still requires the img file, regardless of how you decided to apply it.

bluewavenet · 2025-02-06T19:39:21.757Z

Hostle:

uboot webui works as usual

Then, as usual, I can use uboot web-ui to flash the sysupgrade.bin, as I can for all other gl-inet routers? None of them use a factory.img.

Hostle:

I see no advantage to what you are suggesting

Unlike all the other developers that have worked on porting gl-inet devices to OpenWrt.

Hostle · 2025-02-06T19:48:47.209Z

and all these ports use uboot, not sysupgrade in which i much prefer. Take for example the case a few posts up, where a zip file was attempted to be flash. Thankfully sysugrade denied it, where as uboot, would have uploaded it a he would now have a brick, If i had not gone that route. The use of the sysupgrade method has saved at least 3 devices in this thread alone ....

bluewavenet · 2025-02-06T20:24:15.646Z

Hostle:

and all these ports use uboot, not sysupgrade

All these ports require the use of the sysupgrade.bin in the uboot web-ui.
If you try an img or a ubi or a zip even, it will be rejected.
The exact same sysupgrade.bin can also be used in a running OpenWrt with the sysupgrade utiliy or luci.

The stock firmware is also a sysupgrade.bin.

Hostle:

sysupgrade in which i much prefer.

That is fine if you prefer to use sysupgrade, but that is your choice.

The missing wifi partition should be reinstated and a sysupgrade.bin produced. Then, neither .img nor .ubi would be needed.

Sysupgrade, luci and uboot-web-ui could all be used for flashing official OpenWrt or Stock, simple.foolproof and consistent with all other routers from the same manufacturer.

Hostle · 2025-02-06T20:42:02.811Z

Its not the wifi partition. A custom bootscript (.ifs) is used. Its stored at addr 0x42000000, this script call be adjusted to excluded the wifi partition. But from what i can see it, the kernel load address as well as a few other things need to be altered and imo it looks icky and it much more complicated then what i have done in my port. The only question remaining for me, is if the .ubi file is necessary to include in the build or not.

if you feel you need to be able to flash openwrt via uboot, you're more then welcome to take it on. I will help where i can, but i am in the middle of project at the moment and can't afford the time it takes to implement this and test it as thoroughly as required. And to be honest, i just do not see the need to do more work to implement a secondary upgrade option, that makes the upgrade more prone to user error, and as a result .. more hard bricked devices.

I will send the pr this evening and let the devs decide which is the best option

dmascord · 2025-02-06T23:45:00.694Z

I ordered 2xB3000 yesterday, so love the fact the the PR will be fresh and ready for testing once they arrive

PhilippElhaus · 2025-02-07T15:50:21.214Z

Any idea when the device will be listed in the firmware selector?

IMG_73271367×1502 146 KB

frollic · 2025-02-07T16:16:19.943Z

I can't even find a PR for the B3000.

hecatae · 2025-02-07T16:17:15.915Z

Whenever the PR commit is approved.

hecatae · 2025-02-07T16:18:36.237Z

Glad I'm not the only one struggling to find it

Hostle · 2025-02-07T16:54:18.472Z

I'm just finalizing it now. it'll be there by days end don't worry.

Hostle · 2025-02-08T01:56:48.951Z

I've started the pr ...

github.com/openwrt/openwrt

qualcommax: ipq50xx: add support for GL.iNET GL-B3000

openwrt:main ← TheRootED24:add_glinet_gl-b3000_support

opened 01:55AM - 08 Feb 25 UTC

TheRootED24

+682 -0

Add support for GL.iNET (AX3000) B3000. Speficiations: * SoC: Qualcomm IPQ50…18 (64-bit dual-core ARM Cortex-A53 @ 1.0Ghz) * Memory: Winbond W634GU6NQB-11 (512 MiB DDR3-933) * Serial Port: 3v3 TTL 115200n8 * Wi-Fi: IPQ5018 (2x2 2.4 Ghz 802.11b/g/n/ax) * Wi-Fi: QCN6102 (2x2:2 5 Ghz 802.11an/ac/ax) * Ethernet: IPQ5018 integrated virtual switch connected to an external QCA8337 switch (3 Ports 10/100/1000 GBASE-T) * Flash: Winbond W25N01GWZEIG (128 MiB) * LEDs: 1x single-color blue LED (GPIO 24 Active Low) 1x single-color white LED (GPIO 23 Active Low) * Buttons: 1x Reset (GPIO 27 Active Low) Thanks for your contribution to OpenWrt! To help keep the codebase consistent and readable, and to help people review your contribution, we ask you to follow the rules you find in the wiki at this link https://openwrt.org/submitting-patches Please remove this message before posting the pull request.