summaryrefslogtreecommitdiff
path: root/platforms
AgeCommit message (Collapse)Author
2022-05-23Added support for Wb32fq95 (#16871)Joy Lee
2022-05-18Merge remote-tracking branch 'origin/master' into developQMK Bot
2022-05-18Fix platforms/avr/drivers/ws2812.c (#17043)Takeshi ISHII
* Fix platforms/avr/drivers/ws2812.c `platforms/avr/drivers/ws2812.c` has been changed to use `DDRx_ADDRESS()` and `PORTx_ADDRESS()` instead of `_SFR_IO8()` in #8646. To use them, `#include <pin_defs.h>` is required. ## Error Log * create new keyboard ```shell bash-3.2$ qmk new-keyboard Ψ Generating a new QMK keyboard directory Name Your Keyboard Project For more infomation, see: https://docs.qmk.fm/#/hardware_keyboard_guidelines?id=naming-your-keyboardproject Keyboard Name? ws2812_test .................................. 36. WB32F3G71 Please enter your choice: [12] Ψ Created a new keyboard called ws2812_test. Ψ To start working on things, `cd` into keyboards/ws2812_test, Ψ or open the directory in your preferred text editor. Ψ And build with qmk compile -kb ws2812_test -km default. ``` * Enable RGBLIGHT. ```shell bash-3.2$ echo RGBLIGHT_ENABLE=yes >> ./keyboards/ws2812_test/rules.mk bash-3.2$ echo '#define RGB_DI_PIN B1' >> ./keyboards/ws2812_test/config.h bash-3.2$ echo '#define RGBLED_NUM 6' >> ./keyboards/ws2812_test/config.h ``` * Compile ```shell bash-3.2$ make ws2812_test:default QMK Firmware 0.16.9 Making ws2812_test with keymap default avr-gcc (Homebrew AVR GCC 8.4.0_2) 8.4.0 Copyright (C) 2018 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ..................... Compiling: quantum/process_keycode/process_rgb.c [OK] Compiling: platforms/avr/drivers/ws2812.c platforms/avr/drivers/ws2812.c: In function 'ws2812_setleds': platforms/avr/drivers/ws2812.c:40:5: error: implicit declaration of function 'DDRx_ADDRESS' [-Werror=implicit-function-declaration] DDRx_ADDRESS(RGB_DI_PIN) |= pinmask(RGB_DI_PIN); ^~~~~~~~~~~~ In file included from <command-line>: ./keyboards/ws2812_test/config.h:21:20: error: 'B1' undeclared (first use in this function); did you mean 'PB1'? #define RGB_DI_PIN B1 ^~ platforms/avr/drivers/ws2812.c:40:18: note: in expansion of macro 'RGB_DI_PIN' DDRx_ADDRESS(RGB_DI_PIN) |= pinmask(RGB_DI_PIN); ^~~~~~~~~~ ./keyboards/ws2812_test/config.h:21:20: note: each undeclared identifier is reported only once for each function it appears in #define RGB_DI_PIN B1 ^~ platforms/avr/drivers/ws2812.c:40:18: note: in expansion of macro 'RGB_DI_PIN' DDRx_ADDRESS(RGB_DI_PIN) |= pinmask(RGB_DI_PIN); ^~~~~~~~~~ platforms/avr/drivers/ws2812.c:42:47: error: implicit declaration of function 'PORTx_ADDRESS' [-Werror=implicit-function-declaration] uint8_t masklo = ~(pinmask(RGB_DI_PIN)) & PORTx_ADDRESS(RGB_DI_PIN); ^~~~~~~~~~~~~ In file included from /usr/local/Cellar/avr-gcc@8/8.4.0_2/avr/include/avr/io.h:99, from /usr/local/Cellar/avr-gcc@8/8.4.0_2/avr/include/avr/interrupt.h:38, from platforms/avr/drivers/ws2812.c:24: platforms/avr/drivers/ws2812.c: In function 'ws2812_sendarray_mask': ./keyboards/ws2812_test/config.h:21:20: error: 'B1' undeclared (first use in this function); did you mean 'PB1'? #define RGB_DI_PIN B1 ^~ platforms/avr/drivers/ws2812.c:167:69: note: in expansion of macro 'RGB_DI_PIN' : "r"(curbyte), "I"(_SFR_IO_ADDR(PORTx_ADDRESS(RGB_DI_PIN))), "r"(maskhi), "r"(masklo)); ^~~~~~~~~~ cc1: all warnings being treated as errors [ERRORS] | | | make[1]: *** [.build/obj_ws2812_test_default/ws2812.o] Error 1 make: *** [ws2812_test:default] Error 1 Make finished with errors ``` * change include order
2022-05-18Workaround for recent -Werror=array-bounds AVR issues (#17136)Joel Challis
2022-05-14[Core] Add Reboot keycode to core (#15990)Drashna Jaelre
2022-04-29Move disable_jtag to platforms (#16960)Joel Challis
2022-04-22[Core] Allow usage of AVRs minimal printf library (#16266)Stefan Kerkmann
Co-authored-by: Sergey Vlasov <sigprof@gmail.com>
2022-04-22Provide better config defaults for bluepill boards (#16909)Joel Challis
2022-04-19[CI] Format code according to conventions (#16888)QMK Bot
2022-04-19Update wb32-dfu (#16438)Joy Lee
2022-04-19[Core] Use a mutex guard for split shared memory (#16647)Stefan Kerkmann
2022-04-18Fixup AVR builds. (#16875)Nick Brassel
* Fixup AVR builds. * Update platforms/avr/hardware_id.c Co-authored-by: Ryan <fauxpark@gmail.com> Co-authored-by: Joel Challis <git@zvecr.com> Co-authored-by: Ryan <fauxpark@gmail.com>
2022-04-18Expose API for hardware unique ID (#16869)Joel Challis
2022-04-06Add non blackpill F4x1 config files (#16600)Joel Challis
* Add non blackpill F4x1 config files * Move ld files * Remove f401 i2c bodges * more bodge? * Update to recommended defaults
2022-04-03Refactor CTPC logic to allow future converters (#16621)Joel Challis
* Refactor CTPC logic to allow future converters * Update builddefs/converters.mk Co-authored-by: Stefan Kerkmann <karlk90@pm.me> Co-authored-by: Stefan Kerkmann <karlk90@pm.me>
2022-03-30Add emulated eeprom support for STM32F303xE (#16737)dn9uyen
Added FEE_PAGE_SIZE and FEE_MCU_FLASH_SIZE defines for the STM32F303xE
2022-03-27Refactor writePin to work with statements (#16738)Stefan Kerkmann
2022-03-23Merge remote-tracking branch 'origin/master' into developQMK Bot
2022-03-23[Bug] Fix unused variable error when using ChibiOS Bitbang serial driver ↵Drashna Jaelre
(#16709)
2022-03-19HD44780 driver rework (#16370)Ryan
2022-03-11Redo workaround for pin_def errors on KINETIS (#16620)Joel Challis
* Redo workaround for pin_def errors on KINETIS * Redo workaround for pin_def errors on KINETIS
2022-03-11Workaround for pin_def errors on KINETIS (#16614)Joel Challis
2022-03-10Force platform pin defs to be included (#16611)Joel Challis
* Force platform pin defs to be included * Always grab first header
2022-03-07Add flash target for UF2 bootloaders (#16525)Stefan Kerkmann
2022-03-07ChibiOS 21.11.1 update. (#16251)Nick Brassel
* ChibiOS 21.11.1 update. * `uf2-tinyuf2` => `tinyuf2` * Updated chibios-contrib, fixup preprocessor for tinyuf2 bootloader. * Fixup keychron L433 boards. * Makefile cleanup. * RISC-V build fixes. * Fixup RISC-V build.
2022-03-04Merge remote-tracking branch 'origin/master' into developQMK Bot
2022-03-04analog.[ch]: remove unnecessary includes (#16471)Ryan
2022-02-26[Core] Squeeze AVR some more with `-mrelax` and `-mcall-prologues` (#16269)Stefan Kerkmann
2022-02-13Fix compilation of ChibiOS UART driver (#16348)Joel Challis
Cherry picked fix from 15724
2022-02-12Format code according to conventions (#16322)QMK Bot
2022-02-05Followup to #16220, more test error output. (#16221)Nick Brassel
2022-02-05Initial migration of suspend callbacks (#16067)Joel Challis
* Initial migration of suspend logic * Add header
2022-02-05ChibiOS timer fixes (#16017)Sergey Vlasov
* chibios/timer: Move the 16-bit timer handling into a separate function Extract the code which effectively makes a 32-bit tick counter from a possibly 16-bit ChibiOS system timer into a separate function. Does not really change the behavior of the timer API, but makes the actions done in `timer_clear()` and `timer_read32()` more obvious. * chibios/timer: Rename some variable to better reflect their role * chibios/timer: Fix 32-bit tick counter overflow handling The QMK timer API implementation for ChibiOS used a 32-bit tick counter (obtained from the ChibiOS system timer) and then converted the value to milliseconds to produce the timer value for QMK. However, the frequency of the ChibiOS timer is above 1000 Hz in most cases (values of 10000 Hz or even 100000 Hz are typically used), and therefore the 32-bit tick counter was overflowing and wrapping around much earlier than expected (after about 5 days for 10000 Hz, or about 12 hours for 100000 Hz). When this wraparound happened, the QMK timer value was jumping back to zero, which broke various code dealing with timers (e.g., deferred executors). Just making the tick counter 64-bit to avoid the overflow is not a good solution, because the ChibiOS code which performs the conversion from ticks to milliseconds may encounter overflows when handling a 64-bit value. Adjusting just the value converted to milliseconds to account for lost 2**32 ticks is also not possible, because 2**32 ticks may not correspond to an integer number of milliseconds. Therefore the tick counter overflow is handled as follows: - A reasonably large number of ticks (the highest multiple of the ChibiOS timer frequency that fits into uint32_t) is subtracted from the tick counter, so that its value is again brought below 2**32. The subtracted value is chosen so that it would correspond to an integer number of seconds, therefore it could be converted to milliseconds without any loss of precision. - The equivalent number of milliseconds is then added to the converted QMK timer value, so that the QMK timer continues to count milliseconds as it was before the tick counter overflow. * chibios/timer: Add a virtual timer to make 16-bit timer updates more reliable The code which extends the 16-bit ChibiOS system timer to a 32-bit tick counter requires that it is called at least once for every overflow of the system timer (otherwise the tick counter can skip one or more overflow periods). Normally this requirement is satisfied just from various parts of QMK code reading the current timer value; however, in some rare circumstances the QMK code may be blocked waiting for some event, and when this situation is combined with having a rather high timer frequency, this may result in improper timekeeping. Enhance the timer reliability by adding a ChibiOS virtual timer which invokes a callback every half of the timer overflow period. The virtual timer callback can be invoked even when the normal QMK code is blocked; the only requirement is that the timer interrupts are enabled, and the ChibiOS kernel is not locked for an excessive time (but the timer update will eventually work correctly if the virtual timer handling is not delayed by more than a half of the timer overflow period). Keeping a virtual timer always active also works around a ChibiOS bug that can manifest with a 16-bit system timer and a relatively high timer frequency: when all active virtual timers have delays longer than the timer overflow period, the handling of virtual timers stops completely. In QMK this bug can result in a `wait_ms()` call with a delay larger than the timer overflow period just hanging indefinitely. However, when the timer update code adds a virtual timer with a shorter delay, all other virtual timers are also handled properly.
2022-02-03Create a build error if no bootloader is specified. (#16181)Nick Brassel
* Create a build error if no bootloader is specified. * Update builddefs/bootloader.mk Co-authored-by: Ryan <fauxpark@gmail.com> Co-authored-by: Ryan <fauxpark@gmail.com>
2022-02-02Fixup builds so that teensy EEPROM knows which MCU it's targeting. (#16168)Nick Brassel
2022-02-02Don't make EEPROM size assumptions with dynamic keymaps. (#16054)Nick Brassel
* Don't make EEPROM size assumptions with dynamic keymaps. * Add support for checking against emulated flash, error out if someone attempts to build a board without specifying EEPROM size. * Reorder defines so that MCU is considered last. * Refactor EEPROM definitions for simplicity. * Fix max sizing of kabedon/kabedon980. * Fix max sizing of mechlovin/olly/jf. * Fix unit tests. * Review comments, add messages with values during build failures.
2022-01-26Deprecate split transactions status field (#16023)Stefan Kerkmann
2022-01-26Remove unused suspend_idle (#16063)Joel Challis
2022-01-25Fix bootloader_jump for certain CTRL boards (#16026)Ryan
2022-01-24Default EEPROM implementation should be transient when not implemented. ↵Nick Brassel
Removed the equivalent eeprom_teensy fallback. (#16020)
2022-01-24Add L432, L442. (#16016)Nick Brassel
2022-01-15Fix broken bootloader builds in develop. (#15880)Dasky
2022-01-09Merge remote-tracking branch 'origin/master' into developQMK Bot
2022-01-10Revert "core: make the full 4096 bytes of EEPROM work on Teensy 3.6 ↵Michael Stapelberg
(#12947)" (#15695) This reverts commit 7f8faa429e0c0662cec34a7d60e33ca58333d6d7. related to https://github.com/qmk/qmk_firmware/issues/15521
2022-01-06Fixes for bootloader refactor build failures (#15638)Ryan
2021-12-27Format code according to conventions (#15593)QMK Bot
2021-12-27Refactor `bootloader_jump()` implementations (#15450)Ryan
* Refactor `bootloader_jump()` implementations * Fix tests? * Rename `atmel-samba` to `md-boot`
2021-12-26More GPIO compilation fixes. (#15592)Nick Brassel
2021-12-27Defer pin operations to gpio.h (#15589)Nick Brassel
2021-12-27Add open-drain GPIO support. (#15282)Nick Brassel
* Add open-drain GPIO support. * `qmk format-c` * Wording. * Remove port GPIO implementations as the only board that uses it has its own internal defs anyway. Will wait for first-class handling of ports in core before reimplementing.