[scope] CW-Husky USB blocked after power-up
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 43
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
It often happens that CW-Husky USB communication gets block when running the first capture after power-up.
This has already caused CI to break several times.
PR #300 provides a temporary solution.
If the scope is initialised twice, the USB problem doesn't happen. I am not sure why this helps. I will have to look through CW API to root cause this problem and find a more reasonable fix.
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 with PR #300 and the CW API documentation or entry points involved in initializing CW-Husky. Reproduce the first capture after power-up and compare it with the double-initialization workaround; done means USB communication remains usable without that workaround and CI no longer breaks.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100