Closed l0-0t closed 3 years ago
I fixed that on my Zero Pi.
The problem was that self.power.on() enables LED power, but the LEDs have two 10uF caps wired in parallel. So, when the LED power gets turned on, these two caps start charging (while the LEDs turn on as well) - thus (momentarily) overloading the Zero Pi (W)'s board 5V supply rails. In my case that happened even if I used a 2A 5V power supply to power my Zero Pi. Unlike Zero Pi, the power-beefier Raspberry Pi 4B has no problem with LED power switching on.
The fix is to remove R34 and turn on LED power permanently on by soldering the Q2 FET gate to 5V as shown.
Oh my thank you so much. With what I achieved it at least worked out connecting the boards with cables besides the 5v powerrails and powering them separately over differend powersupplys or like that in my last attempt over an usb hub with one cut off usb cable per board. I will try this later and hopefully I can close this issue then and there.
So I did as you said and finally it actually works. again thank you so much now I am able to close this issue.
So as cburghardt already stated in his issue #163 I am also unable to run any sorts of test codes from multiple repositories. They all trace back to the following code lines: self.power = LED(5) self.power.on() after which the Pi chrashes and reboots. any ideas what could cause this behavior?