Reserve Hobgoblin device #3
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
glopesdev
requested review from
Poofjunior,
artursilva0,
bruno-f-cruz and
filcarv
filcarv
approved these changes
May 24, 2025
artursilva0
approved these changes
May 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR reserves the WhoAmI for the Hobgoblin device.
The Hobgoblin is a simple multi-purpose device built on the Harp
core.picowith a special focus on learning the basics of the Harp standard. The goal is to provide an extremely affordable and accessible board to be used in courses and as an overall introduction to Harp and Bonsai as discussed in https://github.com/orgs/harp-tech/discussions/108.The reason why the WhoAmI is reserved in the smallest byte range (< 256) is to possibly allow in the future a differentiated validation for devices such as this one who are explicitly expected to be heavily modified and polymorphic (i.e. having multiple
device.ymlspecifications). I will clarify better what I mean with this differentiated validation in a separate proposal.No need to merge now, but I wanted to open the PR so that people are aware of the idea re. this WhoAmI range.