July 2025 - TF-A - lists.trustedfirmware.org

Firmware-A v2.13 release code freeze notification

by Olivier Deprez

Hi All, The next release of the Firmware-A bundle of projects tagged v2.13 has an expected code freeze date of May, 2nd 2025. In order to accommodate the Linaro connect event occurring during the week of May 12th we may extend the release completion date up until the week of May 26th. v2.13 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. Regards, Olivier.

16 hours, 20 minutes

1
2
0 0

Does spmd_group0_interrupt_handler_nwd() need to take into account handling of special INTIDs?

by YANG Jun

Hi there, Do spmd_group0_interrupt_handler_nwd() and spmd_handle_group0_intr_swd() need to take into account handling of special INTIDs? Like ehf_el3_interrupt_handler(): /* * Acknowledge interrupt. Proceed with handling only for valid interrupt * IDs. This situation may arise because of Interrupt Management * Framework identifying an EL3 interrupt, but before it's been * acknowledged here, the interrupt was either deasserted, or there was * a higher-priority interrupt of another type. */ intr_raw = plat_ic_acknowledge_interrupt(); intr = plat_ic_get_interrupt_id(intr_raw); if (intr == INTR_ID_UNAVAILABLE) return 0; Best Regards, Joe Yang

2 months, 1 week

3
3
0 0

Re: Does spmd_group0_interrupt_handler_nwd() need to take into account handling of special INTIDs?

by Yang Joe

Hi Madhukar, Yes, I have encountered a spurious ID(1023) issue once. Best Regards, Joe Yang

2 months, 2 weeks

1
0
0 0

Trusted Firmware-A LTS v2.8.35 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.8.35 is now available. This release contains the following patches: 0aaca5da3 fix(cpus): workaround for Cortex-A710 erratum 1901946 [1] b83bf0ad1 fix(cpus): workaround for Cortex-A710 erratum 1916945 [2] e26d08b8c fix(cpus): workaround for Cortex-A710 erratum 1917258 [3] ac23c6eba fix(cpus): workaround for Cortex-A710 erratum 1927200 [4] 777b7063f fix(zynqmp): workaround issue around cntpct_el0 [5] 8a48b31f3 fix(imx8mp): remove ERR050463 VPUMIX workaround [6] [1] https://review.trustedfirmware.org/q/I703f0e6ee122e44a9bc284d90f1465039e3b4… [2] https://review.trustedfirmware.org/q/I54793492c527928d7f266165a31b8613de838… [3] https://review.trustedfirmware.org/q/I1fae91a5e3a8ecea255f0f0a481bfd6196a7d… [4] https://review.trustedfirmware.org/q/I53c4aa17c1c2dc85b68f17d58f93bb1ee6b3d… [5] https://review.trustedfirmware.org/q/Ie43096bb33bb0e02c8cac07f965610b4565e1… [6] https://review.trustedfirmware.org/q/I263531c6eef44a679002cd048e71fb50c63d9… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.8.35/change-log.html Thanks, TF-A LTS team

2 months, 2 weeks

1
0
0 0

Trusted Firmware-A LTS v2.12.5 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.12.5 is now available. This release contains the following patches: df4665589 fix(zynqmp): workaround issue around cntpct_el0 [1] f005662e6 fix(imx8mp): remove ERR050463 VPUMIX workaround [2] da60f9c02 fix(cpus): workaround for Cortex-A710 erratum 1901946 [3] e3f2ee2ca fix(cpus): workaround for Cortex-A710 erratum 1916945 [4] bdb9f85e1 fix(cpus): workaround for Cortex-A710 erratum 1917258 [5] 4aa3e4c6c fix(cpus): workaround for Cortex-A710 erratum 1927200 [6] [1] https://review.trustedfirmware.org/q/Ie43096bb33bb0e02c8cac07f965610b4565e1… [2] https://review.trustedfirmware.org/q/I263531c6eef44a679002cd048e71fb50c63d9… [3] https://review.trustedfirmware.org/q/I703f0e6ee122e44a9bc284d90f1465039e3b4… [4] https://review.trustedfirmware.org/q/I54793492c527928d7f266165a31b8613de838… [5] https://review.trustedfirmware.org/q/I1fae91a5e3a8ecea255f0f0a481bfd6196a7d… [6] https://review.trustedfirmware.org/q/I53c4aa17c1c2dc85b68f17d58f93bb1ee6b3d… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.12.5/change-log.html Thanks, TF-A LTS team

2 months, 2 weeks

1
0
0 0

