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

'device' passed as string not USB device object #276

Open
s1e3p3r opened this issue Jul 7, 2023 · 0 comments
Open

'device' passed as string not USB device object #276

s1e3p3r opened this issue Jul 7, 2023 · 0 comments

Comments

@s1e3p3r
Copy link

s1e3p3r commented Jul 7, 2023

If 'device' and 'hardware' are both specified on the command line, eg: device="1:7" hardware="cc2531", 'killerbee/init,py' will pass the 'device' variable to the hardware class constructor: 'killerbee/dev_cc253x.py' class 'CC253Zx.init()' as a string, not as a usb device object as expected. This will raise an exception when device.set_configuration() is called. This appears to be an issue for all non-serial usb devices.

If neither 'device' or 'hardware' are specified it 'killerbee/init.py' will autodetect the usb device and passes the device object to the hardware class constructor correctly.

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

1 participant