All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gujulan Elango, Hari Prasath (H.)" <hgujulan@visteon.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Cc: "Vadivel, Arulpandiyan \(A.\)" <avadive1@visteon.com>,
	"Ravindran, Madhusudhanan \(M.\)" <mravindr@visteon.com>,
	"Rajagopalan, Thiagarajan \(T.\)" <trajagop@visteon.com>,
	"DHANAPAL,
	GNANACHANDRAN \(G.\)" <gnanachandran.dhanapal@visteon.com>
Subject: Re: FIT Image boot issue
Date: Wed, 5 Apr 2017 04:54:21 +0000	[thread overview]
Message-ID: <DB6PR0601MB26636F9796635B663F069033CF0A0@DB6PR0601MB2663.eurprd06.prod.outlook.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1525 bytes --]

Sorry the its file was blocked by Outlook. Renamed the extension and re-attaching it.

Regards,
Hari Prasath

From: Gujulan Elango, Hari Prasath (H.)
Sent: Tuesday, April 04, 2017 7:39 PM
To: yocto@yoctoproject.org
Cc: Rajagopalan, Thiagarajan (T.); Vadivel, Arulpandiyan (A.); Ravindran, Madhusudhanan (M.); DHANAPAL, GNANACHANDRAN (G.)
Subject: FIT Image boot issue

Hello all,

We are using FIT image in an ARM 64 bit target based instead of separate Linux binary(Image.bin) and DTB. We are using a copy of the kernel fit image bbclass provided by poky in our custom machine layer to build the fit image. We observe that the bootloader is not able to load the device tree from the RAM. We are using Yocto project 2.1 and kernel version 4.9

Additionally, we observe that the fit image size varies across builds. We are observing two different image sizes viz 6855936 and 6855932 bytes. Of these two, the fit image with size 6855932 bytes boot properly while the image with size 6855936 doesn't boot. Most often the image with 6855932 bytes is generated as build output. Out of 5 to 7 builds (approximately), the image with size 6855936 bytes that causes the boot issue is generated once.

We had modified our custom machine conf file and the kernel-fitimage.bbclass provided by poky layer for adding fit Image support . I have attached the modified fitimage bbclass file,our custom machine layer conf file ,its file generated and the error log during boot for your reference.

Regards,
Hari Prasath


[-- Attachment #1.2: Type: text/html, Size: 4450 bytes --]

[-- Attachment #2: fitImage-its-salvator-x --]
[-- Type: application/octet-stream, Size: 1486 bytes --]

/dts-v1/;

/ {
        description = "U-Boot fitImage for Poky (Yocto Project Reference Distro)/4.9.0+gitAUTOINC+13e7680774/salvator-x";
        #address-cells = <1>;

        images {
                kernel@1 {
                        description = "Linux kernel";
                        data = /incbin/("linux.bin");
                        type = "kernel";
                        arch = "arm64";
                        os = "linux";
                        compression = "gzip";
                        load = <0x48080000>;
                        entry = <0x48080000>;
                        hash@1 {
                                algo = "sha1";
                        };
                };
                fdt@1 {
                        description = "Flattened Device Tree blob";
                        data = /incbin/("arch/arm64/boot/dts/renesas/r8a7795-es1-salvator-x.dtb");
                        type = "flat_dt";
                        arch = "arm64";
                        compression = "none";
                        hash@1 {
                                algo = "sha1";
                        };
                };
	};

        configurations {
                default = "conf@1";
                conf@1 {
                        description = "Boot Linux kernel with FDT blob";
			kernel = "kernel@1";
			fdt = "fdt@1";
                        hash@1 {
                                algo = "sha1";
                        };
                };
	};
};

             reply	other threads:[~2017-04-05  5:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05  4:54 Gujulan Elango, Hari Prasath (H.) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-04-04 14:08 FIT Image boot issue Gujulan Elango, Hari Prasath (H.)
2017-04-05  9:07 ` Fabien Lahoudere

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=DB6PR0601MB26636F9796635B663F069033CF0A0@DB6PR0601MB2663.eurprd06.prod.outlook.com \
    --to=hgujulan@visteon.com \
    --cc=avadive1@visteon.com \
    --cc=gnanachandran.dhanapal@visteon.com \
    --cc=mravindr@visteon.com \
    --cc=trajagop@visteon.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.