From: Hubert Feurstein <h.feurstein@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: bootm: booting of uncompressed uimages broken
Date: Wed, 24 Feb 2016 11:12:44 +0100 [thread overview]
Message-ID: <CAFfN3gV8iJTNJxkm41QcRPoame_NPqxnCh4P5Z9DApoLyHFLdA@mail.gmail.com> (raw)
In-Reply-To: <20160223120404.GG3939@pengutronix.de>
Hi Sascha,
> Hm, yes, you said so in your mail, I misread it. Then I don't see what
> could be the problem. Does bootm -v give some valuable output?
here is the output of bootm -v <image> (fixed version):
barebox:/ bootm -v /mnt/emmc0/boot/uImage
Image Name: Linux-3.10.14.vd2
Created: 2015-08-06 10:13:02 UTC
OS: Linux
Architecture: ARM
Type: Kernel Image
Compression: uncompressed
Data Size: 2929528 Bytes = 2.8 MiB
Load Address: 10008000
Entry Point: 10008000
Loading U-Boot uImage '/mnt/emmc0/boot/uImage'
OS image not yet relocated
Passing control to ARM Linux uImage handler
no initrd load address, defaulting to 0x18000000
commandline: console=ttymxc2,115200n8
Starting kernel at 0x10008000, oftree at 0x18000000...
> Could it be that the device tree blob is inside the Kernels bss segment?
According to System.map bss ends at offset 0x0567b04. So bss will
overwrite the device-tree blob, because currently the oftree is placed
at 0x103d4000. I've played with the oftree-offset a little bit, and I
need at least 6MB offset from the end of the kernel image in order to
get the system booting.
Hubert
2016-02-23 13:04 GMT+01:00 Sascha Hauer <s.hauer@pengutronix.de>:
> On Tue, Feb 23, 2016 at 12:29:41PM +0100, Hubert Feurstein wrote:
>> Hi Sascha,
>>
>> I use an *uncompressed* kernel image. So the kernel is loaded once
>> without any relocation (LoadAddress == StartAddress).
>
> Hm, yes, you said so in your mail, I misread it. Then I don't see what
> could be the problem. Does bootm -v give some valuable output?
> Could it be that the device tree blob is inside the Kernels bss segment?
>
> Sascha
>
>
> --
> 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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2016-02-24 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 9:52 Hubert Feurstein
2016-02-23 11:09 ` Sascha Hauer
[not found] ` <CAFfN3gVK2BHq4wC9gTxN-pJ=-j6FHiikfuV+FdGfVwiOKG2a_Q@mail.gmail.com>
[not found] ` <20160223120404.GG3939@pengutronix.de>
2016-02-24 10:12 ` Hubert Feurstein [this message]
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=CAFfN3gV8iJTNJxkm41QcRPoame_NPqxnCh4P5Z9DApoLyHFLdA@mail.gmail.com \
--to=h.feurstein@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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