Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Erase before clearing EEPROM #185

Merged
merged 2 commits into from
Apr 14, 2020
Merged

Erase before clearing EEPROM #185

merged 2 commits into from
Apr 14, 2020

Conversation

nooges
Copy link
Member

@nooges nooges commented Apr 7, 2020

Description

Rollbacks the removal of the erase command done in #75 and adds a message to remind user to reflash firmware.

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Documentation

Issues Fixed or Closed by This PR

@drashna
Copy link
Member

drashna commented Apr 10, 2020

In this case, wouldn't it be better to have "erase eeprom" as a checkbox, and have it part of the flash firmware option?

This way, there is less of a possibility for users to screw up?

@fauxpark
Copy link
Member

My goal is to have the Toolbox determine whether to do a full chip erase or not by looking at the USB device revision - QMK-DFU will have 0x0936 (qmk/lufa#7) whenever we update the LUFA submodule again, and people start generating bootloaders from that. Obviously... this will miss pre-existing QMK-DFUs.

Another option would be to just bruteforce it, try the EEPROM clear on its own first and check if it failed before running a full chip erase.

@drashna drashna merged commit 1080229 into qmk:master Apr 14, 2020
@nooges nooges deleted the erase-before-clear branch May 3, 2020 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants