Lines Matching refs:to
4 The purpose of this document is to provide a guide on how to integrate TF-M
13 OS migration to Armv8-M <os_migration_guide_armv8m.rst>
25 How to build TF-M
30 How to export files for building non-secure applications
35 How to add a new platform
38 :doc:`Porting TF-M to a New Hardware </integration_guide/platform/porting_TFM_to_a_new_hardware>`
39 contains guidance on how to add a new platform.
42 How to integrate another OS
45 OS migration to Armv8-M platforms
47 To work with TF-M on Armv8-M platforms, the OS needs to support the Armv8-M
48 architecture and, in particular, it needs to be able to run in the non-secure
49 world. More information about OS migration to the Armv8-M architecture can be
51 the system configuration this may require configuring drivers to use appropriate
57 ``<install_dir>/interface`` path. The NS side is only allowed to call
68 ``tfm_ns_interface_dispatch()`` to integrate with TF-M implementation of PSA
73 ``tfm_ns_interface_dispatch()`` to synchronize multiple NS client calls to TF-M.
83 A non-secure application that wants to run the non-secure regression tests
84 needs to call the ``tfm_non_secure_client_run_tests()``. This function is
90 needs to link against the library to be able to invoke the
95 ``<build_dir>/install/export/tfm/test/inc``. OS needs to provide the
96 implementation of these wrappers to be able to run the tests.
111 Non-secure interrupts are allowed to preempt Secure thread mode.
114 Note, that ``AIRCR.PRIS`` is still set to restrict the priority range available
115 to NS interrupts to the lower half of available priorities so that it wouldn't
116 be possible for any non-secure interrupt to preempt a higher-priority secure
131 arguments will be needed to be provided. Please refer to
134 Some variables are used in the template files, these will need to be set in the