baseband-devel

baseband-devel@lists.osmocom.org

2023 discussions

"OsmoDevCall" on Nov 25, 2021: Control/User Plane Separation (CUPS) + PFCP
by Harald Welte 24 Nov '21

24 Nov '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at November 25, 2021 at 20:00 CET (yes, Thursday instead of Friday this time!) at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:10 presentation "Control/User Plane Separation (CUPS) + PFCP" by laforge 21:00 unstructured supplementary social event [*] Attendance is free of charge and open to anyone with an interest in Osmocom or open source cellular technologies. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 1

"OsmoDevCall" on Nov 12, 2021: icE1usb in practice
by Harald Welte 11 Nov '21

11 Nov '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at November 12, 2021 at 20:00 CET at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:10 presentation "E1 / TDM / PDH / SDH basics" by laforge 20:30 presentation "icE1usb in practice" by tnt later USSE: unstructured supplementary social event [*] Attendance is free of charge and open to anyone with an interest in Osmocom. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

Re: OsmoDevCon 2022 ?
by Harald Welte 06 Nov '21

06 Nov '21

Hi Kevin, On Fri, Nov 05, 2021 at 02:18:14PM +0100, Kévin Redon wrote: > I'm also happy to help with the recording and streaming of the public talks for those not able to join on site. thanks for that, as usual. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

Re: OsmoDevCon 2022 ?
by Neels Hofmeyr 04 Nov '21

04 Nov '21

> requiring vaccination to attend by default. Maybe with the option for attendees > to request attendance despite no vaccination, and then see whether we can > unanimously agree on that? I'd like to add that I find it should also be sufficient to have recovered from COVID. This is a common rule in schools in Berlin that does relieve teachers from the need to test regularly (called 2G, incidentally). Another question is whether we play by RKI rules and not accept certain vaccines. I guess we should first see whether anyone would be refused attendance based on these rules and take it from there? Here is a dudle to anonymously figure out the current vaccination status. Feel free to enter your current status, especially if you're not fully vaccinated and would like to attend. This is just to get a basis for discussion: https://dudle.inf.tu-dresden.de/w93G6NPqfA/ I guess we need to repeat such poll in early '22.

1 0

GSMTAP messages not generated
by Mario Lucas 30 Oct '21

30 Oct '21

Dear All, I am running a GSM stack: osmo-stp smo-msc osmo-hlr osmo-bsc osmo-bts-trx osmo-trx-lms It seems that my transmitter is emitting radio-waves into air (osmo-bts-trx and osmo-trx-lms communicate with each other through ports 5702 / 5802 — pls see attached printscreen), however i could not make GSMTAP tracing. Osmo-bts-trx does not send GSMTAP messages to port 4729. In most recent version of osmo-bts, GSMTAP tracing is arranged through config file: bts 0 gsmtap-remote-host 127.0.0.1 gsmtap-sapi ccch I could not run the GSMTAP tracing even in previous verions of osmo-bts where you have to specify in synopsis when you call a program: /usr/bin/osmo-bts-trx -s -c /etc/osmocom/osmo-bts-trx.cfg --gsmtap-ip 127.0.0.1 I thought may be i am having some issues in stack components behind osmo-bts for example in osmo-bsc or behind and i tried to run virtual bts. When i tried to run osmo-bts-virtual GSMTAP messages were visible in wireshark (please see attached file osmo-bts-virtual), therefore bts-bsc communication is good. However I still could not figure out why my osmo-bts-trx does not send GSMTAP messages. Or would you advise what log might be helpful to see what i am doing wrong …. Thank you for your always helpful assistance -- Mario Lucas

2 1

(bts=0,trx=0,ts=0,pchan_from_config=CCCH+SDCCH4,state=NOT_INITIALIZED) Abis RSL rx CCHAN: mismatching chan_nr=0x90
by Mario Lucas 22 Oct '21

22 Oct '21

When i try to run osmo-bts-trx i am getting following log in osmo-bsc abis_rsl.c:142 (bts=0,trx=0,ts=0,pchan_from_config=CCCH+SDCCH4,state=NOT_INITIALIZED) Abis RSL rx CCHAN: mismatching chan_nr=0x90 I tried to find out in bugs: https://osmocom.org/issues/4872 but could not understand … i am using osmo-bsc 1.7.1 and osmo-bts-trx 1.3.3 Could you pls advise me briefly whats happening and how to sort it out ? -- Mario Lucas

2 1

libmobile.a(mncc_sock.o) undefined reference
by Mario Lucas 16 Oct '21

16 Oct '21

Dear All, I am having following error during ‘make’ osmocombb: libmobile.a(mncc_sock.o): In function `mncc_sock_accept': /home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile/mncc_sock.c:229: undefined reference to `osmo_fd_read_disable' libmobile.a(mncc_sock.o): In function `mncc_sock_close': /home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile/mncc_sock.c:95: undefined reference to `osmo_fd_read_enable' libmobile.a(mncc_sock.o): In function `mncc_sock_write': /home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile/mncc_sock.c:159: undefined reference to `osmo_fd_write_disable' /home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile/mncc_sock.c:174: undefined reference to `osmo_fd_write_enable' libmobile.a(mncc_sock.o): In function `mncc_sock_from_cc': /home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile/mncc_sock.c:75: undefined reference to `osmo_fd_write_enable' libmobile.a(mncc_sock.o): In function `mncc_sock_write_pending': /home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile/mncc_sock.c:81: undefined reference to `osmo_fd_write_enable' collect2: error: ld returned 1 exit status Makefile:394: recipe for target 'mobile' failed make[3]: *** [mobile] Error 1 make[3]: Leaving directory '/home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile' Makefile:325: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src' Makefile:351: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23' Makefile:97: recipe for target 'host/layer23/layer23' failed make: *** [host/layer23/layer23] Error 2 My arm-elf-gcc is gcc version 4.5.2 (GCC) libosmocore 1.4.1 I believe it is something with libraries but could not figure out …. -- Mario Lucas

2 1

Announcement of "OsmoDevCall" on September 24, 2021
by Harald Welte 23 Sep '21

23 Sep '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at September 24, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "ISO 7816 smart card interface FPGA softcore" by tnt 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

Catching Frequency correction burst
by Mario Lucas 15 Sep '21

15 Sep '21

Dear Forum members i am not sure this question directly relates to Osmocom, but I don’t know where I can post it else …. If you know some active / alive technical forum which relates to GSM side (frequencies, modulations, GMSK etc etc) it would be very great if you could advise me ….. Meanwhile I ll continue with my question…. 51 TDMA multiframe starts with a FCCH which carries frequency correction burst on TS0. Due to nature of GMSK modulation and initial zeros of frequency correction burst the aired signal (signal that GSM modulator emits into air) as I understand is nothing but sine wave of an approximately 67Khz on top of the carrier frequency. Once mobile finds the frequency correction burst on some frequency it subtracts 67 Khz and precisely gets / sits on beacon frequency. So when it is said that upon switching the mobile phone on - it is looking for frequency correction bursts means in different words that it is looking for sine wave in GSM frequency interval it can work. Let’s say if my phone can work only in E-GSM900 interval (925 - 960 Mhz) it is looking for sine wave (frequency correction burst) and once finds it will subtract 67 Khz and it will be precisely the carrier frequency of beacon channel ? So if I use my rtl-sdr and software that analyzes RF spectrum (something like only oscilloscope) in 925 960 Mhz interval and I notice sine waves with periodic occurrence - as many times as FCCH appears in 51 multiframe - can I say that got frequency correction burst and subtracting 67 Khz I got beacon frequency ? -- Mario Lucas

1 0

osmo-bsc default config file time-slot TS0 configuration CCCH+SDCCH4 understanding
by Mario Lucas 11 Sep '21

11 Sep '21

Dear All, Could you please advise me based on what logic (how) can i decompose logical channel configuration CCCH+SDCCH4 which is mapped on TS0… ? So my understanding is as follows: There are 51 TDMA frames in multiframe, therefore i am having 51 consecutive TS0 slots. So CCCH+SDCCH4 should be redistributed in these 51 slots. SDCCH4 means that there are 4 SDCCH blocks, each block is having 4 bursts or 4 timeslots in another words (as i understand to transmit SDCCH «unit data» it is needed 4 burts), so 16 slots are occupied by SDCCH. Does it mean 51-16 = 35 slots to be occupied by CCCH ? If i use following notation CCCH=C, SDCCH1=S1, SDCCH2=S2, SDCCH3=S3 and SDCCH4=S4 does the decomposition looks like: CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC S1S1S1S1 S2S2S2S2 S3S3S3S3 S4S4S4S4 If so should not there be an idle slots … ? Thank you so much. -- Mario Lucas

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel