I'm still confused concerning the correct approach for building a distroless image.
In this response ... https://lists.yoctoproject.org/pipermail/meta-ti/2014-July/004863.html to a recent post, Maupin says that the kernel provider should be defined by the distribution. But if I compare the conf/machine/beagleboard.conf in danny and daisy branches, the danny version includes PREFERRED_PROVIDER_virtual/kernel = "linux-mainline" PREFERRED_PROVIDER_virtual/bootloader = "u-boot-beagleboard" PREFERRED_PROVIDER_u-boot = "u-boot-beagleboard" while in the daisy (and also master) version there is nothing like that. Could someone answer the first 2 questions my original post? Thanks Mira On 07/08/2014 03:41 PM, Dmytriyenko, Denys wrote: > Sorry, missed it was BeagleBoard and 3.2 kernel... > > > Sent from my Android phone using TouchDown (www.nitrodesk.com) > > -----Original Message----- > *From:* Miroslav Keš [[email protected]] > *Received:* Tuesday, 08 Jul 2014, 6:29 > *To:* Dmytriyenko, Denys [[email protected]]; [email protected] > [[email protected]] > *Subject:* Re: [meta-ti] BeagleBoard / Beagleboard-xM build > > On 07/07/14 15:54, Dmytriyenko, Denys wrote: > > Missing DTB files: > > http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto/tree/README.hardware#n190 > > > > > Denys, > > The hardware README note in your link is related to BeagleBone. Is the DTB > true also for BeagleBoard? > I'm asking because my BeagleBoard build doesn't produce any .dtb image. > Should it create one? > > Thanks > > Mira > > Sent from my Android phone using TouchDown (www.nitrodesk.com > > <http://www.nitrodesk.com>) > > > > -----Original Message----- > > *From:* Miroslav Keš [[email protected]] > > *Received:* Monday, 07 Jul 2014, 9:36 > > *To:* [email protected] [[email protected]] > > *Subject:* [meta-ti] BeagleBoard / Beagleboard-xM build > > > > Hi! > > > > I tried to build the kernel plus core-image-minimal for BeagleBoard using > > just > > > > BBLAYERS ?= " \ > > ${OEBASE}/meta-ti \ > > ${OEBASE}/openembedded-core/meta \ > > " > > The build completed OK but the boot process hangs on both BeagleBoard and > > Beagleboard-xM after > > the "booting the kernel" message (see the output bellow). > > > > I have spent 3 days googling on potential reasons. I found some people > > having similar problems but it looks like the kernel debugging options are > > turned on in the kernel configuration and the ttyO2 should be OK for kernel > > 3.2.28 > > > > I would appreciate if someone could answer these questions: > > > > 1) Is it good idea trying to build the BeagleBoard distro using just > > meta-ti and openembedded-core (i.e. without Angstrom)? > > 2) Is there particular combination of meta-ti and openembedded-core > > versions that should be used? > > 3) What is the relationship between meta-ti and meta-beagleboard (it looks > > like meta-ti supports beagleboards while meta-beagleboard supports > > beaglebone) > > > > Any hints would be really welcome > > > > Mira > > > > --------------------------------------------------------------------- > > > > Welcome to minicom 2.6 > > > > OPTIONS: I18n > > Compiled on Nov 18 2013, 11:01:02. > > Port /dev/ttyS0 > > > > Press CTRL-A Z for help on special keys > > > > ...40V...þ > > U-Boot SPL 2011.09-01172-gfdbe8b9-dirty (Jul 02 2014 - 14:36:18) > > Texas Instruments Revision detection unimplemented > > OMAP SD/MMC: 0 > > reading u-boot.img > > reading u-boot.img > > > > > > U-Boot 2011.09-01172-gfdbe8b9-dirty (Jul 02 2014 - 14:36:18) > > > > OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz > > OMAP3 Beagle board + LPDDR/NAND > > I2C: ready > > DRAM: 256 MiB > > WARNING: Caches not enabled > > NAND: 256 MiB > > MMC: OMAP SD/MMC: 0 > > In: serial > > Out: serial > > Err: serial > > Beagle Rev C1/C2/C3 > > timed out in wait_for_pin: I2C_STAT=0 > > I2C read: I/O error > > Unrecognized expansion board: 0 > > timed out in wait_for_pin: I2C_STAT=0 > > I2C read: I/O error > > Unrecognized expansion board: 0 > > Die ID #5ac400030000000004013f8901001001 > > Net: Net Initialization Skipped > > No ethernet found. > > Hit any key to stop autoboot: 0 > > OMAP3 beagleboard.org # mmc rescan > > OMAP3 beagleboard.org # setenv bootargs console=ttyO2,115200n8 > > root=/dev/mmcblk0p2 rw rootdelay=1 > > OMAP3 beagleboard.org # fatload mmc 0:1 0x80000000 uImage > > reading uImage > > > > 4337768 bytes read > > OMAP3 beagleboard.org # bootm 0x80000000 > > ## Booting kernel from Legacy Image at 80000000 ... > > Image Name: Linux-3.2.28 > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 4337704 Bytes = 4.1 MiB > > Load Address: 80008000 > > Entry Point: 80008000 > > Verifying Checksum ... OK > > Loading Kernel Image ... OK > > OK > > > > Starting kernel ... > > > > Uncompressing Linux... done, booting the kernel. > > -- > > _______________________________________________ > > meta-ti mailing list > > [email protected] > > https://lists.yoctoproject.org/listinfo/meta-ti > -- _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
