From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Wed, 29 Oct 2014 10:36:30 -0600
Subject: [U-Boot] Flat Image Tree and boot arguments
In-Reply-To: <910058E0AFC89142822B093FD70D46220C65A79D@S0MSMAIL112.arc.local>
References: <910058E0AFC89142822B093FD70D46220C65A79D@S0MSMAIL112.arc.local>
Message-ID: <5451178E.4020905@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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.