baseband-devel Digest, Vol 54, Issue 15

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.

tom mc loughlin tomei9dl at gmail.com
Fri Jul 25 20:50:00 UTC 2014


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 at lists.osmocom.org>
wrote:

> Send baseband-devel mailing list submissions to
>         baseband-devel at 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 at lists.osmocom.org
>
> You can reach the person managing the list at
>         baseband-devel-owner at 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 at gmail.com>
> To: baseband-devel at 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 at gmail.com>
> To: tom mc loughlin <tomei9dl at gmail.com>
> Cc: baseband-devel <baseband-devel at 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 at bridgecommunication.co.uk>
> To: baseband-devel at 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 at lists.osmocom.org
> https://lists.osmocom.org/mailman/listinfo/baseband-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20140725/22479e0d/attachment.htm>


More information about the baseband-devel mailing list