td-firmware

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Yes Noe said to replace with new register

Yes Noe said to replace with new register

Updated

Updated

Sure

Sure

please add bpLeftHomeTimerCounter to inputs and outputs.

please add bpLeftHomeTimerCounter to inputs and outputs.

please add bpLeftHomeTimerCounter to inputs and outputs.

please add bpLeftHomeTimerCounter to inputs and outputs.

Why was this function header changed? I think it was correct before.

Why was this function header changed? I think it was correct before.

If these messages are for change to UF volume during treatment, the message ID should have the word TREATMENT in it to distinguish from the original UF volume message that comes in pre-treatment.

If these messages are for change to UF volume during treatment, the message ID should have the word TREATMENT in it to distinguish from the original UF volume message that comes in pre-treatment.

If we don't set this pwm time anymore, we don't need this. Please make sure we really don't need this anymore though.

If we don't set this pwm time anymore, we don't need this. Please make sure we really don't need this anymore though.

I don't think these definitions need to be public. Some of these should probably be inside the FpgaTD.c and some should probably be inside your driver's .c file.

I don't think these definitions need to be public. Some of these should probably be inside the FpgaTD.c and some should probably be inside your driver's .c file.

create a local BOOL result and use a ternary to assign FALSE or TRUE explicitly.

create a local BOOL result and use a ternary to assign FALSE or TRUE explicitly.

Did Noe delete the H12 period register? According to this structure, syrPumpDACControl is 2 bytes (U16), so next register should be 42 (40+2). So why do you have 41? Something is out of sync with H...

Did Noe delete the H12 period register?
According to this structure, syrPumpDACControl is 2 bytes (U16), so next register should be 42 (40+2). So why do you have 41? Something is out of sync with HDD here. Please align with the HDD.

What is in registers 378..383? We need to add those registers or incoming data won't overlay properly into structure.

What is in registers 378..383? We need to add those registers or incoming data won't overlay properly into structure.

Call the init for the battery driver here.

Call the init for the battery driver here.

INVALID_BATTERY

INVALID_BATTERY

Remove repeating entries.

Remove repeating entries.

remove extra blank line.

remove extra blank line.

Remove this comment.

Remove this comment.

Remove blank line.

Remove blank line.

initialize all of these in init function.

initialize all of these in init function.

Missing doxygen group

Missing doxygen group

These should be in alphabetical order.

These should be in alphabetical order.

Update all function headers to Leahi format (e.g. input and output have a \b to make them bold).

Update all function headers to Leahi format (e.g. input and output have a \b to make them bold).

Add blank line after banner

Add blank line after banner

Add blank line after banner

Add blank line after banner

Add a blank line after banner. Initialize in init function instead of here.

Add a blank line after banner.

Initialize in init function instead of here.

Move all but I2CBatteryStatus override functions to the battery monitor.

Move all but I2CBatteryStatus override functions to the battery monitor.

Move definitions to top (above functions).

Move definitions to top (above functions).

BatteryDriver

BatteryDriver

Use Leahi function format and helper functions for overrides.

Use Leahi function format and helper functions for overrides.