baseband-devel

baseband-devel@lists.osmocom.org

2022 discussions

Re: Usefulness of the Calypso (was Re: seL4 is open source now)
by Alan Carvalho de Assis 06 Aug '14

06 Aug '14

Hi Scott, On 8/5/14, Scott Weisman <sweisman(a)pobox.com> wrote: > I think this desire is recognized. I remember an initiative some years > back, started with some enthusiasm, that never got passed the stage of > deciding on NuttX as the OS to use, and forking it. > We got NuttX running on compal phones (Motorola C1xx, W220, etc), including display support using NuttX's native graphic subsystem. The code was submitted to NuttX mainline and now it is integrated. Unfortunately nobody with more knowledge about GSM L1/L2 layers was available to help in the stack porting. During the porting we got help from Steve Markgraf. Now the scenario is more complex, the original "team" is separated and we don't have spare time to help. Best Regards, Alan

1 0

Re: Usefulness of the Calypso (was Re: seL4 is open source now)
by msokolov＠ivan.Harhan.ORG 06 Aug '14

06 Aug '14

Steve Markgraf <steve(a)steve-m.de> wrote: > I don't quite see how waving the Free Software flag and distributing > proprietary source from the TSM30/Locosto leaks (pretty much everything > in freecalypso-sw/gsm-fw/) go together. That source is NOT proprietary, it is *ex*-proprietary. It *was* proprietary, but not any more - it is now in the public domain. Free Software is not just a "flag" to be waved, it is a practical reality: in *practical* terms, software that is based on ex-proprietary code that has been liberated through the exercise of Eminent Domain and subsequently developed and maintained in the manner of a free sw project gives its users all of the 4 freedoms defined by FSF. However, I shall leave it here -- any further replies or comments or questions in this thread will *not* elicit a further reply from me. But if there is anyone else on this list who desires a usable cellphone for talking to his or her significant other like I do, please be assured that I have no plans of dropping the project; the work is progressing at a steady pace as you can see from the Mercurial commit history, and I have high hopes of some actually-usable result some time around the end of 2014. VLR, SF

3 2

Aw: Re: Re: Re: Re: seL4 is open source now
by mark.neuhaus＠email.de 05 Aug '14

05 Aug '14

The kernel comes with a hypervisor (under BSD on Githu, too) and you can run Linux in one virtual environment (see http://l4linux.org/) and for example an GSM stack in another virtual environment. So you can think of that kernel as a kind of virtual machine that seperates the hardware This way all virtual systems are prooven separated and I think that is what the merkel-phone does. owever NICTA is actually going much further. Thei are working on a zero-bug (verified file system) and much more. This kind of programming is entirely different from common way to write a program. (YOU don't write the program, but you write a proof in Coq or ISABEL ect and from this proof a programm can be derived automatically) > Gesendet: Dienstag, 05. August 2014 um 10:50 Uhr > Von: "Sebastien Lorquet" <sebastien(a)lorquet.fr> > An: mark.neuhaus(a)email.de > Betreff: Re: Aw: Re: Re: Re: seL4 is open source now > > Hello, > > Reading through the se4l FAQ at http://sel4.systems/FAQ/ , I'm reading this: > > > Unique about seL4 is its unprecedented degree of assurance, achieved through > formal verification. Specifically, the ARM version of seL4 is the first (and > still only) general-purpose OS kernel with a full code-level functional > correctness proof, meaning a mathematical proof that the implementation (written > in C) adheres to its specification. In short, the implementation is proved to be > bug-free (see below). This also implies a number of other properties, such as > freedom from buffer overflows, null pointer exceptions, use-after-free, etc. > > > Okay with that. But also: > > > There is a further proof that the binary code which executes on the hardware is > a correct translation of the C code. This means that the compiler does not have > to be trusted, and extends the functional correctness property to the binary. > > > So that is very cool, even the binary result is proved, not only the source code ! > > The only thing that bothers me is: what can I do with this cool software? It > seems that little can be done without a set of userspace servers, so I guess we > have to wait until some open source community provides useful software to run > with this microkernel. > > Best regards, > > Sébastien Lorquet > > Le 02/08/2014 12:49, mark.neuhaus(a)email.de a écrit : > > > >> My idea is that at some point, the developers working at xda-developers > >> (android phone hackers) will get enough knowledge of their baseband > >> chips so that something can be done with osmocom. But this is only my > >> opinion! > > > > Yes lets hope. The calypso is just to outdated to be interesting > > for anything 'useable' beyond pure hacking-fun. > > >

1 0

seL4 is open source now
by mark.neuhaus＠email.de 31 Jul '14

31 Jul '14

Hey, new to the mailing list. Two things: 1.) Probably you know, but in case not: The proven correct, highest security L4 microkernel (seL4) is under GPL since yesterday! In addition useful tools like a compatible hypervisor and dev tools are under BSD, too. See https://sel4.systems/ for general stuff or get the src on https://github.com/seL4/seL4 If I understand your research correctly, you likely have use for such an advanced kernel, to separate BB and APP system in separate containers, running on the same CPU. ... I'm a mathematician and involved in zero-bug-programming aka verified programming used in ultra secure environments and I think that this step of the NICTA research group is just awesome. I'm not entirely sure but I believe that seL4 is already used as the kernel of the "Merkel-phone" used now in Germany. 2.) I'm actually reading through your mailing list, but I have two questions which you are eventually kind to answer: a.) For what baseband chips has OsmocomBB actually working drivers (Layer1 as you call it, I think) and on what chipsets are you working to get the Layer1 in the future? It' pretty hard to get phones with the Calypso these days. b.) Is there a list of actually supported phones? I know the wiki, but non of these phones was available for me anymore. So long. Best, \mark

1 0

OsmoComBB - Burst_ind Sylvian c121 / c123
by Milinko Isakovic 30 Jul '14

30 Jul '14

Hi to all, I reacently try to install and work with OsmocomBB, and I had very strange situation. Last time I was usien it was 3 years ago. When I use branch sylvian / test... with TX enabled, phone can not find any cell avb ? I tried: 1. Sim remove 1 2. Configure terminal; ms 1; sim test; shutdown; no shutdown 3. sim remove 1 4. network seach ... and see no network. On my old compuer with sam phone, seems to me it is working ok? Any idea about this ? Milinko

1 0

Re: Error loading firmware onto Motorola C115.
by msokolov＠ivan.Harhan.ORG 30 Jul '14

30 Jul '14

