Skip to content

Releases: Bastardkb/bastardkb-qmk

Firmware for Bastard Keyboards

23 Apr 12:37
184d5a3
Compare
Choose a tag to compare

Summary

  • Update for removal of legacy architectures and new flattened source tree. In theory functionally identical to the previous release.

Contact

Please report any bugs by opening an issue. Thanks!

If you have any questions, feel free to join the Discord server.

Firmware for Bastard Keyboards

21 Apr 11:27
184d5a3
Compare
Choose a tag to compare

Summary

  • Bootmagic is now configured across all BastardKB boards
  • Charybdis: The bootloader and eeprom clear keys have been moved to the top outer keys to prevent misactuations
  • Dilemma Max: Now comes with layer indicators using the underglow LEDs
  • Update to qmk's 2024q2 breaking changes

Contact

Please report any bugs by opening an issue. Thanks!

If you have any questions, feel free to join the Discord server.

Firmware for Bastard Keyboards

19 Oct 11:33
Compare
Choose a tag to compare

Summary

Hot fix release to restore missing pointer layer keycodes in the Charybdis 3x6 keymap.

Contact

Please report any bugs by opening an issue. Thanks!

If you have any questions, feel free to join the Discord server.

Firmware for Bastard Keyboards

02 Oct 13:17
Compare
Choose a tag to compare

Dilemma Max

This release marks the introduction of the official firmware for the new Dilemma Max.

@casuanoob has been hard at work to deliver this new firmware. Thanks a ton!

Skeletyl, TBKmini, Scylla, Charybdis

In addition, this release also contains the updated firmwares for the Splinky v3 and Splintegrated (a.k.a. rp2040_ce which represents the Community Edition pinout for RP2040 based controllers).

The controllers included in the Bastard Keyboard kits are compatible with the Splinky v3.

Via

All Bastard Keyboards, including the Dilemma MAX and Charybdis Mini are now officially supported in QMK and Via. No more sideloading required.

Contact

Please report any bugs by opening an issue. Thanks!

If you have any questions, feel free to join the Discord server.

Firmware for Bastard Keyboards

09 Apr 12:02
Compare
Choose a tag to compare

Dilemma v2

This release marks the introduction of the official firmware for the new Dilemma v2.

@casuanoob has been hard at work to deliver this new firmware. Thanks a ton!

Skeletyl, TBKmini, Scylla, Charybdis

In addition, this release also contains the updated firmwares for the following (MCU, adapter versions) pairs:

  • Elite-C on adapter v1.x
  • Elite-C on adapter v2.0
  • STeMCell on adapter v2.0
  • Splinky (v2 and v3) on adapter v2.0
  • Blackpill on adapter v1.1

Splinky versions

The Splinky changed its pins assignment between version 2 and 3. The version is visible on the silkscreen, so make sure you use the correct version of the firmware for your hardware.

This release includes firmwares for both v2 and v3. For any keyboard supporting the Splinky, you can now choose between:

  • …_splinky_v2…
  • …_splinky_v3…

For example bastardkb_skeletyl_v2_splinky_v3_vial.uf2.

The Splinky included in the Bastard Keyboard kits are v3.

Moving away from Vial in favor of Via

The Vial fork still lags behind QMK's master, which means that Vial-enabled firmwares are now lagging behind the ones built against QMK's master branch by almost 9 months.

It is therefore not advised to use these firmwares anymore. For this reason, they are not included in this release. They are still available in past releases if necessary (the most recent one being v3.1.0).

We're evaluating using Via as an alternative, until XAP is production ready. For now, all stock firmwares in this release have been built with Via support.

Contact

Please report any bugs by opening an issue. Thanks!

If you have any questions, feel free to join the Discord server.

Firmwares for Bastard Keyboards

19 Feb 07:15
Compare
Choose a tag to compare

Skeletyl, TBKmini, Scylla, Charybdis

This release contains the firmwares for the following (MCU, adapter versions) pairs:

  • Elite-C on adapter v1.x
  • Elite-C on adapter v2.0
  • STeMCell on adapter v2.0
  • Splinky (v2 and v3) on adapter v2.0
  • Blackpill on adapter v1.1

Splinky versions

The Splinky changed its pins assignment between version 2 and 3. The version is visible on the silkscreen, so make sure you use the correct version of the firmware for your hardware.

This release includes firmwares for both v2 and v3. For any keyboard supporting the Splinky, you can now choose between:

  • …_splinky_v2…
  • …_splinky_v3…

For example bastardkb_skeletyl_v2_splinky_v3_vial.uf2.

The Splinky included in the Bastard Keyboard kits are v3.

Vial

The Vial fork still lags behind QMK's master.

This release comes in late because we were waiting for Vial to catch up and hoping they'd sync to the latest version of QMK. It appears that this is still not done, which means that Vial-enabled firmwares are now lagging behind the ones built against QMK's master branch by almost 6 months.

It is therefore not advised to use these firmwares anymore. For this reason, they are not included in this release. They are still available in past releases if necessary (the most recent one being v3.1.0).

We're evaluating using Via as an alternative, until XAP is production ready. For now, all stock firmwares in this release have been built with Via support. Until the Via JSON are merged into Via's repository of keyboards, you will need to manually load the relevant .via.json file (included in this release) in Via's "Design" tab.

Contact

Please report any bugs by opening an issue. Thanks!

If you have any questions, feel free to join the Discord server.

Firmwares for Bastard Keyboards

03 Nov 13:05
Compare
Choose a tag to compare

Skeletyl, TBKmini, Scylla, Charybdis

This release contains the firmwares for the following (MCU, adapter versions) pairs:

  • Elite-C on adapter v1.x
  • Elite-C on adapter v2.0
  • STeMCell on adapter v2.0
  • Splinky (v2 and v3) on adapter v2.0
  • Blackpill on adapter v1.1

Splinky versions

The Splinky changed its pins assignment between version 2 and 3. The version is visible on the silkscreen, so make sure you use the correct version of the firmware for your hardware.

This release includes firmwares for both v2 and v3. For any keyboard supporting the Splinky, you can now choose between:

  • …_splinky_v2…
  • …_splinky_v3…

For example bastardkb_skeletyl_v2_splinky_v2_vial.uf2.

The Splinky included in the Bastard Keyboard kits are v3.

LTS

The previous release moved Vial-enabled firmwares targeting AVR controllers to a LTS release cycle.

This means that the following Vial-enabled firmwares are built from a frozen branch (namely, bkb-lts-vial), and will only be updated on a one-off basis, specifically after a critical bug fix:

  • skeletyl/v1/elitec:vial
  • skeletyl/v2/elitec:vial
  • tbkmini/v1/elitec:vial
  • tbkmini/v2/elitec:vial
  • scylla/v1/elitec:vial
  • scylla/v2/elitec:vial
  • charybdis/3x5/v1/elitec:vial
  • charybdis/3x5/v2/elitec:vial
  • charybdis/3x6/v1/elitec:vial
  • charybdis/3x6/v2/elitec:vial
  • charybdis/4x6/v1/elitec:vial
  • charybdis/4x6/v2/elitec:vial

In the future, new features, if any, will not be merged to this branch.

See #24 for details and reasoning.

Note that:

  • This only affects Vial-enabled firmwares on AVR (Elite-C): non-vial enabled firmwares for AVR will still be regularly updated for as long as the original feature set fits on supported controllers
  • Going forward, Vial will only be maintained for ARM controllers
    • STM32F411 blackpill and STeMCell
    • RP2040-based controllers like the Splinky, and the upcoming Elite-Pi

Contact

Please report any bugs by opening an issue. Thanks!

If you have any questions, feel free to join the Discord server.

Firmwares for Bastard Keyboards

11 Sep 10:28
Compare
Choose a tag to compare

Skeletyl, TBKmini, Scylla, Charybdis

This release contains the firmwares for the following (MCU, adapter versions) pairs:

  • Elite-C on adapter v1.x
  • Elite-C on adapter v2.0
  • STeMCell on adapter v2.0
  • Splinky on adapter v2.0
  • Blackpill on adapter v1.1

STeMCell

Support for the STeMCell has been officially merged into QMK's master, which means that this target is now officially supported for the entire Bastard Keyboards lineup. This also means that pre-built Vial-enabled firmwares are now available.

LTS

This release moves Vial-enabled firmwares targeting AVR controllers to a LTS release cycle.

This means that the following Vial-enabled firmwares are built from a frozen branch (namely, bkb-lts-vial), and will only be updated on a one-off basis, specifically after a critical bug fix:

  • skeletyl/v1/elitec:vial
  • skeletyl/v2/elitec:vial
  • tbkmini/v1/elitec:vial
  • tbkmini/v2/elitec:vial
  • scylla/v1/elitec:vial
  • scylla/v2/elitec:vial
  • charybdis/3x5/v1/elitec:vial
  • charybdis/3x5/v2/elitec:vial
  • charybdis/3x6/v1/elitec:vial
  • charybdis/3x6/v2/elitec:vial
  • charybdis/4x6/v1/elitec:vial
  • charybdis/4x6/v2/elitec:vial

In the future, new features, if any, will not be merged to this branch.

See #24 for details and reasoning.

Note that:

  • This only affects Vial-enabled firmwares on AVR (Elite-C): non-vial enabled firmwares for AVR will still be regularly updated for as long as the original feature set fits on supported controllers
  • Going forward, Vial will only be maintained for ARM controllers
    • STM32F411 blackpill and STeMCell
    • RP2040-based controllers like the Splinky, and the upcoming Elite-Pi

Keymaps

  • Use the default keymap for Skeletyl, TBK Mini and Scylla.
  • Use the stock keymap for the Charybdis (3x5 and 4x6).
  • Use the vial keymap for all boards if you want Vial support.

Vial-aware keymaps are also available for all keyboards (AVR and ARM).

Dilemma

This release contains the firmwares for the following version:

  • Splinky on the DIY Dilemma
  • Assembled Dilemma

Keymaps

  • Use the stock keymap
  • Use the vial keymap if you want Vial support

Via- and Vial-enabled firmwares improvements

Thanks to https://github.com/casuanoob, all Via and Vial descriptor files (a.k.a. the JSON files) for the Charybdis and Dilemma now support custom keycodes defined by those keyboards. This means that drag-scroll and sniping mode, and DPI-related keycodes are now labeled as such in the UI of these tools, instead of their default, obscure, labels (eg. USER00).

Contact

Please report any bugs by opening an issue. Thanks!

If you have any questions, feel free to join the Discord server.

Firmwares for Bastard Keyboards

07 Aug 10:55
Compare
Choose a tag to compare

This release contains the firmwares for the following (MCU, adapter versions) pairs:

  • Elite-C on adapter v1.x
  • Elite-C on adapter v2.0
  • STeMCell on adapter v2.0
  • Splinky on adapter v2.0
  • Blackpill on adapter v1.1

Dilemma

It also adds firmwares for the latest addition to the Bastard Keyboards lineup: the Dilemma assembled, with the same stock keymap as the Charybdis Nano!

Note that the Dilemma is still under active development, and the firmwares provided here are only for testing purposes and may be incomplete.

Keymaps

  • Use the default keymap for Skeletyl, TBK Mini and Scylla.
  • Use the stock keymap for the Charybdis (3x5 and 4x6).

Vial-aware keymaps are also available for all keyboards (AVR and ARM).

Contact

Please report any bugs by opening an issue. Thanks!

If you have any questions, feel free to join the Discord server.

Firmwares for Bastard Keyboards

02 Jul 12:42
Compare
Choose a tag to compare

This release contains the firmwares for the following (MCU, adapter versions) pairs:

  • Elite-C on adapter v1.x
  • Elite-C on adapter v2.0
  • STeMCell on adapter v2.0
  • Splinky on adapter v2.0
  • Blackpill on adapter v1.1

A new boy in da house

It also adds firmwares for the latest addition to the Bastard Keyboards lineup: the Dilemma!

Note that the Dilemma is still under active development, and the firmwares provided here are only for testing purposes and may be incomplete.

bkb-rp2040 is dead, long live bkb-develop

The support for RP2040 chips (qmk#14877) was merged into qmk:develop! This means that firmwares targeting RP2040-based controllers (like the Splinky) can know be built from the develop branch and don't need to manually track the PR. The bkb-rp2040 branch has been updated one last time after the PR was merged, but going forward, new changes will be made directly against bkb-develop.

Additionally, support for emulated EEPROM for RP2040 (qmk#17519) has just been merged. This means that it is now possible to build Via-enabled firmwares for RP2040-based controllers.

What about Vial

These recent changes need to be merged into qmk:master before they can make it to Vial. This means that Vial support will be available only after the next QMK quarterly release.

Keymaps

  • Use the default keymap for Skeletyl, TBK Mini and Scylla.
  • Use the stock keymap for the Charybdis (3x5 and 4x6).

Vial-aware keymaps are also available for all keyboards (only for Elite-C and Blackpill).

Changelog

In addition to the above changes, this release also fixes a couple of bugs:

  • With the via keymaps for all sizes of the Charybdis: an infinite recursion that would prevent the keyboard from working altogether (3866050). Note that this bug had already been fixed in the previous release for the vial keymaps.
  • With all keymaps for all sizes of the Charybdis: a missing invocation of the pointing_device_init_user() callback that would prevent that user-level function to run (729bfdb).

Contact

Please report any bugs by opening an issue. Thanks!

If you have any questions, feel free to join the Discord server.