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”
Try following the firmware update video precisely step by step, including the pandrew utility and using Atmel flip. Not sure what QMK configurator you are using but you need the one specific to Model F keyboards linked to in the manual – the regular QMK project does not work with Model F.
Hey, sorry. I was under the impression that my keyboard was a QMK configurator model. “Option 2: QMK […] The QMK configurator has been preinstalled on hundreds of new Model F keyboards starting in mid-2020.” Mine was manufacturer stamped with August 2020, so I assumed it’d be loaded already. My mistake.
I used the direct IP link starting with 35.164 to access the beta/dev version of QMK Config that has the F-77 keymap available.
I did not use the Pandrew utility, in my morning stupor I simply pressed the key combination for reset and then for bootloader, Fn + Space + R then LShift + RShift + B, and used QMK toolbox to flash based on “Option 2: QMK”, “As of August 2021, it is suggested by pandrew to use the QMK Toolbox program to flash firmware on Apple/Mac computers.” I’m not a bright spark, so this to me just meant “yeah, QMK Toolbox will work”.
I think we’re past the point where I can retry the steps with an unresponsive keyboard, since it doesn’t even connect when plugged into my computer. Should I just short PROG on the xwhatsit controller and try the instructions again?
Comments seem to be broken so the comment I’d typed has vanished. In short, I followed everything to the best of my ability given that I’d just woken up and my brain wasn’t in gear yet.
I used the QMK Configurator linked directly by IP: 35:164.28.200:5000
I did not use the pandrew utility and entered bootloader through the key combo for reset. I used QMK Toolbox, which was recommended for Mac devices because in my muddled mind at the time I just assumed it worked for both Mac and Windows.
However, I think we’re past that point because I am unable to get a reaction from my computer when plugging in my keyboard and I genuinely think it’s bricked. Do I need to short PROG on the physical controller?
Comments seem to be broken so the comment I’d typed has vanished. In short, I followed everything to the best of my ability given that I’d just woken up and my brain wasn’t in gear yet. I used the QMK Configurator linked directly by IP: 35:164.28.200:5000. I did not use the pandrew utility and entered bootloader through the key combo for reset. I used QMK Toolbox, which was recommended for Mac devices because in my muddled mind at the time I just assumed it worked for both Mac and Windows. However, I think we’re past that point because I am unable to get a reaction from my computer when plugging in my keyboard and I genuinely think it’s bricked. Do I need to short PROG on the physical controller?
The keyboard may already be in bootloader mode (if so, it would say ATMEGA32 DFU in device manager, at least on Windows) – in that case you would use the atmel flip utility on windows to load the firmware. I am not familiar with other OSes so I recommend using Windows if you can have access to such a machine.
Under no circumstance would I recommend using anything but the correct torx bit – otherwise you will damage the keyboard case.
Unfortunately I have no idea what was done here so I can’t be of much help but as a last resort shorting PROG will work as these controllers cannot be bricked permanently to my knowledge.
Did you use the f77/wcass or f62/wcass selection in the QMK beta site? This is what is shown in the instructional firmware video. If you selected another option it may have resulted in what you are seeing.
Thanks for these tips, I will go back over my steps tonight. And sorry about commenting 3x, I just assumed due to a serious delay my comments didn’t arrive.
To the best of my memory I did use the wcass layout. I really appreciate the support, and if all else fails I’ll go buy a set of torx bits and open the back to short PROG.
I mistakenly used the /universal version as I didn’t catch the instruction to use the /wcass version, and I think that was the actual problem since QMK Toolbox still recognized and flashed my keyboard despite the fact that I should have used Atmel Flip.
I don’t see anything in Device Manager or the Control Panel’s Devices & Printers.
Shorting PROG didn’t seem to do anything, I’ve followed the instructions to hold it, plug in, and then remove the short quickly with a lot of different pieces of metal (including a spoon) to rule out the possibility that I might have been using a coated paperclip that won’t short.
Neither Atmel Flip nor the Pandrew utility can detect my keyboard.
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.