Hi!
I've been playing with some code earlier today, trying to reuse the RR
implementation of 'mobile' but without 'MM' and '03.22' code. Next step was to
play with RR+MM but without 03.22.
Both were not that easy to do, given the various different function calls
between those modules.
While trying to resolve it, I discovered that we have many sequences like
gsm322_msgb_alloc() followed by some error checking and a final
gsm322_plmn_senmsg(). Similar pattersn could be seen for gsm48_mmevent.
I've tried to simplify/unify this code a bit, as you can see from the
attached patches (also in laforge/mobile_event branch). It's not tested
yet, but I would like to get some comments on it.
Initially I thought to use libosmocore signal code, but then signals are
_emitted_, and they don't fit the picture where we have some incoming events
into e.g. 03.22 code - as all the events are already labelled GSM322
and thus by the recipient, not its originator.
So now there is one gsm322_event_input() and a gsm48_mmevent_input()
function each. Somebody who wants to reuse partial 'mobile' code can simply
provide stub functions for either one of those (or both)...
The goal of this exercise is to have a tool that can open a dedicated
channel to a user-specified cell and then send user-specified messages
while optionally taking care of loc upd / auth / ciphering in order
to make the network happy.
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)
Hello,
I noticed that when I start the mobile application, after the phone chooses a specific channel I get different messages regarding IMSI saying that it's not for us. What are these messages? Phones that camp on this channel? If so, I tried turning off/on a phone from the same operator but I can't see my IMSI showing up.
Hello,
I have created few patches that aim to add abstraction for gpio
handling. First patch adds functions:
gpio_config - configure gpio as input/output
gpio_read - read state of gpio(s)
gpio_write - write/toggle state of gpio(s)
gpio_set_handler - enables interrupt on given gpio.
Also changes board init files to make them more sane :-)
Second patch adds interrupt demuxing and masking into keypad driver as
gpio and keypad are handled by the same peripheral.
It would make sense to split the keypad driver into calypso-specific
and generic stuff once there is support for other chipsets.
Also note that interrupt levels in datasheet are active low (p.120),
my testing shows otherwise.
Michal Demin
Hi,
sorry if I shouldn`t write correclly, i`m not that good in english.
i have a Motorola c118 and this usb/serial cable:
http://www.gsmbase.de/shop/show_product.php?products_id=620 here
my problem:
compiling was successfully.
than i run osmocon:
./osmocon -p /dev/ttyUSB0 -m c123xor
/home/test/install/osmocom-bb/src/target/firmware/board/compal_e88/layer1.ramload.bin
i pressed power on the phone.
nothing happend.
again.
nothing happend, no output, no upload/download to/from the phone...
what is my fault? can you help me?
i have tested it with: -m 123 ; -m 118xor ; -m 118 (the same thing)
my system is ubuntu 10.10 (not in a virtual box or something else).
thanks a lot,
tobsen
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/doesn-t-get-output-from-osmocon-…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hi guys,
I think it is desparately needed that we write more documentation about the
'mobile' program in our wiki. It just occurred to me today that no such
page exists so far, and I've created it at
http://bb.osmocom.org/trac/wiki/mobile
I believe a simple reference of commands is not even all that important (after
all, there is 'list' in the telnet interface), but somethnig like common
scenarios like
* behaving like a normal phone with cell-selection (using real sim)
* behaving like a normal phone with cell-selection (using simulated sim)
* how to lock to a certain ARFCN/cell
* how to manually trigger location area update
* how to send/receive sms
* how to make mo/mt phone call
It would be great if some of the more experienced people would find a
couple of minutes to contribute to it. Thanks a lot in advance.
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)
This is a Mailman mailing list bounce action notice:
List: baseband-devel
Member: arslangali(a)inbox.ru
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.
>> To make it work you have to recompile the module pl2303, with this
>> patch
>> (my kernel is 2.6.35.10-74.fc14.i686). Be careful to setup the right
>> values in the kernel root Makefile in order to fit your running
>> kernel.
>
> Not necessarily. You should also be able to check without recompiling.
>
> Just go to the drivers-directory in sysfs:
>
> cd /sys/bus/usb/drivers/<driver>
>
which <driver>?I cannot find any pl2303 driver here. (Debian and ubuntu
8.04)> and echo the data to the file new_id (as root):
>
> echo "067b 0307" > new_id
>
> This should bind the driver to the new_id.
Niko