<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://wiki.newae.com/index.php?action=history&amp;feed=atom&amp;title=V3%3AGlitch_Explorer</id>
		<title>V3:Glitch Explorer - Revision history</title>
		<link rel="self" type="application/atom+xml" href="http://wiki.newae.com/index.php?action=history&amp;feed=atom&amp;title=V3%3AGlitch_Explorer"/>
		<link rel="alternate" type="text/html" href="http://wiki.newae.com/index.php?title=V3:Glitch_Explorer&amp;action=history"/>
		<updated>2026-06-13T09:15:08Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.26.2</generator>

	<entry>
		<id>http://wiki.newae.com/index.php?title=V3:Glitch_Explorer&amp;diff=3149&amp;oldid=prev</id>
		<title>Fheubach: Adding V3 page for the glitch explorer</title>
		<link rel="alternate" type="text/html" href="http://wiki.newae.com/index.php?title=V3:Glitch_Explorer&amp;diff=3149&amp;oldid=prev"/>
				<updated>2018-03-02T22:17:25Z</updated>
		
		<summary type="html">&lt;p&gt;Adding V3 page for the glitch explorer&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;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.&lt;br /&gt;
&lt;br /&gt;
[[File:glitch explorer overview.png|1100px]]&lt;br /&gt;
&lt;br /&gt;
== The Glitch Explorer Window ==&lt;br /&gt;
The main window of the glitch explorer looks like this:&lt;br /&gt;
&lt;br /&gt;
[[File:Screen Shot 2016-07-15 at 10.24.13 AM.png|400px]]&lt;br /&gt;
&lt;br /&gt;
In top, the output of the system combined with the parameters of the glitch is displayed (the 'output window').&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Using the Glitch Explorer - The Basic ==&lt;br /&gt;
To start using the Glitch Explorer, you should first switch to the &amp;quot;Target Settings&amp;quot; tab and set the &amp;quot;Output Format&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
Then, you should define what is a Normal and a Successful Response. This information is used to highlight the individual attacks. You should use Python expressions here, where 's' is a str-type variable which contains the response of the system (ex.: s.endswith(&amp;quot;123456&amp;quot;)).&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
[[File:Screen Shot 2016-07-15 at 10.30.53 AM.png|400px]]&lt;br /&gt;
* Name - is just a reminder of what we are tuning.&lt;br /&gt;
&lt;br /&gt;
* 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).&lt;br /&gt;
* Data Format - defines what type of data will be inserted into the parameter.&lt;br /&gt;
* Range - defines the range from the minimum to maximum that will be swept for the parameter.&lt;br /&gt;
* 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.&lt;br /&gt;
* 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.&lt;br /&gt;
* Repeat - defines how many times to perform the same value. This can be used to determine the reliability of each glitch value.&lt;br /&gt;
The last step is to set the &amp;quot;Generic Settings&amp;quot;-&amp;gt;&amp;quot;Acquisition Settings&amp;quot;-&amp;gt;&amp;quot;Number of Traces&amp;quot; to a value high enough to loop trough all the value combinations. It can be performed automatically clicking in the &amp;quot;Glitch Explorer&amp;quot;-&amp;gt;&amp;quot;Traces Required&amp;quot;-&amp;gt;&amp;quot;Use this value&amp;quot; button.&lt;br /&gt;
&lt;br /&gt;
Now you are ready to click the &amp;quot;Capture M&amp;quot; to start the exploration.&lt;br /&gt;
&lt;br /&gt;
== Using the Glitch Explorer - Advanced ==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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.&lt;/div&gt;</summary>
		<author><name>Fheubach</name></author>	</entry>

	</feed>