Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Existing designs cannot add GPIO drivers externally
See original GitHub issue#1130 Before writing the driver, I refer to the implementation of the existing driver. Due to the protection of some keywords, I cannot call the internal methods of UnixDriver outside the System.Device.Gpio package.
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Additional power supply for circuits controlled by GPIO
Hi,. RaspbJan wrote: Could you tell me pls some general rules about connecting external current sources to circuits controlled by raspberry GPIO ......
Read more >Add GPIO Peripherals to a Block Design
This will add the IP to your design, and connect it to an external port, which will not require any further work to...
Read more >Gpio state can't be changed when connected to a DC ...
I tested it on two different raspberry pi's, breadboards, libraries(pi4j and rpi.gpio), exchanged cables and reinstalled raspbian, the problem ...
Read more >GPIO Driver Interface
Inside a GPIO driver, individual GPIO lines are identified by their hardware ... If this state can not be configured in hardware, i.e....
Read more >Adding GPIO functionality to a Linux desktop computer
I have recently been using some low powered "CPU Onboard" (Intel) linux system in the mITX form factor for audio work.
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 Free
Top 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
True, creating “forwarding drivers” (drivers that use other drivers) is not possible right now due to protection levels.
@joperezr This could only be solved by changing all the methods on GpioDriver to public, I suppose. Since that’s not what we generally want, I currently see little possibility of fixing this. The use case is valid, though, as we actually do the very same internally already.
I basically agree as well, but we have to consider the risk that people start using the drivers directly, for which they’re not intended. There must be some protection against directly working with the drivers.