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.

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

Regression from hidapi switchover: Multiple dev boards don't seem to work right #95

Closed
azonenberg opened this issue Jun 8, 2017 · 4 comments
Assignees

Comments

@azonenberg
Copy link
Owner

azonenberg@skipjack:/nfs4/home/azonenberg/code/openfpga/build$ ./bin/gp4prog --device 1 --blink
GreenPAK 4 programmer by Andrew D. Zonenberg and whitequark.

License: LGPL v2.1+
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Searching for developer board at index 1
ERROR: No device found, giving up

OLD VERSION (before hidapi switchover)
azonenberg@skipjack:/nfs4/home/azonenberg/code/openfpga/build$ /usr/local/bin/gp4prog --device 1 --blink
GreenPAK 4 programmer by Andrew D. Zonenberg and whitequark.

License: LGPL v2.1+
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Searching for developer board at index 1
Found: Silego GreenPAK Universal Dev. Board 1
Detecting part
Detected empty SLG46620V
No actions requested, exiting (use --help for help)

@ArcaneNibble ArcaneNibble self-assigned this Jun 8, 2017
@ArcaneNibble
Copy link
Collaborator

Can you please run before/after with --debug?

@ArcaneNibble
Copy link
Collaborator

Er, really strange question: while testing this, did you ever run the old libusb-based version? If so, then this version will not work until you unplug and replug the board. This is because the old code detached the Linux HID driver to get it out of the way, but it doesn't ever attach it back. Once that happens, this version can't access it anymore.

@azonenberg
Copy link
Owner Author

That would explain a lot. Confirmed, that's the problem.

Closing as invalid.

@ArcaneNibble
Copy link
Collaborator

Just for completeness, I tested interactions with the blob. The blob doesn't seem to have problems grabbing the device even if libusb detached the kernel driver, but it also does correctly reattach the kernel driver, so there are no new problems with that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants