Don't worry I had already made a backup img so continually messing things up wasn't really an issue. Just takes a few minutes to download the img back to the sd.
It is similar to what is on both Robert's and your blogs, so I'm not sure why it got messed up when I tried recreating the partition table as well. Regardless: I skipped this step: Erase partition table/labels on microSD card and it appeared the base uboot directly from Roberts guide worked properly. Then I added the patch from here http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue and repeated the procedure. On power up while holding 'a' on the keyboard the boot process continued as desired. So knock on wood I think I got the bootloader replaced and the new patch worked. Thank you both for your help and Miki for the patch! Before I'm content is there any issue from not cleaning out the MBR? Like if the img after the last patch is a different size then Robert's img file? Intending to run reboot tests overnight to make sure the patch clears up the issue. Although if the "random" noise on the rx line spells out stop I'm going to be a little spooked. Thanks, Chris On Thu, Oct 8, 2015 at 5:30 PM, William Hermans <yyrk...@gmail.com> wrote: > >> *Read everything below before half fast attempting such procedure * >> >> >> >> *If I understand what you're asking here, yes it is possible. I've >> experimented with this personally. I talk about what I've done here in a >> blog post. >> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-working-with-debianlinux-images/ >> <http://www.embeddedhobbyist.com/2015/09/beaglebone-black-working-with-debianlinux-images/>* >> >> >> >> >> *So here is the idea. First you would want to backup the MBR liek this: $ >> sudo dd if=/dev/sdb of=/home/william/mbr-sdb.bak bs=1M count=1* >> > *Second You write the wanted MLO / uboot.img file into the first 512k of > the MBR. As demonstrated on Roberts eewiki guide - Which I think you linked > to already ?* > > > > Before attempting the second step here. You would need to use tar to > backup the rootfs as well. Because in effect you do have to wipe out the > partition table. but it can be restored. > > *That *should* leave the partition table intact. But in case it fails, you >> can put the whole partition table, plus original MLO, and uboot.image back >> on the sdcard like so.* >> >> *$ sudo dd if=/home/william/mbr-sdb.bak of=/dev/sdb bs=1M count=1* >> >> > > **OR** > *It would probably be safer / easier to just dd the whole block device > into an image file stored in a safe place* > > > On Thu, Oct 8, 2015 at 2:20 PM, William Hermans <yyrk...@gmail.com> wrote: > >> Sorry not finished and accidentally hit "send". But if you need more >> information on the steps. I can test, and duplicate exact step in order for >> you to do the same - In a safe way. >> >> On Thu, Oct 8, 2015 at 2:19 PM, William Hermans <yyrk...@gmail.com> >> wrote: >> >>> *Sorry that this is probably a dumb question, but is it possible to not >>>> blow* >>>> * away the partition table since I just want to swap the MLO and >>>> u-boot.img?* >>> >>> >>> *Read everything below before half fast attempting such procedure* >>> >>> If I understand what you're asking here, yes it is possible. I've >>> experimented with this personally. I talk about what I've done here in a >>> blog post. >>> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-working-with-debianlinux-images/ >>> >>> So here is the idea. >>> >>> First you would want to backup the MBR liek this: $ sudo dd if=/dev/sdb >>> of=/home/william/mbr-sdb.bak bs=1M count=1 >>> >>> Second You write the wanted MLO / uboot.img file into the first 512k of >>> the MBR. As demonstrated on Roberts eewiki guide - Which I think you linked >>> to already ? >>> >>> That *should* leave the partition table intact. But in case it fails, >>> you can put the whole partition table, plus original MLO, and uboot.image >>> back on the sdcard like so. >>> >>> $ sudo dd if=/home/william/mbr-sdb.bak of=/dev/sdb bs=1M count=1 >>> >>> *OR* >>> >>> It would probably be safer / easier to just dd the whole block device >>> into an image file stored in a safe place. >>> >>> Actually, the whole process is very similar to the exact steps I've laid > out in my blog post. Except that instead of resizing the partition smaller. > You create the partition size however large you want it, and then untar the > rootfs backup to that. > > The whole process is pretty complex, so if you have any questions or > doubts. Ask prior to attempting such a procedure. As there are ways to at > minimum get back to where you started if things go wrong. Mainly, start off > with "dd-ing" the whole top level block device. > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/aXv6An1xfqI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
