Project

General

Profile

OsmoTRX » History » Version 46

laforge, 02/21/2016 02:48 PM

1 41 ttsou
{{>toc}}
2 1 ttsou
3 41 ttsou
h1. [[OsmoTRX]]
4 1 ttsou
5
6 41 ttsou
[[OsmoTRX]] is a software-defined radio transceiver that implements the Layer 1 physical layer of a BTS comprising the following 3GPP specifications:
7
* TS 05.01 "Physical layer on the radio path"
8
* TS 05.02 "Multiplexing and Multiple Access on the Radio Path"
9
* TS 05.04 "Modulation"
10
* TS 05.10 "Radio subsystem synchronization"
11 1 ttsou
12 45 laforge
[[OsmoTRX]] is based on the transceiver code from the [[OpenBTS]] project, but setup to operate independently with the purpose of using with non-OpenBTS software and projects, while still maintaining backwards compatibility with [[OpenBTS]]. Currently there are numerous features contained in [[OsmoTRX]] that extend the functionality of the [[OpenBTS]] transceiver. These features include enhanced support for various embedded platforms - notably ARM - and dual channel diversity support for the Fairwaves [[umtrx:]].
13 41 ttsou
14 46 laforge
h2. OsmoTRX in the Osmocom GSM architecture
15
16
{{graphviz_link()
17
digraph G {
18
    rankdir = LR;
19
    SDR -> OsmoTRX [label="Raw Samples"];
20
    OsmoTRX -> OsmoBTS [label="bursts over UDP"];
21
    OsmoBTS -> OsmoNITB [label="Abis/IP"];
22
    OsmoBTS -> OsmoPCU [label="pcu_sock"];
23
    OsmoPCU -> OsmoSGSN [label="Gb/IP"];
24
    OsmoTRX [color=red];
25
}
26
}}
27 41 ttsou
28
h2. Features
29
30
31
*Intel SSE Support*
32 6 ttsou
* SSE3
33
* SSE4.1
34 20 ttsou
35 41 ttsou
On Intel processors, [[OsmoTRX]] makes heavy use of the Streaming SIMD Extensions (SSE) instruction set. Accelerated operations include pulse shape filtering, resampling, sequence correlation, and many other signal processing operations. SSE3 is the minimum requirement for accelerated use.
36 1 ttsou
37 20 ttsou
SSE3 is present in the majority of Intel processors since later versions of the Pentium 4 architecture and is also present on low power Atom processors. Support is automatically detected at build time. For additional performance information, please see the performance and benchmarks section.
38 29 ttsou
39 41 ttsou
*ARM Support*
40 1 ttsou
* NEON
41
* NEON-VFPv4
42 20 ttsou
43 41 ttsou
[[OsmoTRX]] runs on a variety of ARM processors with and without NEON coprocessors. Like SSE on Intel processors, NEON provides acceleration with SIMD vectorized instructions.
44 20 ttsou
45 1 ttsou
Tested popular architectures include ARM11 (Raspberry Pi), Cortex-A8 (!BeagleBoard), and Cortex-A15 (!ArndaleBoard). Loosely speaking, these platforms are representative of low cost embedded devices, mid-level handsets, and high-end smartphones respectively. Similarly, in order, these platforms include no NEON coprocessor, standard NEON, and NEON-VFPv4. The latter NEON variation, VFPv4, provides additional fused-multiply-accumulate (FMA) instructions useful for many DSP operations.
46
47 26 ttsou
NEON support must be enabled by the user at build time. For additional information, please see the configuration and performance and benchmarks sections.
48 37 ttsou
49 41 ttsou
*Dual Channel (UmTRX and B210)*
50 7 ttsou
51 1 ttsou
Two dual channel modes are available: standard dual channel mode and diversity. In standard dual channel mode, each RF
52 28 ttsou
path of the dual channel device supports a different ARFCN. Each path operates independently a
53 1 ttsou
nd operates similarly to two separate devices. GSM channel capacity in this mode is doubled. This option can be configured at run time from the command line.
54
55 41 ttsou
*Dual Channel Diversity (UmTRX, experimental)*
56 1 ttsou
57 28 ttsou
Diversity mode is similar to the standard dual channel mode except each antenna supports both ARFCN channels. In this case, the receiver sample bandwidth is widened to handle both ARFCN's and subsequently converted and demultiplexed into separate sample streams. Each GSM receive path is fed dual signals, where antenna selection diversity is performed by taking the stronger signal on a burst-by-burst basis. This diversity setup improves uplink reception performance in multipath fading environments.
58 16 ttsou
59 28 ttsou
Limitations are increased CPU utilization and that ARFCN spacing is restricted (currently at 400 kHz) by the receiver sampling bandwidth. Setting the ARFCN spacing beyond the sampling limit will disable the diversity path and operate in standard dual channel mode. This options can be configured at run time from the command line.
60 20 ttsou
61 41 ttsou
*Uplink Burst Detection*
62 39 ttsou
63 41 ttsou
[[OsmoTRX]] utilizes an updated receive burst detection algorithm that provides greater sensitivity and reliability than the original [[OpenBTS]] approach, which relied on energy detection for the initial stage of burst acquisition.
64 39 ttsou
65 1 ttsou
The limitation of the previous approach was that it was slow to adapt to highly transient power levels and false burst detection in challenging situations such as receiver saturation, which may occur in close range lab testing. The other issue was that a high degree of level tuning was often necessary to operate reliably.
66
67
The current receiver code addressed those limitations for improved performance in a wider variety of environments.
68
69 41 ttsou
*Low Phase Error Modulator*
70 16 ttsou
71
The default GSM downlink signal is configured for low distortion using a linearized GMSK modulator. The implementation is based on a two pulse Laurent approximation of continuous phase modulated (CPM) signals. The baseband output signal measures with very low phase error and is capable of passing industry spectrum mask requirements. Please note that actual performance will depend strongly on the particular device in use.
72 1 ttsou
73 41 ttsou
Theoretical details can be found in the report on "GMSK":http://tsou.cc/gsm/report_gmsk.pdf. Octave / Matlab code for "pulse generation":http://tsou.cc/gsm/laurent.m is also available.
74 1 ttsou
75
This option can be enabled or disabled at run time from the command line.
76 28 ttsou
77
Very Low Phase Error (Ettus Research N200)
78 16 ttsou
79 42 laforge
!http://tsou.cc/gsm/osmo-trx-phase75.gif!
80 1 ttsou
81 21 ttsou
Spectrum Mask (Ettus Research N200)
82 1 ttsou
83 42 laforge
!http://tsou.cc/gsm/osmo-trx-spectrum75.gif!
84 1 ttsou
85
86 41 ttsou
h2. RF Hardware support
87 1 ttsou
88 41 ttsou
89
Multiple RF devices are currently supported. These include USRP family products from Ettus Research, and the [[UmTRX]] from Fairwaves.
90
91
||*Fairwaves*||*Notes*||
92 20 ttsou
||UmTRX||Dual channel||
93
94
All Ettus Research devices are supported.
95 1 ttsou
96 41 ttsou
||*Ettus Research*||*Notes*||
97 1 ttsou
||USRP1||Requires legacy libusrp driver and clocking modification||
98
||USRP2||10 MHz external reference required||
99
||B100||
100
||B110||
101
||B200||GPSDO or 10 MHz external reference recommended||
102
||B210||Dual channel, 10 MHz external reference recommended||
103
||N200||
104 20 ttsou
||N210||
105 1 ttsou
||E100||
106
||E110||
107
108 41 ttsou
h2. Embedded Platform Support
109 1 ttsou
110 41 ttsou
111
[[OsmoTRX]] has been tested on the multiple embedded platforms representing a wide range of device types. Low cost ARM devices are generally limited by memory and I/O as much CPU utilization.
112
113 1 ttsou
Running a full or near full ARFCN configuration (7 simultaneous TCH channels with Combination V) may require running the GSM stack remotely, which can be configured at runtime on the command line. This limitation appears to be scheduling related more so than lack of CPU resources, and may be resolved at a later time.
114
115 43 laforge
|_.Platform|_.SoC*|_.Processor|_.SIMD/FPU|_.Testing Notes|
116
|ArndaleBoard|Samsung Exynos 5250|ARM Cortex-A15|NEON-VFPv4|7 TCH|
117
|BeagleBoard-xM|Texas Instruments OMAP3|ARM Cortex-A8|NEON|7 TCH, remote [[osmobts:]] stack|
118
|Ettus E100|Texas Instruments OMAP3|ARM Cortex-A8|NEON|7 TCH, remote [[osmobts:]] stack|
119
|Raspberry Pi|Broadcom BCM2835|ARM11|VFP|2 TCH, remote [[osmobts:]] stack|
120
|Shuttle PC|NA|Intel Atom D2550|SSE3|Dual channel, 15 TCH|
121 1 ttsou
122
All embedded plaforms were tested with low-phase error modulator disabled. Use of the more accurate modulator on embedded platforms has not been extensively tested.
123 19 ttsou
124 41 ttsou
h2. Mailing List
125 22 ttsou
126 41 ttsou
127
For development purposes, [[OsmoTRX]] is discussed on both [[OpenBTS]] and [[OpenBSC]] mailing lists at openbts-discuss@lists.sourceforge.net and openbsc@lists.osmocom.org respectively.
128
129 1 ttsou
Please direct questions and bug reports to the list appropriate for the GSM stack being used.
130
131 41 ttsou
Subscription information is available at "and [http://lists.osmocom.org/mailman/listinfo/openbsc/":https://lists.sourceforge.net/lists/listinfo/openbts-discuss].
132 1 ttsou
133
134 41 ttsou
h2. GPRS support
135 1 ttsou
136
137 44 laforge
[[OsmoTRX]] supports GPRS through [[osmobts:]].
138 1 ttsou
139 41 ttsou
For GPRS support with [[OpenBTS]], please use the transceiver supplied with [[OpenBTS]].
140
141
142
h2. Source code
143
144
145 1 ttsou
The source code is available from git.osmocom.org (module osmo-trx).
146 18 ttsou
147
Public read-only access is available via
148 41 ttsou
<pre>
149 19 ttsou
$ git clone git://git.osmocom.org/osmo-trx
150 41 ttsou
</pre>
151 1 ttsou
You can browse it via cgit: http://cgit.osmocom.org/cgit/osmo-trx/
152
153
154 41 ttsou
h2. Configuration and Build
155 1 ttsou
156 41 ttsou
157
The only package dependency is the Universal Hardware Driver (UHD), which is available from Ettus Research or Fairwaves depending on the device. Please note that the UHD implementation must match hardware (i.e. Ettus Research UHD for USRP devices and Fairwaves UHD with [[UmTRX]]). The one device that does not use the UHD driver is the USRP1, which is supported through the legacy libusrp driver provided in GNU Radio 3.4.2.
158
159 36 ttsou
First, run autoreconf to remake the build system files.
160 41 ttsou
<pre>
161 1 ttsou
$ autoreconf -i
162 18 ttsou
...
163 41 ttsou
</pre>
164 18 ttsou
165 41 ttsou
*Intel Platforms (All)*
166 18 ttsou
167 1 ttsou
Intel SSE support is automatically detected on Intel x86 platforms. No user intervention is necessary. The general configuration defaults to the low phase error modulator. Atom users may wish to use the low-CPU utilization modulator, which can be later enabled from the command line at runtime.
168 41 ttsou
<pre>
169 18 ttsou
$ ./configure
170 1 ttsou
...
171
checking whether mmx is supported... yes
172 19 ttsou
checking whether sse is supported... yes
173 18 ttsou
checking whether sse2 is supported... yes
174
checking whether sse3 is supported... yes
175
checking whether ssse3 is supported... yes
176
checking whether sse4.1 is supported... yes
177
checking whether sse4.2 is supported... yes
178
...
179 41 ttsou
</pre>
180 18 ttsou
181 41 ttsou
*ARM Platforms with NEON*
182 18 ttsou
183 41 ttsou
Many popular ARM development boards fall under this category including BeagleBoard, PandaBoard, and Ettus E100 USRP. This option will disable the low phase error modulator, which can be re-enabled at runtime. NEON support must be manually enabled.
184
<pre>
185 24 ttsou
$ ./configure --with-neon
186 41 ttsou
</pre>
187 1 ttsou
188 41 ttsou
*ARM Platforms with NEON-VFPv4*
189 1 ttsou
190 41 ttsou
Currently very few development platforms support this instruction set, which is seen mainly in high end smartphones and tablets. Available development boards are ArndaleBoard and ODROID-XU. This option will disable the low phase error modulator, which can be re-enabled at runtime. NEON-VFPv4 support must be manually enabled.
191
<pre>
192 1 ttsou
$ ./configure --with-neon-vfpv4
193 41 ttsou
</pre>
194 1 ttsou
195 41 ttsou
*ARM Platforms without NEON*
196 1 ttsou
197 41 ttsou
This configuration mainly targets the Raspberry Pi. ARM platforms without NEON vector units are almost always very slow processors, and generally not very suitable for running [[OsmoTRX]]. Running [[OsmoTRX]] on a Raspberry Pi, however, is possible along with limited TCH (voice) channel support. Currently this configuration requires minor code changes.
198 1 ttsou
199
Coming soon...
200
201 41 ttsou
*Build and Install*
202 1 ttsou
203 16 ttsou
After configuration, installation is simple.
204
205 41 ttsou
<pre>
206 16 ttsou
$ make
207
$ sudo make install
208 41 ttsou
</pre>
209 16 ttsou
210
211 41 ttsou
h2. Running
212 16 ttsou
213 41 ttsou
214
[[OsmoTRX]] can be configured with a variety of options on the command line. In most cases, the default settings will suffice. Notable options include UHD device argument passing, which is often useful for using network based devices with firewalls, and external 10 MHz reference support.
215
216
<pre>
217 16 ttsou
$ osmo-trx -h
218
linux; GNU C++ version 4.8.1 20130603 (Red Hat 4.8.1-1); Boost_105300; UHD_003.005.004-140-gfb32ed16
219
220
Options:
221
  -h    This text
222 1 ttsou
  -a    UHD device args
223 16 ttsou
  -l    Logging level (EMERG, ALERT, CRT, ERR, WARNING, NOTICE, INFO, DEBUG)
224
  -i    IP address of GSM core
225 1 ttsou
  -p    Base port number
226
  -d    Enable dual channel diversity receiver
227 16 ttsou
  -x    Enable external 10 MHz reference
228
  -s    Samples-per-symbol (1 or 4)
229 38 ttsou
  -c    Number of ARFCN channels (default=1)
230
  -f    Enable C0 filler table
231 16 ttsou
  -o    Set baseband frequency offset (default=auto)
232 41 ttsou
</pre>
233 16 ttsou
234 41 ttsou
<pre>
235 1 ttsou
$ osmo-trx -a "addr=192.168.10.2"
236 16 ttsou
linux; GNU C++ version 4.8.1 20130603 (Red Hat 4.8.1-1); Boost_105300; UHD_003.004.000-b14cde5
237
238
Config Settings
239
   Log Level............... INFO
240 1 ttsou
   Device args............. addr=192.168.10.2
241 16 ttsou
   TRX Base Port........... 5700
242 1 ttsou
   TRX Address............. 127.0.0.1
243 16 ttsou
   Channels................ 1
244
   Samples-per-Symbol...... 4
