From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Booting armv8 kernel on uboot
Date: Wed, 21 May 2014 11:28:53 -0400 [thread overview]
Message-ID: <20140521152853.GC1752@bill-the-cat> (raw)
In-Reply-To: <20140521094038.GC17827@leverpostej>
On Wed, May 21, 2014 at 10:40:38AM +0100, Mark Rutland wrote:
> On Wed, May 21, 2014 at 09:46:35AM +0100, Vishal Bhoj wrote:
> > Hi ,
>
> Hi,
>
> > I have added mmc driver into the vexpress64 board file for uboot and tested
> > it on FVP base model. I tried booting a kernel on that but it is aborting
> > with the following message:
> > Final value for argc=3
> > Loading Kernel Image ... OK
> > kernel loaded at 0x00080000, end = 0x00827024
> > using: FDT
> > reserving fdt memory region: addr=80000000 size=10000
> > ## initrd_high = 0xffffffffffffffff, copy_to_ram = 1
> > ramdisk load start = 0x00000000, ramdisk load end = 0x00000000
> > ## device tree at 0000000090008000 ... 000000009000a850 (len=22609 [0x5851])
> > Loading Device Tree to 000000009fffa000, end 000000009ffff850 ... OK
> > Initial value for argc=3
> > Final value for argc=3
> > ## Transferring control to Linux (at address 80000)...
> > Starting kernel ...
> >
> > "Synchronous Abort" handler, esr 0x02000000
>
> That ESR_ELx value means Unknown/uncategorized. It would be fantastic if
> U-Boot would tell us what EL it's branching to the kernel at as a matter
> of course -- it's not really possible to debug from logs otherwise.
>
> Which EL are you loading the kernel at?
So, this I suspect is one of the problems I was trying to describe to
you back at ELC which turned out to be loading things at the very wrong
address (0x80000 rather than 0x80080000).
Vishal, cay you apply:
http://patchwork.ozlabs.org/patch/345746/
http://patchwork.ozlabs.org/patch/345748/
http://patchwork.ozlabs.org/patch/345749/
http://patchwork.ozlabs.org/patch/345747/
I need to do a v2 still to address some feedback, and then also say we
require Mark's recent series to add an image size field (and other
cleanups) and make use of that (and the rest of the series
changes/clarifications).
But it should get you farther along.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140521/ad40c473/attachment.pgp>
next prev parent reply other threads:[~2014-05-21 15:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 8:46 [U-Boot] Booting armv8 kernel on uboot Vishal Bhoj
2014-05-21 9:40 ` Mark Rutland
2014-05-21 15:28 ` Tom Rini [this message]
2014-05-21 15:34 ` Mark Rutland
2014-05-22 5:48 ` Vishal Bhoj
2014-05-22 12:39 ` Tom Rini
2014-05-22 13:07 ` Vishal Bhoj
2014-05-22 14:26 ` fenghua at phytium.com.cn
2014-05-22 16:36 ` Tom Rini
2014-05-22 16:55 ` Vishal Bhoj
2014-05-26 13:45 ` fenghua at phytium.com.cn
2014-05-27 13:56 ` fenghua at phytium.com.cn
2014-05-28 4:44 ` TigerLiu at via-alliance.com
2014-05-29 13:00 ` fenghua at phytium.com.cn
2014-06-04 4:31 ` Vishal Bhoj
2014-06-04 9:35 ` Sudeep Holla
2014-05-23 5:38 ` TigerLiu at via-alliance.com
-- strict thread matches above, loose matches on Subject: below --
2016-07-20 11:28 [U-Boot] Booting armv8 Kernel on UBoot Rajkumar Ramasamy
2016-07-21 4:11 Rajkumar Ramasamy
2016-07-21 5:14 Rajkumar Ramasamy
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=20140521152853.GC1752@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.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