[capture] Re-add range / saturation checks for Husky
Open
Nobody has claimed this yet.
enhancement
Priority:P2
- Dominant language
- Jupyter Notebook
- Stars
- 43
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
When doing FPGA measurements, I noticed that - at least for AES - we no longer have range / saturation checks for Husky. If the user chooses a gain value which is to high, the ADC will just saturate which invalidates measurements. It's pretty difficult to detect such issues without these automated checks. I am strongly in favor for re-adding them again.
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
No files, tests, or entry points are named. Start by locating the Husky FPGA capture path and the AES measurement flow, then identify how gain and ADC saturation are handled. Done means range and saturation checks are restored for high-gain measurements and covered by automated checks.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100