KodexMedia, I'm assuming you are referring to this instruction (I should have moved it out to its own thread): Boot Kirkwood rootfs with stock u-boot https://forum.doozan.com/read.php?2,102054,105374#msg-105374 1. Booting with stock u-boot that supports usb, ext2load, and run commands 2. Booting with stock u-boot that does not supports usb, ext2load, and run commands 3. Bootingby bodhi - Debian
Rodrigo, > Hi again, do you know why the > Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > didn't work.. just curiosity. This stock u-boot might have some limitation regarding the size of the kernel. You are booting using a set of envs that are not from my recommendation. See here: Boot Kirkwood rootfs with stock u-boot: https://forum.doozan.com/read.php?2,102054,by bodhi - uBoot
Attached is the latest uboot for DS116. It's only a few days before the mainline u-boot 2025.07 will be released, so I'd expect there will be no significant change upstream. uboot.2025.07-rc5-tld-1.ds116.kwb sha256: a161d56317ee9f0cb8e883ed81b61e4796f6a82ee114c7f276d24b15389ff760by bodhi - uBoot
tiramisu376, > After flashing the U-Boot with > ‘CONFIG_SYS_NAND_5_ADDR_CYCLE’ enabled, the > NAND version of the 2015.10 U-Boot now boots > successfully. Nice! Let me move this thread to U-Boot subforum.by bodhi - uBoot
Here is the default envs for Synology DS116.by bodhi - uBoot
eno789, > Question, on DS116/DS216/RS816, if this release > candidate U-Boot tests okay, we no longer need to > flash uImage to mtd for USB rootfs boot, or write > uImage/uInitrd to raw sectors for SATA rootfs > boot, right? Exactly, it is a full feature u-boot. There is no limitation as how you want to boot the box. You can boot straight from USB or HDD rootfs. I'by bodhi - uBoot
> Update, i try with > Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > and start.. so far, I must change some parts > beacuse dont find the roorfs, I must put a label > to the partition on the usbstick Yes, the instruction: Quote1. Format a new USB drive with a single Ext3 partition, and label it rootfs. This step should be done at Linux command line using fdisk, mkfsby bodhi - uBoot
adrien60, Thanks for the feedback!by bodhi - Debian
BayPanard, > Do you need me to boot debian using stock uboot > with tftp boot? or using your uboot with esata > booting? It's really the same in Debian (everything should be working with either boot method). But please do eSATA booting with new u-boot.by bodhi - Debian
Kernel linux-6.15.2-mvebu-370xp-tld-1-bodhi.tar.bz2 package has been uploaded. Please see 1st post for download link.by bodhi - Debian
Kernel 6.15.2-mvebu-tld-1 package has been uploaded. See 1st post for download link. Please create a new thread for any installation problem or questions.by bodhi - Debian
Kernel linux-6.15.2-kirkwood-tld-1 package has been uploaded. See 1st post for download link. And please create a new thread for any installation problem or question.by bodhi - Debian
BayPanard , Log into Debian and lspci lspci -vvv Please post the output here.by bodhi - Debian
eno789, Looks for Synology NAS with Armada 385 or 388 SoC. They have a lot more support, therefore quite stable. I'd avoid Armada 375 and XP because the potential problems (some are working fine, some seeing PCI SATA problem).by bodhi - Off-Topic
BayPanard, > Okay seems like having a working modern uboot on > this box is not an easy task, You can boot with eSATA rootfs in the mean time.by bodhi - Debian
Sorry, I have bad news! this box PCI bus has some issues in Linux.by bodhi - Off-Topic
BayPanard, Thanks! looks like I need to rebase this u-boot to 2025.07-x to make sure we don't miss other indirect bugs. The good thing is what we found out about "unable to assign mbus window for io" error is a real bug and I will send that patch to U-Boot. The difficulty is the Linux driver for MVEBU PCI is quite different from the U-Boot version. So even though we know itby bodhi - Debian
BayPanard, Attached is the new PCIe bug work around/debug build. Please try again the same test. uboot.2024.10-tld-1.ds112.bodhi.250619.tar md5: a2b07d5f4b0d58210b822e24574468a3 sha256: 66e05c7edf4b310e61c8844edb1cb36eb2f4fabe0f6c485cfba398542fc116e1 This tarball includes 5 files. uboot.2024.10-tld-1.ds112.kwb uboot.2024.10-tld-1.ds112.environment.img uboot.2024.10-tld-1.ds112.by bodhi - Debian
BayPanard, Damn, fix one bug and another one shows up :) Thanks for testing!by bodhi - Debian
BayPanard, Attached is the new PCIe bug fix and debug build. Please try again the same test. I have high hope for this build. uboot.2024.10-tld-1.ds112.bodhi.250617.tar md5: 9c3bbbba90519277bf50abbc80372d6f sha256: d51aabe2620b36cb80590d61c1cb1b2084b6ea19cae6ee6fe621fe9eef88eb1b This tarball includes 5 files. uboot.2024.10-tld-1.ds112.kwb uboot.2024.10-tld-1.ds112.environment.imby bodhi - Debian
BayPanard, Thanks! very informative. It fails right away. And looks like we need a work around for this u-boot bug. I will upload another version.by bodhi - Debian
Up in the Wiki. Thanks! QuoteHome Automation & Tools X10 CALDav Calendar Server using Radicale Pogoplug Network Stack with PiHole: pics, and description Pi-hole on Pogoplug Mobile Pi-hole on Pogoplug Pro V3 (OXNAS) Pi-hole 5.0 ad-blocker on Seagate Dockstar Pi-hole 6.x ad-blocker on Seagate Dockstar/Debian 12.xby bodhi - Debian
BayPanard, Attached is the new PCIe debug build. uboot.2024.10-tld-1.ds112.bodhi.250616.tar md5: ccc884672cafb769f42bed15b75fd605 sha256: 36a67888b352a9a3f4d608d27457c24c4f9046bbc22ab04b81188b5485fb211c This tarball includes 5 files. uboot.2024.10-tld-1.ds112.kwb uboot.2024.10-tld-1.ds112.environment.img uboot.2024.10-tld-1.ds112.environment uboot.2024.10-tld-1.ds112.boot.cmdby bodhi - Debian
BayPanard, > uboot.2024.10-tld-1.ds112.kwb: Invalid image. Let me take a look. May be a bad build.by bodhi - Debian
rayknight Wrote: ------------------------------------------------------- > shermbug Wrote: > ------------------------------------------------------- > > If/when I come across some additional Pogo v4 / > > Mobile hardware, I will :-). > > If you're located in the US I can send you via US > Mail a > Smartenit > Harmony P2 which is essentially a relabby bodhi - uBoot
shermbug, > On the plus side, this has been a really good > learning experience to get JTAG up and running on > the Pi and generally having the ability to use > that interface to talk to a device. This may serve > me well in the future, and I also can advise users > about this forum if they run into similar issues > with uboot and the like. > Indeed. Next tby bodhi - uBoot
> But the serial console remains quiet. I think the serial port was fried (damaged) and u-boot could not start because of that.by bodhi - uBoot
If it were in u-boot command prompt, we would run go. Not sure what resume does here. go 0x800200by bodhi - uBoot
> load_image uboot.kwb 524288 bytes written at address 0x00000000 downloaded 524288 bytes in 56.624947s (9.042 KiB/s) > verify_image uboot.kwb verified 524288 bytes in 2.988857s (171.303 KiB/s) > > resume 0x800200 That's fishy. The load address should be 0x800000. resume 0x800200 meaning jump to 0x800200 and execute (where u-boot image was loaded with offset 0x200by bodhi - uBoot
In running from RAM test, did you run pogo_load_uboot right after pogo_init? do you have a log of this attempt? > Could we have an incorrect register setting that > is preventing the serial line from operating as > expected? That's not likely. The BootROM configured the serial port when the box is powered up (that's why we don't do anything regby bodhi - uBoot