From: Cameron Hutchison <lists@xdna.net>
To: buildroot@busybox.net
Subject: [Buildroot] Confusion with building at91bootstrap
Date: Wed, 03 Feb 2010 03:36:19 -0000 [thread overview]
Message-ID: <411b.4b68ef33.cfddb@getafix.xdna.net> (raw)
I am trying to build an image for an AT91SAM9260EK board and I'm getting
a little confused with the build ot at91bootstrap. I'm using BR 2009.11
When at91bootstrap is configured, the buildroot makefile
(at91bootstrap.mk) runs "make at91sam9260ek_defconfig" which sets up
at91bootstrap for building for my specific board.
That config file defines IMG_SIZE to be 0x40000 and passes
-DIMG_SIZE=0x40000 to the compiler.
The buildroot makefile passes -DIMG_SIZE=0x32000. This value comes from
the buildroot config.
This causes a build warning that IMG_SIZE is redefined.
Apart from that I don't yet know what the correct image size should be,
it looks like the at91bootstrap integration into buildroot is broken.
The option to set the image size in the BR config cannot work, since the
at91bootstrap (2.10) source will attempt to override it anyway. Am I
missing something here?
Also, the at91bootstrap defconfig for this board adds the suffix of
"card" to the output file, making that filename contain "dataflashcard"
when I have configured for "dataflash" not "dataflashcard". I dont yet
know what the difference is between these (my board does not appear to
have any sort of card or slot for one), so I'm not sure what should be
done here, but it appears inconsistent.
Finally, is this the best place to discuss at91bootstrap and other
issues related to this board and buildroot, or is there a better forum?
Thanks
next reply other threads:[~2010-02-03 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 3:36 Cameron Hutchison [this message]
2010-02-03 13:29 ` [Buildroot] Confusion with building at91bootstrap Ulf Samuelsson
2010-02-03 23:48 ` Cameron Hutchison
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=411b.4b68ef33.cfddb@getafix.xdna.net \
--to=lists@xdna.net \
--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