Setting DXL_PWR GPIO pin while a binary is running in the NUC results to a freeze that needs a power cycle to fix
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Hypothesised to be because the NUC is drawing more current due to operation and setting a GPIO pin causes a catastrophic voltage dip that results to a need to power cycle the whole robot to get it to be responsive again.
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 reproducing the freeze on the NUC while a binary is running and DXL_PWR GPIO is set. Compare the robot's behavior before and after the GPIO change, including whether a power cycle is required. Done means the cause is identified and a verified fix or mitigation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100