maybe a workaround ? in the 1st (fat) partition : no uImage is present, while am335x-bone.dtb is here.
So I've copied yocto/poky/build/tmp/deploy/images/beaglebone/uImage to the the boot partition and then got: > U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14) > > >> I2C: ready > > DRAM: 512 MiB > > WARNING: Caches not enabled > > NAND: No NAND device found!!! > > 0 MiB > > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 > > *** Warning - readenv() failed, using default environment > > >> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, >> SoftConn) > > musb-hdrc: MHDRC RTL version 2.0 > > musb-hdrc: setup fifo_mode 4 > > musb-hdrc: 28/31 max ep, 16384/16384 memory > > USB Peripheral mode controller at 47401000 using PIO, IRQ 0 > > musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, >> SoftConn) > > musb-hdrc: MHDRC RTL version 2.0 > > musb-hdrc: setup fifo_mode 4 > > musb-hdrc: 28/31 max ep, 16384/16384 memory > > USB Host mode controller at 47401800 using PIO, IRQ 0 > > Net: <ethaddr> not set. Validating first E-fuse MAC > > cpsw, usb_ether > > Hit any key to stop autoboot: 0 > > gpio: pin 53 (gpio 53) value is 1 > > mmc0 is current device > > micro SD card found > > mmc0 is current device > > gpio: pin 54 (gpio 54) value is 1 > > SD/MMC found on device 0 > > reading uEnv.txt > > 226 bytes read in 3 ms (73.2 KiB/s) > > Loaded environment from uEnv.txt > > Importing environment from mmc ... > > Running uenvcmd ... > > mmc0 is current device > > reading uImage > > 4392120 bytes read in 539 ms (7.8 MiB/s) > > reading am335x-boneblack.dtb > > ** Unable to read file am335x-boneblack.dtb ** > > ## Booting kernel from Legacy Image at 80200000 ... > > Image Name: Linux-3.12.0-rc3 > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 4392056 Bytes = 4.2 MiB > > Load Address: 80008000 > > Entry Point: 80008000 > > Verifying Checksum ... OK > > ERROR: Did not find a cmdline Flattened Device Tree > > Could not find a valid device tree > > gpio: pin 55 (gpio 55) value is 1 > > ** File not found /boot/uImage ** > > U-Boot# > > > it seems to get a little bit better as the uImage is accepted, but the dtb is still refused . Please advise 2013/11/30 David Lewin <[email protected]> > I get back as a new try with the script didn't helped to start. > Attached a log to what happend > > In some words : boot with user btn presed ends with : > >> >> wrong image format for bootm command >> ERROR: can't get kernel image > > > > 2013/11/26 David Lewin <[email protected]> > >> Hi, >> >> After some tries I've changed from Mint Host ( Petra is unrecognized and >> Linaro seems not to be installed with Olivia) >> I finally succeeded to execute these scripts on Debian Wheezy 32: it >> worked directly without any trouble. >> Nevertheless, booting with the MMC isn't recognized : the BBB start with >> Angstrom . >> >> I've used a 4 GB uSD Card to be sure. >> >> , but don't see what is wrong there. >> >> >> 2013/11/18 Charles Steinkuehler <[email protected]> >> >>> On 11/18/2013 10:40 AM, dlewin555 wrote: >>> > Christmas time ! thanks Charles, I'll try : >>> > >>> > ./build_kernel.sh + ./tools/install_kernel.sh >>> > >>> > I think this assume the following to be uselless : >>> > >>> > 1- Checkout the "am33x-v3.8" branch in the Robert Nelson repository >>> [3], >>> >> >>> >> the patch has been tested with commit >>> 3fc8a73d782231ab2750ff29793a760e8fa076bb >>> >> 2- apply beaglebone/ipipe-core-3.8.13-beaglebone-pre.patch >>> >> 3- apply ipipe-core-3.8.13-arm-1.patch >>> >> 4- apply beaglebone/ipipe-core-3.8.13-beaglebone-post.patch >>> >> 5- you can resume to generic installation instructions. >>> >>> Yes, those are the instructions for patching the BeagleBone kernel >>> source manually and can be safely ignored if you're using my github >>> repository. In my repo, the above patching is done for you by the >>> scripts, along with adding the rest of Xenomai to the kernel. >>> >>> -- >>> Charles Steinkuehler >>> [email protected] >>> >>> -- >>> 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/-zyg4FrkMmY/unsubscribe. >>> To unsubscribe from this group and all its topics, 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.
