11-07-2016, 10:16 AM
(11-07-2016, 10:03 AM)Artyom Wrote:(11-07-2016, 08:50 AM)MarkHaysHarris777 Wrote: Actually , the default state of the gpio pins on the Raspberry PI are 'input' , which is 'correct' logic.
The pine board is not consistent in this regard. It may be possible to set the default state in dts|dtb , but I have not looked into it yet seriously; although , I am not at all hopeful.
If you choose your pins carefully , and provide secondary buffering , you can work around the problem.
Good evening. You certainly are right, but I'm not looking for a solution to the problem only for me. I wish to attract the attention of the community to solve the problem for everyone.
(emphasis mine) Yes, I understand that; and thank you.
This is one of those little details that needs to be taken into account for the next generation of pine board; whatever that may be.
In short, as a requirement, all gpio pins 'must' conform to logical 'inputs' throughout the power-up boot cycle.
It should be noted that in some use cases the pine board is useless as a controller unless the previous requirement is met.
Thanks again for your input, I agree whole heartedly.
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! )