File | Date | Author | Commit |
---|---|---|---|
app | 2017-11-06 |
![]() |
[f463f8] fix system tray |
images | 2017-11-06 |
![]() |
[92324a] version 1.0 updates |
.gitignore | 2017-10-26 |
![]() |
[ad0fe7] Initial commit |
LICENSE | 2017-10-26 |
![]() |
[ad0fe7] Initial commit |
README.md | 2018-02-05 |
![]() |
[f78d7a] fix commands |
requirements.txt | 2017-10-26 |
![]() |
[b5271b] Adding source code |
run.py | 2017-10-29 |
![]() |
[7c8dc3] add license |
run_me_on_linux.sh | 2017-11-06 |
![]() |
[92324a] version 1.0 updates |
todo.md | 2017-11-06 |
![]() |
[92324a] version 1.0 updates |
git clone https://github.com/mrf345/usb-resetter.git
cd usb-resetter
pip2.7 install -r requirements.txt
python2.7 run.py
- You can get an executable that's suitable to your OS from :
https://sourceforge.net/projects/usb-resetter/
This tool is based on PyUsb, an open source python library that requires some extra USB drivers to allow us to interact with USB devices. One of those drives is libusb, there's an old but still working perfectly window version of it on :
https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
Since MacOS is actually a unix-like OS, the bundled libusb driver seems to work perfectly. Only issue that might accrue here, is not knowing exactly which device you want to reset, due to the short descriptors and unintended vague categories. So you can make use of the command
system_profiler SPUSBDataType
in terminal to get the idvendor, idproduct. Which are used to identify the devices in usb-resetter.
Has no issue in running the bundled libusb drive, and using
lsusb
command to get the exact idvendor and idproduct, in case you confused the device. Another thing, some might consider it an issue, is the need forsudo
since interacting with USB devices requires a higher permissions.
You can find a command-line version here: https://github.com/mrf345/usb-resetter-cli