| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
Co-authored-by: Sergey Vlasov <[email protected]>
|
| |
|
|\ |
|
| |
| |
| | |
Change STM32L433 LSI to False, this is to fix board startup issue , change is same to stm32L432 board
|
|/ |
|
| |
|
| |
|
|
|
|
|
| |
* WS2812 PWM: prefix for DMA defines
* Add backward compatibility defines
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* onekey: stm32f3_disco: add usart pins and activate peripheral
Signed-off-by: Stefan Kerkmann <[email protected]>
* chibios: uart: change SD1 prefix to UART
Signed-off-by: Stefan Kerkmann <[email protected]>
* chibios: uart: add SIO driver and RP2040 compatibility
Signed-off-by: Stefan Kerkmann <[email protected]>
Co-authored-by: Sergey Vlasov <[email protected]>
* Update platforms/chibios/drivers/uart.h
Co-authored-by: Joel Challis <[email protected]>
---------
Signed-off-by: Stefan Kerkmann <[email protected]>
Co-authored-by: Sergey Vlasov <[email protected]>
Co-authored-by: Joel Challis <[email protected]>
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Co-authored-by: Joy <[email protected]>
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Partially revert #19780
* Finish
* Get teensy 3.5/3.6 board files too
* fix lint issue
* Revert "[Bug] Restore usb suspend wakeup delay (#21676)"
This reverts commit e8e989fd7ad7c10e725e50ae8b0a4426e09f7f30.
* Apply suggestions from code review
Co-authored-by: Joel Challis <[email protected]>
---------
Co-authored-by: Joel Challis <[email protected]>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Update ChibiOS-Contrib for USB suspend fixes
* Remove S3 wakup workaround
ChibiOS OTGv1 driver has a remote wakeup bug that prevents the device to
resume it's operation. 02516cbc24647f522eee975e69cc0c8a925470eb
introduced a hotfix that forcefully restarted the usb driver as a workaround.
This workaround broke multiple boards which do not use this driver /
peripheral. With the update of ChibiOS this hotfix is now obsolete.
* Remove restart_usb_driver overrides
they are no longer necessary as the workaround is not needed anymore
for stm32f4
* Remove unused RP_USB_USE_SOF_INTR defines
The SOF interrupt is enabled dynamically by the RP2040 usb driver
|
|
|
|
|
|
|
| |
* Duplicate board files for blok converter
* Swap converters board file too
* Update platforms/chibios/boards/QMK_BLOK/configs/board.h
|
| |
|
|
|
|
|
| |
* Remove bootloader logic from mcu_selection.mk
* Move MCU/BOOTLOADER to info.json
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Add STM32F446-Nucleo onekey.
* Fixup onekey build for F446, all keymaps.
* Fixup board inclusion search ordering.
|
| |
| |
| | |
Co-authored-by: Ryan <[email protected]>
|
| | |
|
| | |
|
| |
| |
| | |
Co-authored-by: Nick Brassel <[email protected]>
|
| |
| |
| | |
Co-authored-by: Nick Brassel <[email protected]>
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Set up Bonsai C4 as a platform board file
* corrections and improvements based on testing and feedback
* Added VBUS sensing as default capability for improved split support using Bonsai C4
* Update clock divisor for SPI flash
Co-authored-by: Nick Brassel <[email protected]>
Co-authored-by: Nick Brassel <[email protected]>
|
|\ |
|
| | |
|
| | |
|
| | |
|
|/
|
| |
Co-authored-by: Joy <[email protected]>
|
|
|
|
|
| |
Co-authored-by: Mariappan Ramasamy <[email protected]>
Co-authored-by: Mariappan Ramasamy <[email protected]>
Co-authored-by: Sadek Baroudi <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Unfortunately, the crippled versions of “Bluepill” boards with
STM32F103C6xx chips instead of STM32F103C8xx are now sold all over the
place, sometimes advertised in a confusing way to make the difference
not noticeable until too late. Add minimal support for these MCUs in
the common “Bluepill with stm32duino” configuration, so that it could be
possible to make something useful from those boards (although fitting
QMK into the available 24 KiB of flash may be rather hard).
(In fact, I'm not sure whether the “STM32” part of the chip name is
actually correct for those boards of uncertain origin, so the onekey
board name is `bluepill_f103c6`; another reason for that name is to
match the existing `blackpill_f401` and `blackpill_f411`.)
The EEPROM emulation support is not included on purpose, because
enabling it without having a working firmware size check would be
irresponsible with such flash size (the chance that someone would build
a firmware where the EEPROM backing store ends up overlapping some
firmware code is really high). Other than that, enabling the EEPROM
emulation code is mostly trivial (the `wear_leveling` driver with the
`embedded_flash` backing store even works without any custom
configuration, although its code is significantly larger than the
`vendor` driver, which may also be important for such flash size).
|
| |
|
| |
|
| |
|
| |
|
| |
|