From: sproon <sproon@hotmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] E-Ink AM300 development Board
Date: Tue, 23 Feb 2010 02:03:10 -0800 (PST) [thread overview]
Message-ID: <27700904.post@talk.nabble.com> (raw)
Hello,
I am new to buildroot and I have been trying to figure out exactly how to
utilize the program properly for a while now. I am currently stuck on trying
to get the buildroot environment to make the linux kernel and drivers for
the am300 development board. Support for the board has been available for
some time and I am able to select the architecture, processor and
developement board on both the buildroot menuconfig and the
linux26-menuconfig.
When I try to run make it gives me the following error:
ging/include --sysroot=/home/sproon/buildroot/output/staging/ -isysroot
/home/sproon/buildroot/output/staging -mtune=xscale -march=armv5te
-mabi=aapcs-linux -msoft-float" \
LDFLAGS="-L/home/sproon/buildroot/output/staging/lib
-L/home/sproon/buildroot/output/staging/usr/lib
--sysroot=/home/sproon/buildroot/output/staging/" \
\
/usr/bin/make -j1 -C /home/sproon/buildroot/output/build/u-boot-2009.11 \
am300_board_config
make[1]: Entering directory
`/home/sproon/buildroot/output/build/u-boot-2009.11'
make[1]: *** No rule to make target `am300_board_config'. Stop.
make[1]: Leaving directory
`/home/sproon/buildroot/output/build/u-boot-2009.11'
make: *** [/home/sproon/buildroot/output/build/u-boot-2009.11/.configured]
Error 2
It seems that this stems from the BR2_TARGET_UBOOT_BOARDNAME option from the
das uboot option under kernel selection of the main menuconfig. At first I
thought that it just needed any name at all so I called it am300_board but
appartently this is not the case.
So my question is, what should I put as my board name, and how do I look
such a thing up in the future development process?
Thanks for any help,
Sproon
--
View this message in context: http://old.nabble.com/E-Ink-AM300-development-Board-tp27700904p27700904.html
Sent from the BuildRoot mailing list archive at Nabble.com.
reply other threads:[~2010-02-23 10:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=27700904.post@talk.nabble.com \
--to=sproon@hotmail.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