Glitch Explorer - Revision history

Adewar: /* Using the Glitch Explorer - The Basics */

2018-09-06T12:59:04Z

‎Using the Glitch Explorer - The Basics

Fheubach at 20:17, 14 March 2018

2018-03-14T20:17:50Z

Fheubach: Rewrote the page for cw4.0

2018-03-14T20:17:15Z

Rewrote the page for cw4.0

Fheubach at 18:53, 14 March 2018

2018-03-14T18:53:10Z

Fheubach: Added under construction notice

2018-03-14T18:52:32Z

Added under construction notice

Fheubach: Updated glitch explorer page

2018-03-02T22:20:17Z

Updated glitch explorer page

Adriel: /* Using the Glitch Explorer - The Basic */

2016-07-15T21:42:25Z

‎Using the Glitch Explorer - The Basic

Coflynn at 14:51, 15 July 2016

2016-07-15T14:51:24Z

Adriel: /* Using the Glitch Explorer - Advanced */

2016-07-15T14:34:33Z

‎Using the Glitch Explorer - Advanced

Adriel: /* Using the Glitch Explorer - Advanced */

2016-07-15T14:34:19Z

‎Using the Glitch Explorer - Advanced

@@ Line 23: / Line 23: @@
 <br>
 <li>
-Set up the parameters for glitching (example: run the <code>connect_cwlite_glitch.py</code> script)
+Set up the parameters for glitching (example: run the <code>setup_cwlite_glitch.py</code> script)
 [[File: run_glitch_script.png|800px]]
 </li>

← Older revision		Revision as of 20:17, 14 March 2018
Line 1:		Line 1:
	{{Warningbox\|For the older V3.x tools, see [[V3:Glitch_Explorer]]}}		{{Warningbox\|For the older V3.x tools, see [[V3:Glitch_Explorer]]}}
−	~~<br>~~
−	~~{{Warningbox\|This page is under construction }}~~

	The Glitch Explorer allows an automatic exploration of a range of one or more parameter values. It means that the user can test multiple glitch setups at the same time and see the result in a nice scatterplot, highlighting the successful attempts.		The Glitch Explorer allows an automatic exploration of a range of one or more parameter values. It means that the user can test multiple glitch setups at the same time and see the result in a nice scatterplot, highlighting the successful attempts.

@@ Line 5: / Line 5: @@
 The Glitch Explorer allows an automatic exploration of a range of one or more parameter values. It means that the user can test multiple glitch setups at the same time and see the result in a nice scatterplot, highlighting the successful attempts.
-[[File:glitch explorer overview.png|1100px]]
+[[File:glitch_explorer_overview_v4.PNG|1100px]]
 == The Glitch Explorer Window ==
 The main window of the glitch explorer looks like this:
-[[File:Screen Shot 2016-07-15 at 10.24.13 AM.png|400px]]
+[[File:glitch_explorer_window_v4.png|400px]]
 In top, the output of the system combined with the parameters of the glitch is displayed (the 'output window').
-In bottom, you can adjust general parameters of the glitching system, such as what counts as a successful glitch or not and how many parameters to fiddle with.
+In bottom, you can adjust general parameters of the glitching system, such as what counts as a successful glitch or not and the ability to load existing data into the glitch explorer table.
-== Using the Glitch Explorer - The Basic ==
+== Using the Glitch Explorer - The Basics ==
-To start using the Glitch Explorer, you should first switch to the "Target Settings" tab and set the "Output Format" to be $GLITCH$. This will mean data is no longer sent to the terminal emulator when using the capture 1 or capture M buttons, but instead, is logged in the glitch explorer window.
+Here are a few steps that should be done before using the glitch explorer (example uses the ChipWhisperer Lite):
-The next step is to set the number of tuning parameters. You may want to start with 1 (0 is used to just record manual exploration attempts in the table) and then increment it to 2 or more later. This will generate another group in the list where you can tune the settings for each parameter:
+Now you are ready to click the "Capture M" to start the exploration. </b>If you run into forced trigger issues go back to the previous steps where it was mentioned how to fix the issue.</b>
-−
-[[File:Screen Shot 2016-07-15 at 10.30.53 AM.png|400px]]
-* Name - is just a reminder of what we are tuning.
-−
-* Parameter Path - defines what will be modified. This string can simply be copied from the Script Commands, provided that you remove the last element first (which is the value).
-* Data Format - defines what type of data will be inserted into the parameter.
-* Range - defines the range from the minimum to maximum that will be swept for the parameter.
-* Value - defines the current/start value of the sweep. This is NOT automatically set to the minimum value of your sweep since you may want to stop and continue later or attack a smaller number of traces. If you want to perform the full sweep, you must manually set this to the minimum of the range or click reset.
-* Step - defines the incremented on each glitch attempt. When the value reaches the maximum defined by the range, it will loop around to the minimum and continue incrementing.
-* Repeat - defines how many times to perform the same value. This can be used to determine the reliability of each glitch value.
-The last step is to set the "Generic Settings"->"Acquisition Settings"->"Number of Traces" to a value high enough to loop trough all the value combinations. It can be performed automatically clicking in the "Glitch Explorer"->"Traces Required"->"Use this value" button.
-−
-Now you are ready to click the "Capture M" to start the exploration.
 == Using the Glitch Explorer - Advanced ==
 To get more detailed information of how to use the Glitch Explorer, follow the [[Tutorial A2 Introduction to Glitch Attacks (including Glitch Explorer)|A2]] and [[Tutorial A3 VCC Glitch Attacks|A3]] tutorials.
-If you want to create a script to fully automate this attack, check the example in <code> chipwhisperer/software/scripting-examples/glitch_explorer_simple.py </code>.
+If you want to create a script to fully automate this attack, check out the example in <code> chipwhisperer/software/scripting-examples/glitch_explorer_simple.py </code>.

@@ Line 1: / Line 1: @@
 {{Warningbox|For the older V3.x tools, see [[V3:Glitch_Explorer]]}}
-{{Warningbox| This page is under construction }}
+<br>
 The Glitch Explorer allows an automatic exploration of a range of one or more parameter values. It means that the user can test multiple glitch setups at the same time and see the result in a nice scatterplot, highlighting the successful attempts.

← Older revision		Revision as of 18:52, 14 March 2018
Line 1:		Line 1:
	{{Warningbox\|For the older V3.x tools, see [[V3:Glitch_Explorer]]}}		{{Warningbox\|For the older V3.x tools, see [[V3:Glitch_Explorer]]}}
		+	{{Warningbox\| This page is under construction }}

	The Glitch Explorer allows an automatic exploration of a range of one or more parameter values. It means that the user can test multiple glitch setups at the same time and see the result in a nice scatterplot, highlighting the successful attempts.		The Glitch Explorer allows an automatic exploration of a range of one or more parameter values. It means that the user can test multiple glitch setups at the same time and see the result in a nice scatterplot, highlighting the successful attempts.

← Older revision		Revision as of 14:34, 15 July 2016
Line 33:		Line 33:

	== Using the Glitch Explorer - Advanced ==		== Using the Glitch Explorer - Advanced ==
−	To get more detailed information of how to use the Glitch Explorer, follow the [[Tutorial A2 Introduction to Glitch Attacks (including Glitch Explorer)\|A2]] and [[Tutorial A3 VCC Glitch Attacks\|A3]] tutorials. If you want to create a script to fully automate this attack, check the example in the file chipwhisperer/software/chipwhisperer/tests/glitchscript.py that currently is being used internally for testing purposes.	+	To get more detailed information of how to use the Glitch Explorer, follow the [[Tutorial A2 Introduction to Glitch Attacks (including Glitch Explorer)\|A2]] and [[Tutorial A3 VCC Glitch Attacks\|A3]] tutorials.
		+
		+	If you want to create a script to fully automate this attack, check the example in the file chipwhisperer/software/chipwhisperer/tests/glitchscript.py that currently is being used internally for testing purposes.