Author Topic: TMK USB to USB keyboard converter (Read 591814 times)

pupmonster · « **Reply #900 on:** Fri, 01 March 2024, 00:37:34 »

I continued with my testing of miniM_ab4b44.hex and populated it with my layout.

It solved a problem with the previous last-working version where keystrokes would strangely appear that I had not typed. Perhaps this information is useful to you.

pupmonster · « **Reply #901 on:** Sat, 02 March 2024, 03:20:08 »

Continuing testing ...
Perhaps it was not the intention of the interim file you provided, but using it, I have not been able to remap the bottom-row control keys, e.g. left-option, japanese_pc_nfer, japanese_pc_xfer, japanese_pc_katakana.

hasu · « **Reply #902 on:** Sat, 02 March 2024, 03:57:33 »

This is not what I expected, I missed something probably.
I'll have to start over debug process.

Quote from: pupmonster on Thu, 29 February 2024, 00:42:31

Hasu, here are the results:
miniM_ab4b44.hex: All keys register
miniM_woHubFix.hex: No keys register

The firmwares I attached before were built only for debug and cannot be remapped with keymap editor.

Use one attached in this post if you need to remap. This firmware is not full-function but should work.

Quote from: pupmonster on Sat, 02 March 2024, 03:20:08

Continuing testing ...
Perhaps it was not the intention of the interim file you provided, but using it, I have not been able to remap the bottom-row control keys, e.g. left-option, japanese_pc_nfer, japanese_pc_xfer, japanese_pc_katakana.

miniM_ab4b44_unimap.hex (71.92 kB - downloaded 104 times.)

pupmonster · « **Reply #903 on:** Sat, 02 March 2024, 07:21:01 »

Merci! That helps a lot!

hasu · « **Reply #904 on:** Sat, 02 March 2024, 08:46:51 »

Can you try these fimwares to when you have time?
And let me know your result.

Thank you

miniM_35606b.hex (56.54 kB - downloaded 103 times.)

miniM_a98e6f.hex (59.45 kB - downloaded 101 times.)

pupmonster · « **Reply #905 on:** Sat, 02 March 2024, 22:24:23 »

Here are my results as tested on Mac and Linux

miniM_35606b.hex:
all keys register
behaviour while typing is as desired (no strange extra character inserts)
capslock light comes on
numlock light does not come on
scrolllock light does not come on

miniM_a98e6f.hex:
all keys register
behaviour while typing is as desired (no strange extra character inserts)
capslock light comes on
numlock light does not come on
scrolllock light does not come on

hasu · « **Reply #906 on:** Tue, 05 March 2024, 02:01:07 »

pupmonster,

I don't find a fault point yet. Can you try these also?
Post debug prints if it fails.

Thank you for your help.

miniM_85af76.hex (60.41 kB - downloaded 106 times.)

miniM_df8e64.hex (61.97 kB - downloaded 107 times.)

pupmonster · « **Reply #907 on:** Tue, 05 March 2024, 10:25:21 »

Hasu, glad to assist.

Here you go:

miniM_85af76.hex: no keys register
miniM_df8e64.hex: no keys register

Tested on MacOS and Linux.

hasu · « **Reply #908 on:** Wed, 06 March 2024, 00:21:15 »

Can you post debug prints from miniM_85af76.hex?

This fix affects the issue, perhaps.
https://github.com/tmk/USB_Host_Shield_2.0/commit/9072c34c6fc669d696a8f0a99807e076531a2163

pupmonster · « **Reply #909 on:** Wed, 06 March 2024, 09:33:45 »

I am not sure I did what you need, but this is what I have:

I flashed the keyboard with miniM_85af76.hex, and started hid_listen as root on Linux. I pressed every key from left to right, top to bottom.

The results are in the next message as an attachment. It is named "out.hex" because when I tried to upload a file with a .txt extension the server gave me an uncaught exception. The same happened when I tried to insert the output into this message.

hasu · « **Reply #910 on:** Wed, 06 March 2024, 23:48:31 »

That log is what I needed. Thank you.

I think I found one of the causes at least and fixed it.

miniM_fix_5ed16b.hex (61.9 kB - downloaded 218 times.)

Can you try this and share debug prints?

Use this procedure to get debug prints.
1. run hid_listen
2. plug in the converter first and wait for 5 sec
3. plug in the keyboard then
4. press a few keys

pupmonster · « **Reply #911 on:** Thu, 07 March 2024, 03:20:34 »

Results here inline, as attachment somehow was disallowed by forum:

Code: [Select]

sudo ./hid_listen 

Waiting for device:....
Listening:

TMK:5ed16b/LUFA:d6a7df/UHS2:df8e64
u:20
[S][W][W]u:40
u:50
u:51
[W]BM Init
Addr:01
NC:01
HID_PROTOCOL_KEYBOARD
bNumEP:02
Cnf:01
bIfaceNum:00
bNumIface:00

Interface:00
SET_PROTOCOL: 00
SET_IDLE: 00
RPIPE: 00
RWU: 00
BM configured
u:90
s:f

USB configured.
[i]
Loop start.
usb_state: 90
speed: full
input 1: 00 00 0A 00 00 00 00 00 00 00 00 00
00 00 0A 00 00 00 00 00 00 00 00 00 
ginput 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
input 1: 00 00 0B 00 00 00 00 00 00 00 00 00
00 00 0B 00 00 00 00 00 00 00 00 00 
hinput 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
input 1: 00 00 12 00 00 00 00 00 00 00 00 00
00 00 12 00 00 00 00 00 00 00 00 00 
oinput 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
input 1: 00 00 26 00 00 00 00 00 00 00 00 00
00 00 26 00 00 00 00 00 00 00 00 00 
9input 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
input 1: 00 00 49 00 00 00 00 00 00 00 00 00
00 00 49 00 00 00 00 00 00 00 00 00 
^[[2~input 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
input 1: 00 00 46 00 00 00 00 00 00 00 00 00
00 00 46 00 00 00 00 00 00 00 00 00 
input 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
·input 1: 00 00 45 00 00 00 00 00 00 00 00 00
00 00 45 00 00 00 00 00 00 00 00 00 
input 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
^C
steveg@fedora-t14:/data/apps$ sudo ./hid_listen 
Waiting for device:........
Listening:

TMK:5ed16b/LUFA:d6a7df/UHS2:df8e64
u:20
[S][W][W]u:40
u:50
u:51
[W]BM Init
Addr:01
NC:01
HID_PROTOCOL_KEYBOARD
bNumEP:02
Cnf:01
bIfaceNum:00
bNumIface:00

Interface:00
SET_PROTOCOL: 00
SET_IDLE: 00
RPIPE: 00
RWU: 00
BM configured
u:90
s:f

USB configured.
[i]
Loop start.
usb_state: 90
speed: full
input 1: 00 00 04 00 00 00 00 00 00 00 00 00
00 00 04 00 00 00 00 00 00 00 00 00 
ainput 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
input 1: 00 00 16 00 00 00 00 00 00 00 00 00
00 00 16 00 00 00 00 00 00 00 00 00 
sinput 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
input 1: 00 00 52 00 00 00 00 00 00 00 00 00
00 00 52 00 00 00 00 00 0^[[A0 00 00 00 
input 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
input 1: 00 00 49 00 00 00 00 00 00 00 00 00
00 00 49 00 00 00 00 00 00 00 00 00 
^[[2~input 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
input 1: 00 00 43 00 00 00 00 00 00 00 00 00
00 00 43 00 00 00 00 00 00 00 00 00 
^[[21~input 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
input 1: 00 00 33 00 00 00 00 00 00 00 00 00
00 00 33 00 00 00 00 00 00 00 00 00 
òinput 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
input 1: 00 00 8A 00 00 00 00 00 00 00 00 00
00 00 8A 00 00 00 00 00 00 00 00 00 
input 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 
input 1: 01 00 00 00 00 00 00 00 00 00 00 00
01 00 00 00 00 00 00 00 00 00 00 00 
input 1: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00

hasu · « **Reply #912 on:** Thu, 07 March 2024, 06:25:37 »

It looks good now according to the log.

Let me know if you still have a problem. I'll update firmware on Keymap Editor soon later if not.

Next time, you can use CODE tag to include debug output in your message on this forum.

https://en.wikipedia.org/wiki/BBCode
https://www.bbcode.org/showing-code-with-bbcode.php

pupmonster · « **Reply #913 on:** Thu, 07 March 2024, 10:07:07 »

Sounds good. Thanks so much. Your service is outstanding.

However, I do not quite understand how you intend to proceed or what I should ideally be doing on my end.

Should I use miniM_fix_5ed16b.hex as the basis of any adaptations to my keyboard layout in TMK Keymap Editor?

And ... I also just received the newest USB-USB adapter today in the mail. Thanks. Should I also use miniM_fix_5ed16b.hex there as well?

Or ... should I just start TMK Keyboard editor without first uploading a base hex file, in the understanding that the latest and greatest is being used automatically there?

Thanks much for the clarification!

hasu · « **Reply #914 on:** Thu, 07 March 2024, 18:03:02 »

miniM_fix_5ed16b.hex was built just for debug/test and it can be used with Keymap Editor.
With the fix the converter doesn't seem to have obvious problem with Mini M now.

I just updated firmware on github and Keymap Editor for Mini M support. Now you can edit keymap and download the fixed firmware on Keymap Editor.

https://www.tmk-kbd.com/tmk_keyboard/editor/unimap/?usb_usb

Thank you for your help.

pupmonster · « **Reply #915 on:** Fri, 08 March 2024, 10:20:30 »

Thanks, Hasu!

I thought you would like to know that I used the TMK Layout Editor to modify my layout of the Japanese Mini M using both my older USB-USB adapter and the brand-new adapter just received, and everything looks good.

paiste · « **Reply #916 on:** Thu, 11 April 2024, 14:39:14 »

Hi,

so does this work if there is a hub between the real keyboard and the converter? Is it possible to have the firmware supporting for mouse only? (We have a devices that accepts only keyboard or mouse directly attached, but we need to use a USB over LAN that shows up as hub between keyboard / mouse and the device? Need tens of units.

hasu · « **Reply #917 on:** Thu, 11 April 2024, 18:47:39 »

- My firmware with current configuration can support two hubs. Yes, you can use hub between the converter and keyboard.
- My firmware does not support mouse.

It is possible for the converter to support hub, keyboard and mouse technically if you can write custom code for that.

timd · « **Reply #918 on:** Sat, 19 October 2024, 16:49:28 »

Hi Hasu,

I received my usb-usb converter the other day (thanks!), and I've been partly successful using it with my Chilkey ND75. Everything is good if I use the USB cable connection, however I'm not able to get it working with the 2.4G wireless dongle.

I was hoping that if I post the debug & dump hid_listen logs that you might be able to help?

usb_usb_debug.hex:

Code: [Select]

Waiting for device:
Listening:
usb_state: 20
usb_state: 40
usb_state: 50
usb_state: 51
BM Init
Addr:01
NC:01
HID_PROTOCOL_KEYBOARD
bNumEP:01
D1
>>>>BUSRST
BM Init
Addr:01
NC:01
HID_PROTOCOL_KEYBOARD
bNumEP:01
D1
>>>>BUSRST
BM Init
Addr:01
NC:01
HID_PROTOCOL_KEYBOARD
bNumEP:01
D1
>>>>BUSRST
BM Init
Addr:01
NC:01
HID_PROTOCOL_KEYBOARD
bNumEP:01
D1
>>>>BUSRST
>>>>BUSRST
>>>>BUSRST
host.Task: 2457
usb_state: 90
speed: full

usb_desc_dump.hex:

Code: [Select]

Waiting for device:
Listening:

TMK:7b2827/LUFA:d6a7df/UHS2:96112d
Start

USB configured.

Loop start.
usb_state: 12
usb_state: 20
usb_state: 40
usb_state: 50
usb_state: 51
usb_state: 90

//////////////////////////////////////////////////////////////////////
// USB_desc_dump
// Address: 01
// Lowspeed: 00

// Devicer dump:
12 01 10 01 00 00 00 08 45 0C FE FE 23 01 01 02
00 01

// Device:
bLength:		12
bDescriptorType:	01
bcdUSB:			0110
bDeviceClass:		00
bDeviceSubClass:	00
bDeviceProtocol:	00
bMaxPacketSize0:	08
idVendor:		0C45
idProduct:		FEFE
bcdDevice:		0123
iManufacturer:		01
iProduct:		02
iSerialNumber:		00
bNumConfigurations:	01

// String Zero: len: 04
// 04 03 09 04
// LangId: 0409

// iManufacturer: ERROR: 05

// iProduct: String2(0409): len: 18
// 18 03 32 00 2E 00 34 00 47 00 20 00 44 00 6F 00
// 6E 00 67 00 6C 00 65 00
// 2.4G Dongle

// Config0 dump:	len: 0094
09 02 94 00 05 01 00 A0 23 09 04 00 00 01 03 00
00 00 09 21 00 01 00 01 22 48 00 07 05 81 03 08
00 01 09 04 01 00 01 03 00 00 00 09 21 00 01 00
01 22 3D 00 07 05 82 03 08 00 01 09 04 02 00 01
03 00 00 00 09 21 00 01 00 01 22 CD 00 07 05 83
03 10 00 01 09 04 03 00 02 03 00 00 00 09 21 00
01 00 01 22 22 00 07 05 85 03 30 00 01 07 05 05
03 30 00 01 09 04 04 00 02 03 00 00 00 09 21 00
01 00 01 22 22 00 07 05 86 03 40 00 01 07 05 06
03 40 00 01

// Config:
bLength:		09
bDescriptorType:	02
wTotalLength:		0094
bNumInterfaces:		05
bConfigurationValue:	01
iConfiguration:		00
bmAttributes:		A0
bMaxPower:		23

// Interface0.0:
bLength:		09
bDescriptorType:	04
bInterfaceNumber:	00
bAlternateSetting:	00
bNumEndpoints:		01
bInterfaceClass:	03
bInterfaceSubClass:	00
bInterfaceProtocol:	00
iInterface:		00

// HID: 
bLength:		09
bDescriptorType:	21
bcdHID:			0100
bCountryCode:		00
bNumDescriptors:	01
bDescrType:		22
wDescriptorLength:	0048

// Report0 dump:	len: 0048
05 01 09 06 A1 01 05 07 19 E0 29 E7 15 00 25 01
75 01 95 08 81 02 95 01 75 08 81 01 95 03 75 01
05 08 19 01 29 03 91 02 95 05 75 01 91 01 95 05
75 08 26 FF 00 05 07 19 00 29 FF 81 00 05 FF 09
03 75 08 95 01 81 02 C0

// Endpoint:
bLength:		07
bDescriptorType:	05
bEndpointAddress:	81
bmAttributes:		03
wMaxPacketSize:		0008
bInterval:		01

// Interface1.0:
bLength:		09
bDescriptorType:	04
bInterfaceNumber:	01
bAlternateSetting:	00
bNumEndpoints:		01
bInterfaceClass:	03
bInterfaceSubClass:	00
bInterfaceProtocol:	00
iInterface:		00

// HID: 
bLength:		09
bDescriptorType:	21
bcdHID:			0100
bCountryCode:		00
bNumDescriptors:	01
bDescrType:		22
wDescriptorLength:	003D

// Report0 dump:	len: 003D
05 01 09 02 A1 01 09 01 A1 00 05 09 19 01 29 03
15 00 25 01 95 05 75 01 81 02 95 01 75 03 81 01
05 01 09 30 09 31 09 38 15 81 25 7F 75 08 95 03
81 06 95 01 05 0C 0A 38 02 81 06 C0 C0

// Endpoint:
bLength:		07
bDescriptorType:	05
bEndpointAddress:	82
bmAttributes:		03
wMaxPacketSize:		0008
bInterval:		01

// Interface2.0:
bLength:		09
bDescriptorType:	04
bInterfaceNumber:	02
bAlternateSetting:	00
bNumEndpoints:		01
bInterfaceClass:	03
bInterfaceSubClass:	00
bInterfaceProtocol:	00
iInterface:		00

// HID: 
bLength:		09
bDescriptorType:	21
bcdHID:			0100
bCountryCode:		00
bNumDescriptors:	01
bDescrType:		22
wDescriptorLength:	00CD

// Report0 dump:	len: 00CD
05 0C 09 01 A1 01 85 01 19 00 2A 3C 03 15 00 26
3C 03 95 01 75 10 81 00 C0 05 01 09 80 A1 01 85
02 05 01 19 81 29 83 15 00 25 01 95 03 75 01 81
02 95 01 75 05 81 01 C0 05 01 09 06 A1 01 85 03
05 07 15 00 25 01 19 00 29 77 95 78 75 01 81 02
C0 05 01 09 0E A1 01 85 06 05 0D 09 21 A1 00 05
09 09 01 95 01 75 01 15 00 25 01 81 02 05 01 09
37 95 01 75 0F 55 0F 65 14 36 F0 F1 46 10 0E 16
F0 F1 26 10 0E 81 06 09 30 75 10 55 0D 65 13 35
00 46 C0 5D 15 00 26 FF 7F 81 02 09 31 46 B0 36
81 02 05 0D 09 48 36 B8 0B 46 B8 0B 16 B8 0B 26
B8 0B 81 03 C0 C0 06 FF FF 09 01 A1 01 85 05 09
01 15 00 26 FF 00 75 08 95 03 81 02 C0

// Endpoint:
bLength:		07
bDescriptorType:	05
bEndpointAddress:	83
bmAttributes:		03
wMaxPacketSize:		0010
bInterval:		01

// Interface3.0:
bLength:		09
bDescriptorType:	04
bInterfaceNumber:	03
bAlternateSetting:	00
bNumEndpoints:		02
bInterfaceClass:	03
bInterfaceSubClass:	00
bInterfaceProtocol:	00
iInterface:		00

// HID: 
bLength:		09
bDescriptorType:	21
bcdHID:			0100
bCountryCode:		00
bNumDescriptors:	01
bDescrType:		22
wDescriptorLength:	0022

// Report0 dump:	len: 0022
06 60 FF 09 61 A1 01 09 62 15 00 26 FF 00 95 20
75 08 81 02 09 63 15 00 26 FF 00 95 20 75 08 91
02 C0

// Endpoint:
bLength:		07
bDescriptorType:	05
bEndpointAddress:	85
bmAttributes:		03
wMaxPacketSize:		0030
bInterval:		01

// Endpoint:
bLength:		07
bDescriptorType:	05
bEndpointAddress:	05
bmAttributes:		03
wMaxPacketSize:		0030
bInterval:		01

// Interface4.0:
bLength:		09
bDescriptorType:	04
bInterfaceNumber:	04
bAlternateSetting:	00
bNumEndpoints:		02
bInterfaceClass:	03
bInterfaceSubClass:	00
bInterfaceProtocol:	00
iInterface:		00

// HID: 
bLength:		09
bDescriptorType:	21
bcdHID:			0100
bCountryCode:		00
bNumDescriptors:	01
bDescrType:		22
wDescriptorLength:	0022

// Report0 dump:	len: 0022
06 60 FF 09 61 A1 01 09 62 15 00 26 FF 00 95 40
75 08 81 02 09 63 15 00 26 FF 00 95 40 75 08 91
02 C0

// Endpoint:
bLength:		07
bDescriptorType:	05
bEndpointAddress:	86
bmAttributes:		03
wMaxPacketSize:		0040
bInterval:		01

// Endpoint:
bLength:		07
bDescriptorType:	05
bEndpointAddress:	06
bmAttributes:		03
wMaxPacketSize:		0040
bInterval:		01

// Parse data here: http://eleccelerator.com/usbdescreqparser/

Many thanks,
Tim

hasu · « **Reply #919 on:** Mon, 21 October 2024, 04:49:47 »

Hi Tim,
Thanks for the info.

It seems interface0 is boot keyboard compatible but it does not assert itself as a 'Boot keyboard' in USB descriptor for some reason. So Chilkey ND75 dongle is not a boot keyboard and the converter cannot detect it.

I'll look into to find a workaround for the dongle.

timd · « **Reply #920 on:** Mon, 21 October 2024, 13:50:36 »

Quote from: hasu on Mon, 21 October 2024, 04:49:47

I'll look into to find a workaround for the dongle.

Thank you

hasu · « **Reply #921 on:** Tue, 22 October 2024, 09:35:14 »

timd,
Can you try attached firmware and post its log?

Thanks

usb_usb_debug.hex (64.3 kB - downloaded 27 times.)

timd · « **Reply #922 on:** Tue, 22 October 2024, 09:52:18 »

Thanks hasu - here's the log:

Code: [Select]

Waiting for device:
Listening:
usb_state: 20
usb_state: 40
usb_state: 50
usb_state: 51
BM Init
Addr:01
NC:01
vid:0C45
pid:FEFE
HID_PROTOCOL_KEYBOARD
bNumEP:02
Cnf:01sssddddd
bIfaceNum:01
bNumIface:00

Interface:00
skip SET_PROTOCOL
SET_IDLE: 00
RPIPE: 00
RWU: 00
BM configured
host.Task: 2327
usb_state: 90
speed: full

It isn't picking up any keystrokes.

hasu · « **Reply #923 on:** Tue, 22 October 2024, 11:04:41 »

hmm, It seems to work still in nkro mode.
we have to make keyboard turn into 6kro boot mode, perhaps. This firmware may work.

usb_usb_debug.hex (64.35 kB - downloaded 26 times.)

timd · « **Reply #924 on:** Tue, 22 October 2024, 14:55:04 »

Hi Hasu, here's the log:

Code: [Select]

Waiting for device:
Listening:
usb_state: 20
usb_state: 40
usb_state: 50
usb_state: 51
BM Init
Addr:01
NC:01
vid:0C45
pid:FEFE
HID_PROTOCOL_KEYBOARD
bNumEP:02
Cnf:01
bIfaceNum:01
bNumIface:00

Interface:00
SET_PROTOCOL: 00
SET_IDLE: 00
RPIPE: 00
RWU: 00
BM configured
host.Task: 2327
usb_state: 90
speed: full

~~Still no key presses recognised.~~

Thanks,
Tim

timd · « **Reply #925 on:** Tue, 22 October 2024, 16:05:08 »

Sorry, not sure what I did before... I was rushing as it was half-time in the football.

It's registering input now - thank you for looking into this:

Code: [Select]

Waiting for device:
Listening:
usb_state: 20
usb_state: 40
usb_state: 50
usb_state: 51
BM Init
Addr:01
NC:01
vid:0C45
pid:FEFE
HID_PROTOCOL_KEYBOARD
bNumEP:02
Cnf:01
bIfaceNum:01
bNumIface:00

Interface:00
SET_PROTOCOL: 00
SET_IDLE: 00
RPIPE: 00
RWU: 00
BM configured
host.Task: 2328
usb_state: 90
speed: full
input 1: 00 00 0B 00 00 00 00 00
00 00 0B 00 00 00 00 00 
hinput 1: 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 
input 1: 00 00 0B 00 00 00 00 00
00 00 0B 00 00 00 00 00 
hinput 1: 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 
input 1: 00 00 0B 00 00 00 00 00
00 00 0B 00 00 00 00 00 
hinput 1: 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 
input 1: 00 00 0E 00 00 00 00 00
00 00 0E 00 00 00 00 00 
kinput 1: 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 
input 1: 00 00 14 00 00 00 00 00
00 00 14 00 00 00 00 00 
qinput 1: 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 
input 1: 00 00 1A 00 00 00 00 00
00 00 1A 00 00 00 00 00 
winput 1: 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 
input 1: 00 00 08 00 00 00 00 00
00 00 08 00 00 00 00 00 
einput 1: 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 
input 1: 00 00 15 00 00 00 00 00
00 00 15 00 00 00 00 00 
rinput 1: 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 
input 1: 00 00 17 00 00 00 00 00
00 00 17 00 00 00 00 00 
tinput 1: 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 
input 1: 00 00 1C 00 00 00 00 00
00 00 1C 00 00 00 00 00

Regards,
Tim

hasu · « **Reply #926 on:** Wed, 23 October 2024, 01:55:27 »

OK. I updated firmware on Keymap Editor and github.

You can download the fixed firmware on Keymap Editor now.
Let me know if you have any problem.

Thanks

timd · « **Reply #927 on:** Wed, 23 October 2024, 15:42:06 »

Thanks for your time debugging the issue, Hasu.

I've added a bit more information to the github issue https://github.com/tmk/tmk_keyboard/issues/778, but I just realised you may not have been notified as the issue is closed now. Basically, the keyboard isn't always recognised correctly, and the connection doesn't get re-established if the keyboard goes to sleep and is woken up.

Regards,
Tim

News:

Author Topic: TMK USB to USB keyboard converter (Read 591814 times)