SystemCommMessages.h

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Do we really want to use a whole flash sector for a flag? I thought bootloader was going to talk to UI to determine whether an update was in progress?

Do we really want to use a whole flash sector for a flag? I thought bootloader was going to talk to UI to determine whether an update was in progress?

What is this for?

What is this for?

This is adding conversion to binary step post-build, correct? Are we losing the alarm check here?

This is adding conversion to binary step post-build, correct? Are we losing the alarm check here?

Don't make changes outside of user code sections.

Don't make changes outside of user code sections.

So app start address is offset by 64K. Assuming that is plenty of room for bootloader but we should check. Also, have we checked that the first 64K of Flash memory is discreet sector-wise? We do no...

So app start address is offset by 64K. Assuming that is plenty of room for bootloader but we should check.
Also, have we checked that the first 64K of Flash memory is discreet sector-wise? We do not want bootloader and app sharing a sector.

Why aren't each of these messages calling their own handler function? They appear to exist in SystemCommMessages.c so I believe that was the intent.

Why aren't each of these messages calling their own handler function? They appear to exist in SystemCommMessages.c so I believe that was the intent.

Should we use new reboot function in Update.c?

Should we use new reboot function in Update.c?

Spaces in (). Be explicit on BOOL conditions.

Spaces in (). Be explicit on BOOL conditions.

Spaces in ().

Spaces in ().

Why not call the reboot function in Update.c?

Why not call the reboot function in Update.c?

Spaces inside (). Be explicit with BOOL conditions.

Spaces inside (). Be explicit with BOOL conditions.

Spaces inside (). Use ternary to set to TRUE or FALSE explicitly.

Spaces inside (). Use ternary to set to TRUE or FALSE explicitly.

Where is this being called?

Where is this being called?

This message will not get sent immediately - it is only queued. Reset will occur before transmit.

This message will not get sent immediately - it is only queued. Reset will occur before transmit.

Where is this called?

Where is this called?

I don't see SystemComm calling this or reboot function. Why are they here?

I don't see SystemComm calling this or reboot function. Why are they here?

These changes look wrong. This is UI comm check.

These changes look wrong. This is UI comm check.

Need doxygen group stuff here.

Need doxygen group stuff here.

Need doxygen group stuff here.

Need doxygen group stuff here.

Why do we need this function? Why not just use the reset function below to start the bootloader?

Why do we need this function? Why not just use the reset function below to start the bootloader?

This doesn't look like a mode - it looks like a small collection of services - suggest moving to Services folder.

This doesn't look like a mode - it looks like a small collection of services - suggest moving to Services folder.

Are these changes necessary? What do they do exactly?

Are these changes necessary? What do they do exactly?

HD-DEN-16565_SW Updater HD DG App Side Intake From Sunrise
HD-DEN-16565_SW Updater HD DG App Side Intake From Sunrise
RESOLVED in CODE WALKTHROUGH

RESOLVED in CODE WALKTHROUGH

HD-DEN-14150_HD Dialysate Flow Estimation
HD-DEN-14150_HD Dialysate Flow Estimation
HD-DEN-11750_DG Dev Dialysate Temperature Control Tune Up
HD-DEN-11750_DG Dev Dialysate Temperature Control Tune Up