baseband-devel

baseband-devel@lists.osmocom.org

1982 discussions

Start a nNew thread

Aw: Re: Re: Compile error - osmocom-bb | No package 'libosmocore' found but libosmocore is installed

by Dennis Schneck

8 years, 6 months

Aw: Re: Compile error - osmocom-bb | No package 'libosmocore' found but libosmocore is installed

by Dennis Schneck

8 years, 6 months

Compile error - osmocom-bb | No package 'libosmocore' found but libosmocore is installed

by Dennis Schneck

Hello, I am suing Manjaro Linux (Arch Linux based) and do not get the osmocom-bb compiled. git clone https://github.com/osmocom/osmocom-bb cd osmocom-bb/src make .... .... checking pkg-config is at least version 0.9.0... yes checking for LIBOSMOCORE... no configure: error: Package requirements (libosmocore) were not met: No package 'libosmocore' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [Makefile:69: host/layer23/Makefile] Fehler 1 but libosmocore is compiled and installed ( /usr/local ) $ ls -la /usr/local/include/osmocom/ insgesamt 40 drwxr-xr-x 10 root root 4096 12. Feb 06:45 . drwxr-xr-x 3 root root 4096 12. Feb 06:45 .. drwxr-xr-x 2 root root 4096 12. Feb 06:45 codec drwxr-xr-x 2 root root 4096 12. Feb 06:45 core drwxr-xr-x 2 root root 4096 12. Feb 06:45 crypt drwxr-xr-x 2 root root 4096 12. Feb 06:45 ctrl drwxr-xr-x 3 root root 4096 12. Feb 06:45 gprs drwxr-xr-x 3 root root 4096 12. Feb 06:45 gsm drwxr-xr-x 2 root root 4096 12. Feb 06:45 sim drwxr-xr-x 2 root root 4096 12. Feb 06:45 vty $ ls -la /usr/local/lib/ insgesamt 3408 drwxr-xr-x 3 root root 4096 12. Feb 06:45 . drwxr-xr-x 11 root root 4096 16. Feb 2015 .. -rwxr-xr-x 1 root root 981 12. Feb 06:45 libosmocodec.la lrwxrwxrwx 1 root root 21 12. Feb 06:45 libosmocodec.so -> libosmocodec.so.0.0.0 lrwxrwxrwx 1 root root 21 12. Feb 06:45 libosmocodec.so.0 -> libosmocodec.so.0.0.0 -rwxr-xr-x 1 root root 26968 12. Feb 06:45 libosmocodec.so.0.0.0 -rwxr-xr-x 1 root root 945 12. Feb 06:45 libosmocore.la lrwxrwxrwx 1 root root 20 12. Feb 06:45 libosmocore.so -> libosmocore.so.8.0.0 lrwxrwxrwx 1 root root 20 12. Feb 06:45 libosmocore.so.8 -> libosmocore.so.8.0.0 -rwxr-xr-x 1 root root 441216 12. Feb 06:45 libosmocore.so.8.0.0 -rwxr-xr-x 1 root root 1033 12. Feb 06:45 libosmoctrl.la lrwxrwxrwx 1 root root 20 12. Feb 06:45 libosmoctrl.so -> libosmoctrl.so.0.0.0 lrwxrwxrwx 1 root root 20 12. Feb 06:45 libosmoctrl.so.0 -> libosmoctrl.so.0.0.0 -rwxr-xr-x 1 root root 100072 12. Feb 06:45 libosmoctrl.so.0.0.0 -rwxr-xr-x 1 root root 1021 12. Feb 06:45 libosmogb.la lrwxrwxrwx 1 root root 18 12. Feb 06:45 libosmogb.so -> libosmogb.so.4.0.0 lrwxrwxrwx 1 root root 18 12. Feb 06:45 libosmogb.so.4 -> libosmogb.so.4.0.0 -rwxr-xr-x 1 root root 430400 12. Feb 06:45 libosmogb.so.4.0.0 -rwxr-xr-x 1 root root 969 12. Feb 06:45 libosmogsm.la lrwxrwxrwx 1 root root 19 12. Feb 06:45 libosmogsm.so -> libosmogsm.so.6.1.0 lrwxrwxrwx 1 root root 19 12. Feb 06:45 libosmogsm.so.6 -> libosmogsm.so.6.1.0 -rwxr-xr-x 1 root root 957032 12. Feb 06:45 libosmogsm.so.6.1.0 -rwxr-xr-x 1 root root 1018 12. Feb 06:45 libosmosim.la lrwxrwxrwx 1 root root 19 12. Feb 06:45 libosmosim.so -> libosmosim.so.0.0.0 lrwxrwxrwx 1 root root 19 12. Feb 06:45 libosmosim.so.0 -> libosmosim.so.0.0.0 -rwxr-xr-x 1 root root 175416 12. Feb 06:45 libosmosim.so.0.0.0 -rwxr-xr-x 1 root root 969 12. Feb 06:45 libosmovty.la lrwxrwxrwx 1 root root 19 12. Feb 06:45 libosmovty.so -> libosmovty.so.3.0.0 lrwxrwxrwx 1 root root 19 12. Feb 06:45 libosmovty.so.3 -> libosmovty.so.3.0.0 -rwxr-xr-x 1 root root 378280 12. Feb 06:45 libosmovty.so.3.0.0 -rw-r--r-- 1 root root 578174 6. Jan 2016 libphysfs.a lrwxrwxrwx 1 root root 14 6. Jan 2016 libphysfs.so -> libphysfs.so.1 lrwxrwxrwx 1 root root 18 6. Jan 2016 libphysfs.so.1 -> libphysfs.so.2.0.3 -rwxr-xr-x 1 root root 340504 6. Jan 2016 libphysfs.so.2.0.3 $ pacman -Ss arm- community/arm-none-eabi-binutils 2.27-2 [Installiert] A set of programs to assemble and manipulate binary and object files for the ARM EABI (bare-metal) target community/arm-none-eabi-gcc 6.3.0-1 [Installiert] The GNU Compiler Collection - cross compiler for ARM EABI (bare-metal) target community/arm-none-eabi-gdb 7.12-3 [Installiert] The GNU Debugger for the ARM EABI (bare-metal) target community/arm-none-eabi-newlib 2.5.0-1 [Installiert] A C standard library implementation intended for use on embedded systems (ARM bare metal) What did i wrong ? Thanks

