Hey guys, I tried to flash my Model F with QMK Toolbox, which appears to be the preferred method, after making a new .hex keymap with the dev version of QMK configurator. I hit reset (Fn + Space + R) and flashed it, and it disconnected at the end of the process as expected. When I tried to reconnect though, I get nothing – no recognition that the keyboard has been plugged in from either of my Windows computers, and the keyboard itself doesn’t type anything. I can’t seem to get it into bootloader mode again either, to attempt the flash again. Can this be saved, or do I need to open up the back of the keyboard and reset the controller?
I really don’t want to have to because I don’t have any torx heads on hand so I have to grab and twist each screw out with a set of pliers to remove the back plate, and there are a lot of screws.
Solved! Thank you, Joe! Resetting PROG does not return the keyboard to any default keymap, but rather erases the stored keymap, meaning the keyboard won’t magically start typing after you hit reset. As the answer indicates, please have a software like QMK Toolbox or the Windows Device Manager open for visual verification that a plugged-in device has entered bootloader mode.
As noted by two folks on the Deskthority forum thread:
“You need to short the PROG pads while plugging the device in. You need to find something low resistance to short the PROG pads with. You might think that a screwdriver is gonna be enough, but due to surface oxidation it is likely not gonna be good enough. I like to use sharp metal tweezers, because they can dig into the pad a little bit, breaking up the surface oxidation, and I can actually be sure it’s shorting. Apply constant strong pressure on the pads while plugging in the keyboard to make sure they’re perfectly shorted.
I’ve personally had the best success using a paperclip that’s first been completely unwound/straightened, and then folded in half. Take the two ends, make sure they are both making good contact with the pad opposite the other, then plug in the USB cable into the computer. I like to do this while QMK Toolbox is running so that I can clearly see that it has worked & the controller has connected up to the computer in bootloader mode, and if it hasn’t, I can then try again immediately”
Thank you! This did it. The piece of the puzzle I’d been missing was that shorting PROG doesn’t return it to the default keymap, making it appear as the keyboard was still dead (ie: not typing anything). I probably shorted PROG successfully a few times repeatedly, but I should have had QMK Toolbox for a visual indication that the keyboard entered bootloader mode. I appreciate you finding this information for me, actually bothering to have the software up for immediate feedback instead of guesswork is something that I failed to realize. Thank you so much for your assistance and continuing to reply even though it didn’t seem like it was getting anywhere.