hdfirmware / firmware / App

Services

Clone Tools

Stats

Commits this week: 0
Total Committers: 16
Last Commit: 10 Jun
Commits this week: 0

Lines of code count not available

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 

Most active committers (90 days)

loading
loading
  • last updated a few minutes ago
All Commits Reviews
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Monday 17 May 2021
9:48 am

Peman Montazemi <pmontazemi@diality.com>

DEN-7860: Addressed code review comments

Options
    • -7
    • +5
    ./FPGA.c
  2. … 1 more file in changeset.
9:47 am

pmontazemi  (deleted user)

Addressed.

Addressed.

9:43 am

pmontazemi  (deleted user)

Removed ADA/ADV bubble state test masks as there are no separate FPGA registers that output these variables.

Removed ADA/ADV bubble state test masks as there are no separate FPGA registers that output these variables.

9:40 am

pmontazemi  (deleted user)

Removed ADA/ADV bubble state test masks.

Removed ADA/ADV bubble state test masks.

Friday 14 May 2021
1:35 pm

Quang Nguyen <qnguyen@diality.com>

DEN-8103: Added firmware image integrity check for POST

Options
    • -0
    • +1
    ./AlarmMgmt.h
    • -0
    • +95
    ./Integrity.c
    • -0
    • +40
    ./Integrity.h
  4. … 2 more files in changeset.
10:39 am

qnguyen  (deleted user)

This seems to be conflict with FPGA_BLOOD_LEAK_ZERO_STATE_MASK if we are reading from the same FPGA gpio.

This seems to be conflict with FPGA_BLOOD_LEAK_ZERO_STATE_MASK if we are reading from the same FPGA gpio.

Thursday 13 May 2021
1:21 pm

Dara Navaei

Are we adding an alarm here later?

Are we adding an alarm here later?

1:02 pm

Dara Navaei

It looks like you have not added these functions to SystemComm.c. They need to be added there otherwise the commands will not be handled.

It looks like you have not added these functions to SystemComm.c. They need to be added there otherwise the commands will not be handled.

10:42 am

Dara Navaei

Merge branch 'DEN-8030-dg-hd_dev-dg-mode-chemical-disinfect' into develop

Options
    • -3
    • +3
    ./SystemCommMessages.c
10:37 am

Dara Navaei

DEN-8030 fixed fluid leak detector in systemcommmessages.c

Options
    • -3
    • +3
    ./SystemCommMessages.c
Wednesday 12 May 2021
3:31 pm

Peman Montazemi <pmontazemi@diality.com>

DEN-7860: Addressed part of code review comments

Options
    • -0
    • +1
    ./AlarmMgmt.h
    • -2
    • +2
    ./FPGA.c
  3. … 2 more files in changeset.
Tuesday 11 May 2021
3:39 pm

Sean Nash

I think this makes sense. We've done the same in other monitors/controllers like valves where there are several similar components handled in same driver.

I think this makes sense. We've done the same in other monitors/controllers like valves where there are several similar components handled in same driver.

3:36 pm

Sean Nash

Maybe cast the status params as U32 as well so there won't be an issue within the broadcast function (see my comment there for context).

Maybe cast the status params as U32 as well so there won't be an issue within the broadcast function (see my comment there for context).

3:34 pm

Sean Nash

For blood leak sensor, we didn't want to go to normal state until it was zeroed and self-tested. For bubble detector, do we want to be stuck in init state until self-test is requested? I think if w...

For blood leak sensor, we didn't want to go to normal state until it was zeroed and self-tested. For bubble detector, do we want to be stuck in init state until self-test is requested?
I think if we keep this state machine as is, we will want to request self-test in POST so that we can move on to normal state quickly. Then still request another self-test in each pre-treatment as we are now doing.

3:30 pm

qnguyen  (deleted user)

Should we broadcast both bubble detectors' data in one message?

Should we broadcast both bubble detectors' data in one message?

3:30 pm

Sean Nash

Same. Validate bubble param at top of function before using it. Then no need for else below.

Same. Validate bubble param at top of function before using it. Then no need for else below.

3:28 pm

Sean Nash

Should validate bubble param up top before you use it. S/W fault if invalid. Then don't need the else below.

Should validate bubble param up top before you use it. S/W fault if invalid. Then don't need the else below.

3:24 pm

Sean Nash

Initialize the other 3 fields of the override structure.

Initialize the other 3 fields of the override structure.

3:21 pm

Sean Nash

I agree we want to send the two status enums as a U32 over the CAN. I think it's better to assign w/ cast the two status to local U32s before memcpy into payload. That way, memcpy is given 4 bytes ...

I agree we want to send the two status enums as a U32 over the CAN. I think it's better to assign w/ cast the two status to local U32s before memcpy into payload. That way, memcpy is given 4 bytes to copy. As is, I worry compiler will only have 1 or 2 bytes for the enum passed into the function and we're forcing memcpy to copy 4 bytes - could corrupt the upper bytes of the two status fields in the message payload.

3:12 pm

Sean Nash

Code below looks like this message is expected to have a payload of type OVERRIDE_PUMP_SET_PT_PAYLOAD_T. Not sure why a bubble test request would have a pump type payload, maybe it had what you nee...

Code below looks like this message is expected to have a payload of type OVERRIDE_PUMP_SET_PT_PAYLOAD_T. Not sure why a bubble test request would have a pump type payload, maybe it had what you needed (an index). But this structure will have a length larger than 0. Should be "if ( sizeof( OVERRIDE_PUMP_SET_PT_PAYLOAD_T ) == message->hdr.payloadLen ).

3:06 pm

Sean Nash

I think it's worth checking that the self-test mode was entered as expected.

I think it's worth checking that the self-test mode was entered as expected.

3:03 pm

Sean Nash

Same comment as above.

Same comment as above.

3:03 pm

Sean Nash

No return value for this function.

No return value for this function.

3:03 pm

Sean Nash

Looks like fpgaActuatorSetPoints is an output and no inputs.

Looks like fpgaActuatorSetPoints is an output and no inputs.

3:02 pm

Sean Nash

This should be a s/w fault.

This should be a s/w fault.

2:54 pm

Sean Nash

Agreed. This is for me to add a check for this error. Will remove comment when I'm done.

Agreed. This is for me to add a check for this error. Will remove comment when I'm done.

2:54 pm

Sean Nash

Is this still an issue?

Is this still an issue?

2:53 pm

Sean Nash

Agreed. This is for me to add a check for this error. I'll remove comment when I'm done.

Agreed. This is for me to add a check for this error. I'll remove comment when I'm done.

2:53 pm

Sean Nash

Is this still an issue?

Is this still an issue?

2:01 pm

Sean Nash

Fixed merge conflicts.

Options
    • -9
    • +9
    ./FPGA.c
  2. … 3 more files in changeset.