[slave] Use the AL error field to inform master from failures
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 170
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
At the moment the slave stack does not handle the error code.
ie:
- Fail to switch state in ESM
- Fail to load EEPROM ?
Contributor guide
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 tracing the slave stack's state-transition and EEPROM failure paths, then inspect how the AL error field is currently represented and propagated. The work is done when failures such as ESM state-switch and EEPROM-load errors inform the master through that field.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100