public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Christoph Egger <christoph@christoph-egger.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] MMC boot / mvebu / clearfog
Date: Mon, 24 Oct 2016 15:47:40 +0200	[thread overview]
Message-ID: <87twc1j1tv.fsf@anonymous.siccegge.de> (raw)
In-Reply-To: <87vawldxpn.fsf@anonymous.siccegge.de> (Christoph Egger's message of "Sat, 22 Oct 2016 02:38:44 +0200")

Hi!

Christoph Egger <christoph@christoph-egger.org> writes:
> Indeeed, the following patch fixes MMC booting for me (and most
> certainly breaks SD card booting)

It actually seems to be somewhat more difficult. It worked because I had
a old u-boot image at mmcblk0 at offset 1 block and a new u-boot at
mmcblk0boot0. (old ~ before removing the +1). I guess u-boot gets loaded
from the mmc0boot0 device (which is also where the SPL is from) and as
soon as the post-SPL u-boot tries to access it's own bytes it falls over
to mmcblk0.

I have a working setup by

  dd if=u-boot-spl.kwb of=/dev/mmcblk0boot0 bs=512
  dd if=u-boot-spl.kwb of=/dev/mmcblk0      bs=512 seek=1 skip=1

(skipping the first sector to keep the MBR alive and assuming it only
contains SPL code anyway)

  Christoph

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161024/b5c300d4/attachment.sig>

      reply	other threads:[~2016-10-24 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-02 20:21 [U-Boot] MMC boot / mvebu / clearfog Christoph Egger
2016-10-22  0:22 ` Christoph Egger
2016-10-22  0:38   ` Christoph Egger
2016-10-24 13:47     ` Christoph Egger [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=87twc1j1tv.fsf@anonymous.siccegge.de \
    --to=christoph@christoph-egger.org \
    --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