From: Mathieu Othacehe <othacehe@gnu.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: "Tom Rini" <trini@konsulko.com>, "Peng Fan" <peng.fan@nxp.com>,
"Shiji Yang" <yangshiji66@outlook.com>, "Ye Li" <ye.li@nxp.com>,
"Sébastien Szymanski" <sebastien.szymanski@armadeus.com>,
"Simon Glass" <sjg@chromium.org>,
u-boot@lists.denx.de
Subject: Re: [PATCH 0/2] imx93_var_som: Enable AHAB support
Date: Fri, 09 Feb 2024 09:04:58 +0100 [thread overview]
Message-ID: <87le7uyset.fsf@gnu.org> (raw)
In-Reply-To: <CAOMZO5DhQqjsAy4eoZqKdaTT96EWfRa+Vra3gvRCwXP+6fXt0w@mail.gmail.com> (Fabio Estevam's message of "Thu, 8 Feb 2024 18:20:57 -0300")
Hello Fabio,
> Just wanted to make sure I understand: if someone programs the fuse to
> close the board,
> it will fail to boot U-Boot proper and this means that the board is
> bricked. Is this correct?
No. I fused the board and with this series applied and the three HAFDBS
commits reverted, I can boot just fine on that board.
Without reverting those commits, the SPL is working fine and u-boot
hangs at relocation. It is 100% reproducible on my board.
> Is the boot failure related to some malloc size needing to be increased?
I tried that it has no influence.
Thanks,
Mathieu
next prev parent reply other threads:[~2024-02-09 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 9:45 [PATCH 0/2] imx93_var_som: Enable AHAB support Mathieu Othacehe
2024-02-08 9:45 ` [PATCH 1/2] board: imx93_var_som: Probe ELE MU Mathieu Othacehe
2024-02-08 21:27 ` Fabio Estevam
2024-02-09 10:30 ` Mathieu Othacehe
2024-02-08 9:45 ` [PATCH 2/2] configs: imx93_var_som: Enable AHAB support Mathieu Othacehe
2024-02-08 21:20 ` [PATCH 0/2] " Fabio Estevam
2024-02-09 8:04 ` Mathieu Othacehe [this message]
2024-02-09 10:35 ` Fabio Estevam
2024-02-09 14:24 ` Mathieu Othacehe
2024-02-09 14:28 ` 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=87le7uyset.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=festevam@gmail.com \
--cc=peng.fan@nxp.com \
--cc=sebastien.szymanski@armadeus.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=yangshiji66@outlook.com \
--cc=ye.li@nxp.com \
/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