Lines Matching +full:apt +full:- +full:get

1 TF-M Requirements
4 The following are some of the boards that can be used with TF-M:
6 .. list-table::
7    :header-rows: 1
9    * - Board
10      - NSPE board name
11    * - :ref:`mps2_an521_board`
12      - ``mps2/an521/cpu0/ns`` (qemu supported)
13    * - :ref:`mps3_board`
14      - ``mps3/corstone300/an547/ns`` (qemu supported)
15    * - :zephyr:board:`bl5340_dvk`
16      - ``bl5340_dvk/nrf5340/cpuapp/ns``
17    * - :zephyr:board:`lpcxpresso55s69`
18      - ``lpcxpresso55s69_ns``
19    * - :ref:`nrf9160dk_nrf9160`
20      - ``nrf9160dk/nrf9160/ns``
21    * - :ref:`nrf5340dk_nrf5340`
22      - ``nrf5340dk/nrf5340/cpuapp/ns``
23    * - :zephyr:board:`b_u585i_iot02a`
24      - ``b_u585i_iot02a/stm32u585xx/ns``
25    * - :zephyr:board:`nucleo_l552ze_q`
26      - ``nucleo_l552ze_q/stm32l552xx/ns``
27    * - :zephyr:board:`stm32l562e_dk`
28      - ``stm32l562e_dk/stm32l562xx/ns``
29    * - :ref:`v2m_musca_b1_board`
30      - ``v2m_musca_b1/musca_b1/ns``
31    * - :ref:`v2m_musca_s1_board`
32      - ``v2m_musca_s1/musca_s1/ns``
34 To make sure TF-M is supported for a board
41 The following Python modules are required when building TF-M binaries:
53    .. code-block:: bash
55       $ pip3 install --user cryptography pyasn1 pyyaml cbor>=1.0.0 imgtool>=1.9.0 jinja2 click
57 They are used by TF-M's signing utility to prepare firmware images for
61 secure and non-secure binaries on certain platforms also requires the use of
66    .. code-block:: bash
68       $ sudo apt-get install srecord
72    .. code-block:: bash
76 For Windows-based systems, please make sure you have a copy of the utility
78 `SRecord for Windows <https://sourceforge.net/projects/srecord/files/srecord-win32>`_