All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <jeremy@rhtech.co.nz>, <yocto@yoctoproject.org>
Subject: Re: Anybody managed to get Beagleboard xM to work?
Date: Tue, 6 May 2014 23:19:59 -0400	[thread overview]
Message-ID: <5369A65F.8060006@windriver.com> (raw)
In-Reply-To: <53695DDA.1020204@rhtech.co.nz>

On 2014-05-06, 6:10 PM, Jeremy Cole-Baker wrote:
> On 7/05/2014 2:01 a.m., Bruce Ashfield wrote:
>
>>> Anything else I am missing? Some configuration I need to set up? I have
>>> no idea where to look! It is frustrating because it seems to be very
>>> close to working.
>>
>> As an alternative to using the Yocto reference BSP (Which I mentioned
>> has moved onto the BBB with a better focus on core functionality), the
>> meta-beagleboard layer has a more complete feature focus and should
>> solve the problem (via a different kernel and configuration).
>>
>
>
> Hi, can you explain how to use the meta-beagleboard layer? My build was
> done using the BSP for "Texas Instruments ARM Cortex-A8 development
> board (Beagleboard)" (10.0.0 Dora). I downloaded it, and I think I built
> it with Hob the first time. I also used 'bitbake' to adjust the
> configuration and build from the command line to try different options.
>
> I just downloaded the latest Yocto project 1.6 (11.0.0 Daisy), and had a
> look around including running Hob. However, I couldn't find a
> meta-beagleboard layer.

If I recall correctly, its this:

    https://github.com/beagleboard/meta-beagleboard

The Yocto reference BSPs themselves are about exercising core
functionality on easily available h/w references (one per major arch).

Those reference BSPs are on the Yocto release kernel (which is now
typically LTSI kernel), and hence have all the Yocto kernel features
(union filesystems, optional preempt-rt support, CVEs, -stable updates,
etc) and configuration meta-data (base policy + configuration fragemnt
support).

We try and make them as functional as possible, but sticking with the
stable and longer term kernels means that development which happens
on the latest mainline, or different community trees is only merged to
the Yocto kernel if we get explicit support and patches ported. That
means that some bleeding edge, or advanced functionality is available
in those feature-full and community supported trees.

The layer I pointed at above, has that mix of extended/enhanced
functionality.

We refreshed the the ARM reference to the beaglebone black in the latest
Yocto release, and thanks to TIs (via DenysD) support .. we have a
mainline supported, and very functional refernece.

That being said, working USB is core functionality and it was tested
green for the 1.5 release .. at least if my memory serves. So it
should be working in your build.

Bruce

>
> I also downloaded and installed binaries for the latest build from:
>
> autobuilder.yoctoproject.org/pub/releases/CURRENT/machines/beagleboard/
>
> These worked but showed the same behaviour (i.e. no USB). Maybe it has
> something to do with the way I set up the boot environment?
>
> Thanks,
> Jeremy



  reply	other threads:[~2014-05-07  3:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.16489.1397995243.26702.yocto@yoctoproject.org>
2014-05-06  2:38 ` Anybody managed to get Beagleboard xM to work? Jeremy Cole-Baker
2014-05-06  9:02   ` Kai Ulrich
2014-05-06 14:01   ` Bruce Ashfield
2014-05-06 22:10     ` Jeremy Cole-Baker
2014-05-07  3:19       ` Bruce Ashfield [this message]
2014-05-07  2:36   ` Yi Zhao
2014-05-07  4:41     ` Jeremy Cole-Baker

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=5369A65F.8060006@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=jeremy@rhtech.co.nz \
    --cc=yocto@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.