- TF-A - lists.trustedfirmware.org

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 days, 3 hours

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 days, 6 hours

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 days, 7 hours

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

3 days, 8 hours

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

4 days, 6 hours

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…

4 days, 10 hours

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

4 days, 23 hours

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

5 days, 7 hours

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 week, 1 day

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 week, 1 day

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

TF-A