fwcommon

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'DEN-7605-hd_dg_dev-self-tests' into develop

DEN-7605: Fixed misspelled function name.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Merge branch 'DEN-7605-hd_dg_dev-self-tests' into develop

DEN-7605: Fixed epoch to date/time conversion.

Merge branch 'DEN-7605-hd_dg_dev-self-tests' into develop

DEN-7605: Added support for UI clock sync.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

DEN-8103: Refactor RTC accuracy self-test

Changed to use treatmentTimeMS to increase the log time.

Changed to use treatmentTimeMS to increase the log time.

DEN-8103: Updated doxygen comment

DEN-8103: Allow callers to give the initial value for crc32

Removed. UI will be the logger, so the clock comes from only one source.

Removed. UI will be the logger, so the clock comes from only one source.

It took around 55 ms for the largest section (.text). I have imposed a maximum size per each CRC calculation, which takes around 7 ms each.

It took around 55 ms for the largest section (.text). I have imposed a maximum size per each CRC calculation, which takes around 7 ms each.

Done.

Done.

Done.

Done.

Removed.

Removed.

Done.

Done.

Change PERIOD to PERIODIC?

Change PERIOD to PERIODIC?

How long does this take? We may need to break this loop into smaller pieces and have ModeInitPOST call this function multiple times so that general task does not take too long (> 40ms or so). Other...

How long does this take? We may need to break this loop into smaller pieces and have ModeInitPOST call this function multiple times so that general task does not take too long (> 40ms or so). Otherwise, watchdog will not get pet within its ~50ms window and expire - and also other general and background operations will be blocked until this test is completed.

This enum is getting big. Should we put it in its own .h file (AlarmMgmtSWFaults.h) with same doxygen group name (AlarmManagement) that would be included by this header?

This enum is getting big. Should we put it in its own .h file (AlarmMgmtSWFaults.h) with same doxygen group name (AlarmManagement) that would be included by this header?