Software stack requirements
Device Management Client is pre-integrated with Mbed OS, which provides the capabilities described below. However, you can choose a different real-time operating system (RTOS) and port Device Management Client by implementing a Platform Abstraction Layer (PAL) for it. See the porting guide for more information. We provide a porting layer to Linux.
To use Device Management Client with an OS other than Mbed OS, your platform and components must provide these capabilities:
|* Mbed OS v5: See the compatibility matrix.
* Linux: Ubuntu 16.04 LTS, Yocto v2.3.x
|For porting to other OS/RTOS, see the porting guide.
|Flash and filesystem drivers.
|* Networking Drivers.
* DNS resolver.
* Optional (recommended): DHCP.
|* IP over the HW supported bearer.
* DNS and DHCP simplifies the device configuration during deployment.
|Mbed TLS or equivalent Crypto and TLS/DTLS libraries.
|You should configure Mbed TLS to use only the latest TLS cipher suites, because older ones become vulnerable.
|Platform’s TRNG driver.
Crypto module programmed to use the TRNG.
|System’s tick availability at a rate of at least one tick per millisecond (higher than one Khz tick).
|The tick is the OS (platform) kernel system tick counter.
|Ability to software-reboot the device.
|Required for tests and for Device Management Update.
|Bootloader with firmware update capability.
|Required for Device Management Update.
Optional, if you do not use Device Management Update.
We provide a bootloader you can use with Mbed OS and reuse in other platforms.