Skip to contentSkip to conversation

Basic questions about using BuildRoot

Buildroot Martin Peevski 6 participants 25 messages Sep 15, 2012 – Oct 3, 2012 3 messages not in the archive

lore
Share & tools
lore
#0 lore raw

Hello, I'm new embedded Linux user and need a little help to build
embedded Linux system with BuildRoot tool for AT91SAM9263 target. May questions are described below:

1. After system configuration is done with make menuconfig
command, shall I execute only make command to build the entire embedded system? Or there is need to execute make at91sam9263ek_defconfig command prior or after the pure make command?

2. If I not make additional configuration with busybox-menuconfig
or the corresponding command for configuration the Linux Kernel, shall the build system work on the target?

I will be thankful to any help!
With best regards, Martin Peevski.

#1 lore raw

Op 15 sep. 2012 19:29 schreef "Martin Peevski" <[email protected]> het volgende:

Quoted 2 lines

Hello, I'm new embedded Linux user and need a little help to build

embedded Linux system with BuildRoot tool for AT91SAM9263 target. May questions are described below:

Quoted 2 lines

1. After system configuration is done with make menuconfig command,

shall I execute only make command to build the entire embedded system? Or there is need to execute make at91sam9263ek_defconfig command prior or after the pure make command?

If there is a defconfig for your board, you would start with 'make xxx_defconfig' and then possibly 'make menuconfig' to tune the configuration. The defconfig serves as a start that should work out of the box.

Quoted 2 lines

2. If I not make additional configuration with busybox-menuconfig or

the corresponding command for configuration the Linux Kernel, shall the build system work on the target?

If you started from a defconfig that corresponds to your board, then yes it's supposed to work just like that.

Quoted 4 lines

I will be thankful to any help!
With best regards, Martin Peevski.

Best regards,
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120915/1e90cd26/attachment.html>

#3 lore raw
In reply to a message not in the archive

Hi Martin,

Please keep the list in copy, and please don't top-post...

Op 15 sep. 2012 20:17 schreef "Martin Peevski" <[email protected]> het volgende:

Quoted 4 lines

Thank you very much for the fast response!

When i wrote the first letter the building was in progress. When it

finish only the u-boot.bin was in the output/images/ directory. Neither a Kernel nor a File system was build. It was included in the menuconfig but was not build. Also i program the u-boot.bin in the target and it not work. Can you please help me again to resolve that problem?

If the kernel is not built and there were no errors during the build process, it must mean that your config is not ok.
Can you re-verify the .config file for e.g. the kernel settings?

Note that I don't have specific experience with this board nor with uboot, so I can't answer that question.
In general, I'd wonder whether you programmed the bootloader correctly, what the errors were you encountered, if any, ...
Did you follow the procedure regarding configuration I outlined in my first response? First defconfig, then make. Can you try with a clean defconfig without any modifications?

Best regards, Thomas

Quoted 9 lines · Thomas De Schampheleire
Quoted 3 lines

Op 15 sep. 2012 19:29 schreef "Martin Peevski" <[email protected]> het

volgende:

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Hello, I'm new embedded Linux user and need a little help to

build embedded Linux system with BuildRoot tool for AT91SAM9263 target. May questions are described below:

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

1. After system configuration is done with make menuconfig

command, shall I execute only make command to build the entire embedded system? Or there is need to execute make at91sam9263ek_defconfig command prior or after the pure make command?

Quoted 2 lines
Quoted 2 lines

If there is a defconfig for your board, you would start with 'make

xxx_defconfig' and then possibly 'make menuconfig' to tune the configuration. The defconfig serves as a start that should work out of the box.

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

2. If I not make additional configuration with busybox-menuconfig

or the corresponding command for configuration the Linux Kernel, shall the build system work on the target?

Quoted 2 lines
Quoted 2 lines

If you started from a defconfig that corresponds to your board, then yes

it's supposed to work just like that.

Quoted 10 lines
Quoted 8 lines
Quoted 5 lines

I will be thankful to any help!
With best regards, Martin Peevski.

Best regards,
Thomas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120915/6632e400/attachment-0001.html>

#5 lore raw
In reply to a message not in the archive

Hi Martin,

Op 16 sep. 2012 12:26 schreef "Martin Peevski" <[email protected]> het volgende:

Quoted 15 lines

-------- Original Message --------
Subject:
Re: [Buildroot] Basic questions about using BuildRoot Date:
Sat, 15 Sep 2012 20:26:18 +0200
From:
Thomas De Schampheleire <[email protected]> To:
Martin Peevski <[email protected]>, buildroot <[email protected]>

