458
edits
Changes
no edit summary
= ChipWhisperer V3v3.5 x to V44.0 =
ChipWhisperer software release V4.0.0 has drastically changed the API and interface. The V4.0.0 architecture tries to open up the program internals, and force you (the user) to use the API instead of clicking buttons. While it's a little harder to get started, it's MUCH easier to perform complex tasks, or even to use the command line for interactive work.
The "example scripts" and "glitch explorer" have all been replaced with true Python scripts. You write small (or large) snippets of code, and run those code to perform automated tasks.
If you have used ChipWhisperer before see [[Tutorial_B5_Breaking_AES_(Straightforward)]] for a quick overview of how things changed.
== Analyzer Changes ==
The analyzer interface looks different. Most noteably:
* The "Attack" button is disabled (will be re-enabled once better integrated). Instead you just run a script which explicitly configures things.
* The GUI does not affect the actual script being run. You can view settings from the GUI, but you must manually copy things into the scripts.
== Example Scripts ==
== Glitch Explorer ==
The Glitch Explorer has drastically changed in 4.0.0. Previously the Glitch Explorer used the "Scripting" interface and relied on you specifying some arbitrary data to change. Now instead you define a Python function that changes the glitch parameters, and use the existing "auxiliary" links to execute the functions.
== API Changes==
The ChipWhisperer is moving towards a "sane" API. This means that now for example you can inspect the value of a "scope" object, and it will print all current settings:<syntaxhighlight lang="python">
>>> scope.clock.clkgen_freq = 4E6
</syntaxhighlight>
== Using ChipWhisperer as a python package ==
Find [[Making Scripts|scripting examples]] of how to use ChipWhisperer as python package.