Nexus6, > devices=usb sata My bad. The env above should be devices=usb sata mmc So in serial console setenv devices 'usb sata mmc' And then boot boot Furthermore, see the rootfs release notes. https://forum.doozan.com/read.php?2,12096 QuoteUpdated 01 Nov 2023: Basic Debian bookworm Kirkwood rootfs for most Kirwood plugs: QuoteInstallation: Installaby bodhi - uBoot
Nexus6, > Hello there, i recently got a fully new Pogoplug > V4 from work and decided to install debian and > stuff, used my Pi1 for TTL and i manage to make it > work, only issue is that the SD didnt boot unless > i manually set the envs, noticed the 2023 uBoot > envs dosent have anything related to emmc booting > but the 2016 does, i havent tried to downgrade (ifby bodhi - uBoot
Try the normal ARM version kwboot_2024.04-rc3 (it's the same as the static version but load share libs dynamically). QuoteUpdate Feb 29, 2024 1 . If you are installing u-boot and Debian rootfs on Kirkwood boxes for the first time, you can use the latest flashing utilities on the rootfs itself. No need to download the binpack. But if you'd prefer to have a tool box just in case, tby bodhi - uBoot
Sash, Try using my kwboot build. It is more resilient in error recovery. U-Boot flashing utilities and kwboot binary QuoteUpdate Mar 02, 2024 1 . If you are installing u-boot and Debian rootfs on Kirkwood boxes for the first time, you can use the latest flashing utilities on the rootfs itself. No need to download the binpack. But if you'd prefer to have a tool box just in case,by bodhi - uBoot
Let me move this thread back to U-Boot section. This Rescue section is for OpenWRT and other older rescue systems.by bodhi - uBoot
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 eby bodhi - uBoot
> I have another question. I have read that > processor with bootrom 1.1 whici is my case have > the capability to boot from NAND, SPI, SATA. Yes, this 6281 SoC BootROM does have the capability to boot with one of those boot sources. > I should be able to recover it by > placing uboot kwb file on a sata HD starting from > sector 0 and be able to boot the uboot. >by bodhi - Rescue System
neuro, > this NAS box has one USB 3.0 port. I'll let you > know when I have prepared the usb stick and > proceeded somewhat further. There is a ton of > information in that thread to read ;-) Only the 1st post is relevant! The first installation is simple QuoteNote: If this is your first time installation, then you need rootfs Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tarby bodhi - Debian
New kernel was uploaded. https://forum.doozan.com/read.php?2,16044,140588#msg-140588by bodhi - Debian
Kernel linux-5.15.196-oxnas-tld-1 package was uploaded. See 1st post for download link. And please create a new thread for questions or problem in installation.by bodhi - Debian
BTW, I've just updated the instruction to clarify a few things.by bodhi - Debian
Thanks Trond, That's a non-trivial performance loss! Too bad, but I hope eventually the Linux developers will find some optimization. This conversion to SMP was done somewhat of a mechanical change. It has certainly made the scheduler code much cleaner without all the ugly ifdefs for UP. But for the Kirkwood kernel (armv5 so it cannot be configured as SMP), the conversion has introby bodhi - Debian
Here is the Wiki thread. Booting with uEnv.txt (to fix messed up U-Boot envs or corrupted NAND envs area) https://forum.doozan.com/read.php?3,116134,116139#msg-116139 You don't need a USB rootfs, just a regular USB data drive. But if you're booting with USB rootfs then the /boot folder is already there. At top folder create a /boot/ folder and copy the file cd /media/sdbby bodhi - Debian
stalker, Your envs are for the 2023.04 version. You must have flashed this while installing the wrong u-boot. The easiest way to fix this this to use the default envs from the 2017.07 tarball. Let me look at the tarball and post the instruction.by bodhi - Debian
Thanks all! I will release another version for 5.15 oxnas stable kernel.by bodhi - Debian
@bluzfanmr1, > I am one who's never been able to boot past this > on my Pogoplug Pro. I did post here occasionally > and we tried some things but never got anywhere as > I just settled there to keep it working. > Interesting find if this would apply to my > situation, thanks. It's different. Because the Pogo Pro does have PCIe slot inside for Wifi. The Pogoby bodhi - Debian
Sash, > 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 >by bodhi - uBoot
Here is the 2025.10 u-boot for NSA325. 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 theby bodhi - uBoot
stalker, > Hit any key to stop autoboot: 0 > NSA3x0S> Do these commands List your envs printenv Bring up both HDD/SDD in the slots ide reset ide info ide part See if both disks are spun up (if you have both HDD and SDD in the slot). And then swap the disks to the other slots, and repeat the commands ide reset ide info ide partby bodhi - Debian
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 uby bodhi - uBoot
neuro, You don't really need to use | tee to capture the log. You could just copy/paste the log from the terminal. Here is a good kwboot log (using the DS116 u-boot as example). Note that we are seeing how kwboot prepared the payload here in the log. kwboot -t -p -B 115200 /dev/ttyUSB0 -b uboot.2024.04-tld-1.ds116.kwb kwboot version 2024.04-rc4-00012-g417264db85-dirty Detected kwbby bodhi - Debian
stalker, > I managed to access the data partition after > uploading new firmware (uboot 2017). There were > some issues with this because the partition was > marked as RAID, but after reading the guides, I > “disarmed” the RAID and changed the partition > type to regular Ext4. Debian handled it perfectly > :) Do keep the log of what you did above? please postby bodhi - Debian
Here is the new build. uboot.2025.10-tld-1.wd-glacier.bodhi.251123.tar sha256: ffe0d78687513477ed1f71b3d2d2b0a59553acdac2a62983c205d74ff1a1e345 uboot.2025.10-tld-1.wd-glacier.bodhi.251123.tar This tarball contains 4 files uboot.2025.10-tld-1.wd-glacier.kwb uboot.2025.10-tld-1.wd-glacier.boot.cmd uboot.2025.10-tld-1.wd-glacier.boot.scr README.txt Please do this test dm tree usbby bodhi - Debian
neuro, > I please check the attached file with the tests. Cool! looks like USB and SATA are working. Is the attached USB drive plugged in USB2 port or USB3 port? How many USB ports does this NAS have? and what type are they? > After issuing "ping" it crashes and resets the > device. I've retried it directly after kwboot > u-boot with similar result.by bodhi - Debian
stalker, > Thank you for the clarification. I currently have > an HDD with data inserted to NAS, formatted with > stock firmware. One partition is swap, the other > contains backup data. I'm afraid to tinker with > this drive (change partition size, etc.) in case I > lose data. Good idea. > I think I'll buy a small SSD and use it > as a boot/systemby bodhi - Debian
LME, > Tried the USB to SD card trick and was > getting no where until I remembered you can't boot > off of the two USB 3 ports on the back of the V4, > you have to use the top one. So there is this if > you are having trouble. Right! if you are running the 2017.07-tld-1, the USB3 ports cannot be used for booting. So install the 2023.04-tld-1 if needed, Quotehttby bodhi - Debian
stalker, > that I shouldn't use uboot with nsa325 or nsa320 > in name but nsa310s. Then uboot started as > expected and I was able to flash NAND from USB. Cool! > Now board starts with new uboot - but only if USB > with Debian is plugged in. How can I make it work > in such way that USB dongle is unnecessary? In > other words, how do I transfer Debian fromby bodhi - Debian
Attached to this post is the new u-boot for this box. uboot.2025.10-tld-1.wd-glacier.bodhi.tar sha256: 08496db64e6a92945971ad54bf24677ff724976d2a10e215620c22325e77850f uboot.2025.10-tld-1.wd-glacier.bodhi.tar 6d5b5773a53a7609e3bdb48e210f03d127cf57f96287cf4eba69bc4b7c2742db uboot.2025.10-tld-1.wd-glacier.kwb This tarball contains 4 files uboot.2025.10-tld-1.wd-glacier.kwb uboot.2025.by bodhi - Debian
neuro, Is your serial boot log looks like this (from osa)? U-Boot 2013.01_v1.05 (Mar 31 2015 - 18:27:56) Marvell version: 2014_T2.0p3 Board: WD_Glacier_DB-88F6720-V2 SoC: MV88F6720 Rev A0 running 2 CPUs CPU: ARM Cortex A9 MPCore (Rev 1) LE CPU 0 CPU @ 800 L2 @ 400 TClock @ 200 DDR @ 534 DDR 16Bit Width, FastPatby bodhi - Debian
neuro, > I hope the attached info helps. I am quite new to > this uboot stuff, but I am willing to test things > if possible. Very good info! Stay tune for my new u-boot upload. I've done everything else except for the registers dump you've just provided.by bodhi - Debian