Charging not working- 180w charger Framework 16

Windows 11
BIOS 3.0.2
Have gpu
180w charger
Only usb a and one usb c cards

Frequently cannot charge the framework.
Sometimes i can charge after removing AC power from the charger and plugging it back in. Other times not. All my other usb c PD cables either don’t work, or charge for 5 seconds, then stop, then charge for 5 more seconds, then stop.
Factory cable charges for awhile, but then stops and my battery dies.
If i use the back left port, i get some success, but if i use the back right slot, Windows reports that usb port doesn’t support charging, even though it worked a week ago.

Ive tried reseating the usb c card, moving it around, and using a different card. Rebooting has no effect other than sometimes making it stop charging if was already working.

Sorry to hear that you are experiencing this issue, do you think this issue is related to the expansion port, expansion card or the adapter?

I strongly suggest contacting the support team since they can help you troubleshoot this issue.

Thanks!

Sorry to hear about your charging not working on your FW16 machine. Do you have another USBC charger to try? I was impressed that the little 30W USBC PD charger that came with my Pixel 7 charges both the FW13 and FW16.

Definitely contact support to help them work with you. You might need to reset the Mainboard if something is going on with the Embedded Controller that is shutting down the charging and which ports it is allowing.

Let us know how it turns out. If the other charger works like a charm then the 180W might just be out of spec/not talking correctly and the laptop is shutting it down to protect itself.

Were you able to get this working? My framework is also having trouble accepting charge from anything higher than about a ~60W charger

Guys,
See my comment here and check if it works for you:

My bet is that there is a bug on the EC firmware that get triggered from time to time whatever the charger/cable used.

1 Like

Holding the power button until the laptop reset fixed the charging issue for me.

2 Likes

I see a bunch of such issue all over the places. Here, reddit and other forum. I can’t always answer everywhere and help everyone unfortunately.

Is this being investigated at Framework ?

This seem to be really related to an EC bug. It would be nice to have some official feedback or recognition about this. I couldnt find anything in the FAQ or any official KB.

I still need to do this trick at least 1 time every one/two month or so while using different charger (official one at home, various 65w/100w docking stations at work)
cc @Destroya @Matt_Hartley

Just in case, here are some info that might help:
FW16 batch1 here on Fedora40 fully updated, kernel 6.10.x and also testing the 6.11.0-RCx line.

Has anyone figured this out? I was having the same issue and now it won’t power on at all.

And a USB C expansion module is being used in Slot 1, 2, 4, or 5 for charging?

Also @amoun posted in another thread that you may be able to resolve by performaing a mainboard reset:

I was going to create a new post, but I saw this one, and it is almost the exact same issue I am experiencing, so I’m going to bump this thread and piggyback on it.

I have a 13 (Windows 11, 13th gen Intel) and it began to intermittently charge, then stopped altogether. I have two chargers, and two USB-C cards. Right side won’t recognize any USB devices, left side will read media but not charge. Updated BIOS, drivers, and reset the mainboard with no change. Can charge by bypassing the EC. Rebooting by long pressing the power button will restore charging functionality, but only for a few minutes.

Hi @jiminyspigot,

Someone just had a similar issue with I think a FW13 13th gen machine. His was data only on the right side but no charging.

If you have time and the parts try this:

Try powering the mainboard by itself outside of the laptop. Ideally you would have a HDMI/Display port plugged into one of the other expansion slots and a USB keyboard.

In his case, there was something strange with the battery connector that was causing his issue, he got it to boot stand-alone and when it was all put back together it all started working again correctly. Worth a shot! (Be sure to ground yourself and rest the board on something nonconductive like a piece of paper or cardboard)

1 Like

Thank you! I’ll definitely make the time to do that later this week.

By chance, was this resolved in a different post in the forum, and if so, do you happen to have the link to it?

Found it! :white_check_mark:

Here is hoping it is a similar fix! :grin: