From: Anshul Dalal <anshuld@ti.com>
To: Anshul Dalal <anshuld@ti.com>, <meta-ti@lists.yoctoproject.org>
Cc: <c-shilwant@ti.com>, <reatmon@ti.com>, <vigneshr@ti.com>,
<praneeth@ti.com>
Subject: Re: [PATCH v1 1/2] conf: machine: k3: update fitImage load address
Date: Fri, 27 Jun 2025 11:36:31 +0530 [thread overview]
Message-ID: <DAX394J0MLYR.3DH4O5A7846IF@ti.com> (raw)
In-Reply-To: <20250627060416.639661-1-anshuld@ti.com>
On Fri Jun 27, 2025 at 11:34 AM IST, Anshul Dalal wrote:
> In yocto, the UBOOT_ENTRYPOINT and UBOOT_*LOADADDRESS variables specify
> the entry point and load addresses for the kernel image and the DTB when
> creating the fitImage[1].
>
> Currently the load address for the kernel is set to 0x81000000 and
> 0x83000000 for the DTB for all k3 platforms.
>
> However the region 0x80080000 to 0x81880000 is reserved for OPTEE on
> am62xxsip-evm, leading to boot failure[2] when using the fitImage.
>
> This patch fixes the issue by changing the addresses to 0x82000000 for
> kernel and 0x88000000 for the DTB. This also allows us to load kernel
> images > 32MiB in size when not using initrd while also making the
> falcon and standard boot addresses consistent.
>
> [1]:
> https://docs.yoctoproject.org/ref-manual/variables.html#term-UBOOT_ENTRYPOINT
> [2]:
> https://raw.githubusercontent.com/ArchUsr64/ti_boot_logs/HEAD/am62xxsip-evm/failures/fitImage_load_addr_issue.log
>
> Signed-off-by: Anshul Dalal <anshuld@ti.com>
> ---
Sorry I forgot to add prefix in the subject, this patch set is meant for
scarthgap-next.
Regards,
Anshul
prev parent reply other threads:[~2025-06-27 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 6:04 [PATCH v1 1/2] conf: machine: k3: update fitImage load address Anshul Dalal
2025-06-27 6:04 ` [PATCH v1 2/2] conf: machine: move UBOOR_*ADDRESS to top level ti-soc Anshul Dalal
2025-06-27 14:32 ` Ryan Eatmon
2025-06-27 14:39 ` Anshul Dalal
2025-06-27 14:43 ` Ryan Eatmon
2025-06-27 6:06 ` Anshul Dalal [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=DAX394J0MLYR.3DH4O5A7846IF@ti.com \
--to=anshuld@ti.com \
--cc=c-shilwant@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.