Installing ChipWhisperer/Required Tools - Windows - Revision history

Adewar at 14:06, 31 May 2019

2019-05-31T14:06:51Z

Fheubach: Change header levels

2018-05-01T14:12:56Z

Change header levels

Gdeon at 17:29, 19 May 2017

2017-05-19T17:29:34Z

Fheubach: /* Installing Hardware Drivers */

2017-05-19T16:30:31Z

‎Installing Hardware Drivers

Gdeon at 19:47, 16 May 2017

2017-05-16T19:47:43Z

Gdeon at 19:46, 16 May 2017

2017-05-16T19:46:37Z

Gdeon at 18:08, 16 May 2017

2017-05-16T18:08:07Z

Gdeon at 18:02, 16 May 2017

2017-05-16T18:02:23Z

Gdeon at 18:01, 16 May 2017

2017-05-16T18:01:59Z

Coflynn: /* Getting AVR Compiler Toolchain */

2017-03-27T01:02:40Z

‎Getting AVR Compiler Toolchain

← Older revision		Revision as of 14:06, 31 May 2019
Line 72:		Line 72:
	Now when you want to run WinAVR (e.g. to continue the examples here), you can simply double-click on the winavr.bat file. This will configure the path for just that terminal, rather than every terminal you open.		Now when you want to run WinAVR (e.g. to continue the examples here), you can simply double-click on the winavr.bat file. This will configure the path for just that terminal, rather than every terminal you open.

−	Note if using WinAVR on Windows 8.1, you must replace the dll msys-1.0.dll with an updated version. See [http://www.avrfreaks.net/forum/windows-81-compilation-error Windows 8.1 Fix] for a link to this DLL replacement.	+	Note if using WinAVR on Windows 8.1/10, you must replace the dll msys-1.0.dll with an updated version. See [http://www.avrfreaks.net/forum/windows-81-compilation-error Windows 8.1 Fix] for a link to this DLL replacement.

@@ Line 1: / Line 1: @@
-<h2> Python </h2>
+<h4> Python </h4>
 For any of the other installation methods, you'll need to have Python 2 installed on your computer. If you already a recent version of Python installed (2.7.x), you can skip this step. Note that Python 3.x will not work with this codebase. There's also a bit of setup that's needed to get other tools and prepare other drivers.
@@ Line 12: / Line 12: @@
 ''Optional'': You can add the python.exe you just installed to your PATH. To do so navigate to your installation folder, and run the '''WinPython Control Panel.exe''' program. Then select ''Advanced -> Register distribution...''. If you do not do this, you will have to run all commands in this document via the '''WinPython Command Prompt.exe'''. If you plan on running both 32-bit and 64-bit Python, you should not register them. Instead explicitly call the correct Python by always running the '''WinPython Command Prompt.exe''', and then calling specific programs (such as CW Capture or Analyzer) from that command prompt.
-<h2> Python Packages </h2>
+<h4> Python Packages </h4>
 There are a number of packages that the ChipWhisperer project uses. You'll need to install these so that the software can run. Note that the PyPi install process should automatically install these, so you shouldn't need to manually install everything there.
@@ Line 36: / Line 36: @@
 '''PYSCARD:''' If planning on using a PS/SC smartcard reader (i.e. standard USB-connected reader), you will need to install [https://sourceforge.net/projects/pyscard/files/pyscard/ pyscard].
-<h2> Installing Hardware Drivers </h2>
+<h4> Installing Hardware Drivers </h4>
 Details of driver installation are on specific pages for supported hardware (such as cwcapturerev2 and naecw1173_cwlite). Drivers are available from [http://chipwhisperer.com ChipWhisperer] release section.
-<h2> Getting AVR Compiler Toolchain </h2>
+<h4> Getting AVR Compiler Toolchain </h4>
 The following section is not required for your first attack - you can jump right to the tutorial if you wish. However you'll ultimately wish to modify the code of the device under test, and these instructions tell you how. You should first follow the tutorial to confirm your system is working before modifying the code however!
@@ Line 61: / Line 61: @@
 For details about programming the targets, see [[Tutorial B1 Building a SimpleSerial Project]].
-<h3> WinAVR Path Settings </h3>
+<h5> WinAVR Path Settings </h5>
 By default, WinAVR is added to your system path. This means you can run avr-gcc, make and other programs from your normal Windows command line. You may not want this on certain systems where you already have similar tools installed. In which case either uncheck the Add WinAVR to Path option, or edit your system path to remove the WinAVR directories.

@@ Line 1: / Line 1: @@
-== Python ==
+<h2> Python </h2>
 For any of the other installation methods, you'll need to have Python 2 installed on your computer. If you already a recent version of Python installed (2.7.x), you can skip this step. Note that Python 3.x will not work with this codebase. There's also a bit of setup that's needed to get other tools and prepare other drivers.
@@ Line 12: / Line 12: @@
 ''Optional'': You can add the python.exe you just installed to your PATH. To do so navigate to your installation folder, and run the '''WinPython Control Panel.exe''' program. Then select ''Advanced -> Register distribution...''. If you do not do this, you will have to run all commands in this document via the '''WinPython Command Prompt.exe'''. If you plan on running both 32-bit and 64-bit Python, you should not register them. Instead explicitly call the correct Python by always running the '''WinPython Command Prompt.exe''', and then calling specific programs (such as CW Capture or Analyzer) from that command prompt.
-== Python Packages ==
+<h2> Python Packages </h2>
 There are a number of packages that the ChipWhisperer project uses. You'll need to install these so that the software can run. Note that the PyPi install process should automatically install these, so you shouldn't need to manually install everything there.
@@ Line 36: / Line 36: @@
 '''PYSCARD:''' If planning on using a PS/SC smartcard reader (i.e. standard USB-connected reader), you will need to install [https://sourceforge.net/projects/pyscard/files/pyscard/ pyscard].
-== Installing Hardware Drivers ==
+<h2> Installing Hardware Drivers </h2>
 Details of driver installation are on specific pages for supported hardware (such as cwcapturerev2 and naecw1173_cwlite). Drivers are available from [http://chipwhisperer.com ChipWhisperer] release section.
-== Getting AVR Compiler Toolchain ==
+<h2> Getting AVR Compiler Toolchain </h2>
 The following section is not required for your first attack - you can jump right to the tutorial if you wish. However you'll ultimately wish to modify the code of the device under test, and these instructions tell you how. You should first follow the tutorial to confirm your system is working before modifying the code however!
@@ Line 61: / Line 61: @@
 For details about programming the targets, see [[Tutorial B1 Building a SimpleSerial Project]].
-=== WinAVR Path Settings ===
+<h3> WinAVR Path Settings </h3>
 By default, WinAVR is added to your system path. This means you can run avr-gcc, make and other programs from your normal Windows command line. You may not want this on certain systems where you already have similar tools installed. In which case either uncheck the Add WinAVR to Path option, or edit your system path to remove the WinAVR directories.

@@ Line 38: / Line 38: @@
 == Installing Hardware Drivers ==
-Details of driver installation are on specific pages for supported hardware (such as hwcapturerev2 and naecw1173_cwlite). Drivers are available from [http://chipwhisperer.com ChipWhisperer] release section.
+Details of driver installation are on specific pages for supported hardware (such as cwcapturerev2 and naecw1173_cwlite). Drivers are available from [http://chipwhisperer.com ChipWhisperer] release section.
 == Getting AVR Compiler Toolchain ==

@@ Line 56: / Line 56: @@
 <p>If this is successful, you'll see an output like the following:</p>
 <p>[[File:Avr-build-ok.png|image]]</p>
-<p>If instead you get an error something like <code>make: *** No rule to make target `simpleserial.elf', needed by `elf'.  Stop.</code>, this means a required file was missing.</p></li>
+<p>If instead you get an error something like <code>make: *** No rule to make target `simpleserial.elf', needed by `elf'.  Stop.</code>, this means a required file was missing.</p>
 Programming the target AVR is accomplished in one of two methods depending on your hardware. The ChipWhisperer Capture Rev 2 uses the external "AVR Studio" program, whereas the CW1173 and CW1200 use a programmer menu from the ChipWhisperer-Capture software.

@@ Line 51: / Line 51: @@
 To test the code build, follow these steps:
-<ol style="list-style-type: decimal;">
+<p><code>cd</code> to the directory with the avr-serial example, and run <code>make</code>:</p>
-<li><p><code>cd</code> to the directory with the avr-serial example, and run <code>make</code>:</p>
 <pre>cd c:\chipwhisperer\hardware\victims\firmware\simpleserial-aes
 make</pre>
@@ Line 58: / Line 57: @@
 <p>[[File:Avr-build-ok.png|image]]</p>
 <p>If instead you get an error something like <code>make: *** No rule to make target `simpleserial.elf', needed by `elf'.  Stop.</code>, this means a required file was missing.</p></li>
-<li>Programming the target AVR is accomplished in one of two methods depending on your hardware. The ChipWhisperer Capture Rev 2 uses the external "AVR Studio" program, whereas the CW1173 and CW1200 use a programmer menu from the ChipWhisperer-Capture software.
+Programming the target AVR is accomplished in one of two methods depending on your hardware. The ChipWhisperer Capture Rev 2 uses the external "AVR Studio" program, whereas the CW1173 and CW1200 use a programmer menu from the ChipWhisperer-Capture software.
 For details about programming the targets, see [[Tutorial B1 Building a SimpleSerial Project]].

← Older revision		Revision as of 18:08, 16 May 2017
Line 1:		Line 1:
−	~~Test~~
−
	== Python ==		== Python ==
	For any of the other installation methods, you'll need to have Python 2 installed on your computer. If you already a recent version of Python installed (2.7.x), you can skip this step. Note that Python 3.x will not work with this codebase. There's also a bit of setup that's needed to get other tools and prepare other drivers.		For any of the other installation methods, you'll need to have Python 2 installed on your computer. If you already a recent version of Python installed (2.7.x), you can skip this step. Note that Python 3.x will not work with this codebase. There's also a bit of setup that's needed to get other tools and prepare other drivers.

← Older revision		Revision as of 18:02, 16 May 2017
Line 1:		Line 1:
−	=== Python ===	+	Test
		+
		+	== Python ==
	For any of the other installation methods, you'll need to have Python 2 installed on your computer. If you already a recent version of Python installed (2.7.x), you can skip this step. Note that Python 3.x will not work with this codebase. There's also a bit of setup that's needed to get other tools and prepare other drivers.		For any of the other installation methods, you'll need to have Python 2 installed on your computer. If you already a recent version of Python installed (2.7.x), you can skip this step. Note that Python 3.x will not work with this codebase. There's also a bit of setup that's needed to get other tools and prepare other drivers.

← Older revision		Revision as of 18:01, 16 May 2017
Line 1:		Line 1:
−	== Python ==	+	=== Python ===
	For any of the other installation methods, you'll need to have Python 2 installed on your computer. If you already a recent version of Python installed (2.7.x), you can skip this step. Note that Python 3.x will not work with this codebase. There's also a bit of setup that's needed to get other tools and prepare other drivers.		For any of the other installation methods, you'll need to have Python 2 installed on your computer. If you already a recent version of Python installed (2.7.x), you can skip this step. Note that Python 3.x will not work with this codebase. There's also a bit of setup that's needed to get other tools and prepare other drivers.

@@ Line 46: / Line 46: @@
 To build the code, you'll need to install avr-gcc on Windows (if using the Virtual Machine, the following is ''not required'', as the VM comes setup with the AVR compiler already). On Windows, you could choose to install:
-* Atmel AVR-GCC standalone - see [http://www.atmel.com/tools/atmelavrtoolchainforwindows.aspx Atmel avr-gcc standalone]
+* Atmel AVR-GCC standalone - see [http://www.atmel.com/tools/atmelavrtoolchainforwindows.aspx Atmel avr-gcc standalone] (registration required)
-* WinAVR. Last release - 2010, see [https://sourceforge.net/projects/winavr/files/latest/download?source=typ_redirect WinAVR Page]
+* WinAVR. Last release - 2010, see [https://sourceforge.net/projects/winavr/files/latest/download?source=typ_redirect WinAVR Page] (no registration required)
 To test the code build, follow these steps: