2023.04 U-Boot Kirkwood - ZyXEL NSA325
Posted by bodhi
|
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325 September 01, 2025 05:41PM |
Admin Registered: 14 years ago Posts: 19,984 |
> I don't see errors during boot. But also no
> internet on the NSA325. I can login over ssh from
> my laptop, so LAN seems ok. But apt update gives
> 'Temporary failure resolving ' and ping gives '
> Name or service not known'. So a DNS problem?
Yes, which Debian version are you on?
Check your /etc/resolv.config
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> internet on the NSA325. I can login over ssh from
> my laptop, so LAN seems ok. But apt update gives
> 'Temporary failure resolving ' and ping gives '
> Name or service not known'. So a DNS problem?
Yes, which Debian version are you on?
Check your /etc/resolv.config
cat /etc/resolv.conf
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325 September 02, 2025 03:20AM |
Registered: 4 years ago Posts: 27 |
|
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325 September 02, 2025 12:36PM |
Admin Registered: 14 years ago Posts: 19,984 |
Bobby,
It's no longer a u-boot issue. I'd suggest creating a new thread in the Debian section for this.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
It's no longer a u-boot issue. I'd suggest creating a new thread in the Debian section for this.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325 November 25, 2025 10:24AM |
Registered: 9 years ago Posts: 26 |
hi @bodhi
i managed to flash the 2023 uboot to my device. coming from stock to 2017 (testing) and now 2023. but i get constant watchdog kicking in in an rebooting the box. is this caused by not adapting the new envvars?
btw i want to use openwrt with our uboot verson cause the openwrts is from 2020.
when i switch to the openwrt uboot no watchdog problems occur.
i managed to flash the 2023 uboot to my device. coming from stock to 2017 (testing) and now 2023. but i get constant watchdog kicking in in an rebooting the box. is this caused by not adapting the new envvars?
btw i want to use openwrt with our uboot verson cause the openwrts is from 2020.
when i switch to the openwrt uboot no watchdog problems occur.
NSA325> version U-Boot 2020.04 (Oct 19 2025 - 16:37:45 +0000) Zyxel NSA325 2-Bay Power Media Server arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 13.3.0 r28959-29397011cc) 13.3.0 GNU ld (GNU Binutils) 2.42 NSA325>
|
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325 November 25, 2025 03:55PM |
Admin Registered: 14 years ago Posts: 19,984 |
Sash,
> i managed to flash the 2023 uboot to my device.
> coming from stock to 2017 (testing) and now 2023.
> but i get constant watchdog kicking in in an
> rebooting the box. is this caused by not adapting
> the new envvars?
No, not the env vars. I might have messed it up somehow. The 2017.07 should work fine with the watchdog killed early.
>
> btw i want to use openwrt with our uboot verson
> cause the openwrts is from 2020.
>
> when i switch to the openwrt uboot no watchdog
> problems occur.
>
>
Thanks for the report!
Let me check code. I might have missed something during rebase. I will post a 2025.10 version for this box for you to test.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> i managed to flash the 2023 uboot to my device.
> coming from stock to 2017 (testing) and now 2023.
> but i get constant watchdog kicking in in an
> rebooting the box. is this caused by not adapting
> the new envvars?
No, not the env vars. I might have messed it up somehow. The 2017.07 should work fine with the watchdog killed early.
>
> btw i want to use openwrt with our uboot verson
> cause the openwrts is from 2020.
>
> when i switch to the openwrt uboot no watchdog
> problems occur.
>
>
> NSA325> version > U-Boot 2020.04 (Oct 19 2025 - 16:37:45 +0000) > Zyxel NSA325 2-Bay Power Media Server > > arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC > 13.3.0 r28959-29397011cc) 13.3.0 > GNU ld (GNU Binutils) 2.42 > NSA325> > > > >
Thanks for the report!
Let me check code. I might have missed something during rebase. I will post a 2025.10 version for this box for you to test.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325 November 26, 2025 07:57AM |
Registered: 9 years ago Posts: 26 |
bodhi Wrote:
-------------------------------------------------------
> No, not the env vars. I might have messed it up
> somehow. The 2017.07 should work fine with the
> watchdog killed early.
jep. forgott to mention the 2017 works also fine.
>
> Let me check code. I might have missed something
> during rebase. I will post a 2025.10 version for
> this box for you to test.
thx!
-------------------------------------------------------
> No, not the env vars. I might have messed it up
> somehow. The 2017.07 should work fine with the
> watchdog killed early.
jep. forgott to mention the 2017 works also fine.
>
> Let me check code. I might have missed something
> during rebase. I will post a 2025.10 version for
> this box for you to test.
thx!
|
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325 November 26, 2025 04:10PM |
Admin Registered: 14 years ago Posts: 19,984 |
Here is the 2025.10 u-boot for NSA325.
uboot.2025.10-tld-1.nsa325.kwb
Try kwboot first. Interrupt the count down.
Test if the watchdog is active (30s is the period): let it sit there at the prompt for about 60 seconds, and run some commands (ie. help, sata init, ....). And then do nothing for 60s again. And then boot (if you have flashed the 2023.04 version then the envs are ok, if not, you can boot with USB rootfs only).
If all went well, flash this u-boot image (or wait until I post the tarball for installation). If the envs are old (ie. 2017.07) then again it can boot with USB rootfs only. And then I'll post the complete release tarball to have the envs matching with this 2025.10 version.
If you have flashed this new image, reboot, and repeat the same test. This time also get the envs listing
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/26/2025 04:21PM by bodhi.
uboot.2025.10-tld-1.nsa325.kwb
sha256: 161072546ea02a4b1e3a73007be9b9d67df2ef858e52c99329a1a2a78033875f
Try kwboot first. Interrupt the count down.
Test if the watchdog is active (30s is the period): let it sit there at the prompt for about 60 seconds, and run some commands (ie. help, sata init, ....). And then do nothing for 60s again. And then boot (if you have flashed the 2023.04 version then the envs are ok, if not, you can boot with USB rootfs only).
printenv boot
If all went well, flash this u-boot image (or wait until I post the tarball for installation). If the envs are old (ie. 2017.07) then again it can boot with USB rootfs only. And then I'll post the complete release tarball to have the envs matching with this 2025.10 version.
If you have flashed this new image, reboot, and repeat the same test. This time also get the envs listing
printenv boot
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/26/2025 04:21PM by bodhi.
|
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325 November 28, 2025 07:06AM |
Registered: 9 years ago Posts: 26 |
hi
[s] the new version works! no reboot caused by the watchdog. you can use it as the default of this thread and remove the non working one.
many thanks! [/s] ...(bb code doesnt seem to work here.... the text should be striked through)
while the watchdog problem is fixed it stops booting from nand.
the openwrt version works
your new version doesnt find nand
Edited 2 time(s). Last edit at 11/28/2025 07:20AM by Sash.
[s] the new version works! no reboot caused by the watchdog. you can use it as the default of this thread and remove the non working one.
many thanks! [/s] ...(bb code doesnt seem to work here.... the text should be striked through)
while the watchdog problem is fixed it stops booting from nand.
the openwrt version works
U-Boot 2020.04 (Oct 19 2025 - 16:37:45 +0000) Zyxel NSA325 2-Bay Power Media Server SoC: Kirkwood 88F6282_A1 DRAM: 512 MiB NAND: 128 MiB MMC: Loading Environment from NAND... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 Error: egiga0 address not set. MV88E1318 PHY initialized on egiga0 Hit any key to stop autoboot: 0 ubi0: attaching mtd3 ubi0: scanning is finished ubi0: attached mtd3 (name "ubi", size 126 MiB) ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512 ubi0: VID header offset: 512 (aligned 512), data offset: 2048 ubi0: good PEBs: 1012, bad PEBs: 2, corrupted PEBs: 0 ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128 ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1750711236 ubi0: available PEBs: 0, total reserved PEBs: 1012, PEBs reserved for bad PEB handling: 18 No size specified -> Using max size (3225600) Read 3225600 bytes from volume kernel to 00800000 ## Booting kernel from Legacy Image at 00800000 ... Image Name: ARM OpenWrt Linux-6.6.110 Created: 2025-10-19 16:37:45 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3133564 Bytes = 3 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 6.6.110 (builder@buildhost) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 13.3.0 r28959-29397011cc) 13.3.0, GNU ld (GNU Binutils) 2.42) #0 Sun Oct 19 16:37:45 2025 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] OF: fdt: Machine model: ZyXEL NSA325 [ 0.000000] Memory policy: Data cache writeback [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000000000000-0x000000001fffffff] [ 0.000000] Movable zone start fo
your new version doesnt find nand
U-Boot 2025.07-tld-1 (Nov 13 2025 - 14:11:50 -0800) ZyXEL NSA325 2-Bay Power Media Server SoC: Kirkwood 88F6282_A1 MPP: Variant 88F6281 Model: ZyXEL NSA325 DRAM: 512 MiB Core: 20 devices, 15 uclasses, devicetree: separate NAND: 128 MiB Loading Environment from NAND... *** Warning - bad CRC, using default environment Resetting console stdin/stdout/stderr to serial... In: serial Out: serial Err: serial pcie0.0: Link up Net: Warning: ethernet-controller@72000 (eth0) using random MAC address - fe:c8:26:94:ed:20 eth0: ethernet-controller@72000 Hit any key to stop autoboot: 0 Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Hunting with: ahci scanning bus for devices... Rescanning SATA bus for devices... Hunting with: usb USB EHCI 1.00 Register 4000820 NbrPorts 4 Starting the controller USB XHCI 0.96 Bus usb@50000: 2 USB Device(s) found Bus xhci_pci: 1 USB Device(s) found Hunting with: ethernet Scanning bootdev 'ethernet-controller@72000.boo': No more bootdevs --- ----------- ------ -------- ---- ------------------------ ---------------- (0 bootflows, 0 valid) NSA325>
Edited 2 time(s). Last edit at 11/28/2025 07:20AM by Sash.
|
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325 November 28, 2025 02:21PM |
Admin Registered: 14 years ago Posts: 19,984 |
Sash,
> [s] the new version works! no reboot caused by the
> watchdog. you can use it as the default of this
> thread and remove the non working one.
>
Cool!
>
>
> while the watchdog problem is fixed it stops
> booting from nand.
>
> the openwrt version works
It's apple and orange.
NAND always works. But the OpenWRT envs are different from mine (which are scripted to boot Debian on external storage devices such as USB or SATA). To boot OpenWRT (which is on NAND), you would need to adjust the envs (it's aactually very simple, just a few envs tweaks).
Look at the OpenWrt threads in the Rescue system section.
https://forum.doozan.com/read.php?4,86219
https://forum.doozan.com/read.php?4,42279
https://forum.doozan.com/read.php?4,29966
When you play with the envs, don't do saveenv, it will mess up things badly. Just test booting with the modified envs and when you power off, it'll all be back to the existing envs.
Post the existing OpenWrt u-boot envs here first so I can help later if you are confused about something.
If you think those OpenWrt threads are too confusing, post back.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> [s] the new version works! no reboot caused by the
> watchdog. you can use it as the default of this
> thread and remove the non working one.
>
Cool!
>
>
> while the watchdog problem is fixed it stops
> booting from nand.
>
> the openwrt version works
It's apple and orange.
> U-Boot 2025.07-tld-1 (Nov 13 2025 - 14:11:50 > -0800) > ZyXEL NSA325 2-Bay Power Media Server > > SoC: Kirkwood 88F6282_A1 > MPP: Variant 88F6281 > Model: ZyXEL NSA325 > DRAM: 512 MiB > Core: 20 devices, 15 uclasses, devicetree: > separate > NAND: 128 MiB
NAND always works. But the OpenWRT envs are different from mine (which are scripted to boot Debian on external storage devices such as USB or SATA). To boot OpenWRT (which is on NAND), you would need to adjust the envs (it's aactually very simple, just a few envs tweaks).
Look at the OpenWrt threads in the Rescue system section.
https://forum.doozan.com/read.php?4,86219
https://forum.doozan.com/read.php?4,42279
https://forum.doozan.com/read.php?4,29966
When you play with the envs, don't do saveenv, it will mess up things badly. Just test booting with the modified envs and when you power off, it'll all be back to the existing envs.
Post the existing OpenWrt u-boot envs here first so I can help later if you are confused about something.
If you think those OpenWrt threads are too confusing, post back.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325 December 03, 2025 06:41AM |
Registered: 9 years ago Posts: 26 |
|
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325 December 03, 2025 02:32PM |
Admin Registered: 14 years ago Posts: 19,984 |
Sash,
> oh. i didnt get that the new uboot overwrites the
> existing envars. put the openwrt back in and it
> worked.
Not quite. Did you got through the whole procedure of flashing u-boot image and u-boot envs image?
5. Flash u-boot image to NAND
6. Flash default u-boot envs image
Post the flashing section if you have kept the log.
The reason it did not boot was the envs are different. To boot OpenWrt, you just need to modify a couple of the envs came with my u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> oh. i didnt get that the new uboot overwrites the
> existing envars. put the openwrt back in and it
> worked.
Not quite. Did you got through the whole procedure of flashing u-boot image and u-boot envs image?
5. Flash u-boot image to NAND
6. Flash default u-boot envs image
Post the flashing section if you have kept the log.
The reason it did not boot was the envs are different. To boot OpenWrt, you just need to modify a couple of the envs came with my u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
