Date:2011-05-18 19:25:54 (12 years 10 months ago)
Author:Werner Almesberger
Commit:e11d7b15cc3ab1b6343402371da84a20532e93be
Message:prod/doc/index.html: split into one file per topic

Files: prod/doc/analysis.html (1 diff)
prod/doc/flash.html (1 diff)
prod/doc/index.html (1 diff)
prod/doc/setup.html (1 diff)
prod/doc/test.html (1 diff)

Change Details

prod/doc/analysis.html
1<TITLE>Production and testing: Fault analysis</TITLE>
2<BODY>
3<HTML>
4<H1>Production and testing: Fault analysis</H1>
5
6
7<!-- ---------------------------------------------------------------------- -->
8
9
10<H3>Component placement and orientation</H3>
11
12<!-- ---------------------------------------------------------------------- -->
13
14
15<H3>Supply voltages</H3>
16
17<!-- ---------------------------------------------------------------------- -->
18
19
20<H3>Clock frequency</H3>
21
22The flawless performance of the crystal oscillator is crucial for
23operation. Anomalies are easy to detect with even a low-cost oscilloscope
24and pinpoint specific problems and help to select further analysis steps.
25<P>
26The crystal used in <B>atben</B> and <B>atusb</B> has a nominal tolerance
27of +/- 15 ppm at 22-28 C. Low-cost oscilloscopes typically have a timing
28accuracy of
29+/- 100 ppm, which means that only major excursions can be detected by
30measuring the clock output with such an instrument. Full-speed USB only
31requires an accuracy of +/- 2500 ppm.
32We can therefore consider all results within a range of +/- 1000 ppm as
33sufficient, and perform more precise measurements by other means. This
34applies to <B>atben</B> as well as to <B>atusb</B>.
35<P>
36
37
38<H4>Measuring the clock on atben</H4>
39
40<B>atben</B> normally does not output a clock signal. A 1 MHz clock
41can be enabled with the following command:
42<PRE>
43atrf-txrx -d net:ben -C 1
44</PRE>
45This configures <B>atben</B> as a promiscuous receiver. The reception
46of any IEEE 802.15.4 frame or pressing Ctrl-C will terminate the command.
47<P>
48<TABLE>
49<TR><TH align="left">Clock<TH align="left">Action
50<TR><TD>0 Hz<TD>Check voltages; check that the clock is enabled;
51  check for shorts around crystal; check connectivity of crystal
52<TR><TD>0.999-1.001 MHz, ~3.3 Vpp<TD>Perform precision measurement with
53  <B>atrf-xtal</B>
54<TR><TD>Other<TD>Check voltages; check for contamination around crystal
55</TABLE>
56<P>
57
58
59<H4>Measuring the clock on atusb</H4>
60
61The transceiver provides the clock for the microcontroller in <B>atusb</B>.
62A clock signal is therefore always available. Immediately after reset,
63the transceiver generates a 1 MHz clock. When the microcontrolled comes out
64of reset, it raises the transceiver's clock output to 8 MHz and then
65enables USB.
66<P>
67<TABLE>
68<TR><TH align="left">Clock<TH align="left">Action
69<TR><TD>0 Hz<TD>Check voltages; check for shorts around crystal; check
70  connectivity of crystal
71<TR><TD>0.999-1.001 MHz, ~3.3 Vpp<TD>Check presence of firmware; check for
72  shorts on SPI signals; check connectivity of SPI signals
73<TR><TD>7.992-8.008 MHz, ~3.3 Vpp<TD>Perform precision measurement with
74  <B>atrf-xtal</B>
75<TR><TD>Other<TD>Check voltages; check for contamination around crystal
76</TABLE>
77
78
79<H4>Precision measurements</H4>
80
81<P>
82<HR>
83Last update: 2011-05-18&nbsp;&nbsp;<I>Werner Almesberger</I>
84<HR>
85</BODY>
86</HTML>
prod/doc/flash.html
1<TITLE>Production and testing: Flashing</TITLE>
2<BODY>
3<HTML>
4<H1>Production and testing: Flashing</H1>
5
6
7(atusb only)
8
9<!-- ---------------------------------------------------------------------- -->
10
11
12<H3>Flashing the boot loader</H3>
13
14<P>
15<IMG src="setup-C.png">
16<P>
17
18
19<!-- ---------------------------------------------------------------------- -->
20
21
22<H3>Flashing the application</H3>
23
24<P>
25<IMG src="setup-D.png">
26<P>
27
28<P>
29<HR>
30Last update: 2011-05-18&nbsp;&nbsp;<I>Werner Almesberger</I>
31<HR>
32</BODY>
33</HTML>
prod/doc/index.html
7979<!-- ====================================================================== -->
8080
8181
82<H2>Software setup</H2>
82<H2>Detailed description</H2>
8383
84Before performing any production tests, various pieces of software
85need to be installed on Ben and PC, and configuration settings
86@@@
84The following pages describe the preparation and the execution of the
85production and test process:
86<UL>
87  <LI><A href="setup.html">Software setup</A>
88  <LI><A href="flash.html">Flashing (<B>atusb</B> only)</A>
89  <LI><A href="test.html">Functional test</A>
90  <LI><A href="analysis.html">Fault analysis</A>
91</UL>
8792
8893
89<!-- ---------------------------------------------------------------------- -->
90
91
92<H3>PC software installation</H3>
93
94@@@
95
96<H4>Install ben-wpan tools</H4>
97
98@@@
99
100<H4>Register Ben host name</H4>
101
102To simplify accessing the Ben via TCP/IP, its IP address should be
103registered in the hosts file on the PC. If the Ben is running OpenWrt,
104use the following command:
105<PRE>
106echo 192.168.254.101 ben >>/etc/hosts
107</PRE>
108<P>
109If the Ben is running Jlime, the address would be as follows:
110<PRE>
111echo 192.168.1.202 ben >>/etc/hosts
112</PRE>
113<P>
114If using the same PC with Bens running OpenWrt and Jlime, one may choose
115different host names depending on the distribution, and adapt the commands
116used in the production and testing process accordingly. For example,
117<PRE>
118echo 192.168.254.101 ben >>/etc/hosts
119echo 192.168.1.202 jlime >>/etc/hosts
120</PRE>
121
122
123<!-- ---------------------------------------------------------------------- -->
124
125
126<H3>Ben system setup</H3>
127
128The configuration setting described in this section are lost on each
129reset or reboot and either need to be entered again or a setup script
130running at boot time has to
131This needs to be done each time the Ben is booted.
132
133
134<H4>Enable network access</H4>
135
136Once the Ben has booted and started USB networking, the interface
137on the PC side is configured as follows:
138<PRE>
139ifconfig usb0 192.168.254.100 up
140</PRE>
141<P>
142These are the settings for OpenWrt, assuming the network device is
143called "usb0". If using Jlime, the command would be as follows:
144<PRE>
145ifconfig usb0 192.168.1.200 up
146</PRE>
147
148
149<H4>Silence other 8:10 card users</H4>
150
151Before running any of the ben-wpan utilities, other users of the 8:10
152card slot have to be disabled. In a Ben running the regular OpenWrt or
153Jlime distribution, the only such user that is automatically started
154is the MMC kernel driver. The following command disables it:
155<PRE>
156echo jz4740-mmc.0 >/sys/bus/platform/drivers/jz4740-mmc/unbind
157</PRE>
158<P>
159If a WPAN-enabled kernel has been installed, the AT86RF230 driver takes
160the place of the MMC driver. To disable it, run
161<PRE>
162echo spi2.0 >/sys/bus/spi/drivers/at86rf230/unbind
163</PRE>
164
165
166<H4>Start atrf-proxy</H4>
167
168On the Ben, launch the proxy daemon. We pass the option -b to background it:
169<PRE>
170atrf-proxy -b
171</PRE>
172
173
174<!-- ---------------------------------------------------------------------- -->
175
176
177<H3>Ben software installation</H3>
178
179<H4>Password-less remote access</H4>
180
181To enable password-less remote access from the PC, setup to betwork
182access to the Ben and run the following command:
183<PRE>
184ssh ben 'cat >>/etc/dropbear/authorized_keys' <~/.ssh/id_rsa.pub
185</PRE>
186
187
188<!-- ---------------------------------------------------------------------- -->
189
190
191<H3>Test profiles</H3>
192
193
194<!-- ====================================================================== -->
195
196
197<H2>Flashing (atusb only)<H2>
198
199<!-- ---------------------------------------------------------------------- -->
200
201
202<H3>Flashing the boot loader</H3>
203
204<P>
205<IMG src="setup-C.png">
206<P>
207
208
209<!-- ---------------------------------------------------------------------- -->
210
211
212<H3>Flashing the application</H3>
213
214<P>
215<IMG src="setup-D.png">
216<P>
217
218
219<!-- ====================================================================== -->
220
221
222<H2>Functional test</H2>
223
224<!-- ---------------------------------------------------------------------- -->
225
226
227<H3>Test setup for atben</H3>
228
229<P>
230<IMG src="setup-A.png">
231<P>
232
233<!-- ---------------------------------------------------------------------- -->
234
235
236<H3>Test setup for atusb</H3>
237
238<P>
239<IMG src="setup-B.png">
240<P>
241
242<!-- ---------------------------------------------------------------------- -->
243
244
245<H3>Test procedure</H3>
246
247
248<!-- ====================================================================== -->
249
250
251<H2>Fault analysis</H2>
252
253<!-- ---------------------------------------------------------------------- -->
254
255
256<H3>Component placement and orientation</H3>
257
258<!-- ---------------------------------------------------------------------- -->
259
260
261<H3>Supply voltages</H3>
262
263<!-- ---------------------------------------------------------------------- -->
264
265
266<H3>Clock frequency</H3>
267
268The flawless performance of the crystal oscillator is crucial for
269operation. Anomalies are easy to detect with even a low-cost oscilloscope
270and pinpoint specific problems and help to select further analysis steps.
271<P>
272The crystal used in <B>atben</B> and <B>atusb</B> has a nominal tolerance
273of +/- 15 ppm at 22-28 C. Low-cost oscilloscopes typically have a timing
274accuracy of
275+/- 100 ppm, which means that only major excursions can be detected by
276measuring the clock output with such an instrument. Full-speed USB only
277requires an accuracy of +/- 2500 ppm.
278We can therefore consider all results within a range of +/- 1000 ppm as
279sufficient, and perform more precise measurements by other means. This
280applies to <B>atben</B> as well as to <B>atusb</B>.
281<P>
282
283
284<H4>Measuring the clock on atben</H4>
285
286<B>atben</B> normally does not output a clock signal. A 1 MHz clock
287can be enabled with the following command:
288<PRE>
289atrf-txrx -d net:ben -C 1
290</PRE>
291This configures <B>atben</B> as a promiscuous receiver. The reception
292of any IEEE 802.15.4 frame or pressing Ctrl-C will terminate the command.
293<P>
294<TABLE>
295<TR><TH align="left">Clock<TH align="left">Action
296<TR><TD>0 Hz<TD>Check voltages; check that the clock is enabled;
297  check for shorts around crystal; check connectivity of crystal
298<TR><TD>0.999-1.001 MHz, ~3.3 Vpp<TD>Perform precision measurement with
299  <B>atrf-xtal</B>
300<TR><TD>Other<TD>Check voltages; check for contamination around crystal
301</TABLE>
302<P>
303
304
305<H4>Measuring the clock on atusb</H4>
306
307The transceiver provides the clock for the microcontroller in <B>atusb</B>.
308A clock signal is therefore always available. Immediately after reset,
309the transceiver generates a 1 MHz clock. When the microcontrolled comes out
310of reset, it raises the transceiver's clock output to 8 MHz and then
311enables USB.
312<P>
313<TABLE>
314<TR><TH align="left">Clock<TH align="left">Action
315<TR><TD>0 Hz<TD>Check voltages; check for shorts around crystal; check
316  connectivity of crystal
317<TR><TD>0.999-1.001 MHz, ~3.3 Vpp<TD>Check presence of firmware; check for
318  shorts on SPI signals; check connectivity of SPI signals
319<TR><TD>7.992-8.008 MHz, ~3.3 Vpp<TD>Perform precision measurement with
320  <B>atrf-xtal</B>
321<TR><TD>Other<TD>Check voltages; check for contamination around crystal
322</TABLE>
323
324
325<H4>Precision measurements</H4>
326
32794<P>
32895<HR>
32996Last update: 2011-05-18&nbsp;&nbsp;<I>Werner Almesberger</I>
prod/doc/setup.html
1<TITLE>Production and testing: Software setup</TITLE>
2<BODY>
3<HTML>
4<H1>Production and testing: Software setup</H1>
5
6Before performing any production tests, various pieces of software
7need to be installed on Ben and PC, and configuration settings
8@@@
9
10
11<!-- ---------------------------------------------------------------------- -->
12
13
14<H3>PC software installation</H3>
15
16@@@
17
18<H4>Install ben-wpan tools</H4>
19
20@@@
21
22<H4>Register Ben host name</H4>
23
24To simplify accessing the Ben via TCP/IP, its IP address should be
25registered in the hosts file on the PC. If the Ben is running OpenWrt,
26use the following command:
27<PRE>
28echo 192.168.254.101 ben >>/etc/hosts
29</PRE>
30<P>
31If the Ben is running Jlime, the address would be as follows:
32<PRE>
33echo 192.168.1.202 ben >>/etc/hosts
34</PRE>
35<P>
36If using the same PC with Bens running OpenWrt and Jlime, one may choose
37different host names depending on the distribution, and adapt the commands
38used in the production and testing process accordingly. For example,
39<PRE>
40echo 192.168.254.101 ben >>/etc/hosts
41echo 192.168.1.202 jlime >>/etc/hosts
42</PRE>
43
44
45<!-- ---------------------------------------------------------------------- -->
46
47
48<H3>Ben system setup</H3>
49
50The configuration setting described in this section are lost on each
51reset or reboot and either need to be entered again or a setup script
52running at boot time has to
53This needs to be done each time the Ben is booted.
54
55
56<H4>Enable network access</H4>
57
58Once the Ben has booted and started USB networking, the interface
59on the PC side is configured as follows:
60<PRE>
61ifconfig usb0 192.168.254.100 up
62</PRE>
63<P>
64These are the settings for OpenWrt, assuming the network device is
65called "usb0". If using Jlime, the command would be as follows:
66<PRE>
67ifconfig usb0 192.168.1.200 up
68</PRE>
69
70
71<H4>Silence other 8:10 card users</H4>
72
73Before running any of the ben-wpan utilities, other users of the 8:10
74card slot have to be disabled. In a Ben running the regular OpenWrt or
75Jlime distribution, the only such user that is automatically started
76is the MMC kernel driver. The following command disables it:
77<PRE>
78echo jz4740-mmc.0 >/sys/bus/platform/drivers/jz4740-mmc/unbind
79</PRE>
80<P>
81If a WPAN-enabled kernel has been installed, the AT86RF230 driver takes
82the place of the MMC driver. To disable it, run
83<PRE>
84echo spi2.0 >/sys/bus/spi/drivers/at86rf230/unbind
85</PRE>
86
87
88<H4>Start atrf-proxy</H4>
89
90On the Ben, launch the proxy daemon. We pass the option -b to background it:
91<PRE>
92atrf-proxy -b
93</PRE>
94
95
96<!-- ---------------------------------------------------------------------- -->
97
98
99<H3>Ben software installation</H3>
100
101<H4>Password-less remote access</H4>
102
103To enable password-less remote access from the PC, setup to betwork
104access to the Ben and run the following command:
105<PRE>
106ssh ben 'cat >>/etc/dropbear/authorized_keys' <~/.ssh/id_rsa.pub
107</PRE>
108
109
110<!-- ---------------------------------------------------------------------- -->
111
112
113<H3>Test profiles</H3>
114
115
116<P>
117<HR>
118Last update: 2011-05-18&nbsp;&nbsp;<I>Werner Almesberger</I>
119<HR>
120</BODY>
121</HTML>
prod/doc/test.html
1<TITLE>Production and testing: Functional test</TITLE>
2<BODY>
3<HTML>
4<H1>Production and testing: Functional test</H1>
5
6
7<!-- ---------------------------------------------------------------------- -->
8
9
10<H3>Test setup for atben</H3>
11
12<P>
13<IMG src="setup-A.png">
14<P>
15
16<!-- ---------------------------------------------------------------------- -->
17
18
19<H3>Test setup for atusb</H3>
20
21<P>
22<IMG src="setup-B.png">
23<P>
24
25<!-- ---------------------------------------------------------------------- -->
26
27
28<H3>Test procedure</H3>
29
30
31<P>
32<HR>
33Last update: 2011-05-18&nbsp;&nbsp;<I>Werner Almesberger</I>
34<HR>
35</BODY>
36</HTML>

Archive Download the corresponding diff file



interactive