OpenBSC January 2018

openbsc@lists.osmocom.org

29 participants
52 discussions

libosmocore wiki page and doxygen online documentation
by Pau Espin Pedrol 18 Jan '18

18 Jan '18

Hi, I was trying to find if the doxygen documentation is uploaded and publicly available somewhere in some web server. Google pointed me to this libosmocore wiki page: ftp://ftp.osmocom.org/api/latest/libosmonetif/ In there, there are several links to stuff like http://www.osmocom.org/doc/libosmocore/latest/html/, but I get access forbidden when trying to use that one. On the other hand, I found somewhere else a link to http://ftp.osmocom.org/api/latest/libosmonetif/html/ which seems to be working. Now the question is: which is the expected way to access the documentation? should "www.osmocom.org" work instead of having to use "ftp.osmocom.org"? -- - Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

2 1

OSmux ideas implementation
by Rafael Diniz 17 Jan '18

17 Jan '18

Hi people, Is there anything implemented from the OSmux[1] ideas? [1] http://ftp.osmocom.org/docs/latest/osmux-reference.pdf Thanks, Rafael Diniz

2 2

Help required for non-sync Handover
by Muhammad Awais Aslam 16 Jan '18

16 Jan '18

Hi, We have manged to decode the BSIC in dedicated mode which were not implemented before. Now we are working on the synchronize and non-synchronize Handover. Once we send the fake measurement report to the BTS we get a handover command from the network. That could be synchronized or non-synchronized. In case of synchronized hand over, without making any changes in the TPU clock offset and the frame number and frequency correction, we are able to complete the handover process most of the time. In case of non-synchronized handover, a physical info is required from the network when mobile station would send Handover access burst to the network before the timer expires but we never get physical info during this period. Here we are stuck. Changes: for non-synchronized handover we need to change the TPU offset and frequency correction offset and frame number parameters which we stored during the BSIC decoding. We set these values before we send handover access burst to the network but no success. Anybody who is working on the handover currently or in the past can discuss these things with me so we can figure out why we are not getting the physical info during the non-sync handover. I have also attached the main changed files with this email. I hope someone would give advice how to debug the issue. Regards M. Awais

3 6

binary packages problem
by Rafael Diniz 16 Jan '18

16 Jan '18

Hi all, Anyone experiencing this error in Latest packages (Debian 9): "The following packages have unmet dependencies: osmo-mgw : Depends: libosmo-mgcp0 but it is not installable" Nightly works great thou. Cheers, Rafael Diniz

2 1

stow fallout, problem in osmo-bts-sysmo build
by Neels Hofmeyr 16 Jan '18

16 Jan '18

In osmo-bts, we just have the configure flag --enable-sysmocom-bts, and don't pass a header include location. i.e. we expect the header files to exist locally. I'm a bit stumped on why introducing stow would cause this to break. IIUC stow should only affect the installed dependencies, while the sysmocom headers are just placed in a local dir? If we can't fix the osmo-bts build quickly, we'll have to revert the stow patch until that works. https://jenkins.osmocom.org/jenkins/view/master/job/master-osmo-bts/36/BTS_… The build scripts are (obviously) in osmo-bts/contrib/ and osmo-ci/scripts. Any help is appreciated. ~N

2 2

External USSD interface development
by Vadim Yanitskiy 16 Jan '18

16 Jan '18

