From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id DD185E00576; Mon, 14 Jul 2014 07:52:16 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (miroslav.kes[at]gmail.com) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [209.85.192.51 listed in list.dnswl.org] Received: from mail-qg0-f51.google.com (mail-qg0-f51.google.com [209.85.192.51]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id D5F81E002AA for ; Mon, 14 Jul 2014 07:52:11 -0700 (PDT) Received: by mail-qg0-f51.google.com with SMTP id a108so3452987qge.10 for ; Mon, 14 Jul 2014 07:52:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=UKDLt2TXMi4Afq2qAGAylnMk2gWsjItADZ9HYrWGuBI=; b=OdWnmf3DJ5qlkrx1cMrbmCVF3EAPNruYTibhnFxfYaK0+Tvvm4ll6mKfUMIHvUO+sy 0YTp6B1PDguq7UksZSBR29Eq+gGwdMl3JqBvW2Ubr3Qgh/SY8LschXuE6k1bWucNaW/F LmCVTLCdsFSGUwy4gEXG52jWCi6IDdkDpYwxG/7Q/hjxJ48wM8Mvbj8VGhLI08LDJ9Y2 PGbLGkZLou+XfJtDTvtTiJuHcu3BrbyyjDe34ds9wSfr0dN1owtlIqdhOr0cneF+i15C lQqFw5ZwUw/pBwTs5t8VCb2pVZLGS7b0Y2jGA4dY1p7oxG7SfPbFrn14CWfxbxTjAKuE A/wA== X-Received: by 10.224.92.83 with SMTP id q19mr23517970qam.29.1405349530693; Mon, 14 Jul 2014 07:52:10 -0700 (PDT) Received: from [10.70.136.159] ([205.175.202.247]) by mx.google.com with ESMTPSA id p67sm11394318qgd.34.2014.07.14.07.52.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Jul 2014 07:52:10 -0700 (PDT) Message-ID: <53C3EE94.1040103@gmail.com> Date: Mon, 14 Jul 2014 16:52:04 +0200 From: =?windows-1252?Q?Miroslav_Ke=9A?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "meta-ti@yoctoproject.org" References: <53BAA233.4030803@gmail.com> , <53BBC7F2.50803@gmail.com> In-Reply-To: Subject: Re: BeagleBoard / Beagleboard-xM build X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2014 14:52:16 -0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Finally, I got it working ! I have switched to the daisy branch in both meta-ti and branch and openembedded-core. This changed the mainline kernel from 3.2 to 3.14 and my distroless build now boots OK on both BeagleBoard and BeagleBoard xM The only problem was the missing network support in the kernel configuration. 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š [miroslav.kes@gmail.com] > *Received:* Tuesday, 08 Jul 2014, 6:29 > *To:* Dmytriyenko, Denys [denys@ti.com]; meta-ti@yoctoproject.org [meta-ti@yoctoproject.org] > *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 ) > > > > -----Original Message----- > > *From:* Miroslav Keš [miroslav.kes@gmail.com] > > *Received:* Monday, 07 Jul 2014, 9:36 > > *To:* meta-ti@yoctoproject.org [meta-ti@yoctoproject.org] > > *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 > > meta-ti@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/meta-ti >