- Device Pairing
- — High-end —
- — YDKB(BLE Series) —
- — YDKB(Other) —
At present, a few of YDKB's keyboards use this bootloader, which does not need third-party driver(it uses the system's default HIDUSB driver).
The ydkbs-reflash tool calls HIDBootFlash.exe. reference: http://vusb.wikidot.com/project:hidbootflash
Source code for BootHID commandline: https://github.com/yangdigi/BootHID/tree/master/commandline
When the firmware works well, generally press and hold the top-left button on the keyboard and meanwhile insert the USB data cable. Then, drag the hex file of the firmware to ydkbs-reflash.exe, and the firmware will automatically start to refresh. The keyboard will restart when the reflash is complete.
You can also manually use HIDBootFlash.exe in the bin directory of the flashing tool. It needs VS2005SP1.
Visual Studio 2005 (VC++ 8.0) SP1
Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update
The interface for opening the software is as follows:
Proceed as follows:
Use the above source code to compile the bootloadHID. Then,
1 chmod 755 bootloadHID 2 brew install libusb-compat 3 ./bootloadHID
If there is no error description here, it is right.
When you want to reflash the firmware, use
./bootloadHID -r hex_path
As the picture below, the reflash is complete with the end address of 0x7c00. The error that appears at the end can be ignored.
Here to talk about possible problems if you can't reflash. The latest reflash tool has added a function to detect if the driver is wrong.
1.Use zadig (download url: http://zadig.akeo.ie), select “list all” in the option, and then let the keyboard enter the flash mode. Check if the USB ID is 16C0 05DF, and the driver is HidUsb. This setting may display the name HIDBoot or just a USB input device. In short, the USB ID is the one below.
The two pictures above are all driven normally. If the display here is not HidUSB, for example, it may be:
This driver is wrong and must be uninstalled.
Also remove the device driver when uninstalling
After uninstalling, go to zadig and check if the driver is restored to HidUsb. If not, refresh the device manager and continue uninstalling (for example, if the winusb or libusb driver is installed multiple times, it will need to be uninstalled multiple times).