All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Ford <aford173@gmail.com>
To: u-boot@lists.denx.de
Subject: i.MX8MM-EVK Boot failure
Date: Sat, 7 Dec 2019 08:42:32 -0600	[thread overview]
Message-ID: <CAHCN7xKx1G-RmP5QA3nHinSPi60ji1TOi08USydU=vXEWU4=8g@mail.gmail.com> (raw)

I am trying to run the latest master

4b19b89ca4a866b7baa642533e6dbd67cd832d27
with the clock patches applied for 8mm, but I am getting a boot
failure when I follow the instructions in the README, which are also a
bit wrong.  (the firmware versions don't match, and the ./firmware
command is missing the trailing '.bin', but it's trivial.)

What comes out of the kit with DEBUG enabled is:

(bunch of stuff deleted)

[PMU Major message = 0x000000fe]
[PMU Major message = 0x00000007]
Training PASS
DDRINFO: ddrphy config done
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
>>SPL: board_init_r()
using memory lx-lx for malloc()
spl_init
Normal Boot
Trying to boot from MMC1
common/dlmalloc.c:792: do_check_inuse_chunk: Assertion `inuse(p)' failed.
resetting ...

The above sequence repeats again and again.  I didn't put all the junk
into the log because it looked like everything seemed OK until the
dlmalloc failure at the end.  If someone has any suggestions, I'd like
to try the 8mm-evk with a modern U-Boot.

thank you,


adam

             reply	other threads:[~2019-12-07 14:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-07 14:42 Adam Ford [this message]
2019-12-07 18:25 ` i.MX8MM-EVK Boot failure Tom Rini
2019-12-08 12:50   ` Adam Ford
2019-12-08 15:34     ` Adam Ford
2019-12-08 16:26       ` Michael Nazzareno Trimarchi
2019-12-10  1:17 ` Fabio Estevam
2019-12-11  1:48 ` Peng Fan
2019-12-11  1:58   ` Fabio Estevam
2019-12-11  3:05     ` Peng Fan
2019-12-11  3:13       ` Fabio Estevam
2019-12-11 12:58         ` Adam Ford
2019-12-11 13:46           ` Fabio Estevam
2019-12-12 21:19       ` Ricardo Salveti
2019-12-13  9:44         ` Fabio Estevam
2019-12-13 11:22           ` Ricardo Salveti
2019-12-16 19:20         ` Fabio Estevam

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='CAHCN7xKx1G-RmP5QA3nHinSPi60ji1TOi08USydU=vXEWU4=8g@mail.gmail.com' \
    --to=aford173@gmail.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 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.