- TF-M - lists.trustedfirmware.org

PEM format is enabled in crypto service by default

by Sherry Zhang

Hi, I want to talk about whether TFM should support the PEM key format in crypto operation. In the PSA crypto spec, it describes: ``` This specification supports a single format for each key type. Implementations may support other formats as long as the standard format is supported. ``` The PEM format is not the standard format described in the spec. However, in the tfm_mbedcrypto_config_default.h, the MBEDTLS_PEM_PARSE_C and the MBEDTLS_PEM_WRITE_C is defined which leads to that PEM key format operation is enabled in TFM crypto service. In isolation level1, about more than 2000 bytes code is introduced by this feature: .ER_TFM_CODE 0x2a01c // MBEDTLS_PEM_PARSE_C and the MBEDTLS_PEM_WRITE_C enabled .ER_TFM_CODE 0x29848 // MBEDTLS_PEM_PARSE_C and the MBEDTLS_PEM_WRITE_C disabled Is it necessary to support the PEM format in the key operation in crypto service at the cost of more than 2000 bytes? Any comments on that? Regards, Sherry Zhang

3 years, 11 months

1
0
0 0

Questions about psa crypto persistent key

by Edward Yang

Hi Experts, I have some questions about crypto persisten keys. 1. psa_open_key() is removed in psa crypto spec,so it is impossible to import a persistent key into key slot with key_id,which means encrypt/decrypt data directly with a persistent key is not allowed,these persistent keys can only be used to derive volatile keys which will be used for encryption/decryption, I am not sure if I understand correctly. 2. Besides,HUK can be used to derive the other crypto keys,such as ps crypto key.HUK may be stored in OTP area of MCU(without crypto element such as cc312),then what's intended flow to derive crypto keys from HUK via calling PSA crypto service?There is no reference implementation in tf-m code. tfm_plat_get_huk_derived_key(){ get HUK from OTP || || \/ how to derive crypto key from HUK with calling crypto service? } 3. BTW,HUK has a persistent key id TFM_CRYPTO_KEY_ID_HUK defined in tfm_crypto_defs.h,but I haven't seen any reference to this macro. What's the intended use of this key id?And what's the key owner of HUK? 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

Re: [TF-M] Technical Forum call - May 27

by Anton Komlev

Hi, The agenda for the forum: 1. Linker script/scatter file templating (Ken Liu) 2. Discussion on Non-Secure Client ID update (David Wang). 3. AOB Regards, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Wednesday, May 19, 2021 6:21 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - May 27 Hi, The next Technical Forum is planned on Thursday, May 27 , 07:00-08: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

3 years, 11 months

1
0
0 0

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

by Andrew Thoelke

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> On Behalf Of Suresh Marisetty via TF-M Sent: 25 May 2021 02:37 To: Sherry Zhang <Sherry.Zhang2(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 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>

3 years, 11 months

2
1
0 0

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

by Sherry Zhang

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> On Behalf Of Suresh Marisetty via TF-M Sent: Thursday, May 13, 2021 11:09 AM To: tf-m(a)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>

3 years, 11 months

2
4
0 0

Re: [TF-M] A question on tfm its filesystem

by David Hu

Hi Poppy, SPRT requires the shared library shall not own static R/W data. ITS filesystem may not satisfy this requirement. Usually, a SP, for example Protected Storage, can rely on ITS service to access data in non-volatile memory. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: Monday, May 24, 2021 12:54 PM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] A question on tfm its filesystem Hi, I'd like to ask a question to see if the filesystem part of tf-m its partition can be moved to lib/sprt folder,to make this filesystem a shared library for PRoT part of tfm. Therefore,besides its partition, other extra secure partitions can also make use of this filesystem. 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, 11 months

2
2
0 0

Wiki page sorting out

by Ken Liu

Hi, There are some out of sync contents in the wiki page (mainly the design chapter), which needs to be cleaned a bit. https://developer.trustedfirmware.org/w/tf_m/ As the first step, the following article would be removed (Would move to a recyclable place at first): Cooperative Scheduling Rules - content out of date. Non-Secure Interrupt Handling - covered in the design document. Secure Partition Interrupt Handling - covered in the interrupt handling document. Service IPC compatibility - Attestation - low priority, no need to be a standalone item. Service IPC compatibility - SST - same as above. Trusted Firmware-m Isolation Level 2 - covered by document 'FF-M isolation'. Uniform Secure Service Signature - out of date, as most of related files are changed. Any comments please feel free to ping me. Would do this on Thursday (27th May) this week. Thanks. /Ken

3 years, 11 months

1
0
0 0

A question on tfm its filesystem

by Edward Yang

Hi, I'd like to ask a question to see if the filesystem part of tf-m its partition can be moved to lib/sprt folder,to make this filesystem a shared library for PRoT part of tfm. Therefore,besides its partition, other extra secure partitions can also make use of this filesystem. 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, 11 months

1
0
0 0

Re: [TF-M] A question on Arm linker - GCC NOLOAD equivalent

by Gyorgy Szing

Hi, Just a guess, but the "UNINIT" attribute described here [1] might be the one you are looking for. [1] https://developer.arm.com/documentation/100070/0612/scatter-file-syntax/exe… /George From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: 21 May 2021 03:22 To: Suresh.Marisetty(a)infineon.com; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] A question on Arm linker - GCC NOLOAD equivalent Hi Suresh, Could you please forward the question to Arm complier forum (https://community.arm.com/developer/tools-software/tools/f/arm-compilers-fo… I believe they can provide a more comprehensive answer. Best regards, Hu Ziji 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, May 21, 2021 12:13 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] A question on Arm linker - GCC NOLOAD equivalent Wondering if anybody can answer this (may not be the right forum): >>I need the equivalent of the gcc NOLOAD attribute with armlink linker 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>

3 years, 12 months

1
0
0 0

Re: [TF-M] A question on Arm linker - GCC NOLOAD equivalent

by David Hu

Hi Suresh, Could you please forward the question to Arm complier forum (https://community.arm.com/developer/tools-software/tools/f/arm-compilers-fo… I believe they can provide a more comprehensive answer. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Suresh Marisetty via TF-M Sent: Friday, May 21, 2021 12:13 AM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] A question on Arm linker - GCC NOLOAD equivalent Wondering if anybody can answer this (may not be the right forum): >>I need the equivalent of the gcc NOLOAD attribute with armlink linker 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>

3 years, 12 months

1
0
0 0

A question on Arm linker - GCC NOLOAD equivalent

by Suresh.Marisetty＠infineon.com

Wondering if anybody can answer this (may not be the right forum): >>I need the equivalent of the gcc NOLOAD attribute with armlink linker 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>

3 years, 12 months

1
0
0 0

Tentative future TF-M release dates

by Shebu Varghese Kuriakose

Hi All, As many might know, TF-M is now making release tags around every 4 months as defined here<https://ci-builds.trustedfirmware.org/static-files/TZFdL484qZZgYcbWIGLS09zb…>. In order to help contributors and users of Trusted Firmware-M releases, the code freeze and release dates of the next 2 releases are published here<https://ci-builds.trustedfirmware.org/static-files/TZFdL484qZZgYcbWIGLS09zb…> (TF-M -> Docs -> Future release plans) Note that these dates are tentative and can shift if issues are identified leading upto the release. Regards, Shebu

3 years, 12 months

1
0
0 0

Technical Forum call - May 27

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, May 27 , 07:00-08: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

3 years, 12 months

1
0
0 0

CMSIS_5 pack cloning issue in old TF-M version

by Anton Komlev

Hi, Some of you using TF-M v1.0 or earlier may have experienced build failures recently because of the CMSIS_5 repo git-lfs quota. To avoid this issue, it is recommended to either update to the latest TF-M version or to manually download the CMSIS_5 pack without using git-lfs. TF-M only uses a small part of the CMSIS_5 pack for testing purposes. To avoid cloning the entire CMSIS_5 pack, TF-M has been using a forked copy of the required RTX libraries in the tf-m-tests repo since v1.1 so updating to any TF-M version including and after v1.1 is fine. Hope that helps, Anton K.

3 years, 12 months

1
0
0 0

Re: [TF-M] Factory provisioning with tf-m

by Tamas Ban

Hi Poppy, There is no reference implementation for the case when only attest service can access to IAK, which is stored in on-chip flash. Attest code is part of PRoT code, they have the same privileged level. Tamas From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: 2021. május 18., kedd 6:07 To: David Wang <David.Wang(a)arm.com>; Raef Coles <Raef.Coles(a)arm.com>; tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] Factory provisioning with tf-m Hi Raef and David, Thanks for the detailed explanation. As I understand it,in the scenario without CC312 ,these keys(HUK,IAK,RoTPK) can be stored in secure-privileged area(using SAU and MPU) of embedded flash during factory provisioning,so these keys cannot be accessed by ARoT and non-secure code. But how to make IAK accessible only to the Initial Attestation Service？Is there any reference implementation? Best Regards, Poppy Wu Macronix Microelectronics (Suzhou) Co.,Ltd Http: //www.mxic.com.cn David Wang <David.Wang(a)arm.com<mailto:David.Wang@arm.com>> 2021/05/17 20:54 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>>, Edward Yang <EdwardYang(a)mxic.com.cn<mailto:EdwardYang@mxic.com.cn>> cc nd <nd(a)arm.com<mailto:nd@arm.com>> Subject Re: [TF-M] Factory provisioning with tf-m Hi Poppy, One more thing about IAK, it's defined as one of the immutable PSA parameters in PSA security model document. And "To prevent cloning or spoofing, the IAK must be secret and accessible only to the Initial Attestation Service." In that case, for the product, you may need to consider how to ensure confidentiality/integrity and it's immutable based on the embedded flash solution. Regards, David Wang ARM Electronic Technology (Shanghai) Co., Ltd Phone: +86-21-6154 9142 (ext. 59142) ________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> on behalf of Raef Coles via TF-M <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Sent: 17 May 2021 16:50 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>>; Edward Yang <EdwardYang(a)mxic.com.cn<mailto:EdwardYang@mxic.com.cn>> Subject: Re: [TF-M] Factory provisioning with tf-m Hi Poppy. The current code we use for provisioning the CC312 OTP on the Musca reference platforms is under platform/ext/accelerator/cc312/cc312_provisioning.c, and the code for using keys from OTP is at platform/ext/target/musca_b1/sse_200/crypto_keys.c Note that because the Musca S1 has volatile OTP memory (I think it's a design choice that makes sense on a dev-board) a workaround is used, for the reference implementation it's best to look at the Musca B1. The basic flow is: * Build TF-M with -DCRYPTO_HW_ACCELERATOR_OTP_STATE=PROVISIONING, which will cause an ifdef in the bootloader to jump to the provisioning code instead of TF-M * TF-M then generates a 256 bit AES HUK and an ECC_P256 private key using the code in cc312_provisioning.c, and program these key into the OTP memory of the CC312 * Programming these keys into OTP causes the lifecycle state to be changed, so a reboot is needed between programming the keys to allow the new LCS to be used * The board is now provisioned - building TF-M with * -DCRYPTO_HW_ACCELERATOR_OTP_STATE=ON will cause TF-M to use the HUK, IAK and ROTPK from OTP, and will derive the SST/PS keys from the HUK on boot The general idea is that a platform can provide it's own implementation of the platform/ext/common/template/crypto_keys.c file, which could then load the keys from wherever they've been provisioned. I'd say it's reasonable to program keys into any NV storage region that is internal to the chip itself (and hence safe from tampering), which would include embedded flash. You'd then just need to load that data from flash in crypto_keys.c. Note that it would also be necessary to prevent secure partitions / non-secure code from directly accessing the flash where the keys are stored, probably by using an mpc/ppc to make it only accessible by secure-privileged code. Let me know if you have any other questions about the current CC312 provisioning flow. Raef ________________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> on behalf of Edward Yang via TF-M <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Sent: 14 May 2021 10:04 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] Factory provisioning with tf-m Hi, I would like to know about how to use tf-m with factory provisioning,for example,HUK,IAK,ROTPK these ROT assets should be injected to device via factory provisioning,besides,application specific certificates and private keys can also be injected during this procedure,in tf-m roadmap,there is a provision service,what's the functionality of this service? In initial attestation service, attest_register_initial_attestation_key() calls tfm_plat_get_symmetric_iak() to get IAK, I found implementation template of tfm_plat_get_symmetric_iak() just copys hardcoded key value(for developer mode). I think this is not allowed in production mode.Is there any recommended implementation of this API? What if I stored IAK in a specific address of MCU embedded flash during factory provisioning, such as #define IAK_REGION IAK_base_addr in flash_layout.h,and then use flash.read get the key value？ tfm_plat_get_symmetric_iak( ) { TFM_HAL_ITS_FLASH_DRIVER.ReadData(IAK_REGION, buff, size); } 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. ===================================================================== -- TF-M mailing list TF-M(a)lists.trustedfirmware.org<mailto:TF-M@lists.trustedfirmware.org> https://lists.trustedfirmware.org/mailman/listinfo/tf-m

3 years, 12 months

1
0
0 0

Re: [TF-M] Factory provisioning with tf-m

by David Wang

Hi Poppy, One more thing about IAK, it's defined as one of the immutable PSA parameters in PSA security model document. And "To prevent cloning or spoofing, the IAK must be secret and accessible only to the Initial Attestation Service." In that case, for the product, you may need to consider how to ensure confidentiality/integrity and it's immutable based on the embedded flash solution. Regards, David Wang ARM Electronic Technology (Shanghai) Co., Ltd Phone: +86-21-6154 9142 (ext. 59142) ________________________________ 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: 17 May 2021 16:50 To: tf-m(a)lists.trustedfirmware.org <tf-m(a)lists.trustedfirmware.org>; Edward Yang <EdwardYang(a)mxic.com.cn> Subject: Re: [TF-M] Factory provisioning with tf-m Hi Poppy. The current code we use for provisioning the CC312 OTP on the Musca reference platforms is under platform/ext/accelerator/cc312/cc312_provisioning.c, and the code for using keys from OTP is at platform/ext/target/musca_b1/sse_200/crypto_keys.c Note that because the Musca S1 has volatile OTP memory (I think it's a design choice that makes sense on a dev-board) a workaround is used, for the reference implementation it's best to look at the Musca B1. The basic flow is: * Build TF-M with -DCRYPTO_HW_ACCELERATOR_OTP_STATE=PROVISIONING, which will cause an ifdef in the bootloader to jump to the provisioning code instead of TF-M * TF-M then generates a 256 bit AES HUK and an ECC_P256 private key using the code in cc312_provisioning.c, and program these key into the OTP memory of the CC312 * Programming these keys into OTP causes the lifecycle state to be changed, so a reboot is needed between programming the keys to allow the new LCS to be used * The board is now provisioned - building TF-M with * -DCRYPTO_HW_ACCELERATOR_OTP_STATE=ON will cause TF-M to use the HUK, IAK and ROTPK from OTP, and will derive the SST/PS keys from the HUK on boot The general idea is that a platform can provide it's own implementation of the platform/ext/common/template/crypto_keys.c file, which could then load the keys from wherever they've been provisioned. I'd say it's reasonable to program keys into any NV storage region that is internal to the chip itself (and hence safe from tampering), which would include embedded flash. You'd then just need to load that data from flash in crypto_keys.c. Note that it would also be necessary to prevent secure partitions / non-secure code from directly accessing the flash where the keys are stored, probably by using an mpc/ppc to make it only accessible by secure-privileged code. Let me know if you have any other questions about the current CC312 provisioning flow. 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: 14 May 2021 10:04 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Factory provisioning with tf-m Hi, I would like to know about how to use tf-m with factory provisioning,for example,HUK,IAK,ROTPK these ROT assets should be injected to device via factory provisioning,besides,application specific certificates and private keys can also be injected during this procedure,in tf-m roadmap,there is a provision service,what's the functionality of this service? In initial attestation service, attest_register_initial_attestation_key() calls tfm_plat_get_symmetric_iak() to get IAK, I found implementation template of tfm_plat_get_symmetric_iak() just copys hardcoded key value(for developer mode). I think this is not allowed in production mode.Is there any recommended implementation of this API? What if I stored IAK in a specific address of MCU embedded flash during factory provisioning, such as #define IAK_REGION IAK_base_addr in flash_layout.h,and then use flash.read get the key value？ tfm_plat_get_symmetric_iak( ) { TFM_HAL_ITS_FLASH_DRIVER.ReadData(IAK_REGION, buff, size); } 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. ===================================================================== -- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m

3 years, 12 months

2
1
0 0

MbedTLS version updated to 2.26.0

by Maulik Patel

Hello All, TF-M has been updated to work with MbedTLS version 2.26.0. Best Regards Maulik Patel

3 years, 12 months

1
0
0 0

Re: [TF-M] Factory provisioning with tf-m

by Raef Coles

Hi Poppy. The current code we use for provisioning the CC312 OTP on the Musca reference platforms is under platform/ext/accelerator/cc312/cc312_provisioning.c, and the code for using keys from OTP is at platform/ext/target/musca_b1/sse_200/crypto_keys.c Note that because the Musca S1 has volatile OTP memory (I think it's a design choice that makes sense on a dev-board) a workaround is used, for the reference implementation it's best to look at the Musca B1. The basic flow is: * Build TF-M with -DCRYPTO_HW_ACCELERATOR_OTP_STATE=PROVISIONING, which will cause an ifdef in the bootloader to jump to the provisioning code instead of TF-M * TF-M then generates a 256 bit AES HUK and an ECC_P256 private key using the code in cc312_provisioning.c, and program these key into the OTP memory of the CC312 * Programming these keys into OTP causes the lifecycle state to be changed, so a reboot is needed between programming the keys to allow the new LCS to be used * The board is now provisioned - building TF-M with * -DCRYPTO_HW_ACCELERATOR_OTP_STATE=ON will cause TF-M to use the HUK, IAK and ROTPK from OTP, and will derive the SST/PS keys from the HUK on boot The general idea is that a platform can provide it's own implementation of the platform/ext/common/template/crypto_keys.c file, which could then load the keys from wherever they've been provisioned. I'd say it's reasonable to program keys into any NV storage region that is internal to the chip itself (and hence safe from tampering), which would include embedded flash. You'd then just need to load that data from flash in crypto_keys.c. Note that it would also be necessary to prevent secure partitions / non-secure code from directly accessing the flash where the keys are stored, probably by using an mpc/ppc to make it only accessible by secure-privileged code. Let me know if you have any other questions about the current CC312 provisioning flow. 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: 14 May 2021 10:04 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Factory provisioning with tf-m Hi, I would like to know about how to use tf-m with factory provisioning,for example,HUK,IAK,ROTPK these ROT assets should be injected to device via factory provisioning,besides,application specific certificates and private keys can also be injected during this procedure,in tf-m roadmap,there is a provision service,what's the functionality of this service? In initial attestation service, attest_register_initial_attestation_key() calls tfm_plat_get_symmetric_iak() to get IAK, I found implementation template of tfm_plat_get_symmetric_iak() just copys hardcoded key value(for developer mode). I think this is not allowed in production mode.Is there any recommended implementation of this API? What if I stored IAK in a specific address of MCU embedded flash during factory provisioning, such as #define IAK_REGION IAK_base_addr in flash_layout.h,and then use flash.read get the key value？ tfm_plat_get_symmetric_iak( ) { TFM_HAL_ITS_FLASH_DRIVER.ReadData(IAK_REGION, buff, size); } 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, 12 months

1
0
0 0

Re: [TF-M] Factory provisioning with tf-m

by Edward Yang

Hi Shebu, Thanks for your reply.I would like to know is there any reference usage example of tf-m available now? Best Regards, Poppy Wu Macronix Microelectronics (Suzhou) Co.,Ltd Http: //www.mxic.com.cn ----- Forwarded by Edward Yang/CHINA/MXIC on 2021/05/17 11:56 ----- Shebu Varghese Kuriakose <Shebu.VargheseKuriakose(a)arm.com> 2021/05/15 01:19 To Edward Yang <EdwardYang(a)mxic.com.cn>, "tf-m(a)lists.trustedfirmware.org" <tf-m(a)lists.trustedfirmware.org> cc nd <nd(a)arm.com> Subject RE: [TF-M] Factory provisioning with tf-m Hi Poppy, In the roadmap, provisioning service is noted incase there is any standard provisioning mechanism that PSA defines in future. There is no plans around provisioning at this point. It is upto the platform to generate the keys and provision it securely on the device which TF-M can make use of. On Arm reference platforms, MuscaB1 and MuscaS1, the HUK, IAK are generated in Cryptocell-312. HUK, IAK private keys and ROTPK are provisioned in the OTP of CC-312. The hardcoding of keys in TF-M is just for development purposes and not to be used in production environment. Provisioning the attestation key in the secure region of the embedded flash might be acceptable. Experts in the list can comment. Regards, Shebu From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: Friday, May 14, 2021 10:04 AM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Factory provisioning with tf-m Hi, I would like to know about how to use tf-m with factory provisioning,for example,HUK,IAK,ROTPK these ROT assets should be injected to device via factory provisioning,besides,application specific certificates and private keys can also be injected during this procedure,in tf-m roadmap,there is a provision service,what's the functionality of this service? In initial attestation service, attest_register_initial_attestation_key() calls tfm_plat_get_symmetric_iak() to get IAK, I found implementation template of tfm_plat_get_symmetric_iak() just copys hardcoded key value(for developer mode). I think this is not allowed in production mode.Is there any recommended implementation of this API? What if I stored IAK in a specific address of MCU embedded flash during factory provisioning, such as #define IAK_REGION IAK_base_addr in flash_layout.h,and then use flash.read get the key value？ tfm_plat_get_symmetric_iak( ) { TFM_HAL_ITS_FLASH_DRIVER.ReadData(IAK_REGION, buff, size); } 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. ===================================================================== ============================================================================ 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, 12 months

1
0
0 0

Re: [TF-M] Factory provisioning with tf-m

by Shebu Varghese Kuriakose

Hi Poppy, In the roadmap, provisioning service is noted incase there is any standard provisioning mechanism that PSA defines in future. There is no plans around provisioning at this point. It is upto the platform to generate the keys and provision it securely on the device which TF-M can make use of. On Arm reference platforms, MuscaB1 and MuscaS1, the HUK, IAK are generated in Cryptocell-312. HUK, IAK private keys and ROTPK are provisioned in the OTP of CC-312. The hardcoding of keys in TF-M is just for development purposes and not to be used in production environment. Provisioning the attestation key in the secure region of the embedded flash might be acceptable. Experts in the list can comment. Regards, Shebu From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: Friday, May 14, 2021 10:04 AM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Factory provisioning with tf-m Hi, I would like to know about how to use tf-m with factory provisioning,for example,HUK,IAK,ROTPK these ROT assets should be injected to device via factory provisioning,besides,application specific certificates and private keys can also be injected during this procedure,in tf-m roadmap,there is a provision service,what's the functionality of this service? In initial attestation service, attest_register_initial_attestation_key() calls tfm_plat_get_symmetric_iak() to get IAK, I found implementation template of tfm_plat_get_symmetric_iak() just copys hardcoded key value(for developer mode). I think this is not allowed in production mode.Is there any recommended implementation of this API? What if I stored IAK in a specific address of MCU embedded flash during factory provisioning, such as #define IAK_REGION IAK_base_addr in flash_layout.h,and then use flash.read get the key value？ tfm_plat_get_symmetric_iak( ) { TFM_HAL_ITS_FLASH_DRIVER.ReadData(IAK_REGION, buff, size); } 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. =====================================================================

4 years

1
0
0 0

Re: [TF-M] Questions on Musca-B1 SE implementation

by David Hu

Hi @Mark Horvath<mailto:Mark.Horvath@arm.com>, Could you please help take a look at the following questions about Musca-B1 SE? Thanks 😊 Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Suresh Marisetty via TF-M Sent: Thursday, May 13, 2021 6:04 AM To: Tamas Ban <Tamas.Ban(a)arm.com>; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Questions on Musca-B1 SE implementation Hi Tamas, The following is good information. A few questions: 1. Is it correct to state that for the SE, the PSA RoT services do not have any software Crypto implementation, but leverage from CC-312? 2. What is the size of the TFM on the host (M33) with only PSA RoT service proxy with redirection to SE 3. Just trying to understand the TFM image size requirements on M33 vs. SE 4. How much of the Flash region/code Executed In Place vs. execution out of SRAM (XIP) thanks Suresh Marisetty Infineon Semiconductor Corporation From: Tamas Ban <Tamas.Ban(a)arm.com<mailto:Tamas.Ban@arm.com>> Sent: Friday, April 30, 2021 12:40 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: Questions on Musca-B1 SE implementation 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, Here is a link how to build images to Musca-B1 SE: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e… I have built with GCC and MinSizeRel build type: Profile Medium: Memory region Used Size Region Size %age Used FLASH: 101464 B 381 KB 26.01% RAM: 61304 B 64 KB 93.54% [100%] Built target tfm_s Profile Large: Memory region Used Size Region Size %age Used FLASH: 170448 B 381 KB 43.69% RAM: 62980 B 64 KB 96.10% [ 97%] Built target tfm_s The profiles means different capabilities of TF-M, they were introduced to support constrained devices as well, with limited capability. There is a detailed description about the profiles here: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/techn… BR, Tamas 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: 2021. április 29., csütörtök 21:49 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] Questions on Musca-B1 SE implementation I am following up on a question that came up on the TFM Core and MCUBoot image sizes that is built for SE on Musca-B1. We are trying to figure out the resource requirements for SE, to be able to host the TF-M as suggested in the slides below. Wondering if anyone throw more light on the RAM/FLASH requirements for it. Also, does the TFM profile small/medium/large map to this at all or is it different from them. Also, what’s are the estimated latencies of boot on SE with all the Flash accesses, etc. https://www.trustedfirmware.org/docs/Musca-B1-Secure-Enclave-Solution.pdf https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e… Any info on this would be appreciated. thanks Suresh Marisetty Infineon Semiconductor Corporation

4 years

2
1
0 0

Factory provisioning with tf-m

by Edward Yang

Hi, I would like to know about how to use tf-m with factory provisioning,for example,HUK,IAK,ROTPK these ROT assets should be injected to device via factory provisioning,besides,application specific certificates and private keys can also be injected during this procedure,in tf-m roadmap,there is a provision service,what's the functionality of this service? In initial attestation service, attest_register_initial_attestation_key() calls tfm_plat_get_symmetric_iak() to get IAK, I found implementation template of tfm_plat_get_symmetric_iak() just copys hardcoded key value(for developer mode). I think this is not allowed in production mode.Is there any recommended implementation of this API? What if I stored IAK in a specific address of MCU embedded flash during factory provisioning, such as #define IAK_REGION IAK_base_addr in flash_layout.h,and then use flash.read get the key value？ tfm_plat_get_symmetric_iak( ) { TFM_HAL_ITS_FLASH_DRIVER.ReadData(IAK_REGION, buff, size); } 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. =====================================================================

4 years

1
0
0 0

Re: [TF-M] Technical Forum call - May 13

by Anton Komlev

Hi, The agenda for the forum today: 1. How to use docker to build TFM on Windows and Linux by Hugo L'hostis 2. Linker script/scatter file templating (preliminary and tentative) 3. AOB Regards, Anton From: docker to build TFM on windows and Linux (It should take 10 to 15 minutes). <Hugo.Lhostis(a)arm.com> Sent: Wednesday, May 12, 2021 10:36 AM To: Anton Komlev <Anton.Komlev(a)arm.com> Cc: nd <nd(a)arm.com> Subject: RE: Technical Forum call - May 13 Hi Anton, I would like to speak about using docker to build TFM on windows and Linux (It should take 10 to 15 minutes). Best regards, Hugo 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: 06 May 2021 19:20 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 - May 13 Hi, The next Technical Forum is planned on Thursday, May 13, 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
0
0 0

Firmware update API - MCUboot update

by Suresh.Marisetty＠infineon.com

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

1
0
0 0

Re: [TF-M] Questions on Musca-B1 SE implementation

by Tamas Ban

Hi Suresh, Here is a link how to build images to Musca-B1 SE: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e… I have built with GCC and MinSizeRel build type: Profile Medium: Memory region Used Size Region Size %age Used FLASH: 101464 B 381 KB 26.01% RAM: 61304 B 64 KB 93.54% [100%] Built target tfm_s Profile Large: Memory region Used Size Region Size %age Used FLASH: 170448 B 381 KB 43.69% RAM: 62980 B 64 KB 96.10% [ 97%] Built target tfm_s The profiles means different capabilities of TF-M, they were introduced to support constrained devices as well, with limited capability. There is a detailed description about the profiles here: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/techn… BR, Tamas From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Suresh Marisetty via TF-M Sent: 2021. április 29., csütörtök 21:49 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Questions on Musca-B1 SE implementation I am following up on a question that came up on the TFM Core and MCUBoot image sizes that is built for SE on Musca-B1. We are trying to figure out the resource requirements for SE, to be able to host the TF-M as suggested in the slides below. Wondering if anyone throw more light on the RAM/FLASH requirements for it. Also, does the TFM profile small/medium/large map to this at all or is it different from them. Also, what's are the estimated latencies of boot on SE with all the Flash accesses, etc. https://www.trustedfirmware.org/docs/Musca-B1-Secure-Enclave-Solution.pdf https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e… Any info on this would be appreciated. thanks Suresh Marisetty Infineon Semiconductor Corporation

4 years

2
1
0 0

Security vulnerability notice - abort() function may not take effect in TF-M Crypto multi-part operations

by David Wang

Hi Everyone, This email is a notification of a new security vulnerability reported to TF-M. It's about the Crypto service in TF-M - abort() function may not take effect in TF-M Crypto multi-part MAC/hashing/cipher operations. Please check the details in the security advisory attached. (.rst version is coming soon) The fix has been merged on the latest master branch - Crypto: Remove unnecessary multi-part operation clean-up (I9cd0fa38) * Gerrit Code Review (trustedfirmware.org)<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9932> We're planning a hot fix release. Will share the plan with you when it's ready. Thanks. Regards, David Wang ARM Electronic Technology (Shanghai) Co., Ltd Phone: +86-21-6154 9142 (ext. 59142)

4 years

1
0
0 0

[RFC] Overall Secure Partition Management (SPM) design document

by Ken Liu

Hi everyone, SPM came at the begging of the project, so the design document was spread into several small pieces as features. Now it is a chance to provide an overall document as we are going to have significant feature updates for FFM 1.1. Here is the draft of the design document: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9928 This document is trying to address the overall design for 1.1 much. It based on FFM 1.1 update alpha stage document. Several points: * I want to publish this document public earlier for a quick taste, even though some features are not introduced yet (such as MMIOVEC), so there defecation would be some missing items, and I would keep updating recently. * Meanwhile, I would collect feedbacks from you and update them into the design document, too. * Prototype would be performed to see the situation. * In this document I am trying to tell the conclusion directly instead of go over the conceptual items described in FF-M. If you can not find background either in this document or in the specification please tell me, I would try to add the missing part. Or if you think some text is quite redundant, tell me and I would remove the without hesitation. The 1.1 specification (alpha): https://developer.arm.com/documentation/aes0039/latest Please provide your feedback - both mailing list and patch are welcome (in the patch is more welcome, as there may be long discussions so patch comment is easier to be tracked). Thanks! /Ken

4 years

1
0
0 0

Re: [TF-M] Technical Forum call - May 13

by Ken Liu

Hi Anton, I would like to discuss the linker script integration things, would summarized the situation and potential improvement plan. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Friday, May 7, 2021 2:20 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - May 13 Hi, The next Technical Forum is planned on Thursday, May 13, 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
0
0 0

Technical Forum call - May 13

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, May 13, 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
0
0 0

Re: [TF-M] Timeframe on release/approval

by David Wang

Hi Jamie, The patch has been reviewed and merged. Thanks. Regards, David Wang From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Jamie Mccrae via TF-M Sent: Thursday, May 6, 2021 2:48 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Timeframe on release/approval Hi, Would it be possible to get some quick reviews on some fixes and a missing file for our board at https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9882 please? Thanks, Jamie From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Tamas Ban via TF-M Sent: 14 April 2021 08:35 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] Timeframe on release/approval Hi, TF-M release cadence is 4 month. In theory 1.4 release is around July. Tamas 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: 2021. április 14., szerda 8:10 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] Timeframe on release/approval Hi Minos/David/Shebu, Many thanks for the details. Is there a timeframe in mind for the next major release of TF-M i.e. version 1.4? Thanks, Jamie 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: 13 April 2021 17:57 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] Timeframe on release/approval Hi Jamie, My understanding is that Zephyr integrates release tags of TF-M. TF-M v1.2 was integrated and I assume v1.3 will be done sometime soon. 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, April 13, 2021 3:14 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] Timeframe on release/approval Hi Jaime, Anton and I have reviewed your patch. Please check our comments on the patch. I believe other reviewers will provide their input as well soon. Although it is difficult to guarantee the timeframe in TF-M as in other open-source project, it will speed up the review process if reviewers’ comments can be addressed in time. 😊 Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Minos Galanakis via TF-M Sent: Tuesday, April 13, 2021 12:09 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] Timeframe on release/approval Hi Jamie, Thank you very much for your interest in supporting for TF-M in your platform. Since you are contributing a new platform, I would recommend that you read the Trusted Firmware maintenance process<https://developer.trustedfirmware.org/w/collaboration/project-maintenance-p…>, for further details on the process. To answer your questions about the timeframe, that really depends on various factors, such as how busy the maintainers of this code are, weather there is a release pending which would follow a code freeze, and how complicated the changes are. I don't believe it is easy to estimate a figure. Regards, Minos ________________________________ 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 <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Sent: 12 April 2021 09:40 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>> Subject: [TF-M] Timeframe on release/approval Hi, I submitted a patch to add our board to the Trusted Firmware-M repository under https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9508 and was wondering on timeframes for receiving comments or having the pull request accepted? We want to have our board added to Zephyr RTOS and for that, we need the board in TF-M and pulled into the Zephyr version of this repository (I’m not sure if they can pull any version of the code or if they only pull full release versions e.g. 1.3.0), are there any comments on this and does anyone have any idea of a rough estimate the time required from now to get the base files into the zephyr version of the repository so we can submit our boards file? Thanks, Jamie 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

2
1
0 0

Re: [TF-M] Timeframe on release/approval

by Kevin Townsend

Hi Shebu, Just as a FYI TF-M 1.3 has already been integrated into Zephyr and will be part of the 2.6.0 release, scheduled for the end of the month. If TF-M 1.4 happens in July, that will likely be the version that Zephyr 2.7.0 will likely use, which will be an LTS release. Kevin On Tue, 13 Apr 2021 at 18:57, Shebu Varghese Kuriakose via TF-M < tf-m(a)lists.trustedfirmware.org> wrote: > Hi Jamie, > > > > My understanding is that Zephyr integrates release tags of TF-M. TF-M v1.2 > was integrated and I assume v1.3 will be done sometime soon. > > > > Regards, > > Shebu > > > > *From:* TF-M <tf-m-bounces(a)lists.trustedfirmware.org> * On Behalf Of *David > Hu via TF-M > *Sent:* Tuesday, April 13, 2021 3:14 AM > *To:* tf-m(a)lists.trustedfirmware.org > *Cc:* nd <nd(a)arm.com> > *Subject:* Re: [TF-M] Timeframe on release/approval > > > > Hi Jaime, > > > > Anton and I have reviewed your patch. Please check our comments on the > patch. > > I believe other reviewers will provide their input as well soon. > > Although it is difficult to guarantee the timeframe in TF-M as in other > open-source project, it will speed up the review process if reviewers’ > comments can be addressed in time. 😊 > > > > Best regards, > > Hu Ziji > > > > *From:* TF-M <tf-m-bounces(a)lists.trustedfirmware.org> *On Behalf Of *Minos > Galanakis via TF-M > *Sent:* Tuesday, April 13, 2021 12:09 AM > *To:* tf-m(a)lists.trustedfirmware.org > *Cc:* nd <nd(a)arm.com> > *Subject:* Re: [TF-M] Timeframe on release/approval > > > > Hi Jamie, > > > > Thank you very much for your interest in supporting for TF-M in your > platform. Since you are contributing a new platform, I would recommend that > you read the Trusted Firmware maintenance process > <https://developer.trustedfirmware.org/w/collaboration/project-maintenance-p…>, > for further details on the process. > > > > To answer your questions about the timeframe, that really depends on > various factors, such as how busy the maintainers of this code are, weather > there is a release pending which would follow a code freeze, and how > complicated the changes are. I don't believe it is easy to estimate a > figure. > > > > Regards, > > Minos > > > ------------------------------ > > *From:* TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Jamie > Mccrae via TF-M <tf-m(a)lists.trustedfirmware.org> > *Sent:* 12 April 2021 09:40 > *To:* tf-m(a)lists.trustedfirmware.org <tf-m(a)lists.trustedfirmware.org> > *Subject:* [TF-M] Timeframe on release/approval > > > > Hi, > > I submitted a patch to add our board to the Trusted Firmware-M repository > under https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9508 > and was wondering on timeframes for receiving comments or having the pull > request accepted? We want to have our board added to Zephyr RTOS and for > that, we need the board in TF-M and pulled into the Zephyr version of this > repository (I’m not sure if they can pull any version of the code or if > they only pull full release versions e.g. 1.3.0), are there any comments on > this and does anyone have any idea of a rough estimate the time required > from now to get the base files into the zephyr version of the repository so > we can submit our boards file? > > Thanks, > > Jamie > > 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. > -- > TF-M mailing list > TF-M(a)lists.trustedfirmware.org > https://lists.trustedfirmware.org/mailman/listinfo/tf-m >

4 years

1
0
0 0

Re: [TF-M] Timeframe on release/approval

by Jamie Mccrae

Hi, Would it be possible to get some quick reviews on some fixes and a missing file for our board at https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9882 please? Thanks, Jamie From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Tamas Ban via TF-M Sent: 14 April 2021 08:35 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Timeframe on release/approval Hi, TF-M release cadence is 4 month. In theory 1.4 release is around July. Tamas From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Jamie Mccrae via TF-M Sent: 2021. április 14., szerda 8:10 To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] Timeframe on release/approval Hi Minos/David/Shebu, Many thanks for the details. Is there a timeframe in mind for the next major release of TF-M i.e. version 1.4? Thanks, Jamie 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: 13 April 2021 17:57 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] Timeframe on release/approval Hi Jamie, My understanding is that Zephyr integrates release tags of TF-M. TF-M v1.2 was integrated and I assume v1.3 will be done sometime soon. 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, April 13, 2021 3:14 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] Timeframe on release/approval Hi Jaime, Anton and I have reviewed your patch. Please check our comments on the patch. I believe other reviewers will provide their input as well soon. Although it is difficult to guarantee the timeframe in TF-M as in other open-source project, it will speed up the review process if reviewers’ comments can be addressed in time. 😊 Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Minos Galanakis via TF-M Sent: Tuesday, April 13, 2021 12:09 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] Timeframe on release/approval Hi Jamie, Thank you very much for your interest in supporting for TF-M in your platform. Since you are contributing a new platform, I would recommend that you read the Trusted Firmware maintenance process<https://developer.trustedfirmware.org/w/collaboration/project-maintenance-p…>, for further details on the process. To answer your questions about the timeframe, that really depends on various factors, such as how busy the maintainers of this code are, weather there is a release pending which would follow a code freeze, and how complicated the changes are. I don't believe it is easy to estimate a figure. Regards, Minos ________________________________ 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 <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Sent: 12 April 2021 09:40 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>> Subject: [TF-M] Timeframe on release/approval Hi, I submitted a patch to add our board to the Trusted Firmware-M repository under https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9508 and was wondering on timeframes for receiving comments or having the pull request accepted? We want to have our board added to Zephyr RTOS and for that, we need the board in TF-M and pulled into the Zephyr version of this repository (I’m not sure if they can pull any version of the code or if they only pull full release versions e.g. 1.3.0), are there any comments on this and does anyone have any idea of a rough estimate the time required from now to get the base files into the zephyr version of the repository so we can submit our boards file? Thanks, Jamie 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

1
0
0 0

Re: [TF-M] [FIH lib] : fih question on a specific fault injection

by Raef Coles

I think at the moment that wouldn't get caught by the flow control countermeasures. However, we did have an idea for an improvement (which didn't get implemented), that should resolve it. At the moment, calling a function with FIH_CALL increases the flow control counter by 1. The alternative we considered was to instead increase the counter by a value that was generated based on the function that was called. Exactly how to generate this number is tricky, since we can't really implement a proper hash function in the preprocessor. The compromise we came to was that we could increase it by sizeof(__func__), (the length of the function name). This is accessible to both the call and the ret, and should be reasonably easily implementable. This wouldn't solve your issue immediately, but one function could then be renamed to be of different length. Another alternative is that you could manually increment and check the flow-control counter, though having to do that manually isn't ideal. Do either of these options seem reasonable? Raef ________________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Michel JAOUEN via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 30 April 2021 13:55 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] [FIH lib] : fih question on a specific fault injection Hello I start using FIH library and I doubt that it can solve following fault injection : Here are 2 tests function being placed by linker very closed from each other to make possible to jump from test_1 start address to test_2 start address with a fault injection. fih_int test_1(void) { fih_int fih_rc = FIH_FAILURE; fih_rc = fih_int_encode(TFM_PLAT_ERR_SUCCESS); FIH_RET(fih_rc); } fih_int test_2(void) { fih_int fih_rc = FIH_FAILURE; fih_rc = fih_int_encode(TFM_PLAT_ERR_SUCCESS); FIH_RET(fih_rc); } Is the following able to detect that code return from test_2 instead of test_1 after such fault ? FIH_CALL(test_1()); if (fih_not_eq(fih_rc, fih_int_encode(TFM_HAL_SUCCESS))) { tfm_core_panic(); } Best regards Michel

4 years

2
1
0 0

[FIH lib] : fih question on a specific fault injection

by Michel JAOUEN

Hello I start using FIH library and I doubt that it can solve following fault injection : Here are 2 tests function being placed by linker very closed from each other to make possible to jump from test_1 start address to test_2 start address with a fault injection. fih_int test_1(void) { fih_int fih_rc = FIH_FAILURE; fih_rc = fih_int_encode(TFM_PLAT_ERR_SUCCESS); FIH_RET(fih_rc); } fih_int test_2(void) { fih_int fih_rc = FIH_FAILURE; fih_rc = fih_int_encode(TFM_PLAT_ERR_SUCCESS); FIH_RET(fih_rc); } Is the following able to detect that code return from test_2 instead of test_1 after such fault ? FIH_CALL(test_1()); if (fih_not_eq(fih_rc, fih_int_encode(TFM_HAL_SUCCESS))) { tfm_core_panic(); } Best regards Michel

4 years

1
0
0 0

Re: [TF-M] Questions on Musca-B1 SE implementation

by David Hu

Hi Suresh, Secure Enclave and dual-cpu so far only support IPC model. Therefore Profile Medium and Profile Large can run on SE and dual-cpu platforms. Besides, Profile Large by default enables Fault Injection Hardening library. It requires platform to support Fault Injection Hardening. The secure firmware binary size may vary with different underlying inter-core communication and assigned resources. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Tamas Ban via TF-M Sent: Friday, April 30, 2021 3:40 PM To: Suresh.Marisetty(a)infineon.com; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Questions on Musca-B1 SE implementation Hi Suresh, Here is a link how to build images to Musca-B1 SE: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e… I have built with GCC and MinSizeRel build type: Profile Medium: Memory region Used Size Region Size %age Used FLASH: 101464 B 381 KB 26.01% RAM: 61304 B 64 KB 93.54% [100%] Built target tfm_s Profile Large: Memory region Used Size Region Size %age Used FLASH: 170448 B 381 KB 43.69% RAM: 62980 B 64 KB 96.10% [ 97%] Built target tfm_s The profiles means different capabilities of TF-M, they were introduced to support constrained devices as well, with limited capability. There is a detailed description about the profiles here: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/techn… BR, Tamas 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: 2021. április 29., csütörtök 21:49 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] Questions on Musca-B1 SE implementation I am following up on a question that came up on the TFM Core and MCUBoot image sizes that is built for SE on Musca-B1. We are trying to figure out the resource requirements for SE, to be able to host the TF-M as suggested in the slides below. Wondering if anyone throw more light on the RAM/FLASH requirements for it. Also, does the TFM profile small/medium/large map to this at all or is it different from them. Also, what's are the estimated latencies of boot on SE with all the Flash accesses, etc. https://www.trustedfirmware.org/docs/Musca-B1-Secure-Enclave-Solution.pdf https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e… Any info on this would be appreciated. thanks Suresh Marisetty Infineon Semiconductor Corporation

4 years

1
0
0 0

Questions on Musca-B1 SE implementation

by Suresh.Marisetty＠infineon.com

I am following up on a question that came up on the TFM Core and MCUBoot image sizes that is built for SE on Musca-B1. We are trying to figure out the resource requirements for SE, to be able to host the TF-M as suggested in the slides below. Wondering if anyone throw more light on the RAM/FLASH requirements for it. Also, does the TFM profile small/medium/large map to this at all or is it different from them. Also, what's are the estimated latencies of boot on SE with all the Flash accesses, etc. https://www.trustedfirmware.org/docs/Musca-B1-Secure-Enclave-Solution.pdf https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e… Any info on this would be appreciated. thanks Suresh Marisetty Infineon Semiconductor Corporation

4 years

1
0
0 0

Re: [TF-M] Decouple NS specific code from TF-M NS interface

by David Hu

Hi all, The patch sets to decouple NS code from TF-M secure part have been merged. Sorry for the early merge as other pending patches depend on this patch set. Please rebase your patches if build reports an error about conflicting types of `tfm_ns_interface_init()`. Sorry for any inconvenience. If this decoupling brings any issue in NS integration with TF-M, sorry about the trouble and I'd appreciate it if you can share the issue details. Any further comment or suggestion 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: Tuesday, April 27, 2021 11:50 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] [Ask for review] Decouple NS specific code from TF-M NS interface Hi all, Thanks a lot for all your review and comments! I'd like to merge the patch sets *this Friday* if there is no further critical comment. Please feel free to continue to review and comment. 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: Thursday, April 15, 2021 4:12 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] [Ask for review] Decouple NS specific code from TF-M NS interface Hi all, May I ask you to take a look at the following patch set to decouple NS specific code from TF-M NS interface? https://review.trustedfirmware.org/q/topic:%22decouple-ns-interface%22+(sta… The decoupled NS code is moved from trusted-firmware-m repo to tf-m-tests repo, as an example of NS implementation. https://review.trustedfirmware.org/q/topic:%22add-ns-code%22+(status:open%2… The purpose of this change is to make it more flexible and simple to integrate NS OS with TF-M NS interface. Currently TF-M provides some reference implementations of NS interface for NS OS integration. However, it may have limitations during NS OS integration as various NS OSes/application usages prefer different implementations. Therefore, those NS OS specific code is removed from TF-M interface for NS clients in this patch set. The removed NS code includes NS interface lock ops, os wrappers and NS test specific implementation. Those NS code can be taken as an example in tf-m-tests. NS developers can follow or replace them during integration with TF-M, according to NS OS implementation and actual scenarios, without hacking trusted-firmware-m repo. This patch set doesn't change the current integration scheme. Instead, it exports the "tfm_ns_interface_dispatch()" API and enables NS OS to implement it according to NS OS and application specific requirement, such as NS interface lock operations. Any comment is welcome! Best regards, Hu Ziji

4 years

1
0
0 0

Re: [TF-M] Technical Forum call - April 29

by Anton Komlev

Hi, We have no explicit items in the agenda. Let's use this chance to discuss any ongoing topics and questions like: * Planning repo restructuring * S <> NS decoupling * Pended PS reviews and a need for clarification * Your topic See you, 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, April 21, 2021 11:40 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 - April 29 Hi, The next Technical Forum is planned on Thursday, April 29 , 07:00-08: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

1
0
0 0

Re: [TF-M] Supporting integrated Non-Secure RTOS applications that use the FPU

by Feder Liang

Hi, Ioannis Sorry for late response. I am out of office these two days. Thank you very much for sharing your problem here. As Keven mentioned, could you please report your problem on phabricator first with more details? This will be very helpful for us to analyze the problem you mentioned. 1. Which cortex-m core? 2. TF-M changeset you are using and compiler version. 3. Please list all changes you did for TF-M while integrated to your project. 4. More information about the crash: * IPC mode, right? Which isolation level? * Detail sequences of actions between NS and S when crash. * Lzay FP enabled? Crash when FPCCR_NS.LSPACT = 1 or something else? * Which PSA calls causes the crash, or all PSA calls? * How about the occurrence of crash? Always crash or sometimes? * Which fault entered? Value of registers and stack frame in memory at crash time are very useful for analysis. * ……., Other information if possible. The more information the better, please try to attached them in phabricator. Thank you. Best Regards Feder From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Glaropoulos, Ioannis via TF-M Sent: Thursday, April 22, 2021 3:24 PM To: Kevin Townsend (kevin.townsend(a)linaro.org) <kevin.townsend(a)linaro.org>; tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] Supporting integrated Non-Secure RTOS applications that use the FPU Hi Kevin, Thanks for the link to the presentation 😊 I guess, then, Feder Liang, as the author of the presentation, should be able to provide some feedback on the questions I raised? Once more, I am stressing that our questions concern the usage of FPU in Non-Secure applications that integrate with TF-M today; it is not about future improvements for FPU support inside TF-M, which was (I guess) the main point of this presentation. Best, Ioannis From: Kevin Townsend <kevin.townsend(a)linaro.org<mailto:kevin.townsend@linaro.org>> Sent: Wednesday, April 21, 2021 8:03 PM To: Glaropoulos, Ioannis <Ioannis.Glaropoulos(a)nordicsemi.no<mailto:Ioannis.Glaropoulos@nordicsemi.no>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] Supporting integrated Non-Secure RTOS applications that use the FPU On Wed, 21 Apr 2021 at 18:56, Glaropoulos, Ioannis via TF-M <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> wrote: I would like to ask the community whether these issues have been raised in the past – and if so, please, inform me what the conclusions have been. Are there current activities that attempt to address the problems raised above? Not been able to fully utilize the FP context stacking in Non-Secure Zephyr applications that integrate with TF-M removes value of our TF-M based solutions. Thanks! I am looking forward to hearing the thoughts of the community. Hi Ioannis, The previous technical forum call did discuss FP usage ... I don't think you were on the call at the time, but the presentation and video can be viewed here, and should point to the people to follow up with here on the mailing list of on phabricator, etc. Presentation: https://www.trustedfirmware.org/docs/FP-support-in-TF-M.pdf<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.trust…> Video link(s) available here: https://www.trustedfirmware.org/meetings/tf-m-technical-forum/<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.trust…> Best rehards, Kevin

4 years

2
1
0 0

Re: [TF-M] [Ask for review] Decouple NS specific code from TF-M NS interface

by David Hu

Hi all, Thanks a lot for all your review and comments! I'd like to merge the patch sets *this Friday* if there is no further critical comment. Please feel free to continue to review and comment. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Thursday, April 15, 2021 4:12 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [Ask for review] Decouple NS specific code from TF-M NS interface Hi all, May I ask you to take a look at the following patch set to decouple NS specific code from TF-M NS interface? https://review.trustedfirmware.org/q/topic:%22decouple-ns-interface%22+(sta… The decoupled NS code is moved from trusted-firmware-m repo to tf-m-tests repo, as an example of NS implementation. https://review.trustedfirmware.org/q/topic:%22add-ns-code%22+(status:open%2… The purpose of this change is to make it more flexible and simple to integrate NS OS with TF-M NS interface. Currently TF-M provides some reference implementations of NS interface for NS OS integration. However, it may have limitations during NS OS integration as various NS OSes/application usages prefer different implementations. Therefore, those NS OS specific code is removed from TF-M interface for NS clients in this patch set. The removed NS code includes NS interface lock ops, os wrappers and NS test specific implementation. Those NS code can be taken as an example in tf-m-tests. NS developers can follow or replace them during integration with TF-M, according to NS OS implementation and actual scenarios, without hacking trusted-firmware-m repo. This patch set doesn't change the current integration scheme. Instead, it exports the "tfm_ns_interface_dispatch()" API and enables NS OS to implement it according to NS OS and application specific requirement, such as NS interface lock operations. Any comment is welcome! Best regards, Hu Ziji

4 years

1
0
0 0

Temporary moving 'tfm_spm_hal_configure_default_isolation' out of FIH mointoring

by Ken Liu

Hi, We are refining the HAL logics for MMIO, so this legacy API 'tfm_spm_hal_configure_default_isolation', which is now monitored under FIH library would be out of monitoring for a while. The successors for this API would be added back after the refining is done, unless there are coming FIH updates. Moving this single function out of FIH monitoring won't trigger problems - in most of the cases this API just returns without actions as few partition has bound MMIOs. Thanks. /Ken

4 years

1
0
0 0

[Partition and Build] Partition storage arrangement patches

by Ken Liu

Hi, As we planned some time ago in one of the Tech Forums about updating the partition storage (Search "TF-M Partition Storage Arrangement" here:https://www.trustedfirmware.org/meetings/tf-m-technical-forum/ ), we have created several patches to complete this. Here in this mail is to broadcast that the partition storage would get updated after this patch, the loading process in SPM would be updated as well to provide: * Better modularization, especially for partitions. Now the partition info are put inside sections, hence there is no source level dependencies in SPM. When partitions get added/removed during one build it won't trigger a build of SPM library. * Clear interface for future expansion, such as other partition loading mechanism, for example, a partition saved in a non-XIP flash or else. But at current stage we still focus on storing partition in XIP based ROM. Some intermedia patches can't be perfect during the movement, so please focus on the final result of patch groups instead of focusing to make one of the staging patches perfect - we don't want to create a big patch hence some trade-off-like patches have to be there. The patches can be found here: https://review.trustedfirmware.org/q/topic:%22partition_storage%22+(status:… Feel free to comment and provide ideas! BR /Ken

4 years

1
0
0 0

Re: [TF-M] Supporting integrated Non-Secure RTOS applications that use the FPU

by Anton Komlev

This is a test message. I know that Feder have posted to the list but message was not delivered. From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kevin Townsend via TF-M Sent: Thursday, April 22, 2021 11:31 AM To: Glaropoulos, Ioannis <Ioannis.Glaropoulos(a)nordicsemi.no> Cc: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] Supporting integrated Non-Secure RTOS applications that use the FPU On Thu, 22 Apr 2021 at 09:23, Glaropoulos, Ioannis <Ioannis.Glaropoulos(a)nordicsemi.no<mailto:Ioannis.Glaropoulos@nordicsemi.no>> wrote: Once more, I am stressing that our questions concern the usage of FPU in Non-Secure applications that integrate with TF-M today; it is not about future improvements for FPU support inside TF-M, which was (I guess) the main point of this presentation. Looking at this a bit further it is indeed a serious issue, since most modern applications are going to want to make use of the FPU. This prevents the FPU from being used inside NS interrupts as well. I’m not sure if there are currently any change requests that identify or fix this problem (I’ll look), but it’s something that should have some sort of test on the NS side, for sure. Do you mind filing the details on TF-M’s phabricator and it can more easily be tracked there? Thanks for bringing this up, Kevin

4 years

1
0
0 0

Re: [TF-M] Supporting integrated Non-Secure RTOS applications that use the FPU

by Kevin Townsend

On Wed, 21 Apr 2021 at 18:56, Glaropoulos, Ioannis via TF-M < tf-m(a)lists.trustedfirmware.org> wrote: > I would like to ask the community whether these issues have been raised in > the past – and if so, please, inform me what the conclusions have been. Are > there current activities that attempt to address the problems raised above? > Not been able to fully utilize the FP context stacking in Non-Secure Zephyr > applications that integrate with TF-M removes value of our TF-M based > solutions. > > > > Thanks! I am looking forward to hearing the thoughts of the community. > > Hi Ioannis, The previous technical forum call did discuss FP usage ... I don't think you were on the call at the time, but the presentation and video can be viewed here, and should point to the people to follow up with here on the mailing list of on phabricator, etc. Presentation: https://www.trustedfirmware.org/docs/FP-support-in-TF-M.pdf Video link(s) available here: https://www.trustedfirmware.org/meetings/tf-m-technical-forum/ Best rehards, Kevin

4 years

2
2
0 0

Removal of the nRF5340 PDK platform

by Głąbek, Andrzej

Hello, As announced on March 3 (see https://lists.trustedfirmware.org/pipermail/tf-m/2021-March/001516.html) and in the absence of objections, the nRF5340 PDK platform (nordic_nrf/nrf5340pdk_nrf5340_cpuapp) has been deprecated in the v1.3.0 release and the release is the last one to support this platform. Today, the code and documentation related to this platform have been removed from TF-M. Best regards, Andrzej Głąbek

4 years

1
0
0 0

Re: [TF-M] [Ask for review] Decouple NS specific code from TF-M NS interface

by Anton Komlev

Hi, Here is the proposal to restructure TF-M following the intention to split it on the essential part and supplementary items with better logical separation. The proposed new structure, composed from 4 repositories is following: 1. trusted-firmware-m (The essential TF-M core: SPM + PSA partitions and interface. Documentation) 2. tf-m-tests * regression * other test 3. tf-m-tools (additional tools and place for integration glue with 3rd party frameworks) * cmsis * fuzzer * Iat-verifier * ... 4. tf-m-extras (extra components, used in a specific case, but optional for common use) * examples i. NS ii. S * S-partitions - (3rd party production partitions) The questions to the community: 1. Any concern or dependency on the proposed restructure? 2. Shall we treat tests separately or as one of the extra component? Effectively the question are tests deserves a dedicated repo or a folder in tf-m-extra? 3. Better name for tf-m-extra? tf-m-apps? Looking for your comments, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Thursday, April 15, 2021 12:24 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] [Ask for review] Decouple NS specific code from TF-M NS interface Thanks, David, The connected job is to rename tf-m-tests repo to something more general to keep supplementary code and not interfere it with TF-M core on secure side. The first candidate was tf-m-ns to reflect the collection of non-secure elements but it might confuse when using it for custom and examples of secure partitions. Thoughts and proposals for the repo naming are welcome. Regards, Anton 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: Thursday, April 15, 2021 9:12 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] [Ask for review] Decouple NS specific code from TF-M NS interface Hi all, May I ask you to take a look at the following patch set to decouple NS specific code from TF-M NS interface? https://review.trustedfirmware.org/q/topic:%22decouple-ns-interface%22+(sta… The decoupled NS code is moved from trusted-firmware-m repo to tf-m-tests repo, as an example of NS implementation. https://review.trustedfirmware.org/q/topic:%22add-ns-code%22+(status:open%2… The purpose of this change is to make it more flexible and simple to integrate NS OS with TF-M NS interface. Currently TF-M provides some reference implementations of NS interface for NS OS integration. However, it may have limitations during NS OS integration as various NS OSes/application usages prefer different implementations. Therefore, those NS OS specific code is removed from TF-M interface for NS clients in this patch set. The removed NS code includes NS interface lock ops, os wrappers and NS test specific implementation. Those NS code can be taken as an example in tf-m-tests. NS developers can follow or replace them during integration with TF-M, according to NS OS implementation and actual scenarios, without hacking trusted-firmware-m repo. This patch set doesn't change the current integration scheme. Instead, it exports the "tfm_ns_interface_dispatch()" API and enables NS OS to implement it according to NS OS and application specific requirement, such as NS interface lock operations. Any comment is welcome! Best regards, Hu Ziji

4 years

1
0
0 0

Technical Forum call - April 29

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, April 29 , 07:00-08: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

1
0
0 0

Supporting integrated Non-Secure RTOS applications that use the FPU

by Glaropoulos, Ioannis

Hi, I would like to raise an issue around Floating Point support in the context of Non-Secure RTOS-based applications integrated with TF-M. The problem: We cannot fully (and easily) utilize the cortex-m Floating point features in Zephyr running together with TF-M. (Note, this has little to do with TF-M not having a secure floating point support today - we focus entirely on using the FPU in non-secure domain.) Description of the case: In Zephyr multi-thread environment we enable the FP co-processor and the advanced context-control features in Cortex-M * Automatic state preservation * Lazy stacking Zephyr threads are free to use the floating point registers; the automatic state preservation ensures the caller-saved registers are preserved and the context-switch routines ensure the callee-saved registers are preserved as well. The situation becomes interesting when Zephyr threads with active FP context are doing calls to the TF-M services. In such a scenario, it may happen that the TF-M secure threads will need to preserve the FP context themselves, during a non-secure interrupt that accesses the FP registers. Currently this triggers a TF-M system crash, as TF-M does not enable the FP co-processor. I guess this could be solved by enabling the FP co-processor in TF-M. Even in this case, the TF-M would need to preserve the FP context state when switching between threads in Secure PendSV, so Non-Secure interrupts (and potential Non-Secure reschedule actions) would not interfere with FP state preservation. What we see today is that the Non-Secure FP context is not preserved during TF-M thread switches, leading to weird situations such as when the lazy state preservation active bit is set in Secure thread mode; which should not be the case. I would like to ask the community whether these issues have been raised in the past - and if so, please, inform me what the conclusions have been. Are there current activities that attempt to address the problems raised above? Not been able to fully utilize the FP context stacking in Non-Secure Zephyr applications that integrate with TF-M removes value of our TF-M based solutions. Thanks! I am looking forward to hearing the thoughts of the community. Ioannis

4 years

1
0
0 0

Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification

by Kevin Peng

Hi Andrew, - Are there other important uses for the query API? I cannot really answer this question. But as you have mentioned, when this query API is provided, it couldn't be always reliable - the status could be changed between query and control. And I also think the nested critical section could really happen (this was the main use case of the IRQ status I guess): A Partition thread and a FLIH function for IRQ1 both wants to mask IRQ2 because they both have data shared with IRQ2. This means the IRQ1 and Partition thread have shared data. Then the Secure Partition thread should mask both IRQ1 and IRQ2 when it accesses the shared data. So IMHO, I don't think Secure Partitions need to the status of IRQs. Best Regards, Kevin -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Andrew Thoelke via TF-M Sent: Wednesday, April 14, 2021 6:15 PM To: tf-m(a)lists.trustedfirmware.org; nd <nd(a)arm.com> Subject: Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification Hi Kevin, In light of the concern regarding atomicity and race conditions, is there a real benefit to retaining the behaviour of psa_irq_disable() returning the prior status. By defining the API this way, it forces every implementation to ensure that the test-and-disable action of this API is atomic with respect to all interrupts in the system (as these could modify the target interrupt state between the test and the disable). Even if TF-M today does this as a result of using an SVC to implement this API, that does not imply that all implementations will need to do that. If we remove the return value from psa_irq_disable(), this also simplifies the TF-M implementation using the CMSIS NVIC_DisableIRQ() function. This would leave us with: void psa_irq_enable(psa_signal_t irq_signal); void psa_irq_disable(psa_signal_t irq_signal); Is it problematic to provide no mechanism to query the state? Are the following use cases for psa_irq_is_enabled() important enough to include this API: * Diagnostics (e.g. when debugging) * Initialisation * Recovery from error conditions The last two of these shouldn't require such an API, as the software should be aware of the peripheral and interrupt state at these points - but the API might make coding these easier? Are there other important uses for the query API? Regards, Andrew -----Original Message----- From: Kevin Peng <Kevin.Peng(a)arm.com> Sent: 13 April 2021 05:03 To: Andrew Thoelke <Andrew.Thoelke(a)arm.com>; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: RE: Arm Firmware Framework for M 1.1 Extensions Alpha specification Hi Andrew, [Sorry for the long delay of resuming this discussion.] I think psa_irq_is_enabled() could be removed. As the peripherals are exclusively owned by Partitions, Partitions should be able to manage the status of the IRQs by themselves. And the psa_irq_disable() could still return the previous status. It (and the psa_irq_enable() as well) should be atomic anyway because the caller would consider the IRQ is disabled or enabled by calling the corresponding API. The APIs must ensure the validness, to do that disabling interrupts entirely might be inevitable. In TF-M, this is done by calling SVC in the APIs to tell SPM to manipulate the interrupt controller. And SVC has higher priority than all interrupts. Best Regards, Kevin -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Andrew Thoelke via TF-M Sent: Monday, February 22, 2021 11:03 PM To: tf-m(a)lists.trustedfirmware.org; nd <nd(a)arm.com> Subject: Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification I've had some further input on the interrupt management API. The use of patterns such as: bool irq_enabled = psa_irq_is_enabled(MY_IRQ); // [1] psa_irq_disable(MY_IRQ); // [2] // critical section if (irq_enabled) psa_irq_enable(MY_IRQ); must be discouraged as this is not guaranteed to be safe in the presence of interrupts that can change the status of MY_IRQ between the query [1] and the disable [2]. In general, it requires whole system analysis to determine that there are no such interrupts, and that this code is 100% reliable. However, providing the originally proposed API such as psa_irq_disable(), which returns the prior status, does not practically solve the problem. Instead, it just moves the race condition window into the implementation of that API. The only way in which such an API would be generally safe from the race condition is if the query+disable is atomic with respect to all other interrupts in the system - this either requires disabling interrupts entirely, or having an atomic read+disable capability in the interrupt controller. In systems which worry about such race conditions, disabling all interrupts can be unacceptable. The recommended approach is to avoid having software that depends on the state of the interrupt, but which does not implicitly know the state of the interrupt. In such a system, there is never a need to query the current interrupt state as on any line of code, the interrupt state is always known at design time. I am not sure if this suggests that we should: 1. Remove even the psa_irq_is_enabled() function, to prevent developers writing the above code, OR 2. We do not document the above pattern as a way to manage nested critical sections, OR 3. Retain the example above, but explain that this must be coupled with a software design that ensures the stability of the MY_IRQ status between [1] and [2]? Regards, Andrew From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: 22 February 2021 04:49 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification As the ‘psa_irq_status_t’ is a implementation-defined value, is it possible let the implementation-define the status encoding? Then the status and its checking code needs to be define by implementation, too: PSA_IRQ_STATUS_NOCHANGE PSA_IRQ_STATUS_DISABLE PSA_IRQ_STATUS_ENABLE PSA_IRQ_STAUTS_IS_ENABLED(status) This would make everything implementation-defined and this affects the headers, and one extra header: psa_impdef.h needs to be created by implementations. With this the ffm based applications just use preprocessors to get status and check them; the enable/disable can be out of ‘true’ and ‘false’ values. /Ken From: TF-M <mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M Sent: Tuesday, January 26, 2021 11:08 AM To: mailto:tf-m@lists.trustedfirmware.org Cc: nd <mailto:nd@arm.com> Subject: Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification Hi all, Per the off-line discussion with Andrew, I’d like to start a wider discussion on the interrupt APIs, specifically the Secure Partition API changes for interrupt control in chapter 6.3.3. There are the following APIs: • uint32_t psa_irq_is_enabled (psa_signal_t irq_signal); This API returns 0 if the interrupt is disabled and 1 if the interrupt is enabled. • psa_irq_status_t psa_irq_disable(psa_signal_t irq_signal); This API returns the status of the interrupt prior to this call with an implementation defined value Note the return type of the interrupt status is different. The first one is only to tell whether the interrupt is enabled (1) or not (0) – an equivalent to bool type. The second one could be any value to indicate an interrupt status. And that value is intended to be passed to psa_irq_restore to write to the interrupt control register directly. • void psa_irq_restore(psa_signal_t irq_signal, psa_irq_status_t saved_status); The typical usage: psa_irq_status irq2_state = psa_irq_disable(IRQ2_SIGNAL) ; // manipulate data shared with IRQ2 … psa_irq_restore(IRQ2_SIGNAL, irq2_state); This is a very efficient design as the 'saved status value' can be the exact value that needs to be written to an interrupt control register to restore the previous state. But TF-M seems to be unable to take that advantage. Because the most common interrupt controller is the NVIC provided by the core. The NVIC takes 1/0 to enable or disable the interrupt and one register for 32 interrupts. The underlying NVIC operation provided by CMSIS is NVIC_Enable/DisableIRQ. So the psa_irq_status_t in TF-M would simply 1 or 0 for a specific interrupt signal. Then the psa_irq_restore could be unnecessary if psa_irq_disable returns uint32_t just like psa_irq_is_enabled: uint32_t irq_status = psa_irq_disable(IRQ); ... // critical section if (irq_status) psa_irq_enable(IRQ); Any thoughts on the necessity of the psa_irq_restore API? The draft implementation of the current APIs for easy understanding: https://review.trustedfirmware.org/q/topic:%22psa_interrupt_api%22+(status:… Best Regards, Kevin -----Original Message----- From: TF-M <mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Andrew Thoelke via TF-M Sent: Friday, January 15, 2021 1:25 AM To: mailto:tf-m@lists.trustedfirmware.org; nd <mailto:nd@arm.com> Subject: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification Hi all, The PSA Firmware Framework for M 1.1 Extensions specification is now published on Arm Developer. This document introduces a set of updates and extensions to the Arm® Platform Security Architecture Firmware Framework (FF-M) specification, designed to build on the capabilities provided in version 1.0. This is an initial ALPHA release in order to enable wider review and feedback on the changes proposed to be included in the v1.1 specification. At this quality level, the changes and interfaces defined are not stable enough for product development. When the proposed extensions are sufficiently stable to be classed as Beta, they will be integrated into the FF-M version 1.1 specification. The 1.1 Extensions document can be downloaded from: https://developer.arm.com/documentation/aes0039/latest Both the 1.0 Specification and the 1.1 Extensions document are linked from the main PSA architecture page: https://developer.arm.com/architectures/security-architectures/platform-sec… Ken and I have presented a number of times at last year's Tech Forums on the proposals in the specification, most recently I provided a summary of the whole document on 10th December 2020. If you have any feedback, please provide it to mailto:arm.psa-feedback@arm.com, or discuss the proposals here in the TF-M mailing list. Regards, Andrew -- TF-M mailing list mailto:TF-M@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

1
0
0 0

Re: [TF-M] [Ask for review] Decouple NS specific code from TF-M NS interface

by Anton Komlev

Thanks, David, The connected job is to rename tf-m-tests repo to something more general to keep supplementary code and not interfere it with TF-M core on secure side. The first candidate was tf-m-ns to reflect the collection of non-secure elements but it might confuse when using it for custom and examples of secure partitions. Thoughts and proposals for the repo naming are welcome. Regards, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Thursday, April 15, 2021 9:12 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [Ask for review] Decouple NS specific code from TF-M NS interface Hi all, May I ask you to take a look at the following patch set to decouple NS specific code from TF-M NS interface? https://review.trustedfirmware.org/q/topic:%22decouple-ns-interface%22+(sta… The decoupled NS code is moved from trusted-firmware-m repo to tf-m-tests repo, as an example of NS implementation. https://review.trustedfirmware.org/q/topic:%22add-ns-code%22+(status:open%2… The purpose of this change is to make it more flexible and simple to integrate NS OS with TF-M NS interface. Currently TF-M provides some reference implementations of NS interface for NS OS integration. However, it may have limitations during NS OS integration as various NS OSes/application usages prefer different implementations. Therefore, those NS OS specific code is removed from TF-M interface for NS clients in this patch set. The removed NS code includes NS interface lock ops, os wrappers and NS test specific implementation. Those NS code can be taken as an example in tf-m-tests. NS developers can follow or replace them during integration with TF-M, according to NS OS implementation and actual scenarios, without hacking trusted-firmware-m repo. This patch set doesn't change the current integration scheme. Instead, it exports the "tfm_ns_interface_dispatch()" API and enables NS OS to implement it according to NS OS and application specific requirement, such as NS interface lock operations. Any comment is welcome! Best regards, Hu Ziji

4 years, 1 month

1
0
0 0

[Ask for review] Decouple NS specific code from TF-M NS interface

by David Hu

Hi all, May I ask you to take a look at the following patch set to decouple NS specific code from TF-M NS interface? https://review.trustedfirmware.org/q/topic:%22decouple-ns-interface%22+(sta… The decoupled NS code is moved from trusted-firmware-m repo to tf-m-tests repo, as an example of NS implementation. https://review.trustedfirmware.org/q/topic:%22add-ns-code%22+(status:open%2… The purpose of this change is to make it more flexible and simple to integrate NS OS with TF-M NS interface. Currently TF-M provides some reference implementations of NS interface for NS OS integration. However, it may have limitations during NS OS integration as various NS OSes/application usages prefer different implementations. Therefore, those NS OS specific code is removed from TF-M interface for NS clients in this patch set. The removed NS code includes NS interface lock ops, os wrappers and NS test specific implementation. Those NS code can be taken as an example in tf-m-tests. NS developers can follow or replace them during integration with TF-M, according to NS OS implementation and actual scenarios, without hacking trusted-firmware-m repo. This patch set doesn't change the current integration scheme. Instead, it exports the "tfm_ns_interface_dispatch()" API and enables NS OS to implement it according to NS OS and application specific requirement, such as NS interface lock operations. Any comment is welcome! Best regards, Hu Ziji

4 years, 1 month

1
0
0 0

Re: [TF-M] Technical Forum call - April 15

by Feder Liang

Hi, Anton I would like to introduce the topic about "FP support in TF-M". It may take about 60 mins. Best Regards Feder From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Wednesday, April 7, 2021 9:27 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - April 15 Hi, The next Technical Forum is planned on Thursday, April 15, 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
1
0 0

Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification

by Kevin Peng

Hi Andrew, [Sorry for the long delay of resuming this discussion.] I think psa_irq_is_enabled() could be removed. As the peripherals are exclusively owned by Partitions, Partitions should be able to manage the status of the IRQs by themselves. And the psa_irq_disable() could still return the previous status. It (and the psa_irq_enable() as well) should be atomic anyway because the caller would consider the IRQ is disabled or enabled by calling the corresponding API. The APIs must ensure the validness, to do that disabling interrupts entirely might be inevitable. In TF-M, this is done by calling SVC in the APIs to tell SPM to manipulate the interrupt controller. And SVC has higher priority than all interrupts. Best Regards, Kevin -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Andrew Thoelke via TF-M Sent: Monday, February 22, 2021 11:03 PM To: tf-m(a)lists.trustedfirmware.org; nd <nd(a)arm.com> Subject: Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification I've had some further input on the interrupt management API. The use of patterns such as: bool irq_enabled = psa_irq_is_enabled(MY_IRQ); // [1] psa_irq_disable(MY_IRQ); // [2] // critical section if (irq_enabled) psa_irq_enable(MY_IRQ); must be discouraged as this is not guaranteed to be safe in the presence of interrupts that can change the status of MY_IRQ between the query [1] and the disable [2]. In general, it requires whole system analysis to determine that there are no such interrupts, and that this code is 100% reliable. However, providing the originally proposed API such as psa_irq_disable(), which returns the prior status, does not practically solve the problem. Instead, it just moves the race condition window into the implementation of that API. The only way in which such an API would be generally safe from the race condition is if the query+disable is atomic with respect to all other interrupts in the system - this either requires disabling interrupts entirely, or having an atomic read+disable capability in the interrupt controller. In systems which worry about such race conditions, disabling all interrupts can be unacceptable. The recommended approach is to avoid having software that depends on the state of the interrupt, but which does not implicitly know the state of the interrupt. In such a system, there is never a need to query the current interrupt state as on any line of code, the interrupt state is always known at design time. I am not sure if this suggests that we should: 1. Remove even the psa_irq_is_enabled() function, to prevent developers writing the above code, OR 2. We do not document the above pattern as a way to manage nested critical sections, OR 3. Retain the example above, but explain that this must be coupled with a software design that ensures the stability of the MY_IRQ status between [1] and [2]? Regards, Andrew From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: 22 February 2021 04:49 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification As the ‘psa_irq_status_t’ is a implementation-defined value, is it possible let the implementation-define the status encoding? Then the status and its checking code needs to be define by implementation, too: PSA_IRQ_STATUS_NOCHANGE PSA_IRQ_STATUS_DISABLE PSA_IRQ_STATUS_ENABLE PSA_IRQ_STAUTS_IS_ENABLED(status) This would make everything implementation-defined and this affects the headers, and one extra header: psa_impdef.h needs to be created by implementations. With this the ffm based applications just use preprocessors to get status and check them; the enable/disable can be out of ‘true’ and ‘false’ values. /Ken From: TF-M <mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M Sent: Tuesday, January 26, 2021 11:08 AM To: mailto:tf-m@lists.trustedfirmware.org Cc: nd <mailto:nd@arm.com> Subject: Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification Hi all, Per the off-line discussion with Andrew, I’d like to start a wider discussion on the interrupt APIs, specifically the Secure Partition API changes for interrupt control in chapter 6.3.3. There are the following APIs: • uint32_t psa_irq_is_enabled (psa_signal_t irq_signal); This API returns 0 if the interrupt is disabled and 1 if the interrupt is enabled. • psa_irq_status_t psa_irq_disable(psa_signal_t irq_signal); This API returns the status of the interrupt prior to this call with an implementation defined value Note the return type of the interrupt status is different. The first one is only to tell whether the interrupt is enabled (1) or not (0) – an equivalent to bool type. The second one could be any value to indicate an interrupt status. And that value is intended to be passed to psa_irq_restore to write to the interrupt control register directly. • void psa_irq_restore(psa_signal_t irq_signal, psa_irq_status_t saved_status); The typical usage: psa_irq_status irq2_state = psa_irq_disable(IRQ2_SIGNAL) ; // manipulate data shared with IRQ2 … psa_irq_restore(IRQ2_SIGNAL, irq2_state); This is a very efficient design as the 'saved status value' can be the exact value that needs to be written to an interrupt control register to restore the previous state. But TF-M seems to be unable to take that advantage. Because the most common interrupt controller is the NVIC provided by the core. The NVIC takes 1/0 to enable or disable the interrupt and one register for 32 interrupts. The underlying NVIC operation provided by CMSIS is NVIC_Enable/DisableIRQ. So the psa_irq_status_t in TF-M would simply 1 or 0 for a specific interrupt signal. Then the psa_irq_restore could be unnecessary if psa_irq_disable returns uint32_t just like psa_irq_is_enabled: uint32_t irq_status = psa_irq_disable(IRQ); ... // critical section if (irq_status) psa_irq_enable(IRQ); Any thoughts on the necessity of the psa_irq_restore API? The draft implementation of the current APIs for easy understanding: https://review.trustedfirmware.org/q/topic:%22psa_interrupt_api%22+(status:… Best Regards, Kevin -----Original Message----- From: TF-M <mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Andrew Thoelke via TF-M Sent: Friday, January 15, 2021 1:25 AM To: mailto:tf-m@lists.trustedfirmware.org; nd <mailto:nd@arm.com> Subject: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification Hi all, The PSA Firmware Framework for M 1.1 Extensions specification is now published on Arm Developer. This document introduces a set of updates and extensions to the Arm® Platform Security Architecture Firmware Framework (FF-M) specification, designed to build on the capabilities provided in version 1.0. This is an initial ALPHA release in order to enable wider review and feedback on the changes proposed to be included in the v1.1 specification. At this quality level, the changes and interfaces defined are not stable enough for product development. When the proposed extensions are sufficiently stable to be classed as Beta, they will be integrated into the FF-M version 1.1 specification. The 1.1 Extensions document can be downloaded from: https://developer.arm.com/documentation/aes0039/latest Both the 1.0 Specification and the 1.1 Extensions document are linked from the main PSA architecture page: https://developer.arm.com/architectures/security-architectures/platform-sec… Ken and I have presented a number of times at last year's Tech Forums on the proposals in the specification, most recently I provided a summary of the whole document on 10th December 2020. If you have any feedback, please provide it to mailto:arm.psa-feedback@arm.com, or discuss the proposals here in the TF-M mailing list. Regards, Andrew -- TF-M mailing list mailto:TF-M@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, 1 month

2
1
0 0

Re: [TF-M] Timeframe on release/approval

by Tamas Ban

Hi, TF-M release cadence is 4 month. In theory 1.4 release is around July. Tamas From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Jamie Mccrae via TF-M Sent: 2021. április 14., szerda 8:10 To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] Timeframe on release/approval Hi Minos/David/Shebu, Many thanks for the details. Is there a timeframe in mind for the next major release of TF-M i.e. version 1.4? Thanks, Jamie 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: 13 April 2021 17:57 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] Timeframe on release/approval Hi Jamie, My understanding is that Zephyr integrates release tags of TF-M. TF-M v1.2 was integrated and I assume v1.3 will be done sometime soon. 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, April 13, 2021 3:14 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] Timeframe on release/approval Hi Jaime, Anton and I have reviewed your patch. Please check our comments on the patch. I believe other reviewers will provide their input as well soon. Although it is difficult to guarantee the timeframe in TF-M as in other open-source project, it will speed up the review process if reviewers’ comments can be addressed in time. 😊 Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Minos Galanakis via TF-M Sent: Tuesday, April 13, 2021 12:09 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] Timeframe on release/approval Hi Jamie, Thank you very much for your interest in supporting for TF-M in your platform. Since you are contributing a new platform, I would recommend that you read the Trusted Firmware maintenance process<https://developer.trustedfirmware.org/w/collaboration/project-maintenance-p…>, for further details on the process. To answer your questions about the timeframe, that really depends on various factors, such as how busy the maintainers of this code are, weather there is a release pending which would follow a code freeze, and how complicated the changes are. I don't believe it is easy to estimate a figure. Regards, Minos ________________________________ 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 <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Sent: 12 April 2021 09:40 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>> Subject: [TF-M] Timeframe on release/approval Hi, I submitted a patch to add our board to the Trusted Firmware-M repository under https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9508 and was wondering on timeframes for receiving comments or having the pull request accepted? We want to have our board added to Zephyr RTOS and for that, we need the board in TF-M and pulled into the Zephyr version of this repository (I’m not sure if they can pull any version of the code or if they only pull full release versions e.g. 1.3.0), are there any comments on this and does anyone have any idea of a rough estimate the time required from now to get the base files into the zephyr version of the repository so we can submit our boards file? Thanks, Jamie 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, 1 month

1
0
0 0

Re: [TF-M] Timeframe on release/approval

by Jamie Mccrae

Hi Minos/David/Shebu, Many thanks for the details. Is there a timeframe in mind for the next major release of TF-M i.e. version 1.4? Thanks, Jamie From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Shebu Varghese Kuriakose via TF-M Sent: 13 April 2021 17:57 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Timeframe on release/approval Hi Jamie, My understanding is that Zephyr integrates release tags of TF-M. TF-M v1.2 was integrated and I assume v1.3 will be done sometime soon. Regards, Shebu From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Tuesday, April 13, 2021 3:14 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Timeframe on release/approval Hi Jaime, Anton and I have reviewed your patch. Please check our comments on the patch. I believe other reviewers will provide their input as well soon. Although it is difficult to guarantee the timeframe in TF-M as in other open-source project, it will speed up the review process if reviewers’ comments can be addressed in time. 😊 Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Minos Galanakis via TF-M Sent: Tuesday, April 13, 2021 12:09 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] Timeframe on release/approval Hi Jamie, Thank you very much for your interest in supporting for TF-M in your platform. Since you are contributing a new platform, I would recommend that you read the Trusted Firmware maintenance process<https://developer.trustedfirmware.org/w/collaboration/project-maintenance-p…>, for further details on the process. To answer your questions about the timeframe, that really depends on various factors, such as how busy the maintainers of this code are, weather there is a release pending which would follow a code freeze, and how complicated the changes are. I don't believe it is easy to estimate a figure. Regards, Minos ________________________________ 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 <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Sent: 12 April 2021 09:40 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>> Subject: [TF-M] Timeframe on release/approval Hi, I submitted a patch to add our board to the Trusted Firmware-M repository under https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9508 and was wondering on timeframes for receiving comments or having the pull request accepted? We want to have our board added to Zephyr RTOS and for that, we need the board in TF-M and pulled into the Zephyr version of this repository (I’m not sure if they can pull any version of the code or if they only pull full release versions e.g. 1.3.0), are there any comments on this and does anyone have any idea of a rough estimate the time required from now to get the base files into the zephyr version of the repository so we can submit our boards file? Thanks, Jamie 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, 1 month

1
0
0 0

Re: [TF-M] Timeframe on release/approval

by Shebu Varghese Kuriakose

Hi Jamie, My understanding is that Zephyr integrates release tags of TF-M. TF-M v1.2 was integrated and I assume v1.3 will be done sometime soon. Regards, Shebu From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Tuesday, April 13, 2021 3:14 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Timeframe on release/approval Hi Jaime, Anton and I have reviewed your patch. Please check our comments on the patch. I believe other reviewers will provide their input as well soon. Although it is difficult to guarantee the timeframe in TF-M as in other open-source project, it will speed up the review process if reviewers’ comments can be addressed in time. 😊 Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Minos Galanakis via TF-M Sent: Tuesday, April 13, 2021 12:09 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] Timeframe on release/approval Hi Jamie, Thank you very much for your interest in supporting for TF-M in your platform. Since you are contributing a new platform, I would recommend that you read the Trusted Firmware maintenance process<https://developer.trustedfirmware.org/w/collaboration/project-maintenance-p…>, for further details on the process. To answer your questions about the timeframe, that really depends on various factors, such as how busy the maintainers of this code are, weather there is a release pending which would follow a code freeze, and how complicated the changes are. I don't believe it is easy to estimate a figure. Regards, Minos ________________________________ 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 <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Sent: 12 April 2021 09:40 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>> Subject: [TF-M] Timeframe on release/approval Hi, I submitted a patch to add our board to the Trusted Firmware-M repository under https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9508 and was wondering on timeframes for receiving comments or having the pull request accepted? We want to have our board added to Zephyr RTOS and for that, we need the board in TF-M and pulled into the Zephyr version of this repository (I’m not sure if they can pull any version of the code or if they only pull full release versions e.g. 1.3.0), are there any comments on this and does anyone have any idea of a rough estimate the time required from now to get the base files into the zephyr version of the repository so we can submit our boards file? Thanks, Jamie 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, 1 month

1
0
0 0

Re: [TF-M] TF-M at Linaro Connect 2021

by Shebu Varghese Kuriakose

The video links to the TF-M presentations @ Linaro Virtual Connect 2021 can be found here - https://developer.trustedfirmware.org/w/tf_m/tf-m_videos/linaro_virtual_con… Thanks, Shebu From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Thursday, March 18, 2021 3:58 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] TF-M at Linaro Connect 2021 Hello, This is the list of TF-M related sessions on Linaro Virtual Connect 2021 https://connect.linaro.org/schedule/ * 23/3 @ 17:15 Introducing the Trusted Services project - Julian Hall * 23/3 @ 18:30 Physical Attack Mitigation - Tamas Ban, Raef Coles * 24/3 @ 9:45 Firmware update service in TF-M - Sherry Zhang * 24/3 @ 10:45 Firmware Framework - M 1.1 feature update in TF-M - Ken Liu * 25/3 @ 12:45 X.509 Certificate Management with Zephyr/TF-M - David Vincze * 25/3 @ 13:15 Essential ARM Cortex-M Debugging with GDB - Kevin Townsend Cheers, Anton

4 years, 1 month

1
0
0 0

Re: [TF-M] Timeframe on release/approval

by David Hu

Hi Jaime, Anton and I have reviewed your patch. Please check our comments on the patch. I believe other reviewers will provide their input as well soon. Although it is difficult to guarantee the timeframe in TF-M as in other open-source project, it will speed up the review process if reviewers’ comments can be addressed in time. 😊 Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Minos Galanakis via TF-M Sent: Tuesday, April 13, 2021 12:09 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Timeframe on release/approval Hi Jamie, Thank you very much for your interest in supporting for TF-M in your platform. Since you are contributing a new platform, I would recommend that you read the Trusted Firmware maintenance process<https://developer.trustedfirmware.org/w/collaboration/project-maintenance-p…>, for further details on the process. To answer your questions about the timeframe, that really depends on various factors, such as how busy the maintainers of this code are, weather there is a release pending which would follow a code freeze, and how complicated the changes are. I don't believe it is easy to estimate a figure. Regards, Minos ________________________________ 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 <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Sent: 12 April 2021 09:40 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>> Subject: [TF-M] Timeframe on release/approval Hi, I submitted a patch to add our board to the Trusted Firmware-M repository under https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9508 and was wondering on timeframes for receiving comments or having the pull request accepted? We want to have our board added to Zephyr RTOS and for that, we need the board in TF-M and pulled into the Zephyr version of this repository (I’m not sure if they can pull any version of the code or if they only pull full release versions e.g. 1.3.0), are there any comments on this and does anyone have any idea of a rough estimate the time required from now to get the base files into the zephyr version of the repository so we can submit our boards file? Thanks, Jamie 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, 1 month

1
0
0 0

Re: [TF-M] Timeframe on release/approval

by Minos Galanakis

Hi Jamie, Thank you very much for your interest in supporting for TF-M in your platform. Since you are contributing a new platform, I would recommend that you read the Trusted Firmware maintenance process<https://developer.trustedfirmware.org/w/collaboration/project-maintenance-p…>, for further details on the process. To answer your questions about the timeframe, that really depends on various factors, such as how busy the maintainers of this code are, weather there is a release pending which would follow a code freeze, and how complicated the changes are. I don't believe it is easy to estimate a figure. Regards, Minos ________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Jamie Mccrae via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 12 April 2021 09:40 To: tf-m(a)lists.trustedfirmware.org <tf-m(a)lists.trustedfirmware.org> Subject: [TF-M] Timeframe on release/approval Hi, I submitted a patch to add our board to the Trusted Firmware-M repository under https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9508 and was wondering on timeframes for receiving comments or having the pull request accepted? We want to have our board added to Zephyr RTOS and for that, we need the board in TF-M and pulled into the Zephyr version of this repository (I’m not sure if they can pull any version of the code or if they only pull full release versions e.g. 1.3.0), are there any comments on this and does anyone have any idea of a rough estimate the time required from now to get the base files into the zephyr version of the repository so we can submit our boards file? Thanks, Jamie 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, 1 month

1
0
0 0

Timeframe on release/approval

by Jamie Mccrae

Hi, I submitted a patch to add our board to the Trusted Firmware-M repository under https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9508 and was wondering on timeframes for receiving comments or having the pull request accepted? We want to have our board added to Zephyr RTOS and for that, we need the board in TF-M and pulled into the Zephyr version of this repository (I'm not sure if they can pull any version of the code or if they only pull full release versions e.g. 1.3.0), are there any comments on this and does anyone have any idea of a rough estimate the time required from now to get the base files into the zephyr version of the repository so we can submit our boards file? Thanks, Jamie 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, 1 month

1
0
0 0

TF-M v1.3.0 release

by Anton Komlev

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, 1 month

1
0
0 0

Technical Forum call - April 15

by Anton Komlev

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

1
0
0 0

Re: [TF-M] Issues with alignment and buffer locations

by Ken Liu

Hi Jamie, Thanks for your reply. Looks like it is mostly flash related. I have created one task for tracking this: https://developer.trustedfirmware.org/T918 We need some time to analyze this, so the response may be not short and we would keep updating. Feel free to provide your done solutions on the task. Thanks. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Jamie Mccrae via TF-M Sent: Thursday, April 1, 2021 4:59 PM To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] Issues with alignment and buffer locations Hi Ken, > Could help to provide the details so that we can see what the problem is? Looks like you mentioned two problems here, one for the un-aligned memory accessing and another is the FLASH read/write. Sure. This is being based on the nRF5340 (Cortex-M33) chipset, it uses image swapping rather than overwriting, the primary image is located in the on-chip flash and the secondary slot is located in QSPI flash, the scratch slot is also located in QSPI flash, this is the trailing part of the log when the issue with trying to write to QSPI from a non-RAM buffer occurs (GCC build): [ERR] Qerase 0xfe000 [ERR] Qerase 0xff000 [ERR] read area=3, off=0x9fff0, len=0x10 [ERR] Qread 0x9fff0 10 to 0x20005ad8 [ERR] read area=3, off=0x9ffd8, len=0x1 [ERR] Qread 0x9ffd8 1 to 0x20005ad7 [ERR] read area=3, off=0x9ffe0, len=0x1 [ERR] Qread 0x9ffe0 1 to 0x20005b22 [ERR] read area=3, off=0x9ffe8, len=0x1 [ERR] Qread 0x9ffe8 1 to 0x20005b23 [ERR] write area=5, off=0x1ffd8, len=0x4 [ERR] Qwrite 0xfffd8 4 from 0x20005ae0 [ERR] write area=5, off=0x1ffd0, len=0x4 [ERR] Qwrite 0xfffd0 4 from 0x20005ae0 [ERR] write area=5, off=0x1fff0, len=0x10 [ERR] Qwrite 0xffff0 10 from 0xcfdc [ERR] QSPI write failed -400 assertion "rc == 0" failed: file "lib/ext/mcuboot-src/boot/bootutil/src/swap_misc.c", line 125, function: swap_status_init The final write fails because it is attempting to write to QSPI from a non-RAM address, 0xcfdc is an address in the internal flash. Unless this is possibly an issue with the buffer address being overwritten somehow? > For the memory alignment, to ensure the isolation setting all sections should be 32-bytes aligned; and the stack-alignment is 8 bytes. Other contents are set as default, the toolchain should have handled them correctly. This is the error in the trailing part of the log I am getting with it reading 1 byte at a time to an invalid buffer: [ERR] read area=1, off=0, len=0x20 [ERR] Fread 0x10000 0x20 to 0x20002530 [ERR] read area=3, off=0, len=0x20 [ERR] Qread 0x0 0x20 to 0x2000255c [ERR] read area=1, off=0x9fff0, len=0x10 [ERR] Fread 0xafff0 10 to 0x20005b60 [ERR] read area=1, off=0x9ffd8, len=0x1 [ERR] Fread 0xaffd8 1 to 0x20005b5f [ERR] read area=1, off=0x9ffe0, len=0x1 [ERR] Fread 0xaffe0 1 to 0x20005baa [ERR] read area=1, off=0x9ffe8, len=0x1 [ERR] Fread 0xaffe8 1 to 0x20005bab [ERR] read area=5, off=0x1fff0, len=0x10 [ERR] Qread 0xffff0 10 to 0x20005b60 [ERR] read area=5, off=0x1ffd8, len=0x1 [ERR] Qread 0xfffd8 1 to 0x20005b5f [ERR] Qread QSPI failed assertion "rc == 0" failed: file "lib/ext/mcuboot-src/boot/bootutil/src/swap_scratch.c", line 384, function: swap_status_source The 2 issues are QSPI reads must be multiples of 4 bytes, it cannot read just 1 byte, and secondly the 0x20005b5f buffer is not 4-byte aligned so it cannot be used to store the data anyway. The same GCC linker .ld files are being used as are currently in the TF-M repository for the nRF5340-DK which is 4-byte aligned for data and bss and 8-byte aligned for heap. Qread/Qwrite = QSPI, Fread/Write = internal flash, area 5 is the scratch partition. This is TF-M built with separate secure and non-secure image slots. > Please provide the details, thank you! > > /Ken > > From: TF-M <tf-m-bounces at lists.trustedfirmware.org> On Behalf Of Jamie Mccrae via TF-M > Sent: Monday, March 29, 2021 10:19 PM > To: tf-m at lists.trustedfirmware.org > Subject: [TF-M] Issues with alignment and buffer locations > > Hi, > There seems to be a large oversight in the TF-M codeline relating to buffer alignment and locations of buffers, in terms of buffer alignment, some ARM-based silicon has restrictions on buffer alignment, generally 4-byte boundaries, this means that if a non-4 byte boundary address, buffer or data size is provided, the operation cannot be completed. Another issue is that some ARM-based silicon has restrictions on where data can be located, e.g. in RAM only for writing and not from other address spaces. > I am currently trying to get TF-M working on a Nordic nRF53-based designed and have encountered these issues many times, and can see no way to set an alignment, data size or address space limitation in the whole code line which I find to be quite displeasing given that both the silicon and software are ARM-based, I would expect the software you give for silicon based on your reference designs to actually work with it out of the box rather than need lots of work to have these limitations supported. On Nordic silicon, data can only be written and read from RAM e.g. you cannot write to flash from a flash offset, and writes must be 4-byte aligned and 4-byte sized (the QSPI functionality is being used here). > > So I am emailing here to ask: what is the suggestion for dealing with this? Why does the baseline project not (from what I can see) have any sort of support for this? > Thanks, > Jamie 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, 1 month

1
0
0 0

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

by Don Harbin

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 10am to 11am on Thursday Central Time - Chicago (changed) 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 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, 1 month

1
0
0 0

Issues with alignment and buffer locations

by Jamie Mccrae

Hi, There seems to be a large oversight in the TF-M codeline relating to buffer alignment and locations of buffers, in terms of buffer alignment, some ARM-based silicon has restrictions on buffer alignment, generally 4-byte boundaries, this means that if a non-4 byte boundary address, buffer or data size is provided, the operation cannot be completed. Another issue is that some ARM-based silicon has restrictions on where data can be located, e.g. in RAM only for writing and not from other address spaces. I am currently trying to get TF-M working on a Nordic nRF53-based designed and have encountered these issues many times, and can see no way to set an alignment, data size or address space limitation in the whole code line which I find to be quite displeasing given that both the silicon and software are ARM-based, I would expect the software you give for silicon based on your reference designs to actually work with it out of the box rather than need lots of work to have these limitations supported. On Nordic silicon, data can only be written and read from RAM e.g. you cannot write to flash from a flash offset, and writes must be 4-byte aligned and 4-byte sized (the QSPI functionality is being used here). So I am emailing here to ask: what is the suggestion for dealing with this? Why does the baseline project not (from what I can see) have any sort of support for this? Thanks, Jamie 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, 1 month

1
1
0 0

Re: [TF-M] Technical Forum call - April 1 (not a joke :)

by Anton Komlev

Hi, the agenda for the forum tomorrow : 1. News and update by Anton Komlev 2. Open discussion on TF-M documentation structure by David Wang 3. Stateless handle and service in TF-M by Mingyang Sun 4. AOB Regards, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Wang via TF-M Sent: Tuesday, March 30, 2021 3:20 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Technical Forum call - April 1 (not a joke :) Hi Anton, If we still have slot, I'd like to share some thoughts and have a discussion for the TF-M documentation structure. It should be less than 20 mins. Thanks. Regards, David Wang From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Mingyang Sun via TF-M Sent: Monday, March 29, 2021 11:15 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: [TF-M] Technical Forum call - April 1 (not a joke :) Hi Anton, I'd like give a short session on "stateless handle and service in TF-M", about 20min. Regards, Mingyang 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: Friday, March 26, 2021 6:57 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] Technical Forum call - April 1 (not a joke :) Hi, The next Technical Forum is planned on Thursday, April 1 , 07:00-08:00 UTC (Asia time zone). Please mine the gap of the time change in Europe! 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

1
0
0 0

TF-M v1.3.0 Release Candidate 3

by Anton Komlev

Hi, New TF-M Release Candidate 3 is tagged by TF-Mv1.3.0-RC3. Please update your repositories and report all issues you encountered. Best regards, Anton

4 years, 1 month

1
0
0 0

Announcement: New TF-M maintainers

by Anton Komlev

Hi Everyone, Let me announce the new maintainers of TF-M project: * Chris Brand aka UEWBot <chris.brand(a)cypress.com<mailto:chris.brand@cypress.com>> * Ken Liu aka KenLSoft <Ken.Liu(a)arm.com<mailto:Ken.Liu@arm.com>> * David Hu aka davidhuziji <David.Hu(a)arm.com<mailto:David.Hu@arm.com>> Previous maintainers convinced in your ability to push it forward thanks to your contribution and active involvement to the project development. At the same time, these maintainers are leaving the club: * Abhishek Pandit aka abhishek-pandit <abhishek.pandit(a)arm.com<mailto:abhishek.pandit@arm.com>> * Ashutosh Singh aka ashutoshksingh <ashutosh.singh(a)arm.com<mailto:ashutosh.singh@arm.com>> * Miklos Balint ara wmnt <miklos.balint(a)arm.com<mailto:miklos.balint@arm.com>> Huge thanks for your Blood, sweat and tears in bringing TF-M to the way it is now. Cheers, Anton

4 years, 1 month

1
0
0 0

Re: [TF-M] Regression observed in PSA Crypto after Mbed TLS upgrade to 2.25

by Summer Qin

Hi Alexander, Thanks for your information. For current TF-Mv1.3.0-RC1, yes, we have some extra failed test cases for crypto psa arch tests. They are 208, 211, 237, 243, and 244. We are now trying to fix them. 206 and 207 are our know issues. Details can be found in our tfm release failure analysis: https://developer.trustedfirmware.org/w/tf_m/release/psa_arch_crypto_test_f… https://developer.trustedfirmware.org/w/tf_m/release/psa_arch_crypto_test_f… Thanks, Summer ________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Alexander.Moore--- via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: Wednesday, March 24, 2021 3:55 PM To: David Hu <David.Hu(a)arm.com> Cc: nd <nd(a)arm.com>; tf-m(a)lists.trustedfirmware.org <tf-m(a)lists.trustedfirmware.org> Subject: Re: [TF-M] Regression observed in PSA Crypto after Mbed TLS upgrade to 2.25 What’s the build configuration on PSoC 64 with PSA Arch test: + BUILD_OPTS='-DTEST_PSA_API=CRYPTO -DTFM_PSA_API=ON -DTFM_ISOLATION_LEVEL=2' + cmake -S . -B build_clang_psoc64 -DTFM_PLATFORM=cypress/psoc64 -DTFM_TOOLCHAIN_FILE=toolchain_ARMCLANG.cmake -DCMAKE_BUILD_TYPE=Release -DTEST_PSA_API=CRYPTO -DTFM_PSA_API=ON -DTFM_ISOLATION_LEVEL=2 -- The C compiler identification is ARMClang 6.12.1 -- The ASM compiler identification is ARMCC We build both debug/release, and also use gcc/armclang, all four combinations give the same PSA Crypto test results. What’s the version of TF-M? Have you tried the latest one in master branch: * We are using the latest master (v1.2.0) and isolated the problem commit to be 28659c498c3bdbbc610959e7518bece5aaf72a19. What’s the version of PSA Arch test: * We are using the default tagged version associated with TF-M master branch, which is “8644bd0 musca_s1 support” Can you share more log of the failure test case: TEST: 206 | DESCRIPTION: Testing crypto hash functions APIs [Info] Executing tests from non-secure [Check 1] Test psa_hash_compute with SHA224 algorithm [Check 2] Test psa_hash_compute with SHA256 algorithm [Check 3] Test psa_hash_compute with SHA384 algorithm [Check 4] Test psa_hash_compute with SHA512 algorithm [Check 5] Test psa_hash_compute with small buffer size [Check 6] Test psa_hash_compute with invalid algorithm Failed at Checkpoint: 3 Actual: -135 Expected: -134 TEST RESULT: FAILED (Error Code=0x1) TEST: 207 | DESCRIPTION: Testing crypto hash functions APIs [Info] Executing tests from non-secure [Check 1] Test psa_hash_compare - SHA224 algorithm [Check 2] Test psa_hash_compare - SHA256 algorithm [Check 3] Test psa_hash_compare - SHA384 algorithm [Check 4] Test psa_hash_compare - SHA512 algorithm [Check 5] Test psa_hash_compare - incorrect hash [Check 6] Test psa_hash_compare - incorrect hash length [Check 7] Test psa_hash_compare - invalid algorithm Failed at Checkpoint: 3 Actual: -135 Expected: -134 TEST RESULT: FAILED (Error Code=0x1) TEST: 208 | DESCRIPTION: Testing crypto key derivation APIs [Info] Executing tests from non-secure [Check 1] Test psa_key_derivation_setup - ECDH + HKDF-SHA-256 [Check 2] Test psa_key_derivation_setup - ECDH, unknown KDF [Check 3] Test psa_key_derivation_setup - bad key derivation algorithm Failed at Checkpoint: 3 Actual: -134 Expected: -135 TEST RESULT: FAILED (Error Code=0x1) TEST: 211 | DESCRIPTION: Testing crypto hash functions APIs [Info] Executing tests from non-secure [Check 1] Test psa_hash_setup with SHA224 algorithm [Check 2] Test psa_hash_setup with SHA256 algorithm [Check 3] Test psa_hash_setup with SHA384 algorithm [Check 4] Test psa_hash_setup with SHA512 algorithm [Check 5] Test psa_hash_setup with Invalid hash algorithm Failed at Checkpoint: 3 Actual: -135 Expected: -134 TEST RESULT: FAILED (Error Code=0x1) TEST: 237 | DESCRIPTION: Testing crypto symmetric cipher APIs [Info] Executing tests from non-secure [Check 1] Test psa_cipher_finish - Encrypt - AES CBC_NO_PADDING [Check 2] Test psa_cipher_finish - Encrypt - AES CBC_NO_PADDING (Short in) [Check 3] Test psa_cipher_finish - Encrypt - AES CBC_PKCS7 [Check 4] Test psa_cipher_finish - Encrypt - AES CBC_PKCS7 (Short input) [Check 5] Test psa_cipher_finish - Encrypt - AES CTR [Check 6] Test psa_cipher_finish - Encrypt - AES CTR (short input) [Check 7] Test psa_cipher_finish - Encrypt - small output buffer size [Check 8] Test psa_cipher_finish - Decrypt - AES CBC_NO_PADDING [Check 9] Test psa_cipher_finish - Decrypt - AES CBC_NO_PADDING (Short in) Failed at Checkpoint: 8 Actual: -135 Expected: -137 TEST RESULT: FAILED (Error Code=0x1) TEST: 243 | DESCRIPTION: Testing crypto key derivation APIs [Info] Executing tests from non-secure [Check 1] Test psa_raw_key_agreement - ECDH SECP256R1 [Check 2] Test psa_raw_key_agreement - Small buffer size [Check 3] Test psa_raw_key_agreement - ECDH SECP384R1 [Check 4] Test psa_raw_key_agreement - Invalid usage [Check 5] Test psa_raw_key_agreement - Unknown KDF Failed at Checkpoint: 4 Actual: -134 Expected: -135 TEST RESULT: FAILED (Error Code=0x1) TEST: 244 | DESCRIPTION: Testing crypto key management APIs [Info] Executing tests from non-secure [Check 1] Test psa_copy_key - 16 Byte AES [Check 2] Test psa_copy_key - without copy usage [Check 3] Test psa_copy_key - invalid lifetime Failed at Checkpoint: 4 Actual: -136 Expected: -135 TEST RESULT: FAILED (Error Code=0x1) Thanks, Alex From: David Hu <David.Hu(a)arm.com> Sent: Monday, March 22, 2021 7:56 PM To: Moore Alexander (CSCA CSS ICW SW PSW 1) <Alexander.Moore(a)infineon.com> Cc: tf-m(a)lists.trustedfirmware.org; nd <nd(a)arm.com> Subject: RE: [TF-M] Regression observed in PSA Crypto after Mbed TLS upgrade to 2.25 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 Alexander, Thanks for reporting this issue. Can I ask for more details of the failures? * What’s the build configuration on PSoC 64 with PSA Arch test? * What’s the version of TF-M? Have you tried the latest one in master branch? * What’s the version of PSA Arch test? * Can you share more log of the failure test case? Thanks. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Alexander.Moore--- via TF-M Sent: Tuesday, March 23, 2021 6:42 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] Regression observed in PSA Crypto after Mbed TLS upgrade to 2.25 Hello, After “28659c49 Crypto: Upgrade Mbed TLS to 2.25” we see the following 7 PSA Crypto test failures on PSoC64 which were passing before this commit: TEST: 206 TEST: 207 TEST: 208 TEST: 211 TEST: 237 TEST: 243 TEST: 244 Are these failures expected? As far as we can tell, there is nothing else to be done associated with the 2.25 upgrade, i.e. the build automatically pulls 2.25 down, and there are no corresponding commits to psa-arch-tests to support the upgrade or any other changes necessary. Thanks, Alex

4 years, 1 month

2
2
0 0

Re: [TF-M] FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed

by Thomas Törnblom

Never mind, I found the issue and have uploaded an updated patch. /Thomas Den 2021-03-30 kl. 15:17, skrev Thomas Törnblom via TF-M: > Hi Anton, > > Is it these issues that is causing the problems? > --- > In file included from > ..\platform\ext\accelerator\stm\..\..\..\ext\target\stm\common\stm32l5xx\Device\Include\stm32l5xx.h:106: > ..\platform\ext\accelerator\stm\..\..\..\ext\target\stm\common\stm32l5xx\Device\Include/stm32l562xx.h:1808:13: > warning: parameter 'pointer' not found in the function declaration > [-Wdocumentation] > * @param pointer on the vector table containing the reset handler > the function > ^~~~~~~ > ..\platform\ext\accelerator\stm\..\..\..\ext\target\stm\common\stm32l5xx\Device\Include/stm32l562xx.h:1808:13: > note: did you mean 'VectorTableAddr'? > * @param pointer on the vector table containing the reset handler > the function > ^~~~~~~ > VectorTableAddr > ..\platform\ext\target\stm\common\stm32l5xx\accelerator\rsa_alt.c:353:17: > warning: parameter 'dP' not found in the function declaration > [-Wdocumentation] > * @param[in] dP pΓÇÖs CRT exponent > ^~ > ..\platform\ext\target\stm\common\stm32l5xx\accelerator\rsa_alt.c:353:17: > note: did you mean 'dp'? > * @param[in] dP pΓÇÖs CRT exponent > ^~ > dp > ..\platform\ext\target\stm\common\stm32l5xx\accelerator\rsa_alt.c:354:17: > warning: parameter 'dQ' not found in the function declaration > [-Wdocumentation] > * @param[in] dQ qΓÇÖs CRT exponent > ^~ > ..\platform\ext\target\stm\common\stm32l5xx\accelerator\rsa_alt.c:354:17: > note: did you mean 'dp'? > * @param[in] dQ qΓÇÖs CRT exponent > ^~ > dp > ..\platform\ext\target\stm\common\stm32l5xx\accelerator\rsa_alt.c:1185:24: > warning: unused parameter 'p_rng' [-Wunused-parameter] > void *p_rng, > ^ > 4 warnings generated. > --- > > This has nothing to do with my patch but seems related to: > > PS > C:\Users\thomasto\Projects\tf-m8\trusted-firmware-m\platform\ext\target\stm\common\stm32l5xx\accelerator> > git log rsa_alt.c > commit 1ea82c0329f45204868df20a3bd8627286c0cdaa > Author: Michel Jaouen <michel.jaouen(a)st.com> > Date: Mon Jan 25 15:18:21 2021 +0100 > > Platform: stm: Add crypto accelerator support > > Change-Id: I7c0686c6f6470bebc7f258af125272d28bc4ce84 > Signed-off-by: Michel Jaouen <michel.jaouen(a)st.com> > > If it is not that issue, then please elaborate as I get exactly the > same result with or without my patch when building with armclang. > > /Thomas > > [ > Den 2021-03-30 kl. 13:27, skrev Anton Komlev via TF-M: >> >> Hi Michel, Thomas, >> >> The fix >> https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9455 >> <https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9455>fails >> for armclang. Please check the CI test. >> >> If it’s important feature of the release then could you check and fix >> it? Let me know if we can progress with RC3 without waiting for the fix. >> >> Thanks, >> >> Anton >> >> *From:*TF-M <tf-m-bounces(a)lists.trustedfirmware.org> *On Behalf Of >> *Michel JAOUEN via TF-M >> *Sent:* Monday, March 29, 2021 9:08 PM >> *To:* tf-m(a)lists.trustedfirmware.org >> *Subject:* Re: [TF-M] FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 >> failed >> >> Thanks , it solved. >> >> Best Regards >> >> Michel >> >> *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:* lundi 29 mars 2021 17:37 >> *To:* tf-m(a)lists.trustedfirmware.org >> <mailto:tf-m@lists.trustedfirmware.org> >> *Subject:* Re: [TF-M] FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 >> failed >> >> Apparently I have not tested this before. >> >> Check the fix at: >> https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9455 >> <https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9455> >> >> /Thomas >> >> Den 2021-03-29 kl. 16:35, skrev Michel JAOUEN via TF-M: >> >> Sure >> >> Variable $tfm_work point to trustedfirmware local dir. >> >> Here is my command >> >> cmake -S . -B build_dir -G"Unix Makefiles" >> >> -DTFM_PLATFORM=stm/stm32l562e_dk >> >> -DTFM_TOOLCHAIN_FILE=$tfm_work/toolchain_IARARM.cmake >> >> -DCMAKE_BUILD_TYPE=RelWithDebInfo >> >> -DTEST_S=ON -DTEST_NS=ON -DTFM_PSA_API=ON -DTFM_ISOLATION_LEVEL=2 >> >> Best regards >> >> Michel >> >> *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:* lundi 29 mars 2021 16:06 >> *To:* tf-m(a)lists.trustedfirmware.org >> <mailto:tf-m@lists.trustedfirmware.org> >> *Subject:* Re: [TF-M] TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 >> failed >> >> Hi Michel, >> >> Can you provide the cmake line and I'll have a look. >> >> That argument looks like a gcc argument not recognized by the IAR >> tools. >> >> Cheers, >> Thomas >> >> Den 2021-03-29 kl. 15:34, skrev Michel JAOUEN via TF-M: >> >> Hello, >> >> I got the following build issue when I build with IARAR, it >> occurs when build mbed-crypto >> >> IAR ANSI C/C++ Compiler V8.50.4.261/W32 for ARM >> >> Copyright 1999-2020 IAR Systems AB. >> >> Network license: 10.157.2.156 (STD) >> >> Command line error: Unexpected command line arguments: >> >> -Wno-unused-parameter >> >> Does someone else reproduce the issue ? >> >> Best regards >> >> -- >> >> *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, 1 month

1
0
0 0

Re: [TF-M] FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed

by Thomas Törnblom

Hi Anton, Is it these issues that is causing the problems? --- In file included from ..\platform\ext\accelerator\stm\..\..\..\ext\target\stm\common\stm32l5xx\Device\Include\stm32l5xx.h:106: ..\platform\ext\accelerator\stm\..\..\..\ext\target\stm\common\stm32l5xx\Device\Include/stm32l562xx.h:1808:13: warning: parameter 'pointer' not found in the function declaration [-Wdocumentation] * @param pointer on the vector table containing the reset handler the function ^~~~~~~ ..\platform\ext\accelerator\stm\..\..\..\ext\target\stm\common\stm32l5xx\Device\Include/stm32l562xx.h:1808:13: note: did you mean 'VectorTableAddr'? * @param pointer on the vector table containing the reset handler the function ^~~~~~~ VectorTableAddr ..\platform\ext\target\stm\common\stm32l5xx\accelerator\rsa_alt.c:353:17: warning: parameter 'dP' not found in the function declaration [-Wdocumentation] * @param[in] dP pΓÇÖs CRT exponent ^~ ..\platform\ext\target\stm\common\stm32l5xx\accelerator\rsa_alt.c:353:17: note: did you mean 'dp'? * @param[in] dP pΓÇÖs CRT exponent ^~ dp ..\platform\ext\target\stm\common\stm32l5xx\accelerator\rsa_alt.c:354:17: warning: parameter 'dQ' not found in the function declaration [-Wdocumentation] * @param[in] dQ qΓÇÖs CRT exponent ^~ ..\platform\ext\target\stm\common\stm32l5xx\accelerator\rsa_alt.c:354:17: note: did you mean 'dp'? * @param[in] dQ qΓÇÖs CRT exponent ^~ dp ..\platform\ext\target\stm\common\stm32l5xx\accelerator\rsa_alt.c:1185:24: warning: unused parameter 'p_rng' [-Wunused-parameter] void *p_rng, ^ 4 warnings generated. --- This has nothing to do with my patch but seems related to: PS C:\Users\thomasto\Projects\tf-m8\trusted-firmware-m\platform\ext\target\stm\common\stm32l5xx\accelerator> git log rsa_alt.c commit 1ea82c0329f45204868df20a3bd8627286c0cdaa Author: Michel Jaouen <michel.jaouen(a)st.com> Date: Mon Jan 25 15:18:21 2021 +0100 Platform: stm: Add crypto accelerator support Change-Id: I7c0686c6f6470bebc7f258af125272d28bc4ce84 Signed-off-by: Michel Jaouen <michel.jaouen(a)st.com> If it is not that issue, then please elaborate as I get exactly the same result with or without my patch when building with armclang. /Thomas [ Den 2021-03-30 kl. 13:27, skrev Anton Komlev via TF-M: > > Hi Michel, Thomas, > > The fix > https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9455 > <https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9455>fails > for armclang. Please check the CI test. > > If it’s important feature of the release then could you check and fix > it? Let me know if we can progress with RC3 without waiting for the fix. > > Thanks, > > Anton > > *From:*TF-M <tf-m-bounces(a)lists.trustedfirmware.org> *On Behalf Of > *Michel JAOUEN via TF-M > *Sent:* Monday, March 29, 2021 9:08 PM > *To:* tf-m(a)lists.trustedfirmware.org > *Subject:* Re: [TF-M] FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed > > Thanks , it solved. > > Best Regards > > Michel > > *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:* lundi 29 mars 2021 17:37 > *To:* tf-m(a)lists.trustedfirmware.org > <mailto:tf-m@lists.trustedfirmware.org> > *Subject:* Re: [TF-M] FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed > > Apparently I have not tested this before. > > Check the fix at: > https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9455 > <https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9455> > > /Thomas > > Den 2021-03-29 kl. 16:35, skrev Michel JAOUEN via TF-M: > > Sure > > Variable $tfm_work point to trustedfirmware local dir. > > Here is my command > > cmake -S . -B build_dir -G"Unix Makefiles" > > -DTFM_PLATFORM=stm/stm32l562e_dk > > -DTFM_TOOLCHAIN_FILE=$tfm_work/toolchain_IARARM.cmake > > -DCMAKE_BUILD_TYPE=RelWithDebInfo > > -DTEST_S=ON -DTEST_NS=ON -DTFM_PSA_API=ON -DTFM_ISOLATION_LEVEL=2 > > Best regards > > Michel > > *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:* lundi 29 mars 2021 16:06 > *To:* tf-m(a)lists.trustedfirmware.org > <mailto:tf-m@lists.trustedfirmware.org> > *Subject:* Re: [TF-M] TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed > > Hi Michel, > > Can you provide the cmake line and I'll have a look. > > That argument looks like a gcc argument not recognized by the IAR > tools. > > Cheers, > Thomas > > Den 2021-03-29 kl. 15:34, skrev Michel JAOUEN via TF-M: > > Hello, > > I got the following build issue when I build with IARAR, it > occurs when build mbed-crypto > > IAR ANSI C/C++ Compiler V8.50.4.261/W32 for ARM > > Copyright 1999-2020 IAR Systems AB. > > Network license: 10.157.2.156 (STD) > > Command line error: Unexpected command line arguments: > > -Wno-unused-parameter > > Does someone else reproduce the issue ? > > Best regards > > -- > > *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, 1 month

1
0
0 0

Re: [TF-M] FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed

by Anton Komlev

Hi Michel, Thomas, The fix https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9455 fails for armclang. Please check the CI test. If it's important feature of the release then could you check and fix it? Let me know if we can progress with RC3 without waiting for the fix. Thanks, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Michel JAOUEN via TF-M Sent: Monday, March 29, 2021 9:08 PM To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed Thanks , it solved. Best Regards Michel 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: lundi 29 mars 2021 17:37 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed Apparently I have not tested this before. Check the fix at: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9455 /Thomas Den 2021-03-29 kl. 16:35, skrev Michel JAOUEN via TF-M: Sure Variable $tfm_work point to trustedfirmware local dir. Here is my command cmake -S . -B build_dir -G"Unix Makefiles" -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=$tfm_work/toolchain_IARARM.cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo -DTEST_S=ON -DTEST_NS=ON -DTFM_PSA_API=ON -DTFM_ISOLATION_LEVEL=2 Best regards Michel 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: lundi 29 mars 2021 16:06 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed Hi Michel, Can you provide the cmake line and I'll have a look. That argument looks like a gcc argument not recognized by the IAR tools. Cheers, Thomas Den 2021-03-29 kl. 15:34, skrev Michel JAOUEN via TF-M: Hello, I got the following build issue when I build with IARAR, it occurs when build mbed-crypto IAR ANSI C/C++ Compiler V8.50.4.261/W32 for ARM Copyright 1999-2020 IAR Systems AB. Network license: 10.157.2.156 (STD) Command line error: Unexpected command line arguments: -Wno-unused-parameter Does someone else reproduce the issue ? Best regards -- 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, 1 month

1
0
0 0

Re: [TF-M] Technical Forum call - April 1 (not a joke :)

by David Wang

Hi Anton, If we still have slot, I'd like to share some thoughts and have a discussion for the TF-M documentation structure. It should be less than 20 mins. Thanks. Regards, David Wang From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Mingyang Sun via TF-M Sent: Monday, March 29, 2021 11:15 AM 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 - April 1 (not a joke :) Hi Anton, I'd like give a short session on "stateless handle and service in TF-M", about 20min. Regards, Mingyang 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: Friday, March 26, 2021 6:57 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] Technical Forum call - April 1 (not a joke :) Hi, The next Technical Forum is planned on Thursday, April 1 , 07:00-08:00 UTC (Asia time zone). Please mine the gap of the time change in Europe! 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

1
0
0 0

Re: [TF-M] Issues with alignment and buffer locations

by Ken Liu

Hi Jamie, Could help to provide the details so that we can see what the problem is? Looks like you mentioned two problems here, one for the un-aligned memory accessing and another is the FLASH read/write. For the memory alignment, to ensure the isolation setting all sections should be 32-bytes aligned; and the stack-alignment is 8 bytes. Other contents are set as default, the toolchain should have handled them correctly. Please provide the details, thank you! /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Jamie Mccrae via TF-M Sent: Monday, March 29, 2021 10:19 PM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Issues with alignment and buffer locations Hi, There seems to be a large oversight in the TF-M codeline relating to buffer alignment and locations of buffers, in terms of buffer alignment, some ARM-based silicon has restrictions on buffer alignment, generally 4-byte boundaries, this means that if a non-4 byte boundary address, buffer or data size is provided, the operation cannot be completed. Another issue is that some ARM-based silicon has restrictions on where data can be located, e.g. in RAM only for writing and not from other address spaces. I am currently trying to get TF-M working on a Nordic nRF53-based designed and have encountered these issues many times, and can see no way to set an alignment, data size or address space limitation in the whole code line which I find to be quite displeasing given that both the silicon and software are ARM-based, I would expect the software you give for silicon based on your reference designs to actually work with it out of the box rather than need lots of work to have these limitations supported. On Nordic silicon, data can only be written and read from RAM e.g. you cannot write to flash from a flash offset, and writes must be 4-byte aligned and 4-byte sized (the QSPI functionality is being used here). So I am emailing here to ask: what is the suggestion for dealing with this? Why does the baseline project not (from what I can see) have any sort of support for this? Thanks, Jamie 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, 1 month

1
0
0 0

Re: [TF-M] TF-M v1.3.0 Release Candidate 2

by Anton Komlev

Hi, New TF-M Release Candidate 2 is tagged by TF-Mv1.3.0-RC2. Please update all repositories as it contain fixes for issues found in RC1. Best regards, Anton

4 years, 1 month

1
0
0 0

Re: [TF-M] FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed

by Michel JAOUEN

Thanks , it solved. Best Regards Michel From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M Sent: lundi 29 mars 2021 17:37 To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed Apparently I have not tested this before. Check the fix at: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9455 /Thomas Den 2021-03-29 kl. 16:35, skrev Michel JAOUEN via TF-M: Sure Variable $tfm_work point to trustedfirmware local dir. Here is my command cmake -S . -B build_dir -G"Unix Makefiles" -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=$tfm_work/toolchain_IARARM.cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo -DTEST_S=ON -DTEST_NS=ON -DTFM_PSA_API=ON -DTFM_ISOLATION_LEVEL=2 Best regards Michel 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: lundi 29 mars 2021 16:06 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed Hi Michel, Can you provide the cmake line and I'll have a look. That argument looks like a gcc argument not recognized by the IAR tools. Cheers, Thomas Den 2021-03-29 kl. 15:34, skrev Michel JAOUEN via TF-M: Hello, I got the following build issue when I build with IARAR, it occurs when build mbed-crypto IAR ANSI C/C++ Compiler V8.50.4.261/W32 for ARM Copyright 1999-2020 IAR Systems AB. Network license: 10.157.2.156 (STD) Command line error: Unexpected command line arguments: -Wno-unused-parameter Does someone else reproduce the issue ? Best regards -- 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, 1 month

1
0
0 0

Re: [TF-M] FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed

by Thomas Törnblom

Apparently I have not tested this before. Check the fix at: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9455 /Thomas Den 2021-03-29 kl. 16:35, skrev Michel JAOUEN via TF-M: > > Sure > > Variable $tfm_work point to trustedfirmware local dir. > > Here is my command > > cmake -S . -B build_dir -G"Unix Makefiles" > > -DTFM_PLATFORM=stm/stm32l562e_dk > > -DTFM_TOOLCHAIN_FILE=$tfm_work/toolchain_IARARM.cmake > > -DCMAKE_BUILD_TYPE=RelWithDebInfo > > -DTEST_S=ON -DTEST_NS=ON -DTFM_PSA_API=ON -DTFM_ISOLATION_LEVEL=2 > > Best regards > > Michel > > *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:* lundi 29 mars 2021 16:06 > *To:* tf-m(a)lists.trustedfirmware.org > <mailto:tf-m@lists.trustedfirmware.org> > *Subject:* Re: [TF-M] TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed > > Hi Michel, > > Can you provide the cmake line and I'll have a look. > > That argument looks like a gcc argument not recognized by the IAR tools. > > Cheers, > Thomas > > Den 2021-03-29 kl. 15:34, skrev Michel JAOUEN via TF-M: > > Hello, > > I got the following build issue when I build with IARAR, it occurs > when build mbed-crypto > > IAR ANSI C/C++ Compiler V8.50.4.261/W32 for ARM > > Copyright 1999-2020 IAR Systems AB. > > Network license: 10.157.2.156 (STD) > > Command line error: Unexpected command line arguments: > > -Wno-unused-parameter > > Does someone else reproduce the issue ? > > Best regards > > -- > > *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, 1 month

1
0
0 0

FW: TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed

by Michel JAOUEN

Sure Variable $tfm_work point to trustedfirmware local dir. Here is my command cmake -S . -B build_dir -G"Unix Makefiles" -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=$tfm_work/toolchain_IARARM.cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo -DTEST_S=ON -DTEST_NS=ON -DTFM_PSA_API=ON -DTFM_ISOLATION_LEVEL=2 Best regards Michel 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: lundi 29 mars 2021 16:06 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed Hi Michel, Can you provide the cmake line and I'll have a look. That argument looks like a gcc argument not recognized by the IAR tools. Cheers, Thomas Den 2021-03-29 kl. 15:34, skrev Michel JAOUEN via TF-M: Hello, I got the following build issue when I build with IARAR, it occurs when build mbed-crypto IAR ANSI C/C++ Compiler V8.50.4.261/W32 for ARM Copyright 1999-2020 IAR Systems AB. Network license: 10.157.2.156 (STD) Command line error: Unexpected command line arguments: -Wno-unused-parameter Does someone else reproduce the issue ? Best regards -- 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, 1 month

1
0
0 0

Re: [TF-M] TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed

by Thomas Törnblom

Hi Michel, Can you provide the cmake line and I'll have a look. That argument looks like a gcc argument not recognized by the IAR tools. Cheers, Thomas Den 2021-03-29 kl. 15:34, skrev Michel JAOUEN via TF-M: > > Hello, > > I got the following build issue when I build with IARAR, it occurs > when build mbed-crypto > > IAR ANSI C/C++ Compiler V8.50.4.261/W32 for ARM > > Copyright 1999-2020 IAR Systems AB. > > Network license: 10.157.2.156 (STD) > > Command line error: Unexpected command line arguments: > > -Wno-unused-parameter > > Does someone else reproduce the issue ? > > Best regards > > -- *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, 1 month

1
0
0 0

TF-Mv1.3.0-RC1 => build with IARARM 8.5.4 failed

by Michel JAOUEN

Hello, I got the following build issue when I build with IARAR, it occurs when build mbed-crypto IAR ANSI C/C++ Compiler V8.50.4.261/W32 for ARM Copyright 1999-2020 IAR Systems AB. Network license: 10.157.2.156 (STD) Command line error: Unexpected command line arguments: -Wno-unused-parameter Does someone else reproduce the issue ? Best regards

4 years, 1 month

1
0
0 0

Re: [TF-M] Technical Forum call - April 1 (not a joke :)

by Mingyang Sun

Hi Anton, I'd like give a short session on "stateless handle and service in TF-M", about 20min. Regards, Mingyang From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Friday, March 26, 2021 6:57 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - April 1 (not a joke :) Hi, The next Technical Forum is planned on Thursday, April 1 , 07:00-08:00 UTC (Asia time zone). Please mine the gap of the time change in Europe! 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

1
0
0 0

Technical Forum call - April 1 (not a joke :)

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, April 1 , 07:00-08:00 UTC (Asia time zone). Please mine the gap of the time change in Europe! 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

1
0
0 0

Re: [TF-M] Regression observed in PSA Crypto after Mbed TLS upgrade to 2.25

by David Hu

Hi Alexander, Thanks for reporting this issue. Can I ask for more details of the failures? * What's the build configuration on PSoC 64 with PSA Arch test? * What's the version of TF-M? Have you tried the latest one in master branch? * What's the version of PSA Arch test? * Can you share more log of the failure test case? Thanks. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Alexander.Moore--- via TF-M Sent: Tuesday, March 23, 2021 6:42 AM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Regression observed in PSA Crypto after Mbed TLS upgrade to 2.25 Hello, After "28659c49 Crypto: Upgrade Mbed TLS to 2.25" we see the following 7 PSA Crypto test failures on PSoC64 which were passing before this commit: TEST: 206 TEST: 207 TEST: 208 TEST: 211 TEST: 237 TEST: 243 TEST: 244 Are these failures expected? As far as we can tell, there is nothing else to be done associated with the 2.25 upgrade, i.e. the build automatically pulls 2.25 down, and there are no corresponding commits to psa-arch-tests to support the upgrade or any other changes necessary. Thanks, Alex

4 years, 1 month

2
1
0 0

Re: [TF-M] Armclang linker alignement question

by Kevin Peng

Hi Michel, Quote from the armlink user guide: ALIGN on an execution region causes both the load address and execution address to be aligned. This can result in padding being added to the ELF file. To align only the execution address, use the AlignExpr expression on the base address. So I guess the alignment on execution regions (TFM_UNPRIV_CODE) overrides the alignment of the Load Region. And the fix is easy - as the user guide suggests - use AlignExpr In you case, could you try: +0 ALIGN 0x2000 -> AlignExpr(+0, 0x2000) Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Michel JAOUEN via TF-M Sent: Tuesday, March 16, 2021 10:33 PM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Armclang linker alignement question Hello, This question is relative to linker script with Compiler armclang 'V6.14' (For the other toolchain IAR , GNUARM ,it works ) I need to place code aligned to flash PAGE SIZE (0x2000 or 8192) to be able to set hardware protection. As follow , here is the description of the issue. With a Linker file having the following value for Code placement LR_CODE 0x0c024400 0x20000 { ER_TFM_CODE 0x0c024400 { *.o (RESET +First) * (+RO) } TFM_UNPRIV_CODE +0 ALIGN 0x2000 { stm32u5xx_hal*.o (+RO) tick.o (+RO) *(SFN) *armlib* } } We get the following error : Build started: Project: Project_s *** Using Compiler 'V6.14', folder: 'C:\Keil_v5\ARM\ARMCLANG\Bin' Build Project 'Project_s' - Target xxxxxxxxxxx _TFM_Appli_S' linking... xxxxxxxxxxx_S\Exe\Project.axf: Error: L6244E: Load region LR_CODE address (0x0c024400) not aligned on a 8192 byte boundary. Not enough information to list image symbols. Finished: 1 information, 0 warning and 1 error messages. " xxxxxxxxxxx _S\Exe\Project.axf" - 1 Error(s), 0 Warning(s). Target not created. Build Time Elapsed: 00:00:03 If we change the linker file as follow : LR_CODE 0x0c024400 0x20000 { ER_TFM_CODE 0x0c024400 { *.o (RESET +First) * (+RO) } TFM_UNPRIV_CODE +0 ALIGN 0x400 { stm32u5xx_hal*.o (+RO) tick.o (+RO) *(SFN) *armlib* } } No Error is reported. Is this an known issue with ARMCLANG ? Best Regards .

4 years, 1 month

2
5
0 0

Regression observed in PSA Crypto after Mbed TLS upgrade to 2.25

by Alexander.Moore＠infineon.com

Hello, After "28659c49 Crypto: Upgrade Mbed TLS to 2.25" we see the following 7 PSA Crypto test failures on PSoC64 which were passing before this commit: TEST: 206 TEST: 207 TEST: 208 TEST: 211 TEST: 237 TEST: 243 TEST: 244 Are these failures expected? As far as we can tell, there is nothing else to be done associated with the 2.25 upgrade, i.e. the build automatically pulls 2.25 down, and there are no corresponding commits to psa-arch-tests to support the upgrade or any other changes necessary. Thanks, Alex

4 years, 1 month

1
0
0 0

TF-M v1.3.0 Release Candidate 1 is ready

by Anton Komlev

Hi, All TF-M repositories are tagged with TF-Mv1.3.0-RC1 tag. Code is frozen for the release candidate testing. Please use this tag for your tests and report any issues found by the end of April 2. The best, Anton

4 years, 1 month

1
0
0 0

TF-M at Linaro Connect 2021

by Anton Komlev

Hello, This is the list of TF-M related sessions on Linaro Virtual Connect 2021 https://connect.linaro.org/schedule/ * 23/3 @ 17:15 Introducing the Trusted Services project - Julian Hall * 23/3 @ 18:30 Physical Attack Mitigation - Tamas Ban, Raef Coles * 24/3 @ 9:45 Firmware update service in TF-M - Sherry Zhang * 24/3 @ 10:45 Firmware Framework - M 1.1 feature update in TF-M - Ken Liu * 25/3 @ 12:45 X.509 Certificate Management with Zephyr/TF-M - David Vincze * 25/3 @ 13:15 Essential ARM Cortex-M Debugging with GDB - Kevin Townsend Cheers, Anton

4 years, 1 month

1
0
0 0

Re: [TF-M] Static analysic checking & reporting - inquiry about interest

by Karl Zhang

Hi Ioannis, Thanks for the suggestions. There are already a lot of info from Anton and Leonardo, I would like to clarify from: * The static check is applied to the CI per-patch job, it will feedback to the Gerrit review of each patch, this has been enabled per the recent mail, attached. * Coverity scan daily, and upload the result, https://scan.coverity.com/projects/trusted-firmware-m-35b064f0-65c2-4afb-9b… BR Karl From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Leonardo Sandoval via TF-M Sent: 2021年3月17日 23:15 To: Anton Komlev <Anton.Komlev(a)arm.com<mailto:Anton.Komlev@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] Static analysic checking & reporting - inquiry about interest Hi Anton & Ioannis, Karl's presentation goes in detail but I just want to highlight that TF-M (and also TF-A) are two type of static checks: [1] Project related static checks & cppcheck executed per-patch [2] Coverity scan, executed daily For 1, other project-related static checks can be included. For 2, coverity scan coverage is about 42 % so one community effort would be to increase it and cover mode code. In order to increase the latter, 'coverity needs to compile more code', which means that more platforms/parameters should be taken into account. Check this file [3] in case you want to participate in this effort. [1] https://ci.trustedfirmware.org/job/tf-m-static/ [2] https://ci.trustedfirmware.org/job/tf-m-coverity/ [3] https://git.trustedfirmware.org/ci/tf-m-ci-scripts.git/tree/script/tf-cover… On Wed, 17 Mar 2021 at 05:31, Anton Komlev via TF-M <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> wrote: Hi Ioannis, Thanks for bringing up the important topic up. Believe Karl will comment the details of it in TF-M but you could be interested watch his presentation on Tech Forum from Feb 4th. https://www.trustedfirmware.org/docs/tech_forum_20210204_TF-M_openCI_static… Forum records are here: https://www.trustedfirmware.org/meetings/tf-m-technical-forum/ And yes, the check we have now is not enough so any improvements are welcome. Hope it helps, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Glaropoulos, Ioannis via TF-M Sent: Wednesday, March 17, 2021 11:15 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] Static analysic checking & reporting - inquiry about interest Hi everyone, I would like to ask whether there is an interest in the Project for integrating static code analysis tools with the rest of CI, on the TF-M code base. To the best of my knowledge, this is not available today. In short, a simple process would involve maintaining and running static analysis checking (e.g. using Coverity or any other licensed tool) in nightly/weekly/etc. CI runs, reporting the found issues in the Project, triaging them, and tracking the progress of fixing the issues that are identified as real bugs. Has this topic been raised already in the Project? If not, is this something the project members would consider adding as part of the TF-M Project QA/release process? Thanks! Ioannis Glaropoulos Nordic Semiconductor -- 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, 1 month

1
0
0 0

Re: [TF-M] Technical Forum call - March 18

by Anton Komlev

The agenda for the forum tomorrow: 1. Upcoming changes in Secure Partition Manager (SPM) 2. AOB Thanks, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: Tuesday, March 16, 2021 8:20 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Technical Forum call - March 18 Hi, I would introduce the upcoming SPM changes in general. Assume it is a big topic so 40 mins are needed. /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: Thursday, March 11, 2021 12:56 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] Technical Forum call - March 18 Hello, The next Technical Forum is planned on Thursday, March 18 at 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

1
0
0 0

Re: [TF-M] Static analysic checking & reporting - inquiry about interest

by Leonardo Sandoval

Hi Anton & Ioannis, Karl's presentation goes in detail but I just want to highlight that TF-M (and also TF-A) are two type of static checks: [1] Project related static checks & cppcheck executed per-patch [2] Coverity scan, executed daily For 1, other project-related static checks can be included. For 2, coverity scan coverage is about 42 % so one community effort would be to increase it and cover mode code. In order to increase the latter, 'coverity needs to compile more code', which means that more platforms/parameters should be taken into account. Check this file [3] in case you want to participate in this effort. [1] https://ci.trustedfirmware.org/job/tf-m-static/ [2] https://ci.trustedfirmware.org/job/tf-m-coverity/ [3] https://git.trustedfirmware.org/ci/tf-m-ci-scripts.git/tree/script/tf-cover… On Wed, 17 Mar 2021 at 05:31, Anton Komlev via TF-M < tf-m(a)lists.trustedfirmware.org> wrote: > Hi Ioannis, > > > > Thanks for bringing up the important topic up. Believe Karl will comment > the details of it in TF-M but you could be interested watch his > presentation on Tech Forum from Feb 4th. > > > https://www.trustedfirmware.org/docs/tech_forum_20210204_TF-M_openCI_static… > > Forum records are here: > > https://www.trustedfirmware.org/meetings/tf-m-technical-forum/ > > > > And yes, the check we have now is not enough so any improvements are > welcome. > > > > Hope it helps, > > Anton > > > > > > *From:* TF-M <tf-m-bounces(a)lists.trustedfirmware.org> *On Behalf Of *Glaropoulos, > Ioannis via TF-M > *Sent:* Wednesday, March 17, 2021 11:15 AM > *To:* tf-m(a)lists.trustedfirmware.org > *Subject:* [TF-M] Static analysic checking & reporting - inquiry about > interest > > > > Hi everyone, > > > > I would like to ask whether there is an interest in the Project for > integrating static code analysis tools with the rest of CI, on the TF-M > code base. To the best of my knowledge, this is not available today. In > short, a simple process would involve maintaining and running static > analysis checking (e.g. using Coverity or any other licensed tool) in > nightly/weekly/etc. CI runs, reporting the found issues in the Project, > triaging them, and tracking the progress of fixing the issues that are > identified as real bugs. Has this topic been raised already in the Project? > If not, is this something the project members would consider adding as part > of the TF-M Project QA/release process? > > > > Thanks! > > Ioannis Glaropoulos > > Nordic Semiconductor > > > > > -- > TF-M mailing list > TF-M(a)lists.trustedfirmware.org > https://lists.trustedfirmware.org/mailman/listinfo/tf-m >

4 years, 1 month

1
0
0 0

Re: [TF-M] Static analysic checking & reporting - inquiry about interest

by Anton Komlev

Hi Ioannis, Thanks for bringing up the important topic up. Believe Karl will comment the details of it in TF-M but you could be interested watch his presentation on Tech Forum from Feb 4th. https://www.trustedfirmware.org/docs/tech_forum_20210204_TF-M_openCI_static… Forum records are here: https://www.trustedfirmware.org/meetings/tf-m-technical-forum/ And yes, the check we have now is not enough so any improvements are welcome. Hope it helps, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Glaropoulos, Ioannis via TF-M Sent: Wednesday, March 17, 2021 11:15 AM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Static analysic checking & reporting - inquiry about interest Hi everyone, I would like to ask whether there is an interest in the Project for integrating static code analysis tools with the rest of CI, on the TF-M code base. To the best of my knowledge, this is not available today. In short, a simple process would involve maintaining and running static analysis checking (e.g. using Coverity or any other licensed tool) in nightly/weekly/etc. CI runs, reporting the found issues in the Project, triaging them, and tracking the progress of fixing the issues that are identified as real bugs. Has this topic been raised already in the Project? If not, is this something the project members would consider adding as part of the TF-M Project QA/release process? Thanks! Ioannis Glaropoulos Nordic Semiconductor

4 years, 2 months

1
0
0 0

Static analysic checking & reporting - inquiry about interest

by Glaropoulos, Ioannis

Hi everyone, I would like to ask whether there is an interest in the Project for integrating static code analysis tools with the rest of CI, on the TF-M code base. To the best of my knowledge, this is not available today. In short, a simple process would involve maintaining and running static analysis checking (e.g. using Coverity or any other licensed tool) in nightly/weekly/etc. CI runs, reporting the found issues in the Project, triaging them, and tracking the progress of fixing the issues that are identified as real bugs. Has this topic been raised already in the Project? If not, is this something the project members would consider adding as part of the TF-M Project QA/release process? Thanks! Ioannis Glaropoulos Nordic Semiconductor

4 years, 2 months

1
0
0 0

Re: [TF-M] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board

by Edward Yang

Hi Jamie, Thanks for your reply,I have tried with the latest master, and it works OK. The commit info of TF-M version which I tested before is as follow: commit 4f953f5f50809991510003e588695508effcdbb0 Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 http://www.mxic.com.cn Jamie Fox via TF-M <tf-m(a)lists.trustedfirmware.org> Sent by: "TF-M" <tf-m-bounces(a)lists.trustedfirmware.org> 2021/03/15 22:22 Please respond to Jamie Fox <Jamie.Fox(a)arm.com> To "tf-m(a)lists.trustedfirmware.org" <tf-m(a)lists.trustedfirmware.org> cc Subject Re: [TF-M] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board Hi, Which version of TF-M does the problem occur with? If it’s not the latest master, please can you retry with that? Are you able to find which commit introduces the issue? Recently this patch was merged to fix an issue on the STM platform https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8686. It would be a good place to start to check if that commit has an effect. Kind regards, Jamie From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: 15 March 2021 12:55 To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board Hi Ken, Thank you for your reply. I have enabled the TEST_S and tested again, it turned out to be the same results. The test log is as 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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_PS_TEST_2XXX)... > Executing 'TFM_PS_TEST_2001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_PS_TEST_2XXX)... > Executing 'TFM_PS_TEST_2001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_PS_TEST_2XXX)... > Executing 'TFM_PS_TEST_2001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_PS_TEST_2XXX)... > Executing 'TFM_PS_TEST_2001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... The building procedure log is as following: (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ cmake .. -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_NS=ON -DTEST_S=ON -- 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 PSA manifests: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/psa_manifest/tfm_protected_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/auto_generated/intermedia_tfm_protected_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/psa_manifest/tfm_internal_trusted_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/intermedia_tfm_internal_trusted_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/psa_manifest/tfm_audit_logging.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/auto_generated/intermedia_tfm_audit_logging.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/psa_manifest/tfm_crypto.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/auto_generated/intermedia_tfm_crypto.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/psa_manifest/tfm_platform.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/auto_generated/intermedia_tfm_platform.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/psa_manifest/tfm_initial_attestation.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/auto_generated/intermedia_tfm_initial_attestation.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/psa_manifest/tfm_ss_core_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/auto_generated/intermedia_tfm_ss_core_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/psa_manifest/tfm_ss_core_test_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/auto_generated/intermedia_tfm_ss_core_test_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/psa_manifest/tfm_secure_client_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/auto_generated/intermedia_tfm_secure_client_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/psa_manifest/tfm_ipc_service_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/auto_generated/intermedia_tfm_ipc_service_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/psa_manifest/tfm_ipc_client_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/auto_generated/intermedia_tfm_ipc_client_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/psa_manifest/tfm_irq_test_service_1.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/auto_generated/intermedia_tfm_irq_test_service_1.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/psa_manifest/tfm_ps_test_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/auto_generated/intermedia_tfm_ps_test_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/psa_manifest/tfm_secure_client_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/auto_generated/intermedia_tfm_secure_client_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/psa_manifest/tfm_psa_proxy.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/auto_generated/intermedia_tfm_psa_proxy.c Start to generate file from the generated list: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_spm_db_func.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_spm_db_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/tfm_service_list.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_veneers.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/tfm_veneers.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_secure_irq_handlers.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_secure_irq_handlers_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/sid.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/pid.h 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.275", 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_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_GENERATOR_MODULE_DISABLED is set to FALSE -- CRYPTO_ASYMMETRIC_MODULE_DISABLED is set to FALSE -- CRYPTO_ENGINE_BUF_SIZE is set to 0x2080 -- CRYPTO_CONC_OPER_NUM is set to 8 -- ---------- Display crypto configuration - stop --------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- 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 ------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- Configuring done -- Generating done -- Build files have been written to: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ make install Scanning dependencies of target tfm_generated_files [ 0%] Built target tfm_generated_files Scanning dependencies of target platform_ns [ 0%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 0%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/common/uart_stdout.o [ 2%] Linking C static library libplatform_ns.a [ 2%] Built target platform_ns Scanning dependencies of target tfm_ns_log [ 2%] Building C object ns_log/CMakeFiles/tfm_ns_log.dir/tfm_log_raw.o [ 3%] Linking C static library libtfm_ns_log.a [ 3%] Built target tfm_ns_log Scanning dependencies of target tfm_test_suite_platform_ns [ 3%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/platform_tests_common.o [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/non_secure/platform_ns_interface_testsuite.o [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework.o [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_helpers.o [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 4%] Linking C static library libtfm_test_suite_platform_ns.a [ 4%] Built target tfm_test_suite_platform_ns Scanning dependencies of target tfm_t_cose [ 4%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_sign.o [ 4%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_verify.o [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_util.o [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_parameters.o [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/crypto_adapters/t_cose_psa_crypto.o [ 5%] Linking C static library libtfm_t_cose.a [ 5%] Built target tfm_t_cose Scanning dependencies of target tfm_qcbor [ 5%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/ieee754.o [ 5%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_encode.o [ 5%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_decode.o [ 5%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/UsefulBuf.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/util/qcbor_util.o [ 6%] Linking C static library libtfm_qcbor.a [ 6%] Built target tfm_qcbor Scanning dependencies of target tfm_qcbor_test [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/float_tests.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/half_to_double_from_rfc7049.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_decode_tests.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_encode_tests.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/run_tests.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/UsefulBuf_Tests.o [ 7%] Linking C static library libtfm_qcbor_test.a [ 7%] Built target tfm_qcbor_test Scanning dependencies of target tfm_t_cose_test [ 7%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/run_tests.o [ 7%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_psa_test_key.o [ 8%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_test_messages.o [ 8%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_sign_verify_test.o [ 8%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_test.o [ 8%] Linking C static library libtfm_t_cose_test.a [ 8%] Built target tfm_t_cose_test Scanning dependencies of target tfm_api_ns [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_platform_func_api.o [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_audit_func_api.o [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ps_func_api.o [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_its_func_api.o [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_crypto_func_api.o [ 10%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_initial_attestation_func_api.o [ 10%] 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 [ 10%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ns_interface.o [ 10%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/test_services/tfm_secure_client_service/tfm_secure_client_service_api.o [ 10%] Linking C static library libtfm_api_ns.a [ 10%] Built target tfm_api_ns Scanning dependencies of target tfm_s_scatter [ 10%] Building C object platform/target/CMakeFiles/tfm_s_scatter.dir/__/__/__/common/gcc/tfm_common_s.o [ 10%] Built target tfm_s_scatter Scanning dependencies of target tfm_app_rot_partition_secure_client_2 [ 11%] Building C object test/test_services/tfm_secure_client_2/CMakeFiles/tfm_app_rot_partition_secure_client_2.dir/tfm_secure_client_2.o [ 11%] Building C object test/test_services/tfm_secure_client_2/CMakeFiles/tfm_app_rot_partition_secure_client_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 11%] Linking C static library libtfm_app_rot_partition_secure_client_2.a [ 11%] Built target tfm_app_rot_partition_secure_client_2 Scanning dependencies of target tfm_psa_rot_partition_secure_client_service [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/tfm_secure_client_service.o [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/__/__/framework/test_framework.o [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/__/__/framework/test_framework_helpers.o [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/__/__/framework/test_framework_integ_test_helper.o [ 12%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/__/__/framework/secure_suites.o [ 12%] Linking C static library libtfm_psa_rot_partition_secure_client_service.a [ 12%] Built target tfm_psa_rot_partition_secure_client_service Scanning dependencies of target tfm_psa_rot_partition_ps_test [ 12%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/tfm_ps_test_service.o [ 12%] 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 [ 13%] Linking C static library libtfm_psa_rot_partition_ps_test.a [ 13%] Built target tfm_psa_rot_partition_ps_test Scanning dependencies of target tfm_app_rot_partition_core_test_2 [ 13%] 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 [ 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/interface/src/log/tfm_log_raw.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/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_helpers.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_integ_test_helper.o [ 15%] Linking C static library libtfm_psa_rot_partition_core_test.a [ 15%] Built target tfm_psa_rot_partition_core_test Scanning dependencies of target tfm_test_suite_ps_s [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/suites/ps/secure/psa_ps_s_interface_testsuite.o [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/suites/ps/secure/psa_ps_s_reliability_testsuite.o [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/suites/ps/secure/ps_rollback_protection_testsuite.o [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/framework/test_framework.o [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/framework/test_framework_helpers.o [ 16%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/framework/test_framework_integ_test_helper.o [ 16%] Linking C static library libtfm_test_suite_ps_s.a [ 16%] Built target tfm_test_suite_ps_s Scanning dependencies of target tfm_test_suite_crypto_s [ 16%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/suites/crypto/crypto_tests_common.o [ 16%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/suites/crypto/secure/crypto_sec_interface_testsuite.o [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/framework/test_framework.o [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/framework/test_framework_helpers.o [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/framework/test_framework_integ_test_helper.o [ 17%] Linking C static library libtfm_test_suite_crypto_s.a [ 17%] Built target tfm_test_suite_crypto_s Scanning dependencies of target tfm_test_suite_audit_s [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_audit_s.dir/__/suites/audit/secure/audit_s_interface_testsuite.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_audit_s.dir/__/framework/test_framework.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_audit_s.dir/__/framework/test_framework_helpers.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_audit_s.dir/__/framework/test_framework_integ_test_helper.o [ 18%] Linking C static library libtfm_test_suite_audit_s.a [ 18%] Built target tfm_test_suite_audit_s Scanning dependencies of target tfm_test_suite_attestation_s [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/attest_public_key.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/attest_token_test.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/attest_token_decode_common.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/attest_token_decode_asymmetric.o [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/secure/attest_asymmetric_s_interface_testsuite.o [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/framework/test_framework.o [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/framework/test_framework_helpers.o [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/framework/test_framework_integ_test_helper.o [ 19%] Linking C static library libtfm_test_suite_attestation_s.a [ 19%] Built target tfm_test_suite_attestation_s Scanning dependencies of target tfm_test_suite_platform_s [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/suites/platform/platform_tests_common.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/suites/platform/secure/platform_s_interface_testsuite.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/framework/test_framework.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/framework/test_framework_helpers.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/framework/test_framework_integ_test_helper.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 20%] Linking C static library libtfm_test_suite_platform_s.a [ 20%] Built target tfm_test_suite_platform_s Scanning dependencies of target tfm_test_suite_its_s [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/suites/its/its_tests_common.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/suites/its/secure/psa_its_s_interface_testsuite.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/suites/its/secure/psa_its_s_reliability_testsuite.o [ 21%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 21%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/framework/test_framework.o [ 21%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/framework/test_framework_helpers.o [ 21%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/framework/test_framework_integ_test_helper.o [ 21%] Linking C static library libtfm_test_suite_its_s.a [ 21%] Built target tfm_test_suite_its_s Scanning dependencies of target platform_s [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/system_stm32l5xx.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/spm_hal.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_hal_isolation.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/target_cfg.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/low_level_device.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc_ex.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng_ex.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_isolation_mpu_v8m.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_platform_system.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/attest_hal.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_ps.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_its.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_platform.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/uart_stdout.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_spm_logdev_peripheral.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_memory_symbols.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/nv_counters.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/crypto_keys.o [ 28%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_rotpk.o [ 28%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 28%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/log/tfm_log_raw.o [ 28%] Linking C static library libplatform_s.a [ 28%] Built target platform_s Scanning dependencies of target tfm_spm [ 28%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_boot_data.o [ 28%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_utils.o [ 28%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/utilities.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/spm_log.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_mem_check.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/main.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/arch.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/spm_func.o /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_seal_psp_stacks': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:91:5: warning: array subscript 1 is outside array bounds of 'uint32_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds] 91 | *(arm_lib_stck_seal_base + 1) = TFM_STACK_SEAL_VALUE; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:23: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:18: note: while referencing 'Image$$ARM_LIB_STACK_SEAL$$ZI$$Base' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:12:25: note: in definition of macro 'REGION' 12 | #define REGION(a, b, c) a##b##c | ^ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:15:47: note: in expansion of macro 'REGION_NAME' 15 | #define REGION_DECLARE_T(a, b, c, t) extern t REGION_NAME(a, b, c) | ^~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:1: note: in expansion of macro 'REGION_DECLARE_T' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_sfn_request_handler': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:450:31: warning: 'iovecs.orig_outvec' may be used uninitialized in this function [-Wmaybe-uninitialized] 450 | runtime_data->orig_outvec = iovec_ptr->orig_outvec; | ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.orig_outvec' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:446:5: warning: 'iovecs.out_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 446 | for (i = 0U; i < runtime_data->iovec_args.out_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.out_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:441:5: warning: 'iovecs.in_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 441 | for (i = 0U; i < runtime_data->iovec_args.in_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.in_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_core_svcalls_func.o [ 30%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_nspm_func.o [ 30%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_secure_api.o [ 30%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/log/tfm_log_raw.o [ 30%] Linking C static library libtfm_spm.a [ 30%] Built target tfm_spm Scanning dependencies of target tfm_psa_rot_partition_platform [ 30%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/platform_sp.o [ 30%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 30%] Linking C static library libtfm_psa_rot_partition_platform.a [ 30%] Built target tfm_psa_rot_partition_platform Scanning dependencies of target tfm_psa_rot_partition_its [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_its_req_mngr.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_internal_trusted_storage.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/its_utils.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nand.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nor.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_ram.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_dblock.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_mblock.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 32%] Linking C static library libtfm_psa_rot_partition_its.a [ 32%] Built target tfm_psa_rot_partition_its Scanning dependencies of target tfm_app_rot_partition_ps [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_ps_req_mngr.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_protected_storage.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_system.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_table.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_utils.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/crypto/ps_crypto_interface.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_encrypted_object.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/ps/secure/nv_counters/test_ps_nv_counters.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 33%] Linking C static library libtfm_app_rot_partition_ps.a [ 33%] Built target tfm_app_rot_partition_ps Scanning dependencies of target tfm_psa_rot_partition_attestation [ 33%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest.o [ 33%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest_req_mngr.o [ 33%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_core.o [ 34%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_asymmetric_key.o [ 34%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_token_encode.o [ 34%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 34%] Linking C static library libtfm_psa_rot_partition_attestation.a [ 34%] Built target tfm_psa_rot_partition_attestation Scanning dependencies of target crypto_service_mbedcrypto [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aes.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aesni.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/arc4.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aria.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1parse.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1write.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/base64.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/bignum.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/blowfish.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/camellia.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ccm.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chacha20.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chachapoly.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher_wrap.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cmac.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ctr_drbg.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/des.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/dhm.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdh.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdsa.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecjpake.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp_curves.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy_poll.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/error.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/gcm.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/havege.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hkdf.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hmac_drbg.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md2.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md4.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md5.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/memory_buffer_alloc.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/nist_kw.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/oid.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/padlock.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pem.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk_wrap.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs12.o [ 41%] 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 [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform_util.o [ 42%] 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_se.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_slot_management.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_storage.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_its_file.o [ 43%] 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_internal.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha1.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha256.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha512.o [ 44%] 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/xtea.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/secure_fw/partitions/crypto/tfm_mbedcrypto_alt.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%] Linking C static library libmbedcrypto.a [ 46%] Built target crypto_service_mbedcrypto Scanning dependencies of target tfm_psa_rot_partition_crypto [ 46%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_init.o [ 46%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_alloc.o [ 46%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_cipher.o [ 46%] 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 [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key_derivation.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C static library libtfm_psa_rot_partition_crypto.a [ 48%] Built target tfm_psa_rot_partition_crypto Scanning dependencies of target tfm_psa_rot_partition_audit [ 48%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/audit_core.o [ 48%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 49%] Linking C static library libtfm_psa_rot_partition_audit.a [ 49%] Built target tfm_psa_rot_partition_audit Scanning dependencies of target tfm_sprt [ 49%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcmp.o [ 49%] 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/__/__/audit_logging/tfm_audit_secure_api.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 [ 52%] 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 [ 52%] 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_secure_client_2/tfm_secure_client_2_api.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/log/tfm_log_raw.o [ 52%] Linking C static library libtfm_sprt.a [ 52%] Built target tfm_sprt Scanning dependencies of target tfm_s_log [ 53%] 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 [ 53%] Linking C static library libtfm_s_log.a [ 53%] Built target tfm_s_log Scanning dependencies of target tfm_s [ 53%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/spm/cmsis_func/tfm_veneers.o [ 53%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 54%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_s.o [ 54%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/log/tfm_log_raw.o [ 54%] Linking C executable ../bin/tfm_s.axf Memory region Used Size Region Size %age Used FLASH: 205120 B 219328 B 93.52% RAM: 56760 B 127 KB 43.65% VENEERS: 800 B 832 B 96.15% [ 54%] Built target tfm_s [ 55%] Generating s_veneers.o Scanning dependencies of target tfm_s_veneers [ 55%] Generating s_veneers.o [ 55%] Linking C static library libtfm_s_veneers.a [ 55%] Built target tfm_s_veneers Scanning dependencies of target tfm_test_suite_attestation_ns [ 55%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_public_key.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_test.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_common.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_asymmetric.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/non_secure/attest_asymmetric_ns_interface_testsuite.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_helpers.o [ 57%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 57%] Linking C static library libtfm_test_suite_attestation_ns.a [ 57%] Built target tfm_test_suite_attestation_ns Scanning dependencies of target tfm_test_suite_audit_ns [ 57%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/non_secure/audit_ns_interface_testsuite.o [ 58%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework.o [ 58%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_helpers.o [ 58%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 58%] Linking C static library libtfm_test_suite_audit_ns.a [ 58%] Built target tfm_test_suite_audit_ns Scanning dependencies of target tfm_test_suite_crypto_ns [ 58%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/crypto_tests_common.o [ 58%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/non_secure/crypto_ns_interface_testsuite.o [ 59%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework.o [ 59%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_helpers.o [ 59%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 59%] Linking C static library libtfm_test_suite_crypto_ns.a [ 59%] Built target tfm_test_suite_crypto_ns Scanning dependencies of target tfm_test_suite_its_ns [ 59%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/its_tests_common.o [ 60%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/non_secure/psa_its_ns_interface_testsuite.o [ 60%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework.o [ 60%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_helpers.o [ 60%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 60%] 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 [ 60%] 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 [ 61%] 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 [ 61%] Linking C static library libtfm_test_suite_its_ns.a [ 61%] Built target tfm_test_suite_its_ns Scanning dependencies of target tfm_test_suite_qcbor_ns [ 61%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/non_secure/qcbor_ns_testsuite.o [ 61%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework.o [ 61%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_helpers.o [ 61%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 62%] Linking C static library libtfm_test_suite_qcbor_ns.a [ 62%] Built target tfm_test_suite_qcbor_ns Scanning dependencies of target tfm_test_suite_ps_ns [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/ns_test_helpers.o [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/psa_ps_ns_interface_testsuite.o [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework.o [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_helpers.o [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 64%] Linking C static library libtfm_test_suite_ps_ns.a [ 64%] Built target tfm_test_suite_ps_ns Scanning dependencies of target tfm_test_suite_t_cose_ns [ 64%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/non_secure/t_cose_ns_testsuite.o [ 64%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework.o [ 64%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_helpers.o [ 64%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 65%] Linking C static library libtfm_test_suite_t_cose_ns.a [ 65%] Built target tfm_test_suite_t_cose_ns Scanning dependencies of target tfm_test_suite_core_ns [ 65%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_interactive_testsuite.o [ 65%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_positive_testsuite.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_test_api.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_helpers.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/non_secure_suites.o [ 66%] 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 [ 67%] 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 [ 67%] 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 [ 67%] Linking C static library libtfm_test_suite_core_ns.a [ 67%] Built target tfm_test_suite_core_ns Scanning dependencies of target tfm_ns_integration_test [ 67%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/tfm_integ_test.o [ 67%] 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 [ 67%] 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 [ 67%] 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 [ 67%] 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 [ 68%] 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 [ 68%] 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 [ 68%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/os_wrapper_cmsis_rtos_v2.o [ 68%] Linking C static library libtfm_ns_integration_test.a [ 68%] Built target tfm_ns_integration_test Scanning dependencies of target tfm_ns_scatter [ 68%] Building C object platform/target/CMakeFiles/tfm_ns_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_ns.o [ 68%] Built target tfm_ns_scatter Scanning dependencies of target tfm_ns [ 69%] Building C object app/CMakeFiles/tfm_ns.dir/main_ns.o [ 69%] 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 [ 69%] 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 [ 69%] 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 [ 69%] Building C object app/CMakeFiles/tfm_ns.dir/os_wrapper_cmsis_rtos_v2.o [ 69%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/non_secure_suites.o [ 70%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework.o [ 70%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_helpers.o [ 70%] 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 [ 70%] Linking C executable ../bin/tfm_ns.axf Memory region Used Size Region Size %age Used FLASH: 128104 B 159 KB 78.68% RAM: 30208 B 128 KB 23.05% [ 70%] Built target tfm_ns Scanning dependencies of target tfm_ns_hex [ 71%] Generating ../bin/tfm_ns.hex [ 71%] Built target tfm_ns_hex Scanning dependencies of target tfm_ns_bin [ 71%] Generating ../bin/tfm_ns.bin [ 71%] Built target tfm_ns_bin Scanning dependencies of target tfm_ns_elf [ 71%] Generating ../bin/tfm_ns.elf [ 71%] Built target tfm_ns_elf Scanning dependencies of target tfm_ns_binaries [ 71%] Built target tfm_ns_binaries Scanning dependencies of target tfm_s_hex [ 71%] Generating ../bin/tfm_s.hex [ 71%] Built target tfm_s_hex Scanning dependencies of target tfm_s_bin [ 71%] Generating ../bin/tfm_s.bin [ 71%] Built target tfm_s_bin Scanning dependencies of target tfm_s_elf [ 71%] Generating ../bin/tfm_s.elf [ 71%] Built target tfm_s_elf Scanning dependencies of target tfm_s_binaries [ 71%] Built target tfm_s_binaries Scanning dependencies of target crypto_service_mbedx509 [ 71%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/certs.o [ 71%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/pkcs11.o [ 71%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509.o [ 71%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_create.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crl.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crt.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_csr.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_crt.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_csr.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 73%] Linking C static library libmbedx509.a [ 73%] Built target crypto_service_mbedx509 Scanning dependencies of target crypto_service_mbedtls [ 73%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/debug.o [ 73%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/net_sockets.o [ 73%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cache.o [ 73%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ciphersuites.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cli.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cookie.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_msg.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_srv.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ticket.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_tls.o [ 75%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 75%] Linking C static library libmbedtls.a [ 75%] Built target crypto_service_mbedtls Scanning dependencies of target bl2_scatter [ 75%] Building C object platform/target/CMakeFiles/bl2_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_bl2.o [ 75%] Built target bl2_scatter Scanning dependencies of target platform_bl2 [ 75%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 75%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/boot_hal.o [ 75%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 75%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/tfm_low_level_security.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/low_level_device.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/boot_hal.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/uart_stdout.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/nv_counters.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_rotpk.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 79%] Linking C static library libplatform_bl2.a [ 79%] Built target platform_bl2 Scanning dependencies of target bl2_mbedcrypto [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aes.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aesni.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/arc4.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aria.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1parse.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1write.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/base64.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/bignum.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/blowfish.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/camellia.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ccm.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chacha20.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chachapoly.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher_wrap.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cmac.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ctr_drbg.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/des.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/dhm.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdh.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdsa.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecjpake.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp_curves.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy_poll.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/error.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/gcm.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/havege.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hkdf.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hmac_drbg.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md2.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md4.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/nist_kw.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/oid.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/padlock.o [ 86%] 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_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_internal.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 [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version_features.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/xtea.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/caps.o [ 92%] 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 [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_rsa.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_validate.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/loader.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_misc.o [ 93%] 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 [ 94%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/tlv.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 [ 95%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_legacy.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_bl2.o [ 95%] 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 [ 96%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/Components/mx25lm51245g/mx25lm51245g.o [ 96%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/stm32l562e_dk/src/stm32l562e_discovery_ospi.o [ 96%] Linking C executable ../bin/bl2.axf Memory region Used Size Region Size %age Used FLASH: 46360 B 66 KB 68.60% FLASH_NOHDP: 244 B 6 KB 3.97% RAM: 27016 B 63 KB 41.88% [ 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/certs.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/pkcs11.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_create.o [ 97%] 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 [ 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 [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cache.o [ 99%] 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 [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ticket.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_tls.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_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/stm_tool.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/regression.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/preprocess.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/TFM_UPDATE.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/postbuild.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/flash_layout.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/region_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/image_macros_to_preprocess_bl2.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/lib/s_veneers.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/client.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/error.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/msg_queue.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/mutex.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/semaphore.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/thread.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/tick.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_manifest/sid.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_interface.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_svc.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/ext/tz_context.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm/veneers/tfm_veneers.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/protected_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/internal_trusted_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/storage_common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_extra.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_compat.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_client_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_sizes.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_types.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_values.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_crypto_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/initial_attestation.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_platform_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ns_interface.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ps_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_its_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_crypto_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_initial_attestation_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_audit_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_platform_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/assemble.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__ -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__/macro_parser.cpython-36.pyc -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/requirements.txt -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper/wrapper.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_s.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_ns.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/keys/root-RSA-3072_1.pem Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 http://www.mxic.com.cn Ken Liu via TF-M <tf-m(a)lists.trustedfirmware.org> Sent by: "TF-M" <tf-m-bounces(a)lists.trustedfirmware.org> 2021/03/12 22:24 Please respond to 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] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board Hi Edward, Noticed that you did not open S test when enabling NS test, we met a similar issue recently. Disable S test would cause one of the test partitions not included into system and you would got an panic when connection to the SID. Should be: ‘TFM_SP_SECURE_CLIENT_2’. Can you try to enable the TEST_S and try again? Also welcome to create a fix for it. Thanks. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: Friday, March 12, 2021 7:44 PM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board Hi everyone, When I run tf-m-tests with stm32l562e_dk discovery board,the following info are showed repeatly,I think this is abnormal,I am not sure whether anyone else has the same problem. [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA protected storage NS interface tests (TFM_PS_TEST_1XXX)... > Executing 'TFM_PS_TEST_1001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA protected storage NS interface tests (TFM_PS_TEST_1XXX)... > Executing 'TFM_PS_TEST_1001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... It seems software reset happened when TFM_PS_TEST_1001 executed. Below is the detailed software version info: The compiler version:gcc-arm-none-eabi-9-2020-q2-update The tf-m source code version: git clone https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git git checkout 4f953f5f50809991510003e588695508effcdbb0 Mbed Crypto(mbedtls-2.24.0) tf-m-tests(98adf32d)：https://git.trustedfirmware.org/TF-M/tf-m-tests.git MCUboot(81d19f0)：https://github.com/mcu-tools/mcuboot psa-arch-tests(90c8e680)：https://github.com/ARM-software/psa-arch-tests The build process logs are as follows: (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ cmake .. -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_NS=ON -- 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 PSA manifests: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/psa_manifest/tfm_protected_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/auto_generated/intermedia_tfm_protected_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/psa_manifest/tfm_internal_trusted_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/intermedia_tfm_internal_trusted_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/psa_manifest/tfm_audit_logging.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/auto_generated/intermedia_tfm_audit_logging.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/psa_manifest/tfm_crypto.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/auto_generated/intermedia_tfm_crypto.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/psa_manifest/tfm_platform.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/auto_generated/intermedia_tfm_platform.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/psa_manifest/tfm_initial_attestation.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/auto_generated/intermedia_tfm_initial_attestation.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/psa_manifest/tfm_ss_core_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/auto_generated/intermedia_tfm_ss_core_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/psa_manifest/tfm_ss_core_test_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/auto_generated/intermedia_tfm_ss_core_test_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/psa_manifest/tfm_secure_client_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/auto_generated/intermedia_tfm_secure_client_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/psa_manifest/tfm_ipc_service_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/auto_generated/intermedia_tfm_ipc_service_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/psa_manifest/tfm_ipc_client_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/auto_generated/intermedia_tfm_ipc_client_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/psa_manifest/tfm_irq_test_service_1.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/auto_generated/intermedia_tfm_irq_test_service_1.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/psa_manifest/tfm_ps_test_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/auto_generated/intermedia_tfm_ps_test_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/psa_manifest/tfm_secure_client_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/auto_generated/intermedia_tfm_secure_client_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/psa_manifest/tfm_psa_proxy.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/auto_generated/intermedia_tfm_psa_proxy.c Start to generate file from the generated list: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_spm_db_func.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_spm_db_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/tfm_service_list.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_veneers.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/tfm_veneers.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_secure_irq_handlers.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_secure_irq_handlers_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/sid.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/pid.h 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.275", 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_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_GENERATOR_MODULE_DISABLED is set to FALSE -- CRYPTO_ASYMMETRIC_MODULE_DISABLED is set to FALSE -- CRYPTO_ENGINE_BUF_SIZE is set to 0x2080 -- CRYPTO_CONC_OPER_NUM is set to 8 -- ---------- Display crypto configuration - stop --------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- 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 ------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- Configuring done -- Generating done -- Build files have been written to: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ make install Scanning dependencies of target tfm_generated_files [ 1%] Built target tfm_generated_files Scanning dependencies of target platform_ns [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 4%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 4%] Building C object platform/CMakeFiles/platform_ns.dir/ext/common/uart_stdout.o [ 4%] Linking C static library libplatform_ns.a [ 4%] Built target platform_ns Scanning dependencies of target tfm_ns_log [ 4%] Building C object ns_log/CMakeFiles/tfm_ns_log.dir/tfm_log_raw.o [ 4%] Linking C static library libtfm_ns_log.a [ 4%] Built target tfm_ns_log Scanning dependencies of target tfm_test_suite_platform_ns [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/platform_tests_common.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/non_secure/platform_ns_interface_testsuite.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_helpers.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 5%] Linking C static library libtfm_test_suite_platform_ns.a [ 5%] Built target tfm_test_suite_platform_ns Scanning dependencies of target tfm_t_cose [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_sign.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_verify.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_util.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_parameters.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/crypto_adapters/t_cose_psa_crypto.o [ 6%] Linking C static library libtfm_t_cose.a [ 6%] Built target tfm_t_cose Scanning dependencies of target tfm_qcbor [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/ieee754.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_encode.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_decode.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/UsefulBuf.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/util/qcbor_util.o [ 7%] Linking C static library libtfm_qcbor.a [ 7%] Built target tfm_qcbor Scanning dependencies of target tfm_qcbor_test [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/float_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/half_to_double_from_rfc7049.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_decode_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_encode_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/run_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/UsefulBuf_Tests.o [ 9%] Linking C static library libtfm_qcbor_test.a [ 9%] Built target tfm_qcbor_test Scanning dependencies of target tfm_t_cose_test [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/run_tests.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_psa_test_key.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_test_messages.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_sign_verify_test.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_test.o [ 11%] Linking C static library libtfm_t_cose_test.a [ 11%] Built target tfm_t_cose_test Scanning dependencies of target tfm_api_ns [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_platform_func_api.o [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_audit_func_api.o [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ps_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_its_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_crypto_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_initial_attestation_func_api.o [ 12%] 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 [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ns_interface.o [ 13%] Linking C static library libtfm_api_ns.a [ 13%] Built target tfm_api_ns Scanning dependencies of target tfm_s_scatter [ 13%] Building C object platform/target/CMakeFiles/tfm_s_scatter.dir/__/__/__/common/gcc/tfm_common_s.o [ 13%] Built target tfm_s_scatter Scanning dependencies of target tfm_psa_rot_partition_ps_test [ 14%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/tfm_ps_test_service.o [ 14%] 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 [ 14%] Linking C static library libtfm_psa_rot_partition_ps_test.a [ 14%] Built target tfm_psa_rot_partition_ps_test Scanning dependencies of target tfm_app_rot_partition_core_test_2 [ 14%] 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 [ 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/interface/src/log/tfm_log_raw.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 [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/tfm_ss_core_test.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/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/__/__/framework/test_framework.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_helpers.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_integ_test_helper.o [ 16%] Linking C static library libtfm_psa_rot_partition_core_test.a [ 16%] Built target tfm_psa_rot_partition_core_test Scanning dependencies of target platform_s [ 16%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/system_stm32l5xx.o [ 16%] 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 [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/spm_hal.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_hal_isolation.o [ 17%] 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 [ 18%] 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 [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc_ex.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/Native_Driver/low_level_rng.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_isolation_mpu_v8m.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_platform_system.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/tfm_hal_ps.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_its.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_platform.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/uart_stdout.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_spm_logdev_peripheral.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_memory_symbols.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/nv_counters.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/crypto_keys.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_rotpk.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/log/tfm_log_raw.o [ 23%] Linking C static library libplatform_s.a [ 23%] Built target platform_s Scanning dependencies of target tfm_spm [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_boot_data.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_utils.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/utilities.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/spm_log.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_mem_check.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/main.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/arch.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/spm_func.o /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_seal_psp_stacks': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:91:5: warning: array subscript 1 is outside array bounds of 'uint32_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds] 91 | *(arm_lib_stck_seal_base + 1) = TFM_STACK_SEAL_VALUE; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:23: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:18: note: while referencing 'Image$$ARM_LIB_STACK_SEAL$$ZI$$Base' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:12:25: note: in definition of macro 'REGION' 12 | #define REGION(a, b, c) a##b##c | ^ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:15:47: note: in expansion of macro 'REGION_NAME' 15 | #define REGION_DECLARE_T(a, b, c, t) extern t REGION_NAME(a, b, c) | ^~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:1: note: in expansion of macro 'REGION_DECLARE_T' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_sfn_request_handler': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:450:31: warning: 'iovecs.orig_outvec' may be used uninitialized in this function [-Wmaybe-uninitialized] 450 | runtime_data->orig_outvec = iovec_ptr->orig_outvec; | ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.orig_outvec' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:446:5: warning: 'iovecs.out_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 446 | for (i = 0U; i < runtime_data->iovec_args.out_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.out_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:441:5: warning: 'iovecs.in_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 441 | for (i = 0U; i < runtime_data->iovec_args.in_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.in_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_core_svcalls_func.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_nspm_func.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_secure_api.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/log/tfm_log_raw.o [ 25%] Linking C static library libtfm_spm.a [ 25%] Built target tfm_spm 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/__/__/__/interface/src/log/tfm_log_raw.o [ 25%] Linking C static library libtfm_psa_rot_partition_platform.a [ 25%] Built target tfm_psa_rot_partition_platform Scanning dependencies of target tfm_psa_rot_partition_its [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_its_req_mngr.o [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_internal_trusted_storage.o [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/its_utils.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nand.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nor.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_ram.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_dblock.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_mblock.o [ 27%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 27%] Linking C static library libtfm_psa_rot_partition_its.a [ 27%] Built target tfm_psa_rot_partition_its Scanning dependencies of target tfm_app_rot_partition_ps [ 27%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_ps_req_mngr.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_protected_storage.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_system.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_table.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_utils.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/crypto/ps_crypto_interface.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_encrypted_object.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/nv_counters/ps_nv_counters.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 29%] Linking C static library libtfm_app_rot_partition_ps.a [ 29%] Built target tfm_app_rot_partition_ps Scanning dependencies of target tfm_psa_rot_partition_attestation [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest_req_mngr.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_core.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_asymmetric_key.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_token_encode.o [ 30%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 30%] Linking C static library libtfm_psa_rot_partition_attestation.a [ 30%] Built target tfm_psa_rot_partition_attestation Scanning dependencies of target crypto_service_mbedcrypto [ 30%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aes.o [ 30%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aesni.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/arc4.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aria.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1parse.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1write.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/base64.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/bignum.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/blowfish.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/camellia.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ccm.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chacha20.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chachapoly.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher_wrap.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cmac.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ctr_drbg.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/des.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/dhm.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdh.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdsa.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecjpake.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp_curves.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy_poll.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/error.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/gcm.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/havege.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hkdf.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hmac_drbg.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md2.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md4.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md5.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/memory_buffer_alloc.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/nist_kw.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/oid.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/padlock.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pem.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk_wrap.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs12.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs5.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkparse.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkwrite.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform_util.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/poly1305.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_se.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_slot_management.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_storage.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_its_file.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ripemd160.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa_internal.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha1.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha256.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha512.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/threading.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/timing.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version_features.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/xtea.o [ 43%] 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/crypto/tfm_mbedcrypto_alt.o [ 43%] 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 [ 43%] Linking C static library libmbedcrypto.a [ 43%] Built target crypto_service_mbedcrypto Scanning dependencies of target tfm_psa_rot_partition_crypto [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_init.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_alloc.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_cipher.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_hash.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_mac.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_aead.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_asymmetric.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key_derivation.o [ 45%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 45%] Linking C static library libtfm_psa_rot_partition_crypto.a [ 45%] Built target tfm_psa_rot_partition_crypto Scanning dependencies of target tfm_psa_rot_partition_audit [ 45%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/audit_core.o [ 45%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 45%] Linking C static library libtfm_psa_rot_partition_audit.a [ 45%] Built target tfm_psa_rot_partition_audit Scanning dependencies of target tfm_sprt [ 45%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcmp.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcpy.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memmove.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memset.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/service_api.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/tfm_sp_log_raw.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/common/tfm_hal_sp_logdev_periph.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/audit_logging/tfm_audit_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/crypto/tfm_crypto_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/initial_attestation/tfm_attest_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/protected_storage/tfm_ps_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/internal_trusted_storage/tfm_its_secure_api.o [ 48%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/platform/tfm_platform_secure_api.o [ 48%] 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 [ 48%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C static library libtfm_sprt.a [ 48%] Built target tfm_sprt Scanning dependencies of target tfm_s_log [ 48%] 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 [ 48%] Linking C static library libtfm_s_log.a [ 48%] Built target tfm_s_log Scanning dependencies of target tfm_s [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/spm/cmsis_func/tfm_veneers.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_s.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C executable ../bin/tfm_s.axf Memory region Used Size Region Size %age Used FLASH: 144552 B 219328 B 65.91% RAM: 50632 B 127 KB 38.93% VENEERS: 800 B 832 B 96.15% [ 48%] Built target tfm_s [ 48%] Generating s_veneers.o Scanning dependencies of target tfm_s_veneers [ 48%] Generating s_veneers.o [ 49%] Linking C static library libtfm_s_veneers.a [ 49%] Built target tfm_s_veneers Scanning dependencies of target tfm_test_suite_attestation_ns [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_public_key.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_test.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_common.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_asymmetric.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/non_secure/attest_asymmetric_ns_interface_testsuite.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_helpers.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 50%] Linking C static library libtfm_test_suite_attestation_ns.a [ 50%] Built target tfm_test_suite_attestation_ns Scanning dependencies of target tfm_test_suite_audit_ns [ 50%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/non_secure/audit_ns_interface_testsuite.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_helpers.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 51%] Linking C static library libtfm_test_suite_audit_ns.a [ 51%] Built target tfm_test_suite_audit_ns Scanning dependencies of target tfm_test_suite_crypto_ns [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/crypto_tests_common.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/non_secure/crypto_ns_interface_testsuite.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_helpers.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 53%] Linking C static library libtfm_test_suite_crypto_ns.a [ 53%] Built target tfm_test_suite_crypto_ns Scanning dependencies of target tfm_test_suite_its_ns [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/its_tests_common.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/non_secure/psa_its_ns_interface_testsuite.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_helpers.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 54%] 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 [ 54%] 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 [ 54%] 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 [ 54%] Linking C static library libtfm_test_suite_its_ns.a [ 54%] Built target tfm_test_suite_its_ns Scanning dependencies of target tfm_test_suite_qcbor_ns [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/non_secure/qcbor_ns_testsuite.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_helpers.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 55%] Linking C static library libtfm_test_suite_qcbor_ns.a [ 55%] Built target tfm_test_suite_qcbor_ns Scanning dependencies of target tfm_test_suite_ps_ns [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/ns_test_helpers.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/psa_ps_ns_interface_testsuite.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_helpers.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 57%] Linking C static library libtfm_test_suite_ps_ns.a [ 57%] Built target tfm_test_suite_ps_ns Scanning dependencies of target tfm_test_suite_t_cose_ns [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/non_secure/t_cose_ns_testsuite.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_helpers.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 58%] Linking C static library libtfm_test_suite_t_cose_ns.a [ 58%] Built target tfm_test_suite_t_cose_ns Scanning dependencies of target tfm_test_suite_core_ns [ 58%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_interactive_testsuite.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_positive_testsuite.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_test_api.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_helpers.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 60%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/non_secure_suites.o [ 60%] 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 [ 60%] 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 [ 60%] 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 [ 60%] Linking C static library libtfm_test_suite_core_ns.a [ 60%] Built target tfm_test_suite_core_ns Scanning dependencies of target tfm_ns_integration_test [ 60%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/tfm_integ_test.o [ 60%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 62%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/os_wrapper_cmsis_rtos_v2.o [ 62%] Linking C static library libtfm_ns_integration_test.a [ 62%] Built target tfm_ns_integration_test Scanning dependencies of target tfm_ns_scatter [ 62%] Building C object platform/target/CMakeFiles/tfm_ns_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_ns.o [ 62%] Built target tfm_ns_scatter Scanning dependencies of target tfm_ns [ 62%] Building C object app/CMakeFiles/tfm_ns.dir/main_ns.o [ 62%] 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 [ 62%] 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 [ 62%] 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 [ 62%] Building C object app/CMakeFiles/tfm_ns.dir/os_wrapper_cmsis_rtos_v2.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/non_secure_suites.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_helpers.o [ 63%] 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 [ 63%] Linking C executable ../bin/tfm_ns.axf Memory region Used Size Region Size %age Used FLASH: 126528 B 159 KB 77.71% RAM: 30208 B 128 KB 23.05% [ 63%] Built target tfm_ns Scanning dependencies of target tfm_ns_hex [ 63%] Generating ../bin/tfm_ns.hex [ 63%] Built target tfm_ns_hex Scanning dependencies of target tfm_ns_bin [ 64%] Generating ../bin/tfm_ns.bin [ 64%] Built target tfm_ns_bin Scanning dependencies of target tfm_ns_elf [ 64%] Generating ../bin/tfm_ns.elf [ 64%] Built target tfm_ns_elf Scanning dependencies of target tfm_ns_binaries [ 64%] Built target tfm_ns_binaries Scanning dependencies of target tfm_s_hex [ 64%] Generating ../bin/tfm_s.hex [ 64%] Built target tfm_s_hex Scanning dependencies of target tfm_s_bin [ 65%] Generating ../bin/tfm_s.bin [ 65%] Built target tfm_s_bin Scanning dependencies of target tfm_s_elf [ 65%] Generating ../bin/tfm_s.elf [ 65%] Built target tfm_s_elf Scanning dependencies of target tfm_s_binaries [ 65%] Built target tfm_s_binaries Scanning dependencies of target crypto_service_mbedx509 [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/certs.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/pkcs11.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_create.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crl.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crt.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_csr.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_crt.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_csr.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 68%] Linking C static library libmbedx509.a [ 68%] Built target crypto_service_mbedx509 Scanning dependencies of target crypto_service_mbedtls [ 68%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/debug.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/net_sockets.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cache.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ciphersuites.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cli.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cookie.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_msg.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_srv.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ticket.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_tls.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 70%] Linking C static library libmbedtls.a [ 70%] Built target crypto_service_mbedtls Scanning dependencies of target bl2_scatter [ 70%] Building C object platform/target/CMakeFiles/bl2_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_bl2.o [ 70%] Built target bl2_scatter Scanning dependencies of target platform_bl2 [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/boot_hal.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/tfm_low_level_security.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/low_level_device.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/boot_hal.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/uart_stdout.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/nv_counters.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_rotpk.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 74%] Linking C static library libplatform_bl2.a [ 74%] Built target platform_bl2 Scanning dependencies of target bl2_mbedcrypto [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aes.o [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aesni.o [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/arc4.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aria.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1parse.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1write.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/base64.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/bignum.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/blowfish.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/camellia.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ccm.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chacha20.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chachapoly.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher_wrap.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cmac.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ctr_drbg.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/des.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/dhm.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdh.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdsa.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecjpake.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp_curves.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy_poll.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/error.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/gcm.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/havege.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hkdf.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hmac_drbg.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md2.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md4.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md5.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/memory_buffer_alloc.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/nist_kw.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/oid.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/padlock.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pem.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk_wrap.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs12.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs5.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkparse.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkwrite.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform_util.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/poly1305.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_se.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_slot_management.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_storage.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_its_file.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ripemd160.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa_internal.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha1.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha256.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha512.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/threading.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/timing.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version_features.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/xtea.o [ 87%] Linking C static library libmbedcrypto.a [ 87%] Built target bl2_mbedcrypto Scanning dependencies of target bootutil [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/boot_record.o [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/bootutil_misc.o [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/caps.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/encrypted.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening_delay_rng_mbedtls.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec256.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ed25519.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_rsa.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_validate.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/loader.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_misc.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_move.o [ 90%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_scratch.o [ 90%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/tlv.o [ 90%] Linking C static library libbootutil.a [ 90%] Built target bootutil Scanning dependencies of target bl2 [ 90%] Building C object bl2/CMakeFiles/bl2.dir/src/security_cnt.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/src/flash_map.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/bl2_main.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/keys.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_extended.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_legacy.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_bl2.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/bl2/low_level_ospi_device.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_ospi_flash.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_ospi.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/Components/mx25lm51245g/mx25lm51245g.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/stm32l562e_dk/src/stm32l562e_discovery_ospi.o [ 92%] Linking C executable ../bin/bl2.axf Memory region Used Size Region Size %age Used FLASH: 46360 B 66 KB 68.60% FLASH_NOHDP: 244 B 6 KB 3.97% RAM: 27016 B 63 KB 41.88% [ 92%] Built target bl2 Scanning dependencies of target bl2_elf [ 93%] Generating ../bin/bl2.elf [ 93%] Built target bl2_elf Scanning dependencies of target bl2_hex [ 93%] Generating ../bin/bl2.hex [ 93%] Built target bl2_hex Scanning dependencies of target bl2_bin [ 93%] Generating ../bin/bl2.bin [ 93%] Built target bl2_bin Scanning dependencies of target bl2_binaries [ 93%] Built target bl2_binaries Scanning dependencies of target signing_layout_s [ 93%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_s.dir/signing_layout_s.o [ 93%] Built target signing_layout_s Scanning dependencies of target signing_layout_ns [ 94%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_ns.dir/signing_layout_ns.o [ 94%] Built target signing_layout_ns Scanning dependencies of target tfm_s_signed_bin [ 94%] Generating tfm_s_signed.bin [ 94%] Built target tfm_s_signed_bin Scanning dependencies of target tfm_ns_signed_bin [ 95%] Generating tfm_ns_signed.bin [ 95%] Built target tfm_ns_signed_bin Scanning dependencies of target tfm_s_ns_signed_bin [ 95%] Generating tfm_s_ns_signed.bin [ 95%] Built target tfm_s_ns_signed_bin Scanning dependencies of target signed_images [ 95%] Built target signed_images Scanning dependencies of target bl2_mbedx509 [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/certs.o [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/pkcs11.o [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509.o [ 95%] 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 [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_crt.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_csr.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_crt.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_csr.o [ 97%] Linking C static library libmbedx509.a [ 97%] Built target bl2_mbedx509 Scanning dependencies of target bl2_mbedtls [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/debug.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/net_sockets.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cache.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ciphersuites.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cli.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cookie.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_msg.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_srv.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ticket.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_tls.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_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/stm_tool.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/regression.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/preprocess.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/TFM_UPDATE.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/postbuild.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/flash_layout.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/region_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/image_macros_to_preprocess_bl2.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/lib/s_veneers.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/client.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/error.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/msg_queue.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/mutex.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/semaphore.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/thread.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/tick.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_manifest/sid.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_interface.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_svc.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/ext/tz_context.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm/veneers/tfm_veneers.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/protected_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/internal_trusted_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/storage_common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_extra.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_compat.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_client_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_sizes.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_types.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_values.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_crypto_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/initial_attestation.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_platform_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ns_interface.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ps_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_its_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_crypto_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_initial_attestation_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_audit_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_platform_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/assemble.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__ -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__/macro_parser.cpython-36.pyc -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/requirements.txt -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper/wrapper.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_s.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_ns.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/keys/root-RSA-3072_1.pem Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 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. =====================================================================-- 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. =====================================================================-- 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 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. =====================================================================

4 years, 2 months

1
0
0 0

Armclang linker alignement question

by Michel JAOUEN

Hello, This question is relative to linker script with Compiler armclang 'V6.14' (For the other toolchain IAR , GNUARM ,it works ) I need to place code aligned to flash PAGE SIZE (0x2000 or 8192) to be able to set hardware protection. As follow , here is the description of the issue. With a Linker file having the following value for Code placement LR_CODE 0x0c024400 0x20000 { ER_TFM_CODE 0x0c024400 { *.o (RESET +First) * (+RO) } TFM_UNPRIV_CODE +0 ALIGN 0x2000 { stm32u5xx_hal*.o (+RO) tick.o (+RO) *(SFN) *armlib* } } We get the following error : Build started: Project: Project_s *** Using Compiler 'V6.14', folder: 'C:\Keil_v5\ARM\ARMCLANG\Bin' Build Project 'Project_s' - Target xxxxxxxxxxx _TFM_Appli_S' linking... xxxxxxxxxxx_S\Exe\Project.axf: Error: L6244E: Load region LR_CODE address (0x0c024400) not aligned on a 8192 byte boundary. Not enough information to list image symbols. Finished: 1 information, 0 warning and 1 error messages. " xxxxxxxxxxx _S\Exe\Project.axf" - 1 Error(s), 0 Warning(s). Target not created. Build Time Elapsed: 00:00:03 If we change the linker file as follow : LR_CODE 0x0c024400 0x20000 { ER_TFM_CODE 0x0c024400 { *.o (RESET +First) * (+RO) } TFM_UNPRIV_CODE +0 ALIGN 0x400 { stm32u5xx_hal*.o (+RO) tick.o (+RO) *(SFN) *armlib* } } No Error is reported. Is this an known issue with ARMCLANG ? Best Regards .

4 years, 2 months

1
0
0 0

Re: [TF-M] Technical Forum call - March 18

by Ken Liu

Hi, I would introduce the upcoming SPM changes in general. Assume it is a big topic so 40 mins are needed. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Thursday, March 11, 2021 12:56 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - March 18 Hello, The next Technical Forum is planned on Thursday, March 18 at 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

1
0
0 0

Re: [TF-M] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board

by Jamie Fox

Hi, Which version of TF-M does the problem occur with? If it’s not the latest master, please can you retry with that? Are you able to find which commit introduces the issue? Recently this patch was merged to fix an issue on the STM platform https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8686. It would be a good place to start to check if that commit has an effect. Kind regards, Jamie From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: 15 March 2021 12:55 To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board Hi Ken, Thank you for your reply. I have enabled the TEST_S and tested again, it turned out to be the same results. The test log is as 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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_PS_TEST_2XXX)... > Executing 'TFM_PS_TEST_2001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_PS_TEST_2XXX)... > Executing 'TFM_PS_TEST_2001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_PS_TEST_2XXX)... > Executing 'TFM_PS_TEST_2001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_PS_TEST_2XXX)... > Executing 'TFM_PS_TEST_2001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... The building procedure log is as following: (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ cmake .. -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_NS=ON -DTEST_S=ON -- 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 PSA manifests: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/psa_manifest/tfm_protected_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/auto_generated/intermedia_tfm_protected_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/psa_manifest/tfm_internal_trusted_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/intermedia_tfm_internal_trusted_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/psa_manifest/tfm_audit_logging.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/auto_generated/intermedia_tfm_audit_logging.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/psa_manifest/tfm_crypto.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/auto_generated/intermedia_tfm_crypto.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/psa_manifest/tfm_platform.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/auto_generated/intermedia_tfm_platform.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/psa_manifest/tfm_initial_attestation.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/auto_generated/intermedia_tfm_initial_attestation.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/psa_manifest/tfm_ss_core_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/auto_generated/intermedia_tfm_ss_core_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/psa_manifest/tfm_ss_core_test_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/auto_generated/intermedia_tfm_ss_core_test_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/psa_manifest/tfm_secure_client_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/auto_generated/intermedia_tfm_secure_client_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/psa_manifest/tfm_ipc_service_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/auto_generated/intermedia_tfm_ipc_service_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/psa_manifest/tfm_ipc_client_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/auto_generated/intermedia_tfm_ipc_client_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/psa_manifest/tfm_irq_test_service_1.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/auto_generated/intermedia_tfm_irq_test_service_1.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/psa_manifest/tfm_ps_test_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/auto_generated/intermedia_tfm_ps_test_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/psa_manifest/tfm_secure_client_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/auto_generated/intermedia_tfm_secure_client_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/psa_manifest/tfm_psa_proxy.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/auto_generated/intermedia_tfm_psa_proxy.c Start to generate file from the generated list: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_spm_db_func.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_spm_db_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/tfm_service_list.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_veneers.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/tfm_veneers.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_secure_irq_handlers.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_secure_irq_handlers_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/sid.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/pid.h 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.275", 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_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_GENERATOR_MODULE_DISABLED is set to FALSE -- CRYPTO_ASYMMETRIC_MODULE_DISABLED is set to FALSE -- CRYPTO_ENGINE_BUF_SIZE is set to 0x2080 -- CRYPTO_CONC_OPER_NUM is set to 8 -- ---------- Display crypto configuration - stop --------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- 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 ------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- Configuring done -- Generating done -- Build files have been written to: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ make install Scanning dependencies of target tfm_generated_files [ 0%] Built target tfm_generated_files Scanning dependencies of target platform_ns [ 0%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 0%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/common/uart_stdout.o [ 2%] Linking C static library libplatform_ns.a [ 2%] Built target platform_ns Scanning dependencies of target tfm_ns_log [ 2%] Building C object ns_log/CMakeFiles/tfm_ns_log.dir/tfm_log_raw.o [ 3%] Linking C static library libtfm_ns_log.a [ 3%] Built target tfm_ns_log Scanning dependencies of target tfm_test_suite_platform_ns [ 3%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/platform_tests_common.o [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/non_secure/platform_ns_interface_testsuite.o [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework.o [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_helpers.o [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 4%] Linking C static library libtfm_test_suite_platform_ns.a [ 4%] Built target tfm_test_suite_platform_ns Scanning dependencies of target tfm_t_cose [ 4%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_sign.o [ 4%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_verify.o [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_util.o [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_parameters.o [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/crypto_adapters/t_cose_psa_crypto.o [ 5%] Linking C static library libtfm_t_cose.a [ 5%] Built target tfm_t_cose Scanning dependencies of target tfm_qcbor [ 5%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/ieee754.o [ 5%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_encode.o [ 5%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_decode.o [ 5%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/UsefulBuf.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/util/qcbor_util.o [ 6%] Linking C static library libtfm_qcbor.a [ 6%] Built target tfm_qcbor Scanning dependencies of target tfm_qcbor_test [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/float_tests.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/half_to_double_from_rfc7049.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_decode_tests.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_encode_tests.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/run_tests.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/UsefulBuf_Tests.o [ 7%] Linking C static library libtfm_qcbor_test.a [ 7%] Built target tfm_qcbor_test Scanning dependencies of target tfm_t_cose_test [ 7%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/run_tests.o [ 7%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_psa_test_key.o [ 8%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_test_messages.o [ 8%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_sign_verify_test.o [ 8%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_test.o [ 8%] Linking C static library libtfm_t_cose_test.a [ 8%] Built target tfm_t_cose_test Scanning dependencies of target tfm_api_ns [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_platform_func_api.o [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_audit_func_api.o [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ps_func_api.o [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_its_func_api.o [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_crypto_func_api.o [ 10%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_initial_attestation_func_api.o [ 10%] 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 [ 10%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ns_interface.o [ 10%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/test_services/tfm_secure_client_service/tfm_secure_client_service_api.o [ 10%] Linking C static library libtfm_api_ns.a [ 10%] Built target tfm_api_ns Scanning dependencies of target tfm_s_scatter [ 10%] Building C object platform/target/CMakeFiles/tfm_s_scatter.dir/__/__/__/common/gcc/tfm_common_s.o [ 10%] Built target tfm_s_scatter Scanning dependencies of target tfm_app_rot_partition_secure_client_2 [ 11%] Building C object test/test_services/tfm_secure_client_2/CMakeFiles/tfm_app_rot_partition_secure_client_2.dir/tfm_secure_client_2.o [ 11%] Building C object test/test_services/tfm_secure_client_2/CMakeFiles/tfm_app_rot_partition_secure_client_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 11%] Linking C static library libtfm_app_rot_partition_secure_client_2.a [ 11%] Built target tfm_app_rot_partition_secure_client_2 Scanning dependencies of target tfm_psa_rot_partition_secure_client_service [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/tfm_secure_client_service.o [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/__/__/framework/test_framework.o [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/__/__/framework/test_framework_helpers.o [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/__/__/framework/test_framework_integ_test_helper.o [ 12%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/__/__/framework/secure_suites.o [ 12%] Linking C static library libtfm_psa_rot_partition_secure_client_service.a [ 12%] Built target tfm_psa_rot_partition_secure_client_service Scanning dependencies of target tfm_psa_rot_partition_ps_test [ 12%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/tfm_ps_test_service.o [ 12%] 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 [ 13%] Linking C static library libtfm_psa_rot_partition_ps_test.a [ 13%] Built target tfm_psa_rot_partition_ps_test Scanning dependencies of target tfm_app_rot_partition_core_test_2 [ 13%] 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 [ 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/interface/src/log/tfm_log_raw.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/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_helpers.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_integ_test_helper.o [ 15%] Linking C static library libtfm_psa_rot_partition_core_test.a [ 15%] Built target tfm_psa_rot_partition_core_test Scanning dependencies of target tfm_test_suite_ps_s [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/suites/ps/secure/psa_ps_s_interface_testsuite.o [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/suites/ps/secure/psa_ps_s_reliability_testsuite.o [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/suites/ps/secure/ps_rollback_protection_testsuite.o [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/framework/test_framework.o [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/framework/test_framework_helpers.o [ 16%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/framework/test_framework_integ_test_helper.o [ 16%] Linking C static library libtfm_test_suite_ps_s.a [ 16%] Built target tfm_test_suite_ps_s Scanning dependencies of target tfm_test_suite_crypto_s [ 16%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/suites/crypto/crypto_tests_common.o [ 16%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/suites/crypto/secure/crypto_sec_interface_testsuite.o [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/framework/test_framework.o [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/framework/test_framework_helpers.o [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/framework/test_framework_integ_test_helper.o [ 17%] Linking C static library libtfm_test_suite_crypto_s.a [ 17%] Built target tfm_test_suite_crypto_s Scanning dependencies of target tfm_test_suite_audit_s [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_audit_s.dir/__/suites/audit/secure/audit_s_interface_testsuite.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_audit_s.dir/__/framework/test_framework.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_audit_s.dir/__/framework/test_framework_helpers.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_audit_s.dir/__/framework/test_framework_integ_test_helper.o [ 18%] Linking C static library libtfm_test_suite_audit_s.a [ 18%] Built target tfm_test_suite_audit_s Scanning dependencies of target tfm_test_suite_attestation_s [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/attest_public_key.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/attest_token_test.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/attest_token_decode_common.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/attest_token_decode_asymmetric.o [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/secure/attest_asymmetric_s_interface_testsuite.o [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/framework/test_framework.o [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/framework/test_framework_helpers.o [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/framework/test_framework_integ_test_helper.o [ 19%] Linking C static library libtfm_test_suite_attestation_s.a [ 19%] Built target tfm_test_suite_attestation_s Scanning dependencies of target tfm_test_suite_platform_s [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/suites/platform/platform_tests_common.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/suites/platform/secure/platform_s_interface_testsuite.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/framework/test_framework.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/framework/test_framework_helpers.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/framework/test_framework_integ_test_helper.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 20%] Linking C static library libtfm_test_suite_platform_s.a [ 20%] Built target tfm_test_suite_platform_s Scanning dependencies of target tfm_test_suite_its_s [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/suites/its/its_tests_common.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/suites/its/secure/psa_its_s_interface_testsuite.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/suites/its/secure/psa_its_s_reliability_testsuite.o [ 21%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 21%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/framework/test_framework.o [ 21%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/framework/test_framework_helpers.o [ 21%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/framework/test_framework_integ_test_helper.o [ 21%] Linking C static library libtfm_test_suite_its_s.a [ 21%] Built target tfm_test_suite_its_s Scanning dependencies of target platform_s [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/system_stm32l5xx.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/spm_hal.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_hal_isolation.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/target_cfg.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/low_level_device.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc_ex.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng_ex.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_isolation_mpu_v8m.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_platform_system.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/attest_hal.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_ps.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_its.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_platform.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/uart_stdout.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_spm_logdev_peripheral.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_memory_symbols.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/nv_counters.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/crypto_keys.o [ 28%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_rotpk.o [ 28%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 28%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/log/tfm_log_raw.o [ 28%] Linking C static library libplatform_s.a [ 28%] Built target platform_s Scanning dependencies of target tfm_spm [ 28%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_boot_data.o [ 28%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_utils.o [ 28%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/utilities.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/spm_log.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_mem_check.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/main.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/arch.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/spm_func.o /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_seal_psp_stacks': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:91:5: warning: array subscript 1 is outside array bounds of 'uint32_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds] 91 | *(arm_lib_stck_seal_base + 1) = TFM_STACK_SEAL_VALUE; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:23: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:18: note: while referencing 'Image$$ARM_LIB_STACK_SEAL$$ZI$$Base' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:12:25: note: in definition of macro 'REGION' 12 | #define REGION(a, b, c) a##b##c | ^ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:15:47: note: in expansion of macro 'REGION_NAME' 15 | #define REGION_DECLARE_T(a, b, c, t) extern t REGION_NAME(a, b, c) | ^~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:1: note: in expansion of macro 'REGION_DECLARE_T' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_sfn_request_handler': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:450:31: warning: 'iovecs.orig_outvec' may be used uninitialized in this function [-Wmaybe-uninitialized] 450 | runtime_data->orig_outvec = iovec_ptr->orig_outvec; | ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.orig_outvec' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:446:5: warning: 'iovecs.out_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 446 | for (i = 0U; i < runtime_data->iovec_args.out_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.out_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:441:5: warning: 'iovecs.in_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 441 | for (i = 0U; i < runtime_data->iovec_args.in_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.in_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_core_svcalls_func.o [ 30%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_nspm_func.o [ 30%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_secure_api.o [ 30%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/log/tfm_log_raw.o [ 30%] Linking C static library libtfm_spm.a [ 30%] Built target tfm_spm Scanning dependencies of target tfm_psa_rot_partition_platform [ 30%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/platform_sp.o [ 30%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 30%] Linking C static library libtfm_psa_rot_partition_platform.a [ 30%] Built target tfm_psa_rot_partition_platform Scanning dependencies of target tfm_psa_rot_partition_its [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_its_req_mngr.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_internal_trusted_storage.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/its_utils.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nand.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nor.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_ram.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_dblock.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_mblock.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 32%] Linking C static library libtfm_psa_rot_partition_its.a [ 32%] Built target tfm_psa_rot_partition_its Scanning dependencies of target tfm_app_rot_partition_ps [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_ps_req_mngr.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_protected_storage.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_system.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_table.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_utils.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/crypto/ps_crypto_interface.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_encrypted_object.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/ps/secure/nv_counters/test_ps_nv_counters.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 33%] Linking C static library libtfm_app_rot_partition_ps.a [ 33%] Built target tfm_app_rot_partition_ps Scanning dependencies of target tfm_psa_rot_partition_attestation [ 33%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest.o [ 33%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest_req_mngr.o [ 33%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_core.o [ 34%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_asymmetric_key.o [ 34%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_token_encode.o [ 34%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 34%] Linking C static library libtfm_psa_rot_partition_attestation.a [ 34%] Built target tfm_psa_rot_partition_attestation Scanning dependencies of target crypto_service_mbedcrypto [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aes.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aesni.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/arc4.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aria.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1parse.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1write.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/base64.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/bignum.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/blowfish.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/camellia.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ccm.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chacha20.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chachapoly.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher_wrap.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cmac.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ctr_drbg.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/des.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/dhm.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdh.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdsa.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecjpake.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp_curves.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy_poll.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/error.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/gcm.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/havege.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hkdf.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hmac_drbg.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md2.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md4.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md5.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/memory_buffer_alloc.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/nist_kw.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/oid.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/padlock.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pem.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk_wrap.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs12.o [ 41%] 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 [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform_util.o [ 42%] 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_se.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_slot_management.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_storage.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_its_file.o [ 43%] 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_internal.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha1.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha256.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha512.o [ 44%] 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/xtea.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/secure_fw/partitions/crypto/tfm_mbedcrypto_alt.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%] Linking C static library libmbedcrypto.a [ 46%] Built target crypto_service_mbedcrypto Scanning dependencies of target tfm_psa_rot_partition_crypto [ 46%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_init.o [ 46%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_alloc.o [ 46%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_cipher.o [ 46%] 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 [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key_derivation.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C static library libtfm_psa_rot_partition_crypto.a [ 48%] Built target tfm_psa_rot_partition_crypto Scanning dependencies of target tfm_psa_rot_partition_audit [ 48%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/audit_core.o [ 48%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 49%] Linking C static library libtfm_psa_rot_partition_audit.a [ 49%] Built target tfm_psa_rot_partition_audit Scanning dependencies of target tfm_sprt [ 49%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcmp.o [ 49%] 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/__/__/audit_logging/tfm_audit_secure_api.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 [ 52%] 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 [ 52%] 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_secure_client_2/tfm_secure_client_2_api.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/log/tfm_log_raw.o [ 52%] Linking C static library libtfm_sprt.a [ 52%] Built target tfm_sprt Scanning dependencies of target tfm_s_log [ 53%] 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 [ 53%] Linking C static library libtfm_s_log.a [ 53%] Built target tfm_s_log Scanning dependencies of target tfm_s [ 53%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/spm/cmsis_func/tfm_veneers.o [ 53%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 54%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_s.o [ 54%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/log/tfm_log_raw.o [ 54%] Linking C executable ../bin/tfm_s.axf Memory region Used Size Region Size %age Used FLASH: 205120 B 219328 B 93.52% RAM: 56760 B 127 KB 43.65% VENEERS: 800 B 832 B 96.15% [ 54%] Built target tfm_s [ 55%] Generating s_veneers.o Scanning dependencies of target tfm_s_veneers [ 55%] Generating s_veneers.o [ 55%] Linking C static library libtfm_s_veneers.a [ 55%] Built target tfm_s_veneers Scanning dependencies of target tfm_test_suite_attestation_ns [ 55%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_public_key.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_test.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_common.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_asymmetric.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/non_secure/attest_asymmetric_ns_interface_testsuite.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_helpers.o [ 57%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 57%] Linking C static library libtfm_test_suite_attestation_ns.a [ 57%] Built target tfm_test_suite_attestation_ns Scanning dependencies of target tfm_test_suite_audit_ns [ 57%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/non_secure/audit_ns_interface_testsuite.o [ 58%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework.o [ 58%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_helpers.o [ 58%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 58%] Linking C static library libtfm_test_suite_audit_ns.a [ 58%] Built target tfm_test_suite_audit_ns Scanning dependencies of target tfm_test_suite_crypto_ns [ 58%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/crypto_tests_common.o [ 58%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/non_secure/crypto_ns_interface_testsuite.o [ 59%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework.o [ 59%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_helpers.o [ 59%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 59%] Linking C static library libtfm_test_suite_crypto_ns.a [ 59%] Built target tfm_test_suite_crypto_ns Scanning dependencies of target tfm_test_suite_its_ns [ 59%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/its_tests_common.o [ 60%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/non_secure/psa_its_ns_interface_testsuite.o [ 60%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework.o [ 60%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_helpers.o [ 60%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 60%] 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 [ 60%] 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 [ 61%] 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 [ 61%] Linking C static library libtfm_test_suite_its_ns.a [ 61%] Built target tfm_test_suite_its_ns Scanning dependencies of target tfm_test_suite_qcbor_ns [ 61%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/non_secure/qcbor_ns_testsuite.o [ 61%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework.o [ 61%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_helpers.o [ 61%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 62%] Linking C static library libtfm_test_suite_qcbor_ns.a [ 62%] Built target tfm_test_suite_qcbor_ns Scanning dependencies of target tfm_test_suite_ps_ns [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/ns_test_helpers.o [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/psa_ps_ns_interface_testsuite.o [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework.o [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_helpers.o [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 64%] Linking C static library libtfm_test_suite_ps_ns.a [ 64%] Built target tfm_test_suite_ps_ns Scanning dependencies of target tfm_test_suite_t_cose_ns [ 64%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/non_secure/t_cose_ns_testsuite.o [ 64%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework.o [ 64%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_helpers.o [ 64%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 65%] Linking C static library libtfm_test_suite_t_cose_ns.a [ 65%] Built target tfm_test_suite_t_cose_ns Scanning dependencies of target tfm_test_suite_core_ns [ 65%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_interactive_testsuite.o [ 65%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_positive_testsuite.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_test_api.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_helpers.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/non_secure_suites.o [ 66%] 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 [ 67%] 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 [ 67%] 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 [ 67%] Linking C static library libtfm_test_suite_core_ns.a [ 67%] Built target tfm_test_suite_core_ns Scanning dependencies of target tfm_ns_integration_test [ 67%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/tfm_integ_test.o [ 67%] 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 [ 67%] 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 [ 67%] 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 [ 67%] 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 [ 68%] 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 [ 68%] 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 [ 68%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/os_wrapper_cmsis_rtos_v2.o [ 68%] Linking C static library libtfm_ns_integration_test.a [ 68%] Built target tfm_ns_integration_test Scanning dependencies of target tfm_ns_scatter [ 68%] Building C object platform/target/CMakeFiles/tfm_ns_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_ns.o [ 68%] Built target tfm_ns_scatter Scanning dependencies of target tfm_ns [ 69%] Building C object app/CMakeFiles/tfm_ns.dir/main_ns.o [ 69%] 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 [ 69%] 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 [ 69%] 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 [ 69%] Building C object app/CMakeFiles/tfm_ns.dir/os_wrapper_cmsis_rtos_v2.o [ 69%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/non_secure_suites.o [ 70%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework.o [ 70%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_helpers.o [ 70%] 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 [ 70%] Linking C executable ../bin/tfm_ns.axf Memory region Used Size Region Size %age Used FLASH: 128104 B 159 KB 78.68% RAM: 30208 B 128 KB 23.05% [ 70%] Built target tfm_ns Scanning dependencies of target tfm_ns_hex [ 71%] Generating ../bin/tfm_ns.hex [ 71%] Built target tfm_ns_hex Scanning dependencies of target tfm_ns_bin [ 71%] Generating ../bin/tfm_ns.bin [ 71%] Built target tfm_ns_bin Scanning dependencies of target tfm_ns_elf [ 71%] Generating ../bin/tfm_ns.elf [ 71%] Built target tfm_ns_elf Scanning dependencies of target tfm_ns_binaries [ 71%] Built target tfm_ns_binaries Scanning dependencies of target tfm_s_hex [ 71%] Generating ../bin/tfm_s.hex [ 71%] Built target tfm_s_hex Scanning dependencies of target tfm_s_bin [ 71%] Generating ../bin/tfm_s.bin [ 71%] Built target tfm_s_bin Scanning dependencies of target tfm_s_elf [ 71%] Generating ../bin/tfm_s.elf [ 71%] Built target tfm_s_elf Scanning dependencies of target tfm_s_binaries [ 71%] Built target tfm_s_binaries Scanning dependencies of target crypto_service_mbedx509 [ 71%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/certs.o [ 71%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/pkcs11.o [ 71%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509.o [ 71%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_create.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crl.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crt.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_csr.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_crt.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_csr.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 73%] Linking C static library libmbedx509.a [ 73%] Built target crypto_service_mbedx509 Scanning dependencies of target crypto_service_mbedtls [ 73%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/debug.o [ 73%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/net_sockets.o [ 73%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cache.o [ 73%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ciphersuites.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cli.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cookie.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_msg.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_srv.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ticket.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_tls.o [ 75%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 75%] Linking C static library libmbedtls.a [ 75%] Built target crypto_service_mbedtls Scanning dependencies of target bl2_scatter [ 75%] Building C object platform/target/CMakeFiles/bl2_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_bl2.o [ 75%] Built target bl2_scatter Scanning dependencies of target platform_bl2 [ 75%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 75%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/boot_hal.o [ 75%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 75%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/tfm_low_level_security.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/low_level_device.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/boot_hal.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/uart_stdout.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/nv_counters.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_rotpk.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 79%] Linking C static library libplatform_bl2.a [ 79%] Built target platform_bl2 Scanning dependencies of target bl2_mbedcrypto [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aes.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aesni.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/arc4.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aria.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1parse.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1write.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/base64.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/bignum.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/blowfish.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/camellia.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ccm.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chacha20.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chachapoly.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher_wrap.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cmac.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ctr_drbg.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/des.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/dhm.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdh.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdsa.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecjpake.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp_curves.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy_poll.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/error.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/gcm.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/havege.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hkdf.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hmac_drbg.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md2.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md4.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/nist_kw.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/oid.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/padlock.o [ 86%] 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_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_internal.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 [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version_features.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/xtea.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/caps.o [ 92%] 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 [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_rsa.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_validate.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/loader.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_misc.o [ 93%] 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 [ 94%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/tlv.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 [ 95%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_legacy.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_bl2.o [ 95%] 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 [ 96%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/Components/mx25lm51245g/mx25lm51245g.o [ 96%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/stm32l562e_dk/src/stm32l562e_discovery_ospi.o [ 96%] Linking C executable ../bin/bl2.axf Memory region Used Size Region Size %age Used FLASH: 46360 B 66 KB 68.60% FLASH_NOHDP: 244 B 6 KB 3.97% RAM: 27016 B 63 KB 41.88% [ 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/certs.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/pkcs11.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_create.o [ 97%] 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 [ 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 [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cache.o [ 99%] 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 [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ticket.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_tls.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_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/stm_tool.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/regression.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/preprocess.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/TFM_UPDATE.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/postbuild.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/flash_layout.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/region_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/image_macros_to_preprocess_bl2.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/lib/s_veneers.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/client.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/error.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/msg_queue.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/mutex.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/semaphore.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/thread.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/tick.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_manifest/sid.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_interface.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_svc.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/ext/tz_context.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm/veneers/tfm_veneers.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/protected_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/internal_trusted_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/storage_common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_extra.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_compat.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_client_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_sizes.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_types.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_values.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_crypto_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/initial_attestation.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_platform_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ns_interface.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ps_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_its_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_crypto_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_initial_attestation_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_audit_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_platform_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/assemble.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__ -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__/macro_parser.cpython-36.pyc -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/requirements.txt -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper/wrapper.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_s.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_ns.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/keys/root-RSA-3072_1.pem Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 http://www.mxic.com.cn<http://www.mxic.com.cn/> Ken Liu via TF-M <tf-m(a)lists.trustedfirmware.org> Sent by: "TF-M" <tf-m-bounces(a)lists.trustedfirmware.org> 2021/03/12 22:24 Please respond to 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] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board Hi Edward, Noticed that you did not open S test when enabling NS test, we met a similar issue recently. Disable S test would cause one of the test partitions not included into system and you would got an panic when connection to the SID. Should be: ‘TFM_SP_SECURE_CLIENT_2’. Can you try to enable the TEST_S and try again? Also welcome to create a fix for it. Thanks. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: Friday, March 12, 2021 7:44 PM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board Hi everyone, When I run tf-m-tests with stm32l562e_dk discovery board,the following info are showed repeatly,I think this is abnormal,I am not sure whether anyone else has the same problem. [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA protected storage NS interface tests (TFM_PS_TEST_1XXX)... > Executing 'TFM_PS_TEST_1001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA protected storage NS interface tests (TFM_PS_TEST_1XXX)... > Executing 'TFM_PS_TEST_1001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... It seems software reset happened when TFM_PS_TEST_1001 executed. Below is the detailed software version info: The compiler version:gcc-arm-none-eabi-9-2020-q2-update The tf-m source code version: git clone https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git git checkout 4f953f5f50809991510003e588695508effcdbb0 Mbed Crypto(mbedtls-2.24.0) tf-m-tests(98adf32d)：https://git.trustedfirmware.org/TF-M/tf-m-tests.git MCUboot(81d19f0)：https://github.com/mcu-tools/mcuboot psa-arch-tests(90c8e680)：https://github.com/ARM-software/psa-arch-tests The build process logs are as follows: (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ cmake .. -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_NS=ON -- 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 PSA manifests: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/psa_manifest/tfm_protected_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/auto_generated/intermedia_tfm_protected_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/psa_manifest/tfm_internal_trusted_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/intermedia_tfm_internal_trusted_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/psa_manifest/tfm_audit_logging.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/auto_generated/intermedia_tfm_audit_logging.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/psa_manifest/tfm_crypto.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/auto_generated/intermedia_tfm_crypto.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/psa_manifest/tfm_platform.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/auto_generated/intermedia_tfm_platform.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/psa_manifest/tfm_initial_attestation.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/auto_generated/intermedia_tfm_initial_attestation.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/psa_manifest/tfm_ss_core_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/auto_generated/intermedia_tfm_ss_core_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/psa_manifest/tfm_ss_core_test_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/auto_generated/intermedia_tfm_ss_core_test_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/psa_manifest/tfm_secure_client_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/auto_generated/intermedia_tfm_secure_client_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/psa_manifest/tfm_ipc_service_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/auto_generated/intermedia_tfm_ipc_service_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/psa_manifest/tfm_ipc_client_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/auto_generated/intermedia_tfm_ipc_client_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/psa_manifest/tfm_irq_test_service_1.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/auto_generated/intermedia_tfm_irq_test_service_1.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/psa_manifest/tfm_ps_test_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/auto_generated/intermedia_tfm_ps_test_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/psa_manifest/tfm_secure_client_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/auto_generated/intermedia_tfm_secure_client_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/psa_manifest/tfm_psa_proxy.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/auto_generated/intermedia_tfm_psa_proxy.c Start to generate file from the generated list: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_spm_db_func.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_spm_db_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/tfm_service_list.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_veneers.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/tfm_veneers.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_secure_irq_handlers.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_secure_irq_handlers_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/sid.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/pid.h 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.275", 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_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_GENERATOR_MODULE_DISABLED is set to FALSE -- CRYPTO_ASYMMETRIC_MODULE_DISABLED is set to FALSE -- CRYPTO_ENGINE_BUF_SIZE is set to 0x2080 -- CRYPTO_CONC_OPER_NUM is set to 8 -- ---------- Display crypto configuration - stop --------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- 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 ------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- Configuring done -- Generating done -- Build files have been written to: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ make install Scanning dependencies of target tfm_generated_files [ 1%] Built target tfm_generated_files Scanning dependencies of target platform_ns [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 4%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 4%] Building C object platform/CMakeFiles/platform_ns.dir/ext/common/uart_stdout.o [ 4%] Linking C static library libplatform_ns.a [ 4%] Built target platform_ns Scanning dependencies of target tfm_ns_log [ 4%] Building C object ns_log/CMakeFiles/tfm_ns_log.dir/tfm_log_raw.o [ 4%] Linking C static library libtfm_ns_log.a [ 4%] Built target tfm_ns_log Scanning dependencies of target tfm_test_suite_platform_ns [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/platform_tests_common.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/non_secure/platform_ns_interface_testsuite.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_helpers.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 5%] Linking C static library libtfm_test_suite_platform_ns.a [ 5%] Built target tfm_test_suite_platform_ns Scanning dependencies of target tfm_t_cose [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_sign.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_verify.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_util.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_parameters.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/crypto_adapters/t_cose_psa_crypto.o [ 6%] Linking C static library libtfm_t_cose.a [ 6%] Built target tfm_t_cose Scanning dependencies of target tfm_qcbor [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/ieee754.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_encode.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_decode.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/UsefulBuf.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/util/qcbor_util.o [ 7%] Linking C static library libtfm_qcbor.a [ 7%] Built target tfm_qcbor Scanning dependencies of target tfm_qcbor_test [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/float_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/half_to_double_from_rfc7049.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_decode_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_encode_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/run_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/UsefulBuf_Tests.o [ 9%] Linking C static library libtfm_qcbor_test.a [ 9%] Built target tfm_qcbor_test Scanning dependencies of target tfm_t_cose_test [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/run_tests.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_psa_test_key.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_test_messages.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_sign_verify_test.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_test.o [ 11%] Linking C static library libtfm_t_cose_test.a [ 11%] Built target tfm_t_cose_test Scanning dependencies of target tfm_api_ns [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_platform_func_api.o [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_audit_func_api.o [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ps_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_its_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_crypto_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_initial_attestation_func_api.o [ 12%] 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 [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ns_interface.o [ 13%] Linking C static library libtfm_api_ns.a [ 13%] Built target tfm_api_ns Scanning dependencies of target tfm_s_scatter [ 13%] Building C object platform/target/CMakeFiles/tfm_s_scatter.dir/__/__/__/common/gcc/tfm_common_s.o [ 13%] Built target tfm_s_scatter Scanning dependencies of target tfm_psa_rot_partition_ps_test [ 14%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/tfm_ps_test_service.o [ 14%] 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 [ 14%] Linking C static library libtfm_psa_rot_partition_ps_test.a [ 14%] Built target tfm_psa_rot_partition_ps_test Scanning dependencies of target tfm_app_rot_partition_core_test_2 [ 14%] 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 [ 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/interface/src/log/tfm_log_raw.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 [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/tfm_ss_core_test.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/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/__/__/framework/test_framework.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_helpers.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_integ_test_helper.o [ 16%] Linking C static library libtfm_psa_rot_partition_core_test.a [ 16%] Built target tfm_psa_rot_partition_core_test Scanning dependencies of target platform_s [ 16%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/system_stm32l5xx.o [ 16%] 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 [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/spm_hal.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_hal_isolation.o [ 17%] 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 [ 18%] 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 [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc_ex.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/Native_Driver/low_level_rng.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_isolation_mpu_v8m.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_platform_system.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/tfm_hal_ps.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_its.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_platform.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/uart_stdout.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_spm_logdev_peripheral.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_memory_symbols.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/nv_counters.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/crypto_keys.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_rotpk.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/log/tfm_log_raw.o [ 23%] Linking C static library libplatform_s.a [ 23%] Built target platform_s Scanning dependencies of target tfm_spm [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_boot_data.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_utils.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/utilities.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/spm_log.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_mem_check.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/main.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/arch.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/spm_func.o /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_seal_psp_stacks': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:91:5: warning: array subscript 1 is outside array bounds of 'uint32_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds] 91 | *(arm_lib_stck_seal_base + 1) = TFM_STACK_SEAL_VALUE; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:23: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:18: note: while referencing 'Image$$ARM_LIB_STACK_SEAL$$ZI$$Base' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:12:25: note: in definition of macro 'REGION' 12 | #define REGION(a, b, c) a##b##c | ^ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:15:47: note: in expansion of macro 'REGION_NAME' 15 | #define REGION_DECLARE_T(a, b, c, t) extern t REGION_NAME(a, b, c) | ^~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:1: note: in expansion of macro 'REGION_DECLARE_T' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_sfn_request_handler': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:450:31: warning: 'iovecs.orig_outvec' may be used uninitialized in this function [-Wmaybe-uninitialized] 450 | runtime_data->orig_outvec = iovec_ptr->orig_outvec; | ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.orig_outvec' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:446:5: warning: 'iovecs.out_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 446 | for (i = 0U; i < runtime_data->iovec_args.out_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.out_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:441:5: warning: 'iovecs.in_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 441 | for (i = 0U; i < runtime_data->iovec_args.in_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.in_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_core_svcalls_func.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_nspm_func.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_secure_api.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/log/tfm_log_raw.o [ 25%] Linking C static library libtfm_spm.a [ 25%] Built target tfm_spm 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/__/__/__/interface/src/log/tfm_log_raw.o [ 25%] Linking C static library libtfm_psa_rot_partition_platform.a [ 25%] Built target tfm_psa_rot_partition_platform Scanning dependencies of target tfm_psa_rot_partition_its [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_its_req_mngr.o [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_internal_trusted_storage.o [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/its_utils.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nand.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nor.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_ram.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_dblock.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_mblock.o [ 27%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 27%] Linking C static library libtfm_psa_rot_partition_its.a [ 27%] Built target tfm_psa_rot_partition_its Scanning dependencies of target tfm_app_rot_partition_ps [ 27%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_ps_req_mngr.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_protected_storage.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_system.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_table.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_utils.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/crypto/ps_crypto_interface.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_encrypted_object.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/nv_counters/ps_nv_counters.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 29%] Linking C static library libtfm_app_rot_partition_ps.a [ 29%] Built target tfm_app_rot_partition_ps Scanning dependencies of target tfm_psa_rot_partition_attestation [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest_req_mngr.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_core.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_asymmetric_key.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_token_encode.o [ 30%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 30%] Linking C static library libtfm_psa_rot_partition_attestation.a [ 30%] Built target tfm_psa_rot_partition_attestation Scanning dependencies of target crypto_service_mbedcrypto [ 30%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aes.o [ 30%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aesni.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/arc4.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aria.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1parse.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1write.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/base64.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/bignum.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/blowfish.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/camellia.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ccm.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chacha20.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chachapoly.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher_wrap.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cmac.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ctr_drbg.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/des.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/dhm.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdh.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdsa.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecjpake.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp_curves.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy_poll.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/error.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/gcm.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/havege.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hkdf.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hmac_drbg.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md2.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md4.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md5.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/memory_buffer_alloc.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/nist_kw.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/oid.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/padlock.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pem.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk_wrap.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs12.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs5.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkparse.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkwrite.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform_util.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/poly1305.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_se.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_slot_management.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_storage.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_its_file.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ripemd160.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa_internal.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha1.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha256.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha512.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/threading.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/timing.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version_features.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/xtea.o [ 43%] 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/crypto/tfm_mbedcrypto_alt.o [ 43%] 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 [ 43%] Linking C static library libmbedcrypto.a [ 43%] Built target crypto_service_mbedcrypto Scanning dependencies of target tfm_psa_rot_partition_crypto [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_init.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_alloc.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_cipher.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_hash.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_mac.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_aead.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_asymmetric.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key_derivation.o [ 45%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 45%] Linking C static library libtfm_psa_rot_partition_crypto.a [ 45%] Built target tfm_psa_rot_partition_crypto Scanning dependencies of target tfm_psa_rot_partition_audit [ 45%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/audit_core.o [ 45%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 45%] Linking C static library libtfm_psa_rot_partition_audit.a [ 45%] Built target tfm_psa_rot_partition_audit Scanning dependencies of target tfm_sprt [ 45%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcmp.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcpy.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memmove.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memset.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/service_api.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/tfm_sp_log_raw.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/common/tfm_hal_sp_logdev_periph.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/audit_logging/tfm_audit_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/crypto/tfm_crypto_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/initial_attestation/tfm_attest_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/protected_storage/tfm_ps_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/internal_trusted_storage/tfm_its_secure_api.o [ 48%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/platform/tfm_platform_secure_api.o [ 48%] 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 [ 48%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C static library libtfm_sprt.a [ 48%] Built target tfm_sprt Scanning dependencies of target tfm_s_log [ 48%] 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 [ 48%] Linking C static library libtfm_s_log.a [ 48%] Built target tfm_s_log Scanning dependencies of target tfm_s [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/spm/cmsis_func/tfm_veneers.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_s.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C executable ../bin/tfm_s.axf Memory region Used Size Region Size %age Used FLASH: 144552 B 219328 B 65.91% RAM: 50632 B 127 KB 38.93% VENEERS: 800 B 832 B 96.15% [ 48%] Built target tfm_s [ 48%] Generating s_veneers.o Scanning dependencies of target tfm_s_veneers [ 48%] Generating s_veneers.o [ 49%] Linking C static library libtfm_s_veneers.a [ 49%] Built target tfm_s_veneers Scanning dependencies of target tfm_test_suite_attestation_ns [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_public_key.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_test.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_common.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_asymmetric.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/non_secure/attest_asymmetric_ns_interface_testsuite.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_helpers.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 50%] Linking C static library libtfm_test_suite_attestation_ns.a [ 50%] Built target tfm_test_suite_attestation_ns Scanning dependencies of target tfm_test_suite_audit_ns [ 50%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/non_secure/audit_ns_interface_testsuite.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_helpers.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 51%] Linking C static library libtfm_test_suite_audit_ns.a [ 51%] Built target tfm_test_suite_audit_ns Scanning dependencies of target tfm_test_suite_crypto_ns [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/crypto_tests_common.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/non_secure/crypto_ns_interface_testsuite.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_helpers.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 53%] Linking C static library libtfm_test_suite_crypto_ns.a [ 53%] Built target tfm_test_suite_crypto_ns Scanning dependencies of target tfm_test_suite_its_ns [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/its_tests_common.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/non_secure/psa_its_ns_interface_testsuite.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_helpers.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 54%] 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 [ 54%] 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 [ 54%] 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 [ 54%] Linking C static library libtfm_test_suite_its_ns.a [ 54%] Built target tfm_test_suite_its_ns Scanning dependencies of target tfm_test_suite_qcbor_ns [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/non_secure/qcbor_ns_testsuite.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_helpers.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 55%] Linking C static library libtfm_test_suite_qcbor_ns.a [ 55%] Built target tfm_test_suite_qcbor_ns Scanning dependencies of target tfm_test_suite_ps_ns [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/ns_test_helpers.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/psa_ps_ns_interface_testsuite.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_helpers.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 57%] Linking C static library libtfm_test_suite_ps_ns.a [ 57%] Built target tfm_test_suite_ps_ns Scanning dependencies of target tfm_test_suite_t_cose_ns [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/non_secure/t_cose_ns_testsuite.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_helpers.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 58%] Linking C static library libtfm_test_suite_t_cose_ns.a [ 58%] Built target tfm_test_suite_t_cose_ns Scanning dependencies of target tfm_test_suite_core_ns [ 58%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_interactive_testsuite.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_positive_testsuite.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_test_api.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_helpers.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 60%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/non_secure_suites.o [ 60%] 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 [ 60%] 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 [ 60%] 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 [ 60%] Linking C static library libtfm_test_suite_core_ns.a [ 60%] Built target tfm_test_suite_core_ns Scanning dependencies of target tfm_ns_integration_test [ 60%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/tfm_integ_test.o [ 60%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 62%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/os_wrapper_cmsis_rtos_v2.o [ 62%] Linking C static library libtfm_ns_integration_test.a [ 62%] Built target tfm_ns_integration_test Scanning dependencies of target tfm_ns_scatter [ 62%] Building C object platform/target/CMakeFiles/tfm_ns_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_ns.o [ 62%] Built target tfm_ns_scatter Scanning dependencies of target tfm_ns [ 62%] Building C object app/CMakeFiles/tfm_ns.dir/main_ns.o [ 62%] 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 [ 62%] 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 [ 62%] 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 [ 62%] Building C object app/CMakeFiles/tfm_ns.dir/os_wrapper_cmsis_rtos_v2.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/non_secure_suites.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_helpers.o [ 63%] 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 [ 63%] Linking C executable ../bin/tfm_ns.axf Memory region Used Size Region Size %age Used FLASH: 126528 B 159 KB 77.71% RAM: 30208 B 128 KB 23.05% [ 63%] Built target tfm_ns Scanning dependencies of target tfm_ns_hex [ 63%] Generating ../bin/tfm_ns.hex [ 63%] Built target tfm_ns_hex Scanning dependencies of target tfm_ns_bin [ 64%] Generating ../bin/tfm_ns.bin [ 64%] Built target tfm_ns_bin Scanning dependencies of target tfm_ns_elf [ 64%] Generating ../bin/tfm_ns.elf [ 64%] Built target tfm_ns_elf Scanning dependencies of target tfm_ns_binaries [ 64%] Built target tfm_ns_binaries Scanning dependencies of target tfm_s_hex [ 64%] Generating ../bin/tfm_s.hex [ 64%] Built target tfm_s_hex Scanning dependencies of target tfm_s_bin [ 65%] Generating ../bin/tfm_s.bin [ 65%] Built target tfm_s_bin Scanning dependencies of target tfm_s_elf [ 65%] Generating ../bin/tfm_s.elf [ 65%] Built target tfm_s_elf Scanning dependencies of target tfm_s_binaries [ 65%] Built target tfm_s_binaries Scanning dependencies of target crypto_service_mbedx509 [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/certs.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/pkcs11.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_create.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crl.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crt.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_csr.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_crt.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_csr.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 68%] Linking C static library libmbedx509.a [ 68%] Built target crypto_service_mbedx509 Scanning dependencies of target crypto_service_mbedtls [ 68%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/debug.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/net_sockets.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cache.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ciphersuites.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cli.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cookie.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_msg.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_srv.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ticket.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_tls.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 70%] Linking C static library libmbedtls.a [ 70%] Built target crypto_service_mbedtls Scanning dependencies of target bl2_scatter [ 70%] Building C object platform/target/CMakeFiles/bl2_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_bl2.o [ 70%] Built target bl2_scatter Scanning dependencies of target platform_bl2 [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/boot_hal.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/tfm_low_level_security.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/low_level_device.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/boot_hal.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/uart_stdout.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/nv_counters.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_rotpk.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 74%] Linking C static library libplatform_bl2.a [ 74%] Built target platform_bl2 Scanning dependencies of target bl2_mbedcrypto [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aes.o [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aesni.o [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/arc4.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aria.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1parse.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1write.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/base64.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/bignum.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/blowfish.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/camellia.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ccm.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chacha20.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chachapoly.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher_wrap.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cmac.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ctr_drbg.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/des.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/dhm.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdh.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdsa.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecjpake.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp_curves.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy_poll.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/error.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/gcm.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/havege.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hkdf.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hmac_drbg.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md2.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md4.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md5.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/memory_buffer_alloc.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/nist_kw.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/oid.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/padlock.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pem.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk_wrap.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs12.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs5.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkparse.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkwrite.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform_util.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/poly1305.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_se.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_slot_management.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_storage.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_its_file.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ripemd160.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa_internal.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha1.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha256.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha512.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/threading.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/timing.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version_features.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/xtea.o [ 87%] Linking C static library libmbedcrypto.a [ 87%] Built target bl2_mbedcrypto Scanning dependencies of target bootutil [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/boot_record.o [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/bootutil_misc.o [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/caps.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/encrypted.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening_delay_rng_mbedtls.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec256.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ed25519.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_rsa.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_validate.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/loader.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_misc.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_move.o [ 90%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_scratch.o [ 90%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/tlv.o [ 90%] Linking C static library libbootutil.a [ 90%] Built target bootutil Scanning dependencies of target bl2 [ 90%] Building C object bl2/CMakeFiles/bl2.dir/src/security_cnt.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/src/flash_map.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/bl2_main.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/keys.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_extended.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_legacy.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_bl2.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/bl2/low_level_ospi_device.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_ospi_flash.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_ospi.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/Components/mx25lm51245g/mx25lm51245g.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/stm32l562e_dk/src/stm32l562e_discovery_ospi.o [ 92%] Linking C executable ../bin/bl2.axf Memory region Used Size Region Size %age Used FLASH: 46360 B 66 KB 68.60% FLASH_NOHDP: 244 B 6 KB 3.97% RAM: 27016 B 63 KB 41.88% [ 92%] Built target bl2 Scanning dependencies of target bl2_elf [ 93%] Generating ../bin/bl2.elf [ 93%] Built target bl2_elf Scanning dependencies of target bl2_hex [ 93%] Generating ../bin/bl2.hex [ 93%] Built target bl2_hex Scanning dependencies of target bl2_bin [ 93%] Generating ../bin/bl2.bin [ 93%] Built target bl2_bin Scanning dependencies of target bl2_binaries [ 93%] Built target bl2_binaries Scanning dependencies of target signing_layout_s [ 93%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_s.dir/signing_layout_s.o [ 93%] Built target signing_layout_s Scanning dependencies of target signing_layout_ns [ 94%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_ns.dir/signing_layout_ns.o [ 94%] Built target signing_layout_ns Scanning dependencies of target tfm_s_signed_bin [ 94%] Generating tfm_s_signed.bin [ 94%] Built target tfm_s_signed_bin Scanning dependencies of target tfm_ns_signed_bin [ 95%] Generating tfm_ns_signed.bin [ 95%] Built target tfm_ns_signed_bin Scanning dependencies of target tfm_s_ns_signed_bin [ 95%] Generating tfm_s_ns_signed.bin [ 95%] Built target tfm_s_ns_signed_bin Scanning dependencies of target signed_images [ 95%] Built target signed_images Scanning dependencies of target bl2_mbedx509 [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/certs.o [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/pkcs11.o [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509.o [ 95%] 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 [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_crt.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_csr.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_crt.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_csr.o [ 97%] Linking C static library libmbedx509.a [ 97%] Built target bl2_mbedx509 Scanning dependencies of target bl2_mbedtls [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/debug.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/net_sockets.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cache.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ciphersuites.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cli.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cookie.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_msg.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_srv.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ticket.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_tls.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_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/stm_tool.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/regression.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/preprocess.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/TFM_UPDATE.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/postbuild.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/flash_layout.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/region_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/image_macros_to_preprocess_bl2.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/lib/s_veneers.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/client.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/error.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/msg_queue.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/mutex.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/semaphore.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/thread.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/tick.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_manifest/sid.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_interface.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_svc.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/ext/tz_context.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm/veneers/tfm_veneers.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/protected_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/internal_trusted_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/storage_common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_extra.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_compat.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_client_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_sizes.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_types.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_values.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_crypto_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/initial_attestation.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_platform_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ns_interface.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ps_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_its_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_crypto_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_initial_attestation_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_audit_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_platform_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/assemble.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__ -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__/macro_parser.cpython-36.pyc -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/requirements.txt -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper/wrapper.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_s.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_ns.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/keys/root-RSA-3072_1.pem Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 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 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. =====================================================================-- 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, 2 months

1
0
0 0

Re: [TF-M] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board

by Edward Yang

Hi Ken, Thank you for your reply. I have enabled the TEST_S and tested again, it turned out to be the same results. The test log is as 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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_PS_TEST_2XXX)... > Executing 'TFM_PS_TEST_2001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_PS_TEST_2XXX)... > Executing 'TFM_PS_TEST_2001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_PS_TEST_2XXX)... > Executing 'TFM_PS_TEST_2001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Secure area #### Running Test Suite PSA protected storage S interface tests (TFM_PS_TEST_2XXX)... > Executing 'TFM_PS_TEST_2001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... The building procedure log is as following: (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ cmake .. -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_NS=ON -DTEST_S=ON -- 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 PSA manifests: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/psa_manifest/tfm_protected_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/auto_generated/intermedia_tfm_protected_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/psa_manifest/tfm_internal_trusted_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/intermedia_tfm_internal_trusted_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/psa_manifest/tfm_audit_logging.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/auto_generated/intermedia_tfm_audit_logging.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/psa_manifest/tfm_crypto.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/auto_generated/intermedia_tfm_crypto.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/psa_manifest/tfm_platform.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/auto_generated/intermedia_tfm_platform.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/psa_manifest/tfm_initial_attestation.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/auto_generated/intermedia_tfm_initial_attestation.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/psa_manifest/tfm_ss_core_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/auto_generated/intermedia_tfm_ss_core_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/psa_manifest/tfm_ss_core_test_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/auto_generated/intermedia_tfm_ss_core_test_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/psa_manifest/tfm_secure_client_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/auto_generated/intermedia_tfm_secure_client_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/psa_manifest/tfm_ipc_service_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/auto_generated/intermedia_tfm_ipc_service_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/psa_manifest/tfm_ipc_client_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/auto_generated/intermedia_tfm_ipc_client_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/psa_manifest/tfm_irq_test_service_1.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/auto_generated/intermedia_tfm_irq_test_service_1.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/psa_manifest/tfm_ps_test_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/auto_generated/intermedia_tfm_ps_test_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/psa_manifest/tfm_secure_client_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/auto_generated/intermedia_tfm_secure_client_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/psa_manifest/tfm_psa_proxy.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/auto_generated/intermedia_tfm_psa_proxy.c Start to generate file from the generated list: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_spm_db_func.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_spm_db_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/tfm_service_list.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_veneers.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/tfm_veneers.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_secure_irq_handlers.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_secure_irq_handlers_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/sid.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/pid.h 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.275", 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_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_GENERATOR_MODULE_DISABLED is set to FALSE -- CRYPTO_ASYMMETRIC_MODULE_DISABLED is set to FALSE -- CRYPTO_ENGINE_BUF_SIZE is set to 0x2080 -- CRYPTO_CONC_OPER_NUM is set to 8 -- ---------- Display crypto configuration - stop --------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- 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 ------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- Configuring done -- Generating done -- Build files have been written to: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ make install Scanning dependencies of target tfm_generated_files [ 0%] Built target tfm_generated_files Scanning dependencies of target platform_ns [ 0%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 0%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 1%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/common/uart_stdout.o [ 2%] Linking C static library libplatform_ns.a [ 2%] Built target platform_ns Scanning dependencies of target tfm_ns_log [ 2%] Building C object ns_log/CMakeFiles/tfm_ns_log.dir/tfm_log_raw.o [ 3%] Linking C static library libtfm_ns_log.a [ 3%] Built target tfm_ns_log Scanning dependencies of target tfm_test_suite_platform_ns [ 3%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/platform_tests_common.o [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/non_secure/platform_ns_interface_testsuite.o [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework.o [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_helpers.o [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 4%] Linking C static library libtfm_test_suite_platform_ns.a [ 4%] Built target tfm_test_suite_platform_ns Scanning dependencies of target tfm_t_cose [ 4%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_sign.o [ 4%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_verify.o [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_util.o [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_parameters.o [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/crypto_adapters/t_cose_psa_crypto.o [ 5%] Linking C static library libtfm_t_cose.a [ 5%] Built target tfm_t_cose Scanning dependencies of target tfm_qcbor [ 5%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/ieee754.o [ 5%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_encode.o [ 5%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_decode.o [ 5%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/UsefulBuf.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/util/qcbor_util.o [ 6%] Linking C static library libtfm_qcbor.a [ 6%] Built target tfm_qcbor Scanning dependencies of target tfm_qcbor_test [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/float_tests.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/half_to_double_from_rfc7049.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_decode_tests.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_encode_tests.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/run_tests.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/UsefulBuf_Tests.o [ 7%] Linking C static library libtfm_qcbor_test.a [ 7%] Built target tfm_qcbor_test Scanning dependencies of target tfm_t_cose_test [ 7%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/run_tests.o [ 7%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_psa_test_key.o [ 8%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_test_messages.o [ 8%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_sign_verify_test.o [ 8%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_test.o [ 8%] Linking C static library libtfm_t_cose_test.a [ 8%] Built target tfm_t_cose_test Scanning dependencies of target tfm_api_ns [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_platform_func_api.o [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_audit_func_api.o [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ps_func_api.o [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_its_func_api.o [ 9%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_crypto_func_api.o [ 10%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_initial_attestation_func_api.o [ 10%] 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 [ 10%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ns_interface.o [ 10%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/test_services/tfm_secure_client_service/tfm_secure_client_service_api.o [ 10%] Linking C static library libtfm_api_ns.a [ 10%] Built target tfm_api_ns Scanning dependencies of target tfm_s_scatter [ 10%] Building C object platform/target/CMakeFiles/tfm_s_scatter.dir/__/__/__/common/gcc/tfm_common_s.o [ 10%] Built target tfm_s_scatter Scanning dependencies of target tfm_app_rot_partition_secure_client_2 [ 11%] Building C object test/test_services/tfm_secure_client_2/CMakeFiles/tfm_app_rot_partition_secure_client_2.dir/tfm_secure_client_2.o [ 11%] Building C object test/test_services/tfm_secure_client_2/CMakeFiles/tfm_app_rot_partition_secure_client_2.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 11%] Linking C static library libtfm_app_rot_partition_secure_client_2.a [ 11%] Built target tfm_app_rot_partition_secure_client_2 Scanning dependencies of target tfm_psa_rot_partition_secure_client_service [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/tfm_secure_client_service.o [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/__/__/framework/test_framework.o [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/__/__/framework/test_framework_helpers.o [ 11%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/__/__/framework/test_framework_integ_test_helper.o [ 12%] Building C object test/test_services/tfm_secure_client_service/CMakeFiles/tfm_psa_rot_partition_secure_client_service.dir/__/__/framework/secure_suites.o [ 12%] Linking C static library libtfm_psa_rot_partition_secure_client_service.a [ 12%] Built target tfm_psa_rot_partition_secure_client_service Scanning dependencies of target tfm_psa_rot_partition_ps_test [ 12%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/tfm_ps_test_service.o [ 12%] 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 [ 13%] Linking C static library libtfm_psa_rot_partition_ps_test.a [ 13%] Built target tfm_psa_rot_partition_ps_test Scanning dependencies of target tfm_app_rot_partition_core_test_2 [ 13%] 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 [ 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/interface/src/log/tfm_log_raw.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/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework.o [ 14%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_helpers.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_integ_test_helper.o [ 15%] Linking C static library libtfm_psa_rot_partition_core_test.a [ 15%] Built target tfm_psa_rot_partition_core_test Scanning dependencies of target tfm_test_suite_ps_s [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/suites/ps/secure/psa_ps_s_interface_testsuite.o [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/suites/ps/secure/psa_ps_s_reliability_testsuite.o [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/suites/ps/secure/ps_rollback_protection_testsuite.o [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/framework/test_framework.o [ 15%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/framework/test_framework_helpers.o [ 16%] Building C object test/test_services/CMakeFiles/tfm_test_suite_ps_s.dir/__/framework/test_framework_integ_test_helper.o [ 16%] Linking C static library libtfm_test_suite_ps_s.a [ 16%] Built target tfm_test_suite_ps_s Scanning dependencies of target tfm_test_suite_crypto_s [ 16%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/suites/crypto/crypto_tests_common.o [ 16%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/suites/crypto/secure/crypto_sec_interface_testsuite.o [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/framework/test_framework.o [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/framework/test_framework_helpers.o [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_crypto_s.dir/__/framework/test_framework_integ_test_helper.o [ 17%] Linking C static library libtfm_test_suite_crypto_s.a [ 17%] Built target tfm_test_suite_crypto_s Scanning dependencies of target tfm_test_suite_audit_s [ 17%] Building C object test/test_services/CMakeFiles/tfm_test_suite_audit_s.dir/__/suites/audit/secure/audit_s_interface_testsuite.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_audit_s.dir/__/framework/test_framework.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_audit_s.dir/__/framework/test_framework_helpers.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_audit_s.dir/__/framework/test_framework_integ_test_helper.o [ 18%] Linking C static library libtfm_test_suite_audit_s.a [ 18%] Built target tfm_test_suite_audit_s Scanning dependencies of target tfm_test_suite_attestation_s [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/attest_public_key.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/attest_token_test.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/attest_token_decode_common.o [ 18%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/attest_token_decode_asymmetric.o [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/suites/attestation/secure/attest_asymmetric_s_interface_testsuite.o [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/framework/test_framework.o [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/framework/test_framework_helpers.o [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_attestation_s.dir/__/framework/test_framework_integ_test_helper.o [ 19%] Linking C static library libtfm_test_suite_attestation_s.a [ 19%] Built target tfm_test_suite_attestation_s Scanning dependencies of target tfm_test_suite_platform_s [ 19%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/suites/platform/platform_tests_common.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/suites/platform/secure/platform_s_interface_testsuite.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/framework/test_framework.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/framework/test_framework_helpers.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/__/framework/test_framework_integ_test_helper.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_platform_s.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 20%] Linking C static library libtfm_test_suite_platform_s.a [ 20%] Built target tfm_test_suite_platform_s Scanning dependencies of target tfm_test_suite_its_s [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/suites/its/its_tests_common.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/suites/its/secure/psa_its_s_interface_testsuite.o [ 20%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/suites/its/secure/psa_its_s_reliability_testsuite.o [ 21%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 21%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/framework/test_framework.o [ 21%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/framework/test_framework_helpers.o [ 21%] Building C object test/test_services/CMakeFiles/tfm_test_suite_its_s.dir/__/framework/test_framework_integ_test_helper.o [ 21%] Linking C static library libtfm_test_suite_its_s.a [ 21%] Built target tfm_test_suite_its_s Scanning dependencies of target platform_s [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/system_stm32l5xx.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/spm_hal.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_hal_isolation.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/target_cfg.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/low_level_device.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 24%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc_ex.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rng_ex.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/Native_Driver/low_level_rng.o [ 25%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_isolation_mpu_v8m.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_platform_system.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/attest_hal.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_ps.o [ 26%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_its.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_platform.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/uart_stdout.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_spm_logdev_peripheral.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_memory_symbols.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/nv_counters.o [ 27%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/crypto_keys.o [ 28%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_rotpk.o [ 28%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 28%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/log/tfm_log_raw.o [ 28%] Linking C static library libplatform_s.a [ 28%] Built target platform_s Scanning dependencies of target tfm_spm [ 28%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_boot_data.o [ 28%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_utils.o [ 28%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/utilities.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/spm_log.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_mem_check.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/main.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/arch.o [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/spm_func.o /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_seal_psp_stacks': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:91:5: warning: array subscript 1 is outside array bounds of 'uint32_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds] 91 | *(arm_lib_stck_seal_base + 1) = TFM_STACK_SEAL_VALUE; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:23: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:18: note: while referencing 'Image$$ARM_LIB_STACK_SEAL$$ZI$$Base' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:12:25: note: in definition of macro 'REGION' 12 | #define REGION(a, b, c) a##b##c | ^ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:15:47: note: in expansion of macro 'REGION_NAME' 15 | #define REGION_DECLARE_T(a, b, c, t) extern t REGION_NAME(a, b, c) | ^~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:1: note: in expansion of macro 'REGION_DECLARE_T' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_sfn_request_handler': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:450:31: warning: 'iovecs.orig_outvec' may be used uninitialized in this function [-Wmaybe-uninitialized] 450 | runtime_data->orig_outvec = iovec_ptr->orig_outvec; | ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.orig_outvec' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:446:5: warning: 'iovecs.out_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 446 | for (i = 0U; i < runtime_data->iovec_args.out_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.out_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:441:5: warning: 'iovecs.in_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 441 | for (i = 0U; i < runtime_data->iovec_args.in_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.in_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ [ 29%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_core_svcalls_func.o [ 30%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_nspm_func.o [ 30%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_secure_api.o [ 30%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/log/tfm_log_raw.o [ 30%] Linking C static library libtfm_spm.a [ 30%] Built target tfm_spm Scanning dependencies of target tfm_psa_rot_partition_platform [ 30%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/platform_sp.o [ 30%] Building C object secure_fw/partitions/platform/CMakeFiles/tfm_psa_rot_partition_platform.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 30%] Linking C static library libtfm_psa_rot_partition_platform.a [ 30%] Built target tfm_psa_rot_partition_platform Scanning dependencies of target tfm_psa_rot_partition_its [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_its_req_mngr.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_internal_trusted_storage.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/its_utils.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nand.o [ 30%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nor.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_ram.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_dblock.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_mblock.o [ 31%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 32%] Linking C static library libtfm_psa_rot_partition_its.a [ 32%] Built target tfm_psa_rot_partition_its Scanning dependencies of target tfm_app_rot_partition_ps [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_ps_req_mngr.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_protected_storage.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_system.o [ 32%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_table.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_utils.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/crypto/ps_crypto_interface.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_encrypted_object.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/suites/ps/secure/nv_counters/test_ps_nv_counters.o [ 33%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 33%] Linking C static library libtfm_app_rot_partition_ps.a [ 33%] Built target tfm_app_rot_partition_ps Scanning dependencies of target tfm_psa_rot_partition_attestation [ 33%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest.o [ 33%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest_req_mngr.o [ 33%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_core.o [ 34%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_asymmetric_key.o [ 34%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_token_encode.o [ 34%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 34%] Linking C static library libtfm_psa_rot_partition_attestation.a [ 34%] Built target tfm_psa_rot_partition_attestation Scanning dependencies of target crypto_service_mbedcrypto [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aes.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aesni.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/arc4.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aria.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1parse.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1write.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/base64.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/bignum.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/blowfish.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/camellia.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ccm.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chacha20.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chachapoly.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher_wrap.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cmac.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ctr_drbg.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/des.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/dhm.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdh.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdsa.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecjpake.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp_curves.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy_poll.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/error.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/gcm.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/havege.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hkdf.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hmac_drbg.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md2.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md4.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md5.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/memory_buffer_alloc.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/nist_kw.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/oid.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/padlock.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pem.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk_wrap.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs12.o [ 41%] 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 [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform_util.o [ 42%] 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_se.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_slot_management.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_storage.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_its_file.o [ 43%] 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_internal.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha1.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha256.o [ 44%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha512.o [ 44%] 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/xtea.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/secure_fw/partitions/crypto/tfm_mbedcrypto_alt.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%] Linking C static library libmbedcrypto.a [ 46%] Built target crypto_service_mbedcrypto Scanning dependencies of target tfm_psa_rot_partition_crypto [ 46%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_init.o [ 46%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_alloc.o [ 46%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_cipher.o [ 46%] 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 [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key_derivation.o [ 47%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C static library libtfm_psa_rot_partition_crypto.a [ 48%] Built target tfm_psa_rot_partition_crypto Scanning dependencies of target tfm_psa_rot_partition_audit [ 48%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/audit_core.o [ 48%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 49%] Linking C static library libtfm_psa_rot_partition_audit.a [ 49%] Built target tfm_psa_rot_partition_audit Scanning dependencies of target tfm_sprt [ 49%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcmp.o [ 49%] 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/__/__/audit_logging/tfm_audit_secure_api.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 [ 52%] 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 [ 52%] 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_secure_client_2/tfm_secure_client_2_api.o [ 52%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/log/tfm_log_raw.o [ 52%] Linking C static library libtfm_sprt.a [ 52%] Built target tfm_sprt Scanning dependencies of target tfm_s_log [ 53%] 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 [ 53%] Linking C static library libtfm_s_log.a [ 53%] Built target tfm_s_log Scanning dependencies of target tfm_s [ 53%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/spm/cmsis_func/tfm_veneers.o [ 53%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 54%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_s.o [ 54%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/log/tfm_log_raw.o [ 54%] Linking C executable ../bin/tfm_s.axf Memory region Used Size Region Size %age Used FLASH: 205120 B 219328 B 93.52% RAM: 56760 B 127 KB 43.65% VENEERS: 800 B 832 B 96.15% [ 54%] Built target tfm_s [ 55%] Generating s_veneers.o Scanning dependencies of target tfm_s_veneers [ 55%] Generating s_veneers.o [ 55%] Linking C static library libtfm_s_veneers.a [ 55%] Built target tfm_s_veneers Scanning dependencies of target tfm_test_suite_attestation_ns [ 55%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_public_key.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_test.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_common.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_asymmetric.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/non_secure/attest_asymmetric_ns_interface_testsuite.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework.o [ 56%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_helpers.o [ 57%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 57%] Linking C static library libtfm_test_suite_attestation_ns.a [ 57%] Built target tfm_test_suite_attestation_ns Scanning dependencies of target tfm_test_suite_audit_ns [ 57%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/non_secure/audit_ns_interface_testsuite.o [ 58%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework.o [ 58%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_helpers.o [ 58%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 58%] Linking C static library libtfm_test_suite_audit_ns.a [ 58%] Built target tfm_test_suite_audit_ns Scanning dependencies of target tfm_test_suite_crypto_ns [ 58%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/crypto_tests_common.o [ 58%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/non_secure/crypto_ns_interface_testsuite.o [ 59%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework.o [ 59%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_helpers.o [ 59%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 59%] Linking C static library libtfm_test_suite_crypto_ns.a [ 59%] Built target tfm_test_suite_crypto_ns Scanning dependencies of target tfm_test_suite_its_ns [ 59%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/its_tests_common.o [ 60%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/non_secure/psa_its_ns_interface_testsuite.o [ 60%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework.o [ 60%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_helpers.o [ 60%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 60%] 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 [ 60%] 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 [ 61%] 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 [ 61%] Linking C static library libtfm_test_suite_its_ns.a [ 61%] Built target tfm_test_suite_its_ns Scanning dependencies of target tfm_test_suite_qcbor_ns [ 61%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/non_secure/qcbor_ns_testsuite.o [ 61%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework.o [ 61%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_helpers.o [ 61%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 62%] Linking C static library libtfm_test_suite_qcbor_ns.a [ 62%] Built target tfm_test_suite_qcbor_ns Scanning dependencies of target tfm_test_suite_ps_ns [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/ns_test_helpers.o [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/psa_ps_ns_interface_testsuite.o [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework.o [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_helpers.o [ 63%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 64%] Linking C static library libtfm_test_suite_ps_ns.a [ 64%] Built target tfm_test_suite_ps_ns Scanning dependencies of target tfm_test_suite_t_cose_ns [ 64%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/non_secure/t_cose_ns_testsuite.o [ 64%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework.o [ 64%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_helpers.o [ 64%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 65%] Linking C static library libtfm_test_suite_t_cose_ns.a [ 65%] Built target tfm_test_suite_t_cose_ns Scanning dependencies of target tfm_test_suite_core_ns [ 65%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_interactive_testsuite.o [ 65%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_positive_testsuite.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_test_api.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_helpers.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 66%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/non_secure_suites.o [ 66%] 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 [ 67%] 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 [ 67%] 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 [ 67%] Linking C static library libtfm_test_suite_core_ns.a [ 67%] Built target tfm_test_suite_core_ns Scanning dependencies of target tfm_ns_integration_test [ 67%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/tfm_integ_test.o [ 67%] 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 [ 67%] 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 [ 67%] 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 [ 67%] 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 [ 68%] 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 [ 68%] 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 [ 68%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/os_wrapper_cmsis_rtos_v2.o [ 68%] Linking C static library libtfm_ns_integration_test.a [ 68%] Built target tfm_ns_integration_test Scanning dependencies of target tfm_ns_scatter [ 68%] Building C object platform/target/CMakeFiles/tfm_ns_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_ns.o [ 68%] Built target tfm_ns_scatter Scanning dependencies of target tfm_ns [ 69%] Building C object app/CMakeFiles/tfm_ns.dir/main_ns.o [ 69%] 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 [ 69%] 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 [ 69%] 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 [ 69%] Building C object app/CMakeFiles/tfm_ns.dir/os_wrapper_cmsis_rtos_v2.o [ 69%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/non_secure_suites.o [ 70%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework.o [ 70%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_helpers.o [ 70%] 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 [ 70%] Linking C executable ../bin/tfm_ns.axf Memory region Used Size Region Size %age Used FLASH: 128104 B 159 KB 78.68% RAM: 30208 B 128 KB 23.05% [ 70%] Built target tfm_ns Scanning dependencies of target tfm_ns_hex [ 71%] Generating ../bin/tfm_ns.hex [ 71%] Built target tfm_ns_hex Scanning dependencies of target tfm_ns_bin [ 71%] Generating ../bin/tfm_ns.bin [ 71%] Built target tfm_ns_bin Scanning dependencies of target tfm_ns_elf [ 71%] Generating ../bin/tfm_ns.elf [ 71%] Built target tfm_ns_elf Scanning dependencies of target tfm_ns_binaries [ 71%] Built target tfm_ns_binaries Scanning dependencies of target tfm_s_hex [ 71%] Generating ../bin/tfm_s.hex [ 71%] Built target tfm_s_hex Scanning dependencies of target tfm_s_bin [ 71%] Generating ../bin/tfm_s.bin [ 71%] Built target tfm_s_bin Scanning dependencies of target tfm_s_elf [ 71%] Generating ../bin/tfm_s.elf [ 71%] Built target tfm_s_elf Scanning dependencies of target tfm_s_binaries [ 71%] Built target tfm_s_binaries Scanning dependencies of target crypto_service_mbedx509 [ 71%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/certs.o [ 71%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/pkcs11.o [ 71%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509.o [ 71%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_create.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crl.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crt.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_csr.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_crt.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_csr.o [ 72%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 73%] Linking C static library libmbedx509.a [ 73%] Built target crypto_service_mbedx509 Scanning dependencies of target crypto_service_mbedtls [ 73%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/debug.o [ 73%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/net_sockets.o [ 73%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cache.o [ 73%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ciphersuites.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cli.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cookie.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_msg.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_srv.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ticket.o [ 74%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_tls.o [ 75%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 75%] Linking C static library libmbedtls.a [ 75%] Built target crypto_service_mbedtls Scanning dependencies of target bl2_scatter [ 75%] Building C object platform/target/CMakeFiles/bl2_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_bl2.o [ 75%] Built target bl2_scatter Scanning dependencies of target platform_bl2 [ 75%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 75%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/boot_hal.o [ 75%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 75%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/tfm_low_level_security.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/low_level_device.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 76%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 77%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/boot_hal.o [ 78%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/uart_stdout.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/nv_counters.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_rotpk.o [ 79%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 79%] Linking C static library libplatform_bl2.a [ 79%] Built target platform_bl2 Scanning dependencies of target bl2_mbedcrypto [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aes.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aesni.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/arc4.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aria.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1parse.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1write.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/base64.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/bignum.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/blowfish.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/camellia.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ccm.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chacha20.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chachapoly.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher_wrap.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cmac.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ctr_drbg.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/des.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/dhm.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdh.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdsa.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecjpake.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp_curves.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy_poll.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/error.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/gcm.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/havege.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hkdf.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hmac_drbg.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md2.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md4.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/nist_kw.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/oid.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/padlock.o [ 86%] 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_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_internal.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 [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version_features.o [ 91%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/xtea.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/caps.o [ 92%] 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 [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_rsa.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_validate.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/loader.o [ 93%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_misc.o [ 93%] 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 [ 94%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/tlv.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 [ 95%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_legacy.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 95%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_bl2.o [ 95%] 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 [ 96%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/Components/mx25lm51245g/mx25lm51245g.o [ 96%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/stm32l562e_dk/src/stm32l562e_discovery_ospi.o [ 96%] Linking C executable ../bin/bl2.axf Memory region Used Size Region Size %age Used FLASH: 46360 B 66 KB 68.60% FLASH_NOHDP: 244 B 6 KB 3.97% RAM: 27016 B 63 KB 41.88% [ 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/certs.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/pkcs11.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_create.o [ 97%] 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 [ 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 [ 99%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cache.o [ 99%] 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 [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ticket.o [100%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_tls.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_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/stm_tool.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/regression.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/preprocess.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/TFM_UPDATE.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/postbuild.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/flash_layout.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/region_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/image_macros_to_preprocess_bl2.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/lib/s_veneers.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/client.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/error.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/msg_queue.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/mutex.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/semaphore.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/thread.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/tick.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_manifest/sid.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_interface.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_svc.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/ext/tz_context.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm/veneers/tfm_veneers.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/protected_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/internal_trusted_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/storage_common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_extra.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_compat.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_client_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_sizes.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_types.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_values.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_crypto_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/initial_attestation.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_platform_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ns_interface.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ps_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_its_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_crypto_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_initial_attestation_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_audit_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_platform_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/assemble.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__ -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__/macro_parser.cpython-36.pyc -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/requirements.txt -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper/wrapper.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_s.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_ns.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/keys/root-RSA-3072_1.pem Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 http://www.mxic.com.cn Ken Liu via TF-M <tf-m(a)lists.trustedfirmware.org> Sent by: "TF-M" <tf-m-bounces(a)lists.trustedfirmware.org> 2021/03/12 22:24 Please respond to 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] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board Hi Edward, Noticed that you did not open S test when enabling NS test, we met a similar issue recently. Disable S test would cause one of the test partitions not included into system and you would got an panic when connection to the SID. Should be: ‘TFM_SP_SECURE_CLIENT_2’. Can you try to enable the TEST_S and try again? Also welcome to create a fix for it. Thanks. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: Friday, March 12, 2021 7:44 PM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board Hi everyone, When I run tf-m-tests with stm32l562e_dk discovery board,the following info are showed repeatly,I think this is abnormal,I am not sure whether anyone else has the same problem. [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA protected storage NS interface tests (TFM_PS_TEST_1XXX)... > Executing 'TFM_PS_TEST_1001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA protected storage NS interface tests (TFM_PS_TEST_1XXX)... > Executing 'TFM_PS_TEST_1001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... It seems software reset happened when TFM_PS_TEST_1001 executed. Below is the detailed software version info: The compiler version:gcc-arm-none-eabi-9-2020-q2-update The tf-m source code version: git clone https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git git checkout 4f953f5f50809991510003e588695508effcdbb0 Mbed Crypto(mbedtls-2.24.0) tf-m-tests(98adf32d)：https://git.trustedfirmware.org/TF-M/tf-m-tests.git MCUboot(81d19f0)：https://github.com/mcu-tools/mcuboot psa-arch-tests(90c8e680)：https://github.com/ARM-software/psa-arch-tests The build process logs are as follows: (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ cmake .. -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_NS=ON -- 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 PSA manifests: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/psa_manifest/tfm_protected_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/auto_generated/intermedia_tfm_protected_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/psa_manifest/tfm_internal_trusted_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/intermedia_tfm_internal_trusted_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/psa_manifest/tfm_audit_logging.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/auto_generated/intermedia_tfm_audit_logging.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/psa_manifest/tfm_crypto.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/auto_generated/intermedia_tfm_crypto.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/psa_manifest/tfm_platform.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/auto_generated/intermedia_tfm_platform.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/psa_manifest/tfm_initial_attestation.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/auto_generated/intermedia_tfm_initial_attestation.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/psa_manifest/tfm_ss_core_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/auto_generated/intermedia_tfm_ss_core_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/psa_manifest/tfm_ss_core_test_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/auto_generated/intermedia_tfm_ss_core_test_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/psa_manifest/tfm_secure_client_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/auto_generated/intermedia_tfm_secure_client_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/psa_manifest/tfm_ipc_service_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/auto_generated/intermedia_tfm_ipc_service_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/psa_manifest/tfm_ipc_client_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/auto_generated/intermedia_tfm_ipc_client_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/psa_manifest/tfm_irq_test_service_1.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/auto_generated/intermedia_tfm_irq_test_service_1.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/psa_manifest/tfm_ps_test_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/auto_generated/intermedia_tfm_ps_test_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/psa_manifest/tfm_secure_client_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/auto_generated/intermedia_tfm_secure_client_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/psa_manifest/tfm_psa_proxy.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/auto_generated/intermedia_tfm_psa_proxy.c Start to generate file from the generated list: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_spm_db_func.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_spm_db_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/tfm_service_list.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_veneers.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/tfm_veneers.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_secure_irq_handlers.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_secure_irq_handlers_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/sid.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/pid.h 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.275", 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_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_GENERATOR_MODULE_DISABLED is set to FALSE -- CRYPTO_ASYMMETRIC_MODULE_DISABLED is set to FALSE -- CRYPTO_ENGINE_BUF_SIZE is set to 0x2080 -- CRYPTO_CONC_OPER_NUM is set to 8 -- ---------- Display crypto configuration - stop --------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- 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 ------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- Configuring done -- Generating done -- Build files have been written to: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ make install Scanning dependencies of target tfm_generated_files [ 1%] Built target tfm_generated_files Scanning dependencies of target platform_ns [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 4%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 4%] Building C object platform/CMakeFiles/platform_ns.dir/ext/common/uart_stdout.o [ 4%] Linking C static library libplatform_ns.a [ 4%] Built target platform_ns Scanning dependencies of target tfm_ns_log [ 4%] Building C object ns_log/CMakeFiles/tfm_ns_log.dir/tfm_log_raw.o [ 4%] Linking C static library libtfm_ns_log.a [ 4%] Built target tfm_ns_log Scanning dependencies of target tfm_test_suite_platform_ns [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/platform_tests_common.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/non_secure/platform_ns_interface_testsuite.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_helpers.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 5%] Linking C static library libtfm_test_suite_platform_ns.a [ 5%] Built target tfm_test_suite_platform_ns Scanning dependencies of target tfm_t_cose [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_sign.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_verify.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_util.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_parameters.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/crypto_adapters/t_cose_psa_crypto.o [ 6%] Linking C static library libtfm_t_cose.a [ 6%] Built target tfm_t_cose Scanning dependencies of target tfm_qcbor [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/ieee754.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_encode.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_decode.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/UsefulBuf.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/util/qcbor_util.o [ 7%] Linking C static library libtfm_qcbor.a [ 7%] Built target tfm_qcbor Scanning dependencies of target tfm_qcbor_test [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/float_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/half_to_double_from_rfc7049.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_decode_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_encode_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/run_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/UsefulBuf_Tests.o [ 9%] Linking C static library libtfm_qcbor_test.a [ 9%] Built target tfm_qcbor_test Scanning dependencies of target tfm_t_cose_test [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/run_tests.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_psa_test_key.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_test_messages.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_sign_verify_test.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_test.o [ 11%] Linking C static library libtfm_t_cose_test.a [ 11%] Built target tfm_t_cose_test Scanning dependencies of target tfm_api_ns [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_platform_func_api.o [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_audit_func_api.o [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ps_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_its_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_crypto_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_initial_attestation_func_api.o [ 12%] 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 [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ns_interface.o [ 13%] Linking C static library libtfm_api_ns.a [ 13%] Built target tfm_api_ns Scanning dependencies of target tfm_s_scatter [ 13%] Building C object platform/target/CMakeFiles/tfm_s_scatter.dir/__/__/__/common/gcc/tfm_common_s.o [ 13%] Built target tfm_s_scatter Scanning dependencies of target tfm_psa_rot_partition_ps_test [ 14%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/tfm_ps_test_service.o [ 14%] 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 [ 14%] Linking C static library libtfm_psa_rot_partition_ps_test.a [ 14%] Built target tfm_psa_rot_partition_ps_test Scanning dependencies of target tfm_app_rot_partition_core_test_2 [ 14%] 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 [ 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/interface/src/log/tfm_log_raw.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 [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/tfm_ss_core_test.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/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/__/__/framework/test_framework.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_helpers.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_integ_test_helper.o [ 16%] Linking C static library libtfm_psa_rot_partition_core_test.a [ 16%] Built target tfm_psa_rot_partition_core_test Scanning dependencies of target platform_s [ 16%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/system_stm32l5xx.o [ 16%] 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 [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/spm_hal.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_hal_isolation.o [ 17%] 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 [ 18%] 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 [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc_ex.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/Native_Driver/low_level_rng.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_isolation_mpu_v8m.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_platform_system.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/tfm_hal_ps.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_its.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_platform.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/uart_stdout.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_spm_logdev_peripheral.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_memory_symbols.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/nv_counters.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/crypto_keys.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_rotpk.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/log/tfm_log_raw.o [ 23%] Linking C static library libplatform_s.a [ 23%] Built target platform_s Scanning dependencies of target tfm_spm [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_boot_data.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_utils.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/utilities.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/spm_log.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_mem_check.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/main.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/arch.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/spm_func.o /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_seal_psp_stacks': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:91:5: warning: array subscript 1 is outside array bounds of 'uint32_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds] 91 | *(arm_lib_stck_seal_base + 1) = TFM_STACK_SEAL_VALUE; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:23: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:18: note: while referencing 'Image$$ARM_LIB_STACK_SEAL$$ZI$$Base' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:12:25: note: in definition of macro 'REGION' 12 | #define REGION(a, b, c) a##b##c | ^ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:15:47: note: in expansion of macro 'REGION_NAME' 15 | #define REGION_DECLARE_T(a, b, c, t) extern t REGION_NAME(a, b, c) | ^~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:1: note: in expansion of macro 'REGION_DECLARE_T' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_sfn_request_handler': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:450:31: warning: 'iovecs.orig_outvec' may be used uninitialized in this function [-Wmaybe-uninitialized] 450 | runtime_data->orig_outvec = iovec_ptr->orig_outvec; | ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.orig_outvec' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:446:5: warning: 'iovecs.out_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 446 | for (i = 0U; i < runtime_data->iovec_args.out_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.out_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:441:5: warning: 'iovecs.in_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 441 | for (i = 0U; i < runtime_data->iovec_args.in_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.in_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_core_svcalls_func.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_nspm_func.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_secure_api.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/log/tfm_log_raw.o [ 25%] Linking C static library libtfm_spm.a [ 25%] Built target tfm_spm 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/__/__/__/interface/src/log/tfm_log_raw.o [ 25%] Linking C static library libtfm_psa_rot_partition_platform.a [ 25%] Built target tfm_psa_rot_partition_platform Scanning dependencies of target tfm_psa_rot_partition_its [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_its_req_mngr.o [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_internal_trusted_storage.o [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/its_utils.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nand.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nor.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_ram.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_dblock.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_mblock.o [ 27%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 27%] Linking C static library libtfm_psa_rot_partition_its.a [ 27%] Built target tfm_psa_rot_partition_its Scanning dependencies of target tfm_app_rot_partition_ps [ 27%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_ps_req_mngr.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_protected_storage.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_system.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_table.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_utils.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/crypto/ps_crypto_interface.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_encrypted_object.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/nv_counters/ps_nv_counters.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 29%] Linking C static library libtfm_app_rot_partition_ps.a [ 29%] Built target tfm_app_rot_partition_ps Scanning dependencies of target tfm_psa_rot_partition_attestation [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest_req_mngr.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_core.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_asymmetric_key.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_token_encode.o [ 30%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 30%] Linking C static library libtfm_psa_rot_partition_attestation.a [ 30%] Built target tfm_psa_rot_partition_attestation Scanning dependencies of target crypto_service_mbedcrypto [ 30%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aes.o [ 30%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aesni.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/arc4.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aria.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1parse.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1write.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/base64.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/bignum.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/blowfish.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/camellia.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ccm.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chacha20.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chachapoly.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher_wrap.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cmac.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ctr_drbg.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/des.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/dhm.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdh.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdsa.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecjpake.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp_curves.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy_poll.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/error.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/gcm.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/havege.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hkdf.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hmac_drbg.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md2.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md4.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md5.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/memory_buffer_alloc.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/nist_kw.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/oid.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/padlock.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pem.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk_wrap.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs12.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs5.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkparse.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkwrite.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform_util.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/poly1305.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_se.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_slot_management.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_storage.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_its_file.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ripemd160.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa_internal.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha1.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha256.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha512.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/threading.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/timing.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version_features.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/xtea.o [ 43%] 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/crypto/tfm_mbedcrypto_alt.o [ 43%] 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 [ 43%] Linking C static library libmbedcrypto.a [ 43%] Built target crypto_service_mbedcrypto Scanning dependencies of target tfm_psa_rot_partition_crypto [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_init.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_alloc.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_cipher.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_hash.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_mac.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_aead.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_asymmetric.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key_derivation.o [ 45%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 45%] Linking C static library libtfm_psa_rot_partition_crypto.a [ 45%] Built target tfm_psa_rot_partition_crypto Scanning dependencies of target tfm_psa_rot_partition_audit [ 45%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/audit_core.o [ 45%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 45%] Linking C static library libtfm_psa_rot_partition_audit.a [ 45%] Built target tfm_psa_rot_partition_audit Scanning dependencies of target tfm_sprt [ 45%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcmp.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcpy.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memmove.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memset.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/service_api.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/tfm_sp_log_raw.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/common/tfm_hal_sp_logdev_periph.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/audit_logging/tfm_audit_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/crypto/tfm_crypto_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/initial_attestation/tfm_attest_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/protected_storage/tfm_ps_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/internal_trusted_storage/tfm_its_secure_api.o [ 48%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/platform/tfm_platform_secure_api.o [ 48%] 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 [ 48%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C static library libtfm_sprt.a [ 48%] Built target tfm_sprt Scanning dependencies of target tfm_s_log [ 48%] 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 [ 48%] Linking C static library libtfm_s_log.a [ 48%] Built target tfm_s_log Scanning dependencies of target tfm_s [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/spm/cmsis_func/tfm_veneers.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_s.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C executable ../bin/tfm_s.axf Memory region Used Size Region Size %age Used FLASH: 144552 B 219328 B 65.91% RAM: 50632 B 127 KB 38.93% VENEERS: 800 B 832 B 96.15% [ 48%] Built target tfm_s [ 48%] Generating s_veneers.o Scanning dependencies of target tfm_s_veneers [ 48%] Generating s_veneers.o [ 49%] Linking C static library libtfm_s_veneers.a [ 49%] Built target tfm_s_veneers Scanning dependencies of target tfm_test_suite_attestation_ns [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_public_key.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_test.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_common.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_asymmetric.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/non_secure/attest_asymmetric_ns_interface_testsuite.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_helpers.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 50%] Linking C static library libtfm_test_suite_attestation_ns.a [ 50%] Built target tfm_test_suite_attestation_ns Scanning dependencies of target tfm_test_suite_audit_ns [ 50%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/non_secure/audit_ns_interface_testsuite.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_helpers.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 51%] Linking C static library libtfm_test_suite_audit_ns.a [ 51%] Built target tfm_test_suite_audit_ns Scanning dependencies of target tfm_test_suite_crypto_ns [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/crypto_tests_common.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/non_secure/crypto_ns_interface_testsuite.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_helpers.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 53%] Linking C static library libtfm_test_suite_crypto_ns.a [ 53%] Built target tfm_test_suite_crypto_ns Scanning dependencies of target tfm_test_suite_its_ns [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/its_tests_common.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/non_secure/psa_its_ns_interface_testsuite.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_helpers.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 54%] 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 [ 54%] 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 [ 54%] 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 [ 54%] Linking C static library libtfm_test_suite_its_ns.a [ 54%] Built target tfm_test_suite_its_ns Scanning dependencies of target tfm_test_suite_qcbor_ns [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/non_secure/qcbor_ns_testsuite.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_helpers.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 55%] Linking C static library libtfm_test_suite_qcbor_ns.a [ 55%] Built target tfm_test_suite_qcbor_ns Scanning dependencies of target tfm_test_suite_ps_ns [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/ns_test_helpers.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/psa_ps_ns_interface_testsuite.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_helpers.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 57%] Linking C static library libtfm_test_suite_ps_ns.a [ 57%] Built target tfm_test_suite_ps_ns Scanning dependencies of target tfm_test_suite_t_cose_ns [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/non_secure/t_cose_ns_testsuite.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_helpers.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 58%] Linking C static library libtfm_test_suite_t_cose_ns.a [ 58%] Built target tfm_test_suite_t_cose_ns Scanning dependencies of target tfm_test_suite_core_ns [ 58%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_interactive_testsuite.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_positive_testsuite.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_test_api.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_helpers.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 60%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/non_secure_suites.o [ 60%] 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 [ 60%] 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 [ 60%] 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 [ 60%] Linking C static library libtfm_test_suite_core_ns.a [ 60%] Built target tfm_test_suite_core_ns Scanning dependencies of target tfm_ns_integration_test [ 60%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/tfm_integ_test.o [ 60%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 62%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/os_wrapper_cmsis_rtos_v2.o [ 62%] Linking C static library libtfm_ns_integration_test.a [ 62%] Built target tfm_ns_integration_test Scanning dependencies of target tfm_ns_scatter [ 62%] Building C object platform/target/CMakeFiles/tfm_ns_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_ns.o [ 62%] Built target tfm_ns_scatter Scanning dependencies of target tfm_ns [ 62%] Building C object app/CMakeFiles/tfm_ns.dir/main_ns.o [ 62%] 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 [ 62%] 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 [ 62%] 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 [ 62%] Building C object app/CMakeFiles/tfm_ns.dir/os_wrapper_cmsis_rtos_v2.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/non_secure_suites.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_helpers.o [ 63%] 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 [ 63%] Linking C executable ../bin/tfm_ns.axf Memory region Used Size Region Size %age Used FLASH: 126528 B 159 KB 77.71% RAM: 30208 B 128 KB 23.05% [ 63%] Built target tfm_ns Scanning dependencies of target tfm_ns_hex [ 63%] Generating ../bin/tfm_ns.hex [ 63%] Built target tfm_ns_hex Scanning dependencies of target tfm_ns_bin [ 64%] Generating ../bin/tfm_ns.bin [ 64%] Built target tfm_ns_bin Scanning dependencies of target tfm_ns_elf [ 64%] Generating ../bin/tfm_ns.elf [ 64%] Built target tfm_ns_elf Scanning dependencies of target tfm_ns_binaries [ 64%] Built target tfm_ns_binaries Scanning dependencies of target tfm_s_hex [ 64%] Generating ../bin/tfm_s.hex [ 64%] Built target tfm_s_hex Scanning dependencies of target tfm_s_bin [ 65%] Generating ../bin/tfm_s.bin [ 65%] Built target tfm_s_bin Scanning dependencies of target tfm_s_elf [ 65%] Generating ../bin/tfm_s.elf [ 65%] Built target tfm_s_elf Scanning dependencies of target tfm_s_binaries [ 65%] Built target tfm_s_binaries Scanning dependencies of target crypto_service_mbedx509 [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/certs.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/pkcs11.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_create.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crl.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crt.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_csr.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_crt.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_csr.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 68%] Linking C static library libmbedx509.a [ 68%] Built target crypto_service_mbedx509 Scanning dependencies of target crypto_service_mbedtls [ 68%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/debug.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/net_sockets.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cache.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ciphersuites.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cli.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cookie.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_msg.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_srv.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ticket.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_tls.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 70%] Linking C static library libmbedtls.a [ 70%] Built target crypto_service_mbedtls Scanning dependencies of target bl2_scatter [ 70%] Building C object platform/target/CMakeFiles/bl2_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_bl2.o [ 70%] Built target bl2_scatter Scanning dependencies of target platform_bl2 [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/boot_hal.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/tfm_low_level_security.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/low_level_device.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/boot_hal.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/uart_stdout.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/nv_counters.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_rotpk.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 74%] Linking C static library libplatform_bl2.a [ 74%] Built target platform_bl2 Scanning dependencies of target bl2_mbedcrypto [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aes.o [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aesni.o [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/arc4.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aria.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1parse.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1write.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/base64.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/bignum.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/blowfish.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/camellia.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ccm.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chacha20.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chachapoly.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher_wrap.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cmac.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ctr_drbg.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/des.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/dhm.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdh.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdsa.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecjpake.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp_curves.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy_poll.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/error.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/gcm.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/havege.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hkdf.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hmac_drbg.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md2.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md4.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md5.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/memory_buffer_alloc.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/nist_kw.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/oid.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/padlock.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pem.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk_wrap.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs12.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs5.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkparse.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkwrite.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform_util.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/poly1305.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_se.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_slot_management.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_storage.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_its_file.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ripemd160.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa_internal.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha1.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha256.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha512.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/threading.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/timing.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version_features.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/xtea.o [ 87%] Linking C static library libmbedcrypto.a [ 87%] Built target bl2_mbedcrypto Scanning dependencies of target bootutil [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/boot_record.o [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/bootutil_misc.o [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/caps.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/encrypted.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening_delay_rng_mbedtls.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec256.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ed25519.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_rsa.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_validate.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/loader.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_misc.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_move.o [ 90%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_scratch.o [ 90%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/tlv.o [ 90%] Linking C static library libbootutil.a [ 90%] Built target bootutil Scanning dependencies of target bl2 [ 90%] Building C object bl2/CMakeFiles/bl2.dir/src/security_cnt.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/src/flash_map.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/bl2_main.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/keys.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_extended.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_legacy.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_bl2.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/bl2/low_level_ospi_device.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_ospi_flash.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_ospi.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/Components/mx25lm51245g/mx25lm51245g.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/stm32l562e_dk/src/stm32l562e_discovery_ospi.o [ 92%] Linking C executable ../bin/bl2.axf Memory region Used Size Region Size %age Used FLASH: 46360 B 66 KB 68.60% FLASH_NOHDP: 244 B 6 KB 3.97% RAM: 27016 B 63 KB 41.88% [ 92%] Built target bl2 Scanning dependencies of target bl2_elf [ 93%] Generating ../bin/bl2.elf [ 93%] Built target bl2_elf Scanning dependencies of target bl2_hex [ 93%] Generating ../bin/bl2.hex [ 93%] Built target bl2_hex Scanning dependencies of target bl2_bin [ 93%] Generating ../bin/bl2.bin [ 93%] Built target bl2_bin Scanning dependencies of target bl2_binaries [ 93%] Built target bl2_binaries Scanning dependencies of target signing_layout_s [ 93%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_s.dir/signing_layout_s.o [ 93%] Built target signing_layout_s Scanning dependencies of target signing_layout_ns [ 94%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_ns.dir/signing_layout_ns.o [ 94%] Built target signing_layout_ns Scanning dependencies of target tfm_s_signed_bin [ 94%] Generating tfm_s_signed.bin [ 94%] Built target tfm_s_signed_bin Scanning dependencies of target tfm_ns_signed_bin [ 95%] Generating tfm_ns_signed.bin [ 95%] Built target tfm_ns_signed_bin Scanning dependencies of target tfm_s_ns_signed_bin [ 95%] Generating tfm_s_ns_signed.bin [ 95%] Built target tfm_s_ns_signed_bin Scanning dependencies of target signed_images [ 95%] Built target signed_images Scanning dependencies of target bl2_mbedx509 [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/certs.o [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/pkcs11.o [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509.o [ 95%] 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 [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_crt.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_csr.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_crt.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_csr.o [ 97%] Linking C static library libmbedx509.a [ 97%] Built target bl2_mbedx509 Scanning dependencies of target bl2_mbedtls [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/debug.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/net_sockets.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cache.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ciphersuites.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cli.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cookie.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_msg.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_srv.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ticket.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_tls.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_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/stm_tool.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/regression.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/preprocess.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/TFM_UPDATE.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/postbuild.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/flash_layout.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/region_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/image_macros_to_preprocess_bl2.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/lib/s_veneers.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/client.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/error.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/msg_queue.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/mutex.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/semaphore.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/thread.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/tick.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_manifest/sid.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_interface.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_svc.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/ext/tz_context.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm/veneers/tfm_veneers.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/protected_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/internal_trusted_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/storage_common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_extra.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_compat.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_client_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_sizes.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_types.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_values.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_crypto_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/initial_attestation.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_platform_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ns_interface.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ps_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_its_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_crypto_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_initial_attestation_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_audit_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_platform_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/assemble.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__ -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__/macro_parser.cpython-36.pyc -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/requirements.txt -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper/wrapper.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_s.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_ns.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/keys/root-RSA-3072_1.pem Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 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. =====================================================================-- 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, 2 months

1
0
0 0

Re: [TF-M] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board

by Ken Liu

Hi Edward, Noticed that you did not open S test when enabling NS test, we met a similar issue recently. Disable S test would cause one of the test partitions not included into system and you would got an panic when connection to the SID. Should be: ‘TFM_SP_SECURE_CLIENT_2’. Can you try to enable the TEST_S and try again? Also welcome to create a fix for it. Thanks. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: Friday, March 12, 2021 7:44 PM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board Hi everyone, When I run tf-m-tests with stm32l562e_dk discovery board,the following info are showed repeatly,I think this is abnormal,I am not sure whether anyone else has the same problem. [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA protected storage NS interface tests (TFM_PS_TEST_1XXX)... > Executing 'TFM_PS_TEST_1001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA protected storage NS interface tests (TFM_PS_TEST_1XXX)... > Executing 'TFM_PS_TEST_1001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... It seems software reset happened when TFM_PS_TEST_1001 executed. Below is the detailed software version info: The compiler version:gcc-arm-none-eabi-9-2020-q2-update The tf-m source code version: git clone https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git git checkout 4f953f5f50809991510003e588695508effcdbb0 Mbed Crypto(mbedtls-2.24.0) tf-m-tests(98adf32d)：https://git.trustedfirmware.org/TF-M/tf-m-tests.git MCUboot(81d19f0)：https://github.com/mcu-tools/mcuboot psa-arch-tests(90c8e680)：https://github.com/ARM-software/psa-arch-tests The build process logs are as follows: (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ cmake .. -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_NS=ON -- 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 PSA manifests: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/psa_manifest/tfm_protected_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/auto_generated/intermedia_tfm_protected_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/psa_manifest/tfm_internal_trusted_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/intermedia_tfm_internal_trusted_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/psa_manifest/tfm_audit_logging.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/auto_generated/intermedia_tfm_audit_logging.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/psa_manifest/tfm_crypto.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/auto_generated/intermedia_tfm_crypto.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/psa_manifest/tfm_platform.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/auto_generated/intermedia_tfm_platform.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/psa_manifest/tfm_initial_attestation.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/auto_generated/intermedia_tfm_initial_attestation.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/psa_manifest/tfm_ss_core_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/auto_generated/intermedia_tfm_ss_core_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/psa_manifest/tfm_ss_core_test_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/auto_generated/intermedia_tfm_ss_core_test_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/psa_manifest/tfm_secure_client_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/auto_generated/intermedia_tfm_secure_client_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/psa_manifest/tfm_ipc_service_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/auto_generated/intermedia_tfm_ipc_service_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/psa_manifest/tfm_ipc_client_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/auto_generated/intermedia_tfm_ipc_client_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/psa_manifest/tfm_irq_test_service_1.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/auto_generated/intermedia_tfm_irq_test_service_1.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/psa_manifest/tfm_ps_test_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/auto_generated/intermedia_tfm_ps_test_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/psa_manifest/tfm_secure_client_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/auto_generated/intermedia_tfm_secure_client_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/psa_manifest/tfm_psa_proxy.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/auto_generated/intermedia_tfm_psa_proxy.c Start to generate file from the generated list: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_spm_db_func.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_spm_db_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/tfm_service_list.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_veneers.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/tfm_veneers.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_secure_irq_handlers.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_secure_irq_handlers_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/sid.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/pid.h 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.275", 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_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_GENERATOR_MODULE_DISABLED is set to FALSE -- CRYPTO_ASYMMETRIC_MODULE_DISABLED is set to FALSE -- CRYPTO_ENGINE_BUF_SIZE is set to 0x2080 -- CRYPTO_CONC_OPER_NUM is set to 8 -- ---------- Display crypto configuration - stop --------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- 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 ------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- Configuring done -- Generating done -- Build files have been written to: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ make install Scanning dependencies of target tfm_generated_files [ 1%] Built target tfm_generated_files Scanning dependencies of target platform_ns [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 4%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 4%] Building C object platform/CMakeFiles/platform_ns.dir/ext/common/uart_stdout.o [ 4%] Linking C static library libplatform_ns.a [ 4%] Built target platform_ns Scanning dependencies of target tfm_ns_log [ 4%] Building C object ns_log/CMakeFiles/tfm_ns_log.dir/tfm_log_raw.o [ 4%] Linking C static library libtfm_ns_log.a [ 4%] Built target tfm_ns_log Scanning dependencies of target tfm_test_suite_platform_ns [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/platform_tests_common.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/non_secure/platform_ns_interface_testsuite.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_helpers.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 5%] Linking C static library libtfm_test_suite_platform_ns.a [ 5%] Built target tfm_test_suite_platform_ns Scanning dependencies of target tfm_t_cose [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_sign.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_verify.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_util.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_parameters.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/crypto_adapters/t_cose_psa_crypto.o [ 6%] Linking C static library libtfm_t_cose.a [ 6%] Built target tfm_t_cose Scanning dependencies of target tfm_qcbor [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/ieee754.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_encode.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_decode.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/UsefulBuf.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/util/qcbor_util.o [ 7%] Linking C static library libtfm_qcbor.a [ 7%] Built target tfm_qcbor Scanning dependencies of target tfm_qcbor_test [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/float_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/half_to_double_from_rfc7049.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_decode_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_encode_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/run_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/UsefulBuf_Tests.o [ 9%] Linking C static library libtfm_qcbor_test.a [ 9%] Built target tfm_qcbor_test Scanning dependencies of target tfm_t_cose_test [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/run_tests.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_psa_test_key.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_test_messages.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_sign_verify_test.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_test.o [ 11%] Linking C static library libtfm_t_cose_test.a [ 11%] Built target tfm_t_cose_test Scanning dependencies of target tfm_api_ns [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_platform_func_api.o [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_audit_func_api.o [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ps_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_its_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_crypto_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_initial_attestation_func_api.o [ 12%] 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 [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ns_interface.o [ 13%] Linking C static library libtfm_api_ns.a [ 13%] Built target tfm_api_ns Scanning dependencies of target tfm_s_scatter [ 13%] Building C object platform/target/CMakeFiles/tfm_s_scatter.dir/__/__/__/common/gcc/tfm_common_s.o [ 13%] Built target tfm_s_scatter Scanning dependencies of target tfm_psa_rot_partition_ps_test [ 14%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/tfm_ps_test_service.o [ 14%] 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 [ 14%] Linking C static library libtfm_psa_rot_partition_ps_test.a [ 14%] Built target tfm_psa_rot_partition_ps_test Scanning dependencies of target tfm_app_rot_partition_core_test_2 [ 14%] 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 [ 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/interface/src/log/tfm_log_raw.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 [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/tfm_ss_core_test.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/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/__/__/framework/test_framework.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_helpers.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_integ_test_helper.o [ 16%] Linking C static library libtfm_psa_rot_partition_core_test.a [ 16%] Built target tfm_psa_rot_partition_core_test Scanning dependencies of target platform_s [ 16%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/system_stm32l5xx.o [ 16%] 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 [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/spm_hal.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_hal_isolation.o [ 17%] 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 [ 18%] 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 [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc_ex.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/Native_Driver/low_level_rng.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_isolation_mpu_v8m.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_platform_system.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/tfm_hal_ps.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_its.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_platform.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/uart_stdout.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_spm_logdev_peripheral.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_memory_symbols.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/nv_counters.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/crypto_keys.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_rotpk.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/log/tfm_log_raw.o [ 23%] Linking C static library libplatform_s.a [ 23%] Built target platform_s Scanning dependencies of target tfm_spm [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_boot_data.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_utils.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/utilities.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/spm_log.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_mem_check.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/main.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/arch.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/spm_func.o /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_seal_psp_stacks': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:91:5: warning: array subscript 1 is outside array bounds of 'uint32_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds] 91 | *(arm_lib_stck_seal_base + 1) = TFM_STACK_SEAL_VALUE; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:23: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:18: note: while referencing 'Image$$ARM_LIB_STACK_SEAL$$ZI$$Base' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:12:25: note: in definition of macro 'REGION' 12 | #define REGION(a, b, c) a##b##c | ^ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:15:47: note: in expansion of macro 'REGION_NAME' 15 | #define REGION_DECLARE_T(a, b, c, t) extern t REGION_NAME(a, b, c) | ^~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:1: note: in expansion of macro 'REGION_DECLARE_T' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_sfn_request_handler': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:450:31: warning: 'iovecs.orig_outvec' may be used uninitialized in this function [-Wmaybe-uninitialized] 450 | runtime_data->orig_outvec = iovec_ptr->orig_outvec; | ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.orig_outvec' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:446:5: warning: 'iovecs.out_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 446 | for (i = 0U; i < runtime_data->iovec_args.out_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.out_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:441:5: warning: 'iovecs.in_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 441 | for (i = 0U; i < runtime_data->iovec_args.in_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.in_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_core_svcalls_func.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_nspm_func.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_secure_api.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/log/tfm_log_raw.o [ 25%] Linking C static library libtfm_spm.a [ 25%] Built target tfm_spm 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/__/__/__/interface/src/log/tfm_log_raw.o [ 25%] Linking C static library libtfm_psa_rot_partition_platform.a [ 25%] Built target tfm_psa_rot_partition_platform Scanning dependencies of target tfm_psa_rot_partition_its [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_its_req_mngr.o [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_internal_trusted_storage.o [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/its_utils.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nand.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nor.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_ram.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_dblock.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_mblock.o [ 27%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 27%] Linking C static library libtfm_psa_rot_partition_its.a [ 27%] Built target tfm_psa_rot_partition_its Scanning dependencies of target tfm_app_rot_partition_ps [ 27%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_ps_req_mngr.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_protected_storage.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_system.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_table.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_utils.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/crypto/ps_crypto_interface.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_encrypted_object.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/nv_counters/ps_nv_counters.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 29%] Linking C static library libtfm_app_rot_partition_ps.a [ 29%] Built target tfm_app_rot_partition_ps Scanning dependencies of target tfm_psa_rot_partition_attestation [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest_req_mngr.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_core.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_asymmetric_key.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_token_encode.o [ 30%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 30%] Linking C static library libtfm_psa_rot_partition_attestation.a [ 30%] Built target tfm_psa_rot_partition_attestation Scanning dependencies of target crypto_service_mbedcrypto [ 30%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aes.o [ 30%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aesni.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/arc4.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aria.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1parse.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1write.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/base64.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/bignum.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/blowfish.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/camellia.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ccm.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chacha20.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chachapoly.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher_wrap.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cmac.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ctr_drbg.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/des.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/dhm.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdh.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdsa.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecjpake.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp_curves.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy_poll.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/error.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/gcm.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/havege.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hkdf.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hmac_drbg.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md2.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md4.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md5.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/memory_buffer_alloc.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/nist_kw.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/oid.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/padlock.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pem.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk_wrap.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs12.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs5.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkparse.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkwrite.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform_util.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/poly1305.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_se.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_slot_management.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_storage.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_its_file.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ripemd160.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa_internal.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha1.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha256.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha512.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/threading.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/timing.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version_features.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/xtea.o [ 43%] 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/crypto/tfm_mbedcrypto_alt.o [ 43%] 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 [ 43%] Linking C static library libmbedcrypto.a [ 43%] Built target crypto_service_mbedcrypto Scanning dependencies of target tfm_psa_rot_partition_crypto [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_init.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_alloc.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_cipher.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_hash.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_mac.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_aead.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_asymmetric.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key_derivation.o [ 45%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 45%] Linking C static library libtfm_psa_rot_partition_crypto.a [ 45%] Built target tfm_psa_rot_partition_crypto Scanning dependencies of target tfm_psa_rot_partition_audit [ 45%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/audit_core.o [ 45%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 45%] Linking C static library libtfm_psa_rot_partition_audit.a [ 45%] Built target tfm_psa_rot_partition_audit Scanning dependencies of target tfm_sprt [ 45%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcmp.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcpy.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memmove.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memset.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/service_api.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/tfm_sp_log_raw.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/common/tfm_hal_sp_logdev_periph.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/audit_logging/tfm_audit_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/crypto/tfm_crypto_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/initial_attestation/tfm_attest_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/protected_storage/tfm_ps_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/internal_trusted_storage/tfm_its_secure_api.o [ 48%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/platform/tfm_platform_secure_api.o [ 48%] 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 [ 48%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C static library libtfm_sprt.a [ 48%] Built target tfm_sprt Scanning dependencies of target tfm_s_log [ 48%] 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 [ 48%] Linking C static library libtfm_s_log.a [ 48%] Built target tfm_s_log Scanning dependencies of target tfm_s [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/spm/cmsis_func/tfm_veneers.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_s.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C executable ../bin/tfm_s.axf Memory region Used Size Region Size %age Used FLASH: 144552 B 219328 B 65.91% RAM: 50632 B 127 KB 38.93% VENEERS: 800 B 832 B 96.15% [ 48%] Built target tfm_s [ 48%] Generating s_veneers.o Scanning dependencies of target tfm_s_veneers [ 48%] Generating s_veneers.o [ 49%] Linking C static library libtfm_s_veneers.a [ 49%] Built target tfm_s_veneers Scanning dependencies of target tfm_test_suite_attestation_ns [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_public_key.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_test.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_common.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_asymmetric.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/non_secure/attest_asymmetric_ns_interface_testsuite.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_helpers.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 50%] Linking C static library libtfm_test_suite_attestation_ns.a [ 50%] Built target tfm_test_suite_attestation_ns Scanning dependencies of target tfm_test_suite_audit_ns [ 50%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/non_secure/audit_ns_interface_testsuite.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_helpers.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 51%] Linking C static library libtfm_test_suite_audit_ns.a [ 51%] Built target tfm_test_suite_audit_ns Scanning dependencies of target tfm_test_suite_crypto_ns [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/crypto_tests_common.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/non_secure/crypto_ns_interface_testsuite.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_helpers.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 53%] Linking C static library libtfm_test_suite_crypto_ns.a [ 53%] Built target tfm_test_suite_crypto_ns Scanning dependencies of target tfm_test_suite_its_ns [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/its_tests_common.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/non_secure/psa_its_ns_interface_testsuite.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_helpers.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 54%] 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 [ 54%] 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 [ 54%] 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 [ 54%] Linking C static library libtfm_test_suite_its_ns.a [ 54%] Built target tfm_test_suite_its_ns Scanning dependencies of target tfm_test_suite_qcbor_ns [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/non_secure/qcbor_ns_testsuite.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_helpers.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 55%] Linking C static library libtfm_test_suite_qcbor_ns.a [ 55%] Built target tfm_test_suite_qcbor_ns Scanning dependencies of target tfm_test_suite_ps_ns [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/ns_test_helpers.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/psa_ps_ns_interface_testsuite.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_helpers.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 57%] Linking C static library libtfm_test_suite_ps_ns.a [ 57%] Built target tfm_test_suite_ps_ns Scanning dependencies of target tfm_test_suite_t_cose_ns [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/non_secure/t_cose_ns_testsuite.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_helpers.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 58%] Linking C static library libtfm_test_suite_t_cose_ns.a [ 58%] Built target tfm_test_suite_t_cose_ns Scanning dependencies of target tfm_test_suite_core_ns [ 58%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_interactive_testsuite.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_positive_testsuite.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_test_api.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_helpers.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 60%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/non_secure_suites.o [ 60%] 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 [ 60%] 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 [ 60%] 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 [ 60%] Linking C static library libtfm_test_suite_core_ns.a [ 60%] Built target tfm_test_suite_core_ns Scanning dependencies of target tfm_ns_integration_test [ 60%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/tfm_integ_test.o [ 60%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 62%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/os_wrapper_cmsis_rtos_v2.o [ 62%] Linking C static library libtfm_ns_integration_test.a [ 62%] Built target tfm_ns_integration_test Scanning dependencies of target tfm_ns_scatter [ 62%] Building C object platform/target/CMakeFiles/tfm_ns_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_ns.o [ 62%] Built target tfm_ns_scatter Scanning dependencies of target tfm_ns [ 62%] Building C object app/CMakeFiles/tfm_ns.dir/main_ns.o [ 62%] 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 [ 62%] 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 [ 62%] 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 [ 62%] Building C object app/CMakeFiles/tfm_ns.dir/os_wrapper_cmsis_rtos_v2.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/non_secure_suites.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_helpers.o [ 63%] 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 [ 63%] Linking C executable ../bin/tfm_ns.axf Memory region Used Size Region Size %age Used FLASH: 126528 B 159 KB 77.71% RAM: 30208 B 128 KB 23.05% [ 63%] Built target tfm_ns Scanning dependencies of target tfm_ns_hex [ 63%] Generating ../bin/tfm_ns.hex [ 63%] Built target tfm_ns_hex Scanning dependencies of target tfm_ns_bin [ 64%] Generating ../bin/tfm_ns.bin [ 64%] Built target tfm_ns_bin Scanning dependencies of target tfm_ns_elf [ 64%] Generating ../bin/tfm_ns.elf [ 64%] Built target tfm_ns_elf Scanning dependencies of target tfm_ns_binaries [ 64%] Built target tfm_ns_binaries Scanning dependencies of target tfm_s_hex [ 64%] Generating ../bin/tfm_s.hex [ 64%] Built target tfm_s_hex Scanning dependencies of target tfm_s_bin [ 65%] Generating ../bin/tfm_s.bin [ 65%] Built target tfm_s_bin Scanning dependencies of target tfm_s_elf [ 65%] Generating ../bin/tfm_s.elf [ 65%] Built target tfm_s_elf Scanning dependencies of target tfm_s_binaries [ 65%] Built target tfm_s_binaries Scanning dependencies of target crypto_service_mbedx509 [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/certs.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/pkcs11.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_create.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crl.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crt.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_csr.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_crt.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_csr.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 68%] Linking C static library libmbedx509.a [ 68%] Built target crypto_service_mbedx509 Scanning dependencies of target crypto_service_mbedtls [ 68%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/debug.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/net_sockets.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cache.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ciphersuites.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cli.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cookie.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_msg.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_srv.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ticket.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_tls.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 70%] Linking C static library libmbedtls.a [ 70%] Built target crypto_service_mbedtls Scanning dependencies of target bl2_scatter [ 70%] Building C object platform/target/CMakeFiles/bl2_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_bl2.o [ 70%] Built target bl2_scatter Scanning dependencies of target platform_bl2 [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/boot_hal.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/tfm_low_level_security.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/low_level_device.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/boot_hal.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/uart_stdout.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/nv_counters.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_rotpk.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 74%] Linking C static library libplatform_bl2.a [ 74%] Built target platform_bl2 Scanning dependencies of target bl2_mbedcrypto [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aes.o [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aesni.o [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/arc4.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aria.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1parse.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1write.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/base64.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/bignum.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/blowfish.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/camellia.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ccm.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chacha20.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chachapoly.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher_wrap.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cmac.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ctr_drbg.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/des.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/dhm.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdh.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdsa.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecjpake.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp_curves.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy_poll.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/error.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/gcm.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/havege.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hkdf.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hmac_drbg.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md2.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md4.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md5.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/memory_buffer_alloc.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/nist_kw.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/oid.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/padlock.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pem.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk_wrap.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs12.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs5.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkparse.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkwrite.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform_util.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/poly1305.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_se.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_slot_management.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_storage.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_its_file.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ripemd160.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa_internal.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha1.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha256.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha512.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/threading.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/timing.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version_features.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/xtea.o [ 87%] Linking C static library libmbedcrypto.a [ 87%] Built target bl2_mbedcrypto Scanning dependencies of target bootutil [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/boot_record.o [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/bootutil_misc.o [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/caps.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/encrypted.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening_delay_rng_mbedtls.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec256.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ed25519.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_rsa.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_validate.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/loader.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_misc.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_move.o [ 90%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_scratch.o [ 90%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/tlv.o [ 90%] Linking C static library libbootutil.a [ 90%] Built target bootutil Scanning dependencies of target bl2 [ 90%] Building C object bl2/CMakeFiles/bl2.dir/src/security_cnt.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/src/flash_map.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/bl2_main.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/keys.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_extended.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_legacy.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_bl2.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/bl2/low_level_ospi_device.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_ospi_flash.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_ospi.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/Components/mx25lm51245g/mx25lm51245g.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/stm32l562e_dk/src/stm32l562e_discovery_ospi.o [ 92%] Linking C executable ../bin/bl2.axf Memory region Used Size Region Size %age Used FLASH: 46360 B 66 KB 68.60% FLASH_NOHDP: 244 B 6 KB 3.97% RAM: 27016 B 63 KB 41.88% [ 92%] Built target bl2 Scanning dependencies of target bl2_elf [ 93%] Generating ../bin/bl2.elf [ 93%] Built target bl2_elf Scanning dependencies of target bl2_hex [ 93%] Generating ../bin/bl2.hex [ 93%] Built target bl2_hex Scanning dependencies of target bl2_bin [ 93%] Generating ../bin/bl2.bin [ 93%] Built target bl2_bin Scanning dependencies of target bl2_binaries [ 93%] Built target bl2_binaries Scanning dependencies of target signing_layout_s [ 93%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_s.dir/signing_layout_s.o [ 93%] Built target signing_layout_s Scanning dependencies of target signing_layout_ns [ 94%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_ns.dir/signing_layout_ns.o [ 94%] Built target signing_layout_ns Scanning dependencies of target tfm_s_signed_bin [ 94%] Generating tfm_s_signed.bin [ 94%] Built target tfm_s_signed_bin Scanning dependencies of target tfm_ns_signed_bin [ 95%] Generating tfm_ns_signed.bin [ 95%] Built target tfm_ns_signed_bin Scanning dependencies of target tfm_s_ns_signed_bin [ 95%] Generating tfm_s_ns_signed.bin [ 95%] Built target tfm_s_ns_signed_bin Scanning dependencies of target signed_images [ 95%] Built target signed_images Scanning dependencies of target bl2_mbedx509 [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/certs.o [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/pkcs11.o [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509.o [ 95%] 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 [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_crt.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_csr.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_crt.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_csr.o [ 97%] Linking C static library libmbedx509.a [ 97%] Built target bl2_mbedx509 Scanning dependencies of target bl2_mbedtls [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/debug.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/net_sockets.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cache.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ciphersuites.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cli.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cookie.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_msg.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_srv.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ticket.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_tls.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_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/stm_tool.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/regression.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/preprocess.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/TFM_UPDATE.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/postbuild.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/flash_layout.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/region_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/image_macros_to_preprocess_bl2.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/lib/s_veneers.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/client.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/error.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/msg_queue.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/mutex.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/semaphore.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/thread.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/tick.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_manifest/sid.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_interface.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_svc.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/ext/tz_context.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm/veneers/tfm_veneers.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/protected_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/internal_trusted_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/storage_common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_extra.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_compat.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_client_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_sizes.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_types.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_values.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_crypto_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/initial_attestation.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_platform_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ns_interface.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ps_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_its_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_crypto_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_initial_attestation_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_audit_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_platform_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/assemble.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__ -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__/macro_parser.cpython-36.pyc -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/requirements.txt -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper/wrapper.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_s.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_ns.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/keys/root-RSA-3072_1.pem Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 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 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. =====================================================================

4 years, 2 months

1
0
0 0

Exceptions occured when run tf-m-tests with stm32l562e_dk discovery board

by Edward Yang

Hi everyone, When I run tf-m-tests with stm32l562e_dk discovery board,the following info are showed repeatly,I think this is abnormal,I am not sure whether anyone else has the same problem. [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA protected storage NS interface tests (TFM_PS_TEST_1XXX)... > Executing 'TFM_PS_TEST_1001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... #### Execute test suites for the Non-secure area #### Running Test Suite PSA protected storage NS interface tests (TFM_PS_TEST_1XXX)... > Executing 'TFM_PS_TEST_1001' Description: 'Set interface' [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! Booting TFM v1.2.0 Non-Secure system starting... It seems software reset happened when TFM_PS_TEST_1001 executed. Below is the detailed software version info: The compiler version:gcc-arm-none-eabi-9-2020-q2-update The tf-m source code version: git clone https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git git checkout 4f953f5f50809991510003e588695508effcdbb0 Mbed Crypto(mbedtls-2.24.0) tf-m-tests(98adf32d)：https://git.trustedfirmware.org/TF-M/tf-m-tests.git MCUboot(81d19f0)：https://github.com/mcu-tools/mcuboot psa-arch-tests(90c8e680)：https://github.com/ARM-software/psa-arch-tests The build process logs are as follows: (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ cmake .. -DTFM_PLATFORM=stm/stm32l562e_dk -DTFM_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_NS=ON -- 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 PSA manifests: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/psa_manifest/tfm_protected_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/protected_storage/auto_generated/intermedia_tfm_protected_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/psa_manifest/tfm_internal_trusted_storage.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/internal_trusted_storage/auto_generated/intermedia_tfm_internal_trusted_storage.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/psa_manifest/tfm_audit_logging.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/audit_logging/auto_generated/intermedia_tfm_audit_logging.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/psa_manifest/tfm_crypto.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/crypto/auto_generated/intermedia_tfm_crypto.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/psa_manifest/tfm_platform.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/platform/auto_generated/intermedia_tfm_platform.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/psa_manifest/tfm_initial_attestation.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/initial_attestation/auto_generated/intermedia_tfm_initial_attestation.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/psa_manifest/tfm_ss_core_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test/auto_generated/intermedia_tfm_ss_core_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/psa_manifest/tfm_ss_core_test_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_core_test_2/auto_generated/intermedia_tfm_ss_core_test_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/psa_manifest/tfm_secure_client_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_service/auto_generated/intermedia_tfm_secure_client_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/psa_manifest/tfm_ipc_service_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_service/auto_generated/intermedia_tfm_ipc_service_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/psa_manifest/tfm_ipc_client_test.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ipc_client/auto_generated/intermedia_tfm_ipc_client_test.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/psa_manifest/tfm_irq_test_service_1.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_irq_test_service_1/auto_generated/intermedia_tfm_irq_test_service_1.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/psa_manifest/tfm_ps_test_service.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_ps_test_service/auto_generated/intermedia_tfm_ps_test_service.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/psa_manifest/tfm_secure_client_2.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/test_services/tfm_secure_client_2/auto_generated/intermedia_tfm_secure_client_2.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/psa_manifest/tfm_psa_proxy.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/psa_proxy/auto_generated/intermedia_tfm_psa_proxy.c Start to generate file from the generated list: Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_spm_db_func.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_spm_db_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/partitions/tfm_service_list.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_veneers.c Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/tfm_veneers.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_func/tfm_secure_irq_handlers.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/secure_fw/spm/cmsis_psa/tfm_secure_irq_handlers_ipc.inc Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/sid.h Generating /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/generated/interface/include/psa_manifest/pid.h 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.275", 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_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_GENERATOR_MODULE_DISABLED is set to FALSE -- CRYPTO_ASYMMETRIC_MODULE_DISABLED is set to FALSE -- CRYPTO_ENGINE_BUF_SIZE is set to 0x2080 -- CRYPTO_CONC_OPER_NUM is set to 8 -- ---------- Display crypto configuration - stop --------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- 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 ------------- CMake Deprecation Warning at /home/a/workspace1/TF-M/trustedfirmware-m/mbedtls/CMakeLists.txt:23 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake. Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions. -- Configuring done -- Generating done -- Build files have been written to: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build (python3.6) a@Thinos16-dev:~/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build$ make install Scanning dependencies of target tfm_generated_files [ 1%] Built target tfm_generated_files Scanning dependencies of target platform_ns [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 2%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 3%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 4%] Building C object platform/CMakeFiles/platform_ns.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 4%] Building C object platform/CMakeFiles/platform_ns.dir/ext/common/uart_stdout.o [ 4%] Linking C static library libplatform_ns.a [ 4%] Built target platform_ns Scanning dependencies of target tfm_ns_log [ 4%] Building C object ns_log/CMakeFiles/tfm_ns_log.dir/tfm_log_raw.o [ 4%] Linking C static library libtfm_ns_log.a [ 4%] Built target tfm_ns_log Scanning dependencies of target tfm_test_suite_platform_ns [ 4%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/platform_tests_common.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/non_secure/platform_ns_interface_testsuite.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_helpers.o [ 5%] Building C object test/suites/platform/CMakeFiles/tfm_test_suite_platform_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 5%] Linking C static library libtfm_test_suite_platform_ns.a [ 5%] Built target tfm_test_suite_platform_ns Scanning dependencies of target tfm_t_cose [ 5%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_sign.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_sign1_verify.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_util.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/src/t_cose_parameters.o [ 6%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose.dir/crypto_adapters/t_cose_psa_crypto.o [ 6%] Linking C static library libtfm_t_cose.a [ 6%] Built target tfm_t_cose Scanning dependencies of target tfm_qcbor [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/ieee754.o [ 6%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_encode.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/qcbor_decode.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/src/UsefulBuf.o [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor.dir/util/qcbor_util.o [ 7%] Linking C static library libtfm_qcbor.a [ 7%] Built target tfm_qcbor Scanning dependencies of target tfm_qcbor_test [ 7%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/float_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/half_to_double_from_rfc7049.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_decode_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/qcbor_encode_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/run_tests.o [ 8%] Building C object lib/ext/qcbor/CMakeFiles/tfm_qcbor_test.dir/test/UsefulBuf_Tests.o [ 9%] Linking C static library libtfm_qcbor_test.a [ 9%] Built target tfm_qcbor_test Scanning dependencies of target tfm_t_cose_test [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/run_tests.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_psa_test_key.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_make_test_messages.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_sign_verify_test.o [ 10%] Building C object lib/ext/t_cose/CMakeFiles/tfm_t_cose_test.dir/test/t_cose_test.o [ 11%] Linking C static library libtfm_t_cose_test.a [ 11%] Built target tfm_t_cose_test Scanning dependencies of target tfm_api_ns [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_platform_func_api.o [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_audit_func_api.o [ 11%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ps_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_its_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_crypto_func_api.o [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_initial_attestation_func_api.o [ 12%] 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 [ 12%] Building C object app/CMakeFiles/tfm_api_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/tfm_ns_interface.o [ 13%] Linking C static library libtfm_api_ns.a [ 13%] Built target tfm_api_ns Scanning dependencies of target tfm_s_scatter [ 13%] Building C object platform/target/CMakeFiles/tfm_s_scatter.dir/__/__/__/common/gcc/tfm_common_s.o [ 13%] Built target tfm_s_scatter Scanning dependencies of target tfm_psa_rot_partition_ps_test [ 14%] Building C object test/test_services/tfm_ps_test_service/CMakeFiles/tfm_psa_rot_partition_ps_test.dir/tfm_ps_test_service.o [ 14%] 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 [ 14%] Linking C static library libtfm_psa_rot_partition_ps_test.a [ 14%] Built target tfm_psa_rot_partition_ps_test Scanning dependencies of target tfm_app_rot_partition_core_test_2 [ 14%] 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 [ 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/interface/src/log/tfm_log_raw.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 [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/tfm_ss_core_test.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/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/__/__/framework/test_framework.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_helpers.o [ 15%] Building C object test/test_services/tfm_core_test/CMakeFiles/tfm_psa_rot_partition_core_test.dir/__/__/framework/test_framework_integ_test_helper.o [ 16%] Linking C static library libtfm_psa_rot_partition_core_test.a [ 16%] Built target tfm_psa_rot_partition_core_test Scanning dependencies of target platform_s [ 16%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/system_stm32l5xx.o [ 16%] 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 [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/spm_hal.o [ 17%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_hal_isolation.o [ 17%] 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 [ 18%] 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 [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 20%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc_ex.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/Native_Driver/low_level_rng.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_isolation_mpu_v8m.o [ 21%] Building C object platform/CMakeFiles/platform_s.dir/ext/target/stm/common/stm32l5xx/secure/tfm_platform_system.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/tfm_hal_ps.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_its.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_platform.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/uart_stdout.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_spm_logdev_peripheral.o [ 22%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/tfm_hal_memory_symbols.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/nv_counters.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/crypto_keys.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_rotpk.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 23%] Building C object platform/CMakeFiles/platform_s.dir/__/interface/src/log/tfm_log_raw.o [ 23%] Linking C static library libplatform_s.a [ 23%] Built target platform_s Scanning dependencies of target tfm_spm [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_boot_data.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_utils.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/utilities.o [ 23%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/spm_log.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/ffm/tfm_core_mem_check.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/main.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/arch.o [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/spm_func.o /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_seal_psp_stacks': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:91:5: warning: array subscript 1 is outside array bounds of 'uint32_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds] 91 | *(arm_lib_stck_seal_base + 1) = TFM_STACK_SEAL_VALUE; | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:23: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:18: note: while referencing 'Image$$ARM_LIB_STACK_SEAL$$ZI$$Base' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:12:25: note: in definition of macro 'REGION' 12 | #define REGION(a, b, c) a##b##c | ^ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/platform/include/region.h:15:47: note: in expansion of macro 'REGION_NAME' 15 | #define REGION_DECLARE_T(a, b, c, t) extern t REGION_NAME(a, b, c) | ^~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:56:1: note: in expansion of macro 'REGION_DECLARE_T' 56 | REGION_DECLARE_T(Image$$, ARM_LIB_STACK_SEAL, $$ZI$$Base, uint32_t); | ^~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c: In function 'tfm_spm_sfn_request_handler': /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:450:31: warning: 'iovecs.orig_outvec' may be used uninitialized in this function [-Wmaybe-uninitialized] 450 | runtime_data->orig_outvec = iovec_ptr->orig_outvec; | ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.orig_outvec' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:446:5: warning: 'iovecs.out_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 446 | for (i = 0U; i < runtime_data->iovec_args.out_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.out_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:441:5: warning: 'iovecs.in_len' may be used uninitialized in this function [-Wmaybe-uninitialized] 441 | for (i = 0U; i < runtime_data->iovec_args.in_len; ++i) { | ^~~ /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/secure_fw/spm/cmsis_func/spm_func.c:803:27: note: 'iovecs.in_len' was declared here 803 | struct iovec_params_t iovecs; | ^~~~~~ [ 24%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_core_svcalls_func.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_nspm_func.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/cmsis_func/tfm_secure_api.o [ 25%] Building C object secure_fw/spm/CMakeFiles/tfm_spm.dir/__/__/interface/src/log/tfm_log_raw.o [ 25%] Linking C static library libtfm_spm.a [ 25%] Built target tfm_spm 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/__/__/__/interface/src/log/tfm_log_raw.o [ 25%] Linking C static library libtfm_psa_rot_partition_platform.a [ 25%] Built target tfm_psa_rot_partition_platform Scanning dependencies of target tfm_psa_rot_partition_its [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_its_req_mngr.o [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/tfm_internal_trusted_storage.o [ 25%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/its_utils.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nand.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_nor.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash/its_flash_ram.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_dblock.o [ 26%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/flash_fs/its_flash_fs_mblock.o [ 27%] Building C object secure_fw/partitions/internal_trusted_storage/CMakeFiles/tfm_psa_rot_partition_its.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 27%] Linking C static library libtfm_psa_rot_partition_its.a [ 27%] Built target tfm_psa_rot_partition_its Scanning dependencies of target tfm_app_rot_partition_ps [ 27%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_ps_req_mngr.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/tfm_protected_storage.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_system.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_object_table.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_utils.o [ 28%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/crypto/ps_crypto_interface.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/ps_encrypted_object.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/nv_counters/ps_nv_counters.o [ 29%] Building C object secure_fw/partitions/protected_storage/CMakeFiles/tfm_app_rot_partition_ps.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 29%] Linking C static library libtfm_app_rot_partition_ps.a [ 29%] Built target tfm_app_rot_partition_ps Scanning dependencies of target tfm_psa_rot_partition_attestation [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/tfm_attest_req_mngr.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_core.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_asymmetric_key.o [ 29%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/attest_token_encode.o [ 30%] Building C object secure_fw/partitions/initial_attestation/CMakeFiles/tfm_psa_rot_partition_attestation.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 30%] Linking C static library libtfm_psa_rot_partition_attestation.a [ 30%] Built target tfm_psa_rot_partition_attestation Scanning dependencies of target crypto_service_mbedcrypto [ 30%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aes.o [ 30%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aesni.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/arc4.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/aria.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1parse.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/asn1write.o [ 31%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/base64.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/bignum.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/blowfish.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/camellia.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ccm.o [ 32%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chacha20.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/chachapoly.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cipher_wrap.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/cmac.o [ 33%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ctr_drbg.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/des.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/dhm.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdh.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecdsa.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecjpake.o [ 34%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ecp_curves.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/entropy_poll.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/error.o [ 35%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/gcm.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/havege.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hkdf.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/hmac_drbg.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md.o [ 36%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md2.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md4.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/md5.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/memory_buffer_alloc.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/nist_kw.o [ 37%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/oid.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/padlock.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pem.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pk_wrap.o [ 38%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs12.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkcs5.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkparse.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/pkwrite.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform.o [ 39%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/platform_util.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/poly1305.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_se.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_slot_management.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_crypto_storage.o [ 40%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/psa_its_file.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/ripemd160.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/rsa_internal.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha1.o [ 41%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha256.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/sha512.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/threading.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/timing.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version.o [ 42%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/version_features.o [ 43%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedcrypto.dir/xtea.o [ 43%] 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/crypto/tfm_mbedcrypto_alt.o [ 43%] 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 [ 43%] Linking C static library libmbedcrypto.a [ 43%] Built target crypto_service_mbedcrypto Scanning dependencies of target tfm_psa_rot_partition_crypto [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_init.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_alloc.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_cipher.o [ 43%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_hash.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_mac.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_aead.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_asymmetric.o [ 44%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/crypto_key_derivation.o [ 45%] Building C object secure_fw/partitions/crypto/CMakeFiles/tfm_psa_rot_partition_crypto.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 45%] Linking C static library libtfm_psa_rot_partition_crypto.a [ 45%] Built target tfm_psa_rot_partition_crypto Scanning dependencies of target tfm_psa_rot_partition_audit [ 45%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/audit_core.o [ 45%] Building C object secure_fw/partitions/audit_logging/CMakeFiles/tfm_psa_rot_partition_audit.dir/__/__/__/interface/src/log/tfm_log_raw.o [ 45%] Linking C static library libtfm_psa_rot_partition_audit.a [ 45%] Built target tfm_psa_rot_partition_audit Scanning dependencies of target tfm_sprt [ 45%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcmp.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memcpy.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memmove.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/crt_memset.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/service_api.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/tfm_sp_log_raw.o [ 46%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/platform/ext/common/tfm_hal_sp_logdev_periph.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/audit_logging/tfm_audit_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/crypto/tfm_crypto_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/initial_attestation/tfm_attest_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/protected_storage/tfm_ps_secure_api.o [ 47%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/internal_trusted_storage/tfm_its_secure_api.o [ 48%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/platform/tfm_platform_secure_api.o [ 48%] 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 [ 48%] Building C object secure_fw/partitions/lib/sprt/CMakeFiles/tfm_sprt.dir/__/__/__/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C static library libtfm_sprt.a [ 48%] Built target tfm_sprt Scanning dependencies of target tfm_s_log [ 48%] 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 [ 48%] Linking C static library libtfm_s_log.a [ 48%] Built target tfm_s_log Scanning dependencies of target tfm_s [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/generated/secure_fw/spm/cmsis_func/tfm_veneers.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_s.o [ 48%] Building C object secure_fw/CMakeFiles/tfm_s.dir/__/interface/src/log/tfm_log_raw.o [ 48%] Linking C executable ../bin/tfm_s.axf Memory region Used Size Region Size %age Used FLASH: 144552 B 219328 B 65.91% RAM: 50632 B 127 KB 38.93% VENEERS: 800 B 832 B 96.15% [ 48%] Built target tfm_s [ 48%] Generating s_veneers.o Scanning dependencies of target tfm_s_veneers [ 48%] Generating s_veneers.o [ 49%] Linking C static library libtfm_s_veneers.a [ 49%] Built target tfm_s_veneers Scanning dependencies of target tfm_test_suite_attestation_ns [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_public_key.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_test.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_common.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/attest_token_decode_asymmetric.o [ 49%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/non_secure/attest_asymmetric_ns_interface_testsuite.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_helpers.o [ 50%] Building C object test/suites/attestation/CMakeFiles/tfm_test_suite_attestation_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 50%] Linking C static library libtfm_test_suite_attestation_ns.a [ 50%] Built target tfm_test_suite_attestation_ns Scanning dependencies of target tfm_test_suite_audit_ns [ 50%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/non_secure/audit_ns_interface_testsuite.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_helpers.o [ 51%] Building C object test/suites/audit/CMakeFiles/tfm_test_suite_audit_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 51%] Linking C static library libtfm_test_suite_audit_ns.a [ 51%] Built target tfm_test_suite_audit_ns Scanning dependencies of target tfm_test_suite_crypto_ns [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/crypto_tests_common.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/non_secure/crypto_ns_interface_testsuite.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_helpers.o [ 52%] Building C object test/suites/crypto/CMakeFiles/tfm_test_suite_crypto_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 53%] Linking C static library libtfm_test_suite_crypto_ns.a [ 53%] Built target tfm_test_suite_crypto_ns Scanning dependencies of target tfm_test_suite_its_ns [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/its_tests_common.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/non_secure/psa_its_ns_interface_testsuite.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_helpers.o [ 53%] Building C object test/suites/its/CMakeFiles/tfm_test_suite_its_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 54%] 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 [ 54%] 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 [ 54%] 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 [ 54%] Linking C static library libtfm_test_suite_its_ns.a [ 54%] Built target tfm_test_suite_its_ns Scanning dependencies of target tfm_test_suite_qcbor_ns [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/non_secure/qcbor_ns_testsuite.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_helpers.o [ 54%] Building C object test/suites/qcbor/CMakeFiles/tfm_test_suite_qcbor_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 55%] Linking C static library libtfm_test_suite_qcbor_ns.a [ 55%] Built target tfm_test_suite_qcbor_ns Scanning dependencies of target tfm_test_suite_ps_ns [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/ns_test_helpers.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/non_secure/psa_ps_ns_interface_testsuite.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_helpers.o [ 56%] Building C object test/suites/ps/CMakeFiles/tfm_test_suite_ps_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 57%] Linking C static library libtfm_test_suite_ps_ns.a [ 57%] Built target tfm_test_suite_ps_ns Scanning dependencies of target tfm_test_suite_t_cose_ns [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/non_secure/t_cose_ns_testsuite.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_helpers.o [ 57%] Building C object test/suites/t_cose/CMakeFiles/tfm_test_suite_t_cose_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 58%] Linking C static library libtfm_test_suite_t_cose_ns.a [ 58%] Built target tfm_test_suite_t_cose_ns Scanning dependencies of target tfm_test_suite_core_ns [ 58%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_interactive_testsuite.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_ns_positive_testsuite.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/non_secure/core_test_api.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_helpers.o [ 59%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/test_framework_integ_test_helper.o [ 60%] Building C object test/suites/core/CMakeFiles/tfm_test_suite_core_ns.dir/__/__/framework/non_secure_suites.o [ 60%] 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 [ 60%] 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 [ 60%] 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 [ 60%] Linking C static library libtfm_test_suite_core_ns.a [ 60%] Built target tfm_test_suite_core_ns Scanning dependencies of target tfm_ns_integration_test [ 60%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/tfm_integ_test.o [ 60%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 61%] 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 [ 62%] Building C object app/CMakeFiles/tfm_ns_integration_test.dir/os_wrapper_cmsis_rtos_v2.o [ 62%] Linking C static library libtfm_ns_integration_test.a [ 62%] Built target tfm_ns_integration_test Scanning dependencies of target tfm_ns_scatter [ 62%] Building C object platform/target/CMakeFiles/tfm_ns_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_ns.o [ 62%] Built target tfm_ns_scatter Scanning dependencies of target tfm_ns [ 62%] Building C object app/CMakeFiles/tfm_ns.dir/main_ns.o [ 62%] 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 [ 62%] 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 [ 62%] 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 [ 62%] Building C object app/CMakeFiles/tfm_ns.dir/os_wrapper_cmsis_rtos_v2.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/non_secure_suites.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework.o [ 63%] Building C object app/CMakeFiles/tfm_ns.dir/home/a/workspace1/TF-M/trustedfirmware-m/tf-m-tests/test/framework/test_framework_helpers.o [ 63%] 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 [ 63%] Linking C executable ../bin/tfm_ns.axf Memory region Used Size Region Size %age Used FLASH: 126528 B 159 KB 77.71% RAM: 30208 B 128 KB 23.05% [ 63%] Built target tfm_ns Scanning dependencies of target tfm_ns_hex [ 63%] Generating ../bin/tfm_ns.hex [ 63%] Built target tfm_ns_hex Scanning dependencies of target tfm_ns_bin [ 64%] Generating ../bin/tfm_ns.bin [ 64%] Built target tfm_ns_bin Scanning dependencies of target tfm_ns_elf [ 64%] Generating ../bin/tfm_ns.elf [ 64%] Built target tfm_ns_elf Scanning dependencies of target tfm_ns_binaries [ 64%] Built target tfm_ns_binaries Scanning dependencies of target tfm_s_hex [ 64%] Generating ../bin/tfm_s.hex [ 64%] Built target tfm_s_hex Scanning dependencies of target tfm_s_bin [ 65%] Generating ../bin/tfm_s.bin [ 65%] Built target tfm_s_bin Scanning dependencies of target tfm_s_elf [ 65%] Generating ../bin/tfm_s.elf [ 65%] Built target tfm_s_elf Scanning dependencies of target tfm_s_binaries [ 65%] Built target tfm_s_binaries Scanning dependencies of target crypto_service_mbedx509 [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/certs.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/pkcs11.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_create.o [ 66%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crl.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_crt.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509_csr.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_crt.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/x509write_csr.o [ 67%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedx509.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 68%] Linking C static library libmbedx509.a [ 68%] Built target crypto_service_mbedx509 Scanning dependencies of target crypto_service_mbedtls [ 68%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/debug.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/net_sockets.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cache.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ciphersuites.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cli.o [ 69%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_cookie.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_msg.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_srv.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_ticket.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/ssl_tls.o [ 70%] Building C object secure_fw/partitions/crypto/mbedcrypto/library/CMakeFiles/crypto_service_mbedtls.dir/home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/interface/src/log/tfm_log_raw.o [ 70%] Linking C static library libmbedtls.a [ 70%] Built target crypto_service_mbedtls Scanning dependencies of target bl2_scatter [ 70%] Building C object platform/target/CMakeFiles/bl2_scatter.dir/__/common/stm32l5xx/Device/Source/gcc/stm32l5xx_bl2.o [ 70%] Built target bl2_scatter Scanning dependencies of target platform_bl2 [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Device/Source/Templates/system_stm32l5xx.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/boot_hal.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/Native_Driver/mpu_armv8m_drv.o [ 70%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/tfm_low_level_security.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/bl2/low_level_device.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_flash.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_com.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal.o [ 71%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_flash_ex.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr_ex.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_dma.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_pwr.o [ 72%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_rcc.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_cortex.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gpio.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_uart_ex.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_gtzc.o [ 73%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/boot_hal.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/uart_stdout.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/nv_counters.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_rotpk.o [ 74%] Building C object platform/CMakeFiles/platform_bl2.dir/ext/common/template/tfm_initial_attestation_key_material.o [ 74%] Linking C static library libplatform_bl2.a [ 74%] Built target platform_bl2 Scanning dependencies of target bl2_mbedcrypto [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aes.o [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aesni.o [ 74%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/arc4.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/aria.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1parse.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/asn1write.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/base64.o [ 75%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/bignum.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/blowfish.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/camellia.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ccm.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chacha20.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/chachapoly.o [ 76%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cipher_wrap.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/cmac.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ctr_drbg.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/des.o [ 77%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/dhm.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdh.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecdsa.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecjpake.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp.o [ 78%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ecp_curves.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/entropy_poll.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/error.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/gcm.o [ 79%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/havege.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hkdf.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/hmac_drbg.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md2.o [ 80%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md4.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/md5.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/memory_buffer_alloc.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/nist_kw.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/oid.o [ 81%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/padlock.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pem.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pk_wrap.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs12.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkcs5.o [ 82%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkparse.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/pkwrite.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/platform_util.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/poly1305.o [ 83%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_se.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_slot_management.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_crypto_storage.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/psa_its_file.o [ 84%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/ripemd160.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/rsa_internal.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha1.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha256.o [ 85%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/sha512.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/threading.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/timing.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/version_features.o [ 86%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedcrypto.dir/xtea.o [ 87%] Linking C static library libmbedcrypto.a [ 87%] Built target bl2_mbedcrypto Scanning dependencies of target bootutil [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/boot_record.o [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/bootutil_misc.o [ 87%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/caps.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/encrypted.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/fault_injection_hardening_delay_rng_mbedtls.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec.o [ 88%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ec256.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_ed25519.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_rsa.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/image_validate.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/loader.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_misc.o [ 89%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_move.o [ 90%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/swap_scratch.o [ 90%] Building C object bl2/ext/mcuboot/bootutil/CMakeFiles/bootutil.dir/src/tlv.o [ 90%] Linking C static library libbootutil.a [ 90%] Built target bootutil Scanning dependencies of target bl2 [ 90%] Building C object bl2/CMakeFiles/bl2.dir/src/security_cnt.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/src/flash_map.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/bl2_main.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/keys.o [ 90%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_extended.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/ext/mcuboot/flash_map_legacy.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Native_Driver/tick.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/Device/Source/startup_stm32l5xx_bl2.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/bl2/low_level_ospi_device.o [ 91%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/CMSIS_Driver/low_level_ospi_flash.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/stm32l5xx/stm32l5xx_hal/Src/stm32l5xx_hal_ospi.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/common/Components/mx25lm51245g/mx25lm51245g.o [ 92%] Building C object bl2/CMakeFiles/bl2.dir/__/platform/ext/target/stm/stm32l562e_dk/src/stm32l562e_discovery_ospi.o [ 92%] Linking C executable ../bin/bl2.axf Memory region Used Size Region Size %age Used FLASH: 46360 B 66 KB 68.60% FLASH_NOHDP: 244 B 6 KB 3.97% RAM: 27016 B 63 KB 41.88% [ 92%] Built target bl2 Scanning dependencies of target bl2_elf [ 93%] Generating ../bin/bl2.elf [ 93%] Built target bl2_elf Scanning dependencies of target bl2_hex [ 93%] Generating ../bin/bl2.hex [ 93%] Built target bl2_hex Scanning dependencies of target bl2_bin [ 93%] Generating ../bin/bl2.bin [ 93%] Built target bl2_bin Scanning dependencies of target bl2_binaries [ 93%] Built target bl2_binaries Scanning dependencies of target signing_layout_s [ 93%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_s.dir/signing_layout_s.o [ 93%] Built target signing_layout_s Scanning dependencies of target signing_layout_ns [ 94%] Building C object bl2/ext/mcuboot/CMakeFiles/signing_layout_ns.dir/signing_layout_ns.o [ 94%] Built target signing_layout_ns Scanning dependencies of target tfm_s_signed_bin [ 94%] Generating tfm_s_signed.bin [ 94%] Built target tfm_s_signed_bin Scanning dependencies of target tfm_ns_signed_bin [ 95%] Generating tfm_ns_signed.bin [ 95%] Built target tfm_ns_signed_bin Scanning dependencies of target tfm_s_ns_signed_bin [ 95%] Generating tfm_s_ns_signed.bin [ 95%] Built target tfm_s_ns_signed_bin Scanning dependencies of target signed_images [ 95%] Built target signed_images Scanning dependencies of target bl2_mbedx509 [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/certs.o [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/pkcs11.o [ 95%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509.o [ 95%] 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 [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_crt.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509_csr.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_crt.o [ 96%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedx509.dir/x509write_csr.o [ 97%] Linking C static library libmbedx509.a [ 97%] Built target bl2_mbedx509 Scanning dependencies of target bl2_mbedtls [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/debug.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/net_sockets.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cache.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ciphersuites.o [ 97%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cli.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_cookie.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_msg.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_srv.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_ticket.o [ 98%] Building C object bl2/mbedcrypto/library/CMakeFiles/bl2_mbedtls.dir/ssl_tls.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_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/secure_fw/partitions/crypto/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedcrypto.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedx509.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/bl2/mbedcrypto/install/libmbedtls.a -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/stm_tool.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/regression.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/preprocess.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/TFM_UPDATE.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/postbuild.sh -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/flash_layout.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/region_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/image_macros_to_preprocess_bl2.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.elf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.axf -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/bl2.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_ns.map -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s_ns_signed.bin -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/outputs/STM/STM32L562E_DK/tfm_s.hex -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/lib/s_veneers.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/client.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/error.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/msg_queue.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/mutex.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/semaphore.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/thread.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/os_wrapper/tick.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_manifest/sid.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_interface.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_ns_svc.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/ext/tz_context.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm/veneers/tfm_veneers.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/protected_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/internal_trusted_storage.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/storage_common.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_extra.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_compat.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_client_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_sizes.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_struct.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_types.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/crypto_values.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_crypto_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa/initial_attestation.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/psa_audit_defs.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/include/tfm_platform_api.h -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ns_interface.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_ps_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_its_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_crypto_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_initial_attestation_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_audit_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/interface/src/tfm_platform_func_api.c -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/macro_parser.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/assemble.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__ -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/__pycache__/macro_parser.cpython-36.pyc -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/requirements.txt -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/scripts/wrapper/wrapper.py -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_s.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/layout_files/signing_layout_ns.o -- Installing: /home/a/workspace1/TF-M/trustedfirmware-m/trusted-firmware-m/cmake_build/install/image_signing/keys/root-RSA-3072_1.pem Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 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. =====================================================================

4 years, 2 months

1
0
0 0

Re: [TF-M] Profile Large design document for review

by David Hu

Hi all, I merged Profile Large design document as planned. If you have any further comment, please feel free to comment on the patch or send it to this mailing list. Profile Large will be updated if new major feature is required. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Tuesday, March 9, 2021 4:06 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Profile Large design document for review Hi all, I'd like to merge Profile Large design this Thursday if no further comment. Since there are other TF-M major features under development in parallel, Profile Large design will be updated later when other major features are available. 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: Monday, March 1, 2021 10:30 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] Profile Large design document for review Hi all, Can I ask for your comments on the TF-M Profile Large design document? TF-M Profile Large is one of TF-M Profiles. Profile Medium and Profile Small have been supported in TF-M. The document can be reviewed via https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8546/1/docs/…. Any comment is welcome! Best regards, Hu Ziji

4 years, 2 months

1
0
0 0

by Ken Liu

Hi, We are refining the IRQ logic, and every time the new update pushed it needs to make the IRQ enabled test pass - as library model IRQ code is there, it needs efforts to create workarounds ensure the test pass every time. Check if someone is using the library mode IRQ handling (Check if you need the library model 'tfm_secure_irq_handlers.inc' or 'TFM_SVC_DEPRIV_REQ' is a quick path). If there are no users are using this logic we would disable this feature for a while till the IRQ logic get updated, this would save us much effort to maintain the legacy logic. This means if someone set 'TFM_IRQ_TEST' as ON the build system still ignore it. This action would happen after 1.3.0, we mention it now to give enough preparation for this. I would send another follow-up mail for chasing after the release. Please help to provide your feedback, thank you very much! /Ken

4 years, 2 months

1
0
0 0

TF-M static check for each patch has enabled on openCI

by Karl Zhang

Hi, The static check now enabled on openCI per the TF-M open tech forum discussion on 4th February 2021. The slides and video can be found from here<https://www.trustedfirmware.org/meetings/tf-m-technical-forum/>. Please let us know if you have any further concerns about the checks after enabled. A minor change to the slides is the cppcheck version has updated from 1.81 to 2.3. Thanks Karl

4 years, 2 months

1
0
0 0

TF-M v1.3.0 approaching. Code freeze heads up.

by Anton Komlev

Hi, TF-Mv1.3.0 release is approaching, planned for the end of March. TF-M code repository is to be freeze on March 18th, and tagged by TF-Mv1.3.0-RC1. Please plan you work accordingly and push your changes before the date. Thanks, Anton

4 years, 2 months

1
0
0 0

Technical Forum call - March 18

by Anton Komlev

Hello, The next Technical Forum is planned on Thursday, March 18 at 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

1
0
0 0

Re: [TF-M] Profile Large design document for review

by David Hu

Hi all, I'd like to merge Profile Large design this Thursday if no further comment. Since there are other TF-M major features under development in parallel, Profile Large design will be updated later when other major features are available. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Monday, March 1, 2021 10:30 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Profile Large design document for review Hi all, Can I ask for your comments on the TF-M Profile Large design document? TF-M Profile Large is one of TF-M Profiles. Profile Medium and Profile Small have been supported in TF-M. The document can be reviewed via https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8546/1/docs/…. Any comment is welcome! Best regards, Hu Ziji

4 years, 2 months

1
0
0 0

Re: [TF-M] Security vulnerability notice - SVC handler fetches incorrect caller stack pointer under specific cases.

by Kumar Gala

Agreed, I think it's a great thing for the SC to take up and make a policy on. Will add 2 cents: * Being a security focused project, I think its import that at least there is a patch release for the most recent officially released version, regardless of when the next release of TFM might be released. * Maybe looking at what policy a project like mbedtls has as a starting point. - k > On Mar 5, 2021, at 12:34 PM, Anton Komlev via TF-M <tf-m(a)lists.trustedfirmware.org> wrote: > > Hi Kumar, All, > > Thanks for bringing this topic up. > At the moment there is no plan for issuing the release v1.2.1 because of lack of policy for such hot fix releases. The release policy upgrade proposal shall be reviewed and agreed in the Steering Committee with the main questions: > 1. What is the hot fix baseline? > 2. What is the testing scope of the fix? > 3. On which platform(s) the fix shall be tested? > > The policy is under discussion and the community input is welcome. Please share your thoughts on the topic. > > The release v1.3.0 is expected by end of March-beginning of April, which will include the fix. > > Thanks, > Anton > > > -----Original Message----- > From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kumar Gala via TF-M > Sent: Friday, March 5, 2021 5:36 PM > To: Ken Liu <Ken.Liu(a)arm.com> > Cc: nd <nd(a)arm.com>; tf-m(a)lists.trustedfirmware.org > Subject: Re: [TF-M] Security vulnerability notice - SVC handler fetches incorrect caller stack pointer under specific cases. > > > >> On Mar 5, 2021, at 9:28 AM, Ken Liu via TF-M <tf-m(a)lists.trustedfirmware.org> wrote: >> >> Hi Everyone, >> >> There is a new security vulnerability reported about the SVC handler fetches a wrong caller stack pointer under specific cases, which impacts the subsequent execution. >> >> Please find the security advisory specific to TF-M and patches that have been developed as per the TrustedFirmware.org security process[1] below : >> >> 1. TF-M Security advisory: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9005 >> 2. Fix based on the latest master has been merged into TF-M repo. The patch also can be found in Gerrit:https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8575 and https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8576. >> >> Please let us know if you have any comments. >> >> BR >> >> /Ken Liu >> >> [1] https://developer.trustedfirmware.org/w/collaboration/security_center/repor… >> -- >> TF-M mailing list >> TF-M(a)lists.trustedfirmware.org >> https://lists.trustedfirmware.org/mailman/listinfo/tf-m > > Is there plans for a security release of TFM v1.2 with this fix? > > - k > -- > 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, 2 months

1
0
0 0

Re: [TF-M] Security vulnerability notice - SVC handler fetches incorrect caller stack pointer under specific cases.

by Anton Komlev

Hi Kumar, All, Thanks for bringing this topic up. At the moment there is no plan for issuing the release v1.2.1 because of lack of policy for such hot fix releases. The release policy upgrade proposal shall be reviewed and agreed in the Steering Committee with the main questions: 1. What is the hot fix baseline? 2. What is the testing scope of the fix? 3. On which platform(s) the fix shall be tested? The policy is under discussion and the community input is welcome. Please share your thoughts on the topic. The release v1.3.0 is expected by end of March-beginning of April, which will include the fix. Thanks, Anton -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kumar Gala via TF-M Sent: Friday, March 5, 2021 5:36 PM To: Ken Liu <Ken.Liu(a)arm.com> Cc: nd <nd(a)arm.com>; tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] Security vulnerability notice - SVC handler fetches incorrect caller stack pointer under specific cases. > On Mar 5, 2021, at 9:28 AM, Ken Liu via TF-M <tf-m(a)lists.trustedfirmware.org> wrote: > > Hi Everyone, > > There is a new security vulnerability reported about the SVC handler fetches a wrong caller stack pointer under specific cases, which impacts the subsequent execution. > > Please find the security advisory specific to TF-M and patches that have been developed as per the TrustedFirmware.org security process[1] below : > > 1. TF-M Security advisory: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9005 > 2. Fix based on the latest master has been merged into TF-M repo. The patch also can be found in Gerrit:https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8575 and https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8576. > > Please let us know if you have any comments. > > BR > > /Ken Liu > > [1] https://developer.trustedfirmware.org/w/collaboration/security_center/repor… > -- > TF-M mailing list > TF-M(a)lists.trustedfirmware.org > https://lists.trustedfirmware.org/mailman/listinfo/tf-m Is there plans for a security release of TFM v1.2 with this fix? - k -- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m

4 years, 2 months

1
0
0 0

Re: [TF-M] Security vulnerability notice - SVC handler fetches incorrect caller stack pointer under specific cases.

by Kumar Gala

> On Mar 5, 2021, at 9:28 AM, Ken Liu via TF-M <tf-m(a)lists.trustedfirmware.org> wrote: > > Hi Everyone, > > There is a new security vulnerability reported about the SVC handler fetches a wrong caller stack pointer under specific cases, which impacts the subsequent execution. > > Please find the security advisory specific to TF-M and patches that have been developed as per the TrustedFirmware.org security process[1] below : > > 1. TF-M Security advisory: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9005 > 2. Fix based on the latest master has been merged into TF-M repo. The patch also can be found in Gerrit:https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8575 and https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8576. > > Please let us know if you have any comments. > > BR > > /Ken Liu > > [1] https://developer.trustedfirmware.org/w/collaboration/security_center/repor… > -- > TF-M mailing list > TF-M(a)lists.trustedfirmware.org > https://lists.trustedfirmware.org/mailman/listinfo/tf-m Is there plans for a security release of TFM v1.2 with this fix? - k

4 years, 2 months

1
0
0 0

Security vulnerability notice - SVC handler fetches incorrect caller stack pointer under specific cases.

by Ken Liu

Hi Everyone, There is a new security vulnerability reported about the SVC handler fetches a wrong caller stack pointer under specific cases, which impacts the subsequent execution. Please find the security advisory specific to TF-M and patches that have been developed as per the TrustedFirmware.org security process[1] below : 1. TF-M Security advisory: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/9005 2. Fix based on the latest master has been merged into TF-M repo. The patch also can be found in Gerrit: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8575 and https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8576. Please let us know if you have any comments. BR /Ken Liu [1] https://developer.trustedfirmware.org/w/collaboration/security_center/repor…

4 years, 2 months

1
0
0 0

Re: [TF-M] Technical Forum call - March 4

by Anton Komlev

The agenda for the forum tomorrow: 1. CMSIS Pack for TF-M v1.2 presentation 2. AOB Thanks, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Monday, March 1, 2021 11:58 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - March 4 Hi, The next Technical Forum is planned on Thursday, March 4, 07:00-08: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
0
0 0

Re: [TF-M] Review on Firmware Update service in TF-M

by Sherry Zhang

Hi, Add some technical details. The newly added Firmware Update service provides the functionality of updating firmware images. It provides a standard interface for updating firmware and it is designed as platform/bootloader independent. The nonsecure application can call this service to achieve the firmware update by integrating TF-M with, for example, OTA library in the nonsecure side. The implementation provides a shim layer between the bootloader and the firmware update partition. Other bootloaders besides MCUboot should be easily ported with this partition. Any comment is very welcomed! Regards, Sherry Zhang From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Sherry Zhang via TF-M Sent: Monday, January 18, 2021 1:52 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Review on Firmware Update service in TF-M Hi, I created the patchset of adding the Firmware Update service in TF-M feature branch. I would like to ask you to review this patchset if you are interested in it. Top of the patchset: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7883 Regards, Sherry Zhang

4 years, 2 months

1
1
0 0

Deprecation of the nRF5340 PDK platform

by Głąbek, Andrzej

Hello, I would like to propose the deprecation of the nRF5340 PDK platform (nordic_nrf/nrf5340pdk_nrf5340_cpuapp) and the removal of this platform after the v1.3.0 release. The nRF5340 PDK is a preview development kit with an early revision (Engineering A) of the nRF5340 SoC and it has been replaced by the nRF5340 DK (as indicated here: https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF5340-PDK), which is also supported by TF-M. As per the process, should you have any objections to this deprecation, please respond to this proposal within 4 weeks. Best regards, Andrzej Głąbek

4 years, 2 months

1
0
0 0

Re: [TF-M] Please update TFM_TEST_REPO_VERSION

by David Hu

Hi Thomas, Sorry for the trouble. Could you let me know whether this change brought some problems or it fixed something? Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M Sent: Friday, February 26, 2021 6:03 PM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Please update TFM_TEST_REPO_VERSION For some reason it seems that IAR is the only toolchain affected by: https://git.trustedfirmware.org/TF-M/tf-m-tests.git/commit/app/main_ns.c?id… Can we please update update the version to at least 4ae00fe? 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, 2 months

2
7
0 0

Technical Forum call - March 4

by Anton Komlev

Hi, The next Technical Forum is planned on Thursday, March 4, 07:00-08: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
0
0 0

Profile Large design document for review

by David Hu

Hi all, Can I ask for your comments on the TF-M Profile Large design document? TF-M Profile Large is one of TF-M Profiles. Profile Medium and Profile Small have been supported in TF-M. The document can be reviewed via https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8546/1/docs/…. Any comment is welcome! Best regards, Hu Ziji

4 years, 2 months

1
0
0 0

Please update TFM_TEST_REPO_VERSION

by Thomas Törnblom

For some reason it seems that IAR is the only toolchain affected by: https://git.trustedfirmware.org/TF-M/tf-m-tests.git/commit/app/main_ns.c?id… Can we please update update the version to at least 4ae00fe? 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, 2 months

1
0
0 0

Re: [TF-M] TF-M git repo normalization

by Kevin Peng

Hi all, Please be noted that both of the patches have been merged: TF-M: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8283 tf-m-tools: https://review.trustedfirmware.org/c/TF-M/tf-m-tools/+/8484 Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M Sent: Friday, February 19, 2021 1:47 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] TF-M git repo normalization Hi all, As I mentioned on yesterday's forum, I made a patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tools/+/8484> to fix the gitattributes issues in the tools repo. And the last call of review for the main repo normalization: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8283 Plan to have them both merged on next Tuesday. Best Regards, Kevin 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, February 9, 2021 10:03 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>; Anton Komlev <Anton.Komlev(a)arm.com<mailto:Anton.Komlev@arm.com>> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] TF-M git repo normalization Hi, I'd like to give a brief introduction on the git normalization before merging this patch. @Anton Komlev<mailto:Anton.Komlev@arm.com>, can I reserve 15-20 minutes of the next tech forum? Best Regards, Kevin 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: Monday, February 8, 2021 10:56 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] TF-M git repo normalization Hi all, Would like to merge the below patch *tomorrow* if there were no objections. Best Regards, Kevin 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: Friday, February 5, 2021 10:37 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] TF-M git repo normalization This patch was generated by git command automatically: $ git add --renormalize . It does change any contents of the files, except the line-endings in the repository. Your existing local working tree should not be affected when you pick up it or later when it's merged. The only file maintained manually is the .gitattributes Best Regards, Kevin 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: Friday, February 5, 2021 9:53 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 git repo normalization Hi all, Following the git normalization topic of the tech forum yesterday, I checked TF-M. It has not been enabled the git normalization feature. I've made a patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8283> to make this happen. Please check out or rebase your work upon this patch to see any issues. Your existing working tree should not be affected regarding the line-endings. What is the normalization? To be simple, different developers on different Host OS can have different line-endings in their local working tree and do not need to worry about interference with each other. Reference: https://git-scm.com/docs/gitattributes Best Regards, Kevin

4 years, 2 months

1
0
0 0

Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification

by Andrew Thoelke

I've had some further input on the interrupt management API. The use of patterns such as: bool irq_enabled = psa_irq_is_enabled(MY_IRQ); // [1] psa_irq_disable(MY_IRQ); // [2] // critical section if (irq_enabled) psa_irq_enable(MY_IRQ); must be discouraged as this is not guaranteed to be safe in the presence of interrupts that can change the status of MY_IRQ between the query [1] and the disable [2]. In general, it requires whole system analysis to determine that there are no such interrupts, and that this code is 100% reliable. However, providing the originally proposed API such as psa_irq_disable(), which returns the prior status, does not practically solve the problem. Instead, it just moves the race condition window into the implementation of that API. The only way in which such an API would be generally safe from the race condition is if the query+disable is atomic with respect to all other interrupts in the system - this either requires disabling interrupts entirely, or having an atomic read+disable capability in the interrupt controller. In systems which worry about such race conditions, disabling all interrupts can be unacceptable. The recommended approach is to avoid having software that depends on the state of the interrupt, but which does not implicitly know the state of the interrupt. In such a system, there is never a need to query the current interrupt state as on any line of code, the interrupt state is always known at design time. I am not sure if this suggests that we should: 1. Remove even the psa_irq_is_enabled() function, to prevent developers writing the above code, OR 2. We do not document the above pattern as a way to manage nested critical sections, OR 3. Retain the example above, but explain that this must be coupled with a software design that ensures the stability of the MY_IRQ status between [1] and [2]? Regards, Andrew From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: 22 February 2021 04:49 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification As the ‘psa_irq_status_t’ is a implementation-defined value, is it possible let the implementation-define the status encoding? Then the status and its checking code needs to be define by implementation, too: PSA_IRQ_STATUS_NOCHANGE PSA_IRQ_STATUS_DISABLE PSA_IRQ_STATUS_ENABLE PSA_IRQ_STAUTS_IS_ENABLED(status) This would make everything implementation-defined and this affects the headers, and one extra header: psa_impdef.h needs to be created by implementations. With this the ffm based applications just use preprocessors to get status and check them; the enable/disable can be out of ‘true’ and ‘false’ values. /Ken From: TF-M <mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M Sent: Tuesday, January 26, 2021 11:08 AM To: mailto:tf-m@lists.trustedfirmware.org Cc: nd <mailto:nd@arm.com> Subject: Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification Hi all, Per the off-line discussion with Andrew, I’d like to start a wider discussion on the interrupt APIs, specifically the Secure Partition API changes for interrupt control in chapter 6.3.3. There are the following APIs: • uint32_t psa_irq_is_enabled (psa_signal_t irq_signal); This API returns 0 if the interrupt is disabled and 1 if the interrupt is enabled. • psa_irq_status_t psa_irq_disable(psa_signal_t irq_signal); This API returns the status of the interrupt prior to this call with an implementation defined value Note the return type of the interrupt status is different. The first one is only to tell whether the interrupt is enabled (1) or not (0) – an equivalent to bool type. The second one could be any value to indicate an interrupt status. And that value is intended to be passed to psa_irq_restore to write to the interrupt control register directly. • void psa_irq_restore(psa_signal_t irq_signal, psa_irq_status_t saved_status); The typical usage: psa_irq_status irq2_state = psa_irq_disable(IRQ2_SIGNAL) ; // manipulate data shared with IRQ2 … psa_irq_restore(IRQ2_SIGNAL, irq2_state); This is a very efficient design as the 'saved status value' can be the exact value that needs to be written to an interrupt control register to restore the previous state. But TF-M seems to be unable to take that advantage. Because the most common interrupt controller is the NVIC provided by the core. The NVIC takes 1/0 to enable or disable the interrupt and one register for 32 interrupts. The underlying NVIC operation provided by CMSIS is NVIC_Enable/DisableIRQ. So the psa_irq_status_t in TF-M would simply 1 or 0 for a specific interrupt signal. Then the psa_irq_restore could be unnecessary if psa_irq_disable returns uint32_t just like psa_irq_is_enabled: uint32_t irq_status = psa_irq_disable(IRQ); ... // critical section if (irq_status) psa_irq_enable(IRQ); Any thoughts on the necessity of the psa_irq_restore API? The draft implementation of the current APIs for easy understanding: https://review.trustedfirmware.org/q/topic:%22psa_interrupt_api%22+(status:… Best Regards, Kevin -----Original Message----- From: TF-M <mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Andrew Thoelke via TF-M Sent: Friday, January 15, 2021 1:25 AM To: mailto:tf-m@lists.trustedfirmware.org; nd <mailto:nd@arm.com> Subject: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification Hi all, The PSA Firmware Framework for M 1.1 Extensions specification is now published on Arm Developer. This document introduces a set of updates and extensions to the Arm® Platform Security Architecture Firmware Framework (FF-M) specification, designed to build on the capabilities provided in version 1.0. This is an initial ALPHA release in order to enable wider review and feedback on the changes proposed to be included in the v1.1 specification. At this quality level, the changes and interfaces defined are not stable enough for product development. When the proposed extensions are sufficiently stable to be classed as Beta, they will be integrated into the FF-M version 1.1 specification. The 1.1 Extensions document can be downloaded from: https://developer.arm.com/documentation/aes0039/latest Both the 1.0 Specification and the 1.1 Extensions document are linked from the main PSA architecture page: https://developer.arm.com/architectures/security-architectures/platform-sec… Ken and I have presented a number of times at last year's Tech Forums on the proposals in the specification, most recently I provided a summary of the whole document on 10th December 2020. If you have any feedback, please provide it to mailto:arm.psa-feedback@arm.com, or discuss the proposals here in the TF-M mailing list. Regards, Andrew -- TF-M mailing list mailto:TF-M@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m

4 years, 2 months

1
0
0 0

Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification

by Ken Liu

As the ‘psa_irq_status_t’ is a implementation-defined value, is it possible let the implementation-define the status encoding? Then the status and its checking code needs to be define by implementation, too: PSA_IRQ_STATUS_NOCHANGE PSA_IRQ_STATUS_DISABLE PSA_IRQ_STATUS_ENABLE PSA_IRQ_STAUTS_IS_ENABLED(status) This would make everything implementation-defined and this affects the headers, and one extra header: psa_impdef.h needs to be created by implementations. With this the ffm based applications just use preprocessors to get status and check them; the enable/disable can be out of ‘true’ and ‘false’ values. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M Sent: Tuesday, January 26, 2021 11:08 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification Hi all, Per the off-line discussion with Andrew, I’d like to start a wider discussion on the interrupt APIs, specifically the Secure Partition API changes for interrupt control in chapter 6.3.3. There are the following APIs: * uint32_t psa_irq_is_enabled (psa_signal_t irq_signal); This API returns 0 if the interrupt is disabled and 1 if the interrupt is enabled. * psa_irq_status_t psa_irq_disable(psa_signal_t irq_signal); This API returns the status of the interrupt prior to this call with an implementation defined value Note the return type of the interrupt status is different. The first one is only to tell whether the interrupt is enabled (1) or not (0) – an equivalent to bool type. The second one could be any value to indicate an interrupt status. And that value is intended to be passed to psa_irq_restore to write to the interrupt control register directly. * void psa_irq_restore(psa_signal_t irq_signal, psa_irq_status_t saved_status); The typical usage: psa_irq_status irq2_state = psa_irq_disable(IRQ2_SIGNAL) ; // manipulate data shared with IRQ2 … psa_irq_restore(IRQ2_SIGNAL, irq2_state); This is a very efficient design as the 'saved status value' can be the exact value that needs to be written to an interrupt control register to restore the previous state. But TF-M seems to be unable to take that advantage. Because the most common interrupt controller is the NVIC provided by the core. The NVIC takes 1/0 to enable or disable the interrupt and one register for 32 interrupts. The underlying NVIC operation provided by CMSIS is NVIC_Enable/DisableIRQ. So the psa_irq_status_t in TF-M would simply 1 or 0 for a specific interrupt signal. Then the psa_irq_restore could be unnecessary if psa_irq_disable returns uint32_t just like psa_irq_is_enabled: uint32_t irq_status = psa_irq_disable(IRQ); ... // critical section if (irq_status) psa_irq_enable(IRQ); Any thoughts on the necessity of the psa_irq_restore API? The draft implementation of the current APIs for easy understanding: https://review.trustedfirmware.org/q/topic:%22psa_interrupt_api%22+(status:… Best Regards, Kevin -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Andrew Thoelke via TF-M Sent: Friday, January 15, 2021 1:25 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>; nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification Hi all, The PSA Firmware Framework for M 1.1 Extensions specification is now published on Arm Developer. This document introduces a set of updates and extensions to the Arm® Platform Security Architecture Firmware Framework (FF-M) specification, designed to build on the capabilities provided in version 1.0. This is an initial ALPHA release in order to enable wider review and feedback on the changes proposed to be included in the v1.1 specification. At this quality level, the changes and interfaces defined are not stable enough for product development. When the proposed extensions are sufficiently stable to be classed as Beta, they will be integrated into the FF-M version 1.1 specification. The 1.1 Extensions document can be downloaded from: https://developer.arm.com/documentation/aes0039/latest Both the 1.0 Specification and the 1.1 Extensions document are linked from the main PSA architecture page: https://developer.arm.com/architectures/security-architectures/platform-sec… Ken and I have presented a number of times at last year's Tech Forums on the proposals in the specification, most recently I provided a summary of the whole document on 10th December 2020. If you have any feedback, please provide it to arm.psa-feedback(a)arm.com<mailto:arm.psa-feedback@arm.com>, or discuss the proposals here in the TF-M mailing list. Regards, Andrew -- 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, 2 months

1
0
0 0

Re: [TF-M] Bug in GNU Arm Embedded toolchain (version 10-2020-q4-major) for TFM

by David Hu

Hi Kumar, Thanks a lot for reporting this issue. We had also reported it to the GNU toolchain team and were waiting them to make it public. Hi all, Now the details of this issue can be found in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99157. AFIAK, there is no workaround for this issue yet, without modifying the GNU toolchain source code. So I'd like to suggest to *not* use GNU Arm embedded toolchain version 10-2020-q4-major now. The earlier versions are not affected. Best regards, Hu Ziji -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kumar Gala via TF-M Sent: Friday, February 19, 2021 2:41 AM To: Adrian Shaw via TF-M <tf-m(a)lists.trustedfirmware.org> Subject: [TF-M] Bug in GNU Arm Embedded toolchain (version 10-2020-q4-major) for TFM Be aware that the binary release of the GNU Arm embedded toolchain version 10-2020-q4-major has a bug in it that impacts TFM support. I’ve reported this to the Arm team that works on the toolchain and provided a fix as well. The libgcc/cmse.o code isn’t being properly compiled and thus doesn’t work correctly. I’ve made the fix in the Zephyr SDK toolchain that provides an Arm embedded build: https://github.com/zephyrproject-rtos/sdk-ng Bug fix here: https://github.com/zephyrproject-rtos/sdk-ng/blob/master/patches/gcc/10.2.0… - k -- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m

4 years, 2 months

1
0
0 0

Re: [TF-M] TF-M git repo normalization

by Kevin Peng

Hi all, As I mentioned on yesterday's forum, I made a patch<https://review.trustedfirmware.org/c/TF-M/tf-m-tools/+/8484> to fix the gitattributes issues in the tools repo. And the last call of review for the main repo normalization: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8283 Plan to have them both merged on next Tuesday. Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M Sent: Tuesday, February 9, 2021 10:03 AM To: tf-m(a)lists.trustedfirmware.org; Anton Komlev <Anton.Komlev(a)arm.com> Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] TF-M git repo normalization Hi, I'd like to give a brief introduction on the git normalization before merging this patch. @Anton Komlev<mailto:Anton.Komlev@arm.com>, can I reserve 15-20 minutes of the next tech forum? Best Regards, Kevin 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: Monday, February 8, 2021 10:56 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] TF-M git repo normalization Hi all, Would like to merge the below patch *tomorrow* if there were no objections. Best Regards, Kevin 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: Friday, February 5, 2021 10:37 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] TF-M git repo normalization This patch was generated by git command automatically: $ git add --renormalize . It does change any contents of the files, except the line-endings in the repository. Your existing local working tree should not be affected when you pick up it or later when it's merged. The only file maintained manually is the .gitattributes Best Regards, Kevin 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: Friday, February 5, 2021 9:53 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 git repo normalization Hi all, Following the git normalization topic of the tech forum yesterday, I checked TF-M. It has not been enabled the git normalization feature. I've made a patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8283> to make this happen. Please check out or rebase your work upon this patch to see any issues. Your existing working tree should not be affected regarding the line-endings. What is the normalization? To be simple, different developers on different Host OS can have different line-endings in their local working tree and do not need to worry about interference with each other. Reference: https://git-scm.com/docs/gitattributes Best Regards, Kevin

4 years, 2 months

1
0
0 0

Bug in GNU Arm Embedded toolchain (version 10-2020-q4-major) for TFM

by Kumar Gala

Be aware that the binary release of the GNU Arm embedded toolchain version 10-2020-q4-major has a bug in it that impacts TFM support. I’ve reported this to the Arm team that works on the toolchain and provided a fix as well. The libgcc/cmse.o code isn’t being properly compiled and thus doesn’t work correctly. I’ve made the fix in the Zephyr SDK toolchain that provides an Arm embedded build: https://github.com/zephyrproject-rtos/sdk-ng Bug fix here: https://github.com/zephyrproject-rtos/sdk-ng/blob/master/patches/gcc/10.2.0… - k

4 years, 2 months

1
0
0 0

Re: [TF-M] Technical Forum call - February 18

by Anton Komlev

Agenda for the forum: 1. Git repository normalization. 2. Linaro SQUAD interface to visualise TF-M metrics 3. Any Other Business Regards, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: 10 February 2021 17:14 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - February 18 Hello, The next Technical Forum is planned on Thursday, Feb 18 at 15:00-16:00 UTC (US time zone). Please reply on this email with your proposals for agenda topics. Kevin Peng already proposed the one: 1. Git repository normalization. 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
0
0 0

Firmware Update API specification

by Adrian Shaw

Hi all, The PSA Firmware Update API specification is now published on Arm Developer. This document introduces a standard firmware interface for installing firmware updates. The document can be downloaded from https://developer.arm.com/documentation/ihi0093/0000/ This is an initial BETA release in order to enable wider review and feedback. We shall release new Beta versions to address feedback and comments. Sherry Zhang in TF-M has begun an implementation of this interface, which is a work in progress. If you have any feedback about the API specification, please provide it to arm.psa-feedback(a)arm.com, or discuss the proposal here in the TF-M mailing list. Regards, Adrian

4 years, 3 months

1
0
0 0

Technical Forum call - February 18

by Anton Komlev

Hello, The next Technical Forum is planned on Thursday, Feb 18 at 15:00-16:00 UTC (US time zone). Please reply on this email with your proposals for agenda topics. Kevin Peng already proposed the one: 1. Git repository normalization. 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

Re: [TF-M] PSA-ARCH-TEST with zephyr

by David Hu

Hi Antonio, May I suggest to raise the question to PSA Arch test repo https://github.com/ARM-software/psa-arch-tests/issues? Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Antonio Ken IANNILLO via TF-M Sent: Wednesday, February 10, 2021 8:43 PM To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] PSA-ARCH-TEST with zephyr I just add the verbosity (I initially tough was the cmake verbosity..) to the test libraries. This is the new output is somebody can help: https://pastebin.com/JNQ6TD0K In the specific the failure is at : ‘’’ TEST: 403 | DESCRIPTION: Insufficient space check Input id is 01030000 Input id is 01030000 Input id is 02020000 Input id is 02020000 [Info] Executing tests from non-secure [Info] Executing PS tests [Check 1] Overload storage space Setting 0x00000200 bytes for UID 5 Setting 0x00000200 bytes for UID 6 Setting 0x00000200 bytes for UID 7 Setting 0x00000200 bytes for UID 8 Setting 0x00000200 bytes for UID 9 Setting 0x00000200 bytes for UID 10 Setting 0x00000200 bytes for UID 11 Setting 0x00000200 bytes for UID 12 Setting 0x00000200 bytes for UID 13 UID 13 set failed due to insufficient space Remove all registered UIDs Removing UID 5 Removing UID 6 Removing UID 7 Removing UID 8 Removing UID 9 Removing UID 10 Removing UID 11 Removing UID 12 [Check 2] Overload storage again to verify all previous UID removed Setting 0x00000200 bytes for UID 5 Setting 0x00000200 bytes for UID 6 Setting 0x00000200 bytes for UID 7 Setting 0x00000200 bytes for UID 8 Setting 0x00000200 bytes for UID 9 [INF] Starting bootloader [INF] Swap type: none [INF] Swap type: none [INF] Bootloader chainload address offset: 0x80000 [INF] Jumping to the first image slot [Sec Thread] Secure image initializing! Booting TFM v1.2.0 [Crypto] MBEDTLS_TEST_NULL_ENTROPY is not suitable for production! *** Booting Zephyr OS build v2.5.0-rc1-209-g30634334a811 *** ‘’’ -- Antonio Ken Iannillo

4 years, 3 months

1
0
0 0

Re: [TF-M] PSA-ARCH-TEST with zephyr

by Antonio Ken IANNILLO

I just add the verbosity (I initially tough was the cmake verbosity..) to the test libraries. This is the new output is somebody can help: https://pastebin.com/JNQ6TD0K In the specific the failure is at : ‘’’ TEST: 403 | DESCRIPTION: Insufficient space check Input id is 01030000 Input id is 01030000 Input id is 02020000 Input id is 02020000 [Info] Executing tests from non-secure [Info] Executing PS tests [Check 1] Overload storage space Setting 0x00000200 bytes for UID 5 Setting 0x00000200 bytes for UID 6 Setting 0x00000200 bytes for UID 7 Setting 0x00000200 bytes for UID 8 Setting 0x00000200 bytes for UID 9 Setting 0x00000200 bytes for UID 10 Setting 0x00000200 bytes for UID 11 Setting 0x00000200 bytes for UID 12 Setting 0x00000200 bytes for UID 13 UID 13 set failed due to insufficient space Remove all registered UIDs Removing UID 5 Removing UID 6 Removing UID 7 Removing UID 8 Removing UID 9 Removing UID 10 Removing UID 11 Removing UID 12 [Check 2] Overload storage again to verify all previous UID removed Setting 0x00000200 bytes for UID 5 Setting 0x00000200 bytes for UID 6 Setting 0x00000200 bytes for UID 7 Setting 0x00000200 bytes for UID 8 Setting 0x00000200 bytes for UID 9 [INF] Starting bootloader [INF] Swap type: none [INF] Swap type: none [INF] Bootloader chainload address offset: 0x80000 [INF] Jumping to the first image slot [Sec Thread] Secure image initializing! Booting TFM v1.2.0 [Crypto] MBEDTLS_TEST_NULL_ENTROPY is not suitable for production! *** Booting Zephyr OS build v2.5.0-rc1-209-g30634334a811 *** ‘’’ -- Antonio Ken Iannillo

4 years, 3 months

1
0
0 0

Re: [TF-M] Boot data usage

by Ken Liu

Thanks for your inputs. I am seeking if boot data is used for a specific service only - if that is true, this boot data actually can be bound to the specific services, and other could request boot data related services by API. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Michel JAOUEN via TF-M Sent: Tuesday, February 9, 2021 8:53 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Boot data usage Hello, On STM platform, The boot data is also used to pass specific information to user different from attestation. For this support a specific Major is used. The actual implementation available in ST cube needs to be reworked so that each platform can customize it (Major value, and table checking access control on tfm core) Best regards From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Tamas Ban via TF-M Sent: mardi 9 février 2021 11:52 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] Boot data usage Hi Ken, AFAIK current implementation of FWU partition also relies on shared data received from bootloader. Tamas 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: 2021. február 9., kedd 10:47 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] Boot data usage Hi, Wondered if someone is expanding the boot data usage, as the default user is attestation only. Please provide your case if you are expanding boot data usage. Thanks! /Ken

4 years, 3 months

1
0
0 0

PSA-ARCH-TEST with zephyr

by Antonio Ken IANNILLO

Dear all, I’m running the PSA-ARCH-TEST (functional api tests) with Zephyr OS (for now emulated with QEMU 5). I followed the instructions to build the test libraries and linked successfully with an easy zephyr application (it just call the val_entry() function). When everything seems working smoothly with Storage tests, I realized that at a certain point the system fails and restarts. Repeatedly. Does any of you have already integrated these tests with zephyr? Did I forget something in the process? I tried also to understand the test that failed everything. It actually overload storage space (without any problem) and do it again (fails after 6 UIDS). Further, any of you know how to have a debug version of the psa-arch-test libraries? Or how to force them to print debug/test message as well… Terminal output is here: https://pastebin.com/ixmeB0kN Thank you very much for your help, -- Antonio Ken Iannillo Research Scientist – SEDAN group SnT – Interdisciplinary Centre for Security, Reliability and Trust UNIVERSITÉ DU LUXEMBOURG CAMPUS KIRCHBERG 29, avenue John F. Kennedy L-1855 Luxembourg Kirchberg T +352 46 66 44 9660 www.uni.lu/snt https://akiannillo.github.io/

4 years, 3 months

1
0
0 0

Re: [TF-M] Boot data usage

by Michel JAOUEN

Hello, On STM platform, The boot data is also used to pass specific information to user different from attestation. For this support a specific Major is used. The actual implementation available in ST cube needs to be reworked so that each platform can customize it (Major value, and table checking access control on tfm core) Best regards From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Tamas Ban via TF-M Sent: mardi 9 février 2021 11:52 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Boot data usage Hi Ken, AFAIK current implementation of FWU partition also relies on shared data received from bootloader. Tamas 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: 2021. február 9., kedd 10:47 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] Boot data usage Hi, Wondered if someone is expanding the boot data usage, as the default user is attestation only. Please provide your case if you are expanding boot data usage. Thanks! /Ken

4 years, 3 months

1
0
0 0

Re: [TF-M] Boot data usage

by Tamas Ban

Hi Ken, AFAIK current implementation of FWU partition also relies on shared data received from bootloader. Tamas From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: 2021. február 9., kedd 10:47 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Boot data usage Hi, Wondered if someone is expanding the boot data usage, as the default user is attestation only. Please provide your case if you are expanding boot data usage. Thanks! /Ken

4 years, 3 months

1
0
0 0

Boot data usage

by Ken Liu

Hi, Wondered if someone is expanding the boot data usage, as the default user is attestation only. Please provide your case if you are expanding boot data usage. Thanks! /Ken

4 years, 3 months

1
0
0 0

Re: [TF-M] TF-M git repo normalization

by Kevin Peng

Hi, I'd like to give a brief introduction on the git normalization before merging this patch. @Anton Komlev<mailto:Anton.Komlev@arm.com>, can I reserve 15-20 minutes of the next tech forum? Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M Sent: Monday, February 8, 2021 10:56 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] TF-M git repo normalization Hi all, Would like to merge the below patch *tomorrow* if there were no objections. Best Regards, Kevin 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: Friday, February 5, 2021 10:37 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] TF-M git repo normalization This patch was generated by git command automatically: $ git add --renormalize . It does change any contents of the files, except the line-endings in the repository. Your existing local working tree should not be affected when you pick up it or later when it's merged. The only file maintained manually is the .gitattributes Best Regards, Kevin 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: Friday, February 5, 2021 9:53 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 git repo normalization Hi all, Following the git normalization topic of the tech forum yesterday, I checked TF-M. It has not been enabled the git normalization feature. I've made a patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8283> to make this happen. Please check out or rebase your work upon this patch to see any issues. Your existing working tree should not be affected regarding the line-endings. What is the normalization? To be simple, different developers on different Host OS can have different line-endings in their local working tree and do not need to worry about interference with each other. Reference: https://git-scm.com/docs/gitattributes Best Regards, Kevin

4 years, 3 months

1
0
0 0

Re: [TF-M] TF-M git repo normalization

by Kevin Peng

Hi all, Would like to merge the below patch *tomorrow* if there were no objections. Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M Sent: Friday, February 5, 2021 10:37 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] TF-M git repo normalization This patch was generated by git command automatically: $ git add --renormalize . It does change any contents of the files, except the line-endings in the repository. Your existing local working tree should not be affected when you pick up it or later when it's merged. The only file maintained manually is the .gitattributes Best Regards, Kevin 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: Friday, February 5, 2021 9:53 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 git repo normalization Hi all, Following the git normalization topic of the tech forum yesterday, I checked TF-M. It has not been enabled the git normalization feature. I've made a patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8283> to make this happen. Please check out or rebase your work upon this patch to see any issues. Your existing working tree should not be affected regarding the line-endings. What is the normalization? To be simple, different developers on different Host OS can have different line-endings in their local working tree and do not need to worry about interference with each other. Reference: https://git-scm.com/docs/gitattributes Best Regards, Kevin

4 years, 3 months

1
0
0 0

[RFC] Platform data adjustment

by Ken Liu

Hi, I have created a couple of patches to change the way to assemble the partitions, and start with the platform data: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8288 The basic idea is we would avoid using pointer to link data between partitions, as mentioned in one of the past tech forum topics: https://www.trustedfirmware.org/docs/TF-M_partition_storage_arrangement.pdf Please help to review this patch, especially the platform owners, as this change modifies almost all platform sources. Also, I just use a direct 'find and replace' so some of the copyright years are not updated. Would update them in subsequent small patches. Thanks. /Ken

4 years, 3 months

1
0
0 0

Re: [TF-M] Ask for final review on physical attack mitigation design

by David Hu

Hi all, The design document is merged as planned. Thanks a lot for your review! Any further comment or suggestion is always comment. 😊 Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Monday, February 1, 2021 4:01 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Ask for final review on physical attack mitigation design Hi all, I’d like to merge the design document of physical attack mitigation in TF-M this week if no further comment. May I ask you to take another look at the following document patch? https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7476 Best regards, Hu Ziji

4 years, 3 months

1
0
0 0

Re: [TF-M] TF-M git repo normalization

by Kevin Peng

This patch was generated by git command automatically: $ git add --renormalize . It does change any contents of the files, except the line-endings in the repository. Your existing local working tree should not be affected when you pick up it or later when it's merged. The only file maintained manually is the .gitattributes Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M Sent: Friday, February 5, 2021 9:53 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] TF-M git repo normalization Hi all, Following the git normalization topic of the tech forum yesterday, I checked TF-M. It has not been enabled the git normalization feature. I've made a patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8283> to make this happen. Please check out or rebase your work upon this patch to see any issues. Your existing working tree should not be affected regarding the line-endings. What is the normalization? To be simple, different developers on different Host OS can have different line-endings in their local working tree and do not need to worry about interference with each other. Reference: https://git-scm.com/docs/gitattributes Best Regards, Kevin

4 years, 3 months

1
0
0 0

TF-M git repo normalization

by Kevin Peng

Hi all, Following the git normalization topic of the tech forum yesterday, I checked TF-M. It has not been enabled the git normalization feature. I've made a patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8283> to make this happen. Please check out or rebase your work upon this patch to see any issues. Your existing working tree should not be affected regarding the line-endings. What is the normalization? To be simple, different developers on different Host OS can have different line-endings in their local working tree and do not need to worry about interference with each other. Reference: https://git-scm.com/docs/gitattributes Best Regards, Kevin

4 years, 3 months

1
0
0 0

Re: [TF-M] Technical Forum call - February 4

by Anton Komlev

Hi, Looks like we have an empty agenda for tomorrow's forum. Let's use the time for the free discussion on any TF-M topic. Please raise questions / issues / improvements worth to be discussed within the community. See you, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: 28 January 2021 13:29 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - February 4 Hello, The next Technical Forum is planned on Thursday, Feb 4 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, 3 months

1
0
0 0

Re: [TF-M] NXP lpcxpresso55s69 appears broken

by Jamie Fox

Hi Thomas, Sorry about that. I have reproduced the issue on AN521 by copying over the lpcxpresso55s69 storage config. I'll investigate a fix on that platform, but will need you to verify it for me afterwards as I don't have that platform. Kind regards, Jamie From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M Sent: 03 February 2021 13:30 To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] NXP lpcxpresso55s69 appears broken Looks like this is the commit that breaks the nxp/lpcxpresso55s69 support: --- PS C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m> git bisect good 6a3946aa017fa4da3953a825991f8ce755114637 is the first bad commit commit 6a3946aa017fa4da3953a825991f8ce755114637 Author: Jamie Fox <jamie.fox(a)arm.com><mailto:jamie.fox@arm.com> Date: Mon Dec 7 21:50:31 2020 +0000 Platform: TF-M ITS and PS HAL ... --- Den 2021-02-03 kl. 13:54, skrev Thomas Törnblom via TF-M: I have just fixed an IAR linking issue for the nxp/lpcxpresso55s69, see https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8251 I tried using the current sources, but it seems that there is some issues causing the board to run into a hard fault when built with GNUARM. Not sure what commit caused the breakage. 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> -- 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, 3 months

2
1
0 0

Re: [TF-M] NXP lpcxpresso55s69 appears broken

by Kevin Townsend

Hi Jamie, I’ll be happy to test here as well if you add me to the change request. Best regards, Kevin On Wed, 3 Feb 2021 at 16:10, Jamie Fox via TF-M < tf-m(a)lists.trustedfirmware.org> wrote: > Hi Thomas, > > > > Sorry about that. I have reproduced the issue on AN521 by copying over the > lpcxpresso55s69 storage config. I’ll investigate a fix on that platform, > but will need you to verify it for me afterwards as I don’t have that > platform. > > > > Kind regards, > > Jamie > > > > *From:* TF-M <tf-m-bounces(a)lists.trustedfirmware.org> *On Behalf Of *Thomas > Törnblom via TF-M > *Sent:* 03 February 2021 13:30 > *To:* tf-m(a)lists.trustedfirmware.org > *Subject:* Re: [TF-M] NXP lpcxpresso55s69 appears broken > > > > Looks like this is the commit that breaks the nxp/lpcxpresso55s69 support: > --- > PS C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m> git bisect good > 6a3946aa017fa4da3953a825991f8ce755114637 is the first bad commit > commit 6a3946aa017fa4da3953a825991f8ce755114637 > Author: Jamie Fox <jamie.fox(a)arm.com> <jamie.fox(a)arm.com> > Date: Mon Dec 7 21:50:31 2020 +0000 > > Platform: TF-M ITS and PS HAL > ... > --- > > Den 2021-02-03 kl. 13:54, skrev Thomas Törnblom via TF-M: > > I have just fixed an IAR linking issue for the nxp/lpcxpresso55s69, see > https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8251 > > I tried using the current sources, but it seems that there is some issues > causing the board to run into a hard fault when built with GNUARM. > > Not sure what commit caused the breakage. > > 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 > Twitter: 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 Website: www.iar.com > Twitter: www.twitter.com/iarsystems > -- > TF-M mailing list > TF-M(a)lists.trustedfirmware.org > https://lists.trustedfirmware.org/mailman/listinfo/tf-m >

4 years, 3 months

1
0
0 0

Re: [TF-M] NXP lpcxpresso55s69 appears broken

by Thomas Törnblom

Looks like this is the commit that breaks the nxp/lpcxpresso55s69 support: --- PS C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m> git bisect good 6a3946aa017fa4da3953a825991f8ce755114637 is the first bad commit commit 6a3946aa017fa4da3953a825991f8ce755114637 Author: Jamie Fox <jamie.fox(a)arm.com> Date: Mon Dec 7 21:50:31 2020 +0000 Platform: TF-M ITS and PS HAL ... --- Den 2021-02-03 kl. 13:54, skrev Thomas Törnblom via TF-M: > I have just fixed an IAR linking issue for the nxp/lpcxpresso55s69, > see https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8251 > > I tried using the current sources, but it seems that there is some > issues causing the board to run into a hard fault when built with GNUARM. > > Not sure what commit caused the breakage. > > 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> > -- *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, 3 months

1
0
0 0

NXP lpcxpresso55s69 appears broken

by Thomas Törnblom

I have just fixed an IAR linking issue for the nxp/lpcxpresso55s69, see https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8251 I tried using the current sources, but it seems that there is some issues causing the board to run into a hard fault when built with GNUARM. Not sure what commit caused the breakage. 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, 3 months

1
0
0 0

Ask for final review on physical attack mitigation design

by David Hu

Hi all, I'd like to merge the design document of physical attack mitigation in TF-M this week if no further comment. May I ask you to take another look at the following document patch? https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7476 Best regards, Hu Ziji

4 years, 3 months

1
0
0 0

Re: [TF-M] Fatal error handler in secure FW - review request

by Kevin Townsend

Oyvind, Thanks for putting this together. Looks quite useful, and saves some monotony debugging. I put together a similar script but as a Python function for GDB: https://gist.github.com/microbuilder/1677a27e4566a28b36a79f954f1dede6 ... having this in C, however, means you don't need to have a Python-enabled version of GDB. Best regards, Kevin On Fri, 29 Jan 2021 at 11:33, Rønningstad, Øyvind via TF-M < tf-m(a)lists.trustedfirmware.org> wrote: > Hi everyone > > I wanted to make it easier to debug HardFaults/BusFaults/SecureFaults in > TFM, since I’ve gotten quite a few of them while adding the nrf platforms. > > I have created a proposal in > https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7891 and > would like to get some comments on the general idea. > > The proposal gathers a number of different values, especially the ones > that are harder to retrieve in a debugger, like the fault status registers > in SCB. > > The values are placed in memory so they can be inspected in a debugger, > and if built with -DTFM_SPM_LOG_LEVEL=TFM_SPM_LOG_LEVEL_DEBUG they are also > printed. > > Here is an example of the printout: > > FATAL ERROR: HardFault > > Here is some context for the exception: > > EXC_RETURN (LR): 0xFFFFFFBD > > Exception came from non-secure FW in thread mode. > > MSP(_S): 0x200007F8 > > PSP(_S): 0x20000F28 > > Exception frame at: 0x200176D8 > > R0: 0x0000003E > > R1: 0x00000001 > > R2: 0x00000001 > > R3: 0xFFFFFFFF > > R12: 0x00000000 > > LR: 0x00050623 > > PC: 0x00050626 > > CFSR: 0x00000000 > > BFAR: Not Valid > > MMFAR: Not Valid > > HFSR: 0x40000000 > > SFSR: 0x00000000 > > SFAR: Not Valid > > > > BR, Øyvind Rønningstad > -- > TF-M mailing list > TF-M(a)lists.trustedfirmware.org > https://lists.trustedfirmware.org/mailman/listinfo/tf-m >

4 years, 3 months

1
0
0 0

Fatal error handler in secure FW - review request

by Rønningstad, Øyvind

Hi everyone I wanted to make it easier to debug HardFaults/BusFaults/SecureFaults in TFM, since I've gotten quite a few of them while adding the nrf platforms. I have created a proposal in https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7891 and would like to get some comments on the general idea. The proposal gathers a number of different values, especially the ones that are harder to retrieve in a debugger, like the fault status registers in SCB. The values are placed in memory so they can be inspected in a debugger, and if built with -DTFM_SPM_LOG_LEVEL=TFM_SPM_LOG_LEVEL_DEBUG they are also printed. Here is an example of the printout: FATAL ERROR: HardFault Here is some context for the exception: EXC_RETURN (LR): 0xFFFFFFBD Exception came from non-secure FW in thread mode. MSP(_S): 0x200007F8 PSP(_S): 0x20000F28 Exception frame at: 0x200176D8 R0: 0x0000003E R1: 0x00000001 R2: 0x00000001 R3: 0xFFFFFFFF R12: 0x00000000 LR: 0x00050623 PC: 0x00050626 CFSR: 0x00000000 BFAR: Not Valid MMFAR: Not Valid HFSR: 0x40000000 SFSR: 0x00000000 SFAR: Not Valid BR, Øyvind Rønningstad

4 years, 3 months

1
0
0 0

Technical Forum call - February 4

by Anton Komlev

Hello, The next Technical Forum is planned on Thursday, Feb 4 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, 3 months

1
0
0 0

Re: [TF-M] Is Musca-A deprecated already?

by Gyorgy Szing

Hi, Just a humble suggestion: capability could be added to cmake to generate a build environment manifest. This could be a JSON or simple text file listing the location and version of each dependency (tool or software). The manifest file could simplify tracking down similar issues. /George From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M Sent: 28 January 2021 08:38 To: Sherry Zhang <Sherry.Zhang2(a)arm.com>; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Is Musca-A deprecated already? Thanks Sherry, Appears the current "cysecuretools" has a dependency on imgtool 1.7.0a1, which is likely where it came from. I did build for musca_a last week and I may have updated cysecuretools since then as I had issues with flashing the psoc64, and that must have installed 1.7.0a1. I installed 1.7.1, which caused a dependency error on cysecuretools 3.0.0. Works now! Cheers, Thomas Den 2021-01-28 kl. 03:50, skrev Sherry Zhang: Hi Thomas, The issue is caused by the imgtool package itself. The version 1.7.0a1 is a pre-release version. If you check the line 378 of image.py of the imgtool package of version 1.7.0a1, it does not check the 'None' before accessing the custom_tlvs.items: [cid:image003.jpg@01D6F552.951E90A0] In the version of 1.7.1, it has added the 'None' check at line 389 in image.py: [cid:image004.jpg@01D6F552.951E90A0] In TF-M build system, the custom_tlvs should be 'None'. To solve your issue, I suggest you use a release version of the imgtool package, such as 1.7.1, other than a pre-release one. Please let me know how it goes. Regards, Sherry Zhang From: Thomas Törnblom <thomas.tornblom(a)iar.com><mailto:thomas.tornblom@iar.com> Sent: Wednesday, January 27, 2021 4:46 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] Is Musca-A deprecated already? Hi Sherry, Looks like I have version 1.7.0a1. PS C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\cmake_build_iar> imgtool version 1.7.0a1 Cheers, Thomas Den 2021-01-27 kl. 09:22, skrev Sherry Zhang: Hi Thomas, Can you share the version of the imgtool package you used? The recommended version is >=1.6.0. We run the build command on Linux locally and it works well. An alternative option is to use the imgtool script from the upstream MCUBoot repo. To achieve that you can copy the folder ./build_dir/lib/ext/mcuboot-src/scripts/imgtool to bl2/ext/mcuboot/scripts/wrapper/. Regards, Sherry Zhang 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: Wednesday, January 27, 2021 12:28 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] Is Musca-A deprecated already? I'm working on some IAR brokenness for the cypress/psoc64 and for comparison I'm attempting to build for my favorite board, the musca_a, but it seems builds fails now. I think it was working last week, but today I'm unable to build with any of the toolchains. I get the following errors frmo all of them. Here's a gcc build: --- [629/629] Generating tfm_s_ns_signed.bin FAILED: bl2/ext/mcuboot/tfm_s_ns_signed.bin cmd.exe /C "cd /D C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\cmake_build_armclang\bl2\ext\mcuboot && C:\Users\thomasto\AppData\Local\Programs\Python\Python39\python.exe C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/bl2/ext/mcuboot/scripts/wrapper/wrapper.py -v 1.2.0 --layout C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bl2/ext/mcuboot/CMakeFiles/signing_layout_s.dir/./signing_layout_s_ns.o -k C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/bl2/ext/mcuboot/root-RSA-3072.pem --public-key-format full --align 1 --pad --pad-header -H 0x400 -s auto -d "(0, 0.0.0+0)" -d "(1, 0.0.0+0)" tfm_s_ns.bin C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bl2/ext/mcuboot/tfm_s_ns_signed.bin && "C:\Program Files\CMake\bin\cmake.exe" -E copy C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bl2/ext/mcuboot/tfm_s_ns_signed.bin C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bin" Traceback (most recent call last): File "C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\bl2\ext\mcuboot\scripts\wrapper\wrapper.py", line 126, in <module> wrap() File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 829, in __call__ return self.main(*args, **kwargs) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 782, in main rv = self.invoke(ctx) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 1066, in invoke return ctx.invoke(self.callback, **ctx.params) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 610, in invoke return callback(*args, **kwargs) File "C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\bl2\ext\mcuboot\scripts\wrapper\wrapper.py", line 121, in wrap img.create(key, public_key_format, enckey, dependencies, boot_record) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\imgtool\image.py", line 378, in create for tag, value in custom_tlvs.items(): AttributeError: 'NoneType' object has no attribute 'items' ninja: build stopped: subcommand failed. --- cmake line: cmake -GNinja -S .. -B . -DTFM_PLATFORM=musca_a "-DTFM_TOOLCHAIN_FILE=..\toolchain_GNUARM.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=Debug -DMCUBOOT_LOG_LEVEL=DEBUG -DTFM_PSA_API=ON I've tested building for several of the other targets, which seems to work, but I don't have any of these here. Ideas? 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> -- 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, 3 months

1
0
0 0

Re: [TF-M] Is Musca-A deprecated already?

by Sherry Zhang

Hi Thomas, Can you share the version of the imgtool package you used? The recommended version is >=1.6.0. We run the build command on Linux locally and it works well. An alternative option is to use the imgtool script from the upstream MCUBoot repo. To achieve that you can copy the folder ./build_dir/lib/ext/mcuboot-src/scripts/imgtool to bl2/ext/mcuboot/scripts/wrapper/. Regards, Sherry Zhang From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M Sent: Wednesday, January 27, 2021 12:28 AM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Is Musca-A deprecated already? I'm working on some IAR brokenness for the cypress/psoc64 and for comparison I'm attempting to build for my favorite board, the musca_a, but it seems builds fails now. I think it was working last week, but today I'm unable to build with any of the toolchains. I get the following errors frmo all of them. Here's a gcc build: --- [629/629] Generating tfm_s_ns_signed.bin FAILED: bl2/ext/mcuboot/tfm_s_ns_signed.bin cmd.exe /C "cd /D C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\cmake_build_armclang\bl2\ext\mcuboot && C:\Users\thomasto\AppData\Local\Programs\Python\Python39\python.exe C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/bl2/ext/mcuboot/scripts/wrapper/wrapper.py -v 1.2.0 --layout C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bl2/ext/mcuboot/CMakeFiles/signing_layout_s.dir/./signing_layout_s_ns.o -k C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/bl2/ext/mcuboot/root-RSA-3072.pem --public-key-format full --align 1 --pad --pad-header -H 0x400 -s auto -d "(0, 0.0.0+0)" -d "(1, 0.0.0+0)" tfm_s_ns.bin C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bl2/ext/mcuboot/tfm_s_ns_signed.bin && "C:\Program Files\CMake\bin\cmake.exe" -E copy C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bl2/ext/mcuboot/tfm_s_ns_signed.bin C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bin" Traceback (most recent call last): File "C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\bl2\ext\mcuboot\scripts\wrapper\wrapper.py", line 126, in <module> wrap() File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 829, in __call__ return self.main(*args, **kwargs) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 782, in main rv = self.invoke(ctx) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 1066, in invoke return ctx.invoke(self.callback, **ctx.params) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 610, in invoke return callback(*args, **kwargs) File "C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\bl2\ext\mcuboot\scripts\wrapper\wrapper.py", line 121, in wrap img.create(key, public_key_format, enckey, dependencies, boot_record) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\imgtool\image.py", line 378, in create for tag, value in custom_tlvs.items(): AttributeError: 'NoneType' object has no attribute 'items' ninja: build stopped: subcommand failed. --- cmake line: cmake -GNinja -S .. -B . -DTFM_PLATFORM=musca_a "-DTFM_TOOLCHAIN_FILE=..\toolchain_GNUARM.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=Debug -DMCUBOOT_LOG_LEVEL=DEBUG -DTFM_PSA_API=ON I've tested building for several of the other targets, which seems to work, but I don't have any of these here. Ideas? 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, 3 months

2
3
0 0

Re: [TF-M] Is Musca-A deprecated already?

by Minos Galanakis

Hi Thomas, I can also confirm that the build works on a system with the linked environment<https://review.trustedfirmware.org/plugins/gitiles/ci/dockerfiles/+/refs/he…> setup. I have tested your command, as well as the two methods listed in the documentation and all appear to be working. Given this opportunity I would like to share that in accordance to the TrustedFirmware.org project maintenance proposal<https://developer.trustedfirmware.org/w/collaboration/project-maintenance-p…>, the project should not be removing a platform in without fair notice. In TF-M we try to do so in three steps between releases: * Adding a deprecation warning patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6516> which will notify the users during compilation and runtime. * Marking is as soon to be deprecated in documentation. * Removing the files on or after the marked release. Back to your problem, I would also confirm that there are no environment variables setting a pre-downloaded repository for TF-M tests. Please let us know how it goes. Minos ________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Thomas Törnblom via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 27 January 2021 08:46 To: Sherry Zhang <Sherry.Zhang2(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] Is Musca-A deprecated already? Hi Sherry, Looks like I have version 1.7.0a1. PS C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\cmake_build_iar> imgtool version 1.7.0a1 Cheers, Thomas Den 2021-01-27 kl. 09:22, skrev Sherry Zhang: Hi Thomas, Can you share the version of the imgtool package you used? The recommended version is >=1.6.0. We run the build command on Linux locally and it works well. An alternative option is to use the imgtool script from the upstream MCUBoot repo. To achieve that you can copy the folder ./build_dir/lib/ext/mcuboot-src/scripts/imgtool to bl2/ext/mcuboot/scripts/wrapper/. Regards, Sherry Zhang 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: Wednesday, January 27, 2021 12:28 AM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] Is Musca-A deprecated already? I'm working on some IAR brokenness for the cypress/psoc64 and for comparison I'm attempting to build for my favorite board, the musca_a, but it seems builds fails now. I think it was working last week, but today I'm unable to build with any of the toolchains. I get the following errors frmo all of them. Here's a gcc build: --- [629/629] Generating tfm_s_ns_signed.bin FAILED: bl2/ext/mcuboot/tfm_s_ns_signed.bin cmd.exe /C "cd /D C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\cmake_build_armclang\bl2\ext\mcuboot && C:\Users\thomasto\AppData\Local\Programs\Python\Python39\python.exe C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/bl2/ext/mcuboot/scripts/wrapper/wrapper.py -v 1.2.0 --layout C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bl2/ext/mcuboot/CMakeFiles/signing_layout_s.dir/./signing_layout_s_ns.o -k C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/bl2/ext/mcuboot/root-RSA-3072.pem --public-key-format full --align 1 --pad --pad-header -H 0x400 -s auto -d "(0, 0.0.0+0)" -d "(1, 0.0.0+0)" tfm_s_ns.bin C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bl2/ext/mcuboot/tfm_s_ns_signed.bin && "C:\Program Files\CMake\bin\cmake.exe" -E copy C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bl2/ext/mcuboot/tfm_s_ns_signed.bin C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bin" Traceback (most recent call last): File "C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\bl2\ext\mcuboot\scripts\wrapper\wrapper.py", line 126, in <module> wrap() File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 829, in __call__ return self.main(*args, **kwargs) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 782, in main rv = self.invoke(ctx) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 1066, in invoke return ctx.invoke(self.callback, **ctx.params) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 610, in invoke return callback(*args, **kwargs) File "C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\bl2\ext\mcuboot\scripts\wrapper\wrapper.py", line 121, in wrap img.create(key, public_key_format, enckey, dependencies, boot_record) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\imgtool\image.py", line 378, in create for tag, value in custom_tlvs.items(): AttributeError: 'NoneType' object has no attribute 'items' ninja: build stopped: subcommand failed. --- cmake line: cmake -GNinja -S .. -B . -DTFM_PLATFORM=musca_a "-DTFM_TOOLCHAIN_FILE=..\toolchain_GNUARM.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=Debug -DMCUBOOT_LOG_LEVEL=DEBUG -DTFM_PSA_API=ON I've tested building for several of the other targets, which seems to work, but I don't have any of these here. Ideas? 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> -- 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, 3 months

1
0
0 0

Is Musca-A deprecated already?

by Thomas Törnblom

I'm working on some IAR brokenness for the cypress/psoc64 and for comparison I'm attempting to build for my favorite board, the musca_a, but it seems builds fails now. I think it was working last week, but today I'm unable to build with any of the toolchains. I get the following errors frmo all of them. Here's a gcc build: --- [629/629] Generating tfm_s_ns_signed.bin FAILED: bl2/ext/mcuboot/tfm_s_ns_signed.bin cmd.exe /C "cd /D C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\cmake_build_armclang\bl2\ext\mcuboot && C:\Users\thomasto\AppData\Local\Programs\Python\Python39\python.exe C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/bl2/ext/mcuboot/scripts/wrapper/wrapper.py -v 1.2.0 --layout C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bl2/ext/mcuboot/CMakeFiles/signing_layout_s.dir/./signing_layout_s_ns.o -k C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/bl2/ext/mcuboot/root-RSA-3072.pem --public-key-format full --align 1 --pad --pad-header -H 0x400 -s auto -d "(0, 0.0.0+0)" -d "(1, 0.0.0+0)" tfm_s_ns.bin C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bl2/ext/mcuboot/tfm_s_ns_signed.bin && "C:\Program Files\CMake\bin\cmake.exe" -E copy C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bl2/ext/mcuboot/tfm_s_ns_signed.bin C:/Users/thomasto/Projects/tf-m4/trusted-firmware-m/cmake_build_armclang/bin" Traceback (most recent call last): File "C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\bl2\ext\mcuboot\scripts\wrapper\wrapper.py", line 126, in <module> wrap() File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 829, in __call__ return self.main(*args, **kwargs) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 782, in main rv = self.invoke(ctx) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 1066, in invoke return ctx.invoke(self.callback, **ctx.params) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\click\core.py", line 610, in invoke return callback(*args, **kwargs) File "C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m\bl2\ext\mcuboot\scripts\wrapper\wrapper.py", line 121, in wrap img.create(key, public_key_format, enckey, dependencies, boot_record) File "C:\Users\thomasto\AppData\Local\Programs\Python\Python39\lib\site-packages\imgtool\image.py", line 378, in create for tag, value in custom_tlvs.items(): AttributeError: 'NoneType' object has no attribute 'items' ninja: build stopped: subcommand failed. --- cmake line: cmake -GNinja -S .. -B . -DTFM_PLATFORM=musca_a "-DTFM_TOOLCHAIN_FILE=..\toolchain_GNUARM.cmake" -DTEST_NS=ON -DTEST_S=ON -DCMAKE_BUILD_TYPE=Debug -DMCUBOOT_LOG_LEVEL=DEBUG -DTFM_PSA_API=ON I've tested building for several of the other targets, which seems to work, but I don't have any of these here. Ideas? 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, 3 months

1
0
0 0

Re: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification

by Kevin Peng

Hi all, Per the off-line discussion with Andrew, I’d like to start a wider discussion on the interrupt APIs, specifically the Secure Partition API changes for interrupt control in chapter 6.3.3. There are the following APIs: * uint32_t psa_irq_is_enabled (psa_signal_t irq_signal); This API returns 0 if the interrupt is disabled and 1 if the interrupt is enabled. * psa_irq_status_t psa_irq_disable(psa_signal_t irq_signal); This API returns the status of the interrupt prior to this call with an implementation defined value Note the return type of the interrupt status is different. The first one is only to tell whether the interrupt is enabled (1) or not (0) – an equivalent to bool type. The second one could be any value to indicate an interrupt status. And that value is intended to be passed to psa_irq_restore to write to the interrupt control register directly. * void psa_irq_restore(psa_signal_t irq_signal, psa_irq_status_t saved_status); The typical usage: psa_irq_status irq2_state = psa_irq_disable(IRQ2_SIGNAL) ; // manipulate data shared with IRQ2 … psa_irq_restore(IRQ2_SIGNAL, irq2_state); This is a very efficient design as the 'saved status value' can be the exact value that needs to be written to an interrupt control register to restore the previous state. But TF-M seems to be unable to take that advantage. Because the most common interrupt controller is the NVIC provided by the core. The NVIC takes 1/0 to enable or disable the interrupt and one register for 32 interrupts. The underlying NVIC operation provided by CMSIS is NVIC_Enable/DisableIRQ. So the psa_irq_status_t in TF-M would simply 1 or 0 for a specific interrupt signal. Then the psa_irq_restore could be unnecessary if psa_irq_disable returns uint32_t just like psa_irq_is_enabled: uint32_t irq_status = psa_irq_disable(IRQ); ... // critical section if (irq_status) psa_irq_enable(IRQ); Any thoughts on the necessity of the psa_irq_restore API? The draft implementation of the current APIs for easy understanding: https://review.trustedfirmware.org/q/topic:%22psa_interrupt_api%22+(status:… Best Regards, Kevin -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Andrew Thoelke via TF-M Sent: Friday, January 15, 2021 1:25 AM To: tf-m(a)lists.trustedfirmware.org; nd <nd(a)arm.com> Subject: [TF-M] Arm Firmware Framework for M 1.1 Extensions Alpha specification Hi all, The PSA Firmware Framework for M 1.1 Extensions specification is now published on Arm Developer. This document introduces a set of updates and extensions to the Arm® Platform Security Architecture Firmware Framework (FF-M) specification, designed to build on the capabilities provided in version 1.0. This is an initial ALPHA release in order to enable wider review and feedback on the changes proposed to be included in the v1.1 specification. At this quality level, the changes and interfaces defined are not stable enough for product development. When the proposed extensions are sufficiently stable to be classed as Beta, they will be integrated into the FF-M version 1.1 specification. The 1.1 Extensions document can be downloaded from: https://developer.arm.com/documentation/aes0039/latest Both the 1.0 Specification and the 1.1 Extensions document are linked from the main PSA architecture page: https://developer.arm.com/architectures/security-architectures/platform-sec… Ken and I have presented a number of times at last year's Tech Forums on the proposals in the specification, most recently I provided a summary of the whole document on 10th December 2020. If you have any feedback, please provide it to arm.psa-feedback(a)arm.com<mailto:arm.psa-feedback@arm.com>, or discuss the proposals here in the TF-M mailing list. Regards, Andrew -- 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, 3 months

1
0
0 0

[RFC] Doxygen usage

by Ken Liu

Hi, As mentioned in Tech Forum, call for feedbacks for doxygen usage: - Anyone is checking doxygen documents? - Which API are you checking with doxygen documents? The service APIs, or even some internal static API for SPM? - When you are reading code, will you check the docs or you just open them in editors and then read it? The background is we put many efforts on docs, it costs effort to maintain the doxygen format comments for all sources even the concept is covered in the docs folder, we are trying to find a balance to help mitigate the effort spent on internal logics (such as those static APIs inside SPM fewer people would update). For the interfaces API, doxygen would be always there so user can find them easily. Thanks /Ken

4 years, 3 months

1
0
0 0

Review request on design proposal of adding secure Flash support in TF-M

by Edward Yang

Hi everyone, The design proposal of adding secure Flash support in TF-M has been updated, I would like to ask for a review, any comments and suggestions will be appreciated. Link of the design proposal: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8033 Best Regards, 杨雪松 Edward Yang 旺宏微电子（苏州）有限公司 Macronix Microelectronics(Suzhou) Co., Ltd. 地址：中国苏州工业园区苏虹西路55号 No.55，Su Hong Xi Road，Suzhou Industrail Park，Suzhou 215021 P.R.China TEL: 86-512-62580888 EXT: 3102 FAX: 86-512-62585399 ZIP: 215021 E-mail: edwardyang(a)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 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. =====================================================================

4 years, 3 months

1
0
0 0

Re: [TF-M] Technical Forum call - January 21

by Anton Komlev

Hello, The agenda for the forum: 1. Proposal for changes to the OpenCI job coverage 2. Proposal to reduce Doxygen coverage to the interfaces only 3. Ongoing open issues: * Musca-A platform deprecation * Arm Firmware Framework for M 1.1 Extensions Alpha specification Regards,, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: 20 January 2021 14:18 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Technical Forum call - January 21 Hi Anton, I would like to raise a discussion about doxygen usage. I think it is acceptable to apply doxygen usage in interfaces only if we want to keep alignment with CMSIS code since it applied doxygen result as reference manual; but for other logics, the doxygen is almost not used. Wondered how many users would generate reference manual from doxygen; or they just open an editor then start reading code from sources. Thanks. /Ken ________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> on behalf of Karl Zhang via TF-M <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Sent: Wednesday, January 20, 2021 7:54 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>>; Anton Komlev <Anton.Komlev(a)arm.com<mailto:Anton.Komlev@arm.com>> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] Technical Forum call - January 21 Hi Anton, I would like to propose some changes to the openCI job coverage, it may take ~20 mins. BR Karl ________________________________ 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: Thursday, January 14, 2021 4:19 AM 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 - January 21 Hello, The next Technical Forum is planned on Thursday, January 21 at 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, 3 months

1
0
0 0

Re: [TF-M] Technical Forum call - January 21

by Ken Liu

Hi Anton, I would like to raise a discussion about doxygen usage. I think it is acceptable to apply doxygen usage in interfaces only if we want to keep alignment with CMSIS code since it applied doxygen result as reference manual; but for other logics, the doxygen is almost not used. Wondered how many users would generate reference manual from doxygen; or they just open an editor then start reading code from sources. Thanks. /Ken ________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Karl Zhang via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: Wednesday, January 20, 2021 7:54 PM To: tf-m(a)lists.trustedfirmware.org <tf-m(a)lists.trustedfirmware.org>; Anton Komlev <Anton.Komlev(a)arm.com> Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] Technical Forum call - January 21 Hi Anton, I would like to propose some changes to the openCI job coverage, it may take ~20 mins. BR Karl ________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Anton Komlev via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: Thursday, January 14, 2021 4:19 AM To: tf-m(a)lists.trustedfirmware.org <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - January 21 Hello, The next Technical Forum is planned on Thursday, January 21 at 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, 3 months

1
0
0 0

Re: [TF-M] Technical Forum call - January 21

by Karl Zhang

Hi Anton, I would like to propose some changes to the openCI job coverage, it may take ~20 mins. BR Karl ________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Anton Komlev via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: Thursday, January 14, 2021 4:19 AM To: tf-m(a)lists.trustedfirmware.org <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - January 21 Hello, The next Technical Forum is planned on Thursday, January 21 at 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, 3 months

1
0
0 0

Couple of adjustment patches coming

by Ken Liu

Hi, For implementing coming features and optimization, there would be couples of adjustment patches coming, this is the first one (the number looks good): https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8000 The idea is to get these patches to come in first so that we can have more time before the next release to fix spotted issues. Please help to review the patches and provide different thinking if you have. Thanks. /Ken

4 years, 3 months

1
0
0 0

Re: [TF-M] [RFC] Static linker scripts for level 1 and 2 isolation

by Ken Liu

Hi, I have merged these patches so they took place now. For lv1 and lv2 users, they don’t need the linker script template any more. The next step is syncing lv3 with lv1/lv2. This change may miss verification on some platforms, please report the build & run issue if you have, thanks. BR /Ken -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: Thursday, January 14, 2021 9:49 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] [RFC] Static linker scripts for level 1 and 2 isolation I think the link needs to be updated into: https://review.trustedfirmware.org/q/topic:%22static_linker_scripts%22+(sta… This would make the components arrangement more simpler than using a templating. But for level 3 we still have to using a templating as now there is no 'foreach' like functionalities supported in the ld/sct/icf. /Ken -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Raef Coles via TF-M Sent: Wednesday, January 13, 2021 11:44 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [RFC] Static linker scripts for level 1 and 2 isolation Hi everyone I'd like to request comments on an upcoming change to the linker scripts. Because of some recent changes to the memory layout for level 1 and level 2 isolation, it's now possible to avoid the generation step via tfm_parse_manifest_lists.py for those linker files. This means that the files are static and have been committed into the source tree (as they used to be). We anticipate this change will make integrating TF-M into non-cmake buildsystems easier, as it will avoid one of the places where files need to be generated at build-time. The reason this is an RFC is that it is a potentially breaking change, but only for integrators _not_ using the cmake buildsystem. Currently the linker uses a large variety of pattern matches to organise the partition symbols, with these patterns being defined in the tfm_manifest_list.yaml. After this change, the linker will only look for two patterns: `*app_rot_partition*` and `*psa_rot_partition*` With the intention that the secure partitions will be compiled into a static library, where the filename is (for example) `libtfm_psa_rot_partition_crypto.a`. The cmake buildsystem will be updated to generate these filenames, but other integrators will need to adjust their compilation steps else the linking will fail. Any comments or concerns would be appreciated. Patches can be found at: https://review.trustedfirmware.org/q/topic:%23static_linker_scripts%22 Raef -- 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, 3 months

1
0
0 0

Re: [TF-M] Musca-A platform deprecation announcement

by Thomas Törnblom

Hi Anton, The Musca-A is my first choice for testing new things with TF-M, mainly because that’s the simplest Arm board I have access to. What alternative do you recommend? Cheers, Thomas 18 jan. 2021 kl. 18:01 skrev Anton Komlev via TF-M <tf-m(a)lists.trustedfirmware.org>: Hello, I would like to propose the deprecation of Musca-A platform. With whole respect to the first HW platform supported TF-M, it became quite old and difficult to access. The current plan is to remove Musca-A from support and TF-M master code in the next release v1.3.0. Please reply to this mail until Feb 16 (in 4 weeks) having any objection for deprecation. Thanks and Best regards Anton Komlev -- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m

4 years, 3 months

2
1
0 0

Musca-A platform deprecation announcement

by Anton Komlev

Hello, I would like to propose the deprecation of Musca-A platform. With whole respect to the first HW platform supported TF-M, it became quite old and difficult to access. The current plan is to remove Musca-A from support and TF-M master code in the next release v1.3.0. Please reply to this mail until Feb 16 (in 4 weeks) having any objection for deprecation. Thanks and Best regards Anton Komlev

4 years, 3 months

1
0
0 0

Review on Firmware Update service in TF-M

by Sherry Zhang

Hi, I created the patchset of adding the Firmware Update service in TF-M feature branch. I would like to ask you to review this patchset if you are interested in it. Top of the patchset: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7883 Regards, Sherry Zhang

4 years, 3 months

1
0
0 0

Arm Firmware Framework for M 1.1 Extensions Alpha specification

by Andrew Thoelke

Hi all, The PSA Firmware Framework for M 1.1 Extensions specification is now published on Arm Developer. This document introduces a set of updates and extensions to the Arm® Platform Security Architecture Firmware Framework (FF-M) specification, designed to build on the capabilities provided in version 1.0. This is an initial ALPHA release in order to enable wider review and feedback on the changes proposed to be included in the v1.1 specification. At this quality level, the changes and interfaces defined are not stable enough for product development. When the proposed extensions are sufficiently stable to be classed as Beta, they will be integrated into the FF-M version 1.1 specification. The 1.1 Extensions document can be downloaded from: https://developer.arm.com/documentation/aes0039/latest Both the 1.0 Specification and the 1.1 Extensions document are linked from the main PSA architecture page: https://developer.arm.com/architectures/security-architectures/platform-sec… Ken and I have presented a number of times at last year's Tech Forums on the proposals in the specification, most recently I provided a summary of the whole document on 10th December 2020. If you have any feedback, please provide it to arm.psa-feedback(a)arm.com, or discuss the proposals here in the TF-M mailing list. Regards, Andrew

4 years, 4 months

1
0
0 0

Re: [TF-M] Technical Forum call - Jan 7

by Kevin Peng

I'd like give a proposal on how to manage the version of tf-m-tests repo in auto-download mode of the build system. Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Monday, January 4, 2021 5:33 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 - Jan 7 Hi Anton, I'd like to give a brief introduction to TF-M generic threat model. Best regards, Hu Ziji 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: Monday, January 4, 2021 5:30 PM To: 'tf-m(a)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 - Jan 7 Hello, The next Technical Forum is planned on Thursday, January 7 at 6:00-07: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

2
3
0 0

Re: [TF-M] [RFC] Static linker scripts for level 1 and 2 isolation

by Ken Liu

I think the link needs to be updated into: https://review.trustedfirmware.org/q/topic:%22static_linker_scripts%22+(sta… This would make the components arrangement more simpler than using a templating. But for level 3 we still have to using a templating as now there is no 'foreach' like functionalities supported in the ld/sct/icf. /Ken -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Raef Coles via TF-M Sent: Wednesday, January 13, 2021 11:44 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [RFC] Static linker scripts for level 1 and 2 isolation Hi everyone I'd like to request comments on an upcoming change to the linker scripts. Because of some recent changes to the memory layout for level 1 and level 2 isolation, it's now possible to avoid the generation step via tfm_parse_manifest_lists.py for those linker files. This means that the files are static and have been committed into the source tree (as they used to be). We anticipate this change will make integrating TF-M into non-cmake buildsystems easier, as it will avoid one of the places where files need to be generated at build-time. The reason this is an RFC is that it is a potentially breaking change, but only for integrators _not_ using the cmake buildsystem. Currently the linker uses a large variety of pattern matches to organise the partition symbols, with these patterns being defined in the tfm_manifest_list.yaml. After this change, the linker will only look for two patterns: `*app_rot_partition*` and `*psa_rot_partition*` With the intention that the secure partitions will be compiled into a static library, where the filename is (for example) `libtfm_psa_rot_partition_crypto.a`. The cmake buildsystem will be updated to generate these filenames, but other integrators will need to adjust their compilation steps else the linking will fail. Any comments or concerns would be appreciated. Patches can be found at: https://review.trustedfirmware.org/q/topic:%23static_linker_scripts%22 Raef -- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m

4 years, 4 months

1
0
0 0

Technical Forum call - January 21

by Anton Komlev

Hello, The next Technical Forum is planned on Thursday, January 21 at 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, 4 months

1
0
0 0

[RFC] Static linker scripts for level 1 and 2 isolation

by Raef Coles

Hi everyone I'd like to request comments on an upcoming change to the linker scripts. Because of some recent changes to the memory layout for level 1 and level 2 isolation, it's now possible to avoid the generation step via tfm_parse_manifest_lists.py for those linker files. This means that the files are static and have been committed into the source tree (as they used to be). We anticipate this change will make integrating TF-M into non-cmake buildsystems easier, as it will avoid one of the places where files need to be generated at build-time. The reason this is an RFC is that it is a potentially breaking change, but only for integrators _not_ using the cmake buildsystem. Currently the linker uses a large variety of pattern matches to organise the partition symbols, with these patterns being defined in the tfm_manifest_list.yaml. After this change, the linker will only look for two patterns: `*app_rot_partition*` and `*psa_rot_partition*` With the intention that the secure partitions will be compiled into a static library, where the filename is (for example) `libtfm_psa_rot_partition_crypto.a`. The cmake buildsystem will be updated to generate these filenames, but other integrators will need to adjust their compilation steps else the linking will fail. Any comments or concerns would be appreciated. Patches can be found at: https://review.trustedfirmware.org/q/topic:%23static_linker_scripts%22 Raef

4 years, 4 months

1
0
0 0

[RFC] Variable naming refinement in manifest tool

by Kevin Peng

Hi all, I made a patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7817> to refine the variable naming in manifest tooling, specifically the "manifest.manifest" in templates. I'm changing it to "partition.manifest" which should be more accurate and easy understanding. Broadcasting here for anyone has out-of-tree templates. And any comments are welcome. Best Regards, Kevin

4 years, 4 months

1
0
0 0

Re: [TF-M] TF-M generic threat model

by David Hu

Hi Antonio, Thanks a lot for reviewing the threat model and bringing up this topic. To fully mitigate the threat you mentioned, NSPE shall enforce NS tasks isolation and assign/manage NS identifications. IMHO, It mainly relies on non-secure side implementation. Therefore that threat can be covered in the scope of another threat model against NS side. TF-M is trying to figure out how to assist NSPE to manage and transfer NS identifications. Any suggestion or comment is welcome and helpful! 😊 Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Antonio Ken IANNILLO via TF-M Sent: Wednesday, December 30, 2020 7:13 PM To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] TF-M generic threat model Hi Hu, I read the threat model and I have a question regarding a potential threat. I’m not sure it should belong to this generic threat model or it is already included in one of those presented. The scenario is the following: a NS App X uses a RoT Service that store data private to X. Another NS App Y can fool the SPE to impersonate X and retrieve its private data. For example, X save a value in the secure storage and Y retrieves this value. TF-M prevents this using non secure client identification mechanism. This is a classic confused deputy problem. Can this be considered a threat in this model or should it belong to another model/TOE? Best, -- Antonio Ken Iannillo Research Scientist – SEDAN group SnT – Interdisciplinary Centre for Security, Reliability and Trust UNIVERSITÉ DU LUXEMBOURG CAMPUS KIRCHBERG 29, avenue John F. Kennedy L-1855 Luxembourg Kirchberg T +352 46 66 44 9660 https://akiannillo.github.io/

4 years, 4 months

2
2
0 0

Re: [TF-M] Technical Forum call - Jan 7

by David Hu

Hi Anton, I'd like to give a brief introduction to TF-M generic threat model. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Monday, January 4, 2021 5:30 PM To: 'tf-m(a)lists.trustedfirmware.org' <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: [TF-M] Technical Forum call - Jan 7 Hello, The next Technical Forum is planned on Thursday, January 7 at 6:00-07: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
0
0 0

Technical Forum call - Jan 7

by Anton Komlev

Hello, The next Technical Forum is planned on Thursday, January 7 at 6:00-07: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
0
0 0

[RFC] Remove unused section 'TFM_UNPRIV_DATA'

by Ken Liu

Hi, The existing section 'TFM_UNPRIV_DATA' now holds nothing - it was designed for holding some data belong to the unprivileged code block, while now the unprivileged code is required as read-only and no place for its read-write data. Remove this section as it is unused; also remove those code objects exists in the unprivileged code section but has read-write data: 'platform_retarget_dev.o' and 'device_definition.o'. This patch changes some sources inside the platforms, so the platform owner please help to check if that matters: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7754 Thanks. /Ken

4 years, 4 months

1
1
0 0

Re: [TF-M] TF-M generic threat model

by Antonio Ken IANNILLO

Hi Hu, I read the threat model and I have a question regarding a potential threat. I’m not sure it should belong to this generic threat model or it is already included in one of those presented. The scenario is the following: a NS App X uses a RoT Service that store data private to X. Another NS App Y can fool the SPE to impersonate X and retrieve its private data. For example, X save a value in the secure storage and Y retrieves this value. TF-M prevents this using non secure client identification mechanism. This is a classic confused deputy problem. Can this be considered a threat in this model or should it belong to another model/TOE? Best, -- Antonio Ken Iannillo Research Scientist – SEDAN group SnT – Interdisciplinary Centre for Security, Reliability and Trust UNIVERSITÉ DU LUXEMBOURG CAMPUS KIRCHBERG 29, avenue John F. Kennedy L-1855 Luxembourg Kirchberg T +352 46 66 44 9660 https://akiannillo.github.io/

4 years, 4 months

1
0
0 0

Re: [TF-M] RFC on changes to install directory structure

by Xinyu Zhang

Hi Raef, Please merge this patch for CI together with your patches. https://review.trustedfirmware.org/c/ci/tf-m-ci-scripts/+/7755 BR, Xinyu -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Raef Coles via TF-M Sent: Tuesday, December 29, 2020 7:56 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] RFC on changes to install directory structure Hi everyone I'd like to request for comment on some changes to the TF-M installed files. Since this is an interface change (though minor), changes to it might cause issues with existing TF-M integrations. The current install directory looks like: install ├── export │ └── tfm └── outputs This doesn't give any useful information about what is contained in each directory. The proposed replacement is: install ├── image_signing ├── interface └── outputs Where the contents of `export/tfm` have been moved into `interface`, which better captures the contents of that directory. `image_signing` is new in the patchset, and contains the scripts, layouts and keys needed to sign an NS image. The final improvement in the patchset is the ability to control the location of the `install` directory via TFM_INSTALL_PATH which could be useful for integrators. Feedback would be appreciated if you feel that these new directory names could be improved, or if this change would cause significant breakage for your TF-M integration. Patchset here: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7398/6 Raef -- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m

4 years, 4 months

1
0
0 0

RFC on changes to install directory structure

by Raef Coles

Hi everyone I'd like to request for comment on some changes to the TF-M installed files. Since this is an interface change (though minor), changes to it might cause issues with existing TF-M integrations. The current install directory looks like: install ├── export │ └── tfm └── outputs This doesn't give any useful information about what is contained in each directory. The proposed replacement is: install ├── image_signing ├── interface └── outputs Where the contents of `export/tfm` have been moved into `interface`, which better captures the contents of that directory. `image_signing` is new in the patchset, and contains the scripts, layouts and keys needed to sign an NS image. The final improvement in the patchset is the ability to control the location of the `install` directory via TFM_INSTALL_PATH which could be useful for integrators. Feedback would be appreciated if you feel that these new directory names could be improved, or if this change would cause significant breakage for your TF-M integration. Patchset here: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7398/6 Raef

4 years, 4 months

1
0
0 0

Changes to TF-M NS interface build

by David Hu

Hi all, Happy holiday! I'd like to let you know that non-secure interface build has been moved from TF-M to tf-m-tests in following patches: TF-M: https://review.trustedfirmware.org/q/topic:%22move-ns-api%22+(status:open%2… Tf-m-tests: https://review.trustedfirmware.org/q/topic:%22add-ns-api%22+(status:open%20… After that change, the .c files under TF-M interface/src are built during non-secure side build. It aligns with the actual process of NS integration with TF-M. Moreover, non-secure specific flags, which control TF-M NS interface, can be configured and managed in non-secure side build, without affecting TF-M secure part. Please modify tf-m-tests app/CMakeLists.txt for future changes to non-secure interface build. Thanks. Best regards, Hu Ziji

4 years, 4 months

1
0
0 0

Re: [TF-M] Discuss how to support secure Flash in TF-M

by David Hu

Hi Poppy, Some rough ideas about secure Flash support in TF-M. IMHO, there can be two options: 1. Based on ITS service Secure Flash acts as the flash driver at the backend of ITS service. The secure Flash driver can invoke Crypto secure service instead of mbedTLS to avoid building two duplicates of mbedTLS library. The cryptographic operation and key management are implemented in secure Flash driver and can be transparent to ITS service while some initialization can be necessary. But it cannot support persistent keys otherwise it will generate a circular dependency between ITS and Crypto services. 1. Based on PS service With PS service, the cryptographic operations can be implemented by PS crypto steps, such as encryption and authentication. Secure Flash driver only covers communication with remote device. We don’t have to worry about the circular dependency with Crypto service. However, there are some limitations of PS service currently: * PS service cannot support multiple asset keys for cryptography. * PS service cannot work alone without ITS service. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Edward Yang via TF-M Sent: Monday, December 21, 2020 1:22 PM To: Jamie Fox <Jamie.Fox(a)arm.com<mailto:Jamie.Fox@arm.com>> Cc: Julien Su <juliensu(a)mxic.com.tw<mailto:juliensu@mxic.com.tw>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>; Aaron Zhu <AaronZhu(a)mxic.com.cn<mailto:AaronZhu@mxic.com.cn>>; TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>>; nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: [TF-M] Discuss how to support secure Flash in TF-M Hi Jamie, >As I understand it, one of the uses of the secure flash is to store crypto keys, so the dependency from Crypto to the secure flash needs to be kept. The crypto keys you mentioned in your previous reply are the crypto keys used to encrypt the communication channel between host MCU with the secure Flash? Or the secrets such as (public/private)key pairs used in TLS protocol? If the former,I think these keys may be stored in NVM memories such as OTP or internal flash of MCU,and these keys can be loaded and imported as transient keys in RAM with a key handle during such as secure boot, then we can call PSA Crypto service with these key handles, in this case, the dependency from Crypto to secure flash doesn't exist. Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 http://www.mxic.com.cn<http://www.mxic.com.cn/> Poppy Wu/CHINA/MXIC 2020/12/16 14:20 To Edward Yang <EdwardYang(a)mxic.com.cn<mailto:EdwardYang@mxic.com.cn>> cc Subject Re: [TF-M] Discuss how to support secure Flash in TF-MLink<Notes://cnmail01/482583DD001E2E02/DABA975B9FB113EB852564B5001283EA/6BDCE39917970ADF4825863F00689523> Hi Jamie, Thank you for your reply. You are right,the secure Flash can be used to store sensitive information like TLS private keys,in this application, during TLS handshake,Crypto service depends on secure Flash driver to get these private keys,so the dependency from Crypto to the secure flash needs to be kept. And you mentioned implementation of crypto functions varies depending on the platform(some platforms have hardware crypto module while the others have to depend on software crypto library), platfrom without HW crypto module could use AES encrypt/decrypt functions from a software crypto library (e.g. Mbed TLS). As I understand, currently tfm Crypto service also uses Mbed TLS as the backend software crypto library by default. I am wondering if secure Flash driver could call this Mbed TLS library APIs (such as mbedtls_aes_encrypt（）) directly? Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 http://www.mxic.com.cn<http://www.mxic.com.cn/> Jamie Fox via TF-M <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Sent by: "TF-M" <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> 2020/12/16 03:02 Please respond to Jamie Fox <Jamie.Fox(a)arm.com<mailto:Jamie.Fox@arm.com>> To Edward Yang <EdwardYang(a)mxic.com.cn<mailto:EdwardYang@mxic.com.cn>> cc nd <nd(a)arm.com<mailto:nd@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>> Subject Re: [TF-M] Discuss how to support secure Flash in TF-M Hi, The trouble with calling the PSA Crypto functions from your secure flash driver is that it will create a circular dependency between the ITS service and the Crypto service. Crypto uses ITS to store its keys, but then the secure flash driver calls the Crypto service again to encrypt the data. These circular dependencies between partitions are forbidden in TF-M. As I understand it, one of the uses of the secure flash is to store crypto keys, so the dependency from Crypto to the secure flash needs to be kept. That means the dependency on the Crypto service in the secure flash driver needs to be avoided. I think ideally the best way to do this would be to use hardware crypto functions available in the platform instead of PSA Crypto APIs inside the flash driver, but if no crypto hardware is available then you could use AES encrypt/decrypt functions from a software crypto library (e.g. Mbed TLS). Hope that helps. Kind regards, Jamie From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Edward Yang via TF-M Sent: 15 December 2020 10:08 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] Discuss how to support secure Flash in TF-M Dear all, I would like to discuss how to add secure Flash support in TF-M. Firstly, I want to describe the motivation of adding secure Flash support in TF-M. Currently ARM TF-M provides protected storage service(PS service for short) to implement security protection on external normal storage, however this type external normal storage is still vulnerable to unauthorized physical modifications/erasing and cloning.Macronix and other Flash memory suppliers have developed secure Flash products to enhance the security in external flash devices. Secure Flash enables mutual authentication between itself and host MCU/SoC and only permits the authorised host to perform access, besides, the communication channel between host MCU/SoC and secure Flash is protected by encryption, authentication, data scrambling, and frame sequencing with monotonic counters as shown below, so the secure Flash provides dependable defense against unauthorised access, man-in-the-middle, replay, sniffing and other security threats. [cid:image001.gif@01D6D91C.DAC89B20] If we port TF-M to a platform which uses secure Flash as external flash,then secure Flash driver should be added to TF-M.However,compared with nomal external flash driver,secure Flash driver needs extra crypto functions(such as calling AES crypto functions to encrypt/decrypt data), if the secure Flash driver is placed in platform folder in TF-M code structure as a backend of ITS service, I don't know whether secure Flash driver is allowed to call Crypto service(such as psa_aead_encrypt(), psa_aead_decrypt() )directly.If not, are there any other solutions to perform crypto operations in secure Flash driver? Best Regards, Poppy Wu Macronix Microelectronics (Suzhou) Co.,Ltd Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 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<mailto:TF-M@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 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. =====================================================================

4 years, 4 months

1
0
0 0

Re: [TF-M] TF-M generic threat model

by David Hu

Hi all, I’d like to merge the generic threat model by the end of this week if no further comment. I’m also going to give a brief introduction to TF-M threat modeling in future technical forum. 😊 Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Thursday, December 10, 2020 9:37 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] TF-M generic threat model Hi all, A generic threat model of TF-M has been uploaded to gerrit. It is a key step in TF-M Threat Modeling. Please help review the threat model document via the link below. https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7492 Any question or comment is welcome! Best regards, Hu Ziji

4 years, 4 months

1
0
0 0

Discuss how to support secure Flash in TF-M

by Edward Yang

Hi Jamie, >As I understand it, one of the uses of the secure flash is to store crypto keys, so the dependency from Crypto to the secure flash needs to be kept. The crypto keys you mentioned in your previous reply are the crypto keys used to encrypt the communication channel between host MCU with the secure Flash? Or the secrets such as (public/private)key pairs used in TLS protocol? If the former,I think these keys may be stored in NVM memories such as OTP or internal flash of MCU,and these keys can be loaded and imported as transient keys in RAM with a key handle during such as secure boot, then we can call PSA Crypto service with these key handles, in this case, the dependency from Crypto to secure flash doesn't exist. Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 http://www.mxic.com.cn Poppy Wu/CHINA/MXIC 2020/12/16 14:20 To Edward Yang <EdwardYang(a)mxic.com.cn> cc Subject Re: [TF-M] Discuss how to support secure Flash in TF-MLink Hi Jamie, Thank you for your reply. You are right,the secure Flash can be used to store sensitive information like TLS private keys,in this application, during TLS handshake,Crypto service depends on secure Flash driver to get these private keys,so the dependency from Crypto to the secure flash needs to be kept. And you mentioned implementation of crypto functions varies depending on the platform(some platforms have hardware crypto module while the others have to depend on software crypto library), platfrom without HW crypto module could use AES encrypt/decrypt functions from a software crypto library (e.g. Mbed TLS). As I understand, currently tfm Crypto service also uses Mbed TLS as the backend software crypto library by default. I am wondering if secure Flash driver could call this Mbed TLS library APIs (such as mbedtls_aes_encrypt（）) directly? Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 http://www.mxic.com.cn Jamie Fox via TF-M <tf-m(a)lists.trustedfirmware.org> Sent by: "TF-M" <tf-m-bounces(a)lists.trustedfirmware.org> 2020/12/16 03:02 Please respond to Jamie Fox <Jamie.Fox(a)arm.com> To Edward Yang <EdwardYang(a)mxic.com.cn> cc nd <nd(a)arm.com>, "tf-m(a)lists.trustedfirmware.org" <tf-m(a)lists.trustedfirmware.org> Subject Re: [TF-M] Discuss how to support secure Flash in TF-M Hi, The trouble with calling the PSA Crypto functions from your secure flash driver is that it will create a circular dependency between the ITS service and the Crypto service. Crypto uses ITS to store its keys, but then the secure flash driver calls the Crypto service again to encrypt the data. These circular dependencies between partitions are forbidden in TF-M. As I understand it, one of the uses of the secure flash is to store crypto keys, so the dependency from Crypto to the secure flash needs to be kept. That means the dependency on the Crypto service in the secure flash driver needs to be avoided. I think ideally the best way to do this would be to use hardware crypto functions available in the platform instead of PSA Crypto APIs inside the flash driver, but if no crypto hardware is available then you could use AES encrypt/decrypt functions from a software crypto library (e.g. Mbed TLS). Hope that helps. Kind regards, Jamie From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: 15 December 2020 10:08 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Discuss how to support secure Flash in TF-M Dear all, I would like to discuss how to add secure Flash support in TF-M. Firstly, I want to describe the motivation of adding secure Flash support in TF-M. Currently ARM TF-M provides protected storage service(PS service for short) to implement security protection on external normal storage, however this type external normal storage is still vulnerable to unauthorized physical modifications/erasing and cloning.Macronix and other Flash memory suppliers have developed secure Flash products to enhance the security in external flash devices. Secure Flash enables mutual authentication between itself and host MCU/SoC and only permits the authorised host to perform access, besides, the communication channel between host MCU/SoC and secure Flash is protected by encryption, authentication, data scrambling, and frame sequencing with monotonic counters as shown below, so the secure Flash provides dependable defense against unauthorised access, man-in-the-middle, replay, sniffing and other security threats. If we port TF-M to a platform which uses secure Flash as external flash,then secure Flash driver should be added to TF-M.However,compared with nomal external flash driver,secure Flash driver needs extra crypto functions(such as calling AES crypto functions to encrypt/decrypt data), if the secure Flash driver is placed in platform folder in TF-M code structure as a backend of ITS service, I don't know whether secure Flash driver is allowed to call Crypto service(such as psa_aead_encrypt(), psa_aead_decrypt() )directly.If not, are there any other solutions to perform crypto operations in secure Flash driver? Best Regards, Poppy Wu Macronix Microelectronics (Suzhou) Co.,Ltd Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 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 ============================================================================ 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. =====================================================================

4 years, 4 months

1
0
0 0

Discuss how to support secure Flash in TF-M

by Edward Yang

Hi Jamie, Thank you for your reply. You are right,the secure Flash can be used to store sensitive information like TLS private keys,in this application, during TLS handshake,Crypto service depends on secure Flash driver to get these private keys,so the dependency from Crypto to the secure flash needs to be kept. And you mentioned implementation of crypto functions varies depending on the platform(some platforms have hardware crypto module while the others have to depend on software crypto library), platfrom without HW crypto module could use AES encrypt/decrypt functions from a software crypto library (e.g. Mbed TLS). As I understand, currently tfm Crypto service also uses Mbed TLS as the backend software crypto library by default. I am wondering if secure Flash driver could call this Mbed TLS library APIs (such as mbedtls_aes_encrypt（）) directly? Best Regards, Poppy Wu 吴偏偏 Macronix Microelectronics (Suzhou) Co.,Ltd 旺宏微电子（苏州）有限公司 No. 55, Su Hong Xi Road ,SIP, Suzhou, PRC, 215021 苏州工业园区苏虹西路55号 Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 http://www.mxic.com.cn Jamie Fox via TF-M <tf-m(a)lists.trustedfirmware.org> Sent by: "TF-M" <tf-m-bounces(a)lists.trustedfirmware.org> 2020/12/16 03:02 Please respond to Jamie Fox <Jamie.Fox(a)arm.com> To Edward Yang <EdwardYang(a)mxic.com.cn> cc nd <nd(a)arm.com>, "tf-m(a)lists.trustedfirmware.org" <tf-m(a)lists.trustedfirmware.org> Subject Re: [TF-M] Discuss how to support secure Flash in TF-M Hi, The trouble with calling the PSA Crypto functions from your secure flash driver is that it will create a circular dependency between the ITS service and the Crypto service. Crypto uses ITS to store its keys, but then the secure flash driver calls the Crypto service again to encrypt the data. These circular dependencies between partitions are forbidden in TF-M. As I understand it, one of the uses of the secure flash is to store crypto keys, so the dependency from Crypto to the secure flash needs to be kept. That means the dependency on the Crypto service in the secure flash driver needs to be avoided. I think ideally the best way to do this would be to use hardware crypto functions available in the platform instead of PSA Crypto APIs inside the flash driver, but if no crypto hardware is available then you could use AES encrypt/decrypt functions from a software crypto library (e.g. Mbed TLS). Hope that helps. Kind regards, Jamie From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: 15 December 2020 10:08 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Discuss how to support secure Flash in TF-M Dear all, I would like to discuss how to add secure Flash support in TF-M. Firstly, I want to describe the motivation of adding secure Flash support in TF-M. Currently ARM TF-M provides protected storage service(PS service for short) to implement security protection on external normal storage, however this type external normal storage is still vulnerable to unauthorized physical modifications/erasing and cloning.Macronix and other Flash memory suppliers have developed secure Flash products to enhance the security in external flash devices. Secure Flash enables mutual authentication between itself and host MCU/SoC and only permits the authorised host to perform access, besides, the communication channel between host MCU/SoC and secure Flash is protected by encryption, authentication, data scrambling, and frame sequencing with monotonic counters as shown below, so the secure Flash provides dependable defense against unauthorised access, man-in-the-middle, replay, sniffing and other security threats. If we port TF-M to a platform which uses secure Flash as external flash,then secure Flash driver should be added to TF-M.However,compared with nomal external flash driver,secure Flash driver needs extra crypto functions(such as calling AES crypto functions to encrypt/decrypt data), if the secure Flash driver is placed in platform folder in TF-M code structure as a backend of ITS service, I don't know whether secure Flash driver is allowed to call Crypto service(such as psa_aead_encrypt(), psa_aead_decrypt() )directly.If not, are there any other solutions to perform crypto operations in secure Flash driver? Best Regards, Poppy Wu Macronix Microelectronics (Suzhou) Co.,Ltd Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 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 ============================================================================ 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, 5 months

2
1
0 0

[CANCELLED] TF-M Technical Forum - December 24

by Anton Komlev

Hello, Probably the next Technical Forum will not be very popular, planned on Thursday, Dec 24 (US friendly time zone). Let's cancel this slot to meet again in January 7. Wish you pleasant holidays and Happy New Year. 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

Tiny update on the code review guidelines

by Ken Liu

Hi, The purpose of code review guidelines is trying to provide some reference for reviewers. It is still in the evaluation stage. After it gets matured then we can pointer to this document as a required reference. I updated some part of it, the main changes: - The private symbol (static inside a source file) can have a prefix for easier source viewing, a reader would know it is a symbol in the file he/she is viewing which can avoid cross-files 'find reference' operation in the editor. - Clarifies the header file types and the usage: A 'interface' header file is for abstraction, and a typical 'include' header contains exported functionalities for external module usage. Please help to take a look if you have time - as this is one of the upcoming updates, I will treat the review contents out of the changed lines into a new patch if it is possible. https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7577 Thanks. /Ken

4 years, 5 months

1
0
0 0

Re: [TF-M] Discuss how to support secure Flash in TF-M

by Jamie Fox

Hi, The trouble with calling the PSA Crypto functions from your secure flash driver is that it will create a circular dependency between the ITS service and the Crypto service. Crypto uses ITS to store its keys, but then the secure flash driver calls the Crypto service again to encrypt the data. These circular dependencies between partitions are forbidden in TF-M. As I understand it, one of the uses of the secure flash is to store crypto keys, so the dependency from Crypto to the secure flash needs to be kept. That means the dependency on the Crypto service in the secure flash driver needs to be avoided. I think ideally the best way to do this would be to use hardware crypto functions available in the platform instead of PSA Crypto APIs inside the flash driver, but if no crypto hardware is available then you could use AES encrypt/decrypt functions from a software crypto library (e.g. Mbed TLS). Hope that helps. Kind regards, Jamie From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: 15 December 2020 10:08 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Discuss how to support secure Flash in TF-M Dear all, I would like to discuss how to add secure Flash support in TF-M. Firstly, I want to describe the motivation of adding secure Flash support in TF-M. Currently ARM TF-M provides protected storage service(PS service for short) to implement security protection on external normal storage, however this type external normal storage is still vulnerable to unauthorized physical modifications/erasing and cloning.Macronix and other Flash memory suppliers have developed secure Flash products to enhance the security in external flash devices. Secure Flash enables mutual authentication between itself and host MCU/SoC and only permits the authorised host to perform access, besides, the communication channel between host MCU/SoC and secure Flash is protected by encryption, authentication, data scrambling, and frame sequencing with monotonic counters as shown below, so the secure Flash provides dependable defense against unauthorised access, man-in-the-middle, replay, sniffing and other security threats. [cid:image001.gif@01D6D313.1B0E4E10] If we port TF-M to a platform which uses secure Flash as external flash,then secure Flash driver should be added to TF-M.However,compared with nomal external flash driver,secure Flash driver needs extra crypto functions(such as calling AES crypto functions to encrypt/decrypt data), if the secure Flash driver is placed in platform folder in TF-M code structure as a backend of ITS service, I don't know whether secure Flash driver is allowed to call Crypto service(such as psa_aead_encrypt(), psa_aead_decrypt() )directly.If not, are there any other solutions to perform crypto operations in secure Flash driver? Best Regards, Poppy Wu Macronix Microelectronics (Suzhou) Co.,Ltd Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 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. =====================================================================

4 years, 5 months

1
0
0 0

Discuss how to support secure Flash in TF-M

by Edward Yang

Dear all, I would like to discuss how to add secure Flash support in TF-M. Firstly, I want to describe the motivation of adding secure Flash support in TF-M. Currently ARM TF-M provides protected storage service(PS service for short) to implement security protection on external normal storage, however this type external normal storage is still vulnerable to unauthorized physical modifications/erasing and cloning.Macronix and other Flash memory suppliers have developed secure Flash products to enhance the security in external flash devices. Secure Flash enables mutual authentication between itself and host MCU/SoC and only permits the authorised host to perform access, besides, the communication channel between host MCU/SoC and secure Flash is protected by encryption, authentication, data scrambling, and frame sequencing with monotonic counters as shown below, so the secure Flash provides dependable defense against unauthorised access, man-in-the-middle, replay, sniffing and other security threats. If we port TF-M to a platform which uses secure Flash as external flash,then secure Flash driver should be added to TF-M.However,compared with nomal external flash driver,secure Flash driver needs extra crypto functions(such as calling AES crypto functions to encrypt/decrypt data), if the secure Flash driver is placed in platform folder in TF-M code structure as a backend of ITS service, I don't know whether secure Flash driver is allowed to call Crypto service(such as psa_aead_encrypt(), psa_aead_decrypt() )directly.If not, are there any other solutions to perform crypto operations in secure Flash driver? Best Regards, Poppy Wu Macronix Microelectronics (Suzhou) Co.,Ltd Tel: 86-512-62580888 EXT: 3147 Fax: 86-512-62585399 ZIP: 215021 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. =====================================================================

4 years, 5 months

1
0
0 0

ITS and PS HALs pushed for review

by Jamie Fox

Hi all, I have pushed for review the new Internal Trusted Storage and Protected Storage HAL designs, as well as an initial implementation for AN521. I will update the change for all other platforms once the design has settled down. It expands the ITS and PS HALs to cover all flash and filesystem configuration parameters required from the platform. The CMSIS Flash Driver is exposed to abstract the flash device itself. ITS is updated to use the new HALs, with its_flash_info_external.c, its_flash_info_internal.c and its_flash.c removed. The ITS filesystem is updated to take a configuration struct as an initialisation parameter, which is filled using values from the HAL. The gerrit reviews are: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4781 https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7598 Kind regards, Jamie

4 years, 5 months

1
0
0 0

Re: [TF-M] [RFC] Moving partition stack into partition BSS/ZI.

by Ken Liu

😉 No response got yet, as it is closing to Xmas, plan to merge them before end of this week (18th Dec) if there is no more voice. Thanks. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: Monday, December 7, 2020 3:22 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [RFC] Moving partition stack into partition BSS/ZI. Hi, We are now allocating partition’s stack inside linker script file, and there are two external patches trying to move these stack definitions into partition’s BSS/ZI: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5374/5 https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6508/1 The advantages: - Simplify the linker script/sct templating, stack items can be saved. - Stack as global just uses 8 bytes alignment instead of wider bytes alignment (such as 32 bytes in most of the cases). - Stack is private data, putting private data together is a direct way. And the disadvantages: - Stack memory and global memory may affect each other – actually we don’t apply such protecting mechanism now? Anything I missed? Any feedbacks are welcome. We would collect your feedbacks and update the patches if they are still available after your comments. Other proposals are welcome, too. Thanks. /Ken

4 years, 5 months

1
0
0 0

Proposal to fix the version of tf-m-tests for auto-downloading in build system

by Kevin Peng

Hi all, The build system currently fetches the latest "master" of tf-m-tests repo for building, if auto-download dependencies mode is used (which is the default). This would break the building when: * TF-M and tf-m-tests have dependency changes got merged * A developer is working with a local copy of TF-M that has not been updated to the latest. * The developer does a clean build with auto-downloading * The build system fetch the latest tf-m-tests repo which is not compatible with the local copy of TF-M We've seen this kind of issue reported in mailing list. To solve this problem, the proposal<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7550> of fixing the "TFM_TEST_REPO_VERSION" to a hash or tag is raised. With this change, the build system would download a compatible version always. The version of the test repo is not required to be updated for every commit in the test repo. (Guide line on when to update the version is required and it's still under discussion - welcome for ideas.) Developers want a different version can always override "TFM_TEST_REPO_PATH" to a local copy to build. Best Regards, Kevin

4 years, 5 months

1
0
0 0

Re: [TF-M] Secure Enclave solution in TF-M + New path for Musca-B1 platform

by Mark Horvath

Dear All, The Secure Enclave patches have been merged and caused a minor source structure change. The platform so far named musca_b1 became musca_b1/sse_200, because we added support to the other subsystem on the Musca-B1 board, musca_b1/secure_enclave. So to build onto the old Musca-B1 platform the -DTFM_PLATFORM=musca_b1/sse_200 flag will be needed. All information about the Secure Enclave topic can be found in these rsts: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/desig… https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/refer… https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/e… Best regards, Mark From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Mark Horvath via TF-M Sent: 09 December 2020 10:11 To: 'tf-m(a)lists.trustedfirmware.org' <tf-m(a)lists.trustedfirmware.org> Subject: Re: [TF-M] Secure Enclave solution in TF-M Dear All, The patches for the Secure Enclave topic are planned to be merged soon if no further comments raised. https://review.trustedfirmware.org/q/topic:%22Secure+Enclave%22+(status:ope… Best regards, Mark From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Mark Horvath via TF-M Sent: 03 December 2020 16:38 To: 'tf-m(a)lists.trustedfirmware.org' <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Subject: Re: [TF-M] Secure Enclave solution in TF-M Dear All, I would like to merge the Secure Enclave topic at about middle of next week, feel free to give any feedback. https://review.trustedfirmware.org/q/topic:%22Secure+Enclave%22+(status:ope… Best regards, Mark From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Mark Horvath via TF-M Sent: 14 September 2020 21:00 To: 'tf-m(a)lists.trustedfirmware.org' <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Subject: [TF-M] Secure Enclave solution in TF-M Dear All, Following the tech forum presentation (back in 6th August) I uploaded the draft design document for the Secure Enclave topic: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5653 I also updated the first implementation of the proposed solution for the Musca-B1 board with minimal features, marked as WIP: https://review.trustedfirmware.org/q/topic:%22Secure+Enclave%22+(status:ope… Limitations, missing features, notes: * No support for isolation level2 on SSE-200 * Protected Storage is an Application RoT partition, but PS also moved to Secure Enclave * Some regression tests running on secure side of SSE-200 fail as all messages are forwarded with the same client ID to Secure Enclave * All IPC message forwarding is a blocking call * Only one message is put into the mailbox at a time * Musca-B1 related documentation is not complete yet * Generated files are not committed, manifest parser should be run before build. * The BL0 component mentioned in the tech forum presentation is not uploaded, as it is based on the new cmake system, and not so interesting right now * Cmake changes are rudimentary, will be rebased to new cmake system. Any feedback very welcomed! Best regards, Márk Horváth Senior Software Engineer Mark.Horvath(a)arm.com<mailto:Mark.Horvath@arm.com> Arm Hungary Kft., Corvin Offices II, Crystal Tower, Budapest, Futó u. 45. H-1082 Hungary www.arm.com<http://www.arm.com/>

4 years, 5 months

1
0
0 0

TF-M generic threat model

by David Hu

Hi all, A generic threat model of TF-M has been uploaded to gerrit. It is a key step in TF-M Threat Modeling. Please help review the threat model document via the link below. https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7492 Any question or comment is welcome! Best regards, Hu Ziji

4 years, 5 months

1
0
0 0

Re: [TF-M] TF-M Technical Forum call - December 10

by Anton Komlev

Hi All The agenda for the forum: 1. PSA FF-M v1.1 alpha specification overview. Do not miss it! 2. AOB Thanks, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Andrew Thoelke via TF-M Sent: 09 December 2020 15:42 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] TF-M Technical Forum call - December 10 Hi all, The proposed version 1.1 extensions to PSA FF-M version 1.0 will be published as an alpha specification in the next few weeks. I would like to update the Technical Forum on the final set of features for v1.1. (Some of these have already been presented earlier this year to the forum) Kind regards, Andrew 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: 02 December 2020 15:45 To: 'tf-m(a)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] TF-M Technical Forum call - December 10 Hello, The next Technical Forum is planned on Thursday, December 10 at 6:00-07: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
0
0 0

SW countermeasure against physical attacks in SPE

by Tamas Ban

Hi, PSA Level 3 certification mandates protection against physical attack at a certain extent. MCUboot v1.7.0 release already contains SW countermeasures against fault injection attacks. These can be used at device boot-up time. But fault injection attacks are not targeting only the device boot-up time, instead they could be applied against the runtime firmware. The following design proposal is addressing this threat: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7476 Prototype implementation on AN521 and Musca-B1 target (top of the patch set): https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7475/1 Review and comments are welcome! BR, Tamas Ban

4 years, 5 months

1
0
0 0

Re: [TF-M] TF-M Technical Forum call - December 10

by Andrew Thoelke

Hi all, The proposed version 1.1 extensions to PSA FF-M version 1.0 will be published as an alpha specification in the next few weeks. I would like to update the Technical Forum on the final set of features for v1.1. (Some of these have already been presented earlier this year to the forum) Kind regards, Andrew From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: 02 December 2020 15:45 To: 'tf-m(a)lists.trustedfirmware.org' <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: [TF-M] TF-M Technical Forum call - December 10 Hello, The next Technical Forum is planned on Thursday, December 10 at 6:00-07: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
0
0 0

Re: [TF-M] Secure Enclave solution in TF-M

by Mark Horvath

Dear All, The patches for the Secure Enclave topic are planned to be merged soon if no further comments raised. https://review.trustedfirmware.org/q/topic:%22Secure+Enclave%22+(status:ope… Best regards, Mark From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Mark Horvath via TF-M Sent: 03 December 2020 16:38 To: 'tf-m(a)lists.trustedfirmware.org' <tf-m(a)lists.trustedfirmware.org> Subject: Re: [TF-M] Secure Enclave solution in TF-M Dear All, I would like to merge the Secure Enclave topic at about middle of next week, feel free to give any feedback. https://review.trustedfirmware.org/q/topic:%22Secure+Enclave%22+(status:ope… Best regards, Mark From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Mark Horvath via TF-M Sent: 14 September 2020 21:00 To: 'tf-m(a)lists.trustedfirmware.org' <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Subject: [TF-M] Secure Enclave solution in TF-M Dear All, Following the tech forum presentation (back in 6th August) I uploaded the draft design document for the Secure Enclave topic: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5653 I also updated the first implementation of the proposed solution for the Musca-B1 board with minimal features, marked as WIP: https://review.trustedfirmware.org/q/topic:%22Secure+Enclave%22+(status:ope… Limitations, missing features, notes: * No support for isolation level2 on SSE-200 * Protected Storage is an Application RoT partition, but PS also moved to Secure Enclave * Some regression tests running on secure side of SSE-200 fail as all messages are forwarded with the same client ID to Secure Enclave * All IPC message forwarding is a blocking call * Only one message is put into the mailbox at a time * Musca-B1 related documentation is not complete yet * Generated files are not committed, manifest parser should be run before build. * The BL0 component mentioned in the tech forum presentation is not uploaded, as it is based on the new cmake system, and not so interesting right now * Cmake changes are rudimentary, will be rebased to new cmake system. Any feedback very welcomed! Best regards, Márk Horváth Senior Software Engineer Mark.Horvath(a)arm.com<mailto:Mark.Horvath@arm.com> Arm Hungary Kft., Corvin Offices II, Crystal Tower, Budapest, Futó u. 45. H-1082 Hungary www.arm.com<http://www.arm.com/>

4 years, 5 months

1
0
0 0

TF-M openCI nightly notification mail list is ready to subscribe

by Karl Zhang

Hi, There is a CI notification mail list enabled, it aims to send the failure info of TF-M nightly job to the subscribers without spam to a big group. If you are interested in the master branch nightly verification status, feel free to add your email to the list. Subscribing: https://lists.trustedfirmware.org/mailman/listinfo/tf-m-ci-notifications The notification only triggers a notification when CI build or test fail occur from the nightly job. Thanks Karl

4 years, 5 months

1
0
0 0

IAR, problems building with 8.50.9

by Thomas Törnblom

IAR released a new service pack late last week, version 8.50.9. This service pack includes a new compiler version, which although thoroughly tested, apparently introduced a new intricate bug, which causes at least the musca_a mcuboot to fail. The issue has been identified and fixed, and the next release should have this fix. I have no date for when this will be released or in what form. So for the time being, please do not upgrade above version 8.50.7. 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

1
0
0 0

[RFC] Moving partition stack into partition BSS/ZI.

by Ken Liu

Hi, We are now allocating partition's stack inside linker script file, and there are two external patches trying to move these stack definitions into partition's BSS/ZI: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5374/5 https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6508/1 The advantages: - Simplify the linker script/sct templating, stack items can be saved. - Stack as global just uses 8 bytes alignment instead of wider bytes alignment (such as 32 bytes in most of the cases). - Stack is private data, putting private data together is a direct way. And the disadvantages: - Stack memory and global memory may affect each other - actually we don't apply such protecting mechanism now? Anything I missed? Any feedbacks are welcome. We would collect your feedbacks and update the patches if they are still available after your comments. Other proposals are welcome, too. Thanks. /Ken

4 years, 5 months

1
0
0 0

[RFC] Build: Move UART symbols to SPRTL

by Kevin Peng

Hi Platform owners, explicitly ST, Nordic and NXP owners. Could you confirm that this patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6678> wouldn't break your platforms. The patch changes the build system to put the UART drivers to the SPRTL. It is important to improve the isolation implementations. For more details, please see the patch. We will wait for one more week and merge it as is if no feedbacks. Any feedbacks from others are welcome always. Best Regards, Kevin

4 years, 5 months

1
0
0 0

Re: [TF-M] Secure Enclave solution in TF-M

by Mark Horvath

Dear All, I would like to merge the Secure Enclave topic at about middle of next week, feel free to give any feedback. https://review.trustedfirmware.org/q/topic:%22Secure+Enclave%22+(status:ope… Best regards, Mark From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Mark Horvath via TF-M Sent: 14 September 2020 21:00 To: 'tf-m(a)lists.trustedfirmware.org' <tf-m(a)lists.trustedfirmware.org> Subject: [TF-M] Secure Enclave solution in TF-M Dear All, Following the tech forum presentation (back in 6th August) I uploaded the draft design document for the Secure Enclave topic: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5653 I also updated the first implementation of the proposed solution for the Musca-B1 board with minimal features, marked as WIP: https://review.trustedfirmware.org/q/topic:%22Secure+Enclave%22+(status:ope… Limitations, missing features, notes: * No support for isolation level2 on SSE-200 * Protected Storage is an Application RoT partition, but PS also moved to Secure Enclave * Some regression tests running on secure side of SSE-200 fail as all messages are forwarded with the same client ID to Secure Enclave * All IPC message forwarding is a blocking call * Only one message is put into the mailbox at a time * Musca-B1 related documentation is not complete yet * Generated files are not committed, manifest parser should be run before build. * The BL0 component mentioned in the tech forum presentation is not uploaded, as it is based on the new cmake system, and not so interesting right now * Cmake changes are rudimentary, will be rebased to new cmake system. Any feedback very welcomed! Best regards, Márk Horváth Senior Software Engineer Mark.Horvath(a)arm.com<mailto:Mark.Horvath@arm.com> Arm Hungary Kft., Corvin Offices II, Crystal Tower, Budapest, Futó u. 45. H-1082 Hungary www.arm.com<http://www.arm.com/>

4 years, 5 months

1
0
0 0

Review request of TF-M dual-cpu mailbox enhancement

by David Hu

Hi all, Could you please help the patches to enhance TF-M dual-cpu mailbox, as discussed in last Technical Forum? Improvements to make NS RTOS port easier: https://review.trustedfirmware.org/q/topic:%22mailbox-enhance%22+(status:op… A new working model to support NS RTOS application isolation better: https://review.trustedfirmware.org/q/topic:%22mailbox-dedicated-thread%22+(… Any comment is welcome! Please see the slides for the basic ideas of the enhancements mentioned above. Slides link: https://www.trustedfirmware.org/docs/TF-M_Dual-cpu_NSPE_mailbox_enhancement… Best regards, Hu Ziji

4 years, 5 months

1
0
0 0

Re: [TF-M] Review request for adding External Trusted Secure Storage service in TF-M

by Jamie Fox

Hi, Thank you for the proposal, I have commented in the Gerrit review. Kind regards, Jamie From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Edward Yang via TF-M Sent: 02 December 2020 14:28 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Review request for adding External Trusted Secure Storage service in TF-M Hi everyone, Please help review the following design proposal of adding External Trusted Secure Storage service in TF-M,any comments and suggestions will be appreciated. https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7295 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. =====================================================================

4 years, 5 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

TF-M