From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: u-boot@lists.denx.de
Subject: Cannot boot firefly-rk3399: mmc block read error
Date: Thu, 28 May 2020 18:54:06 +0200 (CEST) [thread overview]
Message-ID: <ea26daa123f371ec@bloch.sibelius.xs4all.nl> (raw)
In-Reply-To: <CAPnjgZ3eL9hKTdHiM+Om+gZdu2SRhVnAtouqofEZ0eiaRF_xsw@mail.gmail.com> (message from Simon Glass on Thu, 28 May 2020 08:58:16 -0600)
> From: Simon Glass <sjg@chromium.org>
> Date: Thu, 28 May 2020 08:58:16 -0600
>
> Hi,
>
> I get an error in SPL. Any ideas?
>
> ellesmere:~/u$ dd if=/tmp/b/firefly-rk3399/idbloader.img of=/dev/sdb seek=64
> 265+1 records in
> 265+1 records out
> 135987 bytes (136 kB, 133 KiB) copied, 0.0233712 s, 5.8 MB/s
> ellesmere:~/u$ dd if=/tmp/b/firefly-rk3399/u-boot.itb of=/dev/sdb seek=16384
> ...
>
>
> U-Boot TPL 2020.07-rc3-00009-ge80a17f6909 (May 28 2020 - 08:45:27)
> Channel 0: DDR3, 800MHz
> BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
> Channel 1: DDR3, 800MHz
> BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
> 256B stride
> 256B stride
> Trying to boot from BOOTROM
> Returning to boot ROM...
>
> U-Boot SPL 2020.07-rc3-00009-ge80a17f6909 (May 28 2020 - 08:45:27 -0600)
> Trying to boot from MMC2
> mmc_load_image_raw_sector: mmc block read error
> Trying to boot from MMC1
> mmc_load_image_raw_sector: mmc block read error
> SPL: failed to boot from all boot devices
> ### ERROR ### Please RESET the board ###
What version of ATF are you using? Mine boots fine with upstream ATF 2.3.
Cheers,
Mark
next prev parent reply other threads:[~2020-05-28 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 14:58 Cannot boot firefly-rk3399: mmc block read error Simon Glass
2020-05-28 16:54 ` Mark Kettenis [this message]
2020-05-28 16:59 ` Jagan Teki
2020-05-29 14:29 ` Simon Glass
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=ea26daa123f371ec@bloch.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.