Running SysFsDriverTests or RaspberryPiDriverTests causes PWM to be unusable
See original GitHub issueAfter running SysFsDriverTests or RaspberryPiDriverTests PWM no longer works.
I have 100% repro: If I run PWM tests in a loop or run LibGpiodDriverTests everything works without any issues.
If I run SysFS or RPI3 GPIO tests once after that PWM becomes completely unusable and stops reacting to any changes (regardless if using PWM manually through /sys/class/pwm/
or our APIs) - PI has to be rebooted.
Found during testing https://github.com/dotnet/iot/pull/758
I’m currently on latest from master and my PI3 is running Raspbian after sudo apt-get update
and sudo apt-get upgrade
(was reproing before updates as well).
I’ll try to further isolate the problem if I have time.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
API Suggestion for Low-Level GPIO Drivers · Issue #809
This leads to two main topics: ... Running SysFsDriverTests or RaspberryPiDriverTests causes PWM to be unusable #874.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The reason for your problem is #857. You need to reset the pin to PWM mode after some other test has set it to in or out.
Fixed with #1128.