diff options
author | Jean Cyr <jcyr@dillobits.com> | 2014-04-22 01:19:01 -0400 |
---|---|---|
committer | Jean Cyr <jcyr@dillobits.com> | 2014-04-22 01:19:01 -0400 |
commit | bf4558c31b46bb5d7b30729dd23302048447a890 (patch) | |
tree | 82bb45047dfe13732dba98c06b22102e3249805e /src/modules/att_pos_estimator_ekf | |
parent | af336603517a32b86481c5f57d9be51657eb3f0d (diff) | |
download | px4-firmware-bf4558c31b46bb5d7b30729dd23302048447a890.tar.gz px4-firmware-bf4558c31b46bb5d7b30729dd23302048447a890.tar.bz2 px4-firmware-bf4558c31b46bb5d7b30729dd23302048447a890.zip |
Reduce data manager SD card wear and tear
When the data manager was first designed each file record contained a 2
byte header and an 126 byte data section, resulting in a record length
of 128 bytes. Along the way it was decided to add 2 spare bytes to the
record header, but regrettably the data section was not correspondingly
reduced in size so we end up with a record length of 130 bytes. This is
bad since it does not align with SD card flash sectors and results in
more erase/write flash cycles than necessary thus reducing the SD cards
life.
This update reduced the data section of the data manager to 124,
resulting in an optimal record length of 128 bytes.
In order to avoid the reuse of data previously written data in the old
format, which could result in catastrophic misinterpretation, the data
manager file is checked at startup. If it is found to be in the old
format, it is deleted and recreated with in the new record length. In
this case previously stored data is lost, but that is far safer than the
unpredictable result of using the old file.
Diffstat (limited to 'src/modules/att_pos_estimator_ekf')
0 files changed, 0 insertions, 0 deletions