</code></pre><p>or just:</p><pre><code>$ sudo make <keyboard>:<keymap>:flash
</code></pre><p>Note that running <code>make</code> with <code>sudo</code> is generally <em><strong>not</strong></em> a good idea, and you should use one of the former methods, if possible.</p><h3id="linux-udev-rules"tabindex="-1">Linux <code>udev</code> Rules <aclass="header-anchor"href="#linux-udev-rules"aria-label="Permalink to "Linux `udev` Rules {#linux-udev-rules}""></a></h3><p>On Linux, you'll need proper privileges to communicate with the bootloader device. You can either use <code>sudo</code> when flashing firmware (not recommended), or place <ahref="https://github.com/qmk/qmk_firmware/tree/master/util/udev/50-qmk.rules"target="_blank"rel="noreferrer">this file</a> into <code>/etc/udev/rules.d/</code>.</p><p>Once added, run the following:</p><divclass="language- vp-adaptive-theme"><buttontitle="Copy Code"class="copy"></button><spanclass="lang"></span><preclass="shiki shiki-themes github-light github-dark vp-code"><code><spanclass="line"><span>sudo udevadm control --reload-rules</span></span>
<spanclass="line"><span>sudo udevadm trigger</span></span></code></pre></div><p><strong>Note:</strong> With older versions of ModemManager (< 1.12), filtering only works when not in strict mode. The following commands can update that setting:</p><divclass="language- vp-adaptive-theme"><buttontitle="Copy Code"class="copy"></button><spanclass="lang"></span><preclass="shiki shiki-themes github-light github-dark vp-code"><code><spanclass="line"><span>printf '[Service]\nExecStart=\nExecStart=/usr/sbin/ModemManager --filter-policy=default' | sudo tee /etc/systemd/system/ModemManager.service.d/policy.conf</span></span>
<spanclass="line"><span>sudo systemctl restart ModemManager</span></span></code></pre></div><h3id="serial-device-is-not-detected-in-bootloader-mode-on-linux"tabindex="-1">Serial device is not detected in bootloader mode on Linux <aclass="header-anchor"href="#serial-device-is-not-detected-in-bootloader-mode-on-linux"aria-label="Permalink to "Serial device is not detected in bootloader mode on Linux""></a></h3><p>Make sure your kernel has appropriate support for your device. If your device uses USB ACM, such as Pro Micro (Atmega32u4), make sure to include <code>CONFIG_USB_ACM=y</code>. Other devices may require <code>USB_SERIAL</code> and any of its sub options.</p><h2id="unknown-device-for-dfu-bootloader"tabindex="-1">Unknown Device for DFU Bootloader <aclass="header-anchor"href="#unknown-device-for-dfu-bootloader"aria-label="Permalink to "Unknown Device for DFU Bootloader""></a></h2><p>Issues encountered when flashing keyboards on Windows are most often due to having the wrong drivers installed for the bootloader, or none at all.</p><p>Re-running the QMK installation script (<code>./util/qmk_install.sh</code> from the <code>qmk_firmware</code> directory in MSYS2 or WSL) or reinstalling the QMK Toolbox may fix the issue. Alternatively, you can download and run the <ahref="https://github.com/qmk/qmk_driver_installer"target="_blank"rel="noreferrer"><code>qmk_driver_installer</code></a> package manually.</p><p>If that doesn't work, then you may need to download and run Zadig. See <ahref="./driver_installation_zadig">Bootloader Driver Installation with Zadig</a> for more detailed information.</p><h2id="usb-vid-and-pid"tabindex="-1">USB VID and PID <aclass="header-anchor"href="#usb-vid-and-pid"aria-label="Permalink to "USB VID and PID""></a></h2><p>You can use any ID you want with editing <code>config.h</code>. Using any presumably unused ID will be no problem in fact except for very low chance of collision with other product.</p><p>Most boards in QMK use <code>0xFEED</code> as the vendor ID. You should look through other keyboards to make sure you pick a unique Product ID.</p><p>Also see this. <ahref="https://github.com/tmk/tmk_keyboard/issues/150"target="_blank"rel="noreferrer">https://github.com/tmk/tmk_keyboard/issues/150</a></p><p>You can buy a really unique VID:PID here. I don't think you need this for personal use.</p><ul><li><ahref="https://www.obdev.at/products/vusb/license.html"target="_blank"rel="noreferrer">https://www.obdev.at/products/vusb/license.html</a></li><li><ahref="https://www.mcselec.com/index.php?page=shop.product_details&flypage=shop.flypage&product_id=92&option=com_phpshop&Itemid=1"target="_blank"rel="noreferrer">https://www.mcselec.com/index.php?page=shop.product_details&flypage=shop.flypage&product_id=92&option=com_phpshop&Itemid=1</a></li></ul><h3id="i-just-flashed-my-keyboard-and-it-does-nothing-keypresses-don-t-register-it-s-also-arm-rev6-planck-clueboard-60-hs60v2-etc-feb-2019"tabindex="-1">I just flashed my keyboard and it does nothing/keypresses don't register - it's also ARM (rev6 planck, clueboard 60, hs60v2, etc...) (Feb 2019) <aclass="header-anchor"href="#i-just-flashed-my-keyboard-and-it-does-nothing-keypresses-don-t-register-it-s-also-arm-rev6-planck-clueboard-60-hs60v2-etc-feb-2019"aria-label="Permalink to "I just flashed my keyboard and it does nothing/keypresses don't register - it's also ARM (rev6 planck, clueboard 60, hs60v2, etc...) (Feb 2019)""></a></h3><p>Due to how EEPROM works on ARM based chips, saved settings may no longer be valid. This affects the default layers, and <em>may</em>, under certain circumstances we are still figuring out, make the keyboard unusable. Resetting the EEPROM will correct this.</p><p><ahref="https://cdn.discordapp.com/attachments/473506116718952450/539284620861243409/planck_rev6_default.bin"target="_blank"rel="noreferrer">Planck rev6 reset EEPROM</a> can be used to force an eeprom reset. After flashing this
