Possibly except that one thing doesn’t add up: originally you had one CW-Pro working normally and one with the problem, and they both had FW version 1.62.
What is the FW version on this third(?) CW-Pro? And from which version of chipwhisperer (cw.__version__
) did you run its FW upgrade?
That is correct, right now the CWPRO that works normally has the 1.62 Version, but I never updated it myself, it was provided by my department.
Now, the third one is the replacement I got for the CWPRO that had the problem.
The third one is also a CW-Pro.
Initially it had the firmware 1.30 , and after I ran the update firmware python code in jupyter, it was updated to 1.62 version, expect now it also causes the “Timeout in OpenADC” issue and does not capture the traces.
For the unit that you last upgaded to 1.62, what is the version of chipwhisperer software on the computer that you used to do the upgrade? Run this to find out:
import chipwhisperer as cw
print(cw.__version__)
So the software version, I have been using is:- 5.7.0
Hi, Sorry to trouble you again.
But I was wondering if there is any update on this??
I’ve specifically checked with those versions just be to sure; I can’t reproduce your issue.
As noted previously, I suspect that the issue is with streaming. As I had explained, streaming is done on a “best-effort” basis and can fail due to issues outside our control, such as activity from other devices on the USB bus, or other factors on side of the host PC (such as the USB port, cable, hub, etc). If any of these are limiting the rate at which we can read data from the CW-Pro, then captures will fail exactly as you described.
With the sca204 notebooks specifically, if you set PLATFORM
to “CWLITE”, then streaming won’t be used, and everything should work normally. Let us know if that is not the case.
If you still think there is something wrong with your CW-Pros, contact sales@newae.com and we will arrange to have a look at them. But before doing that I encourage you to properly verify that your problem is not caused by any of the potential causes I mentioned, by following these steps:
- use a modern PC with a USB port that’s USB 2.0 or better
- use a known good USB cable to connect the CW-Pro directly to the PC
- ensure there are no other USB devices connected to that PC (other than the CW305)