{"action":"created","issue":{"url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/1388","labels_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/1388/labels{/name}","comments_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/1388/comments","events_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/1388/events","html_url":"https://github.com/MarlinFirmware/Marlin/issues/1388","id":54825279,"number":1388,"title":"Reset EEPROM when the layout changes","user":{"login":"thinkyhead","id":698003,"avatar_url":"https://avatars.githubusercontent.com/u/698003?v=3","gravatar_id":"","url":"https://api.github.com/users/thinkyhead","html_url":"https://github.com/thinkyhead","followers_url":"https://api.github.com/users/thinkyhead/followers","following_url":"https://api.github.com/users/thinkyhead/following{/other_user}","gists_url":"https://api.github.com/users/thinkyhead/gists{/gist_id}","starred_url":"https://api.github.com/users/thinkyhead/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thinkyhead/subscriptions","organizations_url":"https://api.github.com/users/thinkyhead/orgs","repos_url":"https://api.github.com/users/thinkyhead/repos","events_url":"https://api.github.com/users/thinkyhead/events{/privacy}","received_events_url":"https://api.github.com/users/thinkyhead/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/MarlinFirmware/Marlin/labels/Feature+request","name":"Feature request","color":"006b75"},{"url":"https://api.github.com/repos/MarlinFirmware/Marlin/labels/Improvement","name":"Improvement","color":"009800"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-01-19T23:30:08Z","updated_at":"2015-01-20T14:15:46Z","closed_at":null,"body":"Issues like #1378 and others indicate that new EEPROM layouts can cause Marlin to break on new installs, because Marlin tries to read the old layout as the new one. There needs to be either:\r\n\r\n- Code that converts the previous layout version(s) to the new layout\r\n\r\nor\r\n\r\n- Code that resets the EEPROM and (tries to) present a message to the user\r\n\r\nIs it OK to clear the EEPROM for users who may have stored values that don't match their configuration, if possibly they won't notice that this has occurred? Or, is it better to allow users to encounter undefined behavior, but instruct them to clear the EEPROM when flashing new firmware should issues occur?"},"comment":{"url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/comments/70659035","html_url":"https://github.com/MarlinFirmware/Marlin/issues/1388#issuecomment-70659035","issue_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/1388","id":70659035,"user":{"login":"Booli","id":5080263,"avatar_url":"https://avatars.githubusercontent.com/u/5080263?v=3","gravatar_id":"","url":"https://api.github.com/users/Booli","html_url":"https://github.com/Booli","followers_url":"https://api.github.com/users/Booli/followers","following_url":"https://api.github.com/users/Booli/following{/other_user}","gists_url":"https://api.github.com/users/Booli/gists{/gist_id}","starred_url":"https://api.github.com/users/Booli/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Booli/subscriptions","organizations_url":"https://api.github.com/users/Booli/orgs","repos_url":"https://api.github.com/users/Booli/repos","events_url":"https://api.github.com/users/Booli/events{/privacy}","received_events_url":"https://api.github.com/users/Booli/received_events","type":"User","site_admin":false},"created_at":"2015-01-20T14:15:46Z","updated_at":"2015-01-20T14:15:46Z","body":"Yep, did some research and found that the boot loader lacks: chip erase(because it would erase itself) and some more commands.\r\n\r\nSo, that's not an option."}}