Click to view our Accessibility Statement or contact us with accessibility-related questions
Just got a brand new `DROP + OLKB PREONIC KEYBOARD MX KIT V3`. Put everything together and flash it using `QMK Toolbox 0.0.21` with `.bin` file configured using `preonic/rev3` with layout `LAYOUT_ortho_5x12`. The flash finished successfully without any error: ``` *** STM32 DFU device connected (WinUSB): STMicroelectronics STM32 BOOTLOADER (0483:DF11:2200) *** Attempting to flash, please don't remove device >>> dfu-util.exe -a 0 -d 0483:DF11 -s 0x08000000:leave -D "E:\Downloads\preonic_rev3_sphs_preonic_v3.bin"   dfu-util 0.9       Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.   Copyright 2010-2016 Tormod Volden and Stefan Schmidt   This program is Free Software and has ABSOLUTELY NO WARRANTY     Please report bugs to http://sourceforge.net/p/dfu-util/tickets/       Opening DFU capable USB device...   ID 0483:df11   Run-time device DFU version 011a   Claiming USB DFU Interface...   Setting Alternate Setting #0 ...   Determining device status: state = dfuERROR, status = 10   dfuERROR, clearing status   Determining device status: state = dfuIDLE, status = 0   dfuIDLE, continuing   DFU mode device DFU version 011a   Device returned transfer size 2048   DfuSe interface name: "Internal Flash "   Downloading to address = 0x08000000, size = 55048       Download [             ]  0%      0 bytes   Download [             ]  3%     2048 bytes   Download [=            ]  7%     4096 bytes   Download [==            ] 11%     6144 bytes   Download [===           ] 14%     8192 bytes   Download [====           ] 18%    10240 bytes   Download [=====          ] 22%    12288 bytes   Download [======          ] 26%    14336 bytes   Download [=======         ] 29%    16384 bytes   Download [========         ] 33%    18432 bytes   Download [=========        ] 37%    20480 bytes   Download [==========        ] 40%    22528 bytes   Download [===========       ] 44%    24576 bytes   Download [============       ] 48%    26624 bytes   Download [=============      ] 52%    28672 bytes   Download [==============      ] 59%    32768 bytes   Download [===============     ] 63%    34816 bytes   Download [================     ] 66%    36864 bytes   Download [=================    ] 70%    38912 bytes   Download [==================    ] 74%    40960 bytes   Download [===================   ] 78%    43008 bytes   Download [====================   ] 81%    45056 bytes   Download [=====================  ] 85%    47104 bytes   Download [======================  ] 89%    49152 bytes   Download [======================= ] 93%    51200 bytes   Download [======================== ] 96%    53248 bytes   Download [=========================] 100%    55048 bytes   Download done.   File downloaded successfully   Transitioning to dfuMANIFEST state *** STM32 DFU device disconnected (WinUSB): STMicroelectronics STM32 BOOTLOADER (0483:DF11:2200) *** HID console connected: OLKB Preonic (FEED:6061:0003) ``` Right after flash, the keyboard becomes unresponsive with random keycode spamming non-stop. After investigation, it looks like every time the keyboard is connected, it constantly sends signals of all the keystrokes from the first column and the 7th column. As a result, either the entire keyboard becomes unresponsive or the first and 7th column becomes unresponsive while other column working as expected (this usually happens after an OS reboot without unplugging the keyboard. Unplugging and replugging the keyboard will render the entire keyboard unresponsive again). I've tried flashing with a default bin file, or flash it with several older version of QMK Toolbox, but no luck so far. Please any help would be greatly appreciated as the keyboard is not usable at all at the moment, nor can it be restored to a factory setting...
brucecantarim
1
Mar 22, 2021
pingshunhuangalexThat's too bad! Haven't tried to flash mine yet, just assembled it this weekend. You were using Windows, right? Have you already tried to reinstall the qmk tool? Might be worth a shot. I would also try to change the usb port or cable, hopefully that works. I'll probably try to flash mine next weekend, I wanna move some keys around too.
brucecantarimYeah, I'm using Win10. The issue is the compilation using the latest QMK Firmware (through GUI configurator or code), not the QMK Toolbox for flashing. Let me know if you run into similar issues. If you do, what I got so far is you can flash this super old bin file (https://docs.qmk.fm/#/faq_build?id=i-just-flashed-my-keyboard-and-it-does-nothingkeypresses-dont-register-its-also-arm-rev6-planck-clueboard-60-hs60v2-etc-feb-2019) to get things back to factory settings so you won't get stuck with a pretty brick. It's not ideal for me cuz I don't use QWERTY, still asking around in various places. The issue is raised here: https://github.com/qmk/qmk_firmware/issues/12308
(Edited)
erickongThanks for the reply. That's exactly what I did. Also tried to build from the code directly. Anyways, most likely due to a faulty PCB. Already proceed with a refund. Thanks.
pingshunhuangalexThis is due to a faulty PCB. Everything works like a charm now with a replacement.
kec-h
1
May 4, 2021
pingshunhuangalexDo you find out in the end how to resolve this? I am experience a similar problem but with the 4th column from the left. Pressing on any key in the 4th column triggers all keys there. I've been looking online a lot and cannot figure out how to resolve it. :-/
kec-h
1
May 4, 2021
pingshunhuangalexDid you find out how to resolve it? I am experience a similar problem but with the 5th column from the left. Pressing any key on this column triggers all keys to be fired. I have been looking online a lot but still cannot find any solution. :-(
PRODUCTS YOU MAY LIKE
Trending Posts in Mechanical Keyboards