@bodhi U-Boot 2025.10-tld-1 (Mar 03 2026 - 12:01:44 -0800) Iomega ix4-200d SoC: Kirkwood 88F6281_A1 MPP: Variant 88F6281 DRAM: 512 MiB Core: 20 devices, 14 uclasses, devicetree: separate NAND: 32 MiB MMC: Loading Environment from NAND... *** Warning - bad CRC, using default environment Resetting console stdin/stdout/stderr to serial... In: serial Out: serialby Sash - uBoot
@bodhi u r right! fixed Sash Wrote: ------------------------------------------------------- > also kwb doenst work every time on this unit. > often i start kwboot an the units fan spins to > max,, jsut stits there and nothing else happens. > also tried wir debian kwbooot the solution for this is quiet easy: stop/cancel the kwboot process. restart the kwboot process!by Sash - uBoot
i tested port 1 and 2 the ip is the boxes IP and the ping should work to the local ip, too. there is a very different network on the ethernet which is a vlan that blocks access without registration (corporate network). it was just connected for "link up" purposes i already switched to openwrt but i posted the orig bootlog in the openwrt wiki: https://openwrt.org/toh/iomega/ix4-2by Sash - uBoot
@bodhi i tested both ethernet ports with each a different ip. no ping. dm tree doesnt exist. i also had 3 <1TB hdd inside with are not detected. also kwb doenst work every time on this unit. often i start kwboot an the units fan spins to max,, jsut stits there and nothing else happens. also tried wir debian kwbooot @PHILAP0112:~/Downloads/NAS/iOmega-ix4-200/uboot.2025.10-tld-1.ix4_by Sash - uBoot
also switching to openwrt should fairly easy, with the benefit of flashing the whole system to nand, see: https://openwrt.org/toh/iomega/ix4-200d i like debian and use it exclusively but on these units i perfer something that runs from the internal flash. no hassle with HDD or USB ...by Sash - Debian
bodhi Wrote: ------------------------------------------------------- > Attached here is version tld-0.6 > > This time, kwboot it. And then dump the registers > again ........ hi @bodhi, after 9 years i managed to get my hands again on a ix4 unit, safed from the trash. can we make it possible to have a more recent uboot with all the bugfixes happened in 15 years.....? im wby Sash - uBoot
so this should also view on 115200 baud?by Sash - uBoot
What do you expect to happen? more than Welcome to minicom 2.10 OPTIONS: I18n Port /dev/ttyUSB0, 12:40:45 Press CTRL-A Z for help on special keys �by Sash - uBoot
got it! but no, nothing new. root@Zyxel-NSA325:/tmp# chmod +x kwboot_* root@Zyxel-NSA325:/tmp# ./kwboot_static_2024.04-rc3 -t -B 115200 /dev/ttyUSB0 -b uboot.2025.10-tld-1.nsa325.kwb -p kwboot version 2024.04-rc3-00001-g0861eab8ec-dirty Detected kwbimage v0 with NAND boot signature Patching image boot signature to UART Sending boot message. Please reboot the target...| Sendingby Sash - uBoot
i guess the hw watchdog kicks (blue LED blinks on transfer abort) in cause the transfer so slow?by Sash - uBoot
now im connecting nsa to nsa. the baudrate in the static image cant be set root@Zyxel-NSA325:/tmp# ./kwboot_static_2024.04-rc3 -t -B 9600 /dev/ttyS0 -b uboot.2025.10-tld-1.nsa325.kwb -p kwboot version 2024.04-rc3-00001-g0861eab8ec-dirty Detected kwbimage v0 with NAND boot signature Patching image boot signature to UART Cannot inject code for changing baudrate into v0 image header uboby Sash - uBoot
ah ok. didnt notice that they where arm versions. ok the good thing is i made some connectors to the outside of the working one so i can try that from within openwrt. will report backby Sash - uBoot
havent noticed u replied.... root@PHILAP0112:# uname -a Linux PHILAP0112 6.12.57+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.57-1 (2025-11-05) x86_64 GNU/Linux root@PHILAP0112:# gcc --version gcc (Debian 14.2.0-19) 14.2.0 Copyright (C) 2024 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILIby Sash - uBoot
no enhancement of the trixi delivered kwboot ./kwboot_2025.01-rc1_x86-64 -t -B 115200 /dev/ttyUSB0 -b uboot.2025.10-tld-1.nsa325.kwb -p kwboot version 2025.01-rc1-ge61ea9f2e5d2-dirty Detected kwbimage v0 with NAND boot signature Patching image boot signature to UART Sending boot message. Please reboot the target...- Sending boot image header (512 bytes)... 25 % [....by Sash - uBoot
fyi the static version doesnt run on trixi /Zyxel-NAS325-OpenWRT$ ./kwboot_static_2024.04-rc3 -t -B 115200 /dev/ttyUSB0 -b uboot.2025.10-tld-1.nsa325.kwb -p bash: ./kwboot_static_2024.04-rc3: Kann die Binärdatei nicht ausführen: Fehler im Format der Programmdatei kwboot_2025.01-rc1_x86-64 works in general.by Sash - uBoot
@brodhi i have a 2nd nsa325 which i fu**ed up some years ago while flashing uboot (maybe corrupt). now i tried to kwboot it but it works only parcially: Zyxel-NAS325-OpenWRT$ kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2025.10-tld-1.nsa325.kwb -p kwboot version 2025.01 Detected kwbimage v0 with NAND boot signature Patching image boot signature to UART Sending boot message. Please rebooby Sash - uBoot
just an image update OpenWRT 24.10.04 installs and runs flawlessly. but imho use brodhis lastest uboot (for nsa325 its 2025.10 version with a lot of fixes eg usb enhancements over the "old" (2020) openwrt released uboots). but always kwboot new uboots for testing. sometimes they are broken.by Sash - Rescue System
oh. i didnt get that the new uboot overwrites the existing envars. put the openwrt back in and it worked. this uboot works. u can update the main topic. thx!by Sash - uBoot
another option is: get yourself a serial ttl level converter (just a few bucks) and 3 jumper cables and flash via serial console. this is quiet easy and here well documented.by Sash - uBoot
hi 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! ...(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 NSA325by Sash - uBoot
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 yoby Sash - uBoot
since the units have plenty of cpu power but less RAM it would be wise to use zramfs on newer kernels to free up some ram space in favour of losing some cpu cycles. for reference there is also some nice info on the openwrt forum: https://openwrt.org/toh/iomega/ix4-200dby Sash - Debian
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. NSA325> versionby Sash - uBoot
he bodhi. i'm using zram on all my small ram devices to "enlarge" RAM before using slow swap. Have you tought about updating the rootfs with the zram option by default? its just adding this script to startup: ZRAM on Debianby Sash - Debian
sorry u r right! my fault...used wrong dtb ... root@debian:~# lspci -vvv 00:01.0 PCI bridge: Marvell Technology Group Ltd. 88F6281 ARM SoC (rev 02) (prog-if 00 ) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latenby Sash - Debian
this is k4.8 maybe there is a problem with the dtb....its detected as "OF: fdt:Machine model: Seagate GoFlex Net" but i installed the ix4-200d.dtb from your link...maybe there is the problem located... Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.8.0-kirkwood-tld-1 (root@by Sash - Debian
this is k4.6 root@debian:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.6.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Wed May 18 03:54:14 PDT 2016 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Maby Sash - Debian
hi so 1st tried the k4.6 dtb with k4.8, but no 2nd sata chip not any lspci output. then downgraded to k4.6 with also no sata and pci output. also i see no eth interfaces with k4.6 and k4.6 dtb!by Sash - Debian
ok, will do when i get home in the evening.by Sash - Debian
yep there seems to be a problem with the bus, else there should be an output when calling lspci, right!? i have posted the dmesg above.by Sash - Debian