kmk_firmware VS MicroPython

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!

I'll link to it because many people don't know a version of Python runs on microcontrollers:

https://micropython.org/

I'm personally working on something like this for the ESP32, but written on top of micropython [1]. A few things are written in C such as the display driver, but otherwise most things are in micropython. We chose the T-Watch 2020 V3 microphone variant as the platform [2].

Our objective is to build a modern PDA device via a mostly stand-alone watch that can be synced across devices (initially the Linux desktop). We want to achieve tasks that you might typically do on your desktop, focussed towards productivity.

We did consider a custom OS, but decided against it for a few reasons:

1. Allowing somebody else to handle basic OS stuff allows us to concentrate on what really matters, the higher level stuff on top.

2. Having multiple threads in micropython is super simple and we are able to run many active apps at the same time, rather than having to kill them off [3]. Our background apps can continuously interact with the network in the background.

3. Code written for micropython can be easily run on other Python-capable devices.

[1] https://micropython.org/

[2] https://lilygo.cc/products/t-watch-2020-v3

[3] https://tactility.one/#/application-lifecycle

tools/mpy_ld.py: https://github.com/micropython/micropython/blob/master/tools...

tools/mpy-tool.py lists opcodes: https://github.com/micropython/micropython/blob/master/tools...

Can the same be done with .pyc files; what are the advantages of MicroPython native modules?

Why does it need wasm2c?

For more: https://micropython.org/

For context

> MicroPython is a lean and efficient implementation of the Python 3 programming language that includes a small subset of the Python standard library and is optimised to run on microcontrollers and in constrained environments.

https://micropython.org/

Just putting my hand up to say that MicroPython is awesome (and runs on the RP2040). https://micropython.org