From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Build error: No rule to make target `ubootboard_config'
Date: Mon, 13 Sep 2010 20:30:30 +0200 [thread overview]
Message-ID: <20100913203030.527a8293@surf> (raw)
In-Reply-To: <KAW101-W663381351DE5AA588F11B19B770@phx.gbl>
On Tue, 14 Sep 2010 02:51:42 +0900
S W <sw18@hotmail.co.jp> wrote:
> I am trying to build a Uboot loader for ARM.
"ARM" is a very general core architecture. There are dozens of
companies building processors based on the ARM architecture, producing
hundreds of different processors, used in thousands of different boards.
So "building U-Boot for ARM" is not precise enough, and it's definitely
the thing that you seem to misunderstand.
> If I leave the "U-boot board name" as blank,
> there is an error as "NO U-Boot board name set.
> Check your BR2_TARGET_UBOOT_BOARDNAME setting."
Yes, U-Boot needs to be configured by providing the name of the board
you are targeting. See
> But if I input the U-Boot board name as a name like "ubootboard",
> I encountered another error "No rule to make target
> `ubootboard_config".
Obviously it seems you're misunderstanding a bit what this is all about.
"ubootboard" is not a valid board name. See include/configs/ in U-Boot
sources for the valid board names in U-Boot.
Try "at91sam9263ek" as a board name. U-Boot will compile properly...
but will very likely not work on your hardware, unless it is the
AT91SAM9263-EK board (which is an evaluation kit of the AT91SAM9263
CPU, sold by Atmel).
> How I create the build rule for U-Boot board?
Two choices :
*) U-Boot is already ported to your hardware. In that case, you only
need to find what file in include/configs/ in the U-Boot sources
correspond to the board that you have.
*) U-Boot is not already ported to your hardware. Then it's a lot more
work since you'll have to do the porting by yourself.
I repeat my question: on which hardware do you want to run U-Boot ?
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-09-13 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 22:16 [Buildroot] Build error "cannot find -lc" S W
2010-09-11 8:52 ` Thomas Petazzoni
2010-09-11 18:09 ` S W
2010-09-13 17:37 ` S W
2010-09-13 17:47 ` Thomas Petazzoni
2010-09-13 21:19 ` Peter Korsgaard
2010-09-14 4:09 ` Mitch Davis
2010-09-13 17:51 ` [Buildroot] Build error: No rule to make target `ubootboard_config' S W
2010-09-13 18:30 ` Thomas Petazzoni [this message]
2010-09-13 20:16 ` S W
2010-09-14 17:29 ` Marcus Osdoba
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=20100913203030.527a8293@surf \
--to=thomas.petazzoni@free-electrons.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