New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#3324 - Zyxel EMG2926-Q10A (aka NBG6716) requires changes in tree #8183
Comments
drut: I can confirm - I have Zyxel NBG6716 with 256MB flash and it's not possible to flash 21.02 on the device - it bootlops: |
john: full boot log plz, does it work with the patch pasted above ? if so kindly post the patch on openwrt-devel |
drut: I don't have oppoturnity right now to have bootlog again (I need that hardware working) and I don't have option to test out the patch (as I don't have knowledge and tools needed to compile that). If firmware with patch provided, I can test it later on and provide bootlog. |
drut: Thanks to local openwrt forum user I was able to test firmware compiled with patch (nbg6716) and it works flawlessly. |
I now have another of these devices with which to experiment and I believe the confusion here is that the wiki's instructions do not account for the RAS header in the factory binary, while the I believe this issue can be closed once the wiki is updated to shave off the 0x20000 bytes from the start of the OpenWRT |
which older version does not have this critical brick bug? thx |
I managed to get 20.03 installed using the openwrt factory image from the wiki using the TFTP recovery method. |
I know for a fact that Zyxel NBG6716 boots just fine on 22.03.05 EDIT: I just realized again that there are variants with 256MiB flash and 128MiB flash. My friend owns the 128MiB variant. |
Your second diff has been implemented by: |
nwf_:
459c8c9 added support for the Zyxel NBG6716 device. Unfortunately, I believe it made an error in the partition layout. Because the RAS image header is written to flash, the offsets for sub-partitions of //firmware// must be shifted down by the size of this header (i.e., 128KiB):
diff --git a/target/linux/ath79/dts/qca9558_zyxel_nbg6716.dts b/target/linux/ath79/dts/qca9558_zyxel_nbg6716.dts index 90328078dd..148a6ea2d1 100644 --- a/target/linux/ath79/dts/qca9558_zyxel_nbg6716.dts +++ b/target/linux/ath79/dts/qca9558_zyxel_nbg6716.dts @@ -148,14 +148,19 @@ reg = <0x500000 0x7b00000>; };-
-
-
-
-
-
-
-
-
-
-
-
};
Without this change, the bootloader finds the kernel inside its JFFS2 partition just fine, but then the kernel dies when it cannot find the UBI header at the indicated offset.
It is not clear to me whether this change should be applied to all NBG6716-equivalent devices or merely the one I have in hand.
Speaking of, that device calls itself a //AAVK-EMG2926Q10A// in its RAS header and refuses to flash anything not so labeled. Therefore, I have added a target for it by lightly extending the existing one:
diff --git a/target/linux/ath79/dts/qca9558_zyxel_aavk-emg2926q10a.dts b/target/linux/ath79/dts/qca9558_zyxel_aavk-emg2926q10a.dts new file mode 100644 index 0000000000..ec94aa0d73 --- /dev/null +++ b/target/linux/ath79/dts/qca9558_zyxel_aavk-emg2926q10a.dts @@ -0,0 +1,2 @@ +/* This is just an alias, really */ +#include "qca9558_zyxel_nbg6716.dts" diff --git a/target/linux/ath79/image/nand.mk b/target/linux/ath79/image/nand.mk index ad79c487ad..7336dc45d7 100644 --- a/target/linux/ath79/image/nand.mk +++ b/target/linux/ath79/image/nand.mk @@ -263,3 +263,9 @@ define Device/zyxel_nbg6716 UBINIZE_OPTS := -E 5 endef TARGET_DEVICES += zyxel_nbg6716 + +define Device/zyxel_aavk-emg2926q10a + $(call Device/zyxel_nbg6716) + RAS_BOARD := AAVK-EMG2926Q10A +endef +TARGET_DEVICES += zyxel_aavk-emg2926q10a
The text was updated successfully, but these errors were encountered: