.. zephyr:board:: s32z2xxdc2

Overview

The X-S32Z27X-DC (DC2) board is based on the NXP S32Z2 Real-Time Processor, which includes two Real-Time Units (RTU) composed of four ARM Cortex-R52 cores each, with flexible split/lock configurations.

There is one Zephyr board per SoC/RTU:

s32z2xxdc2/s32z270/rtu0, for S32Z270/RTU0
s32z2xxdc2/s32z270/rtu1, for S32Z270/RTU1.

Hardware

Information about the hardware and design resources can be found at NXP S32Z2 Real-Time Processors website_.

Supported Features

.. zephyr:board-supported-hw::

Connections and IOs

The SoC's pads are grouped into ports and pins for consistency with GPIO driver and the HAL drivers used by this Zephyr port. The following table summarizes the mapping between pads and ports/pins. This must be taken into account when using GPIO driver or configuring the pinmuxing for the device drivers.

This board does not include user LED's or switches, which are needed for some of the samples such as :zephyr:code-sample:blinky or :zephyr:code-sample:button. Follow the steps described in the sample description to enable support for this board.

System Clock

The Cortex-R52 cores are configured to run at 1 GHz.

Serial Port

The SoC has 12 LINFlexD instances that can be used in UART mode. The console can be accessed by default on the USB micro-B connector J119.

Watchdog

The watchdog driver only supports triggering an interrupt upon timer expiration. Zephyr is currently running from SRAM on this board, thus system reset is not supported.

Ethernet

NETC driver supports to manage the Physical Station Interface (PSI0) and/or a single Virtual SI (VSI). The rest of the VSI's shall be assigned to different cores of the system. Refer to :zephyr:code-sample:nxp_s32_netc to learn how to configure the Ethernet network controller.

Controller Area Network

CANEXCEL

CANEXCEL supports CAN Classic (CAN 2.0) and CAN FD modes. Remote transmission request is not supported.

Note that this board does not currently come with CAN transceivers installed for the CANEXCEL ports. To facilitate external traffic, you will need to add a CAN transceiver. Any transceiver pin-compatible with CAN 2.0 and CAN FD protocols can be used.

FlexCAN

FlexCAN supports CAN Classic (CAN 2.0) and CAN FD modes.

ADC

ADC is provided through ADC SAR controller with 2 instances. Each ADC SAR instance has 12-bit resolution. ADC channels are divided into 2 groups (precision and internal/standard).

.. note:: All channels of an instance only run on 1 group channel at the same time.

EDMA

The EDMA modules feature four EDMA3 instances: Instance 0 with 32 channels, and instances 1, 4, and 5, each with 16 channels.

External Flash

The on-board S26HS512T 512M-bit HyperFlash memory is connected to the QSPI controller port A1. This board configuration selects it as the default flash controller.

CRYPTO

The Hardware Security Engine (HSE) supports cryptographic operations, including hashing and symmetric ciphers, with capabilities for ECB, CBC, and CTR modes using RAM-based key catalogs with 128-bit or 256-bit key lengths.

.. note:: The driver assumes that the HSE Firmware has been installed and configured (i.e the key catalogs has been formatted, used MU instances has been activated, etc). HSE Firmware installation and configuration phase documented in HSE Firmware User Manual. Please contact NXP sales person or NXP distributor in order to have access to that document.

Programming and Debugging

.. zephyr:board-supported-runners::

Applications for the s32z2xxdc2 boards can be built in the usual way as documented in :ref:build_an_application.

Currently is only possible to load and execute a Zephyr application binary on this board from the core internal SRAM.

This board supports West runners for the following debug tools:

:ref:NXP S32 Debug Probe <nxp-s32-debug-probe> (default)
:ref:Lauterbach TRACE32 <lauterbach-trace32-debug-host-tools>

Follow the installation steps of the debug tool you plan to use before loading your firmware.

Set-up the Board

Connect the external debugger probe to the board's JTAG connector (J134) and to the host computer via USB or Ethernet, as supported by the probe.

For visualizing the serial output, connect the board's USB/UART port (J119) to the host computer and run your favorite terminal program to listen for output. For example, using the cross-platform pySerial miniterm_ terminal:

.. code-block:: console

python -m serial.tools.miniterm <port> 115200

Replace <port> with the port where the board can be found. For example, under Linux, /dev/ttyUSB0.

Debugging

You can build and debug the :zephyr:code-sample:hello_world sample for the board s32z2xxdc2/s32z270/rtu0 with:

.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: s32z2xxdc2/s32z270/rtu0 :goals: build debug

In case you are using a newer PCB revision, you have to use an adapted board definition as the default PCB revision is B. For example, if using revision D:

.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: s32z2xxdc2@D/s32z270/rtu0 :goals: build debug :compact:

At this point you can do your normal debug session. Set breakpoints and then :kbd:c to continue into the program. You should see the following message in the terminal:

.. code-block:: console

Hello World! s32z2xxdc2

To debug with Lauterbach TRACE32 software run instead:

.. code-block:: console

west debug -r trace32

Flashing

Follow these steps if you just want to download the application to the board SRAM and run.

flash command is supported only by the Lauterbach TRACE32 runner:

.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: s32z2xxdc2/s32z270/rtu0 :goals: build flash :flash-args: -r trace32 :compact:

.. note:: Currently, the Lauterbach start-up scripts executed with flash and debug commands perform the same steps to initialize the SoC and load the application to SRAM. The difference is that flash hides the Lauterbach TRACE32 interface, executes the application and exits.

To imitate a similar behavior using NXP S32 Debug Probe runner, you can run the debug command with GDB in batch mode:

.. code-block:: console

west debug --tool-opt='--batch'

RTU and Core Configuration

This Zephyr port can only run single core in any of the Cortex-R52 cores, either in lock-step or split-lock mode. By default, Zephyr runs on the first core of the RTU chosen and in lock-step mode (which is the reset configuration).

To build for split-lock mode, the :kconfig:option:CONFIG_DCLS must be disabled from your application Kconfig file.

By default the board configuration will set the runner arguments according to the build configuration. To debug for a core different than the default use:

.. tabs::

.. group-tab:: lockstep configuration

  .. code-block:: console

     west debug --core-name='R52_<rtu_id>_<core_id>_LS'

.. group-tab:: split-lock configuration

  .. code-block:: console

     west debug --core-name='R52_<rtu_id>_<core_id>'

Where:

<rtu_id> is the zero-based RTU index
<core_id> is the zero-based core index relative to the RTU on which to run the Zephyr application (0, 1, 2 or 3)

For example, to build the :zephyr:code-sample:hello_world sample for the board s32z2xxdc2/s32z270/rtu0 with split-lock core configuration:

.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: s32z2xxdc2/s32z270/rtu0 :goals: build :gen-args: -DCONFIG_DCLS=n :compact:

To execute this sample in the second core of RTU0 in split-lock mode:

.. code-block:: console

west debug --core-name='R52_0_1'

If using Lauterbach TRACE32, all runner parameters must be overridden from command line:

.. code-block:: console

west debug -r trace32 --startup-args elfFile=<elf_path> rtu=<rtu_id> core=<core_id> lockstep=<yes/no>

Where <elf_path> is the path to the Zephyr application ELF in the output directory.

.. include:: ../../common/board-footer.rst.inc

References

.. target-notes::

.. _NXP S32Z2 Real-Time Processors website: https://www.nxp.com/products/processors-and-microcontrollers/s32-automotive-platform/s32z-and-s32e-real-time-processors/s32z2-safe-and-secure-high-performance-real-time-processors:S32Z2

.. _pySerial miniterm: https://pyserial.readthedocs.io/en/latest/tools.html#module-serial.tools.miniterm