- TF-M - lists.trustedfirmware.org

Enable SPI interrupt in secure partition

by Edward Yang

Hi experts, Recently we're developing a demo based on TF-M, this demo involves using SPI module to drive a sensor by sending commands in a secure partition. And we need to enable SPI receive and send interrupt in this secure partition and the latency shall be as small as possible. I am wondering how to implement this secure interrupts. Is there any example code or instrucstions? Thanks. Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 http://www.mxic.com.cn ============================================================================ CONFIDENTIALITY NOTE: This e-mail and any attachments may contain confidential information and/or personal data, which is protected by applicable laws. Please be reminded that duplication, disclosure, distribution, or use of this e-mail (and/or its attachments) or any part thereof is prohibited. If you receive this e-mail in error, please notify us immediately and delete this mail as well as its attachment(s) from your system. In addition, please be informed that collection, processing, and/or use of personal data is prohibited unless expressly permitted by personal data protection laws. Thank you for your attention and cooperation. Macronix International Co., Ltd. =====================================================================

3 years, 10 months

2
1
0 0

'memset/memcpy/mem*' API usage in secure firmware

by Ken Liu

Hi TF-Mers, There are several versions of mem* API set in the system. At the very beginning, the whole secure firmware was put in the library model, and it is expected to be self-contained -- at least at the source level as the first step. Hence a 'tfm_mem*' API set is created for secure firmware usage. The same reason for involving 'spm_mem*' in the PSA compliance model. When we designed HAL for SPM, we noticed that SPM HAL actually run in the same domain as SPM, hence we encouraged developers to use 'spm_mem*' in SPM HAL. This brings a bit of difficulty, especially when the platform sources are shared for multiple targets, while other targets do not have 'spm_mem*' API. As 'mem*' is actually common enough (as they are fundamental API of libc), hence redefine the name is applicable only a system is highly self-contained. In our case, using 'mem*' API can bring much convenience. Hence I am thinking to let sources other than SPM use 'mem*' API, they are platform, partitions and runtime libraries. For SPM sources (under secure_fw/spm), a source-level 'spm_mem*' is kept, to keep the possibility to make SPM itself really self-contained. Now it is only source-level because 'spm_mem*' is actually forwarded to 'mem*'. I am creating a patch to change this, and want to know your opinion. Thanks. /Ken

3 years, 10 months

1
0
0 0

Any usage of environment variables in manifest lists

by Kevin Peng

Hi, Is there anyone using environment variables for the "manifest" attribute in out-of-tree manifest lists? I'm asking because I'm working to support configurable stack_size for Secure Partitions<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/15155>. In the patch the support of environment variables in manifest lists is removed<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/15155/1/tool…>. Because I have to call the CMake command configure_file to replace the stack_size symbols (CMake variables<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/15155/1/secu…> surrounded with "@") with their values. While configure_file does not recognize environment variables. If you do have environment variables in manifest list, there is an alternative: Replace the env. variables with CMake variables surrounded with "@" and set the value of the CMake variables in either config files or command line inputs. Best Regards, Kevin

3 years, 10 months

3
5
0 0

Re: Technical Forum call - May 12 Cancelled

by David Hu

Hi all, I'd like to cancel tech form in May 12 due to empty agenda. Best regards, Hu Ziji From: David Hu via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: Thursday, May 5, 2022 2:11 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - May 12 Hi, (On behalf of Anton) The next Technical Forum is planned on Thursday, May 12, 15:00-16:00 UTC (West 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, Hu Ziji

3 years, 10 months

1
0
0 0

Attestation token new spec

by Tamas Ban

Hi, the initial attestation token implementation is aligned with this specification: https://datatracker.ietf.org/doc/html/draft-tschofenig-rats-psa-token-05 This spec is still evolving and there is a newer version which changes the key values of the claims in the token: https://www.ietf.org/archive/id/draft-tschofenig-rats-psa-token-09.html#tab…<https://www.ietf.org/archive/id/draft-tschofenig-rats-psa-token-09.html%23t…> This can cause combability issues between token issuer (device) and token verifier (some remote verification service). This is an ABI change between token issuer and consumer. The breaking effect would be manifest in unaccepted IAT tokens by the verifier. On-device side I see these options to make the transition: - A build-time option could be introduced which determines which range of key numbers to use. The default value would be the new range. To not let new users pick up the old values accidentally. Existing users can notice the incompatibility issue during the integration test and adjust their build command accordingly. However, the old range would be announced as deprecated in the next TF-M release, then will be removed in the next release after. - Immediate switch over to the new range, without supporting the old range anymore. On the verification service side, an SW update can handle the transition and might be accepting both ranges for a while. I assume the verification service can be updated more easily than remote devices therefore better to handle the compatibility issue there. - Keeping the support for both ranges for the long term and letting users choose by build time. Please share your thoughts on: - Are you aware that the attestation service is used in deployed devices where this transition can cause incompatibility? - From the above list which option would you vote to support the transition? Best regards, Tamas Ban

3 years, 10 months

1
0
0 0

Under-layer runtime functions in assembly

by Ken Liu

Hi, In one of the past tech forums, we claimed that we don't encourage contribution in common logic in assembly, and one of the patches was abandoned because of this. That patch is designed to improve the memset/memcpy performance. We override these APIs in general because we want the code can be auditable. Then we provided implementations in C, but it shows these implementation does not provide good performance. We want to apply the toolchain provided versions, and looks GNU tool provides the straightest 'byte-copy' version. And armclang involves unnecessary variants which increase the code size a little (not big). Hence we provide a version with 'tiny' optimization in assembly and mark this patch an exception to the review guidelines, as these under-layer functions won't get changed frequently. We are also seeking an ideal way to apply toolchain versions. The patch is here for your review: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/13735 Thanks. /Ken

3 years, 10 months

1
0
0 0

Supporting encryption with ITS

by Vasilakis, Georgios

Hello all, I wanted to let you know that I made the PR which adds encryption on ITS files using the methodology that we discussed before. The encryption is happening in a transparent way for the user, and I tried to avoid major changes in the ITS filesystem. Please add yourself as a reviewer and provide feedback if you think that this is an interesting use case for you. https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/15096 Regards, Georgios Vasilakis

3 years, 10 months

1
0
0 0

Technical Forum call - May 12

by David Hu

Hi, (On behalf of Anton) The next Technical Forum is planned on Thursday, May 12, 15:00-16:00 UTC (West 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, Hu Ziji

3 years, 10 months

1
0
0 0

TF-M v1.6.0 release

by Anton Komlev

Hello, I am pleased to announce the new v1.6.0 released of TF-M project. New major features are: * MCUboot updated to v1.9.0. * Mbed TLS updated to v3.1.0 (Support all required PSA Crypto APIs). * Enabled Secure Function (SFN) Model Partition compliance in IPC backend. * Interrupt support (both SLIH/FLIH) for the SFN backend. * MM-IOVEC Support for the SFN backend. * The following Secure Partitions are converted to SFN model: * Protected Storage * Internal Trusted Storage * Initial Attestation * FF-M v1.1 SFN Model supported in Profile Small. * HAL Separation of Library Model and IPC/SFN backend. * FP support for Armv8.1-M Mainline for IPC backend. * Simplified build output message and configurable output. * Halting instead of rebooting on panic in debug build type. * Automated testing of MCUboot BL2. * A new driver interface for the CC-312 runtime library as specified in the PSA Unified Driver spec [1]_. * Added reference bootloader stage 1 (BL1) bootloader for certain platforms. * A new CC312 ROM library for the BL1. * Updated documentation structure. The changes tagged by TF-Mv1.6.0 and located in the release/v1.6.x<https://review.trustedfirmware.org/q/project:TF-M%252Ftrusted-firmware-m+br…> branch at the moment. In short, they will be integrated with the main branch and be available from there. Thanks everyone for contribution, review and support this milestone. Anton

3 years, 10 months

1
0
0 0

Technical Forum call - April 28

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, April 28, 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

3 years, 10 months

1
1
0 0

Asking for review of external trusted secure storage partition implementation code

by Edward Yang

Hi everyone, We have discussed the design proposal of supporting secure Flash in tf-m framework via this mailing list before,now the implementation code of this external trusted secure storage partition has been uploaded to tf-m-extras repo for review： https://review.trustedfirmware.org/c/TF-M/tf-m-extras/+/14953 And the binary component of this patch has also been uploaded to tf-binaries repo： https://review.trustedfirmware.org/c/tf-binaries/+/14954 For easy understanding please refer to this document first: https://review.trustedfirmware.org/c/TF-M/tf-m-extras/+/14953/1/partitions/… Looking forward to your comments and suggestions. Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 http://www.mxic.com.cn ============================================================================ CONFIDENTIALITY NOTE: This e-mail and any attachments may contain confidential information and/or personal data, which is protected by applicable laws. Please be reminded that duplication, disclosure, distribution, or use of this e-mail (and/or its attachments) or any part thereof is prohibited. If you receive this e-mail in error, please notify us immediately and delete this mail as well as it attachments from your system. In addition, please be informed that collection, processing, and/or use of personal data is prohibited unless expressly permitted by personal data protection laws. Thank you for your attention and cooperation. Macronix International Co., Ltd. =====================================================================

3 years, 11 months

1
0
0 0

Start of TF-M v1.6.0 release process

by Anton Komlev

Hello, The branch release/1.6.x<https://git.trustedfirmware.org/TF-M%2Ftrusted-firmware-m.git/log/?h=refs%2…> has been created, indicating the project feature's freeze and beginning the release process. Expecting to place RC1 tag asap, after successful run of the basic tests. Let me remind that the code is not frozen, and development can be continued on the main branch. Thanks, Anton

3 years, 11 months

1
4
0 0

TF-M Open CI Back to Normal

by Xinyu Zhang

Hi All, TF-M Open CI is back to normal now. Please feel free to use it. Thanks, Xinyu From: Xinyu Zhang via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: Monday, April 18, 2022 12:06 PM To: TF-M mailing list <tf-m(a)lists.trustedfirmware.org> Subject: [TF-M] TF-M Open CI Down Hi All, Sorry to inform you that TF-M Open CI is down for the time being because of Jenkins upgrade. I'll let you know once it is back to normal. Apologize for any inconvenience! Thanks, Xinyu

3 years, 11 months

1
0
0 0

TF-M Open CI Down

by Xinyu Zhang

Hi All, Sorry to inform you that TF-M Open CI is down for the time being because of Jenkins upgrade. I'll let you know once it is back to normal. Apologize for any inconvenience! Thanks, Xinyu

3 years, 11 months

1
0
0 0

Technical Forum call - April 14 is CANCELLED

by Anton Komlev

Hi, The forum is cancelled because of the empty agenda and the assumption that many of us in the west time zone will have a long weekend this week. Thanks, Anton From: Anton Komlev via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: Wednesday, April 6, 2022 12:43 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - April 14 Hi, The next Technical Forum is planned on Thursday, April 14, 15:00-16:00 UTC (West 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

3 years, 11 months

1
0
0 0

TF-M Isolation 3

by Doka.Dokanov-Dobrovolskyi＠infineon.com

Hello! My name is Oleg. I'm working on TF-M Isolation Level 3 testing and I need to develop test cases list for it. Could you be so kind to provide me the test cases list? May be you know where I can find it by myself? Also I have test cases list for Isolation Leve 2. Am I right that it can be reused for Isolation Level 3 with some changes? I will be very appreciate for any help. Thank you so much, Oleg Dokanov

3 years, 11 months

2
1
0 0

Technical Forum call - April 14

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, April 14, 15:00-16:00 UTC (West 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

3 years, 11 months

2
2
0 0

Mbed TLS GitHub migration

by Dave Rodgman

Hi all, Please be advised that the Mbed TLS GitHub migration is complete. The new home for Mbed TLS is: https://github.com/Mbed-TLS We recommend updating your project, checkouts, etc to point at the new repository, but it's not urgent as everything will continue to work for some time via automatic redirection. Also please note that our project boards, which we use for planning upcoming work via epics, and tracking current activity, have moved. They are now available here: Epics board: https://github.com/orgs/Mbed-TLS/projects/1 Current activity: https://github.com/orgs/Mbed-TLS/projects/2 Thanks Dave Rodgman On 22/03/2022, 14:52, "Dave Rodgman via Mbed-tls-announce" <mbed-tls-announce(a)lists.trustedfirmware.org> wrote: Hi all, Please note that in the next couple of weeks, we will migrate Mbed TLS to a new GitHub organisation. Your existing scripts, links etc for accessing Mbed TLS on GitHub should not be affected. This will change the url from https://github.com/ARMmbed/mbedtls to https://github.com/Mbed-TLS/mbedtls . GitHub will redirect any accesses to the old URL for the foreseeable future, but we would recommend updating your links once the migration is complete. All of the Mbed TLS repositories will migrate to this new organisation, i.e.: mbedtls mbedtls-docs mbedtls-test Thanks Dave Rodgman -- Mbed-tls-announce mailing list -- mbed-tls-announce(a)lists.trustedfirmware.org To unsubscribe send an email to mbed-tls-announce-leave(a)lists.trustedfirmware.org

3 years, 11 months

1
0
0 0

Technical Forum call - March 31

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, March 31, 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

3 years, 11 months

3
3
0 0

TF-M on GitHub opinions collection

by Anton Komlev

Hello, Quite some time ago there was a proposal to move TF-M into GitHub. The main motivation is: more convenient review process, the Wiki for knowledge sharing and issue tracking facility. This idea had been discussed multiple times in TSC. The following options were considered: 1. Hybrid: Add TF-M on GitHub with 2 ways synchronization between GitHub and existing Git/Gerrit 2. GitHub only: Move to GitHub completely and drop Gerrit. 3. Mirror: Create a read-only mirror on GitHub. TF-M review process stays in Gerrit but Wiki and issue tracking are on GitHub. 4. Nothing: Stay on Gerrit as good enough solution. The options are ordered by complexity and cost each has pros and cons. The Mirror option (3) seeing as the best compromise and practically affordable in a short time. Please share your opinion and comments on the topic with any dependencies or specific requirements to be considered. Thanks, Anton

3 years, 12 months

8
17
0 0

TF-M Profile Small supports SFN model

by David Hu

Hi all, I'd like to ask for your help to review the patch which enables SFN model in TF-M Profile Small. SFN model is defined in FF-M v1.1 spec. With this patch, Profile Small still enables Library model by default and users can select SFN model instead via build command. Patch: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/14500 TF-M Profile Small document update: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/14501 Any comment or suggestion is welcome. Best regards, Hu Ziji

3 years, 12 months

1
0
0 0

TrustedFirmware Code of Conduct

by Don Harbin

Hi All, Please find the link to the TrustedFirmware Community Code of Conduct here: https://developer.trustedfirmware.org/w/collaboration/community_guidelines/… Trusted Firmware has a very diverse and global developer community. It is important that we adhere to the code of conduct in all our interactions. For some of you all this may be new and for others just a gentle reminder. In either case, if you have any questions, please feel free to reach out to me directly. And thanks to you all for your contributions to the TrustedFirmware community! Best regards, Don Harbin TrustedFirmware Community Manager don.harbin(a)linaro.org

3 years, 12 months

1
0
0 0

Technical Forum call - March 17

by Arnold Gabriel Benedict

Hi, I would like to present our study on RPC Test Framework for TF-M along with a demo in our next technical forum on 17th March. Thanks, Arnold

4 years

2
1
0 0

Secure Partition interrupt signal processing

by Andersson, Joakim

Hi. I've been working on making an example on how an application can use the secure interrupts in a secure partition in TF-M. During this I've encountered an issue where the secure partition will not be scheduled to process the secure interrupt signal in certain conditions. I've compared it to the current SLIH and FLIH test cases to my observed behaviour and I could see that they did not have this problem. I've created a test-case that triggers the problem [0]. In the mailing list I can see that this was actually discussed recently [1] The summary is that secure partitions will not be scheduled to process a secure interrupt signal when the interrupt is interrupting the NSPE. I could not find that this was documented anyway, but maybe I have overlooked. In any case I find this behaviour very unexpected and I would like to know if this is indeed a design decision and the behaviour has to be this way? If I wanted to do some processing in the secure partition context it would now mean that I have to get the NSPE to trigger this through a secure partition call. This seems like a limitation to me . I'd like to know what would be the issue with scheduling the partition once it now has the signal asserted. I've done a quick test with scheduling the partition at this point with [2] and this now works as I expect it to. I'd be happy to follow up with submitting a change to schedule the partition as done in [2] if that is an acceptable solution. [0] https://github.com/joerchan/tf-m-tests/commit/d9f0a3a7653b594d0fa797d9e0bca… [1] https://lists.trustedfirmware.org/archives/list/tf-m@lists.trustedfirmware.… [2] https://github.com/joerchan/sdk-trusted-firmware-m/commit/e5512c6e8b2bad95c…

4 years

2
1
0 0

MCUboot upgraded to v1.9.0 in TF-M

by Sherry Zhang

Hi, Just a reminder that the MCUboot version has been upgraded to v1.9.0<https://github.com/mcu-tools/mcuboot/releases/tag/v1.9.0> in TF-M. If you are using the local MCUboot repo, then you need to update it to that version to avoid build error. Regards, Sherry Zhang

4 years

1
0
0 0

Technical Forum call - March 17

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, March 17, 15:00-16:00 UTC (West 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

4 years

1
0
0 0

The new design proposal guideline now take effect

by David Hu

Hi all, The new and simplified TF-M design proposal guideline is approved: https://tf-m-user-guide.trustedfirmware.org/docs/contributing/tfm_design_pr…. Please feel free to submit your topics to mailing list or tech forum! Formal design documents are NOT required anymore. Best regards, Hu Ziji

4 years

1
0
0 0

TF-M release v1.6,0 date change to April 28

by Anton Komlev

Hello, TF-M release v1.6.0 will be shifted from April 15 to April 28. The main reason is Easter holiday and expected lack of availability from community and platform owners around that date. Feature freeze will be moved to April 6th when the release branch will be created. Please update your plans accordingly. Please let me know if this change make difficulty for you and better date is possible. Thanks, Anton

4 years

1
0
0 0

Simplify TFM_PLATFORM in build system

by Jianliang Shen

Hi all, I want to simplify the flag TFM_PLATFORM in build system. TF-M now already supports two different ways to choose specific platform, for example AN521: - Absolute path: '<tf-m path>/platform/ext/target/arm/mps2/an521' - Relative path: 'arm/mps2/an21' Recently I have uploaded a [tf-m patch]<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/14260> to support platform name: - Platform name: 'an521' I think it will be more convenient for developers to use: - Users don't need to remember and type the absolute or relative path, only target platform name is enough. - If the structure of certain platform is changed, the default build command of TFM_PLATFORM is same. I'd be very grateful if you can give any suggestion or enhancement for me. Thanks. Best Regards Jianliang Shen

4 years

1
0
0 0

TF-M design documents about spm

by zhilei.wang

Dear All, I view the tf-m source code for the first time, and many of the code details can not be make clear. So .., where may I find the design documents of spm, for example: trusted-firmware-m-TF-Mv1.5.0\secure_fw\spm\cmsis_func and cmsis_psa software modules. Best Regards Wang Zhilei | Software Beken Corporation ---------------------------------------------------------------------------- ---------------------------------------------------------

4 years

3
2
0 0

Technical Forum call - March 3

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, March 3, 7:00-8:00 UTC (Asian 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

4 years

2
2
0 0

TF-M covertly results and configs to align our coverity environment to TF-M project CI

by Kostiantyn.Tkachov＠infineon.com

Hi colleagues! Could we get a list of MISRA/CERT-C violations that were found by tf-m Coverity CI, as example from https://ci.trustedfirmware.org/job/tf-m-coverity/lastSuccessfulBuild/ Also (if it possible), could you provide Coverity configs to help align this tool setup on our side to CI and to check all changes before any pool requests? Best regards, Kostiantyn Tkachov Cypress Semiconductor Ukraine Firmware Security

4 years

2
1
0 0

Problem compiling Trusted Firmware M in Linux for PSOC64

by AntonioJavier.CabreraGutierrez＠infineon.com

Hello, I am writing to you asking help because we are having problems when I try to compile the Trusted Firmware M from source code. I downloaded the code from the official repository: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git I moved to the last TAG: TF-Mv1.5.0 I am following this tutorial for PSOC64 platform https://tf-m-user-guide.trustedfirmware.org/platform/ext/target/cypress/pso… When I execute the first cmake command indicating the platform and the toolchain everything works well: cmake -DTFM_PLATFORM=cypress/psoc64 -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake .. The problems appears when I build the code using the second cmake command: cmake --build cmake_build -- -j I got this output [cid:image003.jpg@01D82A77.95B43640] /home/admin/Escritorio/trusted-firmware-m/lib/ext/t_cose/crypto_adapters/t_cose_psa_crypto.c: In function 't_cose_crypto_pub_key_verify': /home/admin/Escritorio/trusted-firmware-m/lib/ext/t_cose/crypto_adapters/t_cose_psa_crypto.c:145:5: error: conversion to non-scalar type requested 145 | verification_key_psa = (psa_key_handle_t)verification_key.k.key_handle; | ^~~~~~~~~~~~~~~~~~~~ /home/admin/Escritorio/trusted-firmware-m/lib/ext/t_cose/crypto_adapters/t_cose_psa_crypto.c: In function 't_cose_crypto_pub_key_sign': /home/admin/Escritorio/trusted-firmware-m/lib/ext/t_cose/crypto_adapters/t_cose_psa_crypto.c:194:5: error: conversion to non-scalar type requested 194 | signing_key_psa = (psa_key_handle_t)signing_key.k.key_handle; | ^~~~~~~~~~~~~~~ /home/admin/Escritorio/trusted-firmware-m/lib/ext/t_cose/crypto_adapters/t_cose_psa_crypto.c: In function 't_cose_crypto_sig_size': /home/admin/Escritorio/trusted-firmware-m/lib/ext/t_cose/crypto_adapters/t_cose_psa_crypto.c:245:5: error: conversion to non-scalar type requested 245 | signing_key_psa = (psa_key_handle_t)signing_key.k.key_handle; | ^~~~~~~~~~~~~~~ secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/build.make:425: recipe for target 'secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/lib/ext/t_cose/crypto_adapters/t_cose_psa_crypto.o' failed make[2]: *** [secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/lib/ext/t_cose/crypto_adapters/t_cose_psa_crypto.o] Error 1 make[2]: *** Waiting for unfinished jobs.... CMakeFiles/Makefile2:1347: recipe for target 'secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/all' failed make[1]: *** [secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/all] Error 2 Makefile:135: recipe for target 'all' failed make: *** [all] Error 2 There are the version of the software that are using: arm-none-eabi-gcc (GNU Arm Embedded Toolchain 10.3-2021.10) 10.3.1 20210824 (release) cmake version 3.23.0-rc2 It seems strange to me that there are compilation errors in the source code, that's why I am writing this mail, in case there is a bug in the code. Best regards. Antonio Javier Cabrera Gutierrez Infineon Technologies AG PhD Candidate R&D Engineer IFAG BEX RDE RDF ISS Office: +49 89 234 36403 Mobile: +49 151 181 34322 AntonioJavier.CabreraGutierrez(a)infineon.com<mailto:AntonioJavier.CabreraGutierrez@infineon.com> Am Campeon 1-15 85579 Neubiberg Germany www.infineon.com<http://www.infineon.com> Discoveries<http://www.infineon.com/discoveries> Facebook<http://www.facebook.com/infineon> Twitter<http://www.twitter.com/Infineon> LinkedIn<http://www.linkedin.com/company/infineon-technologies> Part of your life. Part of tomorrow. Infineon Technologies AG Chairman of the Supervisory Board: Dr. Wolfgang Eder Management Board: Dr. Reinhard Ploss (CEO), Dr. Helmut Gassel, Jochen Hanebeck, Dr. Sven Schneider Registered Office: Neubiberg Commercial Register: München HRB 126492 This e-mail and any attachments are confidential. They are intended solely for the attention and use of the named addressee(s). If you are not the named addressee(s) you must not use, disclose, retain or reproduce all or any part of the information contained in this e-mail or any attachments. Any unauthorized use or disclosure may be unlawful. If you have received this e-mail by mistake, please inform the sender immediately and delete it and all copies from your system and destroy any hard copies of it.

4 years

3
2
0 0

Locking of PRIS bit in AIRCR register

by JAYLES Romain

Hi all, We are currently testing the tfm-m implementation on a STMicroelectronic chip: stm32u5 board. This stm32u5 has a special register: SYSCFG_CSLOCKR (see https://www.st.com/resource/en/reference_manual/rm0456-stm32u575585-armbase…). This register allows to lock the PRIS bit of the AIRCR register from further modification. The issue here is that, in the ST implementation, thanks to this SYSCFG_CSLOCKR, the PRIS bit of the AIRCR is locked at boot (Reset_Handler in file startup_stm32u5xx_s.c). Resulting in the function tfm_arch_set_secure_exception_priorities() not being able to set the PRIS bit of the AIRCR. This situation lead to big issues at runtime as interrupt priority of NSPE are able to pre-empt interrupt of SPE. Disabling the locking of PRIS bit solve our problem but currently we don't see a clean way to integrate chip specific security features (something like callback/tfm_hal_ ) after the function tfm_arch_set_secure_exception_priorities() has been called. What would be the best way to fix the current issue which could also arise on other platform ? Regards, Romain

4 years

3
4
0 0

Please review a new design proposal guideline

by David Hu

Hi all, As part of the documentation improvements, a new design proposal guideline [1] is proposed to replace and simplify the current process. The basic idea is to encourage developers to share their design via mailing list and tech forum, without a well-formatted design document. If developers prefer a document for a new feature, please provide an integration guide/user manual instead. Please check the details in the patch below. [1] https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/14104 The rendered html version: https://ci-builds.trustedfirmware.org/static-files/KTOoRMhB4VsgNQFkdMgWZcZG… Best regards, Hu Ziji

4 years

1
0
0 0

Issues with psa_wait() when waiting for interrupts and IPC function calls.

by Martin Gunnarsson

Hello, I am trying to write an Application RoT for a research project I am a part of. I have run into an issue that I have been unable to solve independently. My problem is the unexpected behavior of psa_wait() when using signal masks. I have two signals, TFM_TIMER1_IRQ_SIGNAL and TFM_SECURE_FUNCTION_SIGNAL. The TIMER1_IRQ signal is triggered by an FLIH interrupt handler that returns TFM_FLIH_SIGNAL. The interrupt is triggered every 1 second by TIMER1. The TFM_SECURE_FUNCTION_SIGNAL is triggered by a periodic function call from the NSPE (a Zephyr thread) and is called every 10 seconds. Observed result: If PSA_WAIT_ANY is used as a signal mask, the TIMER0_IRQ_SIGNAL will only be received when TFM_SECURE_FUNCTION_SIGNAL is received, ergo, every 10 s. Thus any stage 2 handling of an interrupt would be missed. If TFM_TIMER1_IRQ_SIGNAL is used as a signal mask, the signal will be received every 1 s as expected. The TFM_SECURE_FUNCTION_SIGNAL will never be received, as can be expected in the NSPEtoo. I have tried a "hybrid approach" where I call psa_wait(TFM_TIMER1_IRQ_SIGNAL, PSA_BLOCK) /* handle signals .... */ and then psa_wait(TFM_SECURE_FUNCTION_SIGNAL, PSA_POLL). The stage 2 IRS is called, and the secure function is also called. But not with the regularity that I would like. Am I missing something obvious? I have read the Secure Interrupt Integration Guide and carefully studied the SLIH and FLIH test services for the TF-M regression tests. Have I forgotten to reset a signal somewhere? Does the interrupt not preempt the NSPE? I would be immensely grateful for any or all responses. If you need more information, please let me know. Best wishes, Martin Gunnarsson PhD Student RISE Research Institutes of Sweden & Lund University Complete code of my Application RoT: #include <stdbool.h> #include <stdint.h> #include <stddef.h> #include "tfm_api.h" #include "tfm_secure_api.h" #include "psa/service.h" #include "tfm_sp_log.h" #include "psa_manifest/pid.h" #include "psa_manifest/tfm_secure_partition.h" #include <hal/nrf_gpio.h> #include <hal/nrf_timer.h> #include <helpers/nrfx_reset_reason.h> #include <nrf_board.h> #include <region_defs.h> #define TIMER_RELOAD_VALUE (1*1024*1024) static volatile uint32_t interrupt_ctr = 0; static volatile uint32_t function_ctr = 0; static void timer_init(NRF_TIMER_Type * TIMER) { nrf_timer_mode_set(TIMER, NRF_TIMER_MODE_TIMER); nrf_timer_bit_width_set(TIMER, NRF_TIMER_BIT_WIDTH_32); nrf_timer_frequency_set(TIMER, NRF_TIMER_FREQ_1MHz); nrf_timer_cc_set(TIMER, NRF_TIMER_CC_CHANNEL0, TIMER_RELOAD_VALUE); /* Clear the timer once event is generated. */ nrf_timer_shorts_enable(TIMER, NRF_TIMER_SHORT_COMPARE0_CLEAR_MASK); } static void timer_stop(NRF_TIMER_Type * TIMER) { nrf_timer_task_trigger(TIMER, NRF_TIMER_TASK_STOP); nrf_timer_int_disable(TIMER, NRF_TIMER_INT_COMPARE0_MASK); nrf_timer_event_clear(TIMER, NRF_TIMER_EVENT_COMPARE0); } static void timer_start(NRF_TIMER_Type * TIMER) { timer_stop(TIMER); nrf_timer_task_trigger(TIMER, NRF_TIMER_TASK_CLEAR); nrf_timer_int_enable(TIMER, NRF_TIMER_INT_COMPARE0_MASK); nrf_timer_task_trigger(TIMER, NRF_TIMER_TASK_START); } static void timer_event_clear(NRF_TIMER_Type *TIMER) { nrf_timer_event_clear(TIMER, NRF_TIMER_EVENT_COMPARE0); } void tfm_secure_controller_secure_timer_start(void) { timer_init(NRF_TIMER1); timer_start(NRF_TIMER1); } void tfm_secure_controller_secure_timer_clear_intr(void) { timer_event_clear(NRF_TIMER1); } psa_flih_result_t tfm_timer1_irq_flih(void) { tfm_secure_controller_secure_timer_clear_intr(); interrupt_ctr++; return PSA_FLIH_SIGNAL; } static psa_status_t tfm_sp_secure_function_ipc(psa_msg_t *msg) { function_ctr++; LOG_INFFMT("Secure function called %u times, interrupt ctr: %u\n", function_ctr, interrupt_ctr ); return PSA_SUCCESS; } void tfm_sp_secure_function(psa_msg_t *msg) { psa_status_t status; status = tfm_sp_secure_function_ipc(msg); psa_reply(msg->handle, status); } void tfm_sp_entry(void) { LOG_INFFMT("Secure Partition: Init\n"); tfm_secure_controller_secure_timer_start(); psa_irq_enable(TFM_TIMER1_IRQ_SIGNAL); psa_signal_t signals = 0; uint32_t ctr = 0; while (1) { signals = psa_wait(TFM_TIMER1_IRQ_SIGNAL, PSA_BLOCK); if ( (signals & TFM_TIMER1_IRQ_SIGNAL) == TFM_TIMER1_IRQ_SIGNAL) { ctr++; LOG_INFFMT("FLIH stage 2 %u\n", interrupt_ctr); psa_reset_signal(TFM_TIMER1_IRQ_SIGNAL); } if ( ctr % 10 == 0 ) { signals = psa_wait(PSA_WAIT_ANY, PSA_POLL); if ( (signals & TFM_SECURE_FUNCTION_SIGNAL) == TFM_SECURE_FUNCTION_SIGNAL) { psa_msg_t msg; psa_get(signals, &msg); tfm_sp_secure_function(&msg); } } } }

4 years

2
8
0 0

New API tfm_hal_system_halt()

by Bøe, Sebastian

Hi, in the effort to ease debugging by supporting a choice between halting and rebooting we are introducing a new HAL API: void tfm_hal_system_halt(void) which by default (weak) does: __disable_irq(); while(1) { __WFE(); } CPUs cannot halt. But they can sleep until they are awoken in a loop, which is pretty close. tfm_hal_system_halt() is, when configured so, used by tfm_core_panic() which is why we disable irqs to stop all threads of execution, not just the thread that is executing. Currently it is proposed that tfm_core_panic() halts when TFM_HALT_ON_CORE_PANIC is ON and otherwise reboots. TFM_HALT_ON_CORE_PANIC is default ON if and only if Debug mode is enabled. Any feedback to these changes are welcome, and if any platform needs to halt in a different manner then a contribution would be welcome as well. https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/13839

4 years

1
0
0 0

TF-M regression test refinements

by Jianliang Shen

Hi, all I'd like to share two new refinements in TF-M test repo to you. l The struct variable test_result_t has been removed from the definition of struct variable test_t. It is unnecessary to set an initial value of test result for each case. With this change, the binary size will be reduced. Please see [test patch]<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/13822/4> for more details. l The flag TEST_SKIPPED has been added into enum variable test_status_t, works with TEST_PASSED and TEST_FAILED. TEST_SKIPPED indicates that the test case is skipped in runtime when the test environment is unavailable. Please ee [test patch]<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/13826/5> for more details. Hope these two changes can help your work in the future. Please let me know if anything can be improved. Thanks! Best Regards Jianliang Shen

4 years

1
0
0 0

FF PSA API overhead

by Bøe, Sebastian

Hi, the performance improvement presentation[0] reports a FF PSA API overhead of 20 000 CPU cycles for the psa_call. Which is 300 us for a 64MHz CPU. This is quite a lot of instructions and I am concerned about whether real world embedded application's will have time to call these secure services. I'm interested in isolation level 2. I understand that it is not possible to have isolation level 2 with library mode. But what about SFN mode, could that eventually support isolation level 2? If not, what is the current status of optimizing the service call overhead for IPC. Is it considered to be as optimized as it can be or is there still hope for optimizing further? [0] https://www.trustedfirmware.org/docs/tf-m_forum_20211209-TF-M_Performance-I…

4 years

2
1
0 0

Technical Forum call - Feb 17

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, February 17, 15:00-16:00 UTC (US 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

4 years, 1 month

2
2
0 0

[FYI] Tiny update in level 3 ld/sct files

by Ken Liu

Hi, We got a tiny update merged in level 3 ld/sct files to support partition runtime: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/13925 Platforms with level 3 support please have a test and report issue here if spotted. We have internally tested MPS2 and MUSCA_B1. Thanks. /Ken

4 years, 1 month

1
0
0 0

halting or rebooting on faults

by Bøe, Sebastian

Hi, it seems we could try to be more consistent with fault handling. The current default behaviour is: Error code returned from an SPE function? Reboot. MemFault/HardFault/SecureFault in the SPE? Halt. Null-pointer dereference from the NSPE? (results in a secure fault for cortex-m) Halt. Should we perhaps consistently halt or consistently reboot for these three cases and allow this to be configurable? It is not clear to me why an error returned from a function results in a reboot, whereas a Hardfault does not. They both indicate a fault in the SPE. At the very least the behaviour should be configurable, which this PR is a step towards: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/13839

4 years, 1 month

5
4
0 0

Security vulnerability notice - Firmware Update psa_fwu_write service vulnerability

by Sherry Zhang

Hi all, This email is a notification of a new security vulnerability reported to TF-M. In TF-M version between 3e7129f<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/commit/?id=3e71…> and 921d0ea<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/commit/?id=921d…>, the caller of ``psa_fwu_write()`` from SPE or NSPE can overwrite the stack memory outside of the local buffer in Firmware Update partition in IPC model. Please check the details in the security advisory doc<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/13873/5/docs…>. The advisory has been merged in master branch today. The fix<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/commit/?id=78f7…> has been merged into master branch before TF-Mv1.5.0. Regards, Sherry Zhang

4 years, 1 month

1
0
0 0

Dual core broken

by Chris.Brand＠infineon.com

Commit 27f9a49508547320c50056a52a372674c27771eb seems to have missed changing ns_agent_mailbox, breaking dual core. I'd send a patch, but I's not immediately obvious what it should look like... Seems like a good change, but inadequately reviewed? Chris Brand Cypress Semiconductor (Canada), Inc. An Infineon Technologies Company Sr Prin Software Engr CSCA CSS ICW SW PSW 1 Office: +1 778 234 0515 Chris.Brand(a)infineon.com<mailto:Chris.Brand@infineon.com> International Place 13700 V6V 2X8 Richmond Canada www.infineon.com<www.cypress.com> www.cypress.com<http://www.cypress.com> Discoveries<http://www.infineon.com/discoveries> Facebook<http://www.facebook.com/infineon> Twitter<http://www.twitter.com/Infineon> LinkedIn<http://www.linkedin.com/company/infineon-technologies> Part of your life. Part of tomorrow. NOTICE: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material of Infineon Technologies AG and its affiliated entities which is for the exclusive use of the individual designated above as the recipient. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact immediately the sender by returning e-mail and delete the material from any computer. If you are not the specified recipient, you are hereby notified that all disclosure, reproduction, distribution or action taken on the basis of this message is prohibited.

4 years, 1 month

2
1
0 0

Why ARM_FLASH_STATUS is volatile in flash driver?

by Roman Mazurak

Hi all, Why ARM_FLASH_STATUS was declared volatile in https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/commit/platform… commit ? I believe it's much better to declare volatile variable when there is such need instead of forcing all variables to become volatile through typedef. Thanks, Roman.

4 years, 1 month

2
2
0 0

[CANCELLED] Technical Forum call - Feb 3

by Anton Komlev

Hi, Let's cancel the forum tomorrow due to the empty agenda and the holiday time in Asia. Best regards, Anton From: Anton Komlev via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: Thursday, January 27, 2022 4:36 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - Feb 3 Hi, The next Technical Forum is planned on Thursday, Feb 3, 7:00-8:00 UTC (Asia time zone). Please reply on this email with your proposals for agenda topics. This slot is in Chinese New Year celebration period so we can expect fewer participants from Asia. Recording and slides of previous meetings are here: https://www.trustedfirmware.org/meetings/tf-m-technical-forum/ Best regards, Anton

4 years, 1 month

1
0
0 0

Custom implementation of of tfm_hal_system_reset

by Bohdan.Hunko＠infineon.com

Hi everyone, I have a few questions related to TF-M code: 1. Default implementation of tfm_hal_system_reset(void) from platform/ext/common/tfm_platform.c<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e…> just calls NVIC_SystemReset(), but some ARM platform, take musca_b1 for example, reimplement it (platform/ext/target/arm/musca_b1/sse_200/tfm_hal_platform.c<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e…> ). Custom implementations tend to also disable and clean IRQ and call mpc_revert_non_secure_to_secure_cfg(); Is there any benefits of doing that??? If so then what those benefits are? 1. tfm_core_panic() (secure_fw/spm/ffm/utilities.c<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/secure_fw/…>) when TFM_FIH_PROFILE_ON is defined calls fih_delay() and tfm_hal_system_reset() twice. Is this done to ensure that tfm_hal_system_reset() will be called (even if first one was skipped there is second one)? And if so, can a comment be added there to highlight that intention? Regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com>

4 years, 1 month

3
2
0 0

Technical Forum call - Feb 3

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, Feb 3, 7:00-8:00 UTC (Asia time zone). Please reply on this email with your proposals for agenda topics. This slot is in Chinese New Year celebration period so we can expect fewer participants from Asia. Recording and slides of previous meetings are here: https://www.trustedfirmware.org/meetings/tf-m-technical-forum/ Best regards, Anton

4 years, 1 month

1
0
0 0

Please Use Test Version Specified in TF-M CMake Configs

by Xinyu Zhang

Hi All, Please do use the tf-m-tests version specified in TF-M CMake configs (TFM_TEST_REPO_VERSION in trusted-firmware-m/lib/ext/tf-m-tests/repo_config_default.cmake), otherwise there might be some unexpected build errors. Please let us know if there is any problem. Thanks, Xinyu

4 years, 1 month

1
0
0 0

TF-M Open CI Back to Normal

by Xinyu Zhang

Hi All, TF-M Open CI is back to normal. Please feel free to use. Thanks, Xinyu From: Xinyu Zhang Sent: Monday, January 17, 2022 4:05 PM To: TF-M mailing list <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: TF-M Open CI Not Stable Right Now Hi All, Sorry to inform you that TF-M Open CI is not stable right now. Jobs are likely to come into unexpected failure. I'll keep following up with the latest information. Sorry for any inconvenience! Thanks, Xinyu

4 years, 1 month

1
0
0 0

unsubscribe

by st9hack＠yahoo.com

unsubscribe

4 years, 1 month

1
0
0 0

Technical Forum call - Jan 20

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, January 20, 15:00-16:00 UTC (US 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

4 years, 2 months

2
2
0 0

Updated invitation: TF-M Tech forum @ Every 4 weeks from 8am to 9am on Thursday (MST) (tf-m@lists.trustedfirmware.org)

by don.harbin＠linaro.org

This event has been changed. Title: TF-M Tech forum This is an open forum for anyone to participate and it is not restricted to Trusted Firmware project members. It will operate under the guidance of the TF TSC.Feel free to forward it to colleagues.Details of previous meetings are here: https://www.trustedfirmware.org/meetings/tf-m-technical-forum/==… Info====Trusted Firmware is inviting you to a scheduled Zoom meeting.Topic: TF-M Tech forum - US Time Zone FriendlyTime: Oct 29, 2020 03:00 PM Greenwich Mean Time        Every 4 weeks on Thu, until Mar 18, 2021, 6 occurrence(s)        Oct 29, 2020 03:00 PM        Nov 26, 2020 03:00 PM        Dec 24, 2020 03:00 PM        Jan 21, 2021 03:00 PM        Feb 18, 2021 03:00 PM        Mar 18, 2021 03:00 PMPlease download and import the following iCalendar (.ics) files to your calendar system.Weekly: https://linaro-org.zoom.us/meeting/tJEocOmvpz4tHtYu0Wvn2fOsG91u0kv_ECPd/ics… Zoom Meetinghttps://linaro-org.zoom.us/j/95570795742?pwd=N21YWHJpUjZyS3Fzd0tkOG9hanpidz09Meeting ID: 955 7079 5742Passcode: 177658One tap mobile+12532158782,,95570795742# US (Tacoma)+13462487799,,95570795742# US (Houston)Dial by your location        +1 253 215 8782 US (Tacoma)        +1 346 248 7799 US (Houston)        +1 669 900 9128 US (San Jose)        +1 301 715 8592 US (Germantown)        +1 312 626 6799 US (Chicago)        +1 646 558 8656 US (New York)        877 853 5247 US Toll-free        888 788 0099 US Toll-freeMeeting ID: 955 7079 5742Find your local number: https://linaro-org.zoom.us/u/abx3I7IoRq When: Every 4 weeks from 8am to 9am on Thursday Mountain Standard Time - Phoenix Where: https://linaro-org.zoom.us/j/95570795742?pwd=N21YWHJpUjZyS3Fzd0tkOG9hanpidz… Calendar: tf-m(a)lists.trustedfirmware.org Who: * Don Harbin - creator * tf-m(a)lists.trustedfirmware.org * anton.komlev(a)arm.com * abdelmalek.omar1(a)gmail.com * kevin.townsend(a)linaro.org * seth(a)nxmlabs.com * leonardo.sandoval(a)linaro.org Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=djczYWZqa3ZmMW5n… Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account tf-m(a)lists.trustedfirmware.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

4 years, 2 months

1
0
0 0

Updated invitation: TF-M Tech forum @ Every 4 weeks from 8am to 9am on Thursday (MST) (tf-m@lists.trustedfirmware.org)

by don.harbin＠linaro.org

This event has been changed. Title: TF-M Tech forum This is an open forum for anyone to participate and it is not restricted to Trusted Firmware project members. It will operate under the guidance of the TF TSC.Feel free to forward it to colleagues.Details of previous meetings are here: https://www.trustedfirmware.org/meetings/tf-m-technical-forum/==… Info====Trusted Firmware is inviting you to a scheduled Zoom meeting.Topic: TF-M Tech forum - US Time Zone FriendlyTime: Oct 29, 2020 03:00 PM Greenwich Mean Time        Every 4 weeks on Thu, until Mar 18, 2021, 6 occurrence(s)        Oct 29, 2020 03:00 PM        Nov 26, 2020 03:00 PM        Dec 24, 2020 03:00 PM        Jan 21, 2021 03:00 PM        Feb 18, 2021 03:00 PM        Mar 18, 2021 03:00 PMPlease download and import the following iCalendar (.ics) files to your calendar system.Weekly: https://linaro-org.zoom.us/meeting/tJEocOmvpz4tHtYu0Wvn2fOsG91u0kv_ECPd/ics… Zoom Meetinghttps://linaro-org.zoom.us/j/95570795742?pwd=N21YWHJpUjZyS3Fzd0tkOG9hanpidz09Meeting ID: 955 7079 5742Passcode: 177658One tap mobile+12532158782,,95570795742# US (Tacoma)+13462487799,,95570795742# US (Houston)Dial by your location        +1 253 215 8782 US (Tacoma)        +1 346 248 7799 US (Houston)        +1 669 900 9128 US (San Jose)        +1 301 715 8592 US (Germantown)        +1 312 626 6799 US (Chicago)        +1 646 558 8656 US (New York)        877 853 5247 US Toll-free        888 788 0099 US Toll-freeMeeting ID: 955 7079 5742Find your local number: https://linaro-org.zoom.us/u/abx3I7IoRq When: Every 4 weeks from 8am to 9am on Thursday Mountain Standard Time - Phoenix Where: https://linaro-org.zoom.us/j/95570795742?pwd=N21YWHJpUjZyS3Fzd0tkOG9hanpidz… Calendar: tf-m(a)lists.trustedfirmware.org Who: * Don Harbin - creator * tf-m(a)lists.trustedfirmware.org * anton.komlev(a)arm.com * abdelmalek.omar1(a)gmail.com * kevin.townsend(a)linaro.org * seth(a)nxmlabs.com * leonardo.sandoval(a)linaro.org Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=djczYWZqa3ZmMW5n… Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account tf-m(a)lists.trustedfirmware.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

4 years, 2 months

1
0
0 0

TF-M Open CI Not Stable Right Now

by Xinyu Zhang

Hi All, Sorry to inform you that TF-M Open CI is not stable right now. Jobs are likely to come into unexpected failure. I'll keep following up with the latest information. Sorry for any inconvenience! Thanks, Xinyu

4 years, 2 months

1
0
0 0

Remove use of ER_INITIAL_PSP

by Mingyang Sun

Hi, ER_INITIAL_PSP section was used as the Trustzone NS Agent partition stack in IPC model. Since Trustzone NS Agent partition has changed to use private variables as its stack, ER_INITIAL_PSP related definitions and references can be removed. Change: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/13186 This change involves all the platforms for IPC model, it removes: * Definition of ER_INITIAL_PSP section in the linker script * Reference of ER_INITIAL_PSP for isolation configuration in platform HALs This can simplify the linker script a bit. This patch is going to be put there for a while as there are holidays, but please do review it when you see this mail. Plan to merge it before end of Jan, as soon as all concerns get addressed (if there are). Regards, Mingyang

4 years, 2 months

2
2
0 0

Code size analyze tool for TF-M further optimization

by Jianliang Shen

Hi all, I'd like to introduce a code size analyse tool to you. The tool is developed to help optimize TF-M code size by gathering the data from map file and output friendly. These python scripts can - Get a database to implement data tables from ARMCLANG or GNUARM map file. - Supply an UI for developers to scan sorted information of sections, libraries, object files, functions and data. - Help analyse the biggest or smallest targets in certain image. It can also help search functions or data to locate their address and detail information. - Diff two databases to see the code size increment or decrement between two different build results. The patch is: [tf-m-tools]<https://review.trustedfirmware.org/c/TF-M/tf-m-tools/+/12665>, it also contains the document for users. Hope this tool can help you measure code size in the daily work. Please let me know if anything can be improved. I'd like to merge this tool this Friday if no critical comment. Best Regards Jianliang Shen

4 years, 2 months

1
1
0 0

Asking for patch review of aligning flash driver to CMSIS Flash APIs

by Sherry Zhang

Hi, Currently, there is a known misalignment with the current CMSIS Flash interface in TF-M as described in TF-M doc<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/integ…>. I created this patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/13295/> to eliminate the misalignment. As it impacts all the platforms, may I ask for review on this patch? This patch has been verified by staging nightly CI. Thanks! Regards, Sherry Zhang

4 years, 2 months

1
1
0 0

Re: Power management and TFM

by Suresh.Marisetty＠infineon.com

Here is what I could find on Zephyr: https://docs.zephyrproject.org/1.14.1/reference/power_management/index.html Any thoughts from anybody on this topic. thanks Suresh Marisetty Infineon Semiconductor Corporation From: Anton Komlev <Anton.Komlev(a)arm.com> Sent: Thursday, January 13, 2022 2:19 AM To: Joseph Yiu <Joseph.Yiu(a)arm.com>; Marisetty Suresh (CYSC CSS ICW SW SSE) <Suresh.Marisetty(a)infineon.com> Subject: RE: Power management and TFM Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe<https://intranet-content.infineon.com/explore/aboutinfineon/rules/informati…>. Hi Suresh, As you noted, the power management topic is not covered by TF-M, leaving it for a platform or project level handling. Would you like to discuss the topic on TF-M Tech Forum and check what community thinks about it? Best regards, Anton From: Joseph Yiu <Joseph.Yiu(a)arm.com<mailto:Joseph.Yiu@arm.com>> Sent: Wednesday, January 12, 2022 8:52 PM To: Suresh.Marisetty(a)infineon.com<mailto:Suresh.Marisetty@infineon.com>; Anton Komlev <Anton.Komlev(a)arm.com<mailto:Anton.Komlev@arm.com>> Subject: RE: Power management and TFM Hi Suresh, > Power management does have an impact on security flows and how it is done. Agree. > Not sure if there is a standardized framework and application note on how it can be done on Corte-M with or without Secure Enclave model Unfortunately there is no standardization of power management interface for Cortex-M systems today. And given that the low power implementation varies between different vendors significantly, trying to define a power control interface is going to be very challenging. By the way, I noticed you reply to me only. Is that intentional or would you want to have this conversation on the email list? Regards, Joseph From: Suresh.Marisetty(a)infineon.com<mailto:Suresh.Marisetty@infineon.com> <Suresh.Marisetty(a)infineon.com<mailto:Suresh.Marisetty@infineon.com>> Sent: 12 January 2022 18:58 To: Joseph Yiu <Joseph.Yiu(a)arm.com<mailto:Joseph.Yiu@arm.com>> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: Power management and TFM HI Anton and Joseph, Power management does have an impact on security flows and how it is done. This is a town down architecture/implementation starting with NSPE and down with expected behavior of SPE (secure boot, TFM context management, etc.), cold boot, warm boot, deep-sleep, hibernate and active modes. On the Cortex-A, there is PSCI framework couple with ACPI. Not sure if there is a standardized framework and application note on how it can be done on Corte-M with or without Secure Enclave model. thanks Suresh Marisetty Infineon Semiconductor Corporation From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Joseph Yiu via TF-M Sent: Monday, December 20, 2021 8:04 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] Power management and TFM Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe<https://intranet-content.infineon.com/explore/aboutinfineon/rules/informati…>. Hi Suresh, Anton, This is an interesting topic :-) Armv8-M processors has some power management registers that can be restricted to Secure world access only. System Control Register (SCR) - Bit 2 SLEEPDEEP - 0 = Normal Sleep, 1 = Deep Sleep (this can also enable WIC feature). Access permission depends on SLEEPDEEPS. - Bit 3 SLEEPDEEPS - 0 - NS privileged world can r/w to SLEEPDEEP, 1 - SLEEPDEEP is RAZ/WI to NS privileged world (This is applicable to Cortex-M23, Cortex-M33, Cortex-M35P, Cortex-M55) Cortex-M55 also has Implementation defined power model control registers (CPDLPSTATE, DPDLPSTATE) https://developer.arm.com/documentation/101273/0101/Cortex-M55-Processor-le… If TrustZone is used (AIRCR.BFHFNMINS is 0), then these registers are Secure privileged access only. So definitely Secure firmware should provide some APIs for Non-secure software for changing the power control settings. However, I would expect that power control APIs would likely to be at a higher level which also manage other system level power control functions (which, as Anton said, device specific). In such case having APIs for modifying SLEEPDEEP and power model control registers is not helpful (or might even end up with confusions - e.g. if a SW developer trying to use both low level and high level APIs at the same time). Given that a Secure firmware can setup SLEEPDEEPS easily if it wants to allow/disallow access to SLEEPDEEP control, having an API for this might be overkill. Access to Cortex-M55's power model control registers is more tricky. Would an 'optional' reference API for updating power model control registers (CPDLPSTATE, DPDLPSTATE) be considered? Regards, Joseph From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Anton Komlev via TF-M Sent: 20 December 2021 12:32 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] Power management and TFM Hi Suresh, The power management is out of scope of TF-M core or any PSA service. Such functionality is HW platform specific and may vary depending on HW or SW adaptation capabilities. If you concern about a specific use case, where TF-M support is expected - let's discuss it here. Hope that helps, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Suresh Marisetty via TF-M Sent: Friday, December 17, 2021 8:11 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] Power management and TFM Hi, Wondering if anybody can throw some light on any ongoing efforts on power management on a system with TFM (deep sleep, etc). thanks Suresh Marisetty Infineon Semiconductor Corporation CYSC CSS ICW SW SSE Mobile: +5103863997 Suresh.Marisetty(a)infineon.com<mailto:Suresh.Marisetty@infineon.com> 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.

4 years, 2 months

1
0
0 0

FPU register (D8~D15) corrupted in library mode

by Eason Lai (賴易聖)

Hello TFM owners, I would like to report an issue for ARMv8-MAIN in TFM. From GCC9, it may use FPU registers (S16~S31) to backup general purpose registers for better performance. However, TFM’s library mode is not backup and restore FPU registers (S16~S31) base on EXC_RETURN.FType bit in tfm_core_sfn_request. (Reference for LR.FType https://developer.arm.com/documentation/100235/0004/the-cortex-m33-processo… ) This may causes FPU registers (S16~S31) to be corrupted in tfm_core_sfn_request, if interrupt happens between two SVC call. Here is an example to reproduce the issue: 1. Task A uses FPU S16 register to backup GPR R0 2. Task A calls psa_import_key() API 3. After the instruction “SVC %[SVC_REQ]” in tfm_core_sfn_request, the CONTROL.FPCA become “NOT active” 4. Enter FreeRTOS PendSV_Handler and schedule to others task. * Originally, this should backup S16 due to CONTROL.FPCA is active and EXC_RETURN.FType should be 0. * But, the EXC_RETURN.FType become 1 due to step3. So the S16 is not backup in stack and changed by others task. 1. Another task uses FPU S16 register (overwrite the value of S16 from Task A) 2. Enter FreeRTOS PendSV_Handler and schedule back to Task A 3. psa_import_key is finished and exit from TFM 4. Task A restore GPR R0 from FPU R16 5. Memory access violation in Task A due to incorrect value of GPR R0. Stacking FPU s16-s31 in tfm_core_sfn_request can fix this problem. Please check the blue instructions. Thank you. __attribute__((section("SFN"), naked)) int32_t tfm_core_sfn_request(const struct tfm_sfn_req_s *desc_ptr) { __ASM volatile( "PUSH {r4-r12, lr} \n" "MRS r4, control \n" /* Check FPCA in control register */ "TST r4, #0x04 \n" "IT NE \n" /* Stacking S16-S31, if CONTROL.FPCA = 1 */ "VSTMDBNE sp!, {s16-s31} \n" "PUSH {r4} \n" /* Backup CONTROL register */ "PUSH {r4} \n" /* For 8-bytes alignment to prevent xPSR.BIT9 = 1 */ "SVC %[SVC_REQ] \n" /* To remove upon instruction, xPSR.BIT9 should be masked to 0 in prepare_partition_iovec_ctx(…) */ "MOV r4, #0 \n" "MOV r5, r4 \n" "MOV r6, r4 \n" "MOV r7, r4 \n" "MOV r8, r4 \n" "MOV r9, r4 \n" "MOV r10, r4 \n" "MOV r11, r4 \n" "BLX lr \n" "SVC %[SVC_RET] \n" "POP {r4} \n" /* Restore CONTROL register */ "POP {r4} \n" "TST r4, #0x04 \n" /* Check FPCA in control register */ "IT NE \n" "VLDMIANE sp!, {s16-s31} \n" /* Restore S16-S31, if CONTROL.FPCA = 1 */ "POP {r4-r12, pc} \n" : : [SVC_REQ] "I" (TFM_SVC_SFN_REQUEST), [SVC_RET] "I" (TFM_SVC_SFN_RETURN) ); } Best regards!

4 years, 2 months

3
4
0 0

Re: Pending PR needs merging

by Anton Komlev

Hi Jamie, The change has been merged. Sorry for the possible inconveniences caused by end of the year holidays. Best regards, Anton From: Jamie Mccrae via TF-M <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Sent: Tuesday, January 11, 2022 4:03 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] Pending PR needs merging Hi, Would it be possible to get this PR merged https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12686 due to a pending update for Zephyr? Thanks, Jamie THIS MESSAGE, ANY ATTACHMENT(S), AND THE INFORMATION CONTAINED HEREIN MAY BE PROPRIETARY TO LAIRD CONNECTIVITY, LLC. AND/OR ANOTHER PARTY, AND MAY FURTHER BE INTENDED TO BE KEPT CONFIDENTIAL. IF YOU ARE NOT THE INTENDED RECIPIENT, PLEASE DELETE THE EMAIL AND ANY ATTACHMENTS, AND IMMEDIATELY NOTIFY THE SENDER BY RETURN EMAIL. THIS MESSAGE AND ITS CONTENTS ARE THE PROPERTY OF LAIRD CONNECTIVITY, LLC. AND MAY NOT BE REPRODUCED OR USED WITHOUT THE EXPRESS WRITTEN CONSENT OF LAIRD CONNECTIVITY, LLC.

4 years, 2 months

2
1
0 0

Pending PR needs merging

by Jamie Mccrae

Hi, Would it be possible to get this PR merged https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12686 due to a pending update for Zephyr? Thanks, Jamie THIS MESSAGE, ANY ATTACHMENT(S), AND THE INFORMATION CONTAINED HEREIN MAY BE PROPRIETARY TO LAIRD CONNECTIVITY, LLC. AND/OR ANOTHER PARTY, AND MAY FURTHER BE INTENDED TO BE KEPT CONFIDENTIAL. IF YOU ARE NOT THE INTENDED RECIPIENT, PLEASE DELETE THE EMAIL AND ANY ATTACHMENTS, AND IMMEDIATELY NOTIFY THE SENDER BY RETURN EMAIL. THIS MESSAGE AND ITS CONTENTS ARE THE PROPERTY OF LAIRD CONNECTIVITY, LLC. AND MAY NOT BE REPRODUCED OR USED WITHOUT THE EXPRESS WRITTEN CONSENT OF LAIRD CONNECTIVITY, LLC.

4 years, 2 months

1
0
0 0

TF-M Open CI Back to Normal

by Xinyu Zhang

Hi all, TF-M CI is back to normal. Please feel free to use it. 😊 BR, Xinyu From: Xinyu Zhang Sent: Monday, January 10, 2022 11:07 AM To: TF-M mailing list <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: TF-M Open CI Fails to Run Tests Hi all, Sorry to inform you that TF-M Open CI is down for the time being – tests cannot be run. I’ll let you know as long as CI is back to normal. Apologize for any inconvenience! Thanks, Xinyu

4 years, 2 months

1
0
0 0

TF-M Open CI Fails to Run Tests

by Xinyu Zhang

Hi all, Sorry to inform you that TF-M Open CI is down for the time being - tests cannot be run. I'll let you know as long as CI is back to normal. Apologize for any inconvenience! Thanks, Xinyu

4 years, 2 months

1
0
0 0

Mailbox mechanism changed into partition

by Ken Liu

Hi, Thank Chris made a couple of changes to move the mailbox mechanism from a kernel-coupled one into a partition-based one, which simplifies the programming model much. And mailbox-related platforms (musca-b1 secure enclave and corstone 1000) may get affected after merged, please mentioned platform owners take a try on these patches. Another solution is we can merge them and then fix the problems found. Will wait for one more week for the last patch (Patches no affecting platforms out of PSoC are merged already). I think checkout this one should bring all related changes into local: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12311 Feel free to comment, thanks. /Ken

4 years, 2 months

1
1
0 0

Technical Forum call - Jan 6

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, Jan 6, 7:00-8:00 UTC (Asia 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

4 years, 2 months

1
1
0 0

PSA headers difference

by Bohdan.Hunko＠infineon.com

Hi everyone, While taking a look into PSA header files from interface/include/psa/ folder I have found out that they are actually slightly different from PSA headers in build_folder/lib/ext/mbedcrypto-src/include/psa/ folder. Here is list of files that are different: * crypto.h * crypto_compat.h * crypto_extra.h * crypto_sizes.h * crypto_struct.h * crypto_types.h * crypto_values.h My expectation was that PSA interface (header files) should be the same in both folders. Maybe we should use only one version of those files (remove files from interface/include/psa/ and just use files from build_folder/lib/ext/mbedcrypto-src/include/psa/)? Regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com>

4 years, 2 months

2
1
0 0

Some broken builds

by Thomas Törnblom

Back after the holidays I have tested a few builds and I've noticed that a few builds fail a bunch of tests. Fails on all tool chains. Is this a known issue? psoc64, musca_s1 works. Musca_B1 (nxp lpcxpresso55s69 also fails: PS D:\Projects\tf-m6\trusted-firmware-m\armclang> cmake -GNinja -S .. -B . -DTFM_PLATFORM=arm/musca_b1/sse_200 "-DTFM_TOOLCHAIN_FILE=..\toolchain_ARMCLANG.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBL2=ON ... Running Test Suite PSA internal trusted storage S interface tests (TFM_S_ITS_TEST_1XXX)... > Executing 'TFM_S_ITS_TEST_1001' Description: 'Set interface' Set should not fail with valid UID (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:32) TEST: TFM_S_ITS_TEST_1001 - FAILED! > Executing 'TFM_S_ITS_TEST_1002' Description: 'Set interface with create flags' Set should not fail with no flags (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:91) TEST: TFM_S_ITS_TEST_1002 - FAILED! > Executing 'TFM_S_ITS_TEST_1003' Description: 'Set interface with NULL data pointer' Set should succeed with NULL data pointer and zero length (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:115) TEST: TFM_S_ITS_TEST_1003 - FAILED! > Executing 'TFM_S_ITS_TEST_1004' Description: 'Set interface with write once UID' Set should not rewrite a write once UID (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:138) TEST: TFM_S_ITS_TEST_1004 - FAILED! > Executing 'TFM_S_ITS_TEST_1005' Description: 'Get interface with valid data' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:186) TEST: TFM_S_ITS_TEST_1005 - FAILED! > Executing 'TFM_S_ITS_TEST_1006' Description: 'Get interface with zero data length' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:293) TEST: TFM_S_ITS_TEST_1006 - FAILED! ... (lots more failed tests) ... *** Non-secure test suites summary *** Test suite 'PSA protected storage NS interface tests (TFM_NS_PS_TEST_1XXX)' has PASSED Test suite 'PSA internal trusted storage NS interface tests (TFM_NS_ITS_TEST_1XXX)' has FAILED Test suite 'Crypto non-secure interface test (TFM_NS_CRYPTO_TEST_1XXX)' has FAILED Test suite 'Platform Service Non-Secure interface tests(TFM_NS_PLATFORM_TEST_1XXX)' has PASSED Test suite 'Initial Attestation Service non-secure interface tests(TFM_NS_ATTEST_TEST_1XXX)' has PASSED Test suite 'QCBOR regression test(TFM_NS_QCBOR_TEST_1XXX)' has PASSED Test suite 'T_COSE regression test(TFM_NS_T_COSE_TEST_1XXX)' has PASSED Test suite 'PSA firmware update NS interface tests (TFM_NS_FWU_TEST_1xxx)' has PASSED Test suite 'Core non-secure positive tests (TFM_NS_CORE_TEST_1XXX)' has PASSED Test suite 'IPC non-secure interface test (TFM_NS_IPC_TEST_1XXX)' has PASSED Test suite 'TFM IRQ Test (TFM_IRQ_TEST_1xxx)' has PASSED *** End of Non-secure test suites *** -- *Thomas Törnblom*, /Product Engineer/ IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com Website: www.iar.com <http://www.iar.com> Twitter: www.twitter.com/iarsystems <http://www.twitter.com/iarsystems>

4 years, 2 months

2
6
0 0

Some broken builds

by Thomas Törnblom

Back after the holidays I have tested a few builds and I've noticed that a few builds fail a bunch of tests. Fails on all tool chains. Is this a known issue? psoc64, musca_s1 works. Musca_B1 (nxp lpcxpresso55s69 also fails: PS D:\Projects\tf-m6\trusted-firmware-m\armclang> cmake -GNinja -S .. -B . -DTFM_PLATFORM=arm/musca_b1/sse_200 "-DTFM_TOOLCHAIN_FILE=..\toolchain_ARMCLANG.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBL2=ON Musca B eflash Firmware Version 3.4 [INF] Starting bootloader [WRN] This device was provisioned with dummy keys. This device is NOT SECURE [INF] Swap type: none [INF] Swap type: none CC:error_mapping_cc_to_mbedtls_rsa: Converted CC_ERROR 0 (0x00000000) to MBEDTLS_ERR 0 CC:error_mapping_cc_to_mbedtls_rsa: Converted CC_ERROR 0 (0x00000000) to MBEDTLS_ERR 0 [INF] Bootloader chainload address offset: 0x20000 [INF] Jumping to the first image slot [WRN] This device was provisioned with dummy keys. This device is NOT SECURE [Sec Thread] Secure image initializing! TF-M FP mode: Software Booting TFM v1.5.0 #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_S_PS_TEST_1XXX)... > Executing 'TFM_S_PS_TEST_1001' Description: 'Set interface' TEST: TFM_S_PS_TEST_1001 - PASSED! > Executing 'TFM_S_PS_TEST_1002' Description: 'Set interface with create flags' TEST: TFM_S_PS_TEST_1002 - PASSED! > Executing 'TFM_S_PS_TEST_1003' Description: 'Set interface with NULL data pointer' TEST: TFM_S_PS_TEST_1003 - PASSED! > Executing 'TFM_S_PS_TEST_1004' Description: 'Set interface with invalid data length' TEST: TFM_S_PS_TEST_1004 - PASSED! > Executing 'TFM_S_PS_TEST_1005' Description: 'Set interface with write once UID' TEST: TFM_S_PS_TEST_1005 - PASSED! > Executing 'TFM_S_PS_TEST_1006' Description: 'Get interface with valid data' TEST: TFM_S_PS_TEST_1006 - PASSED! > Executing 'TFM_S_PS_TEST_1007' Description: 'Get interface with zero data length' TEST: TFM_S_PS_TEST_1007 - PASSED! > Executing 'TFM_S_PS_TEST_1008' Description: 'Get interface with invalid UIDs' TEST: TFM_S_PS_TEST_1008 - PASSED! > Executing 'TFM_S_PS_TEST_1009' Description: 'Get interface with invalid data lengths and offsets' TEST: TFM_S_PS_TEST_1009 - PASSED! > Executing 'TFM_S_PS_TEST_1010' Description: 'Get interface with NULL data pointer' TEST: TFM_S_PS_TEST_1010 - PASSED! > Executing 'TFM_S_PS_TEST_1011' Description: 'Get info interface with write once UID' TEST: TFM_S_PS_TEST_1011 - PASSED! > Executing 'TFM_S_PS_TEST_1012' Description: 'Get info interface with valid UID' TEST: TFM_S_PS_TEST_1012 - PASSED! > Executing 'TFM_S_PS_TEST_1013' Description: 'Get info interface with invalid UIDs' TEST: TFM_S_PS_TEST_1013 - PASSED! > Executing 'TFM_S_PS_TEST_1014' Description: 'Get info interface with NULL info pointer' TEST: TFM_S_PS_TEST_1014 - PASSED! > Executing 'TFM_S_PS_TEST_1015' Description: 'Remove interface with valid UID' TEST: TFM_S_PS_TEST_1015 - PASSED! > Executing 'TFM_S_PS_TEST_1016' Description: 'Remove interface with write once UID' TEST: TFM_S_PS_TEST_1016 - PASSED! > Executing 'TFM_S_PS_TEST_1017' Description: 'Remove interface with invalid UID' TEST: TFM_S_PS_TEST_1017 - PASSED! > Executing 'TFM_S_PS_TEST_1018' Description: 'Block compaction after remove' TEST: TFM_S_PS_TEST_1018 - PASSED! > Executing 'TFM_S_PS_TEST_1019' Description: 'Multiple partial gets' TEST: TFM_S_PS_TEST_1019 - PASSED! > Executing 'TFM_S_PS_TEST_1020' Description: 'Multiple sets to same UID from same thread' TEST: TFM_S_PS_TEST_1020 - PASSED! > Executing 'TFM_S_PS_TEST_1021' Description: 'Get support interface' TEST: TFM_S_PS_TEST_1021 - PASSED! > Executing 'TFM_S_PS_TEST_1022' Description: 'Set, get and remove interface with different asset sizes' TEST: TFM_S_PS_TEST_1022 - PASSED! TESTSUITE PASSED! Running Test Suite PS reliability tests (TFM_PS_TEST_3XXX)... > Executing 'TFM_S_PS_TEST_2001' Description: 'repetitive sets and gets in/from an asset' > Iteration 15 of 15 TEST: TFM_S_PS_TEST_2001 - PASSED! > Executing 'TFM_S_PS_TEST_2002' Description: 'repetitive sets, gets and removes' > Iteration 15 of 15 TEST: TFM_S_PS_TEST_2002 - PASSED! TESTSUITE PASSED! Running Test Suite PS rollback protection tests (TFM_S_PS_TEST_3XXX)... > Executing 'TFM_S_PS_TEST_3001' Description: 'Check PS area version when NV counters 1/2/3 have the same value' TEST: TFM_S_PS_TEST_3001 - PASSED! > Executing 'TFM_S_PS_TEST_3002' Description: 'Check PS area version when it is different from NV counters 1/2/3' TEST: TFM_S_PS_TEST_3002 - PASSED! > Executing 'TFM_S_PS_TEST_3003' Description: 'Check PS area version when NV counters 1 and 2 are equals, 3 is different, and PS area version match NV counters 1 and 2' TEST: TFM_S_PS_TEST_3003 - PASSED! > Executing 'TFM_S_PS_TEST_3004' Description: 'Check PS area version when NV counters 2 and 3 are equals, 1 is different and PS area version match NV counter 2 and 3' TEST: TFM_S_PS_TEST_3004 - PASSED! > Executing 'TFM_S_PS_TEST_3005' Description: 'Check PS area version when NV counters 2 and 3 are equals, 1 is different and PS area version match NV counter 1' TEST: TFM_S_PS_TEST_3005 - PASSED! > Executing 'TFM_S_PS_TEST_3006' Description: 'Check PS area version when NV counters 1, 2 and 3 have different values and PS area version match NV counter 1 value' TEST: TFM_S_PS_TEST_3006 - PASSED! > Executing 'TFM_S_PS_TEST_3007' Description: 'Check PS area version when NV counters 1, 2 and 3 have different values and PS area version match NV counter 2 value' TEST: TFM_S_PS_TEST_3007 - PASSED! > Executing 'TFM_S_PS_TEST_3008' Description: 'Check PS area version when NV counters 1, 2 and 3 have different values and PS area version match NV counter 3 value' TEST: TFM_S_PS_TEST_3008 - PASSED! > Executing 'TFM_S_PS_TEST_3009' Description: 'Check PS area version when NV counter 1 cannot be incremented' TEST: TFM_S_PS_TEST_3009 - PASSED! TESTSUITE PASSED! Running Test Suite PSA internal trusted storage S interface tests (TFM_S_ITS_TEST_1XXX)... > Executing 'TFM_S_ITS_TEST_1001' Description: 'Set interface' Set should not fail with valid UID (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:32) TEST: TFM_S_ITS_TEST_1001 - FAILED! > Executing 'TFM_S_ITS_TEST_1002' Description: 'Set interface with create flags' Set should not fail with no flags (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:91) TEST: TFM_S_ITS_TEST_1002 - FAILED! > Executing 'TFM_S_ITS_TEST_1003' Description: 'Set interface with NULL data pointer' Set should succeed with NULL data pointer and zero length (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:115) TEST: TFM_S_ITS_TEST_1003 - FAILED! > Executing 'TFM_S_ITS_TEST_1004' Description: 'Set interface with write once UID' Set should not rewrite a write once UID (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:138) TEST: TFM_S_ITS_TEST_1004 - FAILED! > Executing 'TFM_S_ITS_TEST_1005' Description: 'Get interface with valid data' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:186) TEST: TFM_S_ITS_TEST_1005 - FAILED! > Executing 'TFM_S_ITS_TEST_1006' Description: 'Get interface with zero data length' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:293) TEST: TFM_S_ITS_TEST_1006 - FAILED! > Executing 'TFM_S_ITS_TEST_1007' Description: 'Get interface with invalid UIDs' TEST: TFM_S_ITS_TEST_1007 - PASSED! > Executing 'TFM_S_ITS_TEST_1008' Description: 'Get interface with data lengths and offsets greater than UID length' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:426) TEST: TFM_S_ITS_TEST_1008 - FAILED! > Executing 'TFM_S_ITS_TEST_1009' Description: 'Get interface with NULL data pointer' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:541) TEST: TFM_S_ITS_TEST_1009 - FAILED! > Executing 'TFM_S_ITS_TEST_1010' Description: 'Get info interface with write once UID' Get info should not fail for write once UID (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:578) TEST: TFM_S_ITS_TEST_1010 - FAILED! > Executing 'TFM_S_ITS_TEST_1011' Description: 'Get info interface with valid UID' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:612) TEST: TFM_S_ITS_TEST_1011 - FAILED! > Executing 'TFM_S_ITS_TEST_1012' Description: 'Get info interface with invalid UIDs' TEST: TFM_S_ITS_TEST_1012 - PASSED! > Executing 'TFM_S_ITS_TEST_1013' Description: 'Remove interface with valid UID' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:708) TEST: TFM_S_ITS_TEST_1013 - FAILED! > Executing 'TFM_S_ITS_TEST_1014' Description: 'Remove interface with write once UID' Remove should not succeed with write once UID (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:751) TEST: TFM_S_ITS_TEST_1014 - FAILED! > Executing 'TFM_S_ITS_TEST_1015' Description: 'Remove interface with invalid UID' TEST: TFM_S_ITS_TEST_1015 - PASSED! > Executing 'TFM_S_ITS_TEST_1016' Description: 'Block compaction after remove' Set should not fail for UID 1 (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:790) TEST: TFM_S_ITS_TEST_1016 - FAILED! > Executing 'TFM_S_ITS_TEST_1017' Description: 'Multiple partial gets' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:860) TEST: TFM_S_ITS_TEST_1017 - FAILED! > Executing 'TFM_S_ITS_TEST_1018' Description: 'Multiple sets to same UID from same thread' First set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:911) TEST: TFM_S_ITS_TEST_1018 - FAILED! > Executing 'TFM_S_ITS_TEST_1019' Description: 'Set, get and remove interface with different asset sizes' Set should not fail with valid UID (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:995) TEST: TFM_S_ITS_TEST_1019 - FAILED! > Executing 'TFM_S_ITS_TEST_1020' Description: 'Set interface with invalid data length' TEST: TFM_S_ITS_TEST_1020 - PASSED! > Executing 'TFM_S_ITS_TEST_1021' Description: 'Get interface with invalid data lengths and offsets' TEST: TFM_S_ITS_TEST_1021 - PASSED! > Executing 'TFM_S_ITS_TEST_1022' Description: 'Get info interface with NULL info pointer' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/secure/psa_its_s_interface_testsuite.c:210) TEST: TFM_S_ITS_TEST_1022 - FAILED! > Executing 'TFM_S_ITS_TEST_1023' Description: 'Attempt to get a UID set by a different partition' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/secure/psa_its_s_interface_testsuite.c:253) TEST: TFM_S_ITS_TEST_1023 - FAILED! TESTSUITE FAILED! Number of failed tests: 18 of 23 Running Test Suite ITS reliability tests (TFM_ITS_TEST_2XXX)... > Executing 'TFM_S_ITS_TEST_2001' Description: 'repetitive sets and gets in/from an asset' Set should not fail with valid UID (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/secure/psa_its_s_reliability_testsuite.c:75) TEST: TFM_S_ITS_TEST_2001 - FAILED! > Executing 'TFM_S_ITS_TEST_2002' Description: 'repetitive sets, gets and removes' Set should not fail with valid UID (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/secure/psa_its_s_reliability_testsuite.c:133) TEST: TFM_S_ITS_TEST_2002 - FAILED! TESTSUITE FAILED! Number of failed tests: 2 of 2 Running Test Suite Crypto secure interface tests (TFM_S_CRYPTO_TEST_1XXX)... > Executing 'TFM_S_CRYPTO_TEST_1001' Description: 'Secure Key management interface' TEST: TFM_S_CRYPTO_TEST_1001 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1002' Description: 'Secure Symmetric encryption (AES-128-CBC) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:140) TEST: TFM_S_CRYPTO_TEST_1002 - FAILED! > Executing 'TFM_S_CRYPTO_TEST_1005' Description: 'Secure Symmetric encryption (AES-128-CTR) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:140) TEST: TFM_S_CRYPTO_TEST_1005 - FAILED! > Executing 'TFM_S_CRYPTO_TEST_1007' Description: 'Secure Symmetric encryption invalid cipher' TEST: TFM_S_CRYPTO_TEST_1007 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1008' Description: 'Secure Symmetric encryption invalid cipher (AES-152)' TEST: TFM_S_CRYPTO_TEST_1008 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1010' Description: 'Secure Unsupported Hash (SHA-1) interface' TEST: TFM_S_CRYPTO_TEST_1010 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1011' Description: 'Secure Hash (SHA-224) interface' TEST: TFM_S_CRYPTO_TEST_1011 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1012' Description: 'Secure Hash (SHA-256) interface' TEST: TFM_S_CRYPTO_TEST_1012 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1013' Description: 'Secure Hash (SHA-384) interface' TEST: TFM_S_CRYPTO_TEST_1013 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1014' Description: 'Secure Hash (SHA-512) interface' TEST: TFM_S_CRYPTO_TEST_1014 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1019' Description: 'Secure Unsupported HMAC (SHA-1) interface' TEST: TFM_S_CRYPTO_TEST_1019 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1020' Description: 'Secure HMAC (SHA-256) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:634) TEST: TFM_S_CRYPTO_TEST_1020 - FAILED! > Executing 'TFM_S_CRYPTO_TEST_1021' Description: 'Secure HMAC (SHA-384) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:634) TEST: TFM_S_CRYPTO_TEST_1021 - FAILED! > Executing 'TFM_S_CRYPTO_TEST_1022' Description: 'Secure HMAC (SHA-512) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:634) TEST: TFM_S_CRYPTO_TEST_1022 - FAILED! > Executing 'TFM_S_CRYPTO_TEST_1024' Description: 'Secure HMAC with long key (SHA-224) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:634) TEST: TFM_S_CRYPTO_TEST_1024 - FAILED! > Executing 'TFM_S_CRYPTO_TEST_1030' Description: 'Secure AEAD (AES-128-CCM) interface' Algorithm NOT SUPPORTED by the implementation - skip multipart API flow TEST: TFM_S_CRYPTO_TEST_1030 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1031' Description: 'Secure AEAD (AES-128-GCM) interface' Algorithm NOT SUPPORTED by the implementation - skip multipart API flow TEST: TFM_S_CRYPTO_TEST_1031 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1032' Description: 'Secure key policy interface' TEST: TFM_S_CRYPTO_TEST_1032 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1033' Description: 'Secure key policy check permissions' TEST: TFM_S_CRYPTO_TEST_1033 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1034' Description: 'Secure persistent key interface' Failed to import a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:1292) TEST: TFM_S_CRYPTO_TEST_1034 - FAILED! > Executing 'TFM_S_CRYPTO_TEST_1035' Description: 'Key access control' TEST: TFM_S_CRYPTO_TEST_1035 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1036' Description: 'Secure AEAD interface with truncated auth tag (AES-128-CCM-8)' Algorithm NOT SUPPORTED by the implementation - skip multipart API flow TEST: TFM_S_CRYPTO_TEST_1036 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1037' Description: 'Secure TLS 1.2 PRF key derivation' TEST: TFM_S_CRYPTO_TEST_1037 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1038' Description: 'Secure TLS-1.2 PSK-to-MasterSecret key derivation' TEST: TFM_S_CRYPTO_TEST_1038 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1039' Description: 'Secure HKDF key derivation' TEST: TFM_S_CRYPTO_TEST_1039 - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1040' Description: 'Secure ECDH key agreement' Error importing the private key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:1390) TEST: TFM_S_CRYPTO_TEST_1040 - FAILED! > Executing 'TFM_S_CRYPTO_TEST_1041' Description: 'Secure Symmetric encryption (AES-128-OFB) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:140) TEST: TFM_S_CRYPTO_TEST_1041 - FAILED! > Executing 'TFM_S_CRYPTO_TEST_1042' Description: 'Secure Symmetric encryption (AES-128-ECB) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:140) TEST: TFM_S_CRYPTO_TEST_1042 - FAILED! > Executing 'TFM_S_CRYPTO_TEST_1043)' Description: 'Secure Asymmetric encryption interface (RSA_OAEP)' CC:error_mapping_cc_to_mbedtls_rsa: Converted CC_ERROR 0 (0x00000000) to MBEDTLS_ERR 0 CC:error_mapping_cc_to_mbedtls_rsa: Converted CC_ERROR 0 (0x00000000) to MBEDTLS_ERR 0 TEST: TFM_S_CRYPTO_TEST_1043) - PASSED! > Executing 'TFM_S_CRYPTO_TEST_1044' Description: 'Secure Asymmetric encryption interface (RSA_PKCS1V15)' CC:error_mapping_cc_to_mbedtls_rsa: Converted CC_ERROR 0 (0x00000000) to MBEDTLS_ERR 0 CC:error_mapping_cc_to_mbedtls_rsa: Converted CC_ERROR 0 (0x00000000) to MBEDTLS_ERR 0 TEST: TFM_S_CRYPTO_TEST_1044 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1045' Description: 'Secure Sign and verify message interface (ECDSA-SECP256R1-SHA256)' Error importing the private key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:1726) TEST: TFM_NS_CRYPTO_TEST_1045 - FAILED! TESTSUITE FAILED! Number of failed tests: 11 of 31 Running Test Suite Initial Attestation Service secure interface tests(TFM_S_ATTEST_TEST_1XXX)... > Executing 'TFM_S_ATTEST_TEST_1004' Description: 'ECDSA signature test of attest token' TEST: TFM_S_ATTEST_TEST_1004 - PASSED! > Executing 'TFM_S_ATTEST_TEST_1005' Description: 'Negative test cases for initial attestation service' TEST: TFM_S_ATTEST_TEST_1005 - PASSED! TESTSUITE PASSED! Running Test Suite Platform Service Secure interface tests(TFM_S_PLATFORM_TEST_1XXX)... > Executing 'TFM_S_PLATFORM_TEST_1001' Description: 'Minimal platform service test' TEST: TFM_S_PLATFORM_TEST_1001 - PASSED! TESTSUITE PASSED! Running Test Suite IPC secure interface test (TFM_S_IPC_TEST_1XXX)... > Executing 'TFM_S_IPC_TEST_1001' Description: 'Accessing stateless service from secure partition' [IPC_SERVICE_TEST_STATELESS_ROT] Service called! arg=ffffabcd TEST: TFM_S_IPC_TEST_1001 - PASSED! TESTSUITE PASSED! *** Secure test suites summary *** Test suite 'PSA protected storage S interface tests (TFM_S_PS_TEST_1XXX)' has PASSED Test suite 'PS reliability tests (TFM_PS_TEST_3XXX)' has PASSED Test suite 'PS rollback protection tests (TFM_S_PS_TEST_3XXX)' has PASSED Test suite 'PSA internal trusted storage S interface tests (TFM_S_ITS_TEST_1XXX)' has FAILED Test suite 'ITS reliability tests (TFM_ITS_TEST_2XXX)' has FAILED Test suite 'Crypto secure interface tests (TFM_S_CRYPTO_TEST_1XXX)' has FAILED Test suite 'Initial Attestation Service secure interface tests(TFM_S_ATTEST_TEST_1XXX)' has PASSED Test suite 'Platform Service Secure interface tests(TFM_S_PLATFORM_TEST_1XXX)' has PASSED Test suite 'IPC secure interface test (TFM_S_IPC_TEST_1XXX)' has PASSED *** End of Secure test suites *** Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA protected storage NS interface tests (TFM_NS_PS_TEST_1XXX)... > Executing 'TFM_NS_PS_TEST_1001' Description: 'Set interface' TEST: TFM_NS_PS_TEST_1001 - PASSED! > Executing 'TFM_NS_PS_TEST_1002' Description: 'Set interface with create flags' TEST: TFM_NS_PS_TEST_1002 - PASSED! > Executing 'TFM_NS_PS_TEST_1003' Description: 'Set interface with NULL data pointer' TEST: TFM_NS_PS_TEST_1003 - PASSED! > Executing 'TFM_NS_PS_TEST_1004' Description: 'Set interface with write once UID' TEST: TFM_NS_PS_TEST_1004 - PASSED! > Executing 'TFM_NS_PS_TEST_1005' Description: 'Get interface with valid data' TEST: TFM_NS_PS_TEST_1005 - PASSED! > Executing 'TFM_NS_PS_TEST_1006' Description: 'Get interface with zero data length' TEST: TFM_NS_PS_TEST_1006 - PASSED! > Executing 'TFM_NS_PS_TEST_1007' Description: 'Get interface with invalid UIDs' TEST: TFM_NS_PS_TEST_1007 - PASSED! > Executing 'TFM_NS_PS_TEST_1008' Description: 'Get interface with invalid data lengths and offsets' TEST: TFM_NS_PS_TEST_1008 - PASSED! > Executing 'TFM_NS_PS_TEST_1009' Description: 'Get interface with NULL data pointer' TEST: TFM_NS_PS_TEST_1009 - PASSED! > Executing 'TFM_NS_PS_TEST_1010' Description: 'Get info interface with write once UID' TEST: TFM_NS_PS_TEST_1010 - PASSED! > Executing 'TFM_NS_PS_TEST_1011' Description: 'Get info interface with valid UID' TEST: TFM_NS_PS_TEST_1011 - PASSED! > Executing 'TFM_NS_PS_TEST_1012' Description: 'Get info interface with invalid UIDs' TEST: TFM_NS_PS_TEST_1012 - PASSED! > Executing 'TFM_NS_PS_TEST_1013' Description: 'Remove interface with valid UID' TEST: TFM_NS_PS_TEST_1013 - PASSED! > Executing 'TFM_NS_PS_TEST_1014' Description: 'Remove interface with write once UID' TEST: TFM_NS_PS_TEST_1014 - PASSED! > Executing 'TFM_NS_PS_TEST_1015' Description: 'Remove interface with invalid UID' TEST: TFM_NS_PS_TEST_1015 - PASSED! > Executing 'TFM_NS_PS_TEST_1021' Description: 'Block compaction after remove' TEST: TFM_NS_PS_TEST_1021 - PASSED! > Executing 'TFM_NS_PS_TEST_1022' Description: 'Multiple partial gets' TEST: TFM_NS_PS_TEST_1022 - PASSED! > Executing 'TFM_NS_PS_TEST_1023' Description: 'Multiple sets to same UID from same thread' TEST: TFM_NS_PS_TEST_1023 - PASSED! > Executing 'TFM_NS_PS_TEST_1024' Description: 'Get support interface' TEST: TFM_NS_PS_TEST_1024 - PASSED! > Executing 'TFM_NS_PS_TEST_1025' Description: 'Set, get and remove interface with different asset sizes' TEST: TFM_NS_PS_TEST_1025 - PASSED! TESTSUITE PASSED! Running Test Suite PSA internal trusted storage NS interface tests (TFM_NS_ITS_TEST_1XXX)... > Executing 'TFM_NS_ITS_TEST_1001' Description: 'Set interface' Set should not fail with valid UID (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:32) TEST: TFM_NS_ITS_TEST_1001 - FAILED! > Executing 'TFM_NS_ITS_TEST_1002' Description: 'Set interface with create flags' Note: The UID in this test has already been created with the PSA_STORAGE_FLAG_WRITE_ONCE flag in a previous test run. Wipe the storage area to run the full test. TEST: TFM_NS_ITS_TEST_1002 - PASSED! > Executing 'TFM_NS_ITS_TEST_1003' Description: 'Set interface with NULL data pointer' Set should succeed with NULL data pointer and zero length (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:115) TEST: TFM_NS_ITS_TEST_1003 - FAILED! > Executing 'TFM_NS_ITS_TEST_1004' Description: 'Set interface with write once UID' Get should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:146) TEST: TFM_NS_ITS_TEST_1004 - FAILED! > Executing 'TFM_NS_ITS_TEST_1005' Description: 'Get interface with valid data' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:186) TEST: TFM_NS_ITS_TEST_1005 - FAILED! > Executing 'TFM_NS_ITS_TEST_1006' Description: 'Get interface with zero data length' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:293) TEST: TFM_NS_ITS_TEST_1006 - FAILED! > Executing 'TFM_NS_ITS_TEST_1007' Description: 'Get interface with invalid UIDs' TEST: TFM_NS_ITS_TEST_1007 - PASSED! > Executing 'TFM_NS_ITS_TEST_1008' Description: 'Get interface with invalid data lengths and offsets' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:426) TEST: TFM_NS_ITS_TEST_1008 - FAILED! > Executing 'TFM_NS_ITS_TEST_1009' Description: 'Get interface with NULL data pointer' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:541) TEST: TFM_NS_ITS_TEST_1009 - FAILED! > Executing 'TFM_NS_ITS_TEST_1010' Description: 'Get info interface with write once UID' TEST: TFM_NS_ITS_TEST_1010 - PASSED! > Executing 'TFM_NS_ITS_TEST_1011' Description: 'Get info interface with valid UID' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:612) TEST: TFM_NS_ITS_TEST_1011 - FAILED! > Executing 'TFM_NS_ITS_TEST_1012' Description: 'Get info interface with invalid UIDs' TEST: TFM_NS_ITS_TEST_1012 - PASSED! > Executing 'TFM_NS_ITS_TEST_1013' Description: 'Remove interface with valid UID' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:708) TEST: TFM_NS_ITS_TEST_1013 - FAILED! > Executing 'TFM_NS_ITS_TEST_1014' Description: 'Remove interface with write once UID' TEST: TFM_NS_ITS_TEST_1014 - PASSED! > Executing 'TFM_NS_ITS_TEST_1015' Description: 'Remove interface with invalid UID' TEST: TFM_NS_ITS_TEST_1015 - PASSED! > Executing 'TFM_NS_ITS_TEST_1016' Description: 'Block compaction after remove' Set should not fail for UID 1 (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:790) TEST: TFM_NS_ITS_TEST_1016 - FAILED! > Executing 'TFM_NS_ITS_TEST_1017' Description: 'Multiple partial gets' Set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:860) TEST: TFM_NS_ITS_TEST_1017 - FAILED! > Executing 'TFM_NS_ITS_TEST_1018' Description: 'Multiple sets to same UID from same thread' First set should not fail (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:911) TEST: TFM_NS_ITS_TEST_1018 - FAILED! > Executing 'TFM_NS_ITS_TEST_1019' Description: 'Set, get and remove interface with different asset sizes' Set should not fail with valid UID (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/its/its_tests_common.c:995) TEST: TFM_NS_ITS_TEST_1019 - FAILED! TESTSUITE FAILED! Number of failed tests: 13 of 19 Running Test Suite Crypto non-secure interface test (TFM_NS_CRYPTO_TEST_1XXX)... > Executing 'TFM_NS_CRYPTO_TEST_1001' Description: 'Non Secure Key management interface' TEST: TFM_NS_CRYPTO_TEST_1001 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1002' Description: 'Non Secure Symmetric encryption (AES-128-CBC) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:140) TEST: TFM_NS_CRYPTO_TEST_1002 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1005' Description: 'Non Secure Symmetric encryption (AES-128-CTR) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:140) TEST: TFM_NS_CRYPTO_TEST_1005 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1007' Description: 'Non Secure Symmetric encryption invalid cipher' TEST: TFM_NS_CRYPTO_TEST_1007 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1008' Description: 'Non Secure Symmetric encryption invalid cipher (AES-152)' TEST: TFM_NS_CRYPTO_TEST_1008 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1010' Description: 'Non Secure Unsupported Hash (SHA-1) interface' TEST: TFM_NS_CRYPTO_TEST_1010 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1011' Description: 'Non Secure Hash (SHA-224) interface' TEST: TFM_NS_CRYPTO_TEST_1011 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1012' Description: 'Non Secure Hash (SHA-256) interface' TEST: TFM_NS_CRYPTO_TEST_1012 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1013' Description: 'Non Secure Hash (SHA-384) interface' TEST: TFM_NS_CRYPTO_TEST_1013 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1014' Description: 'Non Secure Hash (SHA-512) interface' TEST: TFM_NS_CRYPTO_TEST_1014 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1019' Description: 'Non Secure Unsupported HMAC (SHA-1) interface' TEST: TFM_NS_CRYPTO_TEST_1019 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1020' Description: 'Non Secure HMAC (SHA-256) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:634) TEST: TFM_NS_CRYPTO_TEST_1020 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1021' Description: 'Non Secure HMAC (SHA-384) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:634) TEST: TFM_NS_CRYPTO_TEST_1021 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1022' Description: 'Non Secure HMAC (SHA-512) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:634) TEST: TFM_NS_CRYPTO_TEST_1022 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1024' Description: 'Non Secure HMAC with long key (SHA-224) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:634) TEST: TFM_NS_CRYPTO_TEST_1024 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1030' Description: 'Non Secure AEAD (AES-128-CCM) interface' Algorithm NOT SUPPORTED by the implementation - skip multipart API flow TEST: TFM_NS_CRYPTO_TEST_1030 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1031' Description: 'Non Secure AEAD (AES-128-GCM) interface' Algorithm NOT SUPPORTED by the implementation - skip multipart API flow TEST: TFM_NS_CRYPTO_TEST_1031 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1032' Description: 'Non Secure key policy interface' TEST: TFM_NS_CRYPTO_TEST_1032 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1033' Description: 'Non Secure key policy check permissions' TEST: TFM_NS_CRYPTO_TEST_1033 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1034' Description: 'Non Secure persistent key interface' Failed to import a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:1292) TEST: TFM_NS_CRYPTO_TEST_1034 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1035' Description: 'Non Secure AEAD interface with truncated auth tag (AES-128-CCM-8)' Algorithm NOT SUPPORTED by the implementation - skip multipart API flow TEST: TFM_NS_CRYPTO_TEST_1035 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1036' Description: 'Non Secure TLS 1.2 PRF key derivation' TEST: TFM_NS_CRYPTO_TEST_1036 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1037' Description: 'Non Secure TLS-1.2 PSK-to-MasterSecret key derivation' TEST: TFM_NS_CRYPTO_TEST_1037 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1038' Description: 'Non Secure HKDF key derivation' TEST: TFM_NS_CRYPTO_TEST_1038 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1039' Description: 'Non Secure ECDH key agreement' Error importing the private key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:1390) TEST: TFM_NS_CRYPTO_TEST_1039 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1040' Description: 'Non Secure Symmetric encryption (AES-128-OFB) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:140) TEST: TFM_NS_CRYPTO_TEST_1040 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1041' Description: 'Non Secure Symmetric encryption (AES-128-ECB) interface' Error importing a key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:140) TEST: TFM_NS_CRYPTO_TEST_1041 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1042' Description: 'Non Secure Asymmetric encryption interface (RSA_OAEP)' CC:error_mapping_cc_to_mbedtls_rsa: Converted CC_ERROR 0 (0x00000000) to MBEDTLS_ERR 0 CC:error_mapping_cc_to_mbedtls_rsa: Converted CC_ERROR 0 (0x00000000) to MBEDTLS_ERR 0 TEST: TFM_NS_CRYPTO_TEST_1042 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1043' Description: 'Non Secure Asymmetric encryption interface (RSA_PKCS1V15)' CC:error_mapping_cc_to_mbedtls_rsa: Converted CC_ERROR 0 (0x00000000) to MBEDTLS_ERR 0 CC:error_mapping_cc_to_mbedtls_rsa: Converted CC_ERROR 0 (0x00000000) to MBEDTLS_ERR 0 TEST: TFM_NS_CRYPTO_TEST_1043 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1044' Description: 'Non Secure Sign and verify message interface (ECDSA-SECP256R1-SHA256)' Error importing the private key (Failed at D:/Projects/tf-m6/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/suites/crypto/crypto_tests_common.c:1726) TEST: TFM_NS_CRYPTO_TEST_1044 - FAILED! TESTSUITE FAILED! Number of failed tests: 11 of 30 Running Test Suite Platform Service Non-Secure interface tests(TFM_NS_PLATFORM_TEST_1XXX)... > Executing 'TFM_NS_PLATFORM_TEST_1001' Description: 'Minimal platform service test' TEST: TFM_NS_PLATFORM_TEST_1001 - PASSED! TESTSUITE PASSED! Running Test Suite Initial Attestation Service non-secure interface tests(TFM_NS_ATTEST_TEST_1XXX)... > Executing 'TFM_NS_ATTEST_TEST_1004' Description: 'ECDSA signature test of attest token' TEST: TFM_NS_ATTEST_TEST_1004 - PASSED! > Executing 'TFM_NS_ATTEST_TEST_1005' Description: 'Negative test cases for initial attestation service' TEST: TFM_NS_ATTEST_TEST_1005 - PASSED! TESTSUITE PASSED! Running Test Suite QCBOR regression test(TFM_NS_QCBOR_TEST_1XXX)... > Executing 'TFM_NS_QCBOR_TEST_1001' Description: 'Regression test of QCBOR library' TEST: TFM_NS_QCBOR_TEST_1001 - PASSED! TESTSUITE PASSED! Running Test Suite T_COSE regression test(TFM_NS_T_COSE_TEST_1XXX)... > Executing 'TFM_NS_T_COSE_TEST_1001' Description: 'Regression test of t_cose library' TEST: TFM_NS_T_COSE_TEST_1001 - PASSED! TESTSUITE PASSED! Running Test Suite PSA firmware update NS interface tests (TFM_NS_FWU_TEST_1xxx)... > Executing 'TFM_NS_FWU_TEST_1001' Description: 'Write, install and abort interface' TEST: TFM_NS_FWU_TEST_1001 - PASSED! > Executing 'TFM_NS_FWU_TEST_1003' Description: 'Write interface with image_offset + block_size overflow' TFM FWU: write flash failed. TEST: TFM_NS_FWU_TEST_1003 - PASSED! > Executing 'TFM_NS_FWU_TEST_1004' Description: 'Install interface with NULL dependency uuid' TEST: TFM_NS_FWU_TEST_1004 - PASSED! > Executing 'TFM_NS_FWU_TEST_1005' Description: 'Install interface with NULL dependency version' TEST: TFM_NS_FWU_TEST_1005 - PASSED! > Executing 'TFM_NS_FWU_TEST_1006' Description: 'Install before write' TEST: TFM_NS_FWU_TEST_1006 - PASSED! > Executing 'TFM_NS_FWU_TEST_1007' Description: 'Install after abort' TEST: TFM_NS_FWU_TEST_1007 - PASSED! > Executing 'TFM_NS_FWU_TEST_1008' Description: 'Abort interface with no image is being installing' TEST: TFM_NS_FWU_TEST_1008 - PASSED! > Executing 'TFM_NS_FWU_TEST_1009' Description: 'Query interface with the active image' TEST: TFM_NS_FWU_TEST_1009 - PASSED! > Executing 'TFM_NS_FWU_TEST_1011' Description: 'Query interface invald image id' TFM FWU: invalid slot_id: 3 TEST: TFM_NS_FWU_TEST_1011 - PASSED! > Executing 'TFM_NS_FWU_TEST_1012' Description: 'Accept interface' TEST: TFM_NS_FWU_TEST_1012 - PASSED! > Executing 'TFM_NS_FWU_TEST_1014' Description: 'Image update with dependency, no new image is required' TEST: TFM_NS_FWU_TEST_1014 - PASSED! > Executing 'TFM_NS_FWU_TEST_1015' Description: 'Image update with dependency, new image is required' TEST: TFM_NS_FWU_TEST_1015 - PASSED! > Executing 'TFM_NS_FWU_TEST_1016' Description: 'psa_fwu_write boundary test' TEST: TFM_NS_FWU_TEST_1016 - PASSED! TESTSUITE PASSED! Running Test Suite Core non-secure positive tests (TFM_NS_CORE_TEST_1XXX)... > Executing 'TFM_NS_CORE_TEST_1001' Description: 'Test service request from NS thread mode' TEST: TFM_NS_CORE_TEST_1001 - PASSED! > Executing 'TFM_NS_CORE_TEST_1003' Description: 'Test the success of service init' TEST: TFM_NS_CORE_TEST_1003 - PASSED! > Executing 'TFM_NS_CORE_TEST_1007' Description: 'Test secure service buffer accesses' TEST: TFM_NS_CORE_TEST_1007 - PASSED! > Executing 'TFM_NS_CORE_TEST_1008' Description: 'Test secure service to service call' TEST: TFM_NS_CORE_TEST_1008 - PASSED! > Executing 'TFM_NS_CORE_TEST_1010' Description: 'Test secure service to service call with buffer handling' TEST: TFM_NS_CORE_TEST_1010 - PASSED! > Executing 'TFM_NS_CORE_TEST_1014' Description: 'Test service parameter sanitization' TEST: TFM_NS_CORE_TEST_1014 - PASSED! > Executing 'TFM_NS_CORE_TEST_1015' Description: 'Test outvec write' TEST: TFM_NS_CORE_TEST_1015 - PASSED! TESTSUITE PASSED! Running Test Suite IPC non-secure interface test (TFM_NS_IPC_TEST_1XXX)... > Executing 'TFM_NS_IPC_TEST_1001' Description: 'Get PSA framework version' The version of the PSA Framework API is 257. TEST: TFM_NS_IPC_TEST_1001 - PASSED! > Executing 'TFM_NS_IPC_TEST_1002' Description: 'Get version of an RoT Service' The service version is 1. TEST: TFM_NS_IPC_TEST_1002 - PASSED! > Executing 'TFM_NS_IPC_TEST_1003' Description: 'Connect to an RoT Service' Connect success! TEST: TFM_NS_IPC_TEST_1003 - PASSED! > Executing 'TFM_NS_IPC_TEST_1004' Description: 'Call an RoT Service' TFM service support version is 1. psa_call is successful! outvec1 is: It is just for IPC call test. outvec2 is: It is just for IPC call test. TEST: TFM_NS_IPC_TEST_1004 - PASSED! > Executing 'TFM_NS_IPC_TEST_1005' Description: 'Call IPC_INIT_BASIC_TEST service' Connect success! Call success! TEST: TFM_NS_IPC_TEST_1005 - PASSED! > Executing 'TFM_NS_IPC_TEST_1006' Description: 'Call PSA RoT access APP RoT memory test service' Connect success! Call success! TEST: TFM_NS_IPC_TEST_1006 - PASSED! > Executing 'TFM_NS_IPC_TEST_1010' Description: 'Test psa_call with the status of PSA_ERROR_PROGRAMMER_ERROR' Connect success! The first time call success! The second time call success! TEST: TFM_NS_IPC_TEST_1010 - PASSED! > Executing 'TFM_NS_IPC_TEST_1012' Description: 'Accessing stateless service from non-secure client' [IPC_SERVICE_TEST_STATELESS_ROT] Service called! arg=ffffabcd TEST: TFM_NS_IPC_TEST_1012 - PASSED! TESTSUITE PASSED! Running Test Suite TFM IRQ Test (TFM_IRQ_TEST_1xxx)... > Executing 'TFM_NS_IRQ_TEST_SLIH_1001' Description: 'SLIH HANDLING Case 1' TEST: TFM_NS_IRQ_TEST_SLIH_1001 - PASSED! TESTSUITE PASSED! *** Non-secure test suites summary *** Test suite 'PSA protected storage NS interface tests (TFM_NS_PS_TEST_1XXX)' has PASSED Test suite 'PSA internal trusted storage NS interface tests (TFM_NS_ITS_TEST_1XXX)' has FAILED Test suite 'Crypto non-secure interface test (TFM_NS_CRYPTO_TEST_1XXX)' has FAILED Test suite 'Platform Service Non-Secure interface tests(TFM_NS_PLATFORM_TEST_1XXX)' has PASSED Test suite 'Initial Attestation Service non-secure interface tests(TFM_NS_ATTEST_TEST_1XXX)' has PASSED Test suite 'QCBOR regression test(TFM_NS_QCBOR_TEST_1XXX)' has PASSED Test suite 'T_COSE regression test(TFM_NS_T_COSE_TEST_1XXX)' has PASSED Test suite 'PSA firmware update NS interface tests (TFM_NS_FWU_TEST_1xxx)' has PASSED Test suite 'Core non-secure positive tests (TFM_NS_CORE_TEST_1XXX)' has PASSED Test suite 'IPC non-secure interface test (TFM_NS_IPC_TEST_1XXX)' has PASSED Test suite 'TFM IRQ Test (TFM_IRQ_TEST_1xxx)' has PASSED *** End of Non-secure test suites *** -- *Thomas Törnblom*, /Product Engineer/ IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com Website: www.iar.com <http://www.iar.com> Twitter: www.twitter.com/iarsystems <http://www.twitter.com/iarsystems>

4 years, 2 months

1
0
0 0

nucleo_l552ze_q platform does not build since TF-M 1.5

by Michel JAOUEN

Hello, This platform is tested for profile medium and low (-DTFM_PROFILE=profile_small or -DTFM_PROFILE=profile_medium). I just checked on master with medium profile and GNUARM. The default config takes a crypto config with its associated crypto tests that leads to overlap in flash area. (This device has 512Kbytes Flash) Best Regards ST Restricted From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Bøe, Sebastian via TF-M Sent: mercredi 22 décembre 2021 13:40 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] nucleo_l552ze_q platform does not build since TF-M 1.5 Hi, I am observing that the nucleo_l552ze_q platform is producing hex files that overlap since the 1.5 release. Tested on master and 1.5. Is there an STM maintainer that could look into this? Steps to reproduce: rm -rf cmake_build && cmake -S . -B cmake_build -DTFM_PLATFORM=stm/nucleo_l552ze_q -DTFM_TOOLCHAIN_FILE=toolchain_GNUARM.cmake -DCMAKE_BUILD_TYPE=MinSizeRel -DTEST_S=ON -DTEST_NS=ON && make -C cmake_build install && /usr/bin/python3.8 /home/sebo/ncs/zephyr/scripts/mergehex.py -o merged.hex $(find cmake_build -name "*.hex") "/usr/bin/python3.8 /home/sebo/ncs/zephyr/scripts/mergehex.py" must be replaced with the preferred hex file merging tool. output: Traceback (most recent call last): File "/home/sebo/ncs/zephyr/scripts/mergehex.py", line 28, in merge_hex_files ih.merge(to_merge, overlap=overlap) File "/home/sebo/.local/lib/python3.8/site-packages/intelhex/__init__.py", line 875, in merge raise AddressOverlapError( intelhex.AddressOverlapError: Data overlapped at address 0xC014400 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/sebo/ncs/zephyr/scripts/mergehex.py", line 56, in <module> main() File "/home/sebo/ncs/zephyr/scripts/mergehex.py", line 52, in main merge_hex_files(args.output, args.input_files, args.overlap) File "/home/sebo/ncs/zephyr/scripts/mergehex.py", line 30, in merge_hex_files raise AddressOverlapError("{} has merge issues".format(hex_file_path)) intelhex.AddressOverlapError: cmake_build/install/outputs/STM/NUCLEO_L552ZE_Q/tfm_s.hex has merge issues PS: Depending on the revision tested, it might be necessary to also apply this patch: modified platform/ext/target/stm/common/stm32l5xx/CMakeLists.txt @@ -90,7 +90,7 @@ target_sources(platform_s ${CMAKE_CURRENT_SOURCE_DIR}/hal/Src/stm32l5xx_hal_gtzc.c ${CMAKE_SOURCE_DIR}/platform/ext/common/tfm_hal_isolation_mpu_v8m.c ${CMAKE_SOURCE_DIR}/platform/ext/common/tfm_hal_nvic.c - $<$<BOOL:${TFM_PARTITION_PLATFORM}>:${CMAKE_CURRENT_SOURCE_DIR}/secure/tfm_platform_system> + $<$<BOOL:${TFM_PARTITION_PLATFORM}>:${CMAKE_CURRENT_SOURCE_DIR}/secure/tfm_platform_system.c> ${CMAKE_CURRENT_SOURCE_DIR}/hal/Src/stm32l5xx_hal_rng.c ${CMAKE_CURRENT_SOURCE_DIR}/hal/Src/stm32l5xx_hal_rng_ex.c PUBLIC

4 years, 3 months

2
1
0 0

nucleo_l552ze_q platform does not build since TF-M 1.5

by Bøe, Sebastian

Hi, I am observing that the nucleo_l552ze_q platform is producing hex files that overlap since the 1.5 release. Tested on master and 1.5. Is there an STM maintainer that could look into this? Steps to reproduce: rm -rf cmake_build && cmake -S . -B cmake_build -DTFM_PLATFORM=stm/nucleo_l552ze_q -DTFM_TOOLCHAIN_FILE=toolchain_GNUARM.cmake -DCMAKE_BUILD_TYPE=MinSizeRel -DTEST_S=ON -DTEST_NS=ON && make -C cmake_build install && /usr/bin/python3.8 /home/sebo/ncs/zephyr/scripts/mergehex.py -o merged.hex $(find cmake_build -name "*.hex") "/usr/bin/python3.8 /home/sebo/ncs/zephyr/scripts/mergehex.py" must be replaced with the preferred hex file merging tool. output: Traceback (most recent call last): File "/home/sebo/ncs/zephyr/scripts/mergehex.py", line 28, in merge_hex_files ih.merge(to_merge, overlap=overlap) File "/home/sebo/.local/lib/python3.8/site-packages/intelhex/__init__.py", line 875, in merge raise AddressOverlapError( intelhex.AddressOverlapError: Data overlapped at address 0xC014400 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/sebo/ncs/zephyr/scripts/mergehex.py", line 56, in <module> main() File "/home/sebo/ncs/zephyr/scripts/mergehex.py", line 52, in main merge_hex_files(args.output, args.input_files, args.overlap) File "/home/sebo/ncs/zephyr/scripts/mergehex.py", line 30, in merge_hex_files raise AddressOverlapError("{} has merge issues".format(hex_file_path)) intelhex.AddressOverlapError: cmake_build/install/outputs/STM/NUCLEO_L552ZE_Q/tfm_s.hex has merge issues PS: Depending on the revision tested, it might be necessary to also apply this patch: modified platform/ext/target/stm/common/stm32l5xx/CMakeLists.txt @@ -90,7 +90,7 @@ target_sources(platform_s ${CMAKE_CURRENT_SOURCE_DIR}/hal/Src/stm32l5xx_hal_gtzc.c ${CMAKE_SOURCE_DIR}/platform/ext/common/tfm_hal_isolation_mpu_v8m.c ${CMAKE_SOURCE_DIR}/platform/ext/common/tfm_hal_nvic.c - $<$<BOOL:${TFM_PARTITION_PLATFORM}>:${CMAKE_CURRENT_SOURCE_DIR}/secure/tfm_platform_system> + $<$<BOOL:${TFM_PARTITION_PLATFORM}>:${CMAKE_CURRENT_SOURCE_DIR}/secure/tfm_platform_system.c> ${CMAKE_CURRENT_SOURCE_DIR}/hal/Src/stm32l5xx_hal_rng.c ${CMAKE_CURRENT_SOURCE_DIR}/hal/Src/stm32l5xx_hal_rng_ex.c PUBLIC

4 years, 3 months

1
0
0 0

Eliminate unnecessary space in tfm_s.bin

by Sherry Zhang

Hi, Currently, in the compiler link script, the CMSE VENEER section is placed at a fixed address which is at the end of tfm code. See code for armclang<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e…> and gnu arm<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e…>. Placing the veneers at the fixed address has the benefit that the when the secure image updates, the veneer symbols remain unchanged. So, the nonsecure image does not have to be updated together. The problem is that the size of tfm_s.bin is always the same in different TF-M build configurations(debug mode, release mode, profile small, profile large and so on). So, there can be large empty space between the end of tfm code and the veneer section. As we discussed on today's tech forum meeting, I propose to move the LR_VENEER from the end of tfm code to right after the secure vector table. In this way, the space between the tfm code and the veneers section is eliminated. Also, the supported number of interrupts for each platform is fixed. So, the size of the vector table is fixed for each platform. So, the start address of veneer section is still fixed for each platform. The size of tfm_s.bin is reduced significantly after this change. Take the AN521 platform for example, the size of tfm_s.bin has a 70 percent reduction. The link script change for armclang<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12620/6/plat…> and gnu arm<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12620/6/plat…> in this patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12620/> can help me demonstrating my proposal. I am not hurry asking for review and merge this patch. As it impacts all the platforms, I want to get confirmed that all platforms which are using the common link script are happy with this proposal. Any comments or especially concerns on this proposal? Thanks, Regards, Sherry Zhang

4 years, 3 months

3
5
0 0

Power management and TFM

by Suresh.Marisetty＠infineon.com

Hi, Wondering if anybody can throw some light on any ongoing efforts on power management on a system with TFM (deep sleep, etc). thanks Suresh Marisetty Infineon Semiconductor Corporation CYSC CSS ICW SW SSE Mobile: +5103863997 Suresh.Marisetty(a)infineon.com<mailto:Suresh.Marisetty@infineon.com>

4 years, 3 months

3
2
0 0

Re: [TF-M] Change in ...trusted-firmware-m[master]: Platform: Refine image flash layout

by Thomas Törnblom

I'm working on the IAR part of this and I'm having a problem with the following test in isolation level 3: --- Running Test Suite TFM IRQ Test (TFM_IRQ_TEST_1xxx)... > Executing 'TFM_NS_IRQ_TEST_SLIH_1001' Description: 'SLIH HANDLING Case 1' --- If I run the test at full speed, it will run into a MemManage fault while if I single step through the entire test it will pass. Is there a race condition somewhere in there? If I disable the SLIH tests it succeeds. The exception happens when dereferencing "dev" in this function: bool timer_cmsdk_is_initialized(const struct timer_cmsdk_dev_t* dev) { return dev->data->is_initialized; } dev is 0x30002440 at the time. I've been trying to figure out what part of the memory protection system it is that is causing the exception. DACCVIOL is set and MMFAR shows the faulting address. Ideas? The build line: cmake -GNinja -S .. -B . -DTFM_PLATFORM=arm/musca_b1/sse_200 "-DTFM_TOOLCHAIN_FILE=..\toolchain_IARARM.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=Debug -DBL2=ON -DTFM_ISOLATION_LEVEL=3 -DTEST_NS_SLIH_IRQ=ON -DTEST_NS_QCBOR=OFF Notice that this build runs into a linker bug in the IAR toolchain and I have a non-released fixed version I'm using, in case anyone is attempting to replicate the issue. Cheers, Thomas Den 2021-12-17 kl. 11:30, skrev TrustedFirmware Code Review (Code Review): > > Attention is currently required from: Kevin Peng, Ken Liu, David Hu, > Chris Brand, Anton Komlev, Thomas Törnblom. > > "Build Successful > > http://ci.trustedfirmware.org/job/tf-m-static/3226/display/redirect : > SUCCESS" > > Patch set 16:Verified +1 > > View Change > <https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12620> > > To view, visit change 12620 > <https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12620>. > To unsubscribe, or for help writing mail filters, visit settings > <https://review.trustedfirmware.org/settings>. > > Gerrit-Project: TF-M/trusted-firmware-m > Gerrit-Branch: master > Gerrit-Change-Id: I0084aef576d90af45513c7eaae58ba6c6dbbddab > Gerrit-Change-Number: 12620 > Gerrit-PatchSet: 16 > Gerrit-Owner: sherryzhang <sherry.zhang2(a)arm.com> > Gerrit-Reviewer: Anton Komlev <Anton.Komlev(a)arm.com> > Gerrit-Reviewer: David Hu <david.hu(a)arm.com> > Gerrit-Reviewer: Ken Liu <ken.liu(a)arm.com> > Gerrit-Reviewer: Sebastian Bøe <Sebastian.boe(a)nordicsemi.no> > Gerrit-Reviewer: Thomas Törnblom <thomas.tornblom(a)iar.com> > Gerrit-Reviewer: TrustedFirmware Code Review > Gerrit-Reviewer: sherryzhang <sherry.zhang2(a)arm.com> > Gerrit-CC: Andrej Butok <andrey.butok(a)nxp.com> > Gerrit-CC: Chris Brand <chris.brand(a)cypress.com> > Gerrit-CC: Gabor Abonyi <gabor.abonyi(a)arm.com> > Gerrit-CC: Kevin Peng <kevin.peng(a)arm.com> > Gerrit-CC: Michel Jaouen > Gerrit-CC: Márk Horváth <mark.horvath(a)arm.com> > Gerrit-CC: Satish Kumar <satish.kumar01(a)arm.com> > Gerrit-CC: jamie.mccrae(a)lairdconnect.com > Gerrit-Attention: Kevin Peng <kevin.peng(a)arm.com> > Gerrit-Attention: Ken Liu <ken.liu(a)arm.com> > Gerrit-Attention: David Hu <david.hu(a)arm.com> > Gerrit-Attention: Chris Brand <chris.brand(a)cypress.com> > Gerrit-Attention: Anton Komlev <Anton.Komlev(a)arm.com> > Gerrit-Attention: Thomas Törnblom <thomas.tornblom(a)iar.com> > Gerrit-Comment-Date: Fri, 17 Dec 2021 10:30:20 +0000 > Gerrit-HasComments: No > Gerrit-Has-Labels: Yes > Gerrit-MessageType: comment -- *Thomas Törnblom*, /Product Engineer/ IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com Website: www.iar.com <http://www.iar.com> Twitter: www.twitter.com/iarsystems <http://www.twitter.com/iarsystems>

4 years, 3 months

2
2
0 0

Any existing efforts on enabling X.509 certificate support inside TF-M

by Li, Jun R

Hi everyone, I’m wondering if there is any existing effort on enabling X.509 CSR generation and certificate verification inside TF-M? Our project has some custom secure partitions which need to generate the CSR and verify the issued certificates by themselves. The current TF-M implementation hasn’t added X.509’s support. So, I’m wondering if any open source project already does that which we can leverage? Regards, Jun Li Intel Corporation, CA

4 years, 3 months

3
3
0 0

Technical Forum call - Dec 23 CANCELLED

by Anton Komlev

Hello, In the light of the end of the year celebrations expecting not many joiners on Dec 23, specially for US time zone, hence let's cancel the forum at the next week. Thanks and wish you the great holidays, Anton

4 years, 3 months

1
0
0 0

Tip on cloning TF-M on OS X Monterey

by Kevin Townsend

I recently switched to a new MBP that ships with OS X Monterey, and on both 12.0 and 12.1 (released this week) git clone seems to be broken when you're using HTTP rather than SSH: digital envelope routines:CRYPTO_internal:bad key length In order to clone TF-M, I had to make the following changes. 1. Add these details to $HOME/.ssh/config (microbuilder being my github username, associated with my TF-M account): Host trustedfirmware.org User microbuilder Hostname review.trustedfirmware.org Port 29418 IdentityFile ~/.ssh/id_rsa IdentitiesOnly yes 2. Then try to clone with: $ git clone trustedfirmware.org:/TF-M/trusted-firmware-m.git This fails, however, since it tries to clone tf-m-tests.git, so: 3. Edit lib/ext/tf-m-tests/fetch_repo.cmake, changing: FetchContent_Declare(tfm_test_repo GIT_REPOSITORY trustedfirmware.org:TF-M/tf-m-tests.git # GIT_REPOSITORY https://git.trustedfirmware.org/TF-M/tf-m-tests.git GIT_TAG ${TFM_TEST_REPO_VERSION} GIT_PROGRESS TRUE ) This let me at least clone TF-M until the issues with HTTP-based cloning are fixed. Hope this is useful to someone else working on OS X natively. Kevin

4 years, 3 months

2
1
0 0

Technical Forum call - Dec 9

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, Dec 9, 7:00-8:00 UTC (Asia 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

4 years, 3 months

2
3
0 0

Commit 65064c56 causes cmake errors for AN547 for all toolchains

by Thomas Törnblom

While working on IAR support for AN547 (M55) I notice that this commit causes cmake errors for all toolchains. cmake -GNinja -S .. -B . -DTFM_PLATFORM=arm/mps3/an547 "-DTFM_TOOLCHAIN_FILE=..\toolchain_ARMCLANG.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=Debug -DBL2=ON ... CMake Error at tools/CMakeLists.txt:65 (file): file STRINGS file "D:/Projects/tf-m1/trusted-firmware-m/tools" cannot be read. Call Stack (most recent call first): tools/CMakeLists.txt:84 (parse_field_from_yaml) CMake Error at tools/CMakeLists.txt:65 (file): file STRINGS file "D:/Projects/tf-m1/trusted-firmware-m/armclang/lib/ext/tfm_test_repo-src/test/test_services" cannot be read. Call Stack (most recent call first): tools/CMakeLists.txt:84 (parse_field_from_yaml) Thomas -- *Thomas Törnblom*, /Product Engineer/ IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com Website: www.iar.com <http://www.iar.com> Twitter: www.twitter.com/iarsystems <http://www.twitter.com/iarsystems>

4 years, 3 months

5
7
0 0

IPC mode support for Audit log service

by Bøe, Sebastian

Hi, for PSA Certification level 2 a log of significant security events is required. Which I assume should be done with the Audit log service. But the Audit log service does not support IPC mode. Should PSA Certification level 2 be done with IPC mode or with library mode?

4 years, 3 months

2
2
0 0

TF-M v1.5.0 release

by Anton Komlev

Hello, TF-M project released v1.5.0 in release/v1.5.x<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/log/?h=release/…> branch and tagged as TF-Mv1.5.0. In the following days the changes from the release branch will be integrated with the main branch. Please take a look into the release notes for the new features and changes: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/relea… The HTML version will be available after the main branch update. New major features are: * MCUboot updated to v1.8.0. * Thread mode SPM. * Add Non-secure Client Extension (NSCE) for non-secure client ID management support. * Secure Function model support in framework. * Support Memory-mapped IOVECs. * Decouple documentation and binary builds. * Manifest tool skips disabled Secure Partitions. * Provisioning and OTP are supported. * PSA Protected Storage, Internal Trusted Storage, Initial Attestation services are converted to Stateless services. * Support out-of-tree build of Secure Partitions. * Support out-of-tree build of platform specific test suites. * Introduce platform binding HAL. * ITS enhancement for harden ITS module against invalid data in Flash. * Support to select/deselect single or multiple TF-M regression test cases. * Decouple regression test flag configuration from TF-M. * New platforms added. Thank you, everyone who contributed to this milestone. Anton Komlev

4 years, 3 months

1
0
0 0

Re: [TF-M] Technical Forum call - Nov-25 CANCELLED

by Anton Komlev

Hello, Having no items to discuss - let's cancel the forum today. Have a happy Thanksgiving day and enjoy your turkey if you celebrate it. Thanks, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Monday, November 22, 2021 12:04 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - Nov-25 Hi, The next Technical Forum is planned on Thursday, Nov 25, 15:00-16:00 UTC (US time zone). This is Thanksgiving day and public holiday in US so we might want to cancel the forum expecting fewer participants unless we have a good topic to discuss. 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

4 years, 3 months

1
0
0 0

TF-M v1.5.0 release started

by Anton Komlev

Hello, Let me inform you that release branch "release/1.5.0" is created and tagged with TF-Mv1.5.0-RC1 in these repositories: 1. tf-m-tests<https://git.trustedfirmware.org/TF-M/tf-m-tests.git/> 2. trusted-firmware-m<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/> 3. tf-m-ci-scripts<https://git.trustedfirmware.org/ci/tf-m-ci-scripts.git/> 4. tf-m-job-configs<https://git.trustedfirmware.org/ci/tf-m-job-configs.git/> Normal development can be continued in the main branch as described in the updated release process https://tf-m-user-guide.trustedfirmware.org/docs/releases/release_process.h… Thanks and good luck, Anton

4 years, 3 months

1
2
0 0

Security vulnerability notice - Profile Small Key ID encoding vulnerability

by David Hu

Hi all, This email is a notification of a new security vulnerability reported to TF-M. In TF-M v1.4.0, NSPE may access secure keys stored in TF-M Crypto service in Profile Small with Crypto key ID encoding disabled. This vulnerability impacts Profile Small in TF-M v1.4.0. Please check the details in the security advisory<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12608/1/docs…>. The advisory has been merged in v1.5.0 release and will be port back to master branch. The fix has been merged on the master branch<https://review.trustedfirmware.org/plugins/gitiles/TF-M/trusted-firmware-m/…> and patch release v1.4.1<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/commit/?h=TF-Mv…>. Thanks. Best regards, Hu Ziji

4 years, 3 months

1
0
0 0

Technical Forum call - Nov-25

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, Nov 25, 15:00-16:00 UTC (US time zone). This is Thanksgiving day and public holiday in US so we might want to cancel the forum expecting fewer participants unless we have a good topic to discuss. 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

4 years, 4 months

1
0
0 0

Re: [TF-M] d4dbaa93, "Add FPU support for gnu arm embedded toolchain" causing build errors

by David Hu

Hi Thomas, The tf-m-tests fix is under review and has not been merged yet. Therefore that commit ID is not available in tf-m-tests. I'd suggest to do following to test the fix: * Cherry pick https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/12563 to your local tf-m-tests repo * Cherry pick https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12564 to your local trusted-firmware-m repo * Add `-DTFM_TEST_REPO_PATH=<local tf-m-tests folder>` in the build command. After the fix is merged, the commit will be available when fetching the tf-m-tests repo. Best regards, Hu Ziji ________________________________ From: Thomas Törnblom <thomas.tornblom(a)iar.com> Sent: Thursday, November 18, 2021 8:10 PM To: David Hu <David.Hu(a)arm.com>; David Wang <David.Wang(a)arm.com>; Feder Liang <Feder.Liang(a)arm.com> Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] d4dbaa93, "Add FPU support for gnu arm embedded toolchain" causing build errors I'm getting another error after cherry picking these: PS D:\Projects\trusted-firmware-m\iar> cmake -GNinja -S .. -B . -DTFM_PLATFORM=arm/musca_s1 "-DTFM_TOOLCHAIN_FILE=..\toolchain_IARARM.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=Debug -DBL2=ON -DTEST_NS_QCBOR=OFF -- Populating tfm_test_repo -- Configuring done -- Generating done -- Build files have been written to: D:/Projects/trusted-firmware-m/iar/lib/ext/tfm_test_repo-subbuild [1/9] Creating directories for 'tfm_test_repo-populate' [1/9] Performing download step (git clone) for 'tfm_test_repo-populate' Cloning into 'tfm_test_repo-src'... remote: Enumerating objects: 1094, done. remote: Counting objects: 100% (1094/1094), done. remote: Compressing objects: 100% (613/613), done. remote: Total 2057 (delta 913), reused 511 (delta 481), pack-reused 963 Receiving objects: 100% (2057/2057), 2.05 MiB | 8.43 MiB/s, done. Resolving deltas: 100% (1371/1371), done. fatal: invalid reference: 14ca288 CMake Error at tfm_test_repo-subbuild/tfm_test_repo-populate-prefix/tmp/tfm_test_repo-populate-gitclone.cmake:40 (message): Failed to checkout tag: '14ca288' FAILED: tfm_test_repo-populate-prefix/src/tfm_test_repo-populate-stamp/tfm_test_repo-populate-download cmd.exe /C "cd /D D:\Projects\trusted-firmware-m\iar\lib\ext && "C:\Program Files\CMake\bin\cmake.exe" -P D:/Projects/trusted-firmware-m/iar/lib/ext/tfm_test_repo-subbuild/tfm_test_repo-populate-prefix/tmp/tfm_test_repo-populate-gitclone.cmake && "C:\Program Files\CMake\bin\cmake.exe" -E touch D:/Projects/trusted-firmware-m/iar/lib/ext/tfm_test_repo-subbuild/tfm_test_repo-populate-prefix/src/tfm_test_repo-populate-stamp/tfm_test_repo-populate-download" ninja: build stopped: subcommand failed. CMake Error at C:/Program Files/CMake/share/cmake-3.20/Modules/FetchContent.cmake:1012 (message): Build step for tfm_test_repo failed: 1 Call Stack (most recent call first): C:/Program Files/CMake/share/cmake-3.20/Modules/FetchContent.cmake:1141:EVAL:2 (__FetchContent_directPopulate) C:/Program Files/CMake/share/cmake-3.20/Modules/FetchContent.cmake:1141 (cmake_language) lib/ext/tf-m-tests/fetch_repo.cmake:27 (FetchContent_Populate) lib/ext/tf-m-tests/tf-m-tests.cmake:56 (include) config/set_config.cmake:68 (include) CMakeLists.txt:42 (include) Den 2021-11-18 kl. 13:00, skrev David Hu: Hi Thomas, Sorry for the failure and the trouble. The build logic of QCBOR NS test was adjusted to fit FP feature but the logic has defect when QCBOR NS test = OFF. Please cherry pick the following 2 patches and have a try: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/12563 https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12564 The fix will be port back to master branch when release completes. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org><mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M Sent: Thursday, November 18, 2021 6:57 PM To: David Wang <David.Wang(a)arm.com><mailto:David.Wang@arm.com>; Feder Liang <Feder.Liang(a)arm.com><mailto:Feder.Liang@arm.com> Cc: nd <nd(a)arm.com><mailto:nd@arm.com>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] d4dbaa93, "Add FPU support for gnu arm embedded toolchain" causing build errors Oh, and it fails the same on Windows and linux, as well as ARMCLANG and IARARM. /Thomas Den 2021-11-18 kl. 11:56, skrev Thomas Törnblom: commit fd88f7fbde4d23720c3c9be7350e628df51ef964 (HEAD -> master, tag: TF-Mv1.5.0-RC1, origin/master, origin/HEAD, list) Den 2021-11-18 kl. 11:27, skrev David Wang: Hi Thomas, Could you share the SHA of your branch HEAD? Or you can try to fetch the latest tag and code. Regards, David Wang From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org><mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M Sent: Thursday, November 18, 2021 6:10 PM To: Feder Liang <Feder.Liang(a)arm.com><mailto:Feder.Liang@arm.com> Cc: nd <nd(a)arm.com><mailto:nd@arm.com>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] d4dbaa93, "Add FPU support for gnu arm embedded toolchain" causing build errors Nope, I was using "master", which was 1.5.0 RC1, both fails. /Thomas Den 2021-11-18 kl. 10:56, skrev Feder Liang: Hi, Thomas It seems TF-M and Test repo is not synced. Could you help a try on latest TF-M master branch or tag: TF-Mv1.5.0-RC1? Best Regards Feder From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org><mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M Sent: Thursday, November 18, 2021 5:42 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] d4dbaa93, "Add FPU support for gnu arm embedded toolchain" causing build errors Looks like this patch is causing build errors, at least for Musca S1. cmake line: cmake -GNinja -S .. -B . -DTFM_PLATFORM=arm/musca_s1 "-DTFM_TOOLCHAIN_FILE=..\toolchain_ARMCLANG.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=Debug -DBL2=ON -DTEST_NS_QCBOR=OFF [1233/1238] Linking C executable bin\tfm_ns.axf FAILED: bin/tfm_ns.axf cmd.exe /C "cd . && D:\apps\Keil_v5\ARM\ARMCLANG\bin\armlink.exe --cpu=cortex-m33 --info=summarysizes,sizes,totals,unused,veneers --strict --symbols --xref --diag_suppress=6312 --diag_suppress=6314 --diag_suppress=6304 --diag_suppress=6329 --fpu=softvfp --map --scatter=D:/Projects/trusted-firmware-m/armclang/platform/target/CMakeFiles/tfm_ns_scatter.dir/./Device/Source/armclang/musca_ns.o platform\libplatform_ns.a app\libtfm_ns_integration_test.a app\libtfm_api_ns.a ns_log\libtfm_ns_log.a test\suites\core\libtfm_test_suite_core_ns.a app\libtfm_ns_integration_test.a test\suites\core\libtfm_test_suite_core_ns.a test\suites\attestation\libtfm_test_suite_attestation_ns.a test\suites\crypto\libtfm_test_suite_crypto_ns.a test\suites\qcbor\libtfm_test_suite_qcbor_ns.a -ltfm_qcbor_test test\suites\ps\libtfm_test_suite_ps_ns.a test\suites\its\libtfm_test_suite_its_ns.a test\suites\t_cose\libtfm_test_suite_t_cose_ns.a test\suites\t_cose\libtfm_t_cose_test.a test\suites\t_cose\libtfm_t_cose_ns.a test\suites\qcbor\libtfm_qcbor_ns.a test\suites\platform\libtfm_test_suite_platform_ns.a test\suites\ipc\libtfm_test_suite_ipc_ns.a lib\ext\tfm_test_repo-src\CMSIS\RTOS2\RTX\Library\ARM\RTX_V8MMN.lib app\libtfm_api_ns.a secure_fw\libtfm_s_veneers.a ns_log\libtfm_ns_log.a platform\libplatform_ns.a app\CMakeFiles\tfm_ns.dir\main_ns.o app\CMakeFiles\tfm_ns.dir\__\__\platform\ext\target\arm\musca_s1\Device\Source\armclang\startup_cmsdk_musca_ns.o app\CMakeFiles\tfm_ns.dir\__\ns_interface\ns_client_ext\tz_shim_layer.o app\CMakeFiles\tfm_ns.dir\__\CMSIS\RTOS2\RTX\Config\RTX_Config.o app\CMakeFiles\tfm_ns.dir\__\CMSIS\RTOS2\RTX\Source\rtx_lib.o app\CMakeFiles\tfm_ns.dir\os_wrapper_cmsis_rtos_v2.o -o bin\tfm_ns.axf --list=bin\tfm_ns.axf.map && cd ." Fatal error: L3900U: Unrecognized option '-ltfm_qcbor_test'. Finished: 0 information, 0 warning, 0 error and 1 fatal error messages. ninja: build stopped: subcommand failed. -- Thomas Törnblom, Product Engineer IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com<mailto:thomas.tornblom@iar.com> Website: www.iar.com<http://www.iar.com> Twitter: www.twitter.com/iarsystems<http://www.twitter.com/iarsystems> -- Thomas Törnblom, Product Engineer IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com<mailto:thomas.tornblom@iar.com> Website: www.iar.com<http://www.iar.com> Twitter: www.twitter.com/iarsystems<http://www.twitter.com/iarsystems> -- Thomas Törnblom, Product Engineer IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com<mailto:thomas.tornblom@iar.com> Website: www.iar.com<http://www.iar.com> Twitter: www.twitter.com/iarsystems<http://www.twitter.com/iarsystems> -- Thomas Törnblom, Product Engineer IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com<mailto:thomas.tornblom@iar.com> Website: www.iar.com<http://www.iar.com> Twitter: www.twitter.com/iarsystems<http://www.twitter.com/iarsystems> -- Thomas Törnblom, Product Engineer IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com<mailto:thomas.tornblom@iar.com> Website: www.iar.com<http://www.iar.com> Twitter: www.twitter.com/iarsystems<http://www.twitter.com/iarsystems>

4 years, 4 months

1
0
0 0

Re: [TF-M] d4dbaa93, "Add FPU support for gnu arm embedded toolchain" causing build errors

by David Hu

The mailing list was lost. From: David Hu Sent: Thursday, November 18, 2021 8:00 PM To: Thomas Törnblom <thomas.tornblom(a)iar.com>; David Wang <David.Wang(a)arm.com>; Feder Liang <Feder.Liang(a)arm.com> Cc: nd <nd(a)arm.com> Subject: RE: [TF-M] d4dbaa93, "Add FPU support for gnu arm embedded toolchain" causing build errors Hi Thomas, Sorry for the failure and the trouble. The build logic of QCBOR NS test was adjusted to fit FP feature but the logic has defect when QCBOR NS test = OFF. Please cherry pick the following 2 patches and have a try: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/12563 https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12564 The fix will be port back to master branch when release completes. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Thomas Törnblom via TF-M Sent: Thursday, November 18, 2021 6:57 PM To: David Wang <David.Wang(a)arm.com<mailto:David.Wang@arm.com>>; Feder Liang <Feder.Liang(a)arm.com<mailto:Feder.Liang@arm.com>> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] d4dbaa93, "Add FPU support for gnu arm embedded toolchain" causing build errors Oh, and it fails the same on Windows and linux, as well as ARMCLANG and IARARM. /Thomas Den 2021-11-18 kl. 11:56, skrev Thomas Törnblom: commit fd88f7fbde4d23720c3c9be7350e628df51ef964 (HEAD -> master, tag: TF-Mv1.5.0-RC1, origin/master, origin/HEAD, list) Den 2021-11-18 kl. 11:27, skrev David Wang: Hi Thomas, Could you share the SHA of your branch HEAD? Or you can try to fetch the latest tag and code. Regards, David Wang From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org><mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M Sent: Thursday, November 18, 2021 6:10 PM To: Feder Liang <Feder.Liang(a)arm.com><mailto:Feder.Liang@arm.com> Cc: nd <nd(a)arm.com><mailto:nd@arm.com>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] d4dbaa93, "Add FPU support for gnu arm embedded toolchain" causing build errors Nope, I was using "master", which was 1.5.0 RC1, both fails. /Thomas Den 2021-11-18 kl. 10:56, skrev Feder Liang: Hi, Thomas It seems TF-M and Test repo is not synced. Could you help a try on latest TF-M master branch or tag: TF-Mv1.5.0-RC1? Best Regards Feder From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org><mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M Sent: Thursday, November 18, 2021 5:42 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] d4dbaa93, "Add FPU support for gnu arm embedded toolchain" causing build errors Looks like this patch is causing build errors, at least for Musca S1. cmake line: cmake -GNinja -S .. -B . -DTFM_PLATFORM=arm/musca_s1 "-DTFM_TOOLCHAIN_FILE=..\toolchain_ARMCLANG.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=Debug -DBL2=ON -DTEST_NS_QCBOR=OFF [1233/1238] Linking C executable bin\tfm_ns.axf FAILED: bin/tfm_ns.axf cmd.exe /C "cd . && D:\apps\Keil_v5\ARM\ARMCLANG\bin\armlink.exe --cpu=cortex-m33 --info=summarysizes,sizes,totals,unused,veneers --strict --symbols --xref --diag_suppress=6312 --diag_suppress=6314 --diag_suppress=6304 --diag_suppress=6329 --fpu=softvfp --map --scatter=D:/Projects/trusted-firmware-m/armclang/platform/target/CMakeFiles/tfm_ns_scatter.dir/./Device/Source/armclang/musca_ns.o platform\libplatform_ns.a app\libtfm_ns_integration_test.a app\libtfm_api_ns.a ns_log\libtfm_ns_log.a test\suites\core\libtfm_test_suite_core_ns.a app\libtfm_ns_integration_test.a test\suites\core\libtfm_test_suite_core_ns.a test\suites\attestation\libtfm_test_suite_attestation_ns.a test\suites\crypto\libtfm_test_suite_crypto_ns.a test\suites\qcbor\libtfm_test_suite_qcbor_ns.a -ltfm_qcbor_test test\suites\ps\libtfm_test_suite_ps_ns.a test\suites\its\libtfm_test_suite_its_ns.a test\suites\t_cose\libtfm_test_suite_t_cose_ns.a test\suites\t_cose\libtfm_t_cose_test.a test\suites\t_cose\libtfm_t_cose_ns.a test\suites\qcbor\libtfm_qcbor_ns.a test\suites\platform\libtfm_test_suite_platform_ns.a test\suites\ipc\libtfm_test_suite_ipc_ns.a lib\ext\tfm_test_repo-src\CMSIS\RTOS2\RTX\Library\ARM\RTX_V8MMN.lib app\libtfm_api_ns.a secure_fw\libtfm_s_veneers.a ns_log\libtfm_ns_log.a platform\libplatform_ns.a app\CMakeFiles\tfm_ns.dir\main_ns.o app\CMakeFiles\tfm_ns.dir\__\__\platform\ext\target\arm\musca_s1\Device\Source\armclang\startup_cmsdk_musca_ns.o app\CMakeFiles\tfm_ns.dir\__\ns_interface\ns_client_ext\tz_shim_layer.o app\CMakeFiles\tfm_ns.dir\__\CMSIS\RTOS2\RTX\Config\RTX_Config.o app\CMakeFiles\tfm_ns.dir\__\CMSIS\RTOS2\RTX\Source\rtx_lib.o app\CMakeFiles\tfm_ns.dir\os_wrapper_cmsis_rtos_v2.o -o bin\tfm_ns.axf --list=bin\tfm_ns.axf.map && cd ." Fatal error: L3900U: Unrecognized option '-ltfm_qcbor_test'. Finished: 0 information, 0 warning, 0 error and 1 fatal error messages. ninja: build stopped: subcommand failed. -- Thomas Törnblom, Product Engineer IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com<mailto:thomas.tornblom@iar.com> Website: www.iar.com<http://www.iar.com> Twitter: www.twitter.com/iarsystems<http://www.twitter.com/iarsystems> -- Thomas Törnblom, Product Engineer IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com<mailto:thomas.tornblom@iar.com> Website: www.iar.com<http://www.iar.com> Twitter: www.twitter.com/iarsystems<http://www.twitter.com/iarsystems> -- Thomas Törnblom, Product Engineer IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com<mailto:thomas.tornblom@iar.com> Website: www.iar.com<http://www.iar.com> Twitter: www.twitter.com/iarsystems<http://www.twitter.com/iarsystems> -- Thomas Törnblom, Product Engineer IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com<mailto:thomas.tornblom@iar.com> Website: www.iar.com<http://www.iar.com> Twitter: www.twitter.com/iarsystems<http://www.twitter.com/iarsystems>

4 years, 4 months

1
0
0 0

d4dbaa93, "Add FPU support for gnu arm embedded toolchain" causing build errors

by Thomas Törnblom

Looks like this patch is causing build errors, at least for Musca S1. cmake line: cmake -GNinja -S .. -B . -DTFM_PLATFORM=arm/musca_s1 "-DTFM_TOOLCHAIN_FILE=..\toolchain_ARMCLANG.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=Debug -DBL2=ON -DTEST_NS_QCBOR=OFF [1233/1238] Linking C executable bin\tfm_ns.axf FAILED: bin/tfm_ns.axf cmd.exe /C "cd . && D:\apps\Keil_v5\ARM\ARMCLANG\bin\armlink.exe --cpu=cortex-m33 --info=summarysizes,sizes,totals,unused,veneers --strict --symbols --xref --diag_suppress=6312 --diag_suppress=6314 --diag_suppress=6304 --diag_suppress=6329 --fpu=softvfp --map --scatter=D:/Projects/trusted-firmware-m/armclang/platform/target/CMakeFiles/tfm_ns_scatter.dir/./Device/Source/armclang/musca_ns.o platform\libplatform_ns.a app\libtfm_ns_integration_test.a app\libtfm_api_ns.a ns_log\libtfm_ns_log.a test\suites\core\libtfm_test_suite_core_ns.a app\libtfm_ns_integration_test.a test\suites\core\libtfm_test_suite_core_ns.a test\suites\attestation\libtfm_test_suite_attestation_ns.a test\suites\crypto\libtfm_test_suite_crypto_ns.a test\suites\qcbor\libtfm_test_suite_qcbor_ns.a -ltfm_qcbor_test test\suites\ps\libtfm_test_suite_ps_ns.a test\suites\its\libtfm_test_suite_its_ns.a test\suites\t_cose\libtfm_test_suite_t_cose_ns.a test\suites\t_cose\libtfm_t_cose_test.a test\suites\t_cose\libtfm_t_cose_ns.a test\suites\qcbor\libtfm_qcbor_ns.a test\suites\platform\libtfm_test_suite_platform_ns.a test\suites\ipc\libtfm_test_suite_ipc_ns.a lib\ext\tfm_test_repo-src\CMSIS\RTOS2\RTX\Library\ARM\RTX_V8MMN.lib app\libtfm_api_ns.a secure_fw\libtfm_s_veneers.a ns_log\libtfm_ns_log.a platform\libplatform_ns.a app\CMakeFiles\tfm_ns.dir\main_ns.o app\CMakeFiles\tfm_ns.dir\__\__\platform\ext\target\arm\musca_s1\Device\Source\armclang\startup_cmsdk_musca_ns.o app\CMakeFiles\tfm_ns.dir\__\ns_interface\ns_client_ext\tz_shim_layer.o app\CMakeFiles\tfm_ns.dir\__\CMSIS\RTOS2\RTX\Config\RTX_Config.o app\CMakeFiles\tfm_ns.dir\__\CMSIS\RTOS2\RTX\Source\rtx_lib.o app\CMakeFiles\tfm_ns.dir\os_wrapper_cmsis_rtos_v2.o -o bin\tfm_ns.axf --list=bin\tfm_ns.axf.map && cd ." Fatal error: L3900U: Unrecognized option '-ltfm_qcbor_test'. Finished: 0 information, 0 warning, 0 error and 1 fatal error messages. ninja: build stopped: subcommand failed. -- *Thomas Törnblom*, /Product Engineer/ IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com Website: www.iar.com <http://www.iar.com> Twitter: www.twitter.com/iarsystems <http://www.twitter.com/iarsystems>

4 years, 4 months

3
5
0 0

Open CI Does Not Cover ITS/PS Access Flash Tests on MUSCA_B1

by Xinyu Zhang

Hi, I'm sorry to inform you that ITS/PS access flash on MUSCA_B1 could not be covered on Open CI for the time being. Because the flash on MUSCA_B1 board in Open CI is broken, we temporarily use RAM_FS as workaround. This issue will be fixed ASAP. We'll keep following and inform you with further updates. Sorry for any inconvenience! BR, Xinyu

4 years, 4 months

2
2
0 0

Re: [TF-M] TF-M release v1.5.0 will start after Nov 15

by Anton Komlev

Hello, To include all planned changes we need more time to review the patches so the feature freeze is postponed to the beginning of the next week when release branch will be created. This gives all a few more days for reviews and last moment changes. The intention is to keep the final date unchanged. Best regards, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Thursday, November 11, 2021 8:33 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] TF-M release v1.5.0 will start on Nov 15 Hello, Following the updated release strategy, presented on the tech forum today I plan to create the release branch on Nov 13, and freeze project features at that moment. Please review and merge all patches intended for v1.5.0 by the end of this week. Normal development can continue on the main branch without any restriction. Thanks, Anton

4 years, 4 months

1
0
0 0

Another PSoC problem

by Chris.Brand＠infineon.com

Build command is: cmake -S . -B output -G"Unix Makefiles" -DTFM_PLATFORM=cypress/psoc64 -DTFM_TOOLCHAIN_FILE=toolchain_GNUARM.cmake -DTEST_NS_MULTI_CORE=ON -DTFM_ISOLATION_LEVEL=1 The result is a hang at this point: > Executing 'MULTI_CLIENT_CALL_HEAVY_TEST' Description: 'Multiple outstanding NS PSA client calls heavyweight test' Totally 5 threads for test start Each thread run 0x20 rounds tests Some experimentation shows that: It happens with both gcc and armclang (unable to test IAR). It doesn't always happen, but does seem to hang more often than it succeeds. It doesn't happen with TFM_ISOLATION_LEVEL=2. It looks like this test was passing consistently before 5e68b11764673ee32bae0de8ecf3cde45cc55ea1, so I guess this is another scheduling issue. There's not a lot of code that differs with TFM_LVL, so I wonder if there's a race condition that is always present but just doesn't happen to get hit at TFM_LVL=2...? BTW, being able to build just the one test is extremely useful! Chris Brand Cypress Semiconductor (Canada), Inc. Sr Prin Software Engr CSCA CSS ICW SW PSW 1 Office: +1 778 234 0515 Chris.Brand(a)infineon.com<mailto:Chris.Brand@infineon.com>

4 years, 4 months

4
5
0 0

race condition in IPC

by Sebastian Bøe

Hi, are there any known race conditions in IPC/PS that affect TF-M 1.4-ish? More specifically TF-M revision a199c3047f320a2f82b9a0c27af5b50991184e0f, which is 38 commits prior to TF-Mv1.4.0-RC1. I am observing that adding printfs, or otherwise changing the flash alignment and therefore runtime of my code will affect whether the PS reliability test suite passes or not. More specifically, if it triggers a secure fault after x iterations of 2001, or y iterations of 2002, etc. depending on where I put my printfs or otherwise affect the alignment of the code. This is run on the nrf platform as a part of the nrf SDK. Test Suite PS reliability tests (TFM_PS_TEST_2XXX)... 'repetitive sets and gets in/from an asset' 'repetitive sets, gets and removes' It does not reproduce under GDB and I am unable to unwind the backtrace from the secure fault handler. Any tips about recovering a backtrace from a secure fault handler would also be appreciated. #0 SecureFault_Handler () at /home/sebo/ncs/modules/tee/tfm/trusted-firmware-m/secure_fw/spm/cmsis_psa/arch/tfm_arch_v8m_main.c:96 #1 0xffffffb4 in ?? () I have not been able to reproduce it in the latest upstream TF-M release/revision, but that could just be because I haven't been able to hit the race condition. Sebastian Bøe

4 years, 4 months

2
5
0 0

[ATTENTION REQUIRED] Manifest Tool being aware of Secure Partition enabled status when building

by Kevin Peng

Hi, I worked out a patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12025> to make the Manifest Tool (tfm_parse_manifest_list.py) aware of the Secure Partition status when building. Currently, the tool generates everything and then the Build System picks up the files needed. With the development of FF-M 1.1 feature, we need the tool to be aware of the Secure Partition enabled status to generate SPM configurations. The patch make use of the feature of CMake command configure_file which substitutes variable values referenced as @VAR@ or ${VAR}. It requires the "conditional" attributes in manifest lists to be surrounded by "@" for "${}". Then when you disable some Partition for building, the tool will not generate anything for that Partition such as PID/SID and TF-M Partition load info. So please out of tree Secure Partition manifest lists do the corresponding change to make the tool aware of that any Partitions are DISABLED. The tool currently only takes conditional value "OFF" or "FALSE" as Partitions being disabled, all other values are treated as enabled. This means if you do not make the change in the manifest list, the tool treats all the partitions as enabled always. Best Regards, Kevin

4 years, 4 months

1
1
0 0

TF-M release v1.5.0 will start on Nov 15

by Anton Komlev

Hello, Following the updated release strategy, presented on the tech forum today I plan to create the release branch on Nov 13, and freeze project features at that moment. Please review and merge all patches intended for v1.5.0 by the end of this week. Normal development can continue on the main branch without any restriction. Thanks, Anton

4 years, 4 months

1
0
0 0

Musca B1 SE build broken?

by Chris.Brand＠infineon.com

Hi, I'm trying to build Musca B1 SE (as part of my work to create a new ns_agent_mailbox partition), and it seems that it has been missed in some HAL API changes: spm/libtfm_spm.a(backend_ipc.o): In function `ipc_system_run': .../secure_fw/spm/ffm/backend_ipc.c:132: undefined reference to `tfm_hal_update_boundaries' spm/libtfm_spm.a(spm_ipc.o): In function `tfm_spm_init': .../secure_fw/spm/cmsis_psa/spm_ipc.c:643: undefined reference to `tfm_hal_bind_boundaries' spm/libtfm_spm.a(spm_ipc.o): In function `do_schedule': .../secure_fw/spm/cmsis_psa/spm_ipc.c:694: undefined reference to `tfm_hal_update_boundaries' spm/libtfm_spm.a(static_load.o): In function `load_irqs_assuredly': .../secure_fw/spm/cmsis_psa/static_load.c:195: undefined reference to `tfm_hal_irq_enable' .../secure_fw/spm/cmsis_psa/static_load.c:198: undefined reference to `tfm_hal_irq_disable' spm/libtfm_spm.a(psa_api.o): In function `tfm_spm_partition_psa_eoi': .../secure_fw/spm/ffm/psa_api.c:830: undefined reference to `tfm_hal_irq_clear_pending' .../secure_fw/spm/ffm/psa_api.c:831: undefined reference to `tfm_hal_irq_enable' spm/libtfm_spm.a(psa_api.o): In function `tfm_spm_partition_irq_enable': .../secure_fw/spm/ffm/psa_api.c:858: undefined reference to `tfm_hal_irq_enable' spm/libtfm_spm.a(psa_api.o): In function `tfm_spm_partition_irq_disable': .../secure_fw/spm/ffm/psa_api.c:876: undefined reference to `tfm_hal_irq_disable' spm/libtfm_spm.a(tfm_core_svcalls_ipc.o): In function `tfm_flih_prepare_depriv_flih': .../secure_fw/spm/cmsis_psa/tfm_core_svcalls_ipc.c:137: undefined reference to `tfm_hal_update_boundaries' spm/libtfm_spm.a(tfm_core_svcalls_ipc.o): In function `tfm_flih_return_to_isr': .../secure_fw/spm/cmsis_psa/tfm_core_svcalls_ipc.c:170: undefined reference to `tfm_hal_update_boundaries' Chris Brand Cypress Semiconductor (Canada), Inc. An Infineon Technologies Company Sr Prin Software Engr CSCA CSS ICW SW PSW 1 Office: +1 778 234 0515 Chris.Brand(a)infineon.com<mailto:Chris.Brand@infineon.com> International Place 13700 V6V 2X8 Richmond Canada www.infineon.com<www.cypress.com> www.cypress.com<http://www.cypress.com> Discoveries<http://www.infineon.com/discoveries> Facebook<http://www.facebook.com/infineon> Twitter<http://www.twitter.com/Infineon> LinkedIn<http://www.linkedin.com/company/infineon-technologies> Part of your life. Part of tomorrow. NOTICE: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material of Infineon Technologies AG and its affiliated entities which is for the exclusive use of the individual designated above as the recipient. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact immediately the sender by returning e-mail and delete the material from any computer. If you are not the specified recipient, you are hereby notified that all disclosure, reproduction, distribution or action taken on the basis of this message is prohibited.

4 years, 4 months

2
1
0 0

Technical Forum call - Nov 11

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, Nov 11, 7:00-8:00 UTC (Asia 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

4 years, 4 months

1
1
0 0

lpcxpresso55s69 builds broken

by Thomas Törnblom

More breakage: In file included from ../secure_fw/spm/include/tfm_arch.h:19, from ../secure_fw/spm/cmsis_psa/spm_ipc.h:13, from ../secure_fw/partitions/idle_partition/load_info_idle_sp.c:10: ../secure_fw/spm/include/tfm_arch_v8m.h:58:2: error: #error "VTOR not present, check configurations." 58 | #error "VTOR not present, check configurations." | ^~~~~ ninja: build stopped: subcommand failed. Same issue with IAR. /Thomas -- *Thomas Törnblom*, /Product Engineer/ IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com Website: www.iar.com <http://www.iar.com> Twitter: www.twitter.com/iarsystems <http://www.twitter.com/iarsystems>

4 years, 4 months

3
13
0 0

PSoC64 TF-M - Port to CYB06447BZI-D54

by Cristiano Rodrigues

Hi guys, I am trying to put tf-m running in the PSoC64 board. However, I have a board that is slightly different from the one used by default in the tf-m. (I have *CYB06447BZI-D54* and the default tf-m is prepared to *CYS0644xxZI-S2D44). *For what I saw, the main difference among them is in memory, *CYB06447BZI-D54 *has 1MB of flash and 256kB of RAM and *CYS0644xxZI-S2D44 *has 2MB of Flash and 1MB of RAM. So now I'm trying to make a small port from tf-m to *CYB06447BZI-D54. * I changed the flash size in the flash_layout.h file to meet the *CYB06447BZI-D54 *flash size, however, I am having some difficulties in changing the RAM size. I am trying to change the RAM partitions size in region_defs.h and the smpu definitions of that partitions in smpu_config.h, but without much success. My question are: - Is possible to do the porting? Or does *CYB06447BZI-D54* not have enough memory to run tf-m? - If possible, what is I missing? Are more changes needed than I'm making? Best regards, Cristiano Rodrigues

4 years, 4 months

2
2
0 0

Key derivation from HUK in NS application

by Kevin Townsend

Hi, I need to derive a new key from the HUK using HKDF, but are we able to request key derivation with the HUK from the NS side, or would we need to create a custom ARoT partittion for that? The requirements are identical to what PS does here with HKDF -- no salt and a fixed 'info' value, resulting in a key that is device-bound and can be regenerated at startup with no storage requirements: https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/desig… (that API usage looks to be out of date, BTW, since "psa_open_key" now takes two params). I tried to do something similar from the NS side, modifying this code https://github.com/zephyrproject-rtos/zephyr/blob/main/samples/tfm_integrat… ..., but get an error when trying to open the HUK with "TFM_CRYPTO_KEY_ID_HUK". That isn't surprising, but is there any alternative to generate keys from the HUK without a custom ARoT service? The fact that no storage is required when deriving from the HUK is significant. Best regards, Kevin

4 years, 4 months

1
0
0 0

Using software random generator for FIH library

by Roman.Mazurak＠infineon.com

Hi all, Does anyone know if using software random generator seeded with TRNG to provide random delays for Fault Injection Hardening library is correct from PSA Level 3 certification point of view? The basic idea is to : 1. Use TRNG to provide seed for software random generator on fih_delay_init. 2. Use software random generator to implement fih_delay_random. 3. Periodically reseed software random generator with data from TRNG (optional). Thanks, Roman.

4 years, 4 months

2
1
0 0

Commit b8bc0d2a breaks Musca_S1

by Thomas Törnblom

Appears there are more recent breakage. b8bc0d2a "HAL: Expand the scope of tfm_hal_platform_init API" breaks Musca_S1 /Thomas -- *Thomas Törnblom*, /Product Engineer/ IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com Website: www.iar.com <http://www.iar.com> Twitter: www.twitter.com/iarsystems <http://www.twitter.com/iarsystems>

4 years, 4 months

2
1
0 0

fce78aef breaks psoc64 console output with IARARM and ARMCLANG toolchain

by Thomas Törnblom

The current version breaks console output for the secure partition on psoc64 with IAR or ARMCLANG. Appears to work with GNUARM. It appears that this commit is the culprit: fce78aef Platform: Duplicate the tfm_hal_platform_init The console starts out good, then during tests only garbage is seen. Linker script issues? /Thomas -- *Thomas Törnblom*, /Product Engineer/ IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com Website: www.iar.com <http://www.iar.com> Twitter: www.twitter.com/iarsystems <http://www.twitter.com/iarsystems>

4 years, 4 months

4
4
0 0

BL2 builds, no "PYTHON_EXECUTABLE" defined

by Thomas Törnblom

While attempting to build for the musca_s1, with mcuboot, on Windows, the build failed very late and brought up a Code Writer window on my screen. I nailed it down to no "PYTHON_EXECUTABLE" being defined while processing bl2/ext/mcuboot/CMakeLists.txt, which caused the build line to just attempt to run wrapper.py, with no interpreter, and windows brought up the appropriate tools to write python code. Adding "-DPYTHON_EXECUTABLE=python" to the cmake line fixed that, but it seems that this shouldn't be needed. The build tools should handle this, or? There is a line: #! /usr/bin/env python3 in wrapper.py, and I assume linux will handle this appropriately, but it doesn't seem windows does. Cheers, Thomas -- *Thomas Törnblom*, /Product Engineer/ IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com Website: www.iar.com <http://www.iar.com> Twitter: www.twitter.com/iarsystems <http://www.twitter.com/iarsystems>

4 years, 4 months

2
1
0 0

Flash definitions usage

by Bohdan.Hunko＠infineon.com

Hi everyone, I was trying to understand usage of TOTAL_ROM_SIZE and FLASH_TOTAL_SIZE from musca_b1/sse_200/partitions/flash_layout.h file. I haven't found any usage of these definitions. Does anyone know what is the reason to have them defined? Regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com>

4 years, 4 months

1
0
0 0

Inline asm syntax unified and symbol reference in IAR toolchain

by Ken Liu

Hi Thomas and all, I noticed there are some #if !defined(__ICCARM__) ".syntax unified \n" #endif In source code, looks like ".syntax unified" is not support in IAR, is that true? If it could not be supported in a short term, we can define some wrapper such as: #ifdef __ICCARM__ #define CLAIM_SYNTAX_UNIFIED "\n" #else #define CLAIM_SYNTAX_UNIFIED ".syntax unified \n" #endif Another question is about the: #if defined(__ICCARM__) #pragma required = do_schedule #endif If we claim do_schedule in the constraints, is the above "#pragma required" still needed? __asm (".... :: "i"(do_schedule)); We can create a patch to test this - using a constraint looks more proper. Thanks. /Ken

4 years, 4 months

2
5
0 0

Re: [TF-M] System reset

by Andrew Thoelke

Hi Sebastian, The section in the Platform Security Model is describing the behavior of a system reset – the recommendation is that any preceding runtime state (in volatile memory, or in CPU or peripheral registers) does not influence the execution of the reboot. This is except for an optional suspend or hibernate state, which explicitly maintains runtime state while powering off most or all of the system and will resume via a CPU reset. System security requirements might require explicit clearing of volatile memory on reset to prevent cold-boot style attacks that could allow an attacker to read any residual RAM contents – although software-based attacks of this kind are partly mitigated by trusted boot, which prevents an attacker from running arbitrary code at reset (unlike devices that boot from untrusted flash memory). The specific bullet list in the PSA Firmware Framework for M (in §3.5.1 on Panics) is describing the challenges for an implementation that does NOT do the recommended action of resetting the system when a Secure Partition panics, which justifies the recommendation to reset the system. If the SPM does reset the system, then the challenges in that bullet list are avoided. The issues listed are: > * An individual Secure Partition cannot be reset and restarted in isolation. > * A Secure Partition may have state maintained on behalf of clients that will be destroyed when restarting the service. There is no mechanism to re-synchronize the clients. > * It is not possible to determine at the point of panic how much corruption has occurred within the Secure Partition and elsewhere in the SPE. If the SPM only restarted the Secure Partition that panicked, then any previous runtime state within that Secure Partition is lost, including any ongoing connections with clients of services within that partition, or any resources that those services were managing for their clients. FF-M does not provide a specified mechanism for such clients to be informed that the connections are broken, and there is no way to provide a general strategy that allows a client to recover from a service failure. This is what is meant by “There is no mechanism to re-synchronize the clients.”. I have just realized that in FF-M 1.1, there may be scenarios in which restarting a Secure Partition could be justified and technically feasible. If a Secure Partition with only Stateless services maintains no client state or resources, and also maintains no connections to other RoT Services (so there are no RoT Services maintaining state for this Secure Partition) – then restarting this Secure Partition might not suffer from the first two complications listed in §3.5.1. The third issue is harder to control: the risks from the data corruption that lead up to the panic depends partly on the SPE isolation policies, and on what this Secure Partition was responsible for. Reset remains the recommended response to a Secure Partition panic in v1.1.0. Regards, Andrew Thoelke Arm Ltd. From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: 26 October 2021 10:51 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] System reset Hi Sebastian, The specification writer looks not here these two days, let me try to explain it based on my understanding. I think two specs both recommend clearing general runtime data while resetting. If the booting runtime clearing code can clear the RAM data for a specific platform, the memory clearing in the 'tfm_spm_hal_system_reset ' can be skipped. Basically, simple hardware reset triggering is just fine. The special-purpose memory to be retained during resetting is not a generic runtime memory, hence they need to be treated specially, such as putting them in a special bank or region and skipping clearing them during booting. This special region can be treated as a private asset of one service, which could NOT be shared between components for direct access. The owner service provides the functionality around this asset. Please put more comments or corrections, thanks. /Ken From: TF-M <mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Sebastian Bøe via TF-M Sent: Monday, October 25, 2021 3:16 PM To: mailto:tf-m@lists.trustedfirmware.org Subject: [TF-M] System reset Hi, I would like some clarification about system reset. There are these two statements about it in the PSM and PSA-FF: "No run-time state from before the reset should be retained or used, except where necessary if suspend or hibernate are supported, see section 4.6." -- PSM page 22. "A Secure Partition may have state maintained on behalf of clients that will be destroyed when restarting the service." -- PSA-FF page 47. Is it the responsibility of tfm_spm_hal_system_reset to destroy this state or is it OK to destroy it after reset as a part of the C runtime startup procedure? I assume for instance that PRoT .bss is cleared as a part of the C runtime startup procedure, but should it also have been destroyed as a part of tfm_spm_hal_system_reset ? PSM - Platform Security Model. https://developer.arm.com/documentation/den0128/0100/ PSA-FF PSA Firmware Framework https://armkeil.blob.core.windows.net/developer/Files/pdf/PlatformSecurityA… Sebastian Bøe Nordic Semiconductor

4 years, 4 months

2
1
0 0

[PLATFORM ATTENTION REQUIRED] Unify the HAL APIs for IPC Model

by Kevin Peng

Hi all, I'm been working to unify the HAL APIs for IPC Model. The IPC Model currently uses two different sets of HAL APIs: * tfm_spm_hal_* - This is mainly used by the Library Model and IPC Model re-uses some of them * tfm_hal_* - This is introduced for IPC Model and some are shared to Library Model This might be confusing for platform vendors. So I'm trying to make it clear for IPC Model by: * Duplicating the shared APIs and rename the IPC copy to tfm_hal_* * Combining several platform init APIs to a single tfm_platform_init for IPC Model * tfm_spm_hal_enable_fault_handlers * tfm_spm_hal_system_reset_cfg * tfm_spm_hal_init_debug * tfm_spm_hal_nvic_interrupt_target_state_cfg * tfm_spm_hal_nvic_interrupt_enable With these changes, IPC Model will use tfm_hal_* APIs only. Please platform owners review these patches<https://review.trustedfirmware.org/q/topic:%22decouple_legacy_hal_for_ipc%2…> to see if any mistakes (the patches mainly move codes around) or any platforms missed in the patches. Plan to have them merged before the end of October. Thanks. Best Regards, Kevin

4 years, 4 months

1
1
0 0

System reset

by Sebastian Bøe

Hi, I would like some clarification about system reset. There are these two statements about it in the PSM and PSA-FF: "No run-time state from before the reset should be retained or used, except where necessary if suspend or hibernate are supported, see section 4.6." -- PSM page 22. "A Secure Partition may have state maintained on behalf of clients that will be destroyed when restarting the service." -- PSA-FF page 47. Is it the responsibility of tfm_spm_hal_system_reset to destroy this state or is it OK to destroy it after reset as a part of the C runtime startup procedure? I assume for instance that PRoT .bss is cleared as a part of the C runtime startup procedure, but should it also have been destroyed as a part of tfm_spm_hal_system_reset ? PSM - Platform Security Model. https://developer.arm.com/documentation/den0128/0100/ PSA-FF PSA Firmware Framework https://armkeil.blob.core.windows.net/developer/Files/pdf/PlatformSecurityA… Sebastian Bøe Nordic Semiconductor

4 years, 4 months

2
1
0 0

ITS File System Enhancement

by Sherry Zhang

Hi, I created patches to add the XOR checksum of the whole metadata into the ITS metadata_block header. This is to check the possible error in the flash. It can happen that the ITS file system is upgraded to the new one while the ITS assets are maintained with the current ITS file system. To support compatibility with the current ITS filesystem version, at the initialization of the file system, the file metadata and the block metadata, together with the metadata_block_header are updated to the new ITS file system. The patches are: https://review.trustedfirmware.org/q/topic:%22ITS_FILESYSTEM%22+(status:ope… Would you like to review the patches? Any comments are welcomed! Regards, Sherry Z

4 years, 4 months

1
0
0 0

PSoC scheduling broken

by Chris.Brand＠infineon.com

Running regression tests with the current HEAD, the secure tests all pass but the non-secure tests get stuck early on (I suspect that responses don't get back to the NS core). Reverting 5e68b11764673ee32bae0de8ecf3cde45cc55ea1 "SPM: Trigger scheduler at the end of SPM API" fixes the issue. Was that patch tested with multi-core? I created a patch to revert that patch for now - https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11998 Chris Brand Cypress Semiconductor (Canada), Inc. Sr Prin Software Engr CSCA CSS ICW SW PSW 1 Office: +1 778 234 0515 Chris.Brand(a)infineon.com<mailto:Chris.Brand@infineon.com>

4 years, 4 months

2
5
0 0

Enable GPIO IRQ in TFM 1.3 with zephry v2.7.0 on nrf5340DK

by Singh, Yaduvir

Hi All, I want to enable GPIO IRQ in Trusted firmware-m 1.3 on nrf5340DK. I have TFM 1.3 which comes with zephyr v2.7.0 image flashed to board. followed the steps of https://www.trustedfirmware.org/docs/tech_forum_20210819BriefUpdatesInterru… and tfm_slih_test_service which has TIMER0 interrupt handler. Steps1: Assigning the interrupt GPIOTE0 and TIMER0 in secure partition manifest file. Steps2: Assigning the MMIO region of GPIOTE0 and TIMER0 in secure partition manifest file. Step3: Enable(psa_irq_enable) for both GPIOTE0,TIMER0 and Start (tfm_plat_test_secure_timer_start) the TIMER0. Step4: waiting for interrupt SIGNAL defined in secure partition manifest file for GPIOTE0 and TIMER0) using psa_wait(PSA_WAIT_ANY, PSA_BLOCK) in the secure partition source code. But do not receive any signal for TIMER0 and GPIOTE0. Q1) at least TIMER0 signal should be received after the timer start? Q2)Are there any steps i missed to enable IRQ in TFM secure partition? Q3)Also, for GPIOTE i need to enable IRQ on the particular pin of port0 ex P0.8, How can i know the signal generated for the interrupt is for P0.8? Q4)In tfm_secure_irq_handling.rst it mentions "it is important the macro name matches the platform's handler function for that IRQ source." - In case ``source`` is defined IRQ macro, the name of the handler becomes ``void <macro>_Handler(void)``. I do not understand why we need to have a handler function name matching with IRQ source when we have to wait on psa_wait(PSA_WAIT_ANY, PSA_BLOCK) for IRQ signal? Step1,Step2 /*#####################################################################*/ modules\tee\tfm\trusted-firmware-m\platform\ext\target\nordic_nrf\common\nrf5340\tfm_peripherals_def.h #ifndef __TFM_PERIPHERALS_DEF_H__ #define __TFM_PERIPHERALS_DEF_H__ #include <nrf.h> #ifdef __cplusplus extern "C" { #endif #define TFM_TIMER0_IRQ (TIMER0_IRQn) #define TFM_TIMER1_IRQ (TIMER1_IRQn) #define TFM_GPIOTE0_IRQ (GPIOTE0_IRQn) #define TFM_SPIM4_IRQ (SPIM4_IRQn) struct platform_data_t; extern struct platform_data_t tfm_peripheral_std_uart; extern struct platform_data_t tfm_peripheral_timer0; extern struct platform_data_t tfm_peripheral_std_gpiote0; extern struct platform_data_t tfm_peripheral_std_spim4; #define TFM_PERIPHERAL_STD_UART (&tfm_peripheral_std_uart) #define TFM_PERIPHERAL_TIMER0 (&tfm_peripheral_timer0) #define TFM_PERIPHERAL_GPIOTE0 (&tfm_peripheral_std_gpiote0) #define TFM_PERIPHERAL_SPIM4 (&tfm_peripheral_std_spim4) #define TFM_PERIPHERAL_FPGA_IO (0) #ifdef __cplusplus } #endif #endif /* __TFM_PERIPHERALS_DEF_H__ */ modules\tee\tfm\trusted-firmware-m\platform\ext\target\nordic_nrf\common\nrf5340\target_cfg.c struct platform_data_t tfm_peripheral_timer0 = { NRF_TIMER0_S_BASE, NRF_TIMER0_S_BASE + (sizeof(NRF_TIMER_Type) - 1), }; struct platform_data_t tfm_peripheral_std_uart = { NRF_UARTE1_S_BASE, NRF_UARTE1_S_BASE + (sizeof(NRF_UARTE_Type) - 1), }; struct platform_data_t tfm_peripheral_std_gpiote0 = { NRF_GPIOTE0_S_BASE, NRF_GPIOTE0_S_BASE + (sizeof(NRF_GPIOTE_Type) - 1), }; struct platform_data_t tfm_peripheral_std_spim4 = { NRF_SPIM4_S_BASE, NRF_SPIM4_S_BASE + (sizeof(NRF_SPIM_Type) - 1), }; /*Secure partition manifest file change*/ samplepartition.yaml { "psa_framework_version": 1.1, "name": "TFM_SP_sample", # Possible options: "PSA-ROT | APPLICATION-ROT" "type": "APPLICATION-ROT", "priority": "NORMAL", "model": "IPC", "entry_point": "sample_partition_main", "stack_size": "0x200", "services": [ # Define the secure service here. { "name": "TFM_EXAMPLE_SERVICE", # SIDs must be unique, ones that are currently in use are documented in # tfm_secure_partition_addition.rst on line 184 "sid": "0x00001001", "non_secure_clients": true, "version": 1, "version_policy": "STRICT" }, ], # Define all the IRQs that the service wants to handle. "mmio_regions": [ { "name": "TFM_PERIPHERAL_GPIOTE0", "permission": "READ-WRITE" }, { "name": "TFM_PERIPHERAL_SPIM4", "permission": "READ-WRITE" }, { "name": "TFM_PERIPHERAL_TIMER0", "permission": "READ-WRITE" }, ], "irqs": [ { "source": "TFM_GPIOTE0_IRQ", "name": "TFM_GPIOTE0_IRQ", "handling": "SLIH", "tfm_irq_priority": 64, }, { "source": "TFM_SPIM4_IRQ", "name": "TFM_SPIM4_IRQ", "handling": "SLIH", "tfm_irq_priority": 64, }, { "source": "TFM_TIMER0_IRQ", "name": "TFM_TIMER0_IRQ", "handling": "SLIH", "tfm_irq_priority": 64, } ], "dependencies": [ "TFM_CRYPTO" ] } Step3, Step4 /*#####################################################################*/ /*Secure partition Code*/ sample_partition.c #define TIMER_RELOAD_VALUE (1*1000*1000) static void gpiote0_handler(void) { LOG_INFFMT("gpiote0_handler called!!\n"); psa_irq_disable(TFM_GPIOTE0_IRQ_SIGNAL); psa_eoi(TFM_GPIOTE0_IRQ_SIGNAL); } static void spim4_handler(void) { LOG_INFFMT("spim4_handler called !\n"); psa_irq_disable(TFM_SPIM4_IRQ_SIGNAL); psa_eoi(TFM_SPIM4_IRQ_SIGNAL); } static void timer0_handler(void) { LOG_INFFMT("timer0_handler called!\n"); psa_irq_disable(TFM_TIMER0_IRQ_SIGNAL); psa_eoi(TFM_TIMER0_IRQ_SIGNAL); } static void timer_init(NRF_TIMER_Type * TIMER, uint32_t ticks) { nrf_timer_mode_set(TIMER, NRF_TIMER_MODE_TIMER); nrf_timer_bit_width_set(TIMER, NRF_TIMER_BIT_WIDTH_32); nrf_timer_frequency_set(TIMER, NRF_TIMER_FREQ_1MHz); nrf_timer_cc_set(TIMER, NRF_TIMER_CC_CHANNEL0, ticks); nrf_timer_one_shot_enable(TIMER, NRF_TIMER_CC_CHANNEL0); } static void timer_stop(NRF_TIMER_Type * TIMER) { nrf_timer_task_trigger(TIMER, NRF_TIMER_TASK_STOP); nrf_timer_int_disable(TIMER, NRF_TIMER_INT_COMPARE0_MASK); nrf_timer_event_clear(TIMER, NRF_TIMER_EVENT_COMPARE0); } static void timer_start(NRF_TIMER_Type * TIMER) { timer_stop(TIMER); nrf_timer_task_trigger(TIMER, NRF_TIMER_TASK_CLEAR); nrf_timer_int_enable(TIMER, NRF_TIMER_INT_COMPARE0_MASK); nrf_timer_task_trigger(TIMER, NRF_TIMER_TASK_START); } void tfm_plat_test_secure_timer_start(void) { timer_init(NRF_TIMER0, TIMER_RELOAD_VALUE); timer_start(NRF_TIMER0); } void tfm_plat_test_secure_timer_stop(void) { timer_stop(NRF_TIMER0); } void sample_partition_main(void) { psa_signal_t signals; psa_irq_enable(TFM_SPIM4_IRQ_SIGNAL); psa_irq_enable(TFM_GPIOTE0_IRQ_SIGNAL); /*Start timer interrupt*/ psa_irq_enable(TFM_TIMER0_IRQ_SIGNAL); tfm_plat_test_secure_timer_start(); /* Continually wait for one or more of the partition's RoT Service or * interrupt signals to be asserted and then handle the asserted signal(s). */ while (1) { signals = psa_wait(PSA_WAIT_ANY, PSA_BLOCK); if (signals & TFM_GPIOTE0_IRQ_SIGNAL) { gpiote0_handler(); }else if (signals & TFM_SPIM4_IRQ_SIGNAL) { spim4_handler(); }else if (signals & TFM_TIMER0_IRQ_SIGNAL) { timer0_handler(); } else { psa_panic(); } } } /*#####################################################################*/ Thanks Yaduvir

4 years, 4 months

3
5
0 0

Re: [TF-M] [ATTENTION] SPM Update: Secure Partition build flag 'CONFIG_TFM_BUILDING_SPE' required.

by Ken Liu

Hi everyone, If you are creating out-of-tree partitions, please assign c-flag 'CONFIG_TFM_BUILDING_SPE' to the partitions sources. The reason is that FFM client header is used by both SPE and NSPE clients, and SPE would support multiple ABI methods and these methods can co-exist in the system, this flag can help the partition to choose correct ABI for FFM API. Check here for an example: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11897/11/sec… Or do you think choosing one ABI as the default ABI (default ABI owns the spec originally defined symbols) should work? Any comments please feel free to raise. BR. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: Wednesday, October 20, 2021 3:12 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [ATTENTION] SPM logic is under significant updating before End of Oct Hi, To support FFM 1.1 features (SFN mainly), the SPM logic is under significant updating till End of Oct, please: - If you are doing release-targeted development, please based on the released tags. - If you are developing with the latest master branch, please report bugs met. Our plan is to collect all bugs and fix them after this update, before the next release. - Keen to receive your fixes and contributions. It would be very nice if you can do these. All patches would go as a usual process, hence it should work for most of the configurations, except those not covered by the automation test. The platform related interfaces are not changing, hence no worry for platform owners. Thanks! /Ken

4 years, 5 months

1
0
0 0

Re: [TF-M] Sending events from TF-M to non-secure world?

by Li, Jun R

Hi Ken, Thanks for the suggestions! Actually on the chip we are using (Nordic SoC), there is an event generator unit we can use directly without the needs to do hardware changes. I would like to try that approach. The reason we can't do polling is that the events are generated during the enrollment process. I don't think that our biometric secure partition is reentrant while a process is onging, right? It is using just the single thread model. Regards, Jun Message: 1 Date: Wed, 20 Oct 2021 05:43:23 +0000 From: Ken Liu <Ken.Liu(a)arm.com> To: "tf-m(a)lists.trustedfirmware.org" <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Sending events from TF-M to non-secure world? Message-ID: <DB9PR08MB676161D704B2D3D861283E6CF5BE9(a)DB9PR08MB6761.eurprd08.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Hi Jun, To trigger an interrupt by software, Register 'STIR' may help you. The scenario you are describing is a practical use case hence it makes sense to think more about it. The scenarios you are describing is more related to the programming model - As the SPE is working more like a library, the NS caller polling the status of secure services by service interfaces and updating local presenting are more straight (and simple). And if you have involved a callback/event-based programming model into your secure service already (3rd party provided such a library, e.g.), you'll have to invent some mechanism to interactive with NS. From the Firmware Framework - M perspective, the peripheral is private to a partition, you can treat shared peripheral/memory as private resources to this partition, claim it in the manifest, and use it to communicate with NS. This shared peripheral (Aka MMIO in the specification) is private, it cannot be shared with other partitions. More comments? BR. /Ken -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Li, Jun R via TF-M Sent: Tuesday, October 19, 2021 10:42 PM To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] Sending events from TF-M to non-secure world? Hi Ken, Thanks for the nice suggestions! I was thinking of using an interrupt from TF-M to NS world as well but that needs some hardware support, which should be fine since I'm still designing the device. Maybe there is a software interrupt solution? Our application needs to put a biometric service inside TF-M and its enrollment process needs to send out some intermediate events to give the user some feedbacks. This is why I'm asking this question. I think TF-M can use an input buffer from NS world to store the new events and notify the NS world with the interrupt to fetch the new events. Sounds good? Regards, Jun On 10/19/21, 00:23, "TF-M on behalf of tf-m-request(a)lists.trustedfirmware.org" <tf-m-bounces(a)lists.trustedfirmware.org on behalf of tf-m-request(a)lists.trustedfirmware.org> wrote: Send TF-M mailing list submissions to tf-m(a)lists.trustedfirmware.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.trustedfirmware.org/mailman/listinfo/tf-m or, via email, send a message with subject or body 'help' to tf-m-request(a)lists.trustedfirmware.org You can reach the person managing the list at tf-m-owner(a)lists.trustedfirmware.org When replying, please edit your Subject line so it is more specific than "Re: Contents of TF-M digest..." Today's Topics: 1. Re: Sending events from TF-M to non-secure world? (Ken Liu) 2. Inline asm syntax unified and symbol reference in IAR toolchain (Ken Liu) ---------------------------------------------------------------------- Message: 1 Date: Tue, 19 Oct 2021 02:06:35 +0000 From: Ken Liu <Ken.Liu(a)arm.com> To: "tf-m(a)lists.trustedfirmware.org" <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Sending events from TF-M to non-secure world? Message-ID: <DB9PR08MB67613655A2ACA207C751C791F5BD9(a)DB9PR08MB6761.eurprd08.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Hi Jun, Basically, the service accessing model is a client-service model, hence the service won't call back to the client which makes the client a 'service'. Service can get client info by passed-in parameters and other SPM controlled channels. Assuming you are using a Trustzone based hardware, the hardware provides the capability that calling back to NSPE, but it is not encouraged inside TF-M because it breaks the simplified model proposed by FF-M and difficulties the secure threat analysis - a simple case is that the secure context is blocked because it is waiting for NS returns. If you do need to perform such operations, implement an interrupt based asynchronous mechanism is safer than software callbacks. The most queried requirement we have met is someone querying if the execution can be delivered back to NSPE when secure IDLE is going to happen. Not sure if you are facing the similar, is it okay to share more details? BR /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Li, Jun R via TF-M Sent: Tuesday, October 19, 2021 12:20 AM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Sending events from TF-M to non-secure world? Hi, Anyone has idea how a service inside a secure partition can send out some events to the non-secure world? Does callback still work over IPC? It seems non-secure world can connect to a SP but not easy to do the other way. Appreciate any comments or suggestions! Jun Intel Corporation @ SC, CA -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.trustedfirmware.org/pipermail/tf-m/attachments/20211019/1ff875…> -- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m

4 years, 5 months

1
0
0 0

Re: [TF-M] Supporting encryption with ITS

by Vasilakis, Georgios

Hey Andrew, These are very valuable points! For us I think that we aim mainly for per key integrity and confidentiality on the key material and integrity only for the key metadata. Providing confidentiality for the whole keystore will need major changes in the PSA APIs and will be out of scope for us. Providing per key confidentiality for the key material is a very straightforward change as you described. ITS will not need to change at all in this case, we will only modify the PSA crypto APIs. Providing per key integrity for key metadata will need a bit more thinking since apart from the fields included in the psa_persistent_key_storage_format we will also need the fields from the psa_storage_info_t struct but this should not be a serious issue as well. To conclude I think that we need to design the changes so that it is possible for platforms to implement these two requirments but we don't need to enforce them. I think that we need to have the flexibility to allow platforms to make their decisions on what they want to support depending on their needs. If, for example, a platform wants to support only confidentiality on the key material, they should be able to do that in my opinion. Since we are discussing platform specific implementations, the IV or any additional data needed could be probably stored (hidden to the PSA APIs) inside a platform specific struct inside the psa_persistent_key_storage_format struct. This will minimize the storage requirements for each platform. Regards, George ________________________________ From: Kvamtrø, Frank Audun <frank.kvamtro(a)nordicsemi.no> Sent: Wednesday, October 20, 2021 3:13 PM To: Vasilakis, Georgios <georgios.vasilakis(a)nordicsemi.no> Subject: Vs: [TF-M] Supporting encryption with ITS ________________________________ Fra: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> på vegne av Andrew Thoelke via TF-M <tf-m(a)lists.trustedfirmware.org> Sendt: onsdag 20. oktober 2021 10:31 Til: tf-m(a)lists.trustedfirmware.org <tf-m(a)lists.trustedfirmware.org> Kopi: nd <nd(a)arm.com> Emne: Re: [TF-M] Supporting encryption with ITS Hi, Note that, by specification, ITS must provide confidentiality, integrity and replay protection for the data stored within it. However, if the platform already provides that protection via isolation/logical/physical mechanisms, then adding cryptographic protection provides some defence in depth, or may mitigate some forms of physical attack. In this case, it is not obvious what forms of cryptographic protection are needed, as cryptography is not providing the primary security properties for the ITS data. As a result, I think the best design for this requirement will depend on the details of the protection that is required. In this use case, which of the following types of cryptographic protection are needed: 1. Confidentiality of key material (the actual bits of the key data) 2. Confidentiality of key material and key metadata 3. Confidentiality of the full keystore 4. Per-key Integrity of key material 5. Per-key Integrity of key material and key metadata 6. Per-key Confidentiality and Integrity of key material and key metadata 7. Confidentiality and integrity of the full keystore 8. Rollback protection? Per-key confidentiality, or confidentiality+integrity would be reasonably straight-forward to implement in a layer over the simple ITS storage – but would probably add IV or nonce+tag data to each key stored (assuming a HUK-derived encryption key is used). For just encryption, given the pseudo-random nature of secret keys – it might be possible to drop the need for random IV (and just use the client id + key id as an IV/nonce). Full key store confidentiality or confidentiality+integrity requires much more complex design, as this aims to conceal and protect the identity of the keys that are stored, not just the key material and/or key metadata. Regards, Andrew From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Vasilakis, Georgios via TF-M Sent: 19 October 2021 14:31 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Supporting encryption with ITS Hello again, sorry for the second email by my formatting got lost in the first one unfortunately. Let me include the formatted context below: Following the discussion regarding the encryption with ITS let's discuss a bit further the ideas discussed in the meeting. 1)Allow the protected storage to be used as a storage backend for persistent key storage in PSA crypto: This introduces the problem of reentrance that we discussed before. We cannot call crypto from the inside the PSA storage partition (either ITS of PS if we wanted to switch) 2)Do the encryption in the crypto partition instead of the ITS: This will require to create some platform specific encryption abstraction since we cannot have reentrance in PSA crypto as well. Meaning that we cannot call PSA crypto from PSA crypto. The main thing that needs to be solved in this solution is where can we store the metadata. The key itself can be derived from the HUK and does not need to be stored but the metadata need to be stored. These metadata can be stored by expanding the psa_storage_info_t struct or by introducing a new struct. The crypto storage apis will need to be modified to be aware of the extra information and handle them. 3)Put a frontend to ITS so that we select specific keys that need to be derived by the HUK. This is like the idea 2 I think in a concept level. The previous two designs described in the mailing list was to refactor the ITS and the PS partitions to have a common "encryption" library and the idea of refactoring the ITS itself to have an encryption layer. I personally prefer the solution 2 more than the other solutions. Moving the encryption in a higher level and using the ITS as a simple storage solution seems a cleaner approach. This will introduce a crypto abstraction layer (different than PS) but I don't consider it as a major disadvantage since all the crypto implementations in this scope will be very platform specific. Let me know about your opinions on this, if there are no major objections, I am willing to design a solution and some header files to elaborate more on this design. ________________________________ From: Vasilakis, Georgios <georgios.vasilakis(a)nordicsemi.no<mailto:georgios.vasilakis@nordicsemi.no>> Sent: Tuesday, October 19, 2021 3:18 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] Supporting encryption with ITS Hello all, Following the discussion regarding the encryption with ITS let's discuss a bit further the ideas discussed in the meeting. Allow the protected storage to be used as a storage backend for persistent key storage in PSA crypto: This introduces the problem of reentrance that we discussed before. We cannot call crypto from the inside the PSA storage partition (either ITS of PS if we wanted to switch) Do the encryption in the crypto partition instead of the ITS: This will require to create some platform specific encryption abstraction since we cannot have reentrance in PSA crypto as well. Meaning that we cannot call PSA crypto from PSA crypto. The main thing that needs to be solved in this solution is where can we store the metadata. The key itself can be derived from the HUK and does not need to be stored but the metadata need to be stored. These metadata can be stored by expanding the psa_storage_info_t struct or by introducing a new struct. The crypto storage apis will need to be modified to be aware of the extra information and handle them. Put a frontend to ITS so that we select specific keys that need to be derived by the HUK. This is like the idea 2 I think in a concept level. The previous two designs described in the mailing list was to refactor the ITS and the PS partitions to have a common "encryption" library and the idea of refactoring the ITS itself to have an encryption layer. I personally prefer the solution 2 more than the other solutions. Moving the encryption in a higher level and using the ITS as a simple storage solution seems a cleaner approach. This will introduce a crypto abstraction layer (different than PS) but I don't consider it as a major disadvantage since all the crypto implementations in this scope will be very platform specific. Let me know about your opinions on this, if there are no major objections, I am willing to design a solution and some header files to elaborate more on this design. Regards, George ________________________________ From: Vasilakis, Georgios <georgios.vasilakis(a)nordicsemi.no<mailto:georgios.vasilakis@nordicsemi.no>> Sent: Wednesday, September 29, 2021 2:04 PM To: Sherry Zhang <Sherry.Zhang2(a)arm.com<mailto:Sherry.Zhang2@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] Supporting encryption with ITS Hello Sherry, Thank you for the feedback! Does the storage area on your device meet this requirement? Yes, our devices can secure against read and write access through the dedicated peripherals (SPU + MPU). Is the memory physically isolated? If by that you mean if they are located outside of the chip then it is not. It is part of the package. If not, I wonder why not uses the Protected Storage service instead? The reason that we cannot use the protected storage service is that it is not supported as a storage backend by the PSA crypto APIs. Storing non-volatile keys right now using the PSA APIs uses ITS as a storage backend. Your comments regarding storing the IV and the TAG in Protected Storage are, of course, valid. If we decide to use a common code base we will have to do changes in the design of both services to overcome these issues. Overall, the motivation for encrypted ITS is based on the raising popularity of hardware-based attacks. The fact that right now we provide all the security measures needed does not mean that nothing will get compromised in the future. A security in depth approach seems more reasonable for such sensitive data. I am happy to join the TF-M Tech forum this Thursday and discuss it further, yes! Regards, George ________________________________ From: Sherry Zhang <Sherry.Zhang2(a)arm.com<mailto:Sherry.Zhang2@arm.com>> Sent: Tuesday, September 28, 2021 12:20 PM To: Vasilakis, Georgios <georgios.vasilakis(a)nordicsemi.no<mailto:georgios.vasilakis@nordicsemi.no>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: [TF-M] Supporting encryption with ITS Hi George, The ITS without encryption is not a compromised RoT. In the PSA Secure Storage API spec, the PSA Internal Trust Storage aims at providing a place for devices to store their most intimate secrets. Also “””””””””””””””””””” 1. The storage underlying the PSA Internal Trusted Storage Service MUST be protected from read and modification by attackers with physical access to the device. 2. The storage underlying the PSA Internal Trusted Storage Service MUST be protected from direct read or write access from software partitions outside of the PSA Root of Trust (PRoT). “””””””””””””””””””” So, for internal trusted storage service, it requires the underlying storage itself should provide being read or write protection. The storage area should be a “trusted” area. Does the storage area on your device meet this requirement? Is the memory physically isolated? If not, I wonder why not uses the Protected Storage service instead? For the design of adding encryption in ITS, in the PS partition, the `iv` and the encrypted object data are stored with the object file while the tag of each object is stored with the object table file. So, if encrypt the PS object in the ITS file system, how the PS partition get the `tag` of each object? After a rough thought, I think probably a standalone encryption for ITS is more reasonable. As this is a relatively “big topic”, would you like to hold a discussion on the TF-M Tech forum if it is not limited by confidential information? The next Tech forum will be hold on this Thursday 3:00 PM UTC time. Regards, Sherry Zhang From: Vasilakis, Georgios <georgios.vasilakis(a)nordicsemi.no<mailto:georgios.vasilakis@nordicsemi.no>> Sent: Friday, September 24, 2021 8:52 PM To: Sherry Zhang <Sherry.Zhang2(a)arm.com<mailto:Sherry.Zhang2@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] Supporting encryption with ITS Hello Sherry, Thank you for your input! 1. Our threat model is more concerned about attacks which can happen very early in the boot process, I think. A completely compromised RoT is not in our threat model. 2. I see that, ITS is supposed to store small objects. The storage overhead of adding encryption will be probably bigger than 20 bytes I think but the intention is to have this only as a configuration, not as the default option. 3. Agreed, a HAL API should be used for this. Do you have any opinion on the design of it? Do you think that it adds value to do try to use a common design for the object handling of both PS and ITS or is it better to have it as a standalone thing for the ITS. Regards, George ________________________________ From: Sherry Zhang <Sherry.Zhang2(a)arm.com<mailto:Sherry.Zhang2@arm.com>> Sent: Friday, September 24, 2021 11:58 AM To: Vasilakis, Georgios <georgios.vasilakis(a)nordicsemi.no<mailto:georgios.vasilakis@nordicsemi.no>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: [TF-M] Supporting encryption with ITS Hi George, Some comments from my side: 1. Internal trusted storage is part of the Root of Trust domain. If ITS storage device is attacked, then the code flash where the PSA Rot SP locates may also be attacked. Does the thread model of your system require the encryption in ITS? 2. The ITS service is intended to be used to interface to a small piece of storage. Encryption would increase the context for each ITS file. For example, similarly to PS object context, the `IV` which is used in encryption as well as the generated `tag` should be added into each file context. They total together can be about more than 20 bytes. 3. If the encryption is mandatory/ necessary required by the thread model of your system, as discussed, the PSA crypto service should not be called to avoid the circular. I think a HAL API for encryption may be created in ITS for platform implementation defined encryption/decryption. Regards, Sherry Zhang From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Vasilakis, Georgios via TF-M Sent: Thursday, September 23, 2021 10:47 PM To: Gyorgy Szing <Gyorgy.Szing(a)arm.com<mailto:Gyorgy.Szing@arm.com>>; Fabian Schmidt <fabian.schmidt(a)nxp.com<mailto:fabian.schmidt@nxp.com>> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] Supporting encryption with ITS Hey Gyorgy, These are very valuable comments! I am aware of the circular dependency issue because the PSA apis are using the ITS as a storage backend. This, as you said, can be circumvented by using a software crypto library or an implementation specific API. So, for the encryption a flexible API can be used which can allow externals to use their own function calls. Regarding the key storage, this is what I had in mind as well, using derived keys from the HUK. So that we don't need to store anything but the crypto metadata. Adding another layer of storage will raise more issues, I think. ________________________________ From: Gyorgy Szing <Gyorgy.Szing(a)arm.com<mailto:Gyorgy.Szing@arm.com>> Sent: Thursday, September 23, 2021 4:30 PM To: Fabian Schmidt <fabian.schmidt(a)nxp.com<mailto:fabian.schmidt@nxp.com>>; Vasilakis, Georgios <georgios.vasilakis(a)nordicsemi.no<mailto:georgios.vasilakis@nordicsemi.no>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>>; nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: [TF-M] Supporting encryption with ITS Hi, AFAIK the main reason for ITS not using encryption is the problem of circular dependency. ITS is used by crypto SP for key storage, so how will crypto fetch the key from ITS to decrypt ITS? You could use a software crypto implementation (another mbed-tls instance) in ITS, but where would you safely store the keys? If you have a two layer ITS, one for only storing the keys for the second instance, and a second, encrypted one, then you end up with something like ITS and PS. You may not need a full blown on-chip FLASH device for ITS. If you have a HUK available, you can derive the same SP specific keys from that at each boot, and store these in RAM backed ITS. You won’t be able to store other keys in ITS in a persistent way of course, but for that you can use PS. Well, something along these lines. Perhaps the TF-M team could help better if you could share some details on why your customer would need encrypted ITS. (A PSA for Cortex-A (TS) maintainer chiming in to a “not his business” discussion here 😉 ) /George From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Fabian Schmidt via TF-M Sent: September 23, 2021 15:51 To: Vasilakis, Georgios <georgios.vasilakis(a)nordicsemi.no<mailto:georgios.vasilakis@nordicsemi.no>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] Supporting encryption with ITS Hi George, I’m wondering if that would add value. To my understanding, ITS was never designed to be encrypted because of the way it’s supposed to be set up. (It’s Internal Trusted Storage.) I believe best practice is to place it in a “trusted” location, one that is ideally only accessible from Secure world, and also ideally on-die. If you then restrict outside access to the internal flash (JTAG, flash programmer ports,…), you’re pretty golden, in that no unauthorized party should be able to read from or write to the ITS.* Let me know if I misunderstand anything about ITS or TrustZone, but that’s my view. Maybe I’m painting an idealized picture. Greetings, Fabian Schmidt * at least short of a sophisticated physical attack or finding some loophole in TrustZone… From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Vasilakis, Georgios via TF-M Sent: Donnerstag, 23. September 2021 15:28 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [EXT] [TF-M] Supporting encryption with ITS Caution: EXT Email Hey all, Lately the requirement for an encrypted ITS solution is being asked from our customers and I would like to have a discussion here on how we can design this in a reasonable way. The first thought that came to my mind was to add the functionality to the ITS flash-fs layer. This layer contains file metadata in the its_file_meta_t structure and it should be possible to expand this to include additional crypto metadata (conditionally). This seems to be the less invasive change to me, even though it will introduce some increased memory usage since supporting encryption will mean that we cannot read the data in chunks anymore, we will have to use static buffers. At the same time, I looked at the PS partition since I knew that it has support for encryption. I believe that some core concepts of both solutions have similarities even though the code is quite different. For example, a file in ITS is similar to an object in PS and the (linear) list of file metadata in ITS is similar to the concept of the object table in PS. So, I think that it should be possible to design some generic-enough APIs that we can use for both the ITS and PS. Even though this will require some major refactoring in both partitions, it will decrease the code of these services which will probably decrease maintenance later. What are your thoughts on this? Regards, George

4 years, 5 months

1
0
0 0

Technical Forum call - October 28

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, October 28, 15:00-16:00 UTC (US time zone). That session Chris Reed kindly agreed to present "Introduction to pyOCD" - the method to program and debug TF-M and Cortex-M MCUs, in general, using the open-source tool https://pyocd.io/ Recording and slides of previous meetings are here: https://www.trustedfirmware.org/meetings/tf-m-technical-forum/ Best regards, Anton

4 years, 5 months

1
0
0 0

CMAKE library dependency trace tool for TF-M

by Jianliang Shen

Hi all, I'd like to introduce a CMAKE library dependency trace tool to you. This python script can * Search a specific library's dependent libraries and to-be-linked libraries in a list of repo paths. * Draw a diagram to show the link relationship. * Give some other information about: * Include paths * Source files * Compile definitions The main feature of diagram is similar with [CMakeGraphVizOptions]<https://cmake.org/cmake/help/latest/module/CMakeGraphVizOptions.html#cmakeg…>, the differences are: * The new tool can focus on certain library with specific trace depth like 1, 2 and n. * The new tool is not runtime, it is a static search and can search all libraries whose runtime build may be silenced. * The new tool makes the diagram more colourful to be more readable. With this tool, I hope you can get and check the structure of CMAKE library more quickly when developing the code and libraries. I have proposed a patch in tf-m-tools repo: [library dependency trace tool]<https://review.trustedfirmware.org/c/TF-M/tf-m-tools/+/12019>. This tool may not be convenient for everyone of you so here I beg for your feedbacks to make it better. Thanks. Best Regards Jianliang Shen

4 years, 5 months

1
0
0 0

[ATTENTION] SPM logic is under significant updating before End of Oct

by Ken Liu

Hi, To support FFM 1.1 features (SFN mainly), the SPM logic is under significant updating till End of Oct, please: - If you are doing release-targeted development, please based on the released tags. - If you are developing with the latest master branch, please report bugs met. Our plan is to collect all bugs and fix them after this update, before the next release. - Keen to receive your fixes and contributions. It would be very nice if you can do these. All patches would go as a usual process, hence it should work for most of the configurations, except those not covered by the automation test. The platform related interfaces are not changing, hence no worry for platform owners. Thanks! /Ken

4 years, 5 months

1
0
0 0

Re: [TF-M] Sending events from TF-M to non-secure world?

by Li, Jun R

Hi Ken, Thanks for the nice suggestions! I was thinking of using an interrupt from TF-M to NS world as well but that needs some hardware support, which should be fine since I'm still designing the device. Maybe there is a software interrupt solution? Our application needs to put a biometric service inside TF-M and its enrollment process needs to send out some intermediate events to give the user some feedbacks. This is why I'm asking this question. I think TF-M can use an input buffer from NS world to store the new events and notify the NS world with the interrupt to fetch the new events. Sounds good? Regards, Jun On 10/19/21, 00:23, "TF-M on behalf of tf-m-request(a)lists.trustedfirmware.org" <tf-m-bounces(a)lists.trustedfirmware.org on behalf of tf-m-request(a)lists.trustedfirmware.org> wrote: Send TF-M mailing list submissions to tf-m(a)lists.trustedfirmware.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.trustedfirmware.org/mailman/listinfo/tf-m or, via email, send a message with subject or body 'help' to tf-m-request(a)lists.trustedfirmware.org You can reach the person managing the list at tf-m-owner(a)lists.trustedfirmware.org When replying, please edit your Subject line so it is more specific than "Re: Contents of TF-M digest..." Today's Topics: 1. Re: Sending events from TF-M to non-secure world? (Ken Liu) 2. Inline asm syntax unified and symbol reference in IAR toolchain (Ken Liu) ---------------------------------------------------------------------- Message: 1 Date: Tue, 19 Oct 2021 02:06:35 +0000 From: Ken Liu <Ken.Liu(a)arm.com> To: "tf-m(a)lists.trustedfirmware.org" <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Sending events from TF-M to non-secure world? Message-ID: <DB9PR08MB67613655A2ACA207C751C791F5BD9(a)DB9PR08MB6761.eurprd08.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Hi Jun, Basically, the service accessing model is a client-service model, hence the service won't call back to the client which makes the client a 'service'. Service can get client info by passed-in parameters and other SPM controlled channels. Assuming you are using a Trustzone based hardware, the hardware provides the capability that calling back to NSPE, but it is not encouraged inside TF-M because it breaks the simplified model proposed by FF-M and difficulties the secure threat analysis - a simple case is that the secure context is blocked because it is waiting for NS returns. If you do need to perform such operations, implement an interrupt based asynchronous mechanism is safer than software callbacks. The most queried requirement we have met is someone querying if the execution can be delivered back to NSPE when secure IDLE is going to happen. Not sure if you are facing the similar, is it okay to share more details? BR /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Li, Jun R via TF-M Sent: Tuesday, October 19, 2021 12:20 AM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Sending events from TF-M to non-secure world? Hi, Anyone has idea how a service inside a secure partition can send out some events to the non-secure world? Does callback still work over IPC? It seems non-secure world can connect to a SP but not easy to do the other way. Appreciate any comments or suggestions! Jun Intel Corporation @ SC, CA -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.trustedfirmware.org/pipermail/tf-m/attachments/20211019/1ff875…>

4 years, 5 months

2
1
0 0

Re: [TF-M] Enablement of external bl2 builds

by Bohdan.Hunko＠infineon.com

Hi Sherry, So I actually checked issue from last mail ‘When building TFM with CRYPTO_HW_ACCELERATOR=ON and BL2=OFF I am getting this error:’ and turns out everything is fine in master branch, that error is only present in my local branch due to changes I have made. I am glad we have one bug less 😊 Sorry for wrong report. Best regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com> From: Hunko Bohdan (CSUKR CSS ICW SW FW) Sent: 01 October 2021 12:49 To: Hunko Bohdan (CSUKR CSS ICW SW FW) <Bohdan.Hunko(a)infineon.com>; Sherry.Zhang2(a)arm.com; Brand Chris (CSCA CSS ICW SW PSW 1) <Chris.Brand(a)infineon.com>; Kytsun Hennadiy (CSUKR CSS ICW SW FW) <Hennadiy.Kytsun(a)infineon.com>; Mazurak Roman (CSUKR CSS ICW SW FW) <Roman.Mazurak(a)infineon.com>; Tkachov Kostiantyn (CSUKR CSS ICW SW FW) <Kostiantyn.Tkachov(a)infineon.com> Cc: nd(a)arm.com Subject: RE: Enablement of external bl2 builds Hi all, One more thing on this topic. There is one more issue with building TFM without BL2. When building TFM with CRYPTO_HW_ACCELERATOR=ON and BL2=OFF I am getting this error: CMake Error at platform/ext/accelerator/CMakeLists.txt:11 (add_library): No SOURCES given to target: bl2_crypto_hw So I think this is one more thing that needs to be fixed. Best regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com> From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Bohdan Hunko via TF-M Sent: 30 September 2021 17:34 To: Sherry.Zhang2(a)arm.com<mailto:Sherry.Zhang2@arm.com>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>; Brand Chris (CSCA CSS ICW SW PSW 1) <Chris.Brand(a)infineon.com<mailto:Chris.Brand@infineon.com>>; Kytsun Hennadiy (CSUKR CSS ICW SW FW) <Hennadiy.Kytsun(a)infineon.com<mailto:Hennadiy.Kytsun@infineon.com>>; Mazurak Roman (CSUKR CSS ICW SW FW) <Roman.Mazurak(a)infineon.com<mailto:Roman.Mazurak@infineon.com>>; Tkachov Kostiantyn (CSUKR CSS ICW SW FW) <Kostiantyn.Tkachov(a)infineon.com<mailto:Kostiantyn.Tkachov@infineon.com>> Cc: nd(a)arm.com<mailto:nd@arm.com> Subject: Re: [TF-M] Enablement of external bl2 builds Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe<https://intranet-content.infineon.com/explore/aboutinfineon/rules/informati…>. Hi Sherry, Thanks for patching MCUBOOT_IMAGE_NUMBER issue. It was one of the issues we faced with. I also agree that mcuboot_config.h should be taken from our BL2 repo. So no changes needed there. About porting files (tfm/bl2 folder). We are planning to use existing porting files. But as you said currently they are not included into the build because BL2=0. So this needs to be fixed to include these porting files when TFM_PARTITION_FIRMWARE_UPDATE is ON. One minor issue we have is BOOT_DATA_AVAILABLE currently it is only defined if BL2=1 and MCUBOOT_MEASURED_BOOT=1. See this line of code<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/secure_fw/…>. I think we can either change that line of code or we can defile BOOT_DATA_AVAILABLE in our platform files using add_definitions(-DBOOT_DATA_AVAILABLE). First way is a bit harder but I thinks it fits better into TFM architecture. Second way is easier but it seems more like workaround than like solution. Do you have any suggestions about this problem? We are not blocked by these issues, so no worries here. Best regards Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com> From: Sherry Zhang <Sherry.Zhang2(a)arm.com<mailto:Sherry.Zhang2@arm.com>> Sent: 30 September 2021 11:38 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>; Tkachov Kostiantyn (CSUKR CSS ICW SW FW) <Kostiantyn.Tkachov(a)infineon.com<mailto:Kostiantyn.Tkachov@infineon.com>>; Mazurak Roman (CSUKR CSS ICW SW FW) <Roman.Mazurak(a)infineon.com<mailto:Roman.Mazurak@infineon.com>>; Kytsun Hennadiy (CSUKR CSS ICW SW FW) <Hennadiy.Kytsun(a)infineon.com<mailto:Hennadiy.Kytsun@infineon.com>>; Hunko Bohdan (CSUKR CSS ICW SW FW) <Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com>> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: Enablement of external bl2 builds Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe<https://intranet-content.infineon.com/explore/aboutinfineon/rules/informati…>. Hi Bohdan, I tried to build TF-M with FWU service without BL2 with the following command(FWU enabled with shared data while no BL2): cmake -S . -B cmake_build -DTFM_PLATFORM=arm/musca_b1/sse_200 -DCRYPTO_HW_ACCELERATOR=OFF -DPLATFORM_DUMMY_NV_SEED=ON -DBL2=0 -DMCUBOOT_PATH=../mcuboot The following issues I met: 1. Build time error by that ` MCUBOOT_IMAGE_NUMBER ` is passed as an empty macro into the flash_layout.h I have created a patch to fix it. https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11729 1. Build error in ` bootutil_public.c `. The mcuboot_config.h which is generated automatically when the BL2=ON is not found. Also the files( in tf-m/bl2 folder) about porting MCUboot into TF-M is not found by the build system as BL2=0. For the config file, I think, it should be imported from your specific MCUboot repo as it is generated when BL2 image is built. For the MCUboot porting files, are you using the files under tf-m/bl2 folder or using your specific porting files? The FWU service needs the porting source files. See code at https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/secure_fw/…. Are your blocked by these two issues? Can you share the detailed issue you met if there is more? Regards, Sherry From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Bohdan Hunko via TF-M Sent: Tuesday, September 28, 2021 6:44 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: Kostiantyn.Tkachov(a)infineon.com<mailto:Kostiantyn.Tkachov@infineon.com>; Roman.Mazurak(a)infineon.com<mailto:Roman.Mazurak@infineon.com>; Hennadiy.Kytsun(a)infineon.com<mailto:Hennadiy.Kytsun@infineon.com> Subject: [TF-M] Enablement of external bl2 builds Hi everyone, When adding support for new platform we ran into an issue with BL2 variable. In our architecture we have Bootloader based on MCUboot (aka BL2) but we are not planning to build it with TF-M. Bootloader would be separate repo and be built separately. So we need the way to build TF-M with FWU service and shared data definitions when BL2=OFF. I was trying to add support for this but was not able to do this because build structure is quite complicated. Does anyone have ideas or suggestions about the way we can implement this feature? Best regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com>

4 years, 5 months

2
3
0 0

Deprecation of ARM/MPS2/fvp_sse300 platform

by Anton Komlev

Hi Everyone, I would like to propose the deprecation of arm/mps2/fvp_sse300 platform because the main platform for Corstone-300 is MPS3, available in arm/mps3/an547 and we would like to reduce the number of the platforms to maintain. Following the deprecation process, https://tf-m-user-guide.trustedfirmware.org/platform/ext/platform_deprecati… this proposal is open for discussion at least for 4 weeks before the platform will be marked as deprecated and removed from TF-M unless any objection received. Thanks and Best regards, Anton Komlev

4 years, 5 months

1
1
0 0

Announcement: documentation build is separated from the main.

by Anton Komlev

Hello, >From now on, documentation has no interference with the main build and runs as an independent CMake project. This reduces CMake configuration phase and not requires doc tools for the normal development anymore. There are no changes for building the binaries, but documentation build shall start in the docs folder cmake -S docs -B build_docs cmake --build build_docs More details are here: https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/instr… Thanks, Anton

4 years, 5 months

1
0
0 0

Sending events from TF-M to non-secure world?

by Li, Jun R

Hi, Anyone has idea how a service inside a secure partition can send out some events to the non-secure world? Does callback still work over IPC? It seems non-secure world can connect to a SP but not easy to do the other way. Appreciate any comments or suggestions! Jun Intel Corporation @ SC, CA

4 years, 5 months

2
1
0 0

PSA Arch attestation test failure

by Chris.Brand＠infineon.com

Hi, We're seeing a failure in the PSA Arch attestation test, specifically: TEST: 601 | DESCRIPTION: Testing attestation initial attestation APIs | UT: psa_initial_attestation [Info] Executing tests from non-secure [Check 1] Test psa_initial_attestation_get_token with Challenge 32 [Check 2] Test psa_initial_attestation_get_token with Challenge 48 Failed at Checkpoint: 1 Actual: -138 Expected: 0 TEST RESULT: FAILED (Error Code=0x1) The failure is seen on PSoC, but only the gcc Release build (armclang and the other three gcc builds are all fine. Haven't tested IAR), which makes it tricky to debug. PSoC uses the common attest HAL code, though, so I imagine the issue may also be present on other platforms. Bisecting the problem leads to commit 09d71ffd40368b978d428744ad7ba0d3963f8d1d ("Platform: Use OTP as backing for attestation data"). -138 is PSA_ERROR_BUFFER_TOO_SMALL. I'm running gcc-arm-none-eabi-7-2018-q2-update, in case that matters. Chris Brand Cypress Semiconductor (Canada), Inc. Sr Prin Software Engr CSCA CSS ICW SW PSW 1 Office: +1 778 234 0515 Chris.Brand(a)infineon.com<mailto:Chris.Brand@infineon.com>

4 years, 5 months

3
6
0 0

Automatic code formatting

by Bøe, Sebastian

Hi, does anyone have a .clang-format file, or another technology for automatic code formatting to the TF-M coding standard?

4 years, 5 months

2
2
0 0

Platform specific test out-of-tree build

by Jianliang Shen

Hi all, Thanks for Chris Brand's enhancement suggestion about platform-specific tests. I'm enabling out-of-tree build mode of platform specific test suites with tf-m-tests. Currently I have proposed the following changes: * [TF-M patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11296>] * [tf-m-tests patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11297>] My proposal supplies a flexible interface for partners to out-of-tree build local tests. With this new feature, * Partners can perform local test quickly during development to improve test efficiency * Partners can maintain local test code outside tf-m-tests repo in case of confidential information or IP issues. I also put an out-of-tree example test source code into tf-m-extras repo and a document in TF-M repo: * [tf-m-extras patch<https://review.trustedfirmware.org/c/TF-M/tf-m-extras/+/11323>] * [TF-M patch doc<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11336>] This example indicates that platform-specific tests can be integrated with tf-m-tests, without following tf-m-tests structure or definitions. The document introduces the usage and coding guide of this new feature. PS: If partners would like to upstream platform specific test code, we will be glad to create a specific folder under tf-m-tests repo as Chris Brand suggested. I'd be grateful if you can take a look at the patch sets above. Any suggestion or comment is welcome. Best Regards Jianliang Shen

4 years, 5 months

1
2
0 0

Re: [TF-M] Adding platform specific functions to Crypto Service.

by Roman.Mazurak＠infineon.com

Hi Fabian, Yes, our team is thinking about adding feature to the Crypto service API, which are not cryptographic in nature. This is one of the possible solution in our design to avoid additional data processing layer between cryptographic clients and crypto accelerator. Our crypto accelerator also provides additional features which will be used by other secure partitions in TF-M but it doesn’t support handling of crypto and non-crypto requests at the same time. It’s not a problem for CC312 which is used for crypto services and OTP in the latest commit. As far as I understand CC312 allows to use crypto operations and OTP related functions at the same time without additional synchronization. So, the reference design is not very helpful in our situation. So, implementation of additional service is not the best solution. It will extend processing time for each cryptographic requests. The other option is to implement synchronization by using mutex. I think mutex is preferable approach, but this feature is also not support by TF-M yet 😊 There is the discussion which I started for mutex : https://lists.trustedfirmware.org/pipermail/tf-m/2021-October/001914.html Thanks, Roman. From: Fabian Schmidt <fabian.schmidt(a)nxp.com> Sent: Tuesday, October 12, 2021 13:47 To: Shebu.VargheseKuriakose(a)arm.com; David.Hu(a)arm.com; Mazurak Roman (CSUKR CSS ICW SW FW) <Roman.Mazurak(a)infineon.com>; mbed-tls(a)lists.trustedfirmware.org Cc: nd(a)arm.com Subject: RE: [TF-M] Adding platform specific functions to Crypto Service. Hi Roman, My understanding is that you would like to add features to the Crypto service API, but the features which you would like to add are not cryptographic in nature. Have you considered creating your own service for those features, instead of modifying the Crypto service? Or is there anything makes this not a viable option? If you are thinking about adding hardware acceleration for some Crypto features, that’s indeed covered in Shebu’s link. Greetings, Fabian Schmidt From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Shebu Varghese Kuriakose via TF-M Sent: Dienstag, 12. Oktober 2021 11:46 To: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>>; Roman.Mazurak(a)infineon.com<mailto:Roman.Mazurak@infineon.com>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>; mbed-tls(a)lists.trustedfirmware.org<mailto:mbed-tls@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [EXT] Re: [TF-M] Adding platform specific functions to Crypto Service. Caution: EXT Email Hi Roman, I also might not have understood the question completely. As you mention crypto HAL API, here is the specification which defines a standardized mechanism for PSA Crypto implementations to interface with Secure elements and crypto accelerators - https://github.com/ARMmbed/mbedtls/blob/development/docs/proposed/psa-drive…<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> Also adding mbed-tls mailing list as the thread is crypto related.. Regards, Shebu From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of David Hu via TF-M Sent: Tuesday, October 12, 2021 4:18 AM To: Roman.Mazurak(a)infineon.com<mailto:Roman.Mazurak@infineon.com>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] Adding platform specific functions to Crypto Service. Hi Roman, Are you asking about adding platform specific HAL API to implement PSA Crypto API function? Please correct me if I misunderstand your question. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Roman Mazurak via TF-M Sent: Monday, October 11, 2021 9:45 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] Adding platform specific functions to Crypto Service. Hi all, We would like to add a number of platform specific functions to Crypto Service API. Is it ok if such functions will not be related to cryptographic service, but such approach allows us to optimize platform design? Is there any initiative to create a Crypto Service HAL API to extend Crypto with custom functions? Best regards, Roman.

4 years, 5 months

2
2
0 0

TF-M Cadence change proposal

by Anton Komlev

Hello, Following the Tech Forum today I am duplicating the proposal of TF-M cadence change from 4 to 6 months here. This will generate 2 releases a year, planed for the end or March and the end of October starting from v1.6.0. The upcoming release v1.5.0 will stay on planned date. Please share your comments and concerns on the topic. Thanks, Anton

4 years, 5 months

1
0
0 0

PSA API crypto test breakage

by Chris.Brand＠infineon.com

Commit 42e77b561fcfe19819ff1e63cb7c0b672ee8ba41 ("Crypto: Remove TF-M Crypto service key handle array") seems to break PSA Arch Crypto test 218 (on PSoC64, with gcc, at least). After this commit, the test reports Failed at Checkpoint: 7 Actual: -137 Expected: -136 (so actual is PSA_ERROR_BAD_STATE and expected is PSA_ERROR_INVALID_HANDLE). That same test passes with the previous commit. Chris Brand Cypress Semiconductor (Canada), Inc. Sr Prin Software Engr CSCA CSS ICW SW PSW 1 Office: +1 778 234 0515 Chris.Brand(a)infineon.com<mailto:Chris.Brand@infineon.com>

4 years, 5 months

2
2
0 0

FWU mark TFM image as accepted

by Bohdan.Hunko＠infineon.com

Hi everyone, When studying FWU service I have noticed that there is a function psa_status_t psa_fwu_accept(psa_image_id_t image_id) It is used to mark image as accepted, and it works by writing magic number to image trailer. This function can be used to mark NS or S application as accepted. The first question is: who is responsible for making a call to mark TFM image as accepted ? Is this responsibility of NS application? The second thing I see is write access problem. TFM can receive a call to mark TFM image as accepted, so this means that TFM must have permission to write in its own primary slot. Doesn't this create a possibility for security violation? I can imagine that in ideal world TFM would only have Read and Execute mission for its own primary slot. The only thing that should be able to write to TFM primary slot should be bootloader (it need this functionality to swap images). No one else should be able to write into TFM primary slot. Am I missing something? Best regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com>

4 years, 5 months

4
3
0 0

Technical Forum call - Oct 14

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, Oct 14, 7:00-8:00 UTC (Asia 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

4 years, 5 months

1
1
0 0

Mutex in SPE

by Roman.Mazurak＠infineon.com

Hi all, We need a mutex to protect access to a shared resource within Platform RoT Services. Is there any plan to add implementation of mutex in TF-M? Maybe it should be a platform specific implementation? Thanks, Roman.

4 years, 5 months

2
1
0 0

TF Open CI FYI

by Don Harbin

Hi all, In a discussion with Anton, it was realized that all contributors may not be aware of some of the information available regarding Open CI. If interested in digging deeper and understanding here are some helpful links. - The Open CI "mini-website" can be found here <https://www.trustedfirmware.org/projects/open-ci/>. - Note in the intro paragraph a hotlink to the *Open CI Lava farm* showing the hardware platforms in the lab, recent test results, etc. Note it requires a login to see all the information - Also of value is a detailed *users guide* that provides an overview of Open CI. You can click on the "docs" icon or just go here <https://tf-ci-users-guide.readthedocs.io/en/latest/>. It's a living document and contributions are encouraged. :) - This page also shares how to get further involved and the location of the code. Best regards, Don

4 years, 5 months

1
0
0 0

Adding platform specific functions to Crypto Service.

by Roman.Mazurak＠infineon.com

Hi all, We would like to add a number of platform specific functions to Crypto Service API. Is it ok if such functions will not be related to cryptographic service, but such approach allows us to optimize platform design? Is there any initiative to create a Crypto Service HAL API to extend Crypto with custom functions? Best regards, Roman.

4 years, 5 months

3
2
0 0

Enable a peripheral interrupt to an App RoT

by Cristiano Rodrigues

Hi everyone, I am developing an App RoT for STM32L552 and testing the recent integrated FLIH interrupt feature, but I am missing something in the step of "Initializing the Interrupts" and "Integrating the Interrupt Handling Function". As is described in Secure Interrupt Integration Guide <https://tf-m-user-guide.trustedfirmware.org/docs/integration_guide/tfm_secu…>, to enable an interrupt it is needed: 1. Binding the interrupt to a Secure Partition. 2. Granting the Secure Partition access permissions to the device of the interrupt. 3. Initializing the interrupt. 4. Integrating the interrupt handling function Step *1 *and *2, * think that is "checked": - by adding this code to the partition manifest file. "mmio_regions": [ { "name": "TFM_PERIPHERAL_TIMER7", "permission": "READ-WRITE" } ], "irqs": [ { "source": "TFM_TIMER7_IRQ", "name": "TFM_TIMER7_IRQ", "handling": "FLIH", } - By defining the macro with platform peripheral structure in *patform/ext/target/stm/common/stm32l5xx/boards/tfm_peripherals_def.h* extern struct platform_data_t timer7 #define TFM_PERIPHERAL_TIMER7 &timer7 - *By assign the peripheral address in platform\ext\target\stm\common\stm32l5xx\secure\target_cfg.c* struct platform_data_t timer7 = { __TIMER7_BASE, __TIMER7_BASE + 0x3FF, -1, -1 }; - By adding the peripheral name to “partition_named_mmio_list[]” in the file *patform/ext/target/stm/common/stm32l5xx/boards/mmio_defs.h* const uintptr_t partition_named_mmio_list[] = { (uintptr_t)TFM_PERIPHERAL_TIMER0, (uintptr_t)TFM_PERIPHERAL_STD_UART, (uintptr_t) TFM_PERIPHERAL_TIMER7, }; - And add to my partition code, the irq function, and the function to configure the timer psa_flih_result_t tfm_timer7_irq_flih(void) { .... } static void flih_test_case_1(psa_msg_t *msg) { psa_irq_enable(TFM_TIMER7_IRQ_SIGNAL); timer_start(); ....... timer_stop(); psa_irq_disable(TFM_TIMER7_IRQ_SIGNAL); psa_reply(msg->handle, PSA_SUCCESS); } My problem, I think, is with the other two steps, *3 *and *4. *The TF-M documentation is not clear in these two steps. In step *3, *as is said in the documentation it is needed: i) to configure the interrupt priority; ii) to ensure that the interrupt targets the Secure State. iii) and save the interrupt information. So I suppose it goes something like this: struct irq_t { void *p_pt; struct irq_load_info_t *p_ildi; } save_tfm_timer7_irq_info; enum tfm_hal_status_t tfm_timer7_irq_init(void *p_pt, struct irq_load_info_t *p_ildi) { //targetting the interrupt to S state NVIC_ClearTargetState(TIM7_IRQn); NVIC_SetPriority(TIM7_IRQn, 1); NVIC_EnableIRQ(TIM7_IRQn); //Saving the Interrupt Information save_tfm_timer7_irq_info.p_pt = p_pt; save_tfm_timer7_irq_info.p_ildi = p_ildi; return TFM_HAL_SUCCESS; } *But in which file should I put this function? And where should I call this function??* And in step *4, *I also do not understand how can I meet this requirement -> "Platforms should call this entry function in the interrupt handlers defined in Vector Table with the saved information for each interrupt." Being the function in question -> *void spm_handle_interrupt(void *p_pt, struct irq_load_info_t *p_ildi).* *Which file can I do this in? And how should I do this step?* Cheers, Cristiano Rodrigues

4 years, 5 months

2
1
0 0

Boot shared data TLV length

by Bohdan.Hunko＠infineon.com

Hi everyone, IAS docs have this<https://tf-m-user-guide.trustedfirmware.org/docs/integration_guide/services…> note that says: There is a size field tlv_len which has different definitions in the upstream MCUboot repository and in its TF-M forked version: * Upstream MCUboot: Covers only the length of data but not the header size. * TF-M MCUboot: Covers the size of the entry header and the data together. This difference is handled by TF-M code based on which bootloader is used along with TF-M runtime. I was wondering where in code is this difference handled? When calculating next TLV entry address attest_core.c line 213<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/secure_fw/…> takes into account SHARED_DATA_ENTRY_HEADER_SIZE: tlv_curr = (*tlv_ptr) + SHARED_DATA_ENTRY_HEADER_SIZE + tlv_entry.tlv_len; So tlv_entry.tlv_len then must cover only length of entry (without header). This way corresponds to: "Upstream MCUboot: Covers only the length of data but not the header size" I was not able to find anything related to "TF-M MCUboot: Covers the size of the entry header and the data together". Is this difference handled in TF-M fork of MCUboot or is it just outdated IAS doc? Best regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com>

4 years, 5 months

2
1
0 0

Problem with PSoC armclang build

by Chris.Brand＠infineon.com

Hi, We've been investigating a problem with the armclang builds for PSoC. The symptoms are that the board just repeatedly reboots. We've narrowed it down to commit 300c68da11 "SPM: Use Main Stack for initialization". This commit is fine with the gcc toolchain but doesn't seem right for armclang (we haven't yet looked at IAR). Still digging into the issue, but I figured it might be helpful to give it more publicity. Chris Brand Cypress Semiconductor (Canada), Inc. Sr Prin Software Engr CSCA CSS ICW SW PSW 1 Office: +1 778 234 0515 Chris.Brand(a)infineon.com<mailto:Chris.Brand@infineon.com>

4 years, 5 months

2
3
0 0

nxp/lpcxpresso55s69 builds broken

by Thomas Törnblom

While verifying that my Musca B1/S1 fixes for IAR did not break other targets I ran into building problems for the nxp/lpcxpresso55s69 for both gnuarm and iararm. I've tested with the following cmake line: cmake -GNinja -S .. -B . -DTFM_PLATFORM=nxp/lpcxpresso55s69 "-DTFM_TOOLCHAIN_FILE=..\toolchain_GNUARM.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DTFM_PSA_API=ON -DBL2=OFF Fails with: d:/apps/gnuarm/10-2020-q4-major/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/bin/ld.exe: C:\Users\thomasto\Projects\tf-m12\trusted-firmware-m\gnuarm/../secure_fw/spm/ffm/psa_api.c:890: undefined reference to `tfm_hal_irq_disable' I notice that tfm_hal_irq_disable() is guarded by: #if TFM_LVL == 3 in .../nxp/common/tfm_hal_isolation.c, while the other targets does not have this guard. What isthe reason for that? Trying to set that with cmake causes other failures. commit 8444011d works commit 4051016f fails I tried bisecting between these two commits, but the builds run into other build failures so I gave up on that. Is his a known issue? I have successfully built and run regression tests on musca b1, musca s1, psoc64 and I have built, but not run an519, an521, an524 Cheers, Thomas -- *Thomas Törnblom*, /Product Engineer/ IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com <mailto:thomas.tornblom@iar.com> Website: www.iar.com <http://www.iar.com> Twitter: www.twitter.com/iarsystems <http://www.twitter.com/iarsystems>

4 years, 5 months

2
2
0 0

[PLATFORM ATTENTION REQUIRED] Partition interrupt binding patches have been merged

by Ken Liu

Dear platform owners, Theses interrupt binding patch(es) are merged: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11474 As the most part of the change happen in platform, please report platform integration if you met. Sorry I had thought the notification mail has been sent during the PR stage but it did not, hence it is not broadcasted in time. Current there are build errors reported on nxp/nordic platforms, and this patch should fix the problem: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11741 Also, Ci reported arch-test build fail, hence the fix for arch-test is here: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11742 Feel free to put comments and I will update them later, or just update the patch if it is quick for you, add your name into the author in commit message. You also can create standalone patches if you change is not covered by mentioned patches. Thanks. /Ken

4 years, 5 months

1
0
0 0

Enablement of external bl2 builds

by Bohdan.Hunko＠infineon.com

Hi everyone, When adding support for new platform we ran into an issue with BL2 variable. In our architecture we have Bootloader based on MCUboot (aka BL2) but we are not planning to build it with TF-M. Bootloader would be separate repo and be built separately. So we need the way to build TF-M with FWU service and shared data definitions when BL2=OFF. I was trying to add support for this but was not able to do this because build structure is quite complicated. Does anyone have ideas or suggestions about the way we can implement this feature? Best regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com>

4 years, 5 months

3
3
0 0

Technical Forum call - Sep 30

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, Sep 30, 15:00-16:00 UTC (US 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

4 years, 5 months

1
1
0 0

[IMPORTANT: PLATFORM BUILD ISSUE] [REQUIRE PLATFORM ACK] RE: [Request Platform Support] Abstracted MMIO HAL

by Ken Liu

Hi everyone, Being notified by some platform vendors that platforms build breaks in MASTER branch (releases are working well and not affected) due to not integrate with the latest HAL change: The reference link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11036 And these platforms reported build break: Nordic NXP Because of bandwidth issues, we can’t maintain all the platform sources, hence require upstreamed platform owners to take a look at their platform builds and runs ok, and integrate with the updated HAL if it does fail. Please reply to this thread if there are problems and I have created one ticket for tracking this if replying in a thread is more convenient for you: https://developer.trustedfirmware.org/T967 Sorry for the inconvenience made, I should warn all the platform owners in earlier mails – I will validate the build again later in Oct to see if there are still platform breaks and contact the platform code owners to discuss plans. Thanks. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: Friday, September 17, 2021 3:06 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] [Request Platform Support] Abstracted MMIO HAL The MMIO binding patch set are all merged, assume this will simplify the SPM integration much. Follow up fixups will be created if missing comments reported. Anyway, all platform patches are not blocked anymore, feel free to merge the reviewed and CI passed patches. Thanks. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: Friday, September 3, 2021 1:27 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] [Request Platform Support] Abstracted MMIO HAL Hi, Another reminder to mention the MMIO binding patches. Several platforms are changed to pass the CI, please platform owners to review the patches, such as: PSOC: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11187 STM: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11186 Some of other platform patches are created as well. This is a significant change for platform which helps much easier integration. After the first series of patches, the problems not covered by the CI need to be fixed adhoc. Please read the tech forum topic on 2nd Sep for more details or you can just scroll down to check the previous content. Thanks. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: Monday, August 30, 2021 5:18 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] [Request Platform Support] Abstracted MMIO HAL The patchset has updated and now CI passed okay: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11187 BR /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: Thursday, August 19, 2021 2:16 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] [Request Platform Support] Abstracted MMIO HAL Hi everyone, The existing HAL interface for isolation hardware is not unified, we have to call several interfaces to setup isolation boundaries. Hence, a deeper abstracted interface are provided. Here are the details: - It assumes the hardware resources usages are decided by system designer. Hence there are couple of listed hardware data in the platform code, now most of them are defined in C sources. - When a partition is referencing peripheral (represented as MMIO in FFM), the manifest tooling would link specified resources with the data defined in platform. Now it is using a naming pattern, to let the partition found the resources defined above (now it uses linker to do this). - A HAL API 'tfm_hal_bind_partition' is called when a partition runtime structure is created. This API tells partition info to platform, let platform return an encoded 'p_boundaries' for SPM binding partition with platform. - When boundaries related operations happen in future, SPM would delivery this 'p_boundaries' back to platform, let platform perform boundary setup and check, such as boundary switch or memory check. SPM won't care about the hardware specific settings any more, such as privilged, non-secure/secure and how many MMIO the partition claimed, even the MPU/MPC/PPC things. - Resources defined in platform sources but not referenced would be stripped by toolchain flag. Resources not defined but referenced by partition would generate a linker error, as symbol can't be resolved. We created a patch to showcase the usage on AN521: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11036 This patch applies a simple encoding for all isolation levels. You can check how the p_boundaries is used under different isolation levels. Platform can use other encoding mechanism if applicable. Now come to the request: Please review this patch, and port similar HAL API into your platform. We are maintaining the default platforms such as AN521, AN519 and MUSCA_B1, but it need so much effort on port to all the platforms. Current CI cannot pass on this patch (as it contains modification for one platform only), our first goal is to let CI pass build on all checked platforms, and then please platform owner ensures it works on your platform. Any feedbacks are welcome. Thank you very much! /Ken -- TF-M mailing list TF-M(a)lists.trustedfirmware.org<mailto:TF-M@lists.trustedfirmware.org> https://lists.trustedfirmware.org/mailman/listinfo/tf-m

4 years, 5 months

8
11
0 0

NSID improvement patches are in review

by David Wang

Hi, Believe you still remember I shared the non-secure client ID management update in tech forum<https://www.trustedfirmware.org/meetings/tf-m-technical-forum/> a few months ago (slides<https://www.trustedfirmware.org/docs/Non_Secure_Client_ID_management_update…>, video<https://linaro-org.zoom.us/rec/share/k7vJnf8qcugoRNxu5hRSyc0thzSTbTT295ZLyy…> (passcode: dqHBI$2z)). The patches and document are available in tf.org for public review. The integration reference and test suite are also provided. If you're using SPM to manage the NSID (fixed `-1` for all NS connections) which is the default option (`TFM_NS_CLIENT_IDENTIFICATION` is OFF), then it basically won't affect you (if you don't play with `TFM_NS_CLIENT_IDENTIFICATION` flag which is changed). NSCE (non-secure client extension) module is introduced to manage the non-secure context in TF-M which includes the NSID as a member. If you have a requirement to support different NSIDs for NS tasks, then it's for that purpose. Patches: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11288 (add non-secure context management) https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11289 (add NSCE interface API) https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11616 (Doc) https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11294 (Add NSCE support in nspm and build system) RTOS integration reference (based on RTX): https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11290/ (NSID manager example) https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11291/ (TZ API to NSCE API shim layer) A test suite is added. Tip of the test cases: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11659/ Welcome to comment. Thanks. Regards, David Wang ARM Electronic Technology (Shanghai) Co., Ltd Phone: +86-21-6154 9142 (ext. 59142)

4 years, 5 months

1
0
0 0

Proposal to separate vendor components

by Roman.Mazurak＠infineon.com

Hi all, The goal of this proposal is to separate TF-M core and platform code to simplify development and support. Take, for example, the Cypress PSoC 64 platform, we see that a significant amount of code can be committed into the repository. For end user perspective, it doesn't seem logical that project source tree has a lot of irrelevant stuff. It complicates a performance of IDE, searching and analyzing a code. Pros : Platform support can be provided separately without the need to upgrade outdated platforms or problematic platforms : https://lists.trustedfirmware.org/pipermail/tf-m/2021-January/001454.html https://developer.trustedfirmware.org/w/collaboration/project-maintenance-p… It should help to avoid or at least to minimize number of patches that requires fixes in platform folders : https://lists.trustedfirmware.org/pipermail/tf-m/2019-April/000162.html Reduces the amount of work for core team by delegating promotion of a new API support to vendors : https://lists.trustedfirmware.org/pipermail/tf-m/2019-November/000506.html Proposed solution : There are other projects that face a similar situation, for example OpenWRT, Yocto, Android. Their common feature is that they have many dependencies. The solution they propose is based on the fact that these projects have their own build infrastructure. The user's task is to create a configuration in which you can add your own components. In its current state, the TF-M already has some tools to implement platform as an external dependency. The user can specify the path to the platform using the TFM_PLATFORM variable. There is also work underway to implement support of external test infrastructure. (https://lists.trustedfirmware.org/pipermail/tf-m/2021-September/001824.html). There is a need to add support of external secure partitions instead of current solution (https://tf-m-user-guide.trustedfirmware.org/docs/integration_guide/services…). I can't say if this issue is directly related to the platform, but it's possible that it will give more opportunities to vendors or will be a useful tool for adding new platforms. The last question that needs to be addressed is how to link the sources supplied by vendors (platforms or security partitions) to the TF-M sources. Using the git submodule mechanism probably is not a good solution. There are two options : 1. Platforms, security partitions and test-suits will be listed as a submodule in the TF-M tree. But this approach will not actually solve the main problem of delegating more responsibility to vendors and breaking the connection between the vendors component and TF-M. 2. The TF-M source tree will be specified as a submodule in modules supplied by vendors. In this case we will have more problems. Because if the user's project will use two or more vendor components (for example, platform and custom security partitions), then TF-M will be mentioned more than once and it is quite possible to have several different revisions of TF-M. So, it will be impossible to properly assemble the project. Therefore, I see the use of the following approach as an alternative : 1. External components check the TF-M version using the TFM_VERSION variable. 2. A project that uses TF-M, as well as the necessary components (platforms, external security partitions, vendor / project test suites) specifies dependencies using any method. The simplest way is to commit TF-M and vendor components as submodules in the user project. 3. Paths to all dependencies should be transferred from the project to necessary parts of TF-M via CMake variables. This should be equally convenient for platforms vendors, TF-M components vendors, and TF-M end users. Risks : If the project assembled by end user will use several vendor modules (for example platform and custom security partitions). It is possible that the TF-M version required by different vendors modules will be different. But this problem is present at the moment, because any significant change to the TF-M API generates many problems that need to be solved for all supported platforms (mentioned in the pros). Any feedbacks are welcome. Best regards, Roman

4 years, 5 months

2
2
0 0

Request Access To a Board Peripheral for a App RoT - Problem

by Cristiano Rodrigues

Hi everyone, I'm trying to access an STM32L552 peripheral in a RoT APP (tf-m isolation v1.4 Level 2), but I'm having trouble doing that. I know that I have to request the peripheral in the YAML file of my partition's manifest, but that request didn't work for me. I filled the required campus and couldn't get access to the peripheral. I'm requesting the peripheral by putting this piece of code in my partition manifest YAML file. Am I missing something? ..... "mmio_regions" : [ { "name": "TFM_PERIPHERAL_TIMER0", "permission": "READ-WRITE" } ...... Another thing, I am only able to request the TIMER0 and UART peripherals? If I want to access other timers, e.g., TIMER 6 or TIMER 7, am I not allowed to do so? Cheers, Cristiano

4 years, 5 months

2
2
0 0

[Ask for review] FPU support in TF-M

by Feder Liang

Hi, All Patches for FPU support in TF-M are ready for review now. Looking for your comments! FPU here refers to Float-point unit for Arm-M profile architecture. 1. FPU support in TF-M * Support platforms: all platforms with FPU available. Current patches are developed on arm musca_s1 board as example. * After necessary settings in TF-M, it is configurable that FPU can be enabled in SPE or NSPE, or both sides. System developer can activate FPU feature on a platform by setting those flags in CMake command line. i. Enable FP in secure side: -DTFM_SYSTEM_FP= 0-software, 1-hybird, 2-hardware ii. Enable FP in non-secure side: -DTFM_SYSTEM_FP_NS= 0-software, 1-hybird, 2-hardware Also lazy stacking feature can be enabled/disabled in SPE or NSPE separately. iii. Enable lazy stacking in secure side: -DTFM_LAZY_FP=ON iv. Enable lazy stacking in non-secure side: -DTFM_LAZY_FP_NS=ON * The secure service developer/application developer does need to know the FPU setting details, they can just compile their program with proper toolchain flags to take advantage of FPU. The tested toolchains are: GNU Arm embedded toolchain and Arm Compiler. Other toolchain has FPU support should also work but needs test report from partners. Three floating-point Application Binary Interface (ABI) types of mentioned toolchain are tested: software, hybrid, and hardware option. * Support isolation level 1,2,3. * FPU needs to be available in your platform if you want to take the advantage of a hardware FPU. Please check your platform hardware specification whether FPU is available. Also need to check specification of toolchain whether the FPU architecture of your platform is supported. FPU architecture can be specified by -DTFM_FP_ARCH in CMake command line. 1. Notes: * As FF-M alignment is one of our design goals, it only supports IPC partitions at current stage. * The security mechanism is designed based on ARMv8-M Mainline and later. * To simplify the scenarios, we defined several guidelines that no involving FPU usage inside an interrupt handler, including deprivileged handler in one Partition. This can be fine-tuned later if there are requirements that insists a FPU support in handler mode. * In general, FPU is commonly available on a Armv8.0-M mainline. Please check your platform specification and report exception cases if seen. 1. For the VLLDM instruction security vulnerability of FPU, to mitigate this security vulnerability, it is required to recompile the secure image with compilers that has the software workaround implemented. For more information, please check https://developer.arm.com/support/arm-security-updates/vlldm-instruction-se…. 1. Those patches will be merged in 4-6 weeks if there is no big issue found. tf-m repo: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11688 FP context protection https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11689 Add FPU support for gnu arm embedded toolchain https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11690 Configure non-secrue timer for FPU test https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11691 Add FPU support design document https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11692 Output support for FP numbers https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11693 FPU support for Armclang compiler tf-m-tests repo: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11684 Add FPU support https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11685 Adding FPU test cases https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11686 Adding FPU non-secure interrupt test case https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11687 Printf support for FP numbers Best Regards Feder

4 years, 5 months

1
0
0 0

Outdated file location in FWU doc

by Bohdan.Hunko＠infineon.com

Hi everyone, While reading FWU service doc<https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/desig…> I found that Components paragraph<https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/desig…> contain table which says that tfm_bootloader_fwu_abstraction.h file is located in ./secure_fw/partitions/firmware_update/tfm_bootloader_fwu_abstraction.h , but it TF-M repo it is located in secure_fw\partitions\firmware_update\bootloader\tfm_bootloader_fwu_abstraction.h. Minor thing, but still worth fixing. Best regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com>

4 years, 5 months

2
1
0 0

Trouble building Musca S1 with IAR

by Thomas Törnblom

I'm working on adding IARARM as a toolchain for the Musca S1 (and B1) and I'm running into an issue where the NS image can not properly access the UART. The NS code loops trying to check the UART status @0x40102030, which holds the value 0x301, as can be seen with the debugger and also from the secure code, but when read by the NS code it returns 0, with no error. As this code works when building with ARMCLANG and GNUARM, I assume there is some memory protection that gets incorrectly setup when I build with the IAR toolchain, but I'm struggling to find where this gets setup. I assume it is done in the secure image. Any hints where i should be looking? Thanks, Thomas -- *Thomas Törnblom*, /Product Engineer/ IAR Systems AB Box 23051, Strandbodgatan 1 SE-750 23 Uppsala, SWEDEN Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01 E-mail: thomas.tornblom(a)iar.com <mailto:thomas.tornblom@iar.com> Website: www.iar.com <http://www.iar.com> Twitter: www.twitter.com/iarsystems <http://www.twitter.com/iarsystems>

4 years, 5 months

3
3
0 0

Re: [TF-M] Supporting encryption with ITS

by Fabian Schmidt

Hi George, I'm wondering if that would add value. To my understanding, ITS was never designed to be encrypted because of the way it's supposed to be set up. (It's Internal Trusted Storage.) I believe best practice is to place it in a "trusted" location, one that is ideally only accessible from Secure world, and also ideally on-die. If you then restrict outside access to the internal flash (JTAG, flash programmer ports,.), you're pretty golden, in that no unauthorized party should be able to read from or write to the ITS.* Let me know if I misunderstand anything about ITS or TrustZone, but that's my view. Maybe I'm painting an idealized picture. Greetings, Fabian Schmidt * at least short of a sophisticated physical attack or finding some loophole in TrustZone. From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Vasilakis, Georgios via TF-M Sent: Donnerstag, 23. September 2021 15:28 To: tf-m(a)lists.trustedfirmware.org Subject: [EXT] [TF-M] Supporting encryption with ITS Caution: EXT Email Hey all, Lately the requirement for an encrypted ITS solution is being asked from our customers and I would like to have a discussion here on how we can design this in a reasonable way. The first thought that came to my mind was to add the functionality to the ITS flash-fs layer. This layer contains file metadata in the its_file_meta_t structure and it should be possible to expand this to include additional crypto metadata (conditionally). This seems to be the less invasive change to me, even though it will introduce some increased memory usage since supporting encryption will mean that we cannot read the data in chunks anymore, we will have to use static buffers. At the same time, I looked at the PS partition since I knew that it has support for encryption. I believe that some core concepts of both solutions have similarities even though the code is quite different. For example, a file in ITS is similar to an object in PS and the (linear) list of file metadata in ITS is similar to the concept of the object table in PS. So, I think that it should be possible to design some generic-enough APIs that we can use for both the ITS and PS. Even though this will require some major refactoring in both partitions, it will decrease the code of these services which will probably decrease maintenance later. What are your thoughts on this? Regards, George

4 years, 5 months

4
4
0 0

TF-M v1.4.1 hotfix have been released

by Anton Komlev

Hello, Please be informed about the update v1.4.1 containing a hotfix for a vulnerability found in v1.4.0. The vulnerability exists in Profile Small only so please update to v1.4.1 version if you are currently using TF-M v1.4.0 and Profile Small. The detailed security advisory will be provided later. Best regards, Anton

4 years, 5 months

1
0
0 0

Re: [TF-M] Supporting encryption with ITS

by Vasilakis, Georgios

Thank you both for the input! Andrej, you are correct that right now PS == Encrypted ITS but my understanding of the spec tells me that this will not always be the case. They do refer to platforms that will use external storage for PS (even though they still require ITS even in this case indeed). And just to clarify, I don't propose creating yet another ITS. The second thought that I had regarding the refactoring is mainly a common library that both ITS and PS can use for object handling. Fabian, I also understand it similarly, the ITS is supposed to be trusted on-chip storage which is more protected than PS. And the isolation from TrustZone in normal circumstances should be adequate (at the moment). But physical attacks these days are not that sophisticated anymore, and I think that this is the main driving force for this requirement. Regards, George ________________________________ From: Fabian Schmidt Sent: Thursday, September 23, 2021 3:50 PM To: Vasilakis, Georgios Cc: tf-m(a)lists.trustedfirmware.org Subject: RE: [TF-M] Supporting encryption with ITS Hi George, I’m wondering if that would add value. To my understanding, ITS was never designed to be encrypted because of the way it’s supposed to be set up. (It’s Internal Trusted Storage.) I believe best practice is to place it in a “trusted” location, one that is ideally only accessible from Secure world, and also ideally on-die. If you then restrict outside access to the internal flash (JTAG, flash programmer ports,…), you’re pretty golden, in that no unauthorized party should be able to read from or write to the ITS.* Let me know if I misunderstand anything about ITS or TrustZone, but that’s my view. Maybe I’m painting an idealized picture. Greetings, Fabian Schmidt * at least short of a sophisticated physical attack or finding some loophole in TrustZone… From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Vasilakis, Georgios via TF-M Sent: Donnerstag, 23. September 2021 15:28 To: tf-m(a)lists.trustedfirmware.org Subject: [EXT] [TF-M] Supporting encryption with ITS Caution: EXT Email Hey all, Lately the requirement for an encrypted ITS solution is being asked from our customers and I would like to have a discussion here on how we can design this in a reasonable way. The first thought that came to my mind was to add the functionality to the ITS flash-fs layer. This layer contains file metadata in the its_file_meta_t structure and it should be possible to expand this to include additional crypto metadata (conditionally). This seems to be the less invasive change to me, even though it will introduce some increased memory usage since supporting encryption will mean that we cannot read the data in chunks anymore, we will have to use static buffers. At the same time, I looked at the PS partition since I knew that it has support for encryption. I believe that some core concepts of both solutions have similarities even though the code is quite different. For example, a file in ITS is similar to an object in PS and the (linear) list of file metadata in ITS is similar to the concept of the object table in PS. So, I think that it should be possible to design some generic-enough APIs that we can use for both the ITS and PS. Even though this will require some major refactoring in both partitions, it will decrease the code of these services which will probably decrease maintenance later. What are your thoughts on this? Regards, George

4 years, 6 months

1
0
0 0

Supporting encryption with ITS

by Vasilakis, Georgios

Hey all, Lately the requirement for an encrypted ITS solution is being asked from our customers and I would like to have a discussion here on how we can design this in a reasonable way. The first thought that came to my mind was to add the functionality to the ITS flash-fs layer. This layer contains file metadata in the its_file_meta_t structure and it should be possible to expand this to include additional crypto metadata (conditionally). This seems to be the less invasive change to me, even though it will introduce some increased memory usage since supporting encryption will mean that we cannot read the data in chunks anymore, we will have to use static buffers. At the same time, I looked at the PS partition since I knew that it has support for encryption. I believe that some core concepts of both solutions have similarities even though the code is quite different. For example, a file in ITS is similar to an object in PS and the (linear) list of file metadata in ITS is similar to the concept of the object table in PS. So, I think that it should be possible to design some generic-enough APIs that we can use for both the ITS and PS. Even though this will require some major refactoring in both partitions, it will decrease the code of these services which will probably decrease maintenance later. What are your thoughts on this? Regards, George

4 years, 6 months

2
1
0 0

Use IPC Model to build by default

by Kevin Peng

Hi all, Please be noted that we are changing the build system to build IPC model by default instead of Library model for the following reasons: * The Library Model is not being developed anymore. It does not support for new FF-M features. * New comers to TF-M should be encouraged to start with the IPC model to have the better experiences. * Most importantly, Library Model will be replaced by SFN Model in future. Patch here: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11384 With this patch, the TFM_PSA_API is not intended for users to choose between library and IPC model anymore. To build Library model, please set TFM_LIB_MODEL to ON. The TFM_PSA_API=ON can be kept as is for the time being. So there would be impacts wherever Library Model is used. Please get prepared. Thanks. Best Regards, Kevin

4 years, 6 months

1
2
0 0

Re: [TF-M] [Request Platform Support] Abstracted MMIO HAL

by Ken Liu

Hi, Another reminder to mention the MMIO binding patches. Several platforms are changed to pass the CI, please platform owners to review the patches, such as: PSOC: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11187 STM: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11186 Some of other platform patches are created as well. This is a significant change for platform which helps much easier integration. After the first series of patches, the problems not covered by the CI need to be fixed adhoc. Please read the tech forum topic on 2nd Sep for more details or you can just scroll down to check the previous content. Thanks. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: Monday, August 30, 2021 5:18 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] [Request Platform Support] Abstracted MMIO HAL The patchset has updated and now CI passed okay: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11187 BR /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: Thursday, August 19, 2021 2:16 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] [Request Platform Support] Abstracted MMIO HAL Hi everyone, The existing HAL interface for isolation hardware is not unified, we have to call several interfaces to setup isolation boundaries. Hence, a deeper abstracted interface are provided. Here are the details: - It assumes the hardware resources usages are decided by system designer. Hence there are couple of listed hardware data in the platform code, now most of them are defined in C sources. - When a partition is referencing peripheral (represented as MMIO in FFM), the manifest tooling would link specified resources with the data defined in platform. Now it is using a naming pattern, to let the partition found the resources defined above (now it uses linker to do this). - A HAL API 'tfm_hal_bind_partition' is called when a partition runtime structure is created. This API tells partition info to platform, let platform return an encoded 'p_boundaries' for SPM binding partition with platform. - When boundaries related operations happen in future, SPM would delivery this 'p_boundaries' back to platform, let platform perform boundary setup and check, such as boundary switch or memory check. SPM won't care about the hardware specific settings any more, such as privilged, non-secure/secure and how many MMIO the partition claimed, even the MPU/MPC/PPC things. - Resources defined in platform sources but not referenced would be stripped by toolchain flag. Resources not defined but referenced by partition would generate a linker error, as symbol can't be resolved. We created a patch to showcase the usage on AN521: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11036 This patch applies a simple encoding for all isolation levels. You can check how the p_boundaries is used under different isolation levels. Platform can use other encoding mechanism if applicable. Now come to the request: Please review this patch, and port similar HAL API into your platform. We are maintaining the default platforms such as AN521, AN519 and MUSCA_B1, but it need so much effort on port to all the platforms. Current CI cannot pass on this patch (as it contains modification for one platform only), our first goal is to let CI pass build on all checked platforms, and then please platform owner ensures it works on your platform. Any feedbacks are welcome. Thank you very much! /Ken

4 years, 6 months

5
6
0 0

memory_region_limits structure contents

by Bohdan.Hunko＠infineon.com

Hi everyone, I was wondering is there any reasons to use REGION_NAME(Load$$LR$$, LR_NS_PARTITION, $$Base) declared in this code<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e…> and used here<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e…>? >From code in common linker script<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e…> I can see: Load$$LR$$LR_NS_PARTITION$$Base = NS_PARTITION_START. So the question is: why regions are used instead of simply using NS_PARTITION_START? And the follow up questions is: do platforms that are built in IPC model (not library model) really need REGION_NAME(Load$$LR$$, LR_VENEER, $$Base)in memory_region_limits memory_regions struct, or that could be just dummy value? Best regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com>

4 years, 6 months

2
2
0 0

Move MCUBoot configs to bl2 specific config file

by Jianliang Shen

Hi all, We decide to move MCUBoot specific configurations to TF-M/bl2/ext/mcuboot folder. This change is to decouple MCUBoot and TF-M configurations and make default_config.cmake clearer. I have proposed the patch set: * [TF-M patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/10560>] I'm grateful to receive any suggestion or enhancement from you. Best Regards Jianliang Shen

4 years, 6 months

1
1
0 0

Re: [TF-M] [RFC] Decoupling tf-m-tests from TF-M

by David Hu

Hi all, I'd like to merge the following patch set tomorrow, if there is no more major comment. * Decouple tf-m-tests specific config setting from trusted-firmware-m. [TF-M patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11167>][tf-m-tests patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11169>] * Decouple tf-m-tests secure log from non-secure log. Switch tf-m-tests secure log to TF-M SP log. [TF-M patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11153>][tf-m-tests patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11131/>] After the above patches are merged, there are two major changes: * tf-m-tests dedicated configuration setup process will be moved to tf-m-test repo, from TF-M. Therefore you can update tf-m-tests config setting, without modifying TF-M repo. * Tf-m-tests commit ID is specified in TF-M `lib\ext\tf-m-tests\repo_config_default.cmake`, rather than in TF-M main `config_default.cmake`. You can update tf-m-tests commit ID in TF-M without touching the large `config_default.cmake`. Any suggestion or comment is always welcome! Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Tuesday, August 24, 2021 5:33 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [RFC] Decoupling tf-m-tests from TF-M Hi all, As you may know, Jianliang and I are working to better decouple tf-m-tests from trusted-firmware-m repo. The purpose of the decoupling enhancement includes: * Making it more easier to integrate TF-M and port tf-m-tests * Making it more easier to develop TF-M tests, to minimize the changes to TF-M source code or build system. * Making it more flexible to re-structure tf-m-tests and minimize the impact to TF-M Previously Jianliang has decouple test case control and enable users to select single NS/S regression test case in build and test. Currently we are focusing on decoupling tf-m-tests specific config setting from TF-M. So far we have proposed the following major changes: * Decouple tf-m-tests specific config setting from trusted-firmware-m. [TF-M patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11167>][tf-m-tests patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11169/1>] * Move tf-m-tests specific configs to tf-m-tests repo from trusted-firmware-m [TF-M patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/10647>][tf-m-tests patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/10556>] More patch sets for decoupling are under review as well. * Decouple tf-m-tests secure log from non-secure log. Switch tf-m-tests secure log to TF-M SP log. [TF-M patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11153>][tf-m-tests patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11131/3>] * Trigger secure regression tests in TF-M SPE in IPC model, to simplify multi-core development/tests [TF-M patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11181>][tf-m-tests patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11182>] I'd appreciate it if you can take a look at the patch sets above. Any suggestion or comment is welcome. If you have any specific requirement or suggestion of tf-m-tests enhancement, please feel free to contact Jianliang and me. Thanks in advance. Best regards, Hu Ziji

4 years, 6 months

2
4
0 0

Adding tfm_mailbox_config.h to .gitignore

by Bohdan.Hunko＠infineon.com

Hello everyone. After building the project interface/include/multi_core/tfm_mailbox_config.h is generated, but it is not in .gitignore I think this file should be in .gitignore because it is build artifact and is really annoying to deal with. Am I wrong somewhere? Best regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com>

4 years, 6 months

2
4
0 0

Remove some platform specific test cases

by Shawn Shan

Hi all, We are going to remove some test cases in tfm_core_test. They are: * TFM_INTERACTIVE_TEST * TFM_PERIPH_ACCESS_TEST The main reasons is that these peripheral and interactive test cases are mainly platform specific(button and LEDs), rather than test the main features and secure functionalities of TF-M. Besides, it also a burden for flatform owner to support and maintain those test cases. Do you have any concerns for remove those test cases? Best Regards, Shawn

4 years, 6 months

1
0
0 0

Technical Forum call - Sep 16

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, Sep 16, 7:00-8:00 UTC (Asia 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

4 years, 6 months

3
2
0 0

Re: [TF-M] TF-M Digest, Vol 35, Issue 6

by Michael Thomas

Ken, Hu, I just saw this message now and wanted to give my perspective based on some of the code Renesas has developed. In general, the primary benefits of having enums are return codes are type checking and portability. So of you have a top level application using an API that always returns an error from a defined enum list, then the application can switch to using different implementations of the same API and does not have to change its error handling code etc. However, if you are returning uint32 instead then its likely that different implementations of the same API will have any possible return code making the application non-portable. I think the issue arises when the enum list is not sufficiently well defined so each enum entry ends up acting as a funnel for x number of lower level error code so there is loss of information etc. But w.r.t the line in the TFM coding guide : " Use enumeration for error codes to keep the code readable.", if the objective is just to make the code readable, then you don’t really need an enum for that... you can achieve readability by using #define XYZ_error. I think that will be much harder to maintain particularly in terms of preventing different error codes from being defined to the same value unless we have a common file where all error code are defined for a specific layer. -Michael -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of tf-m-request(a)lists.trustedfirmware.org Sent: Friday, September 3, 2021 4:38 AM To: tf-m(a)lists.trustedfirmware.org Subject: TF-M Digest, Vol 35, Issue 6 Send TF-M mailing list submissions to tf-m(a)lists.trustedfirmware.org To subscribe or unsubscribe via the World Wide Web, visit https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.tru… or, via email, send a message with subject or body 'help' to tf-m-request(a)lists.trustedfirmware.org You can reach the person managing the list at tf-m-owner(a)lists.trustedfirmware.org When replying, please edit your Subject line so it is more specific than "Re: Contents of TF-M digest..." Today's Topics: 1. Re: [RFC] Can we remove the rule to use enum for error code? (Ken Liu) 2. Re: [RFC] Can we remove the rule to use enum for error code? (Andrew Thoelke) ---------------------------------------------------------------------- Message: 1 Date: Fri, 3 Sep 2021 07:54:41 +0000 From: Ken Liu <Ken.Liu(a)arm.com> To: "tf-m(a)lists.trustedfirmware.org" <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] [RFC] Can we remove the rule to use enum for error code? Message-ID: <DBBPR08MB4741B0807FC4ACD9F4466520F5CF9(a)DBBPR08MB4741.eurprd08.prod.outlook.com> Content-Type: text/plain; charset="utf-8" I am okay to remove it. Even it can be used to check the error types, but some of the developers do typecast on enum which makes the rule no sense. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Friday, September 3, 2021 3:45 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [RFC] Can we remove the rule to use enum for error code? Hi all, Probably you didn’t know that there is such a rule in TF-M coding standard<https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftf-m-user…>: * Use enumeration for error codes to keep the code readable. Personally, I’d prefer macros to enum, for error codes. * The implicit type casting of enum can be an issue in coding. TF-M has a document<https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftf-m-user…> to solve this. * Using macros to define error codes aligns with PSA return code definitions. * Enum makes function and variable definitions longer * Enum may help developers skip writing specific error code values. But it becomes a trouble when you see an error number from log. You might need to count the enum fields one by one. * Error codes for errors are usually negative but enums are positive ones by default. I’d like to propose to remove this rule from TF-M coding standard. But it doesn’t mean that enum shall not be used anymore. I’m wondering if macros for error code in TF-M can be approved as well. 😊 May I know your opinions please? If it is a convention or a good practice to use enum for error codes in security/trusted software, please help point me to the reference. I don’t find one via google. Thanks a lot! Best regards, Hu Ziji -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://jpn01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.trus…> ------------------------------ Message: 2 Date: Fri, 3 Sep 2021 08:38:02 +0000 From: Andrew Thoelke <Andrew.Thoelke(a)arm.com> To: "tf-m(a)lists.trustedfirmware.org" <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] [RFC] Can we remove the rule to use enum for error code? Message-ID: <DB7PR08MB38651B33CD7BAEB9BF05F0229ACF9(a)DB7PR08MB3865.eurprd08.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Hi, In my experience, the only significant benefit of using enums is that some debuggers display the symbolic name for a value with the enum type. But, as already mentioned, using enums does not help in parsing logs, or decoding error values in integer variables/registers; particularly when the definition does not provide explicit values for each identifier. In addition, the rules for determining the implicit integer type for an enum type are non-trivial. This results in a lack of transparency when reading or reviewing code with respect to the size of the enum type in a data structure, or the behaviour when converting an enum value to an integer (or back again). This is why the PSA specifications use explicitly sized integer types for types like psa_status_t, and macros to define values of such types. Regards, Andrew From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: 03 September 2021 08:45 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [RFC] Can we remove the rule to use enum for error code? Hi all, Probably you didn’t know that there is such a rule in TF-M coding standard<https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftf-m-user…>: * Use enumeration for error codes to keep the code readable. Personally, I’d prefer macros to enum, for error codes. * The implicit type casting of enum can be an issue in coding. TF-M has a document<https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftf-m-user…> to solve this. * Using macros to define error codes aligns with PSA return code definitions. * Enum makes function and variable definitions longer * Enum may help developers skip writing specific error code values. But it becomes a trouble when you see an error number from log. You might need to count the enum fields one by one. * Error codes for errors are usually negative but enums are positive ones by default. I’d like to propose to remove this rule from TF-M coding standard. But it doesn’t mean that enum shall not be used anymore. I’m wondering if macros for error code in TF-M can be approved as well. 😊 May I know your opinions please? If it is a convention or a good practice to use enum for error codes in security/trusted software, please help point me to the reference. I don’t find one via google. Thanks a lot! Best regards, Hu Ziji -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://jpn01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.trus…> ------------------------------ Subject: Digest Footer TF-M mailing list TF-M(a)lists.trustedfirmware.org https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.tru… ------------------------------ End of TF-M Digest, Vol 35, Issue 6 *********************************** Disclaimer: This message and any files or text attached to it are intended only for the recipients named above and contain information that may be confidential or privileged. If you are not an intended recipient, you must not forward, copy, use or otherwise disclose this communication or the information contained herein. In the event you have received this message in error, please notify the sender immediately by replying to this message, and then delete all copies of it from your system. Thank you.

4 years, 6 months

2
1
0 0

Unaligned flash read/write is supported in Boot & FWU

by Sherry Zhang

Hi, The following patch enables the flash read/write with unaligned address/cnt for MCUboot and Firmware Update partition. https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/10947 This patch has been merged and thanks to all who have reviewed on this patch. As this patch can impact the MCUboot booting up on the platforms, if there is any booting up issue on your platform after this commit, do not hesitate to feedback to me. 😊 Thanks, Regards, Sherry Zhang

4 years, 6 months

1
0
0 0

BOOT_TFM_SHARED_DATA_* usage in arm/musca_b1

by Bohdan.Hunko＠infineon.com

Hi everyone! I see definitions of BOOT_TFM_SHARED_DATA_* in platform\ext\target\arm\musca_b1\sse_200\partition\region_defs.h but I don't see any real usage of that memory. I have found TF-M doc<https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/desig…> that describe usage of shared memory for Firmware Update Service but once again I was not able to find any code that uses that. I would appreciate if someone could point to docs on this or to code that actually uses shared data between BL2 and TF-M SPE. Best regards, Bohdan Hunko Cypress Semiconductor Ukraine Engineer CSUKR CSS ICW SW FW Mobile: +38099 50 19 714 Bohdan.Hunko(a)infineon.com<mailto:Bohdan.Hunko@infineon.com>

4 years, 6 months

4
3
0 0

[RFC] Can we remove the rule to use enum for error code?

by David Hu

Hi all, Probably you didn’t know that there is such a rule in TF-M coding standard<https://tf-m-user-guide.trustedfirmware.org/docs/contributing/coding_guide.…>: * Use enumeration for error codes to keep the code readable. Personally, I’d prefer macros to enum, for error codes. * The implicit type casting of enum can be an issue in coding. TF-M has a document<https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/desig…> to solve this. * Using macros to define error codes aligns with PSA return code definitions. * Enum makes function and variable definitions longer * Enum may help developers skip writing specific error code values. But it becomes a trouble when you see an error number from log. You might need to count the enum fields one by one. * Error codes for errors are usually negative but enums are positive ones by default. I’d like to propose to remove this rule from TF-M coding standard. But it doesn’t mean that enum shall not be used anymore. I’m wondering if macros for error code in TF-M can be approved as well. 😊 May I know your opinions please? If it is a convention or a good practice to use enum for error codes in security/trusted software, please help point me to the reference. I don’t find one via google. Thanks a lot! Best regards, Hu Ziji

4 years, 6 months

4
4
0 0

Re: [TF-M] TF-M v1.3.0 release - Fault Injection and DPA in line with PSA L3 Certification

by Reed Hinkel

Hello Suresh: How are you? I hope all is well with you! Virtual Linaro Connect Fall is next week and there is a presentation relevant to your question along with some others. As an online event, it is free registration and I am listing here below a few sessions that might be of interest to you related to security and AI inferencing for microcontrollers: https://connect.linaro.org/schedule LVC21F-116 Assessing the effectiveness of MCUBoot protections against fault injection attacks https://events.pinetool.ai/2231/#sessions/67139?referrer%5Bpathname%5D=%2Fs… LVC21F-112 Picolibc: A C Library for Smaller Systems https://events.pinetool.ai/2231/#sessions/67136?referrer%5Bpathname%5D=%2Fs… LVC21F-303 Secure Sensor Data Pipeline https://events.pinetool.ai/2231/#sessions/67174?referrer%5Bpathname%5D=%2Fs… LVC21F-312 TrustedFirmware.org panel discussion https://events.pinetool.ai/2231/#sessions/67183?referrer%5Bpathname%5D=%2Fs… LVC21F-319 TVM for micro targets https://events.pinetool.ai/2231/#sessions/67190?referrer%5Bpathname%5D=%2Fs… I thought you may be interested in the AI as well since there are security implications for trusted AI. All the best! Reed From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Suresh Marisetty via TF-M <tf-m(a)lists.trustedfirmware.org> Reply-To: "Suresh.Marisetty(a)infineon.com" <Suresh.Marisetty(a)infineon.com> Date: Thursday, September 2, 2021 at 8:23 AM To: Anton Komlev <Anton.Komlev(a)arm.com>, "tf-m(a)lists.trustedfirmware.org" <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] TF-M v1.3.0 release - Fault Injection and DPA in line with PSA L3 Certification Hi, I have a question related to the PSA L3 certification and the requirement to support Side-channel and fault injection attacks. I have noted that TFM and MCUBoot does implement some software countermeasures for Fault Injection. However, I am wondering if there is similar implementation support for the Crypto Lib in TFM (or Mbed TLS) with software counter measures for side channel DPA. Needless to say, there are some known best practices for DPA software countermeasures. thanks Suresh Marisetty Infineon Semiconductor Corporation From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Friday, April 9, 2021 6:25 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] TF-M v1.3.0 release Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe<https://goto.infineon.com/SocialEngineering>. Hello, TF-M project released version v1.3.0, tagged as TF-Mv1.3.0. Please take a look into the release notes for the new features and changes: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/refer… The major features: * Support stateless RoT Service defined in FF-M 1.1 * Support Second-Level Interrupt Handling (SLIH) defined in FF-M 1.1 * Add Firmware Update (FWU) secure service, following Platform Security Architecture Firmware Update API * Migrate to Mbed TLS v2.25.0 * Update MCUboot version to v1.7.2 * Add a TF-M generic threat model * Implement Fault Injection Handling library to mitigate physical attacks * Add Profile Large * Enable code sharing between boot loader and TF-M * Support Armv8.1-M Privileged Execute Never (PXN) attribute and Thread reentrancy disabled (TRD) feature * New platforms added * Add a TF-M security landing page * Enhance dual-cpu non-secure mailbox reference implementation This is the first release performed in the OpenCI infrastructure with no single issue encountered. Thanks to everyone who directly and indirectly contributed to this milestone. Anton Komlev TF-M technical lead Arm Ltd.

4 years, 6 months

1
0
0 0

Re: [TF-M] TF-M v1.3.0 release - Fault Injection and DPA in line with PSA L3 Certification

by Suresh.Marisetty＠infineon.com

Hi, I have a question related to the PSA L3 certification and the requirement to support Side-channel and fault injection attacks. I have noted that TFM and MCUBoot does implement some software countermeasures for Fault Injection. However, I am wondering if there is similar implementation support for the Crypto Lib in TFM (or Mbed TLS) with software counter measures for side channel DPA. Needless to say, there are some known best practices for DPA software countermeasures. thanks Suresh Marisetty Infineon Semiconductor Corporation From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Friday, April 9, 2021 6:25 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] TF-M v1.3.0 release Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe<https://goto.infineon.com/SocialEngineering>. Hello, TF-M project released version v1.3.0, tagged as TF-Mv1.3.0. Please take a look into the release notes for the new features and changes: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/refer… The major features: * Support stateless RoT Service defined in FF-M 1.1 * Support Second-Level Interrupt Handling (SLIH) defined in FF-M 1.1 * Add Firmware Update (FWU) secure service, following Platform Security Architecture Firmware Update API * Migrate to Mbed TLS v2.25.0 * Update MCUboot version to v1.7.2 * Add a TF-M generic threat model * Implement Fault Injection Handling library to mitigate physical attacks * Add Profile Large * Enable code sharing between boot loader and TF-M * Support Armv8.1-M Privileged Execute Never (PXN) attribute and Thread reentrancy disabled (TRD) feature * New platforms added * Add a TF-M security landing page * Enhance dual-cpu non-secure mailbox reference implementation This is the first release performed in the OpenCI infrastructure with no single issue encountered. Thanks to everyone who directly and indirectly contributed to this milestone. Anton Komlev TF-M technical lead Arm Ltd.

4 years, 6 months

2
1
0 0

Re: [TF-M] Technical Forum call - Sep 2

by Anton Komlev

Hi, The agenda for the forum tomorrow: 1. "Summary of the proposed changes in FF-M v1.1 beta" by Andrew Thoelke 2. "Summary of upcoming significant changes in SPM" by Ken Liu containing: * MMIO and interrupt binding. * Remove unformal symbols such as ARM_LIB_STACK_MSP. Thanks, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: Saturday, August 28, 2021 9:36 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Technical Forum call - Sep 2 Hi, There are some significant changes happen in SPM and I want to introduce them in a summary, contains: * MMIO and interrupt binding. * Remove unformal symbols such as ARM_LIB_STACK_MSP. Assuming 30 mins should be good enough. BR /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Anton Komlev via TF-M Sent: Wednesday, August 25, 2021 7:13 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] Technical Forum call - Sep 2 Hi, The next Technical Forum is planned on Thursday, September 2, 15:00-16:00 UTC (US 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

4 years, 6 months

1
0
0 0

Re: [TF-M] [RFC] Changing initialization Stack from PSP to MSP

by Kevin Peng

Hi all, We plan to merge the below patch on next Monday. We will not be able to verify on all platforms. Please do have a test on your platforms. Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M Sent: Tuesday, August 24, 2021 11:02 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [RFC] Changing initialization Stack from PSP to MSP Hi dear platform maintainers, I'd like to draw your attention on this patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11165>. It changes the initialization stack from PSP to MSP. Would you please check if this change breaks your platform? Hi Thomas@IAR, would you please check the changes for IAR? Thanks. For the details of the change, please refer to the patch. Best Regards, Kevin

4 years, 6 months

1
0
0 0

Re: [TF-M] [Request Platform Support] Abstracted MMIO HAL

by Ken Liu

The patchset has updated and now CI passed okay: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11187 BR /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: Thursday, August 19, 2021 2:16 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [Request Platform Support] Abstracted MMIO HAL Hi everyone, The existing HAL interface for isolation hardware is not unified, we have to call several interfaces to setup isolation boundaries. Hence, a deeper abstracted interface are provided. Here are the details: - It assumes the hardware resources usages are decided by system designer. Hence there are couple of listed hardware data in the platform code, now most of them are defined in C sources. - When a partition is referencing peripheral (represented as MMIO in FFM), the manifest tooling would link specified resources with the data defined in platform. Now it is using a naming pattern, to let the partition found the resources defined above (now it uses linker to do this). - A HAL API 'tfm_hal_bind_partition' is called when a partition runtime structure is created. This API tells partition info to platform, let platform return an encoded 'p_boundaries' for SPM binding partition with platform. - When boundaries related operations happen in future, SPM would delivery this 'p_boundaries' back to platform, let platform perform boundary setup and check, such as boundary switch or memory check. SPM won't care about the hardware specific settings any more, such as privilged, non-secure/secure and how many MMIO the partition claimed, even the MPU/MPC/PPC things. - Resources defined in platform sources but not referenced would be stripped by toolchain flag. Resources not defined but referenced by partition would generate a linker error, as symbol can't be resolved. We created a patch to showcase the usage on AN521: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11036 This patch applies a simple encoding for all isolation levels. You can check how the p_boundaries is used under different isolation levels. Platform can use other encoding mechanism if applicable. Now come to the request: Please review this patch, and port similar HAL API into your platform. We are maintaining the default platforms such as AN521, AN519 and MUSCA_B1, but it need so much effort on port to all the platforms. Current CI cannot pass on this patch (as it contains modification for one platform only), our first goal is to let CI pass build on all checked platforms, and then please platform owner ensures it works on your platform. Any feedbacks are welcome. Thank you very much! /Ken

4 years, 6 months

1
0
0 0

Re: [TF-M] Technical Forum call - Sep 2

by Ken Liu

Hi, There are some significant changes happen in SPM and I want to introduce them in a summary, contains: * MMIO and interrupt binding. * Remove unformal symbols such as ARM_LIB_STACK_MSP. Assuming 30 mins should be good enough. BR /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Wednesday, August 25, 2021 7:13 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - Sep 2 Hi, The next Technical Forum is planned on Thursday, September 2, 15:00-16:00 UTC (US 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

4 years, 6 months

1
0
0 0

Re: [TF-M] [RFC] Decoupling tf-m-tests from TF-M

by David Hu

Hi Chris, It is an excellent suggestion. Out-of-tree Secure Partition build can help integrate secure test service. Non-secure tests are a bit limited due to current tf-m-tests framework right now. Do you prefer to run platform-specific tests alone or still integrate platform-specific tests into TF-M regression tests? Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of chris.brand--- via TF-M Sent: Tuesday, August 24, 2021 11:46 PM To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] [RFC] Decoupling tf-m-tests from TF-M Just wondering if any though has been given to supporting platform-specific tests? Chris From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of David Hu via TF-M Sent: Tuesday, August 24, 2021 3:21 AM To: Andrej Butok <andrey.butok(a)nxp.com<mailto:andrey.butok@nxp.com>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] [RFC] Decoupling tf-m-tests from TF-M Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe<https://intranet-content.infineon.com/explore/aboutinfineon/rules/informati…>. Hi Andrej, Thanks for the suggestion. Sure. I will track it in the backlog. Currently Jianliang and I are more focusing on the structure level enhancement. But definitely later we will take more effort in the detailed optimizations. Please let us know any time if any other potential issue shall be optimized. Best regards, Hu Ziji From: Andrej Butok <andrey.butok(a)nxp.com<mailto:andrey.butok@nxp.com>> Sent: Tuesday, August 24, 2021 6:15 PM To: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: RE: [RFC] Decoupling tf-m-tests from TF-M Hi Hu Zij, Thank you for adding possibility to select test cases flexibly. Also, there are about 10 "test" services/partitions in addition to the core PSA ones. But every instance allocates own resources, which can be shared. Guess, merging these 10 test services, which have a common structure, can save some memory. Thank you, Andrej From: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Sent: Tuesday, August 24, 2021 11:54 AM To: Andrej Butok <andrey.butok(a)nxp.com<mailto:andrey.butok@nxp.com>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: RE: [RFC] Decoupling tf-m-tests from TF-M Hi Andrej, Sorry for the trouble. It does be an issue when TF-M features and test cases are growing faster. So now TF-M support to select a single test case or a subset of test cases to build and run. If running all the tests together costs too much memory, you can select some test cases or just a single one in one time. It is also helpful when you focus on a specific test in debug or development. We are also considering other additional mechanisms to select test case flexibly. Regarding "merging existing ones", do you mean that some test cases shall be disabled by default or combining the similar test cases? May I ask for some examples? Best regards, Hu Ziji From: Andrej Butok <andrey.butok(a)nxp.com<mailto:andrey.butok@nxp.com>> Sent: Tuesday, August 24, 2021 5:44 PM To: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: RE: [RFC] Decoupling tf-m-tests from TF-M Hi Hu Ziji, BTW: The number of the testing partitions and services is growing consuming memory resources. So, we have to disable some tests for our memory constrained devices. Please think about minimizing number of "testing" partitions/services, by merging existing ones, when it is possible. Thank you, Andrej Butok SW Tech Lead Edge Processing NXP Semiconductors From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of David Hu via TF-M Sent: Tuesday, August 24, 2021 11:33 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] [RFC] Decoupling tf-m-tests from TF-M Hi all, As you may know, Jianliang and I are working to better decouple tf-m-tests from trusted-firmware-m repo. The purpose of the decoupling enhancement includes: * Making it more easier to integrate TF-M and port tf-m-tests * Making it more easier to develop TF-M tests, to minimize the changes to TF-M source code or build system. * Making it more flexible to re-structure tf-m-tests and minimize the impact to TF-M Previously Jianliang has decouple test case control and enable users to select single NS/S regression test case in build and test. Currently we are focusing on decoupling tf-m-tests specific config setting from TF-M. So far we have proposed the following major changes: * Decouple tf-m-tests specific config setting from trusted-firmware-m. [TF-M patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>][tf-m-tests patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>] * Move tf-m-tests specific configs to tf-m-tests repo from trusted-firmware-m [TF-M patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>][tf-m-tests patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>] More patch sets for decoupling are under review as well. * Decouple tf-m-tests secure log from non-secure log. Switch tf-m-tests secure log to TF-M SP log. [TF-M patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>][tf-m-tests patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>] * Trigger secure regression tests in TF-M SPE in IPC model, to simplify multi-core development/tests [TF-M patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>][tf-m-tests patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>] I'd appreciate it if you can take a look at the patch sets above. Any suggestion or comment is welcome. If you have any specific requirement or suggestion of tf-m-tests enhancement, please feel free to contact Jianliang and me. Thanks in advance. Best regards, Hu Ziji

4 years, 6 months

2
2
0 0

Technical Forum call - Sep 2

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, September 2, 15:00-16:00 UTC (US 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

4 years, 6 months

1
0
0 0

Re: [TF-M] [RFC] Decoupling tf-m-tests from TF-M

by Chris.Brand＠infineon.com

Just wondering if any though has been given to supporting platform-specific tests? Chris From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Tuesday, August 24, 2021 3:21 AM To: Andrej Butok <andrey.butok(a)nxp.com> Cc: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] [RFC] Decoupling tf-m-tests from TF-M Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe<https://intranet-content.infineon.com/explore/aboutinfineon/rules/informati…>. Hi Andrej, Thanks for the suggestion. Sure. I will track it in the backlog. Currently Jianliang and I are more focusing on the structure level enhancement. But definitely later we will take more effort in the detailed optimizations. Please let us know any time if any other potential issue shall be optimized. Best regards, Hu Ziji From: Andrej Butok <andrey.butok(a)nxp.com<mailto:andrey.butok@nxp.com>> Sent: Tuesday, August 24, 2021 6:15 PM To: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: RE: [RFC] Decoupling tf-m-tests from TF-M Hi Hu Zij, Thank you for adding possibility to select test cases flexibly. Also, there are about 10 "test" services/partitions in addition to the core PSA ones. But every instance allocates own resources, which can be shared. Guess, merging these 10 test services, which have a common structure, can save some memory. Thank you, Andrej From: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Sent: Tuesday, August 24, 2021 11:54 AM To: Andrej Butok <andrey.butok(a)nxp.com<mailto:andrey.butok@nxp.com>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: RE: [RFC] Decoupling tf-m-tests from TF-M Hi Andrej, Sorry for the trouble. It does be an issue when TF-M features and test cases are growing faster. So now TF-M support to select a single test case or a subset of test cases to build and run. If running all the tests together costs too much memory, you can select some test cases or just a single one in one time. It is also helpful when you focus on a specific test in debug or development. We are also considering other additional mechanisms to select test case flexibly. Regarding "merging existing ones", do you mean that some test cases shall be disabled by default or combining the similar test cases? May I ask for some examples? Best regards, Hu Ziji From: Andrej Butok <andrey.butok(a)nxp.com<mailto:andrey.butok@nxp.com>> Sent: Tuesday, August 24, 2021 5:44 PM To: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: RE: [RFC] Decoupling tf-m-tests from TF-M Hi Hu Ziji, BTW: The number of the testing partitions and services is growing consuming memory resources. So, we have to disable some tests for our memory constrained devices. Please think about minimizing number of "testing" partitions/services, by merging existing ones, when it is possible. Thank you, Andrej Butok SW Tech Lead Edge Processing NXP Semiconductors From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of David Hu via TF-M Sent: Tuesday, August 24, 2021 11:33 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] [RFC] Decoupling tf-m-tests from TF-M Hi all, As you may know, Jianliang and I are working to better decouple tf-m-tests from trusted-firmware-m repo. The purpose of the decoupling enhancement includes: * Making it more easier to integrate TF-M and port tf-m-tests * Making it more easier to develop TF-M tests, to minimize the changes to TF-M source code or build system. * Making it more flexible to re-structure tf-m-tests and minimize the impact to TF-M Previously Jianliang has decouple test case control and enable users to select single NS/S regression test case in build and test. Currently we are focusing on decoupling tf-m-tests specific config setting from TF-M. So far we have proposed the following major changes: * Decouple tf-m-tests specific config setting from trusted-firmware-m. [TF-M patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>][tf-m-tests patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>] * Move tf-m-tests specific configs to tf-m-tests repo from trusted-firmware-m [TF-M patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>][tf-m-tests patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>] More patch sets for decoupling are under review as well. * Decouple tf-m-tests secure log from non-secure log. Switch tf-m-tests secure log to TF-M SP log. [TF-M patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>][tf-m-tests patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>] * Trigger secure regression tests in TF-M SPE in IPC model, to simplify multi-core development/tests [TF-M patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>][tf-m-tests patch<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr…>] I'd appreciate it if you can take a look at the patch sets above. Any suggestion or comment is welcome. If you have any specific requirement or suggestion of tf-m-tests enhancement, please feel free to contact Jianliang and me. Thanks in advance. Best regards, Hu Ziji

4 years, 7 months

1
0
0 0

Re: [TF-M] [RFC] Decoupling tf-m-tests from TF-M

by Andrej Butok

Hi Hu Ziji, BTW: The number of the testing partitions and services is growing consuming memory resources. So, we have to disable some tests for our memory constrained devices. Please think about minimizing number of "testing" partitions/services, by merging existing ones, when it is possible. Thank you, Andrej Butok SW Tech Lead Edge Processing NXP Semiconductors From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Tuesday, August 24, 2021 11:33 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [RFC] Decoupling tf-m-tests from TF-M Hi all, As you may know, Jianliang and I are working to better decouple tf-m-tests from trusted-firmware-m repo. The purpose of the decoupling enhancement includes: * Making it more easier to integrate TF-M and port tf-m-tests * Making it more easier to develop TF-M tests, to minimize the changes to TF-M source code or build system. * Making it more flexible to re-structure tf-m-tests and minimize the impact to TF-M Previously Jianliang has decouple test case control and enable users to select single NS/S regression test case in build and test. Currently we are focusing on decoupling tf-m-tests specific config setting from TF-M. So far we have proposed the following major changes: * Decouple tf-m-tests specific config setting from trusted-firmware-m. [TF-M patch <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr ustedfirmware.org%2Fc%2FTF-M%2Ftrusted-firmware-m%2F%2B%2F11167&data=04%7C01 %7Candrey.butok%40nxp.com%7Ce6deb39c9db74755362008d966e231b0%7C686ea1d3bc2b4 c6fa92cd99c5c301635%7C0%7C0%7C637653943958809255%7CUnknown%7CTWFpbGZsb3d8eyJ WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata =4nA45CyrLoYjN2b9ytZ6HL16Of9ItUs5OAUbPlsFPTM%3D&reserved=0> ][tf-m-tests patch <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr ustedfirmware.org%2Fc%2FTF-M%2Ftf-m-tests%2F%2B%2F11169%2F1&data=04%7C01%7Ca ndrey.butok%40nxp.com%7Ce6deb39c9db74755362008d966e231b0%7C686ea1d3bc2b4c6fa 92cd99c5c301635%7C0%7C0%7C637653943958809255%7CUnknown%7CTWFpbGZsb3d8eyJWIjo iMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aBB 0Wq8QLghyfAdwzpK%2BHR8R8LVN5emXxL0KOc4bPho%3D&reserved=0> ] * Move tf-m-tests specific configs to tf-m-tests repo from trusted-firmware-m [TF-M patch <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr ustedfirmware.org%2Fc%2FTF-M%2Ftrusted-firmware-m%2F%2B%2F10647&data=04%7C01 %7Candrey.butok%40nxp.com%7Ce6deb39c9db74755362008d966e231b0%7C686ea1d3bc2b4 c6fa92cd99c5c301635%7C0%7C0%7C637653943958819210%7CUnknown%7CTWFpbGZsb3d8eyJ WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata =QwtROeuQVK8nWtprtRVZJnzXM2%2FBgX1ZZspl6dsxBFE%3D&reserved=0> ][tf-m-tests patch <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr ustedfirmware.org%2Fc%2FTF-M%2Ftf-m-tests%2F%2B%2F10556&data=04%7C01%7Candre y.butok%40nxp.com%7Ce6deb39c9db74755362008d966e231b0%7C686ea1d3bc2b4c6fa92cd 99c5c301635%7C0%7C0%7C637653943958819210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4 wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=IYzd75F NoPwLLzoHqvpNJrn4fAaHTeOYzTujFWJDPTQ%3D&reserved=0> ] More patch sets for decoupling are under review as well. * Decouple tf-m-tests secure log from non-secure log. Switch tf-m-tests secure log to TF-M SP log. [TF-M patch <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr ustedfirmware.org%2Fc%2FTF-M%2Ftrusted-firmware-m%2F%2B%2F11153&data=04%7C01 %7Candrey.butok%40nxp.com%7Ce6deb39c9db74755362008d966e231b0%7C686ea1d3bc2b4 c6fa92cd99c5c301635%7C0%7C0%7C637653943958829167%7CUnknown%7CTWFpbGZsb3d8eyJ WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata =27x4o2UrAFCFMFx3fC7ebiv0EAsBvOEtY%2BqtZzc7Q6Q%3D&reserved=0> ][tf-m-tests patch <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr ustedfirmware.org%2Fc%2FTF-M%2Ftf-m-tests%2F%2B%2F11131%2F3&data=04%7C01%7Ca ndrey.butok%40nxp.com%7Ce6deb39c9db74755362008d966e231b0%7C686ea1d3bc2b4c6fa 92cd99c5c301635%7C0%7C0%7C637653943958829167%7CUnknown%7CTWFpbGZsb3d8eyJWIjo iMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xT5 oks2R0hXyCorWsfkytx%2FCidUF8%2Bv6jMBAFxrgf2g%3D&reserved=0> ] * Trigger secure regression tests in TF-M SPE in IPC model, to simplify multi-core development/tests [TF-M patch <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr ustedfirmware.org%2Fc%2FTF-M%2Ftrusted-firmware-m%2F%2B%2F11181&data=04%7C01 %7Candrey.butok%40nxp.com%7Ce6deb39c9db74755362008d966e231b0%7C686ea1d3bc2b4 c6fa92cd99c5c301635%7C0%7C0%7C637653943958839123%7CUnknown%7CTWFpbGZsb3d8eyJ WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata =tMKKb6FHOh1pBZg62QKHBUCXaAXmv8o%2F%2Bwabe2XXOnc%3D&reserved=0> ][tf-m-tests patch <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.tr ustedfirmware.org%2Fc%2FTF-M%2Ftf-m-tests%2F%2B%2F11182&data=04%7C01%7Candre y.butok%40nxp.com%7Ce6deb39c9db74755362008d966e231b0%7C686ea1d3bc2b4c6fa92cd 99c5c301635%7C0%7C0%7C637653943958839123%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4 wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=j6Hf2wa 6wKm8LphtLfo8SK8kkhnazAJ%2F5RrN2eUhFIc%3D&reserved=0> ] I'd appreciate it if you can take a look at the patch sets above. Any suggestion or comment is welcome. If you have any specific requirement or suggestion of tf-m-tests enhancement, please feel free to contact Jianliang and me. Thanks in advance. Best regards, Hu Ziji

4 years, 7 months

2
3
0 0

[RFC] Decoupling tf-m-tests from TF-M

by David Hu

Hi all, As you may know, Jianliang and I are working to better decouple tf-m-tests from trusted-firmware-m repo. The purpose of the decoupling enhancement includes: * Making it more easier to integrate TF-M and port tf-m-tests * Making it more easier to develop TF-M tests, to minimize the changes to TF-M source code or build system. * Making it more flexible to re-structure tf-m-tests and minimize the impact to TF-M Previously Jianliang has decouple test case control and enable users to select single NS/S regression test case in build and test. Currently we are focusing on decoupling tf-m-tests specific config setting from TF-M. So far we have proposed the following major changes: * Decouple tf-m-tests specific config setting from trusted-firmware-m. [TF-M patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11167>][tf-m-tests patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11169/1>] * Move tf-m-tests specific configs to tf-m-tests repo from trusted-firmware-m [TF-M patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/10647>][tf-m-tests patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/10556>] More patch sets for decoupling are under review as well. * Decouple tf-m-tests secure log from non-secure log. Switch tf-m-tests secure log to TF-M SP log. [TF-M patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11153>][tf-m-tests patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11131/3>] * Trigger secure regression tests in TF-M SPE in IPC model, to simplify multi-core development/tests [TF-M patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11181>][tf-m-tests patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/11182>] I'd appreciate it if you can take a look at the patch sets above. Any suggestion or comment is welcome. If you have any specific requirement or suggestion of tf-m-tests enhancement, please feel free to contact Jianliang and me. Thanks in advance. Best regards, Hu Ziji

4 years, 7 months

1
0
0 0

[RFC] Changing initialization Stack from PSP to MSP

by Kevin Peng

Hi dear platform maintainers, I'd like to draw your attention on this patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11165>. It changes the initialization stack from PSP to MSP. Would you please check if this change breaks your platform? Hi Thomas@IAR, would you please check the changes for IAR? Thanks. For the details of the change, please refer to the patch. Best Regards, Kevin

4 years, 7 months

1
0
0 0

Re: [TF-M] Firmware update API - MCUboot update

by Tamas Ban

Hi Suresh, I think still there is some misunderstanding here about the role of MCUboot in the update process. I try to clarify it: * MCUboot is the *bootloader* in the system, it does not care how the new images are getting installed on the device. * MCUboot defines a static allocation of the flash. There are the primary slot where the active runtime images are stored and executed from there (if upgrade startegy is XIP) and there are the secondary slot where the candidate image is written by the update client, which his part of the runtime firmware. * MCUboot is not involved at all in the process when new image is downloaded from the remote server and written to the flash (to secondary slot). * MCUboot jobs to recognize that there is a new image (magic value is set at the end of secondary slot), validates it (hash + signature) and move it (if valid) to the primary slot to make it executable (because image is XIP and linked to the address space of the primary slot) * When moving is done just jumps to the reset handler of the new image. TF-M expose a standard FWU API, which can be used by any cloud client: * FWU partition in the secure side is responsible to write the new image to the flash * Because TF-M relies on MCUBoot as a bootloader therefore the image must be placed to the right place in the flash (secondary slot) and some MCUboot specific flags must be set (magic value to indicate new image existence). Therefore in the FWU secure partition there is a MCUboot shim layer to handle these bootloader specific task * However, MCUBoot can replaced by any bootloader if one wants and then the shim layer also can be replaced to do other bootloader specific things. * In this architecture update client is responsible to download the image from the remote server and the FWU partition is responsible to write it to the right location. An implementer can choose: * Implement the FWU API on the non-secure side * Do not use FWU API, just writes the image to the right flash location and set certain flags in the flash that allows MCUboot to find the image * Replace MCUboot with custom bootloader if he wants I hope this helps! The call path in the previous mail was incorrect. The correct call path is: Update client application | | Function call V FWU API | | TF-M psa_call() etc. V FWU Partition | | Function call V MCUBoot Shim Layer | | Function call V MCUBoot user API ========================== RESTART ====================== MCUboot engine parse flash, validate new image, if there is any, and move it around to the primary slot | | V Function call, never returns Reset_Handler of new image BR, Tamas From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Suresh Marisetty via TF-M Sent: 2021. május 25., kedd 16:16 To: Andrew Thoelke <Andrew.Thoelke(a)arm.com>; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Firmware update API - MCUboot update Hi Andrew, I am thinking of two paths for the update client application: one through MCUBoot and another direct to the FWU interface. MCUBoot path is for legacy application compatibility purpose. Longer term, I am wondering if MCUBoot is needed. In embedded there is always a challenge to optimize the code size as space in storage is limited and any optimization to remove redundancies will help. Update client application | | Function call V V MCUBoot user API | Shim layer | | | | Function call | V | FWU API <------------| | | TF-M psa_call() etc. V FWU Partition | | Function call V MCUBoot user API MCUBoot engine MCUBoot image size is around 60K and thanks Suresh Marisetty Infineon Semiconductor Corporation From: Andrew Thoelke <Andrew.Thoelke(a)arm.com<mailto:Andrew.Thoelke@arm.com>> Sent: Tuesday, May 25, 2021 1:39 AM To: Marisetty Suresh (CYSC CSS ICW SW SSE) <Suresh.Marisetty(a)infineon.com<mailto:Suresh.Marisetty@infineon.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: Firmware update API - MCUboot update Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe<https://goto.infineon.com/SocialEngineering>. Hi Suresh, > I am of the belief that MCUboot will be a very thin shim layer over the FWU API to provide the compatibility interface to legacy software and most of the work that was done earlier in MCUboot is pushed down into the FWU partition. Are you suggesting that the software stack might look like this: Update client application | | Function call V MCUBoot user API Shim layer | | Function call V FWU API | | TF-M psa_call() etc. V FWU Partition | | Function call V MCUBoot user API MCUBoot engine This looks like it has one more layer than it needs, as either: 1. The Update client application could Talk directly to the FWU API, or 2. The first MCUBoot user API could interact with an MCUBoot update partition (RoT Service), without having to tunnel the MCUBoot API over the FWU API. The latter might not be straightforward - I am not sure that anyone has reviewed the two APIs for this purpose. Are you only considering this software stack for a system where touching the update client application source code is not possible (needed for option #1 above)? - and you also cannot introduce a custom MCUBoot RoT Service partition (option #2 above) so you want to reuse TF-M's existing FWU API and partition? Regards, Andrew From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Suresh Marisetty via TF-M Sent: 25 May 2021 02:37 To: Sherry Zhang <Sherry.Zhang2(a)arm.com<mailto:Sherry.Zhang2@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] Firmware update API - MCUboot update Hi Sherry, Thanks for the info. Wondering if there is some documentation or powerpoint explaining how the MCUBoot is changed to accommodate the FWU API. Details that would help: 1. How the MCUboot works without the FWU API - natively 2. How the MCUBoot needs to be modified to leverage from FWU API 3. What components are retained in MCUBoot ex: image format, signing, metadata, tools I am of the belief that MCUboot will be a very thin shim layer over the FWU API to provide the compatibility interface to legacy software and most of the work that was done earlier in MCUboot is pushed down into the FWU partition. The other way to look at it is: If somebody wants to replace MCUboot with a simple BL to integrate it tightly into TFM, what would that look like? thanks Suresh Marisetty Infineon Semiconductor Corporation From: Sherry Zhang <Sherry.Zhang2(a)arm.com<mailto:Sherry.Zhang2@arm.com>> Sent: Thursday, May 13, 2021 7:51 PM To: Marisetty Suresh (CYSC CSS ICW SW SSE) <Suresh.Marisetty(a)infineon.com<mailto:Suresh.Marisetty@infineon.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: Firmware update API - MCUboot update Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe<https://goto.infineon.com/SocialEngineering>. Hi Suresh, The MCUboot update functionality is about validating the existing images on the device which is different from that of the firmware update service which follows mostly with the PSA Firmware Update API spec<https://developer.arm.com/documentation/ihi0093/latest/>. We designed a shim layer between the firmware update partition and bootloader. A specific bootloader can be ported into the firmware update partition via that shim layer. Please refer to the firmware update service document<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/techn…>. In the MCUboot based shim layer implementation, it calls some user/public APIs provided by MCUboot to achieve its functionality. For example, the Firmware Update API spec describes that psa_fwu_install() API should validate the image or defer the validation to a system reboot. In the MCUboot shim layer implementation, it calls the boot_write_magic() API to mark the image as a candidate image for MCUboot and defers the image validation to a system reboot. Please refer to this link<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/secure_fw/…>. Can you please provide more specific suggestion or questions? Regards, Sherry Zhang From: Suresh.Marisetty(a)infineon.com<mailto:Suresh.Marisetty@infineon.com> <Suresh.Marisetty(a)infineon.com<mailto:Suresh.Marisetty@infineon.com>> Sent: Thursday, May 13, 2021 11:40 PM To: Sherry Zhang <Sherry.Zhang2(a)arm.com<mailto:Sherry.Zhang2@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: Firmware update API - MCUboot update Hi Sherry, Please take a closer look at the MCUboot and TFM might want to have a clear position/distinction between these two and how to transition from MCUboot update to this mechanism or it could be that they complement each other. thanks Suresh Marisetty Infineon Semiconductor Corporation From: Sherry Zhang <Sherry.Zhang2(a)arm.com<mailto:Sherry.Zhang2@arm.com>> Sent: Wednesday, May 12, 2021 8:55 PM To: Marisetty Suresh (CYSC CSS ICW SW SSE) <Suresh.Marisetty(a)infineon.com<mailto:Suresh.Marisetty@infineon.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: Firmware update API - MCUboot update Caution: This e-mail originated outside Infineon Technologies. Do not click on links or open attachments unless you validate it is safe<https://goto.infineon.com/SocialEngineering>. Hi Suresh, The firmware update service APIs are for updating the firmware. The functionalities of these APIs includes loading the image into its target device(flash), verifying the image and installing it and so on. The user can call the these APIs to achieve update images. For example, in the integration of TF-M and the FreeRTOS OTA<https://github.com/Linaro/amazon-freertos/blob/tfm-fwu/libraries/abstractio…>, the OTA agent calls the firmware update service APIs to achieve an image update remotely. I guess that the "MCUboot update services" you mentioned refers to the functionality of MCUboot which acts as a bootloader. As a bootloader, it can verify the image which already exists on the device and chose the right image to start up. But it cannot, for example, load the image into device or control the image update process. The firmware update partition calls some user APIs provided by MCUboot to cooperate with it. You can refer to https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/techn…. Regards, Sherry Zhang From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Suresh Marisetty via TF-M Sent: Thursday, May 13, 2021 11:09 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] Firmware update API - MCUboot update Hi, I would like to see if there is any guidance/documentation on how to coordinate between the firmware update services API with that of MCUboot. Does the use of this API make the MCUboot update services redundant? thanks Suresh Marisetty Infineon Semiconductor Corporation Lead Member of Technical Staff CYSC CSS ICW SW SSE Mobile: +5103863997 Suresh.Marisetty(a)infineon.com<mailto:Suresh.Marisetty@infineon.com>

4 years, 7 months

2
4
0 0

Re: [TF-M] Out-of-tree secure partition build support

by David Hu

Hi all, Out-of-tree secure partition build is enabled in TF-M. I'd appreciate it if you are interested to try it in your daily development. Any feedback is welcome! Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Thursday, August 12, 2021 11:54 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Out-of-tree secure partition build support Hi all, Can I ask you to review the following patch set to enable out-of-tree secure partition build in TF-M? https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/10562/ The purpose is to enable developers to develop their own secure partitions outside TF-M repo. Developers can maintain their own code and repos, independently. Developers can pass their out-of-tree secure partition paths via TF-M command line, to build out-of-tree partitions with TF-M together. For more details, please check the updated document: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/10696 Suggestions and comments are welcome! Best regards, Hu Ziji

4 years, 7 months

1
0
0 0

Test configurations refinements

by Jianliang Shen

Hi all. I have introduced the topic of test configurations refinements in the tech forum on August 5. With this new feature, you can build single test case to decrease the image size and the time to wait irrelevant test cases running when debugging. You can use all the 22 new flags in test repo: TEST_NS TEST_S TEST_NS_ATTESTATION TEST_NS_AUDIT TEST_NS_CRYPTO TEST_NS_ITS TEST_NS_PS TEST_NS_PLATFORM TEST_NS_FWU TEST_NS_IPC TEST_NS_CORE TEST_NS_QCBOR TEST_NS_T_COSE TEST_NS_MULTI_CORE TEST_NS_SLIH_IRQ TEST_NS_FLIH_IRQ TEST_S_ATTESTATION TEST_S_AUDIT TEST_S_CRYPTO TEST_S_ITS TEST_S_PS TEST_S_PLATFORM TEST_S_FWU TEST_S_IPC You can easily use the command below to start single test like NS attestation test case: cmake -S . -B cmake_build -DTFM_PLATFORM=arm/mps2/an521 \ -DTFM_TOOLCHAIN_FILE=toolchain_GNUARM.cmake \ -DCMAKE_BUILD_TYPE=Release \ -DTFM_PSA_API=ON \ -DTEST_NS_ATTESTATION=ON Meanwhile, you may receive the warning messages when your test inputs are not supported on the platform. Here are the patches about this change, any suggestions or improvements are welcome in code review. l 10767: Build: Control single test without TEST_S/TEST_NS [TF-M repo] https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/10767 l 10768: Build: Control single test without TEST_S/TEST_NS [Test repo] | https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/10768 Best Regards Jianliang Shen

4 years, 7 months

1
2
0 0

Re: [TF-M] Technical Forum call - Aug 19

by Kevin Peng

Hi Anton, Did you missed my topic below - brief update on the interrupt status in TF-M and an introduction on how to use/enable it Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Wednesday, August 18, 2021 11:13 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Technical Forum call - Aug 19 The agenda for the forum: 1. "Of out-of-tree Secure Partition build" by David Hu, 2. AOB See you, Anton From: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Sent: Wednesday, August 18, 2021 2:30 AM To: Anton Komlev <Anton.Komlev(a)arm.com<mailto:Anton.Komlev@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: Technical Forum call - Aug 19 Hi Anton, I'd like to introduce the proposal of out-of-tree Secure Partition build. It may take 15 ~ 20 mins. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Kevin Peng via TF-M Sent: Tuesday, August 17, 2021 5:49 PM To: Anton Komlev <Anton.Komlev(a)arm.com<mailto:Anton.Komlev@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] Technical Forum call - Aug 19 Hi Anton, I'd like to give a brief update on the interrupt status in TF-M and an introduction on how to use/enable it. Would take ~20 min. Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Anton Komlev via TF-M Sent: Tuesday, August 17, 2021 5:26 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] Technical Forum call - Aug 19 Hi, The next Technical Forum is planned on Thursday, Aug 19 at 7:00-8:00 UTC (Asia 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

4 years, 7 months

2
1
0 0

[Request Platform Support] Abstracted MMIO HAL

by Ken Liu

Hi everyone, The existing HAL interface for isolation hardware is not unified, we have to call several interfaces to setup isolation boundaries. Hence, a deeper abstracted interface are provided. Here are the details: - It assumes the hardware resources usages are decided by system designer. Hence there are couple of listed hardware data in the platform code, now most of them are defined in C sources. - When a partition is referencing peripheral (represented as MMIO in FFM), the manifest tooling would link specified resources with the data defined in platform. Now it is using a naming pattern, to let the partition found the resources defined above (now it uses linker to do this). - A HAL API 'tfm_hal_bind_partition' is called when a partition runtime structure is created. This API tells partition info to platform, let platform return an encoded 'p_boundaries' for SPM binding partition with platform. - When boundaries related operations happen in future, SPM would delivery this 'p_boundaries' back to platform, let platform perform boundary setup and check, such as boundary switch or memory check. SPM won't care about the hardware specific settings any more, such as privilged, non-secure/secure and how many MMIO the partition claimed, even the MPU/MPC/PPC things. - Resources defined in platform sources but not referenced would be stripped by toolchain flag. Resources not defined but referenced by partition would generate a linker error, as symbol can't be resolved. We created a patch to showcase the usage on AN521: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11036 This patch applies a simple encoding for all isolation levels. You can check how the p_boundaries is used under different isolation levels. Platform can use other encoding mechanism if applicable. Now come to the request: Please review this patch, and port similar HAL API into your platform. We are maintaining the default platforms such as AN521, AN519 and MUSCA_B1, but it need so much effort on port to all the platforms. Current CI cannot pass on this patch (as it contains modification for one platform only), our first goal is to let CI pass build on all checked platforms, and then please platform owner ensures it works on your platform. Any feedbacks are welcome. Thank you very much! /Ken

4 years, 7 months

1
0
0 0

Re: [TF-M] Technical Forum call - Aug 19

by David Hu

Hi Anton, I'd like to introduce the proposal of out-of-tree Secure Partition build. It may take 15 ~ 20 mins. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M Sent: Tuesday, August 17, 2021 5:49 PM To: Anton Komlev <Anton.Komlev(a)arm.com>; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Technical Forum call - Aug 19 Hi Anton, I'd like to give a brief update on the interrupt status in TF-M and an introduction on how to use/enable it. Would take ~20 min. Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Anton Komlev via TF-M Sent: Tuesday, August 17, 2021 5:26 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] Technical Forum call - Aug 19 Hi, The next Technical Forum is planned on Thursday, Aug 19 at 7:00-8:00 UTC (Asia 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

4 years, 7 months

2
1
0 0

Re: [TF-M] Technical Forum call - Aug 19

by Kevin Peng

Hi Anton, I'd like to give a brief update on the interrupt status in TF-M and an introduction on how to use/enable it. Would take ~20 min. Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Tuesday, August 17, 2021 5:26 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - Aug 19 Hi, The next Technical Forum is planned on Thursday, Aug 19 at 7:00-8:00 UTC (Asia 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

4 years, 7 months

1
0
0 0

Technical Forum call - Aug 19

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, Aug 19 at 7:00-8:00 UTC (Asia 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

4 years, 7 months

1
0
0 0

Re: [TF-M] [Question] FIH usage in platforms

by David Hu

Hi Ken, “double-check every return value of sub-functions, this is really a burden when under developing” That’s exactly why FIH can help mitigate physical attacks. It adds redundant checks and increases the complexity in code to make it difficult for attackers. It of course also increase develop efforts and it is expected for physical attack mitigation. Regarding tight schedule, it can be workaround by splitting the HAL API definitions with and without FIH enabled respectively. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: Thursday, August 12, 2021 4:54 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] [Question] FIH usage in platforms Thanks, then we can do some planning and make the FIH feature online again before the deadline. I do agree FIH needs an update. There would be reasons for HAL to change its implementation or prototype; and the existing FIH needs another copy of implementation, change the prototype a bit, and double-check every return value of sub-functions, this is really a burden when under developing: We first need to ensure the non-FIH version work, get reviewed; and then prepare the FIH version, get reviewed again. And, the platform owner may be afraid of changing the HAL implementation, as it is risky to do that. I’d suggest enhancing the solution that: - Doing measurement without changing HAL API prototype. As the bandwidth is always a problem, so I have to prioritize the designs. Let’s see if we can get help from people. Otherwise, I will allocate some effort after HAL update is done. This means, there would be a couple of HAL updates with no FIH support recently, and FIH version comes later. Any volunteer is welcome. /Ken From: Michel JAOUEN <michel.jaouen(a)st.com<mailto:michel.jaouen@st.com>> Sent: Thursday, August 12, 2021 4:39 PM To: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>>; Ken Liu <Ken.Liu(a)arm.com<mailto:Ken.Liu@arm.com>> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: RE: [Question] FIH usage in platforms Hello, Next platform with FIH enabled is foreseen to be in V1.5.0 with FIH enabled (the pull request without FIH enabled is expected in september) FIH support is planned on later pull request. So FIH recovering needs to be done at least 3 weeks before V1.5.0 code freeze, to let the time to do adaptation/test /fix on this new platform. Best Regards Michel ST Restricted From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of David Hu via TF-M Sent: jeudi 12 août 2021 10:34 To: Ken Liu <Ken.Liu(a)arm.com<mailto:Ken.Liu@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] [Question] FIH usage in platforms Hi Ken, Imho, it can be more reasonable to improve HAL and FIH API together, compared to removing existing security protection. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: Thursday, August 12, 2021 4:26 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] [Question] FIH usage in platforms Hi Michel, Is there a rough timeline for the next stm platform? I can estimate if we got time to update or add it back. Besides that, curious if ST got test environments for FIH? If there are some then at least we have a method to evaluate the FIH effect. BR. /Ken From: Michel JAOUEN <michel.jaouen(a)st.com<mailto:michel.jaouen@st.com>> Sent: Thursday, August 12, 2021 4:21 PM To: Ken Liu <Ken.Liu(a)arm.com<mailto:Ken.Liu@arm.com>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: RE: [Question] FIH usage in platforms Hello, Regarding FIH feature, for stm next platform I consider FIH as key for Faul injection Mitigation, so the FIH is enabled for the next stm platform. Even if a platform gets certified without this FIH feature, other mitigations at platform level have been set to get certified. The benefits of FIH is to make the mitigation available for all platform, so I consider that maintaining it during development is important. Best regards Michel ST Restricted From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: mercredi 11 août 2021 07:24 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] [Question] FIH usage in platforms Hi David, This mail is seeking evidence about how FIH is effectively working. As the latest L3 certified device is still using v1.0-RC2, where the FIH is not supported in that codebase. I assumed a pre-condition when “recovering back”: if FIH still can prove its importance. The FIH has to be enhanced before recovering back. FIH is a serious hardware feature so what software can do is limited. Delay and Double-check protection unit is the two easiest way can be applied. Other behaviors, as we can see, affect the development much, which makes it more proper to be done in toolchain instead of programming. Compare with this complex but less used mechanism, we have prioritized features to be done. That is the reason why we need to do the feature development first instead of solving the development difficulty at the current stage. Meanwhile, anyone proposing a better FIH mechanism is welcome – that would make the feature development and difficulty solving in parallel. BR. /Ken From: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Sent: Wednesday, August 11, 2021 11:53 AM To: Ken Liu <Ken.Liu(a)arm.com<mailto:Ken.Liu@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: [Question] FIH usage in platforms Hi Ken, Based on your idea, several fundamental countermeasures against physical attacks will be removed. * Double checking return value * Execution flow counters * Structured variables with initial failure values Mitigation to physical attacks is required in PSA Level 3 certify. It is crucial for TF-M to provide reasonable physical attack mitigations. Please provide proper justifications to prove that removal of those countermeasures above won’t weaken existing protection against physical attacks. On the other hand, even if those countermeasures above are removed now, it will still affect the HAL updates when they are “recovered back”. So why not solve the development difficulty at this moment? Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: Monday, August 9, 2021 10:18 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] [Question] FIH usage in platforms Hi, Is there anyone enables FIH when developing or releasing? Background: We got a couple of HAL updates during feature development and found FIH affects the development progress much, as we need to provide two sets of prototypes and implementation for involved functions, this doubles the efforts on debugging or coding. So a draft idea in my mind is to shut down part of the functionalities during this update stage and recover them back if FIH still can prove its importance later. These functionalities are KEPT during the update stage: - FIH delay, which makes it harder to find the exact time point. - Protection unit validation, ensures the protection unit is initialized as expected. Please provide your feedback about the usage and the idea. For platforms that are applying this feature, we need to find out a trade-off way. Thanks. /Ken

4 years, 7 months

2
1
0 0

Re: [TF-M] [Question] FIH usage in platforms

by Michel JAOUEN

Hello, Next platform with FIH enabled is foreseen to be in V1.5.0 with FIH enabled (the pull request without FIH enabled is expected in september) FIH support is planned on later pull request. So FIH recovering needs to be done at least 3 weeks before V1.5.0 code freeze, to let the time to do adaptation/test /fix on this new platform. Best Regards Michel ST Restricted From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: jeudi 12 août 2021 10:34 To: Ken Liu <Ken.Liu(a)arm.com>; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] [Question] FIH usage in platforms Hi Ken, Imho, it can be more reasonable to improve HAL and FIH API together, compared to removing existing security protection. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: Thursday, August 12, 2021 4:26 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] [Question] FIH usage in platforms Hi Michel, Is there a rough timeline for the next stm platform? I can estimate if we got time to update or add it back. Besides that, curious if ST got test environments for FIH? If there are some then at least we have a method to evaluate the FIH effect. BR. /Ken From: Michel JAOUEN <michel.jaouen(a)st.com<mailto:michel.jaouen@st.com>> Sent: Thursday, August 12, 2021 4:21 PM To: Ken Liu <Ken.Liu(a)arm.com<mailto:Ken.Liu@arm.com>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: RE: [Question] FIH usage in platforms Hello, Regarding FIH feature, for stm next platform I consider FIH as key for Faul injection Mitigation, so the FIH is enabled for the next stm platform. Even if a platform gets certified without this FIH feature, other mitigations at platform level have been set to get certified. The benefits of FIH is to make the mitigation available for all platform, so I consider that maintaining it during development is important. Best regards Michel ST Restricted From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: mercredi 11 août 2021 07:24 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] [Question] FIH usage in platforms Hi David, This mail is seeking evidence about how FIH is effectively working. As the latest L3 certified device is still using v1.0-RC2, where the FIH is not supported in that codebase. I assumed a pre-condition when "recovering back": if FIH still can prove its importance. The FIH has to be enhanced before recovering back. FIH is a serious hardware feature so what software can do is limited. Delay and Double-check protection unit is the two easiest way can be applied. Other behaviors, as we can see, affect the development much, which makes it more proper to be done in toolchain instead of programming. Compare with this complex but less used mechanism, we have prioritized features to be done. That is the reason why we need to do the feature development first instead of solving the development difficulty at the current stage. Meanwhile, anyone proposing a better FIH mechanism is welcome - that would make the feature development and difficulty solving in parallel. BR. /Ken From: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Sent: Wednesday, August 11, 2021 11:53 AM To: Ken Liu <Ken.Liu(a)arm.com<mailto:Ken.Liu@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: [Question] FIH usage in platforms Hi Ken, Based on your idea, several fundamental countermeasures against physical attacks will be removed. * Double checking return value * Execution flow counters * Structured variables with initial failure values Mitigation to physical attacks is required in PSA Level 3 certify. It is crucial for TF-M to provide reasonable physical attack mitigations. Please provide proper justifications to prove that removal of those countermeasures above won't weaken existing protection against physical attacks. On the other hand, even if those countermeasures above are removed now, it will still affect the HAL updates when they are "recovered back". So why not solve the development difficulty at this moment? Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: Monday, August 9, 2021 10:18 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] [Question] FIH usage in platforms Hi, Is there anyone enables FIH when developing or releasing? Background: We got a couple of HAL updates during feature development and found FIH affects the development progress much, as we need to provide two sets of prototypes and implementation for involved functions, this doubles the efforts on debugging or coding. So a draft idea in my mind is to shut down part of the functionalities during this update stage and recover them back if FIH still can prove its importance later. These functionalities are KEPT during the update stage: - FIH delay, which makes it harder to find the exact time point. - Protection unit validation, ensures the protection unit is initialized as expected. Please provide your feedback about the usage and the idea. For platforms that are applying this feature, we need to find out a trade-off way. Thanks. /Ken

4 years, 7 months

2
1
0 0

Re: [TF-M] [Question] FIH usage in platforms

by David Hu

Hi Ken, Imho, it can be more reasonable to improve HAL and FIH API together, compared to removing existing security protection. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: Thursday, August 12, 2021 4:26 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] [Question] FIH usage in platforms Hi Michel, Is there a rough timeline for the next stm platform? I can estimate if we got time to update or add it back. Besides that, curious if ST got test environments for FIH? If there are some then at least we have a method to evaluate the FIH effect. BR. /Ken From: Michel JAOUEN <michel.jaouen(a)st.com<mailto:michel.jaouen@st.com>> Sent: Thursday, August 12, 2021 4:21 PM To: Ken Liu <Ken.Liu(a)arm.com<mailto:Ken.Liu@arm.com>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: RE: [Question] FIH usage in platforms Hello, Regarding FIH feature, for stm next platform I consider FIH as key for Faul injection Mitigation, so the FIH is enabled for the next stm platform. Even if a platform gets certified without this FIH feature, other mitigations at platform level have been set to get certified. The benefits of FIH is to make the mitigation available for all platform, so I consider that maintaining it during development is important. Best regards Michel ST Restricted From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: mercredi 11 août 2021 07:24 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] [Question] FIH usage in platforms Hi David, This mail is seeking evidence about how FIH is effectively working. As the latest L3 certified device is still using v1.0-RC2, where the FIH is not supported in that codebase. I assumed a pre-condition when "recovering back": if FIH still can prove its importance. The FIH has to be enhanced before recovering back. FIH is a serious hardware feature so what software can do is limited. Delay and Double-check protection unit is the two easiest way can be applied. Other behaviors, as we can see, affect the development much, which makes it more proper to be done in toolchain instead of programming. Compare with this complex but less used mechanism, we have prioritized features to be done. That is the reason why we need to do the feature development first instead of solving the development difficulty at the current stage. Meanwhile, anyone proposing a better FIH mechanism is welcome - that would make the feature development and difficulty solving in parallel. BR. /Ken From: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Sent: Wednesday, August 11, 2021 11:53 AM To: Ken Liu <Ken.Liu(a)arm.com<mailto:Ken.Liu@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: [Question] FIH usage in platforms Hi Ken, Based on your idea, several fundamental countermeasures against physical attacks will be removed. * Double checking return value * Execution flow counters * Structured variables with initial failure values Mitigation to physical attacks is required in PSA Level 3 certify. It is crucial for TF-M to provide reasonable physical attack mitigations. Please provide proper justifications to prove that removal of those countermeasures above won't weaken existing protection against physical attacks. On the other hand, even if those countermeasures above are removed now, it will still affect the HAL updates when they are "recovered back". So why not solve the development difficulty at this moment? Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: Monday, August 9, 2021 10:18 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] [Question] FIH usage in platforms Hi, Is there anyone enables FIH when developing or releasing? Background: We got a couple of HAL updates during feature development and found FIH affects the development progress much, as we need to provide two sets of prototypes and implementation for involved functions, this doubles the efforts on debugging or coding. So a draft idea in my mind is to shut down part of the functionalities during this update stage and recover them back if FIH still can prove its importance later. These functionalities are KEPT during the update stage: - FIH delay, which makes it harder to find the exact time point. - Protection unit validation, ensures the protection unit is initialized as expected. Please provide your feedback about the usage and the idea. For platforms that are applying this feature, we need to find out a trade-off way. Thanks. /Ken

4 years, 7 months

1
0
0 0

Re: [TF-M] [Question] FIH usage in platforms

by Michel JAOUEN

Hello, Regarding FIH feature, for stm next platform I consider FIH as key for Faul injection Mitigation, so the FIH is enabled for the next stm platform. Even if a platform gets certified without this FIH feature, other mitigations at platform level have been set to get certified. The benefits of FIH is to make the mitigation available for all platform, so I consider that maintaining it during development is important. Best regards Michel ST Restricted From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: mercredi 11 août 2021 07:24 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] [Question] FIH usage in platforms Hi David, This mail is seeking evidence about how FIH is effectively working. As the latest L3 certified device is still using v1.0-RC2, where the FIH is not supported in that codebase. I assumed a pre-condition when "recovering back": if FIH still can prove its importance. The FIH has to be enhanced before recovering back. FIH is a serious hardware feature so what software can do is limited. Delay and Double-check protection unit is the two easiest way can be applied. Other behaviors, as we can see, affect the development much, which makes it more proper to be done in toolchain instead of programming. Compare with this complex but less used mechanism, we have prioritized features to be done. That is the reason why we need to do the feature development first instead of solving the development difficulty at the current stage. Meanwhile, anyone proposing a better FIH mechanism is welcome - that would make the feature development and difficulty solving in parallel. BR. /Ken From: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Sent: Wednesday, August 11, 2021 11:53 AM To: Ken Liu <Ken.Liu(a)arm.com<mailto:Ken.Liu@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: [Question] FIH usage in platforms Hi Ken, Based on your idea, several fundamental countermeasures against physical attacks will be removed. * Double checking return value * Execution flow counters * Structured variables with initial failure values Mitigation to physical attacks is required in PSA Level 3 certify. It is crucial for TF-M to provide reasonable physical attack mitigations. Please provide proper justifications to prove that removal of those countermeasures above won't weaken existing protection against physical attacks. On the other hand, even if those countermeasures above are removed now, it will still affect the HAL updates when they are "recovered back". So why not solve the development difficulty at this moment? Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: Monday, August 9, 2021 10:18 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] [Question] FIH usage in platforms Hi, Is there anyone enables FIH when developing or releasing? Background: We got a couple of HAL updates during feature development and found FIH affects the development progress much, as we need to provide two sets of prototypes and implementation for involved functions, this doubles the efforts on debugging or coding. So a draft idea in my mind is to shut down part of the functionalities during this update stage and recover them back if FIH still can prove its importance later. These functionalities are KEPT during the update stage: - FIH delay, which makes it harder to find the exact time point. - Protection unit validation, ensures the protection unit is initialized as expected. Please provide your feedback about the usage and the idea. For platforms that are applying this feature, we need to find out a trade-off way. Thanks. /Ken

4 years, 7 months

2
1
0 0

Out-of-tree secure partition build support

by David Hu

Hi all, Can I ask you to review the following patch set to enable out-of-tree secure partition build in TF-M? https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/10562/ The purpose is to enable developers to develop their own secure partitions outside TF-M repo. Developers can maintain their own code and repos, independently. Developers can pass their out-of-tree secure partition paths via TF-M command line, to build out-of-tree partitions with TF-M together. For more details, please check the updated document: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/10696 Suggestions and comments are welcome! Best regards, Hu Ziji

4 years, 7 months

1
0
0 0

Introduce a platform binding HAL API

by Mingyang Sun

Hi, A platform binding HAL API "tfm_hal_bind_partition()" is being introduced to TF-M. This API lets the platform records partition information, and applies specific settings. An encoded handle is returned to SPM, so that SPM can use the handle to decide when and how to update isolation boundaries. The "tfm_hal_update_boundaries()" API is updated accordingly. Check details in the patch. Implementation on AN521 is here: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11036 Any feedback and comments are welcome :) Thanks, MIngyang

4 years, 7 months

1
0
0 0

Re: [TF-M] TF-M v1.4.0 release started

by Sherry Zhang

Hi Jamie, 10-2020-q4-major is the latest release version. I have no idea on when the defect can be fixed in the future GCC 10 release. I think you can query that information in the tools community https://community.arm.com/developer/tools-software/tools?_ga=2.153861944.16…. Regards, Sherry Zhang From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Jamie Mccrae via TF-M Sent: Tuesday, July 27, 2021 5:50 PM To: David Hu <David.Hu(a)arm.com>; Anton Komlev <Anton.Komlev(a)arm.com>; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] TF-M v1.4.0 release started Hi David, The ARM GCC 10 build from https://developer.arm.com/tools-and-software/open-source-software/developer… does indeed seem to be the cause of the issue, tests are now all passing. Do you know on any timeframe for when an updated version of GCC 10 will be available from ARM which fixes this issue? Thanks, Jamie From: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Sent: 27 July 2021 10:09 To: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>>; Jamie Mccrae <Jamie.Mccrae(a)lairdconnect.com<mailto:Jamie.Mccrae@lairdconnect.com>>; Anton Komlev <Anton.Komlev(a)arm.com<mailto:Anton.Komlev@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: RE: TF-M v1.4.0 release started Hi Jamie, Can I ask about your toolchain in use? GNUARM 10-2020-q4-major will cause a similar issue. TF-M suggests to avoid using this version: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/getti…. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of David Hu via TF-M Sent: Tuesday, July 27, 2021 4:48 PM To: Jamie Mccrae <Jamie.Mccrae(a)lairdconnect.com<mailto:Jamie.Mccrae@lairdconnect.com>>; Anton Komlev <Anton.Komlev(a)arm.com<mailto:Anton.Komlev@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] FW: TF-M v1.4.0 release started Hi Jamie, Sorry for the trouble. According to your description, the violation error is caused by non-secure test cases. is it correct? The error message is dumped by tfm_secure_api_error_handler(). It is called multiple times in Library model routine. Can you please help narrow the step in which tfm_secure_api_error_handler() is called? Besides, do you mind trying if IPC model can work on your board? Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Jamie Mccrae via TF-M Sent: Tuesday, July 27, 2021 3:43 PM To: Anton Komlev <Anton.Komlev(a)arm.com<mailto:Anton.Komlev@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] TF-M v1.4.0 release started Hi, I have tried the RC1 and RC2 on our platform, the BL5340 (nRF5340-based), which I am testing by building with the following: cmake -DTFM_PLATFORM=lairdconnectivity/bl5340_dvk_cpuapp -GNinja -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_S=on -DTEST_NS=on -DCMAKE_BUILD_TYPE=debug -DPS_TEST_NV_COUNTERS=on .. And upon starting the non-secure tests, a security violation occurs which reboots the module. Output from secure core: Test suite 'Crypto secure interface tests (TFM_S_CRYPTO_TEST_1XXX)' has PASSED Test suite 'Initial Attestation Service secure interface tests(TFM_S_ATTEST_TEST_1XXX)' has PASSED Test suite 'Platform Service Secure interface tests(TFM_S_PLATFORM_TEST_1XXX)' has PASSED Test suite 'Audit Logging secure interface test (TFM_S_AUDIT_TEST_1XXX)' has PASSED *** End of Secure test suites *** Security violation when calling secure API [INF] Starting bootloader [INF] Primary image: magic=good, swap_type=0x1, copy_done=0x3, image_ok=0x3 [INF] Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3 [INF] Boot source: primary slot Output from non-secure core: Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA protected storage NS interface tests (TFM_NS_PS_TEST_1XXX)... > Executing 'TFM_NS_PS_TEST_1001' Description: 'Set interface' Non-Secure system starting... So something that has changed from 1.3 to 1.4 seems to have broken our platform. Thanks, Jamie From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Anton Komlev via TF-M Sent: 26 July 2021 09:50 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] TF-M v1.4.0 release started EXTERNAL EMAIL: Be careful with attachments and links. Hi, All TF-M repositories are updated with TF-Mv1.4.0-RC2 tag. The changes are minimal and shall not invalidate the tests, already done. Please use this tag for new tests and report any issues found by the end of July 30. Thanks and good luck, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Anton Komlev via TF-M Sent: Wednesday, July 21, 2021 11:25 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] TF-M v1.4.0 release started Hi, All TF-M repositories are tagged with TF-Mv1.4.0-RC1 tag. Code is frozen now for the release candidate testing. Note that changes to other repositories are still possible during that time. Please use this tag for your tests and report any issues found by the end of July 30. Thanks and good luck, Anton THIS MESSAGE, ANY ATTACHMENT(S), AND THE INFORMATION CONTAINED HEREIN MAY BE PROPRIETARY TO LAIRD CONNECTIVITY, INC. AND/OR ANOTHER PARTY, AND MAY FURTHER BE INTENDED TO BE KEPT CONFIDENTIAL. IF YOU ARE NOT THE INTENDED RECIPIENT, PLEASE DELETE THE EMAIL AND ANY ATTACHMENTS, AND IMMEDIATELY NOTIFY THE SENDER BY RETURN EMAIL. THIS MESSAGE AND ITS CONTENTS ARE THE PROPERTY OF LAIRD CONNECTIVITY, INC. AND MAY NOT BE REPRODUCED OR USED WITHOUT THE EXPRESS WRITTEN CONSENT OF LAIRD CONNECTIVITY, INC.

4 years, 7 months

3
3
0 0

Re: [TF-M] [Question] FIH usage in platforms

by David Hu

Hi Ken, Based on your idea, several fundamental countermeasures against physical attacks will be removed. * Double checking return value * Execution flow counters * Structured variables with initial failure values Mitigation to physical attacks is required in PSA Level 3 certify. It is crucial for TF-M to provide reasonable physical attack mitigations. Please provide proper justifications to prove that removal of those countermeasures above won't weaken existing protection against physical attacks. On the other hand, even if those countermeasures above are removed now, it will still affect the HAL updates when they are "recovered back". So why not solve the development difficulty at this moment? Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: Monday, August 9, 2021 10:18 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [Question] FIH usage in platforms Hi, Is there anyone enables FIH when developing or releasing? Background: We got a couple of HAL updates during feature development and found FIH affects the development progress much, as we need to provide two sets of prototypes and implementation for involved functions, this doubles the efforts on debugging or coding. So a draft idea in my mind is to shut down part of the functionalities during this update stage and recover them back if FIH still can prove its importance later. These functionalities are KEPT during the update stage: - FIH delay, which makes it harder to find the exact time point. - Protection unit validation, ensures the protection unit is initialized as expected. Please provide your feedback about the usage and the idea. For platforms that are applying this feature, we need to find out a trade-off way. Thanks. /Ken

4 years, 7 months

2
1
0 0

Applying stateless handle to built-in services

by Ken Liu

Hi, Shawn is applying stateless handle to built-in services, here are the patches for reviewing: https://review.trustedfirmware.org/q/topic:%22Apply_stateless_handle%22+(st… Only those services are really STATELESS can be applied with stateless handle. For the legacy connection-based services (supports multiple sessions), please keep using the connect/call/close based mechanism when accessing services. Thanks. /Ken

4 years, 7 months

1
0
0 0

[RFC] Move re-entrant logic into entrance instead of SPM

by Ken Liu

Hi, There are a v8.0m re-entrant detecting mechanism inside SPM: 'tfm_spm_validate_caller'. For v8.1-M, it has hardware reentrant detection so it does not need a software solution. The concept is to let SVC handler check these points to see if a reentrant is happening: * If the return address is inside of NS Agent partition. * If the LSB of LR is ZERO. * Check if stacked frame equals a standard exception frame size. This mechanism has proven its integrity, but has these shortages: * It needs an SVC, while SPM are going forward to work under thread mode. * The frame size checking is complex, we need to take care if NSPE is applying FPU or not, different configurations has different frame size. Hence I moved this mechanism into NS Agent partition, just the veneer part after SG, by checking if current PSP_S is pointing to a SEAL (We don't use stack before calling into PSA API so stack is totally clear). I did several times emulation and it looks fine. Now I need your help to review on this part, to see if there are risks on updated mechanism. https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/11003 Thanks. /Ken

4 years, 7 months

1
0
0 0

[Question] FIH usage in platforms

by Ken Liu

Hi, Is there anyone enables FIH when developing or releasing? Background: We got a couple of HAL updates during feature development and found FIH affects the development progress much, as we need to provide two sets of prototypes and implementation for involved functions, this doubles the efforts on debugging or coding. So a draft idea in my mind is to shut down part of the functionalities during this update stage and recover them back if FIH still can prove its importance later. These functionalities are KEPT during the update stage: - FIH delay, which makes it harder to find the exact time point. - Protection unit validation, ensures the protection unit is initialized as expected. Please provide your feedback about the usage and the idea. For platforms that are applying this feature, we need to find out a trade-off way. Thanks. /Ken

4 years, 7 months

1
0
0 0

Re: [TF-M] Technical Forum call - August 5

by Raef Coles

I'd also like to talk about my proposed design for the OTP HAL changes, and get some feedback about provisioning. This is probably ~30 minutes Raef ________________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Jianliang Shen via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 02 August 2021 04:08 To: Anton Komlev Cc: nd; tf-m(a)lists.trustedfirmware.org Subject: [TF-M] 回复: Technical Forum call - August 5 Hi I want to introduce my recently work to you about TF-M test configuration refinement in the tech forum on August 5th. It may take 15-20 minutes. Best Regards Jianliang Shen 发件人: Summer Qin <Summer.Qin(a)arm.com> 发送时间: 02 August 2021 10:57 收件人: Anton Komlev <Anton.Komlev(a)arm.com> 抄送: Jianliang Shen <Jianliang.Shen(a)arm.com> 主题: Re: Technical Forum call - August 5 ________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> on behalf of Anton Komlev via TF-M <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Sent: Wednesday, July 28, 2021 7:23 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] Technical Forum call - August 5 Hi, The next Technical Forum is planned on Thursday, August 5, 15:00-16:00 UTC (US 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

4 years, 7 months

2
1
0 0

Re: [TF-M] TF-M v1.4.0 release

by Anton Komlev

Hello, Soon after the release we noticed a mistake in the release notes. The mistake was fixed and the release tag updated. The small change is in documentation only so shall not cause any functional inconsistency. Sorry for the possible inconvenience and thanks for understanding, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Wednesday, August 4, 2021 11:17 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] TF-M v1.4.0 release Hello, TF-M project released v1.4.0, tagged as TF-Mv1.4.0. Please take a look into the release notes for the new features and changes: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/relea… New major features are: * Documentation restructure and enhancements. * PSA Crypto migrates to Mbed TLS v3.0.0. * First-Level Interrupt Handling (FLIH) proof of concept on AN521 and MUSCA-B1. * Firmware Update service enhancement to support image update with dependencies. * Partitions get loaded with Static Load mechanism. * Decouple NS RTOS specific implementation from NS interface. * PSA Crypto API interface updated to be based on Stateless Handle. * MCUboot updated to version 'TF-Mv1.4-integ' to support multiple images in RAM_LOAD and DIRECT_XIP upgrade strategies. * New platforms added. Thanks to everyone who directly or indirectly contributed to this milestone. Anton Komlev TF-M technical lead Arm Ltd.

4 years, 7 months

1
0
0 0

TF-M v1.4.0 release

by Anton Komlev

Hello, TF-M project released v1.4.0, tagged as TF-Mv1.4.0. Please take a look into the release notes for the new features and changes: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/relea… New major features are: * Documentation restructure and enhancements. * PSA Crypto migrates to Mbed TLS v3.0.0. * First-Level Interrupt Handling (FLIH) proof of concept on AN521 and MUSCA-B1. * Firmware Update service enhancement to support image update with dependencies. * Partitions get loaded with Static Load mechanism. * Decouple NS RTOS specific implementation from NS interface. * PSA Crypto API interface updated to be based on Stateless Handle. * MCUboot updated to version 'TF-Mv1.4-integ' to support multiple images in RAM_LOAD and DIRECT_XIP upgrade strategies. * New platforms added. Thanks to everyone who directly or indirectly contributed to this milestone. Anton Komlev TF-M technical lead Arm Ltd.

4 years, 7 months

1
0
0 0

Re: [TF-M] Calling an NSPE function from a secure partition

by Jan Hoogerbrugge

Hi, I am calling osSemaphoreAcquire from SPE and osSemaphoreRelease from a SPE ISR. It seems to work via the CMSE. One thing that worries me is the problem that I had earlier without TF-M. See this posting: https://forums.freertos.org/t/synchonisation-in-trustzone-secure-world-by-c…. FreeRTOS disabled interrupts before entering a critical section and then an interrupt in secure world occurs that makes a call to FreeRTOS via CMSE while the critical section is busy. The call to FreeRTOS causes a second thread to enter the critical section which causes data structure corruption. Can something similar happen with RTX? If so, should I then solve it in the same way as proposed in the FreeRTOS forum thread by posting a non-secure interrupt? Jan. On Mon, Aug 2, 2021 at 10:47 AM Ken Liu via TF-M <tf-m(a)lists.trustedfirmware.org> wrote: > > Hi Jan, > > This behavior is not encouraged in TF-M, as Firmware Framework does not allow such an scenario. > > But if you are working on a simple secure library with Trustzone-M you can try to use CMSE API to do that. > > Please tell us more details if you are using TF-M, sounds like you are trying to avoid blocking in the SPE. > > Thanks. > > /Ken > > > > > -----Original Message----- > From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Jan Hoogerbrugge via TF-M > Sent: Thursday, July 29, 2021 2:07 PM > To: tf-m(a)lists.trustedfirmware.org > Subject: [TF-M] Calling an NSPE function from a secure partition > > Hi, > > Is it possible/allowed to call a function in NSPE from a secure partition using the GCC Cortex M Security Extensions (CMSE)? If NSPE and SPE are on different cores then it is definitely not working but in my case they are on the same M33 core. > > If it is possible then I would like to call a semaphore P operation in the RTOS that might block. Will that work? > > Regards, > Jan. > -- > TF-M mailing list > TF-M(a)lists.trustedfirmware.org > https://lists.trustedfirmware.org/mailman/listinfo/tf-m > -- > TF-M mailing list > TF-M(a)lists.trustedfirmware.org > https://lists.trustedfirmware.org/mailman/listinfo/tf-m

4 years, 7 months

2
1
0 0

Re: [TF-M] TF-M crypto test failure

by Michel JAOUEN

Hello, I tested : -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_NS=ON -DTFM_PSA_API=ON -DTFM_SPM_LOG_LEVEL=TFM_SPM_LOG_LEVEL_DEBUG With compiler GNUARM 9.3.1 I perform the build with sha1 07c2e6868cb702 on https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git and did not provide any library path so that build process fetch all repos. The crypto test got passed. running Test Suite Crypto non-secure interface test (TFM_NS_CRYPTO_TEST_1XXX)... > Executing 'TFM_NS_CRYPTO_TEST_1001' Description: 'Non Secure Key management interface' TEST: TFM_NS_CRYPTO_TEST_1001 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1002' Description: 'Non Secure Symmetric encryption (AES-128-CBC) interface' TEST: TFM_NS_CRYPTO_TEST_1002 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1003' Description: 'Non Secure Symmetric encryption (AES-128-CFB) interface' TEST: TFM_NS_CRYPTO_TEST_1003 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1005' Description: 'Non Secure Symmetric encryption (AES-128-CTR) interface' TEST: TFM_NS_CRYPTO_TEST_1005 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1007' Description: 'Non Secure Symmetric encryption invalid cipher' TEST: TFM_NS_CRYPTO_TEST_1007 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1008' Description: 'Non Secure Symmetric encryption invalid cipher (AES-152)' TEST: TFM_NS_CRYPTO_TEST_1008 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1009' Description: 'Non Secure Symmetric encryption invalid cipher (HMAC-128-CFB)' TEST: TFM_NS_CRYPTO_TEST_1009 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1010' Description: 'Non Secure Unsupported Hash (SHA-1) interface' TEST: TFM_NS_CRYPTO_TEST_1010 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1011' Description: 'Non Secure Hash (SHA-224) interface' TEST: TFM_NS_CRYPTO_TEST_1011 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1012' Description: 'Non Secure Hash (SHA-256) interface' TEST: TFM_NS_CRYPTO_TEST_1012 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1013' Description: 'Non Secure Hash (SHA-384) interface' TEST: TFM_NS_CRYPTO_TEST_1013 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1014' Description: 'Non Secure Hash (SHA-512) interface' TEST: TFM_NS_CRYPTO_TEST_1014 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1019' Description: 'Non Secure Unsupported HMAC (SHA-1) interface' TEST: TFM_NS_CRYPTO_TEST_1019 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1020' Description: 'Non Secure HMAC (SHA-256) interface' TEST: TFM_NS_CRYPTO_TEST_1020 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1021' Description: 'Non Secure HMAC (SHA-384) interface' TEST: TFM_NS_CRYPTO_TEST_1021 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1022' Description: 'Non Secure HMAC (SHA-512) interface' TEST: TFM_NS_CRYPTO_TEST_1022 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1024' Description: 'Non Secure HMAC with long key (SHA-224) interface' TEST: TFM_NS_CRYPTO_TEST_1024 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1030' Description: 'Non Secure AEAD (AES-128-CCM) interface' TEST: TFM_NS_CRYPTO_TEST_1030 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1031' Description: 'Non Secure AEAD (AES-128-GCM) interface' TEST: TFM_NS_CRYPTO_TEST_1031 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1032' Description: 'Non Secure key policy interface' TEST: TFM_NS_CRYPTO_TEST_1032 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1033' Description: 'Non Secure key policy check permissions' TEST: TFM_NS_CRYPTO_TEST_1033 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1034' Description: 'Non Secure persistent key interface' TEST: TFM_NS_CRYPTO_TEST_1034 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1035' Description: 'Non Secure AEAD interface with truncated auth tag (AES-128-CCM-8)' TEST: TFM_NS_CRYPTO_TEST_1035 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1036' Description: 'Non Secure TLS 1.2 PRF key derivation' TEST: TFM_NS_CRYPTO_TEST_1036 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1037' Description: 'Non Secure TLS-1.2 PSK-to-MasterSecret key derivation' TEST: TFM_NS_CRYPTO_TEST_1037 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1038' Description: 'Non Secure HKDF key derivation' TEST: TFM_NS_CRYPTO_TEST_1038 - PASSED! TESTSUITE PASSED! Best regards Michel ST Restricted -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Raef Coles via TF-M Sent: mardi 3 août 2021 15:05 To: Edward Yang <EdwardYang(a)mxic.com.cn>; Summer Qin <Summer.Qin(a)arm.com>; tf-m(a)lists.trustedfirmware.org; TF-M <tf-m-bounces(a)lists.trustedfirmware.org>; nd <nd(a)arm.com> Subject: Re: [TF-M] TF-M crypto test failure It doesn't seem to happen on other platforms, I think this is only STM. One thing I didn't mention is that if you change the cmake config files, the values used in the build won't be updated as they are cached in `CmakeCache.txt`. Did you remove the entire build directory after changing the config file? If not it might still be using the old values, can you try completely removing the build dir. Apologies, I forgot to mention this in the initial request. Meanwhile I'll try to take a look at this based on the logs you've provided. Raef ________________________________________ From: Edward Yang <EdwardYang(a)mxic.com.cn> Sent: 03 August 2021 07:51 To: Raef Coles; Summer Qin; tf-m(a)lists.trustedfirmware.org; TF-M; nd Subject: Re: [TF-M] TF-M crypto test failure Hi Raef and Summer, I have set PLATFORM_DUMMY_NV_SEED = TRUE and CRYPTO_HW_ACCELERATOR=OFF within STM config.cmake file,and the test result was the same,there were 8 crypto failures. I looked into the detailed error, and I commented out the code which set key's id attribute,showned as below. then the key can be imported,but there were still AES_CBC and AES_CFB ...symmetric single-shot API errors. I am wondering whether this test result occurs on the other platforms. Running Test Suite Crypto non-secure interface test (TFM_NS_CRYPTO_TEST_1XXX)... > Executing 'TFM_NS_CRYPTO_TEST_1001' Description: 'Non Secure Key management interface' TEST: TFM_NS_CRYPTO_TEST_1001 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1002' Description: 'Non Secure Symmetric encryption (AES-128-CBC) interface' key handle:2147483616 destroy key handle:2147483616 Error encrypting with the single-shot API (Failed at /home/a/workspace1/TF-M/) TEST: TFM_NS_CRYPTO_TEST_1002 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1003' Description: 'Non Secure Symmetric encryption (AES-128-CFB) interface' key handle:2147483616 destroy key handle:2147483616 Error encrypting with the single-shot API (Failed at /home/a/workspace1/TF-M/) TEST: TFM_NS_CRYPTO_TEST_1003 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1005' Description: 'Non Secure Symmetric encryption (AES-128-CTR) interface' key handle:2147483616 destroy key handle:2147483616 Error encrypting with the single-shot API (Failed at /home/a/workspace1/TF-M/) TEST: TFM_NS_CRYPTO_TEST_1005 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1007' Description: 'Non Secure Symmetric encryption invalid cipher' TEST: TFM_NS_CRYPTO_TEST_1007 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1008' Description: 'Non Secure Symmetric encryption invalid cipher (AES-152)' TEST: TFM_NS_CRYPTO_TEST_1008 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1009' Description: 'Non Secure Symmetric encryption invalid cipher (HMAC-128-CFB)' TEST: TFM_NS_CRYPTO_TEST_1009 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1010' Description: 'Non Secure Unsupported Hash (SHA-1) interface' TEST: TFM_NS_CRYPTO_TEST_1010 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1011' Description: 'Non Secure Hash (SHA-224) interface' TEST: TFM_NS_CRYPTO_TEST_1011 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1012' Description: 'Non Secure Hash (SHA-256) interface' TEST: TFM_NS_CRYPTO_TEST_1012 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1013' Description: 'Non Secure Hash (SHA-384) interface' TEST: TFM_NS_CRYPTO_TEST_1013 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1014' Description: 'Non Secure Hash (SHA-512) interface' TEST: TFM_NS_CRYPTO_TEST_1014 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1019' Description: 'Non Secure Unsupported HMAC (SHA-1) interface' TEST: TFM_NS_CRYPTO_TEST_1019 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1020' Description: 'Non Secure HMAC (SHA-256) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf) TEST: TFM_NS_CRYPTO_TEST_1020 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1021' Description: 'Non Secure HMAC (SHA-384) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf) TEST: TFM_NS_CRYPTO_TEST_1021 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1022' Description: 'Non Secure HMAC (SHA-512) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf) TEST: TFM_NS_CRYPTO_TEST_1022 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1024' Description: 'Non Secure HMAC with long key (SHA-224) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf) TEST: TFM_NS_CRYPTO_TEST_1024 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1030' Description: 'Non Secure AEAD (AES-128-CCM) interface' TEST: TFM_NS_CRYPTO_TEST_1030 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1031' Description: 'Non Secure AEAD (AES-128-GCM) interface' TEST: TFM_NS_CRYPTO_TEST_1031 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1032' Description: 'Non Secure key policy interface' TEST: TFM_NS_CRYPTO_TEST_1032 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1033' Description: 'Non Secure key policy check permissions' TEST: TFM_NS_CRYPTO_TEST_1033 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1034' Description: 'Non Secure persistent key interface' Failed to import a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/t) TEST: TFM_NS_CRYPTO_TEST_1034 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1035' Description: 'Non Secure AEAD interface with truncated auth tag (AES-128-CCM-' TEST: TFM_NS_CRYPTO_TEST_1035 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1036' Description: 'Non Secure TLS 1.2 PRF key derivation' TEST: TFM_NS_CRYPTO_TEST_1036 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1037' Description: 'Non Secure TLS-1.2 PSK-to-MasterSecret key derivation' TEST: TFM_NS_CRYPTO_TEST_1037 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1038' Description: 'Non Secure HKDF key derivation' TEST: TFM_NS_CRYPTO_TEST_1038 - PASSED! TESTSUITE FAILED! Number of failed tests: 8 of 26 Best Regards, Poppy Wu Summer Qin via TF-M <tf-m(a)lists.trustedfirmware.org> Sent by: "TF-M" <tf-m-bounces(a)lists.trustedfirmware.org> 2021/08/03 10:52 Please respond to Summer Qin <Summer.Qin(a)arm.com> To "tf-m(a)lists.trustedfirmware.org" <tf-m(a)lists.trustedfirmware.org>, Edward Yang <EdwardYang(a)mxic.com.cn>, Raef Coles <Raef.Coles(a)arm.com> cc nd <nd(a)arm.com> Subject Re: [TF-M] TF-M crypto test failure Hi Edward, STM uses its own accelerator for crypto as the default config. Please try Raef's suggestion, but you also need to set "-DPLATFORM_DUMMY_NV_SEED = TRUE" when you set "-DCRYPTO_HW_ACCELERATOR=OFF" manually, otherwise you will see cmake error. Best Regards, Summer ________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Raef Coles via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: Monday, August 2, 2021 11:28 PM To: tf-m(a)lists.trustedfirmware.org <tf-m(a)lists.trustedfirmware.org>; Edward Yang <EdwardYang(a)mxic.com.cn> Subject: Re: [TF-M] TF-M crypto test failure Hi Edward As part of the migration to mbedtls 3.0, we had to update some of the code for the STM crypto accelerator mbedtls compatibility layer. It's possible these failures are related to those changes. Could you run the same tests with `-DCRYPTO_HW_ACCELERATOR=OFF`, and see if there are less failures in that mode? Thanks, Raef ________________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Edward Yang via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 02 August 2021 14:31 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] TF-M crypto test failure Hi experts, We tested the latest trusted-firmware-m code with tf-m-tests on stm32l562e_dk discovery board,but some crypto failures occured, The test log is showed below: [INF] Starting bootloader [INF] Swap type: none [INF] Swap type: none [INF] Bootloader chainload address offset: 0x19000 [INF] Jumping to the first image slot [Sec Thread] Secure image initializing! TF-M isolation level is: 0x00000001 Booting TFM v1.3.0 Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA internal trusted storage NS interface tests (TFM_NS_ITS_TEST_1XXX)... > Executing 'TFM_NS_ITS_TEST_1001' Description: 'Set interface' TEST: TFM_NS_ITS_TEST_1001 - PASSED! > Executing 'TFM_NS_ITS_TEST_1002' Description: 'Set interface with create flags' Note: The UID in this test has already been created with the PSA_STORAGE_FLAG_WRITE_ONCE flag in a previous test run. Wipe the storage area to run the full test. TEST: TFM_NS_ITS_TEST_1002 - PASSED! > Executing 'TFM_NS_ITS_TEST_1003' Description: 'Set interface with NULL data pointer' TEST: TFM_NS_ITS_TEST_1003 - PASSED! > Executing 'TFM_NS_ITS_TEST_1004' Description: 'Set interface with write once UID' TEST: TFM_NS_ITS_TEST_1004 - PASSED! > Executing 'TFM_NS_ITS_TEST_1005' Description: 'Get interface with valid data' TEST: TFM_NS_ITS_TEST_1005 - PASSED! > Executing 'TFM_NS_ITS_TEST_1006' Description: 'Get interface with zero data length' TEST: TFM_NS_ITS_TEST_1006 - PASSED! > Executing 'TFM_NS_ITS_TEST_1007' Description: 'Get interface with invalid UIDs' TEST: TFM_NS_ITS_TEST_1007 - PASSED! > Executing 'TFM_NS_ITS_TEST_1008' Description: 'Get interface with invalid data lengths and offsets' TEST: TFM_NS_ITS_TEST_1008 - PASSED! > Executing 'TFM_NS_ITS_TEST_1009' Description: 'Get interface with NULL data pointer' TEST: TFM_NS_ITS_TEST_1009 - PASSED! > Executing 'TFM_NS_ITS_TEST_1010' Description: 'Get info interface with write once UID' TEST: TFM_NS_ITS_TEST_1010 - PASSED! > Executing 'TFM_NS_ITS_TEST_1011' Description: 'Get info interface with valid UID' TEST: TFM_NS_ITS_TEST_1011 - PASSED! > Executing 'TFM_NS_ITS_TEST_1012' Description: 'Get info interface with invalid UIDs' TEST: TFM_NS_ITS_TEST_1012 - PASSED! > Executing 'TFM_NS_ITS_TEST_1013' Description: 'Remove interface with valid UID' TEST: TFM_NS_ITS_TEST_1013 - PASSED! > Executing 'TFM_NS_ITS_TEST_1014' Description: 'Remove interface with write once UID' TEST: TFM_NS_ITS_TEST_1014 - PASSED! > Executing 'TFM_NS_ITS_TEST_1015' Description: 'Remove interface with invalid UID' TEST: TFM_NS_ITS_TEST_1015 - PASSED! > Executing 'TFM_NS_ITS_TEST_1016' Description: 'Block compaction after remove' TEST: TFM_NS_ITS_TEST_1016 - PASSED! > Executing 'TFM_NS_ITS_TEST_1017' Description: 'Multiple partial gets' TEST: TFM_NS_ITS_TEST_1017 - PASSED! > Executing 'TFM_NS_ITS_TEST_1018' Description: 'Multiple sets to same UID from same thread' TEST: TFM_NS_ITS_TEST_1018 - PASSED! > Executing 'TFM_NS_ITS_TEST_1019' Description: 'Set, get and remove interface with different asset sizes' TEST: TFM_NS_ITS_TEST_1019 - PASSED! TESTSUITE PASSED! Running Test Suite Crypto non-secure interface test (TFM_NS_CRYPTO_TEST_1XXX)... > Executing 'TFM_NS_CRYPTO_TEST_1001' Description: 'Non Secure Key management interface' TEST: TFM_NS_CRYPTO_TEST_1001 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1002' Description: 'Non Secure Symmetric encryption (AES-128-CBC) interface' Error destroying a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:345) TEST: TFM_NS_CRYPTO_TEST_1002 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1003' Description: 'Non Secure Symmetric encryption (AES-128-CFB) interface' Error destroying a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:345) TEST: TFM_NS_CRYPTO_TEST_1003 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1005' Description: 'Non Secure Symmetric encryption (AES-128-CTR) interface' Error destroying a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:345) TEST: TFM_NS_CRYPTO_TEST_1005 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1007' Description: 'Non Secure Symmetric encryption invalid cipher' TEST: TFM_NS_CRYPTO_TEST_1007 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1008' Description: 'Non Secure Symmetric encryption invalid cipher (AES-152)' TEST: TFM_NS_CRYPTO_TEST_1008 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1009' Description: 'Non Secure Symmetric encryption invalid cipher (HMAC-128-CFB)' TEST: TFM_NS_CRYPTO_TEST_1009 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1010' Description: 'Non Secure Unsupported Hash (SHA-1) interface' TEST: TFM_NS_CRYPTO_TEST_1010 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1011' Description: 'Non Secure Hash (SHA-224) interface' TEST: TFM_NS_CRYPTO_TEST_1011 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1012' Description: 'Non Secure Hash (SHA-256) interface' TEST: TFM_NS_CRYPTO_TEST_1012 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1013' Description: 'Non Secure Hash (SHA-384) interface' TEST: TFM_NS_CRYPTO_TEST_1013 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1014' Description: 'Non Secure Hash (SHA-512) interface' TEST: TFM_NS_CRYPTO_TEST_1014 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1019' Description: 'Non Secure Unsupported HMAC (SHA-1) interface' TEST: TFM_NS_CRYPTO_TEST_1019 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1020' Description: 'Non Secure HMAC (SHA-256) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:628) TEST: TFM_NS_CRYPTO_TEST_1020 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1021' Description: 'Non Secure HMAC (SHA-384) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:628) TEST: TFM_NS_CRYPTO_TEST_1021 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1022' Description: 'Non Secure HMAC (SHA-512) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:628) TEST: TFM_NS_CRYPTO_TEST_1022 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1024' Description: 'Non Secure HMAC with long key (SHA-224) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:628) TEST: TFM_NS_CRYPTO_TEST_1024 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1030' Description: 'Non Secure AEAD (AES-128-CCM) interface' TEST: TFM_NS_CRYPTO_TEST_1030 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1031' Description: 'Non Secure AEAD (AES-128-GCM) interface' TEST: TFM_NS_CRYPTO_TEST_1031 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1032' Description: 'Non Secure key policy interface' TEST: TFM_NS_CRYPTO_TEST_1032 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1033' Description: 'Non Secure key policy check permissions' TEST: TFM_NS_CRYPTO_TEST_1033 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1034' Description: 'Non Secure persistent key interface' Failed to import a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:107) TEST: TFM_NS_CRYPTO_TEST_1034 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1035' Description: 'Non Secure AEAD interface with truncated auth tag (AES-128-CCM-8)' TEST: TFM_NS_CRYPTO_TEST_1035 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1036' Description: 'Non Secure TLS 1.2 PRF key derivation' TEST: TFM_NS_CRYPTO_TEST_1036 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1037' Description: 'Non Secure TLS-1.2 PSK-to-MasterSecret key derivation' TEST: TFM_NS_CRYPTO_TEST_1037 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1038' Description: 'Non Secure HKDF key derivation' TEST: TFM_NS_CRYPTO_TEST_1038 - PASSED! TESTSUITE FAILED! Number of failed tests: 8 of 26 .... The detailed software versions are as follows: trusted-firmware-m:commit 07c2e6868cb7027325a0b84dd4c14bf619f5dc34 tf-m-tests:commit e1a8c9fb8394b1f6ea66d2611c070915b0d4b573 mcuboot:commit 4f8091318b4026d14af9e5a7036825bff62fb612 mbedtls:commit 8df2f8e7b9c7bb9390ac74bb7bace27edca81a2b And below is the build command and procedure, root@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test# cmake .. -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_NS=ON -DTFM_PSA_API=ON -DTFM_SPM_LOG_LEVEL=TFM_SPM_LOG_LEVEL_DEBUG -- The C compiler identification is GNU 9.3.1 -- The ASM compiler identification is GNU -- Found assembler: /home/a/Tools/gcc-arm-none-eabi-9-2020-q2-update/bin/arm-none-eabi-gcc -- Found Python3: /home/a/python3.6/bin/python3.6 (found version "3.6.12") found components: Interpreter Start to generate partition files: Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/protected_storage/psa_manifest/tfm_protected_storage.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/protected_storage/auto_generated/intermedia_tfm_protected_storage.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/internal_trusted_storage/psa_manifest/tfm_internal_trusted_storage.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/intermedia_tfm_internal_trusted_storage.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/audit_logging/psa_manifest/tfm_audit_logging.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/audit_logging/auto_generated/intermedia_tfm_audit_logging.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/audit_logging/auto_generated/load_info_tfm_audit_logging.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/crypto/psa_manifest/tfm_crypto.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/crypto/auto_generated/intermedia_tfm_crypto.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/platform/psa_manifest/tfm_platform.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/platform/auto_generated/intermedia_tfm_platform.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/initial_attestation/psa_manifest/tfm_initial_attestation.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/initial_attestation/auto_generated/intermedia_tfm_initial_attestation.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_core_test/psa_manifest/tfm_ss_core_test.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_core_test/auto_generated/intermedia_tfm_ss_core_test.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_core_test_2/psa_manifest/tfm_ss_core_test_2.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_core_test_2/auto_generated/intermedia_tfm_ss_core_test_2.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_secure_client_service/psa_manifest/tfm_secure_client_service.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_secure_client_service/auto_generated/intermedia_tfm_secure_client_service.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_secure_client_service/auto_generated/load_info_tfm_secure_client_service.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ipc_service/psa_manifest/tfm_ipc_service_test.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ipc_service/auto_generated/intermedia_tfm_ipc_service_test.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ipc_client/psa_manifest/tfm_ipc_client_test.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ipc_client/auto_generated/intermedia_tfm_ipc_client_test.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ps_test_service/psa_manifest/tfm_ps_test_service.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ps_test_service/auto_generated/intermedia_tfm_ps_test_service.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_secure_client_2/psa_manifest/tfm_secure_client_2.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_secure_client_2/auto_generated/intermedia_tfm_secure_client_2.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_secure_client_2/auto_generated/load_info_tfm_secure_client_2.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/firmware_update/psa_manifest/tfm_firmware_update.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/firmware_update/auto_generated/intermedia_tfm_firmware_update.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/firmware_update/auto_generated/load_info_tfm_firmware_update.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/tfm_ffm11_partition/psa_manifest/tfm_ffm11_partition.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/intermedia_tfm_ffm11_partition.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_attest_test_service/psa_manifest/tfm_attest_test_service.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_attest_test_service/auto_generated/intermedia_tfm_attest_test_service.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_attest_test_service/auto_generated/load_info_tfm_attest_test_service.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_slih_test_service/psa_manifest/tfm_slih_test_service.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_slih_test_service/auto_generated/intermedia_tfm_slih_test_service.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_slih_test_service/auto_generated/load_info_tfm_slih_test_service.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_flih_test_service/psa_manifest/tfm_flih_test_service.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_flih_test_service/auto_generated/intermedia_tfm_flih_test_service.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_flih_test_service/auto_generated/load_info_tfm_flih_test_service.c Per-partition files done: Start to generate file from the generated list: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/spm/cmsis_func/tfm_spm_db_func.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/spm/cmsis_func/tfm_veneers.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/interface/include/tfm_veneers.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/spm/cmsis_func/tfm_secure_irq_handlers.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/spm/cmsis_psa/tfm_secure_irq_handlers_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/interface/include/psa_manifest/sid.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/interface/include/psa_manifest/pid.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/platform/ext/common/armclang/tfm_isolation_l3.sct Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/platform/ext/common/gcc/tfm_isolation_l3.ld Generation of files done -- Found PythonInterp: /home/a/python3.6/bin/python3 (found suitable version "3.6.12", minimum required is "3") -- Could NOT find Sphinx (missing: SPHINX_VERSION) CMake Warning (dev) at /home/a/Tools/cmake-3.19.6-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:426 (message): The package name passed to `find_package_handle_standard_args` (PY_M2R) does not match the name of the calling package (PythonModules). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): cmake/FindPythonModules.cmake:60 (find_package_handle_standard_args) docs/CMakeLists.txt:14 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Can not find Python module m2r (missing: PY_M2R) CMake Warning (dev) at /home/a/Tools/cmake-3.19.6-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:426 (message): The package name passed to `find_package_handle_standard_args` (PY_SPHINX-RTD-THEME) does not match the name of the calling package (PythonModules). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): cmake/FindPythonModules.cmake:60 (find_package_handle_standard_args) docs/CMakeLists.txt:14 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Can not find Python module sphinx-rtd-theme (missing: PY_SPHINX-RTD-THEME) CMake Warning (dev) at /home/a/Tools/cmake-3.19.6-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:426 (message): The package name passed to `find_package_handle_standard_args` (PY_SPHINXCONTRIB.PLANTUML) does not match the name of the calling package (PythonModules). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): cmake/FindPythonModules.cmake:60 (find_package_handle_standard_args) docs/CMakeLists.txt:14 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Can not find Python module sphinxcontrib.plantuml (missing: PY_SPHINXCONTRIB.PLANTUML) -- Found Java: /usr/bin/java (found suitable version "1.8.0.292", minimum required is "1.8") found components: Runtime -- PLANTUML_JAR_PATH variable is missing, PlantUML jar location is unknown. CMake Warning (dev) at /home/a/Tools/cmake-3.19.6-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:426 (message): The package name passed to `find_package_handle_standard_args` (Plantuml) does not match the name of the calling package (PlantUML). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): cmake/FindPlantUML.cmake:63 (find_package_handle_standard_args) docs/CMakeLists.txt:15 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Could NOT find Plantuml (missing: PLANTUML_JAR_PATH PLANTUML_VERSION) -- Found Doxygen: /usr/bin/doxygen (found suitable version "1.8.11", minimum required is "1.8.0") found components: doxygen dot -- Found LATEX: /usr/bin/latex found components: PDFLATEX -- ---------- Display crypto configuration - start -------------- -- CRYPTO_RNG_MODULE_DISABLED is set to FALSE -- CRYPTO_KEY_MODULE_DISABLED is set to FALSE -- CRYPTO_AEAD_MODULE_DISABLED is set to FALSE -- CRYPTO_MAC_MODULE_DISABLED is set to FALSE -- CRYPTO_CIPHER_MODULE_DISABLED is set to FALSE -- CRYPTO_HASH_MODULE_DISABLED is set to FALSE -- CRYPTO_KEY_DERIVATION_MODULE_DISABLED is set to FALSE -- CRYPTO_ASYM_SIGN_MODULE_DISABLED is set to FALSE -- CRYPTO_ASYM_ENCRYPT_MODULE_DISABLED is set to FALSE -- CRYPTO_ENGINE_BUF_SIZE is set to 0x2080 -- CRYPTO_CONC_OPER_NUM is set to 8 -- CRYPTO_KEY_ID_ENCODES_OWNER is set to ON -- CRYPTO_IOVEC_BUFFER_SIZE is set to 5120 -- ---------- Display crypto configuration - stop --------------- -- Performing Test C_COMPILER_SUPPORTS_WFORMAT_SIGNEDNESS -- Performing Test C_COMPILER_SUPPORTS_WFORMAT_SIGNEDNESS - Failed -- ----------- Display storage configuration - start ------------ -- PS_CREATE_FLASH_LAYOUT is set to ON -- PS_ENCRYPTION is set to ON -- PS_RAM_FS is set to OFF -- PS_ROLLBACK_PROTECTION is set to ON -- PS_VALIDATE_METADATA_FROM_FLASH is set to ON -- PS_MAX_ASSET_SIZE is set to 2048 -- PS_NUM_ASSETS is set to 10 -- PS_CRYPTO_AEAD_ALG is set to PSA_ALG_GCM -- ITS_CREATE_FLASH_LAYOUT is set to ON -- ITS_RAM_FS is set to OFF -- ITS_VALIDATE_METADATA_FROM_FLASH is set to ON -- ITS_MAX_ASSET_SIZE is set to 512 -- ITS_NUM_ASSETS is set to 10 -- ITS_BUF_SIZE is not set (defaults to ITS_MAX_ASSET_SIZE) -- ----------- Display storage configuration - stop ------------- -- Configuring done -- Generating done -- Build files have been written to: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test root@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test# make install Scanning dependencies of target tfm_generated_files [ 0%] Built target tfm_generated_files Scanning dependencies of target tfm_qcbor [ 0%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/ieee754.o [ 0%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_encode.o [ 0%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_decode.o [ 1%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/UsefulBuf.o [ 1%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/util/qcbor_util.o [ 1%] Linking C static library libtfm_qcbor.a [ 1%] Built target tfm_qcbor Scanning dependencies of target tfm_t_cose_s [ 1%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_s.dir/src/t_cose_sign1_sign.o [ 1%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_s.dir/src/t_cose_sign1_verify.o [ 1%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_s.dir/src/t_cose_util.o [ 1%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_s.dir/src/t_cose_parameters.o [ 1%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_s.dir/crypto_adapters/t_cose_psa_crypto.o [ 2%] Linking C static library libtfm_t_cose_s.a [ 2%] Built target tfm_t_cose_s Scanning dependencies of target crypto_service_crypto_hw [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/rsa_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/md5_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/stm.o [ 3%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 3%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 3%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 3%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 3%] Linking C static library libcrypto_service_crypto_hw.a [ 3%] Built target crypto_service_crypto_hw Scanning dependencies of target tfm_app_rot_partition_ipc_client [ 3%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/tfm_ipc_client_test.o [ 3%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/intermedia_tfm_ipc_client_test.o [ 3%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_client.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_service.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_lifecycle.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 6%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 6%] Linking C static library libtfm_app_rot_partition_ipc_client.a [ 6%] Built target tfm_app_rot_partition_ipc_client Scanning dependencies of target tfm_psa_rot_partition_ipc_service [ 6%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/tfm_ipc_service_test.o [ 6%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/intermedia_tfm_ipc_service_test.o [ 6%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_client.o [ 6%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_service.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_lifecycle.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/framework/test_framework.o [ 9%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/framework/test_framework_helpers.o [ 9%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/framework/test_framework_integ_test_helper.o [ 9%] Linking C static library libtfm_psa_rot_partition_ipc_service.a [ 9%] Built target tfm_psa_rot_partition_ipc_service Scanning dependencies of target tfm_psa_rot_partition_ps_test [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/tfm_ps_test_service.o [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/intermedia_tfm_ps_test_service.o [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_client.o [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_service.o [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_lifecycle.o [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 11%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 11%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 11%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 11%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 11%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 11%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 11%] Linking C static library libtfm_psa_rot_partition_ps_test.a [ 11%] Built target tfm_psa_rot_partition_ps_test Scanning dependencies of target tfm_app_rot_partition_core_test_2 [ 11%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/tfm_ss_core_test_2.o [ 11%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/intermedia_tfm_ss_core_test_2.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_client.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_service.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_lifecycle.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 14%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 14%] Linking C static library libtfm_app_rot_partition_core_test_2.a [ 14%] Built target tfm_app_rot_partition_core_test_2 Scanning dependencies of target tfm_psa_rot_partition_core_test [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/tfm_ss_core_test.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/intermedia_tfm_ss_core_test.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_client.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_service.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_lifecycle.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_helpers.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_integ_test_helper.o [ 17%] Linking C static library libtfm_psa_rot_partition_core_test.a [ 17%] Built target tfm_psa_rot_partition_core_test Scanning dependencies of target platform_s [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/system_stm32l5xx.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/spm_hal.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_hal_isolation.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/target_cfg.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/low_level_device.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc_ex.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_isolation_mpu_v8m.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_platform_system.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng_ex.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_ps.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_its.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_platform.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/uart_stdout.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_spm_logdev_peripheral.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_memory_symbols.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/attest_hal.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/nv_counters.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/crypto_keys.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_rotpk.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/psa/psa_client.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/psa/psa_service.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/psa/psa_lifecycle.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/log/tfm_log_raw.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 23%] Linking C static library libplatform_s.a [ 23%] Built target platform_s Scanning dependencies of target tfm_app_rot_partition_ffm11 [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/tfm_ffm11_partition.o [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/intermedia_tfm_ffm11_partition.o [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/interface/src/psa/psa_client.o [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/interface/src/psa/psa_service.o [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/interface/src/psa/psa_lifecycle.o [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/ns_proxy_partition/load_info_ns_proxy.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/idle_partition/load_info_idle_sp.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 25%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 25%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 25%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 25%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 25%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 25%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 25%] Linking C static library libtfm_app_rot_partition_ffm11.a [ 25%] Built target tfm_app_rot_partition_ffm11 Scanning dependencies of target tfm_psa_rot_partition_platform [ 25%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/platform_sp.o [ 25%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/intermedia_tfm_platform.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/interface/src/psa/psa_client.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/interface/src/psa/psa_service.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/interface/src/psa/psa_lifecycle.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/ns_proxy_partition/load_info_ns_proxy.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/idle_partition/load_info_idle_sp.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 28%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 28%] Linking C static library libtfm_psa_rot_partition_platform.a [ 28%] Built target tfm_psa_rot_partition_platform Scanning dependencies of target tfm_psa_rot_partition_its [ 28%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_its_req_mngr.o [ 28%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_internal_trusted_storage.o [ 28%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/its_utils.o [ 28%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash.o [ 28%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nand.o [ 28%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nor.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_ram.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_dblock.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_mblock.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/intermedia_tfm_internal_trusted_storage.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/psa/psa_client.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/psa/psa_service.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/psa/psa_lifecycle.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/ns_proxy_partition/load_info_ns_proxy.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/idle_partition/load_info_idle_sp.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 31%] Linking C static library libtfm_psa_rot_partition_its.a [ 31%] Built target tfm_psa_rot_partition_its Scanning dependencies of target tfm_app_rot_partition_ps [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_ps_req_mngr.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_protected_storage.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_system.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_table.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_utils.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/crypto/ps_crypto_interface.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_encrypted_object.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/nv_counters/ps_nv_counters.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/intermedia_tfm_protected_storage.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/psa/psa_client.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/psa/psa_service.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/psa/psa_lifecycle.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/ns_proxy_partition/load_info_ns_proxy.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/idle_partition/load_info_idle_sp.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 34%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 34%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 34%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 34%] Linking C static library libtfm_app_rot_partition_ps.a [ 34%] Built target tfm_app_rot_partition_ps Scanning dependencies of target tfm_psa_rot_partition_attestation [ 34%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest_req_mngr.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_core.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_asymmetric_key.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_token_encode.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/intermedia_tfm_initial_attestation.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/psa/psa_client.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/psa/psa_service.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/psa/psa_lifecycle.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/ns_proxy_partition/load_info_ns_proxy.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/idle_partition/load_info_idle_sp.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/lib/ext/t_cose/src/t_cose_sign1_sign.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/lib/ext/t_cose/src/t_cose_sign1_verify.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/lib/ext/t_cose/src/t_cose_util.o [ 38%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/lib/ext/t_cose/src/t_cose_parameters.o [ 38%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/lib/ext/t_cose/crypto_adapters/t_cose_psa_crypto.o [ 38%] Linking C static library libtfm_psa_rot_partition_attestation.a [ 38%] Built target tfm_psa_rot_partition_attestation Scanning dependencies of target crypto_service_mbedcrypto [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aes.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aesni.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aria.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1parse.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1write.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/base64.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/bignum.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/camellia.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ccm.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chacha20.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chachapoly.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher_wrap.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cmac.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ctr_drbg.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/des.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/dhm.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdh.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdsa.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecjpake.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp_curves.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy_poll.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/error.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/gcm.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hkdf.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hmac_drbg.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md5.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/memory_buffer_alloc.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/mps_reader.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/mps_trace.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/nist_kw.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/oid.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/padlock.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pem.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk_wrap.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs12.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs5.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkparse.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkwrite.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform_util.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/poly1305.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_aead.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_cipher.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_client.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_driver_wrappers.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_ecp.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_hash.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_mac.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_rsa.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_se.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_slot_management.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_storage.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_its_file.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ripemd160.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa_alt_helpers.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha1.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha256.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha512.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/threading.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/timing.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version_features.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_client.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_service.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_lifecycle.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 47%] Linking C static library libmbedcrypto.a [ 47%] Built target crypto_service_mbedcrypto Scanning dependencies of target tfm_psa_rot_partition_crypto [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_init.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_alloc.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_cipher.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_hash.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_mac.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_aead.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_asymmetric.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key_derivation.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_rng.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/intermedia_tfm_crypto.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/psa/psa_client.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/psa/psa_service.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/psa/psa_lifecycle.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/ns_proxy_partition/load_info_ns_proxy.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/idle_partition/load_info_idle_sp.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 50%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 50%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 50%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 50%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 50%] Linking C static library libtfm_psa_rot_partition_crypto.a [ 50%] Built target tfm_psa_rot_partition_crypto Scanning dependencies of target tfm_sprt [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcmp.o [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcpy.o [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memmove.o [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memset.o [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/service_api.o [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/tfm_sp_log_raw.o [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/common/tfm_hal_sp_logdev_periph.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/crypto/tfm_crypto_secure_api.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/initial_attestation/tfm_attest_secure_api.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/protected_storage/tfm_ps_secure_api.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/internal_trusted_storage/tfm_its_secure_api.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/platform/tfm_platform_secure_api.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/test_services/tfm_ps_test_service/tfm_ps_test_service_api.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/psa/psa_client.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/psa/psa_service.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/psa/psa_lifecycle.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/log/tfm_log_raw.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/ns_proxy_partition/load_info_ns_proxy.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/idle_partition/load_info_idle_sp.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 53%] Linking C static library libtfm_sprt.a [ 53%] Built target tfm_sprt Scanning dependencies of target tfm_spm [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_boot_data.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_utils.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/utilities.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/spm_log.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/arch/tfm_arch.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/main.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/spm_ipc.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/static_load.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/spm_psa_client_call.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/psa_client_service_apis.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/tfm_core_svcalls_ipc.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/tfm_nspm_ipc.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/tfm_pools.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/tfm_thread.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/tfm_wait.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/arch/tfm_arch_v8m_main.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/partitions/idle_partition/idle_partition.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/psa/psa_client.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/psa/psa_service.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/psa/psa_lifecycle.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/log/tfm_log_raw.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/partitions/idle_partition/load_info_idle_sp.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 57%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 57%] Linking C static library libtfm_spm.a [ 57%] Built target tfm_spm Scanning dependencies of target tfm_s_log [ 58%] Building C object ns_log/CMakeFiles/tfm_s_log.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 58%] Building C object ns_log/CMakeFiles/tfm_s_log.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 58%] Building C object ns_log/CMakeFiles/tfm_s_log.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 58%] Building C object ns_log/CMakeFiles/tfm_s_log.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 58%] Building C object ns_log/CMakeFiles/tfm_s_log.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 58%] Linking C static library libtfm_s_log.a [ 58%] Built target tfm_s_log Scanning dependencies of target tfm_fih [ 58%] Building C object lib/fih/CMakeFiles/tfm_fih.dir/src/fih.o [ 58%] Building C object lib/fih/CMakeFiles/tfm_fih.dir/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 58%] Building C object lib/fih/CMakeFiles/tfm_fih.dir/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 58%] Building C object lib/fih/CMakeFiles/tfm_fih.dir/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 58%] Building C object lib/fih/CMakeFiles/tfm_fih.dir/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 59%] Linking C static library libtfm_fih.a [ 59%] Built target tfm_fih Scanning dependencies of target platform_ns [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 60%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 60%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 60%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 60%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 60%] Building C object platform/CMakeFiles/platform_ns.dir/ext/common/uart_stdout.o [ 60%] Building C object platform/CMakeFiles/platform_ns.dir/ext/common/template/tfm_initial_attest_pub_key.o [ 60%] Linking C static library libplatform_ns.a [ 60%] Built target platform_ns Scanning dependencies of target tfm_api_ns [ 60%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_platform_ipc_api.o [ 61%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ps_ipc_api.o [ 61%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_its_ipc_api.o [ 61%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_crypto_ipc_api.o [ 61%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_initial_attestation_ipc_api.o [ 61%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_psa_ns_api.o [ 61%] Building C object app/CMakeFiles/tfm_api_ns.dir/tfm_ns_interface.o [ 61%] Linking C static library libtfm_api_ns.a [ 61%] Built target tfm_api_ns Scanning dependencies of target tfm_ns_log [ 61%] Building C object ns_log/CMakeFiles/tfm_ns_log.dir/tfm_log_raw.o [ 61%] Linking C static library libtfm_ns_log.a [ 61%] Built target tfm_ns_log Scanning dependencies of target tfm_test_suite_ipc_ns [ 61%] Building C object test/suites/ipc/CMakeFiles/tfm_test_suite_ipc_ns.dir/non_secure/ipc_ns_interface_testsuite.o [ 61%] Building C object test/suites/ipc/CMakeFiles/tfm_test_suite_ipc_ns.dir/__/__/framework/test_framework.o [ 61%] Building C object test/suites/ipc/CMakeFiles/tfm_test_suite_ipc_ns.dir/__/__/framework/test_framework_helpers.o [ 61%] Building C object test/suites/ipc/CMakeFiles/tfm_test_suite_ipc_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 61%] Linking C static library libtfm_test_suite_ipc_ns.a [ 61%] Built target tfm_test_suite_ipc_ns Scanning dependencies of target tfm_qcbor_test [ 61%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/float_tests.o [ 61%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/half_to_double_from_rfc7049.o [ 61%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_decode_tests.o [ 61%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_encode_tests.o [ 61%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/run_tests.o [ 61%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/UsefulBuf_Tests.o [ 62%] Linking C static library libtfm_qcbor_test.a [ 62%] Built target tfm_qcbor_test Scanning dependencies of target tfm_t_cose_ns [ 62%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_ns.dir/src/t_cose_sign1_sign.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_ns.dir/src/t_cose_sign1_verify.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_ns.dir/src/t_cose_util.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_ns.dir/src/t_cose_parameters.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_ns.dir/crypto_adapters/t_cose_psa_crypto.o [ 63%] Linking C static library libtfm_t_cose_ns.a [ 63%] Built target tfm_t_cose_ns Scanning dependencies of target tfm_t_cose_test [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/run_tests.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_psa_test_key.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_test_messages.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_sign_verify_test.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_test.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/src/t_cose_sign1_sign.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/src/t_cose_sign1_verify.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/src/t_cose_util.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/src/t_cose_parameters.o [ 64%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/crypto_adapters/t_cose_psa_crypto.o [ 64%] Linking C static library libtfm_t_cose_test.a [ 64%] Built target tfm_t_cose_test Scanning dependencies of target tfm_s_scatter [ 64%] Building C object platform/target/CMakeFiles/tfm_s_scatter.dir/__/__/__/common/gcc/tfm_common_s.o [ 64%] Built target tfm_s_scatter Scanning dependencies of target tfm_s [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/spm/cmsis_psa/tfm_psa_api_veneers.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_s.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/partitions/idle_partition/load_info_idle_sp.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 66%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 66%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/psa/psa_client.o [ 66%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/psa/psa_service.o [ 66%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/psa/psa_lifecycle.o [ 66%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/log/tfm_log_raw.o [ 66%] Linking C executable ../bin/tfm_s.axf Memory region Used Size Region Size %age Used FLASH: 157740 B 235712 B 66.92% RAM: 72096 B 127 KB 55.44% VENEERS: 96 B 832 B 11.54% [ 66%] Built target tfm_s [ 67%] Generating s_veneers.o Scanning dependencies of target tfm_s_veneers [ 67%] Generating s_veneers.o [ 67%] Linking C static library libtfm_s_veneers.a [ 67%] Built target tfm_s_veneers Scanning dependencies of target tfm_test_suite_attestation_ns [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_public_key.o [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_test.o [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_common.o [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_asymmetric.o [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/non_secure/attest_asymmetric_ns_interface_testsuite.o [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/lib/ext/t_cose/src/t_cose_sign1_sign.o [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/lib/ext/t_cose/src/t_cose_sign1_verify.o [ 68%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/lib/ext/t_cose/src/t_cose_util.o [ 68%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/lib/ext/t_cose/src/t_cose_parameters.o [ 68%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/lib/ext/t_cose/crypto_adapters/t_cose_psa_crypto.o [ 68%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework.o [ 68%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_helpers.o [ 68%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 68%] Linking C static library libtfm_test_suite_attestation_ns.a [ 68%] Built target tfm_test_suite_attestation_ns Scanning dependencies of target tfm_test_suite_crypto_ns [ 68%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/crypto_tests_common.o [ 68%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/non_secure/crypto_ns_interface_testsuite.o [ 68%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework.o [ 69%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_helpers.o [ 69%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 69%] Linking C static library libtfm_test_suite_crypto_ns.a [ 69%] Built target tfm_test_suite_crypto_ns Scanning dependencies of target tfm_test_suite_its_ns [ 69%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/its_tests_common.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/non_secure/psa_its_ns_interface_testsuite.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_helpers.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Config/RTX_Config.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Source/rtx_lib.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/app/os_wrapper_cmsis_rtos_v2.o [ 70%] Linking C static library libtfm_test_suite_its_ns.a [ 70%] Built target tfm_test_suite_its_ns Scanning dependencies of target tfm_test_suite_qcbor_ns [ 71%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/non_secure/qcbor_ns_testsuite.o [ 71%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework.o [ 71%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_helpers.o [ 71%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 71%] Linking C static library libtfm_test_suite_qcbor_ns.a [ 71%] Built target tfm_test_suite_qcbor_ns Scanning dependencies of target tfm_test_suite_ps_ns [ 71%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/ns_test_helpers.o [ 71%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/psa_ps_ns_interface_testsuite.o [ 71%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework.o [ 71%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_helpers.o [ 71%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 71%] Linking C static library libtfm_test_suite_ps_ns.a [ 71%] Built target tfm_test_suite_ps_ns Scanning dependencies of target tfm_test_suite_t_cose_ns [ 71%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/non_secure/t_cose_ns_testsuite.o [ 71%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework.o [ 71%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_helpers.o [ 71%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 72%] Linking C static library libtfm_test_suite_t_cose_ns.a [ 72%] Built target tfm_test_suite_t_cose_ns Scanning dependencies of target tfm_test_suite_platform_ns [ 72%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/platform_tests_common.o [ 72%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/non_secure/platform_ns_interface_testsuite.o [ 73%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework.o [ 73%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_helpers.o [ 73%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 73%] Linking C static library libtfm_test_suite_platform_ns.a [ 73%] Built target tfm_test_suite_platform_ns Scanning dependencies of target tfm_test_suite_core_ns [ 73%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_positive_testsuite.o [ 73%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_test_api.o [ 73%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework.o [ 74%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_helpers.o [ 74%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 74%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/non_secure_suites.o [ 74%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Config/RTX_Config.o [ 74%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Source/rtx_lib.o [ 74%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/app/os_wrapper_cmsis_rtos_v2.o [ 74%] Linking C static library libtfm_test_suite_core_ns.a [ 74%] Built target tfm_test_suite_core_ns Scanning dependencies of target tfm_ns_integration_test [ 74%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/tfm_integ_test.o [ 74%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/non_secure_suites.o [ 74%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework.o [ 74%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_helpers.o [ 75%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_integ_test_helper.o [ 75%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Config/RTX_Config.o [ 75%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Source/rtx_lib.o [ 75%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/os_wrapper_cmsis_rtos_v2.o [ 75%] Linking C static library libtfm_ns_integration_test.a [ 75%] Built target tfm_ns_integration_test Scanning dependencies of target tfm_ns_scatter [ 75%] Building C object platform/target/CMakeFiles/tfm_ns_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_ns.o [ 75%] Built target tfm_ns_scatter Scanning dependencies of target tfm_ns [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/main_ns.o [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_ns.o [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Config/RTX_Config.o [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Source/rtx_lib.o [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/os_wrapper_cmsis_rtos_v2.o [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/non_secure_suites.o [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework.o [ 76%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_helpers.o [ 76%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_integ_test_helper.o [ 76%] Linking C executable ../bin/tfm_ns.axf Memory region Used Size Region Size %age Used FLASH: 130120 B 163 KB 77.96% RAM: 30368 B 128 KB 23.17% [ 76%] Built target tfm_ns Scanning dependencies of target tfm_ns_hex [ 76%] Generating ../bin/tfm_ns.hex [ 76%] Built target tfm_ns_hex Scanning dependencies of target tfm_ns_bin [ 76%] Generating ../bin/tfm_ns.bin [ 76%] Built target tfm_ns_bin Scanning dependencies of target tfm_ns_elf [ 76%] Generating ../bin/tfm_ns.elf [ 76%] Built target tfm_ns_elf Scanning dependencies of target tfm_ns_binaries [ 76%] Built target tfm_ns_binaries Scanning dependencies of target tfm_s_hex [ 76%] Generating ../bin/tfm_s.hex [ 76%] Built target tfm_s_hex Scanning dependencies of target tfm_s_bin [ 76%] Generating ../bin/tfm_s.bin [ 76%] Built target tfm_s_bin Scanning dependencies of target tfm_s_elf [ 76%] Generating ../bin/tfm_s.elf [ 76%] Built target tfm_s_elf Scanning dependencies of target tfm_s_binaries [ 76%] Built target tfm_s_binaries Scanning dependencies of target crypto_service_mbedx509 [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509.o [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_create.o [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crl.o [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crt.o [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_csr.o [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_crt.o [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_csr.o [ 76%] Linking C static library libmbedx509.a [ 76%] Built target crypto_service_mbedx509 Scanning dependencies of target crypto_service_mbedtls [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/debug.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/net_sockets.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cache.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ciphersuites.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cli.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cookie.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_msg.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_srv.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ticket.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_tls.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_tls13_keys.o [ 78%] Linking C static library libmbedtls.a [ 78%] Built target crypto_service_mbedtls Scanning dependencies of target bl2_scatter [ 78%] Building C object platform/target/CMakeFiles/bl2_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_bl2.o [ 78%] Built target bl2_scatter Scanning dependencies of target platform_bl2 [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/boot_hal.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/tfm_low_level_security.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/low_level_device.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc_ex.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng_ex.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/boot_hal.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/uart_stdout.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/nv_counters.o [ 82%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_rotpk.o [ 82%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 82%] Linking C static library libplatform_bl2.a [ 82%] Built target platform_bl2 Scanning dependencies of target bl2_crypto_hw [ 82%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/rsa_alt.o [ 82%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [ 82%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [ 82%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [ 82%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/md5_alt.o [ 82%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [ 83%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [ 83%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/stm.o [ 83%] Linking C static library libbl2_crypto_hw.a [ 83%] Built target bl2_crypto_hw Scanning dependencies of target bl2_mbedcrypto [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aes.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aesni.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aria.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1parse.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1write.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/base64.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/bignum.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/camellia.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ccm.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chacha20.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chachapoly.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher_wrap.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cmac.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ctr_drbg.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/des.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/dhm.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdh.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdsa.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecjpake.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp_curves.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy_poll.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/error.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/gcm.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hkdf.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hmac_drbg.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md5.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/memory_buffer_alloc.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/mps_reader.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/mps_trace.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/nist_kw.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/oid.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/padlock.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pem.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk_wrap.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs12.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs5.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkparse.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkwrite.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform_util.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/poly1305.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_aead.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_cipher.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_client.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_driver_wrappers.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_ecp.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_hash.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_mac.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_rsa.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_se.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_slot_management.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_storage.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_its_file.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ripemd160.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa_alt_helpers.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha1.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha256.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha512.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/threading.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/timing.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version_features.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/md5_alt.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/stm.o [ 91%] Linking C static library libmbedcrypto.a [ 91%] Built target bl2_mbedcrypto Scanning dependencies of target bootutil [ 91%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/boot_record.o [ 91%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/bootutil_misc.o [ 91%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/bootutil_public.o [ 91%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/caps.o [ 91%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/encrypted.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening_delay_rng_mbedtls.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec256.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ed25519.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_rsa.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_validate.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/loader.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_misc.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_move.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_scratch.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/tlv.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/md5_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/stm.o [ 94%] Linking C static library libbootutil.a [ 94%] Built target bootutil Scanning dependencies of target bl2 [ 94%] Building C object bl2/CMakeFiles/bl2.dir/src/security_cnt.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/src/flash_map.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/bl2_main.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/keys.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_extended.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_legacy.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_bl2.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/bl2/low_level_ospi_device.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_ospi_flash.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_ospi.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/Components/mx25lm51245g/mx25lm51245g.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/stm32l562e_dk/src/stm32l562e_discovery_ospi.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/md5_alt.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [ 96%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [ 96%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/stm.o [ 96%] Linking C executable ../bin/bl2.axf Memory region Used Size Region Size %age Used FLASH: 41968 B 66 KB 62.10% FLASH_NOHDP: 244 B 6 KB 3.97% RAM: 27336 B 63 KB 42.37% [ 96%] Built target bl2 Scanning dependencies of target bl2_elf [ 96%] Generating ../bin/bl2.elf [ 96%] Built target bl2_elf Scanning dependencies of target bl2_hex [ 96%] Generating ../bin/bl2.hex [ 96%] Built target bl2_hex Scanning dependencies of target bl2_bin [ 96%] Generating ../bin/bl2.bin [ 96%] Built target bl2_bin Scanning dependencies of target bl2_binaries [ 96%] Built target bl2_binaries Scanning dependencies of target signing_layout_s [ 96%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_s.dir/signing_layout_s.o [ 96%] Built target signing_layout_s Scanning dependencies of target signing_layout_ns [ 96%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_ns.dir/signing_layout_ns.o [ 96%] Built target signing_layout_ns Scanning dependencies of target tfm_s_signed_bin [ 96%] Generating tfm_s_signed.bin [ 96%] Built target tfm_s_signed_bin Scanning dependencies of target tfm_ns_signed_bin [ 96%] Generating tfm_ns_signed.bin [ 96%] Built target tfm_ns_signed_bin Scanning dependencies of target tfm_s_ns_signed_bin [ 96%] Generating tfm_s_ns_signed.bin [ 96%] Built target tfm_s_ns_signed_bin Scanning dependencies of target signed_images [ 96%] Built target signed_images Scanning dependencies of target bl2_mbedx509 [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_create.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_crl.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_crt.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_csr.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_crt.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_csr.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.o /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.c: In function 'mbedtls_rsa_private': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.c:1182:24: warning: unused parameter 'p_rng' [-Wunused-parameter] 1182 | void *p_rng, | ~~~~~~^~~~~ [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/md5_alt.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/stm.o [ 98%] Linking C static library libmbedx509.a [ 98%] Built target bl2_mbedx509 Scanning dependencies of target bl2_mbedtls [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/debug.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/net_sockets.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cache.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ciphersuites.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cli.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cookie.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_msg.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_srv.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ticket.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_tls.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_tls13_keys.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.o /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.c: In function 'mbedtls_rsa_private': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.c:1182:24: warning: unused parameter 'p_rng' [-Wunused-parameter] 1182 | void *p_rng, | ~~~~~~^~~~~ [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/md5_alt.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/stm.o [100%] Linking C static library libmbedtls.a [100%] Built target bl2_mbedtls Install the project... -- Install configuration: "Release" -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/secure_fw/partitions/crypto/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/secure_fw/partitions/crypto/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/secure_fw/partitions/crypto/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/bl2/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/bl2/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/bl2/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/scripts/stm_tool.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/scripts/bin2hex.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/regression.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/preprocess.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/TFM_UPDATE.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/TFM_BIN2HEX.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/postbuild.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/flash_layout.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/region_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/image_macros_to_preprocess_bl2.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/bl2.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_ns.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/bl2.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_ns.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_ns.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/bl2.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_ns.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/bl2.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/bl2.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_ns.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/lib/s_veneers.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/client.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/error.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa_manifest/sid.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/tfm_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/tfm_ns_interface.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/ext/tz_context.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/tfm_psa_call_param.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/protected_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/internal_trusted_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/storage_common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_extra.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_compat.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_client_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_sizes.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_types.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_values.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/tfm_crypto_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/initial_attestation.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/tfm_platform_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_psa_ns_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_ns_interface.c.example -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_ps_ipc_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_its_ipc_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_crypto_ipc_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_initial_attestation_ipc_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_platform_ipc_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/assemble.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/__pycache__ -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/__pycache__/macro_parser.cpython-36.pyc -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/requirements.txt -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/wrapper -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/wrapper/wrapper.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/layout_files/signing_layout_s.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/layout_files/signing_layout_ns.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/keys/root-RSA-3072_1.pem Best Regards, Poppy Wu Macronix Microelectronics (Suzhou) Co.,Ltd http://www.mxic.com.cn<http://www.mxic.com.cn/> CONFIDENTIALITY NOTE: This e-mail and any attachments may contain confidential information and/or personal data, which is protected by applicable laws. Please be reminded that duplication, disclosure, distribution, or use of this e-mail (and/or its attachments) or any part thereof is prohibited. If you receive this e-mail in error, please notify us immediately and delete this mail as well as its attachment(s) from your system. In addition, please be informed that collection, processing, and/or use of personal data is prohibited unless expressly permitted by personal data protection laws. Thank you for your attention and cooperation. Macronix International Co., Ltd. ===================================================================== -- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m-- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m -- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m

4 years, 7 months

1
0
0 0

Re: [TF-M] TF-M crypto test failure

by Edward Yang

Hi Raef and Summer, I have set PLATFORM_DUMMY_NV_SEED = TRUE and CRYPTO_HW_ACCELERATOR=OFF within STM config.cmake file,and the test result was the same,there were 8 crypto failures. I looked into the detailed error, and I commented out the code which set key's id attribute,showned as below. then the key can be imported,but there were still AES_CBC and AES_CFB ...symmetric single-shot API errors. I am wondering whether this test result occurs on the other platforms. Running Test Suite Crypto non-secure interface test (TFM_NS_CRYPTO_TEST_1XXX)... > Executing 'TFM_NS_CRYPTO_TEST_1001' Description: 'Non Secure Key management interface' TEST: TFM_NS_CRYPTO_TEST_1001 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1002' Description: 'Non Secure Symmetric encryption (AES-128-CBC) interface' key handle:2147483616 destroy key handle:2147483616 Error encrypting with the single-shot API (Failed at /home/a/workspace1/TF-M/) TEST: TFM_NS_CRYPTO_TEST_1002 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1003' Description: 'Non Secure Symmetric encryption (AES-128-CFB) interface' key handle:2147483616 destroy key handle:2147483616 Error encrypting with the single-shot API (Failed at /home/a/workspace1/TF-M/) TEST: TFM_NS_CRYPTO_TEST_1003 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1005' Description: 'Non Secure Symmetric encryption (AES-128-CTR) interface' key handle:2147483616 destroy key handle:2147483616 Error encrypting with the single-shot API (Failed at /home/a/workspace1/TF-M/) TEST: TFM_NS_CRYPTO_TEST_1005 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1007' Description: 'Non Secure Symmetric encryption invalid cipher' TEST: TFM_NS_CRYPTO_TEST_1007 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1008' Description: 'Non Secure Symmetric encryption invalid cipher (AES-152)' TEST: TFM_NS_CRYPTO_TEST_1008 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1009' Description: 'Non Secure Symmetric encryption invalid cipher (HMAC-128-CFB)' TEST: TFM_NS_CRYPTO_TEST_1009 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1010' Description: 'Non Secure Unsupported Hash (SHA-1) interface' TEST: TFM_NS_CRYPTO_TEST_1010 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1011' Description: 'Non Secure Hash (SHA-224) interface' TEST: TFM_NS_CRYPTO_TEST_1011 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1012' Description: 'Non Secure Hash (SHA-256) interface' TEST: TFM_NS_CRYPTO_TEST_1012 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1013' Description: 'Non Secure Hash (SHA-384) interface' TEST: TFM_NS_CRYPTO_TEST_1013 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1014' Description: 'Non Secure Hash (SHA-512) interface' TEST: TFM_NS_CRYPTO_TEST_1014 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1019' Description: 'Non Secure Unsupported HMAC (SHA-1) interface' TEST: TFM_NS_CRYPTO_TEST_1019 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1020' Description: 'Non Secure HMAC (SHA-256) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf) TEST: TFM_NS_CRYPTO_TEST_1020 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1021' Description: 'Non Secure HMAC (SHA-384) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf) TEST: TFM_NS_CRYPTO_TEST_1021 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1022' Description: 'Non Secure HMAC (SHA-512) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf) TEST: TFM_NS_CRYPTO_TEST_1022 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1024' Description: 'Non Secure HMAC with long key (SHA-224) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf) TEST: TFM_NS_CRYPTO_TEST_1024 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1030' Description: 'Non Secure AEAD (AES-128-CCM) interface' TEST: TFM_NS_CRYPTO_TEST_1030 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1031' Description: 'Non Secure AEAD (AES-128-GCM) interface' TEST: TFM_NS_CRYPTO_TEST_1031 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1032' Description: 'Non Secure key policy interface' TEST: TFM_NS_CRYPTO_TEST_1032 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1033' Description: 'Non Secure key policy check permissions' TEST: TFM_NS_CRYPTO_TEST_1033 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1034' Description: 'Non Secure persistent key interface' Failed to import a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/t) TEST: TFM_NS_CRYPTO_TEST_1034 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1035' Description: 'Non Secure AEAD interface with truncated auth tag (AES-128-CCM-' TEST: TFM_NS_CRYPTO_TEST_1035 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1036' Description: 'Non Secure TLS 1.2 PRF key derivation' TEST: TFM_NS_CRYPTO_TEST_1036 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1037' Description: 'Non Secure TLS-1.2 PSK-to-MasterSecret key derivation' TEST: TFM_NS_CRYPTO_TEST_1037 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1038' Description: 'Non Secure HKDF key derivation' TEST: TFM_NS_CRYPTO_TEST_1038 - PASSED! TESTSUITE FAILED! Number of failed tests: 8 of 26 Best Regards, Poppy Wu Summer Qin via TF-M <tf-m(a)lists.trustedfirmware.org> Sent by: "TF-M" <tf-m-bounces(a)lists.trustedfirmware.org> 2021/08/03 10:52 Please respond to Summer Qin <Summer.Qin(a)arm.com> To "tf-m(a)lists.trustedfirmware.org" <tf-m(a)lists.trustedfirmware.org>, Edward Yang <EdwardYang(a)mxic.com.cn>, Raef Coles <Raef.Coles(a)arm.com> cc nd <nd(a)arm.com> Subject Re: [TF-M] TF-M crypto test failure Hi Edward, STM uses its own accelerator for crypto as the default config. Please try Raef's suggestion, but you also need to set "-DPLATFORM_DUMMY_NV_SEED = TRUE" when you set "-DCRYPTO_HW_ACCELERATOR=OFF" manually, otherwise you will see cmake error. Best Regards, Summer From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Raef Coles via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: Monday, August 2, 2021 11:28 PM To: tf-m(a)lists.trustedfirmware.org <tf-m(a)lists.trustedfirmware.org>; Edward Yang <EdwardYang(a)mxic.com.cn> Subject: Re: [TF-M] TF-M crypto test failure Hi Edward As part of the migration to mbedtls 3.0, we had to update some of the code for the STM crypto accelerator mbedtls compatibility layer. It's possible these failures are related to those changes. Could you run the same tests with `-DCRYPTO_HW_ACCELERATOR=OFF`, and see if there are less failures in that mode? Thanks, Raef ________________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Edward Yang via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 02 August 2021 14:31 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] TF-M crypto test failure Hi experts, We tested the latest trusted-firmware-m code with tf-m-tests on stm32l562e_dk discovery board,but some crypto failures occured, The test log is showed below: [INF] Starting bootloader [INF] Swap type: none [INF] Swap type: none [INF] Bootloader chainload address offset: 0x19000 [INF] Jumping to the first image slot [Sec Thread] Secure image initializing! TF-M isolation level is: 0x00000001 Booting TFM v1.3.0 Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA internal trusted storage NS interface tests (TFM_NS_ITS_TEST_1XXX)... > Executing 'TFM_NS_ITS_TEST_1001' Description: 'Set interface' TEST: TFM_NS_ITS_TEST_1001 - PASSED! > Executing 'TFM_NS_ITS_TEST_1002' Description: 'Set interface with create flags' Note: The UID in this test has already been created with the PSA_STORAGE_FLAG_WRITE_ONCE flag in a previous test run. Wipe the storage area to run the full test. TEST: TFM_NS_ITS_TEST_1002 - PASSED! > Executing 'TFM_NS_ITS_TEST_1003' Description: 'Set interface with NULL data pointer' TEST: TFM_NS_ITS_TEST_1003 - PASSED! > Executing 'TFM_NS_ITS_TEST_1004' Description: 'Set interface with write once UID' TEST: TFM_NS_ITS_TEST_1004 - PASSED! > Executing 'TFM_NS_ITS_TEST_1005' Description: 'Get interface with valid data' TEST: TFM_NS_ITS_TEST_1005 - PASSED! > Executing 'TFM_NS_ITS_TEST_1006' Description: 'Get interface with zero data length' TEST: TFM_NS_ITS_TEST_1006 - PASSED! > Executing 'TFM_NS_ITS_TEST_1007' Description: 'Get interface with invalid UIDs' TEST: TFM_NS_ITS_TEST_1007 - PASSED! > Executing 'TFM_NS_ITS_TEST_1008' Description: 'Get interface with invalid data lengths and offsets' TEST: TFM_NS_ITS_TEST_1008 - PASSED! > Executing 'TFM_NS_ITS_TEST_1009' Description: 'Get interface with NULL data pointer' TEST: TFM_NS_ITS_TEST_1009 - PASSED! > Executing 'TFM_NS_ITS_TEST_1010' Description: 'Get info interface with write once UID' TEST: TFM_NS_ITS_TEST_1010 - PASSED! > Executing 'TFM_NS_ITS_TEST_1011' Description: 'Get info interface with valid UID' TEST: TFM_NS_ITS_TEST_1011 - PASSED! > Executing 'TFM_NS_ITS_TEST_1012' Description: 'Get info interface with invalid UIDs' TEST: TFM_NS_ITS_TEST_1012 - PASSED! > Executing 'TFM_NS_ITS_TEST_1013' Description: 'Remove interface with valid UID' TEST: TFM_NS_ITS_TEST_1013 - PASSED! > Executing 'TFM_NS_ITS_TEST_1014' Description: 'Remove interface with write once UID' TEST: TFM_NS_ITS_TEST_1014 - PASSED! > Executing 'TFM_NS_ITS_TEST_1015' Description: 'Remove interface with invalid UID' TEST: TFM_NS_ITS_TEST_1015 - PASSED! > Executing 'TFM_NS_ITS_TEST_1016' Description: 'Block compaction after remove' TEST: TFM_NS_ITS_TEST_1016 - PASSED! > Executing 'TFM_NS_ITS_TEST_1017' Description: 'Multiple partial gets' TEST: TFM_NS_ITS_TEST_1017 - PASSED! > Executing 'TFM_NS_ITS_TEST_1018' Description: 'Multiple sets to same UID from same thread' TEST: TFM_NS_ITS_TEST_1018 - PASSED! > Executing 'TFM_NS_ITS_TEST_1019' Description: 'Set, get and remove interface with different asset sizes' TEST: TFM_NS_ITS_TEST_1019 - PASSED! TESTSUITE PASSED! Running Test Suite Crypto non-secure interface test (TFM_NS_CRYPTO_TEST_1XXX)... > Executing 'TFM_NS_CRYPTO_TEST_1001' Description: 'Non Secure Key management interface' TEST: TFM_NS_CRYPTO_TEST_1001 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1002' Description: 'Non Secure Symmetric encryption (AES-128-CBC) interface' Error destroying a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:345) TEST: TFM_NS_CRYPTO_TEST_1002 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1003' Description: 'Non Secure Symmetric encryption (AES-128-CFB) interface' Error destroying a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:345) TEST: TFM_NS_CRYPTO_TEST_1003 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1005' Description: 'Non Secure Symmetric encryption (AES-128-CTR) interface' Error destroying a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:345) TEST: TFM_NS_CRYPTO_TEST_1005 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1007' Description: 'Non Secure Symmetric encryption invalid cipher' TEST: TFM_NS_CRYPTO_TEST_1007 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1008' Description: 'Non Secure Symmetric encryption invalid cipher (AES-152)' TEST: TFM_NS_CRYPTO_TEST_1008 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1009' Description: 'Non Secure Symmetric encryption invalid cipher (HMAC-128-CFB)' TEST: TFM_NS_CRYPTO_TEST_1009 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1010' Description: 'Non Secure Unsupported Hash (SHA-1) interface' TEST: TFM_NS_CRYPTO_TEST_1010 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1011' Description: 'Non Secure Hash (SHA-224) interface' TEST: TFM_NS_CRYPTO_TEST_1011 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1012' Description: 'Non Secure Hash (SHA-256) interface' TEST: TFM_NS_CRYPTO_TEST_1012 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1013' Description: 'Non Secure Hash (SHA-384) interface' TEST: TFM_NS_CRYPTO_TEST_1013 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1014' Description: 'Non Secure Hash (SHA-512) interface' TEST: TFM_NS_CRYPTO_TEST_1014 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1019' Description: 'Non Secure Unsupported HMAC (SHA-1) interface' TEST: TFM_NS_CRYPTO_TEST_1019 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1020' Description: 'Non Secure HMAC (SHA-256) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:628) TEST: TFM_NS_CRYPTO_TEST_1020 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1021' Description: 'Non Secure HMAC (SHA-384) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:628) TEST: TFM_NS_CRYPTO_TEST_1021 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1022' Description: 'Non Secure HMAC (SHA-512) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:628) TEST: TFM_NS_CRYPTO_TEST_1022 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1024' Description: 'Non Secure HMAC with long key (SHA-224) interface' Error importing a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:628) TEST: TFM_NS_CRYPTO_TEST_1024 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1030' Description: 'Non Secure AEAD (AES-128-CCM) interface' TEST: TFM_NS_CRYPTO_TEST_1030 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1031' Description: 'Non Secure AEAD (AES-128-GCM) interface' TEST: TFM_NS_CRYPTO_TEST_1031 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1032' Description: 'Non Secure key policy interface' TEST: TFM_NS_CRYPTO_TEST_1032 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1033' Description: 'Non Secure key policy check permissions' TEST: TFM_NS_CRYPTO_TEST_1033 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1034' Description: 'Non Secure persistent key interface' Failed to import a key (Failed at /home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/crypto/crypto_tests_common.c:107) TEST: TFM_NS_CRYPTO_TEST_1034 - FAILED! > Executing 'TFM_NS_CRYPTO_TEST_1035' Description: 'Non Secure AEAD interface with truncated auth tag (AES-128-CCM-8)' TEST: TFM_NS_CRYPTO_TEST_1035 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1036' Description: 'Non Secure TLS 1.2 PRF key derivation' TEST: TFM_NS_CRYPTO_TEST_1036 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1037' Description: 'Non Secure TLS-1.2 PSK-to-MasterSecret key derivation' TEST: TFM_NS_CRYPTO_TEST_1037 - PASSED! > Executing 'TFM_NS_CRYPTO_TEST_1038' Description: 'Non Secure HKDF key derivation' TEST: TFM_NS_CRYPTO_TEST_1038 - PASSED! TESTSUITE FAILED! Number of failed tests: 8 of 26 .... The detailed software versions are as follows: trusted-firmware-m:commit 07c2e6868cb7027325a0b84dd4c14bf619f5dc34 tf-m-tests:commit e1a8c9fb8394b1f6ea66d2611c070915b0d4b573 mcuboot:commit 4f8091318b4026d14af9e5a7036825bff62fb612 mbedtls:commit 8df2f8e7b9c7bb9390ac74bb7bace27edca81a2b And below is the build command and procedure, root@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test# cmake .. -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_NS=ON -DTFM_PSA_API=ON -DTFM_SPM_LOG_LEVEL=TFM_SPM_LOG_LEVEL_DEBUG -- The C compiler identification is GNU 9.3.1 -- The ASM compiler identification is GNU -- Found assembler: /home/a/Tools/gcc-arm-none-eabi-9-2020-q2-update/bin/arm-none-eabi-gcc -- Found Python3: /home/a/python3.6/bin/python3.6 (found version "3.6.12") found components: Interpreter Start to generate partition files: Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/protected_storage/psa_manifest/tfm_protected_storage.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/protected_storage/auto_generated/intermedia_tfm_protected_storage.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/internal_trusted_storage/psa_manifest/tfm_internal_trusted_storage.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/intermedia_tfm_internal_trusted_storage.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/audit_logging/psa_manifest/tfm_audit_logging.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/audit_logging/auto_generated/intermedia_tfm_audit_logging.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/audit_logging/auto_generated/load_info_tfm_audit_logging.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/crypto/psa_manifest/tfm_crypto.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/crypto/auto_generated/intermedia_tfm_crypto.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/platform/psa_manifest/tfm_platform.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/platform/auto_generated/intermedia_tfm_platform.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/initial_attestation/psa_manifest/tfm_initial_attestation.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/initial_attestation/auto_generated/intermedia_tfm_initial_attestation.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_core_test/psa_manifest/tfm_ss_core_test.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_core_test/auto_generated/intermedia_tfm_ss_core_test.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_core_test_2/psa_manifest/tfm_ss_core_test_2.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_core_test_2/auto_generated/intermedia_tfm_ss_core_test_2.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_secure_client_service/psa_manifest/tfm_secure_client_service.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_secure_client_service/auto_generated/intermedia_tfm_secure_client_service.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_secure_client_service/auto_generated/load_info_tfm_secure_client_service.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ipc_service/psa_manifest/tfm_ipc_service_test.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ipc_service/auto_generated/intermedia_tfm_ipc_service_test.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ipc_client/psa_manifest/tfm_ipc_client_test.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ipc_client/auto_generated/intermedia_tfm_ipc_client_test.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ps_test_service/psa_manifest/tfm_ps_test_service.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ps_test_service/auto_generated/intermedia_tfm_ps_test_service.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_secure_client_2/psa_manifest/tfm_secure_client_2.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_secure_client_2/auto_generated/intermedia_tfm_secure_client_2.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_secure_client_2/auto_generated/load_info_tfm_secure_client_2.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/firmware_update/psa_manifest/tfm_firmware_update.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/firmware_update/auto_generated/intermedia_tfm_firmware_update.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/firmware_update/auto_generated/load_info_tfm_firmware_update.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/tfm_ffm11_partition/psa_manifest/tfm_ffm11_partition.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/intermedia_tfm_ffm11_partition.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_attest_test_service/psa_manifest/tfm_attest_test_service.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_attest_test_service/auto_generated/intermedia_tfm_attest_test_service.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_attest_test_service/auto_generated/load_info_tfm_attest_test_service.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_slih_test_service/psa_manifest/tfm_slih_test_service.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_slih_test_service/auto_generated/intermedia_tfm_slih_test_service.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_slih_test_service/auto_generated/load_info_tfm_slih_test_service.c Generating Header: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_flih_test_service/psa_manifest/tfm_flih_test_service.h Generating Intermedia: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_flih_test_service/auto_generated/intermedia_tfm_flih_test_service.c Generating Loadinfo: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/test_services/tfm_flih_test_service/auto_generated/load_info_tfm_flih_test_service.c Per-partition files done: Start to generate file from the generated list: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/spm/cmsis_func/tfm_spm_db_func.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/spm/cmsis_func/tfm_veneers.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/interface/include/tfm_veneers.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/spm/cmsis_func/tfm_secure_irq_handlers.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/secure_fw/spm/cmsis_psa/tfm_secure_irq_handlers_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/interface/include/psa_manifest/sid.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/interface/include/psa_manifest/pid.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/platform/ext/common/armclang/tfm_isolation_l3.sct Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/generated/platform/ext/common/gcc/tfm_isolation_l3.ld Generation of files done -- Found PythonInterp: /home/a/python3.6/bin/python3 (found suitable version "3.6.12", minimum required is "3") -- Could NOT find Sphinx (missing: SPHINX_VERSION) CMake Warning (dev) at /home/a/Tools/cmake-3.19.6-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:426 (message): The package name passed to `find_package_handle_standard_args` (PY_M2R) does not match the name of the calling package (PythonModules). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): cmake/FindPythonModules.cmake:60 (find_package_handle_standard_args) docs/CMakeLists.txt:14 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Can not find Python module m2r (missing: PY_M2R) CMake Warning (dev) at /home/a/Tools/cmake-3.19.6-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:426 (message): The package name passed to `find_package_handle_standard_args` (PY_SPHINX-RTD-THEME) does not match the name of the calling package (PythonModules). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): cmake/FindPythonModules.cmake:60 (find_package_handle_standard_args) docs/CMakeLists.txt:14 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Can not find Python module sphinx-rtd-theme (missing: PY_SPHINX-RTD-THEME) CMake Warning (dev) at /home/a/Tools/cmake-3.19.6-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:426 (message): The package name passed to `find_package_handle_standard_args` (PY_SPHINXCONTRIB.PLANTUML) does not match the name of the calling package (PythonModules). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): cmake/FindPythonModules.cmake:60 (find_package_handle_standard_args) docs/CMakeLists.txt:14 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Can not find Python module sphinxcontrib.plantuml (missing: PY_SPHINXCONTRIB.PLANTUML) -- Found Java: /usr/bin/java (found suitable version "1.8.0.292", minimum required is "1.8") found components: Runtime -- PLANTUML_JAR_PATH variable is missing, PlantUML jar location is unknown. CMake Warning (dev) at /home/a/Tools/cmake-3.19.6-Linux-x86_64/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:426 (message): The package name passed to `find_package_handle_standard_args` (Plantuml) does not match the name of the calling package (PlantUML). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): cmake/FindPlantUML.cmake:63 (find_package_handle_standard_args) docs/CMakeLists.txt:15 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Could NOT find Plantuml (missing: PLANTUML_JAR_PATH PLANTUML_VERSION) -- Found Doxygen: /usr/bin/doxygen (found suitable version "1.8.11", minimum required is "1.8.0") found components: doxygen dot -- Found LATEX: /usr/bin/latex found components: PDFLATEX -- ---------- Display crypto configuration - start -------------- -- CRYPTO_RNG_MODULE_DISABLED is set to FALSE -- CRYPTO_KEY_MODULE_DISABLED is set to FALSE -- CRYPTO_AEAD_MODULE_DISABLED is set to FALSE -- CRYPTO_MAC_MODULE_DISABLED is set to FALSE -- CRYPTO_CIPHER_MODULE_DISABLED is set to FALSE -- CRYPTO_HASH_MODULE_DISABLED is set to FALSE -- CRYPTO_KEY_DERIVATION_MODULE_DISABLED is set to FALSE -- CRYPTO_ASYM_SIGN_MODULE_DISABLED is set to FALSE -- CRYPTO_ASYM_ENCRYPT_MODULE_DISABLED is set to FALSE -- CRYPTO_ENGINE_BUF_SIZE is set to 0x2080 -- CRYPTO_CONC_OPER_NUM is set to 8 -- CRYPTO_KEY_ID_ENCODES_OWNER is set to ON -- CRYPTO_IOVEC_BUFFER_SIZE is set to 5120 -- ---------- Display crypto configuration - stop --------------- -- Performing Test C_COMPILER_SUPPORTS_WFORMAT_SIGNEDNESS -- Performing Test C_COMPILER_SUPPORTS_WFORMAT_SIGNEDNESS - Failed -- ----------- Display storage configuration - start ------------ -- PS_CREATE_FLASH_LAYOUT is set to ON -- PS_ENCRYPTION is set to ON -- PS_RAM_FS is set to OFF -- PS_ROLLBACK_PROTECTION is set to ON -- PS_VALIDATE_METADATA_FROM_FLASH is set to ON -- PS_MAX_ASSET_SIZE is set to 2048 -- PS_NUM_ASSETS is set to 10 -- PS_CRYPTO_AEAD_ALG is set to PSA_ALG_GCM -- ITS_CREATE_FLASH_LAYOUT is set to ON -- ITS_RAM_FS is set to OFF -- ITS_VALIDATE_METADATA_FROM_FLASH is set to ON -- ITS_MAX_ASSET_SIZE is set to 512 -- ITS_NUM_ASSETS is set to 10 -- ITS_BUF_SIZE is not set (defaults to ITS_MAX_ASSET_SIZE) -- ----------- Display storage configuration - stop ------------- -- Configuring done -- Generating done -- Build files have been written to: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test root@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test# make install Scanning dependencies of target tfm_generated_files [ 0%] Built target tfm_generated_files Scanning dependencies of target tfm_qcbor [ 0%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/ieee754.o [ 0%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_encode.o [ 0%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_decode.o [ 1%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/UsefulBuf.o [ 1%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/util/qcbor_util.o [ 1%] Linking C static library libtfm_qcbor.a [ 1%] Built target tfm_qcbor Scanning dependencies of target tfm_t_cose_s [ 1%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_s.dir/src/t_cose_sign1_sign.o [ 1%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_s.dir/src/t_cose_sign1_verify.o [ 1%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_s.dir/src/t_cose_util.o [ 1%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_s.dir/src/t_cose_parameters.o [ 1%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_s.dir/crypto_adapters/t_cose_psa_crypto.o [ 2%] Linking C static library libtfm_t_cose_s.a [ 2%] Built target tfm_t_cose_s Scanning dependencies of target crypto_service_crypto_hw [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/rsa_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/md5_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [ 2%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/stm.o [ 3%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 3%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 3%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 3%] Building C object platform/ext/accelerator/CMakeFiles/crypto_service_crypto_hw.dir/__/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 3%] Linking C static library libcrypto_service_crypto_hw.a [ 3%] Built target crypto_service_crypto_hw Scanning dependencies of target tfm_app_rot_partition_ipc_client [ 3%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/tfm_ipc_client_test.o [ 3%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/intermedia_tfm_ipc_client_test.o [ 3%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_client.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_service.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_lifecycle.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 4%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/test_services/t fm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 5%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 6%] Building C object test/test_services/tfm_ipc_client/CMakeFiles/tfm_app_rot_partition_ipc_client.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 6%] Linking C static library libtfm_app_rot_partition_ipc_client.a [ 6%] Built target tfm_app_rot_partition_ipc_client Scanning dependencies of target tfm_psa_rot_partition_ipc_service [ 6%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/tfm_ipc_service_test.o [ 6%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/intermedia_tfm_ipc_service_test.o [ 6%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_client.o [ 6%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_service.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_lifecycle.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 7%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 8%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/framework/test_framework.o [ 9%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/framework/test_framework_helpers.o [ 9%] Building C object test/test_services/tfm_ipc_service/CMakeFiles/tfm_psa_rot_partition_ipc_service.dir/__/__/framework/test_framework_integ_test_helper.o [ 9%] Linking C static library libtfm_psa_rot_partition_ipc_service.a [ 9%] Built target tfm_psa_rot_partition_ipc_service Scanning dependencies of target tfm_psa_rot_partition_ps_test [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/tfm_ps_test_service.o [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/intermedia_tfm_ps_test_service.o [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_client.o [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_service.o [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_lifecycle.o [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 9%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 10%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 11%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 11%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 11%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 11%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 11%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 11%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 11%] Linking C static library libtfm_psa_rot_partition_ps_test.a [ 11%] Built target tfm_psa_rot_partition_ps_test Scanning dependencies of target tfm_app_rot_partition_core_test_2 [ 11%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/tfm_ss_core_test_2.o [ 11%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/intermedia_tfm_ss_core_test_2.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_client.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_service.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_lifecycle.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 12%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 13%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 14%] Building C object test/test_services/tfm_core_test_2/CMakeFiles/tfm_app_rot_partition_core_test_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 14%] Linking C static library libtfm_app_rot_partition_core_test_2.a [ 14%] Built target tfm_app_rot_partition_core_test_2 Scanning dependencies of target tfm_psa_rot_partition_core_test [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/tfm_ss_core_test.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/intermedia_tfm_ss_core_test.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_client.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_service.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_lifecycle.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_helpers.o [ 16%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_integ_test_helper.o [ 17%] Linking C static library libtfm_psa_rot_partition_core_test.a [ 17%] Built target tfm_psa_rot_partition_core_test Scanning dependencies of target platform_s [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/system_stm32l5xx.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/spm_hal.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_hal_isolation.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/target_cfg.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/low_level_device.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 18%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc_ex.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 19%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_isolation_mpu_v8m.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_platform_system.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng_ex.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_ps.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_its.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_platform.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/uart_stdout.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_spm_logdev_peripheral.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_memory_symbols.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/attest_hal.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/nv_counters.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/crypto_keys.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_rotpk.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/psa/psa_client.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/psa/psa_service.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/psa/psa_lifecycle.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/log/tfm_log_raw.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/__/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 23%] Linking C static library libplatform_s.a [ 23%] Built target platform_s Scanning dependencies of target tfm_app_rot_partition_ffm11 [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/tfm_ffm11_partition.o [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/intermedia_tfm_ffm11_partition.o [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/interface/src/psa/psa_client.o [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/interface/src/psa/psa_service.o [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/interface/src/psa/psa_lifecycle.o [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 23%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/ns_proxy_partition/load_info_ns_proxy.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/idle_partition/load_info_idle_sp.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 24%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 25%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 25%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 25%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 25%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 25%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 25%] Building C object secure_fw/partitions/tfm_ffm11_partition/CMakeFiles/tfm_app_rot_partition_ffm11.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 25%] Linking C static library libtfm_app_rot_partition_ffm11.a [ 25%] Built target tfm_app_rot_partition_ffm11 Scanning dependencies of target tfm_psa_rot_partition_platform [ 25%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/platform_sp.o [ 25%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/intermedia_tfm_platform.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/interface/src/psa/psa_client.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/interface/src/psa/psa_service.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/interface/src/psa/psa_lifecycle.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 26%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/ns_proxy_partition/load_info_ns_proxy.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/idle_partition/load_info_idle_sp.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 27%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 28%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 28%] Linking C static library libtfm_psa_rot_partition_platform.a [ 28%] Built target tfm_psa_rot_partition_platform Scanning dependencies of target tfm_psa_rot_partition_its [ 28%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_its_req_mngr.o [ 28%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_internal_trusted_storage.o [ 28%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/its_utils.o [ 28%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash.o [ 28%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nand.o [ 28%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nor.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_ram.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_dblock.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_mblock.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/intermedia_tfm_internal_trusted_storage.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/psa/psa_client.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/psa/psa_service.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/psa/psa_lifecycle.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 29%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/ns_proxy_partition/load_info_ns_proxy.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/idle_partition/load_info_idle_sp.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 31%] Linking C static library libtfm_psa_rot_partition_its.a [ 31%] Built target tfm_psa_rot_partition_its Scanning dependencies of target tfm_app_rot_partition_ps [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_ps_req_mngr.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_protected_storage.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_system.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_table.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_utils.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/crypto/ps_crypto_interface.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_encrypted_object.o [ 31%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/nv_counters/ps_nv_counters.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/intermedia_tfm_protected_storage.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/psa/psa_client.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/psa/psa_service.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/psa/psa_lifecycle.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/ns_proxy_partition/load_info_ns_proxy.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/idle_partition/load_info_idle_sp.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 34%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 34%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 34%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 34%] Linking C static library libtfm_app_rot_partition_ps.a [ 34%] Built target tfm_app_rot_partition_ps Scanning dependencies of target tfm_psa_rot_partition_attestation [ 34%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest_req_mngr.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_core.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_asymmetric_key.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_token_encode.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/intermedia_tfm_initial_attestation.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/psa/psa_client.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/psa/psa_service.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/psa/psa_lifecycle.o [ 35%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/ns_proxy_partition/load_info_ns_proxy.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/idle_partition/load_info_idle_sp.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 36%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/lib/ext/t_cose/src/t_cose_sign1_sign.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/lib/ext/t_cose/src/t_cose_sign1_verify.o [ 37%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/lib/ext/t_cose/src/t_cose_util.o [ 38%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/lib/ext/t_cose/src/t_cose_parameters.o [ 38%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/lib/ext/t_cose/crypto_adapters/t_cose_psa_crypto.o [ 38%] Linking C static library libtfm_psa_rot_partition_attestation.a [ 38%] Built target tfm_psa_rot_partition_attestation Scanning dependencies of target crypto_service_mbedcrypto [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aes.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aesni.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aria.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1parse.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1write.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/base64.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/bignum.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/camellia.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ccm.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chacha20.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chachapoly.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher_wrap.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cmac.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ctr_drbg.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/des.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/dhm.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdh.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdsa.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecjpake.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp_curves.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy_poll.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/error.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/gcm.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hkdf.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hmac_drbg.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md5.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/memory_buffer_alloc.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/mps_reader.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/mps_trace.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/nist_kw.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/oid.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/padlock.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pem.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk_wrap.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs12.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs5.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkparse.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkwrite.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform_util.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/poly1305.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_aead.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_cipher.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_client.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_driver_wrappers.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_ecp.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_hash.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_mac.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_rsa.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_se.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_slot_management.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_storage.o [ 44%] Building C object secure_fw/par titions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_its_file.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ripemd160.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa_alt_helpers.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha1.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha256.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha512.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/threading.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/timing.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version_features.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_client.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_service.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/psa/psa_lifecycle.o [ 45%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/partitions/idle_partition/load_info_idle_sp.o [ 46%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/__/__/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 47%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 47%] Linking C static library libmbedcrypto.a [ 47%] Built target crypto_service_mbedcrypto Scanning dependencies of target tfm_psa_rot_partition_crypto [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_init.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_alloc.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_cipher.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_hash.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_mac.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_aead.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_asymmetric.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key_derivation.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_rng.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/intermedia_tfm_crypto.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/psa/psa_client.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/psa/psa_service.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/psa/psa_lifecycle.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 48%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/ns_proxy_partition/load_info_ns_proxy.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/idle_partition/load_info_idle_sp.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 49%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 50%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 50%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 50%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 50%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 50%] Linking C static library libtfm_psa_rot_partition_crypto.a [ 50%] Built target tfm_psa_rot_partition_crypto Scanning dependencies of target tfm_sprt [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcmp.o [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcpy.o [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memmove.o [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memset.o [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/service_api.o [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/tfm_sp_log_raw.o [ 50%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/common/tfm_hal_sp_logdev_periph.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/crypto/tfm_crypto_secure_api.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/initial_attestation/tfm_attest_secure_api.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/protected_storage/tfm_ps_secure_api.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/internal_trusted_storage/tfm_its_secure_api.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/platform/tfm_platform_secure_api.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/test_services/tfm_ps_test_service/tfm_ps_test_service_api.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 51%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/psa/psa_client.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/psa/psa_service.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/psa/psa_lifecycle.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/log/tfm_log_raw.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/ns_proxy_partition/load_info_ns_proxy.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/idle_partition/load_info_idle_sp.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 53%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 53%] Linking C static library libtfm_sprt.a [ 53%] Built target tfm_sprt Scanning dependencies of target tfm_spm [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_boot_data.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_utils.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/utilities.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/spm_log.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/arch/tfm_arch.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/main.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/spm_ipc.o [ 53%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/static_load.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/spm_psa_client_call.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/psa_client_service_apis.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/tfm_core_svcalls_ipc.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/tfm_nspm_ipc.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/tfm_pools.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/tfm_thread.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/tfm_wait.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_psa/arch/tfm_arch_v8m_main.o [ 54%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/partitions/idle_partition/idle_partition.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/psa/psa_client.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/psa/psa_service.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/psa/psa_lifecycle.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/log/tfm_log_raw.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 55%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/partitions/idle_partition/load_info_idle_sp.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 56%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 57%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 57%] Linking C static library libtfm_spm.a [ 57%] Built target tfm_spm Scanning dependencies of target tfm_s_log [ 58%] Building C object ns_log/CMakeFiles/tfm_s_log.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 58%] Building C object ns_log/CMakeFiles/tfm_s_log.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 58%] Building C object ns_log/CMakeFiles/tfm_s_log.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 58%] Building C object ns_log/CMakeFiles/tfm_s_log.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 58%] Building C object ns_log/CMakeFiles/tfm_s_log.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 58%] Linking C static library libtfm_s_log.a [ 58%] Built target tfm_s_log Scanning dependencies of target tfm_fih [ 58%] Building C object lib/fih/CMakeFiles/tfm_fih.dir/src/fih.o [ 58%] Building C object lib/fih/CMakeFiles/tfm_fih.dir/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 58%] Building C object lib/fih/CMakeFiles/tfm_fih.dir/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 58%] Building C object lib/fih/CMakeFiles/tfm_fih.dir/__/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 58%] Building C object lib/fih/CMakeFiles/tfm_fih.dir/__/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 59%] Linking C static library libtfm_fih.a [ 59%] Built target tfm_fih Scanning dependencies of target platform_ns [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 59%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 60%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 60%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 60%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 60%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 60%] Building C object platform/CMakeFiles/platform_ns.dir/ext/common/uart_stdout.o [ 60%] Building C object platform/CMakeFiles/platform_ns.dir/ext/common/template/tfm_initial_attest_pub_key.o [ 60%] Linking C static library libplatform_ns.a [ 60%] Built target platform_ns Scanning dependencies of target tfm_api_ns [ 60%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_platform_ipc_api.o [ 61%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ps_ipc_api.o [ 61%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_its_ipc_api.o [ 61%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_crypto_ipc_api.o [ 61%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_initial_attestation_ipc_api.o [ 61%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_psa_ns_api.o [ 61%] Building C object app/CMakeFiles/tfm_api_ns.dir/tfm_ns_interface.o [ 61%] Linking C static library libtfm_api_ns.a [ 61%] Built target tfm_api_ns Scanning dependencies of target tfm_ns_log [ 61%] Building C object ns_log/CMakeFiles/tfm_ns_log.dir/tfm_log_raw.o [ 61%] Linking C static library libtfm_ns_log.a [ 61%] Built target tfm_ns_log Scanning dependencies of target tfm_test_suite_ipc_ns [ 61%] Building C object test/suites/ipc/CMakeFiles/tfm_test_suite_ipc_ns.dir/non_secure/ipc_ns_interface_testsuite.o [ 61%] Building C object test/suites/ipc/CMakeFiles/tfm_test_suite_ipc_ns.dir/__/__/framework/test_framework.o [ 61%] Building C object test/suites/ipc/CMakeFiles/tfm_test_suite_ipc_ns.dir/__/__/framework/test_framework_helpers.o [ 61%] Building C object test/suites/ipc/CMakeFiles/tfm_test_suite_ipc_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 61%] Linking C static library libtfm_test_suite_ipc_ns.a [ 61%] Built target tfm_test_suite_ipc_ns Scanning dependencies of target tfm_qcbor_test [ 61%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/float_tests.o [ 61%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/half_to_double_from_rfc7049.o [ 61%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_decode_tests.o [ 61%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_encode_tests.o [ 61%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/run_tests.o [ 61%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/UsefulBuf_Tests.o [ 62%] Linking C static library libtfm_qcbor_test.a [ 62%] Built target tfm_qcbor_test Scanning dependencies of target tfm_t_cose_ns [ 62%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_ns.dir/src/t_cose_sign1_sign.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_ns.dir/src/t_cose_sign1_verify.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_ns.dir/src/t_cose_util.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_ns.dir/src/t_cose_parameters.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_ns.dir/crypto_adapters/t_cose_psa_crypto.o [ 63%] Linking C static library libtfm_t_cose_ns.a [ 63%] Built target tfm_t_cose_ns Scanning dependencies of target tfm_t_cose_test [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/run_tests.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_psa_test_key.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_test_messages.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_sign_verify_test.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_test.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/src/t_cose_sign1_sign.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/src/t_cose_sign1_verify.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/src/t_cose_util.o [ 63%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/src/t_cose_parameters.o [ 64%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/crypto_adapters/t_cose_psa_crypto.o [ 64%] Linking C static library libtfm_t_cose_test.a [ 64%] Built target tfm_t_cose_test Scanning dependencies of target tfm_s_scatter [ 64%] Building C object platform/target/CMakeFiles/tfm_s_scatter.dir/__/__/__/common/gcc/tfm_common_s.o [ 64%] Built target tfm_s_scatter Scanning dependencies of target tfm_s [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/spm/cmsis_psa/tfm_psa_api_veneers.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_s.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/partitions/crypto/auto_generated/load_info_tfm_crypto.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/partitions/initial_attestation/auto_generated/load_info_tfm_initial_attestation.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/partitions/protected_storage/auto_generated/load_info_tfm_protected_storage.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/load_info_tfm_internal_trusted_storage.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/partitions/platform/auto_generated/load_info_tfm_platform.o [ 64%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/partitions/tfm_ffm11_partition/auto_generated/load_info_tfm_ffm11_partition.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/partitions/ns_proxy_partition/load_info_ns_proxy.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/partitions/idle_partition/load_info_idle_sp.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/test_services/tfm_core_test/auto_generated/load_info_tfm_ss_core_test.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/test_services/tfm_core_test_2/auto_generated/load_info_tfm_ss_core_test_2.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/test_services/tfm_ps_test_service/auto_generated/load_info_tfm_ps_test_service.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/test_services/tfm_ipc_service/auto_generated/load_info_tfm_ipc_service_test.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/test_services/tfm_ipc_client/auto_generated/load_info_tfm_ipc_client_test.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 65%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 66%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 66%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/psa/psa_client.o [ 66%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/psa/psa_service.o [ 66%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/psa/psa_lifecycle.o [ 66%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/log/tfm_log_raw.o [ 66%] Linking C executable ../bin/tfm_s.axf Memory region Used Size Region Size %age Used FLASH: 157740 B 235712 B 66.92% RAM: 72096 B 127 KB 55.44% VENEERS: 96 B 832 B 11.54% [ 66%] Built target tfm_s [ 67%] Generating s_veneers.o Scanning dependencies of target tfm_s_veneers [ 67%] Generating s_veneers.o [ 67%] Linking C static library libtfm_s_veneers.a [ 67%] Built target tfm_s_veneers Scanning dependencies of target tfm_test_suite_attestation_ns [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_public_key.o [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_test.o [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_common.o [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_asymmetric.o [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/non_secure/attest_asymmetric_ns_interface_testsuite.o [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/lib/ext/t_cose/src/t_cose_sign1_sign.o [ 67%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/lib/ext/t_cose/src/t_cose_sign1_verify.o [ 68%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/lib/ext/t_cose/src/t_cose_util.o [ 68%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/lib/ext/t_cose/src/t_cose_parameters.o [ 68%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/lib/ext/t_cose/crypto_adapters/t_cose_psa_crypto.o [ 68%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework.o [ 68%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_helpers.o [ 68%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 68%] Linking C static library libtfm_test_suite_attestation_ns.a [ 68%] Built target tfm_test_suite_attestation_ns Scanning dependencies of target tfm_test_suite_crypto_ns [ 68%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/crypto_tests_common.o [ 68%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/non_secure/crypto_ns_interface_testsuite.o [ 68%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework.o [ 69%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_helpers.o [ 69%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 69%] Linking C static library libtfm_test_suite_crypto_ns.a [ 69%] Built target tfm_test_suite_crypto_ns Scanning dependencies of target tfm_test_suite_its_ns [ 69%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/its_tests_common.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/non_secure/psa_its_ns_interface_testsuite.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_helpers.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Config/RTX_Config.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Source/rtx_lib.o [ 70%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/app/os_wrapper_cmsis_rtos_v2.o [ 70%] Linking C static library libtfm_test_suite_its_ns.a [ 70%] Built target tfm_test_suite_its_ns Scanning dependencies of target tfm_test_suite_qcbor_ns [ 71%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/non_secure/qcbor_ns_testsuite.o [ 71%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework.o [ 71%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_helpers.o [ 71%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 71%] Linking C static library libtfm_test_suite_qcbor_ns.a [ 71%] Built target tfm_test_suite_qcbor_ns Scanning dependencies of target tfm_test_suite_ps_ns [ 71%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/ns_test_helpers.o [ 71%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/psa_ps_ns_interface_testsuite.o [ 71%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework.o [ 71%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_helpers.o [ 71%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 71%] Linking C static library libtfm_test_suite_ps_ns.a [ 71%] Built target tfm_test_suite_ps_ns Scanning dependencies of target tfm_test_suite_t_cose_ns [ 71%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/non_secure/t_cose_ns_testsuite.o [ 71%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework.o [ 71%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_helpers.o [ 71%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 72%] Linking C static library libtfm_test_suite_t_cose_ns.a [ 72%] Built target tfm_test_suite_t_cose_ns Scanning dependencies of target tfm_test_suite_platform_ns [ 72%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/platform_tests_common.o [ 72%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/non_secure/platform_ns_interface_testsuite.o [ 73%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework.o [ 73%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_helpers.o [ 73%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 73%] Linking C static library libtfm_test_suite_platform_ns.a [ 73%] Built target tfm_test_suite_platform_ns Scanning dependencies of target tfm_test_suite_core_ns [ 73%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_positive_testsuite.o [ 73%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_test_api.o [ 73%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework.o [ 74%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_helpers.o [ 74%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 74%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/non_secure_suites.o [ 74%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Config/RTX_Config.o [ 74%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Source/rtx_lib.o [ 74%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/app/os_wrapper_cmsis_rtos_v2.o [ 74%] Linking C static library libtfm_test_suite_core_ns.a [ 74%] Built target tfm_test_suite_core_ns Scanning dependencies of target tfm_ns_integration_test [ 74%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/tfm_integ_test.o [ 74%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/non_secure_suites.o [ 74%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework.o [ 74%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_helpers.o [ 75%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_integ_test_helper.o [ 75%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Config/RTX_Config.o [ 75%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Source/rtx_lib.o [ 75%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/os_wrapper_cmsis_rtos_v2.o [ 75%] Linking C static library libtfm_ns_integration_test.a [ 75%] Built target tfm_ns_integration_test Scanning dependencies of target tfm_ns_scatter [ 75%] Building C object platform/target/CMakeFiles/tfm_ns_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_ns.o [ 75%] Built target tfm_ns_scatter Scanning dependencies of target tfm_ns [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/main_ns.o [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_ns.o [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Config/RTX_Config.o [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/CMSIS/RTOS2/RTX/Source/rtx_lib.o [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/os_wrapper_cmsis_rtos_v2.o [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/non_secure_suites.o [ 75%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework.o [ 76%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_helpers.o [ 76%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_integ_test_helper.o [ 76%] Linking C executable ../bin/tfm_ns.axf Memory region Used Size Region Size %age Used FLASH: 130120 B 163 KB 77.96% RAM: 30368 B 128 KB 23.17% [ 76%] Built target tfm_ns Scanning dependencies of target tfm_ns_hex [ 76%] Generating ../bin/tfm_ns.hex [ 76%] Built target tfm_ns_hex Scanning dependencies of target tfm_ns_bin [ 76%] Generating ../bin/tfm_ns.bin [ 76%] Built target tfm_ns_bin Scanning dependencies of target tfm_ns_elf [ 76%] Generating ../bin/tfm_ns.elf [ 76%] Built target tfm_ns_elf Scanning dependencies of target tfm_ns_binaries [ 76%] Built target tfm_ns_binaries Scanning dependencies of target tfm_s_hex [ 76%] Generating ../bin/tfm_s.hex [ 76%] Built target tfm_s_hex Scanning dependencies of target tfm_s_bin [ 76%] Generating ../bin/tfm_s.bin [ 76%] Built target tfm_s_bin Scanning dependencies of target tfm_s_elf [ 76%] Generating ../bin/tfm_s.elf [ 76%] Built target tfm_s_elf Scanning dependencies of target tfm_s_binaries [ 76%] Built target tfm_s_binaries Scanning dependencies of target crypto_service_mbedx509 [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509.o [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_create.o [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crl.o [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crt.o [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_csr.o [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_crt.o [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_csr.o [ 76%] Linking C static library libmbedx509.a [ 76%] Built target crypto_service_mbedx509 Scanning dependencies of target crypto_service_mbedtls [ 76%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/debug.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/net_sockets.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cache.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ciphersuites.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cli.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cookie.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_msg.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_srv.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ticket.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_tls.o [ 77%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_tls13_keys.o [ 78%] Linking C static library libmbedtls.a [ 78%] Built target crypto_service_mbedtls Scanning dependencies of target bl2_scatter [ 78%] Building C object platform/target/CMakeFiles/bl2_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_bl2.o [ 78%] Built target bl2_scatter Scanning dependencies of target platform_bl2 [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/boot_hal.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/tfm_low_level_security.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/low_level_device.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc_ex.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 80%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_hash_ex.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pka.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng_ex.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/boot_hal.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/uart_stdout.o [ 81%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/nv_counters.o [ 82%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_rotpk.o [ 82%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 82%] Linking C static library libplatform_bl2.a [ 82%] Built target platform_bl2 Scanning dependencies of target bl2_crypto_hw [ 82%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/rsa_alt.o [ 82%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [ 82%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [ 82%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [ 82%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/md5_alt.o [ 82%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [ 83%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [ 83%] Building C object platform/ext/accelerator/CMakeFiles/bl2_crypto_hw.dir/__/target/stm/common/stm32l5xx/accelerator/stm.o [ 83%] Linking C static library libbl2_crypto_hw.a [ 83%] Built target bl2_crypto_hw Scanning dependencies of target bl2_mbedcrypto [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aes.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aesni.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aria.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1parse.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1write.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/base64.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/bignum.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/camellia.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ccm.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chacha20.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chachapoly.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher_wrap.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cmac.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ctr_drbg.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/des.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/dhm.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdh.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdsa.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecjpake.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp_curves.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy_poll.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/error.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/gcm.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hkdf.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hmac_drbg.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md5.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/memory_buffer_alloc.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/mps_reader.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/mps_trace.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/nist_kw.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/oid.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/padlock.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pem.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk_wrap.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs12.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs5.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkparse.o [ 87%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkwrite.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform_util.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/poly1305.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_aead.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_cipher.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_client.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_driver_wrappers.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_ecp.o [ 88%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_hash.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_mac.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_rsa.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_se.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_slot_management.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_storage.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_its_file.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ripemd160.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa.o [ 89%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa_alt_helpers.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha1.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha256.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha512.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/threading.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/timing.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version_features.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [ 90%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/md5_alt.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/stm.o [ 91%] Linking C static library libmbedcrypto.a [ 91%] Built target bl2_mbedcrypto Scanning dependencies of target bootutil [ 91%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/boot_record.o [ 91%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/bootutil_misc.o [ 91%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/bootutil_public.o [ 91%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/caps.o [ 91%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/encrypted.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening_delay_rng_mbedtls.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec256.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ed25519.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_rsa.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_validate.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/loader.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_misc.o [ 92%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_move.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_scratch.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/tlv.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/md5_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/stm.o [ 94%] Linking C static library libbootutil.a [ 94%] Built target bootutil Scanning dependencies of target bl2 [ 94%] Building C object bl2/CMakeFiles/bl2.dir/src/security_cnt.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/src/flash_map.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/bl2_main.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/keys.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_extended.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_legacy.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_bl2.o [ 94%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/bl2/low_level_ospi_device.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_ospi_flash.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_ospi.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/Components/mx25lm51245g/mx25lm51245g.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/stm32l562e_dk/src/stm32l562e_discovery_ospi.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/md5_alt.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [ 96%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [ 96%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/accelerator/stm.o [ 96%] Linking C executable ../bin/bl2.axf Memory region Used Size Region Size %age Used FLASH: 41968 B 66 KB 62.10% FLASH_NOHDP: 244 B 6 KB 3.97% RAM: 27336 B 63 KB 42.37% [ 96%] Built target bl2 Scanning dependencies of target bl2_elf [ 96%] Generating ../bin/bl2.elf [ 96%] Built target bl2_elf Scanning dependencies of target bl2_hex [ 96%] Generating ../bin/bl2.hex [ 96%] Built target bl2_hex Scanning dependencies of target bl2_bin [ 96%] Generating ../bin/bl2.bin [ 96%] Built target bl2_bin Scanning dependencies of target bl2_binaries [ 96%] Built target bl2_binaries Scanning dependencies of target signing_layout_s [ 96%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_s.dir/signing_layout_s.o [ 96%] Built target signing_layout_s Scanning dependencies of target signing_layout_ns [ 96%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_ns.dir/signing_layout_ns.o [ 96%] Built target signing_layout_ns Scanning dependencies of target tfm_s_signed_bin [ 96%] Generating tfm_s_signed.bin [ 96%] Built target tfm_s_signed_bin Scanning dependencies of target tfm_ns_signed_bin [ 96%] Generating tfm_ns_signed.bin [ 96%] Built target tfm_ns_signed_bin Scanning dependencies of target tfm_s_ns_signed_bin [ 96%] Generating tfm_s_ns_signed.bin [ 96%] Built target tfm_s_ns_signed_bin Scanning dependencies of target signed_images [ 96%] Built target signed_images Scanning dependencies of target bl2_mbedx509 [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_create.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_crl.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_crt.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_csr.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_crt.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_csr.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.o /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.c: In function 'mbedtls_rsa_private': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.c:1182:24: warning: unused parameter 'p_rng' [-Wunused-parameter] 1182 | void *p_rng, | ~~~~~~^~~~~ [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/md5_alt.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/stm.o [ 98%] Linking C static library libmbedx509.a [ 98%] Built target bl2_mbedx509 Scanning dependencies of target bl2_mbedtls [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/debug.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/net_sockets.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cache.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ciphersuites.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cli.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cookie.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_msg.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_srv.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ticket.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_tls.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_tls13_keys.o [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.o /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.c: In function 'mbedtls_rsa_private': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/rsa_alt.c:1182:24: warning: unused parameter 'p_rng' [-Wunused-parameter] 1182 | void *p_rng, | ~~~~~~^~~~~ [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecdsa_alt.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_alt.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/ecp_curves_alt.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/md5_alt.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha1_alt.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/sha256_alt.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/ext/target/stm/common/stm32l5xx/accelerator/stm.o [100%] Linking C static library libmbedtls.a [100%] Built target bl2_mbedtls Install the project... -- Install configuration: "Release" -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/secure_fw/partitions/crypto/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/secure_fw/partitions/crypto/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/secure_fw/partitions/crypto/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/bl2/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/bl2/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/bl2/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/scripts/stm_tool.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/scripts/bin2hex.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/regression.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/preprocess.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/TFM_UPDATE.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/TFM_BIN2HEX.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/postbuild.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/flash_layout.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/region_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/image_macros_to_preprocess_bl2.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/bl2.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_ns.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/bl2.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_ns.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32 L562E_DK/tfm_ns.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/bl2.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_ns.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/bl2.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/bl2.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_ns.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/outputs/STM/STM32L562E_DK/tfm_s.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/lib/s_veneers.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/client.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/error.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa_manifest/sid.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/tfm_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/tfm_ns_interface.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/ext/tz_context.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/tfm_psa_call_param.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/protected_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/internal_trusted_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/storage_common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_extra.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_compat.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_client_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_sizes.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_types.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/crypto_values.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/tfm_crypto_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/psa/initial_attestation.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/include/tfm_platform_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_psa_ns_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_ns_interface.c.example -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_ps_ipc_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_its_ipc_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_crypto_ipc_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_initial_attestation_ipc_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/interface/src/tfm_platform_ipc_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/assemble.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/__pycache__ -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/__pycache__/macro_parser.cpython-36.pyc -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/requirements.txt -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/wrapper -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/scripts/wrapper/wrapper.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/layout_files/signing_layout_s.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/layout_files/signing_layout_ns.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_test/install/image_signing/keys/root-RSA-3072_1.pem Best Regards, Poppy Wu Macronix Microelectronics (Suzhou) Co.,Ltd http://www.mxic.com.cn<http://www.mxic.com.cn/> CONFIDENTIALITY NOTE: This e-mail and any attachments may contain confidential information and/or personal data, which is protected by applicable laws. Please be reminded that duplication, disclosure, distribution, or use of this e-mail (and/or its attachments) or any part thereof is prohibited. If you receive this e-mail in error, please notify us immediately and delete this mail as well as its attachment(s) from your system. In addition, please be informed that collection, processing, and/or use of personal data is prohibited unless expressly permitted by personal data protection laws. Thank you for your attention and cooperation. Macronix International Co., Ltd. ===================================================================== -- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m-- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m ============================================================================ CONFIDENTIALITY NOTE: This e-mail and any attachments may contain confidential information and/or personal data, which is protected by applicable laws. Please be reminded that duplication, disclosure, distribution, or use of this e-mail (and/or its attachments) or any part thereof is prohibited. If you receive this e-mail in error, please notify us immediately and delete this mail as well as its attachment(s) from your system. In addition, please be informed that collection, processing, and/or use of personal data is prohibited unless expressly permitted by personal data protection laws. Thank you for your attention and cooperation. Macronix International Co., Ltd. =====================================================================

4 years, 7 months

2
1
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

TF-M