m1rc3/norruption/LOG: cycling in RTEMS boot is sufficient to trigger corruption

I.e., it's not necessary that FN be up or even rendering. Note that
all is was still without NOR locking.

m1rc3/norruption/LOG

@@ -1,5 +1,13 @@
 --- Tue 2011-09-06 ------------------------------------------------------------
 
+Running "loop": power-cycle, sleep 2 s, jtag-boot, sleep 70 seconds,
+which is enough to boot into FN and render "The Tunnel" for a moment,
+then power-cycle again (off-time is 5 s).
+
+Note that the test loop is "open-loop" and will cycle also past any
+problems. The first time a corrupt standby (or any other issue) is
+observed may therefore be well after the actual event.
+
 1: started around 11:53 (M1 configuration is original, without locking)
 (around 500) visually checked boot process; standby was reached normally
 
@@ -37,6 +45,9 @@ CRC-checked the partitions:
   wget http://milkymist.org/updates/current/for-rc3/boot.4e53273.bin
   ./flterm --port /dev/ttyUSB0 --kernel boot.4e53273.bin
 
+  serialboot
+  a
+
   only standby.fpg failed the CRC check
 
 Reflashed the standby bitstream:
@@ -59,3 +70,22 @@ Reflashed the standby bitstream:
   flashmem 0 standby.fpg noverify
 
 M1 enters standby normally again.
+
+Running "loop2": power-cycle, sleep 2 s, jtag-boot, sleep 10 seconds,
+which is enough to begin (but not finish) booting RTEMS, then
+power-cycle again (off-time is 5 s).
+
+1: started around 05:01. Observed until about 200-300 (06:00-06:30)
+that standby was okay.
+~730 (08:48): observed that standby didn't load anymore (note: due to
+a bug in labsw, power is not turned on in about 5-10% of the cycles,
+so the real cycle count should be around 650-700.)
+
+Standby bitstream difference:
+
+-00000080  00 00 4c 83 00 00 4c 87  00 00 cc 85 d8 47 cc 43  |..L...L......G.C|
++00000080  00 00 00 00 00 00 4c 87  00 00 cc 85 d8 47 cc 43  |......L......G.C|
+
+Reflashed standby and locked the NOR. Testing with loop2 again.
+
+1 (09:18): started