u-boot precompiled ?

u-boot precompiled ?

[Matthias.Heise]

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

Hi all,

I'm still trying to find out basic things about getting a system up and running. This question is about U-Boot, is it right that for example for my wandboard a pre-compiled *.imx is just downloaded ?
So if I want to make settings to U-Boot I make them directly in the source, compile it and re-direct in a recipe to take that new file as bootloader ? Or can I make the settings within a recipe and I just didn't find the spot ?
Thanks for your time,
Regards
Mat

[-- Attachment #2: Type: text/html, Size: 2469 bytes --]

Re: u-boot precompiled ?

[Matthias.Heise]

[-- Attachment #1: Type: text/plain, Size: 828 bytes --]

Even if this is a stupid question a little advise would be nice ... like "don't ask so stupid questions, go read this and that" or something... no time ? Should I rather unsubscribe from this list until I'm an expert?

Von: Heise, Matthias
Gesendet: Mittwoch, 3. Dezember 2014 15:15
An: 'yocto@yoctoproject.org'
Betreff: u-boot precompiled ?

Hi all,

I'm still trying to find out basic things about getting a system up and running. This question is about U-Boot, is it right that for example for my wandboard a pre-compiled *.imx is just downloaded ?
So if I want to make settings to U-Boot I make them directly in the source, compile it and re-direct in a recipe to take that new file as bootloader ? Or can I make the settings within a recipe and I just didn't find the spot ?
Thanks for your time,
Regards
Mat

[-- Attachment #2: Type: text/html, Size: 3604 bytes --]

Re: u-boot precompiled ?

[Matt Schuckmann]

[-- Attachment #1: Type: text/plain, Size: 2013 bytes --]

Mat,

I'm fairly new to OpenEmbedded (4 months now and I still feel like a noobi but I'm trying to give back while the pain is still fresh in my mind)
For something like u-boot it kind of depends on what your changing. If you need to change the u-boot code and the changes are small then typically you'd create a patch f for your changes and then make them part of a .bbappend in your layer for the recipe. There are examples on the net for how to create a .bbappend and reference the patch file.

Generally your .bbappend can be as simple as:

FILESEXTRAPATHS_prepend = ":${THISDIR}/files"
SRC_URI += "files://xyzzy.patch"

Where your patches are in subdirectory of your recipe directory.

Remember that generally recipes are about how to obtain the code, build it and package it for distribution, you can do recipes that deal with a pre-built binary but that is generally not the case.

Hope this helps,

Matt S.



From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Matthias.Heise@atlas-elektronik.com
Sent: Thursday, December 04, 2014 1:49 AM
To: yocto@yoctoproject.org
Subject: Re: [yocto] u-boot precompiled ?

Even if this is a stupid question a little advise would be nice ... like "don't ask so stupid questions, go read this and that" or something... no time ? Should I rather unsubscribe from this list until I'm an expert?

Von: Heise, Matthias
Gesendet: Mittwoch, 3. Dezember 2014 15:15
An: 'yocto@yoctoproject.org'
Betreff: u-boot precompiled ?

Hi all,

I'm still trying to find out basic things about getting a system up and running. This question is about U-Boot, is it right that for example for my wandboard a pre-compiled *.imx is just downloaded ?
So if I want to make settings to U-Boot I make them directly in the source, compile it and re-direct in a recipe to take that new file as bootloader ? Or can I make the settings within a recipe and I just didn't find the spot ?
Thanks for your time,
Regards
Mat



[-- Attachment #2: Type: text/html, Size: 6956 bytes --]

Re: u-boot precompiled ?

[Matthias.Heise]

[-- Attachment #1: Type: text/plain, Size: 2677 bytes --]

Hello Matt,

thanks very much for your reply, I was able to create a simple patch changing an u-boot setting as test and "bbappended" it. I just didn't believe before that the various u-boot settings are "hard-coded" but they obviously are in the "<board>.h", so patching it seems to be the only way for changing settings from within yocto, right?
Regards,
Mat

Von: Matt Schuckmann [mailto:Matt.Schuckmann@planar.com]
Gesendet: Donnerstag, 4. Dezember 2014 18:31
An: Heise, Matthias; yocto@yoctoproject.org
Betreff: RE: u-boot precompiled ?

Mat,

I'm fairly new to OpenEmbedded (4 months now and I still feel like a noobi but I'm trying to give back while the pain is still fresh in my mind)
For something like u-boot it kind of depends on what your changing. If you need to change the u-boot code and the changes are small then typically you'd create a patch f for your changes and then make them part of a .bbappend in your layer for the recipe. There are examples on the net for how to create a .bbappend and reference the patch file.

Generally your .bbappend can be as simple as:

FILESEXTRAPATHS_prepend = ":${THISDIR}/files"
SRC_URI += "files://xyzzy.patch"

Where your patches are in subdirectory of your recipe directory.

Remember that generally recipes are about how to obtain the code, build it and package it for distribution, you can do recipes that deal with a pre-built binary but that is generally not the case.

Hope this helps,

Matt S.



From: yocto-bounces@yoctoproject.org<mailto:yocto-bounces@yoctoproject.org> [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Matthias.Heise@atlas-elektronik.com<mailto:Matthias.Heise@atlas-elektronik.com>
Sent: Thursday, December 04, 2014 1:49 AM
To: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
Subject: Re: [yocto] u-boot precompiled ?

Even if this is a stupid question a little advise would be nice ... like "don't ask so stupid questions, go read this and that" or something... no time ? Should I rather unsubscribe from this list until I'm an expert?

Von: Heise, Matthias
Gesendet: Mittwoch, 3. Dezember 2014 15:15
An: 'yocto@yoctoproject.org'
Betreff: u-boot precompiled ?

Hi all,

I'm still trying to find out basic things about getting a system up and running. This question is about U-Boot, is it right that for example for my wandboard a pre-compiled *.imx is just downloaded ?
So if I want to make settings to U-Boot I make them directly in the source, compile it and re-direct in a recipe to take that new file as bootloader ? Or can I make the settings within a recipe and I just didn't find the spot ?
Thanks for your time,
Regards
Mat

[-- Attachment #2: Type: text/html, Size: 9536 bytes --]

Re: u-boot precompiled ?

[Gary Thomas]

On 2014-12-05 05:48, Matthias.Heise@atlas-elektronik.com wrote:
> Hello Matt,
>
> thanks very much for your reply, I was able to create a simple patch changing an u-boot setting as test and “bbappended” it. I just didn’t believe before that the various u-boot
> settings are “hard-coded” but they obviously are in the “<board>.h”, so patching it seems to be the only way for changing settings from within yocto, right?

What U-Boot settings are you asking about?

> *Von:*Matt Schuckmann [mailto:Matt.Schuckmann@planar.com]
> *Gesendet:* Donnerstag, 4. Dezember 2014 18:31
> *An:* Heise, Matthias; yocto@yoctoproject.org
> *Betreff:* RE: u-boot precompiled ?
>
> Mat,
>
> I’m fairly new to OpenEmbedded (4 months now and I still feel like a noobi but I’m trying to give back while the pain is still fresh in my mind)
>
> For something like u-boot it kind of depends on what your changing. If you need to change the u-boot code and the changes are small then typically you’d create a patch f for your
> changes and then make them part of a .bbappend in your layer for the recipe. There are examples on the net for how to create a .bbappend and reference the patch file.
>
> Generally your .bbappend can be as simple as:
>
> FILESEXTRAPATHS_prepend = “:${THISDIR}/files”
>
> SRC_URI += “files://xyzzy.patch”
>
> Where your patches are in subdirectory of your recipe directory.
>
> Remember that generally recipes are about how to obtain the code, build it and package it for distribution, you can do recipes that deal with a pre-built binary but that is
> generally not the case.
>
> Hope this helps,
>
> Matt S.
>
> *From:*yocto-bounces@yoctoproject.org <mailto:yocto-bounces@yoctoproject.org> [mailto:yocto-bounces@yoctoproject.org] *On Behalf Of *Matthias.Heise@atlas-elektronik.com
> <mailto:Matthias.Heise@atlas-elektronik.com>
> *Sent:* Thursday, December 04, 2014 1:49 AM
> *To:* yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> *Subject:* Re: [yocto] u-boot precompiled ?
>
> Even if this is a stupid question a little advise would be nice … like “don’t ask so stupid questions, go read this and that” or something… no time ? Should I rather unsubscribe
> from this list until I’m an expert?
>
> *Von:*Heise, Matthias
> *Gesendet:* Mittwoch, 3. Dezember 2014 15:15
> *An:* 'yocto@yoctoproject.org'
> *Betreff:* u-boot precompiled ?
>
> Hi all,
>
> I’m still trying to find out basic things about getting a system up and running. This question is about U-Boot, is it right that for example for my wandboard a pre-compiled *.imx
> is just downloaded ?
>
> So if I want to make settings to U-Boot I make them directly in the source, compile it and re-direct in a recipe to take that new file as bootloader ? Or can I make the settings
> within a recipe and I just didn’t find the spot ?
>
> Thanks for your time,
>
> Regards
>
> Mat
>
>
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: u-boot precompiled ?

[Matthias.Heise]

> -----Ursprüngliche Nachricht-----
> Von: yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] Im Auftrag von Gary Thomas
> Gesendet: Freitag, 5. Dezember 2014 15:22
> An: yocto@yoctoproject.org
> Betreff: Re: [yocto] u-boot precompiled ?
> 
> On 2014-12-05 05:48, Matthias.Heise@atlas-elektronik.com wrote:
> > Hello Matt,
> >
> > thanks very much for your reply, I was able to create a simple patch
> > changing an u-boot setting as test and "bbappended" it. I just didn't
> believe before that the various u-boot settings are "hard-coded" but they
> obviously are in the "<board>.h", so patching it seems to be the only way for
> changing settings from within yocto, right?
> 
> What U-Boot settings are you asking about?

Starting with setting the boot-delay, via disabling the console, to setting up nfs- or other network-boot with it's parameters , or other boot sources