[Buildroot] First rootfile system build using buildroot

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

Hi ,

I am new to buildroot. I am Trying to learn it. I am following this manual.
http://buildroot.uclibc.org/downloads/manual/manual.html

So i have started with Rpi.

I am trying to build my own rootfile system for RPI using buildroot.

I have downloaded following cross compiler folder from git :--
https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian
as mentioned in this link :--
http://hertaville.com/2012/09/28/development-environment-raspberry-pi-cross-compiler/

My installer GCC compiler is :--
arm-linux-gnueabihf-gcc

crosscompiler is downloaded from git at following location:--
~/home/gcc-linaro-arm-linux-gnueabihf-raspbian

Please suggest what value to fill here for external toolchain selection,
some values i have filled :--

Toolchain type : External toolchain
Toolchain : Custom toolchain
Toolchain origin : Pre-installed toolchain
Toolchain path : ?
Toolchain prefix : ? external
Toolchain kernel header series : ?
external toolchain c library : ?

How i will come to know what is the kernel header is used by above cross
compiler ?

Please suggest.

// katoch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150831/d064c6e7/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

Please suggest have i posted to right list ?

Developer list or user list ?
On 31 Aug 2015 20:07, "Dinesh Guleria" <din.gulu.er@gmail.com> wrote:

> Hi ,
>
> I am new to buildroot. I am Trying to learn it. I am following this manual.
> http://buildroot.uclibc.org/downloads/manual/manual.html
>
> So i have started with Rpi.
>
> I am trying to build my own rootfile system for RPI using buildroot.
>
> I have downloaded following cross compiler folder from git :--
>
> https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian
> as mentioned in this link :--
>
> http://hertaville.com/2012/09/28/development-environment-raspberry-pi-cross-compiler/
>
> My installer GCC compiler is :--
> arm-linux-gnueabihf-gcc
>
> crosscompiler is downloaded from git at following location:--
> ~/home/gcc-linaro-arm-linux-gnueabihf-raspbian
>
> Please suggest what value to fill here for external toolchain selection,
> some values i have filled :--
>
> Toolchain type : External toolchain
> Toolchain : Custom toolchain
> Toolchain origin : Pre-installed toolchain
> Toolchain path : ?
> Toolchain prefix : ? external
> Toolchain kernel header series : ?
> external toolchain c library : ?
>
> How i will come to know what is the kernel header is used by above cross
> compiler ?
>
> Please suggest.
>
> // katoch
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150831/24e4ca5a/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Lee, Tommy]

Katoch,

My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05. I made the former meet the latter?s requirements. My target is Marvell ARMADA A385 (ARM-Cortex-A9) DB-88F6820-GP.

I have succeeded in the building of zImage. It is able to be booted up on the target, using U-Boot-1.73.

For this work I used the Buildroot internal toolchain; configured the rootfilesystem built into zImage and the device tree blob built outside zImage.

I hope my experience is useful for your work.

Tommy

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150831/756a5f96/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

>> My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05
Mine is also same.

>> For this work I used the Buildroot internal toolchain;
But manual says to use external tool chain, to reduce build time.

>> configured the rootfilesystem built into zImage and the device tree blob
built
I want to go step by step, first with separate rootfile system & zimage
with static nodes in dev directory. Then try on the advance combination.

Katoch
On 31 Aug 2015 21:23, "Lee, Tommy" <Tommy_Lee@alliedtelesis.com> wrote:

> Katoch,
>
>
>
> My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05. I made the
> former meet the latter?s requirements. My target is Marvell ARMADA A385
> (ARM-Cortex-A9) DB-88F6820-GP.
>
>
>
> I have succeeded in the building of zImage. It is able to be booted up on
> the target, using U-Boot-1.73.
>
>
>
> For this work I used the Buildroot internal toolchain; configured the
> rootfilesystem built into zImage and the device tree blob built outside
> zImage.
>
>
>
> I hope my experience is useful for your work.
>
>
>
> Tommy
>
> ------------------------------
> This e-mail message is for the sole use of the intended recipient(s) and
> may contain confidential and privileged information. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies of the original message. If you are the intended recipient,
> please be advised that the content of this message is subject to access,
> review and disclosure by the sender's e-mail System Administrator.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150831/3ff2f66d/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Lee, Tommy]

Katoch,

Using the internal toolchain saves your time and effort on the external toolchain installation. This is one of the Buildroot benefits.

Building the rootfilesystem into zImage resolves the rootfilesystem loading/linking issue clearly. I do not see any reason to build and load the rootfilesystem independently.

Tommy

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150831/fc42e45e/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

Thanks Tommy & Peter for your reply.

>> Either use the one generated by Buildroot ("Buildroot
toolchain") or use a pre-defined external toolchain ("Sourcery
CodeBench 2014.05" if you're using the RPi 1, or "Linaro" if you're
using the RPi 2).
I am using Rpi 1.

One more question from my side if i use " Sourcery
CodeBench 2014.05"  toolchain then buildroot will download it for me or i
have to download it manually ? Also if buildroot will download it then in
this case will it be a one time process or if i make a new build for my
rootfile system, then every time tool chain will be downloaded ?

What exactly the diffrence between using external tool chain like Sourcery
CodeBench 2014.05"  & building toolchain using crosstool-ng ?
http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/

>> Building the rootfilesystem into zImage resolves the rootfilesystem
loading/linking issue clearly.

Will uboot be able to understand that my rootfilesystem is inside my zimage
? Or i have to tell uboot explicitly ?

Katoch

Katoch,



Using the internal toolchain saves your time and effort on the external
toolchain installation. This is one of the Buildroot benefits.



Building the rootfilesystem into zImage resolves the rootfilesystem
loading/linking issue clearly. I do not see any reason to build and load
the rootfilesystem independently.



Tommy

------------------------------
This e-mail message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message. If you are the intended recipient,
please be advised that the content of this message is subject to access,
review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150901/83711aee/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Thomas Petazzoni]

Dear Dinesh Guleria,

On Tue, 1 Sep 2015 06:39:34 +0530, Dinesh Guleria wrote:

> One more question from my side if i use " Sourcery
> CodeBench 2014.05"  toolchain then buildroot will download it for me or i
> have to download it manually ?

Buildroot will download it for you.

> Also if buildroot will download it then in
> this case will it be a one time process or if i make a new build for my
> rootfile system, then every time tool chain will be downloaded ?

It is a one time process. Buildroot keeps a cache of the downloaded
files into the dl/ sub-directory (which can be customized using the
BR2_DL_DIR configuration option, which is also an environment variable).

> What exactly the diffrence between using external tool chain like Sourcery
> CodeBench 2014.05"  & building toolchain using crosstool-ng ?
> http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/

Sourcery CodeBench 2014.05 is a pre-built toolchain, used by a lot of
people. It's already there and available, hopefully quite well tested.
However, since it's pre-built, you cannot customize it.

Using crosstool-ng to build your toolchain allows to generate a
completely custom toolchain, tailored for your platform.

> >> Building the rootfilesystem into zImage resolves the rootfilesystem
> loading/linking issue clearly.
> 
> Will uboot be able to understand that my rootfilesystem is inside my zimage
> ? Or i have to tell uboot explicitly ?

If you're using an initramfs bundled inside the zImage, then U-Boot
does not even need to know about it. Just load the zImage in U-Boot,
start the kernel, and that's it.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

Thanks Thomas for your reply. I will use Sourcery CodeBench 2014.05 for
time being.

Build is taking some time. Will Get back to you.

Thanks & Regards,
Katoch



On Tue, Sep 1, 2015 at 12:28 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Dinesh Guleria,
>
> On Tue, 1 Sep 2015 06:39:34 +0530, Dinesh Guleria wrote:
>
> > One more question from my side if i use " Sourcery
> > CodeBench 2014.05"  toolchain then buildroot will download it for me or i
> > have to download it manually ?
>
> Buildroot will download it for you.
>
> > Also if buildroot will download it then in
> > this case will it be a one time process or if i make a new build for my
> > rootfile system, then every time tool chain will be downloaded ?
>
> It is a one time process. Buildroot keeps a cache of the downloaded
> files into the dl/ sub-directory (which can be customized using the
> BR2_DL_DIR configuration option, which is also an environment variable).
>
> > What exactly the diffrence between using external tool chain like
> Sourcery
> > CodeBench 2014.05"  & building toolchain using crosstool-ng ?
> >
> http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/
>
> Sourcery CodeBench 2014.05 is a pre-built toolchain, used by a lot of
> people. It's already there and available, hopefully quite well tested.
> However, since it's pre-built, you cannot customize it.
>
> Using crosstool-ng to build your toolchain allows to generate a
> completely custom toolchain, tailored for your platform.
>
> > >> Building the rootfilesystem into zImage resolves the rootfilesystem
> > loading/linking issue clearly.
> >
> > Will uboot be able to understand that my rootfilesystem is inside my
> zimage
> > ? Or i have to tell uboot explicitly ?
>
> If you're using an initramfs bundled inside the zImage, then U-Boot
> does not even need to know about it. Just load the zImage in U-Boot,
> start the kernel, and that's it.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150901/9c01709f/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

First build is successful. Some questions from my side.

Following images are generated :--
/output/images
rootsfs.tar
rootsfs.tar.gz


1> Why this fakeroot is downloaded ?
2>  Also in the name of the crosscompiler tool chain their is word "686-pc"
does it means tool chain for intel 686 PC ?
3> How to configure the busybox ? Build root make menuconfig does not
provide entry to configure the busy box ?
/dl
arm-2014.05-29-arm-none-linux-gnueabi-1686-pc-linux-gnu.tar.bz2
fakeroot_1.18.4.orig.tar.bz2
busybox-1.23.2.tar.bz2


4> Is this the place where toolchain is unzipped ?
/output/host/opt/ext-toolchain  location contains :--
arm-none-linux-gnueabi
bin
i686-pc-linux-gnu
lib
libexec
share

Regards,
Katoch

On Tue, Sep 1, 2015 at 4:55 PM, Dinesh Guleria <din.gulu.er@gmail.com>
wrote:

> Thanks Thomas for your reply. I will use Sourcery CodeBench 2014.05 for
> time being.
>
> Build is taking some time. Will Get back to you.
>
> Thanks & Regards,
> Katoch
>
>
>
> On Tue, Sep 1, 2015 at 12:28 PM, Thomas Petazzoni <
> thomas.petazzoni at free-electrons.com> wrote:
>
>> Dear Dinesh Guleria,
>>
>> On Tue, 1 Sep 2015 06:39:34 +0530, Dinesh Guleria wrote:
>>
>> > One more question from my side if i use " Sourcery
>> > CodeBench 2014.05"  toolchain then buildroot will download it for me or
>> i
>> > have to download it manually ?
>>
>> Buildroot will download it for you.
>>
>> > Also if buildroot will download it then in
>> > this case will it be a one time process or if i make a new build for my
>> > rootfile system, then every time tool chain will be downloaded ?
>>
>> It is a one time process. Buildroot keeps a cache of the downloaded
>> files into the dl/ sub-directory (which can be customized using the
>> BR2_DL_DIR configuration option, which is also an environment variable).
>>
>> > What exactly the diffrence between using external tool chain like
>> Sourcery
>> > CodeBench 2014.05"  & building toolchain using crosstool-ng ?
>> >
>> http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/
>>
>> Sourcery CodeBench 2014.05 is a pre-built toolchain, used by a lot of
>> people. It's already there and available, hopefully quite well tested.
>> However, since it's pre-built, you cannot customize it.
>>
>> Using crosstool-ng to build your toolchain allows to generate a
>> completely custom toolchain, tailored for your platform.
>>
>> > >> Building the rootfilesystem into zImage resolves the rootfilesystem
>> > loading/linking issue clearly.
>> >
>> > Will uboot be able to understand that my rootfilesystem is inside my
>> zimage
>> > ? Or i have to tell uboot explicitly ?
>>
>> If you're using an initramfs bundled inside the zImage, then U-Boot
>> does not even need to know about it. Just load the zImage in U-Boot,
>> start the kernel, and that's it.
>>
>> Best regards,
>>
>> Thomas
>> --
>> Thomas Petazzoni, CTO, Free Electrons
>> Embedded Linux, Kernel and Android engineering
>> http://free-electrons.com
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150901/700a1c9d/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Vicente Olivert Riera]

Dear Dinesh Guleria,

On 09/01/2015 01:02 PM, Dinesh Guleria wrote:
> First build is successful. Some questions from my side.
> 
> Following images are generated :--
> /output/images
> rootsfs.tar
> rootsfs.tar.gz
> 
> 
> 1> Why this fakeroot is downloaded ?

Because it's needed when generating the image files. Some actions
performed when creating the images would need superuser privileges, but
you run (or should run) Buildroot using a normal user account. fakeroot
fixes that issue by pretending a UID and GID of 0 (root).

> 2>  Also in the name of the crosscompiler tool chain their is word
> "686-pc" does it means tool chain for intel 686 PC ?

It means the toolchain binaries are built for that architecture, but
since it's a cross-toolchain, it can generate code for others.

> 3> How to configure the busybox ? Build root make menuconfig does not
> provide entry to configure the busy box ?
> /dl
> arm-2014.05-29-arm-none-linux-gnueabi-1686-pc-linux-gnu.tar.bz2
> fakeroot_1.18.4.orig.tar.bz2
> busybox-1.23.2.tar.bz2

make busybox-menuconfig

http://buildroot.org/manual.html#_configuration_of_other_components

> 
> 4> Is this the place where toolchain is unzipped ?
> /output/host/opt/ext-toolchain  location contains :--
> arm-none-linux-gnueabi 
> bin
> i686-pc-linux-gnu
> lib
> libexec
> share

Yes.

Regards,

Vincent.

> Regards,
> Katoch
> 
> On Tue, Sep 1, 2015 at 4:55 PM, Dinesh Guleria <din.gulu.er@gmail.com
> <mailto:din.gulu.er@gmail.com>> wrote:
> 
>     Thanks Thomas for your reply. I will use Sourcery CodeBench
>     2014.05 for time being.
> 
>     Build is taking some time. Will Get back to you.
> 
>     Thanks & Regards,
>     Katoch
> 
> 
> 
>     On Tue, Sep 1, 2015 at 12:28 PM, Thomas Petazzoni
>     <thomas.petazzoni@free-electrons.com
>     <mailto:thomas.petazzoni@free-electrons.com>> wrote:
> 
>         Dear Dinesh Guleria,
> 
>         On Tue, 1 Sep 2015 06:39:34 +0530, Dinesh Guleria wrote:
> 
>         > One more question from my side if i use " Sourcery
>         > CodeBench 2014.05"  toolchain then buildroot will download it for me or i
>         > have to download it manually ?
> 
>         Buildroot will download it for you.
> 
>         > Also if buildroot will download it then in
>         > this case will it be a one time process or if i make a new build for my
>         > rootfile system, then every time tool chain will be downloaded ?
> 
>         It is a one time process. Buildroot keeps a cache of the downloaded
>         files into the dl/ sub-directory (which can be customized using the
>         BR2_DL_DIR configuration option, which is also an environment
>         variable).
> 
>         > What exactly the diffrence between using external tool chain like Sourcery
>         > CodeBench 2014.05"  & building toolchain using crosstool-ng ?
>         > http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/
> 
>         Sourcery CodeBench 2014.05 is a pre-built toolchain, used by a
>         lot of
>         people. It's already there and available, hopefully quite well
>         tested.
>         However, since it's pre-built, you cannot customize it.
> 
>         Using crosstool-ng to build your toolchain allows to generate a
>         completely custom toolchain, tailored for your platform.
> 
>         > >> Building the rootfilesystem into zImage resolves the rootfilesystem
>         > loading/linking issue clearly.
>         >
>         > Will uboot be able to understand that my rootfilesystem is inside my zimage
>         > ? Or i have to tell uboot explicitly ?
> 
>         If you're using an initramfs bundled inside the zImage, then U-Boot
>         does not even need to know about it. Just load the zImage in U-Boot,
>         start the kernel, and that's it.
> 
>         Best regards,
> 
>         Thomas
>         --
>         Thomas Petazzoni, CTO, Free Electrons
>         Embedded Linux, Kernel and Android engineering
>         http://free-electrons.com
> 
> 
> 
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

Thanks Vincent.

Regards
Katoch
On 1 Sep 2015 17:44, "Vicente Olivert Riera" <Vincent.Riera@imgtec.com>
wrote:

> Dear Dinesh Guleria,
>
> On 09/01/2015 01:02 PM, Dinesh Guleria wrote:
> > First build is successful. Some questions from my side.
> >
> > Following images are generated :--
> > /output/images
> > rootsfs.tar
> > rootsfs.tar.gz
> >
> >
> > 1> Why this fakeroot is downloaded ?
>
> Because it's needed when generating the image files. Some actions
> performed when creating the images would need superuser privileges, but
> you run (or should run) Buildroot using a normal user account. fakeroot
> fixes that issue by pretending a UID and GID of 0 (root).
>
> > 2>  Also in the name of the crosscompiler tool chain their is word
> > "686-pc" does it means tool chain for intel 686 PC ?
>
> It means the toolchain binaries are built for that architecture, but
> since it's a cross-toolchain, it can generate code for others.
>
> > 3> How to configure the busybox ? Build root make menuconfig does not
> > provide entry to configure the busy box ?
> > /dl
> > arm-2014.05-29-arm-none-linux-gnueabi-1686-pc-linux-gnu.tar.bz2
> > fakeroot_1.18.4.orig.tar.bz2
> > busybox-1.23.2.tar.bz2
>
> make busybox-menuconfig
>
> http://buildroot.org/manual.html#_configuration_of_other_components
>
> >
> > 4> Is this the place where toolchain is unzipped ?
> > /output/host/opt/ext-toolchain  location contains :--
> > arm-none-linux-gnueabi
> > bin
> > i686-pc-linux-gnu
> > lib
> > libexec
> > share
>
> Yes.
>
> Regards,
>
> Vincent.
>
> > Regards,
> > Katoch
> >
> > On Tue, Sep 1, 2015 at 4:55 PM, Dinesh Guleria <din.gulu.er@gmail.com
> > <mailto:din.gulu.er@gmail.com>> wrote:
> >
> >     Thanks Thomas for your reply. I will use Sourcery CodeBench
> >     2014.05 for time being.
> >
> >     Build is taking some time. Will Get back to you.
> >
> >     Thanks & Regards,
> >     Katoch
> >
> >
> >
> >     On Tue, Sep 1, 2015 at 12:28 PM, Thomas Petazzoni
> >     <thomas.petazzoni@free-electrons.com
> >     <mailto:thomas.petazzoni@free-electrons.com>> wrote:
> >
> >         Dear Dinesh Guleria,
> >
> >         On Tue, 1 Sep 2015 06:39:34 +0530, Dinesh Guleria wrote:
> >
> >         > One more question from my side if i use " Sourcery
> >         > CodeBench 2014.05"  toolchain then buildroot will download it
> for me or i
> >         > have to download it manually ?
> >
> >         Buildroot will download it for you.
> >
> >         > Also if buildroot will download it then in
> >         > this case will it be a one time process or if i make a new
> build for my
> >         > rootfile system, then every time tool chain will be downloaded
> ?
> >
> >         It is a one time process. Buildroot keeps a cache of the
> downloaded
> >         files into the dl/ sub-directory (which can be customized using
> the
> >         BR2_DL_DIR configuration option, which is also an environment
> >         variable).
> >
> >         > What exactly the diffrence between using external tool chain
> like Sourcery
> >         > CodeBench 2014.05"  & building toolchain using crosstool-ng ?
> >         >
> http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/
> >
> >         Sourcery CodeBench 2014.05 is a pre-built toolchain, used by a
> >         lot of
> >         people. It's already there and available, hopefully quite well
> >         tested.
> >         However, since it's pre-built, you cannot customize it.
> >
> >         Using crosstool-ng to build your toolchain allows to generate a
> >         completely custom toolchain, tailored for your platform.
> >
> >         > >> Building the rootfilesystem into zImage resolves the
> rootfilesystem
> >         > loading/linking issue clearly.
> >         >
> >         > Will uboot be able to understand that my rootfilesystem is
> inside my zimage
> >         > ? Or i have to tell uboot explicitly ?
> >
> >         If you're using an initramfs bundled inside the zImage, then
> U-Boot
> >         does not even need to know about it. Just load the zImage in
> U-Boot,
> >         start the kernel, and that's it.
> >
> >         Best regards,
> >
> >         Thomas
> >         --
> >         Thomas Petazzoni, CTO, Free Electrons
> >         Embedded Linux, Kernel and Android engineering
> >         http://free-electrons.com
> >
> >
> >
> >
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150901/78bf1338/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Lee, Tommy]

Katosh,

?bootz 0x02000000 ? 0x01000000? is the U-Boot command I am using to boot my zImage and DTB. Before running this command, I download zImage and DTB to addresses 0x02000000 and 0x01000000 separately. My bootargs string is ?console=ttyS0,115200 root/dev/ram0 rw rootdelay=2?. I believe ? ? ? in the bootz command line tells U-Boot that the rootfilesystem has been built into zImage. You probably need to adjust you bootargs string.

Tommy

From: buildroot [mailto:buildroot-bounces at busybox.net] On Behalf Of Dinesh Guleria
Sent: Monday, August 31, 2015 6:10 PM
To: Lee, Tommy
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] First rootfile system build using buildroot


Thanks Tommy & Peter for your reply.

>> Either use the one generated by Buildroot ("Buildroot
toolchain") or use a pre-defined external toolchain ("Sourcery
CodeBench 2014.05" if you're using the RPi 1, or "Linaro" if you're
using the RPi 2).
I am using Rpi 1.

One more question from my side if i use " Sourcery
CodeBench 2014.05"  toolchain then buildroot will download it for me or i have to download it manually ? Also if buildroot will download it then in this case will it be a one time process or if i make a new build for my rootfile system, then every time tool chain will be downloaded ?

What exactly the diffrence between using external tool chain like Sourcery
CodeBench 2014.05"  & building toolchain using crosstool-ng ?
http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/

>> Building the rootfilesystem into zImage resolves the rootfilesystem loading/linking issue clearly.

Will uboot be able to understand that my rootfilesystem is inside my zimage ? Or i have to tell uboot explicitly ?

Katoch
Katoch,

Using the internal toolchain saves your time and effort on the external toolchain installation. This is one of the Buildroot benefits.

Building the rootfilesystem into zImage resolves the rootfilesystem loading/linking issue clearly. I do not see any reason to build and load the rootfilesystem independently.

Tommy

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150901/c218265c/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Lee, Tommy]

??.root/dev/ram0?.? Must be corrected to ??.root=/dev/ram0?.?. Sorry for typo.

From: buildroot [mailto:buildroot-bounces at busybox.net] On Behalf Of Lee, Tommy
Sent: Tuesday, September 01, 2015 8:54 AM
To: Dinesh Guleria
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] First rootfile system build using buildroot

Katosh,

?bootz 0x02000000 ? 0x01000000? is the U-Boot command I am using to boot my zImage and DTB. Before running this command, I download zImage and DTB to addresses 0x02000000 and 0x01000000 separately. My bootargs string is ?console=ttyS0,115200 root/dev/ram0 rw rootdelay=2?. I believe ? ? ? in the bootz command line tells U-Boot that the rootfilesystem has been built into zImage. You probably need to adjust you bootargs string.

Tommy

From: buildroot [mailto:buildroot-bounces at busybox.net] On Behalf Of Dinesh Guleria
Sent: Monday, August 31, 2015 6:10 PM
To: Lee, Tommy
Cc: buildroot at busybox.net<mailto:buildroot@busybox.net>
Subject: Re: [Buildroot] First rootfile system build using buildroot


Thanks Tommy & Peter for your reply.

>> Either use the one generated by Buildroot ("Buildroot
toolchain") or use a pre-defined external toolchain ("Sourcery
CodeBench 2014.05" if you're using the RPi 1, or "Linaro" if you're
using the RPi 2).
I am using Rpi 1.

One more question from my side if i use " Sourcery
CodeBench 2014.05"  toolchain then buildroot will download it for me or i have to download it manually ? Also if buildroot will download it then in this case will it be a one time process or if i make a new build for my rootfile system, then every time tool chain will be downloaded ?

What exactly the diffrence between using external tool chain like Sourcery
CodeBench 2014.05"  & building toolchain using crosstool-ng ?
http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/

>> Building the rootfilesystem into zImage resolves the rootfilesystem loading/linking issue clearly.

Will uboot be able to understand that my rootfilesystem is inside my zimage ? Or i have to tell uboot explicitly ?

Katoch
Katoch,

Using the internal toolchain saves your time and effort on the external toolchain installation. This is one of the Buildroot benefits.

Building the rootfilesystem into zImage resolves the rootfilesystem loading/linking issue clearly. I do not see any reason to build and load the rootfilesystem independently.

Tommy

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150901/04f751ac/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Lee, Tommy]

Katosh,
Please always include buildroot at busybox.net<mailto:buildroot@busybox.net> for messages exchange.

I did not use QEMU ever.

Tommy

From: Dinesh Guleria [mailto:din.gulu.er at gmail.com]
Sent: Tuesday, September 01, 2015 10:37 AM
To: Lee, Tommy
Subject: RE: [Buildroot] First rootfile system build using buildroot


Thanks.

Now my root filesystem is build, please suggest can i run it using qemu ?

Which version of qemu for ARM to use, any reference link which you may have used in past ?
On 1 Sep 2015 21:27, "Lee, Tommy" <Tommy_Lee at alliedtelesis.com<mailto:Tommy_Lee@alliedtelesis.com>> wrote:
??.root/dev/ram0?.? Must be corrected to ??.root=/dev/ram0?.?. Sorry for typo.

From: buildroot [mailto:buildroot-bounces at busybox.net<mailto:buildroot-bounces@busybox.net>] On Behalf Of Lee, Tommy
Sent: Tuesday, September 01, 2015 8:54 AM
To: Dinesh Guleria
Cc: buildroot at busybox.net<mailto:buildroot@busybox.net>
Subject: Re: [Buildroot] First rootfile system build using buildroot

Katosh,

?bootz 0x02000000 ? 0x01000000? is the U-Boot command I am using to boot my zImage and DTB. Before running this command, I download zImage and DTB to addresses 0x02000000 and 0x01000000 separately. My bootargs string is ?console=ttyS0,115200 root/dev/ram0 rw rootdelay=2?. I believe ? ? ? in the bootz command line tells U-Boot that the rootfilesystem has been built into zImage. You probably need to adjust you bootargs string.

Tommy

From: buildroot [mailto:buildroot-bounces at busybox.net] On Behalf Of Dinesh Guleria
Sent: Monday, August 31, 2015 6:10 PM
To: Lee, Tommy
Cc: buildroot at busybox.net<mailto:buildroot@busybox.net>
Subject: Re: [Buildroot] First rootfile system build using buildroot


Thanks Tommy & Peter for your reply.

>> Either use the one generated by Buildroot ("Buildroot
toolchain") or use a pre-defined external toolchain ("Sourcery
CodeBench 2014.05" if you're using the RPi 1, or "Linaro" if you're
using the RPi 2).
I am using Rpi 1.

One more question from my side if i use " Sourcery
CodeBench 2014.05"  toolchain then buildroot will download it for me or i have to download it manually ? Also if buildroot will download it then in this case will it be a one time process or if i make a new build for my rootfile system, then every time tool chain will be downloaded ?

What exactly the diffrence between using external tool chain like Sourcery
CodeBench 2014.05"  & building toolchain using crosstool-ng ?
http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/

>> Building the rootfilesystem into zImage resolves the rootfilesystem loading/linking issue clearly.

Will uboot be able to understand that my rootfilesystem is inside my zimage ? Or i have to tell uboot explicitly ?

Katoch
Katoch,

Using the internal toolchain saves your time and effort on the external toolchain installation. This is one of the Buildroot benefits.

Building the rootfilesystem into zImage resolves the rootfilesystem loading/linking issue clearly. I do not see any reason to build and load the rootfilesystem independently.

Tommy

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150901/f0d2782f/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

Sorry for mistake, i will repost.

Now my root filesystem is build, please suggest can i run it using qemu ?

Which version of qemu for ARM to use, any reference link which anyone on
list  may have used in past ?

Regards,
Katoch
On 1 Sep 2015 23:15, "Lee, Tommy" <Tommy_Lee@alliedtelesis.com> wrote:

> Katosh,
>
> Please always include buildroot at busybox.net for messages exchange.
>
>
>
> I did not use QEMU ever.
>
>
>
> Tommy
>
>
>
> *From:* Dinesh Guleria [mailto:din.gulu.er at gmail.com]
> *Sent:* Tuesday, September 01, 2015 10:37 AM
> *To:* Lee, Tommy
> *Subject:* RE: [Buildroot] First rootfile system build using buildroot
>
>
>
> Thanks.
>
> Now my root filesystem is build, please suggest can i run it using qemu ?
>
> Which version of qemu for ARM to use, any reference link which you may
> have used in past ?
>
> On 1 Sep 2015 21:27, "Lee, Tommy" <Tommy_Lee@alliedtelesis.com> wrote:
>
> ??.root/dev/ram0?.? Must be corrected to ??.root=/dev/ram0?.?. Sorry for
> typo.
>
>
>
> *From:* buildroot [mailto:buildroot-bounces at busybox.net] *On Behalf Of *Lee,
> Tommy
> *Sent:* Tuesday, September 01, 2015 8:54 AM
> *To:* Dinesh Guleria
> *Cc:* buildroot at busybox.net
> *Subject:* Re: [Buildroot] First rootfile system build using buildroot
>
>
>
> Katosh,
>
>
>
> ?bootz 0x02000000 ? 0x01000000? is the U-Boot command I am using to boot
> my zImage and DTB. Before running this command, I download zImage and DTB
> to addresses 0x02000000 and 0x01000000 separately. My bootargs string is
> ?console=ttyS0,115200 root/dev/ram0 rw rootdelay=2?. I believe ? ? ? in the
> bootz command line tells U-Boot that the rootfilesystem has been built into
> zImage. You probably need to adjust you bootargs string.
>
>
>
> Tommy
>
>
>
> *From:* buildroot [mailto:buildroot-bounces at busybox.net
> <buildroot-bounces@busybox.net>] *On Behalf Of *Dinesh Guleria
> *Sent:* Monday, August 31, 2015 6:10 PM
> *To:* Lee, Tommy
> *Cc:* buildroot at busybox.net
> *Subject:* Re: [Buildroot] First rootfile system build using buildroot
>
>
>
> Thanks Tommy & Peter for your reply.
>
> >> Either use the one generated by Buildroot ("Buildroot
> toolchain") or use a pre-defined external toolchain ("Sourcery
> CodeBench 2014.05" if you're using the RPi 1, or "Linaro" if you're
> using the RPi 2).
> I am using Rpi 1.
>
> One more question from my side if i use " Sourcery
> CodeBench 2014.05"  toolchain then buildroot will download it for me or i
> have to download it manually ? Also if buildroot will download it then in
> this case will it be a one time process or if i make a new build for my
> rootfile system, then every time tool chain will be downloaded ?
>
> What exactly the diffrence between using external tool chain like Sourcery
> CodeBench 2014.05"  & building toolchain using crosstool-ng ?
>
> http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/
>
> >> Building the rootfilesystem into zImage resolves the rootfilesystem
> loading/linking issue clearly.
>
> Will uboot be able to understand that my rootfilesystem is inside my
> zimage ? Or i have to tell uboot explicitly ?
>
> Katoch
>
> Katoch,
>
>
>
> Using the internal toolchain saves your time and effort on the external
> toolchain installation. This is one of the Buildroot benefits.
>
>
>
> Building the rootfilesystem into zImage resolves the rootfilesystem
> loading/linking issue clearly. I do not see any reason to build and load
> the rootfilesystem independently.
>
>
>
> Tommy
>
>
> ------------------------------
>
> This e-mail message is for the sole use of the intended recipient(s) and
> may contain confidential and privileged information. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies of the original message. If you are the intended recipient,
> please be advised that the content of this message is subject to access,
> review and disclosure by the sender's e-mail System Administrator.
>
>
> ------------------------------
>
> This e-mail message is for the sole use of the intended recipient(s) and
> may contain confidential and privileged information. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies of the original message. If you are the intended recipient,
> please be advised that the content of this message is subject to access,
> review and disclosure by the sender's e-mail System Administrator.
>
>
> ------------------------------
>
> This e-mail message is for the sole use of the intended recipient(s) and
> may contain confidential and privileged information. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies of the original message. If you are the intended recipient,
> please be advised that the content of this message is subject to access,
> review and disclosure by the sender's e-mail System Administrator.
>
> ------------------------------
> This e-mail message is for the sole use of the intended recipient(s) and
> may contain confidential and privileged information. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies of the original message. If you are the intended recipient,
> please be advised that the content of this message is subject to access,
> review and disclosure by the sender's e-mail System Administrator.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150902/57456ded/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Baruch Siach]

Hi Katoch,

On Wed, Sep 02, 2015 at 05:59:37AM +0530, Dinesh Guleria wrote:
> Now my root filesystem is build, please suggest can i run it using qemu ?
> 
> Which version of qemu for ARM to use, any reference link which anyone on
> list  may have used in past ?

There is a list of tested qemu configurations at configs/qemu_*. Instructions 
for running them are in readme.txt files under board/qemu/.

Hope this helps,
baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

Thanks Baruch.

I have successfully compiled a linux rootfs.Now I am trying to compile a
linux kernel using buildroot.
My kernel settings are ;--
Kernel version : 4.0.4
kernel configuration : use an in-tree deconfig file

But i am getting following error, when make :--
linux/linux.mk:367: *** No kernel defconfig name specified, check your
BR2_LINUX_KERNEL_DEFCONFIG setting.  Stop.


What i got is Buildroot is not able to find the kernel configuration file.
But my kernel is not downloaded by the Buildroot till yet.
And kernel configuration file is generated after we perform "make
menuconfig" to kernel. How to generate kernel configuration file, in this
case ?

Already Thomas have some reply here, but i did not get answer to it.
http://lists.busybox.net/pipermail/buildroot/2013-April/070180.html

what is the diffrence betwen :--
BR2_LINUX_KERNEL_DEFCONFIG  & BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE
enviromental variable.


How to resolve this error ?

Please suggest.

Regards,
katoch

On Wed, Sep 2, 2015 at 9:08 AM, Baruch Siach <baruch@tkos.co.il> wrote:

> Hi Katoch,
>
> On Wed, Sep 02, 2015 at 05:59:37AM +0530, Dinesh Guleria wrote:
> > Now my root filesystem is build, please suggest can i run it using qemu ?
> >
> > Which version of qemu for ARM to use, any reference link which anyone on
> > list  may have used in past ?
>
> There is a list of tested qemu configurations at configs/qemu_*.
> Instructions
> for running them are in readme.txt files under board/qemu/.
>
> Hope this helps,
> baruch
>
> --
>      http://baruch.siach.name/blog/                  ~. .~   Tk Open
> Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
>    - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150902/c4106b82/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Baruch Siach]

Hi Katoch,

On Wed, Sep 02, 2015 at 04:36:51PM +0530, Dinesh Guleria wrote:
> I have successfully compiled a linux rootfs.Now I am trying to compile a
> linux kernel using buildroot.
> My kernel settings are ;--
> Kernel version : 4.0.4
> kernel configuration : use an in-tree deconfig file
> 
> But i am getting following error, when make :--
> linux/linux.mk:367: *** No kernel defconfig name specified, check your
> BR2_LINUX_KERNEL_DEFCONFIG setting.  Stop.

This means that BR2_LINUX_KERNEL_DEFCONFIG is empty. You need to set 
BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name of your 
in-tree defconfig file.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

>> You need to set
BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name of your
in-tree defconfig file.
Is this file an existing file or will be created at runtime ? If existing
then where does this in-tree deconfig file lies in the buildroot directory ?

Regards,
Katoch
Hi Katoch,

On Wed, Sep 02, 2015 at 04:36:51PM +0530, Dinesh Guleria wrote:
> I have successfully compiled a linux rootfs.Now I am trying to compile a
> linux kernel using buildroot.
> My kernel settings are ;--
> Kernel version : 4.0.4
> kernel configuration : use an in-tree deconfig file
>
> But i am getting following error, when make :--
> linux/linux.mk:367: *** No kernel defconfig name specified, check your
> BR2_LINUX_KERNEL_DEFCONFIG setting.  Stop.

This means that BR2_LINUX_KERNEL_DEFCONFIG is empty. You need to set
BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name of your
in-tree defconfig file.

baruch

--
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150902/bcd9e544/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Vicente Olivert Riera]

Dear Katoch,

one quick question. Which one is your name, "Katoch" or "Dinesh Guleira"?

On 09/02/2015 02:54 PM, Dinesh Guleria wrote:
>>> You need to set
> BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name of your
> in-tree defconfig file.
> Is this file an existing file or will be created at runtime ? If
> existing then where does this in-tree deconfig file lies in the
> buildroot directory ?

it is an existing defconfig file in the kernel tree, not in the
Buildroot tree. You can find them in "arch/<your architecture>/configs/".

If you want to use a custom defconfig file, then place it into the
Buildroot tree, maybe at $(TOPDIR), and use the appropriate option in
the Buildroot menuconfig.

Regards,

Vincent.

> Regards,
> Katoch
> 
> Hi Katoch,
> 
> On Wed, Sep 02, 2015 at 04:36:51PM +0530, Dinesh Guleria wrote:
>> I have successfully compiled a linux rootfs.Now I am trying to compile a
>> linux kernel using buildroot.
>> My kernel settings are ;--
>> Kernel version : 4.0.4
>> kernel configuration : use an in-tree deconfig file
>>
>> But i am getting following error, when make :--
>> linux/linux.mk:367 <http://linux.mk:367>: *** No kernel defconfig name
> specified, check your
>> BR2_LINUX_KERNEL_DEFCONFIG setting.  Stop.
> 
> This means that BR2_LINUX_KERNEL_DEFCONFIG is empty. You need to set
> BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name of your
> in-tree defconfig file.
> 
> baruch
> 
> --
>      http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
>    - baruch at tkos.co.il <mailto:baruch@tkos.co.il> - tel:
> +972.2.679.5364, http://www.tkos.co.il -
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

>> one quick question. Which one is your name, "Katoch" or "Dinesh Guleira"?
Katoch is my nick name real name is as per my mail id Dinesh Guleria .. :-)

>> it is an existing defconfig file in the kernel tree, not in the
Buildroot tree. You can find them in "arch/<your architecture>/configs/".
So i need to copy this file from kernel tree to my buildroot tree & point
BR2_LINUX_KERNEL_DEFCONFIG variable to it. Right ?

Regards,
Katoch
On 2 Sep 2015 19:29, "Vicente Olivert Riera" <Vincent.Riera@imgtec.com>
wrote:

> Dear Katoch,
>
> one quick question. Which one is your name, "Katoch" or "Dinesh Guleira"?
>
> On 09/02/2015 02:54 PM, Dinesh Guleria wrote:
> >>> You need to set
> > BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name of your
> > in-tree defconfig file.
> > Is this file an existing file or will be created at runtime ? If
> > existing then where does this in-tree deconfig file lies in the
> > buildroot directory ?
>
> it is an existing defconfig file in the kernel tree, not in the
> Buildroot tree. You can find them in "arch/<your architecture>/configs/".
>
> If you want to use a custom defconfig file, then place it into the
> Buildroot tree, maybe at $(TOPDIR), and use the appropriate option in
> the Buildroot menuconfig.
>
> Regards,
>
> Vincent.
>
> > Regards,
> > Katoch
> >
> > Hi Katoch,
> >
> > On Wed, Sep 02, 2015 at 04:36:51PM +0530, Dinesh Guleria wrote:
> >> I have successfully compiled a linux rootfs.Now I am trying to compile a
> >> linux kernel using buildroot.
> >> My kernel settings are ;--
> >> Kernel version : 4.0.4
> >> kernel configuration : use an in-tree deconfig file
> >>
> >> But i am getting following error, when make :--
> >> linux/linux.mk:367 <http://linux.mk:367>: *** No kernel defconfig name
> > specified, check your
> >> BR2_LINUX_KERNEL_DEFCONFIG setting.  Stop.
> >
> > This means that BR2_LINUX_KERNEL_DEFCONFIG is empty. You need to set
> > BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name of your
> > in-tree defconfig file.
> >
> > baruch
> >
> > --
> >      http://baruch.siach.name/blog/                  ~. .~   Tk Open
> Systems
> >
> =}------------------------------------------------ooO--U--Ooo------------{=
> >    - baruch at tkos.co.il <mailto:baruch@tkos.co.il> - tel:
> > +972.2.679.5364, http://www.tkos.co.il -
> >
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150902/39bf6c1e/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Vicente Olivert Riera]

Dear Dinesh Guleria,

On 09/02/2015 03:51 PM, Dinesh Guleria wrote:
>>> one quick question. Which one is your name, "Katoch" or "Dinesh Guleira"?
> Katoch is my nick name real name is as per my mail id Dinesh Guleria .. :-)
> 
>>> it is an existing defconfig file in the kernel tree, not in the
> Buildroot tree. You can find them in "arch/<your architecture>/configs/".
> So i need to copy this file from kernel tree to my buildroot tree & point
> BR2_LINUX_KERNEL_DEFCONFIG variable to it. Right ?

no, you have to go to:

Kernel
-> Linux Kernel
  -> Kernel configuration

And choose "Using an in-tree defconfig file", which is the default option.

Now go to:

Kernel
-> Linux Kernel
  -> Defconfig name

And type the name of the defconfig (without the trailing _defconfig).

Regards,

Vincent.

> Regards,
> Katoch
> 
> On 2 Sep 2015 19:29, "Vicente Olivert Riera" <Vincent.Riera@imgtec.com
> <mailto:Vincent.Riera@imgtec.com>> wrote:
> 
>     Dear Katoch,
> 
>     one quick question. Which one is your name, "Katoch" or "Dinesh
>     Guleira"?
> 
>     On 09/02/2015 02:54 PM, Dinesh Guleria wrote:
>     >>> You need to set
>     > BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name
>     of your
>     > in-tree defconfig file.
>     > Is this file an existing file or will be created at runtime ? If
>     > existing then where does this in-tree deconfig file lies in the
>     > buildroot directory ?
> 
>     it is an existing defconfig file in the kernel tree, not in the
>     Buildroot tree. You can find them in "arch/<your
>     architecture>/configs/".
> 
>     If you want to use a custom defconfig file, then place it into the
>     Buildroot tree, maybe at $(TOPDIR), and use the appropriate option in
>     the Buildroot menuconfig.
> 
>     Regards,
> 
>     Vincent.
> 
>     > Regards,
>     > Katoch
>     >
>     > Hi Katoch,
>     >
>     > On Wed, Sep 02, 2015 at 04:36:51PM +0530, Dinesh Guleria wrote:
>     >> I have successfully compiled a linux rootfs.Now I am trying to
>     compile a
>     >> linux kernel using buildroot.
>     >> My kernel settings are ;--
>     >> Kernel version : 4.0.4
>     >> kernel configuration : use an in-tree deconfig file
>     >>
>     >> But i am getting following error, when make :--
>     >> linux/linux.mk:367 <http://linux.mk:367> <http://linux.mk:367>:
>     *** No kernel defconfig name
>     > specified, check your
>     >> BR2_LINUX_KERNEL_DEFCONFIG setting.  Stop.
>     >
>     > This means that BR2_LINUX_KERNEL_DEFCONFIG is empty. You need to set
>     > BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name
>     of your
>     > in-tree defconfig file.
>     >
>     > baruch
>     >
>     > --
>     >      http://baruch.siach.name/blog/                  ~. .~   Tk
>     Open Systems
>     >
>     =}------------------------------------------------ooO--U--Ooo------------{=
>     >    - baruch at tkos.co.il <mailto:baruch@tkos.co.il>
>     <mailto:baruch at tkos.co.il <mailto:baruch@tkos.co.il>> - tel:
>     > +972.2.679.5364, http://www.tkos.co.il -
>     >
>     >
>     > _______________________________________________
>     > buildroot mailing list
>     > buildroot at busybox.net <mailto:buildroot@busybox.net>
>     > http://lists.busybox.net/mailman/listinfo/buildroot
>     >
> 

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

>> And choose "Using an in-tree defconfig file", which is the default
option.
Done

>> And type the name of the defconfig (without the trailing _defconfig).
As i need to build for raspberrypi.
And as I have *raspberrypi_deconfig* in my following directory /config of
buildroot.
So i write the name as *raspberrypi *.

But getting following error at the time of make . see the attached image.

Regards,
Katoch

On Wed, Sep 2, 2015 at 8:25 PM, Vicente Olivert Riera <
Vincent.Riera@imgtec.com> wrote:

> Dear Dinesh Guleria,
>
> On 09/02/2015 03:51 PM, Dinesh Guleria wrote:
> >>> one quick question. Which one is your name, "Katoch" or "Dinesh
> Guleira"?
> > Katoch is my nick name real name is as per my mail id Dinesh Guleria ..
> :-)
> >
> >>> it is an existing defconfig file in the kernel tree, not in the
> > Buildroot tree. You can find them in "arch/<your architecture>/configs/".
> > So i need to copy this file from kernel tree to my buildroot tree & point
> > BR2_LINUX_KERNEL_DEFCONFIG variable to it. Right ?
>
> no, you have to go to:
>
> Kernel
> -> Linux Kernel
>   -> Kernel configuration
>
> And choose "Using an in-tree defconfig file", which is the default option.
>
> Now go to:
>
> Kernel
> -> Linux Kernel
>   -> Defconfig name
>
> And type the name of the defconfig (without the trailing _defconfig).
>
> Regards,
>
> Vincent.
>
> > Regards,
> > Katoch
> >
> > On 2 Sep 2015 19:29, "Vicente Olivert Riera" <Vincent.Riera@imgtec.com
> > <mailto:Vincent.Riera@imgtec.com>> wrote:
> >
> >     Dear Katoch,
> >
> >     one quick question. Which one is your name, "Katoch" or "Dinesh
> >     Guleira"?
> >
> >     On 09/02/2015 02:54 PM, Dinesh Guleria wrote:
> >     >>> You need to set
> >     > BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name
> >     of your
> >     > in-tree defconfig file.
> >     > Is this file an existing file or will be created at runtime ? If
> >     > existing then where does this in-tree deconfig file lies in the
> >     > buildroot directory ?
> >
> >     it is an existing defconfig file in the kernel tree, not in the
> >     Buildroot tree. You can find them in "arch/<your
> >     architecture>/configs/".
> >
> >     If you want to use a custom defconfig file, then place it into the
> >     Buildroot tree, maybe at $(TOPDIR), and use the appropriate option in
> >     the Buildroot menuconfig.
> >
> >     Regards,
> >
> >     Vincent.
> >
> >     > Regards,
> >     > Katoch
> >     >
> >     > Hi Katoch,
> >     >
> >     > On Wed, Sep 02, 2015 at 04:36:51PM +0530, Dinesh Guleria wrote:
> >     >> I have successfully compiled a linux rootfs.Now I am trying to
> >     compile a
> >     >> linux kernel using buildroot.
> >     >> My kernel settings are ;--
> >     >> Kernel version : 4.0.4
> >     >> kernel configuration : use an in-tree deconfig file
> >     >>
> >     >> But i am getting following error, when make :--
> >     >> linux/linux.mk:367 <http://linux.mk:367> <http://linux.mk:367>:
> >     *** No kernel defconfig name
> >     > specified, check your
> >     >> BR2_LINUX_KERNEL_DEFCONFIG setting.  Stop.
> >     >
> >     > This means that BR2_LINUX_KERNEL_DEFCONFIG is empty. You need to
> set
> >     > BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name
> >     of your
> >     > in-tree defconfig file.
> >     >
> >     > baruch
> >     >
> >     > --
> >     >      http://baruch.siach.name/blog/                  ~. .~   Tk
> >     Open Systems
> >     >
> >
>  =}------------------------------------------------ooO--U--Ooo------------{=
> >     >    - baruch at tkos.co.il <mailto:baruch@tkos.co.il>
> >     <mailto:baruch at tkos.co.il <mailto:baruch@tkos.co.il>> - tel:
> >     > +972.2.679.5364, http://www.tkos.co.il -
> >     >
> >     >
> >     > _______________________________________________
> >     > buildroot mailing list
> >     > buildroot at busybox.net <mailto:buildroot@busybox.net>
> >     > http://lists.busybox.net/mailman/listinfo/buildroot
> >     >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150902/82a3ef4b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linux_error.png
Type: image/png
Size: 207492 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150902/82a3ef4b/attachment-0001.png>

[Buildroot] First rootfile system build using buildroot

[Baruch Siach]

Hi Katoch,

On Wed, Sep 02, 2015 at 10:27:01PM +0530, Dinesh Guleria wrote:
> >> And type the name of the defconfig (without the trailing _defconfig).
> As i need to build for raspberrypi.
> And as I have *raspberrypi_deconfig* in my following directory /config of
> buildroot.
> So i write the name as *raspberrypi *.
> 
> But getting following error at the time of make . see the attached image.

This option is about the *kernel* config, not Buildroot one. You find the list 
of kernel defconfig files under the arch/<your architecture>/configs/ 
directory of the *kernel*.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

>> You find the list of kernel defconfig files under the arch/<your
architecture>/configs/ directory of the *kernel*.
   I have selected bcm2835 (Rpi controller), its building fine.

Buildroot /board directory contains folder for many boards. What is the
significance of buildroot /board directory ?


What is the significance of  *_deconfig files under buildroot directory
/configs

Regards,
katoch

On Wed, Sep 2, 2015 at 10:46 PM, Baruch Siach <baruch@tkos.co.il> wrote:

> Hi Katoch,
>
> On Wed, Sep 02, 2015 at 10:27:01PM +0530, Dinesh Guleria wrote:
> > >> And type the name of the defconfig (without the trailing _defconfig).
> > As i need to build for raspberrypi.
> > And as I have *raspberrypi_deconfig* in my following directory /config of
> > buildroot.
> > So i write the name as *raspberrypi *.
> >
> > But getting following error at the time of make . see the attached image.
>
> This option is about the *kernel* config, not Buildroot one. You find the
> list
> of kernel defconfig files under the arch/<your architecture>/configs/
> directory of the *kernel*.
>
> baruch
>
> --
>      http://baruch.siach.name/blog/                  ~. .~   Tk Open
> Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
>    - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150902/cf494763/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Dinesh Guleria]

getting this error  --> "specify loadaddr on the commandline to build an
uimage"
As i am using bcm2835_deconfig and i am building Uimage(as u-boot needs a
kernel in uImage format) for kernel.

Now what value should i specify for the *loadaddr . *How is the loadaddr
value decided ? Does it come from controller specs or MCU supplier provides
this value ?

Regards,
katoch

On Wed, Sep 2, 2015 at 11:28 PM, Dinesh Guleria <din.gulu.er@gmail.com>
wrote:

> >> You find the list of kernel defconfig files under the arch/<your
> architecture>/configs/ directory of the *kernel*.
>    I have selected bcm2835 (Rpi controller), its building fine.
>
> Buildroot /board directory contains folder for many boards. What is the
> significance of buildroot /board directory ?
>
>
> What is the significance of  *_deconfig files under buildroot directory
> /configs
>
> Regards,
> katoch
>
> On Wed, Sep 2, 2015 at 10:46 PM, Baruch Siach <baruch@tkos.co.il> wrote:
>
>> Hi Katoch,
>>
>> On Wed, Sep 02, 2015 at 10:27:01PM +0530, Dinesh Guleria wrote:
>> > >> And type the name of the defconfig (without the trailing _defconfig).
>> > As i need to build for raspberrypi.
>> > And as I have *raspberrypi_deconfig* in my following directory /config
>> of
>> > buildroot.
>> > So i write the name as *raspberrypi *.
>> >
>> > But getting following error at the time of make . see the attached
>> image.
>>
>> This option is about the *kernel* config, not Buildroot one. You find the
>> list
>> of kernel defconfig files under the arch/<your architecture>/configs/
>> directory of the *kernel*.
>>
>> baruch
>>
>> --
>>      http://baruch.siach.name/blog/                  ~. .~   Tk Open
>> Systems
>>
>> =}------------------------------------------------ooO--U--Ooo------------{=
>>    - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150902/89fe5d86/attachment.html>

[Buildroot] First rootfile system build using buildroot

[Samuel Martin]

Hi Katoch,

On Wed, Sep 2, 2015 at 7:58 PM, Dinesh Guleria <din.gulu.er@gmail.com> wrote:
>>> You find the list of kernel defconfig files under the arch/<your
>>> architecture>/configs/ directory of the *kernel*.
>    I have selected bcm2835 (Rpi controller), its building fine.
>
> Buildroot /board directory contains folder for many boards. What is the
> significance of buildroot /board directory ?

You might find some answers here [1] (even if this section of the
manual is about for user's project customization, the rough idea is
still followed in the official buildroot tree).

>
>
> What is the significance of  *_deconfig files under buildroot directory
> /configs
>

Please, understand that Buildroot uses the same configuration tool as
the linux kernel, i.e. Kconfig.
So, the *_defconfig files in the <buildroot>/configs/ directory are
exactly the same that what the *_defconfig files in
<linux>/arch/<your_arch>/configs/ are.
IOW,:
- for the kernel: a <cpu>_defconfig file is the minimal set of linux'
configurations for the given CPU;
- for Buildroot: a <target>_defconfig file is the minimal set of
Buildroot's configurations for the given target, with one of these
configurations being the kernel's defconfig name or configuration file
(depending on your selection in the menu).


Take some time in the Buildroot manual [2] (at least, parts I and II),
you'll certainly learn something useful for your work.
Then, if you have not found the answers to some question, let us know
what is missing in the manual (we try hard to make Buildroot easy for
new comers, including the manual ;-]).


[1] http://buildroot.org/downloads/manual/manual.html#customize-dir-structure
[2] http://buildroot.org/downloads/manual/manual.html


> Regards,
> katoch
>
> On Wed, Sep 2, 2015 at 10:46 PM, Baruch Siach <baruch@tkos.co.il> wrote:
>>
>> Hi Katoch,
>>
>> On Wed, Sep 02, 2015 at 10:27:01PM +0530, Dinesh Guleria wrote:
>> > >> And type the name of the defconfig (without the trailing _defconfig).
>> > As i need to build for raspberrypi.
>> > And as I have *raspberrypi_deconfig* in my following directory /config
>> > of
>> > buildroot.
>> > So i write the name as *raspberrypi *.
>> >
>> > But getting following error at the time of make . see the attached
>> > image.
>>
>> This option is about the *kernel* config, not Buildroot one. You find the
>> list
>> of kernel defconfig files under the arch/<your architecture>/configs/
>> directory of the *kernel*.
>>
>> baruch
>>
>> --
>>      http://baruch.siach.name/blog/                  ~. .~   Tk Open
>> Systems
>>
>> =}------------------------------------------------ooO--U--Ooo------------{=
>>    - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

Regards,

-- 
Samuel

[Buildroot] First rootfile system build using buildroot

[Thomas Petazzoni]

Hello,

On Mon, 31 Aug 2015 13:58:04 -0700, Lee, Tommy wrote:

> Building the rootfilesystem into zImage resolves the rootfilesystem
> loading/linking issue clearly. I do not see any reason to build and
> load the rootfilesystem independently.

If by "building the root filesystem into zImage" you mean using the
initramfs mechanism, then clearly there is a reason to have the root
filesystem independently.

The initramfs mechanism is OK when the filesystem is relatively small.
When it starts to be bigger, then initramfs has a number of drawbacks:

 * The entire root filesystem must be loaded at boot time. If you have
   a 5 or 6 MB root filesystem, that's probably alright. But if you
   have a 100-200 MB root filesystem, then it's going to take a while.
   By using a normal root filesystem, it gets mounted at boot time, but
   not its entire contents are loaded into memory at boot time.

 * The entire root filesystem will always be in memory, consuming this
   memory. Again if your filesystem is 5, 6, 8 or 16 MB, this might be
   alright. But if your filesystem is 100-200 MB, you probably don't
   want those 100-200 MB to be permanently loaded into memory.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] First rootfile system build using buildroot

[Thomas Petazzoni]

Dinesh,

On Mon, 31 Aug 2015 20:07:50 +0530, Dinesh Guleria wrote:

> I am new to buildroot. I am Trying to learn it. I am following this manual.
> http://buildroot.uclibc.org/downloads/manual/manual.html
> 
> So i have started with Rpi.
> 
> I am trying to build my own rootfile system for RPI using buildroot.
> 
> I have downloaded following cross compiler folder from git :--
> https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian
> as mentioned in this link :--
> http://hertaville.com/2012/09/28/development-environment-raspberry-pi-cross-compiler/

If you're a beginner with Buildroot, don't start with a customer
compiler. Either use the one generated by Buildroot ("Buildroot
toolchain") or use a pre-defined external toolchain ("Sourcery
CodeBench 2014.05" if you're using the RPi 1, or "Linaro" if you're
using the RPi 2).

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com