Add the header description.

Do we need to transition to next state DD_PREGEN_DRY_BICART_INITIAL_FILL here?

Remove empty lines.

Add comments across the file.

Add comment.

Add a test support for Pregen fill request.

Update header description for all newly added functions.

You may need to check other flags such as DryBicartFillRequested( Initial Fill), bicarbChamberFillRequested (Filling Chamber F), instead of 'bicarbChamberPregenFillRequested'. Keep Drain and DepressurizeRequest flag as is. This makes sure at any given point, dryBicartExec calls one of the service only.

Same here adding 'bicarbChamberPregenFillRequested' flag.

Same here adding 'bicarbChamberPregenFillRequested' flag.

Same here adding 'bicarbChamberPregenFillRequested' flag.

Retain the previous( dryBicartFillRequested) and add 'bicarbChamberPregenFillRequested' flag here.

PregenFillExecState? may be creating a new fault ID for pregen fill.

Update description as required.

Add comment.

Add comment.

Add comment.

Added but crucible is not showing this change. Please check bitbucket.

These variables are correctly initialized to the first enum in the list.

Not needed because the retry mechanism is going to be deleted in the next ticket.

I would rather keep it. Anyways, we need an else block after else if, as per MISRA guidelines.

I would rather keep it. Anyways, we need an else block after else if, as per MISRA guidelines.

Not needed because the retry mechanism is going to be deleted in the next ticket.

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).