where are we calling an alarm?
i think we are only sending event change data in completeBolusToCumulative() right?

do we need this block?

update the comment as required: ml or L?

rejReason = INVALID REQUEST FORMAT

I think these remaining 4 else ifs need to have another && condition that your service is in idle state so that we don't change back into one of these 4 states while a bolus is in progress.

Can we restore the real code here yet? Ask Dara.

Done

Done

This file was updated automatically using HALCoGen.

Done

Done

Non-Dialin messages should be higher in this list than Dialin messages. Move this above all of the "test" handlers.

If the check RAM ECC is disabled in the HALCoGen, this code will not be created.

If the check RAM ECC is disabled in the HALCoGen, this code will not be created.

If you disable mpu in the HALCoGen, this code will not be created.

This is auto generated code. How do we keep this code from re-appearing when somebody regenerates this code?

same.

same.

We shouldn't delete Halcogen code.
Add a #if 0 in this user code section and add a #endif in the user code section following _coreEnableFlashEcc() call.

Should this be commented out before merge?

These are not in alphabetical order. See ModeStandby and ModeService and ModeFault.

These should come before PC channels (higher priority).

Done

Done

Done