I bought a cheap Durgod Hades with the intention of sticking the QMK/VIA firmware on it.

First issue was getting it into the bootloader - the instructions didn’t seem to be working, so I was trying different connection points and implements until it finally kicked into life. In doing that I suspect I may have killed the STM32… but I’m not sure.

Using dfu-util I’ve tried :unprotect:force and :mass-erase:force to try and recover it, and also downloaded STM32Cube to see if I have more luck with that.

dfu-util, no matter what I do, hangs at the erase point 0%. Eventually it times out with an error.

STM32Cube connects to the keyboard but complains it’s in read-only or reset held. If I try again with the suggested Read Unprotect option it says I need to power off and power on the device, and the cycle continues.

So I think I’ve somehow bust it, is there anything else I can try before admitting defeat and getting another one?

  • Metafalls_ (any)@beehaw.org
    2·
    4 days ago

    Im not too familiar with STM32, but I think this should apply on all QMK-based device: is the default program still accessible after you disconnect then reconnect the device?

    If the answer is yes, then your keyboard is probably fine. That said, I am afraid I can’t help you past that.

    Add: If you have access to Discord, you might want to hit QMK Discord server and see if there are any community member that can help you with the issue.

    • Chris@feddit.ukOPEnglish
      1·
      4 days ago

      Thanks, it wasn’t running the default after unplugging and replugging. I ended up replacing it, although I still have the dead one as I’m not sure what to do with it!