Thanks Antonio,
I now think I know what the dependency on CMSIS 5.2.0 is.
In tfm_id_mngr_dummy.c, which seems to have been removed recently, there are a couple of calls into private functions of the RTX5 library which are declared "static" in the later versions of CMSIS, and this causes link errors when using later versions of CMSIS.
Is there any work in progress on updating the TFM CMSIS Pack to use the updated TFM sources?
Thanks, Thomas
Den 2019-01-08 kl. 15:20, skrev Antonio De Angelis via TF-M:
Hi Thomas,
After this patch has been merged in November: http://git.trustedfirmware.org/trusted-firmware-m.git/commit/?id=2b328e94bca...
We don't have any reliance on CMSIS 5.2.0 internals anymore and we use only the public CMSIS interface in the Non-Secure API. As a result, I don't see any reason now that stops us from using newer versions of CMSIS. I have actually tried to build TF-M and run regression using CMSIS 5.3.0 and it works as expected. Can you try to see if you're able to build with CMSIS 5.5.0 as well? In case you see issues, I should be able to have a look to understand them better and come with a solution.
Thanks, Antonio
-----Original Message----- From: TF-M tf-m-bounces@lists.trustedfirmware.org On Behalf Of Thomas Törnblom via TF-M Sent: 07 January 2019 11:48 To: tf-m@lists.trustedfirmware.org Subject: [Tf-m] ARM.TFM CMSIS pack questions
Greetings!
I am working on adding support for IAR Embedded Workbench for ARM (EWARM) to the ARM.TFM.1.1.0 CMSIS Pack and in the ReadMe.txt file in the pack there is a list of limitations, of which I would like an explanation for the following:
2. The Non-Secure API supports CMSIS 5.2.0 version only.
What specifically requires version 5.2.0 that would not work with a later version?
The problem is that I've run across some issues that needs fixing in the ARM.CMSIS pack as well, so I've fixed these in the upcoming 5.5.0 version and would like to know what the issues are using this version with TFM?
Thanks, /Thomas