Hi,
Can't see a similar issue; I've had an L3V7 turn up today. Works great, except for one specific, but very important to my use case, scenario.
If the pi is rebooted via sudo reboot, or if the WittyPi boots the pi due to auto-on when 5v is connected, the power is cut to the board - not a graceful shutdown - after 10s or so.
If the pi is booted using the button on the WittyPi, this doesn't happen.
I've tweaked the GPIO4 timer to 25 as I'm running a 12" DSI display on the same feed to no effect. The fact the pi boots fine on a button press doesn't leave me convinced this is the problem.
I don't think there's any logs from the WittyPi in wittyPi.log during the bad boots. I'm wondering if this is a communication problem?
Anyway, any advice would be appreciated, this is for a rear view mirror display that i want to shutdown and start with the vehicle so I'm a bit stuffed if it dies shortly after auto boot.
Thanks.
It's actually a lot longer than 10s, about 37s when I just timed it from turning on the usb supply to power being cut. Just after reaching desktop and my camera streams opening.
Have you upgraded your Raspberry Pi OS after installing Witty Pi's software?
The Raspberry Pi OS recently moves "/boot/config.txt" to "/boot/firmware/config.txt". The new installation script for Witty Pi has taken this into account, but if you prevously installed Witty Pi software and then upgrade your OS, this could cause the serial port doesn't get configured correctly and similar issue could happen.
If the serial port configuration gets modified manually or by other software, it could lead to similar issue too.
You may run "gpio readall" to confirm if the serial port (TXD, RXD) is correctly configured.
If serial port is not correctly configured, download the new installation script and install Witty Pi software again should fix the problem.
@admin Hi, thanks for the prompt assist. This does seem to be working now. Was a fresh install. I uninstalled the wittypi software and reinstalled and it seems to be working.
Spoke too soon!
Same problem, just now it takes about 10 mins.