15 Commits

Author	SHA1	Message	Date
Werner Almesberger	a80b77de72	m1rc3/norruption/LOG: got a multiple hit	2011-09-18 00:36:45 -03:00
Werner Almesberger	a624fbebc5	m1rc3/norruption/LOG: latest results	2011-09-17 02:32:21 -03:00
Werner Almesberger	0a605c85f9	m1rc3/norruption/peek: new tool to quickly check for corruption at low addresses	2011-09-15 20:18:44 -03:00
Werner Almesberger	88fa76bc88	m1rc3/norruption/LOG: finally got one more	2011-09-15 04:05:40 -03:00
Werner Almesberger	1a2d591947	m1rc3/norruption/LOG: finally got one more corruption	2011-09-13 01:01:47 -03:00
Werner Almesberger	50d66bfdea	m1rc3/norruption/LOG: still trying to reproduce the NOR corruption ...	2011-09-12 20:17:32 -03:00
Werner Almesberger	165d799b17	m1rc3/norruption/LOG: latest result (showing failure to reproduce NOR corruption)	2011-09-11 12:42:11 -03:00
Werner Almesberger	2310466805	m1rc3/norruption/: update of on-going testing; new test loop7 simulating "false start"	2011-09-10 16:33:18 -03:00
Werner Almesberger	db7ae94e64	m1rc3/norruption/: loop5 test: cut power while in standby	2011-09-09 11:07:06 -03:00
Werner Almesberger	2e3553d458	m1rc3/norruption/LOG: NOR corruption not observed without power-cycling	2011-09-08 20:06:58 -03:00
Werner Almesberger	852210cdfa	m1rc3/norruption/: next round of tests, just resetting without power-cycling	2011-09-08 19:07:18 -03:00
Werner Almesberger	b65ca3f49f	m1rc3/norruption/LOG: added results of last (long) test run	2011-09-08 08:34:40 -03:00
Werner Almesberger	37df000637	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.	2011-09-07 09:20:37 -03:00
Werner Almesberger	ed286e6982	m1rc3/norruption/loop2: shorter loop (17 s instead of 77 s) that cycles in RTEMS boot, without rendering	2011-09-07 05:12:03 -03:00
Werner Almesberger	757f19cd7b	moved m1/torture/ to more specific m1rc3/norruption/	2011-09-07 04:23:32 -03:00