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

File Formats

16 bytes added, 14:46, 1 May 2018
no edit summary
==File Formats (Projects and Traces)==
This page explains some of the file formats used in the ChipWhisperer Software.
===Project Files===
Project files are stored as a simple text-file. The most basic file will include information about stored traces, along with some basic project file information.
{{Warningbox|If you perform capture before saving a project file, files will be written to a '''temporary directory'''. In this case your project file will reference this temporary directory. Files may not be automatically moved out of this temporary directory when you save a project, but you can always use the "Consolidate" option to force all data to be moved into the project file directory.}}
===Trace Files===
Trace files in the ChipWhisperer software are defined through a configuration file, with the suffix <code>.cfg</code>. Any trace added to the ChipWhisperer project will have a configuration file - this file does not store data, but tells the software where it is stored and what format it is stored in.
Let's now investigate specific options for the "native" file format, along with format information.
==== Native File Format ====
Specific options for the native file format are:
|}
Each of these is a [http://Docs.scipy.org/doc/numpy/reference/generated/numpy.array.html NumPy array], where the first element is trace n=0, the second is trace n=1, etc. You can load this file using the NumPy load command.
== Example Scripts ==
=== Load Native File Format, modify a value, Save File(s) ===
=== Native File Format to MATLAB Workspace ===
The following will convert a single file into a MATLAB workspace:<syntaxhighlight lang="python">
import scipy.io
</syntaxhighlight>
=== Native File Format to Text Files ===

Navigation menu