You can't just build from Yocto. Angstrom kind of wires in some of the stuff in meta-beagleboard, but you need it in there as well to make it build right with Yocto/Poky.
On Thursday, October 10, 2013 11:40:00 AM UTC-6, dlewin555 wrote: > > This is interesting as I also built from Yocto and didn't managed to make > the BBB starting. > > I'll change the Yocto uImage to the Angstrom one + .dtb and tell if you > tell which version you get them from > > Le mercredi 9 octobre 2013 17:54:43 UTC+2, [email protected] a écrit : >> >> Got it working however it's not exactly clear to me why it wasn't working >> prior and I'm unsure if I'll have issues in the future. Any advice would >> be appreciated. >> >> I replaced the /boot/uImage with the /boot/uImage from the standard >> Angstrom image and used the dtb file from there as well. The kernel >> version that I had built from source that was failing to load was >> 3.12.0-rc3 and the kernel that loads and runs with the dtb file is 3.8.13. >> So I feel like it's one of these options: >> >> 1.) The kernel I built was bad and won't work with anything >> 2.) The kernel I built is not compatible with BBB for whatever reason >> 3.) The kernel I built is not compatible with the version of the dtb >> binary file I used and I need to find an updated dtb file or build one from >> a dts file. >> >> I'll begin testing my application on the board at this point but I'd feel >> more comfortable if I could get a better understanding of the build process >> and why I have to borrow portions (kernel & dtb) from Angstrom builds to >> get it to boot. >> >> Thanks! >> >> ~ Sayguh >> >> On Wednesday, October 9, 2013 10:47:46 AM UTC-4, [email protected] wrote: >>> >>> Update: >>> >>> Got the cable and booted. Here's how things progressed from there: >>> >>> 1.) MLO was loading correctly, so was u-boot but the first issue was it >>> wasn't finding the uImage. It was looking in /boot of the ext3 partition >>> rather than next to the MLO & u-boot file in the Fat32 partition. I copied >>> my uImage into /boot and continued >>> >>> The u-boot output is below but as I understand it, the current issue is >>> that it cannot find the cmdline flattened device tree dtb file. One is not >>> generated by my Poky build. >>> >>> >>> 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 >>> ** Unable to read file uEnv.txt ** >>> gpio: pin 55 (gpio 55) value is 1 >>> 4382696 bytes read in 742 ms (5.6 MiB/s) >>> gpio: pin 56 (gpio 56) value is 1 >>> ** File not found /boot/am335x-boneblack.dtb ** >>> Booting from mmc ... >>> ## Booting kernel from Legacy Image at 80007fc0 ... >>> Image Name: Linux-3.12.0-rc3 >>> Image Type: ARM Linux Kernel Image (uncompressed) >>> Data Size: 4382632 Bytes = 4.2 MiB >>> Load Address: 80008000 >>> Entry Point: 80008000 >>> Verifying Checksum ... OK >>> ERROR: Did not find a cmdline Flattened Device Tree >>> >>> >>> After this, I searched around and found an am335x-boneblack.dtb file in >>> the Angstrom build output and copied that into my SD Card (felt wrong doing >>> it as it wasn't an output of my specific Poky build process). This allowed >>> the kernel to boot however it hung during the boot process as shown below: >>> >>> 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 >>> ** Unable to read file uEnv.txt ** >>> gpio: pin 55 (gpio 55) value is 1 >>> 4382696 bytes read in 742 ms (5.6 MiB/s) >>> gpio: pin 56 (gpio 56) value is 1 >>> 24884 bytes read in 28 ms (867.2 KiB/s) >>> Booting from mmc ... >>> ## Booting kernel from Legacy Image at 80007fc0 ... >>> Image Name: Linux-3.12.0-rc3 >>> Image Type: ARM Linux Kernel Image (uncompressed) >>> Data Size: 4382632 Bytes = 4.2 MiB >>> Load Address: 80008000 >>> Entry Point: 80008000 >>> Verifying Checksum ... OK >>> ## Flattened Device Tree blob at 80f80000 >>> Booting using the fdt blob at 0x80f80000 >>> XIP Kernel Image ... OK >>> OK >>> Using Device Tree in place at 80f80000, end 80f89133 >>> >>> Starting kernel ... >>> >>> >>> Anyone have any advice on how to get it to boot up correctly? >>> >>> ~ Sayguh >>> >>> On Monday, October 7, 2013 9:50:59 AM UTC-4, RobertCNelson wrote: >>>> >>>> On Mon, Oct 7, 2013 at 8:17 AM, <[email protected]> wrote: >>>> > Step 1.) I followed this post to build Poky for the BBB: >>>> > https://gist.github.com/errordeveloper/4056193 >>>> > >>>> > Step 2.) I followed this to setup the SD card: >>>> > https://pixhawk.ethz.ch/tutorials/omap/boot_from_sd_sdhc >>>> > >>>> > Step 3.) I followed this for deploying my artifacts (MLO, u-boot, >>>> uImage & >>>> > file system) >>>> > https://pixhawk.ethz.ch/tutorials/omap/copy_sd_card >>>> > >>>> > I have also tried to swap out Step 2 above for the mkcard.txt script >>>> found >>>> > here: >>>> > http://downloads.angstrom-distribution.org/demo/beaglebone/ >>>> > >>>> > In all cases, I attempt to boot the BBB and I do not get anything >>>> over the >>>> > HDMI display and nothing hits my routers DHCP server to receive an IP >>>> > address. >>>> > >>>> > I do not have an FTDI Cable but can buy one if that is the logical >>>> next step >>>> > in debugging. >>>> > >>>> > Any advice? Without an FTDI Cable, is there anyway to watch the boot >>>> > process? >>>> >>>> Get a Cable.. >>>> >>>> Regards, >>>> >>>> -- >>>> Robert Nelson >>>> http://www.rcn-ee.com/ >>>> >>> -- 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.
