diff --git a/prod/doc/flash.html b/prod/doc/flash.hmac similarity index 73% rename from prod/doc/flash.html rename to prod/doc/flash.hmac index a140d56..9f21afc 100644 --- a/prod/doc/flash.html +++ b/prod/doc/flash.hmac @@ -1,7 +1,22 @@ -Production and testing: Flashing - + -

Production and testing: Flashing

+Production and testing: Flashing + + + + + + Software setup + Flashing + Functional test + Fault analysis + + + + Boot loader + Application + +

The microcontroller of atusb contains firmware that must be loaded before the testing process can commence. The firmware consists @@ -18,7 +33,7 @@ any flashing. -

Flashing the boot loader

+
The following image shows the setup for flashing the boot loader:

@@ -51,7 +66,7 @@ If flashing fails despite numerous attempts, proceed to the -

Flashing the application

+
The flashing script proceeds automatically to the flashing of the application. All you need to do is insert the atusb board @@ -69,11 +84,7 @@ If the board fails to enumerate, proceed with the

-Up: Production and testing  -Prev: Software setup -Next: Functional test  -
-Last update: 2011-05-26  Werner Almesberger +Last update: 2011-05-27  Werner Almesberger
diff --git a/prod/doc/setup.html b/prod/doc/setup.hmac similarity index 79% rename from prod/doc/setup.html rename to prod/doc/setup.hmac index e31be38..0eb0eb5 100644 --- a/prod/doc/setup.html +++ b/prod/doc/setup.hmac @@ -1,7 +1,25 @@ -Production and testing: Software setup - + -

Production and testing: Software setup

+Production and testing: Software setup + + + + + + Software setup + Flashing + Functional test + Fault analysis + + + + PC software + Ben software + Ben system + Test profiles + + +

Before performing any production tests, various pieces of software need to be installed on Ben and PC, and configuration settings @@ -11,7 +29,7 @@ need to be installed on Ben and PC, and configuration settings -

PC software installation

+
@@@ @@ -19,7 +37,7 @@ need to be installed on Ben and PC, and configuration settings -

Install ben-wpan tools

+ @@@ @@ -27,7 +45,7 @@ need to be installed on Ben and PC, and configuration settings -

Install test scripts

+ @@@ @@ -35,7 +53,7 @@ need to be installed on Ben and PC, and configuration settings -

Install firmware binary

+ The binary of the application running on atusb is transferred from the PC. To download a pre-compiled version, use this command: @@ -52,7 +70,7 @@ Instructions for building the binary from sources are -

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, @@ -78,7 +96,7 @@ echo 192.168.1.202 jlime >>/etc/hosts -

Customize test scripts

+ @@@ @@ -86,7 +104,7 @@ echo 192.168.1.202 jlime >>/etc/hosts -

Ben software installation

+
@@@ @@ -94,7 +112,7 @@ echo 192.168.1.202 jlime >>/etc/hosts -

Password-less remote access

+ To enable password-less remote access from the PC, set up network access to the Ben and run the following command: @@ -106,7 +124,7 @@ ssh ben 'cat >>/etc/dropbear/authorized_keys' <~/.ssh/id_rsa.pub -

Install ben-wpan tools

+ @@@ @@ -114,7 +132,7 @@ ssh ben 'cat >>/etc/dropbear/authorized_keys' <~/.ssh/id_rsa.pub -

Install avrdude

+ The atusb boot loader is flashed using avrdude. A pre-compiled static binary (suitable for OpenWrt and Jlime) can be installed by running @@ -134,7 +152,7 @@ Instructions for building avrdude from sources are -

Install boot-loader binary

+ The binary of the boot loader running on atusb is transferred from the Ben. To download a pre-compiled version, use this command: @@ -151,7 +169,7 @@ Instructions for building the binary from sources are -

Ben system setup

+
The configuration setting described in this section are lost on each reset or reboot and either need to be entered again. Alternatively, @@ -161,7 +179,7 @@ a setup script running at boot time can be written. -

Enable network access

+ Once the Ben has booted and started USB networking, the interface on the PC side is configured as follows: @@ -179,7 +197,7 @@ 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 @@ -199,7 +217,7 @@ 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: 
@@ -210,7 +228,7 @@ atrf-proxy -b
 
 
 
-
Test profiles

+

 
 Some of the functional tests measure characteristics that are strongly
 influenced by the test setup. It is therefore not possible to provide
@@ -221,7 +239,7 @@ in the actual test environment.
 
 
 
-
Clock count (atben only)

+
 
 Insert a known to be good atben board and run the following
 command directly on the Ben to record the reference value for the
@@ -241,17 +259,14 @@ Ben, and if a stable temperature is maintained.
 
 
 
-
Signal strength

+
 
 @@@
 
 
 

 

-Up: Production and testing 
-Next: Flashing (atusb only) 
-

-Last update: 2011-05-19  Werner Almesberger
+Last update: 2011-05-27  Werner Almesberger
 

 
 
diff --git a/prod/doc/test.html b/prod/doc/test.hmac
similarity index 83%
rename from prod/doc/test.html
rename to prod/doc/test.hmac
index f50ab8e..628d0a8 100644
--- a/prod/doc/test.html
+++ b/prod/doc/test.hmac
@@ -1,13 +1,28 @@
-Production and testing: Functional test
-
+
 
-
Production and testing: Functional test

+Production and testing: Functional test
+
+
+
+
+
+  Software setup
+  Flashing
+  Functional test
+  Fault analysis
+
+
+
+  atben setup
+  atusb setup
+  Test procedure
+
 
 
 
 
 
-
Test setup for atben

+

 
 To test an atben board, place a reference atusb board into
 the PC, insert the
@@ -19,7 +34,7 @@ the PC, insert the
 
 
 
-
Test setup for atusb

+

 
 

 
@@ -29,7 +44,7 @@ the PC, insert the
 
 
 
-
Test procedure

+

 
 The test process is started with
 
@@ -61,7 +76,7 @@ file _log.
 
 
 
-
Enumeration (atusb only)

+
 
 The enumeration test verifies that the atusb board has been
 identified by the PC's USB stack. If this test fails, the board may
@@ -73,7 +88,7 @@ should always pass the enumeration test.
 
 
 
-
LED (atusb only)

+
 
 @@@
 
@@ -81,7 +96,7 @@ should always pass the enumeration test.
 
 
 
-
GPIO scan

+
 
 @@@
 
@@ -89,7 +104,7 @@ should always pass the enumeration test.
 
 
 
-
Identification

+
 
 This test reads the transceiver's registers that contain values identifying
 the manufacturer, the chip's part number, and the chip revision. If an
@@ -109,7 +124,7 @@ eventually provide more detailed results for problems with the SPI interface.
 
 
 
-
Crystal frequency (atben only)

+
 
 This test measures the frequency of the crystal oscillator in the DUT.
 On atben, it does this by transmitting packets, and measuring
@@ -128,7 +143,7 @@ testing the crystal oscillator.
 
 
 
-
Spectrum

+
 
 The spectrum test measures the reception of a signal sent from the
 reference device to the DUT. It does this across the entire frequency
@@ -162,7 +177,7 @@ and can only be entered if the measurements is outside the limits.
 
 
 
-
Receive

+
 
 In the receive test, the reference device sends a number of frames to the
 DUT. The test program verifies correct reception of all the frames. A
@@ -174,7 +189,7 @@ the bypassing of the transceiver's 1.8 V supplies.
 
 
 
-
Send

+
 
 The send test is like the receive test, but with the DUT acting as the
 sender and the reference acting as the receiver. If a device passes the
@@ -187,11 +202,7 @@ remain undetected until the send test.
 
 

 

-Up: Production and testing 
-Prev: Flashing (atusb only) 
-Next: Fault analysis 
-

-Last update: 2011-05-26  Werner Almesberger
+Last update: 2011-05-27  Werner Almesberger