App: Port application to rev 3

Open
#271 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
c
Domain
embedded-iot

Research direction

No files, tests, or entry points are named. Start by reviewing the rev 2 application layer, the rev 3 folder, and the planned hardware validation routines after HW/SW integration. Confirm the architecture with the listed points of contact; done means rev 3 supports a strict superset of rev 2 features except for explicitly unsupported drivers.

Written by the indexing model from the issue text.

Description

enhancement

**Requester: @ETSells **

Describe the solution you'd like
Rev 3 needs to port the app layer. There are a couple of ways we can do this:

  1. Branch off of mainline and do regular pull ups from rev 2.
  2. Copy everything from rev 2 into the rev 3 folder.
  3. Add a build flag for rev 3 to the rev 2 makefile and build them out of the same source tree.

I feel like option 3 has the least dual maintenance, so that's my personal preference but as this impacts other projects we will solicit the needs of their leads before committing to that.

Describe alternatives you've considered
See above lol

Additional context
Rev 3 should have a strict SUPERSET of rev 2 features except for certain drivers. In early development though, we might not have support for everything yet.

Scheduling will place this task out after initial HW/SW integration so that we can run the hardware validation routines for each driver.

Points of Contact
This should probably be some kind of combined effort between @NArmistead and @ETSells, at least for design purposes.

Dominant language
C
Stars
8
Forks
6
Avg merge
6d 15h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SunDevilRocketry/Flight-Computer-Firmware

All issues in SunDevilRocketry/Flight-Computer-Firmware

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.