Skip to content
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

Design review: Field device management #28

Open
krook opened this issue Jul 8, 2021 · 0 comments
Open

Design review: Field device management #28

krook opened this issue Jul 8, 2021 · 0 comments

Comments

@krook
Copy link
Member

krook commented Jul 8, 2021

Implement a plan to support existing devices in the field with new versions.

It is common that devices already deployed to customers will require updates for new functionality, bug fixes, device improvements, or security patches. It is critical that these updates are able to be deployed in the field, by a customer. Otherwise, support of the product over its lifetime becomes difficult.

It is recommended that a secure bootloader is included, such as mcuboot, and a device management layer (such as mcumgr) which allows transport of new firmware images should be included in the application firmware. The transport protocol would ideally be Bluetooth since the device is already expected to connect to a mobile phone through this interface. This interface can also be used to download log files or retrieve device statistics.

@krook krook added the firmware label Jul 8, 2021
@krook krook added this to To do in Pyrrha Development via automation Jul 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

1 participant