Ravi Sharan <ravisharan(a)iith.ac.in> wrote: > I am trying out osmocom-bb with the Motorla C115. [...] < I get the following error: > > $ osmocon -p /dev/ttyUSB0 -m c123 > ~/osmocom-bb/src/target/firmware/board/compal_e88/hello_world.compalram.bin > [snipped the part where everything goes as it should] > got 1 bytes from modem, data looks like: 1b . > got 1 bytes from modem, data looks like: f6 . > got 1 bytes from modem, data looks like: 02 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 45 E > got 1 bytes from modem, data looks like: 53 S > got 1 bytes from modem, data looks like: 16 . > Received DOWNLOAD NACK from phone, something went wrong :( Try -m c123xor instead of -m c123. HTH, SF

4 6

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

29 Jul '14

This is a Mailman mailing list bounce action notice: List: baseband-devel Member: softwaredefinesradio(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 unable to register
by tom mc loughlin 29 Jul '14

29 Jul '14

I was having problems with unable to register with real network and sim reader on the testing branch. I was advised on the list to use master branch to sort this problem, I have done this and now I get the following. <0003> gsm322.c:829 new state 'C1 normal cell selection' -> 'C3 camped normally' <0005> gsm48_mm.c:4320 (ms 1) Received 'MM_EVENT_CELL_SELECTED' event in state MM IDLE, PLMN search <0005> gsm48_mm.c:909 new MM IDLE state PLMN search -> location updating needed <0005> gsm48_mm.c:909 new MM IDLE state location updating needed -> attempting to update <0005> gsm48_mm.c:426 starting T3212 (periodic loc. upd. delay) with 21600 seconds <0005> gsm48_mm.c:2291 Do normal Loc. upd. <000e> gsm48_mm.c:2208 Perform location update (MCC 272, MNC 02 LAC 0x4e2a) <0005> gsm48_mm.c:2342 LOCATION UPDATING REQUEST <0005> gsm48_mm.c:2364 using LAI (mcc 272 mnc 02 lac 0x8cad) <0005> gsm48_mm.c:2372 using TMSI 0x49059a60 <0005> gsm48_mm.c:914 new state MM IDLE, attempting to update -> wait for RR connection (location updating) <0001> gsm48_rr.c:5449 (ms 1) Message 'RR_EST_REQ' received in state idle (sapi 0) <000e> gsm48_rr.c:1307 Establish radio link due to mobility management request <0003> gsm322.c:4049 (ms 1) Event 'EVENT_LEAVE_IDLE' for Cell selection in state 'C3 camped normally' <0003> gsm322.c:829 new state 'C3 camped normally' -> 'connected mode 1' <0003> gsm322.c:3665 Going to camping (normal) ARFCN 47. <0003> gsm322.c:452 Sync to ARFCN=47, but there is a sync already pending <0001> gsm48_rr.c:355 new state idle -> connection pending <0001> gsm48_rr.c:1454 CHANNEL REQUEST: 00 (Location Update with NECI) <0003> gsm322.c:2947 Channel synched. (ARFCN=47, snr=16, BSIC=59) <0001> gsm322.c:2968 using DSC of 90 <0003> gsm48_rr.c:4820 Channel provides data. <0001> gsm48_rr.c:1590 RANDOM ACCESS (requests left 5) <0001> gsm48_rr.c:1647 RANDOM ACCESS (Tx-integer 7 combined no S(lots) 0 ra 0x02) <0001> gsm48_rr.c:1686 Use MS-TXPWR-MAX-CCH power value 5 (33 dBm) msgb(0x89b3528): Not enough headroom msgb_push (4150577812 < 7) backtrace() returned 11 addresses /usr/local/lib/libosmocore.so.4(osmo_generate_backtrace+0x16) [0xb76df8a6] /usr/local/lib/libosmocore.so.4(osmo_panic+0x4c) [0xb76df71c] /usr/local/lib/libosmogsm.so.5(lapdm_phsap_up+0x18c) [0xb76aca4c] ./mobile() [0x808516f] ./mobile() [0x8085c39] /usr/local/lib/libosmocore.so.4(osmo_wqueue_bfd_cb+0x9e) [0xb76dc98e] /usr/local/lib/libosmocore.so.4(osmo_select_main+0x192) [0xb76db912] ./mobile() [0x804b9cc] /lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xe6) [0xb7541e66] ./mobile() [0x804bb99] Signal 6 received. full talloc report on 'layer2 context' (total 21588 bytes in 50 blocks) Layer2 contains 356 bytes in 1 blocks (ref 0) 0x89b3528 GSM 04.08 L3 contains 388 bytes in 1 blocks (ref 0) 0x89b6380 struct gsm322_ba_list contains 180 bytes in 1 blocks (ref 0) 0x89b3440 struct gsm48_sysinfo contains 1452 bytes in 1 blocks (ref 0) 0x89b4d60 struct gsm48_sysinfo contains 1452 bytes in 1 blocks (ref 0) 0x89b4780 struct gsm_sub_plmn_na contains 16 bytes in 1 blocks (ref 0) 0x89b3f98 struct gsm_sub_plmn_na contains 16 bytes in 1 blocks (ref 0) 0x89b3f50 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3f10 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3ed0 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3e90 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3e50 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3e10 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3dd0 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3d90 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3d50 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3d10 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3cd0 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3c90 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3c50 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3c10 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3bd0 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3b90 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3b50 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3b10 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3ad0 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3a90 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3a50 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3a10 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b39d0 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3990 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3950 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3910 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b38d0 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b3890 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89aeda8 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89aed68 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89aebe0 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89aeea0 struct gsm_sub_plmn_list contains 12 bytes in 1 blocks (ref 0) 0x89b31a8 SIM contains 644 bytes in 1 blocks (ref 0) 0x89b44c8 struct gsm_sim_handler contains 16 bytes in 1 blocks (ref 0) 0x89b3160 struct gsm_sim_handler contains 16 bytes in 1 blocks (ref 0) 0x89b3118 struct gsm_sim_handler contains 16 bytes in 1 blocks (ref 0) 0x89aee18 telnet_connection contains 49 bytes in 2 blocks (ref 0) 0x89aefa8 struct telnet_connection contains 48 bytes in 1 blocks (ref 0) 0x89aef38 struct gsm322_ba_list contains 180 bytes in 1 blocks (ref 0) 0x89b3358 struct osmocom_ms contains 16364 bytes in 1 blocks (ref 0) 0x89aefe0 /root/.osmocom/bb contains 29 bytes in 1 blocks (ref 0) 0x8973488 main.c:240 contains 29 bytes in 1 blocks (ref 0) 0x8973430 Aborted root@tom-ei9dl:~/osmocom-bb/src/host/layer23/src/mobile# Can some one please help me solve this. Tom

1 0

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

28 Jul '14

devinechristophe(a)gmail.com has been removed from baseband-devel.

1 0

Re: baseband-devel Digest, Vol 54, Issue 15
by tom mc loughlin 26 Jul '14

26 Jul '14

Sylvain I am reading from osmocommbb sim reader which states the following. Reading SIM card isn't supported in master branch of osmocom-bb. To experiment with provider SIM card and network (which is possibly the easiest way to try osmocom-bb out) you will need sylvain/testing branch which you can checkout using following commands: Has this being changed and now part of the master branch. Tom On Fri, Jul 25, 2014 at 12:28 PM, <baseband-devel-request(a)lists.osmocom.org> wrote: > Send baseband-devel mailing list submissions to > baseband-devel(a)lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osmocom.org/mailman/listinfo/baseband-devel > or, via email, send a message with subject or body 'help' to > baseband-devel-request(a)lists.osmocom.org > > You can reach the person managing the list at > baseband-devel-owner(a)lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of baseband-devel digest..." > > Today's Topics: > > 1. Mobile testing branch (tom mc loughlin) > 2. Re: Mobile testing branch (Sylvain Munaut) > 3. mobile app simulated-delay (TSAREGORODTSEV, Yury) > > > ---------- Forwarded message ---------- > From: tom mc loughlin <tomei9dl(a)gmail.com> > To: baseband-devel(a)lists.osmocom.org > Cc: > Date: Fri, 25 Jul 2014 11:25:40 +0100 > Subject: Mobile testing branch > Hi all > I have built Osmocommbb with testing branch and I want to run Mobile app > allowing me to make a call via my local network. > All goes well in the build but I am unable to register on my own network > while using a genuine network sim. > This is output from my compal_e88/layer1.compalram.bin. > As you can see all looks good with signal levels fairly ok until this > point and then level drops to -138 dbm and there it stays on all chanells. > I have tried this with 3 different sims and all is the same. > Can someone help? > Tom > bat_compal_e88_chg_state=0 > L1CTL_RESET_REQ: FULL!SIM Request (7): a0 a4 00 00 02 3f 00 > SIM Response (2): 9f 20 > SIM Request (5): a0 c0 00 00 20 > SIM Response (34): 00 00 02 b7 3f 00 01 00 00 00 00 00 13 b3 05 0a 04 00 > 83 8a 83 8a 00 03 00 00 02 b7 00 00 02 b7 90 00 > SIM Request (7): a0 a4 00 00 02 2f e2 > SIM Response (2): 9f 0f > SIM Request (5): a0 c0 00 00 0f > SIM Response (17): 00 00 00 0a 2f e2 04 00 0f 00 ff 01 02 00 00 90 00 > SIM Request (5): a0 b0 00 00 0a > SIM Response (12): 98 53 03 11 02 08 22 45 65 f6 90 00 > SIM Request (7): a0 a4 00 00 02 7f 20 > SIM Response (2): 9f 20 > SIM Request (5): a0 c0 00 00 20 > SIM Response (34): 00 00 00 00 7f 20 02 00 00 00 00 00 13 b3 00 23 04 00 > 83 8a 83 8a 00 03 00 00 02 b7 00 00 00 00 90 00 > SIM Request (7): a0 a4 00 00 02 6f 07 > SIM Response (2): 9f 0f > SIM Request (5): a0 c0 00 00 0f > SIM Response (17): 00 00 00 09 6f 07 04 00 14 00 14 01 02 00 00 90 00 > SIM Request (5): a0 b0 00 00 09 > SIM Response (11): 08 29 27 10 17 21 89 26 33 90 00 > SIM Request (7): a0 a4 00 00 02 6f 7e > SIM Response (2): 9f 0f > SIM Request (5): a0 c0 00 00 0f > SIM Response (17): 00 00 00 0b 6f 7e 04 00 11 00 14 01 02 00 00 90 00 > SIM Request (5): a0 b0 00 00 0b > SIM Response (13): ff ff ff ff 72 f2 60 ff fe 00 03 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 > SIM Response (17): 00 00 00 09 6f 20 04 00 11 00 44 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 > SIM Response (17): 00 00 01 2c 6f 30 04 00 11 00 44 01 02 00 00 90 00 > SIM Request (5): a0 b0 00 00 2c > SIM Response (46): 32 f4 51 02 f8 01 12 f4 60 12 f4 10 62 f2 20 02 f4 40 > 22 f2 01 02 f6 10 22 f8 10 72 f0 77 62 f8 10 42 f0 80 32 f8 10 02 f2 50 32 > f2 90 00 > BAT-ADC: 593 6 0 0 1023 353 327 277 > Charger at 51 mV. > > PM MEAS: ARFCN=1016, 33 dBm at baseband, -104 dBm at RF > PM MEAS: ARFCN=1017, 33 dBm at baseband, -104 dBm at RF > PM MEAS: ARFCN=1018, 29 dBm at baseband, -108 dBm at RF > PM MEAS: ARFCN=1019, 29 dBm at baseband, -108 dBm at RF > PM MEAS: ARFCN=1020, 28 dBm at baseband, -109 dBm at RF > PM MEAS: ARFCN=1021, 29 dBm at baseband, -108 dBm at RF > PM MEAS: ARFCN=1022, 27 dBm at baseband, -110 dBm at RF > PM MEAS: ARFCN=1023, 39 dBm at baseband, -98 dBm at RF > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=1, flags=0x7) > Starting FCCH RecognitionFB0 (3859:4): TOA= 3792, Power= -88dBm, > Angle=-1361Hz > DSP Error Status: 256 > FB1 (3869:8): TOA= 8751, Power= -88dBm, Angle= -36Hz > fn_offset=3867 (fn=3869 + attempt=8 + ntdma = 6) > delay=8 (fn_offset=3867 + 11 - fn=3869 - 1 > scheduling next FB/SB detection task with delay 8 > =>FB @ FNR 3867 fn_offset=3867 qbits=4820 > Synchronize_TDMA > LOST 3711! > DSP Error Status: 256 > DSP Error Status: 264 > L1CTL_RESET_REQ: FULL!LOST 1893! > L1CTL_FBSB_REQ (arfcn=981, flags=0x7) > Starting FCCH RecognitionLOST 1857! > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=71, flags=0x7) > Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=993, > flags=0x7) > Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!LOST 1899! > L1CTL_FBSB_REQ (arfcn=979, flags=0x7) > Starting FCCH RecognitionLOST 1851! > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=4, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > BAT-ADC: 590 6 0 0 1023 356 330 277 > Charger at 51 mV. > Battery at 4033 mV. > Charging at 0 mA. > Battery capacity is 100%. > Battery range is 3199..3999 mV. > Battery full at 468 LSB .. full at 585 LSB > Charging at 239 LSB (204 mA). > BCICTL2=0x3ff > battery-info.flags=0x00000000 > bat_compal_e88_chg_state=0 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=1023, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!LOST 1900! > L1CTL_FBSB_REQ (arfcn=980, flags=0x7) > Starting FCCH RecognitionLOST 1850! > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=78, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=53, flags=0x7) > LOST 1880! > Starting FCCH RecognitionLOST 1870! > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=69, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=94, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=57, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=985, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=970, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=45, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=43, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=33, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=7, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=988, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=971, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=969, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=42, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=40, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=32, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > BAT-ADC: 592 6 0 0 1023 353 327 270 > Charger at 51 mV. > Battery at 4047 mV. > Charging at 0 mA. > Battery capacity is 100%. > Battery range is 3199..3999 mV. > Battery full at 468 LSB .. full at 585 LSB > Charging at 239 LSB (204 mA). > BCICTL2=0x3ff > battery-info.flags=0x00000000 > bat_compal_e88_chg_state=0 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=85, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=55, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=47, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=28, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=5, flags=0x7) > Starting FCCH RecognitionDSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > DSP Error Status: 8 > L1CTL_RESET_REQ: FULL!L1CTL_PM_REQ start=0 end=124 > DSP Error Status: 8 > PM MEAS: ARFCN=0, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=1, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=2, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=3, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=4, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=5, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=6, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=7, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=8, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=9, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=10, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=11, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=12, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=13, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=14, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=15, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=16, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=17, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=18, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=19, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=20, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=21, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=22, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=23, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=24, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=25, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=26, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=27, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=28, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > PM MEAS: ARFCN=29, 0 dBm at baseband, -138 dBm at RF > DSP Error Status: 8 > > > > ---------- Forwarded message ---------- > From: Sylvain Munaut <246tnt(a)gmail.com> > To: tom mc loughlin <tomei9dl(a)gmail.com> > Cc: baseband-devel <baseband-devel(a)lists.osmocom.org> > Date: Fri, 25 Jul 2014 12:54:02 +0200 > Subject: Re: Mobile testing branch > Hi, > > > I have built Osmocommbb with testing branch and I want to run Mobile app > > allowing me to make a call via my local network. > > All goes well in the build but I am unable to register on my own network > > while using a genuine network sim. > > This is output from my compal_e88/layer1.compalram.bin. > > As you can see all looks good with signal levels fairly ok until this > point > > and then level drops to -138 dbm and there it stays on all chanells. > > I have tried this with 3 different sims and all is the same. > > Can someone help? > > Use master, not testing. > > > > > ---------- Forwarded message ---------- > From: "TSAREGORODTSEV, Yury" <yury(a)bridgecommunication.co.uk> > To: baseband-devel(a)lists.osmocom.org > Cc: > Date: Fri, 25 Jul 2014 11:28:07 +0000 (UTC) > Subject: mobile app simulated-delay > Hi, > anyone can tell why phone won't register in network > if simulated-delay more then -2 ? > > > > > Thx a lot, > Yury > > > _______________________________________________ > baseband-devel mailing list > baseband-devel(a)lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/baseband-devel > >

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel