[meta-ti] BeagleBone Black , u-boot, and zImage

Mon Aug 18 05:28:24 PDT 2014

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 wrote:
> >>>> Hello,
> >>>> 
> >>>> after building a rootfs for the Beaglebone Black, I see the
> >>>> following files in the deploy folder for the machine:
> >>>> 
> >>>> MLO
> >>>> u-boot.img
> >>>> u-boot-spl.bin
> >>>> zImage
> >>>> 
> >>>> as well as other symlinks with "-beaglebone" attached to their
> >>>> filenames.
> >>>> 
> >>>> 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 built.
> >>>> 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?
> >>> 
> >>> Depends on the rootfs image you are building. Most images that are 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.
> >>> 
> >>> 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.
> >>> 
> >>> Then, if your rootfs does not already have zImage and the necessary 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 will
> >>> work
> >>> for out-of-the-box in this case. No uEnv.txt is necessary, unless you
> >>> need to do something extra special...
> >> 
> >> Oh, I just built core-image-base .
> >> 
> >> 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 one.
> >> 
> >> 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 bootfile env
> >> var to "zImage" won't work, because the u-boot script will try to boot
> >> with the incorrect command.
> > 
> > Try setting bootfile=zImage in uEnv.txt in the first partition.
> > 
> >> I am trying to rule out that something went wrong in my build, that
> >> something is wrong in my setup. If I build core-image-base , the
> >> resulting u-boot.img should automatically load a zImage, not a uImage,
> >> correct?
> > 
> > Can you post serial output from uboot?
> > 
> > Your default environment should look similar to what is here:
> > http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/am335x_evm.h;h=a
> > 48b386477167010c8e0d206423a3bdbe611cf83;hb=524123a70761110c5cf3ccc5f52f6d4
> > 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 CEST
> 2014 armv7l GNU/Linux
> (the kernel was built by the linux-ti-staging recipe)
> 
> The u-boot problem bootfile is set to uImage, and mmcboot uses bootm
> instead of bootz.
> 
> Furthermore, once I correct these two values, it boots, but I see this
> eventually:
> 
>    Error opening /dev/fb0: No such file or directory
> 
> After a bit of investigation, it turned out that omaplfb wasn't loading
> due to missing symbols:
> 
>    root at beaglebone:~# modprobe omaplfb
>    [   83.010309] omaplfb: Unknown symbol register_vsync_cb (err 0)
>    [   83.016642] omaplfb: Unknown symbol unregister_vsync_cb (err 0)
> 
> 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 ?
> 
> Layer git configuration:
> All layers are in their daisy branches.
> poky: SRCREV 87671f72e7459d5d5ddb37691354fab970c557ee
> meta-ti: SRCREV a817ad5826b1c35084a6abb093b89a3916ecb283
> meta-oe: 9ee63edfd9c6e5c22ce707770955a5796cde2cfc
> meta-qt5: a06222499ab602e7c67c1433dd0b559d51d3d744
> 
> 
> 
> The u-boot serial output:
> 
> 
> 
> U-Boot SPL 2013.04-rc1-14237-g90639fe-dirty (Apr 13 2013 - 13:57:11)
> 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
> OMAP SD/MMC: 0
> mmc_send_cmd : timeout: No status update
> reading u-boot.img
> reading u-boot.img
> 
> 
> 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 following 
official instruction to make it boot off SD card: 
https://www.yoctoproject.org/downloads/bsps/daisy16/beaglebone

-- 

Maciej Borzęcki 
Senior Software Engineer Open-RnD Sp. z o.o. 
www.open-rnd.pl, Facebook, Twitter 
mobile: +48 telefon, fax: +48 42 657 9079 

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku 
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 

This message, including any attachments hereto, may contain privileged or 
confidential information and is sent solely for the attention and use of the 
intended addressee(s). If you are not an intended addressee, you may neither 
use this message nor copy or deliver it to anyone. In such case, you should 
immediately destroy this message and kindly notify the sender by reply email. 
Thank you. 