-
Notifications
You must be signed in to change notification settings - Fork 37
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
PINOUTS DEFAULT AND ON/OFF COMMANDS #18
Comments
There aren't any default pins set up. You need to run the config utility by typing:
it will ask you questions about how many D-pads + buttons you have, then it will have you press each one in turn and watch the pins to configure it. Turning the pi on/off. I suggest connecting your power button to pin 5 (GPIO 03). This pin can be used to power on the raspberry pi without any code. To get it to turn off the pi, you need to use the config utility and on the first screen, select the option Commands, then follow the prompts. To turn off the raspberry pi, enter the command:
then you should be good to go |
THANKS MAN! YOU ARE GREAT! -
At that moment I am also dedicating myself to creating a VGA666 CONVERTER based on the GERT666 schematics. Thank you very much for your attention!
Enviado do Outlook<http://aka.ms/weboutlook>
…________________________________
De: mholgatem <notifications@github.com>
Enviado: domingo, 16 de setembro de 2018 23:22:41
Para: mholgatem/GPIOnext
Cc: andrellvs; Author
Assunto: Re: [mholgatem/GPIOnext] PINOUTS DEFAULT AND ON/OFF COMMANDS (#18)
Closed #18<#18>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#18 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AcgxaJ8F0SzHBtGYOUZAd9aakq-vPhuGks5ubwdxgaJpZM4We2NI>.
|
Nice! That sounds like a fun project! |
mholgatem, hello how are you? Greetings here from BRAZIL!
First of all, I would like to thank you. His project solved an old problem of the RETROPIE, in relation to the GPIO.
I would like you to clarify two issues that I believe have been misunderstood in GITHUB:
It would be very interesting a video of you on this. But I would be grateful if you answer here too.
The text was updated successfully, but these errors were encountered: