Firmware, Faliures during Setup Must Not Block, Set an Error Flag, Errors Reported in "i" command
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
_A clear and concise description of what the problem is. Ex. I'm always frustrated when Setup() code testing hardware blocks the rest of setup when a test fails.
Describe the solution you'd like
A clear and concise description of what you want to happen.
For example the program pattern of going to a while(1) {;} should instead set an error flag?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the firmware Setup() code and the handler for the "i" command. Trace how hardware-test failures currently block setup, including any while(1) loop, and determine where an error flag can be retained and reported. Done means setup continues after a failure and the "i" command reports the recorded error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100