fwcommon

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-13834 added a function to check the HD usage info's CRC

DEN-13834 updated the HD NV events

DEN-13834 added DG NV data events

DEN-13834 added a function to set the service time

DEN-13834 transferred the disable check for service and disinfect software configuration from DG to HD

DEN-13598 updated and cleaned up the code

DEN-13598 updated the integrity file

Merge branch 'DEN-13834-dg_hd_dev-hd_dg_dvt-update-part-3' into develop

DEN-13834 updated the DG usage info CRC check

Merged DEN-13834

Merge branch 'DEN-13834-dg_hd_dev-hd_dg_dvt-update-part-3' into develop

DEN-13598 Updated code for RAM error checking.

DEN-13834 updated the DG service record.

DEN-13834 updated the service record to add the last time that a record was reset. Added a new software configuration to disable the serive time and disinfects in DG. Changed the DG RTC broadcast message.

DEN-13834 moved some of the broadcast data into the common file in the fwcommon to be shared with HD.

Merge branch 'DEN-13460-dg_hd_dev-hd_dg_dvt-update-part-2' into develop

Line 1902 is the same check but reverses the order.

Line 1902 is the same check but reverses the order.

DEN-13460 addressed the code review comments and changed the way the FPGA persistent alarms are initialized so the isConditionClear is set to TRUE and the persistent is not alarmed with the first cout out of range

This code is un-commented.

This code is un-commented.

Done.

Done.

In in DEN-13834.

In in DEN-13834.

Done.

Done.

Added TODO to un-comment this line of code.

Added TODO to un-comment this line of code.

"FAPI_CHECK_FSM_READY_BUSY" is a macro.

"FAPI_CHECK_FSM_READY_BUSY" is a macro.

Done.

Done.

DEN-13460 updated the software fault alarms of the FPGA persistent alarms

DEN-13460 updated the FPGA persistent alarms functions and fixed the system information CRC correction

Done.

Done.

What is the value of SEMAPHORE_IN_USE_TIMEOUT_MS? The timeout appears to only be check when getSemaphore is called. Seems like you could acquire the semaphore and the process that acquired the sema...

What is the value of SEMAPHORE_IN_USE_TIMEOUT_MS? The timeout appears to only be check when getSemaphore is called. Seems like you could acquire the semaphore and the process that acquired the semaphore could hold onto it for a time much longer than SEMAPHORE_IN_USE_TIMEOUT.