[PATCH 2/2] tx51: Disable kallsyms. It prevents the board from booting.
s.hauer at pengutronix.de
Mon Jul 16 11:16:48 EDT 2012
On Mon, Jul 16, 2012 at 04:41:45PM +0200, Christian Kapeller wrote:
> On 07/16/2012 04:31 PM, Sascha Hauer wrote:
> > On Mon, Jul 16, 2012 at 11:53:59AM +0200, Christian Kapeller wrote:
> >> diff --git a/arch/arm/configs/tx51stk5_defconfig b/arch/arm/configs/tx51stk5_defconfig
> >> index 7fff0f0..e1796b9 100644
> >> --- a/arch/arm/configs/tx51stk5_defconfig
> >> +++ b/arch/arm/configs/tx51stk5_defconfig
> >> @@ -32,7 +32,6 @@ CONFIG_HAVE_CONFIGURABLE_TEXT_BASE=y
> >> CONFIG_HAVE_CONFIGURABLE_MEMORY_LAYOUT=y
> >> CONFIG_MEMORY_LAYOUT_DEFAULT=y
> >> CONFIG_MALLOC_TLSF=y
> >> -CONFIG_KALLSYMS=y
> > Of course I rather would like to fix the underlying issue. Does this
> > happen on a second stage barebox aswell?
> I hear you. My intend was to have at least a booting board, rather than
> a brick.
> I just flashed tx51 barebox without CONFIG_KALLSYMS, and could
> successfully start a barebox binary with CONFIG_KALLSYMS set using
A binary built with CONFIG_KALLSYMS is >256k and without CONFIG_KALLSYMS
it's smaller than 256k. Looking at the karo i.MX51 flash_header.c it
seems it does it right:
unsigned long __image_len_section barebox_len = DCD_BAREBOX_SIZE;
Nevertheless 256k is a typical maximum bootloader size which is assumed
in some places, I would start looking there.
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox