dgfirmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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

    • -137
    • +342
    /firmware/App/Modes/ModeChemicalDisinfect.c
    • -114
    • +26
    /firmware/App/Modes/ModeHeatDisinfect.c
    • -2
    • +7
    /firmware/App/Modes/ModeHeatDisinfect.h
    • -14
    • +1
    /firmware/App/Services/Reservoirs.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

    • -0
    • +28
    /firmware/checkAlarms.sh
DEN-8103: Added filter flush time period override

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

    • -135
    • +0
    /firmware/App/Services/Integrity.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?

Do we need to support more than one 32-bit CRC algorithm in firmware? If not, do we need this wrapper function?

Do we need to support more than one 32-bit CRC algorithm in firmware? If not, do we need this wrapper function?

Done.

Done.

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

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

DEN-7605: Addressed code review feedback.

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

Merge branch 'develop' of ssh://dvm-linux02:7999/dg/dgfirmware into develop

DEN-7605: Addressed code review feedback.

Fixed.

Fixed.

Yes. Fixed.

Yes. Fixed.