POG (KMK) not compatible with CircuitPython 10.0.0 and above

[szafranski]

Hi,

I programmed YD RP2040 without any issues. Now I wanted to use smaller MCU (RP2040-Zero),
but I constantly got this:

�]0;🐍code.py | 10.0.3�\starting keyboard RPtest (01K94JTPWSEX1ARJ5VAH452RVF)
66579 kmk.keyboard: Initialising POGKeyboard
Traceback (most recent call last):
File "kmk/kmk_keyboard.py", line 440, in go
File "kmk/kmk_keyboard.py", line 475, in _init
File "kmk/kmk_keyboard.py", line 288, in _init_hid
File "kmk/hid.py", line 301, in init
File "kmk/hid.py", line 320, in wait_until_connected
File "kmk/scheduler.py", line 57, in create_task
AttributeError: 'TaskQueue' object has no attribute 'push_head'
66588 kmk.keyboard: cleaning up...
Traceback (most recent call last):
File "code.py", line 30, in
File "kmk/kmk_keyboard.py", line 453, in go
File "kmk/kmk_keyboard.py", line 295, in _deinit_hid
TypeError: function takes 1 positional arguments but 0 were given
�]0;🐍295@kmk/kmk_keyboard.py TypeError | 10.0.3�
Code done running.
Press any key to enter the REPL. Use CTRL-D to reload.

Any ideas how can this be fixed?

Regards

[szafranski]

I made more research. Issue is not linked with RP2040-Zero usage, but with CircuitPython 10.0.0 and above. I tried another board and got this:

After changing to CirPyth 9.2.9 everything works fine.

Finding older versions of CirPyth can be tricky on the site tbh. Cheers, happy to help if needed

[szafranski]

After some investigation - KMK itself barely works with CP10. Even some extensions are broken. Most issues are related to KMK, Only thing that can be strictly linked to POG is coordmap. CP10 doesn't allow "leading zeros" as far as a researched. So map should more look like:

coord_mapping = [
0,1,2,3,4,5,               11,10,9,8,7,6,
12,13,14,15,16,17,            23,22,21,20,19,18,
]

than

coord_mapping = [
000,001,002,003,004,005,            011,010,009,008,007,006,
012,013,014,015,016,017,            023,022,021,020,019,018,
]

[JanLunge]

My current issue with this is either

• make the changes work backwards compatible with cp9 and cp8 as users have these installed too.
• make a version detection just for this

Or just tell people to install v9. I'd like to version lock everything as then things dont break out of nowhere.
Adjusting the coordmap should not be an issue i will have a look at that