-
Notifications
You must be signed in to change notification settings - Fork 16
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
Progress on flashing #51
Comments
By default if there is a single led defined in the device tree it will toggle it on start of provisioning and when done. cmprovision/resources/views/scriptexecute.blade.php Lines 107 to 119 in f19ceec
Naturally, if you use a different board design and want other GPIOs than usual for leds, you must alter the device tree accordingly so the led maps to the right GPIO, and toss the device tree (overlay) files and config.txt modification in /var/lib/cmprovision/scriptexecute If you want to take shortcuts, and access GPIOs directly instead of writing a device tree file for your board, you can do so as well, but then you will need to use shell commands that work with the /sys gpio interface instead of convenience programs like "raspi-gpio" that do not exist in Linux distributions other than RPI OS. Among the lines of:
(untested) |
Hello,
I'm trying to work out if I can turn an LED on when a board is being flashed and turn it off when it has finished. I was thinking of using the pre and post install scripts and raspi-gpio configure a gpio to output and drive it high/low with the scripts.
I think that the pre/post install scripts are run on the target RPi however a simple command of raspi-gpio set 17 OP dh in the script doesn't work. Is it possible for the pre install scripts to access the GPIO hardware or am I limited to file operations alone.
If that is the case then where on the provisioner code is the area that controls the flashing please? I can then look at hooking lights up to the provisioner RPi to detail that something is being flashed.
Thanks.
Cheers,
Neil
The text was updated successfully, but these errors were encountered: