bootloader / firmware

source

Clone Tools

Stats

Commits this week: 1
Total Committers: 1
Last Commit: 20 Mar
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 minutes ago
All Commits Reviews
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Friday 20 Mar
12:54 pm

Dara Navaei

LDT-3259 added a new CAN message ID for broadcast. Work in progess, updating the FPGA module with the new FPGA build

Options
    • -1
    • +20
    ./can.c
  2. … 7 more files in changeset.
Sunday 08 Mar
2:23 pm

Dara Navaei

LDT-3259 work in progress added a new broadcast channel from FFU

Options
    • -2
    • +2
    ./can.c
  2. … 8 more files in changeset.
2:22 pm

Dara Navaei

Friday 27 Feb
9:14 am

Sean Nash

else shouldn't we go back to waiting for an update or something? Seems wrong to just get stuck here.

else shouldn't we go back to waiting for an update or something? Seems wrong to just get stuck here.

9:12 am

Sean Nash

Is Noe never going to change these IDs? I think he has already changed DD fpga ID for beta 2.0. If these IDs are not fixed forever, we cannot hardcode them here in the bootloader code.

Is Noe never going to change these IDs? I think he has already changed DD fpga ID for beta 2.0. If these IDs are not fixed forever, we cannot hardcode them here in the bootloader code.

9:08 am

Sean Nash

We can't jump to app if fpga ID is bad? Why not?

We can't jump to app if fpga ID is bad? Why not?

9:03 am

Sean Nash

Where is this function defined?

Where is this function defined?

8:59 am

Sean Nash

Align comments

Align comments

8:57 am

Sean Nash

Why 2 conditions? Are there 2 ways to initiate an update? And why isn't this check done in the CHECK_FOR_UPDATE_STATE?

Why 2 conditions? Are there 2 ways to initiate an update?

And why isn't this check done in the CHECK_FOR_UPDATE_STATE?

Saturday 07 Feb
3:44 pm

Dara Navaei

LDT-3259 work in progress. Completed firmware remote update.

Options
    • -4
    • +23
    ./can.c
  2. … 7 more files in changeset.
Friday 06 Feb
9:48 am

Dara Navaei

LDT-3259 work in progress

Options
    • -49
    • +11
    ./can.c
  2. … 8 more files in changeset.
Wednesday 21 Jan
5:18 pm

Dara Navaei

LDT-3259 imported the code changes from LEAH-1415

Options
    • -0
    • +19
    ./can.c
    • -2
    • +0
    ./rti.c
    • -2
    • +2
    ./sci.c
    • -6
    • +6
    ./sys_core.asm
    • -2
    • +7
    ./sys_link.cmd
    • -6
    • +42
    ./sys_main.c
    • -2
    • +3
    ./sys_startup.c
    • -1
    • +1
    ./sys_vim.c
  9. … 46 more files in changeset.
5:17 pm

Dara Navaei

LEAHI-BOOTLOADER-LDT-3259_Software Update - TD
LEAHI-BOOTLOADER-LDT-3259_Software Update - TD
11:20 am

Dara Navaei

LEAH-1415 updated the bootloader code to be more comaptible with Leahi

Options
    • -2
    • +2
    ./sys_startup.c
  2. … 3 more files in changeset.
Tuesday 20 Jan
2:40 pm

Sean Nash

TODO

TODO

2:39 pm

Sean Nash

TODO

TODO

2:39 pm

Sean Nash

TODO should be all caps.

TODO should be all caps.

2:39 pm

Sean Nash

TODO should be all caps for consistency (so we know what to search for).

TODO should be all caps for consistency (so we know what to search for).

2:38 pm

Sean Nash

I think it should be restored even if it's not used anywhere yet.

I think it should be restored even if it's not used anywhere yet.

2:34 pm

Sean Nash

Do we need an end of group marker down here?

Do we need an end of group marker down here?

2:34 pm

Sean Nash

Can you capture intent to resolve my comment in a TODO so we don't lose track of it? (General recommendation for all comments that we are postponing resolution for).

Can you capture intent to resolve my comment in a TODO so we don't lose track of it? (General recommendation for all comments that we are postponing resolution for).

2:31 pm

Sean Nash

Can we put test code inside of #ifdef TEST_CODE_ENABLED or something so that it is easy to remove later?

Can we put test code inside of #ifdef TEST_CODE_ENABLED or something so that it is easy to remove later?

Saturday 17 Jan
4:39 pm

Dara Navaei

LEAH-1415 addressed the code review comments

Options
    • -0
    • +5
    ./sys_main.c
  2. … 11 more files in changeset.
4:30 pm

Dara Navaei

It will be implemented in the new branch.

It will be implemented in the new branch.

4:30 pm

Dara Navaei

Done

Done

4:08 pm

Dara Navaei

Done

Done

3:59 pm

Dara Navaei

Done

Done

3:59 pm

Dara Navaei

Done

Done

3:58 pm

Dara Navaei

Removed the variable.

Removed the variable.

3:55 pm

Dara Navaei

Removed the TODO.

Removed the TODO.