Trusted Firmware-A LTS v2.10.19 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.10.19 is now available. This release contains the following patches: 5a70c5221 fix(cpus): workaround for Cortex-A710 erratum 1901946 [1] d16c477c7 fix(cpus): workaround for Cortex-A710 erratum 1916945 [2] 2a571f7f2 fix(cpus): workaround for Cortex-A710 erratum 1917258 [3] bc44ad427 fix(cpus): workaround for Cortex-A710 erratum 1927200 [4] b1926f4c0 fix(zynqmp): workaround issue around cntpct_el0 [5] b200b62c2 fix(imx8mp): remove ERR050463 VPUMIX workaround [6] [1] https://review.trustedfirmware.org/q/I703f0e6ee122e44a9bc284d90f1465039e3b4… [2] https://review.trustedfirmware.org/q/I54793492c527928d7f266165a31b8613de838… [3] https://review.trustedfirmware.org/q/I1fae91a5e3a8ecea255f0f0a481bfd6196a7d… [4] https://review.trustedfirmware.org/q/I53c4aa17c1c2dc85b68f17d58f93bb1ee6b3d… [5] https://review.trustedfirmware.org/q/Ie43096bb33bb0e02c8cac07f965610b4565e1… [6] https://review.trustedfirmware.org/q/I263531c6eef44a679002cd048e71fb50c63d9… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.10.19/change-log.html Thanks, TF-A LTS team

2 months, 2 weeks

1
0
0 0

Contributing to Trusted Firmware Armv7-A and Armv8-A

by Waqas Mazhar

Hi all, Hope you are well. I have recently joined this mailing list and am quite keen to contribute to this project but don't know where to start. Currently, I am going through Trusted Firmware A Documentation <https://trustedfirmware-a.readthedocs.io/en/latest/index.html> document and Gerrit code reviews <https://review.trustedfirmware.org/q/status:open+-is:wip> to develop some initial understanding and familiarity about the project. As a first step, I am trying to understand areas where I can contribute. Is there any simple issue for me to pick? I am happy to volunteer. Looking forward to hearing from you, Waqas

2 months, 4 weeks

1
0
0 0

TF-A Tech Forum on July 10th 2025 - SMC Fuzzing

by Olivier Deprez

Hi, In the TF-A Tech Forum on July 10th 2025 Mark Dykes from Arm TF-A team will present the topic of SMC Fuzzing with the agenda: Overview of the TF-A fuzzer and its basic implementation in practice. Regards, Olivier. TF-A Tech Forum Thursday Jul 10, 2025 ⋅ 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 tf-a(a)lists.trustedfirmware.org

3 months

2
1
0 0

MISRA Compliance: Request to consider filing deviation for 11.1 (Function Pointer Conversions) in TF-A

by Dhruva Gole

Hello, Background & Justification: MISRA C:2012 Rule 11.1 forbids the conversion from a function pointer to any other type. However, in the context of TF-A, we encounter scenarios where this conversion is necessary and performed with full knowledge of the target architecture and toolchain behavior. A prominent example is in low-level platform code, such as transferring control between bootloader stages or passing function entry points for CPU/core bring-up, where the conversion is unavoidable and well-understood. One such example is the K3 PSCI driver [1] where we pass the k3_sec_entrypoint which is of type uintptr_t, to the ti_sci_proc_set_boot_cfg function where the parameter is of type uint64_t. Another place that triggered the discussions behind this MISRA C issue was the TI AM62L PSCI driver [2] that needs a 16b aligned function pointer. We don't have to go into specific case by case discussion of solving these issues, but just wanted to share example use cases of function pointer conversion. Request: I propose we formally document a project-wide MISRA C:2012 Rule 11.1 deviation, reflecting current and future usage throughout the TF-A codebase. This deviation allows us to balance MISRA objectives with the practical and architectural necessities of TF-A development. Rationale: * Conversions between function pointers and other types are essential in several parts of the TF-A codebase, not limited to one module or file. * Platform-specific code (e.g., power management, bootloader hand-offs) relies on this pattern for correct operation. References: [1] https://github.com/ARM-software/arm-trusted-firmware/blob/master/plat/ti/k3… [2] https://github.com/ARM-software/arm-trusted-firmware/blob/master/plat/ti/k3… -- Best regards, Dhruva Gole Texas Instruments Incorporated

3 months, 1 week

2
1
0 0

Context uninitialized assertion failure in xlat_tables_core for ZynqMP

by Michał Kruszewski

Hello, I want to boot Linux on ZynqMP (XCZU15EG). I follow the standard procedure. I have generated FSBL using Vitis. I have compiled bl31 (tag: xilinx-v2025.1). I have a standard boot.bif configuration looking as follows: the_ROM_image: { [bootloader] fsbl.elf [pmufw_image] pmufw.elf [destination_cpu = a53-0, exception_level= el-3, trustzone] bl31.bin [destination_cpu = a53-0, exception_level= el-2, load = 0x10000000] images/u-boot.bin } However, the bl31 reports the following error during the handoff to u-boot: ASSERT: lib/xlat_tables_v2/xlat_tables_core.c:788 BACKTRACE: START: assert 0: F_FUNCTION: 0x2880 1: F_FUNCTION: 0x4cac 2: F_FUNCTION: 0x2628 3: F_FUNCTION: 0x36e0 4: F_FUNCTION: 0x108 5: F_FUNCTION: 0xfffcd8e8 BACKTRACE: END: assert This is an assertion for context being uninitialized in the mmap_add_region_ctx function. /* Static regions must be added before initializing the xlat tables. */ assert(!ctx->initialized); Does anyone have any idea what might be wrong? Best regards, Michał Kruszewski Sent with [Proton Mail](https://proton.me/mail/home) secure email.

3 months, 1 week

2
2
0 0

2025

2024

2023

2022

2021

2020

2019

2018

TF-A July 2025