Project

General

Profile

OsmoTRX » History » Version 51

neels, 06/28/2016 02:03 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 49 neels
[[OsmoTRX]] is based on the transceiver code from the [[OsmoBTS:OpenBTS]] project, but setup to operate independently with the purpose of using with non-OpenBTS software and projects, while still maintaining backwards compatibility with [[OsmoBTS:OpenBTS]]. Currently there are numerous features contained in [[OsmoTRX:]] that extend the functionality of the [[OsmoBTS: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 49 neels
[[OsmoTRX]] utilizes an updated receive burst detection algorithm that provides greater sensitivity and reliability than the original [[OsmoBTS: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 41 ttsou
h2. RF Hardware support
86 1 ttsou
87
88 50 neels
Multiple RF devices are currently supported. These include USRP family products from Ettus Research, and the [[UmTRX:]] from Fairwaves.
89 41 ttsou
90
||*Fairwaves*||*Notes*||
91 20 ttsou
||UmTRX||Dual channel||
92
93
All Ettus Research devices are supported.
94 1 ttsou
95 41 ttsou
||*Ettus Research*||*Notes*||
96 1 ttsou
||USRP1||Requires legacy libusrp driver and clocking modification||
97
||USRP2||10 MHz external reference required||
98
||B100||
99
||B110||
100
||B200||GPSDO or 10 MHz external reference recommended||
101
||B210||Dual channel, 10 MHz external reference recommended||
102
||N200||
103 20 ttsou
||N210||
104 1 ttsou
||E100||
105
||E110||
106
107 41 ttsou
h2. Embedded Platform Support
108 1 ttsou
109 41 ttsou
110
[[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.
111
112 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.
113
114 43 laforge
|_.Platform|_.SoC*|_.Processor|_.SIMD/FPU|_.Testing Notes|
115
|ArndaleBoard|Samsung Exynos 5250|ARM Cortex-A15|NEON-VFPv4|7 TCH|
116
|BeagleBoard-xM|Texas Instruments OMAP3|ARM Cortex-A8|NEON|7 TCH, remote [[osmobts:]] stack|
117
|Ettus E100|Texas Instruments OMAP3|ARM Cortex-A8|NEON|7 TCH, remote [[osmobts:]] stack|
118
|Raspberry Pi|Broadcom BCM2835|ARM11|VFP|2 TCH, remote [[osmobts:]] stack|
119
|Shuttle PC|NA|Intel Atom D2550|SSE3|Dual channel, 15 TCH|
120 1 ttsou
121
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.
122 19 ttsou
123 41 ttsou
h2. Mailing List
124 22 ttsou
125 41 ttsou
126 49 neels
For development purposes, [[OsmoTRX:]] is discussed on both [[OsmoBTS:OpenBTS]] and [[OpenBSC:]] mailing lists at openbts-discuss@lists.sourceforge.net and openbsc@lists.osmocom.org respectively.
127 41 ttsou
128 1 ttsou
Please direct questions and bug reports to the list appropriate for the GSM stack being used.
129 41 ttsou
130 47 laforge
Subscription information is available at "and [http://lists.osmocom.org/mailman/listinfo/openbsc/":https://lists.sourceforge.net/lists/listinfo/openbts-discuss].  Please make sure to read our [[cellular-infrastructure:MailingListRules]] before posting.
131 1 ttsou
132 41 ttsou
h2. GPRS support
133 1 ttsou
134
135 44 laforge
[[OsmoTRX]] supports GPRS through [[osmobts:]].
136 1 ttsou
137 49 neels
For GPRS support with [[OsmoBTS:OpenBTS]], please use the transceiver supplied with [[OsmoBTS:OpenBTS]].
138 41 ttsou
139
140
h2. Source code
141
142
143 1 ttsou
The source code is available from git.osmocom.org (module osmo-trx).
144 18 ttsou
145
Public read-only access is available via
146 41 ttsou
<pre>
147 19 ttsou
$ git clone git://git.osmocom.org/osmo-trx
148 41 ttsou
</pre>
149 1 ttsou
You can browse it via cgit: http://cgit.osmocom.org/cgit/osmo-trx/
150
151 48 neels
h2. Dependencies
152 1 ttsou
153 48 neels
Install libusb-1.0 and libbost dev packages. On debian 8.4:
154 1 ttsou
155 48 neels
<pre>
156
sudo apt-get install --no-install-recommends libusb-1.0-0-dev libboost-dev
157
</pre>
158 41 ttsou
159 48 neels
*UHD*
160 1 ttsou
161 48 neels
Unless using USRP1, you will need the Universal Hardware Driver (UHD),
162
which is available from Ettus Research or Fairwaves; the UHD implementation
163
must match your hardware:
164
165
* Ettus Research UHD for USRP devices
166 51 neels
* Fairwaves UHD with [[UmTRX:]]
167 48 neels
* USRP1 does not use the UHD driver, it is supported through the legacy libusrp driver provided in GNU Radio 3.4.2.
168
169
*Debian*
170
171
At time of writing, the debian 8.4 packages for UHD are sufficient for running osmo-trx and osmo-bts-trx.
172
here are some of the packages that need to be installed:
173
174
<pre>
175
sudo apt-get install --no-install-recommends libuhd-dev uhd-host
176
</pre>
177
178
It may be necessary to use the pothos PPA instead:
179
180
<pre>
181
sudo add-apt-repository ppa:guruofquality/pothos
182
sudo apt-get update
183
sudo apt install libboost-dev uhd
184
</pre>
185
186
*Firmware*
187
188
You also need to download the firmware using a script provided by the UHD package.
189
Instructions suggest running the script as root, but this way is less dangerous:
190
191
<pre>
192
sudo mkdir /usr/share/uhd
193
sudo chown $USER: /usr/share/uhd
194
/usr/lib/uhd/utils/uhd_images_downloader.py
195
</pre>
196
197
*Group*
198
199
You may need to add yourself to the usrp group:
200
201
<pre>
202
sudo gpasswd -a $USER usrp
203
# and re-login to acquire the group
204
</pre>
205
206
*Verify*
207
208
run uhd_find_devices to make sure b200 is available:
209
210
<pre>
211
$ uhd_find_devices 
212
linux; GNU C++ version 4.9.1; Boost_105500; UHD_003.007.003-0-unknown
213
214
--------------------------------------------------
215
-- UHD Device 0
216
--------------------------------------------------
217
Device Address:
218
    type: b200
219
    name: MyB210
220
    serial: 1C0FFEE
221
    product: B210
222
</pre>
223
224
h2. Configuration and Build
225
226 41 ttsou
First, run autoreconf to remake the build system files.
227 1 ttsou
<pre>
228 18 ttsou
$ autoreconf -i
229 41 ttsou
...
230 18 ttsou
</pre>
231 41 ttsou
232 18 ttsou
*Intel Platforms (All)*
233 1 ttsou
234 41 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.
235 18 ttsou
<pre>
236 1 ttsou
$ ./configure
237
...
238 19 ttsou
checking whether mmx is supported... yes
239 18 ttsou
checking whether sse is supported... yes
240
checking whether sse2 is supported... yes
241
checking whether sse3 is supported... yes
242
checking whether ssse3 is supported... yes
243
checking whether sse4.1 is supported... yes
244
checking whether sse4.2 is supported... yes
245 41 ttsou
...
246 18 ttsou
</pre>
247 41 ttsou
248 18 ttsou
*ARM Platforms with NEON*
249 41 ttsou
250
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.
251 24 ttsou
<pre>
252 41 ttsou
$ ./configure --with-neon
253 1 ttsou
</pre>
254 41 ttsou
255 1 ttsou
*ARM Platforms with NEON-VFPv4*
256 41 ttsou
257
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.
258 1 ttsou
<pre>
259 41 ttsou
$ ./configure --with-neon-vfpv4
260 1 ttsou
</pre>
261 41 ttsou
262 1 ttsou
*ARM Platforms without NEON*
263 41 ttsou
264 1 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.
265
266
Coming soon...
267 41 ttsou
268 1 ttsou
*Build and Install*
269 16 ttsou
270
After configuration, installation is simple.
271 41 ttsou
272 16 ttsou
<pre>
273
$ make
274 41 ttsou
$ sudo make install
275 16 ttsou
</pre>
276
277 41 ttsou
h2. Running
278 16 ttsou
279 41 ttsou
280
[[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.
281
282
<pre>
283 16 ttsou
$ osmo-trx -h
284
linux; GNU C++ version 4.8.1 20130603 (Red Hat 4.8.1-1); Boost_105300; UHD_003.005.004-140-gfb32ed16
285
286
Options:
287
  -h    This text
288 1 ttsou
  -a    UHD device args
289 16 ttsou
  -l    Logging level (EMERG, ALERT, CRT, ERR, WARNING, NOTICE, INFO, DEBUG)
290
  -i    IP address of GSM core
291 1 ttsou
  -p    Base port number
292
  -d    Enable dual channel diversity receiver
293 16 ttsou
  -x    Enable external 10 MHz reference
294
  -s    Samples-per-symbol (1 or 4)
295 38 ttsou
  -c    Number of ARFCN channels (default=1)
296
  -f    Enable C0 filler table
297 16 ttsou
  -o    Set baseband frequency offset (default=auto)
298 41 ttsou
</pre>
299 16 ttsou
300 41 ttsou
<pre>
301 1 ttsou
$ osmo-trx -a "addr=192.168.10.2"
302 16 ttsou
linux; GNU C++ version 4.8.1 20130603 (Red Hat 4.8.1-1); Boost_105300; UHD_003.004.000-b14cde5
303
304
Config Settings
305
   Log Level............... INFO
306 1 ttsou
   Device args............. addr=192.168.10.2
307 16 ttsou
   TRX Base Port........... 5700
308 1 ttsou
   TRX Address............. 127.0.0.1
309 16 ttsou
   Channels................ 1
310
   Samples-per-Symbol...... 4
311
   External Reference...... Disabled
312
   Diversity............... Disabled
313
314 41 ttsou
-- Opening a [[UmTRX]] device...
315 13 ttsou
-- Current recv frame size: 1472 bytes
316 38 ttsou
-- Current send frame size: 1472 bytes
317 41 ttsou
-- Setting [[UmTRX]] 4 SPS
318 38 ttsou
-- Transceiver active with 1 channel(s)
319 41 ttsou
</pre>
320 38 ttsou
321 1 ttsou
322 49 neels
h2. [[OsmoTRX]] with [[OsmoBTS:OpenBTS]]
323 38 ttsou
324
325 49 neels
[[OsmoTRX]] is fully compatible with [[OsmoBTS:OpenBTS]] for voice and SMS services. Due to differences in handing of GPRS, [[OsmoTRX]] does not support GPRS when used with [[OsmoBTS:OpenBTS]], however, GPRS with the Osmocom stack is supported.
326 41 ttsou
327 49 neels
For use with [[OsmoBTS:OpenBTS]], enable the filler table option "Enable C0 filler table", which enables [[OsmoBTS:OpenBTS]] style idle bursts and retransmissions.
328 41 ttsou
329
<pre>
330 1 ttsou
$ osmo-trx -f
331 41 ttsou
</pre>
332 17 ttsou
333 49 neels
The [[OsmoTRX]] transceiver should be started before running [[OsmoBTS:OpenBTS]]. No symbolic link to './transceiver' should exist in the [[OsmoBTS:OpenBTS]] directory. This prevents [[OsmoBTS:OpenBTS]] from starting its own transceiver instance.
334 35 ttsou
335 1 ttsou
336 41 ttsou
h2. Benchmarks
337 1 ttsou
338 35 ttsou
339 49 neels
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 [[OsmoBTS:OpenBTS]] core.
340 35 ttsou
341 41 ttsou
*Repository*
342
343
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]].
344
345
<pre>
346 35 ttsou
$ git clone https://github.com/ttsou/trx-bench.git
347
348
$ cd trx-bench
349
$ autoreconf -i
350
$ ./configure [--with-neon] [--with-neon-vfp4]
351 1 ttsou
$ make
352
$ src/conv_test
353 35 ttsou
$ src/convert_test
354
$ src/convolve_test
355 41 ttsou
</pre>
356 35 ttsou
357
The convolutional decoding test includes command options including experimental support for benchmarking with multiple threads.
358
359 41 ttsou
<pre>
360 35 ttsou
$ ./conv_test -h
361
Options:
362
  -h    This text
363 1 ttsou
  -i    Number of iterations
364
  -j    Number of threads for benchmark (1 to 32)
365 13 ttsou
  -b    Run benchmark tests
366
  -a    Run validity checks
367
  -e    Run bit-error-rate tests
368 41 ttsou
</pre>
369 10 ttsou
370 1 ttsou
Selected benchmark results are provided below. All tests are run on a single core only.
371
372 41 ttsou
*Intel Haswell (i7 4770K 3.5 GHz)*
373 1 ttsou
374 41 ttsou
<pre>
375 1 ttsou
--- Floating point to integer conversions
376
-- Testing 40000 iterations of 3120 values
377
- Measuring conversion time
378
- Elapsed time base...                  0.065508 secs
379
- Validating SIMD conversion results... PASS
380 3 ttsou
- Measuring conversion time
381
- Elapsed time SIMD ...                 0.011424 secs
382
- Speedup...                            5.734244
383 41 ttsou
</pre>
384 1 ttsou
385 41 ttsou
<pre>
386 3 ttsou
[+] Testing: GSM TCH/AFS 7.95 (recursive, flushed, punctured)
387
[.] Input length  : ret = 165  exp = 165 -> OK
388
[.] Output length : ret = 448  exp = 448 -> OK
389
[.] Pre computed vector checks:
390
[..] Encoding: OK
391
[..] Decoding base: 
392
[..] Decoding SIMD: 
393 1 ttsou
[..] Code N 3
394
[..] Code K 7
395
OK
396
[.] Random vector checks:
397
[.] Testing baseline:
398 17 ttsou
[..] Encoding / Decoding 10000 cycles:
399
[.] Elapsed time........................ 1.435066 secs
400
[.] Rate................................ 3.121808 Mbps
401
[.] Testing SIMD:
402
[..] Encoding / Decoding 10000 cycles:
403
[.] Elapsed time........................ 0.073524 secs
404
[.] Rate................................ 60.932485 Mbps
405
[.] Speedup............................. 19.518334
406 41 ttsou
</pre>
407 17 ttsou
408 41 ttsou
*Intel Atom (D2500 1.86 GHz)*
409
<pre>
410 17 ttsou
--- Floating point to integer conversions
411
-- Testing 40000 iterations of 3120 values
412
- Measuring conversion time
413
- Elapsed time base...                 1.147449 secs
414 1 ttsou
- Validating SSE conversion results... PASS
415 17 ttsou
- Measuring conversion time
416 1 ttsou
- Elapsed time SSE ...                 0.347838 secs
417
- Quotient...                          3.298803
418 41 ttsou
</pre>
419 17 ttsou
420 41 ttsou
<pre>
421 1 ttsou
[+] Testing: GSM TCH/AFS 7.95 (recursive, flushed, punctured)
422
[.] Input length  : ret = 165  exp = 165 -> OK
423
[.] Output length : ret = 448  exp = 448 -> OK
424
[.] Pre computed vector checks:
425 17 ttsou
[..] Encoding: OK
426
[..] Decoding base: 
427
[..] Decoding SIMD: 
428
[..] Code N 3
429
[..] Code K 7
430
OK
431
[.] Random vector checks:
432 19 ttsou
[.] Testing baseline:
433
[..] Encoding / Decoding 10000 cycles:
434
[.] Elapsed time........................ 11.822688 secs
435 17 ttsou
[.] Rate................................ 0.378932 Mbps
436
[.] Testing SIMD:
437
[..] Encoding / Decoding 10000 cycles:
438
[.] Elapsed time........................ 0.550423 secs
439
[.] Rate................................ 8.139195 Mbps
440
[.] Speedup............................. 21.479277
441 41 ttsou
</pre>
442 17 ttsou
443 41 ttsou
*!ArndaleBoard (ARM Cortex-A15 1.7 GHz)*
444 17 ttsou
445
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.
446
447 41 ttsou
<pre>
448 17 ttsou
--- Floating point to integer conversions
449
-- Testing 40000 iterations of 3120 values
450
- Measuring conversion time
451
- Elapsed time base...                 0.384097 secs
452
- Validating SSE conversion results... PASS
453
- Measuring conversion time
454
- Elapsed time SSE ...                 0.100877 secs
455
- Quotient...                          3.807578
456 41 ttsou
</pre>
457 17 ttsou
458 41 ttsou
<pre>
459 17 ttsou
[+] Testing: GSM TCH/AFS 7.95 (recursive, flushed, punctured)
460
[.] Input length  : ret = 165  exp = 165 -> OK
461
[.] Output length : ret = 448  exp = 448 -> OK
462
[.] Pre computed vector checks:
463
[..] Encoding: OK
464
[..] Decoding base: 
465
[..] Decoding SIMD: 
466
[..] Code N 3
467
[..] Code K 7
468
OK
469
[.] Random vector checks:
470
[.] Testing baseline:
471
[..] Encoding / Decoding 10000 cycles:
472
[.] Elapsed time........................ 5.371288 secs
473
[.] Rate................................ 0.834064 Mbps
474 3 ttsou
[.] Testing SIMD:
475
[..] Encoding / Decoding 10000 cycles:
476
[.] Elapsed time........................ 1.016621 secs
477
[.] Rate................................ 4.406755 Mbps
478
[.] Speedup............................. 5.283471
479 41 ttsou
</pre>
480 3 ttsou
481 41 ttsou
*!BeagleBoard-xM (ARM Cortex-A8 800 MHz)*
482
<pre>
483 5 ttsou
--- Floating point to integer conversions
484 3 ttsou
-- Testing 40000 iterations of 3120 values
485
- Measuring conversion time
486
- Elapsed time base...                  6.292542 secs
487 4 ttsou
- Validating SIMD conversion results... PASS
488 3 ttsou
- Measuring conversion time
489
- Elapsed time SIMD ...                 0.839081 secs
490
- Quotient...                           7.499326
491 41 ttsou
</pre>
492 1 ttsou
493 41 ttsou
<pre>
494 31 ttsou
[+] Testing: GSM TCH/AFS 7.95 (recursive, flushed, punctured)
495
[.] Input length  : ret = 165  exp = 165 -> OK
496
[.] Output length : ret = 448  exp = 448 -> OK
497
[.] Pre computed vector checks:
498
[..] Encoding: OK
499
[..] Decoding base: 
500
[..] Decoding SIMD: 
501
[..] Code N 3
502
[..] Code K 7
503 1 ttsou
OK
504 32 ttsou
[.] Random vector checks:
505
[.] Testing baseline:
506
[..] Encoding / Decoding 10000 cycles:
507
[.] Elapsed time........................ 21.963257 secs
508
[.] Rate................................ 0.203977 Mbps
509
[.] Testing SIMD:
510
[..] Encoding / Decoding 10000 cycles:
511
[.] Elapsed time........................ 3.083282 secs
512
[.] Rate................................ 1.452997 Mbps
513
[.] Speedup............................. 7.123337
514 41 ttsou
</pre>
515 32 ttsou
516
517 41 ttsou
*Full Results*
518 32 ttsou
519 41 ttsou
"[http://tsou.cc/gsm/shuttle.txt":http://tsou.cc/gsm/haswell.txt]
520 31 ttsou
521 41 ttsou
"[http://tsou.cc/gsm/beagle.txt":http://tsou.cc/gsm/arndale.txt]
522 1 ttsou
523 30 ttsou
524 1 ttsou
525 41 ttsou
h2. Authors
526 1 ttsou
527
528 49 neels
[[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 [[OsmoBTS:OpenBTS]] project, which was originally developed by David Burgess and Harvind Samra at Range Networks.
Add picture from clipboard (Maximum size: 48.8 MB)