-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
[nrf52,ota] zephyr mcumgr ota #5740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: next
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| image: system-update.svg | ||
| --- | ||
|
|
||
| The nRF52 platform supports firmware updates via Over-the-Air (OTA) mechanisms. The **only supported bootloader** for OTA updates is **MCUboot**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we improve the documentation on what we need around MCUboot? Most of what I read suggests that we only need slot0 partition but I suspect we need at least two slots for MCUBoot? My nice!nano nRF52 currently has an Adarfruit boot loader and I'm not certain what is required.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Best if you could open a PR with redaction of the doc. Push to this branch or just open new PR. I can link it to main PR. nrf52 doc could be improved in few places but I have no much time to think about it.
In the nut shell you need:
- flash firmware using SWD e.g. by stlink https://esphome.io/components/nrf52/#flashing-with-mcuboot
- From that moment you can flash new firmware using serial, cdc serial or ble
By default it use slot0 and slot1. https://docs.nordicsemi.com/bundle/ncs-latest/page/mcuboot/readme-zephyr.html
Description:
Related issue (if applicable): fixes
Pull request in esphome with YAML changes (if applicable):
Checklist:
I am merging into
nextbecause this is new documentation that has a matching pull-request in esphome as linked above.or
I am merging into
currentbecause this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.Link added in
/components/index.rstwhen creating new documents for new components or cookbook.New Component Images
If you are adding a new component to ESPHome, you can automatically generate a standardized black and white component name image for the documentation.
To generate a component image:
Comment on this pull request with the following command, replacing
COMPONENT_NAMEwith your component name in UPPER_CASE format with underscores (e.g.,BME280,SHT3X,DALLAS_TEMP):The ESPHome bot will respond with a downloadable ZIP file containing the SVG image.
Extract the SVG file and place it in the
images/folder of this repository.Use the image in your component's index table entry in
/components/index.rst.Example: For a component called "DHT22 Temperature Sensor", use: