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: Hardware abstraction #29

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

Design review: Hardware abstraction #29

krook opened this issue Jul 8, 2021 · 0 comments

Comments

@krook
Copy link
Member

krook commented Jul 8, 2021

Implement code in a way to abstract specific components so they can be replaced as needed and to support a larger range of component types.

It is common in product lifecycles to experience changes to hardware, especially changing sensors and even processors. This is especially true in times of global supply chain crises, as is the case with semiconductor shortages at the present time.

It is a significant risk to be bottlenecked into a particular sensor, sensor family/series, or processor. To that end, the firmware should be designed with hardware abstraction in mind. Minimal, if any, application firmware should be written which references specific implementations of sensors or processors. All core functionality should be implemented through hardware abstraction layers so that changes can be made safely in the future without the risk of complication.

@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