From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 2/3] spl: Allow to load a FIT containing U-Boot from FS
Date: Tue, 3 May 2016 19:19:40 +0530 [thread overview]
Message-ID: <5728AC74.8020403@ti.com> (raw)
In-Reply-To: <5728A01E.3020306@xilinx.com>
On Tuesday 03 May 2016 06:27 PM, Michal Simek wrote:
> Hi,
[..snip..]
>
> this is not working for me. I haven't had a time to look at it
> but you might know where the problem is.
>
> Thanks,
> Michal
>
> U-Boot SPL 2016.05-rc3-00067-g01d410633461-dirty (May 03 2016 - 14:43:30)
> Trying to boot from MMC1
> reading u-boot.bin
> reading u-boot.img
> Found FIT
> spl_fit_read: name u-boot.img, file_offset 0, size 44c, buf 7fffb40
> reading u-boot.img
> spl_fit_read: error reading image u-boot.img, ret - 0
> fit read sector 0, sectors=1100, dst=0000000007fffb40, count=1100
> data_offset=0, data_size=80310
> U-Boot size 80310, data 0000000008000000
> Aligned image read: dst=0000000008000000, src_sector=440, sectors=80310
> spl_fit_read: name u-boot.img, file_offset 440, size 80310, buf 8000000
> reading u-boot.img
> spl_fit_read: error reading image u-boot.img, ret - 0
> image: dst=0000000008000000, data_offset=44c, size=80310
> Selecting config 'zynqmp-zcu102', fdt 'fdt at 1'
> FIT: Selected 'zynqmp-zcu102'
> spl_fit_read: name u-boot.img, file_offset 80740, size 6603, buf 8080340
> reading u-boot.img
> ** Unable to read file u-boot.img **
> spl_fit_read: error reading image u-boot.img, ret - -1
The error started here. It is able to detect fdt from fit header but not
able to read it from file. If you don't mind can you tell me what is the
size of the file u-boot.img?
A dumb question: Can you confirm that on this same HEAD the RFC patch
from you works fine?
I verified this on 2 different platforms and worked fine. Lets see If I
am missing any corner case.
Thanks and regards,
Lokesh
> Aligned fdt read: dst 0000000008080340, src_sector = 80740, sectors 6603
> reading u-boot.img
> spl_load_image_fat: error reading image u-boot.img, err - -1
> SPL: failed to boot from all boot devices
> ### ERROR ### Please RESET the board ###
>
>
next prev parent reply other threads:[~2016-05-03 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 9:05 [U-Boot] [PATCH v4 0/3] spl: Add support to load FIT from Filesystem Lokesh Vutla
2016-05-03 9:05 ` [U-Boot] [PATCH v4 1/3] spl: fit: Fix the number of bytes read when reading fdt from fit Lokesh Vutla
2016-05-03 9:05 ` [U-Boot] [PATCH v4 2/3] spl: Allow to load a FIT containing U-Boot from FS Lokesh Vutla
2016-05-03 12:57 ` Michal Simek
2016-05-03 13:49 ` Lokesh Vutla [this message]
2016-05-03 12:59 ` Michal Simek
2016-05-03 14:12 ` Lokesh Vutla
2016-05-03 9:05 ` [U-Boot] [PATCH v4 3/3] spl: Support loading a FIT from FAT FS Lokesh Vutla
2016-05-03 12:58 ` Michal Simek
2016-05-03 13:59 ` Lokesh Vutla
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=5728AC74.8020403@ti.com \
--to=lokeshvutla@ti.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