-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help getting NUC123 in bootloader mode #1
Comments
nu-isp-cli is designed with no specific hardware in mind. so technically this issue is off-topic. 0416:0123 is the VID:PID pair for when Ducky One2Mini is functioning as a keyboard. specifying that in the command-line is clearly wrong operation. nu-isp-cli do not come with means to put devices into boot-loader mode. You have to manually put your keyboard in to boot-loader mode somehow.
Here "boot" is referring to the action powering your keyboard, in other words the action connecting a USB cable to it. Then your keyboard in boot-loader mode should show up as 0416:3F00 . In case of Linux like system, be aware of permissions of the device file. that is, take care of udev rules OR run with root privilege. |
Thanks for the response. I've already added the relevant udev rules like specified in the readme, and the only thing I seem to be missing is getting the board into bootloader mode. |
Might be a bit late, but I get my Ducky One 2 Mini RGB (dkon2061st) into bootloader (ISP mode) by holding D while I plug in the USB cable. You know it's in bootloader mode since the backlight isn't running and the keys aren't working. |
I'm trying to flash my Ducky One 2 Mini keyboard using the instructions here, but I can't seem to get it in bootloader mode. I'm using Linux (NixOS if it matters).
I manage to get the board to freeze if I run
nu-isp-cli 0416:0123 info
, but trying to flash after doing that doesn't do anything, and replugging the board makes it work like before.Sometimes I get this error
or this one
Is there some library I've left out while building the program?
The text was updated successfully, but these errors were encountered: