boards/adi/max32657evkit/doc/index.rst
.. zephyr:board:: max32657evkit
Overview
The MAX32657 microcontroller (MCU) is an advanced system-on-chip (SoC) featuring an Arm® Cortex®-M33 core with single-precision floating point unit (FPU) with digital signal processing (DSP) instructions, large flash and SRAM memories, and the latest generation Bluetooth® 5.4 Low Energy (LE) radio. The nano-power modes increase battery life substantially.
The MAX32657 is qualified to operate at a temperature range of -20 °C to +85 °C. Bluetooth 5.4 LE radio supports Mesh, long-range (coded), and high-throughput modes. A cryptographic toolbox (CTB) provides advanced root of trust security features, including an Advanced Encryption Standard (AES) Engine, TRNG, and secure boot. TrustZone is also included in the M33 Core. Many high-speed interfaces are supported on the device, including multiple SPI, UART, and I3C/I2C serial interfaces. All interfaces support efficient DMA-driven transfers between peripheral and memory.
The Zephyr port is running on the MAX32657 MCU.
Hardware
MAX32657 MCU:
Arm Cortex-M33 CPU with TrustZone® and FPU
1.2V to 1.6V Input Range for Integrated Boost DC-DC Converter
50MHz Low Power Oscillator
External Crystal Support
1MB Internal Flash with ECC
256kB Internal SRAM
8kB Cache
32.768kHz RTC external crystal
Typical Electrical Characteristics
Bluetooth 5.4 LE Radio
Optimal Peripheral Mix Provides Platform Scalability
Cryptographic Tool Box (CTB) for IP/Data Security
Secure Boot ROM
.. zephyr:board-supported-hw::
+-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | Name | Name | Settings | Description | +===========+===============+===============+==================================================================================================+ | JP1 | VLDO SEL | | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Sets the LDO output used for system power according to the value of resistor R4. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 3-4 | | | Sets the LDO output used for system power to 1.2V. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 5-6 | | | Sets the LDO output used for system power to 1.5V. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Sets the LDO output used for system power to 1.6V. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP2 | VIN SEL | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | VIN Powered from LDO. (USB Type-C connector is board's power source) | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 2-3 | | | VIN Powered from Battery | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP3 | VIN EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Connects the board's power source to system power by connecting VIN to VSYS_IN. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disconnects system power by disconnecting VIN from VSYS_IN. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP4 | VDD12 EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Connects system power to the MAX32657 by connecting VDD12 to VSYS_OUT. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disconnects system power from the MAX32657 by disconnecting VDD12 from VSYS_OUT. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP5 | VTREF EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Connects a reference voltage to the OBD circuit. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disconnects a reference voltage from the OBD circuit. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP6 | OBD VBUS EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Enables the OBD by connecting OBD_VBUS to VBUS. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disables the OBD by disconnecting OBD_VBUS from VBUS. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | J7 | VSYS EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Connects system power to all peripherals by connecting VSYS to VSYS_OUT. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disconnects system power to all peripherals by disconnecting VSYS from VSYS_OUT. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP7 | ACC VS EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Enables the accelerometer by connecting its supply voltage pin VS to VSYS. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disables the accelerometer by disconnecting its supply voltage pin VS from VSYS. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP8 | ACC VDD EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Enables the accelerometer by connecting its VDDIO pin to VSYS. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disables the accelerometer by disconnecting its VDDIO pin from VSYS. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP9 | ACC I2C EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Accelerometer SDA Pin is connected to MAX32657 I2C0_SDA. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Accelerometer SDA Pin is disconnected from MAX32657 I2C0_SDA. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP10 | ACC I2C EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Accelerometer SCL Pin is connected to MAX32657 I2C0_SCL. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Accelerometer SCL Pin is disconnected from MAX32657 I2C0_SCL. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP11 | BYP MAG SW | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Bypass Magnetic Switch. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Enables magnetic switch. The output of the switch is controlled by the AFE pin. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP12 | LOCK RSTN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | AFE Lock Pin is connected to MAX32657 RSTN pin. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | AFE Lock Pin is disconnected from MAX32657 RSTN pin. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP13 | LATCH CTRL | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Connects the AFE (LOCK) to the magnetic switch (OUTPUT LATCH CONTROL). | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 2-3 | | | Connects the AFE (WAKE) to the magnetic switch (OUTPUT LATCH CONTROL). | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP14 | AFE EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Enables the AFE (VBAT) by connecting it to VSYS. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disables the AFE (VBAT) by disconnecting it from VSYS. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP15 | AFE SPI EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | AFE CSB is connected to MAX32657 SPI0_CS0. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 3-4 | | | AFE SDI is connected to MAX32657 SPI0_MOSI. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 5-6 | | | AFE SCLK is connected to MAX32657 SPI0_SCK. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 7-8 | | | AFE SDO is connected to MAX32657 SPI0_MISO. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 9-10 | | | AFE INTB is connected to MAX32657 P0.7. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 11-12 | | | AFE GPIO2 is connected to MAX32657 P0.8. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open All | | | Disconnect SPI Interface from MAX32657. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP16 | I2C PU EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Enable SCL PU resistor. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disable SCL PU resistor. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP17 | I2C PU EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Enable SDA PU resistor. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disable SDA PU resistor. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP18 | OBD SWD EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 3-4 | | | OBD SWDIO is connected to the MAX32657 SWDIO. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 5-6 | | | OBD SWCLK is connected to the MAX32657 SWCLK. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 7-8 | | | OBD JTAG TDO Enable Jumper (It's not used on MAX32657). | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 9-10 | | | OBD JTAG TDI Enable Jumper (It's not used on MAX32657). | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 11-12 | | | OBD RSTN is connected to the MAX32657 RSTN. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 13-14 | | | OBD JTAG TRST Enable Jumper (It's not used on MAX32657). | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open All | | | Disable OBD SWD Connection from MAX32657. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP19 | OBD VCOM EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 3-4 | | | OBD VCOM TXD is connected VCOM EN RX Jumper. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 5-6 | | | OBD VCOM RXD is connected VCOM EN TX Jumper. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 7-8 | | | OBD VCOM CTS Enable Jumper (It's not used on MAX32657). | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 9-10 | | | OBD VCOM RTS Enable Jumper (It's not used on MAX32657). | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disable OBD VCOM connection from MAX32657. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP20 | VCOM EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Connects OBD VCOM RXD to the MAX32657 UART0A_TX. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disconnects OBD VCOM RXD from the MAX32657 UART0A_TX. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP21 | VCOM EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Connects OBD VCOM TXD to the MAX32657 UART0A_RX. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disconnects OBD VCOM TXD from the MAX32657 UART0A_RX. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP22 | EXT SWD EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Connects EXT SWD Connector Data Signals to the MAX32657 SWDIO pin. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disconnects EXT SWD Connector Data Signals from the MAX32657 SWDIO pin. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+ | JP23 | EXT SWD EN | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | 1-2 | | | Connects EXT SWD Connector Clock Signals to the MAX32657 SWDCLK pin. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | Open | | | Disconnects EXT SWD Connector Clock Signals from the MAX32657 SWDCLK pin. | | | | | +-----------+ | +----------------------------------------------------------------------------------+ | | | | | | +-----------+---------------+---------------+--------------------------------------------------------------------------------------------------+
Zephyr board options
The MAX32657 microcontroller (MCU) is an advanced system-on-chip (SoC) featuring an ARM Cortex-M33 architecture that provides Trustzone technology which allow define secure and non-secure application. Zephyr provides support for building for both Secure (S) and Non-Secure (NS) firmware.
The BOARD options are summarized below:
+-------------------------------+-------------------------------------------+ | BOARD | Description | +===============================+===========================================+ | max32657evkit/max32657 | For building Trust Zone Disabled firmware | +-------------------------------+-------------------------------------------+ | max32657evkit/max32657/ns | Building with TF-M (includes NS+S images) | +-------------------------------+-------------------------------------------+
Build the zephyr app for max32657evkit/max32657 board target will generate secure firmware
for zephyr. In this configuration 960KB of flash is used to store the code and 64KB
is used for storage section. In this mode tf-m is off and secure mode flag is on
(:kconfig:option:CONFIG_TRUSTED_EXECUTION_SECURE to y and
:kconfig:option:CONFIG_BUILD_WITH_TFM to n)
+----------+------------------+---------------------------------+ | Name | Address[Size] | Comment | +==========+==================+=================================+ | slot0 | 0x1000000[960k] | Secure zephyr image | +----------+------------------+---------------------------------+ | storage | 0x10f0000[64k] | File system, persistent storage | +----------+------------------+---------------------------------+
Here are the instructions to build zephyr with a secure configuration,
using :zephyr:code-sample:blinky sample:
.. zephyr-app-commands:: :zephyr-app: samples/basic/blinky/ :board: max32657evkit/max32657 :goals: build
The max32657evkit/max32657/ns board target is used to build the secure firmware
image using TF-M (:kconfig:option:CONFIG_BUILD_WITH_TFM to y) and
the non-secure firmware image using Zephyr
(:kconfig:option:CONFIG_TRUSTED_EXECUTION_NONSECURE to y).
Here are the instructions to build zephyr with a non-secure configuration,
using :zephyr:code-sample:blinky sample:
.. zephyr-app-commands:: :zephyr-app: samples/basic/blinky/ :board: max32657evkit/max32657/ns :goals: build
The above command will:
tfm_merged.hex which contain all images.Note:
Zephyr build TF-M with :kconfig:option:CONFIG_TFM_PROFILE_TYPE_NOT_SET mode
that meet most use case configuration especially for BLE related applications.
if TF-M small profile meet your application requirement you can set TF-M profile as small
:kconfig:option:CONFIG_TFM_PROFILE_TYPE_SMALL to y to decrease TF-M RAM and flash use.
MAX32657 1MB flash and 256KB RAM split to define section for MCUBoot, TF-M (S), Zephyr (NS) and storage that used for secure services and configurations. Default layout of MAX32657 is listed in below table.
+----------+------------------+---------------------------------+ | Name | Address[Size] | Comment | +==========+==================+=================================+ | boot | 0x1000000[64K] | MCU Bootloader | +----------+------------------+---------------------------------+ | slot0 | 0x1010000[320k] | Secure image slot0 (TF-M) | +----------+------------------+---------------------------------+ | slot0_ns | 0x1060000[576k] | Non-secure image slot0 (Zephyr) | +----------+------------------+---------------------------------+ | slot1 | 0x10F0000[0k] | Updates slot0 image | +----------+------------------+---------------------------------+ | slot1_ns | 0x10F0000[0k] | Updates slot0_ns image | +----------+------------------+---------------------------------+ | storage | 0x10f0000[64k] | Persistent storage | +----------+------------------+---------------------------------+
+----------------+------------------+-------------------+ | RAM | Address[Size] | Comment | +================+==================+===================+ | secure_ram | 0x20000000[64k] | Secure memory | +----------------+------------------+-------------------+ | non_secure_ram | 0x20010000[192k] | Non-Secure memory | +----------------+------------------+-------------------+
Flash memory layout are defines both on zephyr board file and Trusted Firmware M_ (TF-M) project
these definition shall be match. Zephyr defines it in
:zephyr_file:boards/adi/max32657evkit/max32657evkit_max32657_common.dtsi
file under flash section. TF-M project define them in
<zephyr_path>../modules/tee/tf-m/trusted-firmware-m/platform/ext/target/adi/max32657/partition/flash_layout.h file.`
If you would like to update flash region for your application you shall update related section in
these files.
Additionally if firmware update feature requires slot1 and slot1_ns section need to be defined. On default the section size set as 0 due to firmware update not requires on default.
The ARM Security Extensions model allows system developers to partition device hardware and
software resources, so that they exist in either the Secure world for the security subsystem,
or the Normal world for everything else. Correct system design can ensure that no Secure world
assets can be accessed from the Normal world. A Secure design places all sensitive resources
in the Secure world, and ideally has robust software running that can protect assets against
a wide range of possible software attacks (1_).
MPC (Memory Protection Controller) and PPC (Peripheral Protection Controller) are allow to protect memory and peripheral. In case of need peripheral and flash ownership can be updated in <zephyr_path>../modules/tee/tf-m/trusted-firmware-m/platform/ext/target/adi/max32657/s_ns_access.cmake` file by updating cmake flags to ON/OFF.
As an example for below configuration TRNG, SRAM_0 and SRAM_1 is not going to be accessible by non-secure. All others is going to be accessible by NS world.
.. code-block::
set(ADI_NS_PRPH_GCR ON CACHE BOOL "") set(ADI_NS_PRPH_SIR ON CACHE BOOL "") set(ADI_NS_PRPH_FCR ON CACHE BOOL "") set(ADI_NS_PRPH_WDT ON CACHE BOOL "") set(ADI_NS_PRPH_AES OFF CACHE BOOL "") set(ADI_NS_PRPH_AESKEY OFF CACHE BOOL "") set(ADI_NS_PRPH_CRC ON CACHE BOOL "") set(ADI_NS_PRPH_GPIO0 ON CACHE BOOL "") set(ADI_NS_PRPH_TIMER0 ON CACHE BOOL "") set(ADI_NS_PRPH_TIMER1 ON CACHE BOOL "") set(ADI_NS_PRPH_TIMER2 ON CACHE BOOL "") set(ADI_NS_PRPH_TIMER3 ON CACHE BOOL "") set(ADI_NS_PRPH_TIMER4 ON CACHE BOOL "") set(ADI_NS_PRPH_TIMER5 ON CACHE BOOL "") set(ADI_NS_PRPH_I3C ON CACHE BOOL "") set(ADI_NS_PRPH_UART ON CACHE BOOL "") set(ADI_NS_PRPH_SPI ON CACHE BOOL "") set(ADI_NS_PRPH_TRNG OFF CACHE BOOL "") set(ADI_NS_PRPH_BTLE_DBB ON CACHE BOOL "") set(ADI_NS_PRPH_BTLE_RFFE ON CACHE BOOL "") set(ADI_NS_PRPH_RSTZ ON CACHE BOOL "") set(ADI_NS_PRPH_BOOST ON CACHE BOOL "") set(ADI_NS_PRPH_BBSIR ON CACHE BOOL "") set(ADI_NS_PRPH_BBFCR ON CACHE BOOL "") set(ADI_NS_PRPH_RTC ON CACHE BOOL "") set(ADI_NS_PRPH_WUT0 ON CACHE BOOL "") set(ADI_NS_PRPH_WUT1 ON CACHE BOOL "") set(ADI_NS_PRPH_PWR ON CACHE BOOL "") set(ADI_NS_PRPH_MCR ON CACHE BOOL "")
set(ADI_NS_SRAM_0 OFF CACHE BOOL "Size: 32KB") set(ADI_NS_SRAM_1 OFF CACHE BOOL "Size: 32KB") set(ADI_NS_SRAM_2 ON CACHE BOOL "Size: 64KB") set(ADI_NS_SRAM_3 ON CACHE BOOL "Size: 64KB") set(ADI_NS_SRAM_4 ON CACHE BOOL "Size: 64KB")
set(ADI_S_RAM_CODE_SIZE "0x800" CACHE STRING "Default: 2KB")
set(ADI_FLASH_AREA_BL2_SIZE "0x10000" CACHE STRING "Default: 64KB") set(ADI_FLASH_S_PARTITION_SIZE "0x50000" CACHE STRING "Default: 320KB") set(ADI_FLASH_NS_PARTITION_SIZE "0x90000" CACHE STRING "Default: 576KB") set(ADI_FLASH_PS_AREA_SIZE "0x4000" CACHE STRING "Default: 16KB") set(ADI_FLASH_ITS_AREA_SIZE "0x4000" CACHE STRING "Default: 16KB")
if(EXISTS "${CMAKE_BINARY_DIR}/../../s_ns_access_overlay.cmake") include(${CMAKE_BINARY_DIR}/../../s_ns_access_overlay.cmake) endif()
As an alternative method (which recommended) user can configure ownership peripheral by
an cmake overlay file too without touching TF-M source files. For this path
create s_ns_access_overlay.cmake file under your project root folder and put peripheral/memory
you would like to be accessible by secure world.
As an example if below configuration files been put in the s_ns_access_overlay.cmake file
TRNG, SRAM_0 and SRAM_1 will be accessible by secure world only.
.. code-block::
set(ADI_NS_PRPH_TRNG OFF CACHE BOOL "") set(ADI_NS_SRAM_0 OFF CACHE BOOL "Size: 32KB") set(ADI_NS_SRAM_1 OFF CACHE BOOL "Size: 32KB")
Programming and Debugging
.. zephyr:board-supported-runners::
Here is an example for the :zephyr:code-sample:hello_world application. This example uses the
:ref:jlink-debug-host-tools as default.
.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: max32657evkit/max32657 :goals: flash
Open a serial terminal, reset the board (press the RESET button), and you should see the following message in the terminal:
.. code-block:: console
***** Booting Zephyr OS build v4.1.0 ***** Hello World! max32657evkit/max32657
The TF-M integration samples can be run using the
max32657evkit/max32657/ns board target. To run we need to manually flash
the resulting image (tfm_merged.hex) with a J-Link as follows
(reset and erase are for recovering a locked core):
.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: max32657evkit/max32657/ns :goals: build
.. code-block:: console
west flash --hex-file build/zephyr/tfm_merged.hex
.. code-block:: console
[INF] Starting bootloader [WRN] This device was provisioned with dummy keys. This device is NOT SECURE [INF] PSA Crypto init done, sig_type: RSA-3072 [WRN] Cannot upgrade: slots have non-compatible sectors [WRN] Cannot upgrade: slots have non-compatible sectors [INF] Bootloader chainload address offset: 0x10000 [INF] Jumping to the first image slot ***** Booting Zephyr OS build v4.1.0 ***** Hello World! max32657evkit/max32657/ns
Here is an example for the :zephyr:code-sample:hello_world application. This example uses the
:ref:jlink-debug-host-tools as default.
.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: max32657evkit/max32657 :goals: debug
Open a serial terminal, step through the application in your debugger, and you should see the following message in the terminal:
.. code-block:: console
***** Booting Zephyr OS build v4.1.0 ***** Hello World! max32657evkit/max32657
References
.. _1: https://developer.arm.com/documentation/100935/0100/The-TrustZone-hardware-architecture-
.. _Trusted Firmware M: https://tf-m.docs.trustedfirmware.org/en/latest/building/tfm_build_instruction.html