moved m1/torture/ to more specific m1rc3/norruption/

m1/torture/LOG

@@ -1,61 +0,0 @@
---- Tue 2011-09-06 ------------------------------------------------------------
-
-1: started around 11:53 (M1 configuration is original, without locking)
-(around 500) visually checked boot process; standby was reached normally
-
---- Wed 2011-09-07 ------------------------------------------------------------
-
-645: neocon stopped working (around 01:58)
-666: detected neocon failure at run 666: restarted neocon; urjtag failed
-     this cycle; back to normal at 667
-684: checked LEDs again (first time since ~500) and found that standby
-     may be failing. stopping test at 685 (around 02:50) for
-     investigation.
-
-Downloaded the standby bitstream:
-
-  wget https://raw.github.com/milkymist/scripts/master/scripts/reflash_m1.sh
-  chmod 755 reflash_m1.sh
-
-  ./reflash_m1.sh --read-flash
-
-Found two corruptions in the standby bitstream:
-
-  diff -u <(hexdump -C standby.fpg) <(hexdump -C /home/root/.qi/milkymist/read-flash/2011...)
-
--00000080  00 00 4c 83 00 00 4c 87  00 00 cc 85 d8 47 cc 43  |..L...L......G.C|
-+00000080  00 00 4c 83 00 00 4c 87  00 00 c4 80 d8 47 cc 43  |..L...L......G.C|
-
--00002840  00 08 cc 26 00 00 00 00  00 00 00 00 0c 44 00 98  |...&.........D..|
-+00002840  00 00 cc 26 00 00 00 00  00 00 00 00 0c 44 00 98  |...&.........D..|
-
-CRC-checked the partitions:
-
-  git clone git://github.com/milkymist/milkymist
-  cd milkymist/tools/
-  gcc -Wall -I. -o flterm flterm.c
-  wget http://milkymist.org/updates/current/for-rc3/boot.4e53273.bin
-  ./flterm --port /dev/ttyUSB0 --kernel boot.4e53273.bin
-
-  only standby.fpg failed the CRC check
-
-Reflashed the standby bitstream:
-
-  wget http://milkymist.org/updates/2011-07-13/for-rc3/fjmem.bit
-  (or http://milkymist.org/updates/fjmem.bit.bz2)
-  wget http://milkymist.org/updates/current/standby.fpg
-
-  jtag
-
-  cable milkymist
-  detect
-  instruction CFG_OUT  000100 BYPASS
-  instruction CFG_IN   000101 BYPASS
-  pld load fjmem.bit
-  initbus fjmem opcode=000010
-  frequency 6000000
-  detectflash 0
-  endian big
-  flashmem 0 standby.fpg noverify
-
-M1 enters standby normally again.

m1/torture/README

@@ -1,30 +0,0 @@
-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.

m1/torture/loop

@@ -1,17 +0,0 @@
-#!/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