Thanks!
docs/integration_guide/platform/porting_tfm_to_a_new_hardware.rst also mentions NS build which I think is no longer supported.
.. code-block:: CMake
set(CONFIG_TFM_USE_TRUSTZONE ON) set(TFM_MULTI_CORE_TOPOLOGY OFF) set(BL2 OFF CACHE BOOL "Whether to build BL2") set(NS FALSE CACHE BOOL "Whether to build NS app" FORCE)
Regards, Brian
From: David Hu David.Hu@arm.com Sent: Wednesday, November 29, 2023 2:47 AM To: Quach, Brian brian@ti.com; tf-m@lists.trustedfirmware.org Subject: [EXTERNAL] Re: preload.cmake
Hi Brian,
Sorry for the confusion. You are right. All the preload.cmake files have been renamed to cpuarch.cmake to specify their usage. Those documents will be updated later. Thanks for reporting this issue.
Where should be put fixed platform-specific definitions which are not related to CPU architecture?
It is suggested to put them under platform specific config.cmake file as non-cache variables.
Best regards, Hu Ziji
From: Quach, Brian via TF-M <tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org> Date: Wednesday, November 29, 2023 at 04:37 To: tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org <tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] preload.cmake Hi, I'm seeing references in the documentation for preload.cmake and several files with that name in TF-M v2.0.0. But looking at the code it seems like preload.cmake was replaced with cpuarch.cmake. Am I missing something? Where should be put fixed platform-specific definitions which are not related to CPU architecture?
Regards,
Brian Quach SimpleLink MCU Texas Instruments Inc.