From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Ramdisk Error
Date: Thu, 21 May 2015 14:01:37 +0200 [thread overview]
Message-ID: <555DC921.5020307@gmail.com> (raw)
In-Reply-To: <CAMvYpdmkPF+gkMvmjUbpgYKqWw--Ms+ZNoeZeZ1MF1P1wWERKQ@mail.gmail.com>
Dear Gaurav Pathak,
On 05/21/2015 12:01 PM, Gaurav Pathak wrote:
> Hello,
> I have two versions of u-boot one is U-Boot 2012.10-00142-g56ac3aa-dirty
> and the latest one is U-Boot 2015.01-linux4sam_4.7-dirty.
> I am using ATSAMA5D31, the issue that I am facing is that the older version
> of u-boot i.e. "U-Boot 2012.10-00142-g56ac3aa-dirty" is able to load
> ramdisk of size greater than 4MB but at later point of time during kernel
> bootup "External imprecise abort 0x1c06" error is shown and the latest
> version of u-boot i.e. "U-Boot 2015.01-linux4sam_4.7-dirty" is not able to
> boot with ramdisk size greater than 4MB and gives error "Verifying
> Checksum.... Bad Data CRC".
> ?
> I want to use latest u-boot from Atmel with
please contact Atmel support for their software. This is the mainline
U-Boot Mailinglist, we can only give support fort mainline U-Boot. But
let's see if I can help you ...
The 'Bad Data CRC' may be some corrupted image or code. It may fail in
2015.01 due to U-Boot relocation, uImage extraction or some other
mechanism which may has changed since 2012.10 (plus unknown patches). So
a bit more information about what exactly is failing and some
surroundings required: Which board? What type of image(s)? What was the
command failing? Which addresses used and how many RAM is available? Any
constraints regarding reserved memory? ....
I'll verify that sama5d3xek is loading ramdisk larger than 4MiB with
mainline U-Boot and post the results.
regards
Andreas Bie?mann
next prev parent reply other threads:[~2015-05-21 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 10:01 [U-Boot] Ramdisk Error Gaurav Pathak
2015-05-21 12:01 ` Andreas Bießmann [this message]
2015-05-22 8:37 ` Andreas Bießmann
2015-05-22 10:12 ` Gaurav Pathak
2015-05-25 13:56 ` Gaurav Pathak
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=555DC921.5020307@gmail.com \
--to=andreas.devel@googlemail.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