Skip to content

Bumped to version 0.17.0 and bumped dependencies - #54

Merged
evoggy merged 1 commit into
mainfrom
evoggy/release-0.17.0
Oct 15, 2026
Merged

evoggy merged 1 commit into
mainfrom
evoggy/release-0.17.0

Conversation

@evoggy

@evoggy evoggy commented Oct 15, 2026

Copy link
Copy Markdown
Member

Prepares the 0.17.0 release: #49, #24, #51 and #53 since 0.16.0. They add features (broadcast flashing of a swarm, nRF51 bootloader and softdevice upgrades, numbering new swarm Crazyflies) and change some output, hence a minor bump.

Changes

  • Version 0.17.0.
  • Dependency requirements in Cargo.toml now give major.minor only (tokio = "1.53", serde = "1.0", ...) instead of pinning a patch version. Cargo.lock still pins the exact versions. Every direct dependency is at its latest version within those ranges, so there are no major bumps this time. cfloader 0.2 came with Upgrade the nRF51 bootloader and softdevice when flashing #24.
  • cargo update moves 30 crates within their ranges, among them tokio 1.53.3, serde_json 1.0.154, octocrab 0.54.4, rustls 0.23.46 and zip 9.0.3. The newer zip pulls in zstd 0.14. No code changes.

Testing

Release notes (draft)

0.17.0 release notes

This release flashes a whole swarm at once by broadcast, brings Crazyflies
with an old nRF51 bootloader or softdevice up to date as part of a normal
flash, and numbers new swarm Crazyflies as they are added.

New features

  • Flashing a swarm by broadcast — swarm bootload flash sends the STM32
    and nRF51 firmware once to all the Crazyflies of a platform whose bootloaders
    take broadcast (protocol 0x11, shown by swarm bootload info), so they all
    receive it at the same time: about 45 s for both images, whether for 3
    Crazyflies or 50. Each Crazyflie is then checked page by page, and pages that
    didn't make it are flashed again to that Crazyflie alone. Crazyflies with
    older bootloaders are flashed one after another as before, and --unicast
    flashes them all that way. Deck firmware is flashed afterwards on all the
    Crazyradios at once, one Crazyflie per Crazyradio at a time. See
    docs/swarm.md.
    (#53)

    Broadcast to 3 Crazyflies (Crazyflie 2.1 Brushless): CF-02, CF-03, CF-04
    STM32 firmware sent to 3 Crazyflies
    nRF51 firmware sent to 3 Crazyflies
    
    CF    | Platform                | Result
    ------+-------------------------+---------------------
    CF-02 | Crazyflie 2.1 Brushless | flashed (broadcast)
    CF-03 | Crazyflie 2.1 Brushless | flashed (broadcast)
    CF-04 | Crazyflie 2.1 Brushless | flashed (broadcast)
    Took 0:45
    
  • nRF51 bootloader and softdevice upgrades — releases carry the nRF51
    bootloader and softdevice as one bootloader+softdevice binary, and the nRF51
    firmware says which softdevice it needs. bootload flash and
    swarm bootload flash now flash it before the nRF51 firmware when the
    Crazyflie has an older softdevice (S110 instead of S130) or an older
    bootloader than the release. A Crazyflie on S110 usually runs firmware too old
    for cfcli to connect to, so flash it with --cold. Upgrades only go forwards:
    a release with an older softdevice than the Crazyflie is refused, and the
    Crazyflie is restarted into its firmware.
    (#15)

    nrf51-bootloader+softdevice is a new flash target, so a bootloader can also
    be given as a file. A file can be anything, and a Crazyflie whose nRF51
    bootloader doesn't start can only be recovered with an SWD debug probe, so
    cfcli asks first (default no, once for a whole swarm).
    --accept-bootloader-risk flashes it without asking. See
    docs/bootload.md.

    cfcli bootload flash --bin nrf51-bootloader+softdevice=sd130_bootloader.bin,nrf51-fw=cf2_nrf.bin
    
  • Numbering new swarm Crazyflies — a swarm can store a base name and a base
    address (swarm config set base-name=CF-,base-address=ABAD1DEA,
    swarm config clear). swarm config add --base-name --base-address then
    names a new Crazyflie CF-07 and reprograms it to ABAD1DEA07, using the
    first free number, written in decimal digits. --set-address and
    --set-channel reprogram to an exact link. The new link is written over USB
    (--from-usb) or the radio and read back, the Crazyflie is rebooted over the
    radio (so a Crazyradio is needed even over USB), and it is only added to the
    swarm once it answers on its new link. See
    docs/swarm.md.

    cfcli swarm config add --from-usb --base-name --base-address --set-channel 90
    

Bug fixes

  • swarm bootload info no longer leaves Crazyflies in their bootloader —
    a Crazyflie whose bootloader didn't answer in time was left in it, where the
    swarm commands can't reach it, and only the power button got it out. Each one
    is now restarted into its firmware whatever happened, and checked to have
    left the bootloader. The bootloader is also asked again for 2 s when it
    doesn't answer at once, instead of giving up after 100 ms, and at most 2
    Crazyflies per Crazyradio are in their bootloaders at the same time.
    bootload info (without --cold) restarts the Crazyflie into its firmware
    afterwards too; it used to leave it in the bootloader.
    (#44)

Improvements

  • Updated dependencies — including cfloader 0.2.0.

Changes that can affect scripts

  • bootload flash with a release or zip can now also write the nRF51
    bootloader and softdevice, when the Crazyflie's are older.
  • An nRF51 bootloader given with --bin needs --accept-bootloader-risk when
    running non-interactively (exit code 30 without it).
  • The summary of swarm bootload flash says flashed (broadcast) or
    flashed (unicast) instead of flashed, and ends with how long it took.
    --unicast flashes the way 0.16.0 did.
  • bootload info without --cold now leaves the Crazyflie in its firmware,
    not in its bootloader.

Dependency requirements now give major.minor only; Cargo.lock pins the
exact versions.
@evoggy
evoggy merged commit e4c7203 into main Oct 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant