From: Anshul Dalal <anshuld@ti.com>
To: Wadim Egorov <w.egorov@phytec.de>, <trini@konsulko.com>,
<ggiordano@phytec.com>, <d.schultz@phytec.de>, <bb@ti.com>
Cc: <u-boot@lists.denx.de>, <upstream@lists.phytec.de>
Subject: Re: [PATCH 1/2] board: phytec: phycore_am6xx: Update scriptaddr
Date: Fri, 19 Sep 2025 17:28:59 +0530 [thread overview]
Message-ID: <DCWRCRBERKOZ.3QATM9M067WNX@ti.com> (raw)
In-Reply-To: <20250919063948.3093358-2-w.egorov@phytec.de>
On Fri Sep 19, 2025 at 12:09 PM IST, Wadim Egorov wrote:
> After switching our boards to standard boot, we observed that the
> kernel hangs when booting with the "script" boot method over the
> network.
>
> The original scriptaddr value was copied from ti_common.env and
> remained unused for some time. On phycore-am62x and phycore-am62ax,
> however, this address conflicts with the current location where
> ATF is loaded (CONFIG_K3_ATF_LOAD_ADDR).
>
We should look into doing similar for K3 as well, would be useful when
we switch to std boot as well.
> Move scriptaddr to 0x89100000, directly after fdtoverlay_addr_r.
> The phycore-am64x is not affected by this issue, but we update it
> as well to keep all phycore-am6xx boards consistent.
>
> Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
> ---
Reviewed-by: Anshul Dalal <anshuld@ti.com>
Regards,
Anshul
next prev parent reply other threads:[~2025-09-19 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 6:39 [PATCH 0/2] Fix boot w/ scriptaddr & minor newline issue Wadim Egorov
2025-09-19 6:39 ` [PATCH 1/2] board: phytec: phycore_am6xx: Update scriptaddr Wadim Egorov
2025-09-19 11:58 ` Anshul Dalal [this message]
2025-09-19 6:39 ` [PATCH 2/2] board: phytec: common: Fix missing newline in error message Wadim Egorov
2025-09-24 13:52 ` [PATCH 0/2] Fix boot w/ scriptaddr & minor newline issue Tom Rini
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=DCWRCRBERKOZ.3QATM9M067WNX@ti.com \
--to=anshuld@ti.com \
--cc=bb@ti.com \
--cc=d.schultz@phytec.de \
--cc=ggiordano@phytec.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox