MK32 VS kmk_firmware

You will find very little esp-idf based resources, outside of the espressif documentation. If you dive in, you might be able to get it. I’ve been trying to figure out how to get a proS3 board to be used as the controller for a Bluetooth keyboard. Your hill is steep. But it can be done MK32 aaaaaand that’s the end of esp-idf related links, in case anyone gets annoyed by links that are not esp-idf, be forewarned the next links are just that. hackaday asterics t-vK best of luck, I truly hope you figure it out and leave breadcrumbs for the rest of us. Or sell your esp s2 board for the big bucks.

It might be worth looking into an ESP32 board and the MK32 firmware. It won’t be as feature rich as QMK, but I think it will get the job done.

Hey guys! I'm building my first keyboard and trying to get experience before spending a lot on a nice one. I'm 3D printing the "pcb" (can it even be called that?) and hand-wiring everything. I'll either end up using the MK32 firmware or KMK on an ESP32. Anyway, I was looking at backlight options and found most controllers that can control individual LEDs in large numbers (like the IS31FL3731) are fairly expensive and can be hard to find. Now they might not have as many features, but what about chips like the MY9221 (this uses two) or MAX7219? They cost the same as a few switches and consume very little power. The MAX7219 seems perfect for a budget build and is well-supported, but before I go learn how to make my own custom driver and spend a lot of time, is there a reason these chips are not used?

The main event started when I realize I have all the parts to Frankenstein together a working wireless keyboard, all inspired by this post and this post. The Ducky One uses a 15x8 matrix for all of the 108 keys. The way they wired it would be a nightmare for hand-wiring but I am just piggy riding on the existing PCB with an ESP32 that has enough GPIO pins. The firmware is based on the MK32 project but I have to modify parts of it to properly make use of GPIO34-39. That was intended for split keyboards so it is fair that nobody tried to hook up 23 GPIO and left nothing for an encoder or OLED display.

check this out to see if it fits before coding too much.

plenty.. try their zulip and you will see(https://kmkfw.zulipchat.com/).. also google may help... plenty of youtube pushers also will provide you the info...

Im not really sure where the problem would be. Try to flash the example firmware from the official kmk github and see if that works for you. If it doesn't then there may be a problem with the hardware 🤔 https://github.com/KMKfw/kmk_firmware/tree/master/boards/reviung41

You'll need to copy the following onto storage device: 1. CircuitPython files/binaries for controller, if not present 2. kmk folder from KMK firmware. github, if not present. 3. kb.py and main.py files for your board. Pre-configured boards can be found in KMK firmware github in boards directory.

I'll try to set it up locally and will otherwise contact... Got time over Easter. Thx a lot. I also have seen that piantor for KMK has an open pull request which means the board dev will soon be ready for workflow builds of Miryoku. https://github.com/KMKfw/kmk_firmware/pull/723 I like KMK a bit more as it will allow me to quickly change the extra keys to whatever makes sense .... All just with s simple text editor.

Here's a pull request to add piantor board to KMK firmware. The logic to define config for left and right halves is actually really nice.

There's a recent pull request to add the Piantor to KMK, and that's a split 42 key that uses the pico with direct pins to keys: https://github.com/KMKfw/kmk_firmware/pull/723

See above. I set this up some time ago; the one I am using is pretty much the demo one from the KMK github.

I've uploaded these files to github here if you wish to look around but I recommend also looking through the various boards in the kmk github as well for more guidance too. This was my first kmk based keyboard so my code might not be the best lol but I hope this is helpful regardless. Let me know if you have any questions!