services/tfm/requirements.html · services/tfm/requirements.rst 공식 원문 ↗

Zephyr 3.7.0 · TF-M · Prerequisites

TF-M Requirements

지원되는 non-secure target과 signing·merge 도구를 먼저 준비합니다.

Official pathservices/tfm/requirements.html
Source fileservices/tfm/requirements.rst
Source versionZephyr 3.7.0
TranslationFull · reviewed

본문 기준: Zephyr 3.7.0 LTS3 · 이후 유지보수 패치는 별도입니다.

Part 1

요약·해설

TF-M 지원 board variant를 확인하는 법, Python signing dependency와 platform별 srec_cat 설치를 설명합니다.

Boards

11 NSPE targets

Python

Signing modules

Merge

SRecord · srec_cat

Part 2

접을 수 있는 영어 원문 전체

영어 원문 전체 펼치기
원문 SHA-256 6606F7DCD6291BB9D3BBEBBC0D85F4355939DE84682737B418F2145344A7D642
TF-M Requirements
#################

The following are some of the boards that can be used with TF-M:

.. list-table::
   :header-rows: 1

   * - Board
     - NSPE board name
   * - :ref:`mps2_an521_board`
     - ``mps2_an521_ns`` (qemu supported)
   * - :ref:`mps3_an547_board`
     - ``mps3_an547_ns`` (qemu supported)
   * - :ref:`bl5340_dvk`
     - ``bl5340_dvk/nrf5340/cpuapp/ns``
   * - :ref:`lpcxpresso55s69`
     - ``lpcxpresso55s69_ns``
   * - :ref:`nrf9160dk_nrf9160`
     - ``nrf9160dk/nrf9160/ns``
   * - :ref:`nrf5340dk_nrf5340`
     - ``nrf5340dk/nrf5340/cpuapp/ns``
   * - :ref:`b_u585i_iot02a_board`
     - ``b_u585i_iot02a/stm32u585xx/ns``
   * - :ref:`nucleo_l552ze_q_board`
     - ``nucleo_l552ze_q/stm32l552xx/ns``
   * - :ref:`stm32l562e_dk_board`
     - ``stm32l562e_dk/stm32l562xx/ns``
   * - :ref:`v2m_musca_b1_board`
     - ``v2m_musca_b1_ns``
   * - :ref:`v2m_musca_s1_board`
     - ``v2m_musca_s1_ns``

You can run ``west boards -n _ns$`` to search for non-secure variants
of different board targets. To make sure TF-M is supported for a board
in its output, check that :kconfig:option:`CONFIG_TRUSTED_EXECUTION_NONSECURE`
is set to ``y`` in that board's default configuration.

Software Requirements
*********************

The following Python modules are required when building TF-M binaries:

* cryptography
* pyasn1
* pyyaml
* cbor>=1.0.0
* imgtool>=1.9.0
* jinja2
* click

You can install them via:

   .. code-block:: bash

      $ pip3 install --user cryptography pyasn1 pyyaml cbor>=1.0.0 imgtool>=1.9.0 jinja2 click

They are used by TF-M's signing utility to prepare firmware images for
validation by the bootloader.

Part of the process of generating binaries for QEMU and merging signed
secure and non-secure binaries on certain platforms also requires the use of
the ``srec_cat`` utility.

This can be installed on Linux via:

   .. code-block:: bash

      $ sudo apt-get install srecord

And on OS X via:

   .. code-block:: bash

      $ brew install srecord

For Windows-based systems, please make sure you have a copy of the utility
available on your system path. See, for example:
`SRecord for Windows <https://sourceforge.net/projects/srecord/files/srecord-win32>`_

Part 3

한국어 전문 번역

TF-M를 사용할 수 있는 대표 board와 Zephyr non-secure processing environment(NSPE) target 이름은 다음과 같습니다.

BoardNSPE board name
MPS2 AN521mps2_an521_ns (QEMU 지원)
MPS3 AN547mps3_an547_ns (QEMU 지원)
BL5340 DVKbl5340_dvk/nrf5340/cpuapp/ns
LPCXpresso55S69lpcxpresso55s69_ns
nRF9160 DKnrf9160dk/nrf9160/ns
nRF5340 DKnrf5340dk/nrf5340/cpuapp/ns
B-U585I-IOT02Ab_u585i_iot02a/stm32u585xx/ns
Nucleo L552ZE-Qnucleo_l552ze_q/stm32l552xx/ns
STM32L562E-DKstm32l562e_dk/stm32l562xx/ns
V2M Musca-B1v2m_musca_b1_ns
V2M Musca-S1v2m_musca_s1_ns

다른 non-secure variant는 west boards -n _ns$로 찾습니다. 이름에 _ns가 있다고 모두 TF-M 통합 target인 것은 아니므로 board default configuration에서 CONFIG_TRUSTED_EXECUTION_NONSECURE=y인지 확인합니다.

Software Requirements

TF-M binary build와 signing에는 Python module cryptography, pyasn1, pyyaml, cbor>=1.0.0, imgtool>=1.9.0, jinja2, click이 필요합니다.

$ pip3 install --user cryptography pyasn1 pyyaml cbor>=1.0.0 imgtool>=1.9.0 jinja2 click

이 module들은 bootloader가 검증할 firmware image를 signing utility로 준비할 때 사용됩니다.

QEMU용 binary를 만들거나 일부 platform에서 signed secure·non-secure binary를 merge하려면 srec_cat도 필요합니다. Linux에서는 srecord package로 설치합니다.

$ sudo apt-get install srecord

macOS에서는 Homebrew를 사용합니다.

$ brew install srecord

Windows에서는 SRecord for Windows 같은 배포본의 executable을 받아 system PATH에서 찾을 수 있게 해야 합니다.

Source

출처

영어 원문에는 문단, 문서 지시문, 표, 코드, 코드 심벌, 경로를 그대로 보존했습니다.