cFS header definition Version 2 CI
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.5k
- Forks
- 391
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 19
Description
Is your feature request related to a problem? Please describe.
Certification configuration is CCSDS extended header, 32bit. Default config is currently CCSDS primary only, 64 bit.
Describe the solution you'd like
CI with cFS header definition V2, and any other minor tweaks for cert config.
Describe alternatives you've considered
Leaning towards adding a V2 config that maps to the cert configuration to CI
Won't be the full CI until related issues get resolved.
Additional context
Will need to resolve any related V2 issues (cmdUtil doesn't support it, etc), issues in implicit packet padding differences, etc.
Requester Info
Jacob Hageman - NASA/GSFC
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the cFS header definition V2 and the related cmdUtil and implicit packet-padding issues mentioned in the report. Done means CI uses a V2 configuration mapped to the certification configuration and the related V2 compatibility issues are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100