Hello, I’ve bought a [SparkFun Qwiic Pro Micro - USB-C which I’ve wired up as required for the [TMK ADB to USB keyboard converter. However, I can’t get dfu-programmer to load the TMK firmware to test it out. I know the Pro Micro is working, because the Arduino IDE can see it and upload code to it which runs (e.g. I can make the RX and TX lights flash). I can get the Pro Micro into DFU mode by double-tapping the reset button, and have confirmed this is working by using the Arduino Serial Monitor. However, when I put the Pro Micro in DFU mode and try to erase the memory contents using dfu-programmer so I can upload a TMK .hex file, I get the following error (immediately):
It appears that dfu-programmer doesn’t know where to find the device, because it’s clearly present as seen by the Arduino software, and by the presence of /dev/cu.usbmodem2101 and /dev/tty.usbmodem2101 (and it appears in System Profiler as being attached to the USB bus). Does anyone know how I can instruct dfu-programmer to find the Pro Micro? Or some way I can interact with the boot loader on the command line? It works fine with the Arduino IDE, but I need to be able to upload compiled .hex files. I’m using MacOS 12.3.1. Any help would be greatly appreciated!](tmk_keyboard/converter/adb_usb at master · tmk/tmk_keyboard · GitHub)](SparkFun Qwiic Pro Micro - USB-C (ATmega32U4))
Try using it on another device (PC/linux) if available to see if the OS is the issue
-if it works with a non-Mac device, try re-installing the legacy USB drivers per these instructions https://community.silabs.com/s/question … anguage=ko , or similar roll-back/upgrade to get the system and peripherals talking to one another
Hi @TS-Russell, thanks very much for getting back to me! I found out from another forum that dfu-programmer was unlikely to work with the Caterina bootloader used by the Pro Micro. But the most recent release of QMK Toolbox also wasn’t recognising my Pro Micro, and it should support it. The Arduino IDE works fine, but I want to be able to easily upload my own binary .hex files, hence trying to get QMK Toolbox working.
I don’t have a PC available and installing Linux on my Mac would have taken too much time at the moment, but that suggestion did make me think that I should try my old Intel-based Mac in case the issue was somehow related to the ARM-based M1 chip in my current MacBook Pro. I downloaded QMK Toolbox to my 2013 MacBook Air, and it successfully recognised the Pro Micro in DFU mode.
With the knowledge that my Pro Micro should work with QMK Toolbox, I went back to my M1 MacBook Pro. I tried a few things (removing quarantine xattrs from QMK Toolbox, running it under Rosetta) that didn’t work. Then I thought I’d download the latest beta and see if that somehow had a fix, and… it worked! I’ve had a look through the GitHub issues for QMK Toolbox, and I can’t see anything that specifically addresses the problem I was having, but possibly it is this one: [[macOS] Add libhidapi #357.
