td-firmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Bamboo Commit: Updated TDCommon.h with build versions from Bamboo.

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

Merge branch 'LDT-3215-measured-venous-pressure-decreases' into staging

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

resolved merge conflicts and merged LDT-1886

LDT-3970 Updated edit treatment parameters during treatment

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

Updated

Updated

LDT-4033-patient-vitals-fw-implementation

LDT-1886: Add StateServices in release include options

Removed

Removed

Fixed

Fixed

resolved merge conflicts and merged LDT-1886

    • -18
    • +240
    /firmware/App/Services/FpgaTD.c
Removed

Removed

Added alarm

Added alarm

Added back

Added back

Changes

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

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

Add alarm here.

Add alarm here.

Make h10DACControl a U08.

Make h10DACControl a U08.

Remove extra blank line.

Remove extra blank line.

This looks like leftover from merge conflict. Remove this line.

This looks like leftover from merge conflict. Remove this line.

What do we do if BP module reports an error? Do we just go to idle state and there is no alarm?

What do we do if BP module reports an error? Do we just go to idle state and there is no alarm?

Merge branch 'staging' of bitbucket.org:diality-cloud/td-firmware into LDT-3215-measured-venous-pressure-decreases

    • -18
    • +240
    /firmware/App/Services/FpgaTD.c
Merge fix

    • -25
    • +25
    /firmware/App/Controllers/BPModule.c
    • -12
    • +12
    /firmware/App/Drivers/BPDriver.c
    • -18
    • +226
    /firmware/App/Services/FpgaTD.c
Thats for error register so not required now

Thats for error register so not required now

You’re right. I should also check the busy status before transitioning to the GET_DATA state. I’ll update the measurement completion logic to first verify the busy bit is cleared, then validate the...

You’re right. I should also check the busy status before transitioning to the GET_DATA state. I’ll update the measurement completion logic to first verify the busy bit is cleared, then validate the BP data response code before moving to BP_DRIVER_GET_DATA_STATE.