From 96a5dd3b603b5401faac2d6120cc10ddae853542 Mon Sep 17 00:00:00 2001
From: Werner Almesberger <werner@almesberger.net>
Date: Tue, 6 Sep 2011 12:09:56 -0300
Subject: [PATCH] m1/torture/: quick and dirty power-cycling test loop

---
 m1/torture/README | 30 ++++++++++++++++++++++++++++++
 m1/torture/loop   | 17 +++++++++++++++++
 2 files changed, 47 insertions(+)
 create mode 100644 m1/torture/README
 create mode 100755 m1/torture/loop

diff --git a/m1/torture/README b/m1/torture/README
new file mode 100644
index 0000000..5a425dd
--- /dev/null
+++ b/m1/torture/README
@@ -0,0 +1,30 @@
+power-cycling torture test, to see if booting into FN and then
+power-cycling causes NOR corruption.
+
+You need:
+- an M1 with JTAG board
+- a Lab Switch (../../labsw) to control power to the M1
+- a USB connection to the Lab Switch
+- the Lab Switch control tool "labsw" installed
+- a USB connection to the JTAG board
+- UrJTAG installed, see
+  http://milkymist.org/wiki/index.php?title=Flashing_the_Milkymist_One#compile_urjtag
+- neocon from http://svn.openmoko.org/developers/werner/neocon/
+  (or any other program to monitor and log an outbound serial line)
+
+Run
+neocon -a -l log -T /dev/ttyUSB0
+
+Then
+./loop
+
+This will:
+- power-cycle the M1, leaving it powered off for 5 seconds
+- give it two seconds to power on
+- boot the "regular" bitstream, i.e., Flickernoise
+- wait 70 seconds for Flickernoise to start and to render the
+  "The Tunnel" for a few seconds
+- repeat this forever
+
+The log file records the console output from the M1, plus time
+stamps and cycle numbers written from the "loop" script.
diff --git a/m1/torture/loop b/m1/torture/loop
new file mode 100755
index 0000000..b46e9b3
--- /dev/null
+++ b/m1/torture/loop
@@ -0,0 +1,17 @@
+#!/bin/sh
+n=0
+while true; do
+	n=`expr $n + 1`
+	echo ===== $n =====
+
+	labsw ch1=0 ch2=0
+	sleep 5
+	labsw ch1=1 ch2=1
+	sleep 2
+
+	make -C ../jtag-boot boot
+
+	sleep 60
+	echo echo === $n === `date` >/dev/ttyUSB0
+	sleep 10
+done