Difference between revisions of "Configuration Update"
| Line 1: | Line 1: | ||
==Configuration Location== | ==Configuration Location== | ||
The current configuration is stored in a non-volatile memory (EEPROM). The current configuration can be changed via the web user interface. When hit the “Apply” button the new values are stored into the EEPROM. | The current configuration is stored in a non-volatile memory (EEPROM). The current configuration can be changed via the web user interface. When hit the “Apply” button the new values are stored into the EEPROM. | ||
Revision as of 14:04, 27 March 2009
Configuration Location
The current configuration is stored in a non-volatile memory (EEPROM). The current configuration can be changed via the web user interface. When hit the “Apply” button the new values are stored into the EEPROM.
Factory defaults using Serial Rescue
The EEPROM is overwritten during a Serial Rescue by the factory defaults configuration using the binary file config.bin which is located in the folder “update_rescue” of the delivered Firmware Update Kit. This file can be edited with a hex editor. Consult the “configuration memory usage” table carefully before you make any changes.
Factory defaults using Web Update
The “factory defaults configuration” (config.bin) is also contained in the application image which is loaded into the flash memory. When applying the “Web Update” make sure to apply the “factory defaults configuration” by pushing the reset button for more than 10 seconds.
