The first 32 bytes of this header are the bhr_t struct, as defined in tools/kwbimage.h. The original Pogoplug uBoot on /dev/mtd0 is prefixed by a 512 byte header.Tar -xjvf pogoplug-u-boot-1.1.4.pp2.0.tar.bz2Ī few points of interest regarding the original Pogoplug uBoot's boot process: Interrupt the Pogoplug uBoot loader and enter the following commands: You should alter these values for your specific network.Ĭopy the file to /tftproot The example below assumes that your TFTP server is at 192.168.0.100 and that 192.168.0.200 is an acceptable IP address for uBoot to use. If you do not have a serial cable, you should not be playing with mtd0.Ĭonfigure a TFTP server someplace on your network. This assumes you have a serial cable to watch and interact with the uBoot process. This will create a file called that you can flash to /dev/mtd0 Testing your new uBoot # Switch to the cross compiler environmentĭd if=u-boot.kwb of= bs=512k conv=sync # if you're interested in building uBoot for those platforms # You can also grab mach-pinkpogo.patch and mach-goflexnet.patch Get the latest uBoot release and apply patches WARNING: Writing to /dev/mtd0 can brick your device. Build replacement uBoot (replaces the existing uBoot on /dev/mtd0) Unless you really want to mess with the old version of uBoot, you do not need to The newer version, so I had to tweak the NAS Central install script a little to install it. The older arm-2006q1 package is packaged a little differently than For building the old Cloud Engines uBoot, I used arm-2006q1. The latest versions of uBoot, I used arm-2009q3. I followed the directions at NAS Central. Your USB device and sometimes it boots into the original Pogoplug install. It's notĪ perfect solution, however: the "chained" loading commands don't always boot properly. It doesn't touch any of the stock firmware so if something goes wrong, you can always attach a serial cable and restore your system. The "chained bootloader" technique is an older technique that was used by projects before there was a good replacement for the uBoot on mtd0. More reliably, and most importantly, it leaves the 219-megabyte partition on /dev/mtd3 available to be used any way you see fit. And it comes with some advantages: with only one bootloader on your dockstar, it will boot several seconds faster, it will boot It's no riskier than flashing new firmware on any other device. However, if you use a known image, like the one I've provided, You can brick your Dockstar by flashing a bad image to /dev/mtd0. The replacement uBoot is the best option, but it's not risk free. To unlock the Dockstar, we need to install an updated uBoot. It's lacking some of the nice features of uBoot, like booting from USB or NFS. This bootloader works well enough to boot the built-in Pogoplug install on the NAND, but The Dockstar comes with a very old version of uBoot installed to /dev/mtd0. Building uBoot for the Seagate Dockstar, GoFlex Net, and Pogoplug Pink If you arrived here by search engine, and just want to install a new uBoot on your device, please see this page.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |