Release Notes

Release Notes#

v4.1.0#

Release date: October 15, 2026
Type: Minor

Adds the SP500 DSP API for the REGULUS Vision DSP, the MLX-R1 image with A/B over-the-air updates, and MLD-R1 firmware v1.1.0.

Component

Version

SP500 DSP API

1.0.0

qb Runtime

1.5.1

Added#

  • [Highlight] SP500 DSP API 1.0.0 — the first release of the C API that runs pre- and postprocessing on the REGULUS Vision DSP. The package installs libsp500.so, the DSP firmware, the dsp_firmware_load loader, and the sp500/ headers. See DSP Overview.

    • Letterbox — sp500_letterbox() resizes an 8-bit HWC frame to a fixed model input size while preserving the aspect ratio, pads the border with a constant value, and returns the scale and padding needed to map detections back to the source frame. Nearest, bilinear, bicubic, and Lanczos interpolation are supported.

    • Log-mel spectrogram — sp500_log_mel() computes the Whisper-style log-mel spectrogram of float32 PCM, matching the Hugging Face WhisperFeatureExtractor, in the [n_frames, n_mels] layout the MXQ Whisper models take. sp500_log_mel_cpu() computes the same result on the host CPU.

    • YOLO decode — sp500_yolo_decode(), sp500_yolo_decode_anchor(), and sp500_yolo_postprocess() turn YOLO head outputs into detection, segmentation, or pose records in one DSP round trip, for the anchor-less (v3u, v5u, v8, v9, GELAN, 11, 12), anchor (v3, v5, v7), NMS-free (v10), and DFL-free (26) head families.

    • Shared memory and buffers — sp500_buffer_alloc() allocates zero-copy buffers in the shared-memory window, and sp500_shmem_phys_addr() returns their physical address so the NPU can use the same memory. sp500_buffer_wrap() passes application memory through a staged copy.

    • Lifecycle, locking, and versioning — sp500_dsp_open(), the system-wide DSP lock, the call deadline, status codes, and sp500_version().

  • [Highlight] MLX-R1 image and A/B over-the-air updates — core-image-regulus-mlx-r1 builds the root file system for the MLX-R1 Mini AI Box, with Modbus, OPC UA, CAN, and NetworkManager. With the rauc distro feature, regulus-emmc-ab-image builds an eMMC image with A/B slots for the kernel and root file system, updated through RAUC bundles.

  • MLD-R1 firmware v1.1.0 — for MLD-R1 Rev03B. The MLD-R1 ramdisk now includes the kernel modules and firmware it needs, and both firmware slots of the SPI flash hold the same image out of the factory.

  • eMMC gang image — regulus-emmc-image builds an image for factory provisioning.

  • lrzsz — serial file transfer.

  • WPA3 — the hostapd configuration supports WPA3.

Revised#

  • [Breaking] No compiler on the device — the OpenCV -dev and -staticdev packages, and the compiler and -dev packages they pulled in (gcc, binutils, and about 380 others), are no longer installed in the root file system. The OpenCV runtime libraries stay. Cross-compile applications on a host PC with the REGULUS SDK, as described in DSP Programming Guide.

  • Faster boot — the initramfs no longer waits for udev, which shortens boot time.

  • DNS and NTP — name resolution goes through systemd-resolved (DNS 8.8.8.8, fallback 1.1.1.1), and chrony replaces systemd-timesyncd for NTP.

  • lz4 — upgraded to 1.10.0.

v4.0.1#

Release date: July 15, 2026
Type: Patch

Release for the following target:

Item

Value

Target device

regulus-rb

SoM board version

REGULUS_SOM_REV01B or later

Carrier board version

REGULUS_CARRIER_REV.01B or later

Target board

regulus-evk-rev01

  • The regulus-version command shows the target device of the REGULUS board. The example below is for regulus-rb.

    REGULUS target device

  • Release v4.0.1 cannot be applied to the regulus-base-b target board.

  • The download URL for the image archives and documentation now depends on the target device:

    • regulus-ra: dl.mobilint.com/REGULUS/ra

    • regulus-rb: dl.mobilint.com/REGULUS/rb

    REGULUS target device menu

v3.4.0#

Release date: April 7, 2026
Type: Minor

  • The NPU driver is refactored. It is compatible with runtime library v1.1.0 or later.

  • The NPU SDK is renamed from maccel to qbruntime.

Important

To upgrade from v3.3.0 to v3.4.0:

  1. Burn the v3.4.0 boot images to the REGULUS board.

  2. In the application source code:

    • Change the header file from <maccel/maccel.h> to <qbruntime/qbruntime.h>.

    • Change the library from -lmaccel to -lqbruntime.

    • Recompile the application.

v3.3.0#

Release date: October 17, 2025
Type: Minor

  • The source code required to create the boot image is taken from gitlab.mobilint.com.

Important

To access gitlab.mobilint.com, sign in to dl.mobilint.com and generate a password for gitlab.mobilint.com. See the REGULUS PlatformSDK Build Guide (v1.6) for the steps.

v3.2.1#

Release date: August 13, 2025
Type: Patch

  • The PlatformSDK script and the PlatformSDK manual are updated.

Warning

Known issue (reported August 25, 2025): on a REGULUS board with 7 eMMC partitions, the burning image made by v3.2.1 fails the first time. Perform the burning process twice.

Fixed August 26, 2025: the script that makes the burning image is fixed. Download the poky_v3.2.1.tar.gz uploaded on August 26.

v3.2.0#

Release date: August 8, 2025
Type: Minor

  • PlatformSDK (poky), images, and source code are released.

  • The REGULUS Image Archive includes all images, the root file system, source code, and the toolchain. The image below shows the contents of regulus-release_v3.2.0.tar.gz.

    REGULUS release v3.2.0

Warning

From v3.2.0, the eMMC has 8 partitions, so v3.2.0 is not compatible with v3.1.0, which uses 7. To move from v3.1.0 to v3.2.0, create an eMMC burning image for v3.2.0 and burn the eMMC of the REGULUS board again. Back up any files in the user area of the board first.

v3.1.0#

Release date: June 17, 2025
Type: Minor

  • PlatformSDK (poky), images, and source code are released.

  • REGULUS PlatformSDK and the REGULUS Image Archive include everything needed for REGULUS development. The Image Archive includes all images, the root file system, source code, and the toolchain.

  • To start, read the REGULUS Application Note or the REGULUS Application Development guide. To develop an application without developing hardware, the Application Development guide alone is enough.

  • For more information, see the REGULUS PlatformSDK Build Guide and the other manuals.

Updates after release

  • June 19, 2025 — updated manuals: Application Note v1.6, Application Development v1.5, PlatformSDK Build Guide v1.1, eMMC Burning Guide v1.3.

  • July 9, 2025 — the MediaCreationTool in regulus-release_v3.1.0.tar.gz is updated for SD cards partitioned with GPT.

  • July 21, 2025 — new manuals: IP Modules Guide v1.0, Image Processing Program Guide v1.1.