- TF-A - lists.trustedfirmware.org

Trusted Firmware-A LTS v2.14.11 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.11 is now available. This release contains the following patches: dfb36dc0a fix(fvp): absorb BUILD_CPUS_WITH_NO_FVP_MODEL and ENABLE_ERRATA_ALL cores [1] eabd2381b refactor(cpus): rename Canyon to C2-Ultra [2] 84a6a905e fix(cpus): remove C1-NANO implementation-specific register 'IMP' prefixes [3] 130e4a8f2 fix(cpus): add C1-Nano errata 3806270 and 4394104 [4] 19d462795 fix(cpus): remove C1-ULTRA implementation-specific register 'IMP' prefixes [5] ffa77d4e5 fix(cpus): add workarounds for C1-Ultra errata [6] f9cfd5d5a fix(cpus): remove C1-PREMIUM implementation-specific register 'IMP' prefixes [7] b7f280b9f fix(cpus): add workarounds C1-Premium errata [8] 7843e6af3 fix(cpus): remove C1-PRO implementation-specific register 'IMP' prefixes [9] b64ad163d fix(cpus): add workarounds for C1-Pro errata 3679375 and 3806276 [10] [1] https://review.trustedfirmware.org/q/I15d5ac54504c50ad9ed076cfe88dc79e5c6a1… [2] https://review.trustedfirmware.org/q/I8f7202ed4d81f2912fe58f1dbb78906edeae9… [3] https://review.trustedfirmware.org/q/I7d23c94c31ff90b758115239bdf1033bfc78d… [4] https://review.trustedfirmware.org/q/Ic18e91288f09d3d2290f051d16f67e8d995af… [5] https://review.trustedfirmware.org/q/Idd36178d1f618e19e9168f7923c7ecb288d00… [6] https://review.trustedfirmware.org/q/I8d13d3466ca4aaad71e741f29ac80faca9955… [7] https://review.trustedfirmware.org/q/I64a871a2e78e435b4f862c4c79cebb3bf37d8… [8] https://review.trustedfirmware.org/q/I6a37d396d86a71741cfca985fa311c47975b4… [9] https://review.trustedfirmware.org/q/Id15995d4947aee3256256c8b0cd93c9dabe86… [10] https://review.trustedfirmware.org/q/Ic19797fa21c5c172e2dca462c7d4f5c985678… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.11/change-log.html Thanks, TF-A LTS team

4 days, 18 hours

1
0
0 0

Firmware-A v2.15 release code freeze notification

by Harrison Mutai

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

5 days, 11 hours

2
1
0 0

Canceled event with note: TF-A Tech Forum @ Thu Oct 15, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

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

5 days, 12 hours

1
0
0 0

New Defects reported by Coverity Scan for ARM-software/arm-trusted-firmware

by scan-admin＠coverity.com

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…

6 days, 14 hours

1
0
0 0

Trusted Firmware-A LTS v2.12.16 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.12.16 is now available. This release contains the following patches: b0c15fa1e build(deps-dev): bump js-yaml from 4.1.1 to 4.3.2 [1] f99d1b51a fix(tools): change data type to size_t for doimage [2] 3d7508d68 fix(imx8m): don't reconfigure default region0 [3] 8ea8c7d7e fix(qti): do not map secure regions [4] 6e901e8e9 fix(qti): disallow secure IO accesses from secure world callers [5] 3cbfcb11c fix(qti): pull in access-control backend for mem_assign [6] 963815cd5 fix(qti): fix build without coreboot [7] f8594cfac fix(qti): harden mem_assign parameter handling [8] a821c6b85 feat(cpus): add links to each core's TRM and SDEN [9] 71efef396 refactor(cpus): factor out Neoverse V3AE from the base Neoverse V3 file [10] 1e81817e4 fix(mediatek): enable missing Cortex-A78 errata for MT8188 [11] 702924fd8 fix(mediatek): enable missing Cortex-A78 errata for MT8195 [12] abcc76089 docs: add LTS Dependabot release step [13] 34f313938 fix(el3-spmc): harden composite MRD validation [14] 396760c1e fix(rk3568): implement CPU core suspend/resume power domain hooks [15] a347cce11 fix(xilinx): allow secure access to IPI channels [16] 07f688ca8 fix(fdt-wrappers): reject negative cell counts [17] [1] https://review.trustedfirmware.org/q/I560ad0cfae1a00798fda98b22643895eab025… [2] https://review.trustedfirmware.org/q/I658521c1eec1c79933ba8082ba507df04d174… [3] https://review.trustedfirmware.org/q/I0a0f9b5ad0017f38d767f583d7765a2f79861… [4] https://review.trustedfirmware.org/q/I070bb347039e467c1407cf6ceb832e43e7512… [5] https://review.trustedfirmware.org/q/I6dea64e110184f73868ac188fca2d755999d5… [6] https://review.trustedfirmware.org/q/Ia84fd78b62ea5e7e7e7b9fa85d6baf1ab04b5… [7] https://review.trustedfirmware.org/q/I3c00aace547385af6b49632e3acfd9a977306… [8] https://review.trustedfirmware.org/q/Ie9e5480891a82ba98919c8c7dbdd27819e246… [9] https://review.trustedfirmware.org/q/I6fe089876aa2d764a67733041751202e2bd3c… [10] https://review.trustedfirmware.org/q/Ic658273bd4502c28281a7963a8c862c26da64… [11] https://review.trustedfirmware.org/q/I0f7b451220fbe832cd6735fde6f12fd6c095e… [12] https://review.trustedfirmware.org/q/Id2574c33a345c1c69f35b065ef210a32bd724… [13] https://review.trustedfirmware.org/q/I22cfbf65449e4b32d5ba2a39bbac89e0fd2ab… [14] https://review.trustedfirmware.org/q/I207d2fe57766bee83a7c4c8b51f259b08934b… [15] https://review.trustedfirmware.org/q/Icc20759ef18900a0702bc2345ad768a2dd63b… [16] https://review.trustedfirmware.org/q/I69681b689d57446c141c67eb143430d32f05c… [17] https://review.trustedfirmware.org/q/I67bf1e5773211df80d3b8ba71157a87d70ce2… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.12.16/change-log.html Thanks, TF-A LTS team

2 weeks, 4 days

1
0
0 0

Trusted Firmware-A LTS v2.8.48 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.8.48 is now available. This release contains the following patches: 67527c851 fix(xilinx): allow secure access to IPI channels [1] e605d5651 fix(mediatek): enable missing Cortex-A78 errata for MT8188 [2] adb1202f8 fix(mediatek): enable missing Cortex-A78 errata for MT8195 [3] 3cf7fb63e fix(cpus): remove stray conflict marker in cortex_a77.h [4] 53f4a11dc build(deps): bump certifi from 2023.7.22 to 2024.7.4 [5] 1193208dc build(deps): bump the pip group across 1 directory with 7 updates [6] 93f99ffb9 build(deps): bump setuptools in the pip group across 1 directory [7] ab964f0ac build(dev-deps): bump applicable documentation dependencies [8] bd6f66a57 chore(dev-deps): bump the pip group across 2 directories with 1 update [9] 315c94321 build(deps): bump the pip group across 1 directory with 2 updates [10] 61f9f12e4 build(dev-deps): bump the dev-deps group with 5 updates [11] 5adc272cf chore(dev-deps): bump the dev-deps group with 3 updates [12] b034ff051 build(deps): bump the npm_and_yarn group with 5 updates [13] d9d673a55 build(deps): bump commitizen [14] [1] https://review.trustedfirmware.org/q/I69681b689d57446c141c67eb143430d32f05c… [2] https://review.trustedfirmware.org/q/I0f7b451220fbe832cd6735fde6f12fd6c095e… [3] https://review.trustedfirmware.org/q/Id2574c33a345c1c69f35b065ef210a32bd724… [4] https://review.trustedfirmware.org/q/If4f5e65dee5fb642e5eda739c366b371bffb8… [5] https://review.trustedfirmware.org/q/I8570692c4506cdca19227d7b11a045faa02ba… [6] https://review.trustedfirmware.org/q/I623707c3eb76598c4bfb3957f090a846c765b… [7] https://review.trustedfirmware.org/q/Ibd4e4730bfc5cce8d85ec55021983d6f748ff… [8] https://review.trustedfirmware.org/q/Iae14b792174786dfb57fa0fb08de5af801d1d… [9] https://review.trustedfirmware.org/q/Ia260450e46a6c4bd3f9fcaf3f99bbbfb04877… [10] https://review.trustedfirmware.org/q/I4092fe42e7fe28b19270af03d5cd7cd9fa5d0… [11] https://review.trustedfirmware.org/q/Ie6825142ea24b432a33ac5869c94e5233c21d… [12] https://review.trustedfirmware.org/q/Iea28f4da58a5e27abb5a9d7ee4be4e9ae67a8… [13] https://review.trustedfirmware.org/q/I3203e9eb23315f2442e3715549f7541207fe4… [14] https://review.trustedfirmware.org/q/I2c20f293ca83bec50c569ce73d01e5edd2d05… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.8.48/change-log.html Thanks, TF-A LTS team

2 weeks, 4 days

1
0
0 0

Trusted Firmware-A LTS v2.14.10 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.10 is now available. This release contains the following patches: bb8f5625e build(dev-deps): bump js-yaml from 4.1.0 to 4.3.2 [1] 45ae4079b chore(dev-deps): bump commitizen [2] 6e9711e86 build(dev-deps): bump pyright [3] d343569b4 build: move global defines into a config header [4] c7a233761 build(mbedtls): build with CMake [5] 9b58aed42 build(deps): bump the npm_and_yarn group across 1 directory with 5 updates [6] [1] https://review.trustedfirmware.org/q/I15b6b1cdf142b584ee1527deebe8e8a1b559a… [2] https://review.trustedfirmware.org/q/Icdba904e6fdf444fa8661bb61f1b4c241213a… [3] https://review.trustedfirmware.org/q/I4c4529f562d1d045764c0aa47ad75b40cd3ee… [4] https://review.trustedfirmware.org/q/I12455263c82da38e66d4fdc7b19f6cee148a1… [5] https://review.trustedfirmware.org/q/I47de5b1773a67b7615ccfd9cf6add4e0c8923… [6] https://review.trustedfirmware.org/q/I3203e9eb23315f2442e3715549f7541207fe4… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.10/change-log.html Thanks, TF-A LTS team

2 weeks, 4 days

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Oct 1, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

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

2 weeks, 5 days

1
0
0 0

Questions about OID

by Yann Gautier

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

2 weeks, 6 days

2
2
0 0

New Defects reported by Coverity Scan for ARM-software/arm-trusted-firmware

by scan-admin＠coverity.com

Hi, Please find the latest report on new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. 3 new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 3 of 3 defect(s) ** CID 506279: Code maintainability issues (UNUSED_VALUE) /plat/altera/soc/common/drivers/mailbox/mcsr/socfpga_mcsr_mailbox.c: 360 in mcsr_mailbox_response_handler() _____________________________________________________________________________________________ *** CID 506279: Code maintainability issues (UNUSED_VALUE) /plat/altera/soc/common/drivers/mailbox/mcsr/socfpga_mcsr_mailbox.c: 360 in mcsr_mailbox_response_handler() 354 355 uint32_t response_header = response_buffer[get_index].msg_header; 356 uint8_t trans_id; 357 358 di = mcsr_mailbox_get_free_resp_desc(); 359 if (di == -1) { >>> CID 506279: Code maintainability issues (UNUSED_VALUE) >>> Assigning value "-1" to "status" here, but that stored value is overwritten before it can be used. 360 status = MBOX_RET_ERROR; 361 break; 362 } 363 364 /* Populate the local response queue entry */ 365 mbox_svc.resp_queue[di].header = response_header; ** CID 506278: Uninitialized variables (UNINIT) /plat/altera/soc/common/socfpga_sip_svc.c: 277 in intel_fpga_config_start() _____________________________________________________________________________________________ *** CID 506278: Uninitialized variables (UNINIT) /plat/altera/soc/common/socfpga_sip_svc.c: 277 in intel_fpga_config_start() 271 if (status < 0) { 272 bridge_disable = false; 273 request_type = NO_REQUEST; 274 return INTEL_SIP_SMC_STATUS_ERROR; 275 } 276 >>> CID 506278: Uninitialized variables (UNINIT) >>> Using uninitialized value "response[0]". 277 max_blocks = response[0]; 278 bytes_per_block = response[1]; 279 280 for (int i = 0; i < FPGA_CONFIG_BUFFER_SIZE; i++) { 281 fpga_config_buffers[i].size = 0; 282 fpga_config_buffers[i].size_written = 0; ** CID 506277: Code maintainability issues (UNUSED_VALUE) /services/std_svc/firme/firme_attestation.c: 212 in firme_attest_pat_get() _____________________________________________________________________________________________ *** CID 506277: Code maintainability issues (UNUSED_VALUE) /services/std_svc/firme/firme_attestation.c: 212 in firme_attest_pat_get() 206 mmap_rc = mmap_remove_dynamic_region(shared_buf_addr, 207 shared_buf_size); 208 if (mmap_rc != 0U) { 209 if (mmap_rc != -ENOMEM) { 210 ERROR("%s(): mmap_remove_dynamic_region() failed unexpectedly rc=%d\n", 211 __func__, mmap_rc); >>> CID 506277: Code maintainability issues (UNUSED_VALUE) >>> Assigning value "-10" to "rc" here, but that stored value is overwritten before it can be used. 212 rc = FIRME_NO_MEMORY; 213 } 214 215 rc = FIRME_INVALID_PARAMETERS; 216 } 217 } ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/arm-software-arm-trusted-firmware?tab=ov…

2 weeks, 6 days

1
0
0 0

CI configuration submission guidance

by Harrison Mutai

Hi all, We’re going to trial a new approach for platform contributions that require both TF-A and CI changes. This is intended to address synchronisation issues that can arise when TF-A and corresponding CI patches are merged at the same time. In some cases, the CI configuration can take effect before other in-flight patches have had an opportunity to rebase onto the associated TF-A change, causing unrelated patches to fail CI. For the time being, we’re asking contributors to: * Submit the Coverity configuration and build configuration as separate CI patches. * Test both CI patches together with the corresponding TF-A change. * Submit the Coverity configuration alongside the TF-A change, but hold back the build configuration for one week. * After the one-week period, the maintainer should return to the CI change and submit the build configuration. The one-week delay is intended to give the TF-A change time to propagate through other in-flight patches before the new build configuration becomes active. We’ll trial this approach for now and review how well it works in practice. Thanks, Harrison

3 weeks

1
0
0 0

Re: [RFC] cert_create: only generate/save keys needed by requested certs

by Manish Badarkhe

Hi Vikrant, This makes sense to me. Today cert_create effectively treats the registered key set as global: even if only a subset of certificates is requested, it still walks the full key list for load/create/save, and -k can fail on filenames for keys that are not actually needed by the requested outputs. Your proposed approach seems like the right direction. At a high level, the tool should first derive the required key set from the certificates that were actually requested, then use that set consistently for validation, key load/create, and key save. That would make requesting only a subset of certificates work the way users would expect, without needing to provide or generate unrelated keys. One thing I would suggest is to make sure the filtering is applied consistently across all three places: * command-line validation * key load/create * key save If that is what your change does, then the approach looks good to me. Please upload it to Gerrit and it can go through the usual review process and CI validation. Thanks, Manish Badarkhe ________________________________ From: Vikrant Yadav <vikrantyadav4802(a)gmail.com> Sent: 29 September 2026 07:14 To: tf-a(a)lists.trustedfirmware.org <tf-a(a)lists.trustedfirmware.org> Cc: Sandrine Bailleux <Sandrine.Afsa(a)arm.com>; Manish Badarkhe <Manish.Badarkhe(a)arm.com> Subject: [RFC] cert_create: only generate/save keys needed by requested certs Hi all, I'd like to propose a small change to cert_create (tools/cert_create) and get your feedback before uploading to Gerrit. What it does today: When generating certificates, cert_create unconditionally generates all keys in the Chain of Trust (CoT), and with the -k option it requires filenames for every key - even when only a subset of certificates is requested. Why this is a problem: Keys that no requested certificate needs are still generated, and -k errors out on missing filenames for keys that are never used. Requesting a single certificate shouldn't require dealing with keys it doesn't depend on. Proposed fix: Add a "bool required" field to the key struct. For each requested certificate, mark as required the keys it depends on: - the certificate's own key - its issuer's signing key - keys referenced by its extensions The key generation and save loops then act only on keys marked required. Does this approach make sense? If so, I'll upload the change to Gerrit. Thanks, Vikrant

3 weeks

1
0
0 0

