This is a dependency that is not in the Debian repository, but it is easy to build it.
Requires cmake and libusb-1.0-0-dev, from the Debian repository.
Get the source code:
git clone https://github.com/WestberryTech/wb32-dfu-updater/From the wb32-dfu-updater directory, run:
cmake -DCMAKE_BUILD_TYPE=Release \
-DLIBUSB_INCLUDE_DIRS=/usr/include/libusb-1.0 \
-DLIBUSB_LIBRARIES=/usr/lib/x86_64-linux-gnu/libusb-1.0.so
cmake --build .This tells cmake where to find the libusb libraries and headers installed by apt.
Then create a symlink somewhere that’s in my path, to the built binary in ./bin/Linux_64_Release/wb32-dfu-updater_cli
Requires qmk, from the Debian repository.
If necessary, clone your copy of qmk:
git clone https://github.com/qmk/qmk_firmwareNow make sure you have qmk submodules available in your copy of qmk_firmware, because qmk will need some of them to build this firmware. From the qmk_firmware directory:
qmk git-submoduleFirst, identify the keyboard, by connecting the keyboard while holding down the Escape key.
ls -l /dev/bus/usb/00*There should be at least one directory listed, with files in it. Each file refers to a connected USB device. The keyboard is probably the highest number.
To make sure, disconnect the keyboard, and connect it again while holding down Escape. You should observe that one of the numbers has incremented by one. This is the number that refers to your keyboard. With that, you can make it writable so that you can flash it.
In the example below, the keyboard was 001/033 the last time I plugged it in, so I run the command below to make it writable:
sudo chmod o+w /dev/bus/usb/001/033Now flash your firmware. From the qmk_firmware directory:
qmk flash -kb inland/mk47 -km defaultReplace default with the name of your keymap, if you made
one.