3ede5667d4
1324: Add MCO support for L4 and F4 families r=Dirbaio a=m-dupont Add MCO support for L4 and F4 as already done in F7. When the 'HSI' source is selected as MCO source, 'HSI' is activated (`set_hsion(true)`) . This is done to operate the MCO in case 'MSI' is chosen as the clock source for the CPU. The same applies to PLL, etc. 1327: Avoid write before erase r=Dirbaio a=rmja This introduces an additional marker to the state partition right after the magic which indicates whether the current progress is valid or not. Validation in tests that we never write without an erase is added. There is currently a FIXME in the FirmwareUpdater. Let me know if we should take the erase value as a parameter. I opened a feature request in embedded-storage to get this value in the trait. Before this, the assumption about ERASE_VALUE=0xFF was the same. I have made some thoughts about whether this is a breaking change between the app and firmware, i.e. whether adding the "Progress valid" field is breaking. My conclusion is that it is not a breaking change. For the case where an app uses this new FirmwareUpdater together with an old bootloader, what it now does, is that it: 1. Writes the progress valid field to all zeros. This field is not known in the old bootloader, so it actually writes a "current progress" index. 2. The entire state partition is erased - effectively removing any trace of 1. 3. Set magic This should be compatible. Co-authored-by: Mathieu Dupont <mdupont@cppm.in2p3.fr> Co-authored-by: Rasmus Melchior Jacobsen <rmja@laesoe.org> |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
embassy-boot
An Embassy project.
A lightweight bootloader supporting firmware updates in a power-fail-safe way, with trial boots and rollbacks.
The bootloader can be used either as a library or be flashed directly with the default configuration derived from linker scripts.
By design, the bootloader does not provide any network capabilities. Networking capabilities for fetching new firmware can be provided by the user application, using the bootloader as a library for updating the firmware, or by using the bootloader as a library and adding this capability yourself.
Hardware support
The bootloader supports different hardware in separate crates:
embassy-boot-nrf- for the nRF microcontrollers.embassy-boot-stm32- for the STM32 microcontrollers.
Minimum supported Rust version (MSRV)
embassy-boot requires Rust nightly to compile as it relies on async traits for interacting with the flash peripherals.
License
This work is licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.