firmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-8103: Added alarm table size check

Is this needed. Should we just let Standby mode set actuators as it wants on entry?

Is this needed. Should we just let Standby mode set actuators as it wants on entry?

I think we should at least say that the mode variables are reset to re-start the mode or something.

I think we should at least say that the mode variables are reset to re-start the mode or something.

Why are some values aligned at left and others at right? I think all values should align at left.

Why are some values aligned at left and others at right? I think all values should align at left.

I'm assuming HET was enabled to get access to a GPIO pin? If so, do we need these notifications? Is there a place in HalCOGen to disable HET interrupts?

I'm assuming HET was enabled to get access to a GPIO pin? If so, do we need these notifications? Is there a place in HalCOGen to disable HET interrupts?

Not necessary - included in .h file.

Not necessary - included in .h file.

Please keep this case in last position in switch statement.

Please keep this case in last position in switch statement.

Why commented out?

Why commented out?

Remove comments or add TODO.

Remove comments or add TODO.

I think we can remove this test code now.

I think we can remove this test code now.

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.

Bamboo Commit: Updated DGCommon.h with build versions from Bamboo

Disabled CAL_CHECK build switch

DEN-8030: Updated heater PWM limits for V3.

DEN-8030 tested modes and continued developing chemical disinfect

    • -6
    • +53
    ./App/Controllers/TemperatureSensors.c
    • -137
    • +342
    ./App/Modes/ModeChemicalDisinfect.c
    • -114
    • +26
    ./App/Modes/ModeHeatDisinfect.c
    • -0
    • +56
    ./App/Services/SystemCommMessages.c
DG-DEN-8030_DG-HD DEV Mode Chemical Disinfect
DG-DEN-8030_DG-HD DEV Mode Chemical Disinfect
DEN-8103: Added mismatch check for alarm enum and alarm table

DEN-8103: Added filter flush time period override

    • -0
    • +32
    ./App/Services/SystemCommMessages.c
Good point. The module has been moved to fwcommon.

Good point. The module has been moved to fwcommon.

Removed the wrapper function. For now, only support one type of 32-bit CRC algorithm.

Removed the wrapper function. For now, only support one type of 32-bit CRC algorithm.

DEN-8103: Moved integrity module to fwcommon

    • -3
    • +3
    ./App/Controllers/TemperatureSensors.c
Done.

Done.

Noe said they updated the ID and this is the new ID for DG FPGA. The FPGA test will fail without this change.

Noe said they updated the ID and this is the new ID for DG FPGA.
The FPGA test will fail without this change.

Should mention somewhere that timer is counting ms.

Should mention somewhere that timer is counting ms.

Why did this change?

Why did this change?

Is there a reason why this module isn't in fwcommon? And if it can't be common for some reason, should this module (or group name) be named DGIntegrity?

Is there a reason why this module isn't in fwcommon? And if it can't be common for some reason, should this module (or group name) be named DGIntegrity?