| As of August 2020 the site you are on (wiki.newae.com) is deprecated, and content is now at rtfm.newae.com. |
Difference between revisions of "Installing ChipWhisperer/Required Tools - Linux"
(Created page with "== Python == On Linux, installing Python & all the associated packages is much easier than on Windows. Typically you can install them from a package manager, if you are us...") |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <h4> Python </h4> | |
| − | On Linux, installing Python & all the associated packages is | + | On Linux, installing Python & all the associated packages is straightforward. Typically you can install them from a package manager, if you are using Fedora Core or similar, just type: |
<pre>$ sudo yum install python27 python27-devel python27-libs python-pyside numpy scipy python-configobj pyusb | <pre>$ sudo yum install python27 python27-devel python27-libs python-pyside numpy scipy python-configobj pyusb | ||
| Line 11: | Line 11: | ||
</pre> | </pre> | ||
| − | + | <h4> Getting the AVR Toolchain </h4> | |
Many of the tutorials use the AVR XMEGA microcontrollers as a target. In order to compile code for these targets, you'll need the AVR toolchain. This is easy to set up: | Many of the tutorials use the AVR XMEGA microcontrollers as a target. In order to compile code for these targets, you'll need the AVR toolchain. This is easy to set up: | ||
<pre> | <pre> | ||
| Line 17: | Line 17: | ||
</pre> | </pre> | ||
| − | + | <h4> Hardware Drivers </h4> | |
The ''driver'' for Linux is built in, however you need to allow your user account to access the peripheral. To do so, you'll have to make a file called <code>/etc/udev/rules.d/99-newae.rules</code> . The contents of this file should be: | The ''driver'' for Linux is built in, however you need to allow your user account to access the peripheral. To do so, you'll have to make a file called <code>/etc/udev/rules.d/99-newae.rules</code> . The contents of this file should be: | ||
| Line 42: | Line 42: | ||
Finally log out & in again for the group change to take effect. | Finally log out & in again for the group change to take effect. | ||
| − | You can always find the latest version of this file in [https:// | + | You can always find the latest version of this file in [https://github.com/newaetech/chipwhisperer/blob/master/hardware/99-newae.rules GIT]. |
| − | + | <h4> FTDI Hardware Driver (SASEBO-W, SAKURA-G, SASEBO-GII) </h4> | |
'''This is only required for supporting FTDI-connected hardware''' such as the SASEBO-W, SAKURA-G, SASEBO-GII. This is NOT required for the ChipWhisperer Capture Rev2. | '''This is only required for supporting FTDI-connected hardware''' such as the SASEBO-W, SAKURA-G, SASEBO-GII. This is NOT required for the ChipWhisperer Capture Rev2. | ||
Latest revision as of 06:47, 1 May 2018
Contents
Python
On Linux, installing Python & all the associated packages is straightforward. Typically you can install them from a package manager, if you are using Fedora Core or similar, just type:
$ sudo yum install python27 python27-devel python27-libs python-pyside numpy scipy python-configobj pyusb $ sudo pip install pyqtgraph
On Ubuntu or similar:
$ sudo apt-get install python2.7 python2.7-dev python2.7-libs python-numpy python-scipy python-pyside python-configobj python-setuptools python-pip $ sudo pip install pyusb $ sudo pip install pyqtgraph
Getting the AVR Toolchain
Many of the tutorials use the AVR XMEGA microcontrollers as a target. In order to compile code for these targets, you'll need the AVR toolchain. This is easy to set up:
sudo apt-get install avr-libc gcc-avr
Hardware Drivers
The driver for Linux is built in, however you need to allow your user account to access the peripheral. To do so, you'll have to make a file called /etc/udev/rules.d/99-newae.rules . The contents of this file should be:
# CW-Lite
SUBSYSTEM=="usb", ATTRS{idVendor}=="2b3e", ATTRS{idProduct}=="ace2", MODE="0664", GROUP="plugdev"
# CW-1200
SUBSYSTEM=="usb", ATTRS{idVendor}=="2b3e", ATTRS{idProduct}=="ace3", MODE="0664", GROUP="plugdev"
# CW-305 (Artix Target)
SUBSYSTEM=="usb", ATTRS{idVendor}=="2b3e", ATTRS{idProduct}=="c305", MODE="0664", GROUP="plugdev"
# CW-CR2
SUBSYSTEM=="usb", ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="8613", MODE="0664", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="221a", ATTRS{idProduct}=="0100", MODE="0664", GROUP="plugdev"
Then add your username to the plugdev group:
$ sudo usermod -a -G plugdev YOUR-USERNAME
And reset the udev system:
$ sudo udevadm control --reload-rules
Finally log out & in again for the group change to take effect.
You can always find the latest version of this file in GIT.
FTDI Hardware Driver (SASEBO-W, SAKURA-G, SASEBO-GII)
This is only required for supporting FTDI-connected hardware such as the SASEBO-W, SAKURA-G, SASEBO-GII. This is NOT required for the ChipWhisperer Capture Rev2.
First, you need to install the D2XX drivers & python module. See the section #Optional_Packages.
Currently, there is a bit of a hack needed. You have to create (or modify if it exists) the file /etc/udev/rules.d/99-libftdi.rules . The following modifications will cause any FTDI-serial device to stop working, so backup the existing file! The contents of this file should be:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", MODE="0664", GROUP="plugdev"
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", RUN+="/bin/sh -c 'echo $kernel > /sys/bus/usb/drivers/ftdi_sio/unbind'"
Then add your username to the plugdev group (if not already done):
$ sudo usermod -a -G plugdev YOUR-USERNAME
And reset the udev system:
$ sudo udevadm control --reload-rules
Finally log out & in again for the group change to take effect.
