Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[scope] CW-Husky USB blocked after power-up #301

Open
vrozic opened this issue Jan 25, 2024 · 2 comments
Open

[scope] CW-Husky USB blocked after power-up #301

vrozic opened this issue Jan 25, 2024 · 2 comments
Labels
enhancement New feature or request Priority:P2

Comments

@vrozic
Copy link
Contributor

vrozic commented Jan 25, 2024

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.
@vogelpi
Copy link
Collaborator

vogelpi commented Jan 25, 2024

Thanks for opening up this issue. Please don't dive any deeper into this. Having a workaround is perfectly sufficient at this point.

@vogelpi vogelpi added enhancement New feature or request Priority:P2 labels Jan 25, 2024
vrozic added a commit to vrozic/ot-sca that referenced this issue Jan 29, 2024
@vrozic
[capture] Unblock Husky USB communication after power-up
db735dd 
CW Husky often blocks USB communication after power-up.
Initializing the scope twice seems to solve the problem.
Resolves lowRISC#301

Signed-off-by: Vladimir Rozic <[email protected]>
vrozic added a commit to vrozic/ot-sca that referenced this issue Jan 29, 2024
@vrozic
[capture] Unblock Husky USB communication after power-up
722811f 
CW Husky often blocks USB communication after power-up.
Initializing the scope twice seems to solve the problem.

Resolves lowRISC#301

Signed-off-by: Vladimir Rozic <[email protected]>
@vrozic
Copy link
Contributor Author

vrozic commented Feb 6, 2024 •
edited
Loading

In case that we encounter the problem again #245 description contains instructions on how to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request Priority:P2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vogelpi @vrozic