fwcommon

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'DEN-7605-hd_dg_dev-self-tests' of ssh://dvm-linux02:7999/comm/fwcommon into DEN-7605-hd_dg_dev-self-tests

DEN-7605: Addressed code review issue.

Merge branch 'DEN-7605-hd_dg_dev-self-tests' of ssh://dvm-linux02:7999/comm/fwcommon into DEN-7605-hd_dg_dev-self-tests

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

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

DEN-7605: Fixed function headers in RTC.c.

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

DEN-7605: Fixed epoch bug.

Fixed merge conflicts.

DEN-7605: Fixes to new epoch conversion functions per lab testing.

Fixed new RTC epoch functions - will fix in DEN-7605 too.

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

DEN-7605: Updates to epoch conversion functions.

DEN-7605: Added non-lib epoch converter functions to RTC.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Per Dara Navaei, we will need to implement this functions.

Per Dara Navaei, we will need to implement this functions.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Good point. Test will need to be longer than 50ms anyway - FPGA ramps the sound and there is a ~250ms time constant in the electronics. But I will want the sound to at least get started immediately.

Good point. Test will need to be longer than 50ms anyway - FPGA ramps the sound and there is a ~250ms time constant in the electronics. But I will want the sound to at least get started immediately.

Change order of comparison.

Change order of comparison.

Blank line after declaration.

Blank line after declaration.

DEN-8103: Added safety shutdown to integrity check

I think we should add the new THd temperature sensor now. I know it's currently using TRo connection (and so we don't have a TRo), but we should handle that with build switch (THd reads from TRo ch...

I think we should add the new THd temperature sensor now. I know it's currently using TRo connection (and so we don't have a TRo), but we should handle that with build switch (THd reads from TRo channel and TRo can just be a copy of TDi for now if THD_USING_TRO_CONNECTOR build switch enabled, actual future code where both sensors exist on their own connectors if build switch is disabled).

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.