From: Chirag Shilwant <c-shilwant@ti.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: <meta-ti@lists.yoctoproject.org>, Ryan Eatmon <reatmon@ti.com>
Subject: Re: [meta-ti][master/scarthgap][PATCH] conf: machine: am62axx: Exclude tiboot3.bin for GP
Date: Mon, 21 Apr 2025 12:07:28 +0530 [thread overview]
Message-ID: <0feaf15d-e3ec-4f10-b651-db4225a40437@ti.com> (raw)
In-Reply-To: <20250417182828.GX13634@denix.org>
On 17/04/25 23:58, Denys Dmytriyenko wrote:
> On Thu, Apr 17, 2025 at 09:05:14AM +0530, Chirag Shilwant wrote:
>> * The GP variant of SK-AM62A-LP is no longer tested.
> * Is it still being built?
>
> * Also, what about other BSPs, e.g. 6.1?
The GP part was built during the device bring-up (~ 2years back)
Apparently GP samples are limited to TI internal. Hence, the logic to
deploy tiboot3 for it was added in meta-ti-bsp at that time to support
internal development.
Post device APL, all TI internal development is moved to HS-FS part.
(Ideally, this logic of deploying tiboot3 for GP should have been
removed at that time)
From customer / 3rd party SOM pov, all receive HS-FS part by default
from TI.
So, they shouldn't be affected if meta-ti-bsp no longer deploys
|tiboot3-am62ax-gp-evm.bin|
>
> * What about derivative or customer platforms, besides SK-AM62A-LP? I.e. you
> are modifying the entire am62axx SoC family, which is supposed to be shared
> by multiple platforms in the AM62A SoC family.
In meta-ti-bsp, am62axx-evm (which represents SK-AM62A-LP) is the only
machine which utilizes AM62A SoC.
& for customer platforms...as mentioned above, ideally they shouldn't be
affected
as GP parts weren't shipped to them
For reference, we can checkout prebuilt-images folder of phyCORE-AM62A [0]
[0] :
https://download.phytec.de/Software/Linux/BSP-Yocto-AM62Ax/BSP-Yocto-Ampliphy-AM62Ax-PD24.1.2/images/ampliphy/phyboard-lyra-am62axx-2/
--
Chirag
>
>
>> Hence, don't include it under IMAGE_BOOT_FILES to ensure
>> tiboot3-am62ax-gp-evm.bin is not packaged inside /boot
>> partition of wic image
>>
>> Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
>> ---
>> meta-ti-bsp/conf/machine/include/am62axx.inc | 3 ---
>> 1 file changed, 3 deletions(-)
>>
>> diff --git a/meta-ti-bsp/conf/machine/include/am62axx.inc b/meta-ti-bsp/conf/machine/include/am62axx.inc
>> index 98cea203..e5f827a9 100644
>> --- a/meta-ti-bsp/conf/machine/include/am62axx.inc
>> +++ b/meta-ti-bsp/conf/machine/include/am62axx.inc
>> @@ -10,9 +10,6 @@ TFA_K3_SYSTEM_SUSPEND = "1"
>> # Default tiboot3.bin on AM62A is for HS-FS
>> IMAGE_BOOT_FILES += "tiboot3-am62ax-hs-fs-evm.bin"
>>
>> -# Since default tiboot3.bin on AM62A is for HS-FS, add a version for GP
>> -IMAGE_BOOT_FILES += "tiboot3-am62ax-gp-evm.bin"
>> -
>> # Since default tiboot3.bin on AM62A is for HS-FS, add a version for HS-SE
>> IMAGE_BOOT_FILES += "tiboot3-am62ax-hs-evm.bin"
>>
>> --
>> 2.34.1
next prev parent reply other threads:[~2025-04-21 6:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 3:35 [meta-ti][master/scarthgap][PATCH] conf: machine: am62axx: Exclude tiboot3.bin for GP Chirag Shilwant
2025-04-17 18:28 ` Denys Dmytriyenko
2025-04-21 6:37 ` Chirag Shilwant [this message]
2025-04-22 21:05 ` Denys Dmytriyenko
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=0feaf15d-e3ec-4f10-b651-db4225a40437@ti.com \
--to=c-shilwant@ti.com \
--cc=denis@denix.org \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@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.