Hi Baseband,
I'm trying to figure out if there's any standard set for how often a
handset should scan for signal when out of coverage. I haven't been
able to find much, just the following in 3GPP TS 22.011:
3.2.2.2 At switch-on or recovery from lack of coverage
If registration cannot be achieved on any PLMN, the UE shall indicate
"no service" to the user, wait until a new PLMN is detected, or new
location areas of an allowed PLMN are found which are not in the
forbidden LA list(s), and then repeat the procedure. When registration
cannot be achieved, different (discontinuous) PLMN search schemes may
be used in order to minimize the access time while maintaining battery
life, e.g. by prioritising the search in favour of BCCH carriers which
have a high probability of belonging to an available and allowable
PLMN.
Sounds like it's up to each manufacturer to just pick a delay? Any
other thoughts/intuitions which might help us bound this number?
Thanks!
To whom it may concern:
Has anyone implemented RRLP request handling in osmocombb's layer 3? We
are particularly interested in the transmission of GPS data.
Additionally, if anyone has any helpful advice/documentation on the
message format which is more detailed or useful than the gsm 04.31 spec we
would greatly appreciate it.
Thanks you,
Max Feldman
Hi all!
This is the announcement for the 2nd incarnation of our bi-weekly
Osmocom Berlin meeting.
April 25, 7pm @ CCC Berlin, Marienstr. 11, 10113 Berlin
The schedule is as follows:
19:00 Introduction into the TETRA base station located @ CCCB
For quite some time, there is a full TETRA base station located
in the Berlin CCC, consisting of two base radios (BR), a site
controller (TSC), an auto-tuning cavity combiner and other
equipment. The talk will introduce the architecture of the
system and the current status of getting it running.
20:00 Presenting the CC32RS512 / towards an Osmocom Card OS
The CC32RS512 is a flash-based smart card controller to which
the documentation is available without NDA. This means that we
finally are able to implement a Smart Card OS (COS) as free
software.
20:30 Informal discussions
If you are interested to show up, feel free to do so. There is no
registration required. If the initial part is not interesting to you,
feel free to join us later at 20:30. The meeting is free as in "free
beer", despite no actual free beer being around ;)
Regards,
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)
Hi all:
I've been on and off trying to set up Osmocom-BB for quite a while now. I've
tried using several Cxxx with no luck of being able to lock on to a cell. I
shifted to Pirelli_dpl10 hoping to avoid configuration change required of
dual-band phones to work with Osmocom-BB but no positive outcome.
I'm using Sylvain testing branch with transmit enabled; create mobile config
file with PCS1900 and GSM850 as the only bands to be supported. For US
Motorola dual band phones c139 and c155, I modified the required section of
the rffe file to support PCS1900; and for Pirelli, I made the recommended
modification to UART option before being able to communicate with the
device. I guess I did all what need to be done for preliminary setting.
Layer1 load perfectly but mobile application never work.
Sim reader worked perfectly; Sim information was read, mobile app used the
previous PLMN information to start power measurement. I was able to get
average power of -92dB with Pirelli but while still performing the scanning
the result output repeatedly fix prim_pm.c file with value to be overwrite
message.
I guess the issue has to do with passing the right parameters to layer1 to
perform ARFCN scanning in order to obtain power measurement of the available
channels. I'm not really sure if there is need to modify any part of layer1
or Rita files before accurate measurement could be done for PCS1900.
I'm not that deeply knowledgeable in GSM standard but I can still figure out
what to do if any hint
is given toward what need to be done before PCS1900 band will work with any
osmocom-compatible phone.
I know that some people have worked on PCS1900 and GSM850 but there is no
information
towards what need to be done in terms of specific file to hack to change
default GSM900 and DCS1800 bands configurations to GSM850 and PCS1900.
I am pretty much sure that If I were in Europe I would by now step up from
trying to make Osmocom lock to a serving cell to the point studying the code
to work for a specific purpose. I am using the project as part of thesis
work to analyze the Um interface and to explain processes that occur between
BTS and mobile station.
I will so much appreciate it if anyone could be of any help. Thanks.
Rasak
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Basic-Set-Up-For-PCS-1900-tp3927…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hello.
CKSN - Ciphering Key Sequence Number is associated with Kc and is a bit trickier than
trivial counter.
According to GSM 04.08 (p. 278 in v5.3.0 in my case) it's comprised as follows:
* 3 bits - actual key sequence (value 111 seems to be reserved)
* 1 bit - always 0
* 3 bits - CKSN IEI
Could you help me to understand how to properly generate it:
- the last bit (8th) is not specified - does it mean it's always 0?
- what is CKSN IEI and how do I calculate\use it?
- am I right that 3-bit key seq. value is simple counter that I increment with each
Kc generation?
- what do I do when key seq. reach 6 - start over with 0 again?
And of course I'm interested if CKSN-related code is available as part of libosmogsm
or some other open source project: the code is always helpful in understanding and I
don't have to reinvent the wheel :)
best regards,
Max.
Dear all,
I lecture at strathmore university, Kenya, East Africa. For my PhD, i
need to develop a cell-phone model that senses and recognizes a
specific RF frequency from a source. It then submits the value of that
frequency by SMS.
Is it possible to use the OsmocomBB platform to program such a device
using motorola C123?
Ojenge
I am testing mobile app and when the program exit, it occur the flowing errors:
Dropping frame with 85 bit errors
LOSS counter for ACCH 31
Dropping frame with 85 bit errors
Dropping frame with 86 bit errors
Dropping frame with 78 bit errors
LOSS counter for ACCH 30
Dropping frame with 79 bit errors
Dropping frame with 77 bit errors
Dropping frame with 86 bit errors
Hi,
Synopsis
--------
I started on a driver for the MT5921 wlan chip from MediaTek and am now trying
to find developers wo would be interested in this, as I don't have the
necessary knowledge of the whole wireless part, or to determine if trying
this is completely futile.
Available is:
- a (hopefully) nearly complete register-map of the chip
- my initial work of basic communication through its spi interface up to and
including reading the chips eeprom
- a proprietary driver through which it's possible to log the spi-traffic
Also it seems I would be able to provide hardware to interested parties.
MT5921 and MediaTek
-------------------
The MT5921 [1] can be connected via SPI, SDIO, HPI and compact flash. It seems
to be used mostly in phones based on MediaTek SoCs, but also gained a
relatively wide spread through the ebook readers from Qisda (Oyo in germany,
Fnacbook / Sagem Binder in france, bq Avant in spain, Positivo Alfa in brazil,
Mr. Book in russia, ...).
MediaTek itself does not provide any information about the chip and also
does not seem to answer inquiries [via various channels] at all.
From talks to some of the device makers, I gathered that MediaTek also
completely refuses to release any material to them. The proprietary driver
mentioned above also seems to have been made by MediaTek directly.
The device
----------
I'm working on the Qisda ebook readers mentioned above (S3C2416 with 400MHz or
S3C2450 with 533MHz depending on the device). The overall support at this
point is quite good, including the driver for the epd controller, multitouch-
capable capacitive touchscreen, suspending and resuming the device.
Impressions of these devices can be found on [2].
I have a spare "Oyo 1" that was donated to me, that I could redonate for this
and it seems I could gain the support of one of the device makers, who will
also supply a small number of devices, if I can find interested developers
for this endavour.
State of the driver
-------------------
The kernel release by Alcatel of their OT890 [3] did include headers describing
most of the chips registers and the eeprom structure of the sdio version. It
explicitly did non include sources for the wifi driver itself.
For things like chip signature and mac address, the eeprom struct also matches
the spi version, so I guess it could match also for most of the non-sdio stuff
On the Qisda devices modifying the underlying spi-dev driver makes it possible
to log the traffic the module sends to and receives from the chip.There also
exists a debug-version of the proprietary module that emits more in-depth
information on what it's currently doing [4].
I also build a crude script [5] to convert these dumps to a representation of
registers and constants form the header. There are probably better tools around
to do such things, but it made the reading of the dumps easier, like:
Array
(
[mode] => write
[register] => MCR_RFCR
[reg-desc] => Receive Filter Control Register
[valstr] => RFCR_RX_SAMEBSSIDPRORESP_CTRL | RFCR_RX_SAMEBSSIDBCN_CTRL
[unmatched] => 0x0
)
As written above, bringup of and basic communication with the device
works and I'm lacking the necessary knowledge of the whole wireless part.
So, if anybody is interested in this I would be very happy :-) .
Thanks
Heiko
[1] http://www.mediatek.com/en/Products/product_content.php?sn=48
[2] http://www.youtube.com/user/MMind81
[3] http://sourceforge.net/projects/alcatel/files/
[4] examples in
https://gitorious.org/oyo-hack/kernel/blobs/topic/board/sg060/drivers/net/w…https://gitorious.org/oyo-hack/kernel/blobs/topic/board/sg060/drivers/net/w…
[5] https://gitorious.org/oyo-hack/kernel/blobs/topic/board/sg060/drivers/net/w…
