The Raspberry Pi Thread

So you are not seeing any LED glowing, right?

Does it have micro USB or type C? Maybe that port is faulty?
Its type c
Well when I insert the charging plug in the type c socket I can see an utterly faint red light for a split second but nothing afterwards, if I do the same after a few minutes I can see the faint red light.


It seems the aukey adaptor might have sent more current to it but it was working fine for more tha. 2 years and suddenly one day it stopped.
 
Its type c
Well when I insert the charging plug in the type c socket I can see an utterly faint red light for a split second but nothing afterwards, if I do the same after a few minutes I can see the faint red light.


It seems the aukey adaptor might have sent more current to it but it was working fine for more tha. 2 years and suddenly one day it stopped.
Try to pull out the type-C pin ever so slightly.
 
It seems the aukey adaptor might have sent more current to it but it was working fine for more tha. 2 years and suddenly one day it stopped.
Current is delivered by order. Adapter can't force it. If you overvolt the pi only then more current will flow through it.

See if it works any different with different adapter and cable.
Or dip the type c pin in alcohol and insert/pull out of the pi socket like 30 times. That should clean the contacts.
 
Tried
I can say every time when the charger pin is inserted in the charging socket the faint red light blinks once and that's it.
The same happened to one of my friend's pi 3b some years back and it was working fine after pulling the usb 2.0 pin slightly outward. Just a litttttle bit.
If that is not working then try to clean both pin and port.
 
Spent a few hours setting up an old USB webcam I had lying around with my Raspberry Pi as a security camera. It took some time to get everything right, but in the end I was able to view live feed over local network. I can easily make this available on the Internet using Tailscale.

Searching for something like this returns a lot of results which use Motion. However, the Motion project is not seeing active development and there are a lot of issues. I spent a couple of hours trying and failing with Motion before looking for alternatives.

I found Zoneminder, which is an excellent application. It's not noob-friendly though, requires some patience and at least some experience with Linux to set it up.

Zoneminder comes with the ability to stream and record video, motion detection, alerts, etc. There are a lot of settings which I haven't explored yet since I was already exhausted by the time I got it working.
 
Its type c
Well when I insert the charging plug in the type c socket I can see an utterly faint red light for a split second but nothing afterwards, if I do the same after a few minutes I can see the faint red light.


It seems the aukey adaptor might have sent more current to it but it was working fine for more tha. 2 years and suddenly one day it stopped.
I seem to recall reading that the board has a hardware design issue that leads adapters to incorrectly identify the device type. It therefore supplies it with more power than 5V, blowing the power supply. Other times, it completely fails to power the board.
 
I seem to recall reading that the board has a hardware design issue that leads adapters to incorrectly identify the device type. It therefore supplies it with more power than 5V, blowing the power supply. Other times, it completely fails to power the board.
Any way to get it fixed???
 
Any way to get it fixed???
I think it was fixed in boards manufactured later on, but if you have one of the earlier ones, only way to be safe is to use the official power supply.

It's because of USB C works. Devices on both end need to correctly identify the capabilities of the device on the other end. This doesn't happen properly in the Pi 4.

From https://www.tomshardware.com/news/raspberry-pi-4-usb-c-update

The problem had to do with the Pi 4's USB Type-C port, which it uses to receive power. The way that the port was constructed meant that it would not work with high-speed, "e-marked" cables. We tested a wide number of cables to see which would work, but found that most cables did not have any issues.

In short, if you have a USB 3.1 5 or 10 Gbps cable, chances are that it it is "electronically marked" while USB 2.0 cables are just fine. The high-speed cables require two pull down resistors (see resistor color codes) on the Type-C port, because they use two lines to talk to the system. The original Pi 4 had only one resistor so these cables won't work with it. Considering that the Pi 4's USB-C port is only usable for charging, chances are that you wouldn't want to use a high-speed data cable with it anyway.

However, if you just happen to have high-speed USB Type-C cables lying around, you will now be able to use them to power your Raspberry Pi 4, if you have one of the newly-revised units that are selling now.
 
Any way to get it fixed???
You may have attempted fixes such as using a different adapter/cable (the official one as mentioned above by @gourav), reflashing a corrupted eeprom, booting without any peripherals connected, and so on.

If none of them worked, it's most likely fried and needs professional intervention.
 
1674130263724.png
 
One can only hope you understand the difference between a Pi and a desktop.
There is, but he's right. Lots of refurbished tiny PCs in the market from Dell/Lenovo around 10-12k. They will outperform the Pi at not a significantly larger footprint. And x86 will give you more choices on terms of software you can run on it.
 
Back
Top