From: Bartlomiej Sieka <tur@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problem creating new uImage
Date: Wed, 04 Jun 2008 14:39:50 +0200 [thread overview]
Message-ID: <48468D16.4080605@semihalf.com> (raw)
In-Reply-To: <87mym1mnlx.fsf@denx.de>
Markus Klotzb?cher wrote:
> Dear List,
>
> I'm facing a problem creating a new fdt image following the instructions
> in the u-boot/doc/uImage.FIT/howto.txt
>
> u-boot and dtc are top of git:
>
> $ dtc -v
> Version: DTC 1.1.0-g050e6f0c
>
> ~/src/git/u-boot/ $ git-describe
> v1.3.3-32-gf2aeecc
>
> I'm in the linux-2.6-denx/ directory with kernel and target blob:
>
> ~/src/git/linux-2.6-denx/ $ ls target.dtb vmlinux.bin.gz
> target.dtb vmlinux.bin.gz
>
> I try to create the new image as follows:
>
> $ ../u-boot/tools/mkimage -f ../u-boot/doc/uImage.FIT/kernel_fdt.its kernel_fdt.itb
> FIT format handling
> Trying to execute "dtc -I dts -O dtb -p 500 ../u-boot/doc/uImage.FIT/kernel_fdt.its > kernel_fdt.itb.tmp"
> DTC: dts->dtb on file "../u-boot/doc/uImage.FIT/kernel_fdt.its"
> ../u-boot/doc/uImage.FIT/kernel_fdt.its:11 syntax error
> FATAL ERROR: Unable to parse input tree
> ../u-boot/tools/mkimage: Can't read kernel_fdt.itb.tmp: Invalid argument
>
> Any ideas?
Hi Markus,
Line 11 of doc/uImage.FIT/kernel_fdt.its is:
data = /incbin/("./vmlinux.bin.gz");
So most likely your problem is due to mainline dtc not supporting binary
includes (yet). You need to patch it with original Scott Wood's patch,
see:
http://www.nabble.com/-PATCH--Add-support-for-binary-includes.-td15596760.html
HTH,
Bartlomiej
next prev parent reply other threads:[~2008-06-04 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 11:43 [U-Boot-Users] Problem creating new uImage Markus Klotzbücher
2008-06-04 12:39 ` Bartlomiej Sieka [this message]
2008-06-04 13:53 ` Markus Klotzbücher
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=48468D16.4080605@semihalf.com \
--to=tur@semihalf.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