One of the changes that I have noticed in the guide, when I visited recently after a long absence is that how much of the details are hidden inside the build script. It's less educational this way!
I have a question though, is the small text means it has jump from MLO to u-boot already and the failure inside u-boot or there is a possibility that it didn't see the u-boot? On Monday, June 27, 2016 at 1:07:57 AM UTC-4, William Hermans wrote: > > I'd also like to point out that it's really easy to mess up using Robert's > guide. Not because of the guide per se, but because of the amount of steps > required in order to achieve the end goal. > > I've found it beneficial to copy paste each command into a text file as I > do them so I can be absolutely sure what I've done. > > On Sun, Jun 26, 2016 at 10:05 PM, William Hermans <[email protected] > <javascript:>> wrote: > >> U-Boot SPL 2016.07-rc2-dirty (Jun 26 2016 - 03:11:33) >> No AC power, disabling frequency switch >> Trying to boot from MMC1 >> *Expected Linux image is not found. Trying to start U-boot* >> >> >> U-Boot 2016.07-rc2-dirty (Jun 26 2016 - 03:11:33 -0400) >> >> Watchdog enabled >> I2C: ready >> DRAM: 256 MiB >> >> So, I just expect that this is a pathing issue. It could be something >> else, but I'd double check pathing first. Also, if he skipped the step of >> echoing `uname-r` into /boot/uEnv.txt. It would act the same. Hence why >> I wanted to see the contents of /boot, and /boot/uEnv.txt ;) >> >> >> On Sun, Jun 26, 2016 at 3:09 PM, Charles Steinkuehler < >> [email protected] <javascript:>> wrote: >> >>> Of course! <doh!> >>> You can tell how long it's been since I booted my BBW. :blush: >>> >>> Anyway, there have been lots of changes with the boot loader since the >>> BBW, and I'd recommend starting with a working console image with a >>> recent kernel and u-Boot, with the console images probably being the >>> best starting point if you're wanting to craft your own image. >>> >>> The ROM boot code of the AM335x hasn't changed, but there are very >>> specific constraints on what makes a bootable uSD image (specifically >>> the MLO boot-loader and it's location on the physical media). The >>> easiest way to deal with the constraints is to start with a working >>> image. >>> >>> On 6/26/2016 4:34 PM, evilwulfie wrote: >>> > BBW has no emmc :) >>> > >>> > On 6/26/2016 12:59 PM, Charles Steinkuehler wrote: >>> >> On 6/26/2016 7:56 AM, Hesham wrote: >>> >>> Hi all, >>> >>> >>> >>> I have an old BBW that I wanted to revive. It boots fine with the SD >>> card that >>> >>> came with it. It boots well with an old SD that I built following >>> come old >>> >>> instructions, pre-dates DTS. >>> >>> >>> >>> Now, I've tried to build it following the instructions on: >>> >>> https://eewiki.net/display/linuxonarm/BeagleBone >>> >>> It fails to boot. I think something is wrong regarding the >>> bootloader, either >>> >>> the way I built it or the instructions might be wrong for this old >>> platform. >>> >> An old BBW is going to have an ancient (in computer time-scale) >>> >> boot-loader. I recommend you flash the on-board eMMC with a new boot >>> >> loader. You can do this manually if you really want to (and know >>> >> how), but the easiest way would be to use a recent console image >>> >> flasher like: >>> >> >>> >> >>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flasher:_.28console.29_.28BeagleBone_Black.2FGreen_eMMC.29 >>> >> >>> >> ...assuming you don't mind trashing whatever is in the eMMC, of >>> course! >>> >> >>> > >>> >>> >>> -- >>> Charles Steinkuehler >>> [email protected] <javascript:> >>> >>> -- >>> 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 [email protected] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/c8ef72d8-eea3-6a1b-0ec0-b607b03003e9%40steinkuehler.net >>> . >>> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/8d5aa026-e6f7-4729-86fa-bd06129a37ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
