UHK 60 doesn't work after upgrade v15.0.1

General
1

After upgrade to 15.0.1, UHK 60 doesn’t work.

At the beggining left keyboard and cluster module worked.but soon after none of the key responsed.
Indicater showed FTY, so I changed the cable to new one,but doesn’t work well.
Get off the key and push reset button,but doesn’t work well.

Does anyone have same issue?

Below is the code after pushing reset key backside the keyboard.
Printing trace buffer because: Looks like your uhk60 crashed.
EV: 0
Tag: v15.0.1
=== K22P121M120SF7 Reset Cause Debug ===
RCM_SRS0: 0x00
RCM_SRS1: 0x04
RCM_SSRS0: 0x82
RCM_SSRS1: 0x04
PMC_LVDSC1: 0x10
PMC_LVDSC2: 0x00
PMC_REGSC: 0x04
SCB_HFSR: 0x00000000
SCB_CFSR: 0x00000000
SCB_BFAR: 0xE000ED38
SCB_MMFAR: 0xE000ED34

=== Reset Cause Analysis ===
Trace:
}{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}{()
}{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}<i1

{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}<i4
{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}{()}###

2

FTY may be shown on uhk60 because you have pressed the reset button. If it was shown even before pressing the reset button, it probably indicates a problem with User Configuration.

The reset cause log is a false positive. It should go away if you upgrade to 15.1.0 or higher (from Releases · UltimateHackingKeyboard/firmware · GitHub ).

In other words, please upgrade to 15.2.0, then make sure to save the config to your UHK. Then let us know whether it works. If not, then please post your UserConfig.json.

3

Thank you for your reply!
I updated to version 15.2.0, and initially, only the left keyboard was functional.
FTY error has not shown anymore.
When I then reverted the UserConfig.json file to its default settings, the right keyboard began working, although it felt a bit awkward (the response was delayed, some keystrokes were ignored,behaviors of long press and right-click are visible).
However, after switching back to my original UserConfig.json, the right keyboard stopped working again.

Could you check my json please?
I could not share json file directly, here is the code via Codepen

4

Is this the newest Agent?

We have seen this bug before.

I have opened a ticket at UserConfig migration: Extra layer after UserConfig upgrade. · Issue #2742 · UltimateHackingKeyboard/agent · GitHub . It would be appreciated if you subscribed it, wrote some short comment there (just a hi so that we know that you are watching) and be available for Robi’s questions.

Especially appreciated then would be your UserConfig history folder (in Agent, go to Settings → Open configuration folder → open Electron and take user-configs) and an information which firmware version you were on before the upgrade and which Agent you used for the upgrade.

As for your config, I have fixed its structure manually: https://github.com/user-attachments/files/22574297/UserConfig_yoyo_fixed.json I hope it will work fine.

5

Thanks a lot! I set the config you made for me!!

I tried unbrick but nothing changed.

BTW,the modules suddenly stopped being recognized after several attempts to change the firmware version.
In the firmware tab, the right keyboard and left keyboard are all displayed, but the left cluster module and , and right trackball do not appear.
Although the other components (keyboardsl) can be updated successfully, connecting modules causes error (despite it not being recognized).
here is the error code

Have there been any previous instances of this issue? I apologize for bringing forward a potentially new problem.

image
image1074×940 82.5 KB

6

Why are you trying to downgrade the firmware?

Does the edited config not work?

7

Sorry if I have not been clear: your firmware is fine and the uhk works fine. The only issue is that migration of your UseConfig to new version failed for some reason.

You need to:

  • flash 15.2.0 (if you are not on it already)
  • import and save the above fixed config

If there are any problems after that, please first enable leds (segment display and backlight) and then tell us what you see.

8

I apologize for the confusion and the somewhat complicated situation. I attempted a downgrade to see if a different version would improve performance.

  • The config file seems to be working, as I successfully imported the configuration file you created for me.
  • I have now upgraded to ver 15.2, and I am no longer getting any errors.

The only remaining issue is that the Left Cluster Module cannot be loaded. I’ve tried forcefully re-seating it, applying contact cleaner spray, and rebooting, all without success. I have also visually inspected the metal contacts and confirmed they show no corrosion or damage. I had never experienced a similar issue until this current set of troubles began.

Other Information Shared

  • The Agent software version is 8.0.0, both before and after the issue started.
  • The errors initially occurred after a firmware update. (I don’t recall the original version, perhaps ver12 or ver14? The version after the update was 15.0.1, labeled as “bundled with Agent”).
  • I did not make any configuration changes or add any macros at the time of the firmware update.
  • Regarding third-party tools (assuming you mean software): I may have used some in the past, but I have confirmed that no related software is currently installed.
  • I have never manually edited user settings (i.e., I have never directly modified the code; all edits were made through the Agent interface).
9

The only remaining issue is that the Left Cluster Module cannot be loaded. I’ve tried forcefully re-seating it, applying contact cleaner spray, and rebooting, all without success. I have also visually inspected the metal contacts and confirmed they show no corrosion or damage. I had never experienced a similar issue until this current set of troubles began.

The config seems fine (i.e., works on mine uhk80)

Please try the module unbricking procedure: https://ultimatehackingkeyboard.com/repair/unbricking-modules

1 Like
10

Thank you for replying me.
Congfigue looks perfect.

I tried unbricking procedure,but it didn’t work.

I suspect there might be an issue with the electrical system of the cluster module.

I need to determine if the problem lies with the left keyboard body itself or the cluster module. Do you have any good ideas for how I can troubleshoot this? If it’s just a module issue, buying a replacement might solve it.

I’ve been using this for almost three years and I love it. This might be a good opportunity to buy a new one.

==========================================
unbricking procedure erorr code
[DeviceService] stop poll UHK Device

[DeviceService] stopped poll UHK Device

[DeviceService] UHK Module recovery starts: {“id”:2,“asCliArg”:“uhk60v2”,“firmwareUpgradeMethod”:“kboot”,“logName”:“UHK 60 v2”,“name”:“UHK 60 v2”,“keyboard”:[{“vid”:7504,“pid”:24868},{“vid”:14248,“pid”:3}],“bootloader”:[{“vid”:7504,“pid”:24867}],“buspal”:[{“vid”:7504,“pid”:24865},{“vid”:14248,“pid”:2}],“reportId”:0}

[DeviceService] UHK Module: {“id”:2,“name”:“Key cluster”,“configPath”:“/add-on/key-cluster”,“slotId”:2,“i2cAddress”:32,“firmwareUpgradeSupported”:true}

[UhkOperations] Start flashing “Key cluster” module firmware

[UhkHidDevice] Device communication closing.

[UhkHidDevice] Device communication closed.

[UhkHidDevice] Start reenumeration, mode: NormalKeyboard, timeout: 5000ms

[UhkHidDevice] Reenumerating devices

[UhkHidDevice] Device communication closing.

[UhkHidDevice] Available devices unchanged

[UhkHidDevice] Used device: {“vendorId”:“0x37A8”,“productId”:“0x3”,“path”:“\\?\HID#VID_37A8&PID_0003&MI_04#9&1f50f274&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}”,“serialNumber”:“5001047770”,“manufacturer”:“Ultimate Gadget Laboratories”,“product”:“UHK 60 v2”,“release”:2,“interface”:4,“usagePage”:65280,“usage”:1}

[UhkHidDevice] Device communication closing.

[UhkHidDevice] Device communication closed.

[UhkHidDevice] Available devices unchanged

11

So the flashing didn’t succeed? (Rather than successfully flashed, but didn’t solve the problem.)

I find hardware failure rather unlikely.

As for the unbricking procedure for the module, it may be worth to capture logs with --log=usb and opening an Agent ticket so that Robi takes a look.

It may also be worth to try resetting the user config (just for a temporary test: reset, powercycle, test, return to your normal config).

1 Like