I’m trying to nail down various hardware modules we’re going to need for our blueprints (starting with the door lock) so we can procure them locally and use them across blueprints.
I’ve done a first draft for the Door Lock and now I need a review before I go further.
Please review Reference HW 1st and 2nd choice and see if you approve (especially if you are the blueprint owner).
Then please look at the HW and SW scope (common, v1 and v2) proposals.
Common are features used across blueprints
v1 are features to be delivered for Jasmine
v2 are stretch-goal for Jasmine and probably enhancements to the blueprints in Jasmine+1
This way we can constrain what functionality we will deliver for the blueprint. Remember the goal is NOT to deliver an end product, but a technology demonstration of the Jasmine stack (OTA, networking, security and applications that implement core blueprint functionality).
You can comment in the sheet directly or in a thread here. I am working on the other blueprints this week.
Right now RPi4 is the initial implementation goal for the OTA stack, most likely followed by the Avenger (broad availability and u-boot test platform). Can you please remind me if B68 is the x86 board or the IMX board? While a stretch, it might be interesting to have an x86 board there to cover all the boot-loader cases.
Thanks, so without too much foresight from my side, we have a very solid set of devices for the OTA stack, that should be more or less representative of what we can expect to find in the wild! Nice
