Am 11.03.19 um 14:16 schrieb Guillaume Gardet:
I think it is because we use an upstream kernel which does not name it. I
guess this would not be too difficult to get it, but someone need to make the
patch and upstream it.
The missing names are not really a problem, as long as the mapping of
the line numbers is identical with the BCM/GPIO numbers (which is true,
as far as I understand your answer below).
Also the "led0" and other output-GPIOs do not match in their position.
It seems that there is a mismatch in the device tree and I think the
Tumbleweed kernel uses a generic .dts config file, whereas Raspian
uses an adapted one.
It should match just fine. On my RPi3 B, it does match.
On my RPi3B+ too.
First, I thought that my tries to test all GPIOs broke something, so no
GPIO did work until a reset, but...
I have updated this wiki page now to use '--mode=wait' option. Otherwise,
this tool set the GPIO to 1 and exit immediately and release the GPIO and
does not set it anymore and you will not notice that anything happened.
With wait mode, press ctrl-c to stop setting the value.
On Tumbleweed 20190308, with my RPi3 B, the following command just
works to set GPIO26 to 1 (3V3) :
gpioset --mode=wait gpiochip0 26=1
Could you test the '--mode=wait' option, please?
Tested right now on My RPi3B+, with the wait mode, it does work properly.
Yes, thanks, this did work! I have also tested some other GPIOs. The
option '--mode=wait' did help. So it just was a layer 8 problem...
Greetings and thanks again
Simon
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
