Root/m1rc3/norruption/README

Source at commit 852210cdfa0b62e85df9c7aa4ca0195ff93f19d6 created 8 years 5 months ago.
By Werner Almesberger, m1rc3/norruption/: next round of tests, just resetting without power-cycling
1power-cycling torture test, to see if booting into FN and then
2power-cycling causes NOR corruption.
3
4You need:
5- an M1 with JTAG board
6- a Lab Switch (../../labsw) to control power to the M1
7- a USB connection to the Lab Switch
8- the Lab Switch control tool "labsw" installed
9- a USB connection to the JTAG board
10- UrJTAG installed, see
11  http://milkymist.org/wiki/index.php?title=Flashing_the_Milkymist_One#compile_urjtag
12- neocon from http://svn.openmoko.org/developers/werner/neocon/
13  (or any other program to monitor and log an outbound serial line)
14
15Run
16neocon -a -l log -T /dev/ttyUSB0
17
18Then
19./loop
20
21This will:
22- power-cycle the M1, leaving it powered off for 5 seconds
23- give it two seconds to power on
24- boot the "regular" bitstream, i.e., Flickernoise
25- wait 70 seconds for Flickernoise to start and to render the
26  "The Tunnel" for a few seconds
27- repeat this forever
28
29The log file records the console output from the M1, plus time
30stamps and cycle numbers written from the "loop" script.
31
32Update: there's another test, loop2, which performs a shorter loop,
33which still produces corruption.
34
35Update: loop4 does the same as loop2, but uses "pld reconfigure" instead
36of power-cycling. Since loop2 was used for a test run #2 (NOR unlocked)
37and a test run #3 (first 55 pages of NOR locked), there is no loop3
38script.
39
40

Archive Download this file

Branches:
master



interactive