From: mike sander <msander@cogeco.ca>
To: buildroot@busybox.net
Subject: [Buildroot] u-boot fails with custom board support
Date: Wed, 08 Apr 2009 10:08:14 -0400 [thread overview]
Message-ID: <49DCAFCE.4030001@cogeco.ca> (raw)
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
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
next reply other threads:[~2009-04-08 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 14:08 mike sander [this message]
2009-04-08 15:09 ` [Buildroot] u-boot fails with custom board support Thiago A. Corrêa
2009-04-08 17:52 ` Mike Sander
2009-04-08 15:56 ` Ulf Samuelsson
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=49DCAFCE.4030001@cogeco.ca \
--to=msander@cogeco.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.