OpenStickCommunity / OpenStickCommunity/GP2040-CE
Addons with migrated GPIO do not correctly update Pin Mapping
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.5k
- Forks
- 666
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 7
Description
It seems that with the new Pin Mapping functionality to allow multiple actions per pin, GPIO migration does not properly occur from previous versions.
To repro, assume an upgrade to #1216 and attempt the following.
- Start with release 0.7.10
- Enable the Tilt addon, and set Tilt 1 to a free GPIO pin. All other values can remain at their defaults.
- Save & Restart
- Update to build #1216
Expectation:
A GpioAction::ANALOG_DIRECTION_MOD_LOW definition should be assigned in Pin Mapping to the Pin previously defined in Tilt 1.
Issue:
The Pin in Pin Mapping remains GpioAction::ASSIGNED_TO_ADDON and cannot be unassigned. The previous value in the addon itself is not updated in the proto data.
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
Reproduce the migration from release 0.7.10 to build #1216 with the Tilt addon and a configured Tilt 1 GPIO. Start by tracing GPIO migration into the Pin Mapping and proto data, focusing on the expected GpioAction::ANALOG_DIRECTION_MOD_LOW assignment. Done means the migrated pin is assignable and the previous addon value is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100