Shared docs: update description of Release vs. Development builds#108
Conversation
Signed-off-by: Moritz Barsnick <moritz.barsnick@chargebyte.com>
This was never valid for EVerest builds. Even the newly provided "Release" builds are signed with the devel key, and their symbolic link reflects this correctly. Signed-off-by: Moritz Barsnick <moritz.barsnick@chargebyte.com>
| developer or release image. In order to update the firmware with a chargebyte EVerest developer | ||
| image, the developer key must be set in the :code:`"/etc/rauc"` directory to pass the internal | ||
| validation process of the RAUC firmware update mechanism. The image type can be identified by the | ||
| file name. |
There was a problem hiding this comment.
Please keep this section for the rare cases of Truffle to EVerest migration.
There was a problem hiding this comment.
You're right; that's important hint if you're updating from the legacy Truffle stack. However, EVerest uses the developer key for both image types (release and developer). Therefore, the text should be updated accordingly so that customers don't mistakenly reconfigure the key when using the EVerest release image.
There was a problem hiding this comment.
Maybe this note should be directly described in section "Updating from chargebyte’s proprietary charging stack to EVerest-based charging stack"
There was a problem hiding this comment.
I agree with Fabian. This only ever applies to Charge Control C, as the other platforms never had a legacy stack, and EVerest builds always (for the time being) use the development signing key.
I propose to keep this change, and modify CCC in #109.
There was a problem hiding this comment.
I'm fine with the suggestion
mhei
left a comment
mhei
left a comment
There was a problem hiding this comment.
well... not sure, how important the upgrade path Truffle -> EVerest still is... no strong opinion for this... LGTM otherwise
5 participants
Also drop the rauc keyring section, it was never useful for EVerest builds.