Closed gottwald closed 3 years ago
Give https://github.com/kinx-project/qmk_firmware/commit/c61d90b80415343d86b9c0c1b659823aaaee47c9 a try — I think the LEDs just weren’t wired up before.
But, the GPIO functionality is working now, so I think the wiring should be okay. In a quick test, this made the Caps Lock LED work for me on my Teensy 4.1 board.
Edit: I also figured out that the multimeter LED test procedure only seems to work when there is no micro controller on the board, i.e. is only useful during soldering or if you decide to use a socket.
Thank you! Works like a charm. I was only able to verify CAPS_LOCK due to my layout but re-measured the pins and now the measurements on all LED pins make sense so I'm pretty sure the others are also OK.
I've built the board with a Teensy 4.1 and used the firmware form your qmk_firmware fork (https://github.com/kinx-project/qmk_firmware) and kint41 branch (e2f82ab2dac). I've used the exact components from the guide.
Mostly stuff seems to work but none of the LEDs do.
I've done some measurements and I'm a bit confused by the results:
3V3_2
pin of the cross row. I also didn't forget to solder it.12
,24
,25
,26
GND
,GND mounting pad
,GND 3
).0L
in forward and reverse bias. I use a Brymen BM257s which IIRC has a 1V range for diode testing which might be the reason). But I can make them all light up with some help from a 3V batteryHere's where it becomes strange:
12
,24
,25
,26
.The rest of the keyboard seems to work fine as I'm typing this issue on it. The only thing that doesn't work is waking up my mac from sleep with this keyboard, but I'm guessing this is more of a firmware thing.
Any idea what could be wrong?