HI, I was learning a couple demos and courses from the chipwhisperer toolkit, but after running the update firmware python codes, the device gives a connection error. I get the following error:
OSError: Unable to communicate with found ChipWhisperer. Check that
another process isn’t connected to it and that you have permission to communicate with it.
How can I resolve this?
Try unplugging + replugging
I did try that, I tried most of the solutions I found. Replugging, Shutdown kernels and restart. Restarting my PC , and even the basic chipwhisperer setup. Everything gave me the same error.
What operating system are you using?
windows 10 - home basic
64 bit operating system
Typically, this error comes up on Windows when you’re trying to connect, but something else is already connected to the USB device. Is there any other program on your computer that might be connecting to the USB device?
No there isn’t. The device used to usually connect cause I have already did a lot of existing attacks. It is after I did the chipwhisperer upgrade python codes, It says it can no longer connect to chipwhisperer. But the CW1200 shows that clk_gen and ADC_clk is locked. But yet I get the error when I run this line " scope = cw.scope()". And this is the error: “OSError: Unable to communicate with found ChipWhisperer. Check that
another process isn’t connected to it and that you have permission to communicate with it”. So I am not sure what to do. I tried to run on different windows system by reinstalling the chipwhisperer application, but it still gave the same error.
From what version did you upgrade? Much older versions used a different driver setup, so that might be your issue.
I am unsure about the version, the application was of 5.6.1 version. I don’t remember the hardware version.
Do you see your device in Device Manager under Universal Serial Bus devices?
Yes, The chipwhisperer is detected at the USB, I can see it in the Device manager
Can you post the full stack trace from the connection error?
Yeah, that’s very strange. Can you run the following before trying to connect, can you run cw.naeusb_logger.setLevel(logging.INFO), then post the resulting output? That should get the error that happened when we tried to access the device.
Sorry that was a typo; use cw.naeusb_logger.setLevel(cw.logging.INFO) instead.
