September 2026 - TF-A - lists.trustedfirmware.org

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

2 weeks, 3 days

2
1
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

1 month

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…

1 month

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

1 month

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

1 month

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

1 month

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…

1 month

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

1 month, 1 week

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

1 month, 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 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…

1 month, 1 week

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

TF-A September 2026