mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Renaud Barbier <Renaud.Barbier@ametek.com>
To: Barebox List <barebox@lists.infradead.org>
Subject: ls1046ardb tfa
Date: Fri, 18 Jul 2025 14:05:18 +0000	[thread overview]
Message-ID: <DM5PR07MB35323A0A603D7DA45560BFE5EC50A@DM5PR07MB3532.namprd07.prod.outlook.com> (raw)

We have a board using the LS1046A (based on the LS1046ARDB) and recently moved to v2025.06.1.
There is a failure to boot.
I noticed that the PPA support is gone from the ls1046ardb and enabled FIRMWARE_LS1046A_ATF and
built the bl31.bin file from  https://github.com/nxp-qoriq/atf.git which is copied under the directory firmware/
At present, I have a limited knowledge of TFA support.

The dram structure passed to bl31 is as follows:
 static struct dram_regions_info dram_info = {
           .num_dram_regions = 1,
           .total_dram_size = SZ_2G,
           .region = {
                   {
                           .addr = SZ_2G,
                           .size = SZ_2G,
                   },
           },
  };

Debug output:
Data Bus test:
        Walking 0: PASS
        Walking 1: PASS

Pattern Test:
        Pattern (ffffffff): PASS.............
        Pattern (0): PASS.............

layerscape-tfa: ls1046_start_tfa
firmware_ext_verify
CH cb617c70c11f0f4d21bc31e1e324a952b313de0629cd13f80bd50470814e8a1a
IH cb617c70c11f0f4d21bc31e1e324a952b313de0629cd13f80bd50470814e8a1a
Hexdump of first 64 bytes of 70065

HASH ret = 0
layerscape-tfa: copy bl31: 00000000800975e0, 70065
layerscape-tfa: sync cache
layerscape-tfa: asm
layerscape-tfa: call bl2_plat_get_bl31_params_v2
layerscape-tfa: Starting bl31

Seeing the TQMLS1046A uses the BL31 firmware, I was wondering if my build of bl31.bin is correct.
Any help welcome.

Cheers,
Renaud






             reply	other threads:[~2025-07-18 14:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18 14:05 Renaud Barbier [this message]
2025-07-18 14:31 ` Renaud Barbier

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=DM5PR07MB35323A0A603D7DA45560BFE5EC50A@DM5PR07MB3532.namprd07.prod.outlook.com \
    --to=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