baseband-devel

baseband-devel@lists.osmocom.org

2023 discussions

Start a nNew thread

baseband-devel unsubscribe notification
by mailman-bounces＠lists.osmocom.org 09 Jul '14

09 Jul '14

luca.bongiorni1(a)studenti.unimi.it has been removed from baseband-devel.

1 0

Bounce action notification
by mailman＠lists.osmocom.org 07 Jul '14

07 Jul '14

This is a Mailman mailing list bounce action notice: List: baseband-devel Member: devinechristophe(a)gmail.com Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman(a)lists.osmocom.org.

1 0

./mobile-build
by tom 03 Jul '14

03 Jul '14

Hi all Have built Osmocommbb mobile app and have a problem to get phone to register with my network. From "show subscriber" it shows all the preferred PLMNs but not mine. How can I include my info into this list. Access classes: C7 List of preferred PLMNs: MCC |MNC -------+------- 234 |10 (Guernsey, O2) 234 |33 (Guernsey, Orange) 214 |07 (Spain, movistar) 214 |03 (Spain, Orange) 208 |01 (France, Orange) 208 |20 (France, Bouygues) 222 |01 (Italy, TIM) 268 |06 (Portugal, TMN) 262 |07 (Germany, O2) 262 |01 (Germany, T-Mobile) 204 |08 (Netherlands, KPN) 206 |20 (Belgium, BASE) 232 |03 (Austria, T-Mobile) 286 |01 (Turkey, Turkcell) 202 |01 (Greece, Cosmote) 505 |01 (Australia, Telstra) 230 |02 (Czech Republic, O2) 228 |02 (Switzerland, Sunrise) 655 |10 (South Africa, MTN) 240 |01 (Sweden, Telia) 216 |30 (Hungary, Westel 900) 238 |02 (Denmark, Sonofon / Telenor) 244 |91 (Finland, Sonera) 242 |01 (Norway, Telenor) 219 |10 (Croatia, VIPnet) 226 |10 (Romania, Orange) 260 |02 (Poland, Era) 284 |05 (Bulgaria, GLOBUL) 424 |02 (United Arab Emirates, Etisalat) 520 |01 (Thailand, AIS) List of forbidden PLMNs: MCC |MNC |cause -------+-------+------- 272 |01 |#255 (Ireland, Vodafone) 272 |03 |#255 (Ireland, Meteor) I think this is reason why I am unable to register on the network. <0003> gsm322.c:2861 Scanning frequencies. (955..1023) <0002> gsm322.c:3929 (ms 1) Event 'EVENT_CHOOSE_PLMN' for manual PLMN selection in state 'M4 trying PLMN' <0002> gsm322.c:1756 User selects PLMN. (mcc=272 mnc=02 Ireland, O2) <0002> gsm322.c:820 new state 'M4 trying PLMN' -> 'M4 trying PLMN' <0003> gsm322.c:4049 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in state 'C1 normal cell selection' <000e> gsm322.c:3631 Selecting PLMN (mcc=272 mnc=02 Ireland, O2) <0003> gsm322.c:3637 Start stored cell selection. <0003> gsm322.c:829 new state 'C1 normal cell selection' -> 'C2 stored cell selection' <0003> gsm322.c:836 changing state while power scanning <0003> gsm322.c:2793 Scanning power for stored BA list. <0003> gsm322.c:2861 Scanning frequencies. (1..1) <0005> gsm48_mm.c:4320 (ms 1) Received 'MM_EVENT_USER_PLMN_SEL' event in state MM IDLE, no cell available <0005> gsm48_mm.c:4333 Message unhandled at this state. <0003> gsm322.c:2922 Done with power scanning range. Can someone give me a little help with this. Tom

1 0

Hardware Preparation for Osmocom Bb Project
by sammy zada 27 Jun '14

27 Jun '14

Hi All, I'm interesting to make a final report for my study at college about the Osmocom Bb Topics. According to information from http://bb.osmocom.org/trac/ the most important device is old handset such as motorola C123. My question is, do we have to modify the component board of the motorola C123 or we can use it directly to build Osmocom Bb system? Is there any info regarding this question? Thanks, Sammy

2 1

baseband-devel unsubscribe notification
by mailman-bounces＠lists.osmocom.org 26 Jun '14

26 Jun '14

osmocom(a)ninoc.nl has been removed from baseband-devel.

1 0

baseband-devel unsubscribe notification
by mailman-bounces＠lists.osmocom.org 23 Jun '14

23 Jun '14

3304xfq(a)163.com has been removed from baseband-devel.

1 0

Bounce action notification
by mailman＠lists.osmocom.org 21 Jun '14

21 Jun '14

This is a Mailman mailing list bounce action notice: List: baseband-devel Member: mki(a)mki-consult.de Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman(a)lists.osmocom.org.

1 0

Bounce action notification
by mailman＠lists.osmocom.org 21 Jun '14

21 Jun '14

This is a Mailman mailing list bounce action notice: List: baseband-devel Member: cbalke(a)charter.net Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman(a)lists.osmocom.org.

1 0

Calypso differences between C139 and C156?
by msokolov＠ivan.Harhan.ORG 21 Jun '14

21 Jun '14

Hello fellow hackers, In process of getting FreeCalypso loadtools (primarily the flash manipulation utility fc-loadtool) working on the C1xx family in addition to the previously supported Openmoko and Pirelli targets, I discovered one bit of strangeness for which I have no explanation, and I wonder if anyone else has seen it or might have an explanation for it. According to Calypso chip documentation (gathered on the GSM mini- Wikileaks site ftp.ifctf.org:/pub/GSM), the complete nCS0 flash bank should always be accessible at address 0x03000000, regardless of whether the physical nIBOOT input is low or high, and regardless of what may have been written into the FFFF:FB10 register to enable or disable the mapping of the boot ROM at address 0. And indeed I have always used this nCS0 mapping at 0x03000000 on Openmoko and Pirelli targets, and have got used to it always working. But when I started playing with Compal phones a few months ago, I discovered that at least on the North American (1900+850 MHz) C139s reading from 0x03000000 returns all 0xFF's instead of the flash content, no matter what the FFFF:FB10 register is set to. So I figured it must be some difference between the full Calypso in the Openmoko & Pirelli phones and the Calypso Lite in C1xx, or perhaps that mapping at 0x03000000 only works when the physical nIBOOT input is low. Then last night I dusted off my North American C156 (this C156 and a bunch of NA C139s are the only Compal phones I have, as the more "mainstream" 900+1800 MHz models aren't of much use to me, given my geographic location) and tried my tools on it, as I'm polishing them up for a stable release. And guess what: reading from 0x03000000 yields the flash content on this phone, not the 0xFF's I get on all of the C139s I've tested! But don't all C1xx phones use the same Calypso Lite chip? And this C156 surely has nIBOOT tied high just like the other C1xx: the small sector at 0x2000 is all 0xFF's (blank), so if the boot ROM were enabled, the phone would never boot. (The boot ROM requires the 32-bit word at 0x2000 to be either 0 or 1, selecting different modes of booting the main fw.) Just wondering if anyone else has seen this strangeness, and what the behaviour might be on other C1xx phones besides those I have... Oh, and all of the work I've done for Compal target support in FreeCalypso loadtools is in the public Hg repository: https://bitbucket.org/falconian/freecalypso-sw VLR, SF P.S. Is Christophe Devine still on this list? Christophe, if you are reading this: I sent unicast email to your gmail address last night, but it bounced. Are you still around?

1 0

Bounce action notification
by mailman＠lists.osmocom.org 18 Jun '14

18 Jun '14

This is a Mailman mailing list bounce action notice: List: baseband-devel Member: luca.bongiorni1(a)studenti.unimi.it Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman(a)lists.osmocom.org.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel