All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Salveti <rsalveti@rsalveti.net>
To: u-boot@lists.denx.de
Subject: i.MX8MM-EVK Boot failure
Date: Thu, 12 Dec 2019 18:19:53 -0300	[thread overview]
Message-ID: <CAHYQr0oZVmvNSWq5ojtXLWqf=OvZVMVvZ0VEhwFCobfAtxa=wg@mail.gmail.com> (raw)
In-Reply-To: <AM0PR04MB44818B2932C9671226C8E564885A0@AM0PR04MB4481.eurprd04.prod.outlook.com>

Hi,

On Wed, Dec 11, 2019 at 12:05 AM Peng Fan <peng.fan@nxp.com> wrote:
>
> > Subject: Re: i.MX8MM-EVK Boot failure
> >
> > Hi Peng,
> >
> > On Tue, Dec 10, 2019 at 10:48 PM Peng Fan <peng.fan@nxp.com> wrote:
> >
> > > What you modified? It boots well with Tom's tree.
> >
> > Does imx8mq-evk also boot for you?
> >
> > I followed the imx8mq-evk README instructions and it does not boot here.
> >
> > Maybe you are using different ATF/DDR firmware versions?
> >
> > Does it work if you follow the README steps?
>
> I not download that, just use my local ATF/DDR,
> U-Boot SPL 2020.01-rc4-00208-g520f955902 (Dec 11 2019 - 11:22:53 +0800)
> PMIC:  PFUZE100 ID=0x10
> DDRINFO: start DRAM init
> DDRINFO:ddrphy calibration done
> DDRINFO: ddrmix config done
> Normal Boot
> Trying to boot from MMC2
> NOTICE:  Configuring TZASC380
> NOTICE:  RDC off
> NOTICE:  BL31: v2.0(release):rel_imx_4.14.98_2.3.0_rc1-1-g8138ffe5c-dirty
> NOTICE:  BL31: Built : 03:17:34, Dec 11 2019
> NOTICE:  sip svc init
>
>
> U-Boot 2020.01-rc4-00208-g520f955902 (Dec 11 2019 - 11:22:53 +0800)
>
> CPU:   Freescale i.MX8MQ rev2.1 at 1000 MHz
> Reset cause: POR
> Model: NXP i.MX8MQ EVK
> DRAM:  3 GiB
> MMC:   FSL_SDHC: 0, FSL_SDHC: 1
> Loading Environment from MMC... unable to select a mode
> *** Warning - No block device, using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Net:
> Warning: ethernet at 30be0000 using MAC address from ROM
> eth0: ethernet at 30be0000
> Hit any key to stop autoboot:  0
>
> But there is true a mmc env issue here, I am checking.

Can you also confirm if mmc is working correctly on imx8mm evk?

I currently building with atf imx_4.19.35_1.1.0 and firmware-imx 8.5
(tried multiple versions, no difference) and I'm unable to get u-boot
to find the mmc device. The funny thing is that SPL itself seems to be
fine, the problem is really just u-boot:

U-Boot SPL 2020.01-rc4-00245-g7ab49b8c8a (Dec 12 2019 - 18:15:31 -0300)
DDRINFO: start DRAM init
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from MMC1
NOTICE:  Configuring TZASC380
NOTICE:  RDC off
NOTICE:  BL31: v2.0(release):rel_imx_4.19.35_1.1.0-0-g70fa7bcc1-dirty
NOTICE:  BL31: Built : 18:09:39, Dec 12 2019
NOTICE:  sip svc init

U-Boot 2020.01-rc4-00245-g7ab49b8c8a (Dec 12 2019 - 18:15:31 -0300)

CPU:   Freescale i.MX8MMQ rev1.0 at 1200 MHz
Reset cause: POR
Model: FSL i.MX8MM EVK board
DRAM:  2 GiB
MMC:   FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:
Warning: ethernet at 30be0000 using MAC address from ROM
eth0: ethernet at 30be0000
Hit any key to stop autoboot:  0
MMC Device 0 not found
no mmc device at slot 0
MMC Device 0 not found
no mmc device at slot 0

Will investigate more tomorrow, but reporting as you might know where
the problem is.

Thanks,
-- 
Ricardo Salveti de Araujo

  parent reply	other threads:[~2019-12-12 21:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-07 14:42 i.MX8MM-EVK Boot failure Adam Ford
2019-12-07 18:25 ` 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 [this message]
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='CAHYQr0oZVmvNSWq5ojtXLWqf=OvZVMVvZ0VEhwFCobfAtxa=wg@mail.gmail.com' \
    --to=rsalveti@rsalveti.net \
    --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.