Sebastian Perez - @jay | nullbits I have been h...
@jay | nullbits I have been having trouble entering into bootloader mode on my Nibble and was hoping you could help. Whenever I hit the physical reset button while I have the QMK toolbox open I hear the keyboard disconnecting and connecting on windows, I see it too on the console. But it does not go into flashing mode. I have tried shorting it on the back of the pcb, I have tried every combination of keypresses I could find online, but no luck as of yet. I am starting to read online that it could be due to the usb c cable but I dont want to go buy new ones if i dont have to. I would really appreciate any help with this!
13 Replies
A few questions!
What MCU did you use? Is it Atmega or RP2040?
Did you flash the firmware originally? Do you know if you flashed a VIA firmware? If so, you can bind the “RESET” key to something which will put the board into the bootloader.
Thank you for the quick response!
Its an Atmega (ATmega32U4)
It was a while ago but I belive I flashed some precompiled firmware from the Nullbits website
I have used the browser VIA configurator to rebind some of my keys. Is that what you are refering to?
Ok i have managed to use VIA to rebind one of my keys to "RESET", however when I do flash the firmware I get this error:
dfu-programmer: no device present.
dfu-programmer.exe atmega32u4 flash --force "C:\Users\Seb\Downloads\nullbitsco_nibble_oled_bongocat.hex" dfu-programmer: no device present. dfu-programmer.exe atmega32u4 reset dfu-programmer: no device present.None of my keys work either until I hit that physical reset switch
Alright, it sounds like you're in the programming mode then. That's good. Does the device show up in QMK toolbox? You might need to install the right drivers with QMK or Zadig. That tends to be the issue with with symptoms like these.
My QMK toolbox looks a bit different than in some of the videos ive seen. Do you mean in a little dropdown? or in the console?
USB device connected (HidUsb): (Standard system devices) USB Input Device (6E61:6060:0001)
USB device connected (HidUsb): (Standard system devices) USB Input Device (6E61:6060:0001)
USB device connected (HidUsb): (Standard system devices) USB Input Device (6E61:6060:0001)
USB device connected (usbccgp): (Standard USB Host Controller) USB Composite Device (6E61:6060:0001)
As for the drivers, I have let it install a few times already
interesting, so it looks like your board is entering DFU mode but not showing up in toolbox
I'd say change cable/port, but if the board itself works when not in flashing mode it's likely not that. Do you have another PC you could try?
This is what I'd recommend: https://github.com/qmk/qmk_firmware/blob/master/docs/driver_installation_zadig.md
GitHub
qmk_firmware/docs/driver_installationzadig.md at master · qmk/qmk...
Open-source keyboard firmware for Atmel AVR and Arm USB families - qmk/qmk_firmware
QMK toolbox should show a message in yellow text like
*** Atmel DFU device connected (Libusba): Atmel Corp. ATmega32U4 (03€8:2FF4:0000) when it detects the board in DFU mode. If you're not getting that, it's most likely a driver issue.Thank you, I’ll try that when I get home today.
@jay | nullbits I have not touched Zadig yet but noticed that when I hit the "Reset" button on QMK tool box this message appears: Atmel DFU device connected (WinUSB): Atmel Corp. ATm32U4DFU (03EB:2FF4:0000)
Which is different to what you sent which had "Libusba" instead of "WinUSB" Should it be "Libusba"?
The driver will vary. Follow the guide before we dig further.
I reinstalled the correct drivers with Zadig but am still getting this on Toolbox:
Atmel DFU device connected (WinUSB): Atmel Corp. ATm32U4DFU (03EB:2FF4:0000)
Attempting to flash, please don't remove device
dfu-programmer.exe atmega32u4 erase --force dfu-programmer: no device present. dfu-programmer.exe atmega32u4 flash --force "C:\Users\Seb\Downloads\nullbitsco_nibble_oled_bongocat.hex" dfu-programmer: no device present. dfu-programmer.exe atmega32u4 reset dfu-programmer: no device present.Flash complete
Hmm. Interesting. Can you try one of the other drivers? IIRC on my windows PC I have libusb0 or maybe libusbK
the only other thing I can recommend is trying a different USB cable/port and if all else fails...a different PC.
It worked! I had to change it to driver :libusb-win32 (v1.2.7.3)
Thanks so much for all your help!
AWESOME! I had a feeling that's what was up. Thanks for your patience -- that took some back and forth for sure 👍