Hello All,
For your information I’m facing the same issue.
I tried to understand but no idea for the moment:
Build was ok at Dec the 18th but in January I can’t build with IAR (it is ok with GNU and CLANG)
I didn’t see this before because I mainly use GNU and build with other only before an Uptream to check all compilers are ok for Regression and PSA API tests.
Here is the error message:
"C:\TFM_H5\build_s\build-spe\CMakeFiles\tfm_s.rsp",21 Fatal error[Ms007]:
could not open file "libtfm_s_build_flags.a"
Directories searched:
C:\TFM_H5\build_s\build-spe
Fatal error detected, aborting.
Note in that case it is on STM32H5 but I also faced the same issue on other platforms.
However before in the build there is also a FAILED:
-- -------- TEST Configuration -----------------------
-- TEST_NS ON
-- TEST_S ON
-- TEST_NS_ATTESTATION ON
-- TEST_NS_CRYPTO ON
-- TEST_NS_ITS ON
-- TEST_NS_PS ON
-- TEST_NS_QCBOR OFF
-- TEST_NS_T_COSE OFF
-- TEST_NS_PLATFORM ON
-- TEST_NS_FWU ON
-- TEST_NS_IPC OFF
-- TEST_NS_SLIH_IRQ OFF
-- TEST_NS_FLIH_IRQ OFF
-- TEST_NS_MULTI_CORE OFF
-- TEST_NS_MANAGE_NSID OFF
-- TEST_NS_SFN_BACKEND ON
-- TEST_NS_FPU OFF
-- TEST_S_ATTESTATION ON
-- TEST_S_CRYPTO ON
-- TEST_S_ITS ON
-- TEST_S_PS ON
-- TEST_S_PLATFORM ON
-- TEST_S_FWU OFF
-- TEST_S_IPC OFF
-- TEST_S_SFN_BACKEND ON
-- TEST_S_FPU OFF
-- TEST_S_FIH OFF
-- ---------------------------------------------------
-- Configuring done (125.1s)
-- Generating done (2.4s)
-- Build files have been written to: C:/TFM_H5/build_s/build-spe
[6/9] Performing build step for 'TF-M'
FAILED: temp/src/TF-M-stamp/TF-M-build C:/TFM_H5/build_s/temp/src/TF-M-stamp/TF-M-build
C:\WINDOWS\system32\cmd.exe /C "cd /D C:\TFM_H5\build_s\build-spe && "C:\Program Files\CMake\bin\cmake.exe" --build ."
[1/624] Building C object secure_fw\partitions\crypto\mbedcrypto\3rdparty\everest\CMakeFiles\crypto_service_everest.dir\library\everest.o
[2/624] Building C object secure_fw\partitions\crypto\mbedcrypto\3rdparty\everest\CMakeFiles\crypto_service_everest.dir\library\x25519.o
With GNU:
-- TEST_S_SFN_BACKEND ON
-- TEST_S_FPU OFF
-- TEST_S_FIH OFF
-- ---------------------------------------------------
-- Configuring done (156.7s)
-- Generating done (3.5s)
-- Build files have been written to: C:/TFM_L56/build_s/build-spe
[6/9] Performing build step for 'TF-M'
[1/608] Building C object secure_fw/partitions/crypto/mbedcrypto/3rdparty/everest/CMakeFiles/crypto_service_everest.dir/library/x25519.o
[2/608] Building C object secure_fw/partitions/crypto/mbedcrypto/3rdparty/everest/CMakeFiles/crypto_service_everest.dir/library/everest.o
So issue seems due to :
[6/9] Performing build step for 'TF-M'
Directory content, there is no TF-M-build file
c:\TFM_H5\build_s\temp\src\TF-M-stamp\TF-M-configure
c:\TFM_H5\build_s\temp\src\TF-M-stamp\TF-M-patch
c:\TFM_H5\build_s\temp\src\TF-M-stamp\TF-M-update
c:\TFM_H5\build_s\temp\src\TF-M-stamp\TF-M-download
c:\TFM_H5\build_s\temp\src\TF-M-stamp\TF-M-mkdir
c:\TFM_H5\build_s\temp\src\TF-M-stamp\TF-M-patch-info.txt
c:\TFM_H5\build_s\temp\src\TF-M-stamp\TF-M-update-info.txt
c:\TFM_H5\build_s\temp\src\TF-M-stamp\TF-M-source_dirinfo.txt
Here is the build command:
build_H5_regression_iar_s()
{
cmake -S $TFM_work_dir_H5/tf-m-tests/tests_reg/spe -B $H5_build_s -GNinja -DTFM_PLATFORM=stm/stm32h573i_dk -DTFM_TOOLCHAIN_FILE=$H5_tfm_src/toolchain_IARARM.cmake -DCONFIG_TFM_SOURCE_PATH=$H5_tfm_src -DTEST_S=ON -DTEST_NS=ON
cmake --build $H5_build_s -- install
}
Also note:
I use main branch
It is ok on v2.2.2
Thank you.
Ronan,

Ronan GABOU | Tel: +33 1 58 07 80 19
MDG / General Purpose Microcontroller Sub-Group / Wireless Business Line / Cellular
ST online:
[www.st.com]www.st.com
online: [www.st.com]www.st.com
From: Anton Komlev via TF-M <tf-m@lists.trustedfirmware.org>
Sent: Monday, January 26, 2026 5:04 PM
To: Bohdan.Hunko@infineon.com; tf-m@lists.trustedfirmware.org; David Hazi <David.Hazi@arm.com>
Subject: [TF-M] Re: IAR build seems to be broken
Hi Bohdan,
We don’t have IAR in CI yet and I had trouble running it locally, so the assumption was that nothing needed to change for the IAR toolchain. Unfortunately, you’ve pointed out a side effect of new compiler flags targets. As David mentioned it was simply missed and can be fixed by adding dummy targets.
Hope that helps, and sorry for the trouble,
Anton
From: David Hazi via TF-M <tf-m@lists.trustedfirmware.org>
Sent: Monday, January 26, 2026 15:38
To: Bohdan.Hunko@infineon.com <Bohdan.Hunko@infineon.com>;
tf-m@lists.trustedfirmware.org <tf-m@lists.trustedfirmware.org>
Subject: [TF-M] Re: IAR build seems to be broken
Hey,
I think it is just missed. Hopefully, a dummy interface library will be enough, like it was for Armclang.
Dávid