hasu@tmk

did you push program button on the pcb? You should get output like below in /var/log/kern.log or other log file when you press the button. ``` Jun 20 10:18:36 desk...

yes, the red button. Refer to this also. https://github.com/tmk/tmk_keyboard/wiki#flash-firmware

Yes, TMK HHKB Alt Controller uses 'atmega32u4'. Just plug usb cable normally and then push the button to start bootloader(program/flash mode). Do you see a line like below in output...

Also try it on Windows if possible.

You can 'printf debug' using UART(or software UART) instead of USB. Use `print_set_senchar()` to change debug print destination, see https://github.com/tmk/tmk_keyboard/blob/master/keyboard/hhkb/rn42/main.c#L41 and https://github.com/tmk/tmk_keyboard/blob/master/keyboard/hhkb/rn42/suart.S . Or buy cheap USB protocol analyzer if...

It makes sense. I like to change LED api it self later but this would be useful until then. Only adding the attribute 'weak' is enough for this pupose? don't...

I just tested, it can compiled as you said but it stops working or run away when pressing Capslock. From my understanding with weak attribute symbols are compiled as 0(EDIT:...

I guess we have two solutions; 1. give default implementation In common/led.c: ``` __attribute__((weak)) void led_set(uint8_t usb_led) { } ``` or use alias like: `__attribute__((weak, alias("_led_set")))` ? 1. check before...

Thanks for the suggestion! i'll take into account when I redesign macros.

As for unicode input it would be useful to have dedicated method, like QMK or Kaleidoscope? Kaleidoscope gives us clear idea on this. https://github.com/keyboardio/Kaleidoscope-Unicode https://github.com/keyboardio/Kaleidoscope-HostOS