One of my keyboards is the TEX Shura, which is shown as "04d9:0532 Holtek Semiconductor, Inc. USB-HID Keyboard" under lsusb in Linux; since this listing is the only one that's added when the device is plugged in, I'm inclined to suspect that there's no internal USB hub in the device.
After updating the firmware to v1.0.3 (the Shura did not function with the firmware on the device when first received at all), the Shura's keyboard now functions over the device as expected. However, any attempt to use the Trackpoint-style pointer on the keyboard causes the SterlingKey to vibrate and the LED indicating the active paired device to briefly turn off; no Trackpoint-related data is transmitted over the device. When plugged directly into my laptop via USB, though, the Shura's Trackpoint-style pointer functions as expected.
Let me know if there's any other information that I can provide on my end to help.
[RESOLVED] Partial Incompatibility with TEX Shura
-
- Member
- Posts: 3
- Joined: Tue Apr 02, 2024 8:18 pm
[RESOLVED] Partial Incompatibility with TEX Shura
Last edited by redyoshi49q on Wed Apr 10, 2024 2:43 am, edited 1 time in total.
Re: Partial Incompatibility with TEX Shura
Hello!
Since the keys work, I'm sure it's not recognized as a HUB, otherwise it wouldn't work at all.
I'm glad the new firmware at least partially fixed it. It seems that when you use the trackpoint, SterlingKey crashes and restarts, as indicated by the vibration and LED turning off and on. That means that it's receiving the trackpoint data, so I think that's a good sign.
There's probably an issue in the HID descriptor, I'm probably (hopefully) just parsing something wrong, which can be fixed with an update.
To verify this, could you please do the below?
Connect SterlingKey to a computer using the type c port (like you did when you updated it), while also having the keyboard connected to it. Then go to https://sterling-key.com/updater/ and below Console click on Start. It will open a popup, you will select the first (and probably only) device that shows up in that popup and then click Connect. Lastly, click Reset and it will give you some output. Wait until it is connected to your computer via Bluetooth, and use the trackpoint. It will crash and reset and show some duplicate logs, that's fine. Copy and paste all the output here, so I can read it and see if the "mouse" descriptor is missing.
You can safely unplug SterlingKey from the computer now.
Thank you.
Since the keys work, I'm sure it's not recognized as a HUB, otherwise it wouldn't work at all.
I'm glad the new firmware at least partially fixed it. It seems that when you use the trackpoint, SterlingKey crashes and restarts, as indicated by the vibration and LED turning off and on. That means that it's receiving the trackpoint data, so I think that's a good sign.
There's probably an issue in the HID descriptor, I'm probably (hopefully) just parsing something wrong, which can be fixed with an update.
To verify this, could you please do the below?
Connect SterlingKey to a computer using the type c port (like you did when you updated it), while also having the keyboard connected to it. Then go to https://sterling-key.com/updater/ and below Console click on Start. It will open a popup, you will select the first (and probably only) device that shows up in that popup and then click Connect. Lastly, click Reset and it will give you some output. Wait until it is connected to your computer via Bluetooth, and use the trackpoint. It will crash and reset and show some duplicate logs, that's fine. Copy and paste all the output here, so I can read it and see if the "mouse" descriptor is missing.
You can safely unplug SterlingKey from the computer now.
Thank you.
-
- Member
- Posts: 3
- Joined: Tue Apr 02, 2024 8:18 pm
Re: Partial Incompatibility with TEX Shura
This is the output that I get from the console:
Code: Select all
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x2b (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x44c
load:0x403c9700,len:0xbe4
load:0x403cc700,len:0x2a68
entry 0x403c98d4
E (21) ledc: leEVENT: 0
New Device
USB-HID Keyboard
wMaxPacketSize
8
wMaxPacketSize
64
wMaxPacketSize
64
wMaxPacketSize
64
wMaxPacketSize
64
wMaxPacketSize
64
Connected keyboard with name USB-HID Keyboard
Counter: 1nter: 0
controlCounter: 2
127
1
2
4
REPORT MAP:
0x05,
0x01,
0x09,
0x06,
0xa1,
0x01,
0x85,
0x7f,
0x05,
0x07,
0x19,
0xe0,
0x29,
0xe7,
0x15,
0x00,
0x25,
0x01,
0x75,
0x01,
0x95,
0x08,
0x81,
0x02,
0x95,
0x01,
0x75,
0x08,
0x81,
0x03,
0x95,
0x03,
0x75,
0x01,
0x05,
0x08,
0x19,
0x01,
0x29,
0x03,
0x91,
0x02,
0x95,
0x01,
0x75,
0x05,
0x91,
0x03,
0x95,
0x06,
0x75,
0x08,
0x15,
0x00,
0x26,
0xa4,
0x00,
0x05,
0x07,
0x19,
0x00,
0x29,
0xa4,
0x81,
0x00,
0xc0,
0x05,
0x01,
0x09,
0x80,
0xa1,
0x01,
0x85,
0x01,
0x19,
0x81,
0x29,
0x83,
0x15,
0x00,
0x25,
0x01,
0x95,
0x03,
0x75,
0x01,
0x81,
0x02,
0x95,
0x01,
0x75,
0x05,
0x81,
0x01,
0xc0,
0x05,
0x0c,
0x09,
0x01,
0xa1,
0x01,
0x85,
0x02,
0x15,
0x00,
0x25,
0x01,
0x95,
0x12,
0x75,
0x01,
0x0a,
0x83,
0x01,
0x0a,
0x8a,
0x01,
0x0a,
0x92,
0x01,
0x0a,
0x94,
0x01,
0x09,
0xcd,
0x09,
0xb7,
0x09,
0xb6,
0x09,
0xb5,
0x09,
0xe2,
0x09,
0xea,
0x09,
0xe9,
0x0a,
0x21,
0x02,
0x0a,
0x23,
0x02,
0x0a,
0x24,
0x02,
0x0a,
0x25,
0x02,
0x0a,
0x26,
0x02,
0x0a,
0x27,
0x02,
0x0a,
0x2a,
0x02,
0x81,
0x02,
0x95,
0x01,
0x75,
0x0e,
0x81,
0x01,
0xc0,
0x05,
0x01,
0x09,
0x06,
0xa1,
0x01,
0x85,
0x04,
0x05,
0x07,
0x95,
0x01,
0x75,
0x08,
0x81,
0x03,
0x95,
0xe8,
0x75,
0x01,
0x15,
0x00,
0x25,
0x01,
0x05,
0x07,
0x19,
0x00,
0x29,
0xe7,
0x81,
0x00,
0xc0,
BLE ready
200
Checking address:
9c:da:3e:f2:24:97
9c:da:3e:f2:24:97
7c:d0:96:24:8e:6d
Client connected with address: 9c:da:3e:f2:24:97
Checking address:
7c:d0:96:24:8e:6d
9c:da:3e:f2:24:97
7c:d0:96:24:8e:6d
Client connected with address: 7c:d0:96:24:8e:6d
0 0 0 0 0 0 0 0
3 0 0 0 255 255 0 0
Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.
Core 1 register dump:
PC : 0x4209fad3 PS : 0x00060e30 A0 : 0x82003b26 A1 : 0x3fcebde0
A2 : 0x00000000 A3 : 0x00000001 A4 : 0x0000000a A5 : 0x00060c23
A6 : 0x02c99edc A7 : 0x00ffffff A8 : 0x8200bab4 A9 : 0x3fcebdc0
A10 : 0x00000002 A11 : 0x3c0b4758 A12 : 0x0000000a A13 : 0x3fcf4b90
A14 : 0x02cecad8 A15 : 0x00ffffff SAR : 0x0000000a EXCCAUSE: 0x0000001c
EXCVADDR: 0x0000004c LBEG : 0x400556d5 LEND : 0x400556e5 LCOUNT : 0xffffffff
Backtrace: 0x4209fad0:0x3fcebde0 0x42003b23:0x3fcebe00 0x42002ea6:0x3fcebe20 0x4206cab0:0x3fcebe70 0x42003164:0x3fcebeb0 0x420049d6:0x3fcebed0 0x4200cf29:0x3fcebf20
ELF file SHA256: d1063d9636c16a13
Rebooting...
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU2b (SPI_FAST_FLASH_BOOT)
Saved ce3808,len:0x44c
load:0x403c9700,len:0xbe4
load:0x403cc700,len:0x2a68
entry 0x403c98d4
E (21) ledc: leEVENT: 0
New Device
USB-HID Keyboard
wMaxPacketSize
8
wMaxPacketSize
64
wMaxPacketSize
64
wMaxPacketSize
64
wMaxPacketSize
64
wMaxPacketSize
64
Connected keyboard with name USB-HID Keyboard
controlCounter: 0
controlCounter: 1
controlCounter: 2
127
1
2
4
REPORT MAP:
0x05,
0x01,
0x09,
0x06,
0xa1,
0x01,
0x85,
0x7f,
0x05,
0x07,
0x19,
0xe0,
0x29,
0xe7,
0x15,
0x00,
0x25,
0x01,
0x75,
0x01,
0x95,
0x08,
0x81,
0x02,
0x95,
0x01,
0x75,
0x08,
0x81,
0x03,
0x95,
0x03,
0x75,
0x01,
0x05,
0x08,
0x19,
0x01,
0x29,
0x03,
0x91,
0x02,
0x95,
0x01,
0x75,
0x05,
0x91,
0x03,
0x95,
0x06,
0x75,
0x08,
0x15,
0x00,
0x26,
0xa4,
0x00,
0x05,
0x07,
0x19,
0x00,
0x29,
0xa4,
0x81,
0x00,
0xc0,
0x05,
0x01,
0x09,
0x80,
0xa1,
0x01,
0x85,
0x01,
0x19,
0x81,
0x29,
0x83,
0x15,
0x00,
0x25,
0x01,
0x95,
0x03,
0x75,
0x01,
0x81,
0x02,
0x95,
0x01,
0x75,
0x05,
0x81,
0x01,
0xc0,
0x05,
0x0c,
0x09,
0x01,
0xa1,
0x01,
0x85,
0x02,
0x15,
0x00,
0x25,
0x01,
0x95,
0x12,
0x75,
0x01,
0x0a,
0x83,
0x01,
0x0a,
0x8a,
0x01,
0x0a,
0x92,
0x01,
0x0a,
0x94,
0x01,
0x09,
0xcd,
0x09,
0xb7,
0x09,
0xb6,
0x09,
0xb5,
0x09,
0xe2,
0x09,
0xea,
0x09,
0xe9,
0x0a,
0x21,
0x02,
0x0a,
0x23,
0x02,
0x0a,
0x24,
0x02,
0x0a,
0x25,
0x02,
0x0a,
0x26,
0x02,
0x0a,
0x27,
0x02,
0x0a,
0x2a,
0x02,
0x81,
0x02,
0x95,
0x01,
0x75,
0x0e,
0x81,
0x01,
0xc0,
0x05,
0x01,
0x09,
0x06,
0xa1,
0x01,
0x85,
0x04,
0x05,
0x07,
0x95,
0x01,
0x75,
0x08,
0x81,
0x03,
0x95,
0xe8,
0x75,
0x01,
0x15,
0x00,
0x25,
0x01,
0x05,
0x07,
0x19,
0x00,
0x29,
0xe7,
0x81,
0x00,
0xc0,
BLE ready
200
Checking address:
9c:da:3e:f2:24:97
9c:da:3e:f2:24:97
7c:d0:96:24:8e:6d
Client connected with address: 9c:da:3e:f2:24:97
0 0 0 0 0 0 0 0
Checking address:
7c:d0:96:24:8e:6d
9c:da:3e:f2:24:97
7c:d0:96:24:8e:6d
Client connected with address: 7c:d0:96:24:8e:6d
Re: Partial Incompatibility with TEX Shura
Thank you for the output.
I see that the mouse report is missing. I think I know why, I'll get back to you in a bit.
I see that the mouse report is missing. I think I know why, I'll get back to you in a bit.
Re: Partial Incompatibility with TEX Shura
Hey, could you try again with version 1.0.4-beta-3?
Make sure to unpair and pair again, as this is changing the HID Descriptor and it needs to be re-paired.
Make sure to unpair and pair again, as this is changing the HID Descriptor and it needs to be re-paired.
-
- Member
- Posts: 3
- Joined: Tue Apr 02, 2024 8:18 pm
Re: Partial Incompatibility with TEX Shura
After updating the firmware to v1.0.4-beta-3 and re-pairing the SterlingKey's Bluetooth connections to my laptop and phone, I can confirm that the Shura's keyboard and Trackpoint-style pointer are both functioning through the SterlingKey as expected. Thanks for the prompt update.
Re: [resolved] Partial Incompatibility with TEX Shura
Amazing, glad it's working now, enjoy!