Unable to functionally test app CRC miscompare
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 36
- Forks
- 41
- Avg merge
- 11d 19h
- Merged PRs (30d)
- 2
Description
Description:
If the Application's code segment CRC is not equal to the corresponding Application's baseline code segment CRC, CS shall increment the Application Code Segment CRC Miscompare Counter and send an event message.
Was not able to generate a miscompare when reloading a different version of the reqval_app. Loaded reqval_v500 which should have incremented the following error counter: AppCSErrCounter and also generated an event
20220324 - Likely resolution will be to verify via "analysis", aka unit test if reloading an app can not cause the miscompare. Future work might support getting the module address, use MM to "corrupt" the memory to cause the miscompare.
Imported from GSFCCFS-1906
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
Begin with the analysis or unit-test path for application reloads and the reqval_app/reqval_v500 setup mentioned in the issue. Determine whether reloading can produce the CRC miscompare; done means the behavior is verified or a reproducible test path demonstrates increment of AppCSErrCounter and emission of the event.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100