baseband-devel May 2017

baseband-devel@lists.osmocom.org

17 participants
31 discussions

Re: CalypsoBTS + GPRS and SDR suggestion
by Vadim Yanitskiy 09 May '17

09 May '17

Hi, > I setup CalypsoBTS to work with 2 old motorola c123, I know that isn't the > best way to do that, but I would like to have a cheap solution. I got the > setup working with a normal phone and the BTS seems to work correctly > (using jolly/testing), but from my understanding it support only GSM calls > and SMS and GPRS is not implemented into the transceiver. I'm wrong or this > part has not been implemented yet? Right, isn't implemented. When you run OsmoBTS, it first does some basic configuration of transceiver, including timeslot type setting. PDCH has its own dedicated type, which is being indicated by the SETSLOT command. So you can look at OsmocomBB sources, and check whether the transceiver handles this type or not. > Also, given that CalypsoBTS can only provide single (or two?) timeslot, > there are a long list of reasons why it would not work straight-forward. > But technically also possible to make work. With two Calypso phones it becomes possible to serve two timeslots. Basically, second phone serves one TCH timeslot, but (if I am correct) PDCH has no fundamental differences from TCH, so its support could be implemented too. After a quick look at OsmoTRX source code, I can assume, that the only difference between TCH channel combinations (I, II and III) and PDCH channel combination (XIII) is a fillerModulus value. Correct me if I am wrong. With best regards, Vadim Yanitskiy.

3 2

CalypsoBTS + GPRS and SDR suggestion
by inode 08 May '17

08 May '17

Hi everybody, I'm pretty new to the GSM/UMTS environment and I'm doing some tests. Currently I need to analyze some IoT devices that use 2G network to comunicate via GPRS. I setup CalypsoBTS to work with 2 old motorola c123, I know that isn't the best way to do that, but I would like to have a cheap solution. I got the setup working with a normal phone and the BTS seems to work correctly (using jolly/testing), but from my understanding it support only GSM calls and SMS and GPRS is not implemented into the transceiver. I'm wrong or this part has not been implemented yet? If needed to use a GPRS BTS can you suggest the best cheap SDR to use with OsmoBTS? (I saw BladeRF and LimeSDR but I was unable to understand if they are full supported via OsmoBTS) Thank you in advance. inode

3 2

Re: to qcom hexagon porting
by Craig Comstock 08 May '17

08 May '17

> what are problem should i expect > while porting to qcom hexagon > is it a bad idea There would be a lot of questions and things to research. I am not familiar with qcom hexagon SDK. I am a little familiar with osmocom-bb source code and 2G GSM details. I am currently in the very beginning stages of porting osmocom-bb to the MediaTek 6260/6261 chip which supports 2G. I also have ideas to try and work through 3G on a MediaTek 6735 (ZTE Obsidian phone). Recently there have been mentions of re-writing the PHY layer of osmocom-bb for an SDR platform like LimeSDR. https://github.com/axilirator/osmocom-bb So at the current time I assume that osmocom-bb communicates with the DSP chip on the motorola phones in a way that abstracts the PHY layer details away and relies on the proprietary Texas Instruments firmware in the DSP as-is. So I would imagine you might have to implement the PHY layer and also the interface to the PHY layer. There was a discussion about this recently on IRC #osmocom. It seems the thought was that qcom had released enough with their Hexagon SDK to allow development of a PHY layer + whatever else. Some links of interest. https://developer.qualcomm.com/ - SDK https://github.com/ttsou/openphy - LTE PHY for Ettus USRP https://androiddatahost.com/fgd43 - qcom flash image loader I have a few qcom modems that I'd be happy to do experiment on if that helps. -Craig

1 0

to qcom hexagon porting
by thayyil09 yil 07 May '17

07 May '17

what are problem should i expect while porting to qcom hexagon is it a bad idea

1 0

Re: CalypsoBTS no sync, ms hang
by Vadim Yanitskiy 06 May '17

06 May '17

> isn't fixed in branch jolly/testing I am using for calypsoBTS. > So all I needed is just implement the fix and recompile from sources. You can also use an older version of toolchain as a temporary solution: https://github.com/axilirator/gnu-arm-installer - in this repo I have fixed some installation (texinfo) related issues. With best regards, Vadim Yanitskiy.

2 1

CalypsoBTS no sync, ms hang
by Anton Gorbachev 05 May '17

05 May '17

Dear colleagues, I am trying to setup CalypsoBTS with two c113 phones. Don't you know why can't I sync to any commercial cell with transceiver from branch jolly/testing? What I have: Motorola c113 and c113a, tried both. All other apps like, RSSI, mobile, ccch_scan works like a charm. What I am doing: Built jolly/testing according to maual https://osmocom.org/projects/baseband/wiki/CalypsoBTS Load firmware ./osmocon -r 99 -m c123xor -p /dev/ttyUSB0 -c ../../target/firmware/board/compal_e88/trx.highram.bin Found several strongest cells with RSSI and cell_log. Trying to sync: ./transceiver -a 50 -r 99 -e 1 Here is the log: 50 41 1 <000c> l1ctl.c:77 Tx Reset Req (1) <000c> l1ctl_link.c:171 Sending: '0d 00 00 00 01 00 00 00 ' <0012> l1ctl.c:383 Reset received: Starting sync. <000c> l1ctl.c:95 Sync Req <000c> l1ctl_link.c:171 Sending: '01 00 00 00 00 32 00 64 27 10 03 20 03 07 00 00 00 ' After that phone hangs, no reaction in osmocon on key pressures, holding on power off button... The last messages are: L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=50, flags=0x7) Starting FCCH RecognitionFB0 (2515:4): TOA= 3552, Power= -64dBm, Angle= 1328Hz FB1 (2525:8): TOA= 8543, Power= -64dBm, Angle= 114Hz fn_offset=2523 (fn=2525 + attempt=8 + ntdma = 6) delay=8 (fn_offset=2523 + 11 - fn=2525 - 1 scheduling next FB/SB detection task with delay 8 =>FB @ FNR 2523 fn_offset=2523 qbits=3988 Synchronize_TDMA LOST 3398! I tried different cells, maybe I need to wait some time to warm the crystal? But can it be so important? Kind regards, Anton

1 1

Re: OsmocomBB full Opensouce?
by Vadim Yanitskiy 04 May '17

04 May '17

Hi Anton, > There are some ideas floating around of doing a new run of this using > OsmoTRX as basis, but I don't know if there is any actual progress yet. > Vadim should be able to say more about it. Yeah, I started to work on SDR based PHY about a year ago, but so far I was busy with libosmocore development. Right now almost everything (including libosmocoding of course) is in master branch, so it's good point to resume this work. If you would like to contribute this direction or something else, we are always open for that, so feel free! The source code is currently on GitHub: https://github.com/axilirator/osmocom-bb/ BTW: Harald, is it possible to create a new branch for that work in the project's repo? If yes, I can send you my public key in PM. Thanks! With best regards, Vadim Yanitskiy.

4 3

Phone not receiving calls
by samir 04 May '17

04 May '17

Hello, I test osmocombb for some time with motorola c115. I can make calls but not always receive calls. I tried 2 sim cards one of them is working fine but the other doesn’t receive anything. I really need some help to solve my problem. thanks in advance.

1 0

CalypsoBTS + GPRS and SDR suggestion
by Maurizio Agazzini 04 May '17

04 May '17

1 0

OsmocomBB full Opensouce?
by Anton Gorbachev 04 May '17

04 May '17

Dear collegues, Could you please help me to understand one thing.. If I understood everything correct, osmocombb project consist of all the code for GSM stack L1-L3 functionality but Calypdo DSP code is not Opensource and layer1.bin ask non-opensource DSP module to do execute L1 tasks from ghis list: https://osmocom.org/projects/baseband/wiki/TSM30Layer1#DSP-Tasks Of cource we can patch DSP and ask it to do whatever we want, like send raw bursts to the host, but now osmocombb uses mostly DSP firmware written by Texas Instruments, not its own opdnsource. Is it correct or not? Thanks in advance!

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel May 2017