Quoted 5 lines

Hi Martin,

Please keep the list in copy, and please don't top-post...

Op 15 sep. 2012 20:17 schreef "Martin Peevski" <[email protected]> het

volgende:

Quoted 4 lines
Quoted 4 lines

Thank you very much for the fast response!

When i wrote the first letter the building was in progress. When

it finish only the u-boot.bin was in the output/images/ directory. Neither a Kernel nor a File system was build. It was included in the menuconfig but was not build. Also i program the u-boot.bin in the target and it not work. Can you please help me again to resolve that problem?

Quoted 2 lines

If the kernel is not built and there were no errors during the build

process, it must mean that your config is not ok.

Quoted 3 lines

Can you re-verify the .config file for e.g. the kernel settings?

Note that I don't have specific experience with this board nor with

uboot, so I can't answer that question.

Quoted 1 line

In general, I'd wonder whether you programmed the bootloader correctly,

what the errors were you encountered, if any, ...

Quoted 1 line

Did you follow the procedure regarding configuration I outlined in my

first response? First defconfig, then make. Can you try with a clean defconfig without any modifications?

Quoted 12 lines

Best regards, Thomas

Quoted 9 lines · Thomas De Schampheleire
Quoted 3 lines

Op 15 sep. 2012 19:29 schreef "Martin Peevski" <[email protected]> het

volgende:

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Hello, I'm new embedded Linux user and need a little help to

build embedded Linux system with BuildRoot tool for AT91SAM9263 target. May questions are described below:

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

1. After system configuration is done with make menuconfig

command, shall I execute only make command to build the entire embedded system? Or there is need to execute make at91sam9263ek_defconfig command prior or after the pure make command?

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

If there is a defconfig for your board, you would start with 'make

xxx_defconfig' and then possibly 'make menuconfig' to tune the configuration. The defconfig serves as a start that should work out of the box.

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

2. If I not make additional configuration with

busybox-menuconfig or the corresponding command for configuration the Linux Kernel, shall the build system work on the target?

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

If you started from a defconfig that corresponds to your board, then

yes it's supposed to work just like that.

Quoted 14 lines
Quoted 10 lines
Quoted 8 lines
Quoted 5 lines

I will be thankful to any help!
With best regards, Martin Peevski.

Best regards,
Thomas

Quoted 2 lines

Hi Tomas,
ok, I stop to top-post :)

That's already good, now try to keep the list in copy as well, there may be people with more experience with your board...

Quoted 1 line

It's a new day in Bulgaria and I try again to build running embedded

Linux with at91sam9263 again. In brief I do the following:

Quoted 4 lines

1. Run "make clean", "make distclean" to clean everything;

2. Following your advice in the last letter, I try only with "make

at91sam9263_defconfig" but the build stop because uClibc was not configured for large files. Then I run "make menuconfig" and configure the uClibc for large files. Also configure the following things:

Quoted 1 line

- Host utilities: host sam-ba was checked. I check also and host

u-boot tools.

Quoted 1 line

- Root file system: check ouput format for jffs2 format and

checked the option for Generetate file system summary.

Quoted 1 line

- Bootloader: uncheck the Bootstrap option and check only the

U-boot option.

I don't know this board but are you sure you don't need this bootstrap? Since you're having trouble booting, I'd double check this...

Quoted 1 line

- Configure the Kernel to use the same version as the toolchain -

3.x

Quoted 2 lines

3. Finally I build with make and the result was generated uImage,

rootfs.jffs2 and u-boot.bin. As expected. Then program first the u-boot file on the target but still no life on the RS232 console. Nothing print.

Has this board worked before? What was it running then?

Quoted 3 lines

Can you, please, help me again?
Have a nica day!

Best regards,
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120916/46427326/attachment-0001.html>

#7 lore raw
In reply to a message not in the archive

Martin,
Please, when you reply to an e-mail from a mailing list, hit 'Reply-all' instead of 'Reply'.

Quoted 139 lines · Martin Peevski

On 16/09/12 14:12, Thomas De Schampheleire wrote:

Hi Martin,

Op 16 sep. 2012 12:26 schreef "Martin Peevski" <[email protected]> het volgende:

Quoted 90 lines

-------- Original Message --------
Subject:
Re: [Buildroot] Basic questions about using BuildRoot Date:
Sat, 15 Sep 2012 20:26:18 +0200
From:
Thomas De Schampheleire <[email protected]> To:
Martin Peevski <[email protected]>, buildroot <[email protected]>

Hi Martin,

Please keep the list in copy, and please don't top-post...

Op 15 sep. 2012 20:17 schreef "Martin Peevski" <[email protected]> het volgende:

Quoted 8 lines

Thank you very much for the fast response!

When i wrote the first letter the building was in progress. When it
finish only the u-boot.bin was in the output/images/ directory. Neither a Kernel nor a File system was build. It was included in the menuconfig but was not build. Also i program the u-boot.bin in the target and it not work. Can you please help me again to resolve that problem?

If the kernel is not built and there were no errors during the build process, it must mean that your config is not ok.
Can you re-verify the .config file for e.g. the kernel settings?

Note that I don't have specific experience with this board nor with uboot, so I can't answer that question.
In general, I'd wonder whether you programmed the bootloader correctly, what the errors were you encountered, if any, ...
Did you follow the procedure regarding configuration I outlined in my first response? First defconfig, then make. Can you try with a clean defconfig without any modifications?

Best regards, Thomas

Quoted 34 lines · Thomas De Schampheleire
Quoted 28 lines

Op 15 sep. 2012 19:29 schreef "Martin Peevski" <[email protected]> het volgende:

Quoted 9 lines

Hello, I'm new embedded Linux user and need a little help to
build embedded Linux system with BuildRoot tool for AT91SAM9263 target. May questions are described below:

1. After system configuration is done with make menuconfig
command, shall I execute only make command to build the entire embedded system? Or there is need to execute make at91sam9263ek_defconfig command prior or after the pure make command?

If there is a defconfig for your board, you would start with 'make xxx_defconfig' and then possibly 'make menuconfig' to tune the configuration. The defconfig serves as a start that should work out of the box.

Quoted 4 lines

2. If I not make additional configuration with
busybox-menuconfig or the corresponding command for configuration the Linux Kernel, shall the build system work on the target?

If you started from a defconfig that corresponds to your board, then yes it's supposed to work just like that.

Quoted 1 line
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

I will be thankful to any help!
With best regards, Martin Peevski.

Best regards,
Thomas

Quoted 2 lines

Hi Tomas,
ok, I stop to top-post :)

That's already good, now try to keep the list in copy as well, there may be people with more experience with your board...

Quoted 5 lines

It's a new day in Bulgaria and I try again to build running embedded Linux with at91sam9263 again. In brief I do the following:

1. Run "make clean", "make distclean" to clean everything;

Quoted 10 lines

2. Following your advice in the last letter, I try only with "make
at91sam9263_defconfig" but the build stop because uClibc was not configured for large files. Then I run "make menuconfig" and configure the uClibc for large files. Also configure the following things:
- Host utilities: host sam-ba was checked. I check also and host
u-boot tools.
- Root file system: check ouput format for jffs2 format and
checked the option for Generetate file system summary.
- Bootloader: uncheck the Bootstrap option and check only the
U-boot option.

I don't know this board but are you sure you don't need this bootstrap? Since you're having trouble booting, I'd double check this...

Quoted 6 lines

- Configure the Kernel to use the same version as the toolchain -
3.x

3. Finally I build with make and the result was generated uImage,
rootfs.jffs2 and u-boot.bin. As expected. Then program first the u-boot file on the target but still no life on the RS232 console. Nothing print.

Has this board worked before? What was it running then?

Quoted 3 lines

Can you, please, help me again?
Have a nica day!

Best regards,
Thomas

Quoted 8 lines

Hi, TOmas

The board is Ronetix bb9263 with modul? pm9263. It works fine with other already builded images for u-boot, Kernel, Root FS and without Bootstrap. Now I need custom Root FS, that's the reason to use Buildroot. I plan to build Linux for at91sam9g45 because it's currently not supported by the Build root or I'm not right? And now I'm trening with the 9263 but even it wont not work.

How were these u-boot images built. Do they have custom source? Which configuration was used?
Have you tried using the exact same configuration?

If you're only interested in the rootfs, you could use the original, working u-boot and use the rootfs from buildroot. Have you tried that?

Quoted 4 lines

One question beyond the theme: is it possible to build only Root FS compatible with some external Kernel without any tool and if so how to do that?

It is of course possible to build every package yourself, and create an image from that, but you'd have to know how to do it. That's precisely the reason why you'd use buildroot: to not need to know all the details and benefit from the knowledge and work of others.

Best regards,
Thomas

#8 lore raw
Quoted 7 lines · Thomas De Schampheleire

If you're only interested in the rootfs, you could use the original, working u-boot and use the rootfs from buildroot. Have you tried that?

Quoted 4 lines
Quoted 4 lines

One question beyond the theme: is it possible to build only Root FS compatible with some external Kernel without any tool and if so how to do that?

Indeed, it is entirely possible to use buildroot to build a rootfs and
combine it with a pre-built kernel. There is usually no dependency of an executable on a specific kernel version, because the kernel ABI is backward-compatible. When you build an internal or crosstool-NG toolchain in buildroot, however, do make sure that you use kernel headers with a sufficiently low version (smaller than or equal to the pre-built kernel you use).

If you do want to build a custom kernel later on, you need two
things: the source and the config. Whoever gave you the kernel binary is also obliged to give you the source (GPL), so that should be doable. The config you can usually get from the running kernel, in /proc/config.gz.

Good luck!

Regards,
Arnout

Signature · 6 lines
Arnout Vandecappelle             arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . +32-16-286540 . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
#9 lore raw
Quoted 25 lines · Arnout Vandecappelle
Quoted 8 lines · Thomas De Schampheleire

If you're only interested in the rootfs, you could use the original, working u-boot and use the rootfs from buildroot. Have you tried that?

Quoted 5 lines
Quoted 3 lines

One question beyond the theme: is it possible to build only Root FS compatible with some external Kernel without any tool and if so

how to do

Quoted 1 line

that?

Indeed, it is entirely possible to use buildroot to build a rootfs and
combine it with a pre-built kernel. There is usually no dependency of an executable on a specific kernel version, because the kernel ABI is backward-compatible. When you build an internal or crosstool-NG toolchain in buildroot, however, do make sure that you use kernel headers with a sufficiently low version (smaller than or equal to the pre-built kernel you use).

If you do want to build a custom kernel later on, you need two
things: the source and the config. Whoever gave you the kernel binary is also obliged to give you the source (GPL), so that should be doable. The config you can usually get from the running kernel, in /proc/config.gz.

Quoted 5 lines

Good luck!

Regards,
Arnout

Hi again! Thank you for the help. All my attempts to build Linux
with external version of U-boot and Kernel and the rootfs from buildroot was unsuccessfull. However I get older directory tree and programs and make rootfs with the Linux command mkfs.jffs2. To that moment it works, thank for you time and help!

#10 lore raw
Quoted 33 lines · Martin Peevski
Quoted 25 lines · Arnout Vandecappelle
Quoted 8 lines · Thomas De Schampheleire

If you're only interested in the rootfs, you could use the original, working u-boot and use the rootfs from buildroot. Have you tried that?

Quoted 5 lines
Quoted 3 lines

One question beyond the theme: is it possible to build only Root FS compatible with some external Kernel without any tool and if so

how to do

Quoted 1 line

that?

Indeed, it is entirely possible to use buildroot to build a rootfs and
combine it with a pre-built kernel. There is usually no dependency of an executable on a specific kernel version, because the kernel ABI is backward-compatible. When you build an internal or crosstool-NG toolchain in buildroot, however, do make sure that you use kernel headers with a sufficiently low version (smaller than or equal to the pre-built kernel you use).

If you do want to build a custom kernel later on, you need two
things: the source and the config. Whoever gave you the kernel binary is also obliged to give you the source (GPL), so that should be doable. The config you can usually get from the running kernel, in /proc/config.gz.

Quoted 5 lines

Good luck!

Regards,
Arnout

Quoted 8 lines

Hi again! Thank you for the help. All my attempts to build Linux
with external version of U-boot and Kernel and the rootfs from buildroot was unsuccessfull. However I get older directory tree and programs and make rootfs with the Linux command mkfs.jffs2. To that moment it works, thank for you time and help!
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Hi, I'm back to Buildroot. I new working Linux on board which
isn't supported to that moment in Buildroot, I think - AT91SAM9G45 on Ronetix board. Is it possible to build for it? Moreover I will use external Kernel which support 9g45 - Kernel version 2.6.30. That version isn't supported from the Kernel headers, I think? Can you help me build the Linux again?

Thanks, Martin.

#11 lore raw

Dear Martin Peevski,

Quoted 3 lines · Martin Peevski

Hi, I'm back to Buildroot. I new working Linux on board which
isn't supported to that moment in Buildroot, I think - AT91SAM9G45 on Ronetix board. Is it possible to build for it?

Yes, of course.

Quoted 2 lines

Moreover I will use
external Kernel which support 9g45 - Kernel version 2.6.30.

I'd rather recommend using the latest mainline version. AT91 support in mainline is really good.

Quoted 2 lines

That version isn't supported from the Kernel headers, I think? Can you help me build the Linux again?

Don't worry too much about the kernel headers version, it doesn't have to match exactly the kernel you're running. It should just be *older* than the kernel version you're running on the board.

Best regards,

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
#12 lore raw
Quoted 3 lines · Thomas Petazzoni

Don't worry too much about the kernel headers version, it doesn't have to match exactly the kernel you're running. It should just be*older* than the kernel version you're running on the board.

But the oldest version we provide is 2.6.37 - and even that one is
marked as deprecated.

We really should refactor kernel-headers so it refers to the main kernel
source, if that is configured.

Regards,
Arnout

Signature · 6 lines
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
#13 lore raw
In reply to Thomas Petazzoni
Quoted 7 lines · Thomas Petazzoni

Dear Martin Peevski,

Quoted 3 lines · Martin Peevski

Hi, I'm back to Buildroot. I new working Linux on board which
isn't supported to that moment in Buildroot, I think - AT91SAM9G45 on Ronetix board. Is it possible to build for it?

Quoted 6 lines

Yes, of course.

Quoted 2 lines

Moreover I will use
external Kernel which support 9g45 - Kernel version 2.6.30.

I'd rather recommend using the latest mainline version. AT91 support in mainline is really good.

I think that it's mandatory to use exactly 2.6.30 version because the Ronetix board isn't included in the main line of any later Kernel.

Quoted 10 lines
Quoted 3 lines

That version isn't supported from the Kernel headers, I think? Can you help me build the Linux again?

Don't worry too much about the kernel headers version, it doesn't have to match exactly the kernel you're running. It should just be *older* than the kernel version you're running on the board. Also then

Best regards,

Thomas

I'll try with external toolchain which is used to build the already build externel used Kernel.

#14 lore raw

Dear Martin Peevski,

Quoted 5 lines · Martin Peevski
Quoted 2 lines

I'd rather recommend using the latest mainline version. AT91 support in mainline is really good.

I think that it's mandatory to use exactly 2.6.30 version because the Ronetix board isn't included in the main line of any later Kernel.

Ok. That said, porting a recent kernel on a AT91SAM9G45 board is probably a matter of a few hours for someone knowledgeable with ARM kernel development, unless the board has some funky peripherals that are not supported in mainline.

Best regards,

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
#15 lore raw
Quoted 8 lines · Thomas Petazzoni

Dear Martin Peevski,

Quoted 4 lines · Martin Peevski
Quoted 2 lines

I'd rather recommend using the latest mainline version. AT91 support in mainline is really good.

I think that it's mandatory to use exactly 2.6.30 version because the Ronetix board isn't included in the main line of any later Kernel.

Quoted 8 lines

Ok. That said, porting a recent kernel on a AT91SAM9G45 board is probably a matter of a few hours for someone knowledgeable with ARM kernel development, unless the board has some funky peripherals that are not supported in mainline.

Best regards,

Thomas

Hi again! I build only rootfs with Buildroot using the toolchain for building the Kernel in early stage. But the Ethernet have some problems. Find the PHY correctly but can't make ping.

So my suggestion to fix the problem is to build the Kernel and the rootfs together in Buildroot. Shall this thing correct the problem?

Also want to ask because I was impossible to configure the Buildroot using Kernel sources from my computer. Is it possible and how? If it's impossible I can deliver the sources via internet but they are not in Git repository, is that problem?

Thanks in advance!
Martin

#16 lore raw
Quoted 31 lines · Martin Peevski
Quoted 8 lines · Thomas Petazzoni

Dear Martin Peevski,

Quoted 4 lines · Martin Peevski
Quoted 2 lines

I'd rather recommend using the latest mainline version. AT91 support in mainline is really good.

I think that it's mandatory to use exactly 2.6.30 version because the Ronetix board isn't included in the main line of any later Kernel.

Quoted 8 lines

Ok. That said, porting a recent kernel on a AT91SAM9G45 board is probably a matter of a few hours for someone knowledgeable with ARM kernel development, unless the board has some funky peripherals that are not supported in mainline.

Best regards,

Thomas

Hi again! I build only rootfs with Buildroot using the toolchain for building the Kernel in early stage. But the Ethernet have some problems. Find the PHY correctly but can't make ping.

So my suggestion to fix the problem is to build the Kernel and the rootfs together in Buildroot. Shall this thing correct the problem?

Also want to ask because I was impossible to configure the Buildroot using Kernel sources from my computer. Is it possible and how? If it's impossible I can deliver the sources via internet but they are not in Git repository, is that problem?

Quoted 6 lines

Thanks in advance!
Martin
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Hi again! Before response to my previous letter I want to tell you that build together the kernel and the rootfs and my ethernet is still not working. Can you help me resolve the problem, please? Is the ethernet dependent on my Buildroot configuration or may be something another?

Thanks, Martin.

#17 lore raw

Am 29.09.2012 15:17, schrieb Martin Peevski:

Quoted 6 lines · Martin Peevski
Quoted 5 lines

Also want to ask because I was impossible to configure the Buildroot using Kernel sources from my computer. Is it possible and how? If it's impossible I can deliver the sources via internet but they are not in Git repository, is that problem?

Hi Martin,

you can use a local linux source tree with the source directory override mechanism described here: http://free-electrons.com/blog/buildroot-2011-11/

Quoted 10 lines
Quoted 7 lines

Thanks in advance!
Martin
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Quoted 5 lines

Hi again! Before response to my previous letter I want to tell you that build together the kernel and the rootfs and my ethernet is still not working. Can you help me resolve the problem, please? Is the ethernet dependent on my Buildroot configuration or may be something another?

Do you have any further diagnostics like kernel messages or such? Do you have a working kernel for your board? If yes, did you double-check kernel configuration against the known good one? If no, are you sure your hardware is working correctly? Can you set an IP address without error messages?

Regards

Stephan

Quoted 6 lines

Thanks, Martin.
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Signature · 4 lines
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de
#18 lore raw
Quoted 29 lines · Stephan Hoffmann

Am 29.09.2012 15:17, schrieb Martin Peevski:

Quoted 5 lines · Martin Peevski
Quoted 4 lines

Also want to ask because I was impossible to configure the Buildroot using Kernel sources from my computer. Is it possible and how? If it's impossible I can deliver the sources via internet but they are not in Git repository, is that problem?

Hi Martin,

you can use a local linux source tree with the source directory override mechanism described here: http://free-electrons.com/blog/buildroot-2011-11/

Quoted 8 lines
Quoted 6 lines

Thanks in advance!
Martin
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Quoted 5 lines

Hi again! Before response to my previous letter I want to tell you that build together the kernel and the rootfs and my ethernet is still not working. Can you help me resolve the problem, please? Is the ethernet dependent on my Buildroot configuration or may be something another?

Do you have any further diagnostics like kernel messages or such? Do you have a working kernel for your board? If yes, did you double-check kernel configuration against the known good one? If no, are you sure your hardware is working correctly? Can you set an IP address without error messages?

Quoted 9 lines

Regards

Stephan

Quoted 5 lines

Thanks, Martin.
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

I'm not build the Kernel with diagnostic information but I have working Kernel and may be rootfs because I have command prompt with buildroot. Can execute ifconfig command but the response don't show my IP, shows only this:

# ifconfig
lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

I think I'm sure that the Kernel is working because with another rootfs my Ethernet is working - can read the IP with ifconfig. But I must use the rootfs from Buildroot because the small size of it.

#19 lore raw

Am 29.09.2012 16:09, schrieb Martin Peevski:

Quoted 53 lines · Stephan Hoffmann
Quoted 30 lines

Am 29.09.2012 15:17, schrieb Martin Peevski:

Quoted 5 lines · Martin Peevski
Quoted 4 lines

Also want to ask because I was impossible to configure the Buildroot using Kernel sources from my computer. Is it possible and how? If it's impossible I can deliver the sources via internet but they are not in Git repository, is that problem?

Hi Martin,

you can use a local linux source tree with the source directory override mechanism described here:
http://free-electrons.com/blog/buildroot-2011-11/

Quoted 8 lines
Quoted 6 lines

Thanks in advance!
Martin
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Quoted 5 lines

Hi again! Before response to my previous letter I want to tell you that build together the kernel and the rootfs and my ethernet is still not working. Can you help me resolve the problem, please? Is the ethernet dependent on my Buildroot configuration or may be something another?

Do you have any further diagnostics like kernel messages or such? Do you have a working kernel for your board? If yes, did you double-check kernel configuration against the known good one? If no, are you sure your hardware is working correctly? Can you set an IP address without error messages?

Quoted 9 lines

Regards

Stephan

Quoted 5 lines

Thanks, Martin.
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

I'm not build the Kernel with diagnostic information but I have working Kernel and may be rootfs because I have command prompt with buildroot. Can execute ifconfig command but the response don't show my IP, shows only this:

# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
Quoted 3 lines

I think I'm sure that the Kernel is working because with another rootfs my Ethernet is working - can read the IP with ifconfig. But I must use the rootfs from Buildroot because the small size of it.

Please try

# ifconfig -a
then eth0 should show up.
If not something with your kernel, drivers or hardware is wrong.
If yes try
# ifconfig eth0 <IP-Adress> up
Probably, you do not have the correct entry in /etc/network/interfaces
Signature · 4 lines
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de
#20 lore raw
Quoted 55 lines · Stephan Hoffmann

Am 29.09.2012 16:09, schrieb Martin Peevski:

Quoted 51 lines · Stephan Hoffmann
Quoted 29 lines

Am 29.09.2012 15:17, schrieb Martin Peevski:

Quoted 5 lines · Martin Peevski
Quoted 4 lines

Also want to ask because I was impossible to configure the Buildroot using Kernel sources from my computer. Is it possible and how? If it's impossible I can deliver the sources via internet but they are not in Git repository, is that problem?

Hi Martin,

you can use a local linux source tree with the source directory override mechanism described here:
http://free-electrons.com/blog/buildroot-2011-11/

Quoted 7 lines
Quoted 6 lines

Thanks in advance!
Martin
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Quoted 5 lines

Hi again! Before response to my previous letter I want to tell you that build together the kernel and the rootfs and my ethernet is still not working. Can you help me resolve the problem, please? Is the ethernet dependent on my Buildroot configuration or may be something another?

Do you have any further diagnostics like kernel messages or such? Do you have a working kernel for your board? If yes, did you double-check kernel configuration against the known good one? If no, are you sure your hardware is working correctly? Can you set an IP address without error messages?

Quoted 8 lines

Regards

Stephan

Quoted 5 lines

Thanks, Martin.
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

I'm not build the Kernel with diagnostic information but I have working Kernel and may be rootfs because I have command prompt with buildroot. Can execute ifconfig command but the response don't show my IP, shows only this:

# ifconfig
lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
Quoted 3 lines

I think I'm sure that the Kernel is working because with another rootfs my Ethernet is working - can read the IP with ifconfig. But I must use the rootfs from Buildroot because the small size of it.

Quoted 9 lines

Please try

# ifconfig -a
then eth0 should show up.
If not something with your kernel, drivers or hardware is wrong.
If yes try
# ifconfig eth0 <IP-Adress> up
Probably, you do not have the correct entry in /etc/network/interfaces

You are great! Now my Ethernet is working! It only need to be set with ifconfig eth0 <xx.xx.xx.xx> up end begin works!

Thank a lot for the help;

Now I need dhcp support to my board be possible get its IP from our tftp server. I can't found dhclient command on the target board. Also search for appropriate network package to be installed via make menuconfig but was impossible to find such a packet. Can you help me again?

#21 lore raw

Am 01.10.2012 10:14, schrieb Martin Peevski:

Quoted 10 lines · Stephan Hoffmann
Quoted 6 lines

Am 29.09.2012 16:09, schrieb Martin Peevski:

# ifconfig eth0 <IP-Adress> up
Probably, you do not have the correct entry in /etc/network/interfaces

You are great! Now my Ethernet is working! It only need to be set with ifconfig eth0 <xx.xx.xx.xx> up end begin works!

Quoted 7 lines

Thank a lot for the help;

Now I need dhcp support to my board be possible get its IP from our tftp server. I can't found dhclient command on the target board. Also search for appropriate network package to be installed via make menuconfig but was impossible to find such a packet. Can you help me again?

Try udhcpc, that should be available from busybox. if not: make busybox-menuconfig

You should add

Quoted 2 lines

auto eth0
iface eth0 inet dhcp

to your /etc/network/interfaces file.

Hope it helps

Stephan

Signature · 4 lines
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de
#22 lore raw
In reply to Martin Peevski

2012/10/1 Martin Peevski <[email protected]>:
[...]

Quoted 4 lines

Now I need dhcp support to my board be possible get its IP from our tftp server. I can't found dhclient command on the target board. Also search for appropriate network package to be installed via make menuconfig but was impossible to find such a packet. Can you help me again?

To enable a dhcp client, you can:
- either look at the busybox-menuconfig and make sure 'udhcp client' is selected:
make busybox-menuconfig
After that, rebuild busybox.
- or, in buildroot menuconfig: allow to 'Show packages that are also provided by busybox', then select 'isc dhcp' and finally run 'make'.

It's up to you, depends on what you want ;)

Anyway, for further details, don't hesitate to look at:
http://buildroot.org/downloads/manual/manual.html

and give us your feedback.

Regards.

Signature · 1 line
Sam
#23 lore raw
Quoted 16 lines · Samuel Martin

2012/10/1 Martin Peevski <[email protected]>:
[...]

Quoted 4 lines

Now I need dhcp support to my board be possible get its IP from our tftp server. I can't found dhclient command on the target board. Also search for appropriate network package to be installed via make menuconfig but was impossible to find such a packet. Can you help me again?

To enable a dhcp client, you can:
- either look at the busybox-menuconfig and make sure 'udhcp client' is selected:
make busybox-menuconfig
After that, rebuild busybox.
- or, in buildroot menuconfig: allow to 'Show packages that are also provided by busybox', then select 'isc dhcp' and finally run 'make'.

It's up to you, depends on what you want ;)

Quoted 8 lines

Anyway, for further details, don't hesitate to look at:
http://buildroot.org/downloads/manual/manual.html

and give us your feedback.

Regards.

Yes, I found that in menuconfig! Before search in the manual but there can't find anything about dhcp.

Thank you!

#24 lore raw

2012/10/1 Martin Peevski <[email protected]>:
[...]

Quoted 2 lines

Yes, I found that in menuconfig! Before search in the manual but there can't find anything about dhcp.

Hint:
You can use 'make xconfig' instead of 'make menuconfig'. This way, you will get a (nice) gui, with some search function, and the ability to display all options, even those hidden by some others. ;)

Signature · 1 line
Sam
#25 lore raw
Quoted 11 lines · Samuel Martin

2012/10/1 Martin Peevski <[email protected]>:
[...]

Quoted 2 lines

Yes, I found that in menuconfig! Before search in the manual but there can't find anything about dhcp.

Hint:
You can use 'make xconfig' instead of 'make menuconfig'. This way, you will get a (nice) gui, with some search function, and the ability to display all options, even those hidden by some others. ;)

Yes, its was explained in the manual, I think. I try it earlier but seems like that it want some package to be install and want not to work. That's also explained in the manual :) But I'm new Linux user and prefer not to dive in the deep water. Tha't the reason to use only menuconfig.

Thanks again! I have some more questions but first will try to solve them alone :)

#26 lore raw
Quoted 19 lines · Martin Peevski
Quoted 12 lines · Samuel Martin

2012/10/1 Martin Peevski <[email protected]>:
[...]

Quoted 3 lines

Yes, I found that in menuconfig! Before search in the manual but there can't
find anything about dhcp.

Hint:
You can use 'make xconfig' instead of 'make menuconfig'. This way, you will get a (nice) gui, with some search function, and the ability to display all options, even those hidden by some others. ;)

Yes, its was explained in the manual, I think. I try it earlier but seems like that it want some package to be install and want not to work. That's also explained in the manual :) But I'm new Linux user and prefer not to dive in the deep water. Tha't the reason to use only menuconfig.

Quoted 6 lines

Thanks again! I have some more questions but first will try to solve them alone :)
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

I add a dhclient to buildroot system but have a problem with assigning dynamic IP address to my target. When execute dhclient nothing is done but when I execute udhcpc I get an IP. Where is my mistake?

#27 lore raw
In reply to Martin Peevski
Quoted 19 lines · Martin Peevski
Quoted 12 lines · Samuel Martin

2012/10/1 Martin Peevski <[email protected]>:
[...]

Quoted 3 lines

Yes, I found that in menuconfig! Before search in the manual but there can't
find anything about dhcp.

Hint:
You can use 'make xconfig' instead of 'make menuconfig'. This way, you will get a (nice) gui, with some search function, and the ability to display all options, even those hidden by some others. ;)

Yes, its was explained in the manual, I think. I try it earlier but seems like that it want some package to be install and want not to work. That's also explained in the manual :) But I'm new Linux user and prefer not to dive in the deep water. Tha't the reason to use only menuconfig.

Quoted 6 lines

Thanks again! I have some more questions but first will try to solve them alone :)
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Hello, could you help me to display a picture with the LCD. With another rootfs i do it with the following command:

cp lcd_image /dev/fb0

Now with Buildroot that don't work for me. I try with make menuconfig and install some packages for display, as fbv (frame buffer viewer) and also anothers but with no effect. Still don't display the picture. Any ideas?