From: hendrik <hendrik.vastech@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Cant Create FIT uImage
Date: Thu, 12 Feb 2009 15:35:44 +0200 [thread overview]
Message-ID: <499425B0.2050200@gmail.com> (raw)
Hi all
I would like to boot using the new style FDT kernel booting. I have been
using the guidelines in "u-boot-2009/doc/uImage.FIT/how to" and I have
the latests dtc (v1.2) . But I am unable to compile the FIT image. I
get a syntax error for line 1:
#u-boot/tools/mkimage -f /work/kernel_fdt.its /work/kernel_fdt.itb
FIT format handling
Trying to execute "dtc -I dts -O dtb -p 500 /work/kernel_fdt.its >
/work/kernel_fdt.itb.tmp"
DTC: dts->dtb on file "/work/kernel_fdt.its"
Error: /work/kernel_fdt.its 1:0 syntax error
FATAL ERROR: Unable to parse input tree
usr/src/u-boot/tools/mkimage: Can't read /work/kernel_fdt.itb.tmp:
Invalid argument
#
Can anyone pleas help me to get the FIT image to compile?
My kernel_fdt.its looks as follows: ( taken tron the example given in
u-boot-2009/doc/uImage.FIT/kernel_fdt.its )
/ {
#address-cells = <1>;
description = "Simple image with single Linux kernel and FDT blob";
images {
kernel at 1 {
description = "Linux kernel";
data = /incbin/("/work/build/target/linux/vmlinux.bin.gz");
type = "kernel";
arch = "ppc";
os = "linux";
compression = "gzip";
load = <00000000>;
entry = <00000000>;
hash at 1 {
algo = "crc32";
};
hash at 2 {
algo = "sha1";
};
};
fdt at 1 {
description = "Flattened Device Tree blob";
data = /incbin/("/work/build/target/boot/equus.dtb");
type = "flat_dt";
arch = "ppc";
compression = "none";
hash at 1 {
algo = "crc32";
};
hash at 2 {
algo = "sha1";
};
};
};
configurations {
default = "conf at 1";
conf at 1 {
description = "Boot Linux kernel with FDT blob";
kernel = "kernel at 1";
fdt = "fdt at 1";
};
};
};
Thanks Hendik
next reply other threads:[~2009-02-12 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 13:35 hendrik [this message]
2009-02-16 21:07 ` [U-Boot] Cant Create FIT uImage Wolfgang Denk
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=499425B0.2050200@gmail.com \
--to=hendrik.vastech@gmail.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox