leahi-common

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Please break it into two lines

Please break it into two lines

Please break it into two lines

Please break it into two lines

Please break it into two lines Should the name of the message id be MSG_ID_TD_TREATMENT_UF_VOLUME_VALIDATE_RESPONSE?

Please break it into two lines
Should the name of the message id be MSG_ID_TD_TREATMENT_UF_VOLUME_VALIDATE_RESPONSE?

Please break it into two lines

Please break it into two lines

Please break it into two lines

Please break it into two lines

Please break it into two lines

Please break it into two lines

Please break it into two lines

Please break it into two lines

TREAT_PARAMS_PROPERTIES should also be an input?

TREAT_PARAMS_PROPERTIES should also be an input?

please add @param

please add @param

Shouldn't this file contain the incoming request and associate it to the corresponding function? And that function will trigger the response sending part. Declaring the response here instead seems...

Shouldn't this file contain the incoming request and associate it to the corresponding function?
And that function will trigger the response sending part.

Declaring the response here instead seems out of regular design scheme.

please align the comment

please align the comment

Updated

Updated

Removed

Removed

Fixed

Fixed

Removed

Removed

Added alarm

Added alarm

Added back

Added back

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?

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.

Why do you have {} in the cases?

Why do you have {} in the cases?