My MCU died.. again, and twice!

[seluranen]

Hi there!

I'm afraid I'm back again from Issue #161... This time with the same problem, but with a catch.

Brief introduction: With the 5 boards per order I built 2 cheapinos, one for work, one for home. Great! Both had the same vial code, and where used in different computers (my PC at home, my laptop at work). Issue #161 happened with my "work-pino" one year and a half in as my daily keyboard. Ended replacing the MCU, everything worked perfectly again... till today, 4 months after.

Not as weird as the last time, this time 3 keys stopped working no matter what. It's not terrible, still have some RP2040's left from last time, but seems strange that this happened so soon.

The catch this time is, as I'm in the middle of a huge work crunch, I just took my "home-pino" to work hoping to change the MCU once the deadline was over. And, surprise motherf*** (Dexter meme reference), 3 days later my "home-pino"'s MCU bricked heavily (more keys died, not the same ones).
At this point my "home-pino" was almost 2 years old, with no problems.

It all could be just a coincidence, but seems really strange to me. So, Hoping there's a pattern behind it, I'm writing a list of the thing I can recall that have changed (and may have a slight connection to this):

• Before Issue 3 keys "stopped" working #161:
  - Updated my original VIAL code from, no macros. no tap dance's, less layers, to the current one, with macros, tap dances and more layers.
  - This update was only done in my "work-pino"
  - Moved to another office (doesn't seem really related, but who knows... bad energy?)
  - Changed my USB docker and connected to a different USB (A) port
  - Started using Moonlight to control 2 computer from my laptop

• Issue 3 keys "stopped" working #161 happened
  - Replaced MCU in "work-pino" worked well
  - Used my "home-pino" with my work laptop at home as I was working remotely several days (Christmas), no issues here. My "home-pino"'s VIAL was still the old one at this point.

• My "work-pino" bricked 4 months in (this issue)
  - Removed the MCU and put it back again (had to try...): more keys stopped working
  - Bring my "home-pino" to work as an emergency
  - Updated my "home-pino"'s VIAL to the current one
  - 3 days later it bricked (more and different keys)
  - Started crying.

With all this Inputs seem that my current VIAL code is the culprit, but... is this a thing? Could it harm the hardware? And if so, why 4 months for one and 3 days for the other?
Maybe it's and office-ambient related thing... Or maybe are just my cheap-as-possible rp2040...

Any clues? If there's a way, I'd like to change the MCUs knowing they will last as much as possible.

Thank you very much!

P.S: Please help, It feels really weird and slow to write with current keyboards now!

[tompi]

Hey. I dont think this is fw related. New work you say? My bet is on static elevtricity at your new work. Carpets?

[tompi]

Is your pc connected properly grounded?

[seluranen]

Oh! Now you say...
Before we moved to the new office I checked all electrical fixtures, and there were several of them with no ground connected. We asked the office owner to fix them (along several LAN port failing) and it was suposedly fixed. But now you said it, I never actually check it! Tomorrow I'll make a test.

My USB-C docker is feeded throught a power brick, I know voltage is regulated throught it. Ground also? Or it does nothing to it?

Also, all my pins (from the MCU and all the back hotswappable thingies) are free open. Would it be worth to cover them?

Thankyou very much. I'll keep you updated

No carpets by the way.

[tompi]

BTW, a case should help prevent ESD damage, so worth testing out!

I have yet to zap any of my rp2040-zeros, but my son recently did(after 2+ years....), and his was also caseless...

[seluranen]

Well, I couldn't check for ground because I don't have the tester in the office (what I do have are lousy co-workers who forgot where they put the stuff one they took it...), but checking the office plan, my socket was not one of the groundless.

I'll check again whenever (if-ever) i get my socket tester back, but I'm thinking this may no be the issue.

Talking with my coworkers however, most agree that they get a lot o ESD zaps all the time, with no apparent reason. I myself get zapped every time I touch the whiteboard. So I'm assuming this would be the problem.

What is causing so much static in the new office is a different kettle of fish altogether (apparently this is something in English XD), and a new concern for me.

So, I'm changing the MCU and heavily casing my keyboard and, hopefully, not opening new issues in the near future.

Thank you again for your time