sym key functionality (Improvement)

[DanHolli]

I'm not sure if it already has functionality that just isn't used in English (us) but I feel like sym+1-9,0.#,* should map to f1-f12 and/or act as a menu or AltGr

[DanHolli]

other potential combos
sym+up/down=volume/brightness up/down
sym+left/right=media back/next
sym+select=Play/Pause
sym+0="="
sym+"(" / ")"="[" / "]"
sym+ "/" = "\"

[grymoire]

I'm using the sym key to send CRTL-codes on Linux.

[DanHolli]

I wasn't able to see this in action, but I'll check it out

[grymoire]

This is after I've modified the firmware. However, I still have some issues to resolve,, as I learn how the HID keyboards work. My goal is to use the top 4 keys to send all of the missing ASCII characters + ability to send control codes, making the keyboard useful for a small Kali-based system.

[DanHolli]

Just checked it out and noticed it wasn't working, then I saw your reply XD

Sounds neat, but it would also be nice if it could also be used by more typical systems like Mac and Windows...
Maybe down the road you can figure out a way to make two separate builds at once or make a mode switch? I'm not a code guy so I don't know if that possible though
I also noticed a matrix in keyboard.c that appears to map all the buttons, will this be adapted to also work with sym?

[grymoire]

I'm not a sophisticated git user, but I published a repository of my changes
https://github.com/grymoire/i2c_puppet
It adds support for Control-keys and the missing characters, using the button keys on top.
I don't think I did this right

[grymoire]

Here's the updated version.
https://github.com/grymoire/i2c_puppet-Linux

[eviscerat]

@grymoire Hi, how do I actually flash your code onto the keyboard? I managed to build it but I m not understanding how to add the new functionality.

[grymoire]

It's micropython. You build it and then plug the keyboard in and copy the i2c_puppet.uf2 onto the RPI-RP2 filesystem

…

On Tue, Jan 17, 2023, 11:09 AM Augustus Marius ***@***.***> wrote: @grymoire <https://github.com/grymoire> Hi, how do I actually flash your code onto the keyboard? I managed to build it but I m not understanding how to add the new functionality. — Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAX3WUC5LB47NS44PAOI6Y3WS273FANCNFSM5XCPYHJQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[eviscerat]

@grymoire One more thing, Where are the actual compiled files. I cloned the project and submodules, made build dir and ran ccmake -DPICO_BOARD=bbq20kbd_breakout -DCMAKE_BUILD_TYPE=Debug ... But I got nothing in the elf2uf2 directory or any uf2 files in a similar output directory.

My compile output seems to have succeeded:

CMAKE_BUILD_TYPE=Debug ..
PICO_SDK_PATH is /home/lucian/radxa-stuff/keyboard_software_alternative/i2c_puppet-Linux/3rdparty/pico-sdk
PICO platform is rp2040.
Using regular optimized debug build (set PICO_DEOPTIMIZED_DEBUG=1 to de-optimize)
PICO target board is bbq20kbd_breakout.
Using board configuration from /home/lucian/radxa-stuff/keyboard_software_alternative/i2c_puppet-Linux/boards/bbq20kbd_breakout.h
TinyUSB available at /home/lucian/radxa-stuff/keyboard_software_alternative/i2c_puppet-Linux/3rdparty/pico-sdk/lib/tinyusb/src/portable/raspberrypi/rp2040; enabling build support for USB.
Compiling TinyUSB with CFG_TUSB_DEBUG=1
-- Configuring done
-- Generating done
-- Build files have been written to: /home/lucian/radxa-stuff/keyboard_software_alternative/i2c_puppet-Linux/build

EDIT: nevermind, forgot to run make after that. Also compiled files are in app dir

[grymoire]

Look for ./build/app/i2c_puppet.uf2 And if you want the additional sym key functions, make sure you are using my repository https://github.com/grymoire/i2c_puppet-Linux and check my notes on testing, etc. https://github.com/grymoire/i2c_puppet-Linux/blob/main/LINUX.md

…

On Tue, Jan 17, 2023 at 3:14 PM Augustus Marius ***@***.***> wrote: @grymoire <https://github.com/grymoire> One more thing, Where are the actual compiled files. I cloned the project and submodules, made build dir and ran cmake -DPICO_BOARD=bbq20kbd_breakout ... But I got nothing in the elf2uf2 directory or any uf2 files in a similar output directory. My compile output: PICO_SDK_PATH is /home/lucian/radxa-stuff/keyboard_software_alternative/i2c_puppet-Linux/3rdparty/pico-sdk PICO platform is rp2040. Defaulting PICO platform compiler to pico_arm_gcc since not specified. -- Defaulting build type to 'Release' since not specified. PICO compiler is pico_arm_gcc -- The C compiler identification is GNU 9.2.1 -- The CXX compiler identification is GNU 9.2.1 -- The ASM compiler identification is GNU -- Found assembler: /usr/bin/arm-none-eabi-gcc PICO target board is bbq20kbd_breakout. Using board configuration from /home/lucian/radxa-stuff/keyboard_software_alternative/i2c_puppet-Linux/boards/bbq20kbd_breakout.h -- Found Python3: /usr/bin/python3.8 (found version "3.8.10") found components: Interpreter TinyUSB available at /home/lucian/radxa-stuff/keyboard_software_alternative/i2c_puppet-Linux/3rdparty/pico-sdk/lib/tinyusb/src/portable/raspberrypi/rp2040; enabling build support for USB. -- Configuring done -- Generating done -- Build files have been written to: /home/lucian/radxa-stuff/keyboard_software_alternative/i2c_puppet-Linux/build — Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAX3WUG5AU5LXZALWWKRIJDWS34SDANCNFSM5XCPYHJQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>