Skip to content
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

added oled display for payload select #162

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

added oled display for payload select #162

wants to merge 1 commit into from

Conversation

hahnstep
Copy link

I added a OLED display for payload select.
Article in German with picture is here:
http://stephanhahn.ch/post/P4wnP1-OLED-Bonnet-mod/
I will add a video soon.

btw: this is my first pull request ever

@Brisk4t
Copy link

Brisk4t commented Nov 10, 2017

Sweet, I can't try this right now but love the idea, makes it a lot more useful. Although makes it a little less inconspicuous. A more bash bunny-like device would have a switch instead of a menu.

@Swiftb0y
Copy link
Contributor

That's really useful, but I don't understand how this works exactly, since I can't read the code on my phone. Is this supposed to be used like a payload that overwrites the payload setting in the setup.cfg and reboots? And can you make a list with the number of compatible displays?

@Brisk4t
Copy link

Brisk4t commented Nov 10, 2017

From what I gather (not a lot), it does overwrite the setup.cfg file, but the oled should work with any raspberry pi compatible oled since the pins can be changed in the python code.

@Swiftb0y
Copy link
Contributor

This is already a pretty good starting point, but I would integrate this into to the startup service. So it pauses the boot process until a selection was made or a timer ran out. Similar to the behavior of GRUB. This could be turned on via setup.cfg. It should also provide some sort of fallback mechanism so that in case your script fails for some reason, the pi still continues to boot and doesn't "brick" itself.

I also have some suggestions for the overall architecture of P4wnP1:
For example, the setup.cfg should get split into a modular filebased structure in some kind of "config.d/" directory, which would make it easier for scripts to safely modify the global settings (like the payload).
The other suggestion would be some sort of preboot plugin system which would make modifications to the core like the one I suggested much easier, safer and P4wnP1 more modular.

It would also be nice if you could add some kind of API which would allow other payloads to make use of the screen more easily.

@hahnstep
Copy link
Author

Thanks for the feedback and ideas.
I currently working on a new modular design with support for more HATs.

@Swiftb0y
Copy link
Contributor

Thats cool. The more people work on the project, the less likely it will die someday. More hats are cool but keep in mind that they should be optional and a small physical footprint.

@kouki31
Copy link

kouki31 commented Jul 14, 2019

@kouki31
Copy link

kouki31 commented Jul 14, 2019

hello again i find a video Stéphane BeBoX i suposd its "hahnstep"
it use this https://www.amazon.fr/Waveshare-1-44inch-Interface-Direct-pluggable-Raspberry/dp/B07FJQ4F2C/ref=olp_product_details?_encoding=UTF8&me=&th=1
its oled and its better.
i buy 1 now.
tanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants