dd-firmware / firmware / App / Controllers

ROPump.c

Clone Tools

Stats

Commits this week: 1
Total Committers: 5
Last Commit: 05 Jun
Commits this week: 1

Lines of code count not available

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 

Most active committers (90 days)

loading
loading
  • last updated a few seconds ago
All Commits Reviews
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Wednesday 06 May
8:48 am

Dara Navaei

LEAHI-DD-FIRMWARE-LDT-4246_FW Support for UI Demo
LEAHI-DD-FIRMWARE-LDT-4246_FW Support for UI Demo
Sunday 26 Apr
2:43 pm

Sean Nash

So this unit manages the sending of record messages, right? I don't see a unit managing read/write/erase jobs. Where is that queue?

So this unit manages the sending of record messages, right? I don't see a unit managing read/write/erase jobs. Where is that queue?

2:41 pm

Sean Nash

I think this enum should be in a different header file. I don't think this unit uses this enum.

I think this enum should be in a different header file. I don't think this unit uses this enum.

2:39 pm

Sean Nash

Slot size and offsets can probably be private and maybe better placed in a different header file? I don't see why a msg Q would need/use/be responsible for this kind of thing.

Slot size and offsets can probably be private and maybe better placed in a different header file? I don't see why a msg Q would need/use/be responsible for this kind of thing.

2:32 pm

Sean Nash

These addresses should be calculated in init function from sector start addresses (call driver get function to get these) and your offsets and stored in static variables within the .c file.

These addresses should be calculated in init function from sector start addresses (call driver get function to get these) and your offsets and stored in static variables within the .c file.

2:29 pm

Sean Nash

Do these need to be public? I think only the driver should have to know sector addresses and sizes. If other units want to know these things, they should call a function in this driver to get them.

Do these need to be public?
I think only the driver should have to know sector addresses and sizes.
If other units want to know these things, they should call a function in this driver to get them.

2:25 pm

Sean Nash

I think isSectorStartAddress is a better function name.

I think isSectorStartAddress is a better function name.

2:24 pm

Sean Nash

Be careful with bufferSize. Make sure you understand what it means (e.g. is it bytes or words). I believe the FAPI functions deal in 4-byte words and it caused some issues for Dara because he thoug...

Be careful with bufferSize. Make sure you understand what it means (e.g. is it bytes or words). I believe the FAPI functions deal in 4-byte words and it caused some issues for Dara because he thought this was bytes.

2:21 pm

Sean Nash

don't forget to add function headers.

don't forget to add function headers.

2:21 pm

Sean Nash

// **************** private functions **************

// **************** private functions **************

2:18 pm

Sean Nash

I think this driver should be moved to FWCommon folder as it should work the same for both DD and TD firmware.

I think this driver should be moved to FWCommon folder as it should work the same for both DD and TD firmware.

2:17 pm

Sean Nash

Add a blank line before group end marker.

Add a blank line before group end marker.

2:16 pm

Sean Nash

No load cells in Leahi.

No load cells in Leahi.

2:14 pm

Sean Nash

I think this enum belongs to NVRecords (these are records, not jobs).

I think this enum belongs to NVRecords (these are records, not jobs).

2:13 pm

Sean Nash

I think this enum belongs to the Q (these are Q jobs), not in driver.

I think this enum belongs to the Q (these are Q jobs), not in driver.

1:43 pm

Sean Nash

What about TD record CRC errors?

What about TD record CRC errors?

1:40 pm

Sean Nash

Are we only doing DD messages? And since these could be coming from UI now, these shouldn't be considered "Dialin" messages anymore and should be moved up to section before 0x8000 IDs where normal ...

Are we only doing DD messages?
And since these could be coming from UI now, these shouldn't be considered "Dialin" messages anymore and should be moved up to section before 0x8000 IDs where normal system messages are defined.

Thursday 16 Apr
8:15 am

Michael Garthwaite

Wednesday 15 Apr
5:31 pm

Sean Nash and Vinayakam Mani

4:12 pm

Michael Garthwaite

by the end of S27 we will know if we need to keep this module. If so, then we can integrate it into PIControllers.c

by the end of S27 we will know if we need to keep this module. If so, then we can integrate it into PIControllers.c

3:37 pm

Vinayakam Mani

If this is the core change, can we introduce this logic in PI controller.c itself with a simple flag check (say, if 'IsDerivativeEnabled" set to true, add the derivative signal to Control signal. e...

If this is the core change, can we introduce this logic in PI controller.c itself with a simple flag check (say, if 'IsDerivativeEnabled" set to true, add the derivative signal to Control signal. else, just a PI control signal would work. (something similar to Feed forward enabled flag)

9:52 am

Michael Garthwaite

nope. removed.

nope. removed.

9:52 am

Michael Garthwaite

fixed

fixed

9:52 am

Michael Garthwaite

fixed

fixed

9:52 am

Michael Garthwaite

fixed

fixed

9:52 am

Michael Garthwaite

fixed

fixed

Tuesday 14 Apr
2:08 pm

Sean Nash

Add blank line before return.

Add blank line before return.

2:07 pm

Sean Nash

Add blank line after declarations.

Add blank line after declarations.

2:05 pm

Sean Nash

Why U32? Why not RECOVER_STATE_T?

Why U32? Why not RECOVER_STATE_T?

2:04 pm

Sean Nash

Lower case x

Lower case x