I thought this was a TEST_CONFIG thing. We aren't doing s/w config status, so maybe we should convert it to a TEST_CONFIG.

Let's hard code for time being with a TODO comment. I don't want alarm to be a problem.

Use OVERRIDE_RESET for .override instead of 0.

align indentation, same for line 338 as well.

Yes.
Otherwise, we will have to hard code the calibration record for the time being.

The function getSoftwareConfigStatus() is also part of NVM module.
Moreover, we are planning to remove this function when NVM will be implemented.
So, we will have to perform a cleanup and remove all similar calls that have been currently commented out in other files as well like AirTrap.c, BloodFlow.c, etc.

slaveAddr should be an enum now and so just "device".

Add a banner before Dialin test support functions (see other units for example).

Initialize .override to OVERRIDE_RESET

Why is this commented out? Do we not need to initialize it?

Align comment.

Keep 2 blank lines above banner.

Should this line be un-commented?

So we are going to fail this test until calibration record is ready?

In Leahi, we want to do all initialization in the init function instead of here at declaration (see Bubble.c for example).

Rename similar to ADDR definitions below. these are not commands.

Combine charger and pack data into one payload with one broadcast message.

Move these 3 override messages (should end in OVERRIDE_REQUEST) to TD Dialin section below and assign an ID in the 0x8... range.

I think we only need one data message for both charger and battery pack data.

Remove.

uncomment.

Call the init for the battery driver here.

INVALID_BATTERY

Remove repeating entries.

remove extra blank line.

Remove this comment.

Remove blank line.

initialize all of these in init function.

Missing doxygen group