Facedancer - Revision history

PhilippeTeuwen: /* Raspdancer */

2013-04-26T13:11:16Z

Raspdancer

← Older revision		Revision as of 13:11, 26 April 2013
Line 86:		Line 86:
	==Raspdancer==		==Raspdancer==
	Merging Facedancer & Raspberry Pi		Merging Facedancer & Raspberry Pi
			<br>See dedicated page: [[Raspdancer]]
	===Why?===
	Facedancer11 is a one-purpose version of the flexible GoodFET board.
	<br>It was well designed to move all the intelligence into the host controller, not in the embedded uC.
	<br>Facedancer11 hardware can be seen as:
	USBconn -- FT232RL -- MSP430F2618TPM -- MAX3420E -- USBconn
	where the first two chips are only converting busses:
	USBconn -- FT232RL -- MSP430F2618TPM -- MAX3420E -- USBconn
	USB <> UART <> SPI ... (USB)
	BoM view (excluding taxes, Farnell prices):
	USBconn -- FT232RL -- MSP430F2618TPM -- MAX3420E -- USBconn
	USBconn + 5.45€ + 13.03€ + 8.27€ + USBconn
	So 18.48€ to talk SPI over UART over USB while the Raspberry-Pi has natively SPI, hmmm.
	<br>Bus speed view: yes there is a kind of bottleneck there...
	USBconn -- FT232RL -- MSP430F2618TPM -- MAX3420E -- USBconn
	12MB/s 115200bauds 26MHz
	<br>Let's try to make a RPi extension board with only the MAX3420E.
	<br>And to save a few cents and construction pain let's replace the USB connector by a USB cable from a cannibalized mouse.
	<br>So:
	RPI-MODA-256M -- MAX3420E -- USBcable
	From a BoM point of view this becomes (depending on what you add to the RPi, nice casing etc):
	RPI-MODA-256M -- MAX3420E -- USBcable
	27.66€ + 8.27€
	Bus speed view:
	RPI-MODA-256M -- MAX3420E -- USBcable
	26MHz
	And we get a fully autonomous facedancer which can be even powered over USB and controlled remotely

	===Schematics===
	<pre>
	MAX Signal RPi Signal
	P3 Vcc P17 3v3 \ 0.1uF -- GND
	P4 Vcc P17 3v3 /
	P5 GND P25 GND
	P6 GND P25 GND
	P10 -RES P15 GPIO22
	P11 SCLK P23 SCLK
	P12 -SS P24 CE0
	P13 MISO P21 MISO
	P14 MOSI P19 MOSI
	P17 INT currently not connected, could be e.g. P13=GPIO27
	P18 GND P25 GND
	P19 GND P25 GND ---------- USB conn GND
	P20 D- ----------- R33 -- USB conn D-
	P21 D+ ----------- R33 -- USB conn D+
	P22 Vcc P17 3v3 \ 1uF -- GND
	P23 Vcc P17 3v3 /
	P24 VBCOMP ------------------ USB conn Vcc -- 1uF -- GND
	P26 XI ------------Xtal1- 18pF -- GND
	P27 XO ------------Xtal2- 18pF -- GND
	</pre>
	===First proto===
	[[File:Raspdancer-proto1.jpg\|400px]]
	[[File:Raspdancer-proto1-full.jpg\|400px]]

	===Code===
	Travis did an amazing job at building a Python library and examples for the MAX3420E, let's reuse them!
	<br>You'll need to get [[Raspberry_Pi#GPIO\|GPIO Python support]] and [[Raspberry_Pi#SPI\|SPI Python support]] for your Raspberry Pi.
	<br>From the original facedancer code, you'll need GoodFETMAXUSB.py and the goodfet.maxusb* scripts
	<br>Then instead of the original GoodFET.py library, use [{{#file: GoodFET.py}} this GoodFET.py version]:
	<source lang=python>
	#!/usr/bin/env python
	# (C) 2013 Philippe Teuwen <phil at teuwen.org>

	import spi
	import RPi.GPIO as GPIO

	class GoodFET:
	data=""
	def __init__(self, args, *kargs):
	GPIO.setmode(GPIO.BOARD)
	# pin15=GPIO22 is linked to MAX3420E -Reset
	GPIO.setup(15, GPIO.OUT, initial=GPIO.LOW)
	GPIO.output(15,GPIO.HIGH)
	spi.openSPI(speed=26000000)
	def __del__(self):
	spi.closeSPI()
	GPIO.cleanup()
	def writecmd(self, app, verb, count=0, data=[]):
	if verb: # ignore all but R/W cmd
	return
	if isinstance(data,str):
	data = [ord(x) for x in data]
	data = tuple(data)
	data = spi.transfer(data)
	self.data = "".join([chr(x) for x in data])
	def serInit(self):
	pass
	</source>
	There are probably better ways to integrate it into the GoodFET software stack but with this small code snippet, you can take the latest great GoodFETMAXUSB.py and goodfet.maxusb* python scripts and just drop them along this GoodFET.py, without need for re-applying any patch.

	Note that with the raspdancer, goodfet.maxusbhid is becoming too fast and I'm missing the beginning of the injected string. I had to add some initial "NoEvent / key up" chars ("\x00" * 20) in typestring() in GoodFETMAXUSB.py:
	<source lang=python>
	def typestring(self):
	if self.typestrings.has_key(self.OsLastConfigType):
	return ("\x00" * 20) + self.typestrings[self.OsLastConfigType];
	else:
	return self.typestrings[-1];
	</source>

PhilippeTeuwen: /* Code */

2013-04-26T12:53:21Z

Code

← Older revision		Revision as of 12:53, 26 April 2013
Line 176:		Line 176:
	There are probably better ways to integrate it into the GoodFET software stack but with this small code snippet, you can take the latest great GoodFETMAXUSB.py and goodfet.maxusb* python scripts and just drop them along this GoodFET.py, without need for re-applying any patch.		There are probably better ways to integrate it into the GoodFET software stack but with this small code snippet, you can take the latest great GoodFETMAXUSB.py and goodfet.maxusb* python scripts and just drop them along this GoodFET.py, without need for re-applying any patch.

	Note that goodfet.maxusbhid is becoming ~~a bit~~ too ~~quick~~ and I'm missing the beginning of the injected string. I had to add some initial "NoEvent / key up" chars ("\x00" * 20) in typestring() in GoodFETMAXUSB.py:		Note that with the raspdancer, goodfet.maxusbhid is becoming too fast and I'm missing the beginning of the injected string. I had to add some initial "NoEvent / key up" chars ("\x00" * 20) in typestring() in GoodFETMAXUSB.py:
	<source lang=python>		<source lang=python>
	def typestring(self):		def typestring(self):

PhilippeTeuwen: /* Code */

2013-04-26T12:52:52Z

Code

← Older revision		Revision as of 12:52, 26 April 2013
Line 176:		Line 176:
	There are probably better ways to integrate it into the GoodFET software stack but with this small code snippet, you can take the latest great GoodFETMAXUSB.py and goodfet.maxusb* python scripts and just drop them along this GoodFET.py, without need for re-applying any patch.		There are probably better ways to integrate it into the GoodFET software stack but with this small code snippet, you can take the latest great GoodFETMAXUSB.py and goodfet.maxusb* python scripts and just drop them along this GoodFET.py, without need for re-applying any patch.

	Note that goodfet.maxusbhid is becoming a bit too quick and I'm missing the beginning of the injected string. I had to add some initial "key up" chars ("\x00" * 20) in typestring() in GoodFETMAXUSB.py:		Note that goodfet.maxusbhid is becoming a bit too quick and I'm missing the beginning of the injected string. I had to add some initial "NoEvent / key up" chars ("\x00" * 20) in typestring() in GoodFETMAXUSB.py:
	<source lang=python>		<source lang=python>
	def typestring(self):		def typestring(self):

PhilippeTeuwen: /* Code */

2013-04-26T12:51:55Z

Code

← Older revision		Revision as of 12:51, 26 April 2013
Line 175:		Line 175:
	</source>		</source>
	There are probably better ways to integrate it into the GoodFET software stack but with this small code snippet, you can take the latest great GoodFETMAXUSB.py and goodfet.maxusb* python scripts and just drop them along this GoodFET.py, without need for re-applying any patch.		There are probably better ways to integrate it into the GoodFET software stack but with this small code snippet, you can take the latest great GoodFETMAXUSB.py and goodfet.maxusb* python scripts and just drop them along this GoodFET.py, without need for re-applying any patch.

			Note that goodfet.maxusbhid is becoming a bit too quick and I'm missing the beginning of the injected string. I had to add some initial "key up" chars ("\x00" * 20) in typestring() in GoodFETMAXUSB.py:
			<source lang=python>
			def typestring(self):
			if self.typestrings.has_key(self.OsLastConfigType):
			return ("\x00" * 20) + self.typestrings[self.OsLastConfigType];
			else:
			return self.typestrings[-1];
			</source>

PhilippeTeuwen: /* Code */

2013-04-26T12:38:25Z

Code

← Older revision		Revision as of 12:38, 26 April 2013
Line 162:		Line 162:
	def __del__(self):		def __del__(self):
	spi.closeSPI()		spi.closeSPI()
	GPIO.output(15,GPIO.LOW)
	GPIO.output(15,GPIO.HIGH)
	GPIO.cleanup()		GPIO.cleanup()
	def writecmd(self, app, verb, count=0, data=[]):		def writecmd(self, app, verb, count=0, data=[]):

PhilippeTeuwen: /* First proto */

2013-04-26T12:37:16Z

First proto

← Older revision		Revision as of 12:37, 26 April 2013
Line 137:		Line 137:
	</pre>		</pre>
	===First proto===		===First proto===
			[[File:Raspdancer-proto1.jpg\|400px]]
			[[File:Raspdancer-proto1-full.jpg\|400px]]

	===Code===		===Code===

PhilippeTeuwen: /* Schematics */

2013-04-26T12:32:01Z

Schematics

← Older revision		Revision as of 12:32, 26 April 2013
Line 136:		Line 136:
	P27 XO ------------Xtal2- 18pF -- GND		P27 XO ------------Xtal2- 18pF -- GND
	</pre>		</pre>
			===First proto===

	===Code===		===Code===

PhilippeTeuwen: /* Code */

2013-04-25T23:48:50Z

Code

← Older revision		Revision as of 23:48, 25 April 2013
Line 138:		Line 138:

	===Code===		===Code===
			Travis did an amazing job at building a Python library and examples for the MAX3420E, let's reuse them!
	You'll need to get [[Raspberry_Pi#GPIO\|GPIO Python support]] and [[Raspberry_Pi#SPI\|SPI Python support]] for your Raspberry Pi.		<br>You'll need to get [[Raspberry_Pi#GPIO\|GPIO Python support]] and [[Raspberry_Pi#SPI\|SPI Python support]] for your Raspberry Pi.
⚫	<br>Then ~~just~~ ~~replace~~ the GoodFET.py library by [{{#file: GoodFET.py}} this GoodFET.py]:
			<br>From the original facedancer code, you'll need GoodFETMAXUSB.py and the goodfet.maxusb* scripts
		⚫	<br>Then instead of the original GoodFET.py library, use [{{#file: GoodFET.py}} this GoodFET.py version]:
	<source lang=python>		<source lang=python>
	#!/usr/bin/env python		#!/usr/bin/env python
Line 151:		Line 153:
	def __init__(self, args, *kargs):		def __init__(self, args, *kargs):
	GPIO.setmode(GPIO.BOARD)		GPIO.setmode(GPIO.BOARD)
	# pin15=GPIO22 is linked to ~~MAX3420~~ -~~RST~~		# pin15=GPIO22 is linked to MAX3420E -Reset
	GPIO.setup(15, GPIO.OUT, initial=GPIO.LOW)		GPIO.setup(15, GPIO.OUT, initial=GPIO.LOW)
	GPIO.output(15,GPIO.HIGH)		GPIO.output(15,GPIO.HIGH)
Line 171:		Line 173:
	pass		pass
	</source>		</source>
	There are probably better ways to integrate it into the GoodFET software stack but with this small code snippet, you can take the latest great maxusb python scripts and just drop them along this GoodFET.py, without need for re-applying any patch.		There are probably better ways to integrate it into the GoodFET software stack but with this small code snippet, you can take the latest great GoodFETMAXUSB.py and goodfet.maxusb* python scripts and just drop them along this GoodFET.py, without need for re-applying any patch.

PhilippeTeuwen: /* Merging Facedancer & R-Pi */

2013-04-25T23:41:46Z

Merging Facedancer & R-Pi

← Older revision		Revision as of 23:41, 25 April 2013
Line 84:		Line 84:
	==Scapy support==		==Scapy support==
	http://rmspeers.com/archives/252		http://rmspeers.com/archives/252
			==Raspdancer==
	==Merging Facedancer & R-Pi==		Merging Facedancer & Raspberry Pi
	===Why?===		===Why?===
	Facedancer11 is a one-purpose version of the flexible GoodFET board.		Facedancer11 is a one-purpose version of the flexible GoodFET board.

PhilippeTeuwen at 23:40, 25 April 2013

2013-04-25T23:40:44Z

← Older revision		Revision as of 23:40, 25 April 2013
Line 5:		Line 5:
	* http://goodfet.sourceforge.net/hardware/facedancer11/		* http://goodfet.sourceforge.net/hardware/facedancer11/
	* http://goodfet.sourceforge.net/tutorial/		* http://goodfet.sourceforge.net/tutorial/
			==Making==
			I met Travis at Troopers2013 and he was very kind of giving me one Facedancer11 PCB.
			<br>I soldered the elements by reflow with solder paste in a kitchen pan, on a cooking paper and with good ventilation.
	==Installation==		==Installation==
	<source lang=bash>		<source lang=bash>