Dear Harald, In this mail I would like to express my thoughts and ideas regarding to the 'external interface for USSD'. To provide some background for other mailing list members, who are not aware of this topic, I'll explain it in a few sentences. We already have an external interface for SMS - SMPP. But unfortunately, the same cannot be said about USSD. There is no built-in support of any interface, which could be used to handle USSD requests in a separate application. So, at the moment we only handle *#100# (own number request), which is implemented as a part of both OsmoMSC and legacy OsmoNiTB. And if one would like to implement additional USSD commands, it's required to modify and recompile the whole project :/ Fairwaves team already have some draft implementation for legacy OsmoNiTB, which relays on the libosmocore's GSM 04.80 API. And having the external interface in the mainline would be great not only for Fairwaves, but for the whole Osmocom project and its users. The problem is that the current libosmocore's GSM 04.80 API is not complete and requires some critical modifications, which of course cannot be integrated immediately. Moreover, this implementation doesn't follow Osmocom coding style, for example, unlike other functions, where return code rc = 0 means success, there it means error... So, first of all, we need to know, how many projects are using the current API, especially non-Osmocom projects. After that (taking it into account), it shall be decided: - Should we keep the old API / ABI and maintain all new features among with it. This way would force us to duplicate the existing code and use different symbols. Then the old API would continuously became deprecated... - Should we make all the critical changes in the current API (increasing the libosmocore version?). This way would break builds of dependent projects and would suppose fixing compatibility with the new API. But, at the same time, the implementation would be cleaner and closer to the specification, without any deprecated duplication... Personally, I prefer the second way. At the same time, I want to make the modification as much transparent as possible. Speaking about Osmocom projects, the only users of the GSM 04.80 API are OsmoMSC and legacy OsmoNiTB. Both projects utilize it for '*#100#' handling only :/ To be more convincing, let's look at the following code: #define MAX_LEN_USSD_STRING 31 struct ss_request { uint8_t opcode; uint8_t ss_code; uint8_t ussd_text[MAX_LEN_USSD_STRING + 1]; uint8_t transaction_id; uint8_t invoke_id; }; This is what the current API allows you to obtain from a SS-request (e.g. '*#100#') coming from user. And what's wrong here? - The 'ss_request' doesn't indicate a part of the library it comes from. Would be better to use 'gsm0480_ss_request'. - The 'ussd_text' length doesn't follow the specification, where USSD OCTET STRING length is 160 bytes. So, the amount of characters depends on used coding scheme. - The information about SS-message type, component type, text length and used DCS (Data Coding Scheme), etc. is missing. Despite it could be important for the external application. So, let's discuss together all the 'pros and cons', and decide together, how should we facilitate the external USSD interface development. With best regards, Vadim Yanitskiy.

5 5

osmo-bsc_nat dropped in unrelated patch
by Neels Hofmeyr 16 Jan '18

16 Jan '18

Hi dexter, reading a commit of yours apparently merged to osmo-bsc in November, I notice that you "secretly sneaked in" this: diff --git a/src/Makefile.am b/src/Makefile.am index d04f025..dd1ad3d 100644 --- a/src/Makefile.am +++ b/src/Makefile.am @@ -33,5 +33,4 @@ SUBDIRS += \ utils \ ipaccess \ osmo-bsc \ - osmo-bsc_nat \ $(NULL) in a patch that was supposed to "mgcp: use osmo-mgw to switch RTP streams". http://git.osmocom.org/osmo-bsc/commit/?id=39c609b7c924524172ad311bdf89f92b… So since we merged that patch, osmo-bsc_nat is no longer part of the osmo-bsc build. That's certainly not intended, is it? Confirm and please fix that. thx! ~N

2 1

USRP2 and OsmoTRX
by Rafael Diniz 16 Jan '18

16 Jan '18

Hi people, I'm doing some tests with an old USRP2 + RF900 daughterboard, and I get a very unstable system (with osmo-trx, osmo-bts-trx and osmo-nitb) - some phones can connect, some dont. I'd like to identify the problem - is it a bad GBit ethernet or the lack of a GPSDO connected to the 10MHz port? Here is osmo-trx startup: +++ Info: SSE3 support compiled in and supported by CPU Info: SSE4.1 support compiled in and supported by CPU Config Settings Log Level............... DEBUG Device args............. TRX Base Port........... 5700 TRX Address............. 127.0.0.1 GSM Core Address.........127.0.0.1 Channels................ 1 Tx Samples-per-Symbol... 4 Rx Samples-per-Symbol... 1 EDGE support............ Disabled Reference............... Internal C0 Filler Table......... Disabled Multi-Carrier........... Disabled Tuning offset........... 0 RSSI to dBm offset...... 0 Swap channels........... 0 INFO 140529100949376 09:57:53.4 UHDDevice.cpp:623:open: Using discovered UHD device type=usrp2,addr=192.168.10.2,name=,serial=024N11043 -- Opening a USRP2/N-Series device... -- Current recv frame size: 1472 bytes -- Current send frame size: 1472 bytes INFO 140529100949376 09:57:54.6 UHDDevice.cpp:441:set_rates: Rates configured for N2XX 4/1 Tx/Rx SPS INFO 140529100949376 09:57:54.7 UHDDevice.cpp:401:init_gains: Supported Tx gain range [0; 0] INFO 140529100949376 09:57:54.7 UHDDevice.cpp:406:init_gains: Supported Rx gain range [0; 70] INFO 140529100949376 09:57:54.7 UHDDevice.cpp:410:init_gains: Default setting Tx gain for channel 0 to 0 INFO 140529100949376 09:57:54.7 UHDDevice.cpp:417:init_gains: Default setting Rx gain for channel 0 to 35 INFO 140529100949376 09:57:54.7 UHDDevice.cpp:712:open: Single USRP: Device: USRP2 / N-Series Device Mboard 0: USRP2 r4 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: RFX900 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: RFX900 TX -- Transceiver active with 1 channel(s) +++ From osmo-trx I get millions of messages: +++ DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.1 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 7:1142324 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 0:1142349 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 0:1142325 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 1:1142349 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 2:1142349 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 3:1142349 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 4:1142349 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 5:1142349 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 6:1142349 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 7:1142349 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 2:1142325 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 4:1142325 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 6:1142325 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 7:1142325 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 0:1142350 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 0:1142326 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 1:1142350 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 2:1142350 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 3:1142350 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 4:1142350 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 5:1142350 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 6:1142350 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 7:1142350 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 2:1142326 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 4:1142326 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 6:1142326 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 7:1142326 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 0:1142351 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 0:1142327 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 1:1142351 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 2:1142351 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 3:1142351 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 4:1142351 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 5:1142351 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 6:1142351 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 7:1142351 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 3:1142327 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 4:1142327 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 6:1142327 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 7:1142327 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 0:1142352 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 1:1142352 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 0:1142328 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 2:1142352 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 3:1142352 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 4:1142352 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 5:1142352 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 6:1142352 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 7:1142352 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 3:1142328 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 4:1142328 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 6:1142328 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 7:1142328 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 0:1142353 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 1:1142353 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 0:1142329 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 2:1142353 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 3:1142353 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 4:1142353 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 5:1142353 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 6:1142353 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 7:1142353 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 3:1142329 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 4:1142329 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 6:1142329 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 7:1142329 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 0:1142354 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 1:1142354 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 2:1142354 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 3:1142354 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 0:1142330 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 4:1142354 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 5:1142354 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 6:1142354 DEBUG 140529099826944 10:02:27.4 Transceiver.cpp:852:driveTxPriorityQueue: rcvd. burst at: 7:1142354 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 3:1142330 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 4:1142330 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:946:readSamples: Received timestamp = 32693.2 DEBUG 140529101072128 10:02:27.4 Transceiver.cpp:960:driveTxFIFO: radio clock 6:1142330 DEBUG 140529101039360 10:02:27.4 UHDDevice.cpp:902:readSamples: Requested timestamp = 32693.2 +++ and from osmo-bts-trx: +++ (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127677/850/05/16/45 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127677/850/05/16/45 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127683/850/11/22/03 (bts=0,trx=0,ts=0) SDCCH/4(0): PH-RTS.ind: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:418 1127683/850/11/22/03 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:480 1127714/850/16/02/34 (bts=0,trx=0,ts=0) BCCH: PH-RTS.ind: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:418 1127714/850/16/02/34 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:480 1127718/850/20/06/38 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127718/850/20/06/38 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127724/850/00/12/44 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127724/850/00/12/44 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127728/850/04/16/48 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127728/850/04/16/48 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127734/850/10/22/02 (bts=0,trx=0,ts=0) SDCCH/4(0): PH-RTS.ind: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:418 1127734/850/10/22/02 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:480 1127754/850/04/42/22 (bts=0,trx=0,ts=0) SACCH/4(0): PH-RTS.ind: chan_nr=0x20 link_id=0x40 <0007> scheduler.c:418 1127754/850/04/42/22 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x20 link_id=0x40 <0007> scheduler.c:480 1127765/850/15/02/33 (bts=0,trx=0,ts=0) BCCH: PH-RTS.ind: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:418 1127765/850/15/02/33 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:480 1127769/850/19/06/37 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127769/850/19/06/37 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0006> scheduler_trx.c:1619 TRX Clock Ind: elapsed_us= 997110, elapsed_fn=217, error_us=-4345 <0006> scheduler_trx.c:1637 GSM clock jitter: 3322 us (elapsed_fn=1) <0007> scheduler.c:480 1127775/850/25/12/43 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127775/850/25/12/43 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0006> scheduler_trx.c:1660 We were 1 FN slower than TRX, compensated <0007> scheduler.c:480 1127779/850/03/16/47 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127779/850/03/16/47 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127785/850/09/22/01 (bts=0,trx=0,ts=0) SDCCH/4(0): PH-RTS.ind: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:418 1127785/850/09/22/01 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:480 1127816/850/14/02/32 (bts=0,trx=0,ts=0) BCCH: PH-RTS.ind: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:418 1127816/850/14/02/32 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:480 1127820/850/18/06/36 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127820/850/18/06/36 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127826/850/24/12/42 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127826/850/24/12/42 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127830/850/02/16/46 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127830/850/02/16/46 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127836/850/08/22/00 (bts=0,trx=0,ts=0) SDCCH/4(0): PH-RTS.ind: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:418 1127836/850/08/22/00 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:480 1127856/850/02/42/20 (bts=0,trx=0,ts=0) SACCH/4(0): PH-RTS.ind: chan_nr=0x20 link_id=0x40 <0007> scheduler.c:418 1127856/850/02/42/20 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x20 link_id=0x40 <0007> scheduler.c:480 1127867/850/13/02/31 (bts=0,trx=0,ts=0) BCCH: PH-RTS.ind: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:418 1127867/850/13/02/31 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:480 1127871/850/17/06/35 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127871/850/17/06/35 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127877/850/23/12/41 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127877/850/23/12/41 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127881/850/01/16/45 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127881/850/01/16/45 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127887/850/07/22/51 (bts=0,trx=0,ts=0) SDCCH/4(0): PH-RTS.ind: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:418 1127887/850/07/22/51 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:480 1127918/850/12/02/30 (bts=0,trx=0,ts=0) BCCH: PH-RTS.ind: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:418 1127918/850/12/02/30 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:480 1127922/850/16/06/34 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127922/850/16/06/34 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127928/850/22/12/40 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127928/850/22/12/40 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127932/850/00/16/44 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127932/850/00/16/44 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127938/850/06/22/02 (bts=0,trx=0,ts=0) SDCCH/4(0): PH-RTS.ind: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:418 1127938/850/06/22/02 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:480 1127958/850/00/42/22 (bts=0,trx=0,ts=0) SACCH/4(0): PH-RTS.ind: chan_nr=0x20 link_id=0x40 <0007> scheduler.c:418 1127958/850/00/42/22 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x20 link_id=0x40 <0007> scheduler.c:480 1127969/850/11/02/33 (bts=0,trx=0,ts=0) BCCH: PH-RTS.ind: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:418 1127969/850/11/02/33 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:480 1127973/850/15/06/37 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127973/850/15/06/37 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127979/850/21/12/43 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127979/850/21/12/43 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127983/850/25/16/47 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1127983/850/25/16/47 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:480 1127989/850/05/22/01 (bts=0,trx=0,ts=0) SDCCH/4(0): PH-RTS.ind: chan_nr=0x20 link_id=0x00 <0007> scheduler.c:418 1127989/850/05/22/01 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x20 link_id=0x00 <0006> scheduler_trx.c:1619 TRX Clock Ind: elapsed_us= 998173, elapsed_fn=216, error_us=+1333 <0006> scheduler_trx.c:1637 GSM clock jitter: -2537 us (elapsed_fn=0) <0000> rsl.c:2458 (bts=0,trx=0,ts=0,ss=0) Rx RSL DEACTIVATE_SACCH <0006> l1sap.c:1394 deactivating sacch chan_nr=0x20 trx=0 <0006> scheduler.c:1383 Deactivating SACCH/4(0) on trx=0 ts=0 <0000> rsl.c:2458 (bts=0,trx=0,ts=0,ss=0) Rx RSL RF_CHAN_REL <0006> l1sap.c:1378 deactivating channel chan_nr=0x20 trx=0 <0006> scheduler.c:1383 Deactivating SDCCH/4(0) on trx=0 ts=0 <0006> l1sap.c:602 deactivate confirm chan_nr=0x20 trx=0 <0000> rsl.c:580 (bts=0,trx=0,ts=0,ss=0) Tx RF CHAN REL ACK <0007> scheduler.c:480 1128020/850/10/02/32 (bts=0,trx=0,ts=0) BCCH: PH-RTS.ind: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:418 1128020/850/10/02/32 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0x80 link_id=0x00 <0007> scheduler.c:480 1128024/850/14/06/36 (bts=0,trx=0,ts=0) CCCH: PH-RTS.ind: chan_nr=0x90 link_id=0x00 <0007> scheduler.c:418 1128024/850/14/06/36 (bts=0,trx=0,ts=0) : PH-DATA.req: chan_nr=0 +++ From NITB: +++ Mon Jan 15 10:04:11 2018 <0005> abis_nm.c:507 BTS0 feature 'EGPRS' reported via OML does not match statically set feature: 0 != 1. Please fix. Mon Jan 15 10:04:11 2018 <0005> abis_nm.c:507 BTS0 feature 'OML Alerts' reported via OML does not match statically set feature: 1 != 0. Please fix. Mon Jan 15 10:04:11 2018 <0005> abis_nm.c:573 BTS0: ARI reported sw[0/2]: sysmobts is 0.7.0.20180114 Mon Jan 15 10:04:11 2018 <0005> abis_nm.c:446 BTS0 reported variant: omso-bts-trx Mon Jan 15 10:04:11 2018 <0005> abis_nm.c:468 BTS0 Attribute Manufacturer Dependent State is unreported Mon Jan 15 10:04:11 2018 <0005> abis_nm.c:573 BTS0: ARI reported sw[0/1]: TRX_PHY_VERSION is Unknown +++ And after some time, osmo-trx stops reading samples from UHD and osmo-bts-trx shuts down. Thanks, Rafael Diniz

2 4

osmo-trx test setup & convolve_test failures on different machines
by Pau Espin Pedrol 15 Jan '18

15 Jan '18

Hi everybody, as some of you may have noticed due to the generated noise in gerrit ml during last days, I have been adding some autotest setup to osmo-trx in order to have several tests being run during gerrit review. Since osmo-trx has some specific code built with NEON instructions, I also added some infrastructure to jenkin.sh to generate and use a prebuilt debian armhf rootfs so we can easily build and run tests using qemu-arm from our local workstations or from jenkins slaves, which will check that support for those architectures doesn't become broken. In order to set up the make check tests, I re-used existing tests and moved them to the tests/ directory. I also moved utils/convolvtest/main.c into "tests/Transceiver52M/convolve_test" [1] to become a test that checks "convolve_{real,complex}" APIs. I noticed, however, that this test prints slightly (or not that slightly) different outputs on different machine architectures, which of course make tests fail as it matches the exact values. So far the output is different in my x86_64 workstation, my i686 netbook (or i586 OBS host) and in my qemu-arm (armhf). As each machine uses different instructions sets, I indeed can understand that there appear small differences due to floating operations and rounding, but sometimes I can see relatively big difference between one implementation and the other one (eg 7.032490 vs 6.655972). I'm thinking about modifying the test to, instead of matching the output exactly, check that for each value in the vector it is similar to a value with a maximum epsilon distance from a reference vector. However, as I don't have any knowledge regarding the maths and theory behind the convolution codes, I must admit I am not sure which epsilon should I be using, or which should be the expected output for the test. It may perhaps make sense to have separate reference output for different architectures, I don't know. Can somebody shed some light on this topic? Any advise or hint is welcome. It would also be nice to have some tests for the "convert" API, which uses optimized instructions sets too. If somebody wants to provide those or any hint on how to implement them that's going to be handy. All the test infrastructure is merged now, only the patch adding the qemu part is not merged but already working in [2], I'll merge it tomorrow if nobody is angry with it. You can find related output for the test I was speaking of for different machine arch (x86_64, i686, arm) in [3] and [4]. [1]https://git.osmocom.org/osmo-trx/tree/tests/Transceiver52M/convolve_test.c [2] https://gerrit.osmocom.org/#/c/5763 [3] https://osmocom.org/issues/2826 [4] https://osmocom.org/issues/2828 -- - Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

1 0

Re: [osmocom/gr-osmosdr] Sdrplay2 (#12)
by Neels Hofmeyr 15 Jan '18

15 Jan '18

The github robot is still telling people to submit patches on the mailing lists. Can we please change that message to link to this wiki page instead? http://osmocom.org/projects/cellular-infrastructure/wiki/Coding_standards#S… Thanks! ~N On Fri, Jan 12, 2018 at 09:17:53AM -0800, tsaitgaist wrote: > GitHub is only used to mirror [osmocom projects](http://git.osmocom.org/). Please use the [mailing lists](https://lists.osmocom.org/mailman/listinfo) to [submit patches](http://projects.osmocom.org/projects/cellular-infrastructure/wiki/…. > > -- > You are receiving this because you are subscribed to this thread. > Reply to this email directly or view it on GitHub: > https://github.com/osmocom/gr-osmosdr/pull/12#issuecomment-357299416

3 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC January 2018