Can't reset eeprom about qmk_toolbox HOT 9 CLOSED

Hi, which keyboard is this? Are you still able to flash the firmware with the Toolbox?

from qmk_toolbox.

Hi, which keyboard is this? Are you still able to flash the firmware with the Toolbox?

Mine is called unigo66.
I can only reset EEPROM with toolbox 0.0.9, I can flash the firmware with 0.0.9 and 0.0.10 both.

from qmk_toolbox.

Not really sure what's going on here, as it's working perfectly fine for me. You can add the EEP_RST keycode to your keymap, which will do the same thing. Please also try to reset the EEPROM from the Toolbox after that.

from qmk_toolbox.

I just came across this issue while helping someone else out with their board, version 0.0.10 kept spitting out the following error when attempting to reset the EEPROM, even after reinstalling toolbox, restarting and replugging the board.

We were able to successfully reset the EEPROM by using version 0.0.9 as stated by @kls1991

from qmk_toolbox.

There was a change in how the EEPROM reset is handled. Unfortunately, it seems to cause issues, in some cases.

If you download this file, you can flash it:
https://raw.githubusercontent.com/qmk/qmk_toolbox/3d7c9b4c32f1bb7db49e4b0c2a65859fca20bd27/common/atmega32u4_eeprom_reset.hex

But you'll need to flash another HEX file after that.

from qmk_toolbox.

We still need to find a good solution for this

from qmk_toolbox.

I got it it to work, but I'm not sure if it was my ordering of events or the fact I used an older version:

https://github.com/qmk/qmk_toolbox/releases/tag/0.0.9

Steps:

1. Opened QMK
2. "Reset" (top right button)
3. Loaded eeprom_reset.hex @drashna linked above
4. "Reset EEPROM" button on bottom right (this worked -- it was not working before)
5. Loaded my custom file

from qmk_toolbox.

@internetirl there's a couple of things happening here - first of all, the Reset button is for exiting the bootloader mode (where supported). It doesn't cause the keyboard to jump to the bootloader, and in fact, allowing that is probably not a good idea from a security standpoint.

eeprom_reset.hex is not an actual firmware file that can be flashed using the Toolbox. It has nothing to do with the Reset EEPROM button. You have to run the commands in the README next to it in order to clear it, and it requires you to reflash your layout.

Prior to version 0.0.10 EEPROM reset works, but it has to do a full chip erase first too. This is a limitation of the Atmel factory DFU bootloader, and again requires you to reflash. QMK-DFU (LUFA-DFU) does allow you to write to EEPROM without erasing... and it seems I never actually tested #75 on Atmel-DFU.

I think I will have to add back the erase step, as it appears non-trivial to obtain the actual reported device name on Windows to distinguish between Atmel DFU and QMK DFU.

from qmk_toolbox.

Seems like the above linked PR indicates it fixed this issue, closing.

from qmk_toolbox.