As of August 2020 the site you are on (wiki.newae.com) is deprecated, and content is now at rtfm.newae.com.

Changes

Jump to: navigation, search

CW1200 ChipWhisperer-Pro

1,411 bytes added, 18:14, 1 May 2018
no edit summary
Check out a [https://youtu.be/qS6JwX4SBOI sneak peek of the CW-Pro].
'''(TODO[[File: picture of CW-Pro)'''cwpro_invisible.png|500x500px]]{{TOC|limit=3}}
== Connection Quick-Start == <ol><li>Follow the [[Installing ChipWhisperer]] instructions for the ChipWhisperer software and its prerequisites.</li><li>Connect ChipWhisperer-Lite, install USB Drivers:<dl><dt>Windows:</dt><dd><ul><li>Plug micro-USB cable into ChipWhisperer-Lite</li><li>If the &quot;New Hardware Found&quot; wizard doesn't prompt you for drivers, go to the control panel and find the &quot;ChipWhisperer-Pro&quot; device, and select "Update Drivers".</li><li>You can find drivers in <code>c:\chipwhisperer\hardware\capture\chipwhisperer-cw1200\</code>. You will likely need to extract them from the <code>cw1200_usbdriver.zip</code> file. If so simply extract them somewhere (i.e. your desktop), and then point the new hardware found wizard to that location.</li></ul></dd><dt>Linux:</dt><dd><ul><li><p>Driver installation is not required, but if you do not update the 'udev' system, you will be unable to run ChipWhisperer-Capture as a regular user. To update the udev system, first make sure the ChipWhisperer-Lite is Make a file called <code>/etc/udev/rules.d/99-cwlite.rules</code> . The contents of this file should be:</p><pre># allow users to claim the deviceSUBSYSTEM==&quot;usb&quot;, ATTRS{idVendor}==&quot;2b3e&quot;, ATTRS{idProduct}==&quot;ace3&quot;, MODE=&quot;0664&quot;, GROUP=&quot;plugdev&quot;</pre></li><li><p>Add your username to the plugdev group:</p><pre>$ sudo usermod -a -G plugdev YOUR-USERNAME</pre></li><li><p>And reset the udev system:</p><pre>$ sudo udevadm control --reload-rules</pre></li><li>Finally log out &amp; in again for the group change to take effect.</li><li>Connect the USB-A cable, and DC power cable</li></ul></dd><dt>MAC:</dt><dd><ul><li>No special installation required - must ensure you have installed libusb via homebrew (see instructions at [[MacOSX_Installation]]).</li></ul></dd></dl></li><li><p>To check for a successful installation Run ChipWhisperer-Capture. This can be done from one of three ways:</p><blockquote><ul><li>Double-click on <code>CWCapture.pyw</code> in the <code>chipwhisperer\software</code> folder. You must have installed Python into your path for this to work.</li><li>run <code>python CWCapture.pyw</code> from the <code>chipwhisperer\software</code> folder using a command prompt with Python in the path.</li><li>run <code>python CWCaptureGUI.py</code> from the <code>chipwhisperer\software\chipwhisperer\capture\ui</code> directory.</li></ul> <p>The last option is the most reliable, in that it should always work on all platforms. If it doesn't start look for possible missing modules or other useful errors.</p></blockquote><li>Your ChipWhisperer-Lite is now connected. See the Tutorial B-1 for details of the demo attack.</li></li></ol>  == Power Supply ==
The ChipWhisperer Pro can only be powered through its 5 V jack. It cannot be powered through the USB port - internally, there are no connections to the USB port's 5 V rail. This limitation is primarily due to the high current draw of the Pro: while powering the touchscreen running and an external target, it would be easy to exceed the USB current limit, causing all sorts of issues.
If you're using the USB power cable, it is recommended to use a separate power supply to power any external target boards.
== Basic Usage ==
The basic features on the Pro are exactly the same as the ChipWhisperer Lite. This means that any scripts and tutorials made for the Lite will work on the Pro, too: the connectors and pinouts are exactly the same.
{{CollapsibleSection
|intro = = == AVR Programmer ===
|content= CW1173_ChipWhisperer-Lite/AVR Programmer}}
{{CollapsibleSection
|intro = = == XMEGA Programmer ===
|content= CW1173_ChipWhisperer-Lite/XMEGA Programmer}}
{{CollapsibleSection
|intro = = == Using Glitch Port ===
|content= CW1173_ChipWhisperer-Lite/Glitch Port}}
{{CollapsibleSection
|intro = = == Using Measure Port ===
|content= CW1173_ChipWhisperer-Lite/Measure Port}}
{{CollapsibleSection
|intro = = == 20-Pin Connector ===
|content= CW1173_ChipWhisperer-Lite/20-Pin Connector}}
{{CollapsibleSection
|intro = = == Upgrading SAM3U Firmware ===
|content= CW1173_ChipWhisperer-Lite/Upgrading SAM3U Firmware}}
== Advanced Features =={{CollapsibleSection|intro = === Streaming Mode ===The |content= CW1200 ChipWhisperer -Pro has a streaming mode that allows extremely long captures as long as relatively low sampling rates are used. For example, this plot shows an exerpt from two traces with nearly 1 million samples:/Streaming Mode}}
'''TODO: add streaming example'''{{CollapsibleSection|intro = === Trigger Module ===|content= CW1200 ChipWhisperer-Pro/Trigger Module}}
This capture mode is useful for many types of attacks, including:{{CollapsibleSection* Full captures of slow software AES libraries|intro = === SMA I/O ===* Power analysis on ECC* Context switches on embedded operating systems|content= CW1200 ChipWhisperer-Pro/SMA I/O}}
While streaming, the ChipWhisperer hardware sends ADC data back to the capture software while recording more samples (instead of waiting until the end of the capture). During this process, the ADC samples are sent back to the computer in packets of approximately 3000 samples at a time. As a block diagram, this looks like:{{CollapsibleSection|intro = === Touchscreen ===[[File:Cwpro|content= CW1200 ChipWhisperer-stream.PNG|800px]] The main danger in streaming mode is that the FPGA's sample buffer can overflow if the PC doesn't request these packets quickly enough. In practice, the maximum transfer rate is around 10 MsamplesPro/s, so the maximum ADC frequency is approximately 10 MHz in streaming mode. Trying to stream above this rate will usually cause data to be lost: the FPGA overwrites samples after the buffer is full, so it's impossible to recover these samples after overrunning the buffer.Touchscreen}}
On the software end, there are two things to watch for== Hardware =={{Template:* Long captures from streaming mode (millions of points) may take several seconds to record. When working with these long captures, make sure the software's timeouts are long enough.* Extremely long captures take a lot of memory. 64-bit Python is recommended if you plan on capturing many traces with millions of samples - you can hit the memory limit on 32-bit Python pretty quickly.Hardware}}
== SAD Trigger ==== UART/SPI Trigger ==== SMA I/O == = Touchscreen =- Pictures of screens- Descriptions of displays {{Template[[Category:Capture Hardware}}]]
Retrieved from "http://wiki.newae.com/Special:MobileDiff/1828...3441"

Navigation menu