My keyboard (see it in
https://geekhack.org/index.php?topic=81777.0) has developed a problem. I have uploaded a very short (sorry for the low video quality!) video at:
Has anyone seen this sort of behavior whereby the key does not consistently "fire" and sometimes doubles up on output?
Could this simply be a bad soldering job on my part, or would it be more likely to be a bug in the TMK firmware (and note that I'm using a forked copy which probably needs to be refreshed from upline)?
If it is in the firmware: I have now figured out how to use hid_listen to see debugging output, and can modify my forked version of TMK source code as needed. Then where in the code would I start instrumenting with "printf" (or whatever is the equivalent that sends output to hid_listen) to start debugging?
My leaning is toward a bad soldering job on my part (and I can open up the case and closely examine the G key's soldering points), but am first soliciting opinions as the best place to start debugging this.
Thanks,
bg