Change Store AWS IoT Private Key and Certificate in SPI Flash avoiding device-specific compilations #6179
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.
Description:
Following discussion on #5860, the AWS IoT credentials (~800 bytes) are now moved from source code to SPI Flash in unused location in bank FF.
This means that you will not need to compile device-specific firmwares. The same AWS IoT enabled firmware can be used on multiple devices, and the credentials (Private Key and Certificate) can be loaded with the new
TLSKey
command.Added base64-1.1.1 Arduino library, used only when AWS IoT is enabled.
Code impact: +500 bytes when AWS IoT is enabled. No impact on standard firmware.
Related issue (if applicable): fixes #5860
Checklist:
only 2.4.2 and 2.5.2