Read config from EEPROM only if no config is in Flash #327
Conversation
elral
changed the title
|
Board and firmware folder for this pull request: |
|
Board and firmware folder for this pull request: |
|
For backward compatibility it is first checked, if a config in EEPROM is available. If so, this config will still be used. It is still possible, to upload a user config even if a config in flash is available. This overrules the flash config. |
|
Board and firmware folder for this pull request: |
|
Board and firmware folder for this pull request: |
Co-authored-by: Sebastian M <[email protected]>
Co-authored-by: Sebastian M <[email protected]>
|
Board and firmware folder for this pull request: |
|
Board and firmware folder for this pull request: |
|
Board and firmware folder for this pull request: |
Description of changes
If a configuration is already saved in the EEPROM, and the board gets updated with a new Firmware where the configuration is part of the flash, the exsiting configuration in the EEPROM gets ignored and only the one from the flash gets reported to the connector and loaded into the internal memory.
Before sending the configuration to the connector, it gets's checked if a configuration is stored in the flash. If this is the case (configLength > 0), this configuration is send to the connector. If no config in the flash is available (configLength = 0) but a config in the EEPROM saved, this config gets send to the connector.
The same applies for loading the config into the internal memory.
For now it is only checked if a configuration in the EEPROM
ORFlash is available. If a configuration is saved, this one gets reported to the connector and loaded into the internal memory.Fixes #326