Changes

V5:Installing ChipWhisperer/Required Tools - Windows

575 bytes added, 14:44, 14 May 2019
no edit summary
Go to your installation directory for WinPython, and run the shortcut called '''WinPython Command Prompt.exe'''. This will give you a command prompt which is setup to run Python along with associated scripts.
''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 scripts or Analyzer) from that command promptnotebooks.
<h4> Python Packages </h4>
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 [httphttps://www.atmelmicrochip.com/toolsmymicrochip/atmelavrtoolchainforwindowsfilehandler.aspx Atmel ?ddocname=en607654 avr-gcc standalone] (registration required). You'll need to unzip this file and add the bin folder to your path. See [https://docs.alfresco.com/4.2/tasks/fot-addpath.html this link] for instructions on how to add something to your path.* WinAVR. WinAVR is rather old at this point, so its use is not recommended. 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:
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.1and possibly Windows 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.
==== Installing Arm Toolchain ====
To be able to build firmware for ARM Targets, you'll need to install the GNU Toolchain for ARM Devices. An installer for Windows and archives for Linux/Windows can be found [https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads here]. Make sure you install the '''2018-q2 version''' of the software, as 2018-q4 has a bug that prevents compiling and earlier ones may not work once uploaded. If you use the installer, make sure the "Add path to environment variable", "Add registry information", and "Launch gccvar.bat" boxes are ticked. Otherwise, you'll need to add the compiler to your path as with avr-gcc.
Once you've done this, open a terminal and type <code>arm-none-eabi-gcc</code>. If this fails, you'll need to add the toolchain to your path manually.
 
This doesn't install make like WinAVR does, so if you haven't installed that, you'll need to on your own (the easiest way is just to install WinAVR as well).
Approved_users, administrator
366
edits