-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to use serial to connect pc to Pi #17
Comments
The GPIO 14 (UART TXD) is the only pin which goes high at power on and low at power off. If you check the issues, others have used different pins but they have to write a script to make the GPIO high and hold the power button down until the Pi is booted. |
There are a number of pins that boot to HIGH. e.g. for rpi0 BCM2835 Arm Peripherals 6.2 Alternative function assignments indicates the pins that go high at power on are: So these pins should be able to be substituted for UART. Obviously some of these pins have other functions that you may not want to interfere with so it's up to you to pick which one works. I am using pin 5 at the moment and I don't have to hold the power button down for it to start up. But there is another change necessary to ensure that the pin goes low on power down, here I used the power-off dtoverlay. This worked for me - hope it helps. |
There are other pins which boot to high but they don't go high straight away and stay high until the end of shutdown as far as I know? |
I should have mentioned this is using the RC power up/power down circuit. The RC response gives enough time for the pin to go high. The dtoverlay ensures the pin goes low to disable power at the end of shutdown. |
@karlahaiat See "A Simple Press (no hold) Power Up Version" here: Power-up/power down |
(Re: @jsinkers <https://github.com/jsinkers> I was able to get this to
shutdown with other pins, but am not able to get it to turn on again, did
you do anything special to make this work?)
@karlahaiat did you select one of the pins that goes high when the rpi
starts up? See for example my response here
#17 (comment)
What pin are you using? What behaviour are you seeing when you press the
button? Are you using the RC circuit? Please add some more info
…On Tue, 30 Jul 2019 at 02:19, karlahaiat ***@***.***> wrote:
@jsinkers <https://github.com/jsinkers> I was able to get this to
shutdown with other pins, but am not able to get it to turn on again, did
you do anything special to make this work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17?email_source=notifications&email_token=ABX2PQB2R23HUCTYXZ2F42DQB4J7JA5CNFSM4DCZCJMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3BHGBY#issuecomment-516059911>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABX2PQAXT3HTWADZYTOUAS3QB4J7JANCNFSM4DCZCJMA>
.
|
Do I need to use the UART pins on the raspberry for the LiPoPi to work? I need to access the serial port on my pi zero to communicate between Pi and pc, can I use some other gpio.
The text was updated successfully, but these errors were encountered: