I meant the default keymap from the keyboard's own config repo, but building from unmodified Miryoku ZMK main might be worth trying too if you can't find anything else. Good luck!
manna_harbour
joined 2 years ago
Nice! I assume the 10u version uses the same schematic as the 12u, just dropping the outer pinkie columns? In that case you can use the 12u firmware unmodified.
You could test with the default keymap, check your soldering for shorts, and try USB logging.
That looks like you have Colemak set on the host.
Great!
Here's a sample workflow build run: https://github.com/manna-harbour/miryoku_qmk/actions/runs/5650295293.
cheapino is using the split_3x5_3 layout that Miryoku QMK already supports, but cheapino doesn't have community layout support enabled, so it won't be used. If /u/[email protected] fixes that you'll be able to build by merging branches and building for cheepino. You can merge the cheepino branch automatically at build time by using tompi/qmk_firmware/cheapino with the Miryoku QMK build workflow branches option.
Excellent!
That issue was specifically for revxlp (being one of the few boards that required a ZMK fork), not for xiao ble in general. Can you link your failed build run? I don't know chiper36, so unless it's compatible with an already supported shield (and you build for that shield) it won't be supported. See https://github.com/manna-harbour/miryoku/discussions/81. If you have a ZMK keyboard definition for it I can add it to Miryoku ZMK.
Edit: see https://lemmy.world/comment/1025033.
There are 2 repos involved, ZMK and Miryoku ZMK.
The branch selector in the workflow is for choosing which Miryoku ZMK branch to build from. Unless you've made your own branch in your fork or you've manually sync'd an experimental branch from upstream, you'll only have the main branch in your fork.
The branches field in the workflow is used for selecting and merging ZMK forks and branches. That's what you need to do here, so put zmkfirmware/zmk/main in the workflow branches field.
And thanks for the reminder to fix the issue!
Nice! Good luck!
view more: next ›
Great!