Skip to content

Hubble Device SDK v3.0.0 Release Notes

Latest

Choose a tag to compare

@ceolin ceolin released this 07 Aug 04:50
· 9 commits to main since this release
v3.0.0

Overview

Release 3.0.0 is a major release focused on the Satellite Network, which graduates from pre-production to a production-ready, stable API — the change that drives the major version bump.

Pass prediction is substantially more capable and more correct: passes now report the maximum elevation angle, start time, and duration, and applications can filter passes by a minimum elevation angle. A new Direct Test Mode (DTM) exposes transmit and continuous-wave controls for RF bring-up, certification, and manufacturing test. Satellite radio support arrives for TI CC27xx/CC23xx, Nordic nRF52/nRF53/nRF54 (including a SoftDevice-based path), Silicon Labs EFR32xG24, and Espressif ESP32-C6, with dual-stack, continuous, and DTM samples for each platform.

Key Features

Satellite Network Available

The Satellite Network is available in this release. The pre-production warning has been removed across the SDK: hubble/sat.h and its APIs are now supported for production deployments, with a stable API guaranteed within the 3.x series. Packet construction (hubble_sat_packet_get), frame splitting (hubble_sat_packet_frames_get), transmission with configurable reliability (hubble_sat_packet_send), and pass prediction are all production-ready. The one exception is hubble_sat_next_pass_region_get, which remains marked experimental.

Platform and Board Support

  • FreeRTOS / TI: CC27xx and CC23xx satellite radios; board files and radio flags via
    SysConfig, shipped as a Hubble SDK SysConfig product.
  • Zephyr / Nordic: SoftDevice-based satellite implementation plus an NCS SoftDevice
    snippet; nRF54L15-DK, nRF21540-DK, and Thingy:53 board support; west-ncs.yml manifest
    and CI for nRF Connect SDK.
  • Zephyr / Silicon Labs: EFR32xG24 satellite support via RAIL.
  • ESP-IDF: ESP32-C6 satellite support; the required PHY library is selected
    automatically when the satellite network is enabled.

Device Configuration Vector (HDCV)

A device's build-time configuration as a compact, versioned string, e.g.
HDCV:1.0/E:256/CS:UT/RP:S86400/N:T/TV:1:

  • hubble_config_vector_get — this build's HDCV string (key size, EID counter source and
    rotation period, networks and protocol versions compiled in).
  • hubble_config_vector_check — verify a stored or reported vector still matches the
    running firmware.

Full Changelog: v2.0.0...v3.0.0
Relese notes: https://hubblenetwork.github.io/hubble-device-sdk/release-3.0-branch/releases/3.0.html