245
   External Reference...... Disabled
246
   Diversity............... Disabled
247
248 41 ttsou
-- Opening a [[UmTRX]] device...
249 13 ttsou
-- Current recv frame size: 1472 bytes
250 38 ttsou
-- Current send frame size: 1472 bytes
251 41 ttsou
-- Setting [[UmTRX]] 4 SPS
252 38 ttsou
-- Transceiver active with 1 channel(s)
253 41 ttsou
</pre>
254 38 ttsou
255 1 ttsou
256 41 ttsou
h2. [[OsmoTRX]] with [[OpenBTS]]
257 38 ttsou
258
259 41 ttsou
[[OsmoTRX]] is fully compatible with [[OpenBTS]] for voice and SMS services. Due to differences in handing of GPRS, [[OsmoTRX]] does not support GPRS when used with [[OpenBTS]], however, GPRS with the Osmocom stack is supported.
260
261
For use with [[OpenBTS]], enable the filler table option "Enable C0 filler table", which enables [[OpenBTS]] style idle bursts and retransmissions.
262
263
<pre>
264 1 ttsou
$ osmo-trx -f
265 41 ttsou
</pre>
266 17 ttsou
267 41 ttsou
The [[OsmoTRX]] transceiver should be started before running [[OpenBTS]]. No symbolic link to './transceiver' should exist in the [[OpenBTS]] directory. This prevents [[OpenBTS]] from starting its own transceiver instance.
268 35 ttsou
269 1 ttsou
270 41 ttsou
h2. Benchmarks
271 1 ttsou
272 35 ttsou
273 44 laforge
A variety of performance benchmarks are available for various code optimizations. These include floating point - integer conversions, convolution, and convolutional decoding. Note that convolutional decoding does not take place in [[OsmoTRX]], but one stop higher in the Layer 1 stack - either in [[osmobts:]] or [[OpenBTS]] core.
274 35 ttsou
275 41 ttsou
*Repository*
276
277
Currently the trx-bench repository holds the test files and contains the same NEON and SSE code as [[OsmoTRX]]. The test code may be merged into [[OsmoTRX]] at a later time, but, for now, it exists as a separate repository. NEON configure options are the same as [[OsmoTRX]].
278
279
<pre>
280 35 ttsou
$ git clone https://github.com/ttsou/trx-bench.git
281
282
$ cd trx-bench
283
$ autoreconf -i
284
$ ./configure [--with-neon] [--with-neon-vfp4]
285 1 ttsou
$ make
286
$ src/conv_test
287 35 ttsou
$ src/convert_test
288
$ src/convolve_test
289 41 ttsou
</pre>
290 35 ttsou
291
The convolutional decoding test includes command options including experimental support for benchmarking with multiple threads.
292
293 41 ttsou
<pre>
294 35 ttsou
$ ./conv_test -h
295
Options:
296
  -h    This text
