bodhi Wrote: ------------------------------------------------------- > Please post the boot log. I'd like to double check a few things. Here's an early boot log, with some lines truncated due to capturing a minicom window. I'm not home to check these things until June 5 or 6, but it's a start. I'll post another log I recorded (not truncated) in the next post.by dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > Here is the updated boot script. I've had a wrong > mtdparts in the script before. > > Please try again. Yup, that fixed it. Boots fine, did BOTH parts of Step 6 (flash_erase & nandwrite), then removed the boot.scr because it no longer needed the crutch, and it booted as expected. Changed the MACby dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > Here is the updated boot script. I've had a wrong > mtdparts in the script before. It should be: setenv mtdparts "mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)" > Please try again. That change makes sense. I'll get to it after midnight CT (in office now) anby dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > > So at least now it boots fine. Do I erase the NAND > > block next and retry the nandwrite of the image > > next, or do you have more I need to do? > > Yes, so back to Step 6 and onward. > Quote6. Flash default u-boot envs image So I tried: root@deb05:/tmp# /usr/sbin/flash_erase /dev/mtby dhargens - uBoot
It booted fine - found the uboot script /boot.scr and continued onward. Here's the console log to the boot prompt: U-Boot 2023.04-tld-1 (May 10 2023 - 23:00:14 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 Model: Cloud Engines PogoPlug Series 4 DRAM: 128 MiB Core: 20 devices, 16 uclasses, devicetree: separate NAND: 128 MiB MMC: mvsdio@90000: 0 Loading Environment from NAby dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > Did you erase the NAND block first? Quote6. Flash default u-boot envs image > > If you are upgrading from 2017.07-tld-1 u-boot, > you can skip this step. But some envs will need to > be updated. See Note section below after the > installation steps. > > Be extra careful with the next 2 comby dhargens - uBoot
Ok, after some hardware issues and other unexpected problems, I finally got things working. Here's my findings. Booted USB into Debian 5.13.6-kirkwood-tld-1, which has been updated to current. Connected by serial port. Steps: confirmed kwboot for this uboot works. It did the last time too, so I had no worries. stepped thru Sect B (Flashing) steps 1-7. No problems. 1. /etc/fw_env.cby dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > Are you ready to test the installation instruction? Yes, I have some time set aside for this evening and should be able to get started. Are there any other notes I need to know about before doing this? Pointers, maybe? (Not worried about it, just want to make sure I get the steps down correctly. And...I've sleptby dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > I've uploaded an updated version in the first > post. Great to hear! I'll get to it next week - busy weekend ahead, starting tomorrow.by dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > The CPU LED trigger is in the kernel. So you will > see it in the next kernel release. Way cool! > I would suggest a smaller file such as 50MB. This > box only has 128MB RAM. So if you use large file, > i.e 1GB, it will swap out to disk, and then the > test is invalid. Makes perfect sense. I knby dhargens - uBoot
I was successful kwbooting from the new 2023.04 image. Made a new rootfs with the 5.13.6-kirkwood kernel on a SanDisk 3.2Gen1 (Ultra Fit) and it worked fine. I didn't set any environment vars to do it, and it didn't fall apart when I upgraded the system & completed the install etc. I would consider that a success. Was hoping for the cpu setting for the LED too, but this is aby dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > No, it is not available in the current Kirkwood kernel here. I'll add it in the next release. It's > a better visual indicator than just a solid green health status! I'd agree - and I look forward to that! Also, while a few of the other options are obvious, is there a chart that explains what chooby dhargens - uBoot
Hello. I had originally installed Arch uboot in a few of my Pogo V4s. Now that I'm installing the doozan uboot to my next batch of V4s (and looking forward to the newest release with rear USBv3 booting! nudge nudge, wink wink) I was setting it up for similar operation. Because I don't want the green led to always be on, I liked setting it to show me CPU activity. On Arch uboot I cby dhargens - uBoot
Quote Yes. I'm running with USB 3.0 in the back ports right now. I'm very much looking forward to that!by dhargens - uBoot
1. Yes, it's a v3.0 - I bought a 10-pack to update all my Pogos and boot from these. Guess that wasn't such a good idea here. I've used Cruzer Fits on previous V4s, and they've worked without errors. I'll find some Fits and get those working - they fit better in the case anyway. (I'll use the v3s once the 2023.04 version is released, so they won't go to waste.)by dhargens - uBoot
Hello all. I've now updated 3 Pogo V4 uboots (thanks bodhi!), but am having problems with at least 2 of them with the high-speed USB device resetting constantly (the third is so fresh I can't tell if it's having problems too or not, yet). When this happens it essentially hangs the box. I was unsure if I completed the uboot install properly due to these errors, so I was checkiby dhargens - uBoot
Yes, I see the filename listed in the Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 archive - I must've typed it wrong somehow when I was entering it. Small stuff is important. Thanks again - now I can sleep.by dhargens - uBoot
Since we posted at the same time, here's some results: # ls -l boot/dts/kirkwood-pogo*.dtb -rw-r--r-- 1 root root 10114 Aug 1 2021 boot/dts/kirkwood-pogo_e02.dtb -rw-r--r-- 1 root root 9970 Aug 1 2021 boot/dts/kirkwood-pogo_v4.dtb -rw-r--r-- 1 root root 9970 Aug 1 2021 boot/dts/kirkwood-pogoplug_v4.dtb and the interrupted boot & command: U-Boot 2017.07-tld-1 (Sep 05 20by dhargens - uBoot
Good news - using the instructions on "2017.07 U-Boot Kirkwood" (under "section C") I added a uEnv.txt file to the /boot directory to force it to look in the boot/dts directory and now it boots normally. At this point I'm not sure where it thinks it's looking for the file without that pathing, but at least this forces it to look where I know it is. Thanks for yourby dhargens - uBoot
There's a kirkwood-pogoplug_v4.dtb file in boot/dts, so I renamed it and retried the boot - but same problem. Since I can't boot the V4, I don't know how to get the 'printenv dtb_file' command to work and change it. I can interrupt the autoboot, but I don't think that helps me.by dhargens - uBoot
Hi everyone. This is my first post and first time installing the doozan uBoot and a bootable Debian image on a Pogo V4. A few years ago I installed the Arch uBoot & bootable Arch image on some V4s, but now I'm trying to flash a newer uBoot to the remaining stock devices. I followed many posts here on how to do this, and spent a couple of days trying to document it and do it right.by dhargens - uBoot