|As of August 2020 the site you are on (wiki.newae.com) is deprecated, and content is now at rtfm.newae.com.|
Difference between revisions of "Glitch Explorer"
(→Using the Glitch Explorer - The Basics)
|Line 23:||Line 23:|
Set up the parameters for glitching (example: run the <code>
Set up the parameters for glitching (example: run the <code>.py</code> script)
Latest revision as of 04:59, 6 September 2018
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 Window
The main window of the glitch explorer looks like this:
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 the ability to load existing data into the glitch explorer table.
Using the Glitch Explorer - The Basics
Here are a few steps that should be done before using the glitch explorer (example uses the ChipWhisperer Lite):
Connect the ChipWhisperer Scope and Target (example: run the
Set up the parameters for glitching (example: run the
Setup the automatic reset aux module (example: run the
Note: This file may have to be edited if you later have issues with trigger timeouts. The trigger timeouts can usually be fixed by switching the appropriate lines in a copy of the script
# Reset before arming - more stable aux_list.register(Resetter.resetThenDelay, "before_trace") # Reset after arming - scope can catch entire reset #aux_list.register(Resetter.delayThenReset, "after_arm")
# Reset before arming - more stable #aux_list.register(Resetter.resetThenDelay, "before_trace") # Reset after arming - scope can catch entire reset aux_list.register(Resetter.delayThenReset, "after_arm")
Another note: Remember to run this script and disable the other aux module inside the "Aux Settings" tab.
Change the glitch trigger source from manual to external single. Run this command in the python console:
self.scope.glitch.trigger_src = "ext_single"
Register the change_glitch_parameters function as the glitch explorer iterator (example: run the
ge_widthoffset_vary.pyscript). Changes to the step size and range that the glitch explorer covers can be customized by changing variables within this script and running the changed script.
- Set the normal and successful outputs (example: using the firmware in glitch-simple, after editing the c to use the glitch1() function rather than the glitch_infinite() function)
- Open the glitch explorer graph widget by pressing the Plot Widget button inside the Glitch Explorer Window.
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>