297 1 ttsou
  -i    Number of iterations
298
  -j    Number of threads for benchmark (1 to 32)
299 13 ttsou
  -b    Run benchmark tests
300
  -a    Run validity checks
301
  -e    Run bit-error-rate tests
302 41 ttsou
</pre>
303 10 ttsou
304 1 ttsou
Selected benchmark results are provided below. All tests are run on a single core only.
305
306 41 ttsou
*Intel Haswell (i7 4770K 3.5 GHz)*
307 1 ttsou
308 41 ttsou
<pre>
309 1 ttsou
--- Floating point to integer conversions
310
-- Testing 40000 iterations of 3120 values
311
- Measuring conversion time
312
- Elapsed time base...                  0.065508 secs
313
- Validating SIMD conversion results... PASS
314 3 ttsou
- Measuring conversion time
315
- Elapsed time SIMD ...                 0.011424 secs
316
- Speedup...                            5.734244
317 41 ttsou
</pre>
318 1 ttsou
319 41 ttsou
<pre>
320 3 ttsou
[+] Testing: GSM TCH/AFS 7.95 (recursive, flushed, punctured)
321
[.] Input length  : ret = 165  exp = 165 -> OK
322
[.] Output length : ret = 448  exp = 448 -> OK
323
[.] Pre computed vector checks:
324
[..] Encoding: OK
325
[..] Decoding base: 
326
[..] Decoding SIMD: 
327 1 ttsou
[..] Code N 3
328
[..] Code K 7
329
OK
330
[.] Random vector checks:
331
[.] Testing baseline:
332 17 ttsou
[..] Encoding / Decoding 10000 cycles:
333
[.] Elapsed time........................ 1.435066 secs
334
[.] Rate................................ 3.121808 Mbps
335
[.] Testing SIMD:
336
[..] Encoding / Decoding 10000 cycles:
337
[.] Elapsed time........................ 0.073524 secs
338
[.] Rate................................ 60.932485 Mbps
339
[.] Speedup............................. 19.518334
340 41 ttsou
</pre>
341 17 ttsou
342 41 ttsou
*Intel Atom (D2500 1.86 GHz)*
343
<pre>
344 17 ttsou
--- Floating point to integer conversions
345
-- Testing 40000 iterations of 3120 values
346
- Measuring conversion time
347
- Elapsed time base...                 1.147449 secs
348 1 ttsou
- Validating SSE conversion results... PASS
349 17 ttsou
- Measuring conversion time
350 1 ttsou
- Elapsed time SSE ...                 0.347838 secs
351
- Quotient...                          3.298803
352 41 ttsou
</pre>
353 17 ttsou
354 41 ttsou
<pre>
355 1 ttsou
[+] Testing: GSM TCH/AFS 7.95 (recursive, flushed, punctured)
356
[.] Input length  : ret = 165  exp = 165 -> OK
357
[.] Output length : ret = 448  exp = 448 -> OK
358
[.] Pre computed vector checks:
359 17 ttsou
[..] Encoding: OK
360
[..] Decoding base: 
361
[..] Decoding SIMD: 
362
[..] Code N 3
363
[..] Code K 7
364
OK
365
[.] Random vector checks:
366 19 ttsou
[.] Testing baseline:
367
[..] Encoding / Decoding 10000 cycles:
368
[.] Elapsed time........................ 11.822688 secs
369 17 ttsou
[.] Rate................................ 0.378932 Mbps
370
[.] Testing SIMD:
371
[..] Encoding / Decoding 10000 cycles:
372
[.] Elapsed time........................ 0.550423 secs
373
[.] Rate................................ 8.139195 Mbps
374
[.] Speedup............................. 21.479277
375 41 ttsou
</pre>
376 17 ttsou
377 41 ttsou
*!ArndaleBoard (ARM Cortex-A15 1.7 GHz)*
378 17 ttsou
379
Please note that the Viterbi implementations on ARM is largely C based with speedup generated primarily through algorithm changes. In comparison, vector optimization on Intel platforms with SSE is currently much more aggressive, which explains the disparity on decoding performance.
380
381 41 ttsou
<pre>
382 17 ttsou
--- Floating point to integer conversions
383
-- Testing 40000 iterations of 3120 values
384
- Measuring conversion time
385
- Elapsed time base...                 0.384097 secs
386
- Validating SSE conversion results... PASS
387
- Measuring conversion time
388
- Elapsed time SSE ...                 0.100877 secs
389
- Quotient...                          3.807578
390 41 ttsou
</pre>
391 17 ttsou
392 41 ttsou
<pre>
393 17 ttsou
[+] Testing: GSM TCH/AFS 7.95 (recursive, flushed, punctured)
394
[.] Input length  : ret = 165  exp = 165 -> OK
395
[.] Output length : ret = 448  exp = 448 -> OK
396
[.] Pre computed vector checks:
397
[..] Encoding: OK
398
[..] Decoding base: 
399
[..] Decoding SIMD: 
400
[..] Code N 3
401
[..] Code K 7
402
OK
403
[.] Random vector checks:
404
[.] Testing baseline:
405
[..] Encoding / Decoding 10000 cycles:
406
[.] Elapsed time........................ 5.371288 secs
407
[.] Rate................................ 0.834064 Mbps
408 3 ttsou
[.] Testing SIMD:
409
[..] Encoding / Decoding 10000 cycles:
410
[.] Elapsed time........................ 1.016621 secs
411
[.] Rate................................ 4.406755 Mbps
412
[.] Speedup............................. 5.283471
413 41 ttsou
</pre>
414 3 ttsou
415 41 ttsou
*!BeagleBoard-xM (ARM Cortex-A8 800 MHz)*
416
<pre>
417 5 ttsou
--- Floating point to integer conversions
418 3 ttsou
-- Testing 40000 iterations of 3120 values
419
- Measuring conversion time
420
- Elapsed time base...                  6.292542 secs
421 4 ttsou
- Validating SIMD conversion results... PASS
422 3 ttsou
- Measuring conversion time
423
- Elapsed time SIMD ...                 0.839081 secs
424
- Quotient...                           7.499326
425 41 ttsou
</pre>
426 1 ttsou
427 41 ttsou
<pre>
428 31 ttsou
[+] Testing: GSM TCH/AFS 7.95 (recursive, flushed, punctured)
429
[.] Input length  : ret = 165  exp = 165 -> OK
430
[.] Output length : ret = 448  exp = 448 -> OK
431
[.] Pre computed vector checks:
432
[..] Encoding: OK
433
[..] Decoding base: 
434
[..] Decoding SIMD: 
435
[..] Code N 3
436
[..] Code K 7
437 1 ttsou
OK
438 32 ttsou
[.] Random vector checks:
439
[.] Testing baseline:
440
[..] Encoding / Decoding 10000 cycles:
441
[.] Elapsed time........................ 21.963257 secs
442
[.] Rate................................ 0.203977 Mbps
443
[.] Testing SIMD:
444
[..] Encoding / Decoding 10000 cycles:
445
[.] Elapsed time........................ 3.083282 secs
446
[.] Rate................................ 1.452997 Mbps
447
[.] Speedup............................. 7.123337
448 41 ttsou
</pre>
449 32 ttsou
450
451 41 ttsou
*Full Results*
452 32 ttsou
453 41 ttsou
"[http://tsou.cc/gsm/shuttle.txt":http://tsou.cc/gsm/haswell.txt]
454 31 ttsou
455 41 ttsou
"[http://tsou.cc/gsm/beagle.txt":http://tsou.cc/gsm/arndale.txt]
456 1 ttsou
457 30 ttsou
458 1 ttsou
459 41 ttsou
h2. Authors
460 1 ttsou
461
462 41 ttsou
[[OsmoTRX]] is currently developed and maintained by Thomas Tsou with generous support from Fairwaves, the Open Technology Institute, and Ettus Research. The code is derived from the [[OpenBTS]] project, which was originally developed by David Burgess and Harvind Samra at Range Networks.
Add picture from clipboard (Maximum size: 48.8 MB)