[Buildroot] First rootfile system build using buildroot

Lee, Tommy Tommy_Lee at alliedtelesis.com
Tue Sep 1 17:45:01 UTC 2015


Katosh,
Please always include buildroot at busybox.net<mailto: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 at alliedtelesis.com<mailto:Tommy_Lee at 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 at 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 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 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/20150901/f0d2782f/attachment-0002.html>


More information about the buildroot mailing list