Repository navigation
Bumped to version 0.17.0 and bumped dependencies - #54
Merged
Merged
Conversation
Dependency requirements now give major.minor only; Cargo.lock pins the exact versions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
Cargo.tomlnow give major.minor only (tokio = "1.53",serde = "1.0", ...) instead of pinning a patch version.Cargo.lockstill 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 updatemoves 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
cargo buildandcargo test(104 tests) pass.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 flashsends the STM32and nRF51 firmware once to all the Crazyflies of a platform whose bootloaders
take broadcast (protocol 0x11, shown by
swarm bootload info), so they allreceive 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
--unicastflashes 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)
nRF51 bootloader and softdevice upgrades — releases carry the nRF51
bootloader and softdevice as one
bootloader+softdevicebinary, and the nRF51firmware says which softdevice it needs.
bootload flashandswarm bootload flashnow flash it before the nRF51 firmware when theCrazyflie 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+softdeviceis a new flash target, so a bootloader can alsobe 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-riskflashes it without asking. Seedocs/bootload.md.
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-addressthennames a new Crazyflie
CF-07and reprograms it toABAD1DEA07, using thefirst free number, written in decimal digits.
--set-addressand--set-channelreprogram to an exact link. The new link is written over USB(
--from-usb) or the radio and read back, the Crazyflie is rebooted over theradio (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.
Bug fixes
swarm bootload infono 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 firmwareafterwards too; it used to leave it in the bootloader.
(#44)
Improvements
Changes that can affect scripts
bootload flashwith a release or zip can now also write the nRF51bootloader and softdevice, when the Crazyflie's are older.
--binneeds--accept-bootloader-riskwhenrunning non-interactively (exit code 30 without it).
swarm bootload flashsaysflashed (broadcast)orflashed (unicast)instead offlashed, and ends with how long it took.--unicastflashes the way 0.16.0 did.bootload infowithout--coldnow leaves the Crazyflie in its firmware,not in its bootloader.