baseband-devel

baseband-devel@lists.osmocom.org

2022 discussions

no transceiver binary inside src/host/layer23/src/transceiver folder after running make
by Miguel Rios 14 Jun '13

14 Jun '13

Hi list, I'm trying to experiment with Sylvain's transceiver as per the wiki here http://bb.osmocom.org/trac/wiki/Software/Transceiver I think that I may be doing something wrong when making in that I can see no transceiver binary inside /osmocom-bb/src/host/layer23/src/transceiver. The host/layer23/src/transceiver folder is created properly. After running make HOST_layer23_CONFARGS=--enable-transceiver, I don't see any transceiver binary in there, so naturally OpenBTS fails when I execute the exec <your path to osmocom-bb>/src/host/layer23/src/transceiver/transceiver 1 script. I also don't see any errors when running make, although it scrolls by so fast it is hard to be sure. Thanks, Miguel

2 3

osmocombb not stable
by John Wu 12 Jun '13

12 Jun '13

Hi list, I test osmocombb with C118. At the beginning everything seems ok. but after some minutes osmocombb can not camp to any cell. osmocon print the all cell rssi are -138dbm. Then I reload the ram firmware it camp the cell again. since osmocombb do not do release. So anyone know which version in the git is stable version. Regards

1 0

decoding raw sdcch
by Akib Sayyed 11 Jun '13

11 Jun '13

I am trying to decode raw bits god from burst_ind to get detail info about channel assignment. but i am unable to do so. here are steps i used. take raw bites (23 bits) create lapdm entity and then provide message and try to decode (fails) i get correct system information but not asssignment message. can some one please list details on decoding sdcch. i am using burst_ind branch. -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

1 0

Re: Any interest for Osmocom meetings in Bavaria ?
by Dieter Spaar 11 Jun '13

11 Jun '13

So far three persons have indicated their interest to join a meeting at my place. Considering the time it takes to drive to my place, it probably makes sense to have the meeting at the weekend (either Saturday or Sunday) so that there is more time for the meeting itself. I can suggest one of the following dates for the first meeting, somewhere between 10:00 to 18:00 on each day: 25.8. (Sa) or 26.8. (Su) 1.9. (Sa) or 2.9. (Su) 8.9. (Sa) or 9.9. (Su) So please let me know when you have time and also make suggestions in which Osmocom topic you are interested in so that we can have some sort of agenda for the meeting to make best use of the time. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

13 42

umts rrc question
by ☎ 11 Jun '13

11 Jun '13

Hi all. I've problem reading umts standard etsi ts 125.331 - for example 10.2.11 DOWNLINK DIRECT TRANSFER does not specify length of "message type" or "rrc transaction id", it only references 10.3.3.36 which do not specify length as well - only "Integer (0..3)". Where do I look up the actual bit lengths? As far as I recall in gsm spec it was given right away. I've tried to read asn in wireshark/asn1/rrc but got myself only same "Integer (0..3)" and attempt to read generated code makes my brain reboot. I've tried to compile it with erlc and use parsers as is but hit "function not exported" - I don't know enough erlang yet to fix this. -- best regards, Max, http://fairwaves.ru

2 1

Getting burst in binary format for Kraken
by Obscura 11 Jun '13

11 Jun '13

I sniffed some data in UDP (GSMTAP) format using osmocon, ccch_scan and Wireshark . Next step is "feeding" recived data to Kraken. But i need it in binary format. How can i get data in suitable format (114 bit per burst)?

1 0

TOA in burst_ind
by Akib Sayyed 06 Jun '13

06 Jun '13

Hi Sylvain I wanted to know unit for TOA means, is it in miliseconds,nanoseconds etc. help is appreciated -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

2 2

RE: Cannot open serial device /dev/ttyUSB0
by George Andguladze 05 Jun '13

05 Jun '13

No it doesn't. > From: ml(a)mail.tsaitgaist.info > To: baseband-devel(a)lists.osmocom.org > Subject: Re: Cannot open serial device /dev/ttyUSB0 > Date: Tue, 4 Jun 2013 11:29:13 -0700 > > Excerpts from George Andguladze's message of 2013-06-04 10:40:35 -0700: > > Cannot open serial device /dev/ttyUSB0 > > > > I am getting this error message when I try to connect to my C155 phone and upload hello_world.compalram.bin using this command: > > > > ./osmocon -p /dev/ttyUSB0 -m c155 ../../target/firmware/board/compal_e99/hello_world.compalram.bin > > > > Even though device ttyUSB0 exists in my /dev/ directory, and I have set modprobe cp210x, and chmod 777 /dev/ttyUSB0. > > instead of setting 777 permissions on this device, you can simply add yourself to the dialout group (it's the more proper way) > here the debian command (don't forget to log out and in again for this to take effect) > sudo adduser $USER dialout > > > crw-rw---- 1 root dialout 4, 71 2013-06-04 20:40 /dev/ttyS7 > > crw-rw---- 1 root dialout 4, 72 2013-06-04 20:40 /dev/ttyS8 > > crw-rw---- 1 root dialout 4, 73 2013-06-04 20:40 /dev/ttyS9 > > crwxrwxrwx 1 root dialout 188, 0 2013-06-04 21:07 /dev/ttyUSB0 > > > > > > What is it that I am doing wrong? > > does it work with root rights (using sudo)? > > kevin >

1 0

sim reading hanged
by Akib Sayyed 03 Jun '13

03 Jun '13

while running mobile app. mobile app stuck giving following output <000f> sim.c:151 sending result to callback function (type=0) <0005> subscriber.c:379 received KEY from SIM <0005> subscriber.c:601 Requesting SIM file 0x6f30 <000f> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000f> sim.c:241 SELECT (file=0x6f30) <000f> sim.c:187 sending APDU (class 0xa0, ins 0xa4) <000f> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f) <000f> sim.c:949 command successfull <000f> sim.c:571 GET RESPONSE (len=15) <000f> sim.c:187 sending APDU (class 0xa0, ins 0xc0) <000f> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00) <000f> sim.c:949 command successfull <000f> sim.c:1065 selected file (len 249) <000f> sim.c:277 READ BINARY (offset=0 len=249) <000f> sim.c:187 sending APDU (class 0xa0, ins 0xb0) output of layer1 is SIM Response (17): 00 00 00 0b 6f 7e 04 00 11 ff 1b 21 02 00 00 90 00 LOST 1923! LOST 1827! SIM Request (5): a0 b0 00 00 0b SIM Response (13): ff ff ff ff ff ff ff 00 00 ff 01 90 00 SIM Request (7): a0 a4 00 00 02 6f 20 SIM Response (2): 9f 0f SIM Request (5): a0 c0 00 00 0f LOST 1878! LOST 1873! SIM Response (17): 00 00 00 09 6f 20 04 00 11 ff bb 01 02 00 00 90 00 SIM Request (5): a0 b0 00 00 09 SIM Response (11): ff ff ff ff ff ff ff ff 07 90 00 SIM Request (7): a0 a4 00 00 02 6f 30 SIM Response (2): 9f 0f SIM Request (5): a0 c0 00 00 0f LOST 1880! LOST 1870! SIM Response (17): 00 00 00 f9 6f 30 04 00 11 ff bb 21 02 00 00 90 00 SIM Request (5): a0 b0 00 00 f9 LOST 1880! LOST 1870! Please help me solve this issue -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

1 0

[PATCH] * Bugfix in Firmware: initialising variables
by Bhaskar11 28 May '13

28 May '13

2 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel