Regarding your 4.6 Kernel update notes: cd /boot apt-get remove flash-kernel dpkg -i linux-image-4.6.0-kirkwood-tld-1_1.0_armel.deb The package flash-kernel was not installed so no need to remove it. Also installing the 4.6 kernel DEB file gave a couple of (minor) warnings: root@debian:/boot# dpkg -i linux-image-4.6.0-kirkwood-tld-1_1.0_armel.deb Selecting previously unselecteby armless - uBoot
bodhi Wrote: ------------------------------------------------------- > I think that this version of flash_erase output is > misleading. Go ahead repeat the flashing (step 7, > 8). > > And do fw_printenv afterward for sanity check. And > cross your fingers and reboot :) Aaannnnnnnddddd its rebooted, new U-Boot, finds the USB stick, loads uImage, uInitrd, and DTB (as I&by armless - uBoot
bodhi Wrote: ------------------------------------------------------- > And do fw_printenv afterward for sanity check. And > cross your fingers and reboot :) Flashed u-boot again and default environment. Now doing environment variable "fixup". fw_setenv arcNumber 3542 fw_setenv machid dd6 Should machid be "dd6" or "0xdd6"? Also "restorinby armless - uBoot
bodhi Wrote: ------------------------------------------------------- > Remember, this is the Pogo E02, so we need to be > extra careful. If only the 1 sector was erased, > there is some chance that u-boot image is not > flashed correctly. So don't reboot. Try erase it > again, and btw which version is this Ok, tried again, same behaviour: root@debian:/tmp# flash_by armless - uBoot
bodhi Wrote: ------------------------------------------------------- > Cool, so it was because the mtd partitions > definition in u-boot was removed before. Found why /proc/mtd" was only showing mtd0 previously and then all 4 partitions the latest time: setenv bootargs "console=$(console) root=LABEL=rootfs rootdelay=10 earlyprintk=serial mtdparts=orion_nand:1M(u-boot),4by armless - uBoot
bodhi Wrote: ------------------------------------------------------- > In serial console > ver setenv mtdids 'nand0=orion_nand' setenv partition 'nand0,2' setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' printenv boot No change in behaviour, output inc bootlog attached as file test1.txt setenv mtdidsby armless - uBoot
bodhi Wrote: ------------------------------------------------------- > OK. This time we're going to force it. It looks > like the mtd partitions were not set in stock > u-boot. I realised that when I had updated the uImage for the changed DTB file that I'd actually forgotten to copy it over from the USB rootfs onto the TFTP server. So did that and tried again - still noby armless - uBoot
bodhi Wrote: ------------------------------------------------------- > Basically, we are using the mtdparts from the DTB > in this run. It should show 4 partitions when you > do > > cat/proc/mtd > No different in behaviour, /proc/mtd still just has a mtd0 line. I double-checked the size of uImage to be 100% I'd updated it properly - its 22 bytes smaller than thby armless - uBoot
bodhi Wrote: ------------------------------------------------------- > Please post output of dmesg. Attached.by armless - uBoot
CE>> setenv bootargs "$(console) root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) ro" CE>> printenv bootargs bootargs="console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) ro" root@debian:~# fw_printenv ethact=egiga0 bootdelay=3 baudrate=115200 mainby armless - uBoot
Output is attached (IPs, MAC obscured).by armless - uBoot
Have some free time now to finally sort this out once and for all. Now that TFTP booting is working I'm ready to go ahead with updating u-boot and also the default environment image. Based on the "2016.05 U-Boot Kirkwood" forum thread I've scribbled down a simplified set of steps to perform. Before I hit the big button and start the whole procedure in action I've justby armless - uBoot
bodhi Wrote: ------------------------------------------------------- > This should contain the env location. Something > went wrong in your installation. To use it with > the latest u-boot for Pogo E02, it should be: > > > # MTD device name Device offset Env. size Flash > sector size Number of sectors > /dev/mtd0 0xc0000 0x20000 0x20000 > Actually it didby armless - uBoot
bodhi Wrote: ------------------------------------------------------- > Please post the entire serial console log here, > whether it was successful or not. I'd like to make > this a "Howto boot with tftp" tutorial. Serial console output is attached. It worked fine. Next step I guess is to grab "flash_erase" and "nandwrite" binaries to put ontoby armless - uBoot
bodhi Wrote: ------------------------------------------------------- > QuoteAs I don't currently have a working OS I > can't flash the newer u-boot from there, though I > could use TFTP from the stock u-boot to flash > it? > > Yes. You can boot the new rootfs with tftp. I'm assuming something like this: setenv ipaddr 1.2.3.4 setenv serverip 1.2.3.5by armless - uBoot
bodhi Wrote: ------------------------------------------------------- > So with stock u-boot, > > usb start > > did not work? Nope, gives "Unknown command 'usb' - type 'help'"by armless - uBoot
bodhi Wrote: ------------------------------------------------------- > > OpenWrt u-boot should allow booting from USB. > Interrupt this u-boot, and > > usb start > Ah, but as mentioned earlier in this thread the OpenWRT 2nd stage u-boot (chainloaded from stock CloudEngine u-boot) does not work - it stops at are this part: Verifying Checksum ... OK and neverby armless - uBoot
bodhi Wrote: ------------------------------------------------------- > Your best approach: > > 1. Create Debian 4.4 rootfs on USB from: > http://forum.doozan.com/read.php?2,12096 > > You need to append the pogo e02 DTB to uImage. Done. > 2. Boot, interrupt serial console and copy the > list of current envs, adjust envs (but dont save) > to boot with USBby armless - uBoot
bodhi Wrote: ------------------------------------------------------- > You could stay with that u-boot since it is > relatively new. However, iirc, it is missing a lot > of new features comparing to my u-boot images, so > you might as well flash the newer u-boot. The only > bad thing with installing any u-boot in Pogo E02 > is that it does not have a recovery means such aby armless - uBoot
bodhi Wrote: ------------------------------------------------------- > However, as I mentioned, don't set up > chainloading. Just boot the OpenWrt in NAND with > the new u-boot, Ok, and do you recommend I use your u-boot rather than the OpenWRT (1st stage) u-boot one?by armless - uBoot
Quotebodhi Chainloading from older u-boot (1.1.4) to a modern u-boot such as 2014 or newer is not going to work. You might as well install new u-boot on mtd0 and not having to worry about it at all: http://forum.doozan.com/read.php?3,12381 You think I should use your 2016.05 u-boot in preference to the 2014.10 1st stage OpenWRT u-boot then? One thing to point out is that the documented Opeby armless - uBoot
As per the instructions at "https://wiki.openwrt.org/toh/cloudengines/pogoplug" I flashed the OpenWRT 2nd stage u-boot onto my Pogoplug-E02 to be chainloaded by the stock Cloud Engines u-boot. After flashing and doing the "reset" the Pogoplug did indeed chainload the OpenWRT u-boot but it then hangs at the following point: USB 0: host modeby armless - uBoot
Thanks Bodhi I restored the stock u-boot fine, now having problem with the 2nd stage OpenWRT u-boot - I'll post separately about that.by armless - uBoot
Hi folks I have a Pogoplug-E02 here that I used to run Debian on from a USB HDD. At the time I followed Jeff's guide to install a chainloaded newer U-boot on mtd3. The Pogoplug has been sitting unused for a while as the HDD died. Now I want to install OpenWRT on following their guide (see "https://wiki.openwrt.org/toh/cloudengines/pogoplug"). I have not yet decided whetby armless - uBoot