mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Renaud Barbier <Renaud.Barbier@ametek.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: LS1046A PPA firmware
Date: Thu, 16 Nov 2023 08:47:39 +0100	[thread overview]
Message-ID: <20231116074739.GF3359458@pengutronix.de> (raw)
In-Reply-To: <BL0PR07MB56659217EA475581808B70E7ECB1A@BL0PR07MB5665.namprd07.prod.outlook.com>

Hi Renauld,

On Wed, Nov 15, 2023 at 04:50:54PM +0000, Renaud Barbier wrote:
> For your  information, the ppa firmware loaded for the LS1046A by
> Barebox does not work for the LS1026A.  The build from SDK PPA
> Firmware: Version LSDK-18.06 is needed to work with the dual core.

Good to know, thanks.

On a related note, it seems the PPA firmware loading is broken
in current master and likely the last release. With dba1c26f70
("arm: layerscape: ppa: reserve SDRAM region for PPA") the area
where the PPA is started is mapped uncached and non-executable.
That's silly of course because we jump to that area a few moments
later. We have to map it uncached when the PPA returns, but not
before. I think it was broken already before that patch as we call
barebox_arm_entry() with the PPA area skipped, so I think the PPA
range is uncached/non-executable even without this patch due to
latest MMU changes.

Unfortunately I found that out by bricking my board, so I can only
fix that when the board is recovered.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2023-11-16  7:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 16:50 Renaud Barbier
2023-11-16  7:47 ` Sascha Hauer [this message]

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=20231116074739.GF3359458@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=Renaud.Barbier@ametek.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