Hi,
i have a Zero2Go Rev2 and want to use it with a Raspberry Pi 4. I am running DietPi as OS.
I installed unzip as this isn't preinstalled on DietPi. Then i followed the install instructions from the manual and everything was installed well.
I got no errors. However after the Pi booted the Z2Go cuts power after about 4 seconds. No shutdown, just boom power cut!
I have verified the Zero2Go with RaspberryPiOS. No problems everything works as expected.
Now i am wondering what is the difference. My project relies on DietPi so i have to get this working.
What can i do? Might there be a package missing or something?
For information:
- I am powering the Z2G from official raspberry pi power supply for the pi 5 via USB-C input
- 1-Wire interface is disabled
- When disabling the daemon i can run the Zero2Go.sh script and make settings and read voltages
- No low voltage threshold set
- Step-Down engine always-on is activated
If disabling the daemon can avoid such power cut, most probably it is due to the GPIO tool - the WiringPi utility named "gpio".
The latest version of Zero2Go software uses WiringPi ( https://github.com/WiringPi/WiringPi/ )
The installation script may not properly install it on DietPi.
The deamon.sh may incorrectly "detect" the GPIO-4 falling and shutdown the device. However this will still be a graceful shutdown, instead of direct power cut.
As far as I know, press and hold the button (or keep pulling down GPIO-4) may cause direct power cut.
Thanks for the quick reply.
I installed latest version of wiringpi from the wiring pi github repository.
I then verified installation with gpio -v and it shows V 3.16
I tried running the daemon.sh file manualy. You can see on the picture.
After that the pi went black and also LED of zero2go instantly turned off.
I am here with new information.
I have tinkered a little bit and found that i can trigger zero2go to cut power when doing
gpio -g mode 17 out gpio -g write 17 1
that is the $SYSUP_PIN and is also what caused the issue when the daemon is running.
Before the detection of falling edge on pin 4 $HALT_PIN there are these lines that signals the system is up.
If i comment out the shutdown lines and these lines the daemon is waiting on the falling edge as expected.
Why does the sysup signaling causes a power cut?
@rschwa The related source code is here:
If TxD pin is at low level when SYS_UP signal arrives, the turningOff flag will be set and power cut will be performed after a delay.
With default configuration in Raspberry Pi OS, the TxD pin should be at high level after boot up. Maybe it is not the case for DietPi.
That's it! I got it working now.
With gpio readall i could see the TxD was indeed low after boot.
For people with the same problem:
What i dit
dietpi-config -> advanced options -> Bluetooth [Off] dietpi-config -> advanced options -> Serial/UART -> ttys0 console [Off] dietpi-config -> advanced options -> Serial/UART -> ttys0 (mini UART) device [On]
Then reboot.
Thank you very much for your help!