From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Flat Image Tree and boot arguments
Date: Wed, 29 Oct 2014 10:36:30 -0600 [thread overview]
Message-ID: <5451178E.4020905@wwwdotorg.org> (raw)
In-Reply-To: <910058E0AFC89142822B093FD70D46220C65A79D@S0MSMAIL112.arc.local>
On 10/29/2014 08:22 AM, Wei? Christoph wrote:
> Dear all,
>
> I am trying to get my own build of U-Boot to boot Linux on a Jetson TK1 board. As we are pushing for verified boot I am using the Flat Image Tree (unifying kernel image, device tree blob, ...) to describe my system. U-Boot can load the ITB file and tries to start the kernel but the system hangs after this message.
>
...
> images {
> kernel at 1 {
...
> load = <0x81008000>;
> entry = <0x81008000>;
That looks plausible, but ...
...
> Tegra124 (Jetson TK1) # bootm 0x90000000
> ## Loading kernel from FIT Image at 90000000 ...
> Using 'conf at 1' configuration
> Verifying Hash Integrity ... OK
> Trying 'kernel at 1' kernel subimage
...
> Load Address: 0x00000000
> Entry Point: 0x00000000
That looks like it's copying the kernel to address 0, which isn't RAM on
this system. You'd need to track down why the wrong address is being used.
BTW, you may want to contact linux-tegra-bugs at nvidia.com for support
with L4T. That said, this aspect of L4T U-Boot should be identical to
upstream U-Boot, since the L4T version is so close to upstream now.
next prev parent reply other threads:[~2014-10-29 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 14:22 [U-Boot] Flat Image Tree and boot arguments Weiß Christoph
2014-10-29 15:14 ` Jagan Teki
2014-10-29 16:36 ` Stephen Warren [this message]
2014-10-31 8:05 ` Weiß Christoph
2014-11-01 15:13 ` Simon Glass
[not found] ` <910058E0AFC89142822B093FD70D46220C65FC3E@S0MSMAIL112.arc.local>
2014-11-13 3:08 ` Simon Glass
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=5451178E.4020905@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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