Hi All,
The next release of the Firmware-A bundle of projects tagged v2.15 has an
expected code freeze date of 15/05/2026.
Refer to the release cadence section from TF-A documentation
(https://trustedfirmware-a.readthedocs.io/en/latest/about/release-informatio…).
Closing out the release takes around 6-10 working days after the code freeze.
v2.15 release preparation tasks are on-going and well progressed.
We want to ensure that planned feature patches for the release are submitted in
good time for the review process to conclude.
As a kind reminder and a matter of sharing CI resources, please launch CI
jobs with care e.g.:
*
For simple platform, docs changes, or one liners, use Allow-CI+1 label (no
need for a full Allow-CI+2 run).
*
For large patch stacks use Allow-CI+2 at top of the patch stack (and if
required few individual Allow+CI+1 labels in the middle of the patch stack).
*
Carefully analyze results and fix the change if required, before launching new
jobs on the same change.
*
If after issuing a Allow-CI+1 or Allow-CI+2 label a Build start notice is not
added as a gerrit comment on the patch right away please be patient as under
heavy load CI jobs can be queued and in extreme conditions it can be over an
hour before the Build start notice is issued. Issuing another Allow-CI+1 or
Allow-CI+2 label will just result in an additional job being queued.
Thanks & Regards,
Harrison on behalf of the TF-A team
This event has been canceled with a note:
"Hi, Cancelling as no topic for this week. Regards, Olivier. "
TF-A Tech Forum
Thursday Oct 15, 2026 ⋅ 5pm – 6pm
Central European Time - Paris
Location
https://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34…https://www.google.com/url?q=https%3A%2F%2Flinaro-org.zoom.us%2Fj%2F9355786…
Trusted Firmware is inviting you to a scheduled Zoom meeting.
Topic: TF-A Tech Forum
Time: May 15, 2025 02:00 PM London
Every 2 weeks on Thu, 78 occurrence(s)
Please download and import the following iCalendar (.ics) files to your
calendar system.
Weekly:
https://linaro-org.zoom.us/meeting/tJcocu6gqDgjEtOkyBhSQauR1sUyFwIcNKLa/ics…
Join Zoom Meeting
https://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34…
Meeting ID: 935 5786 3987
Passcode: 939141
---
One tap mobile
+12532158782,,93557863987# US (Tacoma)
+13017158592,,93557863987# US (Washington DC)
---
Dial by your location
• +1 253 215 8782 US (Tacoma)
• +1 301 715 8592 US (Washington DC)
• +1 305 224 1968 US
• +1 309 205 3325 US
• +1 312 626 6799 US (Chicago)
• +1 346 248 7799 US (Houston)
• +1 360 209 5623 US
• +1 386 347 5053 US
• +1 507 473 4847 US
• +1 564 217 2000 US
• +1 646 558 8656 US (New York)
• +1 646 931 3860 US
• +1 669 444 9171 US
• +1 669 900 9128 US (San Jose)
• +1 689 278 1000 US
• +1 719 359 4580 US
• +1 253 205 0468 US
• 833 548 0276 US Toll-free
• 833 548 0282 US Toll-free
• 833 928 4608 US Toll-free
• 833 928 4609 US Toll-free
• 833 928 4610 US Toll-free
• 877 853 5247 US Toll-free
• 888 788 0099 US Toll-free
Meeting ID: 935 5786 3987
Find your local number: https://linaro-org.zoom.us/u/adoz9mILli
Guests
d82620130(a)gmail.com
namyoon(a)google.com
shaikadnanafrid(a)gmail.com
tf-a(a)lists.trustedfirmware.org
~~//~~
Sent by Google Calendar: https://calendar.google.com/calendar/
You are receiving this email because you are an attendee on the event.
Forwarding this invitation could allow any recipient to send a response to
the organizer, be added to the guest list, invite others regardless of
their own invitation status, or modify your RSVP.
Learn more https://support.google.com/calendar/answer/37135#forwarding
Hi,
Please find the latest report on new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan.
1 new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan.
2 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent build analyzed by Coverity Scan.
New defect(s) Reported-by: Coverity Scan
Showing 1 of 1 defect(s)
** CID 506674: Memory - corruptions (OVERRUN)
_____________________________________________________________________________________________
*** CID 506674: Memory - corruptions (OVERRUN)
/plat/rpi/common/rpi_tpm.c: 152 in rpi_bl1_tpm_validate()
146 { .alg_id = EVLOG_TPM_ALG_SHA384 },
147 { .alg_id = EVLOG_TPM_ALG_SHA512 },
148 { .alg_id = TPM_ALG_NULL },
149 };
150 int rc;
151
>>> CID 506674: Memory - corruptions (OVERRUN)
>>> Overrunning array "alg_query" of 4 4-byte elements by passing it to a function which accesses it at element index 63 (byte offset 255).
152 rc = tpm_getcap_query_algs(&tpm_chip_data, alg_query);
153 if (rc < 0) {
154 ERROR("Failed to query TPM algs (%d).\n", rc);
155 panic();
156 }
157
________________________________________________________________________________________________________
To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/arm-software-arm-trusted-firmware?tab=ov…
This event has been canceled with a note:
"Hi, Cancelling as no topic. Regards, Olivier. "
TF-A Tech Forum
Thursday Oct 1, 2026 ⋅ 5pm – 6pm
Central European Time - Paris
Location
https://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34…https://www.google.com/url?q=https%3A%2F%2Flinaro-org.zoom.us%2Fj%2F9355786…
Trusted Firmware is inviting you to a scheduled Zoom meeting.
Topic: TF-A Tech Forum
Time: May 15, 2025 02:00 PM London
Every 2 weeks on Thu, 78 occurrence(s)
Please download and import the following iCalendar (.ics) files to your
calendar system.
Weekly:
https://linaro-org.zoom.us/meeting/tJcocu6gqDgjEtOkyBhSQauR1sUyFwIcNKLa/ics…
Join Zoom Meeting
https://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34…
Meeting ID: 935 5786 3987
Passcode: 939141
---
One tap mobile
+12532158782,,93557863987# US (Tacoma)
+13017158592,,93557863987# US (Washington DC)
---
Dial by your location
• +1 253 215 8782 US (Tacoma)
• +1 301 715 8592 US (Washington DC)
• +1 305 224 1968 US
• +1 309 205 3325 US
• +1 312 626 6799 US (Chicago)
• +1 346 248 7799 US (Houston)
• +1 360 209 5623 US
• +1 386 347 5053 US
• +1 507 473 4847 US
• +1 564 217 2000 US
• +1 646 558 8656 US (New York)
• +1 646 931 3860 US
• +1 669 444 9171 US
• +1 669 900 9128 US (San Jose)
• +1 689 278 1000 US
• +1 719 359 4580 US
• +1 253 205 0468 US
• 833 548 0276 US Toll-free
• 833 548 0282 US Toll-free
• 833 928 4608 US Toll-free
• 833 928 4609 US Toll-free
• 833 928 4610 US Toll-free
• 877 853 5247 US Toll-free
• 888 788 0099 US Toll-free
Meeting ID: 935 5786 3987
Find your local number: https://linaro-org.zoom.us/u/adoz9mILli
Guests
d82620130(a)gmail.com
namyoon(a)google.com
shaikadnanafrid(a)gmail.com
tf-a(a)lists.trustedfirmware.org
~~//~~
Sent by Google Calendar: https://calendar.google.com/calendar/
You are receiving this email because you are an attendee on the event.
Forwarding this invitation could allow any recipient to send a response to
the organizer, be added to the guest list, invite others regardless of
their own invitation status, or modify your RSVP.
Learn more https://support.google.com/calendar/answer/37135#forwarding
Hello,
I was planning to upstream the code to support Trusted Board Boot on
STM32MP2.
But I came to an issue with the OID we have chosen.
Our first implementation was done back in 2023, and based on TF-A v2.8.
We needed an OID for the DDR PHY firmware, almost the same way it was
done by NXP with this patch:
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/6155
So I ended up doing this patch:
https://github.com/STMicroelectronics/arm-trusted-firmware/commit/c7f0e2eb6…
But now that I want to upstream that code, I see that this OID has been
chosen between TF-A v2.8 and TF-A v2.9 for
ETHOSN_NPU_FW_CONTENT_CERT_PK_OID.
As I think OIDs should be unique, I then cannot re-use the same one.
But then I will have some issues with customers that already made
products with with our software based either on either v2.8 or v2.10.
If they need to update their version to a newer one, they will need to
regenerate the certificates for this DDR firmware if the software is
updated.
For the update procedure, only the FIP may be updated, so if the
cert_create tool uses a new OID, it won't match the one used in BL2 DT.
A possible solution would be this one:
#if STM32MP_LEGACY_DDR_FW_OID
#define DDR_FW_HASH_OID "1.3.6.1.4.1.4128.2300.1"
#else
#define DDR_FW_HASH_OID "1.3.6.1.4.1.4128.2400.1"
#endif
But we'd still have the same OID as ETHOSN_NPU_FW_CONTENT_CERT_PK_OID if
STM32MP_LEGACY_DDR_FW_OID is selected.
Another one is just to keep the new value and set the patch as a
breaking change, and then inform our customers through the release notes
that they should take care of this new version.
A third one would be to change ETHOSN_NPU_FW_CONTENT_CERT_PK_OID. But
then you'll face the same issues about such a change, and the
dependencies with other tools or pieces of software that would need update.
In your opinion what would be the better solution?
Another question I have is about the OID entreprise number? Should I
keep Arm one (4128), or use the STMicroelectronics' (7616)? But that
would differ from what NXP has done.
Thanks,
Yann