8 years, 6 months

Re: Why not have the “sim spoof MS” command in now OSMOCOM-BB

by Etraud

Hi! Which branch was that code in? Thank you. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Why-not-have-the-sim-spoof-MS-co… Sent from the baseband-devel mailing list archive at Nabble.com.

8 years, 6 months

Downtime due FreeBSD upgrade.

by Holger Freyther

Hi, the machine hosting most of *.osmocom.org is running FreeBSD9.3 which EOLed end of december and I would like to upgrade to FreeBSD10.3. I do not expect many problems but I also don't want to interfere with other peoples work. Even if it is short notice, any objections for Saturday->Sunday night of a European timezone? Otherwise I would pick next Friday->Saturday. regards holger

8 years, 7 months

osmocom-BB

by salar007

Hi all, 1) Is it possible to increase the number of phones from two to three or more phones as TS in osmocom-BB? plz answer just this question. I strongly need it's answer, if NOT I STOP my working.. 2) what's this ERROR : "DSP Error Status: 24" thank you. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/osmocom-BB-tp4026767.html Sent from the baseband-devel mailing list archive at Nabble.com.

8 years, 7 months

Contribute to Osmocom and receive a free 3.5G femtocell

by Harald Welte

Dear all, not everyone might have seen the news item that was posted in late December on our website at http://osmocom.org/news/62 I'm looking forward to receiving your proposal on how you would contribute to the Osmocom project if you were to receive one of those free 3.5G femtocells. Quote of the news item below: ------ So please excuse me to cross-post this over several Osmocom project mailing lists. I know that a number of people have either hacked on femtocells in the past, or at least expressed interest in doing so... Osmocom's support for 2G/GSM is mature and widespread. Since 2016, we're taking on the next level: 3G/3.5G. The key to running your own 3G network is to obtain actual 3G cell hardware -- here is an exciting opportunity to get started: No less than 50 femtocells will be given away for free by sysmocom, one of the main drivers of the Osmocom project. To receive a free 3G femtocell, tell us how you will help the Osmocom project drive 3.5G forward if you had one, before the end of January 2017. This marks the launch of the 3.5G Acceleration Project, backed by the Osmocom community. Join us! Find further details on the 3.5G Acceleration Project and receiving your own 3G femtocell for free at https://sysmocom.de/downloads/accelerate_3g5_cfp.pdf. ------ Best regards and happy hacking, Harald Welte -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

8 years, 8 months

Moving from trac to a single redmine

by Holger Freyther

Hi guys, I think some of us would like to move to redmine and start using public tickets more frequently. So in case we move there are some topics to be discussed and I would like to start with a couple of them right now. Tickets: Redmine has a global linear sequence of ticket numbers. If we move from many tracs to a single redmine we can either: * not import tickets * only import from one project * deal with changing ticket numbers In terms of installations the GMR trac is broken in regard to tickets, there are some for SDR that are probably not being fixed anytime soon, baseband might be relevant and OpenBSC is unlikely to be relevant. I don't think we have ever used ticket reference in OpenBSC commit messages so in terms of OpenBSC having changing ticket numbers would not be a big deal. E.g. we could add a custom field with the old trac number? Wiki: We have external references that should be redirected to the new place. Is there any way besides maintaining a list in the apache2/nginx configuration and making redirects as we find broken references? Can we proactively manage this? Is anybody willing to come up with a script and nginx configuration for doing this? kind regards holger

8 years, 8 months

More phones through Transceiver

by salar007

Hi all, I've a question about transceiver module in osmocomBB.. I'm gonna to increase the number of TS as the number of connected phones.. now I'll be able to sync 2 phones but in order to have more TS => more traffic channel , I should be able to sync more phones as TS , how can I? plz help me.. tanx. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/More-phones-through-Transceiver-… Sent from the baseband-devel mailing list archive at Nabble.com.

8 years, 8 months

Calypso BTS: my phone my phone doesn't see my base station

by phreaker1983

hi guys, my phone doesn't see my base station.. To start I used : 1. First terminal: ~/osmocombb/trx/src# sudo host/osmocon/osmocon -m c123xor -p /dev/ttyUSB0 -c target/firmware/board/compal_e88/trx.highram.bin -r 99 2. Second terminal: ~/osmocombb/trx/src/host/layer23/src/transceiver# sudo ./transceiver -a 40 -r 99 Then I showed <0012> l1ctl.c:383 Reset received: Starting sync. <0012> l1ctl.c:338 Sync acquired, setting BTS mode ... <0011> trx.c:194 TRX CLK Indication 1890062 <0011> trx.c:194 TRX CLK Indication 1890113 <0011> trx.c:194 TRX CLK Indication 1890164 <0011> trx.c:194 TRX CLK Indicatn 1890215 ........ 3. third terminal: osmo-nitb -c ~/.osmocom/open-bsc.cfg -l ~/.osmocom/hlr.sqlite3 -P -C —debug=DRLL:DCC:DMM:DRR:DRSL:DNM DB: Database initialized. DB: Database prepared. My open-bsc.cfg contains: ! OpenBSC configuration saved from vty ! ! password foo ! line vty no login ! e1_input e1_line 0 driver ipa network network country code 1 mobile network code 1 short name OpenBSC long name OpenBSC auth policy closed location updating reject cause 13 encryption a5 0 neci 1 rrlp mode none mm info 1 handover 0 handover window rxlev averaging 10 handover window rxqual averaging 1 handover window rxlev neighbor averaging 10 handover power budget interval 6 handover power budget hysteresis 3 handover maximum distance 9999 timer t3101 10 timer t3103 0 timer t3105 0 timer t3107 0 timer t3109 4 timer t3111 0 timer t3113 60 timer t3115 0 timer t3117 0 timer t3119 0 timer t3141 0 bts 0 type sysmobts band DCS1800 cell_identity 0 location_area_code 1 training_sequence_code 7 base_station_id_code 63 ms max power 15 cell reselection hysteresis 4 rxlev access min 0 channel allocator ascending rach tx integer 9 rach max transmission 7 ip.access unit_id 1801 0 oml ip.access stream_id 255 line 0 gprs mode none trx 0 rf_locked 0 arfcn 514 nominal power 23 max_power_red 20 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 timeslot 1 phys_chan_config SDCCH8 timeslot 2 phys_chan_config TCH/F timeslot 3 phys_chan_config TCH/F timeslot 4 phys_chan_config TCH/F timeslot 5 phys_chan_config TCH/F timeslot 6 phys_chan_config TCH/F timeslot 7 phys_chan_config TCH/F arfcn I chose the 514..... 4. fourth terminal: cd /osmocombb/osmo-bts/src/osmo-bts-trx osmo-bts-trx -c ~/.osmocom/osmo-bts.cfg showed me: ((*)) | / \ OsmoBTS <0017> control_if.c:693 CTRL at 127.0.0.1 4238 <0010> telnet_interface.c:95 telnet at 127.0.0.1 4241 <0012> input/ipaccess.c:881 enabling ipaccess BTS mode <0006> phy_link.c:58 PHY link state change shutdown -> connectiong <0006> scheduler.c:174 Init scheduler for trx=0 <000b> trx_if.c:584 Open transceiver for phy0.0 <0006> phy_link.c:58 PHY link state change connectiong -> connected <0006> phy_link.c:68 trx_set_avail(1) <0006> scheduler_trx.c:1514 GSM clock skew: old fn=0, new fn=1908169 <0006> scheduler_trx.c:1519 GSM clock jitter: -691 <0006> scheduler_trx.c:1519 GSM clock jitter: 128 <0006> scheduler_trx.c:1519 GSM clock jitter: 674 <0006> scheduler_trx.c:1519 GSM clock jitter: 204 <0006> scheduler_trx.c:1519 GSM clock jitter: 467 <0006> scheduler_trx.c:1519 GSM clock jitter: -1620 <0006> scheduler_trx.c:1519 GSM clock jitter: 1362 <0006> scheduler_trx.c:1519 GSM clock jitter: -668 <0006> scheduler_trx.c:1519 GSM clock jitter: -846 <0006> scheduler_trx.c:1519 GSM clock jitter: 519 <0006> scheduler_trx.c:1519 GSM clock jitter: 457 <0006> scheduler_trx.c:1519 GSM clock jitter: 384 <0006> scheduler_trx.c:1519 GSM clock jitter: 218 ..... My osmo-bts.cfg contains: !OsmoBTS (0.0.1.100-0455) configuration saved from vty !! ! phy 0 instance 0 bts 0 band DCS1800 ipa unit-id 1801 0 oml remote-ip 192.168.100.11 trx 0 phy 0 instance 0 Where I erred? Thank you. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Calypso-BTS-my-phone-my-phone-do… Sent from the baseband-devel mailing list archive at Nabble.com.

8 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel