Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] u-boot fails with custom board support
Date: Wed, 08 Apr 2009 17:56:21 +0200	[thread overview]
Message-ID: <49DCC925.7060706@atmel.com> (raw)
In-Reply-To: <49DCAFCE.4030001@cogeco.ca>

mike sander skrev:
> Hi All:
>
> I'm using buildroot-2009.02. I have a custom board based on atmel
> at91sam9g20. I have created a top level board config.
>
> I invoke make as follows:
>
> make BOARD=xx
>
The normal way of using buildroot is to do:

$ make at91sam9g20ek_defconfig
$ make

If you do any modifications to any the configs (busybox, linux, .config
etc.)
you can do:

$ make saveconfig

which will copy all your configs to $(LOCAL)/$(PROJECT)
It will also update the .config file so that it will use
your updated config files instead of the default.

You can then retrieve this by making:
$ make BOARD=<PROJECT> getconfig
I.E:
$ make BOARD=at91sam9g20-mike getconfig

which will fetch the new config file into the top directory of buildroot

You then type
$ make
to build the project


BR
Ulf Samuelsson


> u-boot is failing with the following messages (see below). I have
> specified "at91sam9g20ek" in the "board name" section for u-boot (same
> behaviour with default setting). It appears that u-boot does correctly
> do the at91sam9g20ek_config. I cannot see how/why make is looking for
> "Project Name" items under u-boot towards the end of the u-boot build.
> Manually building u-boot with "make at91sam9g20ek_config;make" works
> fine. Stock u-boot is perfectly acceptable.
>
> I've read the br docs. I did not see any indication that u-boot needs
> to be tailored when using custom board support. Any suggestions on how
> to force u-boot to build the stock config? I have tried latest br
> snapshot too. same behavior. I suspect I have missed something obvious.
>
>
>
> /usr/bin/make -C board/atmel/xx/
> make: Entering an unknown directory
> make: *** board/atmel/xx/: No such file or directory. Stop.
> make: Leaving an unknown directory
> make[1]: *** [board/atmel/xx/libxx.a] Error 2
> make[1]: Leaving directory
> `/home/br/buildroot/project_build_arm/xx/u-boot-2009.03'
> make: ***
> [/home/br/buildroot/project_build_arm/xx/u-boot-2009.03/u-boot.bin]
> Error 2
>
>
>
> thanks in advance,
>
> mike sander
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  parent reply	other threads:[~2009-04-08 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 14:08 [Buildroot] u-boot fails with custom board support mike sander
2009-04-08 15:09 ` Thiago A. Corrêa
2009-04-08 17:52   ` Mike Sander
2009-04-08 15:56 ` Ulf Samuelsson [this message]
2009-04-08 17:18   ` Mike Sander
     [not found] ` <49DCCA02.30105@atmel.com>
2009-04-08 16:16   ` Mike Sander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49DCC925.7060706@atmel.com \
    --to=ulf.samuelsson@atmel.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox