From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andre Wolokita <andre.wolokita@analog.com>
Date: Tue, 24 Mar 2015 10:42:08 +1100
Subject: [U-Boot] multi-image uImage with fitImage
In-Reply-To: <CAPnjgZ10jCSpSNkf7ydJoBN+QpbPngj_-paSf3_pf6pzqoEqdg@mail.gmail.com>
References: <CAEm3GYK5bv5eX=OJhLgW1HWbSGRkQhPfs7nyRwLcU834UpSjgg@mail.gmail.com>
 <CAPnjgZ10jCSpSNkf7ydJoBN+QpbPngj_-paSf3_pf6pzqoEqdg@mail.gmail.com>
Message-ID: <5510A4D0.1080108@analog.com>
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

Hi Simon,

On 24/03/15 10:14, Simon Glass wrote:
> Hi,
>
> On 23 March 2015 at 00:40, fat loser <george.cluniac@gmail.com> wrote:
>> Hi all,
>>
>> I am currently attempting to port my combined uImage and ramdisk image +
>> dtb over to the fitImage format. I am creating a linux kernel + ramdisk
>> with buildroot and dt blob with buildroot. The .its I am using to create a
>> fitImage is below:
>>
>> /dts-v1/;
>> / {
>>         description = "Linux kernel";
>>         #address-cells = <1>;
>>         images {
>>                 kernel at 1 {
>>                         description = "Linux kernel";
>>                         data = /incbin/("/tftpboot/uImage");
>>                         arch = "arm";
>>                         os = "linux";
>>                         type = "multi";
> What is multi? Do you want kernel or kernel_noload?
I read somewhere that multi can represent a kernel+ramdisk uImage (image with ramdisk linked in.) If try to use "kernel" here, I get an error like: ERROR: new format image overwritten - must RESET the board to recover
resetting ...
>
>>                         compression = "none";
>>                         load = <0x89008000>;
>>                         entry = <0x89008000>;
>>                 };
>>                 fdt at 1 {
>>                         description = "Flattened Device Tree blob";
>>                         data = /incbin/("/tftpboot/arm.dtb");
>>                         type = "flat_dt";
>>                         arch = "arm";
>>                         compression = "none";
>>                 };
>>         };
>>         configurations {
>>                 default = "conf at 1";
>>                 conf at 1 {
>>                         description = "Boot Linux kernel";
>>                         kernel = "kernel at 1";
>>                         fdt = "fdt at 1";
>>                 };
>>         };
>> };
>>
>> After tftp'ing the .itb over to address 0x89000000 and running bootm, I get:
>>
>> # bootm
>> ## Loading kernel from FIT Image at 89000000 ...
>>    Using 'conf at 1' configuration
>>    Trying 'kernel at 1' kernel subimage
>>      Description:  Linux kernel
>>      Type:         Multi-File Image
>>      Compression:  uncompressed
>>      Data Start:   0x890000d0
>>      Data Size:    28604352 Bytes = 27.3 MiB
>>    Verifying Hash Integrity ... OK
>> No Linux ARM Kernel Image Image
>> ERROR: can't get kernel image!
>>
>> The images work perfectly before I try to combine them into a fitImage.
>>
>> Is there a special configuration option for multi-file (combined
>> ramdisk-kernel) images in fitImage?
>>
>> Regards,
>>
>> George.
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
> Regards,
> Simon
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>

-- 
Andre Wolokita (andre.wolokita at analog.com)
Design Engineer, Analog Devices Australia Pty Ltd
Unit 3, 97 Lewis Road, Wantirna, Victoria, 3152, AUSTRALIA
Direct: +61 3 9881 9933   Main: +61 3 9881 9999
Fax: +61 3 9881 9988      Web: www.analog.com/au

Embedded DSP software for multimedia & telecommunications.

This communication is proprietary and confidential.