Hardcoded Configuration: Difference between revisions
No edit summary |
|||
| Line 18: | Line 18: | ||
Getting a firmware setup with the desired parameters requires editing the code by hand and compile it. As we understand not all of you are necessarily comfortable doing so we have build a set of firmware ready to flash. This list is in [[IDCode]]. | Getting a firmware setup with the desired parameters requires editing the code by hand and compile it. As we understand not all of you are necessarily comfortable doing so we have build a set of firmware ready to flash. This list is in [[IDCode]]. | ||
We give each individual firmware a 8 digit random code to make sure we can identify it. For example | |||
Revision as of 15:02, 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.
Firmware with hardcoded configuration
Getting a firmware setup with the desired parameters requires editing the code by hand and compile it. As we understand not all of you are necessarily comfortable doing so we have build a set of firmware ready to flash. This list is in IDCode.
We give each individual firmware a 8 digit random code to make sure we can identify it. For example