Making Scripts - Revision history

Fheubach: Updated scripts and added stm32 scripts

2018-04-10T19:13:56Z

Updated scripts and added stm32 scripts

Show changes

Fheubach: Added the example scripts and a description of each

2018-03-02T21:48:01Z

Added the example scripts and a description of each

Show changes

Fheubach: added cleanup

2018-02-21T17:56:17Z

added cleanup

Fheubach: /* Scripting with ChipWhisperer as python module */

2018-02-21T17:34:09Z

‎Scripting with ChipWhisperer as python module

Fheubach: Added example of headless script

2018-02-21T17:32:28Z

Added example of headless script

Coflynn at 03:21, 21 February 2018

2018-02-21T03:21:51Z

Coflynn: Replaced content with "{{For the older V3.x tools, see V3:Making_Scripts}} TODO: Push the update for V4.x"

2018-02-21T03:21:41Z

Replaced content with "{{For the older V3.x tools, see V3:Making_Scripts}} TODO: Push the update for V4.x"

Show changes

Coflynn at 03:19, 21 February 2018

2018-02-21T03:19:26Z

Coflynn at 02:54, 21 February 2018

2018-02-21T02:54:49Z

Coflynn at 02:54, 21 February 2018

2018-02-21T02:54:37Z

@@ Line 70: / Line 70: @@
 plt.plot(traces[0])
 plt.show()
 </syntaxhighlight>

@@ Line 1: / Line 1: @@
 {{Warningbox|For the older V3.x tools, see [[V3:Making_Scripts]]}}
-== Scripting with ChipWhisperer as python module ==
+== Scripting with ChipWhisperer as a python module ==
 When used without the GUI, the 4.0 API removes much of the high level abstractions so you can have more control over the capture process. It also answers questions like--when I capture a trace in what order are things happening? The following example scripts will give you a starting point when scripting with the ChipWhisperer tool.
-=== Perform Some Traces and get the results as Numpy array ===
+=== Perform Some Traces during AES encryption and get the results as Numpy array ===
 This script is an example of using the <code>chipwhisperer</code> module for capturing traces during AES encryption. <b>Make sure to have the correct firmware loaded on the target.</b>
 <syntaxhighlight lang=python>

← Older revision		Revision as of 17:32, 21 February 2018
Line 1:		Line 1:
	{{Warningbox\|For the older V3.x tools, see [[V3:Making_Scripts]]}}		{{Warningbox\|For the older V3.x tools, see [[V3:Making_Scripts]]}}

−	~~TODO~~: ~~Push~~ the ~~update~~ for V4.x	+	== Scripting with ChipWhisperer as python module ==
		+	When used without the GUI, the 4.0 API removes much of the high level abstractions so you can have more control over the capture process. It also answers questions like--when I capture a trace in what order are things happening? The following example scripts will give you a starting point when scripting with the ChipWhisperer tool.
		+	=== Perform Some Traces and get the results as Numpy array ===
		+	This script is an example of using the <code>chipwhisperer</code> module for capturing traces during AES encryption. <b>Make sure to have the correct firmware loaded on the target.</b>
		+	<syntaxhighlight lang=python>
		+	import time
		+
		+	import numpy as np
		+	import chipwhisperer as cw
		+	from chipwhisperer.capture.acq_patterns.basic import AcqKeyTextPattern_Basic
		+	import matplotlib.pyplot as plt
		+
		+	scope = cw.scope()
		+	target = cw.target(scope)
		+
		+	# setup scope parameters
		+	scope.gain.gain = 45
		+	scope.adc.samples = 3000
		+	scope.adc.offset = 1250
		+	scope.adc.basic_mode = "rising_edge"
		+	scope.clock.clkgen_freq = 7370000
		+	scope.clock.adc_src = "clkgen_x4"
		+	scope.trigger.triggers = "tio4"
		+	scope.io.tio1 = "serial_rx"
		+	scope.io.tio2 = "serial_tx"
		+	scope.io.hs2 = "clkgen"
		+
		+	ktp = AcqKeyTextPattern_Basic(target=target)
		+
		+	traces = []
		+	N = 50 # Number of traces
		+	for i in range(N):
		+	key, text = ktp.newPair() # manual creation of a key, text pair can be substituted here
		+
		+	target.reinit()
		+
		+	target.setModeEncrypt() # only does something for targets that support it
		+	target.loadEncryptionKey(key)
		+	target.loadInput(text)
		+
		+	# run aux stuff that should run before the scope arms here
		+
		+	scope.arm()
		+
		+	# run aux stuff that should run after the scope arms here
		+
		+	target.go()
		+	timeout=50
		+	# wait for target to finish
		+	while target.isDone() is False and timeout:
		+	timeout -= 1
		+	time.sleep(0.01)
		+
		+	try:
		+	ret = scope.capture()
		+	if ret:
		+	print('Timeout happened during acquisition')
		+	except IOError as e:
		+	print('IOError: %s' % str(e))
		+
		+	# run aux stuff that should happen after trace here
		+
		+	traces.append(scope.getLastTrace())
		+
		+	trace_array = np.asarray(traces) # if you prefer to work with numpy array for number crunching
		+
		+	# show an example trace
		+	plt.plot(traces[0])
		+	plt.show()
		+	</syntaxhighlight>

← Older revision		Revision as of 03:21, 21 February 2018
Line 1:		Line 1:
−	{{For the older V3.x tools, see [[V3:Making_Scripts]]}}	+	{{Warningbox\|For the older V3.x tools, see [[V3:Making_Scripts]]}}

	TODO: Push the update for V4.x		TODO: Push the update for V4.x

← Older revision		Revision as of 03:19, 21 February 2018
Line 1:		Line 1:
		+	See [[V3:Making_Scripts]]
		+
	<H1>THIS PAGE IS OLD - ONLY FOR 3.X SCRIPTS. WILL BE UPDATED SHORTLY. </H1>		<H1>THIS PAGE IS OLD - ONLY FOR 3.X SCRIPTS. WILL BE UPDATED SHORTLY. </H1>

@@ Line 1: / Line 1: @@
 =The Basic=
 User scripts allows partial (i.e.: setting up the environment) or total automation of the execution flow.
 A basic script would look like this: