All of lore.kernel.org
 help / color / mirror / Atom feed
From: Schrempf Frieder <frieder.schrempf@kontron.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] i.MX8MM mapped register access causes crashes
Date: Thu, 6 Jun 2019 06:47:52 +0000	[thread overview]
Message-ID: <da66eccb-c229-9c29-f9ac-b5890d655eb6@kontron.de> (raw)
In-Reply-To: <AM0PR04MB448166E5F03C41038C6B24B888170@AM0PR04MB4481.eurprd04.prod.outlook.com>

On 06.06.19 03:58, Peng Fan wrote:
> 
>> Subject: Re: [U-Boot] i.MX8MM mapped register access causes crashes
>>
>> On Wed, Jun 5, 2019 at 10:52 PM Peng Fan <peng.fan@nxp.com> wrote:
>>
>>> You need to pass an arg after `md 0x302d0000`. Default it will dump a
>>> lot registers, might 40 registers. It surely will crash, because there
>>> are only a few registers in GPT1 which is the address you are dumping.
>>
>> Other suggestion is to make sure that the clock for the peripheral you are
>> trying to access is turned on.
> 
> Dump `md 0x302d0000 1` will surely work, but dump `md 0x302d0000 100`
> will surely crash. The clock already on. It is that GPT1 does not have 100
> registers, and trigger error when dumping non-existed registers.

Thanks for your suggestions. I just used GPT1 as an example. As you can 
see GPT1 registers can be dumped, but at the start of GPT2 it crashes.

I have the same problem for all kinds of other peripherals. For example 
I tried to enable I2C1, but the driver hangs in probe when it accesses 
an I2C1 register for the first time.

I suspect that this is either, as Fabio said, caused by clocks that are 
turned off, or because of trustzone settings. I'm not loading any ATF at 
the moment, so I'm booting from SPL directly to U-Boot proper and I'm 
not sure if the trustzone settings restrict access to the peripherals in 
this case.

Thanks,
Frieder

  reply	other threads:[~2019-06-06  6:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05  9:15 [U-Boot] i.MX8MM mapped register access causes crashes Schrempf Frieder
2019-06-06  1:51 ` Peng Fan
2019-06-06  1:55   ` Fabio Estevam
2019-06-06  1:58     ` Peng Fan
2019-06-06  6:47       ` Schrempf Frieder [this message]
2019-06-06  7:26         ` Peng Fan

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=da66eccb-c229-9c29-f9ac-b5890d655eb6@kontron.de \
    --to=frieder.schrempf@kontron.de \
    --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.