kriomant / ch57x-keyboard-tool

Utility for programming ch57x small keyboard
MIT License
483 stars 59 forks source link

Upload command exits without error, but keyboard does not get new config #74

Closed casidiablo closed 2 weeks ago

casidiablo commented 5 months ago

Initially I was getting hit by #50

I was able to workaround it by any of these two methods:

In both cases, when executing the upload command, it seems to be doing something (because the command takes a few seconds to finish) but at the end of the day it does nothing. They keyboard does not actually emit the keys.

config.yaml ``` orientation: normal rows: 2 columns: 3 knobs: 1 layers: - buttons: - ["a", "ctrl-a", "b"] - ["e", "f", "g"] knobs: - ccw: "wheelup" press: "click" cw: "wheeldown" - buttons: - ["a", "ctrl-a", "b"] - ["e", "f", "g"] knobs: - ccw: "wheelup" press: "click" cw: "wheeldown" - buttons: - ["a", "ctrl-a", "b"] - ["e", "f", "g"] knobs: - ccw: "wheelup" press: "click" cw: "wheeldown" ```

I had to use the --endpoint-address 2 flag (to be honest, I do not know what that is, I am just following the advice in #69), because otherwise I get this:

Error: single interrupt endpoint is expected, got:
EndpointDescriptor {
    bLength: 7,
    bDescriptorType: 5,
    bEndpointAddress: 130,
    bmAttributes: 3,
    wMaxPacketSize: 8,
    bInterval: 10,
}
EndpointDescriptor {
    bLength: 7,
    bDescriptorType: 5,
    bEndpointAddress: 2,
    bmAttributes: 3,
    wMaxPacketSize: 8,
    bInterval: 10,
}

You may try to choose one using --endpoint-address

I tried with the endpoint 130, but then I get a Windows popup saying a device is not recognized or something like that.

I also find it interesting that after disconnecting/connecting the keyboard, if I turn the knob it will launch this:

image

By the way, they keyboard I have has 6 keys and 1 knob. Bought it on Temu but won't paste the link to it unless needed. This was the image in the listing:

image

casidiablo commented 5 months ago

I just realized that when I connect the keyboard it shows as CH552. So now I am not sure if that's why it does not work properly (the repo being for ch57x)

kriomant commented 2 weeks ago

Please check version 1.4.4