Hello,
I am thrilled to announce the support of new Clan/LLVM toolchain, freely available here: https://github.com/ARM-software/LLVM-embedded-toolchain-for-Arm. This extends a suite of powerful tools designed to enhance your development experience and boost productivity.
Key Features:
* Offers Clang frontend
* Available for Linux, Windows and macOS
* Builds TF-M binaries for all Arm targets
* Secure side built without libc and picolib libraries, while both are available to Bootloader and Non-Secure side
Important notes:
* Floating point support is not verified
* MVE is not supported yet
* This has been verified with version v18.1.3 of the toolchain.
We're excited for you to try out the new toolchain support and look forward to your feedback. The use of the toolchain_CLANG.cmake is the same as all other toolchains.
I plan to present the new toolchain and compare it with the existing tools in one of the upcoming TF-M forums. Meanwhile I encourage the platform owners to include the new toolchain support using arm platforms as a reference. The relevant changes are in this chain:
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/34351
There is ongoing discussion on the best name for the toolchain to avoid possible confusion. Should it be Clang as now, LLVM, or even LLVMClang? Please share your opinion.
Thanks, and best regards,
Anton.
Hello,
The next Technical Forum is planned on Thursday, Sep 12 at 7:00-8:00 UTC (East time zone).
Please reply on this email with your proposals for agenda topics.
Recording and slides of previous meetings are here:
https://www.trustedfirmware.org/meetings/tf-m-technical-forum/
Best regards,
Anton
Hello all,
Today we have upgraded the version of Arm GNU Toolchain on the TF-M OpenCI to version 14.3rel1. We ask that you please update your local version to match this to allow for ongoing compatibility.
If you have any questions or issues, please do not hesitate to let me know.
Thanks,
Matt Dalzell - Arm
FYI
From: Saheer Babu via Tf-openci <tf-openci(a)lists.trustedfirmware.org>
Date: Wednesday, 10 September 2025 at 15:17
To: tf-openci(a)lists.trustedfirmware.org <tf-openci(a)lists.trustedfirmware.org>
Subject: [Tf-openci] CI infrastructure scheduled maintenance: 12th Sep 2025
Hi all,
We will be performing upgrade of the clusters hosting review.trustedfirmware.org and ci.trustedfirmware.org on Friday, 12th Sep 2025 at 16:00 GMT+1.
During this maintenance window, both services will be unavailable for approximately 4 hours.
A follow-up email will be sent once the services are fully restored.
Best regards,
Saheer
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
--
Tf-openci mailing list -- tf-openci(a)lists.trustedfirmware.org
To unsubscribe send an email to tf-openci-leave(a)lists.trustedfirmware.org
Hello,
We've identified an issue with the TF-M versioning: it reports the wrong version from Git tags (showing v2.1.3 instead of the correct v2.2.1). As a temporary workaround, please set the version manually. We're working on a fix and will share updates as soon as possible.
Best regards,
Anton Komlev
Hello,
I’m trying to enable the secure debug feature and configured TF-M as
follows:
1) Configuration
# ./config/config_base.cmake
set(PLATFORM_PSA_ADAC_SECURE_DEBUG TRUE CACHE BOOL "Whether to use psa-adac
secure debug.")
set(PLATFORM_PSA_ADAC_SOURCE_PATH "DOWNLOAD" CACHE PATH "Path to source dir
of psa-adac.")
set(PLATFORM_PSA_ADAC_VERSION "819a254" CACHE STRING "The version of
psa-adac to use.")
2) Build result (error)
-- Populating libpsaadac
-- Configuring done (0.0s)
-- Generating done (0.0s)
-- Build files have been written to:
/home/jkpark/ADP620/tf-m/cmake_build/rdv3r1/0/lib/ext/libpsaadac-subbuild
[1/9] Creating directories for 'libpsaadac-populate'
[1/9] Performing download step (git clone) for 'libpsaadac-populate'
Cloning into 'libpsaadac-src'...
HEAD is now at 819a254 ADAC: Check return value of
psa_adac_generate_challenge
[2/9] Performing update step for 'libpsaadac-populate'
e*rror: pathspec '819a254;;' did not match any file(s) known to git *
*CMake Error at .../libpsaadac-populate-gitupdate.cmake:188
(execute_process): *
* execute_process failed command indexes: *
* 1: "Child return code: 1" *
3) Generated ExternalProject invocation
/cmake_build/rdv3r1/0/lib/ext/libpsaadac-subbuild/CMakeLists.txt
include(ExternalProject)
ExternalProject_Add(libpsaadac-populate
"UPDATE_DISCONNECTED" "False"
"GIT_REPOSITORY" "https://git.trustedfirmware.org/shared/psa-adac.git"
"EXTERNALPROJECT_INTERNAL_ARGUMENT_SEPARATOR"
"GIT_TAG" "819a254" "" ""
SOURCE_DIR
"/home/jkpark/ADP620/tf-m/cmake_build/rdv3r1/0/lib/ext/libpsaadac-src"
BINARY_DIR
"/home/jkpark/ADP620/tf-m/cmake_build/rdv3r1/0/lib/ext/libpsaadac-build"
CONFIGURE_COMMAND ""
BUILD_COMMAND ""
INSTALL_COMMAND ""
TEST_COMMAND ""
USES_TERMINAL_DOWNLOAD YES
USES_TERMINAL_UPDATE YES
USES_TERMINAL_PATCH YES
)
*Questions *
*https://git.trustedfirmware.org/shared/psa-adac.git
<https://git.trustedfirmware.org/shared/psa-adac.git> *
*What is causing the tag-related error when using the repository at
https://git.trustedfirmware.org/shared/psa-adac.git
<https://git.trustedfirmware.org/shared/psa-adac.git> *
?
Environment
Path: /home/jkpark/ADP620/tf-m/cmake_build/rdv3r1/0/...
Platform: RDV3R1
I would be grateful for any advice or pointers from anyone familiar with
this.
Thank you!
Hi all,
TF-M has recently introduced Python packaging for its modules and
scripts. If you’re building the latest TF-M mainline, you’ll need to
install them by running the following command from the root of the TF-M
repository (using a virtual environment is recommended):
```
pip install .
```
or
```
# `-e` installs modules and scripts in editable/development mode i.e.
source edits are automatically reflected in your dev environment
pip install -e .
```
NOTE: You'll have to re-run the above command every time a new module is
added, module is renamed or a new dependency is added.
The documentation [1] has been updated with more details. In addition,
new guidelines are now available [2] for adding new scripts and modules.
Thank you.
Best regards,
Mudit Sharma
[1]:
https://trustedfirmware-m.readthedocs.io/en/latest/getting_started/index.ht…
[2]:
https://trustedfirmware-m.readthedocs.io/en/latest/contributing/python_scri…
