Modules

Custom features exposed as Community Modules

Refer to QMK’s documentation for details on how to use this feature

allocator

Utilities to use custom allocators instead of stdlib’s implementation.

This is: malloc(), free(), calloc() and realloc().

ALLOCATORS_POOL_SIZE

How big the array to store different allocators will be.

ALLOC_STATS_POOL_SIZE

How big the array to store allocations’ metadata will be.

struct alloc_stats_t

Information about an allocation.

allocator_t *allocator

Allocator used to request this memory.

void *ptr

Pointer to the memory region provided by allocator.

size_t size

Size in bytes of the memory region.

struct [anonymous]

Information about this alloation’s duration.

uint32_t start

When was the memory allocated.

uint32_t end

When was the memory freed.

type malloc_fn

Signature of a malloc() function.

type free_fn

Signature of a free() function.

type calloc_fn

Signature of a calloc() function.

type realloc_fn

Signature of a realloc() function.

struct allocator_t

Information about a custom allocator.

malloc_fn malloc

Pointer to its malloc implementation.

free_fn free

Pointer to its free implementation.

calloc_fn calloc

Pointer to its calloc implementation.

realloc_fn realloc

Pointer to its realloc implementation.

const char *name

A short name/description.

void *arg

F Arbitrary config used by allocator. Eg a ChibiOS’ pool.

Caution

These wrappers add some extra logic as well as calling allocator->function(args).

Use them instead of manually executing the functions.

void *malloc_with(allocator_t *allocator, size_t total_size)

Run malloc’s implementation of the given allocator.

void free_with(allocator_t *allocator, void *ptr)

Run free’s implementation of the given allocator.

void *calloc_with(allocator_t *allocator, size_t nmemb, size_t size)

Run calloc’s implementation of the given allocator.

void *realloc_with(allocator_t *allocator, void *ptr, size_t size)

Run realloc’s implementation of the given allocator.

size_t get_used_heap(void)

Total heap used between all allocators.

const allocator_t **get_known_allocators(int8_t *n)

Get a pointer to every allocator implementation.

n will be set to the number of allocators.

const allocator_t *get_default_allocator(void)

Get the allocator defined as “default”.

extern allocator_t ch_core_allocator

ChibiOS’ core allocator.

allocator_t new_ch_pool_allocator(memory_pool_t *pool, const char *name)

Create a new ChibiOS’ pool allocator.

allocator_t new_ch_heap_allocator(memory_heap_t *heap, const char *name)

Create a new ChibiOS’ heap allocator.

arm_math_m0

Replaces some C builtins for floating point numbers (eg: sinf) with optimized implementations for Cortex-M0 and M0+ cores.

crash

Utilities to check why (if) last execution crashed.

Warning

Only works on Cortex-M microcontrollers, but apparently, not on M4F.

UNWIND_DEPTH

How big the array to store backtraces will be.

backtrace_t *get_crash_call_stack(uint8_t *depth, const char **msg)

Get the information about last execution.

Parameters:

• depth – Pointer to your variable which will be set to how deep the backtrace is (0 if no crash).

• msg – Pointer to your variable which will be set to the crash’s cause (NULL if no crash).

Returns:

Call stack that crashed the program (NULL if no crash)

dual_rp

Run code on the second core of your RP2040.

void c1_main(void)

Entrypoint of the second core.

Its default implementation is:

• Wait for first core to setup ChibiOS

• Run c1_init_kb and c1_init_user

• In an endless loop, run c1_main_kb and c1_main_user

However, it is defined weakly, you can overwrite it.

Caution

If you do so, the functions mentioned above will no longer be called.

void c1_init_kb(void)

Hook for keyboard-level initialization on the second core.

void c1_init_user(void)

Hook for user-level initialization on the second core.

void c1_main_kb(void)

Hook for keyboard-level logic on the second core.

void c1_main_user(void)

Hook for user-level logic on the second core.

indicators

Declaratively define RGB indicators.

Your configuration would look like:

const indicator_t PROGMEM indicators[] = {
   LAYER_INDICATOR(UTILS, RGB_OFF),
   KEYCODE_IN_LAYER_INDICATOR(QK_BOOT, UTILS, RGB_RED),
};

Since indicators are checked (and applied) in the same order that you define them, this config is:

• On the layer UTILS, all LEDs will be off except for QK_BOOT which will be red

• No indicator to be drawn on other layers (running effect left unchanged)

Hint

In general, you will use the convenience macros. However, you might need to manually instantiate these data structures to define custom conditions.

struct indicator_fn_args_t

State about the LED being checked.

Used to tell whether the indicator’s color should be applied.

uint8_t led_index

Index of the LED.

uint8_t layer

Highest active layer.

uint16_t keycode

Keycode currently mapped to the key where LED belongs.

uint8_t mods

Active modifiers (bitmask).

enum indicator_flags_t

Different conditions to be checked

enumerator LAYER = 1

Highest active layer is <X>.

enumerator KEYCODE = 2

Keycode is exactly <X>.

enumerator MODS = 4

Modifiers <X> are active (not an exact match, others can be active too).

enumerator KC_GT_THAN = 8

Keycode is greater than <X>.

struct indicator_t

An indicator’s specification:

rgb_t color

Color to be applied if conditions are fulfilled.

indicator_flags_t flags

Which conditions have to be checked.

indicator_fn_args_t conditions

Values used to check (the <X>s above).

KEYCODE_INDICATOR(_keycode, rgb)

Indicator on any key mapped to the given keycode.

Parameters:

• _keycode – Value of the keycode.

• rgb – Color to be applied.

LAYER_INDICATOR(_layer, rgb)

Indicator for all LEDs in the given layer.

Parameters:

• _layer – Where the indicator should fire.

• rgb – Color to be applied.

KEYCODE_IN_LAYER_INDICATOR(_keycode, _layer, rgb)

Indicator on any key mapped to the given keycode in the given layer.

Parameters:

• _keycode – Value of the keycode.

• _layer – Where the indicator should fire.

• rgb – Color to be applied.

ASSIGNED_KEYCODE_IN_LAYER_INDICATOR(_layer, rgb)

Indicator on any key that has been mapped in the given layer (ie: is not KC_NO nor KC_TRNS) .

Parameters:

• _layer – Where the indicator should fire.

• rgb – Color to be applied.

KEYCODE_WITH_MOD_INDICATOR(_keycode, mod_mask, rgb)

Indicator on any key mapped to the given keycode while mods are active.

Parameters:

• _keycode – Value of the keycode.

• mod_mask – Bitmask of the modifiers that must be active.

• rgb – Color to be applied.

CUSTOM_KEYCODE_IN_LAYER_INDICATOR(_layer, rgb)

Indicator on any key mapped to a custom keycode in the given layer.

Parameters:

• _layer – Where the indicator should fire.

• rgb – Color to be applied.

bool draw_indicators(uint8_t led_min, uint8_t led_max)

Check conditions, drawing the indicator if they met, for all leds in the given range.

Parameters:

• led_min – First LED to be drawn.

• led_max – Last LED to be drawn.

Warning

Since QMK does not (yet?) allow to hook modules into the RGB system, you need to call this function from within rgb_matrix_indicators_advanced_user

ledmap

Define a static, per-key, RGB matrix design.

It works similar to keymaps, mapping a color to each key and allowing transparency.

Your configuration would end up looking like:

const ledmap_color_t PROGMEM ledmap[][MATRIX_ROWS][MATRIX_COLS] = {
    [_QWERTY] = LAYOUT(
        RED,  RED,  RED,  RED,  RED,  RED,     RED,  RED,  RED,  RED,  RED,  RED,
        RED,  RED,  RED,  RED,  RED,  RED,     RED,  RED,  RED,  RED,  RED,  RED,
        RED,  RED,  RED,  RED,  RED,  RED,     RED,  RED,  RED,  RED,  RED,  RED,
        RED,  RED,  RED,  RED,  RED,  RED,     RED,  RED,  RED,  RED,  RED,  RED,
        RED,  RED,  RED,  RED,    BLACK,         WHITE,    RED,  TRNS, RED,  RED
    ),
    [_FN] = LAYOUT(
        TRNS, TRNS, TRNS, TRNS, TRNS, TRNS,    TRNS, TRNS, TRNS, TRNS, TRNS, TRNS,
        CYAN, CYAN, CYAN, CYAN, CYAN, CYAN,    CYAN, CYAN, CYAN, CYAN, CYAN, CYAN,
        BLUE, BLUE, BLUE, BLUE, BLUE, BLUE,    BLUE, BLUE, BLUE, BLUE, BLUE, BLUE,
        ROSE, ROSE, ROSE, ROSE, ROSE, ROSE,    ROSE, ROSE, ROSE, ROSE, ROSE, ROSE,
        WHITE,WHITE,BLACK,TRNS,    BLACK,         BLACK,   RED,  TRNS, WHITE,WHITE
    ),
 };

Warning

Due to reusing LAYOUT macro to define the colors, implementation is not too flexible.

• Assumes existence of a LED under every key.

• Does not support assigning colors to LEDs that aren’t under a key (eg: indicators or underglow)

It also hasn’t been exhaustively tested, there might be some problems.

enum ledmap_color_t

Available colors

enumerator RED

enumerator ORANGE

enumerator YELLOW

enumerator CHARTREUSE

enumerator GREEN

enumerator SPRING

enumerator CYAN

enumerator AZURE

enumerator BLUE

enumerator VIOLET

enumerator MAGENTA

enumerator ROSE

enumerator TRNS

enumerator WHITE

enumerator BLACK

int rgb_at_ledmap_location(uint8_t layer, uint8_t row, uint8_t col, rgb_t *rgb)

Retrieve the color assigned to a key in the ledmap (transparency gets applied).

Parameters:

• layer – Where to look at.

• row – Electrical position of the key in the matrix.

• col – Electrical position of the key in the matrix.

• rgb – Where the value will be written.

Return: Error code.

• 0: Color was found, and assigned into pointer.

• -EINVAL: Some input was wrong.

• -ENODATA: TRNS on layer 0 -> Dont overwrite the existing effect.

• -ENOTSUP: Value read at this position has no logic defined.

void draw_ledmap(uint8_t led_min, uint8_t led_max)

Assign their color to all leds in the given range.

Parameters:

• led_min – First LED to be drawn.

• led_max – Last LED to be drawn.

Warning

Since QMK does not (yet?) allow to hook modules into the RGB system, you need to call this function from within rgb_matrix_indicators_advanced_user

logging

Custom logging utilities, inspired by Python’s logging module.

Note

Under the hood, this is just a wrapper on top of printf().

Default format for logging messages.

enum log_level_t

Different level of severity. Used to filter out messages.

Warning

If you want to add a new one, it has to be the last element.

enumerator LOG_DEBUG

enumerator LOG_INFO

enumerator LOG_WARN

enumerator LOG_ERROR

enumerator LOG_NONE

Hint

The logging() function will apply an extra transformation to your input, based on a custom format. Its specifiers being:

• %LL: The message’s level (long). Eg: DEBUG.

  • These strings are set in level_str.

• %LS: Print only the first char of the previous string. Eg: D.

• %M: The actual message created by msg and ... passed to logging(). With its regular format.

• %T: Current time, you can override log_time() to hook it with a RTC or whatever.

  • Default implementation is seconds since boot.

• %%: Write a literal %.

For example, with format of [%F] (%LL) -- %M | %T, messages would look like: [QP] (DEBUG) -- <msg%args> | 3s

log_level_t get_logging_level(void)

Get the current level. Messages with a lower severity are dropped.

void set_logging_level(log_level_t level)

Change the current level.

void step_logging_level(bool increase)

Increase (or decrease) by one the level.

The direction is based on increase.

Attention

From this point, the functions are mostly implementation details.

You, most likely, don’t need to know anything about them.

log_level_t get_current_message_level(void)

Get the severity of the message being emitted.

This may be used by a sendchar_func_t internally.

const char *log_time(void)

Get a string representing the current time.

By default, seconds since boot, but it can be overwritten.

ASSERT_LEVELS(__array)

Check that an array has as many elements as logging levels are defined.

If not, compilation will error out.

memory

Tiny memory-usage and address “identification” functions.

bool ptr_in_heap(const void *addr)

Check if the input pointer belongs to the heap.

bool ptr_in_main_stack(const void *addr)

Check if the input pointer belongs to the main stack.

bool ptr_in_process_stack(const void *addr)

Check if the input pointer belongs to the process stack.

bool ptr_in_stack(const void *addr)

Check if the input pointer belongs to either stack.

size_t get_heap_size(void)

Get the total size of the heap section.

size_t get_used_flash(void)

Get amount of flash consumed by binary.

Warning

RP2040-only, for now.

size_t get_flash_size(void)

Get total size of the flash memory.

Warning

RP2040-only, for now.

micropython

Embeds microypthon’s interpreter into your board

Since that’s not very useful by itself, a module is provided to hook into QMK APIs. Namely, you use: import qmk

To execute some code, store it as a string and feed it into the mp_embed_exec_str function

Important

In the future, I plan to integrate import ... with QMK filesystem API (not a thing yet)

When (if) this happens, you would be able to run dynamic code, opposed to the current state, where you can only execute something defined as a const char* at compile time

Available APIs are:

qmkqmk.keycodeqmk.rgb

"""Utilities to interact with QMK from MicroPython."""


version: str
"""Version of QMK on which this firmware was built, as a raw string."""

version_info: tuple[int, int, int]
"""Version of QMK on which this firmware was built, as a (major, minor, patch) tuple."""

def get_highest_active_layer() -> int:
    """Get what the highest (currently active) layer is."""

def send_string(text: str, /) -> None:
    """Send a string over HID."""

def tap_code(kc: int, /) -> None:
    """Send a basic keycode over HID."""

rng

Generate (pseudo-)random numbers.

Note

This is just a convenience layer on top of lib8tion.h right now, but may use another source in the future.

void rng_set_seed(uint16_t seed)

Set the seed for the RNG. eg: invoking it from keyboard_post_init_user before consuming RNG.

Tip

You can for example call this:

• The reading on a floating ADC pin

• The value on some uninitialized memory address (only good entropy on cold start)

Warning

Setting a constant value means the PRNG sequence will be the same on every restart.

uint16_t rng_min_max(uint16_t min, uint16_t max)

Generate a random number in the [min, max] range.

It will also add some entropy to the RNG.

rp_sdk_wrappers

Replaces several C builtins (eg: __clzsi2) with optimized implementations provided in the ROM of RP2040

There are no hooks for user logic in this module because its only purpose is setting up such functions

Warning

To set this module up you need to define a custom linker script

This is due to Pico-SDK using a section to reference the functions required to configure these replacements

To do that, you can add this snippet at the end of the default linker script for RP2040 in ChibiOS

SECTIONS {
    .preinit : ALIGN(4){
        . = ALIGN(4);
        __preinit_array_base__ = .;
        KEEP(*(SORT(.preinit_array.*)))
        KEEP(*(.preinit_array))
        __preinit_array_end__ = .;
    } > XTORS_FLASH AT > XTORS_FLASH_LMA
}

scrolling_text

API to draw scrolling text on QP screens.

CONCURRENT_SCROLLING_TEXTS

How many scrolling texts can be drawn at the same time.

struct scrolling_text_state_t

Information about a scrolling text.

painter_device_t device

Screen where to draw.

uint16_t x

X coordinate where to draw.

uint16_t y

Y coordinate where to draw.

painter_font_handle_t font

Font to draw with.

char *str

Full text.

uint8_t n_chars

Amount of chars being drawn each time.

uint32_t delay

Time between drawing steps.

uint8_t char_number

Position (offset) of first char to be drawn.

uint8_t spaces

Spaces drawn before repetitions of the text.

int16_t width

Pixel width of current text, used to clean before next draw.

qp_pixel_t fg

Foreground color.

qp_pixel_t bg

Background color.

deferred_token defer_token

Identifier of the task drawing this scrolling text.

deferred_token draw_scrolling_text(painter_device_t device, uint16_t x, uint16_t y, painter_font_handle_t font, const char *str, uint8_t n_chars, uint32_t delay)

Start a scrolling text.

Parameters:

• device – Display in which to draw

• x – Coordinates where to draw

• y – Coordinates where to draw

• font – Font to be used

• str – Text to be written

• n_chars – How many chars to be written at any time

• delay – Time between animation steps (in ms)

Return: Token of the deferred executor taking care of drawing

deferred_token draw_scrolling_text_recolor(painter_device_t device, uint16_t x, uint16_t y, painter_font_handle_t font, const char *str, uint8_t n_chars, uint32_t delay, uint8_t hue_fg, uint8_t sat_fg, uint8_t val_fg, uint8_t hue_bg, uint8_t sat_bg, uint8_t val_bg)

Start a scrolling text with custom colors.

Parameters:

• device – Display in which to draw

• x – Coordinates where to draw

• y – Coordinates where to draw

• font – Font to be used

• str – Text to be written

• n_chars – How many chars to be written at any time

• delay – Time between animation steps (in ms)

• hue_fg – Foreground (font) color

• sat_fg – Foreground (font) color

• val_fg – Foreground (font) color

• hue_bg – Background color

• sat_bg – Background color

• val_bg – Background color

Return: Token of the deferred executor taking care of drawing

void stop_scrolling_text(deferred_token scrolling_token)

Stop a scrolling text.

Parameters:

• scrolling_token – Deferred token returned by the function that started this drawing.

string

Small utilities to work with text.

struct string_t

“String builder” without heap (malloc(), realloc(), free) usage.

Code using this API would look similar to:

// create a stack-based buffer, 50bytes long
string_t str = str_new(50);
// add text to it
str_append(&str, "Hello");
str_append(&str, " world");
// display it
printf("%s\n", str_get(str));

const size_t size

Total size in bytes.

size_t free

How many bytes are available after ptr.

char *ptr

Location of next position where we can write.

static inline string_t str_new(size_t n)

Create a temporary string_t.

Warning

This works on a VLA. If you need the value to outlive the function where it is declared, use malloc or your own buffer instead.

str_from_buffer(buffer)

Create a string_t wrapper for the given buffer.

char *str_get(string_t str)

Get a pointer to the start of this string.

size_t str_used(string_t str)

Find out how many bytes in the buffer have been used.

void str_reset(string_t *str)

Reset the string’s state.

size_t str_append(string_t *str, const char *text)

Add text to the string.

int pretty_bytes(string_t *str, size_t n)

Write the value of n (# of bytes) in an human-friendly format, into string

bool is_utf8(char c)

Check whether a char is UTF8.

bool is_utf8_continuation(char c)

Check whether a char is a UTF8-continuation byte.