I have the exact same problem. I started flashing a BBB but the user LEDs were all blinking, so I thought the flash had failed and unplugged the board from power. Now the board won't boot from internal eMMC or uSD. My uSD has the dtbs files. I've tried forcing boot to uSD with boot button. The serial debug cable is the only way I can get output. All four user LEDs are solid. Any ideas?
On Sunday, September 1, 2013 7:25:47 PM UTC-4, William Hermans wrote: > > Very good :) > > > On Sun, Sep 1, 2013 at 3:21 PM, Mike Pearson <[email protected]<javascript:> > > wrote: > >> You saved me. Thanks for your help. I wasn't comfortable with that step, >> but thought it did what it needed. Those files were not there. Got em now! >> >> Thanks again, >> Mike >> >> >> On Sunday, September 1, 2013 4:33:08 PM UTC-5, William Hermans wrote: >> >>> ERROR: Did not find a cmdline Flattened Device Tree >>> Could not find a valid device tree >>> >>> uenvcmd was not defined in uEnv.txt ... >>> halting ... >>> >>> Ok so it seems that *maybe* you forgot a step from RCN's instructions . >>> . . so remount that sdcard and make sure that >>> /boot/dtbs/am335x-boneblack.dtb >>> exists. If it does not then scroll down to RCN's instructions where it says >>> . . . >>> >>> export kernel_version=3.X.Y-Z >>> >>> sudo mkdir -p /media/boot/dtbs/ >>> sudo tar xfov ./linux-dev/deploy/${kernel_version}-dtbs.tar.gz -C >>> /media/boot/dtbs/ >>> >>> Issue these commands and you should now have that file. also . . .export >>> kernel_version=3.X.Y-Z <---- this is going ot depend on the kernel version >>> you built. As I have not followed these instructions personally in over 2 >>> months, I do not know which kernel version is is using currently. But, you >>> can also navigate into the /linux-dev/deploy/ direction and issues ls -al >>> to find this information out, as well as navigate directly into the proper >>> directory, and then copy it over to the right location on the SD card ( >>> /boot/dtbs/). >>> >>> >>> On Sun, Sep 1, 2013 at 2:20 PM, William Hermans <[email protected]>wrote: >>> >>>> AH ok i completely missed the attachments on your first post, i will >>>> give them a quick looksee >>>> >>>> >>>> On Sun, Sep 1, 2013 at 2:19 PM, Mike Pearson <[email protected]> wrote: >>>> >>>>> Right. I know the SD card was made correctly because I booted into >>>>> 13.04 before attempting to transfer to eMMC. It worked great. Had I gave >>>>> the transfer the time it needed, I'm fairly confident that would have >>>>> worked well too. I haven't changed anything on the SD card, so was >>>>> assuming >>>>> that was still the same. Would something have changed on that during the >>>>> transfer? >>>>> >>>>> >>>>> On Sunday, September 1, 2013 4:12:59 PM UTC-5, Gerald wrote: >>>>> >>>>>> The button is there to force the boot form SD instead of the eMMC. >>>>>> That is is sole purpose. However, if the SD card is not made correctly, >>>>>> then it can't boot from the SD. IF you do not follow the correct >>>>>> procedure >>>>>> in making the SD card, then you can have issues. >>>>>> >>>>>> Gerald >>>>>> >>>>>> >>>>>> >>>>>> On Sun, Sep 1, 2013 at 4:10 PM, Mike Pearson <[email protected]>wrote: >>>>>> >>>>>>> I'd like to boot from the SD card, but it won't. Other than the >>>>>>> button technique, not sure how I can force it. I am not able to access >>>>>>> anything to delete the MLO file. I do have a cable and posted the >>>>>>> output >>>>>>> but to be honest, it doesn't tell me a whole lot. >>>>>>> >>>>>>> >>>>>>> On Sunday, September 1, 2013 3:23:42 PM UTC-5, William Hermans wrote: >>>>>>> >>>>>>>> Or, you can just boot it off of the uSD card, but this of course >>>>>>>> wont tell if the eMMC has failed. I have followed those instructions >>>>>>>> myself, but have not transferred to eMMC yet ( as i still have lots of >>>>>>>> work >>>>>>>> to do before my project is ready for prime time ). >>>>>>>> >>>>>>>> I did however read the transfer to eMMC instructions, and for what >>>>>>>> it is it did seem fairly complex. I'd try to boot off the sd card, and >>>>>>>> try >>>>>>>> to see / remember if you missed a step. Also, do you have a serial >>>>>>>> debug >>>>>>>> cable / module ? In this regard this could save you a lot of hassle . >>>>>>>> .. as >>>>>>>> uboot / the OS will tell you exactly what is wrong. >>>>>>>> >>>>>>>> >>>>>>>> On Sun, Sep 1, 2013 at 1:02 PM, Gerald Coley < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> I would take it back to the factory setting. Make sure that all >>>>>>>>> works. Then try it again. >>>>>>>>> >>>>>>>>> http://circuitco.com/support/index.php?title=Updating_The_Software >>>>>>>>> >>>>>>>>> >>>>>>>>> Gerald >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sun, Sep 1, 2013 at 12:39 PM, Mike Pearson >>>>>>>>> <[email protected]>wrote: >>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> I was upgrading my beaglebone black from 12.04 to 13.04 and >>>>>>>>>> referencing the following page. >>>>>>>>>> http://eewiki.net/display/linuxonarm/BeagleBone+Black#Beagle >>>>>>>>>> BoneBlack-uEnv.txtbasedbootscript >>>>>>>>>> >>>>>>>>>> I worked through all of this without a problem. I got to the step >>>>>>>>>> to transfer to "copy your microSD card to eMMC", but didn't >>>>>>>>>> realize how much time I was supposed to give it and basically >>>>>>>>>> interrupted >>>>>>>>>> it right away during programming. Now it won't boot. I was hoping >>>>>>>>>> I'd be >>>>>>>>>> able to force it to boot from the SD card aging and restart the >>>>>>>>>> process, >>>>>>>>>> but no luck. >>>>>>>>>> >>>>>>>>>> If anyone is willing to give some advice, I would be very >>>>>>>>>> grateful. I did search this out, but didn't see anything that >>>>>>>>>> applied. I >>>>>>>>>> hope I've provided enough information. I attached a text file >>>>>>>>>> with my boot output via my FTDI cable. I also attached the uEnv.txt >>>>>>>>>> which >>>>>>>>>> is the same as the eewiki page references. >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Mike >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> 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]. >>>>>>>>>> >>>>>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> 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]. >>>>>>>>> >>>>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>> 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]. >>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>> >>>>>> >>>>>> -- >>>>> 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]. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>> >>>> >>> -- >> 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:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
trying eMMC (BeagleBone Black) ... mmc_send_cmd : timeout: No status update mmc1(part 0) is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 1 Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** gpio: pin 55 (gpio 55) value is 1 Checking if uenvcmd is set ... gpio: pin 56 (gpio 56) value is 1 Running uenvcmd ... Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Kernel image @ 0x80200000 [ 0x000000 - 0x32f450 ] ## Loading init Ramdisk from Legacy Image at 81000000 ... Image Name: initramfs Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 2502635 Bytes = 2.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid uenvcmd was not defined in uEnv.txt ... halting ... U-Boot#
