Green light of death with Pro Micro clone

I wanted to build a split keyboard, so bought two chinese clones like this Arduino Pro Micro - Deskthority wiki and flashed them using qmk toolbox (it installed some drivers) GitHub - qmk/qmk_toolbox: A Toolbox companion for QMK Firmware After a few tries I got one fully working and the other one is bricked. The green led is always on and win10 does not react on this board at all, and the board doesn't react on resetting. I installed Arduino IDE but on my PC it's useless - com ports are hidden in the device manager, so the port option is grayed out (ch34x drivers doesn't help). Tried 4 USB cables, all usb 2.0 ports with no luck.

Then I tried to connect it to another PC and got an error 43 (windows can't recognize the device). I installed Arduino IDE (it has a port option), tried to upload the default sketch with "Arduino Micro" in the options, got output like this https://i.imgur.com/tIZRaWF.png with three leds on (green and 2 reds), but after reconnecting it was still the green with error 43.
I installed the sparkfun boards settings and after uploading default sketch with 5v/16MHz option there are no "3 leds on" now, just green, and double reset is not working (?) - pro micro disconnects after the first one.

Is it completely bricked? (I don't have a programmer)

Do you know whether your boards are the "5V" version or the "3.3V" version? I have seen some reports of people having problems like this from uploading a sketch compiled for the 5V 16 MHz, when they have a board running at 8 MHz.

Get a programmer. I use the USBasp Version 2. Others use a Arduino Uno.

I googled it, saw a post saying that J1 doesn't mean anything, and if you have 16Mhz crystal it's 5v/16Mhz (if it's not sparkfun I think), 99% mine is the 5v version. And my problems with this micro started before flashing with 5v/16Mhz option.

I can get another micro for the price, so I don't know if I need one. And I read that I can use another arduino (my second micro) to burn a bootloader (but not found an exact guide, unfortunately).

Found the problem. It was AMD's troubled bios, flashed to the latest with agesa 1.0.0.2 and now the port is available.
upd. Or maybe it was just the default bios settings. There is an option "Super IO Configuration" where you can enable/disable com port.

1 Like

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.