08-15-2017, 02:24 AM
(08-08-2017, 06:20 PM)pfeerick Wrote: My point the whole time as been simply that... if you export the pin, and it says that it's state is currently x, then it should damn well be x. not y, or z... x. The Raspberry Pi folks know that is what should be the case, so they made sure it was. Otherwise, the pin should have have a 'indeterminate' state, so that you know it hasn't been set yet.
My 4K R64 board came in yesterday ; so I played with it most of the night, found that it does NOT have this issue. If the pin is exported its direction is set IN, the active_low is set 0 and its value is set "1". If the pin is grounded than the value changes to "0".
So we need to get to the bottom of it; is it a dts|dtb issue, a hardware issue with the PineA64+, or a build issue ( something inconsistent with export somehow ).
marcushh777 
please join us for a chat @ irc.pine64.xyz:6667 or ssl irc.pine64.xyz:6697
( I regret that I am not able to respond to personal messages; let's meet on irc! )
please join us for a chat @ irc.pine64.xyz:6667 or ssl irc.pine64.xyz:6697
( I regret that I am not able to respond to personal messages; let's meet on irc! )
