Icarus SoM

Overview

The Icarus SoM is a coin-sized, easy-to-solder cellular IoT Module built around Nordic Semi’s nRF9160 modem and combines LTE-M, NB-IoT, GPS, accelerometer as well as an eSIM and option for an external nano SIM connector.

The main uController is the Nordic Semiconductor nRF9160, with ARM Cortex-M33F CPU, ARMv8-M Security Extension and the following devices (provided directly by Nordic):

  • ADC

  • CLOCK

  • FLASH

  • GPIO

  • I2C

  • MPU

  • NVIC

  • PWM

  • RTC

  • Segger RTT (RTT Console)

  • SPI

  • UARTE

  • WDT

  • IDAU

Icarus SoM Pins

Icarus SoM Pins

Icarus SoM

Internal Pinouts

Hardware

The detailed information about the on-board hardware can be found at the Icarus SoM Product Website [2].

Supported Features

The actinius_icarus_som board supports the hardware features listed below.

on-chip / on-board
Feature integrated in the SoC / present on the board.
2 / 2
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files.
vnd,foo
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.

SIM selection

The sim choice (eSIM or nano-SIM) can be configured in Devicetree by adjusting the sim property in the sim_select node.

Security components

  • Implementation Defined Attribution Unit (IDAU [1]). The IDAU is implemented with the System Protection Unit and is used to define secure and non-secure memory maps. By default, all of the memory space (Flash, SRAM, and peripheral address space) is defined to be secure accessible only.

  • Secure boot.

Building Secure/Non-Secure Zephyr applications

The process requires the following steps:

  1. Build the Secure Zephyr application using -DBOARD=actinius_icarus_som.

  2. Build the Non-Secure Zephyr application using -DBOARD=actinius_icarus_som/ns.

  3. Merge the two binaries together.

If you are using Segger Embedded Studio v4.18 or later, the two binaries are built, merged, and burned automatically, unless you have disabled the feature.

When building a Secure/Non-Secure application, the Secure application will have to set the IDAU (SPU) configuration to allow Non-Secure access to all CPU resources utilized by the Non-Secure application firmware. SPU configuration shall take place before jumping to the Non-Secure application.

More information can be found in the Icarus SoM Product Website [2] or the Actinius Documentation Portal [3].

References