-
Overview
-
redpesk OS releases
-
Security updates
- Security CVE / errata
- CVE quick look
-
Redpesk OS Tips and Tricks
-
Application Framework Manager
-
Application Framework Binder
-
APIs & Services
-
Security manager
-
OP-TEE within redpesk
-
Trusted Boot
-
Recovery features
-
redpak
-
Minimal image
- Reduce image size
- Optimizing boot time
-
Kernel fragments description
- Introduction to Linux Kernel Configuration
- 01 Disable IPC, Timers and Audit
- 02 Disable Kconfig, Scheduler and Initrd
- 03 Disable Perf, Profiling and Errata
- 04 Disable EFI, Power Management Debug and Energy Model
- 05 Disable Schedutil, CPUFreq Governors and Virtualization
- 06 Disable Kprobes and Jump Labels
- 07 Disable GCC Plugins and Function Alignment
- 08 Disable Partition Parsers
- 09 Enable Inline Spinlocks and Kernel Operations
- 10 Disable Swap, Memory Hotplug and KSM
- 11 Disable Networking IPv4, IPv6, Netfilter
- 12 Disable SCTP, VLAN, TIPC, BATMAN
- 13 Disable Wireless, Bluetooth, CAN and RFKILL
- 14 Disable PCI and Firmware
- 15 Disable GNSS and ProcEvents
- 16 Disable Block Storage NBD and AoE
- 17 Disable EEPROM and Misc Drivers
- 18 Disable Network Device Drivers
- 19 Disable PHY Drivers
- 20 Disable PPP, WLAN Coexistence, and Failover
- 21 Disable Input Devices
- 22 Disable Serial, TTY and TPM
- 23 Disable I2C, Power and Sensor Drivers
- 24 Disable MFD, Display and Media Drivers
- 25 Disable USB, Sound, RTC and VirtIO
- 26 Disable Filesystem Encodings and Compatibility
- 27 Enable Minimal Cryptographic Core with SHA3 and XTS
- 28 Disable Hardware Cryptography, Keep DRBG and Jitter Entropy
- 29 Disable Kernel Debugging Features
- 30 Disable Filesystem Verity and SecurityFS
-
Zephyr in Redpesk
-
PERM-CHECK extension
-
Mender redpesk (OTA)
-
Hardware support
- Download images
- Image metrics
- Trusted Boot
- Graphical support
- Boards - ARM64
- Boards - x86_64
- Boards - Virtual
- Boards - Archived (legacy)
- Miscs
-
Building microservices natively within SDK container
-
Building microservices and framework from sources
Development
This chapter covers development tasks that are specific to the redpesk SDK container.
Build and run the sample
From inside the SDK container, follow the sample documentation:
Running those commands inside the SDK container uses the libraries and toolchain corresponding to the selected redpesk release.
Debug
For source-level debugging, configure a Debug build in the sample build directory:
cmake -S . -B build -DCMAKE_BUILD_TYPE=Debug
cmake --build build
The GDB helloworld-binding.so configuration from the project’s launch.json uses the cppdbg debugger type. In OpenVSCode Server, install an extension providing cppdbg support if one is not already available.
Set a breakpoint in the binding code, start the debug configuration, then invoke the API as described in Configuration and usage.

Framework debug packages
Debug information for redpesk framework components can be installed directly in the SDK container. For example:
sudo dnf debuginfo-install afb-binder
This installs the matching debug information for the framework version provided by the selected SDK image.
Test
Use the sample’s Validation and testing chapter for the current test dependencies and commands.