Hello,
Thanks for your answer.
I recreated the ITB file and it then showed the load address and entry point given in the IST during boot execution. This however did not change anything. Strangely enough a newly compiled kernel image did the trick (although the original image worked in all other boot methods except for use in an image tree blob) .
Anyways, thanks again. Cheers, Chris
-----Ursprüngliche Nachricht----- Von: Stephen Warren [mailto:swarren@wwwdotorg.org] Gesendet: Mittwoch, 29. Oktober 2014 17:36 An: Weiß Christoph; u-boot@lists.denx.de Cc: Tom Warren Betreff: Re: [U-Boot] Flat Image Tree and boot arguments
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@1 {
...
load = <0x81008000>; entry = <0x81008000>;
That looks plausible, but ...
...
Tegra124 (Jetson TK1) # bootm 0x90000000 ## Loading kernel from FIT Image at 90000000 ... Using 'conf@1' configuration Verifying Hash Integrity ... OK Trying 'kernel@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@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.