Skip to content
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

CM3 shutdown doesn't kill +5V USB power. #31

Open
markatlnk opened this issue Apr 27, 2022 · 5 comments
Open

CM3 shutdown doesn't kill +5V USB power. #31

markatlnk opened this issue Apr 27, 2022 · 5 comments

Comments

@markatlnk
Copy link

I don't believe it affects other CPU modules, just the Compute Module 3.

It looks like it shuts down, but the USB is still powered and it is pulling about 43mA from the batteries. After shutting down, if I take out the batteries and put them back in, current drops to 60uA closer to what I would expect.

Posting this on Discord, looks like other have also had this issue.

@cuu
Copy link
Contributor

cuu commented May 6, 2022

how about sudo halt -p ?

@markatlnk
Copy link
Author

markatlnk commented May 6, 2022

The power button doesn't close it down and shutdown -h now doesn't either. The -P option is the default and shuts down every other pi I own. I only noticed this when I had an arduino plugged in and its lights were still blinking when I shut down the system. I had noticed several times when I pulled it out of my bag after a few days that the batteries were dead. Always thought something pushed the power button in my bag. Shutdown is actually part of systemctl and I attempted a few options with that also. So far the only thing that works is momentary removal of batteries. Just a second or two will do it. The halt command is also just a link to systemctl.

@markatlnk
Copy link
Author

I finally got time to look into this. Looking at the schematic of the power section, R107 and R108 create a divider that feeds pin 11 of the SY7215 part. Starting then turning off the system, I went to measure the voltage on the junction of R107 and R108. This caused the system to shut down. Found that odd, so I tacked a 1 Meg resistor on top of R108 to drop the 100K value just a bit. The meter should be about 10M so thought this would do it, it didn't. I next reduced R108 down to 68K by putting in parallel a 220K resistor. This resolved the problem and the system now shuts down as expected.

@andrwj
Copy link

andrwj commented Sep 16, 2022

Then this problem is caused by hardware problem, can ClockworkPi show some guidelines to appy to CM3 DevTerm?

@markatlnk
Copy link
Author

Yes it is a hardware problem, but a minor one that can be resolved with changing the value of one resistor. These parts are really small so you do need a bit of experience with that. I teach Electrical Engineering and just happen to have a full SMT rework setup on my bench so it wasn't that difficult for me to do that. Because I wanted to lower the resistance of the value on the board, I chose to not remove the old part and just stick another part directly on top of it. It can be done with a microscope and a really fine tipped soldering iron. Make sure you use a drop of flux on there and if you use the no-clean type, you can just leave it. For those with better eyes than mine, you might get by with one of those magnifying glasses. Hope that helps. I think they used 0402 parts, which is way smaller than I typically work with, so I actually tacked an 0805 part off one side and a really tiny wire to connect the other side. Bit of a kludge, but it is still working just fine. The device can sit for weeks without any battery drain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants