baseband-devel

baseband-devel@lists.osmocom.org

2022 discussions

OsmoTRX on Pirelli DP-L10 restarts phone
by Tobias Mädel 05 Oct '15

05 Oct '15

Hello, I'm currently trying to use a Pirelli DP-L10 calypso phone as a rudimentary BTS. I have followed the instructions on http://openbsc.osmocom.org/trac/wiki/network_from_scratch, I'm using the jolly/testing branch of osmocom-bb and I've enabled TX support in the Makefile. The software runs on an xubuntu 14.04 x64 machine. After uploading the firmware to the phones RAM via osmocon, it shows that it's running osmocom-bb on the display, when I then try to run transceiver with the following parameters: -e 5 -r 99 (or alternativly -e 5 -a 958 to sync with german provider O2) the phone just reboots and goes into a state where the keyboard backlight is blinking with 0.5 hertz. The last thing "transceiver" says is: <0012> l1ctl.c:383 Reset received: Starting sync. <000c> l1ctl.c:95 Sync Req <000c> l1ctl_link.c:171 Sending: '01 00 00 00 83 be 00 64 27 10 03 20 03 07 00 00 00 ' and the last log messages from osmocon are: DSP API Version: 0x3606 0x0000 LOST 7200! L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=33726, flags=0x7) Dropping sample ':' I'm not sure if I have configured the correct bands for synchronization. I think it might have to do something with that. I copy'd the default configuration from the osmocom-page stating DCS1800. The only base station I'm seeing here is 958, which is in the GSM900R range. Could this be the problem? Have I overseen something simple? Have I provided all necessary information about my setup? Any ideas? It's probably not a power issue, I have tested it with a lab power supply for providing the USB 5V and battery 4.2V, which resulted in the same behavior. Thanks, Tobias -- This email is encrypted with 2ROT-13. Tobias Mädel t.maedel(a)alfeld.de PGP: 3A69 E9AF 3FA9 3BCF FE50 9694 494E 2F56 C304 60E1 http://tbspace.de

1 1

Oct 07, 8pm / Osmocom Berlin User Group meeting
by Harald Welte 04 Oct '15

04 Oct '15

Hi all! This is the announcement for the re-incarnated Osmocom Berlin meeting: Oct 7, 8pm @ CCC Berlin, Marienstr. 11, 10117 Berlin Harald will be presenting about the Iuh protocol stack of UMTS small cells / femtocells and his work towards implementing it as part of Osmocom. Agenda: 20:00h Welcome 20:15h Presentation about Iuh / osmo-iuh 21:00h Informal meeting / chatting The meeting is open to anyone interested in mobile communications. You do not have to be involved with the Osmocom projects in order to attend. Anyone interested in mobile communications protocols is welcome. If you are interested to show up, feel free to do so. There is no registration required. The meeting is free as in "free beer", despite no actual free beer being around. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 1

Re: Oct 07, 8pm / Osmocom Berlin User Group meeting
by Mychaela Falconia 03 Oct '15

03 Oct '15

Harald Welte <laforge(a)gnumonks.org> wrote: > This is the announcement for the re-incarnated Osmocom Berlin meeting: > > Oct 7, 8pm @ CCC Berlin, Marienstr. 11, 10117 Berlin And for those who happen to be on the other side of the world (Southern California instead of Germany, San Diego instead of Berlin), there is this other meeting/presentation on a related topic happening about a day and a half later in Universal Time: http://www.meetup.com/kernel-panic/events/225595627/ > If you are interested to show up, feel free to do so. There is no > registration required. The meeting is free as in "free beer", Same for ours. > despite no actual free beer being around. While we don't serve beer either (for one thing, the venue who graciously provide us with free meeting space would have a problem with alcohol on the premises), we do usually have free refreshments as in soft drinks and cookies. M~

1 0

CalypsoBTS timeslots allocation
by Вадим Яницкий 17 Sep '15

17 Sep '15

Hello, list! I am trying to make working two and more TCH channels in OpenBSC (NiTB mode) with calypso based phones. How to understand timeslots allocation in this strings of transceiver app? as->l1l[0].tx_mask = 0xe3; /* TS 5,6,7,0,1 */ as->l1l[0].rx_mask = 0x01; /* TS 0 */ Why 2, 3, 4 timeslots is not used? And how to connect more than two phones to the transceiver? Should I add a new TRX in OpenBSC config and/or modify source code of the transceiver app? With best regards, fixeria.

2 3

Osmocom Berlin User Group revival?
by Harald Welte 09 Sep '15

09 Sep '15

Dear all, After two years of intermission, I'm currently pondering to revive the Osmocom Berlin User Group and would like to understand a) who would be interested in attending? b) which day(s) of the week would be preferred / not preferred? Instad of "just" hanging out, chatting about Osmocom related topics etc. I am interested in having actual topics for each of the meetings. There is no need for a formal presentation or anything like that, but at least let's try to stay focussed on the topic for the first hour or so, and then conclude with a more general chat towards the end. Some of the topics that I would like to start with ASAP: * sharing of knowledge regarding 3G and 4G protocol stacks (I'm looking a lot at this recently, and it is a good time to talk about what I've learned) * completing the work towards splitting osmo-nitb into osmo-bsc and osmo-mss - as a first stept towards adding RANAP/Iu to osmo-mss * attempting to decode/analyze BVG bus/tram radio (TETRAPOL) using tetrapol-kit from http://brmlab.cz/git/tetrapol-kit.git * are berlin S-Bahn trains actually still broadcasting their GPS position in MPT1327? * moving ahead with AT91SAM3S based SIMtrace2 with MITM support Let me know who is interested in joining. In terms of venue I would suggest to again use the CCCB, unless somebody objects. We could of course also ask our friends at IN-Berlin or C-Base. In terms of schedule, I would actually want to go for bi-weekly again. Happy hacking, Harald -- - 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)

1 1

network-from-scratch(calypso-setup)-several phones and gprs
by Erich Dachleger 08 Sep '15

08 Sep '15

I was also wondering about if is is possible to use network-frm-scratch setup (calypso-transceiver) with more phones to get more TCH channels as well as gprs? Regards erich Hello, list! I am trying to make working two and more TCH channels in OpenBSC (NiTB mode) with calypso based phones. How to understand timeslots allocation in this strings of transceiver app? as->l1l[0].tx_mask = 0xe3; /* TS 5,6,7,0,1 */ as->l1l[0].rx_mask = 0x01; /* TS 0 */ Why 2, 3, 4 timeslots is not used? And how to connect more than two phones to the transceiver? Should I add a new TRX in OpenBSC config and/or modify source code of the transceiver app? With best regards, fixeria.

1 0

AMR support and B_PLAY_UL
by Anton Guryanov 23 Aug '15

23 Aug '15

Hi, I tried to add simple AMR support in osmocombb project. I tested it with C123 (DSP API v 36). I set AMR config from assigment command, set AMR detection thresholds, make sync, etc. It looks like downlink works fine, but I have problem with uplink: it send data directly from microphone and ignore data in dsp_api.ndb->a_du_1 even if I set dsp_api.ndb->d_tch_mode|=B_PLAY_UL. Also, I can see uplink data on dsp_api.ndb->a_du_0 like B_PLAY_UL is fully ignored. Did anyone have that issue before? I know that AMR codec is more complex that TCH, but did someone know a way to send custom data from host using AMR codec? Best regards, Anton

2 1

Adding features from osmocom-bb to libosmocore
by Piotr Krysik 01 Aug '15

01 Aug '15

Hi all, I'm developing gr-gsm project which uses GNU Radio framework in order to build infrastructure for receiving GSM data. Recently we've added libosmocore as a dependency in order to use it's implementation of ciphering algorithms. I would like to use more of the code that was already implemented thanks to your work, but I've found some parts that I would expect to be in libosmocore are not in there but in osmocom-bb. One of the examples is interpretation of system information messages that is in src/host/layer23/src/common/sysinfo.c. Is it possible to move parts that are usable for projects outside of osmocom into libsomocore? If yes - how can I proceed with that? I'm aware that it is not simple process as it involves also removing these parts from osmocom-bb and maybe also editing them in order to make them independent of osmocom-bb. -- Best Regards, Piotr Krysik

2 1

c113a works
by Craig Comstock 01 Aug '15

01 Aug '15

FWIW, someone asked me whether c113 worked. I found a cheap 113a and hello_world loaded pretty well. The screen on my phone is shot but the backlight did come on.it works fine with the following command: craig@craig:~/c115-osmocom-bb/src$ host/osmocon/osmocon -p /dev/ttyUSB0 -m c123xor target/firmware/board/compal_e88/hello_world.compalram.bin OsmocomBB Hello World (revision osmocon_v0.0.0-1754-gfc20a37) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: c5c63637a5039778 ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== entering interrupt loop

4 3

[patch] sim.c waiting char issue
by etienne 28 Jul '15

28 Jul '15

Hello, The sim driver was not working with my sim card. After some successful apdu requests, it was ceasing to work. It turned out that the sim is sending waiting chars before some rx acks. The following patch solved the problem. diff --git a/src/target/firmware/calypso/sim.c b/src/target/firmware/calypso/sim.c index 752628f..b35909f 100644 --- a/src/target/firmware/calypso/sim.c +++ b/src/target/firmware/calypso/sim.c @@ -536,6 +536,8 @@ void sim_handler(void) /* Case 2: No input / Output of known length */ if (mode == SIM_APDU_PUT) { sim_state = SIM_STATE_RX_ACK; + /* ignore waiting char here*/ + sim_ignore_waiting_char = 1; calypso_sim_receive(response, 1); break; /* Case 4: Input / No output */ @@ -563,6 +565,8 @@ void sim_handler(void) break; /* wait until data is received */ /* Disable all interrupt driven functions */ writew(0xFF, REG_SIM_MASKIT); + /*stop ignoring waiting char*/ + sim_ignore_waiting_char = 0; /* error received */ if (sim_rx_character_count == 2) { puts("SIM: command failed\n"); Regards, Etienne -- View this message in context: http://baseband-devel.722152.n3.nabble.com/patch-sim-c-waiting-char-issue-t… Sent from the baseband-devel mailing list archive at Nabble.com.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel