Scope = cw.scope() command is not running with CW305

naufusa · April 5, 2021, 10:55pm

Hello,
I just received my ChipWhisperer-Lite and the target board: CW305. I am using Windows 10 and I installed ChipWhisperer 5.5 directly (no VM). The USB driver of CW305 was automatically installed. However, I have installed the USB driver for ChipWhisperer-Lite (through device manager). For FPGA is XC7A100T: the M0M1M2 switch is “111”, the led light situation is following: on cw305, the led8(green) is on, the led1(red) is flashing, and the led FPGA_DONE-ON=Unprog(red) is on;
For CW-lite: blue (continuous blinking blue light) and others are off.

I am having great difficulty trying to program the CW305 target board. The scope = cw.scope() command is not working. Did I miss some installation/operation steps so it doesn’t work?

I believe this based upon running the following commands:

import chipwhisperer as cw
scope = cw.scope()

giving the error: chipwhisperer5_64\git\home\portable\chipwhisperer\software\chipwhisperer\hardware\naeusb\naeusb.py", line 354, in open raise OSError(“Failed to find USB device with S/N %s\n. Found S/N’s:\n” + snlist)
OSError: Failed to find USB device with S/N %s
. Found S/N’s:
50203120355448513030353238313033 (ChipWhisperer CW305)

giving the following full response:

import chipwhisperer as cw
scope = cw.scope()
Traceback (most recent call last):
File “c:\users\nalla\chipwhisperer5_64\git\home\portable\chipwhisperer\software\chipwhisperer\hardware\naeusb\naeusb.py”, line 316, in txrx
response = self.open(serial_number=payload)
File “c:\users\nalla\chipwhisperer5_64\git\home\portable\chipwhisperer\software\chipwhisperer\hardware\naeusb\naeusb.py”, line 354, in open
** raise OSError(“Failed to find USB device with S/N %s\n. Found S/N’s:\n” + snlist)**
OSError: Failed to find USB device with S/N %s
. Found S/N’s:
50203120355448513030353238313033 (ChipWhisperer CW305)

Alex_Dewar · April 5, 2021, 10:22pm

Hi,

Usually if we can’t find the ChipWhisperer, it means the device drivers aren’t installed. What does the Lite show up as in device manager? It should show up as a libusb-32 device, or as a Universal Serial Bus device if drivers are installed.

If you’re able to update the drivers for your Lite to the newest ones (0.30), it should automatically install the correct drivers. On our Updating Firmware page, we’ve got a section on updating your firmware if you’re not able to connect on Windows: https://chipwhisperer.readthedocs.io/en/latest/firmware.html#special-case-driverless-windows

Alex

naufusa · April 5, 2021, 10:53pm

Hi Alex,
It shows as

a libusb-32 devices for ChipWhisperer Lite
Universal Serial Bus device for ChipWhisperer CW305

Ses the attachment Device Drivers

Alex_Dewar · April 5, 2021, 10:56pm

Try unplugging your CW305 when trying to connect to your ChipWhisperer.

Alex

naufusa · April 5, 2021, 11:26pm

Yes, now I unplugged my CW305. ChipWhisperer Lite only plugged. Now it is giving the warning when running the same comments: Your firmware is outdated, (and green led also blinking now)

import chipwhisperer as cw
scope = cw.scope()
WARNING:root:Your firmware is outdated - latest is 0.30. Suggested to update firmware, as you may experience errors
See https://chipwhisperer.readthedocs.io/en/latest/api.html#firmware-update

Do I need to update the firmware now? if yes, please give steps if possible.

Alex_Dewar · April 6, 2021, 3:02am

Hi,

The upgrade steps are linked in that warning message/my earlier post (two different pages, but they both cover the autoprogram step).

Alex

naufusa · April 11, 2021, 3:49am

Hi,
I have uninstalled and then installed, updated the drivers from the corresponding directory (cwlite_usb_driver)…but, now I could not connect to the scope also.

When I am running the command scope = cw.scope(), then it’s giving the following error:
Warning: Could not connect to “NewAE USB (CWLite/CW1200)”. It may have been disconnected, is in an error state, or is being used by another tool.

I plugged only my ChipWhisperer Lite. Now device manager is shown as

Universal Serial Bus device (ChipWhisperer Lite) and 2. Universal serial device (COM 5)

How to fix this issue?

Alex_Dewar · April 12, 2021, 4:11pm

Can you try unplugging + replugging? If you run the connect script twice, you’ll run into that error. You should have gotten a longer error message there. Can you post the full error message if disconnecting+reconnecting doesn’t work?

Alex

naufusa · April 17, 2021, 9:15pm

Hi Axel,
Sorry for the late reply due to some other works!
I think it is working fine after updating the firmware. I got the following output when I am running the CW305 AES tutorial (no VM).

attack_results.key_guess()
[208, 20, 249, 168, 201, 238, 37, 137, 225, 63, 12, 200, 182, 99, 12, 166].

Alex_Dewar · April 19, 2021, 6:08pm

If I remember the last round key correctly, that’s correct.

naufusa · April 19, 2021, 7:18pm

Yes, Thanks!

How to plot a captured trace (no VM)?
I am running Demo code without Jupyter: PA_HW_CW305_1-Attacking_AES_on_an_FPGA

Getting no warning when I running the code below, but It can’t plot the captured trace (the plot doesn’t come out).

from bokeh.plotting import figure, show
from bokeh.io import output_notebook

output_notebook()
p = figure(plot_width=800)

xrange = range(len(traces[0]))
p.line(xrange, traces[0], line_color=“red”)
show( p)

Alex_Dewar · April 19, 2021, 7:42pm

Are you trying to plot in a notebook?

naufusa · April 19, 2021, 8:06pm

No. I installed ChipWhisperer 5.5 directly (no VM) and simply running the above (demo) code in python IDLE

Alex_Dewar · April 19, 2021, 8:18pm

I’d recommend just using matplotlib then:

IIRC it should be:

import matplotlib.pyplot as plt
plt.figure()
plt.plot(data)
plt.show()

naufusa · April 19, 2021, 10:36pm

Yes, Now I got the plot! Thanks!

naufusa · April 19, 2021, 10:51pm

Hi Alex,
How to perform a basic TVLA test:

I am unable to perform a basic TVLA test for my above experiments.

First I captured 100 power traces using the TVLA tutorial (It is working fine). However, based on the recorded data, now getting the following warning when running the
Analysis code from https://github.com/newaetech/chipwhisperer-jupyter/blob/e33f4a2c822d7c195674b11a1de72828907e7255/PA_TVLA_1-Performing_TVLA_Testing_for_Crypto_Validation.ipynb

giving the following warning:

WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.BokehRenderer: Use method ‘params’ via param namespace
100 129
WARNING:param.ParameterizedMetaclass: Use method ‘params’ via param namespace
WARNING:param.ParameterizedMetaclass:Use method ‘params’ via param namespace
WARNING:param.Overlay: Use method ‘params’ via param namespace
WARNING:param.Overlay:Use method ‘params’ via param namespace

Alex_Dewar · April 19, 2021, 11:31pm

Hi,

You can fix with https://github.com/newaetech/chipwhisperer/issues/324. This will be fixed in our next release as well.

Alex

naufusa · April 20, 2021, 12:15am

Ok, now no warnings!
Thanks!