From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 8F4B5E007F1; Mon, 18 Aug 2014 05:28:32 -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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from akt59.rev.netart.pl (akt59.rev.netart.pl [85.128.150.59]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 07CBEE007EE for ; Mon, 18 Aug 2014 05:28:28 -0700 (PDT) Received: from localhost.localdomain (unknown [46.170.72.194]) by open-rnd.nazwa.pl (Postfix) with ESMTP id 115451158232 for ; Mon, 18 Aug 2014 14:28:26 +0200 (CEST) From: Maciej Borzecki To: meta-ti@yoctoproject.org Date: Mon, 18 Aug 2014 14:28:24 +0200 Message-ID: <8239334.zKDPeKpJDo@localhost.localdomain> User-Agent: KMail/4.13.3 (Linux/3.15.8-200.fc20.x86_64; KDE/4.13.3; x86_64; ; ) In-Reply-To: <53F1C2F5.50209@pseudoterminal.org> References: <53ED13BE.2090809@pseudoterminal.org> <2948184.BeJYLBqp38@localhost.localdomain> <53F1C2F5.50209@pseudoterminal.org> MIME-Version: 1.0 Subject: Re: BeagleBone Black , u-boot, and zImage 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, 18 Aug 2014 12:28:32 -0000 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" On Monday 18 of August 2014 11:10:13 Carlos Rafael Giani wrote: > On 2014-08-14 22:20, Maciej Borzecki wrote: > > On Thursday 14 of August 2014 22:09:01 Carlos Rafael Giani wrote: > >> On 08/14/2014 10:04 PM, Denys Dmytriyenko wrote: > >>> On Thu, Aug 14, 2014 at 09:53:34PM +0200, Carlos Rafael Giani wro= te: > >>>> Hello, > >>>>=20 > >>>> after building a rootfs for the Beaglebone Black, I see the > >>>> following files in the deploy folder for the machine: > >>>>=20 > >>>> MLO > >>>> u-boot.img > >>>> u-boot-spl.bin > >>>> zImage > >>>>=20 > >>>> as well as other symlinks with "-beaglebone" attached to their > >>>> filenames. > >>>>=20 > >>>> What should I copy, the SPL bin, or the .img u-boot binary? > >>>> Also, u-boot tries to load a uImage, even though a zImage was bu= ilt. > >>>> There is also no uEnv.txt file. > >>>> Do I have to write one to be able to let u-boot load the zImage,= or > >>>> should it work out-of-the-box? > >>>=20 > >>> Depends on the rootfs image you are building. Most images that ar= e based > >>> on > >>> core-image-base will take care of deploying necessary pieces into= the > >>> rootfs. But core-image-minimal is special and very bare-bone, so = extra > >>> manual steps are required. > >>>=20 > >>> Regardless of the rootfs image, you'd need MLO and u-boot.img to = be > >>> located in the first FAT partition of your SD card or eMMC flash.= > >>>=20 > >>> Then, if your rootfs does not already have zImage and the necessa= ry DTB > >>> files in the /boot directory, you have to place them there (i.e. > >>> core-image-minimal) and you are ready to boot. All the defaults w= ill > >>> work > >>> for out-of-the-box in this case. No uEnv.txt is necessary, unless= you > >>> need to do something extra special... > >>=20 > >> Oh, I just built core-image-base . > >>=20 > >> So I should use the .img and not the SPL .bin? I was wondering if = the > >> SPL bin is a newer binary that will eventually replace the .img on= e. > >>=20 > >> But when I use the .img file, it turns out that it tries to load a= > >> uImage, even though a zImage was built. Simply setting the bootfil= e env > >> var to "zImage" won't work, because the u-boot script will try to = boot > >> with the incorrect command. > >=20 > > Try setting bootfile=3DzImage in uEnv.txt in the first partition. > >=20 > >> I am trying to rule out that something went wrong in my build, tha= t > >> something is wrong in my setup. If I build core-image-base , the > >> resulting u-boot.img should automatically load a zImage, not a uIm= age, > >> correct? > >=20 > > Can you post serial output from uboot? > >=20 > > Your default environment should look similar to what is here: > > http://git.denx.de/?p=3Du-boot.git;a=3Dblob;f=3Dinclude/configs/am3= 35x_evm.h;h=3Da > > 48b386477167010c8e0d206423a3bdbe611cf83;hb=3D524123a70761110c5cf3cc= c5f52f6d4 > > da071b959#l78 > I rebuilt the image, with the proper layers, but still I get an > incorrect u-boot environment. Full u-boot serial output and boot log > follow below. > uname -a prints: Linux beaglebone 3.14.16 #1 Thu Aug 14 18:00:21 CES= T > 2014 armv7l GNU/Linux > (the kernel was built by the linux-ti-staging recipe) >=20 > The u-boot problem bootfile is set to uImage, and mmcboot uses bootm > instead of bootz. >=20 > Furthermore, once I correct these two values, it boots, but I see thi= s > eventually: >=20 > Error opening /dev/fb0: No such file or directory >=20 > After a bit of investigation, it turned out that omaplfb wasn't loadi= ng > due to missing symbols: >=20 > root@beaglebone:~# modprobe omaplfb > [ 83.010309] omaplfb: Unknown symbol register_vsync_cb (err 0) > [ 83.016642] omaplfb: Unknown symbol unregister_vsync_cb (err 0)= >=20 > Searching for this, I found > https://groups.google.com/forum/#!topic/beagleboard/dcLtpK7ZsX0 . > According to this, in the kernel log, I should set CONFIG_FB_DA8XX to= > "y". Is this still correct for linux-ti-staging 3.14.16 ? >=20 > Layer git configuration: > All layers are in their daisy branches. > poky: SRCREV 87671f72e7459d5d5ddb37691354fab970c557ee > meta-ti: SRCREV a817ad5826b1c35084a6abb093b89a3916ecb283 > meta-oe: 9ee63edfd9c6e5c22ce707770955a5796cde2cfc > meta-qt5: a06222499ab602e7c67c1433dd0b559d51d3d744 >=20 >=20 >=20 > The u-boot serial output: >=20 >=20 >=20 > U-Boot SPL 2013.04-rc1-14237-g90639fe-dirty (Apr 13 2013 - 13:57:11) > musb-hdrc: ConfigData=3D0xde (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=3D0xde (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 > OMAP SD/MMC: 0 > mmc_send_cmd : timeout: No status update > reading u-boot.img > reading u-boot.img >=20 >=20 > U-Boot 2013.04-rc1-14237-g90639fe-dirty (Apr 13 2013 - 13:57:11) Rough guess, but it looks like a default u-boot from eMMC. Try followin= g=20 official instruction to make it boot off SD card:=20 https://www.yoctoproject.org/downloads/bsps/daisy16/beaglebone --=20 Maciej Borz=C4=99cki=20 Senior Software Engineer Open-RnD Sp. z o.o.=20 www.open-rnd.pl, Facebook, Twitter=20 mobile: +48 telefon, fax: +48 42 657 9079=20 Niniejsza wiadomo=C5=9B=C4=87 wraz z za=C5=82=C4=85cznikami mo=C5=BCe z= awiera=C4=87 chronione prawem lub=20 poufne informacje i zosta=C5=82a wys=C5=82ana wy=C5=82=C4=85cznie do wi= adomo=C5=9Bci i u=C5=BCytku os=C3=B3b, do=20 kt=C3=B3rych zosta=C5=82a zaadresowana. Je=C5=9Bli wiadomo=C5=9B=C4=87 = zosta=C5=82a otrzymana przypadkowo=20 zabrania si=C4=99 jej kopiowania lub rozsy=C5=82ania do os=C3=B3b trzec= ich. W takim przypadku=20 uprasza si=C4=99 o natychmiastowe zniszczenie wiadomo=C5=9Bci oraz poin= formowanie=20 nadawcy o zaistnia=C5=82ej sytuacji za pomoc=C4=85 wiadomo=C5=9Bci zwro= tnej. Dzi=C4=99kujemy.=20 This message, including any attachments hereto, may contain privileged = or=20 confidential information and is sent solely for the attention and use o= f the=20 intended addressee(s). If you are not an intended addressee, you may ne= ither=20 use this message nor copy or deliver it to anyone. In such case, you sh= ould=20 immediately destroy this message and kindly notify the sender by reply = email.=20 Thank you.