From: Stuart Longland <stuartl@vrt.com.au>
To: u-boot@lists.denx.de
Subject: [U-Boot] i.MX286 U-Boot fails with code HTLLCL0x8050100b
Date: Tue, 16 Feb 2016 22:38:41 +1000 [thread overview]
Message-ID: <56C31851.6080302@vrt.com.au> (raw)
In-Reply-To: <56C14F6A.9060406@vrt.com.au>
On 15/02/16 14:09, Stuart Longland wrote:
> I ask again: Is there somewhere else I should be looking for the cause
> of the above issue?
Well, found my issue in the end I think. In exasperation I dd'ed one of
my working SD card images, proved that the machine booted, then dd'ed
the newly build U-Boot image over the top of the old U-Boot partition.
It worked.
So I'll put this down to the i.MX286 boot ROM being *exceptionally*
picky about partition placement. If things aren't *exactly* right,
it'll flatly refuse to work.
I might see if I can reproduce the bad image and hex-dump it to better
understand what was "wrong".
--
Stuart Longland
Systems Engineer
_ ___
\ /|_) | T: +61 7 3535 9619
\/ | \ | 38b Douglas Street F: +61 7 3535 9699
SYSTEMS Milton QLD 4064 http://www.vrt.com.au
prev parent reply other threads:[~2016-02-16 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 5:34 [U-Boot] i.MX286 U-Boot fails with code HTLLCL0x8050100b Stuart Longland
2016-02-15 4:09 ` Stuart Longland
2016-02-16 12:38 ` Stuart Longland [this message]
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=56C31851.6080302@vrt.com.au \
--to=stuartl@vrt.com.au \
--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