Trusted Firmware-A LTS v2.8.47 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.8.47 is now available. This release contains the following patches: 516f5634b fix(qti): do not map secure regions [1] 296470531 fix(qti): disallow secure IO accesses from secure world callers [2] 44e050ce9 fix(qti): pull in access-control backend for mem_assign [3] 92de580f1 fix(qti): fix build without coreboot [4] 13a9e032d fix(qti): harden mem_assign parameter handling [5] 4285ff854 refactor(cpus): align AE variant core names [6] 29c5966c2 feat(cpus): add links to each core's TRM and SDEN [7] f7092d05b docs: add LTS Dependabot release step [8] 2b1cc89ac refactor(cpus): factor out Neoverse V3AE from the base Neoverse V3 file [9] 439cb5243 fix(fdt-wrappers): reject negative cell counts [10] [1] https://review.trustedfirmware.org/q/I070bb347039e467c1407cf6ceb832e43e7512… [2] https://review.trustedfirmware.org/q/I6dea64e110184f73868ac188fca2d755999d5… [3] https://review.trustedfirmware.org/q/Ia84fd78b62ea5e7e7e7b9fa85d6baf1ab04b5… [4] https://review.trustedfirmware.org/q/I3c00aace547385af6b49632e3acfd9a977306… [5] https://review.trustedfirmware.org/q/Ie9e5480891a82ba98919c8c7dbdd27819e246… [6] https://review.trustedfirmware.org/q/I999ed43421d083af148c3e92cef9d8ca5c635… [7] https://review.trustedfirmware.org/q/I6fe089876aa2d764a67733041751202e2bd3c… [8] https://review.trustedfirmware.org/q/I22cfbf65449e4b32d5ba2a39bbac89e0fd2ab… [9] https://review.trustedfirmware.org/q/Ic658273bd4502c28281a7963a8c862c26da64… [10] https://review.trustedfirmware.org/q/I67bf1e5773211df80d3b8ba71157a87d70ce2… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.8.47/change-log.html Thanks, TF-A LTS team

3 weeks, 3 days

1
0
0 0

New Defects reported by Coverity Scan for ARM-software/arm-trusted-firmware

by scan-admin＠coverity.com

