m1rc3/norruption/: next round of tests, just resetting without power-cycling

m1rc3/norruption/LOG

@@ -130,3 +130,16 @@ Compare with the original:
 -0008a380  28 43 00 00 34 64 00 01  58 44 00 00 5c 60 00 1e  |(C..4d..XD..\`..|
 +0008a380  28 43 00 00 00 00 00 01  58 44 00 00 5c 60 00 1e  |(C......XD..\`..|
 ...
+
+Recovered the FN partition and unlocked the NOR:
+
+  flashmem 0x920000 flickernoise.fbi noverify
+  unlockflash 0 55
+
+New test series with script loop4. This differs from loop2 in that
+it uses "pld reconfigure" to return to standby, instead of
+power-cycling. If we still observe corruption with this test, then
+a software problem would be to blame.
+
+1 (09:11): started
+2403 (19:07): standby still looks good

m1rc3/norruption/README

@@ -28,3 +28,12 @@ This will:
 
 The log file records the console output from the M1, plus time
 stamps and cycle numbers written from the "loop" script.
+
+Update: there's another test, loop2, which performs a shorter loop,
+which still produces corruption.
+
+Update: loop4 does the same as loop2, but uses "pld reconfigure" instead
+of power-cycling. Since loop2 was used for a test run #2 (NOR unlocked)
+and a test run #3 (first 55 pages of NOR locked), there is no loop3
+script.
+

m1rc3/norruption/loop4

@@ -0,0 +1,26 @@
+#!/bin/sh
+
+reset()
+{
+	jtag <<EOF
+cable milkymist
+detect
+instruction CFG_OUT 000100 BYPASS
+instruction CFG_IN 000101 BYPASS
+pld reconfigure
+EOF
+}
+n=0
+while true; do
+	n=`expr $n + 1`
+	echo ===== $n =====
+
+	reset
+	sleep 2
+
+	make -C ../../m1/jtag-boot boot
+
+	sleep 8
+	echo echo === $n === `date` >/dev/ttyUSB0
+	sleep 2
+done