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

From: Bohdan.Hunko--- via TF-M <tf-m@lists.trustedfirmware.org>
Date: Monday, 2026. January 26. at 16:29
To: tf-m@lists.trustedfirmware.org <tf-m@lists.trustedfirmware.org>
Subject: [TF-M] IAR build seems to be broken

Hi all

I see that https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/44534 added tfm_s_build_flags for all the compilers except IAR

After version update - in our CI we see:

Fatal error[Ms007]: could not open file "libtfm_s_build_flags.a"

Is this intentional change or IAR file was just missed and the change should also be added for IAR?

Best regards,

Bohdan Hunko

Cypress Semiconductor Ukraine LLC

Senior Engineer

CSS ICW SW INT BFS SFW

Mobile: +380995019714
Bohdan.Hunko@infineon.com