Consider making the CRC size configurable
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 36
- Forks
- 41
- Avg merge
- 11d 19h
- Merged PRs (30d)
- 2
Description
There are two CRC algorithm types specified in the platform config. Are both of these using 32-bit CRC? What if we add another CRC algo later that isn't 32-bit? It might make sense to define the type that holds a CRC result in platform config as well.
Comment is on the CS_ComputeEepromMemory function regarding the uint32 ComputedCSValue parameter.
Imported from GSFCCFS-1326
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 at CS_ComputeEepromMemory and inspect the uint32 ComputedCSValue parameter alongside the platform configuration and the two CRC algorithm types mentioned in the issue. Determine how CRC result sizes are represented and what configuration change would support future algorithms; done means the scope and expected behavior are defined for the existing algorithms and future sizes.
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
- Needs clarification
- Newbie friendliness
- 35/100