All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Denys Dmytriyenko <denys@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: BeagleBone Black , u-boot, and zImage
Date: Thu, 14 Aug 2014 22:09:01 +0200	[thread overview]
Message-ID: <53ED175D.2090502@pseudoterminal.org> (raw)
In-Reply-To: <20140814200450.GX23523@edge>

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.

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?


  reply	other threads:[~2014-08-14 20:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 19:53 BeagleBone Black , u-boot, and zImage Carlos Rafael Giani
2014-08-14 20:04 ` Denys Dmytriyenko
2014-08-14 20:09   ` Carlos Rafael Giani [this message]
2014-08-14 20:20     ` Maciej Borzecki
2014-08-18  9:10       ` Carlos Rafael Giani
2014-08-18 10:31         ` Diego Sueiro
2014-08-18 12:28         ` Maciej Borzecki
2014-08-18 12:34           ` Diego Sueiro
2014-08-18 14:16             ` Denys Dmytriyenko
2014-08-18 14:18               ` Carlos Rafael Giani
2014-08-18 14:45               ` Maciej Borzecki
2014-08-23  3:24                 ` Denys Dmytriyenko
2014-08-23  8:36                   ` Maciej Borzecki
2014-08-14 20:20     ` Denys Dmytriyenko
2014-08-15  9:47       ` Diego Sueiro
2014-08-15 14:10         ` Denys Dmytriyenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53ED175D.2090502@pseudoterminal.org \
    --to=dv@pseudoterminal.org \
    --cc=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.