Re: [meta-ti][master][PATCH] RFC: meta-beagle: Fix TF-A machine name for badge

On 3/19/26 1:53 PM, Denys Dmytriyenko wrote:
> On Thu, Mar 19, 2026 at 12:54:02PM -0500, Mendez, Judith via lists.yoctoproject.org wrote:
>> BeagleBadge board has been renamed to am62l3-badge
>> in the new TFA ti-tfa-2.14.y branch [0], so update
>> recipe TFA_BOARD accordingly.
>>
>> [0] https://github.com/TexasInstruments/arm-trusted-firmware/commit/d203b8453905178252094416448de009931087e0
>> Signed-off-by: Judith Mendez <[email protected]>
>> ---
>> Due to build errors with arago-master-config, this patch
>> has not been built tested, thus sending as RFC.
>> ---
>>   meta-beagle/conf/machine/beaglebadge-ti.conf | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta-beagle/conf/machine/beaglebadge-ti.conf b/meta-beagle/conf/machine/beaglebadge-ti.conf
>> index d62730ed..78525030 100644
>> --- a/meta-beagle/conf/machine/beaglebadge-ti.conf
>> +++ b/meta-beagle/conf/machine/beaglebadge-ti.conf
>> @@ -18,4 +18,4 @@ KERNEL_DEVICETREE = ""
>>   
>>   UBOOT_MACHINE = "am62lx_badge_defconfig"
>>   
>> -TFA_BOARD = "am62l-badge"
>> +TFA_BOARD = "am62l3-badge"
> 
> This looks reasonable, on the surface at least.
> 
> Andrew, Praneeth,
> 
> How stable is the API around TFA?
> 
> Do we want to keep multiple versions of TFA and select the corresponding one
> based on which BSP is in use (6.6, 6.12, 6.18)?
> 

The API "should" be stable, the only pain here is that until
this is upstream our names might change, hopefully that isn't a
long-term issue.

Since we are using versioned TFA for each BSP (scarthgap (6.12) will use
a different TFA branch than 6.18 (ti-tfa-2.14.y)), it might have made sense
to have made versioned TFA recipes. But I don't see a huge need to go back
and add that now.

Andrew

> I realize it's not specific to the kernel version, but to other low-level boot
> pieces, which all get updated at the same time, even though U-boot and kernel
> may be old...
>