Screwed up a DZ60 with win10

Learning and discussion Firmware, programming, and hardware compatability
1

Have DZ60 PC00002 09.10 board. Using a KBDfans plastic plate (variant A 2.0U LShift).

kbdfans: /collections/60/products/dz60-60-pcb

kbdfans: /collections/60-layout-plate-1/products/60-pc-material-plate?variant=19633279631418

Was trying to debug why the space bar, and the right adjacent switch weren’t working.

I wanted to reflash with a new hex file using QMK Toolbox. I chose the correct “Local File” but I accidentally left “Keyboard from qmk.fm” blank. I (1) cleared the EEPROM and (2) Flashed the hex file. It didn’t complain and seemed to work.

*** QMK Toolbox 0.0.20 (https://qmk.fm/toolbox)
    Supported bootloaders:
     - Atmel/LUFA/QMK DFU via dfu-programmer (http://dfu-programmer.github.io/)
     - Caterina (Arduino, Pro Micro) via avrdude (http://nongnu.org/avrdude/)
     - Halfkay (Teensy, Ergodox EZ) via Teensy Loader (https://pjrc.com/teensy/loader_cli.html)
     - ARM DFU (STM32, Kiibohd) via dfu-util (http://dfu-util.sourceforge.net/)
     - Atmel SAM-BA (Massdrop) via Massdrop Loader (https://github.com/massdrop/mdloader)
     - BootloadHID (Atmel, PS2AVRGB) via bootloadHID (https://www.obdev.at/products/vusb/bootloadhid.html)
    Supported ISP flashers:
     - USBTiny (AVR Pocket)
     - AVRISP (Arduino ISP)
     - USBasp (AVR ISP)
*** Atmel DFU device connected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
>>> dfu-programmer.exe atmega32u4 erase --force
>>> dfu-programmer.exe atmega32u4 flash --force --eeprom "reset.eep"
*** Please reflash device with firmware now
    Erasing flash...  Success
    0%                            100%  Programming 0x80 bytes...
    Checking memory from 0x0 to 0x6FFF...  Empty.
    [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  Success
    0%                            100%  Reading 0x400 bytes...
    [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  Success
    Validating...  0 invalid bytes in program region, 891 outside region.
    FAIL
    Memory did not validate. Did you erase?
*** Attempting to flash, please don't remove device
>>> dfu-programmer.exe atmega32u4 erase --force
    Erasing flash...  Success
    Checking memory from 0x0 to 0x6FFF...  Empty.
>>> dfu-programmer.exe atmega32u4 flash --force "C:\Users\chivo\Downloads\dz60_layout_60_ansi_mine.hex"
    0%                            100%  Programming 0x5B80 bytes...
    [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  Success
>>> dfu-programmer.exe atmega32u4 reset
    0%                            100%  Reading 0x7000 bytes...
    [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  Success
    Validating...  Success
    0x5B80 bytes written into 0x7000 bytes memory (81.70%).

But the keyboard emerged in a weird state:

  1. not all the RGB lights are on
  2. keyboard doesn’t type

I tried to reset, clear eeprom, plug/unplug, but QMK Toolbox stubbornly says “There are no devices available” anbd “No HID console interfaces found”

zzz
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  Success
Validating...  Success
0x5B80 bytes written into 0x7000 bytes memory (81.70%).
*** Atmel DFU device disconnected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
*** Atmel DFU device connected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
*** Atmel DFU device disconnected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
*** Atmel DFU device disconnected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
*** Atmel DFU device connected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
  ! There are no devices available
  ! There are no devices available
*** Atmel DFU device disconnected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
  ! There are no devices available
*** Atmel DFU device disconnected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
*** Atmel DFU device connected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
*** Atmel DFU device connected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
*** Atmel DFU device disconnected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
*** Atmel DFU device connected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
  ! There are no devices available
*** No HID console interfaces found.
*** Atmel DFU device disconnected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)
*** Atmel DFU device connected (libusb0): Atmel Corp. ATmega32U4 (03EB:2FF4:0000)

Not sure what to do. I tried to remove the driver from device manager and reinstall using the QMK_driver_installer. No improvement.

(base) C:\Users\chivo\Downloads\qmk_driver_installer\qmk_driver_installer>qmk_driver_installer --force drivers.txt

image
image845×1281 88.9 KB

Any ideas on how to recover this? I don’t know whether I bricked the microntroller with screwed up .hex file, or the driver/win10 is now somehow screwed up.

2

Atmega32u4 is listed in your device list, so at least the DFU bootloader is working and you have not bricked your PCB.
You should be able to write a new firmware, now to look for the right one…

4

I managed to get the eeprom cleared and reloaded the firmware to the layout that partially worked. Not sure what the fix was. I had just been annoyed for a while and unplugged everything and turned off QMK Toolbox. Whe I tried to clear/reflash it worked… I also noticed that when I plugged it all back it, windows recognized it as a generic HID Keyboard and no longer as an Atmel.

5

Good, that means the keyboard booted its QMK firmware.
Atmel DFU is launched either when no firmware is installed or if reset is done either by:

  • pressing the reset button.
  • maintain the configured key in the QMK firmware (often ESC or the key in row 0 and column 0) pressed while plugging the keyboard.

Happy you have partly recovered your board :wink: