Added new keyboard DOIO KB16 (Rev 2) #18699
Conversation
github-actions
bot
added
keyboard
keymap
via
|
I wasn't able to get this one to build. I got the data from this PR and injected it into my existing qmk build env. `qmk compile -kb doio/kb16/rev2 -km default QMK Firmware 0.18.13 Making doio/kb16/rev2 with keymap default ☒ doio/kb16/rev2: Number of keys for LAYOUT does not match! info.json specifies 25 keys, C macro specifies 19 Compiling: keyboards/doio/kb16/lib/layer_status/layer_status.c In file included from : |
Try to update your git submodules with the |
|
I have it in a folder called qmmk because that's what I originally programmed with this env. ❯ make git-submodule QMK Firmware 0.18.13 ☒ doio/kb16/rev2: Number of keys for LAYOUT does not match! info.json specifies 25 keys, C macro specifies 19 Compiling: keyboards/doio/kb16/lib/layer_status/layer_status.c In file included from : |
|
Did you pull all of the changes from this pr? It looks like the rev1 files are still in |
|
I copied everything into the directory structure and didn't move that. I can clear out the folder and try again edit: that appeared to be the issue! I didn't realize a remnant folder that had been moved would cause an issue. Thanks buddy! edit part deux: Copying doio_kb16_rev2_default.bin to qmk_firmware folder [OK] It looks like it compiled okay, but can't flash due to having the incorrect boot device. Mine is the one with the Geehy APM32. |
|
Please checkout all of the changes using the instructions here instead of copying in some files: |
|
I cloned the project into a fresh directory ❯ git clone https://github.com/qmk/qmk_firmware.git Checked out your PR ❯ gh pr checkout 18699
Successfully compiled ❯ qmk compile -kb doio/kb16/rev2 -km default QMK Firmware 0.18.13 arm-none-eabi-gcc (15:9-2019-q4-0ubuntu1) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599] Generating: .build/obj_doio_kb16_rev2/src/info_config.h [OK] Size after: Copying doio_kb16_rev2_default.bin to qmk_firmware folder [OK] Tried to flash with my new macropad in bootloader mode ❯ qmk flash -kb doio/kb16/rev2 -km default QMK Firmware 0.18.13 arm-none-eabi-gcc (15:9-2019-q4-0ubuntu1) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599] Size before: Size after: Copying doio_kb16_rev2_default.bin to qmk_firmware folder [OK] |
I'm pretty sure it's an issue with your environment. Run |
Ahh, dfu rules for the apm32 |
|
I have built the firmware and tested it. don't see anything wrong. |
|
the board does not reboot properly after flashing, reconnection is required. Not sure if this is normal |
|
the CW CCW is in wrong order i have to workaround like this
|
|
(Firmware size check does not yet support STM32F103; skipping) this chip has 128 kB program memory and 20kB ram |
|
Tbh, no it is not wrong order. It just VIAL problem anyway, and QMK compile does not supported firmware size check for ARM |
|
also tested with a via keymap, same issue.
{
"name": "KB16-01",
"vendorId": "0xD010",
"productId": "0x1601",
"lighting": "none",
"matrix": {
"rows": 4,
"cols": 5
},
"layouts": {
"keymap": [
["0,0","0,1","0,2","0,3",{"x":0.25},"0,4\n\n\n\n\n\n\n\n\ne0",{"x":0.75},"1,4\n\n\n\n\n\n\n\n\ne1"],
["1,0","1,1","1,2","1,3"],
["2,0","2,1","2,2","2,3",{"x":0.75,"w":1.75,"h":1.75},"2,4\n\n\n\n\n\n\n\n\ne2"],
["3,0","3,1","3,2","3,3"]
]
}
} |
IMG_2154.mp4the big knob is correct |
HorrorTroll
force-pushed
the
kb16_rev2
branch
from
2413da1 to
00a52b7
Compare
|
@thompson-vii @PHSC138 can u guy check the encoder issue and see if it work correctly or not? |
|
Encoder is fixed. |
|
I'm new to QMK and having issues getting this to work with VIA. It compiles and flashes fine. In VIA I load the keymap from https://wiki.keebmonkey.com/en/products/mmp, however it keeps saying "Searching for devices...".. I assume that I need to use a different keymap? Anyone that can tell me what I'm doing wrong. |
|
the layout file on the wiki will only work with stock firmware, the binary i provided is for and only for use with vial https://get.vial.today/ you need to flash it into the board, i have provided instruction in the link |
|
Thanks for getting back to me @thompson-vii I have actually also tried to get it to work with vial but without succes. Everything goes well but vial says "No devices detected". If I flash your precompiled firmware then it works fine. But if I compile the firmware myself from this PR then vial cannot connect to the board Edit: Thanks for the help |
Hi Peter, do you mind sharing your ported firmware? I tried following that guide, but the firmware keeps coming out too large. I flashed my macropad from thompson-vii, and it's not getting detected in VIAL. It shows up as Maple 003 in my device manager. |
I use the same firmware form thompson-vii and VIAL is able to detect my macropad. After flashing is completed you need to reconnect the board. It is not being detected most probably because it is still in DFU mode (thus it is shown as Maple 003). If the flash is successful, when replugging the underglow LEDs will lit in RGB mode. |
Hi delianto, I disconnected and reconnected the board, and it still shows up as Maple 003. Do you happen to know how to get out of DFU mode? |
|
@Bestmixtape you probably have rev1, the rev2 has an arm chip with 128kb flash. It should show up as a stm32duino
|
Hi @thompson-vii, thanks for the reply. That's what it shows up on mine. It says Maple 003 in both QMK toolbox and Device Manager. Is this what it should be listed as after reboot too? |
|
flash it with stock firmware |
Hay, did you get it to work? Mine uses the same Chip, i don't want to brick my Board with a wrong Firmware. |
it work, u need to flash rev 2 version and everything will be fine |
|
I got it to work using then flashing it in QMK Does anyone know how to add more macros to it? 15 isn't enough for me. I want to use it with autohotkey so I want to set the keys to random shortcuts so that I can run commands from one click without blocking any keys on my main keyboard. On VIAL site it says keymaps/vial/config.h - but there isn't a config.h in this directory. And the files in that directory don't have any lines of code that say "macros" in them. If not then is there a way to assign tap dance keys to autohotkey like TD(0):: |
|
This is better discussed on the QMK discord, rather than adding noise to a closed PR.
|
Where can I get that? |
Description
Due to the shortage ATMEGA32U4, DOIO has changed the PCB on KB16 into APM32F103CBT6. So this PR is make for that version.
And I have to refactor entire keyboard folder, to split them out.
Types of Changes
Issues Fixed or Closed by This PR
Checklist