Re: [U-Boot] Booting kernel/dtb with FIT image

On Fri, Jan 13, 2017 at 6:13 PM, Nicolas le bayon nlebayon@gmail.com wrote:

Hi,

Here is a problem I presently meet, any help or track to follow would be welcome.

My U-boot (2016.09) loads a kernel and a dtb, and "bootm" all this. This is my reference, and this is correctly running.

From this, I'm trying to implement FIT image management, so I enabled CONFIG_FIT.

On the other side, I constructed the ITS FILE from my kernel and my dtb, as described below:

*/dts-v1/;* */ {*

• description = "Simple image with single Linux kernel and FDT blob";*
• #address-cells = <0x1>;*
• images {*

•    kernel@1 {*
  

•        description = "My Linux kernel";*
  

•        data = /incbin/("./uImage");*
  

Usually kernel images can be considered to vmlinux.bin or vmlinux.bin.gz (if compressed) in its

•        type = "kernel";*
  

•        arch = "arm";*
  

•        os = "linux";*
  

•        compression = "none";*
  

•        load = <0x40008000>;*
  

•        entry = <0x40008000>;*
  

•        hash@1 {*
  

•            algo = "md5";*
  

•        };*
  

•        hash@2 {*
  

•            algo = "sha1";*
  

•        };*
  

•    };*
  

•    fdt@1 {*
  

•        description = "My Flattened Device Tree blob";*
  

•        data = /incbin/("./mydtb.dtb");*
  

•        type = "flat_dt";*
  

•        arch = "arm";*
  

•        compression = "none";*
  

•        hash@1 {*
  

•            algo = "md5";*
  

•        };*
  

•        hash@2 {*
  

•            algo = "sha1";*
  

•        };*
  

•    };*
  

• };*

*/* a notable concept of FIT, configurations */*

• configurations {*

•    default = "conf@1";*
  

•    conf@1 {*
  

•        description = "Boot Linux kernel with FDT blob";*
  

•        kernel = "kernel@1";*
  

•        fdt = "fdt@1";*
  

•    };*
  

• };*

*};*

I managed to construct the ITB (using the mkimage of my u-boot, in tools directory) and to store it on my target.

I load this ITB at 0x60000000 address of memory.

The "bootm 0x60000000" gives the following error: "Ramdisk image is corrupt or invalid". Indeed I have no ramdisk. Not what was described in tutorials.

Sorry I didn't see "Ramdisk image" correct on below log, shall I miss?

thanks!