You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

130 lines
6.3 KiB

  1. # Frequently Asked Build Questions
  2. This page covers questions about building QMK. If you haven't yet done so, you should read the [Build Environment Setup](getting_started_build_tools.md) and [Make Instructions](getting_started_make_guide.md) guides.
  3. ## Can't Program on Linux
  4. You will need proper permissions to operate a device. For Linux users, see the instructions regarding `udev` rules, below. If you have issues with `udev`, a work-around is to use the `sudo` command. If you are not familiar with this command, check its manual with `man sudo` or [see this webpage](https://linux.die.net/man/8/sudo).
  5. An example of using `sudo`, when your controller is ATMega32u4:
  6. $ sudo dfu-programmer atmega32u4 erase --force
  7. $ sudo dfu-programmer atmega32u4 flash your.hex
  8. $ sudo dfu-programmer atmega32u4 reset
  9. or just:
  10. $ sudo make <keyboard>:<keymap>:dfu
  11. Note that running `make` with `sudo` is generally *not* a good idea, and you should use one of the former methods, if possible.
  12. ### Linux `udev` Rules
  13. On Linux, you'll need proper privileges to access the MCU. You can either use
  14. `sudo` when flashing firmware, or place these files in `/etc/udev/rules.d/`.
  15. **/etc/udev/rules.d/50-atmel-dfu.rules:**
  16. ```
  17. # Atmel ATMega32U4
  18. SUBSYSTEMS=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2ff4", MODE:="0666"
  19. # Atmel USBKEY AT90USB1287
  20. SUBSYSTEMS=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2ffb", MODE:="0666"
  21. # Atmel ATMega32U2
  22. SUBSYSTEMS=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2ff0", MODE:="0666"
  23. ```
  24. **/etc/udev/rules.d/52-tmk-keyboard.rules:**
  25. ```
  26. # tmk keyboard products https://github.com/tmk/tmk_keyboard
  27. SUBSYSTEMS=="usb", ATTRS{idVendor}=="feed", MODE:="0666"
  28. ```
  29. ## Unknown Device for DFU Bootloader
  30. If you're using Windows to flash your keyboard, and you are running into issues, check the Device Manager. If you see an "Unknown Device" when the keyboard is in "bootloader mode", then you may have a driver issue.
  31. Re-running the installation script for MSYS2 may help (eg run `./util/qmk_install.sh` from MSYS2/WSL) or reinstalling the QMK Toolbox may fix the issue.
  32. If that doesn't work, then you may need to grab the [Zadig Utility](https://zadig.akeo.ie/). Download this, find the device in question, and select the `WinUS(libusb-1.0)` option, and hit "Reinstall driver". Once you've done that, try flashing your board, again.
  33. ## WINAVR is Obsolete
  34. It is no longer recommended and may cause some problem.
  35. See [TMK Issue #99](https://github.com/tmk/tmk_keyboard/issues/99).
  36. ## USB VID and PID
  37. You can use any ID you want with editing `config.h`. Using any presumably unused ID will be no problem in fact except for very low chance of collision with other product.
  38. Most boards in QMK use `0xFEED` as the vendor ID. You should look through other keyboards to make sure you pick a unique Product ID.
  39. Also see this.
  40. https://github.com/tmk/tmk_keyboard/issues/150
  41. You can buy a really unique VID:PID here. I don't think you need this for personal use.
  42. - http://www.obdev.at/products/vusb/license.html
  43. - http://www.mcselec.com/index.php?page=shop.product_details&flypage=shop.flypage&product_id=92&option=com_phpshop&Itemid=1
  44. ## Cortex: `cstddef: No such file or directory`
  45. GCC 4.8 of Ubuntu 14.04 had this problem and had to update to 4.9 with this PPA.
  46. https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded
  47. https://github.com/tmk/tmk_keyboard/issues/212
  48. https://github.com/tmk/tmk_keyboard/wiki/mbed-cortex-porting#compile-error-cstddef
  49. https://developer.mbed.org/forum/mbed/topic/5205/
  50. ## `clock_prescale_set` and `clock_div_1` Not Available
  51. Your toolchain is too old to support the MCU. For example WinAVR 20100110 doesn't support ATMega32u2.
  52. ```
  53. Compiling C: ../../tmk_core/protocol/lufa/lufa.c
  54. avr-gcc -c -mmcu=atmega32u2 -gdwarf-2 -DF_CPU=16000000UL -DINTERRUPT_CONTROL_ENDPOINT -DBOOTLOADER_SIZE=4096 -DF_USB=16000000UL -DARCH=ARCH_AVR8 -DUSB_DEVICE_ONLY -DUSE_FLASH_DESCRIPTORS -DUSE_STATIC_OPTIONS="(USB_DEVICE_OPT_FULLSPEED | USB_OPT_REG_ENABLED | USB_OPT_AUTO_PLL)" -DFIXED_CONTROL_ENDPOINT_SIZE=8 -DFIXED_NUM_CONFIGURATIONS=1 -DPROTOCOL_LUFA -DEXTRAKEY_ENABLE -DCONSOLE_ENABLE -DCOMMAND_ENABLE -DVERSION=unknown -Os -funsigned-char -funsigned-bitfields -ffunction-sections -fdata-sections -fno-inline-small-functions -fpack-struct -fshort-enums -fno-strict-aliasing -Wall -Wstrict-prototypes -Wa,-adhlns=obj_alps64/protocol/lufa/lufa.lst -I. -I../../tmk_core -I../../tmk_core/protocol/lufa -I../../tmk_core/protocol/lufa/LUFA-git -I../../tmk_core/common -std=gnu99 -include config.h -MMD -MP -MF .dep/obj_alps64_protocol_lufa_lufa.o.d ../../tmk_core/protocol/lufa/lufa.c -o obj_alps64/protocol/lufa/lufa.o
  55. ../../tmk_core/protocol/lufa/lufa.c: In function 'setup_mcu':
  56. ../../tmk_core/protocol/lufa/lufa.c:575: warning: implicit declaration of function 'clock_prescale_set'
  57. ../../tmk_core/protocol/lufa/lufa.c:575: error: 'clock_div_1' undeclared (first use in this function)
  58. ../../tmk_core/protocol/lufa/lufa.c:575: error: (Each undeclared identifier is reported only once
  59. ../../tmk_core/protocol/lufa/lufa.c:575: error: for each function it appears in.)
  60. make: *** [obj_alps64/protocol/lufa/lufa.o] Error 1
  61. ```
  62. ## BOOTLOADER_SIZE for AVR
  63. Note that Teensy2.0++ bootloader size is 2048byte. Some Makefiles may have wrong comment.
  64. ```
  65. # Boot Section Size in *bytes*
  66. # Teensy halfKay 512
  67. # Teensy++ halfKay 2048
  68. # Atmel DFU loader 4096 (TMK Alt Controller)
  69. # LUFA bootloader 4096
  70. # USBaspLoader 2048
  71. OPT_DEFS += -DBOOTLOADER_SIZE=2048
  72. ```
  73. ## `avr-gcc: internal compiler error: Abort trap: 6 (program cc1)` on MacOS
  74. This is an issue with updating on brew, causing symlinks that avr-gcc depend on getting mangled.
  75. The solution is to remove and reinstall all affected modules.
  76. ```
  77. brew rm avr-gcc
  78. brew rm dfu-programmer
  79. brew rm dfu-util
  80. brew rm gcc-arm-none-eabi
  81. brew rm avrdude
  82. brew install avr-gcc
  83. brew install dfu-programmer
  84. brew install dfu-util
  85. brew install gcc-arm-none-eabi
  86. brew install avrdude
  87. ```
  88. ### avr-gcc 8.1 and LUFA
  89. If you updated your avr-gcc to above 7 you may see errors involving LUFA. For example:
  90. `lib/lufa/LUFA/Drivers/USB/Class/Device/AudioClassDevice.h:380:5: error: 'const' attribute on function returning 'void'`
  91. For now, you need to rollback avr-gcc to 7 in brew.
  92. ```
  93. brew uninstall --force avr-gcc
  94. brew install avr-gcc@7
  95. brew link avr-gcc@7
  96. ```