[SL-UP] Add OTA Support for series3 #94
Merged
Conversation
This file contains 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
jmartinez-silabs
added
the
sl-up
mkardous-silabs
approved these changes
Nov 11, 2024
selissia
reviewed
Nov 11, 2024
selissia
approved these changes
Nov 11, 2024
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.
The implementation of the Series 3 bootloader OTA API differs from that of Series 2. It utilizes an RTOS thread-safe mechanism, so it can't be wrapped in critical sections like Series 2.
Currently, the Secure element is not thread safe in series3, so, during bootloader ota API calls, the thread stack must be locked.
Also, at the moment, Some OTA process steps on series 3 are slow, and leave the device unresponsive to other task. Add some traces and small osDelay to provide some form of feedback to the user that the device is "working". This is temporary.
Dev notes:
For CMP, Zigbee must be locked to but we don't have this possibility currently.
The Secure element thread safeness will probably be fixed before Zigbee provide us with a locking mechanism so we will see for release.