Testing your keyboard is usually pretty straightforward. Press every single key and make sure it sends the keys you expect. You can use QMK Configurator's test mode to check your keyboard, even if it doesn't run QMK.
You probably don't want to "brick" your keyboard, making it impossible to rewrite firmware onto it. Here are some of the parameters to show what things are (and likely aren't) too risky.
make dfu will erase the block, test the size (oops, wrong order!), which errors out, failing to flash the keyboard, leaving it in DFU mode. Linking: .build/planck_rev4_cbbrowne.elf [OK]\nCreating load file for Flash: .build/planck_rev4_cbbrowne.hex [OK]\n\nSize after:\n text data bss dec hex filename\n 0 22396 0 22396 577c planck_rev4_cbbrowne.hexFirst you have to compile firmware with the build option NKRO_ENABLE in Makefile.
Try Magic N command(LShift+RShift+N by default) when NKRO still doesn't work. You can use this command to toggle between NKRO and 6KRO mode temporarily. In some situations NKRO doesn't work and you will need to switch to 6KRO mode, in particular when you are in BIOS.
Without reset circuit you will have inconsistent result due to improper initialization of the hardware. See circuit schematic of TPM754:
Use 1UL<<16 instead of 1<<16 in read_cols() in [matrix.h] when your columns goes beyond 16.
In C 1 means one of [int] type which is [16 bit] in case of AVR, so you can't shift left more than 15. Thus, calculating 1<<16 will unexpectedly equal zero. To work around this, you have to use [unsigned long] type with 1UL.
You need to define EXTRAKEY_ENABLE in rules.mk to use them in QMK.
EXTRAKEY_ENABLE = yes # Audio control and System controlIn Windows check Allow this device to wake the computer setting in Power Management property tab of Device Manager. Also check your BIOS settings. Pressing any key during sleep should wake host.
Note that Arduino pin naming is different from actual chip. For example, Arduino pin D0 is not PD0. Check circuit with its schematics yourself.
Arduino Leonardo and micro have ATMega32U4 and can be used for TMK, though Arduino bootloader may be a problem.
By default, the JTAG debugging interface is disabled as soon as the keyboard starts up. JTAG-capable MCUs come from the factory with the JTAGEN fuse set, and it takes over certain pins of the MCU that the board may be using for the switch matrix, LEDs, etc.
If you would like to keep JTAG enabled, just add the following to your config.h:
#define NO_JTAG_DISABLESome problems can be fixed by switching from a USB 3.x port to a USB 2.0 port.
See here: https://geekhack.org/index.php?topic=14290.msg1884034#msg1884034
Some people reported their keyboard stops working in BIOS and/or after resume(power cycles).
As of now the root cause is not clear, but some build options seem to be related. In Makefile, try to disable options like CONSOLE_ENABLE, NKRO_ENABLE, SLEEP_LED_ENABLE and/or others.
More info:
', 41); const _hoisted_42 = [ _hoisted_1 ]; function _sfc_render(_ctx, _cache, $props, $setup, $data, $options) { return openBlock(), createElementBlock("div", null, _hoisted_42); } const faq_misc = /* @__PURE__ */ _export_sfc(_sfc_main, [["render", _sfc_render]]); export { __pageData, faq_misc as default };