Wirepas SDK
SDK Environment setup

As a prerequisite for this guide, you must be able to successfully build one of the provided application example from the SDK.

This page contains following sections:

Installation of SDK Environment

To ease the management of SDK environement, Wirepas maintains a docker image with all the required dependencies installed.

For more information to use it, please read guidance from Wirepas Helpdesk.

It is also possible to install requirement in your native environement but it is not described here. Requirement are listed in Github SDK main page under Requirement section.

Flashing devices

Checkout flashing guidance from Wirepas Helpdesk.

Resources on Nordic nRF91x1

The nRF91x1 chip version supported by Wirepas Mesh are nRF9131, nRF9151 and nRF9161. These have minimum 1024kB of flash and 256kB of RAM.

This page contains following sections:

Flash Memory available for application on nRF91x1

As stated in description of memory partitioning, the available flash memory for application is limited by size of the memory area that is used commonly for application and also scratchpad image. If application size is too large, there is possibility that large scratchpad image will override application image. The default maximum size of the application has been set so that it is always safe to use scratchpad image that will contain both firmware and application.

The recommended maximum size of flash memory for an application, according to processor type is following:

ProcessorFlash memory
nRF9131752 kB
nRF9151752 kB
nRF9161752 kB

RAM Memory available for application on nRF91x1

Allocated RAM memory for application by the processor is following:

ProcessorRAM memory
nRF9131155 kB
nRF9151155 kB
nRF9161155 kB

Peripherals accessible by stack only

Some peripherals are used by the Wirepas Mesh stack and cannot be used by the application.

PeripheralAssociated interrupt (from file mcu/nrf/common/vendor/mdk/nrf9120.h)
PowerCLOCK_POWER_IRQn
RadioIPC_IRQn
Timer0TIMER0_IRQn
WDTWDT_IRQn
Rtc1RTC1_IRQn
CRYPTOCELL (AES and RNG)CRYPTOCELL_IRQn
PPI (Channels 0, 1 and 2)None

All the internal interrupt of cortex M are handled by the stack directly (NMI, HardFault,...)

Peripherals shared between the stack and the application

Some peripherals are used by the stack but can also be accessed by the application.

Peripherals available for the application

All the other peripherals not listed above are free to be used by the application.

Related Material

[3] WP-RM-108 - OTAP Reference Manual

[4] https://github.com/wirepas/wm-sdk/blob/master/source/reference_apps/dualmcu_app/api/DualMcuAPI.md