Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Same question as above: should we alarm if the retries failed?

Same question as above: should we alarm if the retries failed?

This else is not needed because isFlashAddressValid is set to False at the top of the function (Optional to change).

This else is not needed because isFlashAddressValid is set to False at the top of the function (Optional to change).

This else is not needed because isFlashAddressValid is set to False at the top of the function (Optional to change).

This else is not needed because isFlashAddressValid is set to False at the top of the function (Optional to change).

If a retry goes wrong will you trigger an alarm?

If a retry goes wrong will you trigger an alarm?

Any fault alarm here?

Any fault alarm here?

Have these variables been initialized correctly?

Have these variables been initialized correctly?

Remove extra blank line.

Remove extra blank line.

We generally don't add { } to switch cases unless they require local variable declarations.

We generally don't add { } to switch cases unless they require local variable declarations.

If we're not including a timestamp, can we just remove this line of code?

If we're not including a timestamp, can we just remove this line of code?

Why commented out?

Why commented out?

LEAHI-DD-FIRMWARE-LDT-4611_HDF - FW Implementation - 5/4:
LEAHI-DD-FIRMWARE-LDT-4611_HDF - FW Implementation - 5/4:
LEAHI-DD-FIRMWARE-LDT-5157_System Data and Logs (DD) - Conductivity Sensor Calibration (1/3)
LEAHI-DD-FIRMWARE-LDT-5157_System Data and Logs (DD) - Conductivity Sensor Calibration (1/3)
Remove blank line.

Remove blank line.

If this is a override message handler, it is not in the table in Messaging.c and it does not have the proper parameter list (1 parameter for a message pointer).

If this is a override message handler, it is not in the table in Messaging.c and it does not have the proper parameter list (1 parameter for a message pointer).

Can we have a payload structure (packed to 1 byte alignment) with 1 field of type U08 for this message and then replace '1' with 'sizeof( new struct type )' ?

Can we have a payload structure (packed to 1 byte alignment) with 1 field of type U08 for this message and then replace '1' with 'sizeof( new struct type )' ?

Add blank line between declarations and rest of function code (throughout this unit)

Add blank line between declarations and rest of function code (throughout this unit)

Add blank line before return statement. ( throughout this unit )

Add blank line before return statement. ( throughout this unit )

Add blank line before return statement.

Add blank line before return statement.

Add blank line between declarations and rest of function code.

Add blank line between declarations and rest of function code.

Add blank line between declarations and rest of function code.

Add blank line between declarations and rest of function code.

Add blank line between declarations and rest of function code.

Add blank line between declarations and rest of function code.

Add blank line between declarations and rest of function code.

Add blank line between declarations and rest of function code.

Add blank line before return statement.

Add blank line before return statement.

Add blank line between declarations and rest of function code.

Add blank line between declarations and rest of function code.

Add blank line before return statement.

Add blank line before return statement.

Add blank line before return statement.

Add blank line before return statement.

Add blank line before return statement.

Add blank line before return statement.

Indent too deep here.

Indent too deep here.

Remove blank line.

Remove blank line.