diff --git a/prod/doc/analysis.html b/prod/doc/analysis.html
new file mode 100644
index 0000000..149753c
--- /dev/null
+++ b/prod/doc/analysis.html
@@ -0,0 +1,86 @@
+Production and testing: Fault analysis
+
+
+Production and testing: Fault analysis
+
+
+
+
+
+Component placement and orientation
+
+
+
+
+Supply voltages
+
+
+
+
+Clock frequency
+
+The flawless performance of the crystal oscillator is crucial for
+operation. Anomalies are easy to detect with even a low-cost oscilloscope
+and pinpoint specific problems and help to select further analysis steps.
+
+The crystal used in atben and atusb has a nominal tolerance
+of +/- 15 ppm at 22-28 C. Low-cost oscilloscopes typically have a timing
+accuracy of
++/- 100 ppm, which means that only major excursions can be detected by
+measuring the clock output with such an instrument. Full-speed USB only
+requires an accuracy of +/- 2500 ppm.
+We can therefore consider all results within a range of +/- 1000 ppm as
+sufficient, and perform more precise measurements by other means. This
+applies to atben as well as to atusb.
+
+
+
+
Measuring the clock on atben
+
+atben normally does not output a clock signal. A 1 MHz clock
+can be enabled with the following command:
+
+atrf-txrx -d net:ben -C 1
+
+This configures atben as a promiscuous receiver. The reception
+of any IEEE 802.15.4 frame or pressing Ctrl-C will terminate the command.
+
+
+| Clock | Action
+ |
|---|
| 0 Hz | Check voltages; check that the clock is enabled;
+ check for shorts around crystal; check connectivity of crystal
+ |
| 0.999-1.001 MHz, ~3.3 Vpp | Perform precision measurement with
+ atrf-xtal
+ |
| Other | Check voltages; check for contamination around crystal
+ |
+
+
+
+
Measuring the clock on atusb
+
+The transceiver provides the clock for the microcontroller in atusb.
+A clock signal is therefore always available. Immediately after reset,
+the transceiver generates a 1 MHz clock. When the microcontrolled comes out
+of reset, it raises the transceiver's clock output to 8 MHz and then
+enables USB.
+
+
+| Clock | Action
+ |
|---|
| 0 Hz | Check voltages; check for shorts around crystal; check
+ connectivity of crystal
+ |
| 0.999-1.001 MHz, ~3.3 Vpp | Check presence of firmware; check for
+ shorts on SPI signals; check connectivity of SPI signals
+ |
| 7.992-8.008 MHz, ~3.3 Vpp | Perform precision measurement with
+ atrf-xtal
+ |
| Other | Check voltages; check for contamination around crystal
+ |
+
+
+Precision measurements
+
+
+
+Last update: 2011-05-18 Werner Almesberger
+
+
+
diff --git a/prod/doc/flash.html b/prod/doc/flash.html
new file mode 100644
index 0000000..4a06351
--- /dev/null
+++ b/prod/doc/flash.html
@@ -0,0 +1,33 @@
+Production and testing: Flashing
+
+
+Production and testing: Flashing
+
+
+(atusb only)
+
+
+
+
+Flashing the boot loader
+
+
+
+
+
+
+
+
+
+
Flashing the application
+
+
+
+
+
+
+
+Last update: 2011-05-18 Werner Almesberger
+
+
+
diff --git a/prod/doc/index.html b/prod/doc/index.html
index 6c99fc1..28b67ec 100644
--- a/prod/doc/index.html
+++ b/prod/doc/index.html
@@ -79,251 +79,18 @@ Defective devices can be discarded or retained for a deeper analysis.
-Software setup
+Detailed description
-Before performing any production tests, various pieces of software
-need to be installed on Ben and PC, and configuration settings
-@@@
+The following pages describe the preparation and the execution of the
+production and test process:
+
-
-
-
-PC software installation
-
-@@@
-
-Install ben-wpan tools
-
-@@@
-
-Register Ben host name
-
-To simplify accessing the Ben via TCP/IP, its IP address should be
-registered in the hosts file on the PC. If the Ben is running OpenWrt,
-use the following command:
-
-echo 192.168.254.101 ben >>/etc/hosts
-
-
-If the Ben is running Jlime, the address would be as follows:
-
-echo 192.168.1.202 ben >>/etc/hosts
-
-
-If using the same PC with Bens running OpenWrt and Jlime, one may choose
-different host names depending on the distribution, and adapt the commands
-used in the production and testing process accordingly. For example,
-
-echo 192.168.254.101 ben >>/etc/hosts
-echo 192.168.1.202 jlime >>/etc/hosts
-
-
-
-
-
-
-Ben system setup
-
-The configuration setting described in this section are lost on each
-reset or reboot and either need to be entered again or a setup script
-running at boot time has to
-This needs to be done each time the Ben is booted.
-
-
-Enable network access
-
-Once the Ben has booted and started USB networking, the interface
-on the PC side is configured as follows:
-
-ifconfig usb0 192.168.254.100 up
-
-
-These are the settings for OpenWrt, assuming the network device is
-called "usb0". If using Jlime, the command would be as follows:
-
-ifconfig usb0 192.168.1.200 up
-
-
-
-Silence other 8:10 card users
-
-Before running any of the ben-wpan utilities, other users of the 8:10
-card slot have to be disabled. In a Ben running the regular OpenWrt or
-Jlime distribution, the only such user that is automatically started
-is the MMC kernel driver. The following command disables it:
-
-echo jz4740-mmc.0 >/sys/bus/platform/drivers/jz4740-mmc/unbind
-
-
-If a WPAN-enabled kernel has been installed, the AT86RF230 driver takes
-the place of the MMC driver. To disable it, run
-
-echo spi2.0 >/sys/bus/spi/drivers/at86rf230/unbind
-
-
-
-Start atrf-proxy
-
-On the Ben, launch the proxy daemon. We pass the option -b to background it:
-
-atrf-proxy -b
-
-
-
-
-
-
-Ben software installation
-
-Password-less remote access
-
-To enable password-less remote access from the PC, setup to betwork
-access to the Ben and run the following command:
-
-ssh ben 'cat >>/etc/dropbear/authorized_keys' <~/.ssh/id_rsa.pub
-
-
-
-
-
-
-Test profiles
-
-
-
-
-
-Flashing (atusb only)
-
-
-
-
-Flashing the boot loader
-
-
-
-
-
-
-
-
-
-
Flashing the application
-
-
-
-
-
-
-
-
-
-
Functional test
-
-
-
-
-Test setup for atben
-
-
-
-
-
-
-
-
-
Test setup for atusb
-
-
-
-
-
-
-
-
-
Test procedure
-
-
-
-
-
-Fault analysis
-
-
-
-
-Component placement and orientation
-
-
-
-
-Supply voltages
-
-
-
-
-Clock frequency
-
-The flawless performance of the crystal oscillator is crucial for
-operation. Anomalies are easy to detect with even a low-cost oscilloscope
-and pinpoint specific problems and help to select further analysis steps.
-
-The crystal used in atben and atusb has a nominal tolerance
-of +/- 15 ppm at 22-28 C. Low-cost oscilloscopes typically have a timing
-accuracy of
-+/- 100 ppm, which means that only major excursions can be detected by
-measuring the clock output with such an instrument. Full-speed USB only
-requires an accuracy of +/- 2500 ppm.
-We can therefore consider all results within a range of +/- 1000 ppm as
-sufficient, and perform more precise measurements by other means. This
-applies to atben as well as to atusb.
-
-
-
-
Measuring the clock on atben
-
-atben normally does not output a clock signal. A 1 MHz clock
-can be enabled with the following command:
-
-atrf-txrx -d net:ben -C 1
-
-This configures atben as a promiscuous receiver. The reception
-of any IEEE 802.15.4 frame or pressing Ctrl-C will terminate the command.
-
-
-| Clock | Action
- |
|---|
| 0 Hz | Check voltages; check that the clock is enabled;
- check for shorts around crystal; check connectivity of crystal
- |
| 0.999-1.001 MHz, ~3.3 Vpp | Perform precision measurement with
- atrf-xtal
- |
| Other | Check voltages; check for contamination around crystal
- |
-
-
-
-
Measuring the clock on atusb
-
-The transceiver provides the clock for the microcontroller in atusb.
-A clock signal is therefore always available. Immediately after reset,
-the transceiver generates a 1 MHz clock. When the microcontrolled comes out
-of reset, it raises the transceiver's clock output to 8 MHz and then
-enables USB.
-
-
-| Clock | Action
- |
|---|
| 0 Hz | Check voltages; check for shorts around crystal; check
- connectivity of crystal
- |
| 0.999-1.001 MHz, ~3.3 Vpp | Check presence of firmware; check for
- shorts on SPI signals; check connectivity of SPI signals
- |
| 7.992-8.008 MHz, ~3.3 Vpp | Perform precision measurement with
- atrf-xtal
- |
| Other | Check voltages; check for contamination around crystal
- |
-
-
-Precision measurements
-
Last update: 2011-05-18 Werner Almesberger
diff --git a/prod/doc/setup.html b/prod/doc/setup.html
new file mode 100644
index 0000000..f06514e
--- /dev/null
+++ b/prod/doc/setup.html
@@ -0,0 +1,121 @@
+Production and testing: Software setup
+
+
+Production and testing: Software setup
+
+Before performing any production tests, various pieces of software
+need to be installed on Ben and PC, and configuration settings
+@@@
+
+
+
+
+
+PC software installation
+
+@@@
+
+Install ben-wpan tools
+
+@@@
+
+Register Ben host name
+
+To simplify accessing the Ben via TCP/IP, its IP address should be
+registered in the hosts file on the PC. If the Ben is running OpenWrt,
+use the following command:
+
+echo 192.168.254.101 ben >>/etc/hosts
+
+
+If the Ben is running Jlime, the address would be as follows:
+
+echo 192.168.1.202 ben >>/etc/hosts
+
+
+If using the same PC with Bens running OpenWrt and Jlime, one may choose
+different host names depending on the distribution, and adapt the commands
+used in the production and testing process accordingly. For example,
+
+echo 192.168.254.101 ben >>/etc/hosts
+echo 192.168.1.202 jlime >>/etc/hosts
+
+
+
+
+
+
+Ben system setup
+
+The configuration setting described in this section are lost on each
+reset or reboot and either need to be entered again or a setup script
+running at boot time has to
+This needs to be done each time the Ben is booted.
+
+
+Enable network access
+
+Once the Ben has booted and started USB networking, the interface
+on the PC side is configured as follows:
+
+ifconfig usb0 192.168.254.100 up
+
+
+These are the settings for OpenWrt, assuming the network device is
+called "usb0". If using Jlime, the command would be as follows:
+
+ifconfig usb0 192.168.1.200 up
+
+
+
+Silence other 8:10 card users
+
+Before running any of the ben-wpan utilities, other users of the 8:10
+card slot have to be disabled. In a Ben running the regular OpenWrt or
+Jlime distribution, the only such user that is automatically started
+is the MMC kernel driver. The following command disables it:
+
+echo jz4740-mmc.0 >/sys/bus/platform/drivers/jz4740-mmc/unbind
+
+
+If a WPAN-enabled kernel has been installed, the AT86RF230 driver takes
+the place of the MMC driver. To disable it, run
+
+echo spi2.0 >/sys/bus/spi/drivers/at86rf230/unbind
+
+
+
+Start atrf-proxy
+
+On the Ben, launch the proxy daemon. We pass the option -b to background it:
+
+atrf-proxy -b
+
+
+
+
+
+
+Ben software installation
+
+Password-less remote access
+
+To enable password-less remote access from the PC, setup to betwork
+access to the Ben and run the following command:
+
+ssh ben 'cat >>/etc/dropbear/authorized_keys' <~/.ssh/id_rsa.pub
+
+
+
+
+
+
+Test profiles
+
+
+
+
+Last update: 2011-05-18 Werner Almesberger
+
+
+
diff --git a/prod/doc/test.html b/prod/doc/test.html
new file mode 100644
index 0000000..d7dfb0c
--- /dev/null
+++ b/prod/doc/test.html
@@ -0,0 +1,36 @@
+Production and testing: Functional test
+
+
+Production and testing: Functional test
+
+
+
+
+
+Test setup for atben
+
+
+
+
+
+
+
+
+
Test setup for atusb
+
+
+
+
+
+
+
+
+
Test procedure
+
+
+
+
+Last update: 2011-05-18 Werner Almesberger
+
+
+