Hardcoded Configuration: Difference between revisions
(Created page with " RPICT series have a convenient way to store the configuration in memory using the lcl-rpict-config.py tool. It is found that eeprom memory might not be always stable especi...") |
No edit summary |
||
| Line 10: | Line 10: | ||
'''Which board can use the hardcoded configuration?''' | '''Which board can use the hardcoded configuration?''' | ||
All of them. However the way to flash the microcontroller will differ from one board to another. | All of them. However the way to flash the microcontroller will differ from one board to another. | ||
The RPICT produced lately will make this easier. For the former ones some special operations might be needed. | The RPICT produced lately will make this easier. For the former ones some special operations might be needed. | ||
Revision as of 14:56, 30 October 2021
RPICT series have a convenient way to store the configuration in memory using the lcl-rpict-config.py tool.
It is found that eeprom memory might not be always stable especially in noisy industrial environment. This usually lead in having to reconfigure the card.
For users requiring high level of stability and minimum intervention we suggest the use of hardcoded configuration.
The hardcoded configuration means that all user parameters are set in the code of the firmware. This require reflashing the microcontroller. Following that parameters can only be modified by reflashing a new firmware with the updated value.
Which board can use the hardcoded configuration?
All of them. However the way to flash the microcontroller will differ from one board to another.
The RPICT produced lately will make this easier. For the former ones some special operations might be needed.