- TF-A - lists.trustedfirmware.org

Trusted Firmware-A LTS v2.14.3 Release Announcement

by svc_openci_enginfra＠arm.com

5 hours, 20 minutes

1
0
0 0

Re: Guidance on direct Linux boot from TF-A (bypassing U-Boot) on ARM64

by Olivier Deprez

Hi, I would suggest looking into the platform ports: https://trustedfirmware-a.readthedocs.io/en/latest/plat/arm/fvp/fvp-specifi… https://trustedfirmware-a.readthedocs.io/en/latest/plat/rpi3.html#build-ins… RPI3_DIRECT_LINUX_BOOT https://trustedfirmware-a.readthedocs.io/en/latest/plat/qemu.html#qemu-virt… ARM_LINUX_KERNEL_AS_BL33 Regards, Olivier. ________________________________ From: Joita Mitra <joita.m(a)delopt.co.in> Sent: 11 June 2026 09:19 To: tf-a-owner(a)lists.trustedfirmware.org <tf-a-owner(a)lists.trustedfirmware.org> Subject: Guidance on direct Linux boot from TF-A (bypassing U-Boot) on ARM64 Hi, I am working on an RZ/G2L based platform and exploring the possibility of booting Linux directly from TF-A without using U-Boot as BL33. Current boot flow: BL2 -> BL31 -> U-Boot (BL33) -> Linux Target boot flow: BL2 -> BL31 -> Linux I have been studying the TF-A image loading framework, including: * desc_image_load.h * bl2_image_load_v2.c * bl2_plat_mem_params_desc.c * bl31_main.c * bl31_prepare_next_image_entry() My understanding is that BL2 loads images according to the image descriptors and passes entry point information to BL31 through the BL33 descriptor. I modified the BL33 descriptor to point to the Linux kernel entry address instead of U-Boot and attempted to transfer execution directly to Linux from BL31. However, Linux does not start successfully, which suggests that additional preparation normally performed by U-Boot may be missing. I would appreciate guidance on the following: 1. Is using the BL33 descriptor to describe the Linux kernel the correct architectural approach when bypassing U-Boot? 2. How should the Linux kernel Image and DTB be loaded from BL2? * Should Linux be treated as BL33? * Should the DTB be loaded as a separate image descriptor? * Is there an existing TF-A mechanism intended for this use case? 3. Which TF-A components are typically modified to support direct Linux boot? * BL2 image loading descriptors? * BL31 handoff logic? * Platform-specific image loading code? 4. Are there any reference implementations or platforms in TF-A that directly boot Linux without U-Boot? 5. Are there any ARM64 Linux boot protocol requirements that TF-A must satisfy before transferring control to Linux? Any guidance or examples would be greatly appreciated. Thank you. [cid:19da2837-2e52-4337-8b03-1cc393171495]<http://www.delopt.co.in/> Joita Mitra Embedded Software Engineer [cid:7d7fa5b9-a852-48ac-a797-7ed0723558b3] +91-7985313796 Fortune Serene, 3rd Floor, Plot No: 89/B, 90/A, West Avenue 9, Electronic City Phase 1,Bangalore 560100

1 day, 19 hours

1
0
0 0

Trusted Firmware-A LTS v2.14.3 Release Announcement

by svc_openci_enginfra＠arm.com

4 days, 8 hours

1
0
0 0

TF-A Tech Forum - Fuzzing TF-RMM Jun 11th 2026 4.00pm UK

by Olivier Deprez

Hi, On Jun 11th 2026 4.00pm UK, Rustam Ismayilov will present the topic of TF-RMM fuzzing with the following agenda: Fuzzed Interfaces fake_host AFL++ seed generation statefull fuzzing Results and performance Limitations and planned improvements Regards, Olivier. TF-A Tech Forum Thursday Jun 11, 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 ForumTime: 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… Zoom Meetinghttps://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34.1Meeting ID: 935 5786 3987Passcode: 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-freeMeeting ID: 935 5786 3987Find 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

4 days, 13 hours

1
0
0 0

Proposal to unify tf.org vulnerability referencing in NVD

by Sandrine Bailleux

Hi everyone, I am sending this email to all tf.org project mailing lists to ensure all maintainers are aware and on board regarding this matter. If you have any concerns or questions, please reply on tf.org Discord #general channel, where I'll create a thread, as I think it will be much easier than dealing with cross-mailing lists emails. Background When a security vulnerability is discovered in one of the trustedfirmware.org projects, it is common to request a "Common Vulnerabilities and Exposures" (CVE) number. This number uniquely references the issue, which can then be searched in the vulnerability databases. One of these databases is NIST's "National Vulnerability Database" (NVD): https://nvd.nist.gov<https://nvd.nist.gov/vuln/detail/CVE-2023-51712> Entering a specific CVE number in NVD search engine will allow you to easily find the details of a specific issue, for example: https://nvd.nist.gov/vuln/detail/CVE-2023-51712 However, sometimes one is not looking for a specific CVE number but rather wants to list all known vulnerabilities affecting a particular project. For this, one can use the Common Platform Enumerations (CPE) search engine: https://nvd.nist.gov/products/cpe/search CPE is a structured naming scheme that includes information like the vendor name, the project name, the version / tag, and so on. See https://nvd.nist.gov/products/cpe for more details. So for example, https://nvd.nist.gov/vuln/detail/CVE-2023-51712 referenced above has the following CPE: cpe:2.3:o:arm:trusted_firmware-m:*:*:*:*:*:*:*:* This basically means * CPE version 2.3 is in use * 'o is the type of project, in this case it stands for Operating Systems (which is probably the closest match for low-level code like TF-M) * 'arm' is the vendor (that is wrong, see below) * 'trusted_firmware-m' is the project name, Problem statement It appears that CPEs used in NVD to reference vulnerabilities in tf.org projects differ a lot across projects. For some projects, there's even multiple of them. Sometimes the vendor is "arm", sometimes it's "linaro", or something else. Some of the TF-A and MbedTLS maintainers have initiated discussions with NVD to get this simplified and unified, but it would make sense to align other tf.org projects as well. Proposal CPE naming rules are that the vendor name should the parent organization of the project. Thus the proposal would be for all tf.org projects to use "trustedfirmware" as the vendor name in their CPE. For example: cpe:2.3:o:trustedfirmware:trusted_firmware-m:*:*:*:*:*:*:*:* cpe:2.3:a:trustedfirmware:mbed_tls:*:*:*:*:*:*:*:* We're only proposing to change the vendor name here ; each project is then free to choose how they want the project name or the type of software project they want to encode there. Thanks for reading, Best regards, Sandrine Afsa

1 week

1
0
0 0

EL3 SPMC shmem datastore sizing for FFA_MEM_RETRIEVE_REQ snapshot

by Daniel Boulby

Hi all, I am sending this note to get feedback from platform maintainers on an EL3 SPMC change in my current series (https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/50778/). The patch updates spmc_ffa_mem_retrieve_req() to take a snapshot of the caller's FFA_MEM_RETRIEVE_REQ descriptor into the EL3 SPMC shmem datastore before validation and response handling. The intent is to avoid repeatedly reading mutable fields from the caller-owned TX buffer while the request is being processed. In other words, once the request enters EL3 SPMC, we operate on a stable local copy rather than on memory that remains under the caller's control. The EL3 SPMC datastore is already used to cache shared memory transaction descriptors. With this change, it is also used to hold a temporary copy of the retrieve request. That means datastore sizing becomes more important, since a valid larger retrieve request may now fail if the backing datastore is too small. The datastore sizes are defined in platform_def.h (https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/… for the fvp platform) and while looking through the existing platform definitions, I noticed that datastore sizes vary quite a lot. For example, some platforms provide a relatively large backing store, while others define much smaller regions. In particular, rdn2 currently defines only a 1024-byte datastore. My concern is that for such platforms, larger memory-share / retrieve flows could fail simply because the datastore is too small to hold the request snapshot. Before I proceed further, I wanted to ask platform maintainers: 1. Is there any platform-specific reason for these reduced datastore sizes? 2. If not, would maintainers be happy for these datastore sizes to be increased so they can accommodate larger valid transactions? In short, I want to confirm whether the smaller datastore definitions are deliberate platform constraints, or whether they should be treated as undersized defaults that now need revisiting. Feedback from maintainers would be very helpful before I post the next revision. Kind Regards, Daniel Boulby

1 week, 1 day

1
0
0 0

CI infrastructure scheduled maintenance: 4th June Sep 2026

by Saheer Babu

Hi all, We will be upgrading Cloudbees CI and clusters hosting review.trustedfirmware.org and ci.trustedfirmware.org on Wednesday, 3rd June 2025 at 16:00 GMT+1. During this maintenance window, both services will be unavailable for approximately 8 hours. A follow-up email will be sent once the services are fully restored. Best regards, Saheer [LOGO SMALL] Saheer Babu Principal Software Engineer CESW – Engineering Infrastructure

1 week, 2 days

1
2
0 0

Firmware-A v2.12 release code freeze notification

by Govindraj Raja

Hi All, The next release of the Firmware-A bundle of projects tagged v2.12 has an expected code freeze date of Nov, 8th 2024. 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.12 release preparation tasks start from now. 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 recommendation 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, Govindraj R

2 weeks

2
4
0 0

TF-A Tech Forum May 28th - BL31 Live Firmware Activation

by Olivier Deprez

Hi, On May 28th at 4.00pm UK, in the TF-A Tech Forum, Manish Badarkhe and John Powell from Arm will present the topic of BL31 Live Firmware Activation with the following agenda: -Quick recap of LFA SMC implementation -BL31 live activation implementation -Assumptions and scope for live activating BL31 -Test cases added for BL31 live activation Regards, Olivier. TF-A Tech Forum Thursday May 28, 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 ForumTime: 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… Zoom Meetinghttps://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34.1Meeting ID: 935 5786 3987Passcode: 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-freeMeeting ID: 935 5786 3987Find your local number: https://linaro-org.zoom.us/u/adoz9mILli Guests qwandor(a)google.com praan(a)google.com jeremimiller(a)google.com jagdish.gediya(a)linaro.org khilman(a)baylibre.com tf-a(a)lists.trustedfirmware.org

2 weeks, 2 days

2
1
0 0

Changelog for v2.15 Release

by Harrison Mutai

Hello Everyone, Ahead of the TF-A v2.15 release, please review the autogenerated changelog for your platform. It’s built from the commit messages of all patches merged since v2.15. If you spot anything that needs a quick manual tweak, just let us know. Patch: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/51064 Rendered Version: https://ci-artifacts.trustedfirmware.org/static-files/kCIohqhXYMnQJYSWz3aUf… -- Thanks, Harrison

3 weeks, 1 day

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

TF-A