All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: meta-ti mailing list <meta-ti@yoctoproject.org>
Subject: Re: using yocto and meta-ti to build for beaglebone black?
Date: Sat, 19 Oct 2013 12:53:15 -0400	[thread overview]
Message-ID: <20131019165314.GL2127@edge> (raw)
In-Reply-To: <alpine.DEB.2.02.1310190717170.9159@oneiric>

On Sat, Oct 19, 2013 at 07:22:31AM -0400, Robert P. J. Day wrote:
> On Sat, 19 Oct 2013, Robert P. J. Day wrote:
> 
> >
> >   a couple quick questions. first, as an example for a tutorial, i
> > want to show using yocto and meta-ti to build a simple
> > (core-image-minimal?) for a BBB. it seems simple enough -- i just
> > configured a new build directory, added the meta-ti layer, set MACHINE
> > to "beaglebone" and it's cranking away on all 8 cores as we speak.
> >
> >   i'm well aware of the recent u-boot uImage->zImage switch, which
> > makes me happy. :-) so as long as i get valid artifacts dumped into
> > the images/ directory when this is over, i figure i can take it from
> > there. as i'm using the master branch for everything (oe-core,
> > meta-ti), should this just work?
> >
> >   also, i just noticed the meta-ti recipe for "x-load". isn't this
> > just for generating the "MLO" file required by a number of TI boards
> > that u-boot takes care of these days? what's the relationship between
> > those two? is x-load just for TI machines for which u-boot doesn't
> > generate an appropriate MLO file?

x-load is deprecated. It's kept for old platforms only.


>   at risk of adding another question to this earlier post, my build of
> a core-image-minimal worked, and among other generated artifacts in
> images/beaglebone/, i have the files:
> 
>  * MLO -> MLO-beaglebone-2013.10-r0+gitrAUTOINC+183acb7003
>  * u-boot-spl.bin-beaglebone-2013.10-r0+gitrAUTOINC+183acb7003
> 
> which are very close in size. i'm used to just installing the MLO
> file, so what's the difference here? what am i supposed to do with the
> "spl" file?

The second one is SPL/UART:

http://processors.wiki.ti.com/index.php/AM335x_U-Boot_User's_Guide#Boot_Over_UART

-- 
Denys


      reply	other threads:[~2013-10-19 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-19 10:54 using yocto and meta-ti to build for beaglebone black? Robert P. J. Day
2013-10-19 11:22 ` Robert P. J. Day
2013-10-19 16:53   ` Denys Dmytriyenko [this message]

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=20131019165314.GL2127@edge \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=rpjday@crashcourse.ca \
    /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.