The official Mender documentation explains how Mender works. This is a board-specific complement to the official documentation.
Device description
Raspberry Pi 5 running the QNX Quick Start Target Image (tested on the 2GB variant).
Support level
Only basic functionality of the Mender Client was tested, in particular generation of an authentication key, connection and authentication to a Mender Server (hosted.mender.io), inventory reporting, and deployment of single-file and directory Mender Artifacts.
Getting started
Here is an APK for aarch64le (ARM8) QNX shipping the Mender Client and pulling in all the required dependencies. It’s enough to run sudo apk add --allow-untrusted ./mender-5.1.0-r0.apk and then follow setup instructions from the /usr/share/doc/mender/README_setup.md file.
Note: --allow-untrusted is required because there is no stable and published signing key for (QNX) APKs from Northern.tech (yet).
References
The QNX QSTI for Raspberry Pi 5 can be downloaded using a QNX Everywhere license.
Known issues
The build only ships one binary – mender-update, with the authentication functionality built-in. There is no mender-auth and thus no DBus API and no HTTP proxy functionality for connections to a Mender Server.
There is no rootfs-image Update Module, no boot loader integration and thus no full-system OTA updates functionality.