![]() |
Wirepas SDK
|
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:
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.
Checkout flashing guidance from Wirepas Helpdesk.
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:
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:
Processor | Flash memory |
---|---|
nRF9131 | 752 kB |
nRF9151 | 752 kB |
nRF9161 | 752 kB |
Allocated RAM memory for application by the processor is following:
Processor | RAM memory |
---|---|
nRF9131 | 155 kB |
nRF9151 | 155 kB |
nRF9161 | 155 kB |
Some peripherals are used by the Wirepas Mesh stack and cannot be used by the application.
Peripheral | Associated interrupt (from file mcu/nrf/common/vendor/mdk/nrf9120.h) |
---|---|
Power | CLOCK_POWER_IRQn |
Radio | IPC_IRQn |
Timer0 | TIMER0_IRQn |
WDT | WDT_IRQn |
Rtc1 | RTC1_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,...)
Some peripherals are used by the stack but can also be accessed by the application.
All the other peripherals not listed above are free to be used by the application.
[3] WP-RM-108 - OTAP Reference Manual
[4] https://github.com/wirepas/wm-sdk/blob/master/source/reference_apps/dualmcu_app/api/DualMcuAPI.md