TODO LIST

[ZiGaMi]

TODO:

• parameters definition based on single table
• parameters API as simple as it gets (set/get function)
• following types shall be supported: uint8_t, int8_t, uint16_t, int16_t, uint32_t, int32_t, float32_t
• shall support two access: read_only and read_write
• option for parameter to be "watch only" by giving variable reference to it
• each parameter shall have name and unit
• each parameter shall have init value as also max and min

[ZiGaMi]

TODO (cont.):

• parameters shall have persistance flag (to tell if will be stored into NVM)
• parameters shall have ID (based on ID there will be stored into NVM memory location)

STORING POLICY:

• table shall have unique identifier to represents itself
• unique ID of parameter table shall be stored to NVM beside persistance parameters
• at device POR parameter table unique ID is being check from NVM and compared with current. In case of match values from NVM parameters table will be loaded to device. In opposite case NVM table will be erased/rewritten with new table.

[ZiGaMi]

TODO (cont.):

• regarding checking param table change it shall be disabled when device is released. Amplification: When device is on the field with all its calibrated factors etc. it should not be ok that with new FW upgrade all this parameters will be deleted. Solution to this is that when device is release there shall not be any change of old param table. But it would be allowed to add some additional parameters with free parameters IDs.

[ZiGaMi]

STORING POLICY (cont.):

• Store parameter ID beside parameter value and CRC
  • therefore storing address of par to NVM will not be defined only by ID
  • storing parameter consecutive into memory space

[ZiGaMi]

Not all features has been implemented but most of all are done in 129cf43c723f772c9148664adff2dbcc92b03263

This issue will be closed with still some missing TODO topics that will be address on new issue