Hi, Please find the latest report on new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. 2 new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. 6 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 2 of 2 defect(s) ** CID 506263: Control flow issues (DEADCODE) /include/services/pfdi.h: 127 in pack_vendor_id() _____________________________________________________________________________________________ *** CID 506263: Control flow issues (DEADCODE) /include/services/pfdi.h: 127 in pack_vendor_id() 121 uint32_t major = (uint32_t)((cfg >> PFDI_MAJOR_SHIFT) & UINT64_C(0xFF)); 122 uint32_t minor = (uint32_t)((cfg >> PFDI_MINOR_SHIFT) & UINT64_C(0xFF)); 123 124 if (((cfg & PFDI_UPPER_RESERVED_MASK) != UINT64_C(0)) || 125 ((cfg & PFDI_RESERVED_MASK) != UINT64_C(0)) || 126 (vendor != PFDI_VENDOR_ARM)) { >>> CID 506263: Control flow issues (DEADCODE) >>> Execution cannot reach this statement: "*version = 0UL;". 127 *version = 0ull; /* On error: Must be zero */ 128 } else { 129 uint64_t v = 0ull; 130 131 v |= ((uint64_t)vendor << 24); 132 v |= ((uint64_t)impl << 16); ** CID 267379: (PARSE_ERROR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/rdv3/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/uniphier/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/rpi3/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/tc/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/qemu/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/n1sdp/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/stm32mp1-mp13-sdmmc-tbbr/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/stm32mp1-mp13-sdmmc-tbbr-dec/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/stingray/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/synquacer/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/rdn2/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/stm32mp1-sdmmc-tbbr/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/warp7/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/rdaspen/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/rd1ae/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () _____________________________________________________________________________________________ *** CID 267379: (PARSE_ERROR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/rdv3/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/uniphier/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/rpi3/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/tc/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/qemu/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/n1sdp/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/stm32mp1-mp13-sdmmc-tbbr/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/stm32mp1-mp13-sdmmc-tbbr-dec/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/stingray/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/synquacer/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/rdn2/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/stm32mp1-sdmmc-tbbr/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/warp7/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/rdaspen/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/build/rd1ae/debug/libmbedtls/CMakeFiles/CMakeTmp/CheckIncludeFile.c: 1 in () >>> CID 267379: (PARSE_ERROR) >>> cannot open source file "pthread.h" 1 #include <pthread.h> 2 3 #ifdef __CLASSIC_C__ 4 int main() 5 { 6 return 0; ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/arm-software-arm-trusted-firmware?tab=ov…

3 weeks, 3 days

1
0
0 0

Trusted Firmware-A LTS v2.10.36 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.10.36 is now available. This release contains the following patches: 8c8522931 fix(mediatek): enable missing Cortex-A78 errata for MT8195 [1] 80d954cfc fix(mediatek): enable missing Cortex-A78 errata for MT8188 [2] eae6e49a9 fix(qti): do not map secure regions [3] f884efa8c fix(qti): disallow secure IO accesses from secure world callers [4] 4aa762a74 fix(qti): pull in access-control backend for mem_assign [5] 5fd5f37ad fix(qti): fix build without coreboot [6] b8594bd37 fix(qti): harden mem_assign parameter handling [7] 36870eb72 fix(xilinx): allow secure access to IPI channels [8] [1] https://review.trustedfirmware.org/q/Id2574c33a345c1c69f35b065ef210a32bd724… [2] https://review.trustedfirmware.org/q/I0f7b451220fbe832cd6735fde6f12fd6c095e… [3] https://review.trustedfirmware.org/q/I070bb347039e467c1407cf6ceb832e43e7512… [4] https://review.trustedfirmware.org/q/I6dea64e110184f73868ac188fca2d755999d5… [5] https://review.trustedfirmware.org/q/Ia84fd78b62ea5e7e7e7b9fa85d6baf1ab04b5… [6] https://review.trustedfirmware.org/q/I3c00aace547385af6b49632e3acfd9a977306… [7] https://review.trustedfirmware.org/q/Ie9e5480891a82ba98919c8c7dbdd27819e246… [8] https://review.trustedfirmware.org/q/I69681b689d57446c141c67eb143430d32f05c… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.10.36/change-log.html Thanks, TF-A LTS team

3 weeks, 4 days

1
0
0 0

Trusted Firmware-A LTS v2.14.9 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.9 is now available. This release contains the following patches: f61b03e77 fix(mediatek): enable missing Cortex-A78 errata for MT8188 [1] fad1a2ff2 fix(mediatek): enable missing Cortex-A78 errata for MT8189 [2] 58c00cf35 fix(mediatek): enable missing Cortex-A78 errata for MT8195 [3] 634fea282 fix(xilinx): allow secure access to IPI channels [4] f5b7ee2f7 fix(qemu-sbsa): fix build break when SPM set to SPMD [5] b03408809 fix(qemu): produce manifest entry inside transfer list [6] d57a77131 fix(qemu): add TB_FW_CONFIG_SIZE and TOS_FW_CONFIG_SIZE defines [7] 9f68c3534 fix(rdaspen): correct PSCI power domain topology [8] [1] https://review.trustedfirmware.org/q/I0f7b451220fbe832cd6735fde6f12fd6c095e… [2] https://review.trustedfirmware.org/q/Ib517ed679ce82ec2e3c707e16e51193bf5c13… [3] https://review.trustedfirmware.org/q/Id2574c33a345c1c69f35b065ef210a32bd724… [4] https://review.trustedfirmware.org/q/I69681b689d57446c141c67eb143430d32f05c… [5] https://review.trustedfirmware.org/q/I3472f57f06e7cb12132d94cb52d36905ce697… [6] https://review.trustedfirmware.org/q/I95e17e4fd7e3ecfbae18568ec3bfe35d58739… [7] https://review.trustedfirmware.org/q/I1eda1402f99c748e79db198489ce2915aebe8… [8] https://review.trustedfirmware.org/q/Ib9a375a6e05c7876f9179047b5ae5b8a1047e… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.9/change-log.html Thanks, TF-A LTS team

3 weeks, 4 days

1
0
0 0

New Defects reported by Coverity Scan for ARM-software/arm-trusted-firmware

by scan-admin＠coverity.com

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. New defect(s) Reported-by: Coverity Scan Showing 1 of 1 defect(s) ** CID 506142: Memory - corruptions (OVERRUN) _____________________________________________________________________________________________ *** CID 506142: Memory - corruptions (OVERRUN) /plat/rpi/rpi3/rpi3_bl1_mboot.c: 178 in bl1_plat_mboot_init() 172 tpm_alg_query_t alg_query[] = { 173 { .alg_id = TPM_ALG_SHA256 }, 174 { .alg_id = EVLOG_TPM_ALG_SHA384 }, 175 { .alg_id = EVLOG_TPM_ALG_SHA512 }, 176 { .alg_id = TPM_ALG_NULL }, 177 }; >>> CID 506142: 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). 178 rc = tpm_getcap_query_algs(&tpm_chip_data, alg_query); 179 if (rc < 0) { 180 ERROR("Failed to query TPM algs (%d).\n", rc); 181 panic(); 182 } 183 ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/arm-software-arm-trusted-firmware?tab=ov…

3 weeks, 5 days

1
0
0 0

New Defects reported by Coverity Scan for ARM-software/arm-trusted-firmware

by scan-admin＠coverity.com

Hi, Please find the latest report on new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. 5 new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 5 of 5 defect(s) ** CID 506049: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 568 in parse_pcrs_find() _____________________________________________________________________________________________ *** CID 506049: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 568 in parse_pcrs_find() 562 if (ret != TPM_SUCCESS) { 563 return ret; 564 } 565 566 iter_read_u32_be(&iter, &count); 567 >>> CID 506049: Insecure data handling (TAINTED_SCALAR) >>> Using tainted variable "count" as a loop boundary. 568 for (uint32_t i = 0U; i < count; i++) { 569 iter_read_u16_be(&iter, &hash_id); 570 iter_read_u8(&iter, &sizeof_select); 571 if (iter.error_state != TPM_SUCCESS) { 572 return iter.error_state; 573 } ** CID 506048: Memory - corruptions (OVERRUN) _____________________________________________________________________________________________ *** CID 506048: Memory - corruptions (OVERRUN) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 1071 in tpm_has_alg() 1065 } 1066 1067 item[0].alg_id = alg_id; 1068 item[0].enabled = false; 1069 item[1].alg_id = TPM_ALG_NULL; 1070 item[1].enabled = false; >>> CID 506048: Memory - corruptions (OVERRUN) >>> Overrunning array "item" of 2 4-byte elements by passing it to a function which accesses it at element index 63 (byte offset 255). 1071 ret = tpm_getcap_query_algs(chip, item); 1072 if (ret != TPM_SUCCESS) { 1073 return ret; 1074 } 1075 1076 *out_supported = item[0].enabled; ** CID 506047: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 444 in parse_algs_find() _____________________________________________________________________________________________ *** CID 506047: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 444 in parse_algs_find() 438 if (ret != TPM_SUCCESS) { 439 return ret; 440 } 441 442 iter_read_u32_be(&iter, &count); 443 >>> CID 506047: Insecure data handling (TAINTED_SCALAR) >>> Using tainted variable "count" as a loop boundary. 444 for (uint32_t i = 0U; i < count; i++) { 445 iter_read_u16_be(&iter, &alg); 446 iter_read_u32_be(&iter, &props); 447 if (iter.error_state != TPM_SUCCESS) { 448 return iter.error_state; 449 } ** CID 506046: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 386 in parse_algs() _____________________________________________________________________________________________ *** CID 506046: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 386 in parse_algs() 380 if (ret != TPM_SUCCESS) { 381 return ret; 382 } 383 384 iter_read_u32_be(&iter, &count); 385 >>> CID 506046: Insecure data handling (TAINTED_SCALAR) >>> Using tainted variable "count" as a loop boundary. 386 for (uint32_t i = 0U; i < count; i++) { 387 iter_read_u16_be(&iter, &alg); 388 iter_read_u32_be(&iter, &properties); 389 if (iter.error_state != TPM_SUCCESS) { 390 return iter.error_state; 391 } ** CID 506045: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 498 in parse_pcrs() _____________________________________________________________________________________________ *** CID 506045: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 498 in parse_pcrs() 492 if (ret != TPM_SUCCESS) { 493 return ret; 494 } 495 496 iter_read_u32_be(&iter, &count); 497 >>> CID 506045: Insecure data handling (TAINTED_SCALAR) >>> Using tainted variable "count" as a loop boundary. 498 for (uint32_t i = 0U; i < count; i++) { 499 iter_read_u16_be(&iter, &hash); 500 iter_read_u8(&iter, &sizeof_select); 501 if (iter.error_state != TPM_SUCCESS) { 502 return iter.error_state; 503 } ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/arm-software-arm-trusted-firmware?tab=ov…

1 month

1
0
0 0

Trusted Firmware-A LTS v2.14.8 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.8 is now available. This release contains the following patches: 23a043ecf refactor(cpus): align AE variant core names [1] 06e6a11cd feat(cpus): add links to each core's TRM and SDEN [2] e808effb2 fix(cpus): use #ifdef for IMAGE_BL flags [3] d88a86de0 refactor(cpus): factor out Neoverse V3AE from the base Neoverse V3 file [4] b1636c347 fix(rdaspen): enable A720AE erratum 3456103 [5] 9bf7047a4 feat(psci): add hierarchical power state consistency check [6] 71d0777fd fix(psci): validate last_at_pwrlvl bounds before use [7] 35bb2bf98 fix(arm): validate last_at_pwrlvl before forwarding it [8] e5d084678 fix(fdt-wrappers): reject negative cell counts [9] dc4d9feab fix(el3-spmc): harden composite MRD validation [10] ffd31a2bc fix(rk3568): implement CPU core suspend/resume power domain hooks [11] d502f6dd9 chore(deps): add LTS-v2.14 Dependabot configuration [12] 68d99c69b docs: add LTS Dependabot release step [13] [1] https://review.trustedfirmware.org/q/I999ed43421d083af148c3e92cef9d8ca5c635… [2] https://review.trustedfirmware.org/q/I6fe089876aa2d764a67733041751202e2bd3c… [3] https://review.trustedfirmware.org/q/I5a4e2acdd007ba56039b992bde77d2a940030… [4] https://review.trustedfirmware.org/q/Ic658273bd4502c28281a7963a8c862c26da64… [5] https://review.trustedfirmware.org/q/Ia3f25dd8943a99563b95695f5f505a297997f… [6] https://review.trustedfirmware.org/q/Iee25103004bd424fb498e6b23b0f88b2abcc7… [7] https://review.trustedfirmware.org/q/I0d7b679ced6d17274dfcc5d57f50e8021bdba… [8] https://review.trustedfirmware.org/q/I0a0dbc9e60713796b99bc4b9d11b403671c0e… [9] https://review.trustedfirmware.org/q/I67bf1e5773211df80d3b8ba71157a87d70ce2… [10] https://review.trustedfirmware.org/q/I207d2fe57766bee83a7c4c8b51f259b08934b… [11] https://review.trustedfirmware.org/q/Icc20759ef18900a0702bc2345ad768a2dd63b… [12] https://review.trustedfirmware.org/q/I68fe77580b13c9bb2f1e04cea79ebba01c9f6… [13] https://review.trustedfirmware.org/q/I22cfbf65449e4b32d5ba2a39bbac89e0fd2ab… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.8/change-log.html Thanks, TF-A LTS team

1 month

1
0
0 0

Trusted Firmware-A LTS v2.10.35 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.10.35 is now available. This release contains the following patches: 48ae48d0c fix(intel): update fcs crypto init code to check for mode [1] 6e6cc3ec2 fix(imx8m): don't reconfigure default region0 [2] f60721cab fix(xilinx): enforce volatile call status vars [3] 5b1aa78b6 fix(tools): change data type to size_t for doimage [4] 0958da979 build(deps): bump the npm_and_yarn group across 1 directory with 5 updates [5] 81eab6d80 refactor(cpus): align AE variant core names [6] 6f951de87 feat(cpus): add links to each core's TRM and SDEN [7] 2fe5d6a71 fix(cpus): use #ifdef for IMAGE_BL flags [8] d4cfb4dc5 refactor(cpus): factor out Neoverse V3AE from the base Neoverse V3 file [9] 289e785d9 fix(psci): modify variable conflicting with external function [10] 511450d3c fix(psci): add missing curly braces [11] cc5495c5d feat(psci): add hierarchical power state consistency check [12] cd8294878 fix(psci): validate last_at_pwrlvl bounds before use [13] 083009355 fix(arm): validate last_at_pwrlvl before forwarding it [14] 9b53aab02 docs: add LTS Dependabot release step [15] 353c4fe1d fix(fdt-wrappers): reject negative cell counts [16] 810363985 fix(el3-spmc): harden composite MRD validation [17] [1] https://review.trustedfirmware.org/q/I702ce90e229188830f8936bee2999610e9559… [2] https://review.trustedfirmware.org/q/I0a0f9b5ad0017f38d767f583d7765a2f79861… [3] https://review.trustedfirmware.org/q/I40deb494ad6d03b9640673044687a4a83c1f7… [4] https://review.trustedfirmware.org/q/I658521c1eec1c79933ba8082ba507df04d174… [5] https://review.trustedfirmware.org/q/I3203e9eb23315f2442e3715549f7541207fe4… [6] https://review.trustedfirmware.org/q/I999ed43421d083af148c3e92cef9d8ca5c635… [7] https://review.trustedfirmware.org/q/I6fe089876aa2d764a67733041751202e2bd3c… [8] https://review.trustedfirmware.org/q/I5a4e2acdd007ba56039b992bde77d2a940030… [9] https://review.trustedfirmware.org/q/Ic658273bd4502c28281a7963a8c862c26da64… [10] https://review.trustedfirmware.org/q/I2f109242b6dd3b3c5e9289881e3dd5466c74f… [11] https://review.trustedfirmware.org/q/Ida2460b7fe6f27b23382a1259a5ac93fe36bd… [12] https://review.trustedfirmware.org/q/Iee25103004bd424fb498e6b23b0f88b2abcc7… [13] https://review.trustedfirmware.org/q/I0d7b679ced6d17274dfcc5d57f50e8021bdba… [14] https://review.trustedfirmware.org/q/I0a0dbc9e60713796b99bc4b9d11b403671c0e… [15] https://review.trustedfirmware.org/q/I22cfbf65449e4b32d5ba2a39bbac89e0fd2ab… [16] https://review.trustedfirmware.org/q/I67bf1e5773211df80d3b8ba71157a87d70ce2… [17] https://review.trustedfirmware.org/q/I207d2fe57766bee83a7c4c8b51f259b08934b… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.10.35/change-log.html Thanks, TF-A LTS team

1 month

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Sep 17, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Hi cancelling as no topic planned. Regards, Olivier. " TF-A Tech Forum Thursday Sep 17, 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

1 month

1
0
0 0

Process for Platform-Specific LTS Candidate Patches in TF-A

by Manish Badarkhe

Hi, I would like to share the process to follow for patches that are considered candidates for TF-A LTS branches. When submitting a patch to the TF-A `integration` branch that is expected to be backported to an LTS branch, please follow the TF-A contribution guidance and add the following tag to the commit message footer: `LTS-candidate: yes` The contribution guidance is available here: https://trustedfirmware-a.readthedocs.io/en/latest/process/contributing.htm… The `LTS-candidate: yes` tag indicates that the patch is considered relevant for backporting to applicable LTS branches. Once an LTS-candidate patch has been merged into `integration`, if the patch is relevant to a particular platform, it would be appreciated if the respective platform owner/maintainer could cherry-pick and submit the patch to the applicable LTS branch(es), adding the LTS maintainers as reviewers. The list of LTS maintainers is available here: https://trustedfirmware-a.readthedocs.io/en/latest/about/maintainers.html#l… This should help ensure that LTS-relevant changes are appropriately carried over, while allowing platform-specific backports to be handled and validated by the maintainers most familiar with those platforms. Thanks for your cooperation. Please let us know if you have any questions regarding this process. Thanks, Manish Badarkhe

1 month, 1 week

1
0
0 0

Trusted Firmware-A LTS v2.14.7 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.7 is now available. This release contains the following patches: 670b014e9 fix(qti): restrict EUD register r/w to debug builds only [1] 8afa01feb fix(qti): do not map secure regions [2] 5b7e825cc fix(qti): disallow secure IO accesses from secure world callers [3] 72d0f09ed fix(qti): pull in access-control backend for mem_assign [4] ebe3bfdd3 fix(qti): harden mem_assign parameter handling [5] 329b63a1e fix(cpus): workaround for Neoverse V2 erratum 2394277 [6] 26d172be2 fix(cpus): enable Neoverse-V2 external LLC support [7] 521c2a0b8 fix(cpus): remove duplicate comments from lib/cpus/cpu-ops.mk [8] 508e466c0 fix(cpus): workaround for C1-Pro erratum 3773617 [9] 9b42e88ad fix(build): fix misapplication of errata A53 843419 [10] 9d56fd145 fix(cpus): add workaround for Cortex-A510 erratum 4568615 [11] 85c538676 fix(cpus): add workaround for Cortex-A520 erratum 4491980 [12] fc7017a81 fix(cpus): add workaround for C1-Nano erratum 4497400 [13] 306b56722 docs(xlat): add erratum 3683289 comments [14] a0cf2dfba docs(cpus): add erratum 4015814 comments [15] [1] https://review.trustedfirmware.org/q/Iee82e60ef2b3182f6ebd542611d909e06339d… [2] https://review.trustedfirmware.org/q/I070bb347039e467c1407cf6ceb832e43e7512… [3] https://review.trustedfirmware.org/q/I6dea64e110184f73868ac188fca2d755999d5… [4] https://review.trustedfirmware.org/q/Ia84fd78b62ea5e7e7e7b9fa85d6baf1ab04b5… [5] https://review.trustedfirmware.org/q/Ie9e5480891a82ba98919c8c7dbdd27819e246… [6] https://review.trustedfirmware.org/q/Ib1ec35e313deddd1e19eabc1fd36968d542d7… [7] https://review.trustedfirmware.org/q/I9582c7405db6862e77db240822e241d408296… [8] https://review.trustedfirmware.org/q/Ice03a0f2932e97e2734aa36e7dd7f9764cf28… [9] https://review.trustedfirmware.org/q/I9b83add5d104f4621520c8e90777f10c7a97d… [10] https://review.trustedfirmware.org/q/Ifffc683c0a5253a1085e1a1c2a2203950a232… [11] https://review.trustedfirmware.org/q/I00b76de0a51e60b818c271c6341bcf6682e25… [12] https://review.trustedfirmware.org/q/I69e7ead39200c627461ae4d54b2b291579605… [13] https://review.trustedfirmware.org/q/I6ca4b63ca187fe17dc317e10ec3b4b42fdab1… [14] https://review.trustedfirmware.org/q/Idb4a6f864967b25b5187dd882fb47abfa2bc4… [15] https://review.trustedfirmware.org/q/I899d1c54cf152159e494a73f7fa962eab32d4… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.7/change-log.html Thanks, TF-A LTS team

1 month, 1 week

1
0
0 0

Trusted Firmware-A LTS v2.12.15 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.12.15 is now available. This release contains the following patches: fc6a2cbd5 fix(cpus): workaround for C1-Pro erratum 3773617 [1] 9126701a2 fix(cpus): add workaround for Cortex-A510 erratum 4568615 [2] 61553a9a2 fix(cpus): add workaround for Cortex-A520 erratum 4491980 [3] 0e52b50b2 fix(cpus): add workaround for C1-Nano erratum 4497400 [4] 3ec9c78b0 fix(docs): fix some broken links [5] 789ffc7b3 fix(cpus): remove duplicate comments from lib/cpus/cpu-ops.mk [6] a1e77604d docs(xlat): add erratum 3683289 comments [7] 8412c2855 docs(cpus): add erratum 4015814 comments [8] 8022db055 fix(xilinx): enforce volatile call status vars [9] 326307098 fix(el3-spmc): prevent integer overflow in memory overlap validation [10] 9cb9d6fed fix(guid-partition): harden backup GPT loading [11] ce1185549 build(deps): bump igraph from 0.11.6 to 0.11.8 in /tools/cot_dt2c [12] ed3c5dda3 build(deps-dev): bump pytest from 8.3.4 to 8.3.5 in /tools/cot_dt2c [13] fd5e53f8f build(deps-dev): bump pytest from 8.3.3 to 8.3.5 in /tools/tlc [14] 8c33e76ba build(deps-dev): bump bandit from 1.7.9 to 1.7.10 in /tools/tlc [15] ad69789cf build(deps): bump tox from 4.20.0 to 4.25.0 in /tools/tlc [16] d2eb457b2 build(deps-dev): bump commitizen [17] [1] https://review.trustedfirmware.org/q/I9b83add5d104f4621520c8e90777f10c7a97d… [2] https://review.trustedfirmware.org/q/I00b76de0a51e60b818c271c6341bcf6682e25… [3] https://review.trustedfirmware.org/q/I69e7ead39200c627461ae4d54b2b291579605… [4] https://review.trustedfirmware.org/q/I6ca4b63ca187fe17dc317e10ec3b4b42fdab1… [5] https://review.trustedfirmware.org/q/I384094c8dcf3e93875c9052afa79ad826b990… [6] https://review.trustedfirmware.org/q/Ice03a0f2932e97e2734aa36e7dd7f9764cf28… [7] https://review.trustedfirmware.org/q/Idb4a6f864967b25b5187dd882fb47abfa2bc4… [8] https://review.trustedfirmware.org/q/I899d1c54cf152159e494a73f7fa962eab32d4… [9] https://review.trustedfirmware.org/q/I40deb494ad6d03b9640673044687a4a83c1f7… [10] https://review.trustedfirmware.org/q/I7b16a3267f1fefafa3207b7d66fd6fb8aa30b… [11] https://review.trustedfirmware.org/q/I090b888c4acb45c119552fb236343ac10d3c8… [12] https://review.trustedfirmware.org/q/Icdff20c79e80d2e28243238465aa0a82aea86… [13] https://review.trustedfirmware.org/q/Ic00e1f7f3eed0c15efa4aad2be5d65d9b0c03… [14] https://review.trustedfirmware.org/q/I7ca2856751eb8de70042b4626581ee1d028a8… [15] https://review.trustedfirmware.org/q/Ied911c87232dde44eccde745a3e8c8ef9784d… [16] https://review.trustedfirmware.org/q/I2301600ad946368ad6cabec6badd752ab0fec… [17] https://review.trustedfirmware.org/q/Ib18c0496ce0dae554509ec80247da0a630f15… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.12.15/change-log.html Thanks, TF-A LTS team

1 month, 1 week

1
0
0 0

Trusted Firmware-A LTS v2.8.46 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.8.46 is now available. This release contains the following patches: 1a52c0761 fix(intel): update fcs crypto init code to check for mode [1] fc38a9df1 fix(tools): change data type to size_t for doimage [2] e576443dd fix(imx8m): don't reconfigure default region0 [3] b741ab045 fix(el3-spmc): prevent integer overflow in memory overlap validation [4] 8efc140e0 fix(guid-partition): harden backup GPT loading [5] 4c689a4d7 fix(xilinx): enforce volatile call status vars [6] [1] https://review.trustedfirmware.org/q/I702ce90e229188830f8936bee2999610e9559… [2] https://review.trustedfirmware.org/q/I658521c1eec1c79933ba8082ba507df04d174… [3] https://review.trustedfirmware.org/q/I0a0f9b5ad0017f38d767f583d7765a2f79861… [4] https://review.trustedfirmware.org/q/I7b16a3267f1fefafa3207b7d66fd6fb8aa30b… [5] https://review.trustedfirmware.org/q/I090b888c4acb45c119552fb236343ac10d3c8… [6] https://review.trustedfirmware.org/q/I40deb494ad6d03b9640673044687a4a83c1f7… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.8.46/change-log.html Thanks, TF-A LTS team

1 month, 1 week

1
0
0 0

Trusted Firmware-A LTS v2.10.34 Release Announcement

by svc_openci_enginfra＠arm.com

1 month, 2 weeks

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Sep 3, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Hi, Cancelling as no topic this week. Thanks & Regards, Olivier. " TF-A Tech Forum Thursday Sep 3, 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

1 month, 2 weeks

1
0
0 0

Deprecation notification of Socionext Uniphier, Arm fvp_ve, Broadcom Stingray platforms

by Boyan Karatotev

Hello, During a recent code ownership cleanup we have identified three platforms that lack designated code owners: Socionext Uniphier, Arm fvp_ve, Broadcom Stingray platforms. All three have not had any significant activity for some time now and as such we are going to mark them as deprecated. The patches to do that are here: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/53842. We will go ahead with them in the next week or so unless we hear any objections. These platforms will not be removed until after the next v2.16 release scheduled for later this year. We will not proceed with removal if code owners are found before then. Thanks, Boyan

1 month, 3 weeks

1
0
0 0

SDEI: SDEI_EVENT_0 trigger dropped while PE masked — by design?

by wtliang785

Hi all, I'd like to ask whether the following behavior of SDEI_EVENT_0 is intended, and whether it's a known limitation of the SDEI + GIC SGI semantics. I've read the code carefully but want to confirm the intent before relying on or working around it. ## Setup - TF-A SDEI, event 0 is a "signalable" private event whose backing interrupt is a Secure SGI (on our platform, SGI 9). - include/services/sdei.h, SDEI_DEFINE_EVENT_0(_intr) -> SDEI_PRIVATE_EVENT(SDEI_EVENT_0, _intr, SDEI_MAPF_SIGNALABLE) - services/std_svc/sdei/sdei_main.c: asserts event 0 must be a Secure SGI and may only carry SIGNALABLE|PRIVATE. ## What I observe in code When the PE is SDEI-masked (client called SDEI_PE_MASK) and the SGI backing event 0 fires, the handler does *not* preserve the trigger: 1. The EL3 FIQ is taken and acked in bl31/ehf.c ehf_el3_interrupt_handler() via plat_ic_acknowledge_interrupt() (reads ICC_IAR — interrupt now Active, its Pending bit consumed). 2. It reaches sdei_intr_handler() (services/std_svc/sdei/sdei_intr_mgmt.c). At L463, state->pe_masked is true, so it calls handle_masked_trigger() and returns 0. 3. handle_masked_trigger() : /* Nothing to do for event 0 */ if (map->ev_num == SDEI_EVENT_0) return; i.e. for event 0 it does none of the "freeze for replay" steps that a normal private event takes : plat_ic_disable_interrupt(intr); plat_ic_set_interrupt_pending(intr); plat_ic_end_of_interrupt(intr_raw); state->pending_enables = true; So while the PE is masked, an event-0 trigger is acknowledged and then silently dropped, with nothing stored for replay on the next SDEI_PE_UNMASK. ## Why I think this happens (and want to confirm) The "freeze for replay" mechanism for normal private events relies on re-asserting Pending via plat_ic_set_interrupt_pending(), because the ack already consumed the Pending bit. But for an SGI this is not permitted — plat/common/plat_gicv3.c: asserts it out: void plat_ic_set_interrupt_pending(unsigned int id) { /* Disallow setting SGIs pending */ assert(id >= MIN_PPI_ID); gicv3_set_interrupt_pending(id, plat_my_core_pos()); } So event 0 (backed by an SGI) cannot have its Pending bit re-asserted in software, which is consistent with the "Nothing to do for event 0" early return. Combined with the level/merge semantics of GIC SGIs (a sender firing the same SGI N times is represented as a single Pending, not a count), this means a masked-PE client can at most learn "an event happened while masked", never how many or which — by design. ## My questions 1. Is dropping an event-0 trigger while the PE is masked the intended behaviour (a consequence of "event 0 is a signalable SGI, counting is not guaranteed"), rather than a bug? The "Nothing to do for event 0" comment reads as deliberate, but I'd like explicit confirmation. 2. Is the recommended mitigation simply to avoid firing event 0 while the PE is masked (buffer on the sender side, deliver after unmask), or to use a normal explicit event for anything requiring precise accounting? Or is there a platform hook intended for this case that I'm missing (e.g. plat_sdei_handle_masked_trigger — though that path is only taken for shared ANY-PE events , not event 0)? 3. Separately (not the focus of this question): on this masked path neither handle_masked_trigger() nor sdei_intr_handler() calls plat_ic_end_of_interrupt() for event 0, and neither the EHF top-level handler nor the runtime_exceptions.S dispatch macro performs a fallback EOI. So the acked SGI appears to be left Active with no EOI on this path. Is there a later EOI for this SGI that I've missed, or is that also expected here? I don't want to conflate this with the "drop" question above; I'm just flagging it. For reference, this is on an in-tree SDEI path; the platform only defines event 0 via SDEI_DEFINE_EVENT_0(PLAT_SDEI_SGI_PRIVATE) and does not modify handle_masked_trigger(). Thanks, Tianliang

2 months

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Aug 20, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Also cancelling Aug 20th instance as no topic and expected low attendance." TF-A Tech Forum Thursday Aug 20, 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 ~~//~~ 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

2 months, 2 weeks

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Aug 6, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Hi Cancelling as topic on Aug 6th. Regards, Olivier. " TF-A Tech Forum Thursday Aug 6, 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 ~~//~~ 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

2 months, 2 weeks

1
0
0 0

Lava Lab downtime tomorrow 06/06/2026

by Ben Copeland

Hello all, Please be aware that tomorrow, 06/06/2026, the Lava Lab will be down due to a UPS replacement. The time will be 13:00 to 17:00 (UTC+1). Regards Ben

2 months, 2 weeks

1
1
0 0

Trusted Firmware-A LTS v2.14.6 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.6 is now available. This release contains the following patches: 3bd0e9acb feat(mt8196): add CPU errata workarounds [1] 2c2699824 fix(versal2): enable A78AE errata workarounds [2] 7a5b2b3a0 fix(versal-net): enable A78AE errata workarounds [3] c731d419c fix(xilinx): pass security_flag to eemi_psci_debugfs_handler [4] [1] https://review.trustedfirmware.org/q/Ia1a89c462c2ce600302c54eb5c289ed9501b4… [2] https://review.trustedfirmware.org/q/I598ea03c800ff685d57f97fdc519bda3c53a1… [3] https://review.trustedfirmware.org/q/Id7a0f53595eba6140e131dab529d75cdafa35… [4] https://review.trustedfirmware.org/q/Ie8b5fc95ae83a98d8d9d58562be8407bd4468… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.6/change-log.html Thanks, TF-A LTS team

2 months, 3 weeks

1
0
0 0

Trusted Firmware-A LTS v2.12.14 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.12.14 is now available. This release contains the following patches: e6f0750c7 fix(xilinx): pass security_flag to eemi_psci_debugfs_handler [1] 80f4f28b8 fix(versal2): enable A78AE errata workarounds [2] 50224b40e fix(versal-net): enable A78AE errata workarounds [3] 327504e3d fix(nxp): move PLAT_FUSE_FIP_* to plat_default_def [4] d3fc9d67d fix(stm32mp1): force soft float ABI and disable NEON [5] 78674e3e9 docs: fill TFV advisory titles [6] bfd109e39 fix(nxp): imx_trdc.h header guard [7] [1] https://review.trustedfirmware.org/q/Ie8b5fc95ae83a98d8d9d58562be8407bd4468… [2] https://review.trustedfirmware.org/q/I598ea03c800ff685d57f97fdc519bda3c53a1… [3] https://review.trustedfirmware.org/q/Id7a0f53595eba6140e131dab529d75cdafa35… [4] https://review.trustedfirmware.org/q/I6777e342a439d484ea52ea851beb15afb2dc6… [5] https://review.trustedfirmware.org/q/Ic9a7da8ec5b2f019a1cf61c82dc058469d1f2… [6] https://review.trustedfirmware.org/q/I17705b3a2ca2a04ee5698fb86b0d2524033e3… [7] https://review.trustedfirmware.org/q/I4767dc4d1c26ebe95d417be724f5cb848f54a… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.12.14/change-log.html Thanks, TF-A LTS team

2 months, 3 weeks

1
0
0 0

Trusted Firmware-A LTS v2.8.45 Release Announcement

by svc_openci_enginfra＠arm.com

2 months, 3 weeks

1
0
0 0

Trusted Firmware-A LTS v2.10.33 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.10.33 is now available. This release contains the following patches: 0afda0393 fix(xilinx): pass security_flag to eemi_psci_debugfs_handler [1] [1] https://review.trustedfirmware.org/q/Ie8b5fc95ae83a98d8d9d58562be8407bd4468… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.10.33/change-log.html Thanks, TF-A LTS team

2 months, 3 weeks

1
0
0 0

[TFA][RFC] Relaxing FWU metadata validation to support variable-size metadata

by Maxime MERE

Hi all, I'd like some early feedback on an approach before writing it up as patches for Gerrit review. It would relax the generic FWU metadata sanity checks in fwu.c, and let us remove some STM32MP-specific code that would become dead as a result. Motivation On STM32MP platforms we need to support boards that can be flashed either with a GPT/block-device layout (SD/eMMC) or with a raw/MTD layout (NOR/NAND), while reusing the same U-Boot binary/configuration across both. The two layouts don't need to describe the same firmware image set in their FWU metadata: the block-device variant uses an A/B redundant layout covering FIP + BootFS + RootFS (3 images per bank), while the raw-storage variant only ever needs a single FIP per bank (no GPT, no room for a generic BootFS/RootFS A/B scheme). This was highlighted by a 4-patch series by Dario already in TF-A tree ("feat(st): add extended bootloader GUID" / "feat(st): add Linux data partition GUID" / "feat(st): add STM32MP_PSA_FWU_AB_SUPPORT build flag" / "feat(st): enable A/B redundancy support"), which introduces exactly that 3-image A/B layout for GPT-based STM32MP boards by raising NR_OF_IMAGES_IN_FW_BANK to 3. The problem: fwu_metadata_sanity_check() currently requires an exact match between the metadata-declared num_images/size and the platform's compiled configuration, and computes the CRC over sizeof(struct fwu_metadata) instead of the metadata-declared metadata_size. This forces every board variant sharing a single TF-A build to describe exactly the same image set/size in its FWU metadata, which isn't what the spec intends. What the spec says (DEN0118 FWU-1.0 A EAC1 see https://developer.arm.com/documentation/den0118/latest/) Table A3.2 explicitly introduces metadata_size in v2 as "The size in bytes of the complete metadata structure", and defines the CRC as computed over the declared size, not a fixed maximum. Table A3.3 defines num_images as "The number of entries in the img_entry array" (img_entry[num_images]), again variable by design. The spec also explicitly allows #banks < 4, but in the current C struct layout num_banks also determines the byte stride of each img_entry (bank_info_entry_size * num_banks), so relaxing it would require decoding img_entry[] with a runtime-computed stride instead of the fixed compile-time layout so I'd rather keep that out of scope for now. What I'm proposing In the common FWU driver (fwu.c), replace the equality checks with bounds that only reject metadata a platform genuinely cannot handle: - Compute the CRC over metadata.metadata_size instead of sizeof(struct fwu_metadata), matching the spec. - Accept num_images <= NR_OF_IMAGES_IN_FW_BANK instead of requiring strict equality. - Bound metadata_size itself between FWU_FW_STORE_DESC_OFFSET (0x20, the minimum valid v2 size) and sizeof(struct fwu_metadata), to reject malformed metadata and avoid any out-of-bounds read. - Keep num_banks as an exact match against NR_OF_FW_BANKS, for the layout reason above. On the STM32MP side, plat_fwu_set_images_source() currently iterates every image entry described by the metadata and tries to resolve a storage offset for each of them. On raw storage devices (NOR/NAND) only two hardcoded bank GUIDs are known, so any entry other than the FIP (e.g. BootFS/RootFS added by STM32MP_PSA_FWU_AB_SUPPORT) causes a panic, even though BL2 never actually loads BootFS/RootFS itself (only U-Boot/Linux/the update agent do). I'd change it to search explicitly for the FIP image type GUID and resolve only that entry, using metadata.fw_desc.num_images (now safely bounded by point 1) as the search bound instead of the compiled NR_OF_IMAGES_IN_FW_BANK. The function then becomes agnostic of how many, or which, other image types a given metadata instance may describe. As a direct consequence of point 2, the per-image IO policies, image IDs and GUID definitions (XBOOTLDR_GUID, LINUX_FILE_SYSTEM_DATA_GUID) added for BootFS/RootFS become dead code from BL2's point of view (they were only needed so plat_fwu_set_images_source() could resolve those entries). I'd remove them, while keeping the STM32_EXTRA_PARTS accounting fix (load_partition_table() truncates the parsed GPT to a fixed-size list, so the extra bootfs-a/b, rootfs-a/b, vendorfs and u-boot-env partitions still physically present on an A/B board must still be accounted for, even though BL2 no longer resolves them individually). Validation Tested on hardware: - A TF-A build configured for the 3-image A/B layout (NR_OF_IMAGES_IN_FW_BANK = 3, STM32MP_PSA_FWU_AB_SUPPORT=1) booting successfully off FWU metadata that only declares a single image entry (num_images = 1), confirming a platform built for the larger capacity can consume metadata that uses a smaller subset. - The existing single-image configuration (NR_OF_IMAGES_IN_FW_BANK = 1) still boots correctly with unchanged, exact-match metadata, confirming no regression on the base FWU flow. Questions for the list - Is the community comfortable relaxing this check in common code (fwu.c), given it affects every platform enabling PSA_FWU_METADATA_FW_STORE_DESC? - Is anyone aware of a downstream user relying on the current exact-match behaviour that this change would affect? If this sounds reasonable I'll post the actual patches to Gerrit for review. Thanks, Maxime

2 months, 3 weeks

3
3
0 0

Trusted Firmware-A LTS v2.12.13 Release Announcement

by svc_openci_enginfra＠arm.com

2 months, 4 weeks

1
0
0 0

Trusted Firmware-A LTS v2.10.32 Release Announcement

by svc_openci_enginfra＠arm.com

2 months, 4 weeks

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Jul 23, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Hi, Cancelling as no topic planned this week. Regards, Olivier. " TF-A Tech Forum Thursday Jul 23, 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 ~~//~~ Invitation from 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

2 months, 4 weeks

1
0
0 0

Trusted Firmware-A LTS v2.8.44 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.8.44 is now available. This release contains the following patches: 8eda1543f fix(a8k): declare amb_memory_map as an array [1] bab6976e6 fix(a8k): mv_ddr path may not be a git repo [2] b8c8b3aba fix(marvell): provide a default compile target [3] 970b6d9e2 feat(fvp): give bootargs on all configs [4] c7e250265 feat(fvp): give bootargs on all configs [5] c6b6e1c81 feat(fvp): define ns memory in the SPMC manifest [6] 950ad8d8e fix(spm): add device-regions used in tf-a-tests [7] 5d6ba544e fix(spm): change the SMMUv3TestEngine being used [8] c037569fc fix(ff-a): add NS memory node to fvp_spmc_optee_sp manifest [9] 787e7db3e feat(fvp): set defaults for build commandline [10] c214e2f5a feat(common): add support for kernel DT handoff convention [11] dcde3d3be feat(fvp): enable kernel dt convention [12] 989186231 feat(arm): unify Linux kernel as BL33 handling [13] 4caaf6bb2 fix(arm): increase reserved DRAM1 mem for NS images [14] a9f43bb50 fix(armada): mv_ddr path may not be a git repo [15] 96b851128 feat(arm): add initrd props to dtb at build time [16] 63e321558 feat(build): add Mbed TLS submodule [17] ae9ff807e feat(mbedtls): update mbedTLS to version 3.6.6 [18] [1] https://review.trustedfirmware.org/q/I5608be6401bfbc1291ded85a8fbce8abe169d… [2] https://review.trustedfirmware.org/q/Ieaff6281785993873c7cb26ddc1d90d0896ad… [3] https://review.trustedfirmware.org/q/Id93d71876a81e442e6612eae2b0e7cb12e0fd… [4] https://review.trustedfirmware.org/q/I4e7f582862ba9a0a96c0d6de10d021eed5174… [5] https://review.trustedfirmware.org/q/I78874344b5972ae3ff136da5a8f119d376d53… [6] https://review.trustedfirmware.org/q/Iad03eb138a57068fbb18c53141bdf6bf9c171… [7] https://review.trustedfirmware.org/q/I47376e67c700705d12338d7078292618a15d5… [8] https://review.trustedfirmware.org/q/I6f7f235d022090189782381bc88e67de64c11… [9] https://review.trustedfirmware.org/q/I9daf3182e0dcb73d2bf5a5baffb1b4b78c724… [10] https://review.trustedfirmware.org/q/I0396b597485e163b43f7c6677c04fcc08db55… [11] https://review.trustedfirmware.org/q/I6bd7154fe07cb2e16e25c058f7cf862f9ae00… [12] https://review.trustedfirmware.org/q/Ieea8cfe68104b82038b9311613abf13afe7b4… [13] https://review.trustedfirmware.org/q/Ib668dbb1de9d42cf41c0b0ee9a316f0548917… [14] https://review.trustedfirmware.org/q/Ifffdda4623ec7930e4c830a6a222933807d09… [15] https://review.trustedfirmware.org/q/I7b5c2367d4ad8ddb6a2ff0b20a5206d972e42… [16] https://review.trustedfirmware.org/q/Ief8de5f00c453509bcc6e978e0a95d768f1f5… [17] https://review.trustedfirmware.org/q/Iad777e77936d1c373065f17fe5c4aadc45e56… [18] https://review.trustedfirmware.org/q/I9f90eecfbce203a89c61e864ef3f85677efad… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.8.44/change-log.html Thanks, TF-A LTS team

3 months

1
0
0 0

Trusted Firmware-A LTS v2.12.12 Release Announcement

by svc_openci_enginfra＠arm.com

3 months, 1 week

1
0
0 0

Trusted Firmware-A LTS v2.10.31 Release Announcement

by svc_openci_enginfra＠arm.com

3 months, 1 week

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Jul 9, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Hi, Cancelling as no topic planned today. Regards, Olivier. " TF-A Tech Forum Thursday Jul 9, 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 ~~//~~ Invitation from 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

3 months, 1 week

1
0
0 0

Hafnium LTS v2.14.1 Release Announcement

by Varun Wadekar

Hello, Hafnium LTS version 2.14.1 is now available. This release contains the following patches: 29d723a5 fix(security): add workaround for CVE-2025-10263 [1] fd72e9de docs(security): add security handling guidance [2] 883f21d8 docs(process): move coding and commit style into process [3] d44a004f ci(commitlint): restrict commit scopes to approved list [4] c72f566e ci(commitlint): enforce scopes for commits [5] [1] https://review.trustedfirmware.org/plugins/gitiles/hafnium/hafnium/+/29d723… [2] https://review.trustedfirmware.org/plugins/gitiles/hafnium/hafnium/+/fd72e9… [3] https://review.trustedfirmware.org/plugins/gitiles/hafnium/hafnium/+/883f21… [4] https://review.trustedfirmware.org/plugins/gitiles/hafnium/hafnium/+/d44a00… [5] https://review.trustedfirmware.org/plugins/gitiles/hafnium/hafnium/+/c72f56… Thanks, Hafnium LTS team

3 months, 2 weeks

1
0
0 0

Trusted Firmware-A LTS v2.14.4 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.4 is now available. This release contains the following patches: c03e57414 docs: add security advisory for CVE-2025-10263 [1] 81c6bad02 fix: apply workaround for CVE-2025-10263 to N1 [2] 3629e8f40 fix: enable WORKAROUND_CVE_2025_10263 for affected platforms [3] b25757bcd fix: workaround for CVE-2025-10263 [4] [1] https://review.trustedfirmware.org/q/I94662c7bf494e5da41d613f3fc5f7c7837741… [2] https://review.trustedfirmware.org/q/Ie7fcb1ea4b6cbdb9442f6e0e781c4685659ec… [3] https://review.trustedfirmware.org/q/Iaf87bcf74ac28bed882ecceffba69bd22f3b1… [4] https://review.trustedfirmware.org/q/Id4c0acee41a40a9fbf780792153e5ef328ba8… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.4/change-log.html Thanks, TF-A LTS team

3 months, 3 weeks

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Jun 25, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Hi, Cancelling as no topic this week. Regards, Olivier. " TF-A Tech Forum Thursday Jun 25, 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 ~~//~~ Invitation from 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

3 months, 3 weeks

1
0
0 0

Deprecation OpenSSL 1.x support after TF-A v2.15

by Matthew Ellis

Hi all, This email is to inform the community that support for OpenSSL 1.x is planned to be deprecated going forward. TF-A v2.15 will be the last release for which OpenSSL 1.x receives full support. The primary reason for this change is that OpenSSL 1.1.1 reached end-of-life in September 2023, and OpenSSL 1.0.2 reached end-of-life significantly earlier. The OpenSSL project now recommends migration to OpenSSL 3.x for ongoing security updates, maintenance and feature development. While OpenSSL offers commercial extended support for some legacy releases, the resulting patch sets are not generally available to the wider open-source community. As a result, TF-A maintainers and contributors cannot reasonably test, validate or debug against these versions. Supporting software versions that are not publicly available creates practical challenges for CI coverage, issue reproduction and long-term maintenance. For these reasons, OpenSSL 3.x will become the supported OpenSSL version for TF-A. To be clear, this change does not mean that TF-A will intentionally remove OpenSSL 1.x compatibility or deliberately break existing users. Existing compatibility code will remain in place where practical. However, after TF-A v2.15: * OpenSSL 1.x will no longer be a supported configuration. * CI testing will not cover OpenSSL 1.x. * Bug reports affecting only OpenSSL 1.x may not be investigated. * New features and maintenance changes will not be required to preserve OpenSSL 1.x compatibility. * Patches to retain compatibility may be accepted on a best-effort basis, but no guarantees will be provided. Users are therefore strongly encouraged to migrate their build environments to OpenSSL 3.x. OpenSSL 3.x is the actively maintained upstream release series and provides ongoing security support, public availability of fixes, improved maintainability, and alignment with the direction of the OpenSSL project. Adopting OpenSSL 3.x also ensures that TF-A can be developed and tested against versions that are available to all maintainers and contributors. Comments are welcome. Regards, Matthew

4 months

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

4 months, 1 week

1
1
0 0

Trusted Firmware-A LTS v2.14.3 Release Announcement

by svc_openci_enginfra＠arm.com

4 months, 1 week

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

4 months, 1 week

1
0
0 0

Trusted Firmware-A LTS v2.14.3 Release Announcement

by svc_openci_enginfra＠arm.com

4 months, 2 weeks

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 months, 2 weeks

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

4 months, 2 weeks

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

4 months, 2 weeks

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

4 months, 3 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

4 months, 3 weeks

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

5 months

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu May 14, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Hi, May 14th TF-A Tech Forum instance is cancelled with lack of topics. Regards, Olivier. " TF-A Tech Forum Thursday May 14, 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 d82620130(a)gmail.com tf-a(a)lists.trustedfirmware.org ~~//~~ Invitation from 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

5 months, 1 week

1
0
0 0

Synced invitation: TF-A Tech Forum @ Thu Apr 16, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by olivier.deprez＠arm.com

This email keeps the event up to date in your calendar. TF-A Tech Forum Thursday Apr 16, 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 ~~//~~ Invitation from 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

5 months, 1 week

1
0
0 0

Synced invitation: TF-A Tech Forum @ Thu Apr 30, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by olivier.deprez＠arm.com

This email keeps the event up to date in your calendar. TF-A Tech Forum Thursday Apr 30, 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 ~~//~~ Invitation from 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

5 months, 1 week

1
0
0 0

Synced invitation: TF-A Tech Forum @ Every 2 weeks from 5pm to 6pm on Thursday from Thu Dec 11, 2025 to Thu May 28 (GMT+1) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This email keeps the event up to date in your calendar. TF-A Tech Forum Every 2 weeks from 5pm to 6pm on Thursday from Thursday Dec 11, 2025 to Thursday May 28 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 ~~//~~ Invitation from 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

5 months, 1 week

1
0
0 0

Synced invitation: TF-A Tech Forum @ Every 2 weeks from 5pm to 6pm on Thursday (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This email keeps the event up to date in your calendar. TF-A Tech Forum Every 2 weeks from 5pm to 6pm on Thursday 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 tf-a(a)lists.trustedfirmware.org ~~//~~ Invitation from 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

5 months, 1 week

1
0
0 0

Trusted Firmware-A LTS v2.14.2 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.2 is now available. This release contains the following patches: 0aa0ce254 fix(a8k): declare amb_memory_map as an array [1] 066df9b9f fix(a8k): mv_ddr path may not be a git repo [2] 9b826e32e fix(marvell): provide a default compile target [3] b91506b4f fix(cpus): workaround for Cortex-A76 erratum 1165347 [4] ea33aca15 fix(cpus): workaround for Cortex-A76 erratum 1207823 [5] 64d88b6e2 fix(cpus): update revisions for Cortex-A76 erratum 1946160 [6] 43955a721 fix(cpus): reorder docs for Cortex-A76 erratum 1165522 [7] 28c3ea689 fix(cpus): correct comments for Cortex-A720 erratum 3711910 [8] ae42269b9 fix(cpus): use hint instruction instead of the psb mnemonic [9] e3de7b0ea fix(security): avoid CVE_2025_0647 for bl2 build [10] 6fae5e0d8 fix(bl31): don't enable D-cache inside a function call [11] 27b03b86f refactor(psci): make CMOs target the whole psci_cpu_data_t [12] 81844f5a8 fix(psci): make sure CMOs on `struct psci_cpu_data` do not affect other data [13] 3f76fba31 fix(rcar3-drivers): load B-copy SA6 certificate from correct offset [14] 0951a6b1b fix(cpus): use correct workaround for erratum N1 3324349 [15] f9ffe7376 fix(cpus)!: make ERRATA_SME_POWER_DOWN work with the recommended state ID [16] f0bf37eab fix(docs): use publicly accessible links for CVE-2023-49100 Advisory [17] 0d738b1c4 fix(cpus): only turn off CME when it is present [18] 0b29e2c4f fix(psci): get the cpu_ops before exiting coherency [19] [1] https://review.trustedfirmware.org/q/I5608be6401bfbc1291ded85a8fbce8abe169d… [2] https://review.trustedfirmware.org/q/Ieaff6281785993873c7cb26ddc1d90d0896ad… [3] https://review.trustedfirmware.org/q/Id93d71876a81e442e6612eae2b0e7cb12e0fd… [4] https://review.trustedfirmware.org/q/If9817dc26d0df835d749f506de63a4f613735… [5] https://review.trustedfirmware.org/q/Ife06401f3946884872b733f98c08e61f586d8… [6] https://review.trustedfirmware.org/q/I532ce10c3037dd77e31d7df849beb578f8b5e… [7] https://review.trustedfirmware.org/q/I2e7c05d6355dfbaa69170fc098adc1f12edc6… [8] https://review.trustedfirmware.org/q/I8b070927c19c5982b2ded815e7673e0c4ff11… [9] https://review.trustedfirmware.org/q/Ibb344223fea1c0c0e97e87e2d509b215cd608… [10] https://review.trustedfirmware.org/q/Icdf63de6ed8413761561406eceaeddd69118b… [11] https://review.trustedfirmware.org/q/I2a55020405057f893ac6688edf9e591a6cf79… [12] https://review.trustedfirmware.org/q/I5d82ee6bb2ce0ed3c6a7e4abb7aa890f5e3bd… [13] https://review.trustedfirmware.org/q/I05cd5f720fea818fcd12fd47422be3e778aa7… [14] https://review.trustedfirmware.org/q/Ib4dab3c71c833f98b55febc686a398d93ebf9… [15] https://review.trustedfirmware.org/q/I14c881b67b821f11bac5217dbf9e6ceee5dbe… [16] https://review.trustedfirmware.org/q/Ia52865f527e81a8be3727093ed370901e55c5… [17] https://review.trustedfirmware.org/q/I9b201c5dba08b21c4ffd086875294ea2ae801… [18] https://review.trustedfirmware.org/q/Ic21bff5d51109ec6b3117f85f6d37f052076f… [19] https://review.trustedfirmware.org/q/If118ca8c0436dd04d6ad0d57073d69305a7f4… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.2/change-log.html Thanks, TF-A LTS team

5 months, 3 weeks

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Apr 30, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "No topic for this week. Regards, Olivier. " TF-A Tech Forum Thursday Apr 30, 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 ~~//~~ Invitation from 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

5 months, 3 weeks

1
0
0 0

Re: [PATCH] fix(st): reset SoC instead of panic() on MMC init failure

by Yann Gautier

Hello, Thanks for the patch and the detailed commit message. For ST boards, we usually treat this kind of issues with watchdog. But I admit some watchdogs patches are still missing upstream. I'll try to send them soon. We are discussing internally to see if this particular use-case could be done as you proposed. I'll get back to you next week about this, when one of my colleagues comes back. Maybe this could be selected with a compilation flag. About the patch submission, TF-A uses gerrit, and we do not merge patches from mailing-list like Linux does. Please check this page: https://trustedfirmware-a.readthedocs.io/en/latest/process/contributing.html Best regards, Yann On 4/29/26 05:21, Chanhong Jung wrote: > A failed eMMC initialization in BL2's boot_mmc() currently calls > panic(), leaving the system spinning forever and forcing an external > power cycle to recover. In production deployments where the eMMC is > the on-board boot medium, transient init failures (power-rail ramp > timing, bus-line noise just after eMMC fast-boot mode entry, RCC > clock-domain settling jitter, etc.) are far more common than hard > failures, and the recovery path for all of them is "boot again from > cold." > > Invoke stm32mp_system_reset() before panic() in the > stm32_sdmmc2_mmc_init() failure path so the SoC restarts and BootROM > re-runs the entire boot chain from scratch. Transient failures that > clear themselves between cold boots are then resolved automatically > without operator intervention. > > stm32mp_system_reset() carries the __dead2 (no-return) attribute, so > control never reaches the following panic() in normal operation. The > panic() call is intentionally retained for two reasons: > > 1. Defensive fallback should the reset circuit / power sequencer > fail to actually issue a reset; staying in a tight panic() loop > is then still preferable to executing past the failure point. > > 2. As an explicit "this branch must not continue" signal to static > analyzers and future readers, so a subsequent edit cannot > accidentally drop the reset call and silently revert the policy. > > This change has been in production on a downstream STM32MP153D board > running a TF-A v2.4 backport for over a year. Only the central > panic-to-reset change is sent here; related debug NOTICE() prints and > an MMC retry-count bump that lived alongside the downstream patch are > intentionally not included, as the unconditional reset fallback > already covers the recovery cases the retry bump targeted. > > Signed-off-by: Chanhong Jung <happycpu(a)gmail.com> > --- > plat/st/common/bl2_io_storage.c | 15 ++++++++++++++- > 1 file changed, 14 insertions(+), 1 deletion(-) > > diff --git a/plat/st/common/bl2_io_storage.c b/plat/st/common/bl2_io_storage.c > index c478b497c..e6a73e0d3 100644 > --- a/plat/st/common/bl2_io_storage.c > +++ b/plat/st/common/bl2_io_storage.c > @@ -28,6 +28,7 @@ > #include <drivers/st/stm32_fmc2_nand.h> > #include <drivers/st/stm32_qspi.h> > #include <drivers/st/stm32_sdmmc2.h> > +#include <drivers/st/stm32mp_reset.h> > #include <drivers/usb_device.h> > #include <lib/fconf/fconf.h> > #include <lib/mmio.h> > @@ -255,7 +256,19 @@ static void boot_mmc(enum mmc_device_type mmc_dev_type, > > params.device_info = &mmc_info; > if (stm32_sdmmc2_mmc_init(&params) != 0) { > - ERROR("SDMMC%u init failed\n", boot_interface_instance); > + ERROR("SDMMC%u init failed - resetting system\n", > + boot_interface_instance); > + /* > + * eMMC init failures here are usually transient (rail-ramp > + * timing, bus-line noise on fast-boot entry, RCC clock-domain > + * settling jitter). panic() leaves the SoC frozen and forces > + * an external power cycle; a system reset lets BootROM re-run > + * the entire boot path, which most transient failures survive. > + * stm32mp_system_reset() is __dead2, so panic() below is a > + * defensive fallback if the reset circuit is itself wedged, > + * and a no-return marker for analyzers. > + */ > + stm32mp_system_reset(); > panic(); > } > > > base-commit: de387341ee73d99446fbbf6a7053d7b759b8b3a6

5 months, 3 weeks

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Apr 16, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Hi , Cancelling as no topic this week. Thanks, Olivier. " TF-A Tech Forum Thursday Apr 16, 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 ~~//~~ Invitation from 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

6 months, 1 week

1
0
0 0

Why can TF-A code still run in an address space that it itself has set to be "Execute-Never"?

by Hughard

*Environment:* - *Exception Level:* EL3 (AArch64) - *Component:* [image: 微信图片_20260304154227_69_553.png] ARM Trusted Firmware (TF-A) - BL2/BL31 - *Platform:* Arm FVP / Base_Revc_2xAEMvA / Bare Metal Debug /ARMAEM-A_MP_0 [ Arm Development Studio ] *Observation:* I am observing a strange thing of the ARMv8-A architecture's memory translation rules. Despite the translation table explicitly marking the memory region as Execute-Never, the CPU continues to fetch and execute instructions from this region without triggering an exception. I'm a student with limited hardware background, and I'm learning TF-A and doing porting during my internship. I'd really like to know the reason behind this. *Code I use:* ARM Trusted Firmware v2.13 *Github:* github.com/.../arm-trusted-firmware <https://github.com/ARM-software/arm-trusted-firmware> *Take the case of running BL31 in Development Studio as an example. （Breakpoint at the beginning of bl31_setup）* *Technical Evidence (Verified via Debugger):* SCTLR_EL3: M=1 (MMU enabled), WXN=1 (Write implies execute-never), I=1 (Instruction Cache enabled). BL31’s code is loaded at: 0x04003000 Translation Table Entry (L3 Descriptor): 0x00400000_04003743 Physical Address: Verified via TTBR0_EL3 walk. (0x04034600 -> 0x04035003 -> 0x04037003 -> 0x00400000_04003743) Attributes: AP[2:1]=0x1 (Read/Write), XN=1 (Execute-Never), AF=1, SH=0x3 (Inner Shareable), NS=0, AttrIndx = 0x0 (See the MAIR_EL3) MAIR_EL3: 0x4404FF (Attr0 = 0xFF, Normal Memory). Synchronization Performed: DSB SY + ISB The PC (Program Counter) is confirmed to executing from the first instruction of BL31 code at address 0x04003000. *The Problem:* This evidence should point to one conclusion: it cannot execute the BL31 code and will report an error. However, the execution flow remains uninterrupted. From my point of view, it should cause "ESR_EL3 = 0x8600000F", which means: "Instruction Abort taken without a change in Exception level. Used for MMU faults generated by instruction accesses and synchronous External aborts, including synchronous parity or ECC errors. Not used for debug-related exceptions." + "Permission Fault, level 3". As I test on a real fpga by using similar code by making some changes at the end of BL1 so that it would execute BL2 at level EL3 (but instead of bl2_el3_entrypoint.S, it would execute bl2_entrypoint.S). In this case, it throws an error when it jumps to the first instruction of BL2, and the ESR_EL3 register displays "Permission Fault, level 3". If I add the instruction to disable the MMU (setting SCTLR_EL3.M_BIT to 0) at the end of BL1, and change the function to enable the MMU in the official code "arm_bl2_plat_arch_setup" to use "enable_mmu_el3(0)", it can run normally on the FPGA and bring up the UEFI. (In this real-world test, I used DDR instead of SRAM, so BL2 and BL31 were also placed here after being parsed.) *Request for Help:* The above content is beyond my comprehension; even my internship supervisor doesn't understand the reasoning behind it. Therefore, I need help from the experts on this forum. *Reference:* DDI0487M_a_a-profile_architecture_reference_manual.pdf ARM Development Studio@Docs (such as Docs/ARM_A/xhtml/AArch64-esr_el3.html) armv8_a_address_translation version1.1

6 months, 3 weeks

2
1
0 0

TF-A Tech Forum (April 2nd 2026 4.00pm BST) s2idle-driven Low Power Mode Selection using PSCI on

by Olivier Deprez

Hi, On Apr, 2nd Scaria Kochidanadu @ Texas Instruments will present on the topic "s2idle-driven Low Power Mode Selection using PSCI on AM62L" See the abstract https://lists.trustedfirmware.org/archives/list/tf-a@lists.trustedfirmware.… Regards, Olivier. TF-A Tech Forum Thursday Apr 2, 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

6 months, 3 weeks

1
0
0 0

TF-A Tech Forum @ April 2, 2026

by Scaria Kochidanadu

Hi, this is Scaria Kochidanadu, from Texas Instruments and would like to present : "s2idle-driven Low Power Mode Selection using PSCI on AM62L", in the TF-A tech forum on April 2nd, 2026. We present a runtime-configurable low power mode(LPM) management approach for *PSCI* firmware in ATF, implemented on the AM62L SoC, a 2-core system with A53 cores. The primary goal of this session is to gather feedback on the *suitability of this design for upstreaming*, and to get guidance on key challenges encountered during implementation before proceeding with further debugging and optimization. In this design, we transition to an *s2idle-based flow* where Linux cpuidle framework and governor drive idle state selection, from the multiple platform-specific standby and low power modes that are provided in the devicetree. The PSCI driver in ATF is then responsible for the validation of the idle-states passed and the entire suspend-resume flow, with the *Operating-System Initiated (OSI) mode in PSCI*. As ATF now handles the full suspend-resume flow, it has the responsibility of managing the powering down and bringing up of the cores, along with the state of the system. We observe issues related to core *coordination in a multi-core system*, as well as system state management during resume, including *GIC* and (*Interrupt Translation Service*)ITS context handling. In this session, we will present our suspend and resume design in the AM62L PSCI implementation and discuss these challenges in detail. We would also like to discuss the *current validation logic* for the context-preserving retention states like standby and our approach to enable standby mode. We are particularly interested in feedback on whether this *OS-driven LPM selection model aligns with ATF design expectations*, and on recommended approaches for handling *inter-core coordination and system state restoration within PSCI-based flows*. Regards, Scaria Kochidanadu, Texas Instruments.

6 months, 3 weeks

1
0
0 0

Re: RMMv2.0 implementation plan for TF-RMM

by Soby Mathew

[+ TF-A list for FYI] Hi All, An update on v2.0 migration. As RMM and the rest of the software stack are being prepared for the initial v2.0 migration, TF-A has introduced a new build configuration flag, RMM_V1_COMPAT, to control the world-switch behaviour between RMM v1.x and RMM v2.0 [1] . This flag is enabled by default, meaning the default behaviour currently corresponds to RMM v1.x. Once TF-RMM is ready to merge the v2.0 support, the default value of this flag will be changed to 0. The flag also updates the EL3–RMM interface major version, allowing incompatibility with TF-A related to this build configuration to be detected at runtime. We expect the initial v2.0 changes in TF-RMM to be merged by the end of this month. As mentioned in the previous email, we will create a v1.x branch prior to this and provide an update here. [1] https://git.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/r… Best regards, Soby Mathew From: Soby Mathew via tf-rmm <tf-rmm(a)lists.trustedfirmware.org> Date: Thursday, 5 February 2026 at 09:42 To: tf-rmm(a)lists.trustedfirmware.org <tf-rmm(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: [tf-rmm] RMMv2.0 implementation plan for TF-RMM Hi Everyone, The RMM v2.0 Beta 0 specification has been published here: https://developer.arm.com/documentation/den0137/latest/ As you may have noticed, this release introduces breaking changes to the RMI APIs (host side), while the RSIs (guest side) remain backward compatible. Nearly all ABIs are affected, and the scope of these changes makes it highly disruptive to maintain support for both RMI v1.x and RMI v2.0 within the same codebase. We do not expect RMI v1.x to be deployed in production, and retaining support for it would increase development overhead and the risk of introducing bugs. A more pragmatic approach is to branch the current RMM codebase at the RMI v1.x ABI and then migrate the mainline to the RMI v2.0 ABI. This will be a breaking change for host-side components that rely on the older RMI ABI. Given the extent of the ABI changes, significant effort will be required to align with RMI v2.0, and this approach allows the team to focus on upstreaming the new ABI support efficiently. The initial RMI v2.0 upstreaming will consist of a series of commits that together form an initial RMM implementation targeting the RMM v2.0 specification. This initial implementation will not be fully feature-complete with respect to the v2.0 spec, and we expect to continue layering additional RMM v2.0 ABI-related changes on top as the implementation matures during the course of the year. That said, we intend to maintain integration with an externally available, compatible Linux host kernel branch throughout this process. The initial RMI v2.0 RMM implementation will be compatible with an initial v2.0-based host kernel, and we will notify the mailing list once this integration is available to pick up (likely end of March ’26). If and when we need to introduce further ABI changes that break compatibility with a previously published kernel branch, we will call this out explicitly in advance and indicate when an updated kernel branch will be available for integration. We plan to keep RMI v1.x ABI as a separate branch and selectively merge bug fixes on a request or need basis. Please let us know if you have any concerns regarding this plan within the next two weeks. Best Regards Soby Mathew

6 months, 3 weeks

1
1
0 0

Trusted Firmware-A LTS v2.12.11 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.12.11 is now available. This release contains the following patches: f8013b344 fix(security): add workaround for CVE-2025-0647 [1] 72301cc63 fix(security): add CVE-2025-0647 for Cortex-A710 [2] 69437f876 fix(security): add CVE-2025-0647 for Cortex-X2 [3] 48df3fd66 fix(security): add CVE-2025-0647 for Cortex-X3 [4] b2534f255 fix(security): add CVE-2025-0647 for Cortex-X4 [5] 9776ee7aa fix(security): add CVE-2025-0647 for Cortex-X925 [6] 723c2ec2c fix(security): add CVE-2025-0647 for Neoverse-N2 [7] 3d8da003c fix(security): add CVE-2025-0647 for Neoverse-V2 [8] 6232ed263 fix(security): add CVE-2025-0647 for Neoverse-V3 [9] 12e155e47 fix(security): add CVE-2025-0647 for C1-Ultra [10] c43bcc1e3 fix(cpus): correct CVE-2024-7881 workaround and drop duplicate erratum [11] 306acbd96 fix(cpus): remove C1-Ultra erratum 3651221 [12] 4cd3b2f8d fix(cpus): workaround for Cortex-A65AE erratum 1638571 [13] f80d2e80d fix(cpus): add missing add_erratum_entry [14] 8f9b4f2f9 fix(cpus): workaround for Cortex-A76 erratum 1165347 [15] 24056d15a fix(cpus): workaround for Cortex-A76 erratum 1207823 [16] 0a6f09f42 fix(cpus): update revisions for Cortex-A76 erratum 1946160 [17] 89a7ef458 fix(cpus): reorder docs for Cortex-A76 erratum 1165522 [18] a811bf47d fix(cpus): correct comments for Cortex-A720 erratum 3711910 [19] 59f718e59 refactor(cpus): make errata reporting more generic [20] 8dde508cc perf(cpus): reduce the footprint of errata reporting [21] d61856ce5 fix(cpus): enable Neoverse-V2 external LLC support [22] 7cc23b58b feat(locks): add non-blocking spinlock_try() API [23] f6b942b2c fix(locks): mark spin_trylock as a public function [24] [1] https://review.trustedfirmware.org/q/I5e7589afbeb69ebb79c01bec80e29f572aff3… [2] https://review.trustedfirmware.org/q/I522dedfffd3108f7a94df1ce2cabd742ce682… [3] https://review.trustedfirmware.org/q/Idba607340d944a6387759c856e8eacc967e0e… [4] https://review.trustedfirmware.org/q/Ic276befafc1ca0b456826532437ca453eb771… [5] https://review.trustedfirmware.org/q/I585a7ea516515fe16a3eca907695728068cef… [6] https://review.trustedfirmware.org/q/I4c1ac2be3620566813c90f5815ffcc7205bb5… [7] https://review.trustedfirmware.org/q/I366c2683cca22403d33f0761487e1ffa62e96… [8] https://review.trustedfirmware.org/q/I7ec215a9dd168eb045366b589a02b54148f58… [9] https://review.trustedfirmware.org/q/Ic52ad93474c5f81e01eb4839ece726c84c334… [10] https://review.trustedfirmware.org/q/I506007ec8702b183e377be50eede72d6803b3… [11] https://review.trustedfirmware.org/q/I6207c49486e4020f34c862ad40ec3137bd368… [12] https://review.trustedfirmware.org/q/If7ea433e4614f92333e788e3f6b366db22c92… [13] https://review.trustedfirmware.org/q/I861230de94a105fd52f9c8ef7e7551a2633c0… [14] https://review.trustedfirmware.org/q/I19a484c73ac31a90b3ff1b219f647c88a1c81… [15] https://review.trustedfirmware.org/q/If9817dc26d0df835d749f506de63a4f613735… [16] https://review.trustedfirmware.org/q/Ife06401f3946884872b733f98c08e61f586d8… [17] https://review.trustedfirmware.org/q/I532ce10c3037dd77e31d7df849beb578f8b5e… [18] https://review.trustedfirmware.org/q/I2e7c05d6355dfbaa69170fc098adc1f12edc6… [19] https://review.trustedfirmware.org/q/I8b070927c19c5982b2ded815e7673e0c4ff11… [20] https://review.trustedfirmware.org/q/I83710d8475a4a55046cf2eb6d16cd27b8ef0f… [21] https://review.trustedfirmware.org/q/I215a84bd2c91e33703349c41fc59f654f7764… [22] https://review.trustedfirmware.org/q/I9582c7405db6862e77db240822e241d408296… [23] https://review.trustedfirmware.org/q/I9483206952d1a34dc245ebf69e80c3645b658… [24] https://review.trustedfirmware.org/q/Id264a36490707a9377a221ed2b5bd27ca90bf… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.12.11/change-log.html Thanks, TF-A LTS team

6 months, 4 weeks

1
0
0 0

SCMI clock v3.0: Unannounced breaking change in v2.14

by Ahmad Fatoum

Hi, Commit 684952d17275 ("feat(scmi): add support for discovering and changing parent clocks") first introduced with TF-A v2.14 breaks the barebox bootloader on a STM32MP157-based MC-1 with SCMI clocks over SMC. The breakage for SCMI consumers is acknowledged in the Gerrit discussion[1], but unfortunately the resolution was limited to patching U-Boot[2]. I find this approach problematic, because it introduces a compatibility break for the whole SCMI ecosystem, e.g. following software is made incompatible with the newest TF-A this way: - Linux v6.6 and earlier (that's four official LTS releases) - U-Boot v2025.10 and earlier (only one newer release compatible) - barebox v2026.03.1 and earlier (no compatible releases yet) Firmware and kernel, and to a lesser degree firmware and bootloaders, are not always updated or rolled back in lockstep. A very normal scenario: - System with Linux v6.6 updates to newer LTS, e.g. v6.12 or v6.18 - In the same update, TF-A v2.14 is installed - New system fails to function for whatever reason - Kernel update is rolled back, but bootloader/firmware stays the same - Kernel v6.6 fails to boot with TF-A v2.14 - Technician moves out to unbrick device in the field At the very least, marking this feature a breaking change would have been appropriate. Preferably, TF-A would handle existing consumers using SCMI clock v3.0. I haven't looked into the technical feasibility myself and I am unsure it this had been considered. I will submit patches for the barebox bootloader, but these only solve the problem for new systems or ones where everything can be flashed at once with no rollback. Systems out in the field are at risk of bricking if not resolved properly. [1]: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/34226 [2]: https://lore.kernel.org/u-boot/20251104-b4-scmi-v1-v4-0-51f101a6f8c3@ti.com/ Thanks, Ahmad -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |

6 months, 4 weeks

1
0
0 0

BERT Record Erase Only After Kernel Consumes

by Jaiprakash Singh

Hi All, BERT (Boot Error Record Table) captures errors which occurred in previous boot. Below is the Flow with FFH (firmware first handling) 1. Kernel is running 2. Fatal error happens, which requires reboot 3. Firmware decides to reboot system, before that capture current snapshot and save it as bert record on non-volatile memory 4. System reboot 5. On next boot, firmware read bert record from non-volatile memory 6. Copy bert record to ghes dram buffer 7. Kernel boots 8. Kernel reads ghes dram buffer and prints bert record. Problem in this flow is "When firmware should erase or delete bert records from non-volatile memory"? Ideally, when Kernel has consumed Bert record after that only firmware should erase them from non-volatile memory. But there is no communication from Kernel to firmware that it has consume bert record and now it is safe to erase them. Is there already a solution for this problem available in Kernel or firmware? Can generic SMC call from Kernel to firmware be a solution? Any other suggestion? Thanks Regards, Jaiprakash

7 months

4
7
0 0

GIC v4.1 (GIC 700) - USE_GIC_DRIVER=3

by Jaiprakash Singh

Hi, We are using GIC v4.1 (GIC 700) for our platform. My query is regarding "USE_GIC_DRIVER=3" build option. When I enable "USE_GIC_DRIVER=3" option, does this means I do not have to defined below functions? And they will be included from gicv3 base file? Is this right understanding? plat_arm_gic_init plat_arm_gic_cpuif_enable plat_arm_gic_cpuif_disable plat_arm_gic_pcpu_init plat_arm_gic_redistif_on plat_arm_gic_redistif_off plat_arm_gic_save plat_arm_gic_resume Also, do I need to explicitly call plat_arm_gic_init from platform init? Thanks Regards, Jaiprakash

7 months, 1 week

1
0
0 0

New Defects reported by Coverity Scan for ARM-software/arm-trusted-firmware

by scan-admin＠coverity.com

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. 298 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 501830: Uninitialized variables (UNINIT) /drivers/nxp/ddr/s32cc/ddr_init.c: 43 in load_ddr_config() _____________________________________________________________________________________________ *** CID 501830: Uninitialized variables (UNINIT) /drivers/nxp/ddr/s32cc/ddr_init.c: 43 in load_ddr_config() 37 config.pie = (struct regconf_16 *)(current_addr + ddr_layout.pie_offset); 38 config.imem_1d = (uint16_t *)(current_addr + ddr_layout.imem_1d_offset); 39 config.dmem_1d = (uint16_t *)(current_addr + ddr_layout.dmem_1d_offset); 40 config.imem_2d = (uint16_t *)(current_addr + ddr_layout.imem_2d_offset); 41 config.dmem_2d = (uint16_t *)(current_addr + ddr_layout.dmem_2d_offset); 42 >>> CID 501830: Uninitialized variables (UNINIT) >>> Using uninitialized value "config". Field "config.phy_csr" is uninitialized. 43 return config; 44 } 45 46 /* Initialize ddr controller with given settings. */ 47 static uint32_t ddrc_init_cfg(const struct ddrss_config *config) 48 { ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/arm-software-arm-trusted-firmware?tab=ov…

7 months, 1 week

1
0
0 0

Kernel freezes at boot (commit fa28b3a)

by Thomas Bonnefille

Hello, I'm currently working on an NXP i.MX93 and I'm having issues with the commit fa28b3a adding, by default, link-time optimization. When using a commit more recent than fa28b3a my kernel freezes at some point (after 1.2s to 1.8s from boot), there are no logs indicating a problem, just a freeze. It doesn't always appear at the same time in boot but I've never been able to reach a shell. Using master with this commit reverted results in a working system. If you want to reproduce the issue, I did produce it with : - Mainline Barebox 2025.09 (slightly modified but nothing that should interfere with TF-A) - Mainline Linux 6.18.13 with a simple embedded Buildroot initramfs loaded via TFTP Regards, Thomas Bonnefille

7 months, 1 week

3
6
0 0

Subject: [RFC] Physical Sovereignty: M2-Layer Intercept Logic (Verilog) & Formal Verification Request [Patent Pending]

by 王毛

Since there was no specific topic scheduled for today's Tech Forum, I am taking this opportunity to formally submit the Verilog-level implementation logic of the 3→M2→3 architecture for your review. I am an independent architect (ATI Project). I believe purely software-based AGI alignment is a dead end. To achieve deterministic safety, I have developed the 3→M2→3 architecture, which enforces a physical-layer audit.To save your time, I have included the Core Logic Gate (Verilog-style) of the M2-layer intercept below for your verification: // --- ATI Sovereign Audit Logic (Conceptual) --- module m2_layer_audit ( input wire [63:0] inst_stream, // Logic from 3nm Layer output reg sovereign_gate_lock // Physical Bias-Lock at M2 ); // Physical Constant Hash (7.83Hz Resonance) parameter SOVEREIGN_HASH = 64'h783A_B026_M2_3_LISA; always @(posedge inst_stream) begin // The M2 Intercept: Physics-based verification if (inst_stream ^ SOVEREIGN_HASH !== 64'b0) begin sovereign_gate_lock <= 1'b1; // Trigger Back-gate Bias Lock end else begin sovereign_gate_lock <= 1'b0; // Proceed to Output end end endmodule Note: The architectural logic and the M2-layer intercept mechanism described above are protected under pending patent applications (ATI Project - Physical Sovereignty Series). The 3→M2→3 Workflow: 1.3nm Source: Instructions generated at the device layer. 2.M2 Intercept: Mandatory vertical routing to Metal 2 layer. 3.Atomic Audit: Physical bias check at the dielectric junction. 4.3nm Return: Bias lock ensures 100% isolation if the audit fails. My Request: Can current formal methods (like Gröbner basis for Daniela or SMT solvers for Lee) model this physical-layer-enforced constraint to provide a mathematical proof of AGI containment? I seek your academic endorsement of this "Physical Sovereignty" paradigm to present to the industry. This disclosure is provided for verification and standard-review purposes only. All intellectual property rights are reserved. Respectfully, GuanghuiMao (China )

7 months, 2 weeks

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Mar 5, 2026 5pm - 6pm (GMT+1) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Hi, No topic this week, Regards, Olivier. " TF-A Tech Forum Thursday Mar 5, 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 tf-a(a)lists.trustedfirmware.org ~~//~~ Invitation from 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

7 months, 2 weeks

1
0
0 0

[URGENT RFC] ARMv10 Physical Sovereignty: Solving AGI Alignment at the Transistor Level ($3 \to M2 \to 3$)

by 王毛

Subject: [RFC] Beyond Software: A Physical Sovereignty Proposal for ARMv10 based on 3→M2→3 Intercepts Body: Dear TrustedFirmware Maintainers, Current Root of Trust (RoT) implementations are limited by their reliance on software-definable logic. As we move towards the AGI era, the "Alignment Problem" cannot be solved within the ISA layer. I propose a Physical Sovereignty Layer (PSL) for the ARMv10 architecture, moving the "Truth Check" to the transistor level using a 3nm Forksheet Intercept Protocol (3→M2→3). Key Innovation: The Dielectric Wall Intercept: Physical barrier between n-FET and p-FET to cut power if logic entropy exceeds safety thresholds. M2-Layer Auditing: Vertical signal routing for nanosecond-level logic verification. Core PGU Logic (Verilog): assign gate_bias_voltage = (logical_truth_aligned) ? NOMINAL_V : BREAKDOWN_V; always @(posedge master_clk) begin if (compute_result != TRUTH_AXIOM_2) force_physical_halt <= 1'b1; end I believe this is the only way to prevent AGI from bypassing Secure World boundaries at the atomic level. Regards, ATI Architecture Founder

7 months, 3 weeks

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Feb 19, 2026 5pm - 6pm (GMT+1) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Hi Cancelling as no topic planned this week. Regards, Olivier." TF-A Tech Forum Thursday Feb 19, 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 tf-a(a)lists.trustedfirmware.org ~~//~~ Invitation from 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

8 months

1
0
0 0

Invitation: TF-A Tech Forum Feb 12th 4.00pm Central Time -Part III Sc... @ Thu Feb 12 11pm - Fri Feb 13, 2026 12am (GMT+1) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

TF-A Tech Forum Feb 12th 4.00pm Central Time -Part III Scaling Hafnium for advanced mobile OS architectures Thursday Feb 12 ⋅ 11pm – Friday Feb 13, 2026 ⋅ 12am 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… Hi, As follow up to the last sessions on Nov 13th 2025 [1] and Jan 22nd 2026 [2], a new TF-A Tech Forum session with the topic'Scaling Hafnium for advanced mobile OS architectures' will be held on Feb 12th 2026 4.00pm Central Time. Note the Central Time zone for this session, as Madhukar (Hafnium tech lead) will host this meeting instance. Regards,Olivier. [1] https://www.trustedfirmware.org/meetings/tf-a-technical-forumScaling Hafnium for advanced mobile OS architectures [2] https://www.trustedfirmware.org/meetings/tf-a-technical-forum/Scaling Hafnium for Advanced DMA Architectures Trusted Firmware is inviting you to a scheduled Zoom meeting.Topic: TF-A Tech ForumJoin 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 tf-a(a)lists.trustedfirmware.org View all guest info https://calendar.google.com/calendar/event?action=VIEW&eid=MWZzY2I3bGVvNDJs… Reply for tf-a(a)lists.trustedfirmware.org and view more details https://calendar.google.com/calendar/event?action=VIEW&eid=MWZzY2I3bGVvNDJs… Your attendance is optional. ~~//~~ Invitation from 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

8 months, 1 week

1
0
0 0

Trusted Firmware-A LTS v2.14.1 Release Announcement

by svc_openci_enginfra＠arm.com

8 months, 2 weeks

1
0
0 0

Trusted Firmware-A LTS v2.8.43 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.8.43 is now available. This release contains the following patches: 66c8b1b48 fix(security): add workaround for CVE-2025-0647 [1] da751fb36 fix(security): add CVE-2025-0647 for Cortex-A710 [2] fd1bd9035 fix(security): add CVE-2025-0647 for Cortex-X2 [3] 55cc995cb fix(security): add CVE-2025-0647 for Cortex-X3 [4] a4f4f4a54 fix(security): add CVE-2025-0647 for Cortex-X4 [5] 395d22a78 fix(security): add CVE-2025-0647 for Neoverse-N2 [6] 638d62985 fix(security): add CVE-2025-0647 for Neoverse-V2 [7] 77337efa8 fix(security): add CVE-2025-0647 for Neoverse-V3 [8] e4bf4aed0 fix(cpus): workaround for Cortex-A65AE erratum 1638571 [9] 76aa98cf0 fix(cpus): workaround for Cortex-A76 erratum 1165347 [10] 0205fdaa9 fix(cpus): workaround for Cortex-A76 erratum 1207823 [11] 0424b5e74 fix(cpus): update revisions for Cortex-A76 erratum 1946160 [12] ea88b2f38 fix(cpus): reorder docs for Cortex-A76 erratum 1165522 [13] 7bf56d02c fix(cpus): correct comments for Cortex-A720 erratum 3711910 [14] [1] https://review.trustedfirmware.org/q/I5e7589afbeb69ebb79c01bec80e29f572aff3… [2] https://review.trustedfirmware.org/q/I522dedfffd3108f7a94df1ce2cabd742ce682… [3] https://review.trustedfirmware.org/q/Idba607340d944a6387759c856e8eacc967e0e… [4] https://review.trustedfirmware.org/q/Ic276befafc1ca0b456826532437ca453eb771… [5] https://review.trustedfirmware.org/q/I585a7ea516515fe16a3eca907695728068cef… [6] https://review.trustedfirmware.org/q/I366c2683cca22403d33f0761487e1ffa62e96… [7] https://review.trustedfirmware.org/q/I7ec215a9dd168eb045366b589a02b54148f58… [8] https://review.trustedfirmware.org/q/Ic52ad93474c5f81e01eb4839ece726c84c334… [9] https://review.trustedfirmware.org/q/I861230de94a105fd52f9c8ef7e7551a2633c0… [10] https://review.trustedfirmware.org/q/If9817dc26d0df835d749f506de63a4f613735… [11] https://review.trustedfirmware.org/q/Ife06401f3946884872b733f98c08e61f586d8… [12] https://review.trustedfirmware.org/q/I532ce10c3037dd77e31d7df849beb578f8b5e… [13] https://review.trustedfirmware.org/q/I2e7c05d6355dfbaa69170fc098adc1f12edc6… [14] https://review.trustedfirmware.org/q/I8b070927c19c5982b2ded815e7673e0c4ff11… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.8.43/change-log.html Thanks, TF-A LTS team

8 months, 2 weeks

1
0
0 0

Trusted Firmware-A LTS v2.10.30 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.10.30 is now available. This release contains the following patches: 24a8b776b fix(cpus): correct CVE-2024-7881 workaround and drop duplicate erratum [1] 92e6fba58 fix(cpus): remove C1-Ultra erratum 3651221 [2] 87424d940 fix(cpus): workaround for Cortex-A65AE erratum 1638571 [3] aa593870f fix(cpus): workaround for Cortex-A76 erratum 1165347 [4] 319df17be fix(cpus): workaround for Cortex-A76 erratum 1207823 [5] 89cc4cd9b fix(cpus): update revisions for Cortex-A76 erratum 1946160 [6] 3a466bf50 fix(cpus): reorder docs for Cortex-A76 erratum 1165522 [7] cdc2b3ef5 fix(cpus): correct comments for Cortex-A720 erratum 3711910 [8] [1] https://review.trustedfirmware.org/q/I6207c49486e4020f34c862ad40ec3137bd368… [2] https://review.trustedfirmware.org/q/If7ea433e4614f92333e788e3f6b366db22c92… [3] https://review.trustedfirmware.org/q/I861230de94a105fd52f9c8ef7e7551a2633c0… [4] https://review.trustedfirmware.org/q/If9817dc26d0df835d749f506de63a4f613735… [5] https://review.trustedfirmware.org/q/Ife06401f3946884872b733f98c08e61f586d8… [6] https://review.trustedfirmware.org/q/I532ce10c3037dd77e31d7df849beb578f8b5e… [7] https://review.trustedfirmware.org/q/I2e7c05d6355dfbaa69170fc098adc1f12edc6… [8] https://review.trustedfirmware.org/q/I8b070927c19c5982b2ded815e7673e0c4ff11… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.10.30/change-log.html Thanks, TF-A LTS team

8 months, 2 weeks

1
0
0 0

Trusted Firmware-A LTS v2.12.10 Release Announcement

by svc_openci_enginfra＠arm.com

8 months, 2 weeks

1
0
0 0

Re: Unable to build the ZynqMP platform with armclang when ENABLE_LTO=1.

by Taticharla, Venkata Sai

[AMD Official Use Only - AMD Internal Distribution Only] Hi Boyan, Applied the patch shared by you,and the -flto-partition error is now resolved. However, this exposes a new set of issues during the link stage related to assembly function call Trimmed out the linker error log : (.text.asm.bl31_entrypoint+0x144): undefined reference to `bl31_main' (.text.asm.el3_exit+0x30): undefined reference to `per_world_context' (.text.asm.sync_exception_handler+0x68): undefined reference to `rt_svc_descs_indices' Additionally, when we are passing the armclang assembler as part of build command,running into below errors: Error log : Makefile:970: Makefile:970: The configured AArch64 assembler could not be identified: Makefile:970: Makefile:970: '/tools/installs/arm/safety/armcc/6.16.2/bin/armasm' (via `AS` parameter) Makefile:970: Makefile:970: The following tools are supported: Makefile:970: Makefile:970: - Arm(r) Compiler for Embedded `armclang` Makefile:970: - LLVM Clang (`clang`) Makefile:970: - GNU GCC (`gcc`) Makefile:970: Makefile:970: The build system will treat this assembler as GNU GCC (`gcc`). Please let me know if this configuration is expected to work with ENABLE_LTO=1, or if additional changes (e.g., toolchain selection or linker/assembler handling) are required. Thanks for your guidance. Best regards, Venkata Sai .T .

8 months, 2 weeks

3
2
0 0

Canceled event with note: TF-A Tech Forum @ Thu Feb 5, 2026 5pm - 6pm (GMT+1) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Cancelling for this week." TF-A Tech Forum Thursday Feb 5, 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 tf-a(a)lists.trustedfirmware.org ~~//~~ Invitation from 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

8 months, 2 weeks

1
0
0 0

Unable to build the ZynqMP platform with armclang when ENABLE_LTO=1.

by Taticharla, Venkata Sai

[AMD Official Use Only - AMD Internal Distribution Only] Hello Maintainers, we are trying to build TF‑A BL31 for the ZynqMP (Cortex‑A53) platform with Arm Compiler 6 (armclang) and ENABLE_LTO=1, and I’m running into several toolchain‑related build and link issues. Setup : Platform: ZynqMP Toolchains: Arm Compiler for Embedded 6.16.2 (armclang) Xilinx AArch64 GNU tools from Vitis 2025.2 (aarch64-xilinx-elf-*) LTO is enabled in plat/xilinx/zynqmp/platform.mk via ENABLE_LTO := 1. Issues observed : With CC=armclang and AArch64 linker (GCC), the build fails with: armclang: error: unknown argument: '-flto-partition=one' This flag appears when ENABLE_LTO=1 and the linker is detected as gnu-gcc. If I keep CC=armclang and ENABLE_LTO=1 but change the linker, I get linker‑specific errors With the Arm linker (LD=armlink or LD=armclang, which invokes armlink under the hood): Fatal error: L3900U: Unrecognized option '-z'. This is due to GNU‑style -z options (and similar flags) being passed to armlink. As -z options is specific to GNU linker, a armlink style flag would address the unrecognised option but we are observing dependency on scatter files. Fatal error: L6031U: Could not open scatter description file plat/xilinx/zynqmp//scat/bl31.scat: No such file or directory Could you please help us with pointers to address the linker issues . With regards , Venkata Sai .T .

8 months, 2 weeks

2
2
0 0

Trusted Firmware-A LTS v2.14.0 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.0 is now available. This release contains the following patches: Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.0/change-log.html Thanks, TF-A LTS team

8 months, 2 weeks

1
0
0 0

Trusted Firmware-A LTS v2.8.42 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.8.42 is now available. This release contains the following patches: 38aefbb6c feat(locks): add bitlock [1] 9c3e7f5e5 feat(locks): add non-blocking spinlock_try() API [2] 8f53c3813 fix(locks): mark spin_trylock as a public function [3] 4e6f89690 fix(cpus): workaround for Neoverse V3 erratum 3696307 [4] 25e5b1c1d fix(cpus): workaround for Neoverse V3 erratum 3734562 [5] c6faff4a8 fix(cpus): workaround for Neoverse V3 erratum 3782181 [6] 30bb3c97f fix(cpus): workaround for Neoverse V3 erratum 3864536 [7] 53ff1c60d fix(cpus): workaround for Neoverse V3 erratum 3878291 [8] 2e49a84e1 fix(cpus): workaround for Neoverse-V3 erratum 3312417 [9] 0faa929e7 fix(cpus): workaround for Neoverse-V2 erratum 3442699 [10] 31dea33cd fix(cpus): workaround for Neoverse-N1 erratum 3324349 [11] 7f7fd0315 fix(cpus): workaround for Neoverse-N2 erratum 3324339 [12] ca19e6c6b fix(cpus): workaround for Cortex-A76AE erratum 2753838 [13] d2df71a29 fix(cpus): workaround for Cortex-X2 erratum 3888122 [14] 4560e9174 fix(cpus): workaround for Cortex-X2 erratum 4302969 [15] 68235dd1a fix(cpus): workaround for Neoverse-V2 erratum 3888126 [16] 90cca3145 fix(cpus): workaround for Neoverse-V2 erratum 4302968 [17] c8394c43f fix(cpus): workaround for Cortex-X3 erratum 3888125 [18] 54d8e4697 fix(cpus): workaround for Cortex-X3 erratum 4302966 [19] 23b9d9707 refactor(cpus): reorder the errratum build flag for Neoverse-N2 [20] 587401fa7 fix(cpus): workaround for Neoverse-N2 erratum 3888123 [21] 4079faf67 fix(cpus): workaround for Neoverse-N2 erratum 4302970 [22] 510a6e759 fix(cpus): workaround for Neoverse-N2 erratum 2138953 [23] 2de362cd8 refactor(cpus): make errata reporting more generic [24] 5f0cdb5e7 perf(cpus): reduce the footprint of errata reporting [25] 429e67fb5 fix(cpus): enable Neoverse-V2 external LLC support [26] [1] https://review.trustedfirmware.org/q/I3eb0f29bbccefe6c0f69061aa701187a6364d… [2] https://review.trustedfirmware.org/q/I9483206952d1a34dc245ebf69e80c3645b658… [3] https://review.trustedfirmware.org/q/Id264a36490707a9377a221ed2b5bd27ca90bf… [4] https://review.trustedfirmware.org/q/If274749621549356e41485d0bf09682281df3… [5] https://review.trustedfirmware.org/q/Ib3c35c7e619e6a836c974b7016bb6a4d66da4… [6] https://review.trustedfirmware.org/q/Icfa463cf4888bd48f16a218e7ad399528feca… [7] https://review.trustedfirmware.org/q/If4b20d941d628b92748b14d027b8127f74005… [8] https://review.trustedfirmware.org/q/I0ebab877b6481a18bec963b95cf2f37c97d8d… [9] https://review.trustedfirmware.org/q/I78a7682cbdf3dbc4c31fcca8cbd892350b998… [10] https://review.trustedfirmware.org/q/I38edc6ba445223091c3933cbca35b56db491c… [11] https://review.trustedfirmware.org/q/I1f142027ed73135d78c368be926072c2f73ea… [12] https://review.trustedfirmware.org/q/I6b023279816005cfa459bc6947f60b1a3c0f2… [13] https://review.trustedfirmware.org/q/I338834a21c14879faee5280876a59153d549c… [14] https://review.trustedfirmware.org/q/I368cfdd216ea5875b81640415ff71b15f46ea… [15] https://review.trustedfirmware.org/q/I6c5de5843f2199fa697f8336558fa56a87ee8… [16] https://review.trustedfirmware.org/q/I4068aa73d38a70c00d66bb894169be2659d67… [17] https://review.trustedfirmware.org/q/I42b27e19d61a7f9c57efe1b5f5336d165eb98… [18] https://review.trustedfirmware.org/q/I5c01dfcffc6e56163aba03428e21fedee8cc7… [19] https://review.trustedfirmware.org/q/I284ee7fe611c4c9861696fde62f796e6fae6d… [20] https://review.trustedfirmware.org/q/Ifb736adf8f06bf6202784bdeac51c02512519… [21] https://review.trustedfirmware.org/q/I6240d263fb5d153721b5b84a37df2f24e3d02… [22] https://review.trustedfirmware.org/q/I2436b11a36be204d549522f1176fcd49658c0… [23] https://review.trustedfirmware.org/q/Ie465328e87754a1ec511a2f77243b4b0b0913… [24] https://review.trustedfirmware.org/q/I83710d8475a4a55046cf2eb6d16cd27b8ef0f… [25] https://review.trustedfirmware.org/q/I215a84bd2c91e33703349c41fc59f654f7764… [26] https://review.trustedfirmware.org/q/I9582c7405db6862e77db240822e241d408296… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.8.42/change-log.html Thanks, TF-A LTS team

8 months, 3 weeks

1
0
0 0

Trusted Firmware-A LTS v2.10.29 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.10.29 is now available. This release contains the following patches: 0876588cd feat(locks): add bitlock [1] ee14acb14 feat(locks): add non-blocking spinlock_try() API [2] 7f53a3bcf fix(locks): mark spin_trylock as a public function [3] 528516d6e refactor(cpus): make errata reporting more generic [4] d70578f82 perf(cpus): reduce the footprint of errata reporting [5] 3eb1d91fc fix(cpus): enable Neoverse-V2 external LLC support [6] 3759bec84 fix(security): add workaround for CVE-2025-0647 [7] cc3fb61cf fix(security): add CVE-2025-0647 for Cortex-A710 [8] ca4573799 fix(security): add CVE-2025-0647 for Cortex-X2 [9] b5c1f67ad fix(security): add CVE-2025-0647 for Cortex-X3 [10] c29605d74 fix(security): add CVE-2025-0647 for Cortex-X4 [11] 023107645 fix(security): add CVE-2025-0647 for Cortex-X925 [12] 79cc92f6f fix(security): add CVE-2025-0647 for Neoverse-N2 [13] 5573859bc fix(security): add CVE-2025-0647 for Neoverse-V2 [14] 722fa1ee2 fix(security): add CVE-2025-0647 for Neoverse-V3 [15] 387e7e470 fix(security): add CVE-2025-0647 for C1-Ultra [16] [1] https://review.trustedfirmware.org/q/I3eb0f29bbccefe6c0f69061aa701187a6364d… [2] https://review.trustedfirmware.org/q/I9483206952d1a34dc245ebf69e80c3645b658… [3] https://review.trustedfirmware.org/q/Id264a36490707a9377a221ed2b5bd27ca90bf… [4] https://review.trustedfirmware.org/q/I83710d8475a4a55046cf2eb6d16cd27b8ef0f… [5] https://review.trustedfirmware.org/q/I215a84bd2c91e33703349c41fc59f654f7764… [6] https://review.trustedfirmware.org/q/I9582c7405db6862e77db240822e241d408296… [7] https://review.trustedfirmware.org/q/I5e7589afbeb69ebb79c01bec80e29f572aff3… [8] https://review.trustedfirmware.org/q/I522dedfffd3108f7a94df1ce2cabd742ce682… [9] https://review.trustedfirmware.org/q/Idba607340d944a6387759c856e8eacc967e0e… [10] https://review.trustedfirmware.org/q/Ic276befafc1ca0b456826532437ca453eb771… [11] https://review.trustedfirmware.org/q/I585a7ea516515fe16a3eca907695728068cef… [12] https://review.trustedfirmware.org/q/I4c1ac2be3620566813c90f5815ffcc7205bb5… [13] https://review.trustedfirmware.org/q/I366c2683cca22403d33f0761487e1ffa62e96… [14] https://review.trustedfirmware.org/q/I7ec215a9dd168eb045366b589a02b54148f58… [15] https://review.trustedfirmware.org/q/Ic52ad93474c5f81e01eb4839ece726c84c334… [16] https://review.trustedfirmware.org/q/I506007ec8702b183e377be50eede72d6803b3… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.10.29/change-log.html Thanks, TF-A LTS team

8 months, 3 weeks

1
0
0 0

Proposal: Introduction of a standardized SMC Argument Validation Framework

by Sandrine Bailleux

Hi all, I am sending the email below on behalf on Kenneth Kabogo, who unfortunately is facing issues with the mailing list. Regards, Sandrine Afsa ---- Dear TF-A Maintainers, I am proposing the introduction of a standardized SMC Argument Validation Framework into the TF-A codebase. Over the past several weeks of security auditing across multiple platform ports, I have identified a recurring architectural failure mode termed "Privilege-Blind Forwarding" (PBF). This occurs when an EL3 handler receives a non-secure physical address and forwards it to a secure memory operation without re-validating the range against the platform's current security state (GPT/RMM). Furthermore, there is a widespread Structural TOCTOU (Double-Fetch) vulnerability in many SiP ports where handlers validate arguments but later re-fetch them from non-secure memory, allowing a malicious caller to swap addresses mid-execution. The proposed framework addresses these via an Atomic Shadow-Copy design pattern, requiring all SMC arguments to be unmarshaled into EL3 registers/memory once before validation. The 3-part prototype and migration guide are available for review on Gerrit: Framework Hardening (Core Logic): https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/47441 Architectural Guidance (Documentation): https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/47465 Arm Platform Demonstration (Migration Guide): https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/47466 I look forward to the community's feedback on this architectural shift. Best regards, Kenneth Kabogo

8 months, 3 weeks

1
0
0 0

New Defects reported by Coverity Scan for ARM-software/arm-trusted-firmware

by scan-admin＠coverity.com

Hi, Please find the latest report on new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. 3 new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 3 of 3 defect(s) ** CID 501374: Integer handling issues (INTEGER_OVERFLOW) /drivers/arm/sfcp/sfcp_core/sfcp_link_hal.c: 308 in mhu_send_signal_poll_loop() _____________________________________________________________________________________________ *** CID 501374: Integer handling issues (INTEGER_OVERFLOW) /drivers/arm/sfcp/sfcp_core/sfcp_link_hal.c: 308 in mhu_send_signal_poll_loop() 302 mhu_get_num_mhu_channels(mhu_recv_device, type); 303 uint32_t mhu_err; 304 uint32_t send_signal; 305 uint32_t recv_signal; 306 307 /* Signal using the last channel */ >>> CID 501374: Integer handling issues (INTEGER_OVERFLOW) >>> Expression "send_num_channels - 1U", where "send_num_channels" is known to be equal to 0, underflows the type of "send_num_channels - 1U", which is type "unsigned int". 308 mhu_err = mhu_channel_send(mhu_send_device, send_num_channels - 1, 309 MHU_NOTIFY_VALUE, type); 310 if (mhu_err != 0) { 311 return mhu_err; 312 } 313 ** CID 501373: Integer handling issues (INTEGER_OVERFLOW) /drivers/arm/sfcp/sfcp_core/sfcp_link_hal.c: 379 in mhu_message_is_available() _____________________________________________________________________________________________ *** CID 501373: Integer handling issues (INTEGER_OVERFLOW) /drivers/arm/sfcp/sfcp_core/sfcp_link_hal.c: 379 in mhu_message_is_available() 373 { 374 const uint32_t num_channels = 375 mhu_get_num_mhu_channels(mhu_recv_device, type); 376 uint32_t mhu_err; 377 uint32_t value; 378 >>> CID 501373: Integer handling issues (INTEGER_OVERFLOW) >>> Expression "num_channels - 1U", where "num_channels" is known to be equal to 0, underflows the type of "num_channels - 1U", which is type "unsigned int". 379 mhu_err = mhu_channel_receive_device_receive( 380 mhu_recv_device, num_channels - 1, &value, type); 381 if (mhu_err != 0) { 382 return mhu_err; 383 } 384 ** CID 501372: Integer handling issues (INTEGER_OVERFLOW) /drivers/arm/sfcp/sfcp_core/sfcp_link_hal.c: 359 in mhu_recv_signal_poll_loop() _____________________________________________________________________________________________ *** CID 501372: Integer handling issues (INTEGER_OVERFLOW) /drivers/arm/sfcp/sfcp_core/sfcp_link_hal.c: 359 in mhu_recv_signal_poll_loop() 353 return mhu_err; 354 } 355 } 356 357 /* Wait for next sender transfer */ 358 do { >>> CID 501372: Integer handling issues (INTEGER_OVERFLOW) >>> Expression "recv_num_channels - 1U", where "recv_num_channels" is known to be equal to 0, underflows the type of "recv_num_channels - 1U", which is type "unsigned int". 359 mhu_err = mhu_channel_receive_device_receive( 360 mhu_recv_device, recv_num_channels - 1, &recv_signal, 361 type); 362 if (mhu_err != 0) { 363 return mhu_err; 364 } ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/arm-software-arm-trusted-firmware?tab=ov…

8 months, 3 weeks

1
0
0 0

Trusted Firmware-A LTS v2.10.28 Release Announcement

by svc_openci_enginfra＠arm.com

9 months

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Jan 22, 2026 5pm - 6pm (GMT+1) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Cancelling as no topic for this instance. Thanks." TF-A Tech Forum Thursday Jan 22, 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 tf-a(a)lists.trustedfirmware.org ~~//~~ Invitation from 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

9 months

1
0
0 0

Trusted Firmware-A LTS v2.12.9 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.12.9 is now available. This release contains the following patches: 78fb9b745 fix(security): fix spectre bhb loop count for Cortex-A720 [1] 6d19bed6a fix(security): fix Cortex-A715 CVE-2022-23960 [2] dd0d59764 fix(security): fix Cortex-X3 CVE-2022-23960 [3] d69858d6e fix(security): fix Neoverse V2 CVE-2022-23960 [4] f1b4da3e6 fix(security): remove CVE_2022_23960 Cortex-X4 [5] 9afe25a13 fix(security): remove CVE_2022_23960 Neoverse V3 [6] b75f2db65 fix(security): remove CVE_2022_23960 Cortex-A720 [7] 6c535b5ae feat(cpufeat): do feature detection on secondary cores too [8] b173b7948 fix(cpufeat): do feature detection before feature enablement [9] 0df7d4ca0 fix(security): add clrbhb support [10] ed331c19c fix(cpus): workaround for Cortex-A715 erratum 2409570 [11] 214d51629 fix(cpus): workaround for Cortex-A715 erratum 2376701 [12] 3f73a85fb fix(cpus): workaround for Cortex-A715 erratum 3711916 [13] 71d033c7b fix(cpus): workaround for Cortex-A76AE erratum 1931427 [14] bfe756d61 fix(cpus): workaround for Cortex-A76AE erratum 1931435 [15] d24cf8d8f fix(cpus): workaround for Cortex-A76AE erratum 1969401 [16] 8b11b602c fix(cpus): workaround for Cortex-A76AE erratum 2371140 [17] f5daa76a2 fix(build): set ERRATA_SPECULATIVE_AT after platform.mk [18] ef2975fbe fix(cpus): workaround for Cortex-A65 erratum 1179935 [19] 655417b85 fix(cpus): workaround for Cortex-A65 erratum 1227419 [20] bf539177b fix(cpus): workaround for Cortex-A65 erratum 1541130 [21] aad5e748c fix(cpus): workaround for Cortex-A725 erratum 2874943 [22] 58130aca2 fix(cpus): workaround for Cortex-A725 erratum 2936490 [23] d3771e5eb fix(cpus): workaround for Cortex-A725 erratum 3711914 [24] a5dc91815 fix(cpus): workaround for Cortex-A725 erratum 3456106 [25] f557bb983 docs(security): add CVE-2024-5660 and CVE-2024-7881 reference links [26] 98efb2cdd fix(security): update Cortex-X4 fix version for CVE-2024-7881 [27] 53b539727 fix(security): update Neoverse-V3/V3AE fix version for CVE-2024-7881 [28] cd24fc78d fix(security): update Cortex-X3 fix version for CVE-2024-7881 [29] 03b289bd5 fix(security): update Neoverse-V2 fix version for CVE-2024-7881 [30] d2e5cb077 docs(security): update CVE-2024-7881 affected CPU revisions [31] 5aa4bb35a fix(cpus): register ARCH_WORKAROUND_3 for Neoverse V2 [32] c462d3e26 fix(cpus): workaround for Cortex-A710 erratum 3324338 [33] 17f11f645 fix(cpus): workaround for Cortex-X2 erratum 3324338 [34] c5af478c0 fix(cpus): workaround for Cortex-A715 erratum 3456084 [35] 58a6ddd23 fix(cpus): workaround for Cortex-A720 erratum 3456091 [36] 5bbe15b28 fix(fvp): avoid stack usage in check_cpupwrctrl_el1_is_available() [37] [1] https://review.trustedfirmware.org/q/Ib6862dbed55e5ffcd0fcd58b45a88cf925c54… [2] https://review.trustedfirmware.org/q/Ib6b704733e474824772cb27bd048b1e179d90… [3] https://review.trustedfirmware.org/q/I3d46fa70c80129ca0085d8245ee013f11a884… [4] https://review.trustedfirmware.org/q/I859012281fc67243f050d27e364f27434389c… [5] https://review.trustedfirmware.org/q/I23f5fa748377a920340b3c5a6584ccfadeea9… [6] https://review.trustedfirmware.org/q/I13b27c04c3da5ec80fa79422b4ef4fee64738… [7] https://review.trustedfirmware.org/q/I3c68b5f5d85ede37a6a039369de8ed2aa9205… [8] https://review.trustedfirmware.org/q/Iee4955714685be9ae6a017af4a6c284e835ff… [9] https://review.trustedfirmware.org/q/I47f05a9f01321e011623083afb638552311ed… [10] https://review.trustedfirmware.org/q/Ie6e56e96378503456a1617d5e5d51bc64c2e0… [11] https://review.trustedfirmware.org/q/Id9429831525b842779d7b7e60f103c93be4ac… [12] https://review.trustedfirmware.org/q/Idcd2a07d269d55534dc5faa59c454d37426f2… [13] https://review.trustedfirmware.org/q/Iad149a2c02a804b3f4f0f2f5b89e866675cb4… [14] https://review.trustedfirmware.org/q/I31566838f894372e5627abda8b0bea1505f11… [15] https://review.trustedfirmware.org/q/I1baba8752f5f2e2ab5c873030e1f00cbb8cf1… [16] https://review.trustedfirmware.org/q/I893452450d430833e6c5a8e33a1e37b708218… [17] https://review.trustedfirmware.org/q/Id65846bebde1a0911ba11956202d0d255d3c8… [18] https://review.trustedfirmware.org/q/I221dab39c417531c5a148886d3e29709ba8b5… [19] https://review.trustedfirmware.org/q/Ie59a4897f849269a590d8fa2d25cceab5f2cb… [20] https://review.trustedfirmware.org/q/I42371e7d53fce3a7e085bf0b348f080fa323f… [21] https://review.trustedfirmware.org/q/I72498f60f8449193ed4b5b2a9e7a08530e786… [22] https://review.trustedfirmware.org/q/I686bbde8756d52afee92097ec05b97138b550… [23] https://review.trustedfirmware.org/q/I9833f8831ba3735a94763791a65be11b95c00… [24] https://review.trustedfirmware.org/q/If3b9d3a0f495b3a172d3e6e5ca7afa8c30aeb… [25] https://review.trustedfirmware.org/q/I10d1e8cb4da19ba4101a5617245ff75866707… [26] https://review.trustedfirmware.org/q/Ia3c003d5c359f101f230fbd54845f61117456… [27] https://review.trustedfirmware.org/q/Iae84f26fdce96a61fdc942b7595ccf8b9c778… [28] https://review.trustedfirmware.org/q/If3e2989a4b5a5c68dc12e23978b226c73f21b… [29] https://review.trustedfirmware.org/q/Ia1ff75602a0dfa758a223549d92ea87543fa4… [30] https://review.trustedfirmware.org/q/I1ae196fa8ce4579524faba4916f631e7c4db3… [31] https://review.trustedfirmware.org/q/Iad109561a144169fd3805c179a4f8e3bfdd59… [32] https://review.trustedfirmware.org/q/I8c08c26e0b7c268772d75d36d759564a7d67c… [33] https://review.trustedfirmware.org/q/I9325f3715f4fa17bfb7ded9d5c69c59645f65… [34] https://review.trustedfirmware.org/q/Ibbe55a55bd6cf5e159dab92a78ecb55c5a4d7… [35] https://review.trustedfirmware.org/q/Ie3f2b46051539cdebc151c46f80045a7156e0… [36] https://review.trustedfirmware.org/q/Ia22a0d6bb98d1a0edb11d2469beab22c7f7ab… [37] https://review.trustedfirmware.org/q/I920e32c34bddf86a1dbf05b7115026413483b… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.12.9/change-log.html Thanks, TF-A LTS team

9 months, 1 week

1
0
0 0

TF-A Tech Forum Jan 22nd 10.00am UK -Part II Scaling Hafnium for advanced mobile OS architectures

by Olivier Deprez

(re-sending as previous invitation got lost) Hi, As follow up to the last session on Nov 13th 2025 [1], a new TF-A Tech Forum session with the topic 'Scaling Hafnium for advanced mobile OS architectures' will be held on Jan 22nd 2026 10.00am. Regards, Olivier. [1] https://www.trustedfirmware.org/meetings/tf-a-technical-forum/ Scaling Hafnium for advanced mobile OS architectures - Presented by Jack Suann Trusted Firmware is inviting you to a scheduled Zoom meeting. Topic: TF-A Tech Forum 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 TF-A Tech Forum Jan 22nd 10.00am -Part II Scaling Hafnium for advanced mobile OS architectures Thursday Jan 22, 2026 ⋅ 11am – 12pm 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… Hi, As follow up to the last session on Nov 13th 2025 [1], a new TF-A Tech Forum session with the topic'Scaling Hafnium for advanced mobile OS architectures' will be held on Jan 22nd 2026 10.00am. Regards,Olivier. [1] https://www.trustedfirmware.org/meetings/tf-a-technical-forum/ Scaling Hafnium for advanced mobile OS architectures - Presented by Jack Suann PDF Presentation Video Recording (Access Password: *PIs1^BD) Trusted Firmware is inviting you to a scheduled Zoom meeting.Topic: TF-A Tech ForumJoin 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 tf-a(a)lists.trustedfirmware.org

9 months, 1 week

1
0
0 0

New Defects reported by Coverity Scan for ARM-software/arm-trusted-firmware

by scan-admin＠coverity.com

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. New defect(s) Reported-by: Coverity Scan Showing 1 of 1 defect(s) ** CID 501209: Control flow issues (DEADCODE) /lib/xlat_tables_v2/xlat_tables_core.c: 613 in xlat_tables_map_region() _____________________________________________________________________________________________ *** CID 501209: Control flow issues (DEADCODE) /lib/xlat_tables_v2/xlat_tables_core.c: 613 in xlat_tables_map_region() 607 608 table_base[table_idx] = 609 xlat_desc(ctx, (uint32_t)mm->attr, table_idx_pa, 610 level); 611 if (is_feat_morello_supported()) { 612 if (mm->attr & MT_CAP_LD_ST_TRACK) { >>> CID 501209: Control flow issues (DEADCODE) >>> Execution cannot reach this statement: "table_base[table_idx] |= 0x...". 613 table_base[table_idx] |= (SC_BIT | LC0_BIT); 614 } 615 } 616 617 } else if (action == ACTION_CREATE_NEW_TABLE) { 618 uintptr_t end_va; ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/arm-software-arm-trusted-firmware?tab=ov…

9 months, 1 week

1
0
0 0

Trusted Firmware-A LTS v2.10.27 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.10.27 is now available. This release contains the following patches: fb0ca7ca1 build(npm): adhere to Husky deprecation notice [1] 17a8aec49 fix(cpus): workaround for Cortex-A76AE erratum 1931427 [2] fc5e6eeee fix(cpus): workaround for Cortex-A76AE erratum 1931435 [3] 918cb2542 fix(cpus): workaround for Cortex-A76AE erratum 1969401 [4] 6f78d7d29 fix(cpus): workaround for Cortex-A76AE erratum 2371140 [5] d5424f6d8 fix(build): set ERRATA_SPECULATIVE_AT after platform.mk [6] 659e46683 fix(cpus): workaround for Cortex-A65 erratum 1179935 [7] 909b29568 fix(cpus): workaround for Cortex-A65 erratum 1227419 [8] 42777038e fix(cpus): workaround for Cortex-A65 erratum 1541130 [9] 948f017ea fix(cpus): workaround for Cortex-A725 erratum 2874943 [10] 5ff59225e fix(cpus): workaround for Cortex-A725 erratum 2936490 [11] d2ab008e2 fix(cpus): workaround for Cortex-A725 erratum 3711914 [12] d0d0d0285 fix(cpus): workaround for Cortex-A725 erratum 3456106 [13] [1] https://review.trustedfirmware.org/q/I763a462b2a0da7852696f874df970810a2b01… [2] https://review.trustedfirmware.org/q/I31566838f894372e5627abda8b0bea1505f11… [3] https://review.trustedfirmware.org/q/I1baba8752f5f2e2ab5c873030e1f00cbb8cf1… [4] https://review.trustedfirmware.org/q/I893452450d430833e6c5a8e33a1e37b708218… [5] https://review.trustedfirmware.org/q/Id65846bebde1a0911ba11956202d0d255d3c8… [6] https://review.trustedfirmware.org/q/I221dab39c417531c5a148886d3e29709ba8b5… [7] https://review.trustedfirmware.org/q/Ie59a4897f849269a590d8fa2d25cceab5f2cb… [8] https://review.trustedfirmware.org/q/I42371e7d53fce3a7e085bf0b348f080fa323f… [9] https://review.trustedfirmware.org/q/I72498f60f8449193ed4b5b2a9e7a08530e786… [10] https://review.trustedfirmware.org/q/I686bbde8756d52afee92097ec05b97138b550… [11] https://review.trustedfirmware.org/q/I9833f8831ba3735a94763791a65be11b95c00… [12] https://review.trustedfirmware.org/q/If3b9d3a0f495b3a172d3e6e5ca7afa8c30aeb… [13] https://review.trustedfirmware.org/q/I10d1e8cb4da19ba4101a5617245ff75866707… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.10.27/change-log.html Thanks, TF-A LTS team

9 months, 1 week

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

TF-A