mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Rouven Czerwinski <r.czerwinski@pengutronix.de>
To: "Yazdani, Reyhaneh" <RYazdani@data-modul.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: load BL31 on imx8mm and imx8mq
Date: Wed, 26 Jun 2019 11:28:18 +0200	[thread overview]
Message-ID: <c1496d83a1ba4d4a61d69bf04abe4c6965a235a3.camel@pengutronix.de> (raw)
In-Reply-To: <24b0cc8b-93b2-ccf8-9b9d-1d618584958e@data-modul.com>

On Wed, 2019-06-26 at 08:46 +0000, Yazdani, Reyhaneh wrote:
> Hello everyone,
> 
> 
> On the process of bring-up imx8mm board, I am at the point that load
> bl31 and
> jump to ATF.Upon exit from ATF's initialization routine, the
> execution level
> should be EL2.
> 
> My question is about imx8mq_atf_load_bl31 function.
> After copy BL31 into OCRAM address, the function sets up the sp_el2
> to
> "MX8MQ_ATF_BL33_BASE_ADDR - 16".
> 
> Can anyone explain me why this address? Because I am using the same
> address for
> imx8mm and it seems Barebox does not return to this point.

sp_el2 is the address for the stack pointer in el2. This is done so
there is a stack pointer setup after returning from TF-A.
The TF-A return address is compiled into the TF-A and may be different
for the imx8mm. Looking into the TF-A PLAT_NS_IMAGE_OFFSET is set to
0x40200000. So execution should continue after TF-A at this address.

Regards,
Rouven Czerwinski


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2019-06-26  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26  8:46 Yazdani, Reyhaneh
2019-06-26  9:28 ` Rouven Czerwinski [this message]
2019-06-26  9:51   ` AW: " Yazdani, Reyhaneh
2019-06-26 10:25     ` Rouven Czerwinski
2019-06-26 13:12       ` Yazdani, Reyhaneh

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=c1496d83a1ba4d4a61d69bf04abe4c6965a235a3.camel@pengutronix.de \
    --to=r.czerwinski@pengutronix.de \
    --cc=RYazdani@data-modul.com \
    --cc=barebox@lists.infradead.org \
    /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