search

Bastardkb / bastardkb-qmk

Open-source keyboard firmware for Atmel AVR and Arm USB families
https://qmk.fm
82 stars 107 forks source link

Skeletyl default firmware #6

Closed bstiq closed 2 years ago

bstiq commented 2 years ago

Hi @0xcharly ,

When flashing skeletyls myself, I use miryoku.

I'd also like to include vial as default.

This means:

I'm a bit unsure on how to do the second one though, let me know if you have ideas.

Regards,

0xcharly commented 2 years ago

Building the Skeletyl firmware with Miryoku and Via support is fairly trivial, but building with Vial support is not.

To build Miryoku for Skeletyl from bkb-vial, we need to

  1. copy the Skeletyl's vial.json file under layouts/community/split_3x5_3/manna-harbour_miryoku:

    cp keyboards/bastardkb/skeletyl/keymaps/vial/vial.json layouts/community/split_3x5_3/manna-harbour_miryoku/.

  2. generate and add a VIAL_KEYBOARD_UID to users/manna-harbour_miryoku/config.h:

    util/vial_generate_keyboard_uid.py >> users/manna-harbour_miryoku/config.h

  3. comment out AUTO_SHIFT_NO_SETUP in users/manna-harbour_miryoku/config.h (already defined in Vial's master I believe):

     sed -i 's|\(#define AUTO_SHIFT_NO_SETUP\)|// \1|' users/manna-harbour_miryoku/config.h

And finally build the firmware with the following command-line:

qmk compile -j0 -kb bastardkb/skeletyl/v2/elitec -km manna-harbour_miryoku -e VIA_ENABLE=yes -e VIAL_ENABLE=yes -e VIAL_INSECURE=yes -e LTO_ENABLE=yes -e SPACE_CADET_ENABLE=no -e TAP_DANCE_ENABLE=no -e KEY_OVERRIDE_ENABLE=no -e QMK_SETTINGS=no -e VIALRGB_ENABLE=yes

This just fits on AVR:

 * The firmware size is approaching the maximum - 28590/28672 (99%, 82 bytes free)

I could stash the changes above in a separate branch based on bkb-vial and use that to generate the firmware. I don't expect too many conflict with future updates to Miryoku.

bstiq commented 2 years ago

Hey,

If it's too much effort - don't bother. Skeletyl firmware with miryoku and without vial is fine.

We can switch to miryoku+vial once we have more space (rp2040) and/or it generates less conflicts between the 2 of them and/or it's less effort, this seems like you're going too much out of your way.

0xcharly commented 2 years ago

Done. https://github.com/Bastardkb/bastardkb-qmk/releases/tag/v2.0.3 is the first release to contain those firmwares:

I've left the default base layer unchanged, which is Colemak DH for Miryoku. Let me know if you prefer another default layer (eg. QWERTY).

Closing this for now.