From steve at steve-m.de  Fri Jan 21 16:47:13 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Fri, 21 Jan 2011 17:47:13 +0100
Subject: Use OsmocomBB as OpenBTS / airprobe clock generator
In-Reply-To: <4BC1F0D1.5010809@steve-m.de>
References: <20100410214745.GB3284@prithivi.gnumonks.org>	<4BC1099B.8070504@steve-m.de>	<20100411053705.GF3284@prithivi.gnumonks.org>
	<4BC1F0D1.5010809@steve-m.de>
Message-ID: <4D39B891.3070306@steve-m.de>

Hi,

On 11.04.2010 17:54, Steve Markgraf wrote:

>> The third one is MCLK, i.e. the clock that the Calypos PLL feeds into
>> the ARM core.
>
> Ah, okay. But this one isn't accessible on all currently known phones
> anyway.

Just as an update on this idea: The Pirelli DP-L10 I have been playing 
around with recently exposes the MCLK pin.

I've added a summary in the wiki:

http://bb.osmocom.org/trac/wiki/PirelliDPL10#Phoneasclockgenerator

Regards,
Steve



From kaleido.scope at msn.com  Wed Jan 26 09:58:42 2011
From: kaleido.scope at msn.com (kaleidoscope)
Date: Wed, 26 Jan 2011 01:58:42 -0800 (PST)
Subject: Trouble building Osmocom
In-Reply-To: <AANLkTikHikm19rIQS9qzN2H0ajrcTL04aHdjkHdHqD7R@mail.gmail.com>
References: <AANLkTilwSlFup1604NJ7DUL_rg4QWfdKRYy4CanufQeh@mail.gmail.com>
	<4C0E3219.7040103@selfish.org> <4C0E41A5.8030304@selfish.org>
	<4C0E464F.1050601@selfish.org> <4C0E49D3.9060400@selfish.org>
	<AANLkTiklORtgMHjO8n40J33AdjjwFUqtOkGBthHTMJEZ@mail.gmail.com>
	<4C0E5300.1020604@gmail.com>
	<AANLkTikHikm19rIQS9qzN2H0ajrcTL04aHdjkHdHqD7R@mail.gmail.com>
Message-ID: <1296035922452-2352768.post@n3.nabble.com>


actually I met the same problem. I read the post again and again, just didn't
find the answer. how did you get it done? don't understand why ppl talk a
lot just don't make it clear. 
thousand thanks.
-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/Trouble-building-Osmocom-tp879206p2352768.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From laforge at gnumonks.org  Sat Jan 22 13:09:33 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Sat, 22 Jan 2011 14:09:33 +0100
Subject: Wanted: Osmocom logo
In-Reply-To: <AANLkTikeyGOS3me0LPS57Hkw3HQkDKEecO=N6EvOc9RF@mail.gmail.com>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de> <4C57D4FA.20107@mail.tsaitgaist.info>
	<AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>
	<4C595701.50708@mail.tsaitgaist.info>
	<4C617226.30403@mail.tsaitgaist.info>
	<AANLkTikeyGOS3me0LPS57Hkw3HQkDKEecO=N6EvOc9RF@mail.gmail.com>
Message-ID: <20110122130933.GJ9164@prithivi.gnumonks.org>

Hi all,

sorry for never really finishing up with this topic.

As you can see from http://bb.osmocom.org/ as well as
http://openbsc.osmocom.org/ and http://tetra.osmocom.org/, I have now used the
second of your logo variants.

Wold you be able (and willing) to do the same logo but continue it with
uppercase TETRA, BB and SECURITY, using the same font/style?

This way we can differentiate the logo depending on the project site that
people visit.

Thanks in advance,

	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From steve at steve-m.de  Sat Jan 22 14:43:50 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Sat, 22 Jan 2011 15:43:50 +0100
Subject: Wanted: Osmocom logo
In-Reply-To: <20110122130933.GJ9164@prithivi.gnumonks.org>
References: <20100730165851.GW13645@prithivi.gnumonks.org>
	<4C56B9AB.60903@mail.tsaitgaist.info>
	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>
	<4C574FE5.6020303@steve-m.de> <4C57D4FA.20107@mail.tsaitgaist.info>
	<AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>
	<4C595701.50708@mail.tsaitgaist.info>
	<4C617226.30403@mail.tsaitgaist.info>
	<AANLkTikeyGOS3me0LPS57Hkw3HQkDKEecO=N6EvOc9RF@mail.gmail.com>
	<20110122130933.GJ9164@prithivi.gnumonks.org>
Message-ID: <4D3AED26.3060708@steve-m.de>

Hi Harald,

On 22.01.2011 14:09, Harald Welte wrote:

> Wold you be able (and willing) to do the same logo but continue it with
> uppercase TETRA, BB and SECURITY, using the same font/style?
>
> This way we can differentiate the logo depending on the project site that
> people visit.

See the attached Inkscape *.svgz and prerendered *.png files for trac.

DECT and OpenBSC are just meant as a RFC, otherwise just take the
osmocom.png for the OpenBSC trac (since there's a small correction in
the first 'm').

Regards,
Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_security.png
Type: image/png
Size: 14207 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110122/1dbc9ef0/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_tetra.png
Type: image/png
Size: 14936 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110122/1dbc9ef0/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocombb.png
Type: image/png
Size: 14426 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110122/1dbc9ef0/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_logo.png
Type: image/png
Size: 13331 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110122/1dbc9ef0/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_logos.svgz
Type: image/svg+xml
Size: 12600 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110122/1dbc9ef0/attachment.svg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_dect.png
Type: image/png
Size: 14788 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110122/1dbc9ef0/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_openbsc.png
Type: image/png
Size: 14562 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110122/1dbc9ef0/attachment-0005.png>

From kaber at trash.net  Sat Jan 22 18:04:39 2011
From: kaber at trash.net (Patrick McHardy)
Date: Sat, 22 Jan 2011 19:04:39 +0100
Subject: Wanted: Osmocom logo
In-Reply-To: <4D3AED26.3060708@steve-m.de>
References: <20100730165851.GW13645@prithivi.gnumonks.org>	<4C56B9AB.60903@mail.tsaitgaist.info>	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>	<4C574FE5.6020303@steve-m.de>
	<4C57D4FA.20107@mail.tsaitgaist.info>	<AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>	<4C595701.50708@mail.tsaitgaist.info>	<4C617226.30403@mail.tsaitgaist.info>	<AANLkTikeyGOS3me0LPS57Hkw3HQkDKEecO=N6EvOc9RF@mail.gmail.com>	<20110122130933.GJ9164@prithivi.gnumonks.org>
	<4D3AED26.3060708@steve-m.de>
Message-ID: <4D3B1C37.3070909@trash.net>

On 22.01.2011 15:43, Steve Markgraf wrote:
> Hi Harald,
> 
> On 22.01.2011 14:09, Harald Welte wrote:
> 
>> Wold you be able (and willing) to do the same logo but continue it with
>> uppercase TETRA, BB and SECURITY, using the same font/style?
>>
>> This way we can differentiate the logo depending on the project site that
>> people visit.
> 
> See the attached Inkscape *.svgz and prerendered *.png files for trac.
> 
> DECT and OpenBSC are just meant as a RFC, otherwise just take the
> osmocom.png for the OpenBSC trac (since there's a small correction in
> the first 'm').

I've put up the DECT logo on dect.osmocom.org, thanks Steve!



From kevredon at mail.tsaitgaist.info  Sat Jan 22 23:33:58 2011
From: kevredon at mail.tsaitgaist.info (Kevin Redon)
Date: Sun, 23 Jan 2011 00:33:58 +0100
Subject: Wanted: Osmocom logo
In-Reply-To: <4D3AED26.3060708@steve-m.de>
References: <20100730165851.GW13645@prithivi.gnumonks.org>	<4C56B9AB.60903@mail.tsaitgaist.info>	<AANLkTime30bC5Oxb=q7ak8c2Vv=o4EPznVQXY3dkSps_@mail.gmail.com>	<4C574FE5.6020303@steve-m.de>
	<4C57D4FA.20107@mail.tsaitgaist.info>	<AANLkTi=7HiXKGOyq-rsmOyefrkKzh3vbYTOr8xrxEcTx@mail.gmail.com>	<4C595701.50708@mail.tsaitgaist.info>	<4C617226.30403@mail.tsaitgaist.info>	<AANLkTikeyGOS3me0LPS57Hkw3HQkDKEecO=N6EvOc9RF@mail.gmail.com>	<20110122130933.GJ9164@prithivi.gnumonks.org>
	<4D3AED26.3060708@steve-m.de>
Message-ID: <4D3B6966.1060006@mail.tsaitgaist.info>

Hi,

To be able to add more extensions, I've added the text as text (using
Yanone Kaffeesatz font http://www.yanone.de/typedesign/kaffeesatz/).
The paths are still present (to use when the font is not available).
I also organized in layers (using inkscape) and added some metadata
(title, project page, license, material used, authors, ...)

kevin

On 01/22/2011 03:43 PM, Steve Markgraf wrote:
> Hi Harald,
> 
> On 22.01.2011 14:09, Harald Welte wrote:
> 
>> Wold you be able (and willing) to do the same logo but continue it with
>> uppercase TETRA, BB and SECURITY, using the same font/style?
>>
>> This way we can differentiate the logo depending on the project site that
>> people visit.
> 
> See the attached Inkscape *.svgz and prerendered *.png files for trac.
> 
> DECT and OpenBSC are just meant as a RFC, otherwise just take the
> osmocom.png for the OpenBSC trac (since there's a small correction in
> the first 'm').
> 
> Regards,
> Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom_logos_inkscape.svgz
Type: image/svg+xml
Size: 8576 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110123/e5a6e555/attachment.svg>

From mki at mki-consult.de  Tue Jan  4 10:07:29 2011
From: mki at mki-consult.de (mki)
Date: Tue, 4 Jan 2011 02:07:29 -0800 (PST)
Subject: Newbie: C123 + layer1.compalram.bin + layer23
In-Reply-To: <AANLkTi=BD+V4PakvYK2YU8xZw3MZKfMHv5jGFGcPYdUn@mail.gmail.com>
References: <87pqve18qk.fsf@chdir.org>
	<AANLkTi=BD+V4PakvYK2YU8xZw3MZKfMHv5jGFGcPYdUn@mail.gmail.com>
Message-ID: <1294135649498-2190744.post@n3.nabble.com>


same newbie prob here --

1. starting osmocon:
osmocon -m c123xor -p /dev/tty.usbserial
firmware/board/compal_e88/layer1.compalram.bin

2. starting layer23 (the arfcn is from my "field test" (iPhone)):
layer23 -i 224.0.0.1 -a 46 -d

3. press the power button

like a minute I receive messages then layer23 is saying:

<000b> l1ctl.c:155 SDCCH/8(0) on TS1 (0913/15/00) -72 dBm: 4d 3b 42 69 1a db
34 d3 a4 0b 1d 0a 4d 98 ba 52 50 e8 d2 c2 42 8c 81 
<000b> l1ctl.c:210 Dropping frame with 78 bit errors
<000b> l1ctl.c:155 SDCCH/8(0) on TS1 (0913/14/00) -71 dBm: 6d f2 0a db 05 54
70 cd a4 0b 1d 0a 94 99 ba 52 50 e8 d2 c2 c2 68 81 
<000b> l1ctl.c:210 Dropping frame with 72 bit errors
<000b> l1ctl.c:155 SDCCH/8(0) on TS1 (0913/20/32) -72 dBm: 84 ea f1 c3 cd 4a
dc da e4 51 1d 33 b6 29 29 98 c1 24 5d 2e 9a 3f 73 
<000b> l1ctl.c:210 Dropping frame with 67 bit errors
<000b> l1ctl.c:155 SDCCH/8(0) on TS1 (0913/13/00) -72 dBm: e2 96 ef f8 8b dc
84 85 e2 29 d4 10 ff 6e 82 c0 17 1e f6 db 29 d9 9f 
<000b> l1ctl.c:210 Dropping frame with 81 bit errors
<000b> l1ctl.c:155 SDCCH/8(0) on TS1 (0913/12/00) -72 dBm: 16 d6 61 e7 c2 4a
4c 2f 6c bd 8c 32 b6 29 29 6a 99 f2 ee 69 28 75 a5 
<000b> l1ctl.c:210 Dropping frame with 76 bit errors

osmocon is saying:

L1CTL_RESET_REQ: FULL!LOST 1641!
EMPTY
L1CTL_FBSB_REQ (arfcn=46, flags=0x7)
Starting FCCH RecognitionFB0 (1523172:1): TOA=  768, Power= -73dBm, Angle=
2625Hz
FB1 (1523182:8): TOA= 9475, Power= -73dBm, Angle=  464Hz
  fn_offset=1523181 (fn=1523182 + attempt=8 + ntdma = 7)m  delay=9
(fn_offset=1523181 + 11 - fn=1523182 - 1
  scheduling next FB/SB detection task with delay 9
=>FB @ FNR 1523181 fn_offset=1523181 qbits=2716
Synchronize_TDMA
LOST 2921!
SB2 (330721:2): TOA=   29, Power= -73dBm, Angle=  324Hz
=> SB 0x0080c66d: BSIC=27 fn=1205386(909/ 0/ 1) qbits=24
Synchronize_TDMA
=>FB @ FNR 330719 fn_offset=1205385 qbits=4932
LOST 1912!
nb_cmd(0) and rxnb.msg != NULLL1CTL_DM_EST_REQ (arfcn=46, chan_nr=0x41,
tsc=3)
L1CTL_DATA_REQ (link_id=0x00)
ul=00811d68, ul->payload=00811d6c, data_ind=00811d6c,
data_ind->data=00811d6c l3h=00811d6c
LOST 2110!

what do i wrong here???

-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/Newbie-C123-layer1-compalram-bin-layer23-tp1694860p2190744.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From mki at mki-consult.de  Thu Jan  6 11:54:13 2011
From: mki at mki-consult.de (mki)
Date: Thu, 6 Jan 2011 03:54:13 -0800 (PST)
Subject: Newbie: C123 + layer1.compalram.bin + layer23
In-Reply-To: <1294135649498-2190744.post@n3.nabble.com>
References: <87pqve18qk.fsf@chdir.org>
	<AANLkTi=BD+V4PakvYK2YU8xZw3MZKfMHv5jGFGcPYdUn@mail.gmail.com>
	<1294135649498-2190744.post@n3.nabble.com>
Message-ID: <1294314853703-2205156.post@n3.nabble.com>


has nobody an Idea about my problem??
-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/Newbie-C123-layer1-compalram-bin-layer23-tp1694860p2205156.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From holger at freyther.de  Thu Jan  6 11:59:42 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 06 Jan 2011 12:59:42 +0100
Subject: Newbie: C123 + layer1.compalram.bin + layer23
In-Reply-To: <1294314853703-2205156.post@n3.nabble.com>
References: <87pqve18qk.fsf@chdir.org>	<AANLkTi=BD+V4PakvYK2YU8xZw3MZKfMHv5jGFGcPYdUn@mail.gmail.com>	<1294135649498-2190744.post@n3.nabble.com>
	<1294314853703-2205156.post@n3.nabble.com>
Message-ID: <4D25AEAE.4000400@freyther.de>

On 01/06/2011 12:54 PM, mki wrote:
> 
> has nobody an Idea about my problem??

Hi,

you have not forumalated a question that can be answered in a very specific
way? You seem to have an expectation that the invocation of tools is doing
something, but they don't do what you think they should do.

Maybe as a start you should describe what you expect should happen and what
happens instead? Maybe people can then help you more.



From mki at mki-consult.de  Thu Jan  6 12:08:21 2011
From: mki at mki-consult.de (mki)
Date: Thu, 6 Jan 2011 04:08:21 -0800 (PST)
Subject: Newbie: C123 + layer1.compalram.bin + layer23
In-Reply-To: <4D25AEAE.4000400@freyther.de>
References: <87pqve18qk.fsf@chdir.org>
	<AANLkTi=BD+V4PakvYK2YU8xZw3MZKfMHv5jGFGcPYdUn@mail.gmail.com>
	<1294135649498-2190744.post@n3.nabble.com>
	<1294314853703-2205156.post@n3.nabble.com>
	<4D25AEAE.4000400@freyther.de>
Message-ID: <1294315701371-2205227.post@n3.nabble.com>


sorry,
my question is, what is with the dropped frames in my submited output of
layer23 is that ok? or not? and if not what must i do?
-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/Newbie-C123-layer1-compalram-bin-layer23-tp1694860p2205227.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From 246tnt at gmail.com  Thu Jan  6 12:18:12 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Thu, 6 Jan 2011 13:18:12 +0100
Subject: Newbie: C123 + layer1.compalram.bin + layer23
In-Reply-To: <1294315701371-2205227.post@n3.nabble.com>
References: <87pqve18qk.fsf@chdir.org>
	<AANLkTi=BD+V4PakvYK2YU8xZw3MZKfMHv5jGFGcPYdUn@mail.gmail.com>
	<1294135649498-2190744.post@n3.nabble.com>
	<1294314853703-2205156.post@n3.nabble.com>
	<4D25AEAE.4000400@freyther.de>
	<1294315701371-2205227.post@n3.nabble.com>
Message-ID: <AANLkTinVXg9gSRqYmP7sv0w7Z1xvHmtKRr9V0+EZpajz@mail.gmail.com>

> sorry,
> my question is, what is with the dropped frames in my submited output of
> layer23 is that ok? or not? and if not what must i do?

layer23 is a debug tool that can only really be used on a network you
control, because it will follow any immediate assignement without  any
further check (refer to GSM 04.08 if you don't understand what that
means)

On a commercial network, it won't do anything good. The output you see
is normal if you run it on a real network and not a test network you
control.

Cheers,

    Sylvain



From mki at mki-consult.de  Fri Jan  7 16:03:27 2011
From: mki at mki-consult.de (mki)
Date: Fri, 7 Jan 2011 08:03:27 -0800 (PST)
Subject: Newbie: C123 + layer1.compalram.bin + layer23
In-Reply-To: <AANLkTinVXg9gSRqYmP7sv0w7Z1xvHmtKRr9V0+EZpajz@mail.gmail.com>
References: <87pqve18qk.fsf@chdir.org>
	<AANLkTi=BD+V4PakvYK2YU8xZw3MZKfMHv5jGFGcPYdUn@mail.gmail.com>
	<1294135649498-2190744.post@n3.nabble.com>
	<1294314853703-2205156.post@n3.nabble.com>
	<4D25AEAE.4000400@freyther.de>
	<1294315701371-2205227.post@n3.nabble.com>
	<AANLkTinVXg9gSRqYmP7sv0w7Z1xvHmtKRr9V0+EZpajz@mail.gmail.com>
Message-ID: <1294416207566-2212592.post@n3.nabble.com>


Hi,
sorry i misunderstand layer23, 
i am searching for a possibility to log my traffic on the um interface, 
to check out if my real phone traffic is encrypted and to what bts i am
connected(is it the real network or a catcher).

PS: all that, i want to do it on a real network.

-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/Newbie-C123-layer1-compalram-bin-layer23-tp1694860p2212592.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From vamposdecampos at gmail.com  Fri Jan 14 19:20:48 2011
From: vamposdecampos at gmail.com (Alex Badea)
Date: Fri, 14 Jan 2011 21:20:48 +0200
Subject: TODO: OsmocomBB to continually iterate over all cells and dump SI
In-Reply-To: <4D123D01.1060008@lakedaemon.net>
References: <20101222165809.GG8073@prithivi.gnumonks.org>	<4D123417.9020307@steve-m.de>
	<4D123D01.1060008@lakedaemon.net>
Message-ID: <4D30A210.30000@gmail.com>

On 2010-12-22 20:01, Jason wrote:
>> So what's missing is really only the PCAP support...
>
> would you want libpcap (a lot of unnecessary code), or just use the file
> and packet headers?

Here's some hackish code I wrote which might be useful.  I've recently 
been abroad (in Austria), and wanted to run cell_log stand-alone on my 
GTA02 without lugging a laptop around.

I ran cell_log on the GTA02 application processor (with hacked timers to 
spend a longer time camped on each ARFCN), sending gsmtap packets to 
localhost.  I then had a small program[1] which receives these and 
writes them to a file in .pcap format.

For simplicity (and somewhat lower overhead) only the raw GSMTAP payload 
is written, and the linktype is set to DLT_USER0.  A small wireshark 
patch[2] then allows these captures to be read directly[3].

Cheers,
Alex



[1], [2] attached.
[3] e.g., wireshark -o "uat:user_dlts:\"User 0 
(DLT=147)\",\"gsmtap\",\"0\",\"\",\"0\",\"\""
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gsmtap_cap.c
Type: text/x-csrc
Size: 1930 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110114/707f009e/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wireshark-gsmtap.patch
Type: text/x-diff
Size: 506 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110114/707f009e/attachment-0001.bin>

From wolfram at the-dreams.de  Sun Jan  2 11:19:22 2011
From: wolfram at the-dreams.de (Wolfram Sang)
Date: Sun, 02 Jan 2011 12:19:22 +0100
Subject: Toolchain tests, problems and a few workarounds...
Message-ID: <4D205F3A.2060201@the-dreams.de>

Hi,

at 27c3, I tested some toolchains with osmocom-bb and found a few
build-problems, even with the recommended gnuarm-3.4.3. I want to
document them here, so other people can find hints about it.

*** GNUARM 3.4.3 TOOLCHAIN

master branch
=============

../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory

Holger suggested to manually remove this line. It is fixed upstream
in libosmocore and osmocom-bb needs to be synced to it. Please do :)

remotes/origin/steve-m/loader_sciphone
======================================

1) First problem is:

In file included from ../../include/osmocore/msgb.h:23,
                 from ../../src/msgb.c:27:
/home/wsa/Dev/osmocom-bb/src/target/firmware/include/stdint.h:13:25: stdint.h: No such file or directory

Cherry-picking e0a605819c39187a494e43cf591f2e79a9d9903f (stdint.h: Next attempt at making this work with various compilers) helps.

2) It then runs into the problem of the master branch.

3) After this is fixed, I get

../../../src/codec/gsm610.c:24:20: stdint.h: No such file or directory
../../../src/codec/gsm610.c:33: error: parse error before "gsm610_bitorder"

which needs 733c894c18c127ce5c023e39609b7d2b9e748e7e (build: Use absolute path in the CFLAGS for libosmocore target build) as a fix.

4) This then, leads to:

arm-elf-ld: address 0x400054d4 of board/mt62xx/loader.mtkram.elf section .text is not within region LRAM

which is sadly also present when you just cherry-pick the main patch

d04761d19c432201f7c0f10c72f788fb695d466a ([WIP] Modify loader for use as first stage bootloader on MT62xx devices)

on top of current master + its build fix. So, does it seem sensible to simply
rebase this branch to master which would eliminate the first three problems?
Or at least cherry-pick the above fixes?

Also, the workarounds for gcc3 do not look very sustainable (see custom stdint.h).
Is it a mid-term option to remove that stuff if a reliable pre-built gcc4 is
available? (I am working on that, see below).

BTW the linker error was not further worked on yet. I got a prebuilt binary now.
It is possibly helpful to put it on the G2-wikipage, so people wanting to
work on the Linux-support only are spared from the above hassle.

*** CUSTOM 4.3.2 TOOLCHAIN

every branch
============

The configure-stage of libosmocom already fails for the target with error
77. The config.log says in detail:

configure:3231: checking whether the C compiler works
configure:3253: arm-elf-gcc -Os -ffunction-sections -I/home/wsa/Dev/osmocom-bb/src/target/firmware/include   conftest.c  >&5
/home/opt/OSELAS.Toolchain-1.99.3/arm-elf/gcc-4.3.2-newlib-1.16.0-binutils-2.18/bin/../lib/gcc/arm-elf/4.3.2/../../../../arm-elf/lib/libc.a(lib_a-exit.o): In function `exit':
/home/mkl/himalia-pengutronix/toolchain/releases/OSELAS.Toolchain-1.99.3.6/platform-arm-elf-gcc-4.3.2-newlib-1.16.0-binutils-2.18/build-target/newlib-1.16.0/newlib/libc/stdlib/exit.c:65: undefined reference to `_exit'
/home/opt/OSELAS.Toolchain-1.99.3/arm-elf/gcc-4.3.2-newlib-1.16.0-binutils-2.18/bin/../lib/gcc/arm-elf/4.3.2/../../../../arm-elf/lib/libc.a(lib_a-sbrkr.o): In function `_sbrk_r':
/home/mkl/himalia-pengutronix/toolchain/releases/OSELAS.Toolchain-1.99.3.6/platform-arm-elf-gcc-4.3.2-newlib-1.16.0-binutils-2.18/build-target/newlib-1.16.0/newlib/libc/reent/sbrkr.c:60: undefined reference to `_sbrk'

27c3 was too interesting ;) so I haven't fixed this yet. The Mac-toolchains
also throw this and I also have seen it on the list before, so I hope I
can work on it the next days.

So much for now. It would be nice if someone with write-access to the repo
could comment on my questions and/or fix the low-hanging fruits. I will 
hopefully be able to send some updates soon, too (famous last words).

It was great to meet you all in person!

All the best,

   Wolfram



From wolfram at the-dreams.de  Tue Jan 18 14:40:27 2011
From: wolfram at the-dreams.de (Wolfram Sang)
Date: Tue, 18 Jan 2011 15:40:27 +0100
Subject: Toolchain tests, problems and a few workarounds...
In-Reply-To: <4D205F3A.2060201@the-dreams.de>
References: <4D205F3A.2060201@the-dreams.de>
Message-ID: <4D35A65B.30900@the-dreams.de>

A small update, good news first:

On 02/01/11 12:19, Wolfram Sang wrote:

> *** GNUARM 3.4.3 TOOLCHAIN
> 
> master branch
> =============
> 
> ../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory

Fixed, thanks.

> remotes/origin/steve-m/loader_sciphone
> ======================================
...
> 4) This then, leads to:
> 
> arm-elf-ld: address 0x400054d4 of board/mt62xx/loader.mtkram.elf section .text is not within region LRAM

Still happens with gnuarm-3.4.3, but not too much of a problem, because...

> *** CUSTOM 4.3.2 TOOLCHAIN
> 
> every branch
> ============
> 
> configure:3231: checking whether the C compiler works
> configure:3253: arm-elf-gcc -Os -ffunction-sections -I/home/wsa/Dev/osmocom-bb/src/target/firmware/include   conftest.c  >&5
> /home/opt/OSELAS.Toolchain-1.99.3/arm-elf/gcc-4.3.2-newlib-1.16.0-binutils-2.18/bin/../lib/gcc/arm-elf/4.3.2/../../../../arm-elf/lib/libc.a(lib_a-exit.o): In function `exit':
> /home/mkl/himalia-pengutronix/toolchain/releases/OSELAS.Toolchain-1.99.3.6/platform-arm-elf-gcc-4.3.2-newlib-1.16.0-binutils-2.18/build-target/newlib-1.16.0/newlib/libc/stdlib/exit.c:65: undefined reference to `_exit'
> /home/opt/OSELAS.Toolchain-1.99.3/arm-elf/gcc-4.3.2-newlib-1.16.0-binutils-2.18/bin/../lib/gcc/arm-elf/4.3.2/../../../../arm-elf/lib/libc.a(lib_a-sbrkr.o): In function `_sbrk_r':
> /home/mkl/himalia-pengutronix/toolchain/releases/OSELAS.Toolchain-1.99.3.6/platform-arm-elf-gcc-4.3.2-newlib-1.16.0-binutils-2.18/build-target/newlib-1.16.0/newlib/libc/reent/sbrkr.c:60: undefined reference to `_sbrk'

... with Michael's patch from today the above is now fixed with the
custom 4.3.2 and it later compiles the loader_sciphone-branch flawlessly
\o/ Compal binaries work, too.

For those interested, our toolchain can be found here:

ftp://ftp.pengutronix.de/pub/oselas/oselas.toolchain-1.99.3.6-arm-elf-gcc-4.3.2-newlib-1.16.0-binutils-2.18_i386.tar.bz2

(Test reports welcome; 4.5.2 is in the making...)

My next step would be to try to get the g2_loader into the master-branch.

Cya,

   Wolfram



From laforge at gnumonks.org  Mon Jan  3 17:39:04 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Mon, 3 Jan 2011 18:39:04 +0100
Subject: HP 8922 at Helmut Singer
Message-ID: <20110103173904.GR20181@prithivi.gnumonks.org>

Hi,

just in case anyone is looking for a HP 8922 MS tester, there is one
available from Helmut Singer.  It has an 'ok but not ridiculously cheap' price,
based on Dieter and my experience.

	http://www.helmut-singer.de/stock/1552426140.html

The 8922 is particularly well suited for layer 1 testing + development. I
personally don't have one (only Racal 6103), and don't want to put another 20kg
of old measurement equipment in my lab...

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From peter at stuge.se  Mon Jan  3 21:32:48 2011
From: peter at stuge.se (Peter Stuge)
Date: Mon, 3 Jan 2011 22:32:48 +0100
Subject: HP 8922 at Helmut Singer
In-Reply-To: <20110103173904.GR20181@prithivi.gnumonks.org>
References: <20110103173904.GR20181@prithivi.gnumonks.org>
Message-ID: <20110103213248.14870.qmail@stuge.se>

Harald Welte wrote:
> just in case anyone is looking for a HP 8922 MS tester, there is one
> available from Helmut Singer.

They are about to scrap it.

--8<--
We do not want to keep this equipment in stock any longer. Nearly
down to scrap price, is this the last chance for enthusiasts and
hobbyists to buy. Offered in "as is" condition only, untested, to
clear.
-->8--

They also have a few other 8922 H test sets, at higher price. Is it
reasonable to assume that the countdown unit is actually in fine
working order, despite their disclaimer?

--8<--
If no order received until January 15, 2011, this unit will be scrapped.
-->8--

How come they decided to scrap this particular unit and not one of
the other 8922s?


//Peter



From enzozordan at gmail.com  Tue Jan  4 04:22:05 2011
From: enzozordan at gmail.com (Enzo Zordan)
Date: Tue, 4 Jan 2011 01:22:05 -0300
Subject: osmocom on windows
Message-ID: <AANLkTikisQcsU4FRDo5HdEJ84WL4c4mA7acAeFj6fqYk@mail.gmail.com>

Hello from Argentina, I'm a 26 years old student of Electronical
Engineering, I'm realy very interesting in this project, I have a C115, so
I'll try to compile the code, but I'm not Linux user yet. Can I run this in
Windows? If not... I'll download a live cd distribution of linux =)

I want to use this c115 as a test field.

Best regards buddy

Enzo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110104/6e33f2c9/attachment.htm>

From technosabby at gmail.com  Sat Jan  8 23:43:25 2011
From: technosabby at gmail.com (Marten Christophe)
Date: Sat, 8 Jan 2011 23:43:25 +0000
Subject: osmocom on windows
In-Reply-To: <AANLkTikisQcsU4FRDo5HdEJ84WL4c4mA7acAeFj6fqYk@mail.gmail.com>
References: <AANLkTikisQcsU4FRDo5HdEJ84WL4c4mA7acAeFj6fqYk@mail.gmail.com>
Message-ID: <AANLkTim=ZUcOQ-00geQTkC6FoMk5CgR9BZOhMMTMoRMt@mail.gmail.com>

 Hi Enzo,

Present phase is not compatible with window, (only using cygbin or other
emulator ) i will suggest you to use ubuntu 10.

Kind regards,
Marten


On Tue, Jan 4, 2011 at 4:22 AM, Enzo Zordan <enzozordan at gmail.com> wrote:

> Hello from Argentina, I'm a 26 years old student of Electronical
> Engineering, I'm realy very interesting in this project, I have a C115, so
> I'll try to compile the code, but I'm not Linux user yet. Can I run this in
> Windows? If not... I'll download a live cd distribution of linux =)
>
> I want to use this c115 as a test field.
>
> Best regards buddy
>
> Enzo.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110108/c2f4a0ba/attachment.htm>

From paul at kristianpaul.org  Sat Jan  8 23:43:30 2011
From: paul at kristianpaul.org (Cristian Paul =?iso-8859-1?Q?Pe=F1aranda?= Rojas)
Date: Sat, 8 Jan 2011 18:43:30 -0500
Subject: osmocom on windows
In-Reply-To: <AANLkTikisQcsU4FRDo5HdEJ84WL4c4mA7acAeFj6fqYk@mail.gmail.com>
References: <AANLkTikisQcsU4FRDo5HdEJ84WL4c4mA7acAeFj6fqYk@mail.gmail.com>
Message-ID: <20110108234330.GC24423@micro.kristianpaul.local>

> Hello from Argentina, I'm a 26 years old student of Electronical

Hola desde Colombia :_)

> Engineering, I'm realy very interesting in this project, I have a C115, so
> I'll try to compile the code, but I'm not Linux user yet. Can I run this in

I think you can, well, is not documented well as must of as do not run
Windows often i think 

So you'll need arm gcc for Cygwing, and actually Cywing is the starting
point
> Windows? If not... I'll download a live cd distribution of linux =)

Sure why not, try get one related to apt package managemetn (Debian,
Ubuntu, etc..)

And then follow:

 http://bb.osmocom.org/trac/wiki/GettingStarted

> 
> I want to use this c115 as a test field.

Good, i think there is Work in Progress support for PCS1900 in case you
needed too.

Regards

Cristian Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110108/b2c64f60/attachment.bin>

From seppel18 at hotmail.com  Wed Jan  5 16:19:31 2011
From: seppel18 at hotmail.com (Sebastian ---)
Date: Wed, 5 Jan 2011 17:19:31 +0100
Subject: Compile Errors
Message-ID: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>


Hi,

I use Ubuntu 9.10, when i try to Compile Osmocom, i get this:

root at r00t-laptop:~# cd /home/r00t/install/osmocom-bb/src
root at r00t-laptop:~/install/osmocom-bb/src# make
cd shared/libosmocore/build-target && ../configure \
            --host=arm-elf-linux --disable-vty --enable-panic-infloop \
            --disable-shared --disable-talloc --disable-tests \
        CC="/home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc" CFLAGS="-Os -ffunction-sections -I/home/r00t/install/osmocom-bb/src/target/firmware/include"
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-elf-linux-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for arm-elf-linux-gcc... /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc accepts -g... yes
checking for /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc... gcc3
checking build system type... i686-pc-linux-gnulibc1
checking host system type... arm-elf-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc... /home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld
checking if the linker (/home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... no
checking for arm-elf-linux-dumpbin... no
checking for arm-elf-linux-link... no
checking for dumpbin... no
checking for link... link -dump -symbols
configure: WARNING: using cross tools not prefixed with host triplet
checking the name lister (link -dump -symbols) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 805306365
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld option to reload object files... -r
checking for arm-elf-linux-objdump... no
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for arm-elf-linux-ar... no
checking for ar... ar
checking for arm-elf-linux-strip... strip
checking for arm-elf-linux-ranlib... no
checking for ranlib... ranlib
checking command to parse link -dump -symbols output from /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc object... failed
checking how to run the C preprocessor... /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... no
checking for inttypes.h... no
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... no
checking for objdir... .libs
checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports -fno-rtti -fno-exceptions... no
checking for /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc option to produce PIC... -fPIC -DPIC
checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc PIC flag -fPIC -DPIC works... yes
checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc static flag -static works... yes
checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports -c -o file.o... yes
checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports -c -o file.o... (cached) yes
checking whether the /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc linker (/home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for ANSI C header files... (cached) yes
checking execinfo.h usability... no
checking execinfo.h presence... no
checking for execinfo.h... no
checking sys/select.h usability... no
checking sys/select.h presence... no
checking for sys/select.h... no
checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports -fvisibility=hidden... no
configure: creating ./config.status
config.status: creating libosmocore.pc
config.status: creating libosmocodec.pc
config.status: creating libosmovty.pc
config.status: creating include/osmocom/Makefile
config.status: creating include/osmocom/vty/Makefile
config.status: creating include/osmocom/codec/Makefile
config.status: creating include/osmocom/crypt/Makefile
config.status: creating include/osmocore/Makefile
config.status: creating include/osmocore/protocol/Makefile
config.status: creating include/Makefile
config.status: creating src/Makefile
config.status: creating src/vty/Makefile
config.status: creating src/codec/Makefile
config.status: creating tests/Makefile
config.status: creating tests/timer/Makefile
config.status: creating tests/sms/Makefile
config.status: creating tests/msgfile/Makefile
config.status: creating tests/ussd/Makefile
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
cd shared/libosmocore/build-target && make
make[1]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target'
make  all-recursive
make[2]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target'
Making all in include
make[3]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include'
Making all in osmocom
make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
Making all in codec
make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec'
make[5]: F?r das Ziel ?all? ist nichts zu tun.
make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec'
Making all in crypt
make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt'
make[5]: F?r das Ziel ?all? ist nichts zu tun.
make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt'
make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
make[5]: F?r das Ziel ?all-am? ist nichts zu tun.
make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
Making all in osmocore
make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
Making all in protocol
make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol'
make[5]: F?r das Ziel ?all? ist nichts zu tun.
make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol'
make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
make[5]: F?r das Ziel ?all-am? ist nichts zu tun.
make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include'
make[4]: F?r das Ziel ?all-am? ist nichts zu tun.
make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include'
make[3]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include'
Making all in src
make[3]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/src'
Making all in .
make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/src'
  CC     rate_ctr.lo
../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory
make[4]: *** [rate_ctr.lo] Fehler 1
make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/src'
make[3]: *** [all-recursive] Fehler 1
make[3]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/src'
make[2]: *** [all-recursive] Fehler 1
make[2]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target'
make[1]: *** [all] Fehler 2
make[1]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target'
make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] Fehler 2
root at r00t-laptop:~/install/osmocom-bb/src# 

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110105/d8094f38/attachment.htm>

From shadown at gmail.com  Wed Jan  5 17:01:55 2011
From: shadown at gmail.com (Sergio 'shadown' Alvarez)
Date: Wed, 5 Jan 2011 18:01:55 +0100
Subject: Compile Errors
In-Reply-To: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
References: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
Message-ID: <F3D24601-ED93-497A-B5AF-7A9D55C3F042@gmail.com>

> ../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory

Just comment the line that includes the inttypes.h, and you are good  
to go.

Cheers,
    sergio


On Jan 5, 2011, at 5:19 PM, Sebastian --- wrote:

> Hi,
>
> I use Ubuntu 9.10, when i try to Compile Osmocom, i get this:
>
> root at r00t-laptop:~# cd /home/r00t/install/osmocom-bb/src
> root at r00t-laptop:~/install/osmocom-bb/src# make
> cd shared/libosmocore/build-target && ../configure \
>             --host=arm-elf-linux --disable-vty --enable-panic- 
> infloop \
>             --disable-shared --disable-talloc --disable-tests \
>         CC="/home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc"  
> CFLAGS="-Os -ffunction-sections -I/home/r00t/install/osmocom-bb/src/ 
> target/firmware/include"
> configure: WARNING: If you wanted to set the --build type, don't use  
> --host.
>     If a cross compiler is detected then cross compile mode will be  
> used.
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for arm-elf-linux-strip... no
> checking for strip... strip
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make sets $(MAKE)... (cached) yes
> checking for arm-elf-linux-gcc... /home/r00t/install/gnuarm-3.4.3/ 
> bin/arm-elf-gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... yes
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc  
> accepts -g... yes
> checking for /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc option  
> to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of /home/r00t/install/gnuarm-3.4.3/bin/arm- 
> elf-gcc... gcc3
> checking build system type... i686-pc-linux-gnulibc1
> checking host system type... arm-elf-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by /home/r00t/install/gnuarm-3.4.3/bin/arm-elf- 
> gcc... /home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld
> checking if the linker (/home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ 
> ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... no
> checking for arm-elf-linux-dumpbin... no
> checking for arm-elf-linux-link... no
> checking for dumpbin... no
> checking for link... link -dump -symbols
> configure: WARNING: using cross tools not prefixed with host triplet
> checking the name lister (link -dump -symbols) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 805306365
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld option  
> to reload object files... -r
> checking for arm-elf-linux-objdump... no
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for arm-elf-linux-ar... no
> checking for ar... ar
> checking for arm-elf-linux-strip... strip
> checking for arm-elf-linux-ranlib... no
> checking for ranlib... ranlib
> checking command to parse link -dump -symbols output from /home/r00t/ 
> install/gnuarm-3.4.3/bin/arm-elf-gcc object... failed
> checking how to run the C preprocessor... /home/r00t/install/ 
> gnuarm-3.4.3/bin/arm-elf-gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... no
> checking for inttypes.h... no
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... no
> checking for objdir... .libs
> checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports  
> -fno-rtti -fno-exceptions... no
> checking for /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc option  
> to produce PIC... -fPIC -DPIC
> checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc PIC flag  
> -fPIC -DPIC works... yes
> checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc static  
> flag -static works... yes
> checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports  
> -c -o file.o... yes
> checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports  
> -c -o file.o... (cached) yes
> checking whether the /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc  
> linker (/home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld) supports  
> shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... no
> checking whether to build static libraries... yes
> checking for ANSI C header files... (cached) yes
> checking execinfo.h usability... no
> checking execinfo.h presence... no
> checking for execinfo.h... no
> checking sys/select.h usability... no
> checking sys/select.h presence... no
> checking for sys/select.h... no
> checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports  
> -fvisibility=hidden... no
> configure: creating ./config.status
> config.status: creating libosmocore.pc
> config.status: creating libosmocodec.pc
> config.status: creating libosmovty.pc
> config.status: creating include/osmocom/Makefile
> config.status: creating include/osmocom/vty/Makefile
> config.status: creating include/osmocom/codec/Makefile
> config.status: creating include/osmocom/crypt/Makefile
> config.status: creating include/osmocore/Makefile
> config.status: creating include/osmocore/protocol/Makefile
> config.status: creating include/Makefile
> config.status: creating src/Makefile
> config.status: creating src/vty/Makefile
> config.status: creating src/codec/Makefile
> config.status: creating tests/Makefile
> config.status: creating tests/timer/Makefile
> config.status: creating tests/sms/Makefile
> config.status: creating tests/msgfile/Makefile
> config.status: creating tests/ussd/Makefile
> config.status: creating Makefile
> config.status: creating config.h
> config.status: config.h is unchanged
> config.status: executing depfiles commands
> config.status: executing libtool commands
> cd shared/libosmocore/build-target && make
> make[1]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target'
> make  all-recursive
> make[2]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target'
> Making all in include
> make[3]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include'
> Making all in osmocom
> make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocom'
> Making all in codec
> make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocom/codec'
> make[5]: F?r das Ziel ?all? ist nichts zu tun.
> make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocom/codec'
> Making all in crypt
> make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocom/crypt'
> make[5]: F?r das Ziel ?all? ist nichts zu tun.
> make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocom/crypt'
> make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocom'
> make[5]: F?r das Ziel ?all-am? ist nichts zu tun.
> make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocom'
> make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocom'
> Making all in osmocore
> make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocore'
> Making all in protocol
> make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocore/protocol'
> make[5]: F?r das Ziel ?all? ist nichts zu tun.
> make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocore/protocol'
> make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocore'
> make[5]: F?r das Ziel ?all-am? ist nichts zu tun.
> make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocore'
> make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include/osmocore'
> make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include'
> make[4]: F?r das Ziel ?all-am? ist nichts zu tun.
> make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include'
> make[3]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/include'
> Making all in src
> make[3]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/src'
> Making all in .
> make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/src'
>   CC     rate_ctr.lo
> ../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory
> make[4]: *** [rate_ctr.lo] Fehler 1
> make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/src'
> make[3]: *** [all-recursive] Fehler 1
> make[3]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target/src'
> make[2]: *** [all-recursive] Fehler 1
> make[2]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target'
> make[1]: *** [all] Fehler 2
> make[1]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/ 
> shared/libosmocore/build-target'
> make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a]  
> Fehler 2
> root at r00t-laptop:~/install/osmocom-bb/src#
>




From hessel at schut.be  Wed Jan  5 17:04:40 2011
From: hessel at schut.be (Hessel Schut)
Date: Wed, 5 Jan 2011 19:04:40 +0200
Subject: Compile Errors
In-Reply-To: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
References: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
Message-ID: <AANLkTik5HTaHKOerkb=3rEVs-_x9ZvKie6MwX4DGpRxA@mail.gmail.com>

Hi Sebastian,

On Wed, Jan 5, 2011 at 18:19, Sebastian --- <seppel18 at hotmail.com> wrote:

>  Hi,
>
> I use Ubuntu 9.10, when i try to Compile Osmocom, i get this:
>

>snip<


> ../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory
>
>
What works for me, is to comment out the include of inttypes.h
from src/shared/libosmocore/src/rate_ctr.c
and the include_next of stdint.h in src/target/firmware/include/stdint.h.

Regards,

Hessel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110105/ee6772b4/attachment.htm>

From paul at kristianpaul.org  Wed Jan  5 17:05:18 2011
From: paul at kristianpaul.org (Cristian Paul =?iso-8859-1?Q?Pe=F1aranda?= Rojas)
Date: Wed, 5 Jan 2011 12:05:18 -0500
Subject: Compile Errors
In-Reply-To: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
References: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
Message-ID: <20110105170518.GP2283@micro.kristianpaul.local>

> ../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory

Just comment/delete that include as is already fixed on upstream
libosmocom

http://ur1.ca/2r4l9

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110105/1cce1623/attachment.bin>

From peter at stuge.se  Wed Jan  5 17:15:09 2011
From: peter at stuge.se (Peter Stuge)
Date: Wed, 5 Jan 2011 18:15:09 +0100
Subject: Compile Errors
In-Reply-To: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
References: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
Message-ID: <20110105171509.23559.qmail@stuge.se>

Sebastian --- wrote:
> I use Ubuntu 9.10, when i try to Compile Osmocom, i get this:
> 
> root at r00t-laptop:~# cd /home/r00t/install/osmocom-bb/src
> root at r00t-laptop:~/install/osmocom-bb/src# make
> cd shared/libosmocore/build-target && ../configure \
>             --host=arm-elf-linux --disable-vty --enable-panic-infloop \
>             --disable-shared --disable-talloc --disable-tests \
>         CC="/home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc" CFLAGS="-Os -ffunction-sections -I/home/r00t/install/osmocom-bb/src/target/firmware/include"

Please don't do this. First, work as a regular user. You could use
r00t. Then, your --host is wrong. Also, please just set your path to
include /home/r00t/install/gnuarm-3.4.3/bin in the path. And I'm not
sure that you need the target/firmware/include, I'd expect that to be
added where needed automatically.

./configure --host=arm-elf --disable-vty --enable-panic-infloop \
--disable-shared --disable-talloc --disable-tests

should be enough. Run as r00t, not root, with PATH set correctly.
Look for cross-compile tutorials for microcontroller projects on the
interwebs to learn more about how to work with projects like these.


//Peter



From wolfram at the-dreams.de  Wed Jan  5 19:07:41 2011
From: wolfram at the-dreams.de (Wolfram Sang)
Date: Wed, 05 Jan 2011 20:07:41 +0100
Subject: Compile Errors
In-Reply-To: <20110105171509.23559.qmail@stuge.se>
References: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
	<20110105171509.23559.qmail@stuge.se>
Message-ID: <4D24C17D.4080205@the-dreams.de>

Peter,

On 05/01/11 18:15, Peter Stuge wrote:
> Sebastian --- wrote:
>> I use Ubuntu 9.10, when i try to Compile Osmocom, i get this:
>>
>> root at r00t-laptop:~# cd /home/r00t/install/osmocom-bb/src
>> root at r00t-laptop:~/install/osmocom-bb/src# make
>> cd shared/libosmocore/build-target && ../configure \
>>             --host=arm-elf-linux --disable-vty --enable-panic-infloop \
>>             --disable-shared --disable-talloc --disable-tests \
>>         CC="/home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc" CFLAGS="-Os -ffunction-sections -I/home/r00t/install/osmocom-bb/src/target/firmware/include"
> 
> Please don't do this. First, work as a regular user. You could use
> r00t. Then, your --host is wrong. Also, please just set your path to
> include /home/r00t/install/gnuarm-3.4.3/bin in the path. And I'm not
> sure that you need the target/firmware/include, I'd expect that to be
> added where needed automatically.

That configure-line is already make-output ;)

The other points are very valid, of course.

All the best,

   Wolfram



From wolfram at the-dreams.de  Wed Jan  5 17:15:52 2011
From: wolfram at the-dreams.de (Wolfram Sang)
Date: Wed, 05 Jan 2011 18:15:52 +0100
Subject: Compile Errors
In-Reply-To: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
References: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
Message-ID: <4D24A748.40301@the-dreams.de>

> ../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory

See my mail from three days ago.

@maintainers: who can do the sync of libosmocore?

Regards,

   Wolfram



From steve at steve-m.de  Wed Jan  5 23:08:11 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Thu, 06 Jan 2011 00:08:11 +0100
Subject: Compile Errors
In-Reply-To: <4D24A748.40301@the-dreams.de>
References: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
	<4D24A748.40301@the-dreams.de>
Message-ID: <4D24F9DB.6020308@steve-m.de>

Hi,

On 05.01.2011 18:15, Wolfram Sang wrote:
>> ../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory
>
> See my mail from three days ago.
>
> @maintainers: who can do the sync of libosmocore?

To prevent that another 20 people will run into this problem, I've taken 
the liberty to test osmocom-bb with the latest version of libosmocore, 
and merged it into master.

Regards,
Steve



From laforge at gnumonks.org  Thu Jan  6 06:21:22 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 6 Jan 2011 07:21:22 +0100
Subject: Compile Errors
In-Reply-To: <4D24F9DB.6020308@steve-m.de>
References: <SNT129-W455F04612E8314E3B70741D9090@phx.gbl>
	<4D24A748.40301@the-dreams.de> <4D24F9DB.6020308@steve-m.de>
Message-ID: <20110106062122.GC30052@prithivi.gnumonks.org>

Hi Steve,

On Thu, Jan 06, 2011 at 12:08:11AM +0100, Steve Markgraf wrote:
>
> >@maintainers: who can do the sync of libosmocore?
> 
> To prevent that another 20 people will run into this problem, I've
> taken the liberty to test osmocom-bb with the latest version of
> libosmocore, and merged it into master.

thanks a lot.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From seppel18 at hotmail.com  Wed Jan  5 20:57:11 2011
From: seppel18 at hotmail.com (Sebastian ---)
Date: Wed, 5 Jan 2011 21:57:11 +0100
Subject: administratively down?
Message-ID: <SNT129-W5D3A4AFBAA9F81EF703FDD9090@phx.gbl>


Next Problem:

./mobile says "MS '1' is administratively down".

I tried everything..put osmocom.cfg in /etc/osmocom ....

How can I bring it "UP"? (Like in Cisco world :)
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110105/82eaab41/attachment.htm>

From Andreas.Eversberg at versatel.de  Thu Jan  6 10:36:03 2011
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Thu, 6 Jan 2011 11:36:03 +0100
Subject: AW: administratively down?
Message-ID: <B16317F2B1592B4492FC414114171CE604C736FA@FLBVEXCH01.versatel.local>

hi sebastian,
 
there are three ways to bing it down:
 
- "enable" -> "conf t" -> "ms 1" -> "shutdown"
- the layer2 socket does not exist on startup (osmocon loader not
started)
- the shutdown state is stored in the config (doing "write" when it is
down)
 
just bring it up after starting osmocon:
 
- "enable" -> "conf t" -> "ms 1" -> "no shutdown"
and don't forget "write" the config, so it must not be done on every
startup.
 
andreas
 

________________________________

Von: baseband-devel-bounces at lists.osmocom.org
[mailto:baseband-devel-bounces at lists.osmocom.org] Im Auftrag von
Sebastian ---
Gesendet: Mittwoch, 5. Januar 2011 21:57
An: baseband-devel at lists.osmocom.org
Betreff: administratively down?


Next Problem:

./mobile says "MS '1' is administratively down".

I tried everything..put osmocom.cfg in /etc/osmocom ....

How can I bring it "UP"? (Like in Cisco world :)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110106/ae752fbc/attachment.htm>

From rakeshnitc at gmail.com  Thu Jan  6 05:29:50 2011
From: rakeshnitc at gmail.com (rakesh mukundan)
Date: Thu, 6 Jan 2011 10:59:50 +0530
Subject: OsmocomBB support in Motorola C168
Message-ID: <AANLkTikgGxCaicvceTQCvw8ocfcHWpU=XQEN8Lo=6gNs@mail.gmail.com>

Hi All.

I am a newbie to OssmocomBB, though I have been reading the mails, never
actually got a chance to start working.
But after watching the 27C3 video, now I am totally inspired :) The problem
I am facing the unavailability of the hardware, the only phone available to
me as of now is Motorola C168, Can anyone tell me if it will be compact able
with OsmocomBB? I have searched in the mailing list archives but could find
an answer :(

Thanks in Advance

Regards

-----
Rakesh Mukundan
http://simplified-security.blogspot.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110106/1b24106b/attachment.htm>

From sweisman at pobox.com  Thu Jan  6 06:11:32 2011
From: sweisman at pobox.com (Scott Weisman)
Date: Thu, 6 Jan 2011 08:11:32 +0200
Subject: OsmocomBB support in Motorola C168
In-Reply-To: <AANLkTikgGxCaicvceTQCvw8ocfcHWpU=XQEN8Lo=6gNs@mail.gmail.com>
References: <AANLkTikgGxCaicvceTQCvw8ocfcHWpU=XQEN8Lo=6gNs@mail.gmail.com>
Message-ID: <AANLkTik5jE0eTYyQgBXK-0gj28QQZtwScLnic93VvDST@mail.gmail.com>

eBay usually has OsmocomBB-compatible phones available as auctions or
Buy-It-Now.

Do a search for "motorola (c115,c117,c123,c121,c118,c140,c139,c155,v171)".

Eg:

http://cell-phones.shop.ebay.com/Cell-Phones-Smartphones-/3312/i.html?LH_BIN=1&_nkw=motorola%20(c115,c117,c123,c121,c118,c140,c139,c155,v171)&_catref=1&_dmpt=Cell_Phones&_fcid=100&_ipg=200&_jgr=1&_localstpos=&_sc=1&_sop=15&_stpos=&gbr=1

Remove any phones from the list above that you're not interested in
(eg GSM850/1900 phones if you're not in North America).

Scott

On Thu, Jan 6, 2011 at 7:29 AM, rakesh mukundan <rakeshnitc at gmail.com> wrote:
>
> Hi All.
>
> I am a newbie to OssmocomBB, though I have been reading the mails, never actually got a chance to start working.
> But after watching the 27C3 video, now I am totally inspired :) The problem I am facing the unavailability of the hardware, the only phone available to me as of now is Motorola C168, Can anyone tell me if it will be compact able with OsmocomBB? I have searched in the mailing list archives but could find an answer :(
>
> Thanks in Advance
>
> Regards
>
> -----
> Rakesh Mukundan
> http://simplified-security.blogspot.com/



From thatsit at gmx.ch  Thu Jan  6 20:31:49 2011
From: thatsit at gmx.ch (Thatsit)
Date: Thu, 6 Jan 2011 21:31:49 +0100
Subject: OsmocomBB support in Motorola C168
In-Reply-To: <AANLkTik5jE0eTYyQgBXK-0gj28QQZtwScLnic93VvDST@mail.gmail.com>
References: <AANLkTikgGxCaicvceTQCvw8ocfcHWpU=XQEN8Lo=6gNs@mail.gmail.com>
	<AANLkTik5jE0eTYyQgBXK-0gj28QQZtwScLnic93VvDST@mail.gmail.com>
Message-ID: <DA57DF72-9A1A-470B-9C79-5F0B1F0A2FDA@gmx.ch>

This raises for me a question regarding the frequency bands the phones can operate in:

The same model e.g. C115 operates in europe in the 900/1800 bands and in america in the 850/1900 bands. That means we can not select on the model. Are these the same phones (hardware) and simply the firmware is a little different or are there differences in hardware? If yes, is difference only the input filters which for the sniffing application have/can be removed anyway?

The goal of my question is obviously to know if we can buy phones from america and use with osmocomBB in the europe bands?

Thanks
Matthias

Am 06.01.2011 um 07:11 schrieb Scott Weisman:

> eBay usually has OsmocomBB-compatible phones available as auctions or
> Buy-It-Now.
> 
> Do a search for "motorola (c115,c117,c123,c121,c118,c140,c139,c155,v171)".
> 
> Eg:
> 
> http://cell-phones.shop.ebay.com/Cell-Phones-Smartphones-/3312/i.html?LH_BIN=1&_nkw=motorola%20(c115,c117,c123,c121,c118,c140,c139,c155,v171)&_catref=1&_dmpt=Cell_Phones&_fcid=100&_ipg=200&_jgr=1&_localstpos=&_sc=1&_sop=15&_stpos=&gbr=1
> 
> Remove any phones from the list above that you're not interested in
> (eg GSM850/1900 phones if you're not in North America).
> 
> Scott
> 
> On Thu, Jan 6, 2011 at 7:29 AM, rakesh mukundan <rakeshnitc at gmail.com> wrote:
>> 
>> Hi All.
>> 
>> I am a newbie to OssmocomBB, though I have been reading the mails, never actually got a chance to start working.
>> But after watching the 27C3 video, now I am totally inspired :) The problem I am facing the unavailability of the hardware, the only phone available to me as of now is Motorola C168, Can anyone tell me if it will be compact able with OsmocomBB? I have searched in the mailing list archives but could find an answer :(
>> 
>> Thanks in Advance
>> 
>> Regards
>> 
>> -----
>> Rakesh Mukundan
>> http://simplified-security.blogspot.com/
> 




From holger at freyther.de  Thu Jan  6 12:41:42 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 06 Jan 2011 13:41:42 +0100
Subject: Dropping the layer23 application?
Message-ID: <4D25B886.10908@freyther.de>

Hi all,

I think the layer23 app was great when Dieter and others worked on the TX part
of Osmocom but right now it has the potential of disturbing a real network.

So it could be changed in a way that it checks if the firmware has TX disabled
(maybe even make TX disabling a runtime setting), and then still follow the
first assignment, never transmit anything and on a CIPHER MODE COMMAND switch
back to the BCCH (or when no enc is used at the release message).

comments?

holger



From 246tnt at gmail.com  Thu Jan  6 12:55:09 2011
From: 246tnt at gmail.com (246tnt at gmail.com)
Date: Thu, 06 Jan 2011 12:55:09 +0000
Subject: Dropping the layer23 application?
In-Reply-To: <4D25B886.10908@freyther.de>
Message-ID: <90e6ba61508000017d04992d03a8@google.com>

> I think the layer23 app was great when Dieter and others worked on the TX  
> part
> of Osmocom but right now it has the potential of disturbing a real  
> network.

Well, you're not supposed to use it with TX enabled :)

I think we should just strip the code that makes a RACH and the code that  
follow assignements.
Just put them in #if 0 as "examples" but make sure that by default it just  
sits on the BCCH, changes the CCCH mode when it knows it and that's it ...

This way, it makes a simple app that dumps SI and paging / immediate  
assignement on a specific ARFCN. And if you want to dig deeper, the example  
on how to do more are still in the code.


We should also group it in a single file like the other example app since  
it doesn't make sense to have so much files for so little function.


Cheers,

Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110106/7d9d72f6/attachment.htm>

From f.koliqi at gmail.com  Thu Jan  6 18:26:33 2011
From: f.koliqi at gmail.com (Fadil Berisha)
Date: Thu, 6 Jan 2011 13:26:33 -0500
Subject: MT612X RF Transceiver Data Sheet
Message-ID: <AANLkTi=bAr0P-4AhP+8NEfytpCpjz0h2LbzqvQ7cPkZx@mail.gmail.com>

I need programming Data Sheet for MT612X RF Transceiver, especially data for
programming serial interface, internal registers, vco etc. Does somebody
know link to get data?

 I did some google search and come to this link:

http://code.google.com/p/ptmtk/source/checkout

There, under directory mtk_datasheet found MT612X IC data with electrical
data, pin description etc. There is also, reference phone design and
detailed programming data sheet for Baseband processors MT6217, MT6219 and
MT6253. Knowing that is under developing osmocomBB driver for MT, I thought
this might interest you!

koliqi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110106/0a734a0d/attachment.htm>

From Andreas.Eversberg at versatel.de  Fri Jan  7 08:43:32 2011
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Fri, 7 Jan 2011 09:43:32 +0100
Subject: AW: Osmocom-BB
Message-ID: <B16317F2B1592B4492FC414114171CE604C73A28@FLBVEXCH01.versatel.local>

hi,
 
can you try the following steps:
 
1. start osmocon
2. start mobile (be sure it is not shutdown)
3. press the power button on the phone to start the loading process
 
after loading the binary into the phone, the phone should indicate power
on to the mobile process. 
 
andreas
 

________________________________

Von: Sebastian --- [mailto:seppel18 at hotmail.com] 
Gesendet: Freitag, 7. Januar 2011 01:37
An: Andreas.Eversberg
Betreff: Osmocom-BB


Hi

Thanks for your Help.

Now it says ms 1 is still down "radio not started". Osmocon is running
(with ramloader) and layer2 socket is available.





hi sebastian,
 
there are three ways to bing it down:
 
- "enable" -> "conf t" -> "ms 1" -> "shutdown"
- the layer2 socket does not exist on startup (osmocon loader not
started)
- the shutdown state is stored in the config (doing "write" when it is
down)
 
just bring it up after starting osmocon:
 
- "enable" -> "conf t" -> "ms 1" -> "no shutdown"
and don't forget "write" the config, so it must not be done on every
startup.
 
andreas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110107/a56ccd5d/attachment.htm>

From b.alecu at yahoo.com  Fri Jan  7 13:56:32 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Fri, 7 Jan 2011 05:56:32 -0800 (PST)
Subject: Osmocon not loading
Message-ID: <475544.25236.qm@web46206.mail.sp1.yahoo.com>

Hello,
I have managed to compile everything, I connected my phone 
trough USB but when I try to run ./osmocon -p /dev/ttyUSB0 -m c123xor 
../../target/firmware/board/compal_e88/loader.compalram.bin I do not get
 the "
Received PROMPT1 from phone, responding with CMD" message

All I get is this:
root at ubuntu:/home/trepx/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin
got 2 bytes from modem, data looks like: f1 06  ..
got 5 bytes from modem, data looks like: 72 82 bf 7d fd  r..}.
got 1 bytes from modem, data looks like: 7f  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: a6  .
got 1 bytes from modem, data looks like: 0a  .
got 1 bytes from modem,
 data looks like: 3a  :
got 1 bytes from modem, data looks like: 02  .
got 1 bytes from modem, data looks like: 4d  M
got 1 bytes from modem, data looks like: da  .


root at ubuntu:/home/trepx/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin
got 2 bytes from modem, data looks like: f1 06  ..
got 4 bytes from modem, data looks like: a6 51 d2 51  .Q.Q
got 1 bytes from modem, data looks like: 4d  M
got 1 bytes from modem, data looks like: a3  .
got 1 bytes from modem, data looks like: a3  .
got 1 bytes from modem, data looks like: 00  .

I have waited for 10 minutes and still nothing. Any idea how to make it work?

Regards,
Bogdan


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110107/24499630/attachment.htm>

From holger at freyther.de  Fri Jan  7 13:58:57 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Fri, 07 Jan 2011 14:58:57 +0100
Subject: Osmocon not loading
In-Reply-To: <475544.25236.qm@web46206.mail.sp1.yahoo.com>
References: <475544.25236.qm@web46206.mail.sp1.yahoo.com>
Message-ID: <4D271C21.4010301@freyther.de>

On 01/07/2011 02:56 PM, Bogdan Alecu wrote:
> Hello,
> I have managed to compile everything, I connected my phone trough USB but when
> I try to run ./osmocon -p /dev/ttyUSB0 -m c123xor
> ../../target/firmware/board/compal_e88/loader.compalram.bin I do not get the "

Did you try without xor? Which toolchain did you use?



From b.alecu at yahoo.com  Fri Jan  7 15:34:12 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Fri, 7 Jan 2011 07:34:12 -0800 (PST)
Subject: Osmocon not loading
Message-ID: <400269.63861.qm@web46211.mail.sp1.yahoo.com>

I used the steps from here http://bb.osmocom.org/trac/wiki/GnuArmToolchain to build the toolchain. I also tried with and without xor, no results.




      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110107/62edbfa7/attachment.htm>

From 246tnt at gmail.com  Fri Jan  7 16:21:26 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Fri, 7 Jan 2011 17:21:26 +0100
Subject: Osmocon not loading
In-Reply-To: <400269.63861.qm@web46211.mail.sp1.yahoo.com>
References: <400269.63861.qm@web46211.mail.sp1.yahoo.com>
Message-ID: <AANLkTimZ7ZE=8tC3ygcxY-T6pFto2yA6EvFHq4kqD=ps@mail.gmail.com>

On Fri, Jan 7, 2011 at 4:34 PM, Bogdan Alecu <b.alecu at yahoo.com> wrote:
>
> I used the steps from here http://bb.osmocom.org/trac/wiki/GnuArmToolchain to build the toolchain. I also tried with and without xor, no results.

Your cable is bad, don't look further ... if the loader doesn't see
the PROMPT1, nothing will ever happen and only a bad cable/connection
to the phone will do that. (or the phone serial port is damaged ...)

   Sylvain



From b.alecu at yahoo.com  Fri Jan  7 18:29:40 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Fri, 7 Jan 2011 10:29:40 -0800 (PST)
Subject: Osmocon not loading
In-Reply-To: <AANLkTimZ7ZE=8tC3ygcxY-T6pFto2yA6EvFHq4kqD=ps@mail.gmail.com>
Message-ID: <285932.27140.qm@web46201.mail.sp1.yahoo.com>

Thank you Sylvain. After some talking on the IRC channel it seems that the phone is not sending the correct strings in HyperTerminal on Windows. I'll try with another cable and phone. It's really hard to find an already made USB cable.

--- On Fri, 1/7/11, Sylvain Munaut <246tnt at gmail.com> wrote:

From: Sylvain Munaut <246tnt at gmail.com>
Subject: Re: Osmocon not loading
To: "Bogdan Alecu" <b.alecu at yahoo.com>
Cc: baseband-devel at lists.osmocom.org
Date: Friday, January 7, 2011, 4:21 PM

On Fri, Jan 7, 2011 at 4:34 PM, Bogdan Alecu <b.alecu at yahoo.com> wrote:
>
> I used the steps from here http://bb.osmocom.org/trac/wiki/GnuArmToolchain to build the toolchain. I also tried with and without xor, no results.

Your cable is bad, don't look further ... if the loader doesn't see
the PROMPT1, nothing will ever happen and only a bad cable/connection
to the phone will do that. (or the phone serial port is damaged ...)

???Sylvain



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110107/352af234/attachment.htm>

From thatsit at gmx.ch  Fri Jan  7 16:30:00 2011
From: thatsit at gmx.ch (Thatsit)
Date: Fri, 7 Jan 2011 17:30:00 +0100
Subject: Osmocon not loading
In-Reply-To: <400269.63861.qm@web46211.mail.sp1.yahoo.com>
References: <400269.63861.qm@web46211.mail.sp1.yahoo.com>
Message-ID: <6B4DE0E2-1883-4010-9D5B-E275335067E2@gmx.ch>

By the way.. If I use a tool chain built according to the mentioned wiki page, the resulting firmware does not work! It is impossible to initialize the flash.. 
Some weeks ago, I started debugging this. I found out that, as much I can remember, the CFI layer gives a bad protocol id (or version). I expected that it could be related to some padding or alignment differences...

If I use binutils-2.17, gcc-4.1.1-c-c++, newlib-1.14.0, everything works fine

Matthias

Am 07.01.2011 um 16:34 schrieb Bogdan Alecu:

> I used the steps from here http://bb.osmocom.org/trac/wiki/GnuArmToolchain to build the toolchain. I also tried with and without xor, no results.
> 
> 




From steve at steve-m.de  Fri Jan  7 16:52:14 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Fri, 07 Jan 2011 17:52:14 +0100
Subject: Osmocon not loading
In-Reply-To: <6B4DE0E2-1883-4010-9D5B-E275335067E2@gmx.ch>
References: <400269.63861.qm@web46211.mail.sp1.yahoo.com>
	<6B4DE0E2-1883-4010-9D5B-E275335067E2@gmx.ch>
Message-ID: <4D2744BE.8060503@steve-m.de>

Hi,

On 07.01.2011 17:30, Thatsit wrote:
> By the way.. If I use a tool chain built according to the mentioned
> wiki page, the resulting firmware does not work! It is impossible
> to initialize the flash..

Well, it might be that the flash support is broken with that toolchain. 
But why would you need flash anyway, we completely run from SRAM at the 
moment, just load layer1.compalram.bin

Feel free to commit a fix for that though ;)

Regards,
Steve



From thatsit at gmx.ch  Fri Jan  7 17:01:09 2011
From: thatsit at gmx.ch (Thatsit)
Date: Fri, 7 Jan 2011 18:01:09 +0100
Subject: Osmocon not loading
In-Reply-To: <4D2744BE.8060503@steve-m.de>
References: <400269.63861.qm@web46211.mail.sp1.yahoo.com>
	<6B4DE0E2-1883-4010-9D5B-E275335067E2@gmx.ch>
	<4D2744BE.8060503@steve-m.de>
Message-ID: <42125341-11D7-4BDE-A2B0-AE95DF419A37@gmx.ch>

I didn't mean that I want to flash something. But any firmware simply does not initialize properly and stops working.
By the way its on Ubuntu-10.10.

Am 07.01.2011 um 17:52 schrieb Steve Markgraf:

> Hi,
> 
> On 07.01.2011 17:30, Thatsit wrote:
>> By the way.. If I use a tool chain built according to the mentioned
>> wiki page, the resulting firmware does not work! It is impossible
>> to initialize the flash..
> 
> Well, it might be that the flash support is broken with that toolchain. But why would you need flash anyway, we completely run from SRAM at the moment, just load layer1.compalram.bin
> 
> Feel free to commit a fix for that though ;)
> 
> Regards,
> Steve
> 




From steve at steve-m.de  Fri Jan  7 17:09:15 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Fri, 07 Jan 2011 18:09:15 +0100
Subject: Osmocon not loading
In-Reply-To: <42125341-11D7-4BDE-A2B0-AE95DF419A37@gmx.ch>
References: <400269.63861.qm@web46211.mail.sp1.yahoo.com>
	<6B4DE0E2-1883-4010-9D5B-E275335067E2@gmx.ch>
	<4D2744BE.8060503@steve-m.de>
	<42125341-11D7-4BDE-A2B0-AE95DF419A37@gmx.ch>
Message-ID: <4D2748BB.8000206@steve-m.de>

On 07.01.2011 18:01, Thatsit wrote:
> I didn't mean that I want to flash something. But any firmware simply does not initialize properly and stops working.
> By the way its on Ubuntu-10.10.

What do you define as 'does not initialize properly and stops working'? 
Can you provide the _full_ output of osmocon?

Regards,
Steve



From thatsit at gmx.ch  Fri Jan  7 17:15:26 2011
From: thatsit at gmx.ch (Thatsit)
Date: Fri, 7 Jan 2011 18:15:26 +0100
Subject: Osmocon not loading
In-Reply-To: <4D2748BB.8000206@steve-m.de>
References: <400269.63861.qm@web46211.mail.sp1.yahoo.com>
	<6B4DE0E2-1883-4010-9D5B-E275335067E2@gmx.ch>
	<4D2744BE.8060503@steve-m.de>
	<42125341-11D7-4BDE-A2B0-AE95DF419A37@gmx.ch>
	<4D2748BB.8000206@steve-m.de>
Message-ID: <C4E10646-AA19-4815-B826-4963A3608CEF@gmx.ch>

It means that the firmware initialization function tries to initialize the flash memory which fails. I put some printfs in every place where it can fail and found that, as much I can remember, the protocol id (or version) returned 0 instead of (probably) 3.. But I will reproduce it and send the output.. It was with a C123. 

Probably I try to find the problem behind it then, if nobody already knows what the root cause is..

Regards
Matthias

Am 07.01.2011 um 18:09 schrieb Steve Markgraf:

> On 07.01.2011 18:01, Thatsit wrote:
>> I didn't mean that I want to flash something. But any firmware simply does not initialize properly and stops working.
>> By the way its on Ubuntu-10.10.
> 
> What do you define as 'does not initialize properly and stops working'? Can you provide the _full_ output of osmocon?
> 
> Regards,
> Steve




From steve at steve-m.de  Fri Jan  7 23:12:15 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Sat, 08 Jan 2011 00:12:15 +0100
Subject: CFI flash init fails when using gcc-4.5.2 (was: Osmocon not loading)
In-Reply-To: <C4E10646-AA19-4815-B826-4963A3608CEF@gmx.ch>
References: <400269.63861.qm@web46211.mail.sp1.yahoo.com>
	<6B4DE0E2-1883-4010-9D5B-E275335067E2@gmx.ch>
	<4D2744BE.8060503@steve-m.de>
	<42125341-11D7-4BDE-A2B0-AE95DF419A37@gmx.ch>
	<4D2748BB.8000206@steve-m.de>
	<C4E10646-AA19-4815-B826-4963A3608CEF@gmx.ch>
Message-ID: <4D279DCF.4050509@steve-m.de>

Hi,

On 07.01.2011 18:15, Thatsit wrote:

> Probably I try to find the problem behind it then, if nobody already knows what the root cause is..

Andreas Oberritter submitted a patch that fixes this issue, I just 
committed it to master.

See:

http://cgit.osmocom.org/cgit/osmocom-bb/commit/?id=0e130bf467923ddaff6000aa43747e88a6d3e00f

Regards,
Steve



From thatsit at gmx.ch  Fri Jan  7 17:23:24 2011
From: thatsit at gmx.ch (Thatsit)
Date: Fri, 7 Jan 2011 18:23:24 +0100
Subject: Osmocon not loading
In-Reply-To: <4D2748BB.8000206@steve-m.de>
References: <400269.63861.qm@web46211.mail.sp1.yahoo.com>
	<6B4DE0E2-1883-4010-9D5B-E275335067E2@gmx.ch>
	<4D2744BE.8060503@steve-m.de>
	<42125341-11D7-4BDE-A2B0-AE95DF419A37@gmx.ch>
	<4D2748BB.8000206@steve-m.de>
Message-ID: <5AD508A0-E828-4179-A947-B71E4E3CB796@gmx.ch>

To be more precise, it was the loader firmware.  which didn't initialize properly.


Am 07.01.2011 um 18:09 schrieb Steve Markgraf:

> On 07.01.2011 18:01, Thatsit wrote:
>> I didn't mean that I want to flash something. But any firmware simply does not initialize properly and stops working.
>> By the way its on Ubuntu-10.10.
> 
> What do you define as 'does not initialize properly and stops working'? Can you provide the _full_ output of osmocon?
> 
> Regards,
> Steve
> 




From thatsit at gmx.ch  Fri Jan  7 16:24:51 2011
From: thatsit at gmx.ch (Thatsit)
Date: Fri, 7 Jan 2011 17:24:51 +0100
Subject: Osmocon not loading
In-Reply-To: <475544.25236.qm@web46206.mail.sp1.yahoo.com>
References: <475544.25236.qm@web46206.mail.sp1.yahoo.com>
Message-ID: <8BD7F9DA-EC95-45A0-AC16-0F032EEF26A9@gmx.ch>

A this stage the firmware has not been involved in any way. It's only osmocon trying to understand what the phone sends. That means the tool chain doesn't matter.

I expect that you are using the wrong or broken cable. Possibly one for 5 V instead of 3.3 V.

Matthias

Am 07.01.2011 um 14:56 schrieb Bogdan Alecu:

> Hello,
> I have managed to compile everything, I connected my phone trough USB but when I try to run ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin I do not get the "
> Received PROMPT1 from phone, responding with CMD" message
> 
> All I get is this:
> root at ubuntu:/home/trepx/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin
> got 2 bytes from modem, data looks like: f1 06  ..
> got 5 bytes from modem, data looks like: 72 82 bf 7d fd  r..}.
> got 1 bytes from modem, data looks like: 7f  .
> got 1 bytes from modem, data looks like: 00  .
> got 1 bytes from modem, data looks like: 00  .
> got 1 bytes from modem, data looks like: a6  .
> got 1 bytes from modem, data looks like: 0a  .
> got 1 bytes from modem,
>  data looks like: 3a  :
> got 1 bytes from modem, data looks like: 02  .
> got 1 bytes from modem, data looks like: 4d  M
> got 1 bytes from modem, data looks like: da  .
> 
> 
> root at ubuntu:/home/trepx/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c123xor
>  ../../target/firmware/board/compal_e88/loader.compalram.bin
> 
> got 2 bytes from modem, data looks like: f1 06  ..
> got 4 bytes from modem, data looks like: a6 51 d2 51  .Q.Q
> got 1 bytes from modem, data looks like: 4d  M
> got 1 bytes from modem, data looks like: a3  .
> got 1 bytes from modem, data looks like: a3  .
> got 1 bytes from modem, data looks like: 00  .
> 
> I have waited for 10 minutes and still nothing. Any idea how to make it work?
> 
> Regards,
> Bogdan
> 




From seppel18 at hotmail.com  Fri Jan  7 15:37:56 2011
From: seppel18 at hotmail.com (Sebastian ---)
Date: Fri, 7 Jan 2011 16:37:56 +0100
Subject: AW: AW: Osmocom-BB
In-Reply-To: <B16317F2B1592B4492FC414114171CE604C73D15@FLBVEXCH01.versatel.local>
References: <B16317F2B1592B4492FC414114171CE604C73D15@FLBVEXCH01.versatel.local>
Message-ID: <SNT129-W102677128C9D94811CB992D90B0@phx.gbl>


no,display shows nothing.

Osmocon shows:
r00t at r00t-laptop:~/install/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin
got 2 bytes from modem, data looks like: 2f 81  /.
got 1 bytes from modem, data looks like: 00  .
got 4 bytes from modem, data looks like: f6 02 00 41  ...A
got 1 bytes from modem, data looks like: 01  .
got 1 bytes from modem, data looks like: 40  @
got 1 bytes from modem, data looks like: 66  f
got 1 bytes from modem, data looks like: 74  t
got 1 bytes from modem, data looks like: 6d  m
got 1 bytes from modem, data looks like: 74  t
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 6c  l
Received FTMTOOL from phone, ramloader has aborted
got 1 bytes from modem, data looks like: 65  e
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: 2f  /
got 1 bytes from modem, data looks like: 81  .
got 1 bytes from modem, data looks like: 00  .
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: 41  A
got 1 bytes from modem, data looks like: 01  .
got 1 bytes from modem, data looks like: 40  @
got 1 bytes from modem, data looks like: 66  f
got 1 bytes from modem, data looks like: 74  t
got 1 bytes from modem, data looks like: 6d  m
got 1 bytes from modem, data looks like: 74  t
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 6c  l
Received FTMTOOL from phone, ramloader has aborted
got 1 bytes from modem, data looks like: 65  e
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: 2f  /
got 1 bytes from modem, data looks like: 81  .
got 1 bytes from modem, data looks like: 00  .
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: 41  A
got 1 bytes from modem, data looks like: 01  .
got 1 bytes from modem, data looks like: 40  @
got 1 bytes from modem, data looks like: 66  f
got 1 bytes from modem, data looks like: 74  t
got 1 bytes from modem, data looks like: 6d  m
got 1 bytes from modem, data looks like: 74  t
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 6c  l
Received FTMTOOL from phone, ramloader has aborted
got 1 bytes from modem, data looks like: 65  e
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: 2e  .
got 1 bytes from modem, data looks like: c8  .
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: 41  A
got 1 bytes from modem, data looks like: 01  .
got 1 bytes from modem, data looks like: 40  @
Received PROMPT1 from phone, responding with CMD
read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=21740, hdr_len=4, dnload_len=21747
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: 41  A
got 1 bytes from modem, data looks like: 02  .
got 1 bytes from modem, data looks like: 43  C
Received PROMPT2 from phone, starting download
handle_write(): 1023 bytes (1023/21747)
handle_write(): 768 bytes (1791/21747)
handle_write(): 768 bytes (2559/21747)
handle_write(): 768 bytes (3327/21747)
handle_write(): 768 bytes (4095/21747)
handle_write(): 768 bytes (4863/21747)
handle_write(): 768 bytes (5631/21747)
handle_write(): 768 bytes (6399/21747)
handle_write(): 768 bytes (7167/21747)
handle_write(): 768 bytes (7935/21747)
handle_write(): 768 bytes (8703/21747)
handle_write(): 768 bytes (9471/21747)
handle_write(): 768 bytes (10239/21747)
handle_write(): 768 bytes (11007/21747)
handle_write(): 768 bytes (11775/21747)
handle_write(): 768 bytes (12543/21747)
handle_write(): 768 bytes (13311/21747)
handle_write(): 768 bytes (14079/21747)
handle_write(): 768 bytes (14847/21747)
handle_write(): 768 bytes (15615/21747)
handle_write(): 768 bytes (16383/21747)
handle_write(): 768 bytes (17151/21747)
handle_write(): 768 bytes (17919/21747)
handle_write(): 768 bytes (18687/21747)
handle_write(): 768 bytes (19455/21747)
handle_write(): 768 bytes (20223/21747)
handle_write(): 768 bytes (20991/21747)
handle_write(): 756 bytes (21747/21747)
handle_write(): finished
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: 41  A
got 1 bytes from modem, data looks like: 03  .
got 1 bytes from modem, data looks like: 42  B
Received DOWNLOAD ACK from phone, your code is running now!
Received DOWNLOAD ACK from phone, your code is running now!


OSMOCOM Loader (revision osmocon_v0.0.0-740-g34bbb12-modified)
======================================================================
Running on compal_e88 in environment compalram
Found flash of 2097152 bytes at 0x0 with 2 regions

I have to press Power on few times before it loads.
Subject: AW: AW: Osmocom-BB
Date: Fri, 7 Jan 2011 15:59:21 +0100
From: Andreas.Eversberg at versatel.de
To: seppel18 at hotmail.com










does the mobile show "layer1.bin" on the display after startup? 
did the firmware actually load on the phone?
 
p.s. do you mind if we CC to the mailing list, so others can help 
or profit from the final solution?
 



Von: Sebastian --- [mailto:seppel18 at hotmail.com] 

Gesendet: Freitag, 7. Januar 2011 15:51
An: 
Andreas.Eversberg
Betreff: RE: AW: Osmocom-BB


still shows "MS '1' is down, radio is not started"




Subject: AW: Osmocom-BB
Date: Fri, 7 Jan 2011 09:43:32 +0100
From: 
Andreas.Eversberg at versatel.de
To: seppel18 at hotmail.com
CC: 
baseband-devel at lists.osmocom.org





hi,
 
can you try the following steps:
 
1. start osmocon
2. start mobile (be sure it is not 
shutdown)
3. press the power button on the phone to start the 
loading process
 
after loading the binary into the phone, the phone 
should indicate power on to the mobile process. 
 
andreas
 



Von: Sebastian --- [mailto:seppel18 at hotmail.com] 

Gesendet: Freitag, 7. Januar 2011 01:37
An: 
Andreas.Eversberg
Betreff: Osmocom-BB


Hi

Thanks for your Help.

Now it says ms 1 is still down "radio not started". Osmocon is running (with ramloader) and layer2 socket is available.





hi sebastian,
 
there are three ways to bing it down:
 
- "enable" -> "conf t" -> "ms 1" -> "shutdown"
- the layer2 socket does not exist on startup (osmocon loader not
started)
- the shutdown state is stored in the config (doing "write" when it is
down)
 
just bring it up after starting osmocon:
 
- "enable" -> "conf t" -> "ms 1" -> "no shutdown"
and don't forget "write" the config, so it must not be done on every
startup.
 
andreas
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110107/f5654bec/attachment.htm>

From steve at steve-m.de  Fri Jan  7 15:45:58 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Fri, 07 Jan 2011 16:45:58 +0100
Subject: Osmocom-BB
In-Reply-To: <SNT129-W102677128C9D94811CB992D90B0@phx.gbl>
References: <B16317F2B1592B4492FC414114171CE604C73D15@FLBVEXCH01.versatel.local>
	<SNT129-W102677128C9D94811CB992D90B0@phx.gbl>
Message-ID: <4D273536.6070507@steve-m.de>

Hi,

On 07.01.2011 16:37, Sebastian --- wrote:
> no,display shows nothing.
> ../../target/firmware/board/compal_e88/loader.compalram.bin

> OSMOCOM Loader (revision osmocon_v0.0.0-740-g34bbb12-modified)

Please, read the wiki first. loader doesn't use the display at all.
Load hello_world.compalram.bin or layer1.compalram.bin to see something 
on the display.
Regarding the failed tries: you might want to test "-m c123"

Regards,
Steve



From seppel18 at hotmail.com  Fri Jan  7 16:56:53 2011
From: seppel18 at hotmail.com (Sebastian ---)
Date: Fri, 7 Jan 2011 17:56:53 +0100
Subject: Osmocom-BB
In-Reply-To: <4D273536.6070507@steve-m.de>
References: <B16317F2B1592B4492FC414114171CE604C73D15@FLBVEXCH01.versatel.local>,
	<SNT129-W102677128C9D94811CB992D90B0@phx.gbl>,
	<4D273536.6070507@steve-m.de>
Message-ID: <SNT129-W613D9FD2F7FD9513A5DD7D90B0@phx.gbl>


Now we come closer :)

I loaded the wrong firmware, "layer1.compalram.bin" works together.

Sorry for my noobish questions, I will try to study the wiki even more.

> Date: Fri, 7 Jan 2011 16:45:58 +0100
> From: steve at steve-m.de
> To: seppel18 at hotmail.com
> Subject: Re: Osmocom-BB
> CC: baseband-devel at lists.osmocom.org; andreas.eversberg at versatel.de
> 
> Hi,
> 
> On 07.01.2011 16:37, Sebastian --- wrote:
> > no,display shows nothing.
> > ../../target/firmware/board/compal_e88/loader.compalram.bin
> 
> > OSMOCOM Loader (revision osmocon_v0.0.0-740-g34bbb12-modified)
> 
> Please, read the wiki first. loader doesn't use the display at all.
> Load hello_world.compalram.bin or layer1.compalram.bin to see something 
> on the display.
> Regarding the failed tries: you might want to test "-m c123"
> 
> Regards,
> Steve
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110107/f4148449/attachment.htm>

From mki at mki-consult.de  Fri Jan  7 17:13:59 2011
From: mki at mki-consult.de (mki)
Date: Fri, 7 Jan 2011 09:13:59 -0800 (PST)
Subject: connect to a specific network with the mobil app
Message-ID: <1294420439189-2213019.post@n3.nabble.com>


I hink my mobil is always connecting to the net with the most power.
is there a way to connect to a specific network?
Down her my config and tries to connect to t-mobile.

if i type in the vty:

local# network select 1 262 01
Network not in list!

local# network search 1 
local#

my config:
local# sh run

Current configuration:
!
service advanced-vty
!
line vty
 no login
!
gps device /dev/ttyACM0
gps baudrate default
no gps enable
!
ms 1
 layer2-socket /tmp/osmocom_l2
 sap-socket /tmp/osmocom_sap
 sim none
 network-selection-mode auto
 imei 000000000000000 0
 imei-fixed
 no emergency-imsi
 no call-waiting
 no auto-answer
 no clip
 no clir
 tx-power auto
 no simulated-delay
 no stick
 location-updating
 codec full-speed prefer
 codec half-speed
 no abbrev
 support
  sms
  a5/1
  a5/2
  p-gsm
  e-gsm
  r-gsm
  dcs
  class-900 4
  class-dcs 1
  channel-capability sdcch+tchf+tchh
  full-speech-v1
  full-speech-v2
  half-speech-v1
  min-rxlev -106
  dsc-max 90
 exit
 test-sim
  imsi 001010000000000
  ki xor 00 00 00 00 00 00 00 00 00 00 00 00 
  no barred-access
  no rplmn
  hplmn-search foreign-country
 exit
 no shutdown
exit
!
end


-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/connect-to-a-specific-network-with-the-mobil-app-tp2213019p2213019.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From mki at mki-consult.de  Fri Jan  7 17:50:12 2011
From: mki at mki-consult.de (mki)
Date: Fri, 7 Jan 2011 09:50:12 -0800 (PST)
Subject: connect to a specific network with the mobil app
In-Reply-To: <1294420439189-2213019.post@n3.nabble.com>
References: <1294420439189-2213019.post@n3.nabble.com>
Message-ID: <1294422612411-2213227.post@n3.nabble.com>


found a solution i think,
write a new config like this:

local# sh run

Current configuration:
!
service advanced-vty
!
line vty
 no login
!
gps device /dev/ttyACM0
gps baudrate default
no gps enable
!
ms 1
 layer2-socket /tmp/osmocom_l2
 sap-socket /tmp/osmocom_sap
 sim test
 network-selection-mode auto
 imei 000000000000000 0
 imei-fixed
 no emergency-imsi
 no call-waiting
 no auto-answer
 no clip
 no clir
 tx-power auto
 no simulated-delay
 no stick
 location-updating
 codec full-speed prefer
 codec half-speed
 no abbrev
 support
  sms
  a5/1
  a5/2
  p-gsm
  e-gsm
  r-gsm
  dcs
  class-900 4
  class-dcs 1
  channel-capability sdcch+tchf+tchh
  full-speech-v1
  full-speech-v2
  half-speech-v1
  min-rxlev -106
  dsc-max 90
 exit
 test-sim
  imsi 001010000000000
  ki xor 00 00 00 00 00 00 00 00 00 00 00 00 
  no barred-access
  rplmn 262 01
  hplmn-search foreign-country
 exit
 no shutdown
exit
!
end

an other question is if i let TX support disabled do the network see
anything from me? 
or is it a real rx only mode?
and is there any doc about the vty or the mobil app and if not where could i
write my solutions for beginners like me?



-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/connect-to-a-specific-network-with-the-mobil-app-tp2213019p2213227.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From ml at mail.tsaitgaist.info  Sat Jan  8 00:06:42 2011
From: ml at mail.tsaitgaist.info (ml at mail.tsaitgaist.info)
Date: Sat, 08 Jan 2011 01:06:42 +0100
Subject: sam7utils
Message-ID: <4D27AA92.4060009@mail.tsaitgaist.info>

Hi,

I'm trying to flash simtrace on an at91sam7s, using samba.
sam7utils compiles well under amd64, but does not work. It does not
output anything and quits.
the only indication on dmesg is :

usb 4-1: usbfs: interface 0 claimed by cdc_acm while 'sam7' sets config #1


Sam_I_Am works great on amd64, but the firmware format is not the same.
Does anyone knows how to convert main_simtrace.samba to a valid intel hex ?

Kevin



From vogelchr at vogel.cx  Sat Jan  8 12:26:23 2011
From: vogelchr at vogel.cx (Christian Vogel)
Date: Sat, 08 Jan 2011 13:26:23 +0100
Subject: sam7utils
In-Reply-To: <4D27AA92.4060009@mail.tsaitgaist.info>
References: <4D27AA92.4060009@mail.tsaitgaist.info>
Message-ID: <op.vozot817unbdei@distress.dillberg.com>

Hi Kevin,

> usb 4-1: usbfs: interface 0 claimed by cdc_acm while 'sam7' sets config  
> #1

sam7 can talk to the device either by using libusb, or by utilizing the  
emulated
serial port of the Linux kernel.

You have compiled sam7 to use usb directly, so you have to rmmod usbserial  
and/or cdc_acm,
because they will block your attempts to talk to the device via libusb.  
This
is the error message you've seen in your kernel log.

(check io_libusb.c (usb) and io_posix.c (emulated serial port) in the  
sam7utils source code,
  it unfortunately provides very little feedback if things don't work out  
well)

       Chris




From ml at mail.tsaitgaist.info  Sat Jan  8 15:02:11 2011
From: ml at mail.tsaitgaist.info (ml at mail.tsaitgaist.info)
Date: Sat, 08 Jan 2011 16:02:11 +0100
Subject: sam7utils
In-Reply-To: <op.vozot817unbdei@distress.dillberg.com>
References: <4D27AA92.4060009@mail.tsaitgaist.info>
	<op.vozot817unbdei@distress.dillberg.com>
Message-ID: <4D287C73.4070209@mail.tsaitgaist.info>

Hi,

Thanks. it works well.
on ubuntu 10.04, 03eb:6124 is mapped to ttyACMx using cdc_acm
I compiled it the same way on x86 and amd64 (./configure
--prefix=/usr/local; make)
on x86, sam7 uses posix (sam7 -l /dev/ttyACM0)
on amd64, sam7 works with libusb directly
while connected, you have to remove ttyACM0 (rmmod cdc_acm), then it's
possible to use
sudo ./sam7 --exec set_clock --exec unlock_regions --exec "flash
../openpcd/firmware/main_simtrace.samba"

once all set up, i'll write on the wiki.

thanks,
kevin

On 08.01.2011 13:26, Christian Vogel wrote:
> Hi Kevin,
>
> > usb 4-1: usbfs: interface 0 claimed by cdc_acm while 'sam7' sets
> > config #1
>
> sam7 can talk to the device either by using libusb, or by utilizing the
> emulated
> serial port of the Linux kernel.
>
> You have compiled sam7 to use usb directly, so you have to rmmod
> usbserial and/or cdc_acm,
> because they will block your attempts to talk to the device via libusb.
> This
> is the error message you've seen in your kernel log.
>
> (check io_libusb.c (usb) and io_posix.c (emulated serial port) in the
> sam7utils source code,
>  it unfortunately provides very little feedback if things don't work out
> well)
>
>       Chris
>
>



From dpavlin at rot13.org  Sat Jan  8 13:58:09 2011
From: dpavlin at rot13.org (Dobrica Pavlinusic)
Date: Sat, 8 Jan 2011 14:58:09 +0100
Subject: stuck in A1 Trying RPLMN while using testing branch? - change
	toolchain
Message-ID: <20110108135809.GA15475@rot13.org>

Yesterday I asked on #osmocom irc channel about my problems with using
provider card and testing branch of osmocom-bb to connect to network.

I was stuck in "A1 Trying RPLMN", and I didn't see any response received
with all debugging turned on.

Today, I decided to change my arm toolchain to gnu-arm recommended at

http://bb.osmocom.org/trac/wiki/GettingStarted

I recompiled, and it worked without problems.

I'm writing this e-mail as future reference since I saw few people
having problem with this on irc.

-- 
Dobrica Pavlinusic               2share!2flame            dpavlin at rot13.org
Unix addict. Internet consultant.             http://www.rot13.org/~dpavlin



From ml at mail.tsaitgaist.info  Sat Jan  8 16:07:17 2011
From: ml at mail.tsaitgaist.info (ml at mail.tsaitgaist.info)
Date: Sat, 08 Jan 2011 17:07:17 +0100
Subject: simtrace simtrace_usb.h
Message-ID: <4D288BB5.3070408@mail.tsaitgaist.info>

Hi

in simtrace/at91sam7/host, simtrace_usb.h is symbolically linked to
sunbeam/home/laforge/projects/git/openpcd/firmware/include/simtrace_usb.h
this might not be generic enough
to keep it linked, it could point to
../../../openpcd/firmware/include/simtrace_usb.h

or will openpcd and simtrace be merged, or combined in any way ?

thanks,
kevin



From laforge at gnumonks.org  Sat Jan  8 22:12:00 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Sat, 8 Jan 2011 23:12:00 +0100
Subject: simtrace simtrace_usb.h
In-Reply-To: <4D288BB5.3070408@mail.tsaitgaist.info>
References: <4D288BB5.3070408@mail.tsaitgaist.info>
Message-ID: <20110108221200.GI32270@prithivi.gnumonks.org>

On Sat, Jan 08, 2011 at 05:07:17PM +0100, ml at mail.tsaitgaist.info wrote:
 
> in simtrace/at91sam7/host, simtrace_usb.h is symbolically linked to
> sunbeam/home/laforge/projects/git/openpcd/firmware/include/simtrace_usb.h
> this might not be generic enough
> to keep it linked, it could point to
> ../../../openpcd/firmware/include/simtrace_usb.h

thanks, I've fixed this.
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From sweisman at pobox.com  Sun Jan  9 11:01:15 2011
From: sweisman at pobox.com (Scott Weisman)
Date: Sun, 9 Jan 2011 13:01:15 +0200
Subject: where to get osmocom-supported phones
Message-ID: <AANLkTim=LmKH1zYY3wrEfknBS+UREmA6LSe45mq724=g@mail.gmail.com>

I know this has been asked before, but I can't find the email(s). eBay
in the past has generally had a few GSM900/1800 Osmocom-supported
phones, although the prices weren't always great. I managed to get a
V171 that way from a Hong Kong source (for about US$20 including
shipping). However, the only phones that seem available today are all
GSM850/1900.

Someone a while back gave a link to Polish site where you could buy
phones for even cheaper. Does someone have that site, or other sites
that might be useful?

Thanks,

Scott



From maciej.grela at gmail.com  Sun Jan  9 11:17:04 2011
From: maciej.grela at gmail.com (Maciej Grela)
Date: Sun, 9 Jan 2011 12:17:04 +0100
Subject: where to get osmocom-supported phones
In-Reply-To: <AANLkTim=LmKH1zYY3wrEfknBS+UREmA6LSe45mq724=g@mail.gmail.com>
References: <AANLkTim=LmKH1zYY3wrEfknBS+UREmA6LSe45mq724=g@mail.gmail.com>
Message-ID: <AANLkTi=uV-O0yF2voMgym3ag4sB1v2aJ3Afq1o+_Bm6P@mail.gmail.com>

2011/1/9 Scott Weisman <sweisman at pobox.com>:
> I know this has been asked before, but I can't find the email(s). eBay
> in the past has generally had a few GSM900/1800 Osmocom-supported
> phones, although the prices weren't always great. I managed to get a
> V171 that way from a Hong Kong source (for about US$20 including
> shipping). However, the only phones that seem available today are all
> GSM850/1900.
>
> Someone a while back gave a link to Polish site where you could buy
> phones for even cheaper. Does someone have that site, or other sites
> that might be useful?
>

For example here:

http://allegro.pl/motorola-c118-stan-bdb-bez-simlocka-i1388956031.html

It costs 18 PLN with shipping.

Br,
Maciej Grela



From mki at mki-consult.de  Sun Jan  9 11:46:42 2011
From: mki at mki-consult.de (mki)
Date: Sun, 9 Jan 2011 03:46:42 -0800 (PST)
Subject: problems on ubuntu (64bit?)
Message-ID: <1294573602393-2220808.post@n3.nabble.com>


if i boot the c118 from a ubuntu 10.04 lts (64bit) or a g20 arm minipc i get
this here

/opt/osmocom/bin/osmocon -m c123 -p /dev/ttyUSB0
/opt/osmocom/firmware/board/compal_e88/layer1.compalram.bin

got 2 bytes from modem, data looks like: 2f 81  /.
got 5 bytes from modem, data looks like: 00 f6 02 00 41  ....A
got 1 bytes from modem, data looks like: 01  .
got 1 bytes from modem, data looks like: 40  @
got 1 bytes from modem, data looks like: 66  f
got 1 bytes from modem, data looks like: 74  t
got 1 bytes from modem, data looks like: 6d  m
got 1 bytes from modem, data looks like: 74  t
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 6c  l
Received FTMTOOL from phone, ramloader has aborted
got 1 bytes from modem, data looks like: 65  e
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 00  .

if i boot it from my mac book or a ubuntu (32bit) i get this:
osmocon -m c123xor -p /dev/tty.usbserial
sylvain/osmocom-bb/src/target/firmware/board/compal_e88/layer1.compalram.bin 
got 6 bytes from modem, data looks like: 00 00 00 00 00 00  ......
got 1 bytes from modem, data looks like: 2f  /
got 1 bytes from modem, data looks like: 81  .
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: 41  A
got 1 bytes from modem, data looks like: 01  .
got 1 bytes from modem, data looks like: 40  @
Received PROMPT1 from phone, responding with CMD
read_file(sylvain/osmocom-bb/src/target/firmware/board/compal_e88/layer1.compalram.bin):
file_size=54152, hdr_len=4, dnload_len=54159
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: 41  A
got 1 bytes from modem, data looks like: 02  .
got 1 bytes from modem, data looks like: 43  C
Received PROMPT2 from phone, starting download
handle_write(): 1023 bytes (1023/54159)
handle_write(): 1024 bytes (2047/54159)
handle_write(): 1024 bytes (3071/54159)
handle_write(): 1024 bytes (4095/54159)
handle_write(): 1024 bytes (5119/54159)
handle_write(): 1024 bytes (6143/54159)
handle_write(): 1024 bytes (7167/54159)
handle_write(): 1024 bytes (8191/54159)
handle_write(): 1024 bytes (9215/54159)
handle_write(): 1024 bytes (10239/54159)
handle_write(): 1024 bytes (11263/54159)
handle_write(): 1024 bytes (12287/54159)
handle_write(): 1024 bytes (13311/54159)
handle_write(): 1024 bytes (14335/54159)
handle_write(): 1024 bytes (15359/54159)
handle_write(): 1024 bytes (16383/54159)
handle_write(): 1024 bytes (17407/54159)
handle_write(): 1024 bytes (18431/54159)
handle_write(): 1024 bytes (19455/54159)
handle_write(): 1024 bytes (20479/54159)
handle_write(): 1024 bytes (21503/54159)
handle_write(): 1024 bytes (22527/54159)
handle_write(): 1024 bytes (23551/54159)
handle_write(): 1024 bytes (24575/54159)
handle_write(): 1024 bytes (25599/54159)
handle_write(): 1024 bytes (26623/54159)
handle_write(): 1024 bytes (27647/54159)
handle_write(): 1024 bytes (28671/54159)
handle_write(): 1024 bytes (29695/54159)
handle_write(): 1024 bytes (30719/54159)
handle_write(): 1024 bytes (31743/54159)
handle_write(): 1024 bytes (32767/54159)
handle_write(): 1024 bytes (33791/54159)
handle_write(): 1024 bytes (34815/54159)
handle_write(): 1024 bytes (35839/54159)
handle_write(): 1024 bytes (36863/54159)
handle_write(): 1024 bytes (37887/54159)
handle_write(): 1024 bytes (38911/54159)
handle_write(): 1024 bytes (39935/54159)
handle_write(): 1024 bytes (40959/54159)
handle_write(): 1024 bytes (41983/54159)
handle_write(): 1024 bytes (43007/54159)
handle_write(): 1024 bytes (44031/54159)
handle_write(): 1024 bytes (45055/54159)
handle_write(): 1024 bytes (46079/54159)
handle_write(): 1024 bytes (47103/54159)
handle_write(): 1024 bytes (48127/54159)
handle_write(): 1024 bytes (49151/54159)
handle_write(): 1024 bytes (50175/54159)
handle_write(): 1024 bytes (51199/54159)
handle_write(): 1024 bytes (52223/54159)
handle_write(): 1024 bytes (53247/54159)
handle_write(): 912 bytes (54159/54159)
handle_write(): finished
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: 41  A
got 1 bytes from modem, data looks like: 03  .
got 1 bytes from modem, data looks like: 42  B
Received DOWNLOAD ACK from phone, your code is running now!


OSMOCOM Layer 1 (revision osmocon_v0.0.0-737-ga4e3431-modified)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: c1900c14ae021565
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
======================================================================
Power up simcard:
Assert DSP into Reset
Releasing DSP from Reset
Setting some dsp_api.ndb values
Setting API NDB parameters
DSP Download Status: 0x0001
DSP API Version: 0x0000 0x0000
Finishing download phase
DSP Download Status: 0x0002
DSP API Version: 0x3606 0x0000
LOST 1880!

-- its working :-)

I have tried to copy the firmware from the working machine to the bad
machines but the result is the same.
Is it possible that the usb driver from ubuntu 10.04 lts 64bit is silly???? 
cable (akku-king) phone all is the same on every plattform.
Have some body an Idea?


-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-on-ubuntu-64bit-tp2220808p2220808.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From mki at mki-consult.de  Sun Jan  9 13:48:35 2011
From: mki at mki-consult.de (mki)
Date: Sun, 9 Jan 2011 05:48:35 -0800 (PST)
Subject: problems on ubuntu (64bit?)
In-Reply-To: <1294573602393-2220808.post@n3.nabble.com>
References: <1294573602393-2220808.post@n3.nabble.com>
Message-ID: <1294580915934-2221236.post@n3.nabble.com>


some more informations:
sometimes it is running, e.g. after a fresh reboot, 
but not after a rmmod pl2303 and modprobe pl2303.
It seems it is something with the timing.
Other people has also problems with programmers/chipreaders 
based on the pl2303 chipset and new ubuntu installations.
Any ideas??

-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-on-ubuntu-64bit-tp2220808p2221236.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From 246tnt at gmail.com  Sun Jan  9 13:58:32 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Sun, 9 Jan 2011 14:58:32 +0100
Subject: problems on ubuntu (64bit?)
In-Reply-To: <1294580915934-2221236.post@n3.nabble.com>
References: <1294573602393-2220808.post@n3.nabble.com>
	<1294580915934-2221236.post@n3.nabble.com>
Message-ID: <AANLkTinjRWYMYZAYD3beyqfSBuDv7C3saFHjkAe0BuHr@mail.gmail.com>

Hi,


> some more informations:
> sometimes it is running, e.g. after a fresh reboot,
> but not after a rmmod pl2303 and modprobe pl2303.
> It seems it is something with the timing.
> Other people has also problems with programmers/chipreaders
> based on the pl2303 chipset and new ubuntu installations.
> Any ideas??

The bootloader inside the phone is sensitive to timing ... not really
anything we can do about it. (basically if there is a 'gap' too big
between two chars, the bootloader will fail).

You can try the mode -m c123xor  instead of -m c123  (which mods a
small detail).

Also make sure you don't use a virtual machine, that screws up the
timing almost certainly.


Cheers,

    Sylvain



From mki at mki-consult.de  Sun Jan  9 14:15:26 2011
From: mki at mki-consult.de (mki)
Date: Sun, 9 Jan 2011 06:15:26 -0800 (PST)
Subject: problems on ubuntu (64bit?)
In-Reply-To: <AANLkTinjRWYMYZAYD3beyqfSBuDv7C3saFHjkAe0BuHr@mail.gmail.com>
References: <1294573602393-2220808.post@n3.nabble.com>
	<1294580915934-2221236.post@n3.nabble.com>
	<AANLkTinjRWYMYZAYD3beyqfSBuDv7C3saFHjkAe0BuHr@mail.gmail.com>
Message-ID: <1294582526626-2221354.post@n3.nabble.com>


i have tried both modes on a fresh installed ThinkPad T61,
on a slower Atom based machine it is working,
but on a embedded foxg20 with a arm cpu only sometimes.
really strange....

-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-on-ubuntu-64bit-tp2220808p2221354.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From mki at mki-consult.de  Mon Jan 10 17:37:31 2011
From: mki at mki-consult.de (mki)
Date: Mon, 10 Jan 2011 09:37:31 -0800 (PST)
Subject: problems on ubuntu (64bit?)
In-Reply-To: <1294582526626-2221354.post@n3.nabble.com>
References: <1294573602393-2220808.post@n3.nabble.com>
	<1294580915934-2221236.post@n3.nabble.com>
	<AANLkTinjRWYMYZAYD3beyqfSBuDv7C3saFHjkAe0BuHr@mail.gmail.com>
	<1294582526626-2221354.post@n3.nabble.com>
Message-ID: <1294681051253-2228742.post@n3.nabble.com>


so, i have connected the serial from the netus g20 board directly to the C118
and it is running but at the same machine with the akku-king adapter it is
not :-(
but for now i am lucky to have a super small computer working with your
great software
-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-on-ubuntu-64bit-tp2220808p2228742.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From osmocom at ehlers.info  Sun Jan  9 13:30:16 2011
From: osmocom at ehlers.info (Tim Ehlers)
Date: Sun, 9 Jan 2011 14:30:16 +0100 (CET)
Subject: GSM Codes with Osmocombb
Message-ID: <alpine.LNX.2.00.1101091423080.28764@ssn.gwdg.de>

Hi,

I'm playing around with Osmocom for a while now. My final goal is to use 
it as a stationary phone on a PC to be able to remotly control the phone.

I checked out the sylvain/testing tree, to use my SIM card and managed to 
be able to make and receive calls. Very amazing so far. :-)

Now I tried to send GSM codes (like *#21#, oder *21*{NUMBER}#) to set and 
unset call diverts. It seems, that "call 1 *21*{NUMBER}#" does not work. 
Normal GSM cellphones seem to handle these codes not as a normal call.

Does anybody know how one could send GSM codes to the network?

Thanks

Tim



From 246tnt at gmail.com  Sun Jan  9 13:55:23 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Sun, 9 Jan 2011 14:55:23 +0100
Subject: GSM Codes with Osmocombb
In-Reply-To: <alpine.LNX.2.00.1101091423080.28764@ssn.gwdg.de>
References: <alpine.LNX.2.00.1101091423080.28764@ssn.gwdg.de>
Message-ID: <AANLkTik6aiUCjtzRki6MJtTqfBwn-Po8ozpU6H9uytY2@mail.gmail.com>

Hi,


> Now I tried to send GSM codes (like *#21#, oder *21*{NUMBER}#) to set and
> unset call diverts. It seems, that "call 1 *21*{NUMBER}#" does not work.
> Normal GSM cellphones seem to handle these codes not as a normal call.

Theses are called USSD and are not implemented in mobile yet

Unstructured Supplementary Service Data (USSD)
GSM 03.90 IIRC.


> Does anybody know how one could send GSM codes to the network?

Sure:
Read the specs for USSD, implement them and submit the patch :)

Cheers,

    Sylvain



From lists at infosecurity.ch  Sun Jan  9 14:08:21 2011
From: lists at infosecurity.ch (Fabio Pietrosanti (naif))
Date: Sun, 09 Jan 2011 15:08:21 +0100
Subject: GSM Codes with Osmocombb
In-Reply-To: <AANLkTik6aiUCjtzRki6MJtTqfBwn-Po8ozpU6H9uytY2@mail.gmail.com>
References: <alpine.LNX.2.00.1101091423080.28764@ssn.gwdg.de>
	<AANLkTik6aiUCjtzRki6MJtTqfBwn-Po8ozpU6H9uytY2@mail.gmail.com>
Message-ID: <4D29C155.2020201@infosecurity.ch>

On 09/01/11 14.55, Sylvain Munaut wrote:
> Sure:
> Read the specs for USSD, implement them and submit the patch :)
A long time ago when i was young and under 18 years old, made a small
USSD scanner by scripting modem interface to find out undocumented USSD
codes in operator's networks.

Found a lot of USSD codes giving "Syntax error" or "APPLICATION NOT
REGISTERED" or "Timeout" .
I always desired to have an USSD scanner and USSD parameter brute forcer
running directly inside a phone!

Another cool protocol like USSD is the UUS (User to User Signaling)
http://www.turkcell.com.tr/c/oth/terminalpdf/23087-800.pdf .

For sure it's not provided on mobile handsets, but who know, maybe some
networks have it by default allowed and two GSM subscriber could
exchange data for free :-)

Fabio



From frank at rosengart.de  Sun Jan  9 15:19:02 2011
From: frank at rosengart.de (Frank Rosengart)
Date: Sun, 09 Jan 2011 16:19:02 +0100
Subject: C123: reading SIM stuck
Message-ID: <4D29D1E6.4050402@rosengart.de>

Hi,

just for curiosity, I would like to get the osmocomBB running on the
Motorola C123. Everything works fine (radio starts scanning for
networks) if I use the test SIM feature. But reading a real SIM plugged
into the phone does not work for me.
The 'mobile' app shows:
<0004> subscriber.c:556 Requesting SIM file 0x2fe2
<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)
<000e> sim.c:697 go MF
<000e> sim.c:241 SELECT (file=0x3f00)
<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)
-end-

Any hints where to start debugging?
(does neither work with 3 different SIMs: swisscom, blau, super-sim)

BTW: Are there any plans to support external SIM readers via PC/SC etc.?

Thanks
Frank



From steve at steve-m.de  Sun Jan  9 15:23:20 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Sun, 09 Jan 2011 16:23:20 +0100
Subject: C123: reading SIM stuck
In-Reply-To: <4D29D1E6.4050402@rosengart.de>
References: <4D29D1E6.4050402@rosengart.de>
Message-ID: <4D29D2E8.9050602@steve-m.de>

Hi,

On 09.01.2011 16:19, Frank Rosengart wrote:

> Any hints where to start debugging?
> (does neither work with 3 different SIMs: swisscom, blau, super-sim)

master does not contain the sim-reader code yet, as it still needs to be 
cleaned up. So you need to checkout sylvain/testing for sim support at 
the moment.

Regards,
Steve



From 246tnt at gmail.com  Sun Jan  9 15:54:44 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Sun, 9 Jan 2011 16:54:44 +0100
Subject: C123: reading SIM stuck
In-Reply-To: <4D29D2E8.9050602@steve-m.de>
References: <4D29D1E6.4050402@rosengart.de>
	<4D29D2E8.9050602@steve-m.de>
Message-ID: <AANLkTi=u+1n-3=r4omkBHmB-FWvJfRCAXxy9tYyJWoJv@mail.gmail.com>

Hi,

>> Any hints where to start debugging?
>> (does neither work with 3 different SIMs: swisscom, blau, super-sim)
>
> master does not contain the sim-reader code yet, as it still needs to be
> cleaned up. So you need to checkout sylvain/testing for sim support at the
> moment.

And btw, notice to everyone joining ... if you're looking for
something simple but dreadly useful to do to contribute back to the
project, cleaning up the sim patch that's in my branch and making it
into a mergeable shape would be an awesome contribution ...

Cheers,

    Sylvain



From dpavlin at rot13.org  Sun Jan  9 18:05:26 2011
From: dpavlin at rot13.org (Dobrica Pavlinusic)
Date: Sun, 9 Jan 2011 19:05:26 +0100
Subject: C123: reading SIM stuck
In-Reply-To: <AANLkTi=u+1n-3=r4omkBHmB-FWvJfRCAXxy9tYyJWoJv@mail.gmail.com>
References: <4D29D1E6.4050402@rosengart.de> <4D29D2E8.9050602@steve-m.de>
	<AANLkTi=u+1n-3=r4omkBHmB-FWvJfRCAXxy9tYyJWoJv@mail.gmail.com>
Message-ID: <20110109180526.GC6310@rot13.org>

On Sun, Jan 09, 2011 at 04:54:44PM +0100, Sylvain Munaut wrote:
> Hi,
> 
> >> Any hints where to start debugging?
> >> (does neither work with 3 different SIMs: swisscom, blau, super-sim)
> >
> > master does not contain the sim-reader code yet, as it still needs to be
> > cleaned up. So you need to checkout sylvain/testing for sim support at the
> > moment.
> 
> And btw, notice to everyone joining ... if you're looking for
> something simple but dreadly useful to do to contribute back to the
> project, cleaning up the sim patch that's in my branch and making it
> into a mergeable shape would be an awesome contribution ...

FWIW, i merged master on top of testing branch and that worked well for me.

What else would be required aside from few identing tweaks to make this
merged?

-- 
Dobrica Pavlinusic               2share!2flame            dpavlin at rot13.org
Unix addict. Internet consultant.             http://www.rot13.org/~dpavlin



From 246tnt at gmail.com  Sun Jan  9 18:08:31 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Sun, 9 Jan 2011 19:08:31 +0100
Subject: C123: reading SIM stuck
In-Reply-To: <20110109180526.GC6310@rot13.org>
References: <4D29D1E6.4050402@rosengart.de> <4D29D2E8.9050602@steve-m.de>
	<AANLkTi=u+1n-3=r4omkBHmB-FWvJfRCAXxy9tYyJWoJv@mail.gmail.com>
	<20110109180526.GC6310@rot13.org>
Message-ID: <AANLkTinR7pf58rSGPpnEEFst-YFTWBMp=sonUv7to+BU@mail.gmail.com>

> FWIW, i merged master on top of testing branch and that worked well for me.
>
> What else would be required aside from few identing tweaks to make this
> merged?

Remove dead code and all the FIXME that are in in, kernel coding style ...
If you fix that already, I'll review the code again and let you know
what's still wrong :)

and preferably switch to BTSAP ... but that could wait.


Cheers,

    Sylvain



From mattjevans at btinternet.com  Sun Jan  9 19:23:11 2011
From: mattjevans at btinternet.com (MATTHEW EVANS)
Date: Sun, 9 Jan 2011 19:23:11 +0000 (GMT)
Subject: OSX build
In-Reply-To: <mailman.2305.1294582530.21529.baseband-devel@lists.osmocom.org>
References: <mailman.2305.1294582530.21529.baseband-devel@lists.osmocom.org>
Message-ID: <390295.95189.qm@web86606.mail.ird.yahoo.com>

Hi All,

I'm really struggling to get the latest source to build on OSX. Would anyone be 
kind enough to offer some assistance to getting this compiled?

Build fails with:

./configure: line 3461: syntax error near unexpected token `LIBOSMOCORE,'
./configure: line 3461: `PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore)'

Any help or advice would be appreciated!

Many Thanks,

Matt.



From holger at freyther.de  Sun Jan  9 20:36:59 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sun, 09 Jan 2011 21:36:59 +0100
Subject: OSX build
In-Reply-To: <390295.95189.qm@web86606.mail.ird.yahoo.com>
References: <mailman.2305.1294582530.21529.baseband-devel@lists.osmocom.org>
	<390295.95189.qm@web86606.mail.ird.yahoo.com>
Message-ID: <4D2A1C6B.4080000@freyther.de>

On 01/09/2011 08:23 PM, MATTHEW EVANS wrote:

> 
> ./configure: line 3461: syntax error near unexpected token `LIBOSMOCORE,'
> ./configure: line 3461: `PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore)'
> 
> Any help or advice would be appreciated!

You need to install pkg-config (which will install a pkgconfig.m4 or such)



From softwaredefinesradio at gmail.com  Mon Jan 10 21:28:46 2011
From: softwaredefinesradio at gmail.com (SoftwareRadioGuy)
Date: Mon, 10 Jan 2011 15:28:46 -0600
Subject: =?ISO-2022-JP?B?SXMgdGhpcyB0cnVlPyAtLS0tPiBSZTogGyRCI1UjUyNFISEjTSNUI0shISNjGyhC?=
	=?ISO-2022-JP?B?GyRCI2gjaSNwISEjcCNoI28jbiNlISEjZiNvI3IhISNEI0kjWSEhI3kjbxsoQg==?=
	=?ISO-2022-JP?B?GyRCI3UjciNzI2UjbCNmISEbKEIgGyRCI0IjVCNTGyhC?=
Message-ID: <AANLkTimhNAjNmAtQL=8kgVMBYKgepDbSLXBjnSVZs3W1@mail.gmail.com>

Everyone,


Is it true you can use a MTK Chipset as a DIY GSM BTS/USRP ?

I've emailed this fellow who posted this back in December 2010
but have gotten no reply to date.

This would be excellent for use on something I'm working
on in Africa for about 50 - 100 IMPOVERISHED villages.

Awaiting anyone's input on this.

Thank you

SoftwareDefinesRadio



2010/12/15 <baseband-devel-request at lists.osmocom.org>

>
>
> Today's Topics:
>
>   1. Price Cheap of USRP for openbts and  GSM  ( ???? )
>
>
> ---------- Forwarded message ----------
> From: "????" <775725965 at qq.com>
> To: "baseband-devel" <baseband-devel at lists.osmocom.org>
> Date: Wed, 15 Dec 2010 14:18:50 +0800
> Subject: Price Cheap of USRP for openbts and GSM
>
>  Hello everybody
>  you may have USRP ??? ??? ???? ????? ??? ??? ????????  ??? Simple ???
> Practical ? ???? Development?? Contact ??
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110110/48c84c0b/attachment.htm>

From 246tnt at gmail.com  Mon Jan 10 22:20:01 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Mon, 10 Jan 2011 23:20:01 +0100
Subject: =?UTF-8?B?UmU6IElzIHRoaXMgdHJ1ZT8gLS0tLT4gUmU6IO+8te+8s++8pSDvvK3vvLTvvKsg772D?=
	=?UTF-8?B?772I772J772QIO+9kO+9iO+9j++9ju+9hSDvvYbvvY/vvZIg77yk77yp77y5IO+9me+9j++9le+9kg==?=
	=?UTF-8?B?772T772F772M772GIO+8ou+8tO+8sw==?=
In-Reply-To: <AANLkTimhNAjNmAtQL=8kgVMBYKgepDbSLXBjnSVZs3W1@mail.gmail.com>
References: <AANLkTimhNAjNmAtQL=8kgVMBYKgepDbSLXBjnSVZs3W1@mail.gmail.com>
Message-ID: <AANLkTi==qkxLj6WzBSf4CvMorZGL+gV_xB_HwcFRBpNF@mail.gmail.com>

Hi,


> Is it true you can use a MTK Chipset as a DIY GSM BTS/USRP ?

No


Cheers,

    Sylvain



From 775725965 at qq.com  Tue Jan 11 12:29:52 2011
From: 775725965 at qq.com (=?gbk?B?wvPM78rYzfs=?=)
Date: Tue, 11 Jan 2011 20:29:52 +0800
Subject: i need help i use MTK chip to do a GSM USRP For my love girl 
Message-ID: <tencent_181DEE746F1A3B755574F8A9@qq.com>

i need help  i will USE MTK6219+6129  to do a GSM USRP    i  need baseband Firmware or USB interface to Connection  PC                           the all base openbts
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110111/bcb3f5e8/attachment.htm>

From squalyl at gmail.com  Tue Jan 11 13:19:01 2011
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Tue, 11 Jan 2011 14:19:01 +0100
Subject: i need help i use MTK chip to do a GSM USRP For my love girl
In-Reply-To: <tencent_181DEE746F1A3B755574F8A9@qq.com>
References: <tencent_181DEE746F1A3B755574F8A9@qq.com>
Message-ID: <AANLkTikaz0sMofq+kctRcAHod+KJrBvoUC=FnSuNFNZR@mail.gmail.com>

this is not relevant to our interest.

I think a ban is required here.

2011/1/11 ???? <775725965 at qq.com>

> i need help  i will USE MTK6219+6129  to do a GSM USRP    i  need baseband
> Firmware or USB interface to Connection  PC                           the
> all base openbts
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110111/b327f112/attachment.htm>

From laforge at gnumonks.org  Tue Jan 11 20:37:25 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 11 Jan 2011 21:37:25 +0100
Subject: i need help i use MTK chip to do a GSM USRP For my love girl
In-Reply-To: <tencent_181DEE746F1A3B755574F8A9@qq.com>
References: <tencent_181DEE746F1A3B755574F8A9@qq.com>
Message-ID: <9a6d696a-3a77-4ad3-8422-bc1506ee94c7@email.android.com>

Dear unknown,

first of all: this is not a group of people who will design your product for you. This is a community, everyone gives and takes. So far, we are not intending to build anything like a USRP.

So if you want to get any jelp from us, tou would have to explain yoir product and give us some reason/motivation how we, or the community at large will bwnefit from it.

Secondly, your mails could be more verbouse, explain who you are, what you are doing and why.

Third, please don't use sublect lines like "for my love girl". That makes your message look like spam, and it has no relevance to the topic here.

Regards, Harald

"????" <775725965 at qq.com> wrote:

>i need help  i will USE MTK6219+6129  to do a GSM USRP    i  need
>baseband Firmware or USB interface to Connection  PC                   
>       the all base openbts

--
Sent from a mobile device, excuse my short response



From quemtuquiseres1 at yahoo.com  Fri Jan 14 12:53:11 2011
From: quemtuquiseres1 at yahoo.com (quem tu quiseres)
Date: Fri, 14 Jan 2011 04:53:11 -0800 (PST)
Subject: Problem compiling OsmocomBB on BT4 RC2
Message-ID: <62178.47191.qm@web39303.mail.mud.yahoo.com>

Hi,

I just started playing around with this great project and am ashamed to say I'm 
stumped with an annoying error when compiling.
I'm compiling on a Backtrack 4 RC2 (*buntu based distro) and that may be why I'm 
having problems.
Basically I downloaded the proper packages as per the instructions on the wiki, 
exported the PATH and all that, but when I run make I get this error:

cd shared/libosmocore/build-target && ../configure \
                        --host=arm-elf-linux --disable-vty 
--enable-panic-infloop \
                        --disable-shared --disable-talloc --disable-tests \
                CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections 
-I/root/GSM/osmocom-bb/src/target/firmware/include"
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
configure: error: cannot find install-sh or install.sh in ".." "../.." 
"../../.."
make: *** [shared/libosmocore/build-target/Makefile] Error 1


Attached is my config.log and you can see the PATH are there.

The error can be seen on this line in the log "configure:1766: error: cannot 
find install-sh or install.sh in ".." "../.." "../../.."


Now i've checked to see if I have autoconf and automake installed (I do, I have 
autoconf 2.61 and automake 1.10) since my searches on the internet seem to 
indicate that maybe the problem.

Now I usually do all my own leg work and I read and read before asking 
questions, but I'm afraid I can't resolve this on my own. Before I spend another 
afternoon searching for the solution, I remembered to ask here.

Anyone have any hints on what I'm doing wrong? Do I need different automake or 
autoconf versions?

Thanks and keep up the great work. It's been fascinating to watch the evolution 
of GSM hacking these last few years.



      
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log
Type: application/octet-stream
Size: 4132 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110114/4b2bb38f/attachment.obj>

From stephan.meier at unitybox.de  Fri Jan 14 21:52:42 2011
From: stephan.meier at unitybox.de (Stephan Meier)
Date: Fri, 14 Jan 2011 22:52:42 +0100
Subject: Problem compiling OsmocomBB on BT4 RC2
In-Reply-To: <62178.47191.qm@web39303.mail.mud.yahoo.com>
References: <62178.47191.qm@web39303.mail.mud.yahoo.com>
Message-ID: <4D30C5AA.8070303@unitybox.de>

Hi,

if you didn't install "libtool" (apt-get install libtool), you'll get
this error if you try to compile the source for the second time.
Install libtool, clean up your source tree (delete the temp files
generated by the autotools; cloning again may be easier for you) and try
again.

Cheers,
    Stephan

On 01/14/2011 01:53 PM, quem tu quiseres wrote:
> Hi,
>
> I just started playing around with this great project and am ashamed to say I'm 
> stumped with an annoying error when compiling.
> I'm compiling on a Backtrack 4 RC2 (*buntu based distro) and that may be why I'm 
> having problems.
> Basically I downloaded the proper packages as per the instructions on the wiki, 
> exported the PATH and all that, but when I run make I get this error:
>
> cd shared/libosmocore/build-target && ../configure \
>                         --host=arm-elf-linux --disable-vty 
> --enable-panic-infloop \
>                         --disable-shared --disable-talloc --disable-tests \
>                 CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections 
> -I/root/GSM/osmocom-bb/src/target/firmware/include"
> configure: WARNING: If you wanted to set the --build type, don't use --host.
>     If a cross compiler is detected then cross compile mode will be used.
> configure: error: cannot find install-sh or install.sh in ".." "../.." 
> "../../.."
> make: *** [shared/libosmocore/build-target/Makefile] Error 1
>
>
> Attached is my config.log and you can see the PATH are there.
>
> The error can be seen on this line in the log "configure:1766: error: cannot 
> find install-sh or install.sh in ".." "../.." "../../.."
>
>
> Now i've checked to see if I have autoconf and automake installed (I do, I have 
> autoconf 2.61 and automake 1.10) since my searches on the internet seem to 
> indicate that maybe the problem.
>
> Now I usually do all my own leg work and I read and read before asking 
> questions, but I'm afraid I can't resolve this on my own. Before I spend another 
> afternoon searching for the solution, I remembered to ask here.
>
> Anyone have any hints on what I'm doing wrong? Do I need different automake or 
> autoconf versions?
>
> Thanks and keep up the great work. It's been fascinating to watch the evolution 
> of GSM hacking these last few years.
>
>
>
>       




From quemtuquiseres1 at yahoo.com  Sat Jan 15 13:19:59 2011
From: quemtuquiseres1 at yahoo.com (quem tu quiseres)
Date: Sat, 15 Jan 2011 05:19:59 -0800 (PST)
Subject: Problem compiling OsmocomBB on BT4 RC2
In-Reply-To: <4D30C5AA.8070303@unitybox.de>
References: <62178.47191.qm@web39303.mail.mud.yahoo.com>
	<4D30C5AA.8070303@unitybox.de>
Message-ID: <148591.57274.qm@web39309.mail.mud.yahoo.com>

Thanks for your help Stephan.
I had libtool installed already but for some reason it wasn't working well in 
the BT4 install.

After much frustration I ended up doing a fresh ubuntu install on virtualbox and 
ran into other problems that others may experience if they try this route.
Basically my problem has to do with the recognition of the USB/serial prolific 
cable by the guest OS (ubuntu). If you experience this issue too I recommend a 
reboot of both host and guest with the cable hooked up (and previously installed 
on your host). After much head scratching a good 'ole reboot did the trick.

Now I can finally talk to my C115 and can't wait to to explore the different 
tools.
Anyone have any recommendations on where to start, what apps to try first, 
guides, etc (besides the wiki)?

Thanks again,
John

P.S. I gather that Sylvain's code to "strip" the encryption from the stream 
passed by the DSP isn't available. Are there any plans to share that too?




----- Original Message ----
From: Stephan Meier <stephan.meier at unitybox.de>
To: quem tu quiseres <quemtuquiseres1 at yahoo.com>
Cc: baseband-devel at lists.osmocom.org
Sent: Fri, January 14, 2011 9:52:42 PM
Subject: Re: Problem compiling OsmocomBB on BT4 RC2

Hi,

if you didn't install "libtool" (apt-get install libtool), you'll get
this error if you try to compile the source for the second time.
Install libtool, clean up your source tree (delete the temp files
generated by the autotools; cloning again may be easier for you) and try
again.

Cheers,
    Stephan

On 01/14/2011 01:53 PM, quem tu quiseres wrote:
> Hi,
>
> I just started playing around with this great project and am ashamed to say I'm 
>
> stumped with an annoying error when compiling.
> I'm compiling on a Backtrack 4 RC2 (*buntu based distro) and that may be why 
>I'm 
>
> having problems.
> Basically I downloaded the proper packages as per the instructions on the wiki, 
>
> exported the PATH and all that, but when I run make I get this error:
>
> cd shared/libosmocore/build-target && ../configure \
>                         --host=arm-elf-linux --disable-vty 
> --enable-panic-infloop \
>                         --disable-shared --disable-talloc --disable-tests \
>                 CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections 
> -I/root/GSM/osmocom-bb/src/target/firmware/include"
> configure: WARNING: If you wanted to set the --build type, don't use --host.
>     If a cross compiler is detected then cross compile mode will be used.
> configure: error: cannot find install-sh or install.sh in ".." "../.." 
> "../../.."
> make: *** [shared/libosmocore/build-target/Makefile] Error 1
>
>
> Attached is my config.log and you can see the PATH are there.
>
> The error can be seen on this line in the log "configure:1766: error: cannot 
> find install-sh or install.sh in ".." "../.." "../../.."
>
>
> Now i've checked to see if I have autoconf and automake installed (I do, I have 
>
> autoconf 2.61 and automake 1.10) since my searches on the internet seem to 
> indicate that maybe the problem.
>
> Now I usually do all my own leg work and I read and read before asking 
> questions, but I'm afraid I can't resolve this on my own. Before I spend 
>another 
>
> afternoon searching for the solution, I remembered to ask here.
>
> Anyone have any hints on what I'm doing wrong? Do I need different automake or 

> autoconf versions?
>
> Thanks and keep up the great work. It's been fascinating to watch the evolution 
>
> of GSM hacking these last few years.
>
>
>
>      


      



From quemtuquiseres1 at yahoo.com  Mon Jan 17 16:20:16 2011
From: quemtuquiseres1 at yahoo.com (quem tu quiseres)
Date: Mon, 17 Jan 2011 08:20:16 -0800 (PST)
Subject: Problem compiling OsmocomBB on BT4 RC2
In-Reply-To: <148591.57274.qm@web39309.mail.mud.yahoo.com>
Message-ID: <300674.90517.qm@web39309.mail.mud.yahoo.com>

Hi again,

In case anyone was wondering, I had libtool installed but for some reason it wasn't working right when compiling so I reinstalled it, deleted the osmocom branch and started over from scratch. This time it worked without a problem and i managed to get layer21 up and running on my C115. So if you get similar error messages I recommend deleting and starting over from scratch.
Now I tried to play around with sylvain's testing branch and I'm getting compile errors. I know this is a bit long to post here but maybe someone here knows what these errors are all about. You can see that the errors begin with the simtest app:

rm-elf-gcc -mcpu=arm7tdmi -Iinclude/ -I../../../include -I../../shared/libosmocore/include -Wall -Wextra -Wcast-align -Wimplicit -Wunused -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wnested-externs -Wbad-function-cast -Wsign-compare -Waggregate-return -Os -ffunction-sections -gdwarf-2 -DGIT_REVISION=\"osmocon_v0.0.0-756-g999254a-modified\" -DCONFIG_TX_ENABLE -DCONFIG_FLASH_WRITE -Wa,-adhlns=apps/simtest/main.lst -c -o apps/simtest/main.o apps/simtest/main.c
apps/simtest/main.c:161: error: parse error before '<<' token
apps/simtest/main.c:168: error: parse error before numeric constant
apps/simtest/main.c:168: warning: type defaults to `int' in declaration of `memset'
apps/simtest/main.c:168: error: conflicting types for 'memset'
apps/simtest/main.c:168: error: conflicting types for 'memset'
apps/simtest/main.c:168: warning: data definition has no type or storage class
apps/simtest/main.c:169: error: parse error before '(' token
apps/simtest/main.c: In function `sim_run_gsm_algorith':
apps/simtest/main.c:179: warning: declaration of 'status_word' shadows a global declaration
apps/simtest/main.c:166: warning: shadowed declaration is here
apps/simtest/main.c: At top level:
apps/simtest/main.c:215: error: parse error before '>>' token
apps/simtest/main.c:230: error: parse error before numeric constant
apps/simtest/main.c:237: error: parse error before numeric constant
apps/simtest/main.c:239: error: parse error before string constant
apps/simtest/main.c:239: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:239: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:239: warning: data definition has no type or storage class
apps/simtest/main.c:242: error: parse error before string constant
apps/simtest/main.c:242: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:242: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:242: warning: data definition has no type or storage class
apps/simtest/main.c:243: warning: type defaults to `int' in declaration of `calypso_sim_init'
apps/simtest/main.c:243: error: conflicting types for 'calypso_sim_init'
include/calypso/sim.h:184: error: previous declaration of 'calypso_sim_init' was here
apps/simtest/main.c:243: error: conflicting types for 'calypso_sim_init'
include/calypso/sim.h:184: error: previous declaration of 'calypso_sim_init' was here
apps/simtest/main.c:243: warning: data definition has no type or storage class
apps/simtest/main.c:246: error: parse error before string constant
apps/simtest/main.c:246: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:246: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:246: warning: data definition has no type or storage class
apps/simtest/main.c:247: error: parse error before numeric constant
apps/simtest/main.c:248: warning: type defaults to `int' in declaration of `atrLength'
apps/simtest/main.c:248: error: conflicting types for 'atrLength'
apps/simtest/main.c:228: error: previous definition of 'atrLength' was here
apps/simtest/main.c:248: error: initializer element is not constant
apps/simtest/main.c:248: warning: data definition has no type or storage class
apps/simtest/main.c:249: warning: type defaults to `int' in declaration of `myHexdump'
apps/simtest/main.c:249: warning: parameter names (without types) in function declaration
apps/simtest/main.c:249: error: conflicting types for 'myHexdump'
apps/simtest/main.c:51: error: previous definition of 'myHexdump' was here
apps/simtest/main.c:249: warning: data definition has no type or storage class
apps/simtest/main.c:252: error: parse error before string constant
apps/simtest/main.c:252: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:252: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:252: warning: data definition has no type or storage class
apps/simtest/main.c:253: error: parse error before numeric constant
apps/simtest/main.c:254: warning: type defaults to `int' in declaration of `atrLength'
apps/simtest/main.c:254: error: redefinition of 'atrLength'
apps/simtest/main.c:248: error: previous definition of 'atrLength' was here
apps/simtest/main.c:254: error: redefinition of 'atrLength'
apps/simtest/main.c:248: error: previous definition of 'atrLength' was here
apps/simtest/main.c:254: error: initializer element is not constant
apps/simtest/main.c:254: warning: data definition has no type or storage class
apps/simtest/main.c:255: warning: type defaults to `int' in declaration of `myHexdump'
apps/simtest/main.c:255: warning: parameter names (without types) in function declaration
apps/simtest/main.c:255: warning: redundant redeclaration of 'myHexdump'
apps/simtest/main.c:249: warning: previous declaration of 'myHexdump' was here
apps/simtest/main.c:255: warning: data definition has no type or storage class
apps/simtest/main.c:259: warning: type defaults to `int' in declaration of `testDataBody'
apps/simtest/main.c:259: error: conflicting types for 'testDataBody'
apps/simtest/main.c:222: error: previous declaration of 'testDataBody' was here
apps/simtest/main.c:259: error: invalid initializer
apps/simtest/main.c:259: warning: data definition has no type or storage class
apps/simtest/main.c:260: warning: type defaults to `int' in declaration of `testDataBody'
apps/simtest/main.c:260: error: conflicting types for 'testDataBody'
apps/simtest/main.c:259: error: previous definition of 'testDataBody' was here
apps/simtest/main.c:260: error: conflicting types for 'testDataBody'
apps/simtest/main.c:259: error: previous definition of 'testDataBody' was here
apps/simtest/main.c:260: error: invalid initializer
apps/simtest/main.c:260: warning: data definition has no type or storage class
apps/simtest/main.c:261: error: parse error before numeric constant
apps/simtest/main.c:261: warning: type defaults to `int' in declaration of `calypso_sim_transceive'
apps/simtest/main.c:261: error: conflicting types for 'calypso_sim_transceive'
apps/simtest/main.c:261: note: an argument type that has a default promotion can't match an empty parameter name list declaration
include/calypso/sim.h:175: error: previous declaration of 'calypso_sim_transceive' was here
apps/simtest/main.c:261: error: conflicting types for 'calypso_sim_transceive'
apps/simtest/main.c:261: note: an argument type that has a default promotion can't match an empty parameter name list declaration
include/calypso/sim.h:175: error: previous declaration of 'calypso_sim_transceive' was here
apps/simtest/main.c:261: warning: data definition has no type or storage class
apps/simtest/main.c:262: error: parse error before numeric constant
apps/simtest/main.c:262: warning: type defaults to `int' in declaration of `calypso_sim_transceive'
apps/simtest/main.c:262: warning: redundant redeclaration of 'calypso_sim_transceive'
apps/simtest/main.c:261: warning: previous declaration of 'calypso_sim_transceive' was here
apps/simtest/main.c:262: warning: data definition has no type or storage class
apps/simtest/main.c:263: error: parse error before numeric constant
apps/simtest/main.c:263: warning: type defaults to `int' in declaration of `myHexdump'
apps/simtest/main.c:263: warning: redundant redeclaration of 'myHexdump'
apps/simtest/main.c:255: warning: previous declaration of 'myHexdump' was here
apps/simtest/main.c:263: warning: data definition has no type or storage class
apps/simtest/main.c:265: error: parse error before string constant
apps/simtest/main.c:265: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:265: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:265: warning: data definition has no type or storage class
apps/simtest/main.c:267: error: parse error before string constant
apps/simtest/main.c:267: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:267: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:267: warning: data definition has no type or storage class
apps/simtest/main.c:268: error: parse error before string constant
apps/simtest/main.c:270: error: parse error before string constant
apps/simtest/main.c:270: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:270: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:270: warning: data definition has no type or storage class
apps/simtest/main.c:271: error: parse error before string constant
apps/simtest/main.c:273: error: parse error before string constant
apps/simtest/main.c:273: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:273: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:273: warning: data definition has no type or storage class
apps/simtest/main.c:274: error: parse error before string constant
apps/simtest/main.c:276: error: parse error before string constant
apps/simtest/main.c:276: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:276: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:276: warning: data definition has no type or storage class
apps/simtest/main.c:277: error: parse error before string constant
apps/simtest/main.c:279: error: parse error before string constant
apps/simtest/main.c:279: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:279: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:279: warning: data definition has no type or storage class
apps/simtest/main.c:280: error: parse error before string constant
apps/simtest/main.c:282: error: parse error before numeric constant
apps/simtest/main.c:283: error: parse error before string constant
apps/simtest/main.c:283: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:283: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:283: warning: data definition has no type or storage class
apps/simtest/main.c:284: error: parse error before string constant
apps/simtest/main.c:285: error: parse error before string constant
apps/simtest/main.c:285: warning: type defaults to `int' in declaration of `printf'
apps/simtest/main.c:285: error: conflicting types for 'printf'
apps/simtest/main.c:285: note: a parameter list with an ellipsis can't match an empty parameter name list declaration
apps/simtest/main.c:285: error: conflicting types for 'printf'
apps/simtest/main.c:285: note: a parameter list with an ellipsis can't match an empty parameter name list declaration
apps/simtest/main.c:285: warning: data definition has no type or storage class
apps/simtest/main.c:286: error: parse error before numeric constant
apps/simtest/main.c:286: warning: type defaults to `int' in declaration of `myHexdump'
apps/simtest/main.c:286: warning: redundant redeclaration of 'myHexdump'
apps/simtest/main.c:263: warning: previous declaration of 'myHexdump' was here
apps/simtest/main.c:286: warning: data definition has no type or storage class
apps/simtest/main.c:288: error: parse error before numeric constant
apps/simtest/main.c:289: error: parse error before string constant
apps/simtest/main.c:289: warning: type defaults to `int' in declaration of `memcpy'
apps/simtest/main.c:289: error: conflicting types for 'memcpy'
apps/simtest/main.c:289: error: conflicting types for 'memcpy'
apps/simtest/main.c:289: warning: data definition has no type or storage class
apps/simtest/main.c:290: error: parse error before string constant
apps/simtest/main.c:290: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:290: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:290: warning: data definition has no type or storage class
apps/simtest/main.c:291: error: parse error before string constant
apps/simtest/main.c:292: error: parse error before string constant
apps/simtest/main.c:292: warning: type defaults to `int' in declaration of `printf'
apps/simtest/main.c:292: warning: redundant redeclaration of 'printf'
apps/simtest/main.c:285: warning: previous declaration of 'printf' was here
apps/simtest/main.c:292: warning: data definition has no type or storage class
apps/simtest/main.c:293: error: parse error before numeric constant
apps/simtest/main.c:293: warning: type defaults to `int' in declaration of `myHexdump'
apps/simtest/main.c:293: warning: redundant redeclaration of 'myHexdump'
apps/simtest/main.c:286: warning: previous declaration of 'myHexdump' was here
apps/simtest/main.c:293: warning: data definition has no type or storage class
apps/simtest/main.c:295: error: parse error before numeric constant
apps/simtest/main.c:295: warning: type defaults to `int' in declaration of `delay_ms'
apps/simtest/main.c:295: error: conflicting types for 'delay_ms'
apps/simtest/main.c:207: error: previous definition of 'delay_ms' was here
apps/simtest/main.c:295: warning: data definition has no type or storage class
apps/simtest/main.c:297: warning: type defaults to `int' in declaration of `calypso_sim_powerdown'
apps/simtest/main.c:297: error: conflicting types for 'calypso_sim_powerdown'
include/calypso/sim.h:161: error: previous declaration of 'calypso_sim_powerdown' was here
apps/simtest/main.c:297: error: conflicting types for 'calypso_sim_powerdown'
include/calypso/sim.h:161: error: previous declaration of 'calypso_sim_powerdown' was here
apps/simtest/main.c:297: warning: data definition has no type or storage class
apps/simtest/main.c:299: error: parse error before string constant
apps/simtest/main.c:299: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:299: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:299: warning: data definition has no type or storage class
apps/simtest/main.c: In function `console_rx_cb':
apps/simtest/main.c:311: warning: `return' with no value, in function returning non-void
apps/simtest/main.c: In function `main':
apps/simtest/main.c:350: warning: passing arg 2 of `sercomm_register_rx_cb' from incompatible pointer type
apps/simtest/main.c:352: warning: implicit declaration of function `do_sim_test'
apps/simtest/main.c:352: warning: nested extern declaration of `do_sim_test'
apps/simtest/main.c: At top level:
apps/simtest/main.c:51: warning: 'myHexdump' defined but not used
make[1]: *** [apps/simtest/main.o] Error 1
make[1]: Leaving directory `/root/install/osmocom-bb/src/target/firmware'
make: *** [firmware] Error 2


Any hints are appreciated.
Thanks,
John

P.S. After telnetting to osmocon and running enable, how do I configure it to use my sim? I know I'm supposed to add "sim reader" to
my osmocom.cfg, but I'm not sure where to add it or whether I have to change anything else in that file.


--- On Sat, 1/15/11, quem tu quiseres <quemtuquiseres1 at yahoo.com> wrote:

> From: quem tu quiseres <quemtuquiseres1 at yahoo.com>
> Subject: Re: Problem compiling OsmocomBB on BT4 RC2
> To: "Stephan Meier" <stephan.meier at unitybox.de>
> Cc: baseband-devel at lists.osmocom.org
> Date: Saturday, January 15, 2011, 5:19 AM
> Thanks for your help Stephan.
> I had libtool installed already but for some reason it
> wasn't working well in 
> the BT4 install.
> 
> After much frustration I ended up doing a fresh ubuntu
> install on virtualbox and 
> ran into other problems that others may experience if they
> try this route.
> Basically my problem has to do with the recognition of the
> USB/serial prolific 
> cable by the guest OS (ubuntu). If you experience this
> issue too I recommend a 
> reboot of both host and guest with the cable hooked up (and
> previously installed 
> on your host). After much head scratching a good 'ole
> reboot did the trick.
> 
> Now I can finally talk to my C115 and can't wait to to
> explore the different 
> tools.
> Anyone have any recommendations on where to start, what
> apps to try first, 
> guides, etc (besides the wiki)?
> 
> Thanks again,
> John
> 
> P.S. I gather that Sylvain's code to "strip" the encryption
> from the stream 
> passed by the DSP isn't available. Are there any plans to
> share that too?
> 
> 
> 
> 
> ----- Original Message ----
> From: Stephan Meier <stephan.meier at unitybox.de>
> To: quem tu quiseres <quemtuquiseres1 at yahoo.com>
> Cc: baseband-devel at lists.osmocom.org
> Sent: Fri, January 14, 2011 9:52:42 PM
> Subject: Re: Problem compiling OsmocomBB on BT4 RC2
> 
> Hi,
> 
> if you didn't install "libtool" (apt-get install libtool),
> you'll get
> this error if you try to compile the source for the second
> time.
> Install libtool, clean up your source tree (delete the temp
> files
> generated by the autotools; cloning again may be easier for
> you) and try
> again.
> 
> Cheers,
> ? ? Stephan
> 
> On 01/14/2011 01:53 PM, quem tu quiseres wrote:
> > Hi,
> >
> > I just started playing around with this great project
> and am ashamed to say I'm 
> >
> > stumped with an annoying error when compiling.
> > I'm compiling on a Backtrack 4 RC2 (*buntu based
> distro) and that may be why 
> >I'm 
> >
> > having problems.
> > Basically I downloaded the proper packages as per the
> instructions on the wiki, 
> >
> > exported the PATH and all that, but when I run make I
> get this error:
> >
> > cd shared/libosmocore/build-target &&
> ../configure \
> >? ? ? ? ? ? ? ?
> ? ? ? ???--host=arm-elf-linux
> --disable-vty 
> > --enable-panic-infloop \
> >? ? ? ? ? ? ? ?
> ? ? ? ???--disable-shared
> --disable-talloc --disable-tests \
> >? ? ? ? ? ? ?
> ???CC="arm-elf-gcc" CFLAGS="-Os
> -ffunction-sections 
> > -I/root/GSM/osmocom-bb/src/target/firmware/include"
> > configure: WARNING: If you wanted to set the --build
> type, don't use --host.
> >? ???If a cross compiler is
> detected then cross compile mode will be used.
> > configure: error: cannot find install-sh or install.sh
> in ".." "../.." 
> > "../../.."
> > make: *** [shared/libosmocore/build-target/Makefile]
> Error 1
> >
> >
> > Attached is my config.log and you can see the PATH are
> there.
> >
> > The error can be seen on this line in the log
> "configure:1766: error: cannot 
> > find install-sh or install.sh in ".." "../.."
> "../../.."
> >
> >
> > Now i've checked to see if I have autoconf and
> automake installed (I do, I have 
> >
> > autoconf 2.61 and automake 1.10) since my searches on
> the internet seem to 
> > indicate that maybe the problem.
> >
> > Now I usually do all my own leg work and I read and
> read before asking 
> > questions, but I'm afraid I can't resolve this on my
> own. Before I spend 
> >another 
> >
> > afternoon searching for the solution, I remembered to
> ask here.
> >
> > Anyone have any hints on what I'm doing wrong? Do I
> need different automake or 
> 
> > autoconf versions?
> >
> > Thanks and keep up the great work. It's been
> fascinating to watch the evolution 
> >
> > of GSM hacking these last few years.

> >
> >
> >
> >? ? ? 
> 
> 
> ? ? ? 
> 
> 


      



From holger at freyther.de  Mon Jan 17 16:26:38 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Mon, 17 Jan 2011 17:26:38 +0100
Subject: Problem compiling OsmocomBB on BT4 RC2
In-Reply-To: <300674.90517.qm@web39309.mail.mud.yahoo.com>
References: <300674.90517.qm@web39309.mail.mud.yahoo.com>
Message-ID: <4D346DBE.4030207@freyther.de>

On 01/17/2011 05:20 PM, quem tu quiseres wrote:
> Hi again,
> 
> In case anyone was wondering, I had libtool installed but for some reason it wasn't working right when compiling so I reinstalled it, deleted the osmocom branch and started over from scratch. This time it worked without a problem and i managed to get layer21 up and running on my C115. So if you get similar error messages I recommend deleting and starting over from scratch.
> Now I tried to play around with sylvain's testing branch and I'm getting compile errors. I know this is a bit long to post here but maybe someone here knows what these errors are all about. You can see that the errors begin with the simtest app:
> 
> rm-elf-gcc -mcpu=arm7tdmi -Iinclude/ -I../../../include -I../../shared/libosmocore/include -Wall -Wextra -Wcast-align -Wimplicit -Wunused -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wnested-externs -Wbad-function-cast -Wsign-compare -Waggregate-return -Os -ffunction-sections -gdwarf-2 -DGIT_REVISION=\"osmocon_v0.0.0-756-g999254a-modified\" -DCONFIG_TX_ENABLE -DCONFIG_FLASH_WRITE -Wa,-adhlns=apps/simtest/main.lst -c -o apps/simtest/main.o apps/simtest/main.c
> apps/simtest/main.c:161: error: parse error before '<<' token
> apps/simtest/main.c:168: error: parse error before numeric constant



this is not C++... so you have a merge error... on the merge you did... fix
the merge error...



From steve at steve-m.de  Mon Jan 17 16:35:27 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Mon, 17 Jan 2011 17:35:27 +0100
Subject: Problem compiling OsmocomBB on BT4 RC2
In-Reply-To: <300674.90517.qm@web39309.mail.mud.yahoo.com>
References: <300674.90517.qm@web39309.mail.mud.yahoo.com>
Message-ID: <4D346FCF.9040509@steve-m.de>

Hi,

this is because of the simtest-app in sylvain/testing being currently 
broken. Simply remove it from the "APPLICATIONS?="-line in the firmware 
Makefile (src/target/firmware).

Regards,
Steve



From 246tnt at gmail.com  Mon Jan 17 16:43:16 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Mon, 17 Jan 2011 17:43:16 +0100
Subject: Problem compiling OsmocomBB on BT4 RC2
In-Reply-To: <4D346FCF.9040509@steve-m.de>
References: <300674.90517.qm@web39309.mail.mud.yahoo.com>
	<4D346FCF.9040509@steve-m.de>
Message-ID: <AANLkTikh2+HWE2j1qfTdCewj7Da_NJjACKJ22GsUa=Zy@mail.gmail.com>

We should just stop giving answer ...

It's like a "test" ... It's an experimental branch. if you can't
compile it you shouldn't be running it in the first place.


    Sylvain



From quemtuquiseres1 at yahoo.com  Mon Jan 17 17:07:56 2011
From: quemtuquiseres1 at yahoo.com (quem tu quiseres)
Date: Mon, 17 Jan 2011 09:07:56 -0800 (PST)
Subject: Problem compiling OsmocomBB on BT4 RC2
In-Reply-To: <AANLkTikh2+HWE2j1qfTdCewj7Da_NJjACKJ22GsUa=Zy@mail.gmail.com>
Message-ID: <608570.42423.qm@web39308.mail.mud.yahoo.com>

Easy there. I realize it's only a test and I did search the list before asking.
While I'm a newbie here I am learning and I did manage to compile it and have it running already and am having fun watching the broadcast traffic go by. Slowly I'm starting to dig deeper and understand it better.
And I do appreciate all the work you guys have been doing for years now and your willingness to share and help out others.

If we don't start exploring, make mistakes and ask silly questions how will we ever progress? I remember over 10 years ago getting similar reactions when I first started out trying to clone my SIM card and everyone said it was impossible and/or the network would never allow 2 identical SIMs to be connected at the same time. Well they were wrong because I managed to clone my SIM onto a gold wafer card and I was able to register both at the same time (although only the latest phone to register would actually receive calls, etc.).

Anyway, to make a long story short, although we may be newbies in GSM and osmocom, and many maybe come here to find a click and record script to listen to GSM (because that's what they read in the silly media), many of us are actually here trying to learn and appreciate some help since it's hard to find any thorough documentation.

Thanks again,
John

--- On Mon, 1/17/11, Sylvain Munaut <246tnt at gmail.com> wrote:

> From: Sylvain Munaut <246tnt at gmail.com>
> Subject: Re: Problem compiling OsmocomBB on BT4 RC2
> To: "Steve Markgraf" <steve at steve-m.de>
> Cc: baseband-devel at lists.osmocom.org, "quem tu quiseres" <quemtuquiseres1 at yahoo.com>
> Date: Monday, January 17, 2011, 8:43 AM
> We should just stop giving answer
> ...
> 
> It's like a "test" ... It's an experimental branch. if you
> can't
> compile it you shouldn't be running it in the first place.
> 
> 
> ? ? Sylvain
> 
> 


      



From 246tnt at gmail.com  Mon Jan 17 17:21:35 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Mon, 17 Jan 2011 18:21:35 +0100
Subject: Problem compiling OsmocomBB on BT4 RC2
In-Reply-To: <608570.42423.qm@web39308.mail.mud.yahoo.com>
References: <AANLkTikh2+HWE2j1qfTdCewj7Da_NJjACKJ22GsUa=Zy@mail.gmail.com>
	<608570.42423.qm@web39308.mail.mud.yahoo.com>
Message-ID: <AANLkTinbA=uoOFmC9SjGFPaWcS4OwgbGjBQAFvgkSgVi@mail.gmail.com>

> Easy there. I realize it's only a test and I did search the list before asking.

Well, you obviously didn't do THE FIRST THING you should have: open
the damn file that failed !
It should then have become obvious where the problem was. (and if it
wasn't you've got more serious problems ...)

I have nothing against GSM newbies, but before asking I think you always should:

 - Check the Wiki
 - Check the Mailing list
 - Just plain google for it
 - Try to fix it yourself for at least a few hours
 - Read the relevant specifications / schematics / whatever doc may be
applicable

(the two last items are not applicable to all questions obviously)

And if it's a build error, then you should even try harder to fix it
yourself because you should just know how all theses things work
already ...

And only if all the above failed, then ask on the ml or IRC.


Don't take it personally, but lately all questions on IRC and the ML
have mostly been around:
 - Building
 - Serial cable
 - Finding phones on ebay

All things you really should be able to solve by yourself without
asking ... all the info is out there, and frankly it's getting
annoying.


Cheers,

    Sylvain



From squalyl at gmail.com  Tue Jan 18 09:28:47 2011
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Tue, 18 Jan 2011 10:28:47 +0100
Subject: Problem compiling OsmocomBB on BT4 RC2
In-Reply-To: <AANLkTinbA=uoOFmC9SjGFPaWcS4OwgbGjBQAFvgkSgVi@mail.gmail.com>
References: <AANLkTikh2+HWE2j1qfTdCewj7Da_NJjACKJ22GsUa=Zy@mail.gmail.com>
	<608570.42423.qm@web39308.mail.mud.yahoo.com>
	<AANLkTinbA=uoOFmC9SjGFPaWcS4OwgbGjBQAFvgkSgVi@mail.gmail.com>
Message-ID: <AANLkTinx9iWWXKZtGDYEVGWWg2ekfb-YANnPk2z0PLcA@mail.gmail.com>

Hi,

what about a baseband-users mailing list to keep this one free of the 'git'
and 'make' help requests that keep coming?

Sebastien

On Mon, Jan 17, 2011 at 6:21 PM, Sylvain Munaut <246tnt at gmail.com> wrote:

> > Easy there. I realize it's only a test and I did search the list before
> asking.
>
> Well, you obviously didn't do THE FIRST THING you should have: open
> the damn file that failed !
> It should then have become obvious where the problem was. (and if it
> wasn't you've got more serious problems ...)
>
> I have nothing against GSM newbies, but before asking I think you always
> should:
>
>  - Check the Wiki
>  - Check the Mailing list
>  - Just plain google for it
>  - Try to fix it yourself for at least a few hours
>  - Read the relevant specifications / schematics / whatever doc may be
> applicable
>
> (the two last items are not applicable to all questions obviously)
>
> And if it's a build error, then you should even try harder to fix it
> yourself because you should just know how all theses things work
> already ...
>
> And only if all the above failed, then ask on the ml or IRC.
>
>
> Don't take it personally, but lately all questions on IRC and the ML
> have mostly been around:
>  - Building
>  - Serial cable
>  - Finding phones on ebay
>
> All things you really should be able to solve by yourself without
> asking ... all the info is out there, and frankly it's getting
> annoying.
>
>
> Cheers,
>
>    Sylvain
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110118/7b62826d/attachment.htm>

From peter at stuge.se  Tue Jan 18 09:41:29 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 18 Jan 2011 10:41:29 +0100
Subject: Problem compiling OsmocomBB on BT4 RC2
In-Reply-To: <AANLkTinx9iWWXKZtGDYEVGWWg2ekfb-YANnPk2z0PLcA@mail.gmail.com>
References: <AANLkTikh2+HWE2j1qfTdCewj7Da_NJjACKJ22GsUa=Zy@mail.gmail.com>
	<608570.42423.qm@web39308.mail.mud.yahoo.com>
	<AANLkTinbA=uoOFmC9SjGFPaWcS4OwgbGjBQAFvgkSgVi@mail.gmail.com>
	<AANLkTinx9iWWXKZtGDYEVGWWg2ekfb-YANnPk2z0PLcA@mail.gmail.com>
Message-ID: <20110118094129.1154.qmail@stuge.se>

S?bastien Lorquet wrote:
> what about a baseband-users mailing list to keep this one free of
> the 'git' and 'make' help requests that keep coming?

I think that's a really good idea!


//Peter



From md at gonium.net  Tue Jan 18 09:45:11 2011
From: md at gonium.net (Mathias Dalheimer)
Date: Tue, 18 Jan 2011 10:45:11 +0100
Subject: Problem compiling OsmocomBB on BT4 RC2
In-Reply-To: <20110118094129.1154.qmail@stuge.se>
References: <AANLkTikh2+HWE2j1qfTdCewj7Da_NJjACKJ22GsUa=Zy@mail.gmail.com>	<608570.42423.qm@web39308.mail.mud.yahoo.com>	<AANLkTinbA=uoOFmC9SjGFPaWcS4OwgbGjBQAFvgkSgVi@mail.gmail.com>	<AANLkTinx9iWWXKZtGDYEVGWWg2ekfb-YANnPk2z0PLcA@mail.gmail.com>
	<20110118094129.1154.qmail@stuge.se>
Message-ID: <4D356127.9050008@gonium.net>

Peter Stuge wrote:
> S?bastien Lorquet wrote:
>> what about a baseband-users mailing list to keep this one free of
>> the 'git' and 'make' help requests that keep coming?
> 
> I think that's a really good idea!

+1

-Mathias



From laforge at gnumonks.org  Tue Jan 18 09:56:29 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 18 Jan 2011 10:56:29 +0100
Subject: splitting the list into user and developer list
In-Reply-To: <AANLkTinx9iWWXKZtGDYEVGWWg2ekfb-YANnPk2z0PLcA@mail.gmail.com>
References: <AANLkTikh2+HWE2j1qfTdCewj7Da_NJjACKJ22GsUa=Zy@mail.gmail.com>
	<608570.42423.qm@web39308.mail.mud.yahoo.com>
	<AANLkTinbA=uoOFmC9SjGFPaWcS4OwgbGjBQAFvgkSgVi@mail.gmail.com>
	<AANLkTinx9iWWXKZtGDYEVGWWg2ekfb-YANnPk2z0PLcA@mail.gmail.com>
Message-ID: <20110118095629.GE14829@prithivi.gnumonks.org>

Hi Sebastien,

On Tue, Jan 18, 2011 at 10:28:47AM +0100, S?bastien Lorquet wrote:
 
> what about a baseband-users mailing list to keep this one free of the 'git'
> and 'make' help requests that keep coming?

I think the traffic on this list is not that high, and we should avoid
fragmenting the number of lists.  I did that with some projects in the past,
and didn't make particularly good experiences with it.

My suggestion would be for Sylvain, Andreas, Steve, myself and others to simply
refrain from answering the same question over and over again.  Either other
people from the community will respond to those kind of questions, or the
original poster may consider reading the archive if he doesn't get any
response.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From dario.lombardo at libero.it  Mon Jan 17 17:04:53 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Mon, 17 Jan 2011 18:04:53 +0100
Subject: Problem compiling OsmocomBB on BT4 RC2
In-Reply-To: <300674.90517.qm@web39309.mail.mud.yahoo.com>
References: <300674.90517.qm@web39309.mail.mud.yahoo.com>
Message-ID: <4D3476B5.9030008@libero.it>



On 01/17/2011 05:20 PM, quem tu quiseres wrote:
> Any hints are appreciated.
> Thanks,
> John
The "dirty and easy" way: delete lines with >>>>> or <<<< (they are old 
diffs) and comment the targets that don't compile.
Base apps work this way.
Anyway Sylvain is right: a testing branch isn't expected to compile as 
the trunk should :).



From sweisman at pobox.com  Fri Jan 14 13:39:23 2011
From: sweisman at pobox.com (Scott Weisman)
Date: Fri, 14 Jan 2011 15:39:23 +0200
Subject: open cell phone hardware questions
Message-ID: <AANLkTimtCw3ayfJ79eUQDFg+y+0on1BJjywB6L9-ym68@mail.gmail.com>

Hi everyone. I'm admittedly more a lurker than an active participant in this
project. I find it very fascinating and regard its objectives as important.

I recently watched several of the C3 presentations, from this and previous
years. Having open, documented hardware and software seems to be an
important goal in itself. Just knowing about all the potential weaknesses in
the software stacks of most phones, as well as hidden "features" like SMS
messages that could, theoretically, do things like remotely enable the phone
mic, among other things (things that are certainly technically possible, and
also due to the closed nature of the software, completely unknown) are of
grave concern to me.

Now, given that the supported phone hardware is old and not reliably
available, I was wondering if anyone knows if the Calypso and other chips in
these old phones are still available for new designs? How much interest
would there be, say, in an open, but VERY SIMPLE, actual phone? Kind of like
the Pandora project, but without the ambition to make the most advanced
portable game player possible.

The Osmocom software would then be very easily portable to such a device.
Given the seemingly widespread interest and enthusiasm for the Osmocom,
OpenBTS, and OpenBSC projects, a real, genuinely open phone (not a
pseudo-open phone like the FreeRunner) might possibly have enough interest,
and be buildable for a low-enough cost, to merit further discussion.

Anyone want to discuss this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110114/c985c06c/attachment.htm>

From steve at steve-m.de  Fri Jan 14 14:23:42 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Fri, 14 Jan 2011 15:23:42 +0100
Subject: open cell phone hardware questions
In-Reply-To: <AANLkTimtCw3ayfJ79eUQDFg+y+0on1BJjywB6L9-ym68@mail.gmail.com>
References: <AANLkTimtCw3ayfJ79eUQDFg+y+0on1BJjywB6L9-ym68@mail.gmail.com>
Message-ID: <4D305C6E.3090509@steve-m.de>

Hi,

just to reflect my own thoughts on this topic:

On 14.01.2011 14:39, Scott Weisman wrote:

> Now, given that the supported phone hardware is old and not reliably
> available, I was wondering if anyone knows if the Calypso and other
> chips in these old phones are still available for new designs? How much
> interest would there be, say, in an open, but VERY SIMPLE, actual phone?
> Kind of like the Pandora project, but without the ambition to make the
> most advanced portable game player possible.

This is more or the less the GSM Devel-Board idea [1] that Harald wanted 
to pursue initially, with the difference that it would have used a 
custom DSP and not the Calypso. But even if you don't take in account 
the time and money it takes to do a proper pcb- and especially 
RF-design, this is definitely something you don't want to do with the 
Calypso (which is EOL and not available for new designs, although you 
might get it still in the semiconductor grey-market).

But what would be the benefit of all this? The Compal-phones are still 
available in huge quantities (see aliexpress.com for example, new 
Motorola C118 for $19.79 including world-wide shipping). You surely 
won't beat that price with your hardware.
And it still isn't really 'open', since you have e.g. the proprietary 
DSP code.

It might make a bit more sense with MediaTek baseband chips (once 
supported) if you want to do something out-of-spec with them, but even 
there you have thousands of different phones readily available.

Just my 2 cents...

Regards,
Steve

[1] http://bb.osmocom.org/trac/wiki/GsmDevelBoard



From laforge at gnumonks.org  Fri Jan 14 19:37:06 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 14 Jan 2011 20:37:06 +0100
Subject: A hardware design (was Re: open cell phone hardware questions)
In-Reply-To: <AANLkTimtCw3ayfJ79eUQDFg+y+0on1BJjywB6L9-ym68@mail.gmail.com>
References: <AANLkTimtCw3ayfJ79eUQDFg+y+0on1BJjywB6L9-ym68@mail.gmail.com>
Message-ID: <20110114193706.GD20603@prithivi.gnumonks.org>

Dear Scott,

On Fri, Jan 14, 2011 at 03:39:23PM +0200, Scott Weisman wrote:
 
> I was wondering if anyone knows if the Calypso and other chips in
> these old phones are still available for new designs? 

Not from TI, it is end of life for a long time.  However, you can certainly buy
the Calypso/Iota/Rita from the 'grey market', i.e. the various surplus
semiconductor traders in Asia.

At least one year ago when I last inquired, I could have easily bought
something like 10,000 of those old chipsets.

The biggest challenge is to find all the other required parts, like SAW filters
with the right impedance and mechanical footprint, and find a stable source of
them where you don't have to change your PCB layout every time you produce
another batch of the phones.

We were considering doing something like this (custom hardware) using the
hardware design of the GSM modem of the Freerunner as a basis.  However, when
we found that you could still buy the Motorola/Compal phones in batches of
thousands one year ago, we decided not to pursue down that road.

Doing a hardware design of this complexity, and building it, including
production testing and calibration is not something you are likely to do as
a one or two-man show in your spare time (which OsmocomBB was a year ago).

Also, if you actually ship a device consisting of hardware + software, you
easily run into regulatory issues like the RT&TTE directive in the EU, since
suddenly you're now selling an end-user consumer device and thus have to comply
with regulatory requirements.

Just distributing software is not falling under that directive, and thus
no certification / regulatory requirement is needed.  Same goes for measurement/lab
equipment like the USRP.

> How much interest would there be, say, in an open, but VERY SIMPLE, actual
> phone? 

Definitely by far not enough interest to ever justify the many man-weeks and
months spent in doing a hardware design, writing production testing software,
getting the tooling done for the plastics, etc.

What I find much more valuable is to put effort into porting OsmocomBB to the
Mediatek MTK62xx chipsets.  There are hundreds of millions of phones in the
market already, and close to 100 million new ones are shipping per quarter.

This way, once again the focus is where it should be: creating and improving
the Free Software GSM protocol stack, creating a simple UI on top.

No need to design, test, produce and verify a hardware design from scratch,
worry about mechanical issues, etc.   Plus, you benefit from the fact that
the devices are available at a price to which you will never get (large scale
production), and the hardware design has been verified.

> The Osmocom software would then be very easily portable to such a device.
> Given the seemingly widespread interest and enthusiasm for the Osmocom,
> OpenBTS, and OpenBSC projects, 

I think you may need to re-calibrate your perception.  Please look at the
actual number of people who have contributed to the source code of all those
projects together.  You will find it is very few, and the same names pop
up everywhere.

Growing the user base without growing the developer base is not something I
think we should put in such an enormous effort as running our own hardware
design.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From sweisman at pobox.com  Sat Jan 15 16:12:02 2011
From: sweisman at pobox.com (Scott Weisman)
Date: Sat, 15 Jan 2011 18:12:02 +0200
Subject: A hardware design (was Re: open cell phone hardware questions)
In-Reply-To: <20110114193706.GD20603@prithivi.gnumonks.org>
References: <AANLkTimtCw3ayfJ79eUQDFg+y+0on1BJjywB6L9-ym68@mail.gmail.com>
	<20110114193706.GD20603@prithivi.gnumonks.org>
Message-ID: <AANLkTinDRa+j-2SdkbtvZV6EAp5SZTeASX5YUiQqT+95@mail.gmail.com>

Thanks everyone for the clarification. I didn't realize there were so many
of the Calypso phones still available *new*. I was only aware of eBay and
some obscure Polish auction site. Now that I know they are available in
single quantities from AliExpress, that's a whole different scenario.

With those kinds of quantities, you are all correct that there is no need to
even think about a hardware design.

Thanks for all the feedback and keep up the great work!

Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110115/f5f808f2/attachment.htm>

From azet at azet.org  Fri Jan 14 16:10:11 2011
From: azet at azet.org (Aaron Zauner)
Date: Fri, 14 Jan 2011 17:10:11 +0100
Subject: running voice data/encryption on compal?
Message-ID: <AANLkTim9PymWmxZsGnwBsr=4cGZi-++41x-3o1uuJzOv@mail.gmail.com>

hi,

a while ago i've read that someone managed to have an active phone call over
osmocom for about 20mins.
i woundered if it is theoretically & technically possible to have an active,
serious (thus not a5) encryption running
for voice or data calls on the stack?

thanks in advance & greetings from vienna ;)
azet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110114/4d83ef7a/attachment.htm>

From laforge at gnumonks.org  Fri Jan 14 20:29:28 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 14 Jan 2011 21:29:28 +0100
Subject: running voice data/encryption on compal?
In-Reply-To: <AANLkTim9PymWmxZsGnwBsr=4cGZi-++41x-3o1uuJzOv@mail.gmail.com>
References: <AANLkTim9PymWmxZsGnwBsr=4cGZi-++41x-3o1uuJzOv@mail.gmail.com>
Message-ID: <20110114202928.GA21832@prithivi.gnumonks.org>

Aaron,

the usual problems with end-to-end encryption in GSM come into play:
* as the voice path is not transparent but transcoded any number of times
  in the core network, you cannot simply encrypt the codec frames but gqwill
  have to initiate a CSD ('modem') connection.
* not many networks support it anymore
* calling rates are more expensive
* you immediately leave a visible trail, since nobody else uses CSD

And no, neither is the ARM7 fast enough for any crypto, nor do we implement
CSD at all.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From lists at infosecurity.ch  Fri Jan 14 22:50:04 2011
From: lists at infosecurity.ch (Fabio Pietrosanti (naif))
Date: Fri, 14 Jan 2011 23:50:04 +0100
Subject: running voice data/encryption on compal?
In-Reply-To: <20110114202928.GA21832@prithivi.gnumonks.org>
References: <AANLkTim9PymWmxZsGnwBsr=4cGZi-++41x-3o1uuJzOv@mail.gmail.com>
	<20110114202928.GA21832@prithivi.gnumonks.org>
Message-ID: <4D30D31C.9090709@infosecurity.ch>

On 14/01/11 21.29, Harald Welte wrote:
> Aaron,
>
> the usual problems with end-to-end encryption in GSM come into play:
> * as the voice path is not transparent but transcoded any number of times
>   in the core network, you cannot simply encrypt the codec frames but gqwill
>   have to initiate a CSD ('modem') connection.
Enciphering directly the GSM/AMR codec payload at GSM it's still a cool
hackish idea!

Regarding transcoding it's also to be considered that within the same
operator or at GSM inter-working national level it's much more difficult
that transcoding it's done in the voice path.
Mobile operators tends to avoid transcoding whether possible to reduce
the infrastructural costs associated with media gateway equipments and
directly interconnected mobile operators probably doesn't do much
transcoding.

I asked you a similar question at ph-neutral a couple of years ago and i
remember that there's also an issue related not being able, due to
hardware design of baseband, to control the path between the
encoder/decoder and the transmitter.

So no "hands on" the audio encoded/decoded payload that will get sent to
the network, right?
> * not many networks support it anymore
> * calling rates are more expensive
> * you immediately leave a visible trail, since nobody else uses CSD
>
> And no, neither is the ARM7 fast enough for any crypto, nor do we implement
> CSD at all.

We all would really like to see incredibly efficient DoV (Data over
Voice) modem technologies reaching at least stable 800bit/s to be able
to run a 600bit/s audio codec along with some encryption on top of it.

For military stuff there's a UK university that made a patent for a
1200bit/s DoV with error correction and 0.03% BER over GSM-to-GSM calls
with GSM codec (13kbit/s).
http://personal.ee.surrey.ac.uk/Personal/N.Katugampala/pubs/iee04.pdf

Some other DoV has been done to develop emergency services such as
in-band transmission of information between emergergy services and law
enforcement operators for european esafety project
(www.esafetysupport.org) standardizing in-band modem over GSM and AMR as
3GPP TS 26.267 but that uber-patented technology are not designed to
handle realtime transport bust just signaling of messages.

-naif



From steve at steve-m.de  Fri Jan 14 22:57:41 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Fri, 14 Jan 2011 23:57:41 +0100
Subject: running voice data/encryption on compal?
In-Reply-To: <4D30D31C.9090709@infosecurity.ch>
References: <AANLkTim9PymWmxZsGnwBsr=4cGZi-++41x-3o1uuJzOv@mail.gmail.com>	<20110114202928.GA21832@prithivi.gnumonks.org>
	<4D30D31C.9090709@infosecurity.ch>
Message-ID: <4D30D4E5.4030408@steve-m.de>

Hi,

On 14.01.2011 23:50, Fabio Pietrosanti (naif) wrote:

> So no "hands on" the audio encoded/decoded payload that will get sent to
> the network, right?

One commit says more than thousand words:

http://bb.osmocom.org/trac/changeset/999254a3a6641ea112b48c1eca65599fb9989185/src

Sylvain also has a uncommitted code that allows to fill the uplink TCH 
data, and Andreas has code for connecting this to the LCR.

Regards,
Steve



From lists at infosecurity.ch  Sat Jan 15 20:56:48 2011
From: lists at infosecurity.ch (Fabio Pietrosanti (naif))
Date: Sat, 15 Jan 2011 21:56:48 +0100
Subject: running voice data/encryption on compal?
In-Reply-To: <4D30D4E5.4030408@steve-m.de>
References: <AANLkTim9PymWmxZsGnwBsr=4cGZi-++41x-3o1uuJzOv@mail.gmail.com>	<20110114202928.GA21832@prithivi.gnumonks.org>
	<4D30D31C.9090709@infosecurity.ch> <4D30D4E5.4030408@steve-m.de>
Message-ID: <4D320A10.8070702@infosecurity.ch>

On 14/01/11 23.57, Steve Markgraf wrote:
> One commit says more than thousand words:
>
> http://bb.osmocom.org/trac/changeset/999254a3a6641ea112b48c1eca65599fb9989185/src
>
>
> Sylvain also has a uncommitted code that allows to fill the uplink TCH
> data, and Andreas has code for connecting this to the LCR.
Woah!

I should probably get a couple of phones to play!

It would be interesting to try to get each audio samples incoming and
outgoing and XOR it, to see if other party receive it "as-is", that
would means that no-transcoding happened.

Maybe there are an area of conditions where transcoding doesn't happen,
like within the same operator or within national gsm operators
interconnections.

If that could be confirmed, it would be possible to have a low latency
full-duplex communication data path at 13.3kbit/s (GSM codec) or
12.2kbit (GSM EFR/AMR codec) to be managed such like a serial connection.

On top of a protocol alike HDLC could provide a serial connection over a
GSM voice raw transport

Someone willing to make a try?

-naif



From dw at botanicus.net  Sat Jan 15 23:23:31 2011
From: dw at botanicus.net (David Wilson)
Date: Sat, 15 Jan 2011 23:23:31 +0000
Subject: running voice data/encryption on compal?
In-Reply-To: <4D320A10.8070702@infosecurity.ch>
References: <AANLkTim9PymWmxZsGnwBsr=4cGZi-++41x-3o1uuJzOv@mail.gmail.com>
	<20110114202928.GA21832@prithivi.gnumonks.org>
	<4D30D31C.9090709@infosecurity.ch>
	<4D30D4E5.4030408@steve-m.de> <4D320A10.8070702@infosecurity.ch>
Message-ID: <AANLkTiky=SRB-VKmTpq0FDt+KOzL=P88Rnq3MDrGNyd6@mail.gmail.com>

Hi Fabio,

On 15 January 2011 20:56, Fabio Pietrosanti (naif)
<lists at infosecurity.ch> wrote:
>
> Maybe there are an area of conditions where transcoding doesn't happen,
> like within the same operator or within national gsm operators
> interconnections.
>
> If that could be confirmed, it would be possible to have a low latency
> full-duplex communication data path at 13.3kbit/s (GSM codec) or
> 12.2kbit (GSM EFR/AMR codec) to be managed such like a serial connection.
>
> On top of a protocol alike HDLC could provide a serial connection over a
> GSM voice raw transport
>
> Someone willing to make a try?

Note the L1 channel coding is intimately linked to characteristics of
the codec/connection type, and it's just not as simple as treating the
bits that usually carry codec frames as a serial link. For example
block size and error correction varies by codec and even between
individual frame types within a codec. I believe L2 has no automatic
retransmission on frame error for voice channels, so that must also be
handled.

I'm not suggesting a solution, just pointing out these are not simple
"boxes and arrows" to be freely substituted without detailed knowledge
of the surrounding system.


David



From frank at rosengart.de  Sun Jan 16 12:11:02 2011
From: frank at rosengart.de (Frank Rosengart)
Date: Sun, 16 Jan 2011 13:11:02 +0100
Subject: running voice data/encryption on compal?
In-Reply-To: <4D320A10.8070702@infosecurity.ch>
References: <AANLkTim9PymWmxZsGnwBsr=4cGZi-++41x-3o1uuJzOv@mail.gmail.com>	<20110114202928.GA21832@prithivi.gnumonks.org>	<4D30D31C.9090709@infosecurity.ch>
	<4D30D4E5.4030408@steve-m.de> <4D320A10.8070702@infosecurity.ch>
Message-ID: <4D32E056.3070609@rosengart.de>

You may have a look at
http://www.cryptophone.de/en/background/cryptophone-technology/

They have gone through all the ideas coming up here, but a few years
ago. I there would be any way to use the GSM voice channel for
encrypted, reliable communication, they would have used it.

Frank



From frank at ccc.de  Sun Jan 16 12:38:11 2011
From: frank at ccc.de (Frank Rieger)
Date: Sun, 16 Jan 2011 13:38:11 +0100
Subject: running voice data/encryption on compal?
In-Reply-To: <4D32E056.3070609@rosengart.de>
References: <AANLkTim9PymWmxZsGnwBsr=4cGZi-++41x-3o1uuJzOv@mail.gmail.com>	<20110114202928.GA21832@prithivi.gnumonks.org>	<4D30D31C.9090709@infosecurity.ch>
	<4D30D4E5.4030408@steve-m.de> <4D320A10.8070702@infosecurity.ch>
	<4D32E056.3070609@rosengart.de>
Message-ID: <40DCC39C-A891-4E78-9AB3-FFC5EDFDEF66@ccc.de>

I went and visited the project of Prof. A. Kondoz in Surrey who got the furthest with a DoV modem in the public domain and he explained their modeling and system. Essentially they got up to about 1 Kbit with 2-8% BER on real-world single-operator (!) GSM-networks running AMR full rate. Kondoz has developed a LPC10 variant for codec that could work with that bandwith, as expected sounding like robots talking through rain-drains. His main speciality is voice codecs.

The computational effort for the modem and the codec was in the 1.5 GHz range, so on the verge of being doable on todays mobile hardware. The project did afaik not progress much further cause the students who did it graduated and the funding apparently dried up (or the project was taken over by a .gov contractor for development of a clandestine comms system, depending on which rumor you believe). Performance over multiple operators (read: international calls) was only good enough for slow message transfer (low hundreds of bit/sec), which is not very attractive. 

The crucial trick Kondoz used was to adapt the symbol table for the DOV-modem dynamically to the AMR voice codec codebook changes. If you want to bring that work further, the first step is of course inserting the frames directly into the baseband (this skipping one codec step), then building a feedback loop that passes information on the AMR codec state on the receiving end to the sender, so it can adapt the modem symbol table accordingly. That combined may yield the crucial datarate improvement to make it work accross operators and with better understandability. At CryptoPhone we stopped further research into the project due too high cost and risk of failure (all others I know off canceled as well). 

Let me know when you succeed so we can license the tech, until then we just use IP ;-)

Greetings from Berlin,

Frank Rieger




From wesley.tanner at gmail.com  Sat Jan 15 00:15:16 2011
From: wesley.tanner at gmail.com (Wesley Tanner)
Date: Fri, 14 Jan 2011 16:15:16 -0800
Subject: running voice data/encryption on compal?
In-Reply-To: <4D30D31C.9090709@infosecurity.ch>
References: <AANLkTim9PymWmxZsGnwBsr=4cGZi-++41x-3o1uuJzOv@mail.gmail.com>
	<20110114202928.GA21832@prithivi.gnumonks.org>
	<4D30D31C.9090709@infosecurity.ch>
Message-ID: <AANLkTiniyvVwJmgO-LmfWjR+WTNeBH-L2PYDMKMGVxi6@mail.gmail.com>

Hi all,

This particular problem domain is why I originally became interested in this
project. In fact I just bought a couple C118s and now have them running the
current build as of yesterday.

There has been additional work done in the academic world on
"data-over-voice" the last few years, mainly out of Chinese and Iranian
universities. Some of them claim reliable data rates of 2000 bps or higher
(not including error correction), which is good enough for low data rate
vocoders (e.g. speex). A search on IEEE comes up with a bunch of papers, and
some have fairly detailed design data. Most are optimized for EFR, and some
for AMR. Some claim to be computationally efficient enough for
implementation on modern smart phones.

So far, the modems have been implemented at the audio interface of the
handset, not the raw OTA compressed voice frames. I believe a project such
as this will make it possible to improve these modems by being able to
directly control the content of the traffic frames. At the very least, I
think it will aid in synchronization issues between the end points, and
easier handling of VAD/DTX/CNG.

The problem is made very difficult because of transcoding done within the
network. And, depending on the call, there may be different transcode
operations between end points (or maybe none at all?). Also, the voice frame
parameters are not all protected equally from channel errors. My hope was to
actually start characterizing network transcode behaviors, since I have not
yet found any real data on this. It is possible to do this without access to
the traffic frames, but it makes for more complex test cases.

At any rate it is an interesting problem.

-Wes

On Fri, Jan 14, 2011 at 2:50 PM, Fabio Pietrosanti (naif) <
lists at infosecurity.ch> wrote:

> On 14/01/11 21.29, Harald Welte wrote:
> > Aaron,
> >
> > the usual problems with end-to-end encryption in GSM come into play:
> > * as the voice path is not transparent but transcoded any number of times
> >   in the core network, you cannot simply encrypt the codec frames but
> gqwill
> >   have to initiate a CSD ('modem') connection.
> Enciphering directly the GSM/AMR codec payload at GSM it's still a cool
> hackish idea!
>
> Regarding transcoding it's also to be considered that within the same
> operator or at GSM inter-working national level it's much more difficult
> that transcoding it's done in the voice path.
> Mobile operators tends to avoid transcoding whether possible to reduce
> the infrastructural costs associated with media gateway equipments and
> directly interconnected mobile operators probably doesn't do much
> transcoding.
>
> I asked you a similar question at ph-neutral a couple of years ago and i
> remember that there's also an issue related not being able, due to
> hardware design of baseband, to control the path between the
> encoder/decoder and the transmitter.
>
> So no "hands on" the audio encoded/decoded payload that will get sent to
> the network, right?
> > * not many networks support it anymore
> > * calling rates are more expensive
> > * you immediately leave a visible trail, since nobody else uses CSD
> >
> > And no, neither is the ARM7 fast enough for any crypto, nor do we
> implement
> > CSD at all.
>
> We all would really like to see incredibly efficient DoV (Data over
> Voice) modem technologies reaching at least stable 800bit/s to be able
> to run a 600bit/s audio codec along with some encryption on top of it.
>
> For military stuff there's a UK university that made a patent for a
> 1200bit/s DoV with error correction and 0.03% BER over GSM-to-GSM calls
> with GSM codec (13kbit/s).
> http://personal.ee.surrey.ac.uk/Personal/N.Katugampala/pubs/iee04.pdf
>
> Some other DoV has been done to develop emergency services such as
> in-band transmission of information between emergergy services and law
> enforcement operators for european esafety project
> (www.esafetysupport.org) standardizing in-band modem over GSM and AMR as
> 3GPP TS 26.267 but that uber-patented technology are not designed to
> handle realtime transport bust just signaling of messages.
>
> -naif
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110114/53994ad7/attachment.htm>

From lists at infosecurity.ch  Sat Jan 15 21:33:01 2011
From: lists at infosecurity.ch (Fabio Pietrosanti (naif))
Date: Sat, 15 Jan 2011 22:33:01 +0100
Subject: running voice data/encryption on compal?
In-Reply-To: <AANLkTiniyvVwJmgO-LmfWjR+WTNeBH-L2PYDMKMGVxi6@mail.gmail.com>
References: <AANLkTim9PymWmxZsGnwBsr=4cGZi-++41x-3o1uuJzOv@mail.gmail.com>	<20110114202928.GA21832@prithivi.gnumonks.org>	<4D30D31C.9090709@infosecurity.ch>
	<AANLkTiniyvVwJmgO-LmfWjR+WTNeBH-L2PYDMKMGVxi6@mail.gmail.com>
Message-ID: <4D32128D.4070006@infosecurity.ch>

On 15/01/11 01.15, Wesley Tanner wrote:
> Hi all,
>
> This particular problem domain is why I originally became interested
> in this project. In fact I just bought a couple C118s and now have
> them running the current build as of yesterday.
Wow, that's extremely interesting!

Some time ago i made an extremely no-so-technologically-advanced test.
I got a friend's old us robotics sportster 14.4k modem, connected to an
VoIP ATA, connected to an Asterisk, connected to a GSM VoIP Gateway as
follow:

PC->Serial->Modem->VoIP ATA->Asterisk-> GSM-VoIP-Gateway->GSM Voice
call(4.75-to-13kbit)->Telephony-network-PSTN-modem(64kbit)

Made calls to a PSTN dialup modem and was able in a GSM-to-GSM calls to
get 300bps modem carrier.
But that's very very dirty tests not even entering into DSP specific
issue to make a DoV modem!

> There has been additional work done in the academic world on
> "data-over-voice" the last few years, mainly out of Chinese and
> Iranian universities. Some of them claim reliable data rates of 2000
> bps or higher (not including error correction), which is good enough
> for low data rate vocoders (e.g. speex).
I immagine that in a real world scenario it would be required something
even more ultra-narrowband than speex, like the ones destinated for use
in HF radio/military world would be required.
Something like NATO STANAG 4479(800bit/s) or MELPe (600/1200/2400) or
MELP (1200/2400) or CDMA EVRC-B (800bit/s) or future CODEC2 (that will
support 1200bit/s).

> A search on IEEE comes up with a bunch of papers, and some have fairly
> detailed design data. Most are optimized for EFR, and some for AMR.
> Some claim to be computationally efficient enough for implementation
> on modern smart phones.
Well, but practically on a smartphone how to specify to use GSM EFR
(giving at least 12.2kbit) respect to AMR (that can go down up to
4.75kbit) ?
Having an higher bitrate codec forced would improve the stability and
performance of such as data over voice modem.

> So far, the modems have been implemented at the audio interface of the
> handset, not the raw OTA compressed voice frames. I believe a project
> such as this will make it possible to improve these modems by being
> able to directly control the content of the traffic frames. At the
> very least, I think it will aid in synchronization issues between the
> end points, and easier handling of VAD/DTX/CNG.
>
> The problem is made very difficult because of transcoding done within
> the network. And, depending on the call, there may be different
> transcode operations between end points (or maybe none at all?). Also,
> the voice frame parameters are not all protected equally from channel
> errors. My hope was to actually start characterizing network transcode
> behaviors, since I have not yet found any real data on this. It is
> possible to do this without access to the traffic frames, but it makes
> for more complex test cases.
Well, probably also targeting very reduced rates such as 800bit/s could
improve the ability to works across more transcoding.
Some times ago i spoke with airbiquity that make this aqlink
uber-patented technology that claim to be able to do 800bit/s even over
AMR codec www.airbiquity.com/pdf/productsheets/*aqLink*.pdf .

A 600bit/s audio codec plus some protocol overhead on top of a powerful
DoV modem running at least at 800bit/s would make probably a new way to
make voice encryption over everything that's a voice channel!

A dream! :)

-naif
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110115/a9338f99/attachment.htm>

From azet at azet.org  Sat Jan 15 22:47:48 2011
From: azet at azet.org (Aaron Zauner)
Date: Sat, 15 Jan 2011 23:47:48 +0100
Subject: running voice data/encryption on compal?
In-Reply-To: <4D32128D.4070006@infosecurity.ch>
References: <AANLkTim9PymWmxZsGnwBsr=4cGZi-++41x-3o1uuJzOv@mail.gmail.com>
	<20110114202928.GA21832@prithivi.gnumonks.org>
	<4D30D31C.9090709@infosecurity.ch>
	<AANLkTiniyvVwJmgO-LmfWjR+WTNeBH-L2PYDMKMGVxi6@mail.gmail.com>
	<4D32128D.4070006@infosecurity.ch>
Message-ID: <AANLkTi=-8JF99=b2ZfxybVg77v_asJszOwgkMhgsNeXT@mail.gmail.com>

thanks for the replys!

this is extremly interesting. but i already suspected that ARM7 wouldn't be
fast enough.
(as you probably can tell, im not much into electronics, but working on
it..)

keep going! :)

azet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110115/54baa832/attachment.htm>

From list_mailing at libero.it  Fri Jan 14 17:06:35 2011
From: list_mailing at libero.it (list_mailing at libero.it)
Date: Fri, 14 Jan 2011 18:06:35 +0100 (CET)
Subject: C115 loader.compalram.bin
Message-ID: <30082936.3551511295024795318.JavaMail.defaultUser@defaultHost>

Hello.
I'm trying to load the loader.compalram.bin. 
The behaviour is very strange because sometimes the download is complete and 
successfull, sometimes; in particular, in this case, the download is complete, 
but any ACK is sent back from the mobile phone (see below). 
./osmocon -p /dev/ttyUSB0 -m c123 ../..
/target/firmware/board/compal_e99/loader.compalram.bin
got 2 bytes from modem, data looks like: 2e c8  ..
got 5 bytes from modem, data looks like: 1b f6 02 00 41  ....A
got 1 bytes from modem, data looks like: 01  .
got 1 bytes from modem, data looks like: 40  @
Received PROMPT1 from phone, responding with CMD
read_file(../../target/firmware/board/compal_e99/loader.compalram.bin): 
file_size=21752, hdr_len=4, dnload_len=21759
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: 41  A
got 1 bytes from modem, data looks like: 02  .
got 1 bytes from modem, data looks like: 43  C
Received PROMPT2 from phone, starting download
handle_write(): 4096 bytes (4096/21759)
handle_write(): 4096 bytes (8192/21759)
handle_write(): 4096 bytes (12288/21759)
handle_write(): 4096 bytes (16384/21759)
handle_write(): 4096 bytes (20480/21759)
handle_write(): 1279 bytes (21759/21759)
handle_write(): finished


The target phone is C115. I tried compal_exx and the result is the same :-(

Please, can someone help me to understand the reasons?
Thanks in advance.




From deacon at volny.cz  Sun Jan 16 03:22:55 2011
From: deacon at volny.cz (Tomas Kopsa)
Date: Sun, 16 Jan 2011 04:22:55 +0100
Subject: C115 loader.compalram.bin
In-Reply-To: <30082936.3551511295024795318.JavaMail.defaultUser@defaultHost>
References: <30082936.3551511295024795318.JavaMail.defaultUser@defaultHost>
Message-ID: <4D32648F.10404@volny.cz>

Hello,
I have C115 too and I use '-m c123xor' switch, the phone mostly boots on 
1st button push  (I never reacher full load with '-m c123').

./osmocon -p /dev/ttyUSB0 -m c123xor 
../../target/firmware/board/compal_e88/hello_world.compalram.bin
./osmocon -p /dev/ttyUSB0 -m c123xor 
../../target/firmware/board/compal_e88/loader.compalram.bin
./osmocon -p /dev/ttyUSB0 -m c123xor 
../../target/firmware/board/compal_e88/layer1.compalram.bin

I have FTDI USB<->RS232 + Calypso serial. When load fails (with xor), I 
have a feeling that it helps reconnection cable to the phone.
(I have also Calypso USB cable which I haven't tested yet, will report 
later.)

- Tomas


> Hello.
> I'm trying to load the loader.compalram.bin.
> The behaviour is very strange because sometimes the download is complete and
> successfull, sometimes; in particular, in this case, the download is complete,
> but any ACK is sent back from the mobile phone (see below).
> ./osmocon -p /dev/ttyUSB0 -m c123 ../..
> /target/firmware/board/compal_e99/loader.compalram.bin
> got 2 bytes from modem, data looks like: 2e c8  ..
> got 5 bytes from modem, data looks like: 1b f6 02 00 41  ....A
> got 1 bytes from modem, data looks like: 01  .
> got 1 bytes from modem, data looks like: 40  @
> Received PROMPT1 from phone, responding with CMD
> read_file(../../target/firmware/board/compal_e99/loader.compalram.bin):
> file_size=21752, hdr_len=4, dnload_len=21759
> 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: 41  A
> got 1 bytes from modem, data looks like: 02  .
> got 1 bytes from modem, data looks like: 43  C
> Received PROMPT2 from phone, starting download
> handle_write(): 4096 bytes (4096/21759)
> handle_write(): 4096 bytes (8192/21759)
> handle_write(): 4096 bytes (12288/21759)
> handle_write(): 4096 bytes (16384/21759)
> handle_write(): 4096 bytes (20480/21759)
> handle_write(): 1279 bytes (21759/21759)
> handle_write(): finished
>
>
> The target phone is C115. I tried compal_exx and the result is the same :-(
>
> Please, can someone help me to understand the reasons?
> Thanks in advance.
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110116/8a7be73f/attachment.htm>

From vamposdecampos at gmail.com  Sat Jan 15 17:43:42 2011
From: vamposdecampos at gmail.com (Alex Badea)
Date: Sat, 15 Jan 2011 19:43:42 +0200
Subject: [PATCH libosmocore] gsm 03.41: fix GSM341_MSG_CODE macro argument
Message-ID: <1295113422-17888-1-git-send-email-vamposdecampos@gmail.com>

One usage of the "ms" argument is typoed as "msg".  Fix it to prevent
subtle future failures.  Also paranthesize the macro argument for good
measure.

Signed-off-by: Alex Badea <vamposdecampos at gmail.com>
---
This was found by visual inspection.

 include/osmocore/protocol/gsm_03_41.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/include/osmocore/protocol/gsm_03_41.h b/include/osmocore/protocol/gsm_03_41.h
index 3b1b7c9..54365cb 100644
--- a/include/osmocore/protocol/gsm_03_41.h
+++ b/include/osmocore/protocol/gsm_03_41.h
@@ -40,7 +40,7 @@ struct gsm341_etws_message {
 	uint8_t data[0];
 } __attribute__((packed));
 
-#define GSM341_MSG_CODE(ms) (ms->serial.code_lo | (msg->serial.code_hi << 4))
+#define GSM341_MSG_CODE(ms) ((ms)->serial.code_lo | ((ms)->serial.code_hi << 4))
 
 /* Section 9.3.2.1 - Geographical Scope */
 #define GSM341_GS_CELL_WIDE_IMMED	0
-- 
1.7.0.4




From 246tnt at gmail.com  Sat Jan 15 22:41:49 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Sat, 15 Jan 2011 23:41:49 +0100
Subject: [PATCH libosmocore] gsm 03.41: fix GSM341_MSG_CODE macro argument
In-Reply-To: <1295113422-17888-1-git-send-email-vamposdecampos@gmail.com>
References: <1295113422-17888-1-git-send-email-vamposdecampos@gmail.com>
Message-ID: <AANLkTinccV+xqFPFCMHgXDqYo8j3yQoHqz+iJK1WRp-B@mail.gmail.com>

> One usage of the "ms" argument is typoed as "msg".  Fix it to prevent
> subtle future failures.  Also paranthesize the macro argument for good
> measure.

Merged, thanks.

Cheers,

    Sylvain



From deacon at volny.cz  Mon Jan 17 03:32:38 2011
From: deacon at volny.cz (Tomas Kopsa)
Date: Mon, 17 Jan 2011 04:32:38 +0100
Subject: R: Re: C115 loader.compalram.bin
In-Reply-To: <12961327.3754611295203226842.JavaMail.defaultUser@defaultHost>
References: <12961327.3754611295203226842.JavaMail.defaultUser@defaultHost>
Message-ID: <4D33B856.1080200@volny.cz>

Hi Lia,

I have tested another cable (USB <-> 2,5 jack, speacial for Compal 
phones) - it is the same chip (Prolific) and I am able to load firmware 
too. Although it is the same chip, there is a difference that this one 
makes the osmocon printing those messages instantly when phone is not 
connected:

got 1 bytes from modem, data looks like: f5  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: f5  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: f5  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: fd  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: f5  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: fd  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: ea  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: ea  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: ea  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: ea  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: fd  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: ea

If I connect phone, printing stops. Here is what happened when I tried 
to load firmware without xor (-m c123) and pressed the button:
(This happened every attempt without xor flag)

Received PROMPT2 from phone, starting download
handle_write(): 1087 bytes (1087/50947)
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 :(
got 1 bytes from modem, data looks like: 66  f
got 1 bytes from modem, data looks like: 74  t
got 1 bytes from modem, data looks like: 6d  m
got 1 bytes from modem, data looks like: 74  t
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 6c  l
Received FTMTOOL from phone, ramloader has aborted
got 1 bytes from modem, data looks like: 65  e
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 00  .


If you have USB adapter (I guess you have), you dont need to check 
model, check 'lsusb'

[root at amilo osmocon]# lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
*Bus 002 Device 017: ID 067b:2303 Prolific Technology, Inc. PL2303 
Serial Port*

If you have Prolific, which is very common, I encourage you to use xor 
flag. You can also try to switch on your phone to check if original
firmware boots. I experienced during my early tests, that phone crashed 
(probably SRAM) and it was unable to boot even original fw. In case 
phone is crashed, reconnect battery and it will fix itself.

Here is the ACK after hello world load:

handle_write(): 768 bytes (17919/19787)
handle_write(): 768 bytes (18687/19787)
handle_write(): 768 bytes (19455/19787)
handle_write(): 332 bytes (19787/19787)
handle_write(): finished
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: 41  A
got 1 bytes from modem, data looks like: 03  .
got 1 bytes from modem, data looks like: 42  B
Received DOWNLOAD ACK from phone, your code is running now!


OSMOCOM Hello World (revision osmocon_v0.0.0-754-gb5abcb6-modified)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: efce3b1ce1001255
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
==============================================


Looking forward your response,

Tomas


> Hi Tomas,
>
> thanks for your feedback.
>
> Actually, I've tried both flags (woth/without xor extension), but hte 
> result is the same.
>
> So, in your opinioni, the problem could depend on the cable?
>
> I don't have the cable model now, but I can send you this information 
> Tuesday.
>
> Thanks again.
>
> cheers.
>
> lia
>
>     ----Messaggio originale----
>     Da: deacon at volny.cz
>     Data: 16-gen-2011 4.26
>     A: <list_mailing at libero.it>
>     ubut Ogg: Re: C115 loader.compalram.bin
>
>     Hello,
>     I have C115 too and I use '-m c123xor' switch, the phone mostly
>     boots on 1st button push  (I never reacher full load with '-m c123').
>
>     ./osmocon -p /dev/ttyUSB0 -m c123xor
>     ../../target/firmware/board/compal_e88/hello_world.compalram.bin
>     ./osmocon -p /dev/ttyUSB0 -m c123xor
>     ../../target/firmware/board/compal_e88/loader.compalram.bin
>     ./osmocon -p /dev/ttyUSB0 -m c123xor
>     ../../target/firmware/board/compal_e88/layer1.compalram.bin
>
>     I have FTDI USB<->RS232 + Calypso serial. When load fails (with
>     xor), I have a feeling that it helps reconnection cable to the phone.
>     (I have also Calypso USB cable which I haven't tested yet, will
>     report later.)
>
>     - Tomas
>
>
>>>     Hello.
>>>     I'm trying to load the loader.compalram.bin.
>>>     The behaviour is very strange because sometimes the download is complete and
>>>     successfull, sometimes; in particular, in this case, the download is complete,
>>>     but any ACK is sent back from the mobile phone (see below).
>>>     ./osmocon -p /dev/ttyUSB0 -m c123 ../..
>>>     /target/firmware/board/compal_e99/loader.compalram.bin
>>>     got 2 bytes from modem, data looks like: 2e c8  ..
>>>     got 5 bytes from modem, data looks like: 1b f6 02 00 41  ....A
>>>     got 1 bytes from modem, data looks like: 01  .
>>>     got 1 bytes from modem, data looks like: 40  @
>>>     Received PROMPT1 from phone, responding with CMD
>>>     read_file(../../target/firmware/board/compal_e99/loader.compalram.bin):
>>>     file_size=21752, hdr_len=4, dnload_len=21759
>>>     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: 41  A
>>>     got 1 bytes from modem, data looks like: 02  .
>>>     got 1 bytes from modem, data looks like: 43  C
>>>     Received PROMPT2 from phone, starting download
>>>     handle_write(): 4096 bytes (4096/21759)
>>>     handle_write(): 4096 bytes (8192/21759)
>>>     handle_write(): 4096 bytes (12288/21759)
>>>     handle_write(): 4096 bytes (16384/21759)
>>>     handle_write(): 4096 bytes (20480/21759)
>>>     handle_write(): 1279 bytes (21759/21759)
>>>     handle_write(): finished
>>>
>>>
>>>     The target phone is C115. I tried compal_exx and the result is the same :-(
>>>
>>>     Please, can someone help me to understand the reasons?
>>>     Thanks in advance.
>>>
>>>
>>>
>>>
>>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110117/a10d1974/attachment.htm>

From thatsit at gmx.ch  Mon Jan 17 20:38:36 2011
From: thatsit at gmx.ch (Thatsit)
Date: Mon, 17 Jan 2011 21:38:36 +0100
Subject: osmocon and boot loader experience
In-Reply-To: <4D33B856.1080200@volny.cz>
References: <12961327.3754611295203226842.JavaMail.defaultUser@defaultHost>
	<4D33B856.1080200@volny.cz>
Message-ID: <C1540A2E-44A8-4F40-B371-A6890C3B48A9@gmx.ch>

Hi

I also want to share my experience with osmocom and USB-serial cables..

My conclusion is clear that it is not a matter of physics (electrical) but of timing constraints.

- both chips (cables) Prolific and FDTI show more or less the same behavior regarding 
 successful firmware loading

- after loading the firmware none of the cables ever made any problems 
 (thanks to Harald's HDLC layer:-)

- Prolific result in smaller buffer sizes used (768) than FTDI (4096)

- Prolific is noisy, that means if the plug is not connected to the phone you will see
 endless random characters received my osmocom

- I made some tests on tree different platforms and 3 different mobiles (C123, C139, C155) 
 and the Prolific cable so far:
	1. very smal PC with Ubuntu 10.10 Server
	2. Vmware with Ubuntu 10.10 Desktop on older MacBookPro
	3. VirtualBox with Ubuntu 10.10 Desktop on a new MacPro (6 cores, 6Gb ram)

- Generally I got the best results with the C155 and worst with the C123

- On the MacBookPro/Vmware I never could successfully load any firmware on any phone

- On the small PC the very first try after a reboot succeeded most of the time. From then on 
 nearly every try failed

- On the new MacPro/VirtualBox nearly every Try succeded!

Then I ordered a FTDI cable in the hope that this would solve all my problems..

- It supports none standard baudrates - thats cool

- But the firmware loading didn't work better... :-((

For me it was then quite clear that i can only be a problem of the timing.. 
that means the phone is simply not willing to wait so long for the next character to read..

On my small PC I started killing some of the processes I don't use right now (mysql, apache, ..)
... and oh wonder.. the firmware loading worked already much better:-))

The I commented out all printf's which printed something out during the boot-loading..
.. and wow... from then on it worked nearly 100% of the times!!

Conclusion: 

If you have a powerful machine, you probably won't have any problems..
Else, we should probably think about changing the code in use during boot-load slightly.

I think that every time the osmocom executable calls select(), and thats a lot of times,
the kernel probably reschedules the processes.. and through this increases the chances
that there results a to big pause sending data to the phone..

Does this sound plausible?

Best regards
Matthias







From peter at stuge.se  Tue Jan 18 15:03:57 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 18 Jan 2011 16:03:57 +0100
Subject: osmocon and boot loader experience
In-Reply-To: <C1540A2E-44A8-4F40-B371-A6890C3B48A9@gmx.ch>
References: <12961327.3754611295203226842.JavaMail.defaultUser@defaultHost>
	<4D33B856.1080200@volny.cz>
	<C1540A2E-44A8-4F40-B371-A6890C3B48A9@gmx.ch>
Message-ID: <20110118150357.20518.qmail@stuge.se>

Thatsit wrote:
> My conclusion is clear that it is not a matter of physics
> (electrical) but of timing constraints.

It's just stupid to expose the UART all the way up in the PC. Better
would be something slightly more clever that could buffer data from
PC and meet strict timings with the phone.


> 	1. very smal PC with Ubuntu 10.10 Server
> 	2. Vmware with Ubuntu 10.10 Desktop on older MacBookPro
> 	3. VirtualBox with Ubuntu 10.10 Desktop on a new MacPro

Virtualizing USB is *always* a bad idea. It will very easily create
lots of problems because USB hosts have very strict requirements,
that do not fit at all in a virtualized environment.

Rather than virtualizing the USB device itself, it would be much
better to let the host OS handle the USB device, and instead share
the actual serial port device with the guest. That way the driver
does not need to run in the very bad guest environment.


> Does this sound plausible?

Sure, timing is important and virtualization easily messes that up.


//Peter



From 246tnt at gmail.com  Tue Jan 18 15:17:31 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Tue, 18 Jan 2011 16:17:31 +0100
Subject: osmocon and boot loader experience
In-Reply-To: <C1540A2E-44A8-4F40-B371-A6890C3B48A9@gmx.ch>
References: <12961327.3754611295203226842.JavaMail.defaultUser@defaultHost>
	<4D33B856.1080200@volny.cz>
	<C1540A2E-44A8-4F40-B371-A6890C3B48A9@gmx.ch>
Message-ID: <AANLkTikKMfpmp4Oszn9h6-qj0N8jR2JkjQfJBFhN_Ubr@mail.gmail.com>

Hi,


> My conclusion is clear that it is not a matter of physics (electrical) but of timing constraints.

If you can see the PROMPT1 / 2 and the download either doesn't finish
or you get a NACK, then yes, it's probably timing.
If you don't see PROMPT1/2 then it's electrical.

The bootloader serial routing is stupid as hell ... basically you have
: (from memory but the idea is there)

uint8_t read_char()
{
  for (int i=0; i<4096; i++)
    if (is_char_ready())
      return get_char_from_buffer();
  return 0;
}

So basically if it doesn't get a char in time, it return 0x00 and the
caller has no idea if the 0 is a received char or a timeout ...


> - after loading the firmware none of the cables ever made any problems
>  (thanks to Harald's HDLC layer:-)

It's both the HDLC and also the fact the uart is handled _way_ better
in our code than the


> - Prolific is noisy, that means if the plug is not connected to the phone you will see
>  endless random characters received my osmocom

Probably depends on the cable ... some prolific could have a pullup/down.


Cheers,

    Sylvain



From steve at steve-m.de  Tue Jan 18 19:14:55 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Tue, 18 Jan 2011 20:14:55 +0100
Subject: osmocon and boot loader experience
In-Reply-To: <AANLkTikKMfpmp4Oszn9h6-qj0N8jR2JkjQfJBFhN_Ubr@mail.gmail.com>
References: <12961327.3754611295203226842.JavaMail.defaultUser@defaultHost>	<4D33B856.1080200@volny.cz>	<C1540A2E-44A8-4F40-B371-A6890C3B48A9@gmx.ch>
	<AANLkTikKMfpmp4Oszn9h6-qj0N8jR2JkjQfJBFhN_Ubr@mail.gmail.com>
Message-ID: <4D35E6AF.9050104@steve-m.de>

Hi,

On 18.01.2011 16:17, Sylvain Munaut wrote:

> The bootloader serial routing is stupid as hell ... basically you have
> : (from memory but the idea is there)

Hm, I didn't know that it was that bad.

 From my experience the Calypso romloader handles the uart much better.

Just as an experiment: Here's a compiled binary, which does nothing more 
then starting the Calypso romloader:

http://www.steve-m.de/projects/osmocom/chainload_tiny.bin

------------------------------------------------------
	.globl _start

#define MEMIF_EXTRA_REG	0xfffffb10
#define BOOTROM_ENABLE	(1 << 8)

_start:
	ldr	r1, =0x000a0000
wait:
	subs	r1, r1, #1
	bne	wait

	ldr	r1, =MEMIF_EXTRA_REG
	ldr	r2, =BOOTROM_ENABLE
	strh	r2, [r1]
	ldr	pc, =0x0

------------------------------------------------------

If anyone wants to try if that works better when having serial issues:

$ ./osmocon -p /dev/ttyUSB0 -m c123 -c 
../../target/firmware/board/compal_e88/layer1.highram.bin chainload_tiny.bin

It works quite well here.

Regards,
Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: chainload_tiny.bin
Type: application/octet-stream
Size: 32 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110118/85cdc108/attachment.bin>

From weicai_huang at agilent.com  Tue Jan 18 05:02:16 2011
From: weicai_huang at agilent.com (weicai_huang at agilent.com)
Date: Mon, 17 Jan 2011 22:02:16 -0700
Subject: R: Re: C115 loader.compalram.bin
In-Reply-To: <4D33B856.1080200@volny.cz>
References: <12961327.3754611295203226842.JavaMail.defaultUser@defaultHost>
	<4D33B856.1080200@volny.cz>
Message-ID: <6B72458CCABAAF44A8FA0F101D24789B048C529FB4@cos-us-mb10.agilent.com>

Hello Tomas,

Does common USB->2.5 jack work? I have a USB->2.5 jack cable, but I am not sure if it can be used or not.

Best Regards,
Weicai

________________________________
From: Tomas Kopsa [mailto:deacon at volny.cz]
Sent: 2011?1?17? 11:33
To: list_mailing at libero.it; baseband-devel at lists.osmocom.org
Subject: Re: R: Re: C115 loader.compalram.bin

Hi Lia,

I have tested another cable (USB <-> 2,5 jack, speacial for Compal phones) - it is the same chip (Prolific) and I am able to load firmware too. Although it is the same chip, there is a difference that this one makes the osmocon printing those messages instantly when phone is not connected:

got 1 bytes from modem, data looks like: f5  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: f5  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: f5  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: fd  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: f5  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: fd  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: ea  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: ea  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: ea  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: ea  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: fd  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: ea

If I connect phone, printing stops. Here is what happened when I tried to load firmware without xor (-m c123) and pressed the button:
(This happened every attempt without xor flag)

Received PROMPT2 from phone, starting download
handle_write(): 1087 bytes (1087/50947)
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 :(
got 1 bytes from modem, data looks like: 66  f
got 1 bytes from modem, data looks like: 74  t
got 1 bytes from modem, data looks like: 6d  m
got 1 bytes from modem, data looks like: 74  t
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 6c  l
Received FTMTOOL from phone, ramloader has aborted
got 1 bytes from modem, data looks like: 65  e
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 6f  o
got 1 bytes from modem, data looks like: 72  r
got 1 bytes from modem, data looks like: 00  .


If you have USB adapter (I guess you have), you dont need to check model, check 'lsusb'

[root at amilo osmocon]# lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 017: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port

If you have Prolific, which is very common, I encourage you to use xor flag. You can also try to switch on your phone to check if original
firmware boots. I experienced during my early tests, that phone crashed (probably SRAM) and it was unable to boot even original fw. In case phone is crashed, reconnect battery and it will fix itself.

Here is the ACK after hello world load:

handle_write(): 768 bytes (17919/19787)
handle_write(): 768 bytes (18687/19787)
handle_write(): 768 bytes (19455/19787)
handle_write(): 332 bytes (19787/19787)
handle_write(): finished
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: 41  A
got 1 bytes from modem, data looks like: 03  .
got 1 bytes from modem, data looks like: 42  B
Received DOWNLOAD ACK from phone, your code is running now!


OSMOCOM Hello World (revision osmocon_v0.0.0-754-gb5abcb6-modified)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: efce3b1ce1001255
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
==============================================


Looking forward your response,

Tomas




Hi Tomas,

thanks for your feedback.

Actually, I've tried both flags (woth/without xor extension), but hte result is the same.

So, in your opinioni, the problem could depend on the cable?

I don't have the cable model now, but I can send you this information Tuesday.

Thanks again.

cheers.

lia
----Messaggio originale----
Da: deacon at volny.cz<mailto:deacon at volny.cz>
Data: 16-gen-2011 4.26
A: <list_mailing at libero.it><mailto:list_mailing at libero.it>
ubut Ogg: Re: C115 loader.compalram.bin

Hello,
I have C115 too and I use '-m c123xor' switch, the phone mostly boots on 1st button push  (I never reacher full load with '-m c123').

./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin
./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin
./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/layer1.compalram.bin

I have FTDI USB<->RS232 + Calypso serial. When load fails (with xor), I have a feeling that it helps reconnection cable to the phone.
(I have also Calypso USB cable which I haven't tested yet, will report later.)

- Tomas




Hello.

I'm trying to load the loader.compalram.bin.

The behaviour is very strange because sometimes the download is complete and

successfull, sometimes; in particular, in this case, the download is complete,

but any ACK is sent back from the mobile phone (see below).

./osmocon -p /dev/ttyUSB0 -m c123 ../..

/target/firmware/board/compal_e99/loader.compalram.bin

got 2 bytes from modem, data looks like: 2e c8  ..

got 5 bytes from modem, data looks like: 1b f6 02 00 41  ....A

got 1 bytes from modem, data looks like: 01  .

got 1 bytes from modem, data looks like: 40  @

Received PROMPT1 from phone, responding with CMD

read_file(../../target/firmware/board/compal_e99/loader.compalram.bin):

file_size=21752, hdr_len=4, dnload_len=21759

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: 41  A

got 1 bytes from modem, data looks like: 02  .

got 1 bytes from modem, data looks like: 43  C

Received PROMPT2 from phone, starting download

handle_write(): 4096 bytes (4096/21759)

handle_write(): 4096 bytes (8192/21759)

handle_write(): 4096 bytes (12288/21759)

handle_write(): 4096 bytes (16384/21759)

handle_write(): 4096 bytes (20480/21759)

handle_write(): 1279 bytes (21759/21759)

handle_write(): finished





The target phone is C115. I tried compal_exx and the result is the same :-(



Please, can someone help me to understand the reasons?

Thanks in advance.













-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110117/6d422abc/attachment.htm>

From deacon at volny.cz  Tue Jan 18 14:22:50 2011
From: deacon at volny.cz (Tomas Kopsa)
Date: Tue, 18 Jan 2011 15:22:50 +0100
Subject: R: Re: C115 loader.compalram.bin
In-Reply-To: <6B72458CCABAAF44A8FA0F101D24789B048C529FB4@cos-us-mb10.agilent.com>
References: <12961327.3754611295203226842.JavaMail.defaultUser@defaultHost>	<4D33B856.1080200@volny.cz>
	<6B72458CCABAAF44A8FA0F101D24789B048C529FB4@cos-us-mb10.agilent.com>
Message-ID: <4D35A23A.70509@volny.cz>

Hello Weicai,

Yes, I'm using this cable (with Prolific Technology converter). You can
check your USB cable info with 'lsusb' command (see my last e-mail).
The most important thing is the voltage of the cable output - cannot
exceed 3.3V else you fry your phone !! (see
http://bb.osmocom.org/trac/wiki/CalypsoSerialCable). If you want to make
100% sure about the voltage, you can measure that with every DC voltmeter.

Tomas



> Hello Tomas,
>
> Does common USB->2.5 jack work? I have a USB->2.5 jack cable, but I am
> not sure if it can be used or not.
>
> Best Regards,
>
> Weicai
>
> ------------------------------------------------------------------------
>
> *From:*Tomas Kopsa [mailto:deacon at volny.cz]
> *Sent:* 2011?1?17?11:33
> *To:* list_mailing at libero.it; baseband-devel at lists.osmocom.org
> *Subject:* Re: R: Re: C115 loader.compalram.bin
>
> Hi Lia,
>
> I have tested another cable (USB <-> 2,5 jack, speacial for Compal
> phones) - it is the same chip (Prolific) and I am able to load
> firmware too. Although it is the same chip, there is a difference that
> this one makes the osmocon printing those messages instantly when
> phone is not connected:
>
> got 1 bytes from modem, data looks like: f5 .
> got 1 bytes from modem, data looks like: 00 .
> got 1 bytes from modem, data looks like: f5 .
> got 1 bytes from modem, data looks like: 00 .
> got 1 bytes from modem, data looks like: f5 .
> got 1 bytes from modem, data looks like: 00 .
> got 1 bytes from modem, data looks like: fd .
> got 1 bytes from modem, data looks like: 00 .
> got 1 bytes from modem, data looks like: f5 .
> got 1 bytes from modem, data looks like: 00 .
> got 1 bytes from modem, data looks like: fd .
> got 1 bytes from modem, data looks like: 00 .
> got 1 bytes from modem, data looks like: ea .
> got 1 bytes from modem, data looks like: 00 .
> got 1 bytes from modem, data looks like: ea .
> got 1 bytes from modem, data looks like: 00 .
> got 1 bytes from modem, data looks like: ea .
> got 1 bytes from modem, data looks like: 00 .
> got 1 bytes from modem, data looks like: ea .
> got 1 bytes from modem, data looks like: 00 .
> got 1 bytes from modem, data looks like: fd .
> got 1 bytes from modem, data looks like: 00 .
> got 1 bytes from modem, data looks like: ea
>
> If I connect phone, printing stops. Here is what happened when I tried
> to load firmware without xor (-m c123) and pressed the button:
> (This happened every attempt without xor flag)
>
> Received PROMPT2 from phone, starting download
> handle_write(): 1087 bytes (1087/50947)
> 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 :(
> got 1 bytes from modem, data looks like: 66 f
> got 1 bytes from modem, data looks like: 74 t
> got 1 bytes from modem, data looks like: 6d m
> got 1 bytes from modem, data looks like: 74 t
> got 1 bytes from modem, data looks like: 6f o
> got 1 bytes from modem, data looks like: 6f o
> got 1 bytes from modem, data looks like: 6c l
> Received FTMTOOL from phone, ramloader has aborted
> got 1 bytes from modem, data looks like: 65 e
> got 1 bytes from modem, data looks like: 72 r
> got 1 bytes from modem, data looks like: 72 r
> got 1 bytes from modem, data looks like: 6f o
> got 1 bytes from modem, data looks like: 72 r
> got 1 bytes from modem, data looks like: 00 .
>
>
> If you have USB adapter (I guess you have), you dont need to check
> model, check 'lsusb'
>
> [root at amilo osmocon]# lsusb
> Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> *Bus 002 Device 017: ID 067b:2303 Prolific Technology, Inc. PL2303
> Serial Port*
>
> If you have Prolific, which is very common, I encourage you to use xor
> flag. You can also try to switch on your phone to check if original
> firmware boots. I experienced during my early tests, that phone
> crashed (probably SRAM) and it was unable to boot even original fw. In
> case phone is crashed, reconnect battery and it will fix itself.
>
> Here is the ACK after hello world load:
>
> handle_write(): 768 bytes (17919/19787)
> handle_write(): 768 bytes (18687/19787)
> handle_write(): 768 bytes (19455/19787)
> handle_write(): 332 bytes (19787/19787)
> handle_write(): finished
> 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: 41 A
> got 1 bytes from modem, data looks like: 03 .
> got 1 bytes from modem, data looks like: 42 B
> Received DOWNLOAD ACK from phone, your code is running now!
>
>
> OSMOCOM Hello World (revision osmocon_v0.0.0-754-gb5abcb6-modified)
> ======================================================================
> Device ID code: 0xb4fb
> Device Version code: 0x0000
> ARM ID code: 0xfff3
> cDSP ID code: 0x0128
> Die ID code: efce3b1ce1001255
> ======================================================================
> REG_DPLL=0x2413
> CNTL_ARM_CLK=0xf0a1
> CNTL_CLK=0xff91
> CNTL_RST=0xfff3
> CNTL_ARM_DIV=0xfff9
> ==============================================
>
>
> Looking forward your response,
>
> Tomas
>
>
>
> Hi Tomas,
>
> thanks for your feedback.
>
> Actually, I've tried both flags (woth/without xor extension), but hte
> result is the same.
>
> So, in your opinioni, the problem could depend on the cable?
>
> I don't have the cable model now, but I can send you this information
> Tuesday.
>
> Thanks again.
>
> cheers.
>
> lia
>
>     ----Messaggio originale----
>     Da: deacon at volny.cz <mailto:deacon at volny.cz>
>     Data: 16-gen-2011 4.26
>     A: <list_mailing at libero.it> <mailto:list_mailing at libero.it>
>     ubut Ogg: Re: C115 loader.compalram.bin
>
>     Hello,
>     I have C115 too and I use '-m c123xor' switch, the phone mostly
>     boots on 1st button push (I never reacher full load with '-m c123').
>
>     ./osmocon -p /dev/ttyUSB0 -m c123xor
>     ../../target/firmware/board/compal_e88/hello_world.compalram.bin
>     ./osmocon -p /dev/ttyUSB0 -m c123xor
>     ../../target/firmware/board/compal_e88/loader.compalram.bin
>     ./osmocon -p /dev/ttyUSB0 -m c123xor
>     ../../target/firmware/board/compal_e88/layer1.compalram.bin
>
>     I have FTDI USB<->RS232 + Calypso serial. When load fails (with
>     xor), I have a feeling that it helps reconnection cable to the phone.
>     (I have also Calypso USB cable which I haven't tested yet, will
>     report later.)
>
>     - Tomas
>
>
>
>>     Hello.
>>     I'm trying to load the loader.compalram.bin. 
>>     The behaviour is very strange because sometimes the download is complete and 
>>     successfull, sometimes; in particular, in this case, the download is complete, 
>>     but any ACK is sent back from the mobile phone (see below). 
>>     ./osmocon -p /dev/ttyUSB0 -m c123 ../..
>>     /target/firmware/board/compal_e99/loader.compalram.bin
>>     got 2 bytes from modem, data looks like: 2e c8  ..
>>     got 5 bytes from modem, data looks like: 1b f6 02 00 41  ....A
>>     got 1 bytes from modem, data looks like: 01  .
>>     got 1 bytes from modem, data looks like: 40  @
>>     Received PROMPT1 from phone, responding with CMD
>>     read_file(../../target/firmware/board/compal_e99/loader.compalram.bin): 
>>     file_size=21752, hdr_len=4, dnload_len=21759
>>     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: 41  A
>>     got 1 bytes from modem, data looks like: 02  .
>>     got 1 bytes from modem, data looks like: 43  C
>>     Received PROMPT2 from phone, starting download
>>     handle_write(): 4096 bytes (4096/21759)
>>     handle_write(): 4096 bytes (8192/21759)
>>     handle_write(): 4096 bytes (12288/21759)
>>     handle_write(): 4096 bytes (16384/21759)
>>     handle_write(): 4096 bytes (20480/21759)
>>     handle_write(): 1279 bytes (21759/21759)
>>     handle_write(): finished
>>      
>>      
>>     The target phone is C115. I tried compal_exx and the result is the same :-(
>>      
>>     Please, can someone help me to understand the reasons?
>>     Thanks in advance.
>>      
>>      
>>      
>>      
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110118/bdfa0898/attachment.htm>

From dario.lombardo at libero.it  Mon Jan 17 14:23:13 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Mon, 17 Jan 2011 15:23:13 +0100
Subject: Sim on C115 & C118
Message-ID: <4D3450D1.10209@libero.it>

Hello everybody
I'm trying to run the "mobile" application on a C115 and a C118 phone. I 
want to use the real sim, so I used "sim reader" in the config. Both 
phones have the same behaviour:

<000e> sim.c:1206 init SIM client
<0005> gsm48_cc.c:61 init Call Control
<0001> gsm48_rr.c:4944 init Radio Ressource process
<0004> gsm48_mm.c:1220 init Mobility Management process
<0004> gsm48_mm.c:971 Selecting PLMN SEARCH state, because no SIM.
<0002> gsm322.c:3471 init PLMN process
<0003> gsm322.c:3472 init Cell Selection process
Mobile '1' initialized, please start phone now!
VTY available on port 4247.
<0004> subscriber.c:556 Requesting SIM file 0x2fe2
<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)
<000e> sim.c:697 go MF
<000e> sim.c:241 SELECT (file=0x3f00)
<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)

no more output beyond this point.
Phones work correctly with other softwares, sim works correctly. I get 
no response from the sim. Is the card reader working on these phones? If 
yes, does anyone have suggestions to solve this issue?
Thanks a lot to everybody.
Dario.



From dpavlin at rot13.org  Mon Jan 17 15:13:28 2011
From: dpavlin at rot13.org (Dobrica Pavlinusic)
Date: Mon, 17 Jan 2011 16:13:28 +0100
Subject: Sim on C115 & C118
In-Reply-To: <4D3450D1.10209@libero.it>
References: <4D3450D1.10209@libero.it>
Message-ID: <20110117151328.GA20636@rot13.org>

On Mon, Jan 17, 2011 at 03:23:13PM +0100, Dario Lombardo wrote:
> Hello everybody
> I'm trying to run the "mobile" application on a C115 and a C118
> phone. I want to use the real sim, so I used "sim reader" in the
> config. Both phones have the same behaviour:
> 
> <000e> sim.c:1206 init SIM client
> <0005> gsm48_cc.c:61 init Call Control
> <0001> gsm48_rr.c:4944 init Radio Ressource process
> <0004> gsm48_mm.c:1220 init Mobility Management process
> <0004> gsm48_mm.c:971 Selecting PLMN SEARCH state, because no SIM.
> <0002> gsm322.c:3471 init PLMN process
> <0003> gsm322.c:3472 init Cell Selection process
> Mobile '1' initialized, please start phone now!
> VTY available on port 4247.
> <0004> subscriber.c:556 Requesting SIM file 0x2fe2
> <000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)
> <000e> sim.c:697 go MF
> <000e> sim.c:241 SELECT (file=0x3f00)
> <000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)
> 
> no more output beyond this point.
> Phones work correctly with other softwares, sim works correctly. I
> get no response from the sim. Is the card reader working on these
> phones? If yes, does anyone have suggestions to solve this issue?

Are you using sylvain/testing branch from git?

I did test (with success) sim with same two phones, and collected some
useful hints about configuration at:

http://blog.rot13.org/2011/01/osmocom-bb_-_free_software_finally_comes_to_gsm.html

(please note recommendation to use gnu-arm cross compiler!)

-- 
Dobrica Pavlinusic               2share!2flame            dpavlin at rot13.org
Unix addict. Internet consultant.             http://www.rot13.org/~dpavlin



From b.alecu at yahoo.com  Mon Jan 17 18:24:51 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Mon, 17 Jan 2011 10:24:51 -0800 (PST)
Subject: Sim on C115 & C118
Message-ID: <995940.63460.qm@web46202.mail.sp1.yahoo.com>

I was going to ask the same question because I have same problem with sim reader mode. However I haven't used Sylvain test. I will and come back with an update.


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110117/cbf3d733/attachment.htm>

From dpavlin at rot13.org  Mon Jan 17 19:05:58 2011
From: dpavlin at rot13.org (Dobrica Pavlinusic)
Date: Mon, 17 Jan 2011 20:05:58 +0100
Subject: wiki: SIMReader Was: Sim on C115 & C118
In-Reply-To: <995940.63460.qm@web46202.mail.sp1.yahoo.com>
References: <995940.63460.qm@web46202.mail.sp1.yahoo.com>
Message-ID: <20110117190558.GA2773@rot13.org>

On Mon, Jan 17, 2011 at 10:24:51AM -0800, Bogdan Alecu wrote:
> I was going to ask the same question because I have same problem with sim reader mode. However I haven't used Sylvain test. I will and come back with an update.

There seems to be sufficiant interest for using SIM reader, so I created
page on wiki which might serve as good pointer:

http://bb.osmocom.org/trac/wiki/SIMReader

-- 
Dobrica Pavlinusic               2share!2flame            dpavlin at rot13.org
Unix addict. Internet consultant.             http://www.rot13.org/~dpavlin



From dpavlin at rot13.org  Mon Jan 17 21:31:38 2011
From: dpavlin at rot13.org (Dobrica Pavlinusic)
Date: Mon, 17 Jan 2011 22:31:38 +0100
Subject: wiki: SIMReader Was: Sim on C115 & C118
In-Reply-To: <473166.78442.qm@web46211.mail.sp1.yahoo.com>
References: <20110117190558.GA2773@rot13.org>
	<473166.78442.qm@web46211.mail.sp1.yahoo.com>
Message-ID: <20110117213138.GA11419@rot13.org>

On Mon, Jan 17, 2011 at 11:46:50AM -0800, Bogdan Alecu wrote:
> Hello,
> ?
> Sorry for writing you directly to your email. Thank you very much for the wiki. I was wondering if you have some knowledge about the "sim test" mode. I tried it by filling in the IMSI and MCC MNC. After I start the layer2 in a few seconds layer1 crashes. What I am trying to achieve is to send a IMSI detach to the network for the specified IMSI. Maybe you could give me a hand with this.

This is often second question after getting SIM working, so I want to
share what I know. However, I'm not an expert, and most of this is
gathered from presentations and speaking with people who know more than
I do, so I wanted to bounce this against mailing list for additional
comments.

As far as I understand it, to connect to provider network, you need
provider's ki which is shared secret between network and sim card.

There are some practical attacks on older sim cards which are used by
multi-network sim cards. It seems there is limited number of brute-force
interations that cards support before disabling themself and that
changed somehow in recent cards.

Best SIM explanation I found so far is on 27C3 wiki about GSM network:

http://events.ccc.de/congress/2010/wiki/GSM#Why_do_I_need_to_buy_your_SIM_card_to_participate.3F

> --- On Mon, 1/17/11, Dobrica Pavlinusic <dpavlin at rot13.org> wrote:
> 
> 
> From: Dobrica Pavlinusic <dpavlin at rot13.org>
> Subject: wiki: SIMReader Was: Sim on C115 & C118
> To: "Bogdan Alecu" <b.alecu at yahoo.com>
> Cc: dario.lombardo at libero.it, baseband-devel at lists.osmocom.org
> Date: Monday, January 17, 2011, 7:05 PM
> 
> 
> On Mon, Jan 17, 2011 at 10:24:51AM -0800, Bogdan Alecu wrote:
> > I was going to ask the same question because I have same problem with sim reader mode. However I haven't used Sylvain test. I will and come back with an update.
> 
> There seems to be sufficiant interest for using SIM reader, so I created
> page on wiki which might serve as good pointer:
> 
> http://bb.osmocom.org/trac/wiki/SIMReader
> 
> -- 
> Dobrica Pavlinusic? ? ? ? ? ? ???2share!2flame? ? ? ? ? ? dpavlin at rot13.org
> Unix addict. Internet consultant.? ? ? ? ? ???http://www.rot13.org/~dpavlin
> 
> 
> 
>       

-- 
Dobrica Pavlinusic               2share!2flame            dpavlin at rot13.org
Unix addict. Internet consultant.             http://www.rot13.org/~dpavlin



From b.alecu at yahoo.com  Mon Jan 17 23:12:02 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Mon, 17 Jan 2011 15:12:02 -0800 (PST)
Subject: wiki: SIMReader Was: Sim on C115 & C118
In-Reply-To: <20110117213138.GA11419@rot13.org>
Message-ID: <341817.42180.qm@web46202.mail.sp1.yahoo.com>

Indeed for registering to the network you'll need the ki, but for IMSI detach it's not necessary. I'm going to try again the sim test mode after getting testing branch. maybe this will solve layer1 crash.
?


--- On Mon, 1/17/11, Dobrica Pavlinusic <dpavlin at rot13.org> wrote:


From: Dobrica Pavlinusic <dpavlin at rot13.org>
Subject: Re: wiki: SIMReader Was: Sim on C115 & C118
To: "Bogdan Alecu" <b.alecu at yahoo.com>
Cc: baseband-devel at lists.osmocom.org
Date: Monday, January 17, 2011, 9:31 PM


On Mon, Jan 17, 2011 at 11:46:50AM -0800, Bogdan Alecu wrote:
> Hello,
> ?
> Sorry for writing you directly to your email. Thank you very much for the wiki. I was wondering if you have some knowledge about the "sim test" mode. I tried it by filling in the IMSI and MCC MNC. After I start the layer2 in a few seconds layer1 crashes. What I am trying to achieve is to send a IMSI detach to the network for the specified IMSI. Maybe you could give me a hand with this.

This is often second question after getting SIM working, so I want to
share what I know. However, I'm not an expert, and most of this is
gathered from presentations and speaking with people who know more than
I do, so I wanted to bounce this against mailing list for additional
comments.

As far as I understand it, to connect to provider network, you need
provider's ki which is shared secret between network and sim card.

There are some practical attacks on older sim cards which are used by
multi-network sim cards. It seems there is limited number of brute-force
interations that cards support before disabling themself and that
changed somehow in recent cards.

Best SIM explanation I found so far is on 27C3 wiki about GSM network:

http://events.ccc.de/congress/2010/wiki/GSM#Why_do_I_need_to_buy_your_SIM_card_to_participate.3F

> --- On Mon, 1/17/11, Dobrica Pavlinusic <dpavlin at rot13.org> wrote:
> 
> 
> From: Dobrica Pavlinusic <dpavlin at rot13.org>
> Subject: wiki: SIMReader Was: Sim on C115 & C118
> To: "Bogdan Alecu" <b.alecu at yahoo.com>
> Cc: dario.lombardo at libero.it, baseband-devel at lists.osmocom.org
> Date: Monday, January 17, 2011, 7:05 PM
> 
> 
> On Mon, Jan 17, 2011 at 10:24:51AM -0800, Bogdan Alecu wrote:
> > I was going to ask the same question because I have same problem with sim reader mode. However I haven't used Sylvain test. I will and come back with an update.
> 
> There seems to be sufficiant interest for using SIM reader, so I created
> page on wiki which might serve as good pointer:
> 
> http://bb.osmocom.org/trac/wiki/SIMReader
> 
> -- 
> Dobrica Pavlinusic? ? ? ? ? ? ???2share!2flame? ? ? ? ? ? dpavlin at rot13.org
> Unix addict. Internet consultant.? ? ? ? ? ???http://www.rot13.org/~dpavlin
> 
> 
> 
>? ? ???

-- 
Dobrica Pavlinusic? ? ? ? ? ? ???2share!2flame? ? ? ? ? ? dpavlin at rot13.org
Unix addict. Internet consultant.? ? ? ? ? ???http://www.rot13.org/~dpavlin



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110117/8f645d84/attachment.htm>

From b.alecu at yahoo.com  Tue Jan 18 19:21:19 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Tue, 18 Jan 2011 11:21:19 -0800 (PST)
Subject: wiki: SIMReader Was: Sim on C115 & C118
In-Reply-To: <20110117213138.GA11419@rot13.org>
Message-ID: <5318.7434.qm@web46205.mail.sp1.yahoo.com>

I finally managed to place a call. After trying to use the test base and compile, it gave error for some function which was expecting a parameter. I found that I had to put NULL as parameter and after this it compiled with no errors. I also reported this on irc and someone has fixed this - the repository now has this parameter.
Someone said that there should be two separate discussion lists - for users and dev - because there are newbie questions around. Well, I must tell you that I really did read the wiki, watched the presentations and so on and still couldn't find a complete guide on how to use Osmocom. As you can see, in the case above it wasn't at all my fault that the parameter was missing. Please don't jump to conclusions so quickly. My impression is that for an open-source project it seems to be more closed. If you did discover something then why not share?
?
For all who try to make your first call: if you followed all the steps from wiki and you still have problems making a call, check if your cable fits good in the phone and try also with the prebuilt arm instead of building yours. For me these two things did the trick.
?
?

--- On Mon, 1/17/11, Dobrica Pavlinusic <dpavlin at rot13.org> wrote:


From: Dobrica Pavlinusic <dpavlin at rot13.org>
Subject: Re: wiki: SIMReader Was: Sim on C115 & C118
To: "Bogdan Alecu" <b.alecu at yahoo.com>
Cc: baseband-devel at lists.osmocom.org
Date: Monday, January 17, 2011, 9:31 PM


On Mon, Jan 17, 2011 at 11:46:50AM -0800, Bogdan Alecu wrote:
> Hello,
> ?
> Sorry for writing you directly to your email. Thank you very much for the wiki. I was wondering if you have some knowledge about the "sim test" mode. I tried it by filling in the IMSI and MCC MNC. After I start the layer2 in a few seconds layer1 crashes. What I am trying to achieve is to send a IMSI detach to the network for the specified IMSI. Maybe you could give me a hand with this.

This is often second question after getting SIM working, so I want to
share what I know. However, I'm not an expert, and most of this is
gathered from presentations and speaking with people who know more than
I do, so I wanted to bounce this against mailing list for additional
comments.

As far as I understand it, to connect to provider network, you need
provider's ki which is shared secret between network and sim card.

There are some practical attacks on older sim cards which are used by
multi-network sim cards. It seems there is limited number of brute-force
interations that cards support before disabling themself and that
changed somehow in recent cards.

Best SIM explanation I found so far is on 27C3 wiki about GSM network:

http://events.ccc.de/congress/2010/wiki/GSM#Why_do_I_need_to_buy_your_SIM_card_to_participate.3F

> --- On Mon, 1/17/11, Dobrica Pavlinusic <dpavlin at rot13.org> wrote:
> 
> 
> From: Dobrica Pavlinusic <dpavlin at rot13.org>
> Subject: wiki: SIMReader Was: Sim on C115 & C118
> To: "Bogdan Alecu" <b.alecu at yahoo.com>
> Cc: dario.lombardo at libero.it, baseband-devel at lists.osmocom.org
> Date: Monday, January 17, 2011, 7:05 PM
> 
> 
> On Mon, Jan 17, 2011 at 10:24:51AM -0800, Bogdan Alecu wrote:
> > I was going to ask the same question because I have same problem with sim reader mode. However I haven't used Sylvain test. I will and come back with an update.
> 
> There seems to be sufficiant interest for using SIM reader, so I created
> page on wiki which might serve as good pointer:
> 
> http://bb.osmocom.org/trac/wiki/SIMReader
> 
> -- 
> Dobrica Pavlinusic? ? ? ? ? ? ???2share!2flame? ? ? ? ? ? dpavlin at rot13.org
> Unix addict. Internet consultant.? ? ? ? ? ???http://www.rot13.org/~dpavlin
> 
> 
> 
>? ? ???

-- 
Dobrica Pavlinusic? ? ? ? ? ? ???2share!2flame? ? ? ? ? ? dpavlin at rot13.org
Unix addict. Internet consultant.? ? ? ? ? ???http://www.rot13.org/~dpavlin



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110118/d5626330/attachment.htm>

From dpavlin at rot13.org  Tue Jan 18 20:42:49 2011
From: dpavlin at rot13.org (Dobrica Pavlinusic)
Date: Tue, 18 Jan 2011 21:42:49 +0100
Subject: wiki: SIMReader Was: Sim on C115 & C118
In-Reply-To: <5318.7434.qm@web46205.mail.sp1.yahoo.com>
References: <20110117213138.GA11419@rot13.org>
	<5318.7434.qm@web46205.mail.sp1.yahoo.com>
Message-ID: <20110118204249.GC7032@rot13.org>

On Tue, Jan 18, 2011 at 11:21:19AM -0800, Bogdan Alecu wrote:
> Someone said that there should be two separate discussion lists - for users
> and dev - because there are newbie questions around. Well, I must tell you
> that I really did read the wiki, watched the presentations and so on and
> still couldn't find a complete guide on how to use Osmocom. As you can see,
> in the case above it wasn't at all my fault that the parameter was missing.
> Please don't jump to conclusions so quickly. My impression is that for an
> open-source project it seems to be more closed. If you did discover
> something then why not share?

I totally understand inpatiance of core developers with us newbies who
are trying to use this project for the first time.

As my appriciation for their's time on something I can allrady use I
decided to document SIMReader on wiki, so all blame on poor page quality
should go to me directly and not to project itself, I'm afraid :-)

However, I extended wiki page with additional steps to place your first
call on provider network, and I would appriciate feedback if this info
would help you get started.

-- 
Dobrica Pavlinusic               2share!2flame            dpavlin at rot13.org
Unix addict. Internet consultant.             http://www.rot13.org/~dpavlin



From b.alecu at yahoo.com  Tue Jan 18 20:29:24 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Tue, 18 Jan 2011 12:29:24 -0800 (PST)
Subject: wiki: SIMReader Was: Sim on C115 & C118
In-Reply-To: <20110117213138.GA11419@rot13.org>
Message-ID: <471770.43898.qm@web46215.mail.sp1.yahoo.com>

I finally managed to place a call. After trying to use the test base and compile, it gave error for some function which was expecting a parameter. I found that I had to put NULL as parameter and after this it compiled with no errors. I also reported this on irc and someone has fixed this - the repository now has this parameter.
Someone said that there should be two separate discussion lists - for users and dev - because there are newbie questions around. Well, I must tell you that I really did read the wiki, watched the presentations and so on and still couldn't find a complete guide on how to use Osmocom. As you can see, in the case above it wasn't at all my fault that the parameter was missing. Please don't jump to conclusions so quickly. My impression is that for an open-source project it seems to be more closed. If you did discover something then why not share?
?
For all who try to make your first call: if you followed all the steps from wiki and you still have problems making a call, check if your cable fits good in the phone and try also with the prebuilt arm instead of building yours. For me these two things did the trick.
?
?

--- On Mon, 1/17/11, Dobrica Pavlinusic <dpavlin at rot13.org> wrote:


From: Dobrica Pavlinusic <dpavlin at rot13.org>
Subject: Re: wiki: SIMReader Was: Sim on C115 & C118
To: "Bogdan Alecu" <b.alecu at yahoo.com>
Cc: baseband-devel at lists.osmocom.org
Date: Monday, January 17, 2011, 9:31 PM


On Mon, Jan 17, 2011 at 11:46:50AM -0800, Bogdan Alecu wrote:
> Hello,
> ?
> Sorry for writing you directly to your email. Thank you very much for the wiki. I was wondering if you have some knowledge about the "sim test" mode. I tried it by filling in the IMSI and MCC MNC. After I start the layer2 in a few seconds layer1 crashes. What I am trying to achieve is to send a IMSI detach to the network for the specified IMSI. Maybe you could give me a hand with this.

This is often second question after getting SIM working, so I want to
share what I know. However, I'm not an expert, and most of this is
gathered from presentations and speaking with people who know more than
I do, so I wanted to bounce this against mailing list for additional
comments.

As far as I understand it, to connect to provider network, you need
provider's ki which is shared secret between network and sim card.

There are some practical attacks on older sim cards which are used by
multi-network sim cards. It seems there is limited number of brute-force
interations that cards support before disabling themself and that
changed somehow in recent cards.

Best SIM explanation I found so far is on 27C3 wiki about GSM network:

http://events.ccc.de/congress/2010/wiki/GSM#Why_do_I_need_to_buy_your_SIM_card_to_participate.3F

> --- On Mon, 1/17/11, Dobrica Pavlinusic <dpavlin at rot13.org> wrote:
> 
> 
> From: Dobrica Pavlinusic <dpavlin at rot13.org>
> Subject: wiki: SIMReader Was: Sim on C115 & C118
> To: "Bogdan Alecu" <b.alecu at yahoo.com>
> Cc: dario.lombardo at libero.it, baseband-devel at lists.osmocom.org
> Date: Monday, January 17, 2011, 7:05 PM
> 
> 
> On Mon, Jan 17, 2011 at 10:24:51AM -0800, Bogdan Alecu wrote:
> > I was going to ask the same question because I have same problem with sim reader mode. However I haven't used Sylvain test. I will and come back with an update.
> 
> There seems to be sufficiant interest for using SIM reader, so I created
> page on wiki which might serve as good pointer:
> 
> http://bb.osmocom.org/trac/wiki/SIMReader
> 
> -- 
> Dobrica Pavlinusic? ? ? ? ? ? ???2share!2flame? ? ? ? ? ? dpavlin at rot13.org
> Unix addict. Internet consultant.? ? ? ? ? ???http://www.rot13.org/~dpavlin
> 
> 
> 
>? ? ???

-- 
Dobrica Pavlinusic? ? ? ? ? ? ???2share!2flame? ? ? ? ? ? dpavlin at rot13.org
Unix addict. Internet consultant.? ? ? ? ? ???http://www.rot13.org/~dpavlin



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110118/906a112d/attachment.htm>

From deacon at volny.cz  Tue Jan 18 23:19:38 2011
From: deacon at volny.cz (Tomas Kopsa)
Date: Wed, 19 Jan 2011 00:19:38 +0100
Subject: wiki: SIMReader Was: Sim on C115 & C118
In-Reply-To: <471770.43898.qm@web46215.mail.sp1.yahoo.com>
References: <471770.43898.qm@web46215.mail.sp1.yahoo.com>
Message-ID: <4D36200A.5000802@volny.cz>


> I finally managed to place a call. After trying to use the test base 
> and compile, it gave error for some function which was expecting a 
> parameter. I found that I had to put NULL as parameter and after this 
> it compiled with no errors. I also reported this on irc and someone 
> has fixed this - the repository now has this parameter.
>
I have just tried this testing branch too. I had version without fix, 
following change is needed:

in osmocom-bb/src/target/firmware/apps/simtest/main.c add NULL as 
parameter to calypso_sim_init()

     /* Initialize Sim-Controller driver */
     puts("Initializing driver:\n");
     calypso_sim_init(NULL);


I try to help with putting information on wiki.

- Tomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110119/647ab8b6/attachment.htm>

From dario.lombardo at libero.it  Wed Jan 19 08:25:53 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Wed, 19 Jan 2011 09:25:53 +0100
Subject: wiki: SIMReader Was: Sim on C115 & C118
In-Reply-To: <471770.43898.qm@web46215.mail.sp1.yahoo.com>
References: <471770.43898.qm@web46215.mail.sp1.yahoo.com>
Message-ID: <4D36A011.7030106@libero.it>



On 01/18/2011 09:29 PM, Bogdan Alecu wrote:
> Someone said that there should be two separate discussion lists - for 
> users and dev - because there are newbie questions around. Well, I 
> must tell you that I really did read the wiki, watched the 
> presentations and so on and still couldn't find a complete guide on 
> how to use Osmocom. As you can see, in the case above it wasn't at all 
> my fault that the parameter was missing. Please don't jump to 
> conclusions so quickly. My impression is that for an open-source 
> project it seems to be more closed. If you did discover something then 
> why not share?
>
>
I think that the right suggestion came from Harald: project experts 
shouldn't answer to newbies questions, but just answer more complex 
ones. I think that other people that faced the basic issues can answer, 
in this case. I understand both points of view: newbies want to be 
helped, and they ask always the same questions (and it's right because, 
I must admin, documentation is not so good), and experts are tired of 
giving always the same infos. Remember that this is not a product but an 
community project, so we must act as a community. Contributions to wiki 
should be done, too.
I definitely like this project.
Dario.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110119/9f9afc93/attachment.htm>

From b.alecu at yahoo.com  Tue Jan 18 08:50:14 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Tue, 18 Jan 2011 00:50:14 -0800 (PST)
Subject: wiki: SIMReader Was: Sim on C115 & C118
In-Reply-To: <20110117190558.GA2773@rot13.org>
Message-ID: <427272.80869.qm@web46209.mail.sp1.yahoo.com>

Hi,
I have just tried to use the test branch but it's seems it's not that easy. After 
git checkout -b testing remotes/origin/sylvain/testing you say to fix merge content.

Any idea on how to do that? I have also tried the diff --git but it tells me that "git" in unrecognized. If I use "git diff"? I get this:

fatal: ambiguous argument 'a/src/target/firmware/apps/simtest/main.c': unknown revision or path not in the working tree.

Please provide us more details.

--- On Mon, 1/17/11, Dobrica Pavlinusic <dpavlin at rot13.org> wrote:

From: Dobrica Pavlinusic <dpavlin at rot13.org>
Subject: wiki: SIMReader Was: Sim on C115 & C118
To: "Bogdan Alecu" <b.alecu at yahoo.com>
Cc: dario.lombardo at libero.it, baseband-devel at lists.osmocom.org
Date: Monday, January 17, 2011, 7:05 PM

On Mon, Jan 17, 2011 at 10:24:51AM -0800, Bogdan Alecu wrote:
> I was going to ask the same question because I have same problem with sim reader mode. However I haven't used Sylvain test. I will and come back with an update.

There seems to be sufficiant interest for using SIM reader, so I created
page on wiki which might serve as good pointer:

http://bb.osmocom.org/trac/wiki/SIMReader

-- 
Dobrica Pavlinusic? ? ? ? ? ? ???2share!2flame? ? ? ? ? ? dpavlin at rot13.org
Unix addict. Internet consultant.? ? ? ? ? ???http://www.rot13.org/~dpavlin



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110118/7b9ae11b/attachment.htm>

From peter at stuge.se  Tue Jan 18 09:16:01 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 18 Jan 2011 10:16:01 +0100
Subject: wiki: SIMReader Was: Sim on C115 & C118
In-Reply-To: <427272.80869.qm@web46209.mail.sp1.yahoo.com>
References: <20110117190558.GA2773@rot13.org>
	<427272.80869.qm@web46209.mail.sp1.yahoo.com>
Message-ID: <20110118091601.29533.qmail@stuge.se>

Bogdan Alecu wrote:
> git checkout -b testing remotes/origin/sylvain/testing you say to
> fix merge content.

I'm not sure the above is quite the right git command, but I could
also be mistaken.

In any case, after git checkout it should never be neccessary to do a
merge, so I think something is not right about your use of git.

I usually recommend the book at http://progit.org for learning Git.


//Peter



From laforge at gnumonks.org  Mon Jan 17 21:26:01 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Mon, 17 Jan 2011 22:26:01 +0100
Subject: sim reader code / master branch / ...
Message-ID: <20110117212601.GA19099@prithivi.gnumonks.org>

Hi all!

In order to avoid the most common problems, I propose exporting something like
a feature bitmask on the L1CTL, i.e.

* L1CTL user code (layer23) can send a L1CTL_GET_FEAT_REQ request
* laye1 in the phone sends a L1CTL_GET_FEAT_RESP with all the bits
  set to 1 for the features it supports
* L1CTL user code (layer23) can then check if all the features it needs are
  supported by the L1.  IF not, it can simply abort or print a warning to the
  user.

We can simply extend the size of the bitmask over time if we need more bits.

Obvious bits I would consider are:

- is this firmware compiled with TX support?
- does this firmware contain a SIM reader driver?
- does this firmware support BURST_IND?

Maybe we could also include a static header containing a compile timestamp or
the git date/revision that the firmware was built, as well as a name of the
board.

Now I know, nice idea, who will implement it?  I currently have othe
priorities, but if somebody lurking on this list is looking for a relatively
simple way to contribute back to the project (without knowing anything about
GSM!) this might be something useful you could do.

Thanks in advance,
	Harald

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From holger at freyther.de  Mon Jan 17 22:00:56 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Mon, 17 Jan 2011 23:00:56 +0100
Subject: sim reader code / master branch / ...
In-Reply-To: <20110117212601.GA19099@prithivi.gnumonks.org>
References: <20110117212601.GA19099@prithivi.gnumonks.org>
Message-ID: <4D34BC18.1070000@freyther.de>

On 01/17/2011 10:26 PM, Harald Welte wrote:

> Obvious bits I would consider are:
> 
> - is this firmware compiled with TX support?

this could become a runtime feature as well? Would we set introduce a
SET_FEAT_REQ?



From laforge at gnumonks.org  Tue Jan 18 09:51:35 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 18 Jan 2011 10:51:35 +0100
Subject: sim reader code / master branch / ...
In-Reply-To: <4D34BC18.1070000@freyther.de>
References: <20110117212601.GA19099@prithivi.gnumonks.org>
	<4D34BC18.1070000@freyther.de>
Message-ID: <20110118095135.GC14829@prithivi.gnumonks.org>

Hi,

On Mon, Jan 17, 2011 at 11:00:56PM +0100, Holger Hans Peter Freyther wrote:
 
> > Obvious bits I would consider are:
> > 
> > - is this firmware compiled with TX support?
> 
> this could become a runtime feature as well? Would we set introduce a
> SET_FEAT_REQ?

it could - but I think just to make a point and avoid any accidents, I would
like to keep an easy way how people can build (and use) firmware that will
absolutely not transmit under any circumstance.

So I think it should remain a GET request for the time being,

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From thatsit at gmx.ch  Tue Jan 18 10:26:41 2011
From: thatsit at gmx.ch (Thatist)
Date: Tue, 18 Jan 2011 11:26:41 +0100
Subject: sim reader code / master branch / ...
In-Reply-To: <20110118095135.GC14829@prithivi.gnumonks.org>
References: <20110117212601.GA19099@prithivi.gnumonks.org>
	<4D34BC18.1070000@freyther.de>
	<20110118095135.GC14829@prithivi.gnumonks.org>
Message-ID: <EF1B6A52-6AB8-4D60-A80C-74C40F02CB04@gmx.ch>

Hi

Am 18.01.2011 um 10:51 schrieb Harald Welte:

> it could - but I think just to make a point and avoid any accidents, I would
> like to keep an easy way how people can build (and use) firmware that will
> absolutely not transmit under any circumstance.
> 
> So I think it should remain a GET request for the time being,

Probably we should allow to switch TX off if it was on, but not vice versa.
This way some apps which are not designed for a TX enabled firmware could switch it off.

Matthias


From peter at stuge.se  Tue Jan 18 10:17:13 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 18 Jan 2011 11:17:13 +0100
Subject: sim reader code / master branch / ...
In-Reply-To: <20110117212601.GA19099@prithivi.gnumonks.org>
References: <20110117212601.GA19099@prithivi.gnumonks.org>
Message-ID: <20110118101713.7097.qmail@stuge.se>

Harald Welte wrote:
> In order to avoid the most common problems, I propose exporting
> something like a feature bitmask on the L1CTL, i.e.
> 
> * L1CTL user code (layer23) can send a L1CTL_GET_FEAT_REQ request
> * laye1 in the phone sends a L1CTL_GET_FEAT_RESP with all the bits
>   set to 1 for the features it supports
> * L1CTL user code (layer23) can then check if all the features it needs are
>   supported by the L1.  IF not, it can simply abort or print a warning to the
>   user.

Any point in using names for features, rather than bits?


> Obvious bits I would consider are:
> 
> - is this firmware compiled with TX support?
> - does this firmware contain a SIM reader driver?
> - does this firmware support BURST_IND?
> 
> Maybe we could also include a static header containing a compile
> timestamp or the git date/revision that the firmware was built, as
> well as a name of the board.

Yes, all good stuff.


//Peter



From laforge at gnumonks.org  Wed Jan 19 09:52:58 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Wed, 19 Jan 2011 10:52:58 +0100
Subject: sim reader code / master branch / ...
In-Reply-To: <20110118101713.7097.qmail@stuge.se>
References: <20110117212601.GA19099@prithivi.gnumonks.org>
	<20110118101713.7097.qmail@stuge.se>
Message-ID: <20110119095258.GC32226@prithivi.gnumonks.org>

Hi Peter,

On Tue, Jan 18, 2011 at 11:17:13AM +0100, Peter Stuge wrote:
> Harald Welte wrote:
> > In order to avoid the most common problems, I propose exporting
> > something like a feature bitmask on the L1CTL, i.e.
> > 
> > * L1CTL user code (layer23) can send a L1CTL_GET_FEAT_REQ request
> > * laye1 in the phone sends a L1CTL_GET_FEAT_RESP with all the bits
> >   set to 1 for the features it supports
> > * L1CTL user code (layer23) can then check if all the features it needs are
> >   supported by the L1.  IF not, it can simply abort or print a warning to the
> >   user.
> 
> Any point in using names for features, rather than bits?

well, simply define an enum for the bits in a common header file.  I really
don't want to pass around strings on the L1CTL interface, it just feels wrong ;)

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From onaips at gmail.com  Tue Jan 18 01:08:31 2011
From: onaips at gmail.com (=?ISO-8859-1?Q?Jos=E9_Luis_Pereira?=)
Date: Tue, 18 Jan 2011 01:08:31 +0000
Subject: buzzer driver
Message-ID: <AANLkTikHtNRkGrcWhopt+LS2Fm0O9nGUMiTKCXVUVG7s@mail.gmail.com>

Hi all, my name is Jose Pereira, and i'm very interested in helping you with
some code! I've wrote the buzzer driver for calypso, not so sure if will
help you of anything, but was just for experimenting :)

Anyway, i send the patch in attachement. The interface can be simply

#include <calypso/buzzer.h>

buzzer_mode_pwt(1);
 buzzer_volume(40);
        buzzer_note(NOTE(NOTE_E,OCTAVE_5));


Please let me know what do you think of the code, and in what way i can
further help.
Best regards,
-- 
Jos? Pereira
http://onaips.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110118/94ee7bf7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: buzzer_patch.diff
Type: application/octet-stream
Size: 4239 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110118/94ee7bf7/attachment.obj>

From mgr at xviews.de  Tue Jan 18 10:58:26 2011
From: mgr at xviews.de (Michael Grzeschik)
Date: Tue, 18 Jan 2011 11:58:26 +0100
Subject: [PATCH] Makefile: be more robust against toolchains without syscalls
Message-ID: <20110118105823.GA5034@jamie.key>

Several toolchains are missing syscalls provided by the libc used. For example,
if the newlib was build with the configure flag "--disable-newlib-supplied-syscalls".
To prevent the configure check for things like "_exit" in osmocom
the CFLAGS+="-nostartfiles -nodefaultlibs" helps a lot.

Signed-off-by: Michael Grzeschik <mgr at xviews.de>
Acked-by: Wolfram Sang <wolfram at the-dreams.de>

---
 src/Makefile |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/src/Makefile b/src/Makefile
index a0dea5d..b3594c1 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -39,7 +39,7 @@ shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/li
 	cd shared/libosmocore/build-target && ../configure \
 			--host=arm-elf-linux --disable-vty --enable-panic-infloop \
 			--disable-shared --disable-talloc --disable-tests \
-		CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include"
+		CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs"
 
 shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile
 	cd shared/libosmocore/build-target && make
-- 
1.7.2.3




From peter at stuge.se  Tue Jan 18 11:20:43 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 18 Jan 2011 12:20:43 +0100
Subject: [PATCH] Makefile: be more robust against toolchains without
	syscalls
In-Reply-To: <20110118105823.GA5034@jamie.key>
References: <20110118105823.GA5034@jamie.key>
Message-ID: <20110118112043.18401.qmail@stuge.se>

Michael Grzeschik wrote:
> Several toolchains are missing syscalls provided by the libc used. For example,
> if the newlib was build with the configure flag "--disable-newlib-supplied-syscalls".
> To prevent the configure check for things like "_exit" in osmocom
> the CFLAGS+="-nostartfiles -nodefaultlibs" helps a lot.
> 
> Signed-off-by: Michael Grzeschik <mgr at xviews.de>
> Acked-by: Wolfram Sang <wolfram at the-dreams.de>

Acked-by: Peter Stuge <peter at stuge.se>



From steve at steve-m.de  Tue Jan 18 12:15:49 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Tue, 18 Jan 2011 13:15:49 +0100
Subject: [PATCH] Makefile: be more robust against toolchains
	without	syscalls
In-Reply-To: <20110118112043.18401.qmail@stuge.se>
References: <20110118105823.GA5034@jamie.key>
	<20110118112043.18401.qmail@stuge.se>
Message-ID: <4D358475.7000501@steve-m.de>

Hi,

On 18.01.2011 12:20, Peter Stuge wrote:
> Michael Grzeschik wrote:
>> Several toolchains are missing syscalls provided by the libc used. For example,
>> if the newlib was build with the configure flag "--disable-newlib-supplied-syscalls".
>> To prevent the configure check for things like "_exit" in osmocom
>> the CFLAGS+="-nostartfiles -nodefaultlibs" helps a lot.
>>
>> Signed-off-by: Michael Grzeschik<mgr at xviews.de>
>> Acked-by: Wolfram Sang<wolfram at the-dreams.de>
>
> Acked-by: Peter Stuge<peter at stuge.se>

I committed it to master.

Regards,
Steve



From 775725965 at qq.com  Tue Jan 18 11:14:06 2011
From: 775725965 at qq.com (=?gbk?B?wvPM78rYzfs=?=)
Date: Tue, 18 Jan 2011 19:14:06 +0800
Subject: you   know   phone   maybe  can   made  USRP
Message-ID: <tencent_19B41624713E890532119EAC@qq.com>

do you know  Which phone  can made USRP    thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110118/2b284068/attachment.htm>

From 246tnt at gmail.com  Tue Jan 18 11:19:31 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Tue, 18 Jan 2011 12:19:31 +0100
Subject: you know phone maybe can made USRP
In-Reply-To: <tencent_19B41624713E890532119EAC@qq.com>
References: <tencent_19B41624713E890532119EAC@qq.com>
Message-ID: <AANLkTi=KjcJ6dKz-2ntJP2ZkJKn9apiBp8hX2K5fS+AC@mail.gmail.com>

> do you know? Which phone? can made USRP??? thanks

None, not possible so would you please stop asking ! ... It's the
fourth time we tell you it's not doable ...


    Sylvain



From keytwho at hotmail.com  Tue Jan 18 11:23:20 2011
From: keytwho at hotmail.com (None None)
Date: Tue, 18 Jan 2011 11:23:20 +0000
Subject: you know phone maybe can made USRP
In-Reply-To: <AANLkTi=KjcJ6dKz-2ntJP2ZkJKn9apiBp8hX2K5fS+AC@mail.gmail.com>
References: <tencent_19B41624713E890532119EAC@qq.com>,
	<AANLkTi=KjcJ6dKz-2ntJP2ZkJKn9apiBp8hX2K5fS+AC@mail.gmail.com>
Message-ID: <BLU131-W2228A27FA45B863AA45744BCF70@phx.gbl>


you're not cool ! it's For his love girl ! :)


> Date: Tue, 18 Jan 2011 12:19:31 +0100
> Subject: Re: you know phone maybe can made USRP
> From: 246tnt at gmail.com
> To: 775725965 at qq.com
> CC: baseband-devel at lists.osmocom.org
> 
> > do you know  Which phone  can made USRP    thanks
> 
> None, not possible so would you please stop asking ! ... It's the
> fourth time we tell you it's not doable ...
> 
> 
>     Sylvain
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110118/9d2c3d4a/attachment.htm>

From Andreas.Eversberg at versatel.de  Tue Jan 18 11:30:07 2011
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Tue, 18 Jan 2011 12:30:07 +0100
Subject: AW: you know phone maybe can made USRP
Message-ID: <B16317F2B1592B4492FC414114171CE604DBEE4B@FLBVEXCH01.versatel.local>

sylvain,
 
looks like you are talking to a spam bot. (harald already did earlier :)
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110118/3c1d2292/attachment.htm>

From xalexu at gmail.com  Tue Jan 18 14:36:37 2011
From: xalexu at gmail.com (xuchenyu)
Date: Tue, 18 Jan 2011 06:36:37 -0800 (PST)
Subject: Why my C118 can't send DOWNLOAD ACK?
Message-ID: <1295361397743-2280185.post@n3.nabble.com>


~/src/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123
../../target/firmware/board/compal_e88/layer1.compalram.bin
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: 2f  /
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: 1b  .
got 2 bytes from modem, data looks like: f6 02  ..
got 1 bytes from modem, data looks like: 00  .
got 1 bytes from modem, data looks like: 41  A
got 1 bytes from modem, data looks like: 01  .
got 1 bytes from modem, data looks like: 40  @
Received PROMPT1 from phone, responding with CMD
read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin):
file_size=50932, hdr_len=4, dnload_len=50939
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: 41  A
got 1 bytes from modem, data looks like: 02  .
got 1 bytes from modem, data looks like: 43  C
Received PROMPT2 from phone, starting download
handle_write(): 4096 bytes (4096/50939)
handle_write(): 4096 bytes (8192/50939)
handle_write(): 4096 bytes (12288/50939)
handle_write(): 4096 bytes (16384/50939)
handle_write(): 4096 bytes (20480/50939)
handle_write(): 4096 bytes (24576/50939)
handle_write(): 4096 bytes (28672/50939)
handle_write(): 4096 bytes (32768/50939)
handle_write(): 4096 bytes (36864/50939)
handle_write(): 4096 bytes (40960/50939)
handle_write(): 4096 bytes (45056/50939)
handle_write(): 4096 bytes (49152/50939)
handle_write(): 1787 bytes (50939/50939)
handle_write(): finished


It stopped here for very long time, I have tried with XOR and without XOR
for many times! Please help me to verify this issue! thanks very much!

-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/Why-my-C118-can-t-send-DOWNLOAD-ACK-tp2280185p2280185.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From deacon at volny.cz  Tue Jan 18 16:18:13 2011
From: deacon at volny.cz (Tomas Kopsa)
Date: Tue, 18 Jan 2011 17:18:13 +0100
Subject: Why my C118 can't send DOWNLOAD ACK?
In-Reply-To: <1295361397743-2280185.post@n3.nabble.com>
References: <1295361397743-2280185.post@n3.nabble.com>
Message-ID: <4D35BD45.9000302@volny.cz>

The simple answer is: reconnect battery in the phone and try again.

When I have experienced this process status, the phone was stucked and 
it was not possible to load even original firmware.
According actual list's discussion, this is probably a timing problem 
and it is necessary to reset phone's RAM by reconnecting battery.

Due to the buffer size, I guess you have cable with FTDI chip (check 
with lsusb), so you should probably use '-m c123' flag (without xor).

- Tomas

> ~/src/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123
> ../../target/firmware/board/compal_e88/layer1.compalram.bin
> got 1 bytes from modem, data looks like: 00  .
> got 1 bytes from modem, data looks like: 00  .
> got 1 bytes from modem, data looks like: 2f  /
> got 1 bytes from modem, data looks like: 00  .
> got 1 bytes from modem, data looks like: 1b  .
> got 2 bytes from modem, data looks like: f6 02  ..
> got 1 bytes from modem, data looks like: 00  .
> got 1 bytes from modem, data looks like: 41  A
> got 1 bytes from modem, data looks like: 01  .
> got 1 bytes from modem, data looks like: 40  @
> Received PROMPT1 from phone, responding with CMD
> read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin):
> file_size=50932, hdr_len=4, dnload_len=50939
> 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: 41  A
> got 1 bytes from modem, data looks like: 02  .
> got 1 bytes from modem, data looks like: 43  C
> Received PROMPT2 from phone, starting download
> handle_write(): 4096 bytes (4096/50939)
> handle_write(): 4096 bytes (8192/50939)
> handle_write(): 4096 bytes (12288/50939)
> handle_write(): 4096 bytes (16384/50939)
> handle_write(): 4096 bytes (20480/50939)
> handle_write(): 4096 bytes (24576/50939)
> handle_write(): 4096 bytes (28672/50939)
> handle_write(): 4096 bytes (32768/50939)
> handle_write(): 4096 bytes (36864/50939)
> handle_write(): 4096 bytes (40960/50939)
> handle_write(): 4096 bytes (45056/50939)
> handle_write(): 4096 bytes (49152/50939)
> handle_write(): 1787 bytes (50939/50939)
> handle_write(): finished
>
>
> It stopped here for very long time, I have tried with XOR and without XOR
> for many times! Please help me to verify this issue! thanks very much!
>




From lists at infosecurity.ch  Wed Jan 19 10:01:42 2011
From: lists at infosecurity.ch (Fabio Pietrosanti (naif))
Date: Wed, 19 Jan 2011 11:01:42 +0100
Subject: USB fetmocell: What's about the sofware?
Message-ID: <4D36B686.7080601@infosecurity.ch>

Hi all,

i noticed that article
http://www.eetimes.com/electronics-news/4212228/Picochip-shares-femtocell-roadmap-to-enable-complete-3G-basestation-on-a-USB-dongle?cid=NL_MicrowaveRF
speaking about 3G basestation on USB dongle.

That's really cool, i don't know about the hardware, but for sure when
those device will be out the hacking perspective would be really
interesting for projects like OpenBSC and OsmocomBB .

-naif



From dario.lombardo at libero.it  Wed Jan 19 11:45:20 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Wed, 19 Jan 2011 12:45:20 +0100
Subject: Motorola usb cable
Message-ID: <4D36CED0.8020909@libero.it>

Hello everydoby
I have Motorola-branded prolific usb cable. This cable, once inserted in 
a port, claims to be a 0307 chipset adapter, and Linux kernel doesn't 
recognize it: not working. Someone told me that Motorola has changed the 
label in those cables that claim to be 0307, but they are pl2303.
Does anyone have one of these cables working? I've tried many ways, 
including udev, to make it work, but no success. My next step is to 
recompile the kernel module, but I was wondering if someone has solved 
it in another way.
Bye
Dario.



From dario.lombardo at libero.it  Wed Jan 19 13:42:37 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Wed, 19 Jan 2011 14:42:37 +0100
Subject: Motorola usb cable
In-Reply-To: <4D36CED0.8020909@libero.it>
References: <4D36CED0.8020909@libero.it>
Message-ID: <4D36EA4D.9060007@libero.it>

On 01/19/2011 12:45 PM, Dario Lombardo wrote:
> Hello everydoby
> I have Motorola-branded prolific usb cable. This cable, once inserted 
> in a port, claims to be a 0307 chipset adapter, and Linux kernel 
> doesn't recognize it: not working. Someone told me that Motorola has 
> changed the label in those cables that claim to be 0307, but they are 
> pl2303.
> Does anyone have one of these cables working? I've tried many ways, 
> including udev, to make it work, but no success. My next step is to 
> recompile the kernel module, but I was wondering if someone has solved 
> it in another way.
> Bye
> Dario.
>
I've succeded with module patching. If someone has one of these cables 
and needs help, I can explain how to pacth (2 lines patch). Anyway, I'm 
still interested if someone has found another approach.



From deacon at volny.cz  Fri Jan 21 02:14:26 2011
From: deacon at volny.cz (Tomas Kopsa)
Date: Fri, 21 Jan 2011 03:14:26 +0100
Subject: Motorola usb cable
In-Reply-To: <4D36EA4D.9060007@libero.it>
References: <4D36CED0.8020909@libero.it> <4D36EA4D.9060007@libero.it>
Message-ID: <4D38EC02.1080403@volny.cz>

Hello Dario,

I'm interested about the patch. I have Prolific USB-jack 2,5 cable (not 
sure if its Motorola brand, details attached), everything is working for 
me but I'm trying to help one guy who's setup is not working and then 
put some helpful information on wiki.

Thanks,
Tomas

>> Hello everydoby
>> I have Motorola-branded prolific usb cable. This cable, once inserted 
>> in a port, claims to be a 0307 chipset adapter, and Linux kernel 
>> doesn't recognize it: not working. Someone told me that Motorola has 
>> changed the label in those cables that claim to be 0307, but they are 
>> pl2303.
>> Does anyone have one of these cables working? I've tried many ways, 
>> including udev, to make it work, but no success. My next step is to 
>> recompile the kernel module, but I was wondering if someone has 
>> solved it in another way.
>> Bye
>> Dario.
>>
> I've succeded with module patching. If someone has one of these cables 
> and needs help, I can explain how to pacth (2 lines patch). Anyway, 
> I'm still interested if someone has found another approach.
>
>
>

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: USB_cable.txt
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110121/babc523c/attachment.txt>

From dario.lombardo at libero.it  Fri Jan 21 08:31:06 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Fri, 21 Jan 2011 09:31:06 +0100
Subject: Motorola usb cable
In-Reply-To: <4D38EC02.1080403@volny.cz>
References: <4D36CED0.8020909@libero.it> <4D36EA4D.9060007@libero.it>
	<4D38EC02.1080403@volny.cz>
Message-ID: <4D39444A.5020205@libero.it>

Hi Tomas

On 01/21/2011 03:14 AM, Tomas Kopsa wrote:
> Device: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
> Device Descriptor:
>    bLength                18
>    bDescriptorType         1
>    bcdUSB               1.10
>    bDeviceClass            0 (Defined at Interface level)
>    bDeviceSubClass         0
>    bDeviceProtocol         0
>    bMaxPacketSize0        64
>    idVendor           0x067b Prolific Technology, Inc.
>    idProduct          0x2303 PL2303 Serial Port
This points out that your cable is ok. Both Vendor and product id are 
ok. The motorola cable is shown as idProduct=0x0307.
>    bcdDevice            3.00
>    iManufacturer           1 Prolific Technology Inc.
>    iProduct                2 USB-Serial Controller
>    iSerial                 0
>    bNumConfigurations      1
This is my dmesg using the moto cable

[ 1075.794167] usb 1-1.2: new full speed USB device using ehci_hcd and 
address 53
[ 1075.879904] usb 1-1.2: New USB device found, idVendor=067b, 
idProduct=0307
[ 1075.879910] usb 1-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 1075.879914] usb 1-1.2: Product: USB-Serial Controller
[ 1075.879917] usb 1-1.2: Manufacturer: Prolific Technology Inc.
[ 1075.879920] usb 1-1.2: SerialNumber: 06001069

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.


*** drivers/usb/serial/pl2303.h.orig    2011-01-21 09:11:21.000000000 +0100
--- drivers/usb/serial/pl2303.h    2011-01-19 13:54:30.000000000 +0100
***************
*** 21,26 ****
--- 21,27 ----
   #define PL2303_PRODUCT_ID_MMX        0x0612
   #define PL2303_PRODUCT_ID_GPRS        0x0609
   #define PL2303_PRODUCT_ID_HCR331    0x331a
+ #define PL2303_PRODUCT_ID_MOTOROLA  0x0307

   #define ATEN_VENDOR_ID        0x0557
   #define ATEN_VENDOR_ID2        0x0547

*** drivers/usb/serial/pl2303.c.orig    2011-01-21 09:11:09.000000000 +0100
--- drivers/usb/serial/pl2303.c    2011-01-19 13:58:22.000000000 +0100
***************
*** 50,55 ****
--- 50,56 ----
       { USB_DEVICE(PL2303_VENDOR_ID, PL2303_PRODUCT_ID_MMX) },
       { USB_DEVICE(PL2303_VENDOR_ID, PL2303_PRODUCT_ID_GPRS) },
       { USB_DEVICE(PL2303_VENDOR_ID, PL2303_PRODUCT_ID_HCR331) },
+     { USB_DEVICE(PL2303_VENDOR_ID, PL2303_PRODUCT_ID_MOTOROLA) },
       { USB_DEVICE(IODATA_VENDOR_ID, IODATA_PRODUCT_ID) },
       { USB_DEVICE(IODATA_VENDOR_ID, IODATA_PRODUCT_ID_RSAQ5) },
       { USB_DEVICE(ATEN_VENDOR_ID, ATEN_PRODUCT_ID) },

Remove the old module (rmmod pl2303) and insert the new one (insmod 
<yoursrckernelroot>/drivers/usbserial/pl2303). Check that the usbserial 
module is running (modprobe usbserial). If the insmod command fails, it 
depends on the wrong values put in the Makefile. Check
"vermagic" using modinfo against old and new modules.

Hope this helps.
Dario.




From wolfram at the-dreams.de  Fri Jan 21 10:09:31 2011
From: wolfram at the-dreams.de (Wolfram Sang)
Date: Fri, 21 Jan 2011 11:09:31 +0100
Subject: Motorola usb cable
In-Reply-To: <4D39444A.5020205@libero.it>
References: <4D36CED0.8020909@libero.it>
	<4D36EA4D.9060007@libero.it>	<4D38EC02.1080403@volny.cz>
	<4D39444A.5020205@libero.it>
Message-ID: <4D395B5B.1030603@the-dreams.de>

> 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>

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.

@Dario: Will you upstream your patch? (Check the whitespaces before with
checkpatch.pl)

Regards,

   Wolfram



From nkohl at web.de  Thu Jan 27 13:40:37 2011
From: nkohl at web.de (Nikolaus Kohl)
Date: Thu, 27 Jan 2011 14:40:37 +0100
Subject: Motorola usb cable
Message-ID: <FF7DE756FB654846AECA8CCBE2051B09@networkcopy>

>> 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 




From dario.lombardo at libero.it  Thu Jan 27 14:40:25 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Thu, 27 Jan 2011 15:40:25 +0100
Subject: Motorola usb cable
In-Reply-To: <FF7DE756FB654846AECA8CCBE2051B09@networkcopy>
References: <FF7DE756FB654846AECA8CCBE2051B09@networkcopy>
Message-ID: <4D4183D9.5060705@libero.it>



On 01/27/2011 02:40 PM, Nikolaus Kohl wrote:
>>
> 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):
>
Probably you have to insert it by hand (modprobe pl2303). However I 
can't make it work this way.
I have submitted the patch to the kernel maintainers, and it will be 
added in the next rc release.
Bye.



From wolfram at the-dreams.de  Thu Jan 27 16:13:50 2011
From: wolfram at the-dreams.de (Wolfram Sang)
Date: Thu, 27 Jan 2011 17:13:50 +0100
Subject: Motorola usb cable
In-Reply-To: <4D4183D9.5060705@libero.it>
References: <FF7DE756FB654846AECA8CCBE2051B09@networkcopy>
	<4D4183D9.5060705@libero.it>
Message-ID: <4D4199BE.3070000@the-dreams.de>

Hi,

> Probably you have to insert it by hand (modprobe pl2303). However I 
> can't make it work this way.

That and you have to use

cd /sys/bus/usb-serial/drivers/<driver>

because I forgot that usb-serial drivers are handled a bit special.

> I have submitted the patch to the kernel maintainers, and it will be 
> added in the next rc release.

And backported to (at least) 2.6.37, because Greg added stable to the
patch \o/

Regards,

   Wolfram




From mrs at infosec-id.com  Thu Jan 20 20:31:45 2011
From: mrs at infosec-id.com (Muhammad Rasyid Sahputra)
Date: Fri, 21 Jan 2011 03:31:45 +0700
Subject: radio is not started
Message-ID: <6398E2D0-BBA2-454C-8E29-6C75F3ACBB39@infosec-id.com>

Hi,

I tried to follow instruction on SIM Reader wiki, but seems I got different result.

OsmocomBB> enable
OsmocomBB# sim reader 1
OsmocomBB# show subscriber
Mobile Subscriber of MS '1':
 IMSI: 
 Status: U2_NOT_UPDATED  IMSI detached  LAI: invalid
 Access barred cells: no
 Access classes:

OsmocomBB# show support
Supported features of MS '1':
 Phase 2 mobile station
 R-GSM       : yes
 E-GSM       : yes
 P-GSM       : yes
 GSM900 Class: 4
 DCS 1800    : yes
 DCS Class   : 1
 CECS        : no
 VGCS        : no
 VBS         : no
 SMS         : yes
 SS_IND      : yes
 PS_CAP      : no
 CMSP        : no
 SoLSA       : no
 LCSVA       : no
 LOC_SERV    : no
 A5/1        : yes
 A5/2        : yes
 A5/3        : no
 A5/4        : no
 A5/5        : no
 A5/6        : no
 A5/7        : no
 A5/1        : yes
 Channels    : SDCCH + TCH/F + TCH/H
 Full-Rate V1: yes
 Full-Rate V2: yes
 Full-Rate V3: no
 Half-Rate V1: yes
 Half-Rate V3: no
 Min RXLEV   : -106

OsmocomBB# show ms
MS '1' is down, radio is not started
  IMEI: 000000000000000
     IMEISV: 0000000000000000
     IMEI generation: fixed
  automatic network selection state: A0 null
  cell selection state: C0 null
  radio ressource layer state: idle
  mobility management layer state: MM idle, PLMN search


from the layer23 part,


$ ./mobile -i 127.0.0.1 -d
Copyright (C) 2008-2010 ...
Contributions by ...

License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

mobile: option requires an argument -- d
VTY available on port 4247.
No Mobile Station defined, creating: MS '1'
<000e> sim.c:1206 init SIM client
<0005> gsm48_cc.c:61 init Call Control
<0001> gsm48_rr.c:4944 init Radio Ressource process
<0004> gsm48_mm.c:1220 init Mobility Management process
<0004> gsm48_mm.c:971 Selecting PLMN SEARCH state, because no SIM.
<0002> gsm322.c:3471 init PLMN process
<0003> gsm322.c:3472 init Cell Selection process
<0003> gsm322.c:3526 No stored BA list
Mobile '1' initialized, please start phone now!
<0004> subscriber.c:556 Requesting SIM file 0x2fe2
<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)
<000e> sim.c:697 go MF
<000e> sim.c:241 SELECT (file=0x3f00)
<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)


can't perform location update, and from the error, is that mean the application failed to read the simcard correctly?

and what's the meaning of "Mobile '1' initialized, please start phone now!", is it starting the phone by push the power button? if so, since the firmware is loaded I can't make the phone start like using original firmware. If i push the button, it will show message like

Found flash of 2097152 bytes at 0x0 with 2 regions
  Region 0 of 31 pages with 65536 bytes each.
  Region 1 of 8 pages with 8192 bytes each.
key=20 pressed
Powering off due to keypress.


I am using motorola c118 anw. any clue about this error?

Thanks.

Best Regards,
Rasyid
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2680 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110121/370b5c3e/attachment.bin>

From b.alecu at yahoo.com  Fri Jan 21 11:19:36 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Fri, 21 Jan 2011 03:19:36 -0800 (PST)
Subject: radio is not started
Message-ID: <467249.75258.qm@web46209.mail.sp1.yahoo.com>

I guess you have the default configuration: 
"No Mobile Station defined, creating: MS '1'"

After you start "mobile" application, select "enable" and then "write". This will write your configuration to /etc/osmocom/osmocom.cfg After that edit this file and set from no sim to sim reader. Restart the mobile application and it should work.



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110121/2b70fa3d/attachment.htm>

From mrs at infosec-id.com  Fri Jan 21 12:51:02 2011
From: mrs at infosec-id.com (Muhammad Rasyid Sahputra)
Date: Fri, 21 Jan 2011 19:51:02 +0700
Subject: radio is not started
In-Reply-To: <467249.75258.qm@web46209.mail.sp1.yahoo.com>
References: <467249.75258.qm@web46209.mail.sp1.yahoo.com>
Message-ID: <2CA8BB43-D48D-4544-B49C-B73DCEF2FE0A@infosec-id.com>

I just newcomer in osmocombb so I guess still miss various concept here. I tried to clarify (several question mark below) the stuff which I hope don't bore anyone here :).

1). sylvain branch: yes. I am using sylvain test branch and uncomment the TX part as written in SIM Reader wiki for firmware Makefile.

2). osmocon

This is the utility to upload osmocombb firmware from laptop to my motorola c118 through usb cable. 

and here's the output I got,

$ ./osmocon -p /dev/tty.usbserial -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin

...
...
Received PROMPT1 from phone, responding with CMD
read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=16864, hdr_len=4, dnload_len=16871
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: 41  A
got 1 bytes from modem, data looks like: 02  .
got 1 bytes from modem, data looks like: 43  C
Received PROMPT2 from phone, starting download
handle_write(): 1023 bytes (1023/16871)
handle_write(): 1024 bytes (2047/16871)
handle_write(): 1024 bytes (3071/16871)
handle_write(): 1024 bytes (4095/16871)
handle_write(): 1024 bytes (5119/16871)
handle_write(): 1024 bytes (6143/16871)
handle_write(): 1024 bytes (7167/16871)
handle_write(): 1024 bytes (8191/16871)
handle_write(): 1024 bytes (9215/16871)
handle_write(): 1024 bytes (10239/16871)
handle_write(): 1024 bytes (11263/16871)
handle_write(): 1024 bytes (12287/16871)
handle_write(): 1024 bytes (13311/16871)
handle_write(): 1024 bytes (14335/16871)
handle_write(): 1024 bytes (15359/16871)
handle_write(): 1024 bytes (16383/16871)
handle_write(): 488 bytes (16871/16871)
handle_write(): finished
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: 41  A
got 1 bytes from modem, data looks like: 03  .
got 1 bytes from modem, data looks like: 42  B
Received DOWNLOAD ACK from phone, your code is running now!
Received DOWNLOAD ACK from phone, your code is running now!


OSMOCOM Loader (revision osmocon_v0.0.0-757-gc4483bf-modified)
======================================================================
Running on compal_e88 in environment compalram
Found flash of 2097152 bytes at 0x0 with 2 regions


Is above output good enough to think that firmware is already downloaded by motorola c118 and the osmocombb firmware is running well there?


3). mobile application

since layer1 stuff is handled by osmocombb firmware which run on the phone by now, mobile application will handle layer2 and layer3. I believe this mean, mobile application will perform logical process of GSM call flow for full location update to the operator network. But to do so, Ki information is needed. And this is where sim reader feature come into the play?to read the Ki (and also IMSI?) information from the operator simcard?

here's the output I got,

$ sudo ./mobile -i 127.0.0.1
Password:
Copyright (C) 2008-2010 ...
Contributions by ...

License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

<000e> sim.c:1206 init SIM client
<0005> gsm48_cc.c:61 init Call Control
<0001> gsm48_rr.c:4944 init Radio Ressource process
<0004> gsm48_mm.c:1220 init Mobility Management process
<0004> gsm48_mm.c:971 Selecting PLMN SEARCH state, because no SIM.
<0002> gsm322.c:3471 init PLMN process
<0003> gsm322.c:3472 init Cell Selection process
Mobile '1' initialized, please start phone now!
VTY available on port 4247.


At this point, the mobile application communicate to the osmocombb firmware through /tmp/osmocom_l2 socket, while also open VTY connection on port 4247 right?

In other words, to communicate with mobile application which will send command to the firmware in my motorola c118 through /tmp/osmocom_l2, we can use telnet to localhost port 4247?


4) VTY communication

$ telnet localhost 4247
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying fe80::1...
telnet: connect to address fe80::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Welcome to the OpenBSC Control interface
OsmocomBB> en
OsmocomBB# show subs
Mobile Subscriber of MS '1':
 No SIM present.


at this state, no sim present yet. and we can ask mobile communication to read the simcard using this command:

OsmocomBB# sim read 1

after running this command, if I see from console where mobile application run earlier, it shows the output:

...
...
<0004> subscriber.c:556 Requesting SIM file 0x2fe2
<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)
<000e> sim.c:697 go MF
<000e> sim.c:241 SELECT (file=0x3f00)
<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)


and if I put command from VTY to show information about subscriber saved inside my simcard,

OsmocomBB# show subs 1
Mobile Subscriber of MS '1':
 IMSI: 
 Status: U2_NOT_UPDATED  IMSI detached  LAI: invalid
 Access barred cells: no
 Access classes:

At this point, I come into conclusion that the mobile application tried to read the simcard (this is shown by <000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)) but failed as it can't show what is the IMSI of my simcard?thus location update process will failed since information such as IMSI and Ki was failed to be retrieved?


5) Mobile application configuration

I think the VTY shell is similar to router configuration, where it could load previous saved simcard configuration, or MS name to be used, etc. Thus modify the MS name won't change the situation as locup is still failed?



Please Advise.

Thanks.


Regards,
Rasyid

On Jan 21, 2011, at 6:19 PM, Bogdan Alecu wrote:

> I guess you have the default configuration: 
> "No Mobile Station defined, creating: MS '1'"
> 
> After you start "mobile" application, select "enable" and then "write". This will write your configuration to /etc/osmocom/osmocom.cfg After that edit this file and set from no sim to sim reader. Restart the mobile application and it should work.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110121/1087c64a/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2680 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110121/1087c64a/attachment.bin>

From b.alecu at yahoo.com  Fri Jan 21 12:56:37 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Fri, 21 Jan 2011 04:56:37 -0800 (PST)
Subject: radio is not started
In-Reply-To: <2CA8BB43-D48D-4544-B49C-B73DCEF2FE0A@infosec-id.com>
Message-ID: <117341.85415.qm@web46204.mail.sp1.yahoo.com>

At step one run "layer1.compalram.bin"

--- On Fri, 1/21/11, Muhammad Rasyid Sahputra <mrs at infosec-id.com> wrote:

From: Muhammad Rasyid Sahputra <mrs at infosec-id.com>
Subject: Re: radio is not started
To: "Bogdan Alecu" <b.alecu at yahoo.com>
Cc: baseband-devel at lists.osmocom.org
Date: Friday, January 21, 2011, 12:51 PM

I just newcomer in osmocombb so I guess still miss various concept here. I tried to clarify (several question mark below) the stuff which I hope don't bore anyone here :).
1). sylvain branch: yes. I am using sylvain test branch and uncomment the TX part as written in SIM Reader wiki for firmware Makefile.
2). osmocon
This is the utility to upload osmocombb firmware from laptop to my motorola c118 through usb cable.?
and here's the output I got,
$ ./osmocon -p /dev/tty.usbserial -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin
......Received PROMPT1 from phone, responding with CMDread_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=16864, hdr_len=4, dnload_len=16871got 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: 41 ?Agot 1 bytes from modem, data looks like: 02 ?.got 1 bytes from modem, data looks like: 43 ?CReceived PROMPT2 from phone, starting downloadhandle_write(): 1023 bytes (1023/16871)handle_write(): 1024 bytes (2047/16871)handle_write(): 1024 bytes (3071/16871)handle_write(): 1024 bytes (4095/16871)handle_write(): 1024 bytes (5119/16871)handle_write(): 1024 bytes (6143/16871)handle_write(): 1024 bytes (7167/16871)handle_write(): 1024 bytes (8191/16871)handle_write(): 1024 bytes (9215/16871)handle_write(): 1024 bytes (10239/16871)handle_write(): 1024 bytes
 (11263/16871)handle_write(): 1024 bytes (12287/16871)handle_write(): 1024 bytes (13311/16871)handle_write(): 1024 bytes (14335/16871)handle_write(): 1024 bytes (15359/16871)handle_write(): 1024 bytes (16383/16871)handle_write(): 488 bytes (16871/16871)handle_write(): finishedgot 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: 41 ?Agot 1 bytes from modem, data looks like: 03 ?.got 1 bytes from modem, data looks like: 42 ?BReceived DOWNLOAD ACK from phone, your code is running now!Received DOWNLOAD ACK from phone, your code is running now!

OSMOCOM Loader (revision osmocon_v0.0.0-757-gc4483bf-modified)======================================================================Running on compal_e88 in environment compalramFound flash of 2097152 bytes at 0x0 with 2 regions

Is above output good enough to think that firmware is already downloaded by motorola c118 and the osmocombb firmware is running well there?

3). mobile application
since layer1 stuff is handled by osmocombb firmware which run on the phone by now, mobile application will handle layer2 and layer3. I believe this mean, mobile application will perform logical process of GSM call flow for full location update to the operator network. But to do so, Ki information is needed. And this is where sim reader feature come into the play?to read the Ki (and also IMSI?) information from the operator simcard?
here's the output I got,
$ sudo ./mobile -i 127.0.0.1Password:Copyright (C) 2008-2010 ...Contributions by ...
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html>This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law.
<000e> sim.c:1206 init SIM client<0005> gsm48_cc.c:61 init Call Control<0001> gsm48_rr.c:4944 init Radio Ressource process<0004> gsm48_mm.c:1220 init Mobility Management process<0004> gsm48_mm.c:971 Selecting PLMN SEARCH state, because no SIM.<0002> gsm322.c:3471 init PLMN process<0003> gsm322.c:3472 init Cell Selection processMobile '1' initialized, please start phone now!VTY available on port 4247.

At this point, the mobile application communicate to the osmocombb firmware through /tmp/osmocom_l2 socket, while also open VTY connection on port 4247 right?
In other words, to communicate with mobile application which will send command to the firmware in my motorola c118 through /tmp/osmocom_l2, we can use telnet to localhost port 4247?

4) VTY communication
$ telnet localhost 4247Trying ::1...telnet: connect to address ::1: Connection refusedTrying fe80::1...telnet: connect to address fe80::1: Connection refusedTrying 127.0.0.1...Connected to localhost.Escape character is '^]'.Welcome to the OpenBSC Control interfaceOsmocomBB> enOsmocomBB# show subsMobile Subscriber of MS '1':?No SIM present.

at this state, no sim present yet. and we can ask mobile communication to read the simcard using this command:
OsmocomBB# sim read 1
after running this command, if I see from console where mobile application run earlier, it shows the output:
......<0004> subscriber.c:556 Requesting SIM file 0x2fe2<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:697 go MF<000e> sim.c:241 SELECT (file=0x3f00)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)

and if I put command from VTY to show information about subscriber saved inside my simcard,
OsmocomBB# show subs 1Mobile Subscriber of MS '1':?IMSI:??Status: U2_NOT_UPDATED ?IMSI detached ?LAI: invalid?Access barred cells: no?Access classes:
At this point, I come into conclusion that the mobile application tried to read the simcard (this is shown by?<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)) but failed as it can't show what is the IMSI of my simcard?thus location update process will failed since information such as IMSI and Ki was failed to be retrieved?

5) Mobile application configuration
I think the VTY shell is similar to router configuration, where it could load previous saved simcard configuration, or MS name to be used, etc. Thus modify the MS name won't change the situation as locup is still failed?


Please Advise.
Thanks.

Regards,Rasyid
On Jan 21, 2011, at 6:19 PM, Bogdan Alecu wrote:
I guess you have the default configuration: 
"No Mobile Station defined, creating: MS '1'"

After you start "mobile" application, select "enable" and then "write". This will write your configuration to /etc/osmocom/osmocom.cfg After that edit this file and set from no sim to sim reader. Restart the mobile application and it should work.



      



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110121/151517e9/attachment.htm>

From mrs at infosec-id.com  Fri Jan 21 16:03:46 2011
From: mrs at infosec-id.com (Muhammad Rasyid Sahputra)
Date: Fri, 21 Jan 2011 23:03:46 +0700
Subject: radio is not started
In-Reply-To: <117341.85415.qm@web46204.mail.sp1.yahoo.com>
References: <117341.85415.qm@web46204.mail.sp1.yahoo.com>
Message-ID: <56244FD9-B1F8-4106-BAA2-031CBD0DBA16@infosec-id.com>

THANKS!!! :)

still no location update yet, but at least radio is working now from the dump....


<0001> gsm48_rr.c:1672 New SYSTEM INFORMATION 2
<0003> gsm322.c:2053 New BA list (mcc=510 mnc=01  Indonesia, INDOSAT).
<0003> gsm322.c:1597 Cell frequency 46: Cell found, (rxlev=-53 mcc=510 mnc=01 lac=141e  Indonesia, INDOSAT)


On Jan 21, 2011, at 7:56 PM, Bogdan Alecu wrote:

> At step one run "layer1.compalram.bin"
> 
> --- On Fri, 1/21/11, Muhammad Rasyid Sahputra <mrs at infosec-id.com> wrote:
> 
> From: Muhammad Rasyid Sahputra <mrs at infosec-id.com>
> Subject: Re: radio is not started
> To: "Bogdan Alecu" <b.alecu at yahoo.com>
> Cc: baseband-devel at lists.osmocom.org
> Date: Friday, January 21, 2011, 12:51 PM
> 
> I just newcomer in osmocombb so I guess still miss various concept here. I tried to clarify (several question mark below) the stuff which I hope don't bore anyone here :).
> 
> 1). sylvain branch: yes. I am using sylvain test branch and uncomment the TX part as written in SIM Reader wiki for firmware Makefile.
> 
> 2). osmocon
> 
> This is the utility to upload osmocombb firmware from laptop to my motorola c118 through usb cable. 
> 
> and here's the output I got,
> 
> $ ./osmocon -p /dev/tty.usbserial -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110121/7f1f0ea1/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2680 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110121/7f1f0ea1/attachment.bin>

From steve at steve-m.de  Thu Jan 20 21:49:36 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Thu, 20 Jan 2011 22:49:36 +0100
Subject: Pirelli DP-L10 support, steve-m/testing branch
Message-ID: <4D38ADF0.8000901@steve-m.de>

Hi all,

last weekend I have grinded down a DP-L10 pcb and traced the TSPACT
wiring of this board. I've added support for this phone, along with a
few other changes in my branch steve-m/testing.

Changes include:

* Add support for Pirelli DP-L10
* Add TX support for the gta0x devices
* separate board images for the Compal E86 (Motorola C139/C140)
   (display/keypad backlight now works by default)

If anyone wants to test those changes (especially the freerunner TX 
support, since I have no freerunner), please feel free to do so. I 
tested the other changes and didn't find any regressions, so if no one 
else does, we can merge it to master soon.

One thing I noticed during testing: The C139/C140 seem to have a 
different SYSTEM_INHERENT_GAIN, I compared the RX levels of several 
C118/C123/C155 with several C139/C140, and the reported rx level was 
always at around 18-20dBm worse than with the C123.

Regards,
Steve



From steve at steve-m.de  Thu Jan 20 21:55:06 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Thu, 20 Jan 2011 22:55:06 +0100
Subject: Pirelli DP-L10 support, steve-m/testing branch
In-Reply-To: <4D38ADF0.8000901@steve-m.de>
References: <4D38ADF0.8000901@steve-m.de>
Message-ID: <4D38AF3A.4040405@steve-m.de>

On 20.01.2011 22:49, Steve Markgraf wrote:

> * Add support for Pirelli DP-L10

One thing I forgot:

I've created a wiki page for the DP-L10:
http://bb.osmocom.org/trac/wiki/PirelliDPL10

Regards,
Steve



From mattjevans at btinternet.com  Fri Jan 21 21:08:36 2011
From: mattjevans at btinternet.com (MATTHEW EVANS)
Date: Fri, 21 Jan 2011 21:08:36 +0000 (GMT)
Subject: Non Standard Baud Rates?
Message-ID: <315934.53060.qm@web86601.mail.ird.yahoo.com>

Hi,

I'm trying to get the burst_ind branch working at the higher speed baud rates. I 
have a USB to Serial FTDI Cable (FT232R) plus the T191. This setup works fine 
with the main trunk of osmocombb. When I fire up osmocon, layer1 appears to 
download to the phone and runs successfully. Osmocon then logs 'Received 
DOWNLOAD ACK from phone, your code is running now!'. The phone has layer1.bin 
displayed as usual. However it goes no further and just hangs.

Could anyone please give any advice on what to try next?

Thanks,

Matt.



From leonardo.nve at gmail.com  Sat Jan 22 12:53:21 2011
From: leonardo.nve at gmail.com (Leonardo)
Date: Sat, 22 Jan 2011 12:53:21 +0000 (UTC)
Subject: Non Standard Baud Rates?
References: <315934.53060.qm@web86601.mail.ird.yahoo.com>
Message-ID: <loom.20110122T135056-532@post.gmane.org>

I have the same problem, normal branch and testing branch works perfect.
I tried some code modifications but no one worked.




From xalexu at gmail.com  Sat Jan 22 08:09:55 2011
From: xalexu at gmail.com (xuchenyu)
Date: Sat, 22 Jan 2011 00:09:55 -0800 (PST)
Subject: Why my phone can't attach the network?
Message-ID: <1295683795751-2307332.post@n3.nabble.com>


Thanks to Tomas and ton, I can run osmocombb on the phone. But the phone
can't attach the network, can't make a call, can't recognise the SIM card. I
found that this was no BCCH received in wireshark. 

And when I type some command via telnet localhost, it always output "Command
incomplete" 

Anybody can give me some solution? Thanks!  
-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/Why-my-phone-can-t-attach-the-network-tp2307332p2307332.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From mrs at infosec-id.com  Sat Jan 22 08:40:08 2011
From: mrs at infosec-id.com (Muhammad Rasyid Sahputra)
Date: Sat, 22 Jan 2011 15:40:08 +0700
Subject: Why my phone can't attach the network?
In-Reply-To: <1295683795751-2307332.post@n3.nabble.com>
References: <1295683795751-2307332.post@n3.nabble.com>
Message-ID: <E3442C62-5A6F-4521-9C53-10192802DC94@infosec-id.com>

While you're in the VTY session, you can always type question mark ("?") after each command, i.e : osmocombb> show ?

it will show you how to complete the command.

On Jan 22, 2011, at 3:09 PM, xuchenyu wrote:

> 
> Thanks to Tomas and ton, I can run osmocombb on the phone. But the phone
> can't attach the network, can't make a call, can't recognise the SIM card. I
> found that this was no BCCH received in wireshark. 
> 
> And when I type some command via telnet localhost, it always output "Command
> incomplete" 
> 
> Anybody can give me some solution? Thanks!  
> -- 
> View this message in context: http://baseband-devel.722152.n3.nabble.com/Why-my-phone-can-t-attach-the-network-tp2307332p2307332.html
> Sent from the baseband-devel mailing list archive at Nabble.com.
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2680 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110122/a609c6aa/attachment.bin>

From tommy.nimare at gmail.com  Sun Jan 23 05:18:43 2011
From: tommy.nimare at gmail.com (Tommy R.)
Date: Sun, 23 Jan 2011 00:18:43 -0500
Subject: serial cable
Message-ID: <AANLkTimP8JmK0Df3mO4bv0z69SDjwjMMSK7AP_qVDhXL@mail.gmail.com>

Hey, I ordered the serial cable coming from dealextreme and it has not
arrived yet. I noticed today that the link was taken off the wiki due to it
not being at TTL levels. I was wondering if I bought a Nokia serial cable
(the ones that have the prolific chips in them) which runs at 3.3v out of
the box, could I just connect the tx and rx pins to the cable I had bought
and it would possibly work or would that be a bad idea and I should cut my
losses and kill the order.

-- 
-Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110123/10bdeb8f/attachment.htm>

From maciej.grela at gmail.com  Sun Jan 23 21:10:10 2011
From: maciej.grela at gmail.com (Maciej Grela)
Date: Sun, 23 Jan 2011 22:10:10 +0100
Subject: serial cable
In-Reply-To: <AANLkTimP8JmK0Df3mO4bv0z69SDjwjMMSK7AP_qVDhXL@mail.gmail.com>
References: <AANLkTimP8JmK0Df3mO4bv0z69SDjwjMMSK7AP_qVDhXL@mail.gmail.com>
Message-ID: <AANLkTimc6fPb+EcQ1XzD=RHwFh0F16Psn+TGguSXiOkd@mail.gmail.com>

2011/1/23 Tommy R. <tommy.nimare at gmail.com>:
> Hey, I ordered the serial cable coming from dealextreme and it has not
> arrived yet. I noticed today that the link was taken off the wiki due to it
> not being at TTL levels. I was wondering if I bought a Nokia serial cable
> (the ones that have the prolific chips in them) which runs at 3.3v out of
> the box, could I just connect the tx and rx pins to the cable I had bought
> and it would possibly work or would that be a bad idea and I should cut my
> losses and kill the order.
>

Yes, this will work. I made my cable from an Ericsson USB cable.

Br,
Maciej Grela



From technosabby at gmail.com  Sun Jan 23 05:30:35 2011
From: technosabby at gmail.com (Marten Christophe)
Date: Sun, 23 Jan 2011 05:30:35 +0000
Subject: Sniff Code..shown @chao conf.. CCC
Message-ID: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>

Hello All,

Pls help me, any one who can

Kindly give me code or even binary file for sniff code which Sylvain
demonstrated in chao meeting,  it will solve my purpose,
i can See, in video  he  made the same interface to tune to a ARFCN,
TS , and hopping sequence as i requested a long time back to mailling
list  It will
be great help for poor students.

my project don't required any a5 creaking so it wont be used as unlawful means.
so far i have arranged 12 USRP1 to run openBTS.

I just wanted to do the same, which Sylvain have  done in video @ chao
presentation, except cracking the encryption as i will configure
openBTS as a5/0
coz it?s education transmission not necessary to encrypt kindly do me a
favour in shake of charity.

Pls reply to my query pls help me in the shake of poor students.
I promise will keep that code secret and will not disclose to any one else.
or pls advise me how i can modify existing code up to that level.

Kindly  reply on my request , can you pls provide me Sniff software?
it will help me allot, my NGO can deploy a pilot project at least

Kind Regards,



From peter at stuge.se  Sun Jan 23 06:08:55 2011
From: peter at stuge.se (Peter Stuge)
Date: Sun, 23 Jan 2011 07:08:55 +0100
Subject: Sniff Code..shown @chao conf.. CCC
In-Reply-To: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>
References: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>
Message-ID: <20110123060855.19462.qmail@stuge.se>

Marten Christophe wrote:
> Kindly give me code or even binary file for sniff code which
> Sylvain demonstrated in chao meeting,

Kindly read
http://lists.osmocom.org/pipermail/baseband-devel/2010-December/000912.html


> Pls reply 
> pls help
> or pls advise
> Kindly  reply
> pls provide

I'm sure you realize that this sounds like a nagging child.

I think one can always beenfit from considering the group that one is
communicating in. Many quite skilled developers work together in this
and most other open source projects, and the way to get things that
one wants is never to nag.

At best one will be silently ignored, at worst one will get banned.
In any case, the impression people will be left with suffers
dramatically from any behavior not clearly trying to further the
project. I have seen this happen in many projects, and many times I
am sure that it is caused mainly by problems in communication, such
as language barriers, rhetoric skill, and so on. Other times it is
simply because someone is stupid. (I don't know you at all well
enough to say if that holds for you, probably not, but your emails
may cause people to think so.)


> advise me how i can modify existing code up to that level.
..
> it will help me allot, my NGO can deploy a pilot project at least

I guess you are still working on the idea that developers here fairly
clearly judged as not being really worthwhile. And now you plea for
people to go out of their way to support it. That demonstrates a lack
of understanding for open source projects, where *you* are always
responsible for fulfilling *your* needs. Of course you can ask others
to do stuff, by politely making suggestions, but you must respect if
they have no interest in your ideas.

But nothing stops you from moving ahead on your own and proving
everyone wrong! In fact that is one great thing about open source.
When going against the flow of course you must be prepared to not
get much, if any, help.

Maybe Sylvain will be interested in licensing some work to your NGO
for a pilot project - if so I guess he will get in touch with you -
but honestly I doubt that, based on nothing but how you behave on
this mailing list. :\

Besides the tone in your email you have hijacked the thread about the
Osmocom logo request. This suggests unfamiliarity with mailing list
etiquette, which also hurts your standing in the project rather
severely. One could think this should not be so important, because it
is a technicality, but on the other hand we are all technicians, and
the technicalities are there for a reason; they allow the most
efficient communication. So by not knowing the etiquette you are
creating inefficiencies for every mailing list subscriber and for the
afterworld (in the archives) which as I am sure you understand is
very strongly frowned upon.


Perhaps you could benefit from the recently announced TETRA code..

http://tetra.osmocom.org/trac/

Maybe it fits your application better than plain GSM, as you seem to
be on good terms with the regulatory body in your deployment area.


Kind regards

//Peter



From azet at azet.org  Sun Jan 23 19:02:45 2011
From: azet at azet.org (Aaron Zauner)
Date: Sun, 23 Jan 2011 20:02:45 +0100
Subject: Sniff Code..shown @chao conf.. CCC
In-Reply-To: <20110123060855.19462.qmail@stuge.se>
References: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>
	<20110123060855.19462.qmail@stuge.se>
Message-ID: <AANLkTi=q6F4mnwYssFZ3ign-8yk185DVtLAOspA-EaXE@mail.gmail.com>

What poor students are you talking of?

azet

On 1/23/11, Peter Stuge <peter at stuge.se> wrote:
> Marten Christophe wrote:
>> Kindly give me code or even binary file for sniff code which
>> Sylvain demonstrated in chao meeting,
>
> Kindly read
> http://lists.osmocom.org/pipermail/baseband-devel/2010-December/000912.html
>
>
>> Pls reply
>> pls help
>> or pls advise
>> Kindly  reply
>> pls provide
>
> I'm sure you realize that this sounds like a nagging child.
>
> I think one can always beenfit from considering the group that one is
> communicating in. Many quite skilled developers work together in this
> and most other open source projects, and the way to get things that
> one wants is never to nag.
>
> At best one will be silently ignored, at worst one will get banned.
> In any case, the impression people will be left with suffers
> dramatically from any behavior not clearly trying to further the
> project. I have seen this happen in many projects, and many times I
> am sure that it is caused mainly by problems in communication, such
> as language barriers, rhetoric skill, and so on. Other times it is
> simply because someone is stupid. (I don't know you at all well
> enough to say if that holds for you, probably not, but your emails
> may cause people to think so.)
>
>
>> advise me how i can modify existing code up to that level.
> ..
>> it will help me allot, my NGO can deploy a pilot project at least
>
> I guess you are still working on the idea that developers here fairly
> clearly judged as not being really worthwhile. And now you plea for
> people to go out of their way to support it. That demonstrates a lack
> of understanding for open source projects, where *you* are always
> responsible for fulfilling *your* needs. Of course you can ask others
> to do stuff, by politely making suggestions, but you must respect if
> they have no interest in your ideas.
>
> But nothing stops you from moving ahead on your own and proving
> everyone wrong! In fact that is one great thing about open source.
> When going against the flow of course you must be prepared to not
> get much, if any, help.
>
> Maybe Sylvain will be interested in licensing some work to your NGO
> for a pilot project - if so I guess he will get in touch with you -
> but honestly I doubt that, based on nothing but how you behave on
> this mailing list. :\
>
> Besides the tone in your email you have hijacked the thread about the
> Osmocom logo request. This suggests unfamiliarity with mailing list
> etiquette, which also hurts your standing in the project rather
> severely. One could think this should not be so important, because it
> is a technicality, but on the other hand we are all technicians, and
> the technicalities are there for a reason; they allow the most
> efficient communication. So by not knowing the etiquette you are
> creating inefficiencies for every mailing list subscriber and for the
> afterworld (in the archives) which as I am sure you understand is
> very strongly frowned upon.
>
>
> Perhaps you could benefit from the recently announced TETRA code..
>
> http://tetra.osmocom.org/trac/
>
> Maybe it fits your application better than plain GSM, as you seem to
> be on good terms with the regulatory body in your deployment area.
>
>
> Kind regards
>
> //Peter
>
>



From azet at azet.org  Sun Jan 23 19:47:23 2011
From: azet at azet.org (Aaron Zauner)
Date: Sun, 23 Jan 2011 20:47:23 +0100
Subject: Sniff Code..shown @chao conf.. CCC
In-Reply-To: <AANLkTike1eo_YAiYhCHtw-meuM3tjw2cCYCme_am+svx@mail.gmail.com>
References: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>
	<20110123060855.19462.qmail@stuge.se>
	<AANLkTi=q6F4mnwYssFZ3ign-8yk185DVtLAOspA-EaXE@mail.gmail.com>
	<AANLkTi=-81edMAVtYORUYmYgLnJU=r1ewzPD5LutFTKF@mail.gmail.com>
	<AANLkTike1eo_YAiYhCHtw-meuM3tjw2cCYCme_am+svx@mail.gmail.com>
Message-ID: <AANLkTimUepj3XTmanmJCP1nPBxTy8OuFjfP-TsxmZNac@mail.gmail.com>

Oh, i also found this:
http://permalink.gmane.org/gmane.comp.gnu.radio.general/31145

-> http://en.wikipedia.org/wiki/Manoj_Kumar

lol.

so long,
azet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110123/e79a03b9/attachment.htm>

From technosabby at gmail.com  Mon Jan 24 15:57:28 2011
From: technosabby at gmail.com (Marten Christophe)
Date: Mon, 24 Jan 2011 15:57:28 +0000
Subject: Sniff Code..shown @chao conf.. CCC
In-Reply-To: <AANLkTimUepj3XTmanmJCP1nPBxTy8OuFjfP-TsxmZNac@mail.gmail.com>
References: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>
	<20110123060855.19462.qmail@stuge.se>
	<AANLkTi=q6F4mnwYssFZ3ign-8yk185DVtLAOspA-EaXE@mail.gmail.com>
	<AANLkTi=-81edMAVtYORUYmYgLnJU=r1ewzPD5LutFTKF@mail.gmail.com>
	<AANLkTike1eo_YAiYhCHtw-meuM3tjw2cCYCme_am+svx@mail.gmail.com>
	<AANLkTimUepj3XTmanmJCP1nPBxTy8OuFjfP-TsxmZNac@mail.gmail.com>
Message-ID: <AANLkTi=jrLikBY5XxDKmxiTetJw-tr=O+jiNpcz3ezUX@mail.gmail.com>

Hello All,

Here i feel to introduce myself again as many are commenting on me.

I'm a PhD Student also associated to a NGO who works for education in
poor and rurale students located at remote location,
 I'm trying to develop a distance teaching system with help of modern
communication techniques but with the equipments which are cheapest
and even available from salvaged , second-hand market ,
repaired-shoppes or  resale store.

second hand Motorola C1xx   series handsets are available here in bulk
within $ 2-4 price, and no end user equipment can be as cheap as it
is.
 OK.. openBTS USRP1 and Motorola C1xx series MS will make cheapest and
reliable  two way communication i have estimated
so pls don't laugh at me.
My THESIS of PhD also same , hence it is mutual benifit of NGO, me and
remotely locating poor children

Mr. Sylvain, I  will again request you to provide sniff code which you
demonstrated @ chao conf.

Kind Regards,

On Sun, Jan 23, 2011 at 7:47 PM, Aaron Zauner <azet at azet.org> wrote:
> Oh, i also found this:
> http://permalink.gmane.org/gmane.comp.gnu.radio.general/31145
>
> -> http://en.wikipedia.org/wiki/Manoj_Kumar
>
> lol.
>
> so long,
> azet
>



From francisg at fnop.net  Mon Jan 24 16:01:32 2011
From: francisg at fnop.net (Francisco Guerreiro)
Date: Mon, 24 Jan 2011 16:01:32 +0000
Subject: Sniff Code..shown @chao conf.. CCC
In-Reply-To: <AANLkTi=jrLikBY5XxDKmxiTetJw-tr=O+jiNpcz3ezUX@mail.gmail.com>
References: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>
	<20110123060855.19462.qmail@stuge.se>
	<AANLkTi=q6F4mnwYssFZ3ign-8yk185DVtLAOspA-EaXE@mail.gmail.com>
	<AANLkTi=-81edMAVtYORUYmYgLnJU=r1ewzPD5LutFTKF@mail.gmail.com>
	<AANLkTike1eo_YAiYhCHtw-meuM3tjw2cCYCme_am+svx@mail.gmail.com>
	<AANLkTimUepj3XTmanmJCP1nPBxTy8OuFjfP-TsxmZNac@mail.gmail.com>
	<AANLkTi=jrLikBY5XxDKmxiTetJw-tr=O+jiNpcz3ezUX@mail.gmail.com>
Message-ID: <AANLkTinuBdU_obt+xWLMKpn=na-N=hS3ktckFek2gxWY@mail.gmail.com>

why do you need the sniff codes to create a "distance teaching system"?

if you have the openBTS working you can use normal phones with it. i don't
see how does it relate to GSM Sniffing at all...

then again, I'm not a PhD student

Cheers,
Francisco

On Mon, Jan 24, 2011 at 3:57 PM, Marten Christophe <technosabby at gmail.com>wrote:

> Hello All,
>
> Here i feel to introduce myself again as many are commenting on me.
>
> I'm a PhD Student also associated to a NGO who works for education in
> poor and rurale students located at remote location,
>  I'm trying to develop a distance teaching system with help of modern
> communication techniques but with the equipments which are cheapest
> and even available from salvaged , second-hand market ,
> repaired-shoppes or  resale store.
>
> second hand Motorola C1xx   series handsets are available here in bulk
> within $ 2-4 price, and no end user equipment can be as cheap as it
> is.
>  OK.. openBTS USRP1 and Motorola C1xx series MS will make cheapest and
> reliable  two way communication i have estimated
> so pls don't laugh at me.
> My THESIS of PhD also same , hence it is mutual benifit of NGO, me and
> remotely locating poor children
>
> Mr. Sylvain, I  will again request you to provide sniff code which you
> demonstrated @ chao conf.
>
> Kind Regards,
>
> On Sun, Jan 23, 2011 at 7:47 PM, Aaron Zauner <azet at azet.org> wrote:
> > Oh, i also found this:
> > http://permalink.gmane.org/gmane.comp.gnu.radio.general/31145
> >
> > -> http://en.wikipedia.org/wiki/Manoj_Kumar
> >
> > lol.
> >
> > so long,
> > azet
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110124/f83fc56f/attachment.htm>

From technosabby at gmail.com  Thu Jan 27 03:23:42 2011
From: technosabby at gmail.com (Marten Christophe)
Date: Thu, 27 Jan 2011 03:23:42 +0000
Subject: Sniff Code..shown @chao conf.. CCC
In-Reply-To: <AANLkTinuBdU_obt+xWLMKpn=na-N=hS3ktckFek2gxWY@mail.gmail.com>
References: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>
	<20110123060855.19462.qmail@stuge.se>
	<AANLkTi=q6F4mnwYssFZ3ign-8yk185DVtLAOspA-EaXE@mail.gmail.com>
	<AANLkTi=-81edMAVtYORUYmYgLnJU=r1ewzPD5LutFTKF@mail.gmail.com>
	<AANLkTike1eo_YAiYhCHtw-meuM3tjw2cCYCme_am+svx@mail.gmail.com>
	<AANLkTimUepj3XTmanmJCP1nPBxTy8OuFjfP-TsxmZNac@mail.gmail.com>
	<AANLkTi=jrLikBY5XxDKmxiTetJw-tr=O+jiNpcz3ezUX@mail.gmail.com>
	<AANLkTinuBdU_obt+xWLMKpn=na-N=hS3ktckFek2gxWY@mail.gmail.com>
Message-ID: <AANLkTi=r6cu+3VRfO8eare2rDJDMNn-frLZyZS2ncH6B@mail.gmail.com>

Hello Francisco ,

It will help you a little also read my all communication on this list
in Sep and Oct Month.



http://lists.osmocom.org/pipermail/baseband-devel/2010-October/000715.html
http://lists.osmocom.org/pipermail/baseband-devel/2010-September/000616.html
http://lists.osmocom.org/pipermail/baseband-devel/2010-October/000641.html
http://lists.osmocom.org/pipermail/baseband-devel/2010-October/000643.html
http://lists.osmocom.org/pipermail/baseband-devel/2010-October/000714.html

Kind Regards,
========



On Mon, Jan 24, 2011 at 4:01 PM, Francisco Guerreiro <francisg at fnop.net> wrote:
> why do you need the sniff codes to create a "distance teaching system"?
> if you have the openBTS working you can use normal phones with it. i don't
> see how does it relate to GSM Sniffing at all...
> then again, I'm not a PhD student
> Cheers,
> Francisco
>
> On Mon, Jan 24, 2011 at 3:57 PM, Marten Christophe <technosabby at gmail.com>
> wrote:
>>
>> Hello All,
>>
>> Here i feel to introduce myself again as many are commenting on me.
>>
>> I'm a PhD Student also associated to a NGO who works for education in
>> poor and rurale students located at remote location,
>> ?I'm trying to develop a distance teaching system with help of modern
>> communication techniques but with the equipments which are cheapest
>> and even available from salvaged , second-hand market ,
>> repaired-shoppes or ?resale store.
>>
>> second hand Motorola C1xx ? series handsets are available here in bulk
>> within $ 2-4 price, and no end user equipment can be as cheap as it
>> is.
>> ?OK.. openBTS USRP1 and Motorola C1xx series MS will make cheapest and
>> reliable ?two way communication i have estimated
>> so pls don't laugh at me.
>> My THESIS of PhD also same , hence it is mutual benifit of NGO, me and
>> remotely locating poor children
>>
>> Mr. Sylvain, I ?will again request you to provide sniff code which you
>> demonstrated @ chao conf.
>>
>> Kind Regards,
>>
>> On Sun, Jan 23, 2011 at 7:47 PM, Aaron Zauner <azet at azet.org> wrote:
>> > Oh, i also found this:
>> > http://permalink.gmane.org/gmane.comp.gnu.radio.general/31145
>> >
>> > -> http://en.wikipedia.org/wiki/Manoj_Kumar
>> >
>> > lol.
>> >
>> > so long,
>> > azet
>> >
>>
>
>



From francisg at fnop.net  Thu Jan 27 08:25:25 2011
From: francisg at fnop.net (Francisco Guerreiro)
Date: Thu, 27 Jan 2011 08:25:25 +0000
Subject: Sniff Code..shown @chao conf.. CCC
In-Reply-To: <AANLkTi=r6cu+3VRfO8eare2rDJDMNn-frLZyZS2ncH6B@mail.gmail.com>
References: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>
	<20110123060855.19462.qmail@stuge.se>
	<AANLkTi=q6F4mnwYssFZ3ign-8yk185DVtLAOspA-EaXE@mail.gmail.com>
	<AANLkTi=-81edMAVtYORUYmYgLnJU=r1ewzPD5LutFTKF@mail.gmail.com>
	<AANLkTike1eo_YAiYhCHtw-meuM3tjw2cCYCme_am+svx@mail.gmail.com>
	<AANLkTimUepj3XTmanmJCP1nPBxTy8OuFjfP-TsxmZNac@mail.gmail.com>
	<AANLkTi=jrLikBY5XxDKmxiTetJw-tr=O+jiNpcz3ezUX@mail.gmail.com>
	<AANLkTinuBdU_obt+xWLMKpn=na-N=hS3ktckFek2gxWY@mail.gmail.com>
	<AANLkTi=r6cu+3VRfO8eare2rDJDMNn-frLZyZS2ncH6B@mail.gmail.com>
Message-ID: <AANLkTikO0c96AE1bnN3XkQbvSjbAeCbSH3uP7rr2WOc=@mail.gmail.com>

it will help everyone if you stop posting on this list.

Kindest Regards,
Francisco

On Thu, Jan 27, 2011 at 3:23 AM, Marten Christophe <technosabby at gmail.com>wrote:

> Hello Francisco ,
>
> It will help you a little also read my all communication on this list
> in Sep and Oct Month.
>
>
>
> http://lists.osmocom.org/pipermail/baseband-devel/2010-October/000715.html
>
> http://lists.osmocom.org/pipermail/baseband-devel/2010-September/000616.html
> http://lists.osmocom.org/pipermail/baseband-devel/2010-October/000641.html
> http://lists.osmocom.org/pipermail/baseband-devel/2010-October/000643.html
> http://lists.osmocom.org/pipermail/baseband-devel/2010-October/000714.html
>
> Kind Regards,
> ========
>
>
>
> On Mon, Jan 24, 2011 at 4:01 PM, Francisco Guerreiro <francisg at fnop.net>
> wrote:
> > why do you need the sniff codes to create a "distance teaching system"?
> > if you have the openBTS working you can use normal phones with it. i
> don't
> > see how does it relate to GSM Sniffing at all...
> > then again, I'm not a PhD student
> > Cheers,
> > Francisco
> >
> > On Mon, Jan 24, 2011 at 3:57 PM, Marten Christophe <
> technosabby at gmail.com>
> > wrote:
> >>
> >> Hello All,
> >>
> >> Here i feel to introduce myself again as many are commenting on me.
> >>
> >> I'm a PhD Student also associated to a NGO who works for education in
> >> poor and rurale students located at remote location,
> >>  I'm trying to develop a distance teaching system with help of modern
> >> communication techniques but with the equipments which are cheapest
> >> and even available from salvaged , second-hand market ,
> >> repaired-shoppes or  resale store.
> >>
> >> second hand Motorola C1xx   series handsets are available here in bulk
> >> within $ 2-4 price, and no end user equipment can be as cheap as it
> >> is.
> >>  OK.. openBTS USRP1 and Motorola C1xx series MS will make cheapest and
> >> reliable  two way communication i have estimated
> >> so pls don't laugh at me.
> >> My THESIS of PhD also same , hence it is mutual benifit of NGO, me and
> >> remotely locating poor children
> >>
> >> Mr. Sylvain, I  will again request you to provide sniff code which you
> >> demonstrated @ chao conf.
> >>
> >> Kind Regards,
> >>
> >> On Sun, Jan 23, 2011 at 7:47 PM, Aaron Zauner <azet at azet.org> wrote:
> >> > Oh, i also found this:
> >> > http://permalink.gmane.org/gmane.comp.gnu.radio.general/31145
> >> >
> >> > -> http://en.wikipedia.org/wiki/Manoj_Kumar
> >> >
> >> > lol.
> >> >
> >> > so long,
> >> > azet
> >> >
> >>
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110127/49cf2a8f/attachment.htm>

From squalyl at gmail.com  Mon Jan 24 16:19:00 2011
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Mon, 24 Jan 2011 17:19:00 +0100
Subject: Sniff Code..shown @chao conf.. CCC
In-Reply-To: <AANLkTi=jrLikBY5XxDKmxiTetJw-tr=O+jiNpcz3ezUX@mail.gmail.com>
References: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>
	<20110123060855.19462.qmail@stuge.se>
	<AANLkTi=q6F4mnwYssFZ3ign-8yk185DVtLAOspA-EaXE@mail.gmail.com>
	<AANLkTi=-81edMAVtYORUYmYgLnJU=r1ewzPD5LutFTKF@mail.gmail.com>
	<AANLkTike1eo_YAiYhCHtw-meuM3tjw2cCYCme_am+svx@mail.gmail.com>
	<AANLkTimUepj3XTmanmJCP1nPBxTy8OuFjfP-TsxmZNac@mail.gmail.com>
	<AANLkTi=jrLikBY5XxDKmxiTetJw-tr=O+jiNpcz3ezUX@mail.gmail.com>
Message-ID: <AANLkTinRB+1_JS-+9Be=Xy8tXELv9+f1Lo8e3auNOgVN@mail.gmail.com>

Hello,

can you read english?

here is a one-liner extract from the first message that you were directed
to:

URL :
http://lists.osmocom.org/pipermail/baseband-devel/2010-December/000912.html
FROM : Sylvain Munaut
SUBJECT : IMPORTANT clarifications about 27C3 GSM Sniff Talk

=================================
Short version:
- The exact tools I used on stage *are _not_ and will _not_* be released (or
sold ... several people asked ...)
=================================

And I guess that includes, no matter how many times you ask and whatever
your purpose.

I hope that's easier to understand now.

Your initiative is not laughable, but your request is quite contradictory
with the official statement that was made on this very list.

And let me ask : what will you do with software whose purpose is to *spy* on
people when your goal seem to be a full fledged communication stack?? I
can't really see what you will reuse from that. audio decoding? that one is
generic. channel scanning? for a teacher-to-students tool?

Regards
Sebastien

PS: Last message from me in this thread

On Mon, Jan 24, 2011 at 4:57 PM, Marten Christophe <technosabby at gmail.com>
wrote:
>
> Hello All,
>
> Here i feel to introduce myself again as many are commenting on me.
>
> I'm a PhD Student also associated to a NGO who works for education in
> poor and rurale students located at remote location,
>  I'm trying to develop a distance teaching system with help of modern
> communication techniques but with the equipments which are cheapest
> and even available from salvaged , second-hand market ,
> repaired-shoppes or  resale store.
>
> second hand Motorola C1xx   series handsets are available here in bulk
> within $ 2-4 price, and no end user equipment can be as cheap as it
> is.
>  OK.. openBTS USRP1 and Motorola C1xx series MS will make cheapest and
> reliable  two way communication i have estimated
> so pls don't laugh at me.
> My THESIS of PhD also same , hence it is mutual benifit of NGO, me and
> remotely locating poor children
>
> Mr. Sylvain, I  will again request you to provide sniff code which you
> demonstrated @ chao conf.
>
> Kind Regards,
>
> On Sun, Jan 23, 2011 at 7:47 PM, Aaron Zauner <azet at azet.org> wrote:
> > Oh, i also found this:
> > http://permalink.gmane.org/gmane.comp.gnu.radio.general/31145
> >
> > -> http://en.wikipedia.org/wiki/Manoj_Kumar
> >
> > lol.
> >
> > so long,
> > azet
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110124/9d143152/attachment.htm>

From holger at freyther.de  Mon Jan 24 17:27:26 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Mon, 24 Jan 2011 18:27:26 +0100
Subject: Sniff Code..shown @chao conf.. CCC
In-Reply-To: <AANLkTinRB+1_JS-+9Be=Xy8tXELv9+f1Lo8e3auNOgVN@mail.gmail.com>
References: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>	<20110123060855.19462.qmail@stuge.se>	<AANLkTi=q6F4mnwYssFZ3ign-8yk185DVtLAOspA-EaXE@mail.gmail.com>	<AANLkTi=-81edMAVtYORUYmYgLnJU=r1ewzPD5LutFTKF@mail.gmail.com>	<AANLkTike1eo_YAiYhCHtw-meuM3tjw2cCYCme_am+svx@mail.gmail.com>	<AANLkTimUepj3XTmanmJCP1nPBxTy8OuFjfP-TsxmZNac@mail.gmail.com>	<AANLkTi=jrLikBY5XxDKmxiTetJw-tr=O+jiNpcz3ezUX@mail.gmail.com>
	<AANLkTinRB+1_JS-+9Be=Xy8tXELv9+f1Lo8e3auNOgVN@mail.gmail.com>
Message-ID: <4D3DB67E.5070204@freyther.de>

On 01/24/2011 05:19 PM, S?bastien Lorquet wrote:

> =================================
> Short version:
> - The exact tools I used on stage _*are _not_ and will _not_*_ be released (or
> sold ... several people asked ...)
> =================================



> Your initiative is not laughable, but your request is quite contradictory with
> the official statement that was made on this very list.

Hi Marten,

your initiative is not laughable, your is goal is nice too. The problem is you
go around and bag and this is not how it works. People prefer to donate
(money, items) to organization that have a proven track record, that one can
relate to (e.g. 'Die Tafeln' in germany, organizations that provide heating
for homeless in winter..).

You should start building some trust, this involves writing code in our
community. So here is something you could do.

1.) Setup a wiki/site for your phd at your university and point us to it
2.) Put the plans for your system on that page
3.) Build a prototype, thanks to the invention of layers you don't need to
have any hardware for that. E.g. start with a prototype that is announcing
classes through the CBCH with your own encapsulation of the message. Build the
code based on osmocomBB to receive this...
4.) Go for other physical channels with more bandwidth, again no RF is needed
you can just start using a SDCH and make the l1ctl connect to your repurposed
BTS code.

5.) Sylvian has shown how to get raw BURSTS from the DSP, maybe he is kind
enough at this state to help you in transmitting raw bursts. You could realize
the 3rd) with two osmocomBB then... at this point you could even do 4th.


6.) if you have done 1.) to 5.) have a prototype in software, some basic
illustration that the RF side is working. Ask for donations for a USRP1 and
the flex frontends and the antenna. I am sure that once you have shown that
1.) to 5.) are done, that you have a NGO at hand for a field trial that one
can make a tax deductible donation to that NGO and they will buy you the USRP
from that money.


so please build the trust by building up the system

regrads
	holger



From 246tnt at gmail.com  Mon Jan 24 18:10:27 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Mon, 24 Jan 2011 19:10:27 +0100
Subject: Sniff Code..shown @chao conf.. CCC
In-Reply-To: <4D3DB67E.5070204@freyther.de>
References: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>
	<20110123060855.19462.qmail@stuge.se>
	<AANLkTi=q6F4mnwYssFZ3ign-8yk185DVtLAOspA-EaXE@mail.gmail.com>
	<AANLkTi=-81edMAVtYORUYmYgLnJU=r1ewzPD5LutFTKF@mail.gmail.com>
	<AANLkTike1eo_YAiYhCHtw-meuM3tjw2cCYCme_am+svx@mail.gmail.com>
	<AANLkTimUepj3XTmanmJCP1nPBxTy8OuFjfP-TsxmZNac@mail.gmail.com>
	<AANLkTi=jrLikBY5XxDKmxiTetJw-tr=O+jiNpcz3ezUX@mail.gmail.com>
	<AANLkTinRB+1_JS-+9Be=Xy8tXELv9+f1Lo8e3auNOgVN@mail.gmail.com>
	<4D3DB67E.5070204@freyther.de>
Message-ID: <AANLkTikbA0_4Jfcd1YsYuxvyjTP=4e1U+2pgdSUv5sLf@mail.gmail.com>

Hi,

> 5.) Sylvian has shown how to get raw BURSTS from the DSP, maybe he is kind
> enough at this state to help you in transmitting raw bursts. You could realize
> the 3rd) with two osmocomBB then... at this point you could even do 4th.

Even more to the point ... there is _no_ _need_ for raw burst rx/tx
for this application whatsoever ... normal signalling would work just
fine.

Cheers,

    Sylvain



From squalyl at gmail.com  Sun Jan 23 19:49:01 2011
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Sun, 23 Jan 2011 20:49:01 +0100
Subject: Sniff Code..shown @chao conf.. CCC
In-Reply-To: <AANLkTi=q6F4mnwYssFZ3ign-8yk185DVtLAOspA-EaXE@mail.gmail.com>
References: <AANLkTik-5PBmXYMpPoH4YME7jN=d0S+fJ0Os5jg3-C1Z@mail.gmail.com>
	<20110123060855.19462.qmail@stuge.se>
	<AANLkTi=q6F4mnwYssFZ3ign-8yk185DVtLAOspA-EaXE@mail.gmail.com>
Message-ID: <AANLkTik6iGs2f7WAzbDz6DT11QF2BiX3so1u1F7xY4d1@mail.gmail.com>

the students in his love girl's school.

Sebastien

On Sun, Jan 23, 2011 at 8:02 PM, Aaron Zauner <azet at azet.org> wrote:

> What poor students are you talking of?
>
> azet
>
> On 1/23/11, Peter Stuge <peter at stuge.se> wrote:
> > Marten Christophe wrote:
> >> Kindly give me code or even binary file for sniff code which
> >> Sylvain demonstrated in chao meeting,
> >
> > Kindly read
> >
> http://lists.osmocom.org/pipermail/baseband-devel/2010-December/000912.html
> >
> >
> >> Pls reply
> >> pls help
> >> or pls advise
> >> Kindly  reply
> >> pls provide
> >
> > I'm sure you realize that this sounds like a nagging child.
> >
> > I think one can always beenfit from considering the group that one is
> > communicating in. Many quite skilled developers work together in this
> > and most other open source projects, and the way to get things that
> > one wants is never to nag.
> >
> > At best one will be silently ignored, at worst one will get banned.
> > In any case, the impression people will be left with suffers
> > dramatically from any behavior not clearly trying to further the
> > project. I have seen this happen in many projects, and many times I
> > am sure that it is caused mainly by problems in communication, such
> > as language barriers, rhetoric skill, and so on. Other times it is
> > simply because someone is stupid. (I don't know you at all well
> > enough to say if that holds for you, probably not, but your emails
> > may cause people to think so.)
> >
> >
> >> advise me how i can modify existing code up to that level.
> > ..
> >> it will help me allot, my NGO can deploy a pilot project at least
> >
> > I guess you are still working on the idea that developers here fairly
> > clearly judged as not being really worthwhile. And now you plea for
> > people to go out of their way to support it. That demonstrates a lack
> > of understanding for open source projects, where *you* are always
> > responsible for fulfilling *your* needs. Of course you can ask others
> > to do stuff, by politely making suggestions, but you must respect if
> > they have no interest in your ideas.
> >
> > But nothing stops you from moving ahead on your own and proving
> > everyone wrong! In fact that is one great thing about open source.
> > When going against the flow of course you must be prepared to not
> > get much, if any, help.
> >
> > Maybe Sylvain will be interested in licensing some work to your NGO
> > for a pilot project - if so I guess he will get in touch with you -
> > but honestly I doubt that, based on nothing but how you behave on
> > this mailing list. :\
> >
> > Besides the tone in your email you have hijacked the thread about the
> > Osmocom logo request. This suggests unfamiliarity with mailing list
> > etiquette, which also hurts your standing in the project rather
> > severely. One could think this should not be so important, because it
> > is a technicality, but on the other hand we are all technicians, and
> > the technicalities are there for a reason; they allow the most
> > efficient communication. So by not knowing the etiquette you are
> > creating inefficiencies for every mailing list subscriber and for the
> > afterworld (in the archives) which as I am sure you understand is
> > very strongly frowned upon.
> >
> >
> > Perhaps you could benefit from the recently announced TETRA code..
> >
> > http://tetra.osmocom.org/trac/
> >
> > Maybe it fits your application better than plain GSM, as you seem to
> > be on good terms with the regulatory body in your deployment area.
> >
> >
> > Kind regards
> >
> > //Peter
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110123/81aa27dc/attachment.htm>

From b.alecu at yahoo.com  Sun Jan 23 20:43:26 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Sun, 23 Jan 2011 12:43:26 -0800 (PST)
Subject: Regarding IMSI detach DoS
Message-ID: <993959.26398.qm@web46203.mail.sp1.yahoo.com>

Hello,
?
In order for this attack to work it has to be on a GSM network because on 3G there is a higher security mechanism. A way to protect against this, for the opperator, could be to implement 3G over 900Mhz so this way even if the targeted phones are on 2G they will still be protected. Am I right?
?
Regards,
Bogdan


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110123/aed00d16/attachment.htm>

From peter at stuge.se  Sun Jan 23 23:36:19 2011
From: peter at stuge.se (Peter Stuge)
Date: Mon, 24 Jan 2011 00:36:19 +0100
Subject: Regarding IMSI detach DoS
In-Reply-To: <993959.26398.qm@web46203.mail.sp1.yahoo.com>
References: <993959.26398.qm@web46203.mail.sp1.yahoo.com>
Message-ID: <20110123233619.343.qmail@stuge.se>

Bogdan Alecu wrote:
> implement 3G over 900Mhz so this way even if the targeted phones
> are on 2G they will still be protected. Am I right?

Unless the phones do not support 3G, in which case the operator loses
customers.


//Peter



From holger at freyther.de  Sun Jan 23 21:16:21 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sun, 23 Jan 2011 22:16:21 +0100
Subject: Creatng a list of known issues somewhere
Message-ID: <4D3C9AA5.8040505@freyther.de>

Hi all,

it appears that we all know of some issues but we are not writing them down.
Would it make sense to start using the bugtracker for that? Or just a
dedicated wiki site?


From 246tnt at gmail.com  Sun Jan 23 22:42:33 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Sun, 23 Jan 2011 23:42:33 +0100
Subject: Creatng a list of known issues somewhere
In-Reply-To: <4D3C9AA5.8040505@freyther.de>
References: <4D3C9AA5.8040505@freyther.de>
Message-ID: <AANLkTikJs5kNos3jsUjv3C4HhXgwGGFgiFedoxnRkpux@mail.gmail.com>

Hi,

> it appears that we all know of some issues but we are not writing them down.
> Would it make sense to start using the bugtracker for that? Or just a
> dedicated wiki site?

The bug tracker seems appropriate to me.


> ? ? ? ?- We don't do frequency synchronization after we have done it the
> ? ? ? ? ?first time?

Huh ?


> ? ? ? ?- We have some issue with the gain on FB detection? Some cells which
> ? ? ? ? ?are very close by (like under the table) do not show up?

Yes, that one.


Cheers,

    Sylvain



From holger at freyther.de  Mon Jan 24 09:17:01 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Mon, 24 Jan 2011 10:17:01 +0100
Subject: Creatng a list of known issues somewhere
In-Reply-To: <AANLkTikJs5kNos3jsUjv3C4HhXgwGGFgiFedoxnRkpux@mail.gmail.com>
References: <4D3C9AA5.8040505@freyther.de>
	<AANLkTikJs5kNos3jsUjv3C4HhXgwGGFgiFedoxnRkpux@mail.gmail.com>
Message-ID: <4D3D438D.3060406@freyther.de>

On 01/23/2011 11:42 PM, Sylvain Munaut wrote:

>>        - We don't do frequency synchronization after we have done it the
>>          first time?
> 
> Huh ?

It has been a while that I went that close to the firmware but if I move the
device on my table i am seeing bit errors, they go away if i put it back to
the original position. My explanation of not updating frequency correction and
such would be a good one. Of course I can be wrong and the explanation is
something else.



From jakob at weite-welt.com  Sun Jan 23 23:44:17 2011
From: jakob at weite-welt.com (Leif Jakob)
Date: Mon, 24 Jan 2011 00:44:17 +0100
Subject: problems getting Pirelli DP-L10 to work
Message-ID: <20110123234417.GY15313@aegir.asgard.sol>

Hi,

maybe I'm missing something, but when I read that the Pirelli DP-L10
would be supported I tried to get it running:

I didn't patch my usb-module, but used:

modprobe -v cp210x
echo "0489 e003" > /sys/bus/usb-serial/drivers/cp210x/new_id

from the steve-m/testing-branch I compiled the firmware and loaded it with

./host/osmocon/osmocon -p /dev/ttyUSB0 -m romload target/firmware/board/pirelli_dpl10/hello_world.highram.bin 

onto the phone... that worked but I was never able to see any messages
after the upload:

Received block ack from phone
Sending checksum: 0xaa 
Checksum on phone side matches, let's branch to your code
Branching to 0x00820000
Received branch ack, your code is running now!

... there it stayed forever ...

I'm pretty sure that the code runs, because I commented in init.c the
keyboard lighting code and it didn't light up after upload. I've tried
other bins but to no success.

Any hint or am it too early playing with that hardware?

Greetings Leif






From steve at steve-m.de  Mon Jan 24 08:58:42 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Mon, 24 Jan 2011 09:58:42 +0100
Subject: problems getting Pirelli DP-L10 to work
In-Reply-To: <20110123234417.GY15313@aegir.asgard.sol>
References: <20110123234417.GY15313@aegir.asgard.sol>
Message-ID: <4D3D3F42.8030803@steve-m.de>

Hi,

On 24.01.2011 00:44, Leif Jakob wrote:

> Any hint or am it too early playing with that hardware?

Ah, yes. There's one unresolved issue I forgot to mention in the wiki:
the sercomm/console UARTs need to be swapped. We still need to come up
with a way to set them dynamically from the board configuration.

Currently those are hardcoded in /firmware/include/console.h and
/firmware/include/comm/sercomm.h. Just swap the values of CONS_UART_NR
and SERCOMM_UART_NR.

Regards,
Steve



From khorben at defora.org  Mon Jan 24 12:02:33 2011
From: khorben at defora.org (Pierre Pronchery)
Date: Mon, 24 Jan 2011 13:02:33 +0100
Subject: [PATCH] Support GNU make when it is not called "make"
Message-ID: <4D3D6A59.3080106@defora.org>

			Hi baseband developers,

just a small patch to help where GNU make is not directly called "make".

HTH,
-- 
khorben
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gmake.diff
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110124/0a3bac26/attachment.ksh>

From sweisman at pobox.com  Mon Jan 24 20:34:59 2011
From: sweisman at pobox.com (Scott Weisman)
Date: Mon, 24 Jan 2011 22:34:59 +0200
Subject: question on pirelli dp l10
Message-ID: <AANLkTi=ACsHThku8sTcddoYCSceQRvqB+RRyP1CXkYbL@mail.gmail.com>

I looked more into this phone recently and found out it supported SIP over
WiFi as well.

Does anyone know about the software running the phone? How are the VOIP
codecs handled? Is there hardware support for them?

Finally, does code and/or drivers already exist for the hardware components?

I happened to be looking for something exactly like this anyway. Cool to
know that OsmocomBB can (potentially) work on it too.

Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110124/23833479/attachment.htm>

From steve at steve-m.de  Mon Jan 24 20:45:45 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Mon, 24 Jan 2011 21:45:45 +0100
Subject: question on pirelli dp l10
In-Reply-To: <AANLkTi=ACsHThku8sTcddoYCSceQRvqB+RRyP1CXkYbL@mail.gmail.com>
References: <AANLkTi=ACsHThku8sTcddoYCSceQRvqB+RRyP1CXkYbL@mail.gmail.com>
Message-ID: <4D3DE4F9.1040406@steve-m.de>

Hi,

On 24.01.2011 21:34, Scott Weisman wrote:

> Does anyone know about the software running the phone? How are the VOIP
> codecs handled? Is there hardware support for them?

Did you read the wiki page for the DP-L10 [1]? Sofware is Nucleus.
"LSI-65194A1 ASIC (seems to be a DSP for VoIP en-/decoding)"

> Finally, does code and/or drivers already exist for the hardware components?

This can be found on said page as well.

Regards,
Steve

[1] http://bb.osmocom.org/trac/wiki/PirelliDPL10



From sweisman at pobox.com  Tue Jan 25 06:23:02 2011
From: sweisman at pobox.com (Scott Weisman)
Date: Tue, 25 Jan 2011 08:23:02 +0200
Subject: question on pirelli dp l10
In-Reply-To: <4D3DE4F9.1040406@steve-m.de>
References: <AANLkTi=ACsHThku8sTcddoYCSceQRvqB+RRyP1CXkYbL@mail.gmail.com>
	<4D3DE4F9.1040406@steve-m.de>
Message-ID: <AANLkTikvr2NjOu=U=movf632sO+PNjW3CaaQcFLm-RNr@mail.gmail.com>

My apologies. I didn't read far enough down the page. Thanks for the
clarification.

On Mon, Jan 24, 2011 at 10:45 PM, Steve Markgraf <steve at steve-m.de> wrote:

> Hi,
>
>
> On 24.01.2011 21:34, Scott Weisman wrote:
>
>  Does anyone know about the software running the phone? How are the VOIP
>> codecs handled? Is there hardware support for them?
>>
>
> Did you read the wiki page for the DP-L10 [1]? Sofware is Nucleus.
> "LSI-65194A1 ASIC (seems to be a DSP for VoIP en-/decoding)"
>
>
>  Finally, does code and/or drivers already exist for the hardware
>> components?
>>
>
> This can be found on said page as well.
>
> Regards,
> Steve
>
> [1] http://bb.osmocom.org/trac/wiki/PirelliDPL10
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/b8781a1d/attachment.htm>

From terrolokaust at gmail.com  Tue Jan 25 07:33:24 2011
From: terrolokaust at gmail.com (MArc Richter)
Date: Tue, 25 Jan 2011 08:33:24 +0100
Subject: Cell_log > gsmmap
Message-ID: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>

Hey!

I've tryed out the Cell_log tool to get the Location of the GSM cells.

But when i convert it into a kml file with gsmmap i can't see any GPS
koordinates. Why ?

I use the Sylvain branch an compiled with TX support

thx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/8678e0fe/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gsm.kml
Type: application/vnd.google-earth.kml+xml
Size: 4430 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/8678e0fe/attachment.bin>

From holger at freyther.de  Tue Jan 25 09:34:56 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 25 Jan 2011 10:34:56 +0100
Subject: Cell_log > gsmmap
In-Reply-To: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
Message-ID: <4D3E9940.3080109@freyther.de>

On 01/25/2011 08:33 AM, MArc Richter wrote:

> But when i convert it into a kml file with gsmmap i can't see any GPS
> koordinates. Why ?

Do you have a GPS receiver attached to your computer?



From terrolokaust at gmail.com  Tue Jan 25 09:40:40 2011
From: terrolokaust at gmail.com (MArc Richter)
Date: Tue, 25 Jan 2011 10:40:40 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
	<4D3E9940.3080109@freyther.de>
	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
Message-ID: <AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>

Do i need a GPS Reciver ?
I tought that it will calculate the location over Triangulation ?


On Tue, Jan 25, 2011 at 10:34 AM, Holger Hans Peter Freyther <
holger at freyther.de> wrote:

> On 01/25/2011 08:33 AM, MArc Richter wrote:
>
> > But when i convert it into a kml file with gsmmap i can't see any GPS
> > koordinates. Why ?
>
> Do you have a GPS receiver attached to your computer?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/ecaf72d6/attachment.htm>

From holger at freyther.de  Tue Jan 25 09:44:51 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 25 Jan 2011 10:44:51 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
Message-ID: <4D3E9B93.4040202@freyther.de>

On 01/25/2011 10:40 AM, MArc Richter wrote:
> Do i need a GPS Reciver ?
> I tought that it will calculate the location over Triangulation ?

You will need one, even for triangulation you will need to some base
coordinates. Please feel encouraged to create a wiki page for the cell_log
application to describe its requirements and features.



Relevant sourcecode to initiate opening the GPS device:
http://bb.osmocom.org/trac/browser/src/host/layer23/src/misc/cell_log.c#L789




From dario.lombardo at libero.it  Tue Jan 25 11:01:55 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Tue, 25 Jan 2011 12:01:55 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3E9B93.4040202@freyther.de>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
	<4D3E9B93.4040202@freyther.de>
Message-ID: <4D3EADA3.3090409@libero.it>



On 01/25/2011 10:44 AM, Holger Hans Peter Freyther wrote:
>
> Relevant sourcecode to initiate opening the GPS device:
> http://bb.osmocom.org/trac/browser/src/host/layer23/src/misc/cell_log.c#L789
>
I can't make it work. The first issue was the /dev/ttyACM0 in the source 
code (my gps is /dev/ttyUSBX). I modified it in the code, but I think 
that a cmd line option would be nicer. I don't see any debug/error log 
lines, but no coordinates appear in my log file. Any hint? My gps 
receiver works fine with other softwares.



From squalyl at gmail.com  Tue Jan 25 11:32:17 2011
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Tue, 25 Jan 2011 12:32:17 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3EADA3.3090409@libero.it>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
	<4D3E9940.3080109@freyther.de>
	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
	<4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it>
Message-ID: <AANLkTi=TBMR0n89rKKyA3mvN-ZsLOLhWK8eYzN8zM5bc@mail.gmail.com>

On Tue, Jan 25, 2011 at 12:01 PM, Dario Lombardo
<dario.lombardo at libero.it>wrote:

> Any hint?
>

contribute!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/effa3625/attachment.htm>

From lbernal at gmail.com  Tue Jan 25 11:34:26 2011
From: lbernal at gmail.com (n0p [Luis Bernal])
Date: Tue, 25 Jan 2011 12:34:26 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3EADA3.3090409@libero.it>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
	<4D3E9940.3080109@freyther.de>
	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
	<4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it>
Message-ID: <AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>

let the GPS warm up, maybe it just needs to start tracking the sats, or add
a printf to dump what data is coming from the GPS

2011/1/25 Dario Lombardo <dario.lombardo at libero.it>

>
>
> On 01/25/2011 10:44 AM, Holger Hans Peter Freyther wrote:
>
>>
>> Relevant sourcecode to initiate opening the GPS device:
>>
>> http://bb.osmocom.org/trac/browser/src/host/layer23/src/misc/cell_log.c#L789
>>
>>  I can't make it work. The first issue was the /dev/ttyACM0 in the source
> code (my gps is /dev/ttyUSBX). I modified it in the code, but I think that a
> cmd line option would be nicer. I don't see any debug/error log lines, but
> no coordinates appear in my log file. Any hint? My gps receiver works fine
> with other softwares.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/1c186388/attachment.htm>

From terrolokaust at gmail.com  Tue Jan 25 12:51:05 2011
From: terrolokaust at gmail.com (MArc Richter)
Date: Tue, 25 Jan 2011 13:51:05 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
	<4D3E9940.3080109@freyther.de>
	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
	<4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it>
	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>
Message-ID: <AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>

So anyone is changing the code to use the config from the osmcom.cfg
file for the gps feature ?
Or is this a missunderstanding on my side?


On Tue, Jan 25, 2011 at 12:34 PM, n0p [Luis Bernal] <lbernal at gmail.com> wrote:
> let the GPS warm up, maybe it just needs to start tracking the sats, or add
> a printf to dump what data is coming from the GPS
>
> 2011/1/25 Dario Lombardo <dario.lombardo at libero.it>
>>
>>
>> On 01/25/2011 10:44 AM, Holger Hans Peter Freyther wrote:
>>>
>>> Relevant sourcecode to initiate opening the GPS device:
>>>
>>> http://bb.osmocom.org/trac/browser/src/host/layer23/src/misc/cell_log.c#L789
>>>
>> I can't make it work. The first issue was the /dev/ttyACM0 in the source
>> code (my gps is /dev/ttyUSBX). I modified it in the code, but I think that a
>> cmd line option would be nicer. I don't see any debug/error log lines, but
>> no coordinates appear in my log file. Any hint? My gps receiver works fine
>> with other softwares.
>>
>
>



From holger at freyther.de  Tue Jan 25 12:57:56 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 25 Jan 2011 13:57:56 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>
	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>
	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>
Message-ID: <4D3EC8D4.4040401@freyther.de>

On 01/25/2011 01:51 PM, MArc Richter wrote:
> So anyone is changing the code to use the config from the osmcom.cfg
> file for the gps feature ?
> Or is this a missunderstanding on my side?

patches welcome, no harm if two people work on this. Personally I would prefer
command line parameters as cell log is not using a config file yet.



From dario.lombardo at libero.it  Tue Jan 25 13:17:17 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Tue, 25 Jan 2011 14:17:17 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3EC8D4.4040401@freyther.de>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>
	<4D3EC8D4.4040401@freyther.de>
Message-ID: <4D3ECD5D.8030701@libero.it>

On 01/25/2011 01:57 PM, Holger Hans Peter Freyther wrote:
>
> patches welcome, no harm if two people work on this. Personally I would prefer
> command line parameters as cell log is not using a config file yet.
>
Me too. But cell_log uses the "common/main.c", so if we put it in that 
file, that would be shared between all "layer23" apps.
Is it ok or anyone can suggest another way?



From holger at freyther.de  Tue Jan 25 13:21:14 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 25 Jan 2011 14:21:14 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3ECD5D.8030701@libero.it>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>
	<4D3ECD5D.8030701@libero.it>
Message-ID: <4D3ECE4A.8030904@freyther.de>

On 01/25/2011 02:17 PM, Dario Lombardo wrote:

> Me too. But cell_log uses the "common/main.c", so if we put it in that file,
> that would be shared between all "layer23" apps.
> Is it ok or anyone can suggest another way?
> 

For command line options. Each app can have its own set, just add them to the
one already present for the cell_log (e.g. to disable rach bursts). If you go
for config file parsing, make sure that no config file is required (keep it
optional). But then again parameters are preferred by me.

z.



From terrolokaust at gmail.com  Tue Jan 25 13:43:10 2011
From: terrolokaust at gmail.com (MArc Richter)
Date: Tue, 25 Jan 2011 14:43:10 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3ECE4A.8030904@freyther.de>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
	<4D3E9940.3080109@freyther.de>
	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
	<4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it>
	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>
	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>
	<4D3EC8D4.4040401@freyther.de> <4D3ECD5D.8030701@libero.it>
	<4D3ECE4A.8030904@freyther.de>
Message-ID: <AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>

Nice so if anyone could add this feature. I would write a Wiki page
how to use this

On Tue, Jan 25, 2011 at 2:21 PM, Holger Hans Peter Freyther
<holger at freyther.de> wrote:
> On 01/25/2011 02:17 PM, Dario Lombardo wrote:
>
>> Me too. But cell_log uses the "common/main.c", so if we put it in that file,
>> that would be shared between all "layer23" apps.
>> Is it ok or anyone can suggest another way?
>>
>
> For command line options. Each app can have its own set, just add them to the
> one already present for the cell_log (e.g. to disable rach bursts). If you go
> for config file parsing, make sure that no config file is required (keep it
> optional). But then again parameters are preferred by me.
>
> z.
>
>



From dario.lombardo at libero.it  Tue Jan 25 15:30:12 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Tue, 25 Jan 2011 16:30:12 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>
	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>
	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>
	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>
Message-ID: <4D3EEC84.5060000@libero.it>



On 01/25/2011 02:43 PM, MArc Richter wrote:
> Nice so if anyone could add this feature. I would write a Wiki page
> how to use this
>
Attached there is my patch to support cmd line gps in cell_log.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dev.diff
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/d4ac7223/attachment.ksh>

From holger at freyther.de  Tue Jan 25 15:34:32 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 25 Jan 2011 16:34:32 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3EEC84.5060000@libero.it>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>
	<4D3EEC84.5060000@libero.it>
Message-ID: <4D3EED88.5000909@freyther.de>

On 01/25/2011 04:30 PM, Dario Lombardo wrote:

awesome!

> +    case 'g':
> +        snprintf(gps.device, 32, "%s", optarg);
> +        LOGP(DGPS, LOGL_INFO, "Using GPS device %s\n", gps.device);

two issues there.

1.) you can use ARRAY_SIZE(gps.device) in case we ever shrink/increase this.
In reality this should be PATH_MAX/MAX_PATH or such.

2.) snprintf will not add a '\0' of optarg is of the length of 32 or longer




From dario.lombardo at libero.it  Tue Jan 25 15:46:29 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Tue, 25 Jan 2011 16:46:29 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3EED88.5000909@freyther.de>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>
	<4D3EED88.5000909@freyther.de>
Message-ID: <4D3EF055.6040006@libero.it>



On 01/25/2011 04:34 PM, Holger Hans Peter Freyther wrote:
> On 01/25/2011 04:30 PM, Dario Lombardo wrote:
>
> awesome!
>
>> +    case 'g':
>> +        snprintf(gps.device, 32, "%s", optarg);
>> +        LOGP(DGPS, LOGL_INFO, "Using GPS device %s\n", gps.device);
> two issues there.
>
> 1.) you can use ARRAY_SIZE(gps.device) in case we ever shrink/increase this.
> In reality this should be PATH_MAX/MAX_PATH or such.
>
> 2.) snprintf will not add a '\0' of optarg is of the length of 32 or longer
>
>
Very good. This is the new patch that should fix both.

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dev.diff
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/939229b0/attachment.ksh>

From holger at freyther.de  Tue Jan 25 15:51:02 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 25 Jan 2011 16:51:02 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3EF055.6040006@libero.it>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>	<4D3EED88.5000909@freyther.de>
	<4D3EF055.6040006@libero.it>
Message-ID: <4D3EF166.4030100@freyther.de>

On 01/25/2011 04:46 PM, Dario Lombardo wrote:
> 
> 
> On 01/25/2011 04:34 PM, Holger Hans Peter Freyther wrote:
>> On 01/25/2011 04:30 PM, Dario Lombardo wrote:
>>
>> awesome!

> Very good. This is the new patch that should fix both.
> 

Almost perfect. I can apply and modify myself or you could do two things. We
tend to avoid the '//' comments, they were only added in C99 and used to be a
GCC extension for C. The other is you could (if you want to) use git commit
and then git format-patch. This way I don't need to copy and paste your name
and mail address.

tell me what you prefer
	holger



From dario.lombardo at libero.it  Wed Jan 26 12:43:41 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Wed, 26 Jan 2011 13:43:41 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3EF166.4030100@freyther.de>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>	<4D3EED88.5000909@freyther.de>	<4D3EF055.6040006@libero.it>
	<4D3EF166.4030100@freyther.de>
Message-ID: <4D4016FD.1060101@libero.it>

Something's going wrong when I try to commit.

git commit .
git formal-patch
git push

Last one returns "fatal: The remote end hung up unexpectedly".
Am I making something wrong?



From holger at freyther.de  Wed Jan 26 12:48:08 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 26 Jan 2011 13:48:08 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D4016FD.1060101@libero.it>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>	<4D3EED88.5000909@freyther.de>	<4D3EF055.6040006@libero.it>	<4D3EF166.4030100@freyther.de>
	<4D4016FD.1060101@libero.it>
Message-ID: <4D401808.4040104@freyther.de>

On 01/26/2011 01:43 PM, Dario Lombardo wrote:
> Something's going wrong when I try to commit.
> 
> git commit .
> git formal-patch
> git push
> 
> Last one returns "fatal: The remote end hung up unexpectedly".
> Am I making something wrong?

git format-patch will create a patch for you. You can send this to the
mailinglist. git push is only for people thay can send commits to the server.




From dario.lombardo at libero.it  Wed Jan 26 13:12:36 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Wed, 26 Jan 2011 14:12:36 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D401808.4040104@freyther.de>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>	<4D3EED88.5000909@freyther.de>	<4D3EF055.6040006@libero.it>	<4D3EF166.4030100@freyther.de>	<4D4016FD.1060101@libero.it>
	<4D401808.4040104@freyther.de>
Message-ID: <4D401DC4.5040701@libero.it>



On 01/26/2011 01:48 PM, Holger Hans Peter Freyther wrote:
>
> git format-patch will create a patch for you. You can send this to the
> mailinglist. git push is only for people thay can send commits to the server.
>
Ok. Attached there is the format-patch.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 0001-Added-command-line-switches-to-cell_log-to-change-de.patch
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110126/4ee73011/attachment.ksh>

From lomato at gmail.com  Wed Jan 26 08:30:14 2011
From: lomato at gmail.com (Dario Lombardo)
Date: Wed, 26 Jan 2011 09:30:14 +0100
Subject: [PATCH] Added command line switches to cell_log to change default gps device and baud rate.
Message-ID: <mailman.13.1641743545.42824.baseband-devel@lists.osmocom.org>

---
 src/host/layer23/src/misc/app_cell_log.c |   17 ++++++++++++++++-
 1 files changed, 16 insertions(+), 1 deletions(-)

diff --git a/src/host/layer23/src/misc/app_cell_log.c b/src/host/layer23/src/misc/app_cell_log.c
index 84f5a83..9c05108 100644
--- a/src/host/layer23/src/misc/app_cell_log.c
+++ b/src/host/layer23/src/misc/app_cell_log.c
@@ -29,6 +29,7 @@
 #include <osmocom/bb/common/l1ctl.h>
 #include <osmocom/bb/common/l23_app.h>
 #include <osmocom/bb/common/logging.h>
+#include <osmocom/bb/common/gps.h>
 #include <osmocom/bb/misc/cell_log.h>
 
 #include <osmocore/talloc.h>
@@ -91,6 +92,8 @@ static int l23_getopt_options(struct option **options)
 		{"logfile", 1, 0, 'l'},
 		{"rach", 1, 0, 'r'},
 		{"no-rach", 1, 0, 'n'},
+		{"gps", 1, 0, 'g'},
+		{"baud", 1, 0, 'b'}
 	};
 
 	*options = opts;
@@ -103,6 +106,8 @@ static int l23_cfg_print_help()
 	printf("  -l --logfile LOGFILE		Logfile for the cell log.\n");
 	printf("  -r --rach    RACH		Nr. of RACH bursts to send.\n");
 	printf("  -n --no-rach			Send no rach bursts.\n");
+	printf("  -g --gps DEVICE		/dev/ttyACM0. GPS device.\n");
+	printf("  -b --baud BAUDRATE	The baud rate of the GPS device\n");
 	return 0;
 }
 
@@ -118,6 +123,16 @@ static int l23_cfg_handle(int c, const char *optarg)
 	case 'n':
 		RACH_MAX = 0;
 		break;
+    case 'g':
+        snprintf(gps.device, ARRAY_SIZE(gps.device), "%s", optarg);
+        /* force string terminator */
+        gps.device[ARRAY_SIZE(gps.device - 1)] = '\0';
+        LOGP(DGPS, LOGL_INFO, "Using GPS device %s\n", gps.device);
+        break;
+    case 'b':
+        gps.baud = atoi(optarg);
+        LOGP(DGPS, LOGL_INFO, "Setting GPS baudrate to %u\n", gps.baud);
+        break;
 	}
 
 	return 0;
@@ -125,7 +140,7 @@ static int l23_cfg_handle(int c, const char *optarg)
 
 static struct l23_app_info info = {
 	.copyright	= "Copyright (C) 2010 Andreas Eversberg\n",
-	.getopt_string	= "l:r:n",
+	.getopt_string	= "l:r:ng:b:",
 	.cfg_supported	= l23_cfg_supported,
 	.cfg_getopt_opt = l23_getopt_options,
 	.cfg_handle_opt	= l23_cfg_handle,
-- 
1.7.3.4


--------------090907080903040108080303--



From holger at freyther.de  Wed Jan 26 13:34:44 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 26 Jan 2011 14:34:44 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D401DC4.5040701@libero.it>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>	<4D3EED88.5000909@freyther.de>	<4D3EF055.6040006@libero.it>	<4D3EF166.4030100@freyther.de>	<4D4016FD.1060101@libero.it>	<4D401808.4040104@freyther.de>
	<4D401DC4.5040701@libero.it>
Message-ID: <4D4022F4.1080200@freyther.de>

On 01/26/2011 02:12 PM, Dario Lombardo wrote:
> +        gps.device[ARRAY_SIZE(gps.device - 1)] = '\0';

You missed Peter's comment. I am going to fix it when pushing.

thanks



From dario.lombardo at libero.it  Wed Jan 26 13:50:19 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Wed, 26 Jan 2011 14:50:19 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D4022F4.1080200@freyther.de>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>	<4D3EED88.5000909@freyther.de>	<4D3EF055.6040006@libero.it>	<4D3EF166.4030100@freyther.de>	<4D4016FD.1060101@libero.it>	<4D401808.4040104@freyther.de>	<4D401DC4.5040701@libero.it>
	<4D4022F4.1080200@freyther.de>
Message-ID: <4D40269B.3000402@libero.it>



On 01/26/2011 02:34 PM, Holger Hans Peter Freyther wrote:
> You missed Peter's comment. I am going to fix it when pushing.
>
Opps... you're right. Thank you.



From holger at freyther.de  Wed Jan 26 14:59:58 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 26 Jan 2011 15:59:58 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D40269B.3000402@libero.it>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>	<4D3EED88.5000909@freyther.de>	<4D3EF055.6040006@libero.it>	<4D3EF166.4030100@freyther.de>	<4D4016FD.1060101@libero.it>	<4D401808.4040104@freyther.de>	<4D401DC4.5040701@libero.it>	<4D4022F4.1080200@freyther.de>
	<4D40269B.3000402@libero.it>
Message-ID: <4D4036EE.8060905@freyther.de>

On 01/26/2011 02:50 PM, Dario Lombardo wrote:
> 
> 
> On 01/26/2011 02:34 PM, Holger Hans Peter Freyther wrote:
>> You missed Peter's comment. I am going to fix it when pushing.
>>
> Opps... you're right. Thank you.
> 

One more nitpick was tabs vs. spaces. :)



From peter at stuge.se  Tue Jan 25 19:24:44 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 25 Jan 2011 20:24:44 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3EF055.6040006@libero.it>
References: <4D3EADA3.3090409@libero.it>
	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>
	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>
	<4D3EC8D4.4040401@freyther.de> <4D3ECD5D.8030701@libero.it>
	<4D3ECE4A.8030904@freyther.de>
	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>
	<4D3EEC84.5060000@libero.it> <4D3EED88.5000909@freyther.de>
	<4D3EF055.6040006@libero.it>
Message-ID: <20110125192444.10362.qmail@stuge.se>

Dario Lombardo wrote:
> Very good. This is the new patch that should fix both.
..

> +	printf("  -g --gps DEVICE		/dev/ttyACM0. GPS device.\n");
> +	printf("  -b --baud BAUDRATE	The baud rate of the GPS device\n");

What is the default baud rate? And where in the code are these
defaults being set?


> @@ -118,6 +123,16 @@ static int l23_cfg_handle(int c, const char *optarg)
>  	case 'n':
>  		RACH_MAX = 0;
>  		break;
> +    case 'g':
> +        snprintf(gps.device, ARRAY_SIZE(gps.device), "%s", optarg);
> +        // force string terminator
> +        gps.device[ARRAY_SIZE(gps.device - 1)] = '\0';

-1 should be outside the parentheses.


//Peter



From holger at freyther.de  Tue Jan 25 19:35:20 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 25 Jan 2011 20:35:20 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <20110125192444.10362.qmail@stuge.se>
References: <4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>
	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>
	<4D3EED88.5000909@freyther.de>	<4D3EF055.6040006@libero.it>
	<20110125192444.10362.qmail@stuge.se>
Message-ID: <4D3F25F8.9050808@freyther.de>

On 01/25/2011 08:24 PM, Peter Stuge wrote:
> Dario Lombardo wrote:

> 
>> +	printf("  -g --gps DEVICE		/dev/ttyACM0. GPS device.\n");
>> +	printf("  -b --baud BAUDRATE	The baud rate of the GPS device\n");
> 
> What is the default baud rate? And where in the code are these
> defaults being set?

src/common/gps.c, statically initialized.



From khorben at defora.org  Wed Jan 26 16:55:05 2011
From: khorben at defora.org (Pierre Pronchery)
Date: Wed, 26 Jan 2011 17:55:05 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3EED88.5000909@freyther.de>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>
	<4D3EED88.5000909@freyther.de>
Message-ID: <4D4051E9.3060902@defora.org>

On 01/25/2011 16:34, Holger Hans Peter Freyther wrote:
> 
> 2.) snprintf will not add a '\0' of optarg is of the length of 32 or longer

Actually it does, even though it may truncate the resulting string in
the process:

   ? snprintf() and vsnprintf() will write at most size-1 of the
     characters printed into the output string (the size'th character
     then gets the terminating `\0') ?

HTH,
-- 
khorben



From holger at freyther.de  Wed Jan 26 20:28:56 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 26 Jan 2011 21:28:56 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D4051E9.3060902@defora.org>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>	<4D3EED88.5000909@freyther.de>
	<4D4051E9.3060902@defora.org>
Message-ID: <4D408408.3010401@freyther.de>

On 01/26/2011 05:55 PM, Pierre Pronchery wrote:
> On 01/25/2011 16:34, Holger Hans Peter Freyther wrote:
>>
>> 2.) snprintf will not add a '\0' of optarg is of the length of 32 or longer
> 
> Actually it does, even though it may truncate the resulting string in
> the process:
> 
>    ? snprintf() and vsnprintf() will write at most size-1 of the
>      characters printed into the output string (the size'th character
>      then gets the terminating `\0') ?

The trailing null byte won't be added to str, if the  string  is  truncated.

from man snprintf on a Linux machine.



From khorben at defora.org  Thu Jan 27 12:04:09 2011
From: khorben at defora.org (Pierre Pronchery)
Date: Thu, 27 Jan 2011 13:04:09 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D408408.3010401@freyther.de>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>	<4D3EED88.5000909@freyther.de>	<4D4051E9.3060902@defora.org>
	<4D408408.3010401@freyther.de>
Message-ID: <4D415F39.30803@defora.org>

			Hi,

On 01/26/2011 21:28, Holger Hans Peter Freyther wrote:
> On 01/26/2011 05:55 PM, Pierre Pronchery wrote:
>> On 01/25/2011 16:34, Holger Hans Peter Freyther wrote:
>>>
>>> 2.) snprintf will not add a '\0' of optarg is of the length of 32 or longer
>>
>> Actually it does, even though it may truncate the resulting string in
>> the process:
>>
>>    ? snprintf() and vsnprintf() will write at most size-1 of the
>>      characters printed into the output string (the size'th character
>>      then gets the terminating `\0') ?
> 
> The trailing null byte won't be added to str, if the  string  is  truncated.
> 
> from man snprintf on a Linux machine.

first, I have to admit that the manual on Linux is very confusing and
unclear about snprintf(), which is why I pasted an extract from BSD.

Still, if you do:
=== BEGIN PASTE ===
$ cat snprintf.c && make snprintf && ./snprintf
#include <sys/utsname.h>
#include <stdio.h>
#include <string.h>

int main(void)
{
        struct utsname uts;
        char buf[16];
        int res;

        if(uname(&uts) == 0)
                printf("%s %s\n", uts.sysname, uts.release);
        memset(buf, 0xff, sizeof(buf));
        res = snprintf(buf, 4, "%s", "AAAAAAAA");
        printf("snprintf() returned %d, buf[3] = 0x%02x\n", res, buf[3]);
        return 0;
}
cc     snprintf.c   -o snprintf
Linux 2.6.9-023stab052.4-enterprise
snprintf() returned 8, buf[3] = 0x00
=== END PASTE ===

Which would tend to argue in my direction, as this was run on a Debian
Lenny host.

However, as I was kindly reminded by a friend in the meantime, you are
also right. Even though POSIX/SUSv3 itself says:

http://pubs.opengroup.org/onlinepubs/009695399/functions/printf.html

? The sprintf() function shall place output followed by the null byte,
'\0', in consecutive bytes starting at *s; it is the user's
responsibility to ensure that enough space is available.

The snprintf() function shall be equivalent to sprintf(), with the
addition of the n argument which states the size of the buffer referred
to by s. If n is zero, nothing shall be written and s may be a null
pointer. Otherwise, output bytes beyond the n-1st shall be discarded
instead of being written to the array, and a null byte is written at the
end of the bytes actually written into the array. ?

(the last sentence is important here)

there are platforms indeed which do not respect this:
http://msdn.microsoft.com/en-us/library/2ts7cx93%28v=vs.80%29.aspx

So on Windows you are right.

Now I guess the question is: is OsmocomBB intended to support non-POSIX
platforms natively?

HTH,
-- 
khorben



From holger at freyther.de  Thu Jan 27 16:23:13 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 27 Jan 2011 17:23:13 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D415F39.30803@defora.org>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>	<4D3EC8D4.4040401@freyther.de>	<4D3ECD5D.8030701@libero.it>	<4D3ECE4A.8030904@freyther.de>	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>	<4D3EEC84.5060000@libero.it>	<4D3EED88.5000909@freyther.de>	<4D4051E9.3060902@defora.org>	<4D408408.3010401@freyther.de>
	<4D415F39.30803@defora.org>
Message-ID: <4D419BF1.4010908@freyther.de>

On 01/27/2011 01:04 PM, Pierre Pronchery wrote:

> Now I guess the question is: is OsmocomBB intended to support non-POSIX
> platforms natively?

Hi Pierre,

thanks for digging into this. My general attitude is to assume the worst. It
is one of the functions that can have portability issues, it is somehow good
to know that the situation is looking better than i though.





From terrolokaust at gmail.com  Wed Jan 26 12:14:55 2011
From: terrolokaust at gmail.com (MArc Richter)
Date: Wed, 26 Jan 2011 13:14:55 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3EEC84.5060000@libero.it>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
	<4D3E9940.3080109@freyther.de>
	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
	<4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it>
	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>
	<AANLkTi=tJanOwsqGSVbMg-TXJ7ONrsice40p=6fAsht2@mail.gmail.com>
	<4D3EC8D4.4040401@freyther.de> <4D3ECD5D.8030701@libero.it>
	<4D3ECE4A.8030904@freyther.de>
	<AANLkTi=QNCM6RENvD+7N=rOj5_-84NyPtV6s-TYFEAKM@mail.gmail.com>
	<4D3EEC84.5060000@libero.it>
Message-ID: <AANLkTik28hQnMu5SnvA2rF2rsxgpOVzj75UvVnjtVMyg@mail.gmail.com>

Nice !
But do you want to deploy this patch to the repository to gave
everyone this feature ?

On Tue, Jan 25, 2011 at 4:30 PM, Dario Lombardo
<dario.lombardo at libero.it> wrote:
>
>
> On 01/25/2011 02:43 PM, MArc Richter wrote:
>>
>> Nice so if anyone could add this feature. I would write a Wiki page
>> how to use this
>>
> Attached there is my patch to support cmd line gps in cell_log.
>



From dario.lombardo at libero.it  Fri Jan 28 13:20:58 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Fri, 28 Jan 2011 14:20:58 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
	<4D3E9940.3080109@freyther.de>
	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
	<4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it>
	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>
Message-ID: <4D42C2BA.5020308@libero.it>



On 01/25/2011 12:34 PM, n0p [Luis Bernal] wrote:
> let the GPS warm up, maybe it just needs to start tracking the sats, 
> or add a printf to dump what data is coming from the GPS
>
I still can't make the gps working. In gps.c the line from serial port 
is parsed to find $GPGLL. My device doesn't give this line. These are 
the lines that it gives me

$GPGGA
$GPGSA
$GPGSV
$GPRMC

$GPGGA should give the position as $GPGLL should, but the software 
doesn't use it. Is it correct to say that the positioning data could be 
taken from different NMEA data? If yes, is it reasonable to add the 
support for other messages?



From mardnh at gmx.de  Fri Jan 28 18:08:28 2011
From: mardnh at gmx.de (Martin Hauke)
Date: Fri, 28 Jan 2011 19:08:28 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D42C2BA.5020308@libero.it>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>
	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>
	<4D42C2BA.5020308@libero.it>
Message-ID: <4D43061C.9050408@gmx.de>


> I still can't make the gps working. In gps.c the line from serial port
> is parsed to find $GPGLL. My device doesn't give this line. These are
> the lines that it gives me
>
> $GPGGA
> $GPGSA
> $GPGSV
> $GPRMC
>
> $GPGGA should give the position as $GPGLL should, but the software
> doesn't use it. Is it correct to say that the positioning data could
> be taken from different NMEA data? If yes, is it reasonable to add the
> support for other messages?
>
>

i've had the same issue. Use the attached patch to read the required
data from the $GPGGA NMEA sentence.

- Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: locosys-gpgga.patch
Type: text/x-patch
Size: 3190 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110128/5c7aac44/attachment.bin>

From dario.lombardo at libero.it  Mon Jan 31 12:34:16 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Mon, 31 Jan 2011 13:34:16 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D43061C.9050408@gmx.de>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>	<4D42C2BA.5020308@libero.it>
	<4D43061C.9050408@gmx.de>
Message-ID: <4D46AC48.3010206@libero.it>



On 01/28/2011 07:08 PM, Martin Hauke wrote:
>
> i've had the same issue. Use the attached patch to read the required
> data from the $GPGGA NMEA sentence.
>
> - Martin
Good, but why did you change the old code? Why don't you put something like

if (strcmp("$GPGLL") {
     // run the old code
} else if(strcmp("$GPGGA)) {
     // run your new code
} else {
     return;
}

That could support both the devices.



From squalyl at gmail.com  Mon Jan 31 12:46:54 2011
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Mon, 31 Jan 2011 13:46:54 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D46AC48.3010206@libero.it>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
	<4D3E9940.3080109@freyther.de>
	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
	<4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it>
	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>
	<4D42C2BA.5020308@libero.it> <4D43061C.9050408@gmx.de>
	<4D46AC48.3010206@libero.it>
Message-ID: <AANLkTik69R5rPCbc9Q0Upm=szKCiMxwW7EgNWQ+nr2SY@mail.gmail.com>

if (!strcmp("$GPGLL") {
   // run the old code
} else if(!strcmp("$GPGGA)) {
   // run your new code
} else {
   return;
}

would work better... ;-)

On Mon, Jan 31, 2011 at 1:34 PM, Dario Lombardo
<dario.lombardo at libero.it> wrote:
>
>
> On 01/28/2011 07:08 PM, Martin Hauke wrote:
>>
>> i've had the same issue. Use the attached patch to read the required
>> data from the $GPGGA NMEA sentence.
>>
>> - Martin
>
> Good, but why did you change the old code? Why don't you put something like
>
> if (strcmp("$GPGLL") {
> ? ?// run the old code
> } else if(strcmp("$GPGGA)) {
> ? ?// run your new code
> } else {
> ? ?return;
> }
>
> That could support both the devices.
>
>



From mad at auth.se  Mon Jan 31 15:28:04 2011
From: mad at auth.se (mad at auth.se)
Date: Mon, 31 Jan 2011 16:28:04 +0100
Subject: Fwd: =?UTF-8?Q?Cell=5Flog=20=3E=20gsmmap?=
In-Reply-To: <4D46AC48.3010206@libero.it>
References: "<AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>	<4D3EADA3.3090409@libero.it>	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>"
	<4D42C2BA.5020308@libero.it> <4D43061C.9050408@gmx.de>
	<4D46AC48.3010206@libero.it>
Message-ID: <2e464f1e06e30d1199879dff023e8be0@auth.se>

 On Mon, 31 Jan 2011 13:34:16 +0100, Dario Lombardo wrote:
> Good, but why did you change the old code? Why don't you put 
> something like
>
> if (strcmp("$GPGLL") {
>     // run the old code
> } else if(strcmp("$GPGGA)) {
>     // run your new code
> } else {
>     return;
> }
>
> That could support both the devices.

 BTW, best practice would be to implement parsing of the 
 "GPRMC"-sentence as it
 is the "Recommended Minimal Sentence" for every NMEA-capable gps 
 receiver.
 It contains time, date, latitude, longitude, validity, speed and 
 heading, so
 everything needed is delivered and should work with all receivers out 
 there.

 Regards,
   Mad




From squalyl at gmail.com  Mon Jan 31 16:08:39 2011
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Mon, 31 Jan 2011 17:08:39 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <2e464f1e06e30d1199879dff023e8be0@auth.se>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
	<4D3E9940.3080109@freyther.de>
	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
	<4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it>
	<AANLkTimbdcoZ5ZhObqAur5hgJzwWaxTDkAgmTC8UhNAk@mail.gmail.com>
	<4D42C2BA.5020308@libero.it> <4D43061C.9050408@gmx.de>
	<4D46AC48.3010206@libero.it>
	<2e464f1e06e30d1199879dff023e8be0@auth.se>
Message-ID: <AANLkTikGm9Tj0kej=Kec4t1f2B35Ru2+nfWdMW+rGC8v@mail.gmail.com>

I don't see a huge problem here.

Why not just parse whatever message with interesting info we get?

if (!strcmp("$GPGLL") {
   // extract coordinates and update buffer
} else if(!strcmp("$GPGGA)) {
   // extract coordinates and update buffer
} else if(!strcmp("$GPRMC)) {
   // extract coordinates and update buffer
} else if(!strcmp("$GPSuperProprietaryMessageWithAwesomePrecisionData")) {
   // extract coordinates and update buffer
} else {
   // no luck with this message
   return;
}

Sebastien

On Mon, Jan 31, 2011 at 4:28 PM,  <mad at auth.se> wrote:
> On Mon, 31 Jan 2011 13:34:16 +0100, Dario Lombardo wrote:
>>
>> Good, but why did you change the old code? Why don't you put something
>> like
>>
>> if (strcmp("$GPGLL") {
>> ? ?// run the old code
>> } else if(strcmp("$GPGGA)) {
>> ? ?// run your new code
>> } else {
>> ? ?return;
>> }
>>
>> That could support both the devices.
>
> BTW, best practice would be to implement parsing of the "GPRMC"-sentence as
> it
> is the "Recommended Minimal Sentence" for every NMEA-capable gps receiver.
> It contains time, date, latitude, longitude, validity, speed and heading, so
> everything needed is delivered and should work with all receivers out there.
>
> Regards,
> ?Mad
>
>
>



From peter at stuge.se  Tue Jan 25 11:40:10 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 25 Jan 2011 12:40:10 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3EADA3.3090409@libero.it>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
	<4D3E9940.3080109@freyther.de>
	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
	<4D3E9B93.4040202@freyther.de> <4D3EADA3.3090409@libero.it>
Message-ID: <20110125114010.4083.qmail@stuge.se>

Dario Lombardo wrote:
> The first issue was the /dev/ttyACM0 in the source code (my gps is
> /dev/ttyUSBX). I modified it in the code, but I think that a cmd
> /line option would be nicer.

Please fix the code so that it uses the value from the config.


//Peter



From holger at freyther.de  Tue Jan 25 11:43:35 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 25 Jan 2011 12:43:35 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <20110125114010.4083.qmail@stuge.se>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>	<4D3E9940.3080109@freyther.de>	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>	<4D3E9B93.4040202@freyther.de>
	<4D3EADA3.3090409@libero.it> <20110125114010.4083.qmail@stuge.se>
Message-ID: <4D3EB767.4050405@freyther.de>

On 01/25/2011 12:40 PM, Peter Stuge wrote:
> Dario Lombardo wrote:
>> The first issue was the /dev/ttyACM0 in the source code (my gps is
>> /dev/ttyUSBX). I modified it in the code, but I think that a cmd
>> /line option would be nicer.
> 
> Please fix the code so that it uses the value from the config.

It is not using the config at all. At the congress I added the possibility
that apps can have app specific config options. So it should be relative
trivial to add two options for the baudrate and the device. This should be
about 15 lines of code. I don't have a GPS device, it works for Andreas like
it is, so someone should step and contribute this 15 lines of code.




From terrolokaust at gmail.com  Tue Jan 25 11:02:29 2011
From: terrolokaust at gmail.com (MArc Richter)
Date: Tue, 25 Jan 2011 12:02:29 +0100
Subject: Fwd: Cell_log > gsmmap
In-Reply-To: <4D3E9B93.4040202@freyther.de>
References: <AANLkTikCUaV-aNu5z1wRgk=_kbm_7+CDD_GZ-OEKLiFk@mail.gmail.com>
	<4D3E9940.3080109@freyther.de>
	<AANLkTikfDGcXjWaXx1Wr7TJ3LU_uQkRJZWhzWYR+BUoB@mail.gmail.com>
	<AANLkTinX48P9PsRA1pbnANoYaUgKq45tzhDGOJ-iquih@mail.gmail.com>
	<4D3E9B93.4040202@freyther.de>
Message-ID: <AANLkTikKQk3jQVcTD5578xnKu7hCbJwxJi_JiErePy-7@mail.gmail.com>

So let me short summarize this
1. conntect GPS device
2. in the config (osmocom.cfg) change the following lines from
.....
!
gps device /dev/ttyACM0
gps baudrate default
no gps enable
!
ms 1
 sim reader
.......
to
....
!
gps device /dev/ttyACM0
gps baudrate default
gps enable
!
ms 1
 sim reader
.....

3. run Cell_log
4. convert Cell_log with gsmmap to a valid .kml file

is this correct ?



On Tue, Jan 25, 2011 at 10:44 AM, Holger Hans Peter Freyther <
holger at freyther.de> wrote:

> On 01/25/2011 10:40 AM, MArc Richter wrote:
> > Do i need a GPS Reciver ?
> > I tought that it will calculate the location over Triangulation ?
>
> You will need one, even for triangulation you will need to some base
> coordinates. Please feel encouraged to create a wiki page for the cell_log
> application to describe its requirements and features.
>
>
>
> Relevant sourcecode to initiate opening the GPS device:
>
> http://bb.osmocom.org/trac/browser/src/host/layer23/src/misc/cell_log.c#L789
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/f5b1e3d9/attachment.htm>

From b.alecu at yahoo.com  Tue Jan 25 11:24:09 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Tue, 25 Jan 2011 03:24:09 -0800 (PST)
Subject: Cell_log > gsmmap
Message-ID: <972619.53541.qm@web46211.mail.sp1.yahoo.com>

A Wiki on how to use it would be great!



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/d1cc608a/attachment.htm>

From terrolokaust at gmail.com  Tue Jan 25 11:34:01 2011
From: terrolokaust at gmail.com (MArc Richter)
Date: Tue, 25 Jan 2011 12:34:01 +0100
Subject: Cell_log > gsmmap
In-Reply-To: <972619.53541.qm@web46211.mail.sp1.yahoo.com>
References: <972619.53541.qm@web46211.mail.sp1.yahoo.com>
Message-ID: <AANLkTinP8mqtcvciLMpbW9e6RvQDnf3JUxWGpcvhAXU4@mail.gmail.com>

No Problem I'll write a Wiki article about it but i've never run it sucessfully
so i wrote thes 5 steps to get re confirmation. These Steps are okay ?

i will try this with this device NL-402U ublox5
This Device should work out of the box with Linux see manuel
http://www.navilock.de/view/PDFs/Linux_mit_uBlox/605





On Tue, Jan 25, 2011 at 12:24 PM, Bogdan Alecu <b.alecu at yahoo.com> wrote:
>
> A Wiki on how to use it would be great!
>



From b.alecu at yahoo.com  Tue Jan 25 14:45:08 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Tue, 25 Jan 2011 06:45:08 -0800 (PST)
Subject: Cell_log > gsmmap
In-Reply-To: <AANLkTinP8mqtcvciLMpbW9e6RvQDnf3JUxWGpcvhAXU4@mail.gmail.com>
Message-ID: <816870.68056.qm@web46209.mail.sp1.yahoo.com>

"3. run Cell_log
4. convert Cell_log with gsmmap to a valid .kml file"

Could these two steps be more detailed? For example when you say to run cell_log it would be great if you could actually copy-paste what you wrote in the terminal (the entire line) and a few lines of the output. The same about step 4. Thank you.



--- On Tue, 1/25/11, MArc Richter <terrolokaust at gmail.com> wrote:

From: MArc Richter <terrolokaust at gmail.com>
Subject: Re: Cell_log > gsmmap
To: "Bogdan Alecu" <b.alecu at yahoo.com>
Cc: baseband-devel at lists.osmocom.org
Date: Tuesday, January 25, 2011, 11:34 AM

No Problem I'll write a Wiki article about it but i've never run it sucessfully
so i wrote thes 5 steps to get re confirmation. These Steps are okay ?

i will try this with this device NL-402U ublox5
This Device should work out of the box with Linux see manuel
http://www.navilock.de/view/PDFs/Linux_mit_uBlox/605





On Tue, Jan 25, 2011 at 12:24 PM, Bogdan Alecu <b.alecu at yahoo.com> wrote:
>
> A Wiki on how to use it would be great!
>



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/23e71677/attachment.htm>

From terrolokaust at gmail.com  Tue Jan 25 15:06:56 2011
From: terrolokaust at gmail.com (MArc Richter)
Date: Tue, 25 Jan 2011 16:06:56 +0100
Subject: Cell_log > gsmmap
In-Reply-To: <816870.68056.qm@web46209.mail.sp1.yahoo.com>
References: <AANLkTinP8mqtcvciLMpbW9e6RvQDnf3JUxWGpcvhAXU4@mail.gmail.com>
	<816870.68056.qm@web46209.mail.sp1.yahoo.com>
Message-ID: <AANLkTimW=EwmfE1ecGq7JuL3CQPA6K8Lz-FL9XCiM9Dk@mail.gmail.com>

Cell_log [Fileparameter]
Attached file is the cellog output. Is it what you mean?

On Tue, Jan 25, 2011 at 3:45 PM, Bogdan Alecu <b.alecu at yahoo.com> wrote:

> "3. run Cell_log
> 4. convert Cell_log with gsmmap to a valid .kml file"
>
> Could these two steps be more detailed? For example when you say to run
> cell_log it would be great if you could actually copy-paste what you wrote
> in the terminal (the entire line) and a few lines of the output. The same
> about step 4. Thank you.
>
>
>
> --- On *Tue, 1/25/11, MArc Richter <terrolokaust at gmail.com>* wrote:
>
>
> From: MArc Richter <terrolokaust at gmail.com>
> Subject: Re: Cell_log > gsmmap
> To: "Bogdan Alecu" <b.alecu at yahoo.com>
> Cc: baseband-devel at lists.osmocom.org
> Date: Tuesday, January 25, 2011, 11:34 AM
>
>
> No Problem I'll write a Wiki article about it but i've never run it
> sucessfully
> so i wrote thes 5 steps to get re confirmation. These Steps are okay ?
>
> i will try this with this device NL-402U ublox5
> This Device should work out of the box with Linux see manuel
> http://www.navilock.de/view/PDFs/Linux_mit_uBlox/605
>
>
>
>
>
> On Tue, Jan 25, 2011 at 12:24 PM, Bogdan Alecu <b.alecu at yahoo.com<http://mc/compose?to=b.alecu at yahoo.com>>
> wrote:
> >
> > A Wiki on how to use it would be great!
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/c04a3f4a/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmocom.log
Type: application/octet-stream
Size: 55317 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/c04a3f4a/attachment.obj>

From spaar at mirider.augusta.de  Tue Jan 25 18:19:34 2011
From: spaar at mirider.augusta.de (Dieter Spaar)
Date: Tue, 25 Jan 2011 18:19:34 
Subject: C99 [was Fwd: Cell_log > gsmmap]
Message-ID: <4d3f1436.mirider@mirider.augusta.de>

Hello Holger,

On Tue, 25 Jan 2011 16:51:02 +0100, "Holger Hans Peter Freyther" <holger at freyther.de> wrote:
> 
> Almost perfect. I can apply and modify myself or you could do two things. We
> tend to avoid the '//' comments, they were only added in C99 and used to be a
> GCC extension for C.

This is a good one ;-) One of the biggest problems when I tried a long
time ago to compile any of OpenBSC or OsmocomBB with a different compiler
than GCC were designated initializer which are _heavily_ used all over the
sources (I don't question their advantage, I only mention it). They are
a C99 feature (besides the library function snprintf() in the patch you
commented). So I would not care about the '//', this was the smallest
problem I had when I did my porting experiment (in fact the compilers
I am aware of silently accept it).

Just out of interest, do we really want to to avoid C99 ? I know there
is this implicit "kernel style" coding rule, does it include C99 ?

Please note that I don't want to discuss this, I use GCC from
Cygwin and can find workarounds for Linux specific issues on Windows
on my own, so I don't care that much. I am just interested in the
reasons for using C99 or not.

Best regards,
  Dieter
-- 
Dieter Spaar, Germany                           spaar at mirider.augusta.de



From holger at freyther.de  Tue Jan 25 19:42:36 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 25 Jan 2011 20:42:36 +0100
Subject: C99 [was Fwd: Cell_log > gsmmap]
In-Reply-To: <4d3f1436.mirider@mirider.augusta.de>
References: <4d3f1436.mirider@mirider.augusta.de>
Message-ID: <4D3F27AC.7030604@freyther.de>

On 01/25/2011 06:19 PM, Dieter Spaar wrote:
> Hello Holger,

Hi Dieter,

> 
> On Tue, 25 Jan 2011 16:51:02 +0100, "Holger Hans Peter Freyther" <holger at freyther.de> wrote:
>>
>> Almost perfect. I can apply and modify myself or you could do two things. We
>> tend to avoid the '//' comments, they were only added in C99 and used to be a
>> GCC extension for C.
> 
> This is a good one ;-)

hehe.


> Just out of interest, do we really want to to avoid C99 ? I know there
> is this implicit "kernel style" coding rule, does it include C99 ?

seems to be just kernel style and not really related to C99.

Documentation/CodingStyle
Linux style for comments is the C89 "/* ... */" style.
Don't use C99-style "// ..." comments.


> 
> I am just interested in the reasons for using C99 or not.

That is a good question. The only practical thing would be C/C++ interworking
as C++ still assumes a C89 environment, another one is that GCC still does not
default to C99.



From steve at steve-m.de  Tue Jan 25 20:01:46 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Tue, 25 Jan 2011 21:01:46 +0100
Subject: C99 [was Fwd: Cell_log > gsmmap]
In-Reply-To: <4D3F27AC.7030604@freyther.de>
References: <4d3f1436.mirider@mirider.augusta.de>
	<4D3F27AC.7030604@freyther.de>
Message-ID: <4D3F2C2A.4040002@steve-m.de>

Hi,

On 25.01.2011 20:42, Holger Hans Peter Freyther wrote:

> That is a good question. The only practical thing would be C/C++ interworking
> as C++ still assumes a C89 environment

But wasn't it C++ that implemented the //-style comments first, and
C99 that added them for more C++ compatibility?

/* Regards,
Steve */



From holger at freyther.de  Tue Jan 25 20:05:57 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 25 Jan 2011 21:05:57 +0100
Subject: C99 [was Fwd: Cell_log > gsmmap]
In-Reply-To: <4D3F2C2A.4040002@steve-m.de>
References: <4d3f1436.mirider@mirider.augusta.de>
	<4D3F27AC.7030604@freyther.de> <4D3F2C2A.4040002@steve-m.de>
Message-ID: <4D3F2D25.3040606@freyther.de>

On 01/25/2011 09:01 PM, Steve Markgraf wrote:
> Hi,
> 
> On 25.01.2011 20:42, Holger Hans Peter Freyther wrote:
> 
>> That is a good question. The only practical thing would be C/C++ interworking
>> as C++ still assumes a C89 environment
> 
> But wasn't it C++ that implemented the //-style comments first, and
> C99 that added them for more C++ compatibility?

This was a general remark on C99 and C++. The current standard is only
compatible with C89, only the upcoming C++ standard will add C99 support.

For all of our concerns it does not matter, in the worse case one has problems
including our header files in C++ but then we can fix things.



From mardnh at gmx.de  Tue Jan 25 21:10:11 2011
From: mardnh at gmx.de (Martin Hauke)
Date: Tue, 25 Jan 2011 22:10:11 +0100
Subject: Cell_log > gsmmap
In-Reply-To: <4D3F2D25.3040606@freyther.de>
References: <4d3f1436.mirider@mirider.augusta.de>	<4D3F27AC.7030604@freyther.de>
	<4D3F2C2A.4040002@steve-m.de> <4D3F2D25.3040606@freyther.de>
Message-ID: <4D3F3C33.2080203@gmx.de>

> i will try this with this device NL-402U ublox5
> This Device should work out of the box with Linux see manuel
> http://www.navilock.de/view/PDFs/Linux_mit_uBlox/605


i've had similar problems with my sirf star III -based locosys btg-31.
After looking at the source code i'd found the issue - only the the
"GPGLL"-NMEA sentence was parsed.

Since my gps-device only supports GPGGA, GPRMC, GPGSA and GPGSV i've
patched /src/host/layer23/src/common/gps.c to get the required data from
GPGGA.

With that i'm also able to get "el-cheapo" support for gpsd (with help
from socat and gpspipe):

/dev/ttyUSB0    // my gps-receiver device
/dev/ttyACM0    // pseudo terminal (created with socat)

start gpsd and connect to the gps receiver
# gpsd -N -n -D 4 /dev/ttyUSB0

create a pseudo terminal and feed it with the output of 'gpspipe -r'
# socat -d -d pty,link=/dev/ttyACM0,raw,echo=0 "exec:gpspipe -r"

Now you can start cell_log and read the gps-data from the newly created
pseudo terminal.


This is by no means a proper integration for gpsd as with libgps/libgpsd
- but at least it works for me.


- Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/c03a1135/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: locosys-gpgga.patch
Type: text/x-patch
Size: 3190 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/c03a1135/attachment.bin>

From b.alecu at yahoo.com  Wed Jan 26 07:27:11 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Tue, 25 Jan 2011 23:27:11 -0800 (PST)
Subject: Cell_log > gsmmap
Message-ID: <534332.23523.qm@web46206.mail.sp1.yahoo.com>

I just thought of another way of using cell_log without GPS. The resulting KML could be parsed and sent to opencellid project, this way we could get the lat-long coordinates and afterward create another kml and send it to Google.
Ex: http://www.opencellid.org/cell/get?mcc=232&mnc=01&cellid=1721&lac=4269



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110125/62d50318/attachment.htm>

From ml at mail.tsaitgaist.info  Wed Jan 26 09:40:33 2011
From: ml at mail.tsaitgaist.info (ml at mail.tsaitgaist.info)
Date: Wed, 26 Jan 2011 10:40:33 +0100
Subject: Cell_log > gsmmap
In-Reply-To: <534332.23523.qm@web46206.mail.sp1.yahoo.com>
References: <534332.23523.qm@web46206.mail.sp1.yahoo.com>
Message-ID: <4D3FEC11.8060709@mail.tsaitgaist.info>

another free cell database is openBmap : http://realtimeblog.free.fr/

Kevin

On 01/26/2011 08:27 AM, Bogdan Alecu wrote:

> Ex: http://www.opencellid.org/cell/get?mcc=232&mnc=01&cellid=1721&lac=4269
> 
> 



From b.alecu at yahoo.com  Wed Jan 26 08:09:53 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Wed, 26 Jan 2011 00:09:53 -0800 (PST)
Subject: Cell_log > gsmmap
Message-ID: <293222.91350.qm@web46215.mail.sp1.yahoo.com>

Or even better, use Google API and this way you could also include the Signal strenght and Timing advance for a better position.
See http://translate.google.com/translate?js=y&prev=_t&hl=en&ie=UTF-8&layout=1&eotf=1&u=http%3A%2F%2Fwww.cnblogs.com%2Fpsunny%2Farchive%2F2010%2F04%2F17%2F1714427.html&sl=zh-CN&tl=en


--- On Wed, 1/26/11, Bogdan Alecu <b.alecu at yahoo.com> wrote:

From: Bogdan Alecu <b.alecu at yahoo.com>
Subject: Re: Cell_log > gsmmap
To: 
Cc: baseband-devel at lists.osmocom.org
Date: Wednesday, January 26, 2011, 7:27 AM

I just thought of another way of using cell_log without GPS. The resulting KML could be parsed and sent to opencellid project, this way we could get the lat-long coordinates and afterward create another kml and send it to Google.
Ex: http://www.opencellid.org/cell/get?mcc=232&mnc=01&cellid=1721&lac=4269









      


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110126/db595614/attachment.htm>

From wolfram at the-dreams.de  Tue Jan 25 20:39:54 2011
From: wolfram at the-dreams.de (Wolfram Sang)
Date: Tue, 25 Jan 2011 21:39:54 +0100
Subject: C99 [was Fwd: Cell_log > gsmmap]
In-Reply-To: <4D3F27AC.7030604@freyther.de>
References: <4d3f1436.mirider@mirider.augusta.de>
	<4D3F27AC.7030604@freyther.de>
Message-ID: <4D3F351A.40707@the-dreams.de>

>> Just out of interest, do we really want to to avoid C99 ? I know there
>> is this implicit "kernel style" coding rule, does it include C99 ?
> 
> seems to be just kernel style and not really related to C99.
> 
> Documentation/CodingStyle
> Linux style for comments is the C89 "/* ... */" style.
> Don't use C99-style "// ..." comments.

The main advantage here is that a consistent commenting style helps
readability IMO. When doing kernel code, I use '//' only for private
TODO-areas, because it sticks out so much :)

Regards,

   Wolfram



From peter at stuge.se  Tue Jan 25 21:31:37 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 25 Jan 2011 22:31:37 +0100
Subject: [PATCH] Adjust top-level Makefile for arm-none-eabi toolchain
Message-ID: <1295991097-26998-1-git-send-email-peter@stuge.se>

The gnuarm.com toolchain works fine but is very old. And although it is
based on newlib, the os name in the tuple that we used to configure for
is arm-elf-linux, which is of course bogus since we are not building
Linux applications.

Finally, CC= should never be set, instead configure should detect the
right compiler using the --host tuple.
---
 src/Makefile |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/Makefile b/src/Makefile
index b3594c1..e66f0ff 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -1,10 +1,10 @@
 
 # this is not really used as we don't do 'make install'. You can still specify
 # it in case you _want_ to manually 'make install' the target libosmocore.
-CROSS_INST_PREFIX=/usr/local/stow/osmocom-bb/arm-elf
+CROSS_INST_PREFIX ?= /usr/local/stow/osmocom-bb/arm-2010.09
 
 # this is the prefix of your cross-toolchain programs
-CROSS_TOOL_PREFIX=arm-elf-
+CROSS_TOOL_PREFIX ?= arm-none-eabi-
 
 TOPDIR=$(shell pwd)
 OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \
@@ -37,9 +37,9 @@ shared/libosmocore/build-target:
 
 shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target
 	cd shared/libosmocore/build-target && ../configure \
-			--host=arm-elf-linux --disable-vty --enable-panic-infloop \
+			--host=arm-none-eabi --disable-vty --enable-panic-infloop \
 			--disable-shared --disable-talloc --disable-tests \
-		CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs"
+		CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs"
 
 shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile
 	cd shared/libosmocore/build-target && make
-- 
1.7.2




From 246tnt at gmail.com  Tue Jan 25 21:38:45 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Tue, 25 Jan 2011 22:38:45 +0100
Subject: [PATCH] Adjust top-level Makefile for arm-none-eabi toolchain
In-Reply-To: <1295991097-26998-1-git-send-email-peter@stuge.se>
References: <1295991097-26998-1-git-send-email-peter@stuge.se>
Message-ID: <AANLkTi=ApWqMS2La6JF13o+FHOk_=hi0T6XRCDdjZEJm@mail.gmail.com>

Hi,

On Tue, Jan 25, 2011 at 10:31 PM, Peter Stuge <peter at stuge.se> wrote:
> The gnuarm.com toolchain works fine but is very old. And although it is
> based on newlib, the os name in the tuple that we used to configure for
> is arm-elf-linux, which is of course bogus since we are not building
> Linux applications.

Well, I don't really agree here.

arm-elf- is a perfectly valid prefix and not only used by the gnuarm
toolchain ...

Also, the cross prefix to use should _always_ be entirely selectable
by an env variable, and it looks to me like your patch removes that.
(i.e. if I do make CROSS_TOLL_PREFIX=arm-elf-  it's not gonna work
anymore AFAICT)

Cheers,

    Sylvain



From peter at stuge.se  Tue Jan 25 21:55:08 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 25 Jan 2011 22:55:08 +0100
Subject: [PATCH] Adjust top-level Makefile for arm-none-eabi toolchain
In-Reply-To: <AANLkTi=ApWqMS2La6JF13o+FHOk_=hi0T6XRCDdjZEJm@mail.gmail.com>
References: <1295991097-26998-1-git-send-email-peter@stuge.se>
	<AANLkTi=ApWqMS2La6JF13o+FHOk_=hi0T6XRCDdjZEJm@mail.gmail.com>
Message-ID: <20110125215508.31666.qmail@stuge.se>

Thanks for review!

Sylvain Munaut wrote:
> On Tue, Jan 25, 2011 at 10:31 PM, Peter Stuge <peter at stuge.se> wrote:
> > The gnuarm.com toolchain works fine but is very old. And although it is
> > based on newlib, the os name in the tuple that we used to configure for
> > is arm-elf-linux, which is of course bogus since we are not building
> > Linux applications.
> 
> Well, I don't really agree here.
> 
> arm-elf- is a perfectly valid prefix and not only used by the gnuarm
> toolchain ...

Note the difference between arm-elf and arm-elf-linux. The latter is
what we configure for. But because that compiler doesn't work CC is
overridden with a hard code to arm-elf-gcc. (Which works fine!)


> Also, the cross prefix to use should _always_ be entirely selectable
> by an env variable, and it looks to me like your patch removes that.
> (i.e. if I do make CROSS_TOLL_PREFIX=arm-elf-  it's not gonna work
> anymore AFAICT)

It looks like the other way around to me. I added ?= so that the
variable only gets set if it does not already have a value, while
previously I think it was overwritten by the value in Makefile?

Anyway I reworked a little, so that HOST= can be used to specify the
desired host tuple, which is then used both for configure, and passed
on to the target/firmware Makefile. Patch attached.


//Peter

From peter at stuge.se  Tue Jan 25 21:27:34 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 25 Jan 2011 22:27:34 +0100
Subject: [PATCH] Adjust top-level Makefile for arm-none-eabi toolchain
Message-ID: <mailman.14.1641743545.42824.baseband-devel@lists.osmocom.org>

The gnuarm.com toolchain works fine but is very old. And although
it is based on newlib, the tuple that we used to configure for was
arm-elf-linux, which is of course bogus since we aren't building
Linux applications.

This patch optimizes for the CodeSourcery G++ Lite 2010.09 ARM EABI
toolchain, and assumes that it was unpacked next to the old one.
Download here:

http://www.codesourcery.com/sgpp/lite/arm/portal/release1592

(I haven't gotten the Linux Installer to work, so I recommend the TAR.)

And since CC is detected by configure when a valid host tuple is given
and that toolchain is sane there's no need for us to hard-code the
gnuarm.com compiler name in our Makefile.
---
 src/Makefile |   11 +++++++----
 1 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/src/Makefile b/src/Makefile
index b3594c1..f2d935b 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -1,10 +1,13 @@
 
 # this is not really used as we don't do 'make install'. You can still specify
 # it in case you _want_ to manually 'make install' the target libosmocore.
-CROSS_INST_PREFIX=/usr/local/stow/osmocom-bb/arm-elf
+CROSS_INST_PREFIX ?= /usr/local/stow/osmocom-bb/arm-2010.09
+
+# this is the host tuple of your cross-toolchain
+HOST ?= arm-none-eabi-
 
 # this is the prefix of your cross-toolchain programs
-CROSS_TOOL_PREFIX=arm-elf-
+CROSS_TOOL_PREFIX ?= $(CROSS)-
 
 TOPDIR=$(shell pwd)
 OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \
@@ -37,9 +40,9 @@ shared/libosmocore/build-target:
 
 shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target
 	cd shared/libosmocore/build-target && ../configure \
-			--host=arm-elf-linux --disable-vty --enable-panic-infloop \
+			--host=$(HOST) --disable-vty --enable-panic-infloop \
 			--disable-shared --disable-talloc --disable-tests \
-		CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs"
+		CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs"
 
 shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile
 	cd shared/libosmocore/build-target && make
-- 
1.7.2


--dMyqICaxQaaUjrCL--



From peter at stuge.se  Tue Jan 25 22:02:32 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 25 Jan 2011 23:02:32 +0100
Subject: [PATCH v3] Adjust top-level Makefile for arm-none-eabi toolchain
In-Reply-To: <20110125215508.31666.qmail@stuge.se>
References: <1295991097-26998-1-git-send-email-peter@stuge.se>
	<AANLkTi=ApWqMS2La6JF13o+FHOk_=hi0T6XRCDdjZEJm@mail.gmail.com>
	<20110125215508.31666.qmail@stuge.se>
Message-ID: <20110125220232.542.qmail@stuge.se>

Peter Stuge wrote:
> Anyway I reworked a little, so that HOST= can be used

But then I typoed it when it was used. Here's an update.


//Peter

From peter at stuge.se  Tue Jan 25 21:27:34 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 25 Jan 2011 22:27:34 +0100
Subject: [PATCH] Adjust top-level Makefile for arm-none-eabi toolchain
Message-ID: <mailman.15.1641743545.42824.baseband-devel@lists.osmocom.org>

The gnuarm.com toolchain works fine but is very old. And although
it is based on newlib, the tuple that we used to configure for was
arm-elf-linux, which is of course bogus since we aren't building
Linux applications.

This patch optimizes for the CodeSourcery G++ Lite 2010.09 ARM EABI
toolchain, and assumes that it was unpacked next to the old one.
Download here:

http://www.codesourcery.com/sgpp/lite/arm/portal/release1592

(I haven't gotten the Linux Installer to work, so I recommend the TAR.)

And since CC is detected by configure when a valid host tuple is given
and that toolchain is sane there's no need for us to hard-code the
gnuarm.com compiler name in our Makefile.
---
 src/Makefile |   11 +++++++----
 1 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/src/Makefile b/src/Makefile
index b3594c1..bb34175 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -1,10 +1,13 @@
 
 # this is not really used as we don't do 'make install'. You can still specify
 # it in case you _want_ to manually 'make install' the target libosmocore.
-CROSS_INST_PREFIX=/usr/local/stow/osmocom-bb/arm-elf
+CROSS_INST_PREFIX ?= /usr/local/stow/osmocom-bb/arm-2010.09
+
+# this is the host tuple of your cross-toolchain
+HOST ?= arm-none-eabi-
 
 # this is the prefix of your cross-toolchain programs
-CROSS_TOOL_PREFIX=arm-elf-
+CROSS_TOOL_PREFIX ?= $(HOST)-
 
 TOPDIR=$(shell pwd)
 OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \
@@ -37,9 +40,9 @@ shared/libosmocore/build-target:
 
 shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target
 	cd shared/libosmocore/build-target && ../configure \
-			--host=arm-elf-linux --disable-vty --enable-panic-infloop \
+			--host=$(HOST) --disable-vty --enable-panic-infloop \
 			--disable-shared --disable-talloc --disable-tests \
-		CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs"
+		CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs"
 
 shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile
 	cd shared/libosmocore/build-target && make
-- 
1.7.2


--nEsDIrWrg+hrB7l1--



From holger at freyther.de  Tue Jan 25 22:14:43 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 25 Jan 2011 23:14:43 +0100
Subject: [PATCH v3] Adjust top-level Makefile for arm-none-eabi toolchain
In-Reply-To: <20110125220232.542.qmail@stuge.se>
References: <1295991097-26998-1-git-send-email-peter@stuge.se>	<AANLkTi=ApWqMS2La6JF13o+FHOk_=hi0T6XRCDdjZEJm@mail.gmail.com>	<20110125215508.31666.qmail@stuge.se>
	<20110125220232.542.qmail@stuge.se>
Message-ID: <4D3F4B53.1070607@freyther.de>

On 01/25/2011 11:02 PM, Peter Stuge wrote:
> +HOST ?= arm-none-eabi-
> +CROSS_TOOL_PREFIX ?= $(HOST)-

one - too many?



From peter at stuge.se  Tue Jan 25 22:48:53 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 25 Jan 2011 23:48:53 +0100
Subject: [PATCH v4] Allow top-level Makefile to use arm-none-eabi toolchain
In-Reply-To: <20110125220232.542.qmail@stuge.se>
References: <1295991097-26998-1-git-send-email-peter@stuge.se>
	<AANLkTi=ApWqMS2La6JF13o+FHOk_=hi0T6XRCDdjZEJm@mail.gmail.com>
	<20110125215508.31666.qmail@stuge.se>
	<20110125220232.542.qmail@stuge.se>
Message-ID: <20110125224854.8427.qmail@stuge.se>

Peter Stuge wrote:
> > Anyway I reworked a little, so that HOST= can be used
> 
> But then I typoed it when it was used. Here's an update.

Maybe this is the winner? :)

After more good review and discussion with Sylvain the next version
will autodetect arm-elf-gcc and default to using arm-elf for prefix
if it is found. If not found will assume arm-none-eabi is available.


//Peter

From peter at stuge.se  Tue Jan 25 21:27:34 2011
From: peter at stuge.se (Peter Stuge)
Date: Tue, 25 Jan 2011 22:27:34 +0100
Subject: [PATCH] Allow top-level Makefile to use arm-none-eabi toolchain
Message-ID: <mailman.16.1641743545.42824.baseband-devel@lists.osmocom.org>

The gnuarm.com toolchain works fine but is very old. And although
it is based on newlib, the tuple that we used to configure for was
arm-elf-linux, which is bogus since we aren't building for Linux.

This patch optimizes for the CodeSourcery G++ Lite 2010.09 ARM EABI
toolchain instead, and for libosmocore installation it assumes that
the new toolchain was unpacked next to the old one. Download it here:

http://www.codesourcery.com/sgpp/lite/arm/portal/release1592

(The Linux Installer seems not to work reliably so I recommend the TAR.)

Since CC is detected by configure when the host tuple points to a sane
toolchain we shouldn't hard-code the gnuarm.com compiler.

The patch autodetects arm-elf-gcc installed in PATH, and uses arm-elf
as prefix if it is found. Otherwise, it defaults to arm-none-eabi.

make CROSS_HOST=arm-xyzzy can be used to override on the command line.
---
 src/Makefile |   11 +++++++----
 1 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/src/Makefile b/src/Makefile
index b3594c1..402f28a 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -1,10 +1,13 @@
 
 # this is not really used as we don't do 'make install'. You can still specify
 # it in case you _want_ to manually 'make install' the target libosmocore.
-CROSS_INST_PREFIX=/usr/local/stow/osmocom-bb/arm-elf
+CROSS_INST_PREFIX ?= /usr/local/stow/osmocom-bb/arm-2010.09
+
+# this is the host tuple of your cross-toolchain
+CROSS_HOST ?= $(shell which arm-elf-gcc >/dev/null 2>&1 && echo arm-elf || echo arm-none-eabi)
 
 # this is the prefix of your cross-toolchain programs
-CROSS_TOOL_PREFIX=arm-elf-
+CROSS_TOOL_PREFIX=$(CROSS_HOST)-
 
 TOPDIR=$(shell pwd)
 OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \
@@ -37,9 +40,9 @@ shared/libosmocore/build-target:
 
 shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target
 	cd shared/libosmocore/build-target && ../configure \
-			--host=arm-elf-linux --disable-vty --enable-panic-infloop \
+			--host=$(CROSS_HOST) --disable-vty --enable-panic-infloop \
 			--disable-shared --disable-talloc --disable-tests \
-		CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs"
+		CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs"
 
 shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile
 	cd shared/libosmocore/build-target && make
-- 
1.7.2


--ibvzjYYg+QDzMCy1--



From mgr at xviews.de  Tue Jan 25 22:55:06 2011
From: mgr at xviews.de (Michael Grzeschik)
Date: Tue, 25 Jan 2011 23:55:06 +0100
Subject: [PATCH v3] Adjust top-level Makefile for arm-none-eabi toolchain
In-Reply-To: <20110125220232.542.qmail@stuge.se>
References: <1295991097-26998-1-git-send-email-peter@stuge.se>
	<AANLkTi=ApWqMS2La6JF13o+FHOk_=hi0T6XRCDdjZEJm@mail.gmail.com>
	<20110125215508.31666.qmail@stuge.se>
	<20110125220232.542.qmail@stuge.se>
Message-ID: <20110125225506.GB5633@jamie.key>

Hi Peter,

On Tue, Jan 25, 2011 at 11:02:32PM +0100, Peter Stuge wrote:
> +HOST ?= arm-none-eabi-

Remove that line.

>  
>  # this is the prefix of your cross-toolchain programs
> -CROSS_TOOL_PREFIX=arm-elf-
> +CROSS_TOOL_PREFIX ?= $(HOST)-

Leave that unchanged.

>  
>  TOPDIR=$(shell pwd)
>  OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \
> @@ -37,9 +40,9 @@ shared/libosmocore/build-target:
>  
>  shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target
>  	cd shared/libosmocore/build-target && ../configure \
> -			--host=arm-elf-linux --disable-vty --enable-panic-infloop \
> +			--host=$(HOST) --disable-vty --enable-panic-infloop \

Use here instead:       --host=$(CROSS_TOOL_PREFIX:-=)

>  			--disable-shared --disable-talloc --disable-tests \
> -		CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs"
> +		CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs"
>  
>  shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile
>  	cd shared/libosmocore/build-target && make

Regards,
Michael



From khorben at defora.org  Wed Jan 26 15:34:10 2011
From: khorben at defora.org (Pierre Pronchery)
Date: Wed, 26 Jan 2011 16:34:10 +0100
Subject: [PATCH] How to compile osmocom on NetBSD
Message-ID: <4D403EF2.4090403@defora.org>

			Hi baseband developers,

a couple days ago I managed to compile osmocom's binaries and firmware
files from a NetBSD host, using a cross-compilation toolchain generated
with the standard build script on this system. This was actually quite
straightforward, but required some patches and tricks, so I figured it'd
be worth posting it here.

I will write the procedure in more details on my blog [1], in my case it
was enough to do this:
$ CPATH="/usr/include" gmake \
CROSS_TOOL_PREFIX="/home/arm/tools/bin/arm--netbsdelf-"

The patch itself is certainly more interesting to discuss here. I do not
expect it to be fully merged, but I think it may raise interesting points:

- src/shared/libosmocore/src/Makefile.am
  linking with "-ldl" is hardcoded, but breaks the build on systems
  where it is not required; this is a usual portability issue, already
  solved about a thousand times, I'll try to come up with a cleaner
  solution here.

- src/shared/libosmocore/src/gsm_utils.c
  I think this one is quite elegant, allowing to build even without
  support for backtraces; an additional #warning would help though/

- src/shared/libosmocore/src/msgfile.c
  here I had to bluntly emulate the functionality of the getline()
  call, which seems to be specific to glibc; again, it'd certainly be
  nicer if I added a test for HAVE_GETLINE or something along this line.

- src/shared/libosmocore/src/talloc.c
  again, talloc seems to rely on strnlen() being part of the libc, which
  is already known to not be the case on MacOS X; considering it also
  absent of NetBSD fixes the build for me.

- src/target/firmware/include/stdint.h
  this one is definitely more ugly, since I tricked the cross-compiler
  to believe /usr/include matches its specific needs I ended up with
  some essential type definitions already; therefore, I am not sure if
  this workaround would not be more harmful upstream than not.

Anyway, the actual patch is attached.

A few more things to NetBSD users:
- my previous patch about building without GNU make is also necessary;
- I haven't tested the resulting binaries on a NetBSD host;
- the firmware images seem to be only partly functional at the moment.

HTH,
-- 
khorben
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: netbsd.diff
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110126/ac7510d5/attachment.ksh>

From khorben at defora.org  Wed Jan 26 16:24:37 2011
From: khorben at defora.org (Pierre Pronchery)
Date: Wed, 26 Jan 2011 17:24:37 +0100
Subject: [PATCH] How to compile osmocom on NetBSD
In-Reply-To: <4D403EF2.4090403@defora.org>
References: <4D403EF2.4090403@defora.org>
Message-ID: <4D404AC5.7060306@defora.org>

On 01/26/2011 16:34, Pierre Pronchery wrote:
> 
> I will write the procedure in more details on my blog [1], in my case it
> was enough to do this: [...]

[1]
http://people.defora.org/~khorben/place/blog/108/Building-OsmocomBB-on-NetBSD

-- 
khorben



From list_mailing at libero.it  Thu Jan 27 17:01:29 2011
From: list_mailing at libero.it (list_mailing)
Date: Thu, 27 Jan 2011 09:01:29 -0800 (PST)
Subject: FCCH and SCH
Message-ID: <1296147689456-2363201.post@n3.nabble.com>


Hello,
I'm newbie to osmocomm and GSM too....I'm studying the protocol and the
source code...but I have many doubts...the first one is the following:
1. Which are the routines handling FCCH and SCH in osmocom source code?
2. When I load layer1 firmware and load mobile app, FCCH and SCH are
automatically handled by this application?
Sorry if my questions are stupid for you, but it's a litlle bit complicate
moving in the code, above all for a newbie.
Thanks in advance.
-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/FCCH-and-SCH-tp2363201p2363201.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From laforge at gnumonks.org  Fri Jan 28 15:35:53 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 28 Jan 2011 18:35:53 +0300
Subject: FCCH and SCH
In-Reply-To: <1296147689456-2363201.post@n3.nabble.com>
References: <1296147689456-2363201.post@n3.nabble.com>
Message-ID: <20110128153553.GC11241@prithivi.gnumonks.org>

On Thu, Jan 27, 2011 at 09:01:29AM -0800, list_mailing wrote:
> 
> Hello,
> I'm newbie to osmocomm and GSM too....I'm studying the protocol and the
> source code...but I have many doubts...the first one is the following:
> 1. Which are the routines handling FCCH and SCH in osmocom source code?

have you ever even bothered to use 'grep' to search for what you are looking
for?

layer1/prim_fbsb.c:/* Layer 1 - FCCH and SCH burst handling */

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From mailman at lists.osmocom.org  Fri Jan 28 11:02:52 2011
From: mailman at lists.osmocom.org (mailman at lists.osmocom.org)
Date: Fri, 28 Jan 2011 12:02:52 +0100
Subject: Bounce action notification
Message-ID: <mailman.27.1296212572.10914.baseband-devel@lists.osmocom.org>

This is a Mailman mailing list bounce action notice:

    List:       baseband-devel
    Member:     arslangali at 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 at lists.osmocom.org.
-------------- next part --------------
An embedded message was scrubbed...
From: Mail Delivery System <Mailer-Daemon at mx110.mail.ru>
Subject: Mail delivery failed: returning message to sender
Date: Fri, 28 Jan 2011 14:02:47 +0300
Size: 11327
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110128/7636f702/attachment.eml>

From torfun at web.de  Fri Jan 28 19:09:06 2011
From: torfun at web.de (tobsen)
Date: Fri, 28 Jan 2011 11:09:06 -0800 (PST)
Subject: doesn't get output from osmocon
Message-ID: <1296241746328-2367658.post@n3.nabble.com>


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-tp2367658p2367658.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From ml at mail.tsaitgaist.info  Fri Jan 28 21:46:27 2011
From: ml at mail.tsaitgaist.info (ml at mail.tsaitgaist.info)
Date: Fri, 28 Jan 2011 22:46:27 +0100
Subject: doesn't get output from osmocon
In-Reply-To: <1296241746328-2367658.post@n3.nabble.com>
References: <1296241746328-2367658.post@n3.nabble.com>
Message-ID: <4D433933.3070205@mail.tsaitgaist.info>

Hi,

first test if the cable is working. a fast but dirty way is to rub the
tip with your fingers. this generates noise that should show some random
input in osmocon.
also but sure to not charge the phone while using osmocon, this can
inhibit the ram loader.

good luck,
kevin

On 01/28/2011 08:09 PM, tobsen wrote:
> 
> 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
> 



From lbernal at gmail.com  Fri Jan 28 22:25:30 2011
From: lbernal at gmail.com (n0p [Luis Bernal])
Date: Fri, 28 Jan 2011 23:25:30 +0100
Subject: doesn't get output from osmocon
In-Reply-To: <4D433933.3070205@mail.tsaitgaist.info>
References: <1296241746328-2367658.post@n3.nabble.com>
	<4D433933.3070205@mail.tsaitgaist.info>
Message-ID: <AANLkTim=hmO+tk+jCFrRs_MycTxvHe2LgULh5vHp7g_N@mail.gmail.com>

another way is to shortcut the tip and middle ring of the connector, open a
serial terminal and see if it echoes back what you type in

2011/1/28 <ml at mail.tsaitgaist.info>

> Hi,
>
> first test if the cable is working. a fast but dirty way is to rub the
> tip with your fingers. this generates noise that should show some random
> input in osmocon.
> also but sure to not charge the phone while using osmocon, this can
> inhibit the ram loader.
>
> good luck,
> kevin
>
> On 01/28/2011 08:09 PM, tobsen wrote:
> >
> > 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
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110128/fc28d58d/attachment.htm>

From edrocoyote at yahoo.es  Sat Jan 29 01:29:39 2011
From: edrocoyote at yahoo.es (Pedro Collote)
Date: Sat, 29 Jan 2011 02:29:39 +0100
Subject: a very simple cuestion (only 1 sec.)
References: <1296241746328-2367658.post@n3.nabble.com><4D433933.3070205@mail.tsaitgaist.info>
	<AANLkTim=hmO+tk+jCFrRs_MycTxvHe2LgULh5vHp7g_N@mail.gmail.com>
Message-ID: <195C0FB7CCA0430EA6895B3206B7F427@CentroSalud>

libtool 2.4
pkg_config 0.4
M4 1.4.15
autoconf 2.68
automake 1.9.6

is ok?

Thank you!




From torfun at web.de  Sat Jan 29 02:34:28 2011
From: torfun at web.de (Tobias Funke)
Date: Sat, 29 Jan 2011 03:34:28 +0100
Subject: doesn't get output from osmocon
In-Reply-To: <4D433933.3070205@mail.tsaitgaist.info>
References: <1296241746328-2367658.post@n3.nabble.com>
	<4D433933.3070205@mail.tsaitgaist.info>
Message-ID: <AANLkTinTEiYR-6XYJ97_fBL5XX3U3V=Sfj_RLY0CVpw2@mail.gmail.com>

thanks to you,

i checked that:

there is no input in osmocon, when i rub the tip, so i think the cable is shit.

that was simple...

i buy a new one, are the akku-king cable and the gsmlibery cable
really the right ones???

both pictures are showing not the t191 unlock cable...

good greetings
tobsen



2011/1/28  <ml at mail.tsaitgaist.info>:
> Hi,
>
> first test if the cable is working. a fast but dirty way is to rub the
> tip with your fingers. this generates noise that should show some random
> input in osmocon.
> also but sure to not charge the phone while using osmocon, this can
> inhibit the ram loader.
>
> good luck,
> kevin
>
> On 01/28/2011 08:09 PM, tobsen wrote:
>>
>> 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
>>
>
>



From ml at mail.tsaitgaist.info  Sat Jan 29 08:34:32 2011
From: ml at mail.tsaitgaist.info (ml at mail.tsaitgaist.info)
Date: Sat, 29 Jan 2011 09:34:32 +0100
Subject: doesn't get output from osmocon
In-Reply-To: <AANLkTinTEiYR-6XYJ97_fBL5XX3U3V=Sfj_RLY0CVpw2@mail.gmail.com>
References: <1296241746328-2367658.post@n3.nabble.com>	<4D433933.3070205@mail.tsaitgaist.info>
	<AANLkTinTEiYR-6XYJ97_fBL5XX3U3V=Sfj_RLY0CVpw2@mail.gmail.com>
Message-ID: <4D43D118.7080503@mail.tsaitgaist.info>

they're the right cables.
ignore the pictures, only the name is important.
these are some cheap websites, don't expect good quality content.

kevin

On 01/29/2011 03:34 AM, Tobias Funke wrote:
> thanks to you,
> 
> i checked that:
> 
> there is no input in osmocon, when i rub the tip, so i think the cable is shit.
> 
> that was simple...
> 
> i buy a new one, are the akku-king cable and the gsmlibery cable
> really the right ones???
> 
> both pictures are showing not the t191 unlock cable...
> 
> good greetings
> tobsen
> 
> 
> 
> 2011/1/28  <ml at mail.tsaitgaist.info>:
>> Hi,
>>
>> first test if the cable is working. a fast but dirty way is to rub the
>> tip with your fingers. this generates noise that should show some random
>> input in osmocon.
>> also but sure to not charge the phone while using osmocon, this can
>> inhibit the ram loader.
>>
>> good luck,
>> kevin
>>
>> On 01/28/2011 08:09 PM, tobsen wrote:
>>>
>>> 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
>>>
>>
>>
> 
> 



From tobiasfunke93 at googlemail.com  Sat Jan 29 10:26:28 2011
From: tobiasfunke93 at googlemail.com (Tobias Funke)
Date: Sat, 29 Jan 2011 11:26:28 +0100
Subject: doesn't get output from osmocon
In-Reply-To: <4D43D118.7080503@mail.tsaitgaist.info>
References: <1296241746328-2367658.post@n3.nabble.com>
	<4D433933.3070205@mail.tsaitgaist.info>
	<AANLkTinTEiYR-6XYJ97_fBL5XX3U3V=Sfj_RLY0CVpw2@mail.gmail.com>
	<4D43D118.7080503@mail.tsaitgaist.info>
Message-ID: <AANLkTingZSi+qUxF1rNVfbHwAVTrUc_-Sc4PsrOeJsxO@mail.gmail.com>

thank you for helping me, kevin.

tobsen

2011/1/29  <ml at mail.tsaitgaist.info>:
> they're the right cables.
> ignore the pictures, only the name is important.
> these are some cheap websites, don't expect good quality content.
>
> kevin
>
> On 01/29/2011 03:34 AM, Tobias Funke wrote:
>> thanks to you,
>>
>> i checked that:
>>
>> there is no input in osmocon, when i rub the tip, so i think the cable is shit.
>>
>> that was simple...
>>
>> i buy a new one, are the akku-king cable and the gsmlibery cable
>> really the right ones???
>>
>> both pictures are showing not the t191 unlock cable...
>>
>> good greetings
>> tobsen
>>
>>
>>
>> 2011/1/28 ?<ml at mail.tsaitgaist.info>:
>>> Hi,
>>>
>>> first test if the cable is working. a fast but dirty way is to rub the
>>> tip with your fingers. this generates noise that should show some random
>>> input in osmocon.
>>> also but sure to not charge the phone while using osmocon, this can
>>> inhibit the ram loader.
>>>
>>> good luck,
>>> kevin
>>>
>>> On 01/28/2011 08:09 PM, tobsen wrote:
>>>>
>>>> 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
>>>>
>>>
>>>
>>
>>
>
>



From laforge at gnumonks.org  Sat Jan 29 06:17:16 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Sat, 29 Jan 2011 09:17:16 +0300
Subject: Documentation for 'mobile' in the wiki
Message-ID: <20110129061716.GC5546@prithivi.gnumonks.org>

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 at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From laforge at gnumonks.org  Sat Jan 29 06:18:50 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Sat, 29 Jan 2011 09:18:50 +0300
Subject: mobile: config file in /etc/osmocom/osmocom.cfg
Message-ID: <20110129061850.GD5546@prithivi.gnumonks.org>

Hi all,

I would like to propose moving the config file into something like ~/.osmocom/
and not put it in a system wide directory.  The path in /etc/ is the only
part of OsmocomBB that requires root privileges, and I don't really think
that in a case of multiple users you would want to e.g. share stuff like
the IMSI / Ki anyway.

What do you think?

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From peter at stuge.se  Sat Jan 29 10:05:56 2011
From: peter at stuge.se (Peter Stuge)
Date: Sat, 29 Jan 2011 11:05:56 +0100
Subject: mobile: config file in /etc/osmocom/osmocom.cfg
In-Reply-To: <20110129061850.GD5546@prithivi.gnumonks.org>
References: <20110129061850.GD5546@prithivi.gnumonks.org>
Message-ID: <20110129100556.22971.qmail@stuge.se>

Harald Welte wrote:
> I would like to propose moving the config file into something like ~/.osmocom/
> and not put it in a system wide directory.  The path in /etc/ is the only
> part of OsmocomBB that requires root privileges, and I don't really think
> that in a case of multiple users you would want to e.g. share stuff like
> the IMSI / Ki anyway.
> 
> What do you think?

Acked-by: Peter Stuge <peter at stuge.se>



From khorben at defora.org  Sat Jan 29 12:56:04 2011
From: khorben at defora.org (Pierre Pronchery)
Date: Sat, 29 Jan 2011 13:56:04 +0100
Subject: [PATCH] Re: mobile: config file in /etc/osmocom/osmocom.cfg
In-Reply-To: <20110129061850.GD5546@prithivi.gnumonks.org>
References: <20110129061850.GD5546@prithivi.gnumonks.org>
Message-ID: <4D440E64.5000500@defora.org>

			Hi,

On 01/29/2011 07:18, Harald Welte wrote:
> 
> I would like to propose moving the config file into something like ~/.osmocom/
> and not put it in a system wide directory.  The path in /etc/ is the only
> part of OsmocomBB that requires root privileges, and I don't really think
> that in a case of multiple users you would want to e.g. share stuff like
> the IMSI / Ki anyway.
> 
> What do you think?

I'm ok too, with a patch attached.

HTH,
-- 
khorben
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config_file.diff
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110129/a197a54a/attachment.ksh>

From khorben at defora.org  Sat Jan 29 13:08:20 2011
From: khorben at defora.org (Pierre Pronchery)
Date: Sat, 29 Jan 2011 14:08:20 +0100
Subject: [PATCH] Re: mobile: config file in /etc/osmocom/osmocom.cfg
In-Reply-To: <4D440E64.5000500@defora.org>
References: <20110129061850.GD5546@prithivi.gnumonks.org>
	<4D440E64.5000500@defora.org>
Message-ID: <4D441144.3000304@defora.org>

On 01/29/2011 13:56, Pierre Pronchery wrote:
> 
> I'm ok too, with a patch attached.

It was missing two additional #include.

For the record, when I implement this I usually fallback on glib's
g_get_home_dir() in case getenv() fails. It typically uses
getpwuid(getuid()) on *nix, but I suppose it'd be a bit overkill here :)

HTH,
-- 
khorben
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config_file.diff
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110129/40b915c0/attachment.ksh>

From ml at mail.tsaitgaist.info  Sat Jan 29 10:49:45 2011
From: ml at mail.tsaitgaist.info (tsaitgaist)
Date: Sat, 29 Jan 2011 11:49:45 +0100
Subject: track ticket
Message-ID: <4D43F0C9.1020205@mail.tsaitgaist.info>

Hi,

Could it be possible to enable the ticket system in trac ?
It could be used to add suggestions/bugs/todo/..., avoid overloading the
mailing list, and keep trac of them.
For example, how about changing the mobile welcome message from:
Welcome to the OpenBSC Control interface
to:
Welcome to the osmocom Control interface
it makes more sense when using osmocomBB.

thanks,
kevin



From laforge at gnumonks.org  Sat Jan 29 14:49:58 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Sat, 29 Jan 2011 17:49:58 +0300
Subject: track ticket
In-Reply-To: <4D43F0C9.1020205@mail.tsaitgaist.info>
References: <4D43F0C9.1020205@mail.tsaitgaist.info>
Message-ID: <20110129144958.GP5546@prithivi.gnumonks.org>

Hi Kevin,

On Sat, Jan 29, 2011 at 11:49:45AM +0100, tsaitgaist wrote:
 
> Could it be possible to enable the ticket system in trac ?
> It could be used to add suggestions/bugs/todo/..., avoid overloading the
> mailing list, and keep trac of them.

I explicitly disabled it about a week ago since it was not being used.

If there are some people on this list who will say that they will
actually use it (i.e. fix stuff reported in there), then I'll re-activate it.  

So far, e.g. in OpenBSC, it was not much used at all... I think I am the only
one who did collect some todo items, but then also stopped to use it soon
after.

> For example, how about changing the mobile welcome message from:
> Welcome to the OpenBSC Control interface

feel free to send a patch :)

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From ml at mail.tsaitgaist.info  Sun Jan 30 22:58:28 2011
From: ml at mail.tsaitgaist.info (tsaitgaist)
Date: Sun, 30 Jan 2011 23:58:28 +0100
Subject: track ticket
In-Reply-To: <20110129144958.GP5546@prithivi.gnumonks.org>
References: <4D43F0C9.1020205@mail.tsaitgaist.info>
	<20110129144958.GP5546@prithivi.gnumonks.org>
Message-ID: <4D45ED14.9080100@mail.tsaitgaist.info>

hi,

> 
>> For example, how about changing the mobile welcome message from:
>> Welcome to the OpenBSC Control interface
> 
> feel free to send a patch :)
> 

here the patch,
kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: welcome.diff
Type: text/x-patch
Size: 430 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/22b75900/attachment.bin>

From peter at stuge.se  Mon Jan 31 05:27:15 2011
From: peter at stuge.se (Peter Stuge)
Date: Mon, 31 Jan 2011 06:27:15 +0100
Subject: track ticket
In-Reply-To: <4D45ED14.9080100@mail.tsaitgaist.info>
References: <4D43F0C9.1020205@mail.tsaitgaist.info>
	<20110129144958.GP5546@prithivi.gnumonks.org>
	<4D45ED14.9080100@mail.tsaitgaist.info>
Message-ID: <20110131052715.26938.qmail@stuge.se>

tsaitgaist wrote:
> >> For example, how about changing the mobile welcome message from:
> >> Welcome to the OpenBSC Control interface

> +++ osmocom-bb/src/shared/libosmocore/src/vty/telnet_interface.c	2011-01-30 23:46:32.305490006 +0100
..
> -		"Welcome to the OpenBSC Control interface\r\n";
> +		"Welcome to the osmocom control interface\r\n";

Maybe basename(argv[0]) ?

Or "Osmocom" like in the logo?


//Peter



From 246tnt at gmail.com  Mon Jan 31 06:49:00 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Mon, 31 Jan 2011 07:49:00 +0100
Subject: track ticket
In-Reply-To: <4D45ED14.9080100@mail.tsaitgaist.info>
References: <4D43F0C9.1020205@mail.tsaitgaist.info>
	<20110129144958.GP5546@prithivi.gnumonks.org>
	<4D45ED14.9080100@mail.tsaitgaist.info>
Message-ID: <AANLkTik=L3Tbu0jiLfdTmCxkPAy-G7C+OvNUH-NKTy01@mail.gmail.com>

Hi,

> here the patch,

You can't change things in shared/libosmocore like that.

You need to somehow make that string application dependent, then
submit a patch for libosmocore itself and then the appropriate patch
for both openbsc and osmocom-bb to adapt to the new interface.


Cheers,

    Sylvain



From michal.demin at gmail.com  Sat Jan 29 16:48:11 2011
From: michal.demin at gmail.com (Michal Demin)
Date: Sat, 29 Jan 2011 17:48:11 +0100
Subject: Gpio driver for calypso
Message-ID: <AANLkTimFL0VzLwTjf+dFn1jtgrkRrhH0gB+v-tJBaGmP@mail.gmail.com>

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Add-GPIO-driver-for-Calypso.patch
Type: application/octet-stream
Size: 9811 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110129/0ca33393/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Add-interrupt-support-for-GPIOs.patch
Type: application/octet-stream
Size: 4645 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110129/0ca33393/attachment-0001.obj>

From michal.demin at gmail.com  Sat Jan 29 17:04:17 2011
From: michal.demin at gmail.com (Michal Demin)
Date: Sat, 29 Jan 2011 18:04:17 +0100
Subject: [PATCH] Gpio driver for calypso
In-Reply-To: <AANLkTimFL0VzLwTjf+dFn1jtgrkRrhH0gB+v-tJBaGmP@mail.gmail.com>
References: <AANLkTimFL0VzLwTjf+dFn1jtgrkRrhH0gB+v-tJBaGmP@mail.gmail.com>
Message-ID: <AANLkTim8Wd1tSWHbnR9jeseh+BC2vkU=7Y2bVtj79SdF@mail.gmail.com>

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Add-GPIO-driver-for-Calypso.patch
Type: application/octet-stream
Size: 9811 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110129/1344495b/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Add-interrupt-support-for-GPIOs.patch
Type: application/octet-stream
Size: 4645 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110129/1344495b/attachment-0001.obj>

From b.alecu at yahoo.com  Sun Jan 30 11:42:43 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Sun, 30 Jan 2011 03:42:43 -0800 (PST)
Subject: Channel info
Message-ID: <378482.759.qm@web46206.mail.sp1.yahoo.com>

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.



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/e08e395a/attachment.htm>

From mad at auth.se  Sun Jan 30 15:54:25 2011
From: mad at auth.se (mad at auth.se)
Date: Sun, 30 Jan 2011 16:54:25 +0100
Subject: Channel info
In-Reply-To: <378482.759.qm@web46206.mail.sp1.yahoo.com>
References: <378482.759.qm@web46206.mail.sp1.yahoo.com>
Message-ID: <4f0edf47b8a7fc2386e51a0bdf7f9934@auth.se>

 On Sun, 30 Jan 2011 03:42:43 -0800 (PST), Bogdan Alecu wrote:
> 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.

 These are paging requests for phones in your location area. As 
 osmocombb
 receives them and checks them for its own imsi/tmsi, it discards those
 ones you observed.
 The imsi of your other phone should not ever be seen on the paging 
 channel as
 gsm trys to avoid sending out imsis as much as possible. Instead the 
 network
 attaches a tmsi to the imsi on your phones first network login 
 (location update)
 and uses that from there on for addressing the phone. This tmsi is kept 
 by
 storing on the sim card even over powercycle.

 Regards,
   Mad




From b.alecu at yahoo.com  Sun Jan 30 17:20:28 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Sun, 30 Jan 2011 09:20:28 -0800 (PST)
Subject: Channel info
In-Reply-To: <4f0edf47b8a7fc2386e51a0bdf7f9934@auth.se>
Message-ID: <208279.7000.qm@web46202.mail.sp1.yahoo.com>

Hi Mad,
Thanks for explaining me this. The case of the TMSI is different from network to network: some operators change it for every x minutes, others after a powercycle (at least here). You say that gsm tries to avoid sending out IMSIs but still some are sent. If I would send an SMS to the phone - so it will get a paging request - I should see the IMSI also in that list?

--- On Sun, 1/30/11, mad at auth.se <mad at auth.se> wrote:

From: mad at auth.se <mad at auth.se>
Subject: Re: Channel info
To: "Bogdan Alecu" <b.alecu at yahoo.com>
Cc: baseband-devel at lists.osmocom.org
Date: Sunday, January 30, 2011, 3:54 PM

On Sun, 30 Jan 2011 03:42:43 -0800 (PST), Bogdan Alecu wrote:
> 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.

These are paging requests for phones in your location area. As osmocombb
receives them and checks them for its own imsi/tmsi, it discards those
ones you observed.
The imsi of your other phone should not ever be seen on the paging channel as
gsm trys to avoid sending out imsis as much as possible. Instead the network
attaches a tmsi to the imsi on your phones first network login (location update)
and uses that from there on for addressing the phone. This tmsi is kept by
storing on the sim card even over powercycle.

Regards,
? Mad




      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/b5c064a4/attachment.htm>

From john at epiq-solutions.com  Sun Jan 30 17:34:01 2011
From: john at epiq-solutions.com (John Orlando)
Date: Sun, 30 Jan 2011 11:34:01 -0600
Subject: Channel info
In-Reply-To: <208279.7000.qm@web46202.mail.sp1.yahoo.com>
References: <4f0edf47b8a7fc2386e51a0bdf7f9934@auth.se>
	<208279.7000.qm@web46202.mail.sp1.yahoo.com>
Message-ID: <AANLkTi=nNG4rhXNChQEN_CT41WHuk_uQN1R7xJ3vu-9e@mail.gmail.com>

On Sun, Jan 30, 2011 at 11:20 AM, Bogdan Alecu <b.alecu at yahoo.com> wrote:

> Hi Mad,
> Thanks for explaining me this. The case of the TMSI is different from
> network to network: some operators change it for every x minutes, others
> after a powercycle (at least here). You say that gsm tries to avoid sending
> out IMSIs but still some are sent. If I would send an SMS to the phone - so
> it will get a paging request - I should see the IMSI also in that list?
>

If you send an SMS to the phone, the "typical scenario" would be:
   -Network pages the mobile, most likely with its TMSI (as stated before)
   -Mobile will send a RACH to request a dedicated channel
   -Network will assign the mobile to a dedicated channel (typically a
SDCCH)
   -Network will perform contention resolution on the dedicated channel to
ensure that it is the correct mobile (to cover the rare case where two
mobiles RACH at the exact same time)
   -Network may or may not begin ciphering at this point
   -Network will deliver the SMS payload to the mobile through a series of
messages on the dedicated channel
   -Mobile will ack each message, letting the network know that it has
received what was sent
   -Network will release the dedicated channel, the mobile will go back to
its idle mode (monitoring the paging channels etc), and the mobile will then
have the SMS

It is up to the network to decide what ID type it wants to use to page a
mobile, and this is dependent on a number of factors.  Almost always it uses
the TMSI, sometimes IMSI, and _very_ rarely an IMEI.  It is certainly
possible that the network can also request identity info (IMSI, IMEI) from
the mobile on the dedicated channel, as well as a whole host of other
message requests while on the dedicated channel.

So in short, unless you're lucky enough to have the network page you with
your IMSI, it is unlikely you will see it.

-- 
John Orlando
CEO/System Architect
Epiq Solutions
www.epiq-solutions.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/c75bf532/attachment.htm>

From mad at auth.se  Sun Jan 30 17:59:50 2011
From: mad at auth.se (mad at auth.se)
Date: Sun, 30 Jan 2011 18:59:50 +0100
Subject: Channel info
In-Reply-To: <AANLkTi=nNG4rhXNChQEN_CT41WHuk_uQN1R7xJ3vu-9e@mail.gmail.com>
References: <4f0edf47b8a7fc2386e51a0bdf7f9934@auth.se>
	<208279.7000.qm@web46202.mail.sp1.yahoo.com>
	<AANLkTi=nNG4rhXNChQEN_CT41WHuk_uQN1R7xJ3vu-9e@mail.gmail.com>
Message-ID: <8f992ce37c57dad330e67d4d0ee6fdb8@auth.se>

 On Sun, 30 Jan 2011 11:34:01 -0600, John Orlando wrote:
>
> It is up to the network to decide what ID type it wants to use to 
> page
> a mobile, and this is dependent on a number of factors.? Almost
> always it uses the TMSI, sometimes IMSI, and _very_ rarely an IMEI.?

 In gsm 04.08 9.1.22.3 it says "The Mobile Identity 1 and 2 IEs shall  
 not
 refer to IMEI.". So a standard compliant network should never do that.

 Have you actually seen that on any live network?

>
> So in short, unless youre lucky enough to have the network page you
> with your IMSI, it is unlikely you will see it.

 Sometimes when some network components like the auth server/vlr are
 overloaded with entrys or requests, then there are many imsis on the
 air. And often at not-so-busy times, too. I've observed that regulary
 but have not heard any fully explainatory conclusion to that yet.

 Regards,
   Mad




From steve at steve-m.de  Sun Jan 30 18:05:02 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Sun, 30 Jan 2011 19:05:02 +0100
Subject: Channel info
In-Reply-To: <8f992ce37c57dad330e67d4d0ee6fdb8@auth.se>
References: <4f0edf47b8a7fc2386e51a0bdf7f9934@auth.se>	<208279.7000.qm@web46202.mail.sp1.yahoo.com>	<AANLkTi=nNG4rhXNChQEN_CT41WHuk_uQN1R7xJ3vu-9e@mail.gmail.com>
	<8f992ce37c57dad330e67d4d0ee6fdb8@auth.se>
Message-ID: <4D45A84E.1000204@steve-m.de>

Hi,

On 30.01.2011 18:59, mad at auth.se wrote:

> In gsm 04.08 9.1.22.3 it says "The Mobile Identity 1 and 2 IEs shall not
> refer to IMEI.". So a standard compliant network should never do that.
>
> Have you actually seen that on any live network?

"The reason why you see paging by IMSI in real-world GSM networks"
http://laforge.gnumonks.org/weblog/2010/06/28/

Regards,
Steve



From steve at steve-m.de  Sun Jan 30 18:32:04 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Sun, 30 Jan 2011 19:32:04 +0100
Subject: Channel info
In-Reply-To: <4D45A84E.1000204@steve-m.de>
References: <4f0edf47b8a7fc2386e51a0bdf7f9934@auth.se>	<208279.7000.qm@web46202.mail.sp1.yahoo.com>	<AANLkTi=nNG4rhXNChQEN_CT41WHuk_uQN1R7xJ3vu-9e@mail.gmail.com>	<8f992ce37c57dad330e67d4d0ee6fdb8@auth.se>
	<4D45A84E.1000204@steve-m.de>
Message-ID: <4D45AEA4.60303@steve-m.de>

Hi again,

On 30.01.2011 19:05, Steve Markgraf wrote:

>> In gsm 04.08 9.1.22.3 it says "The Mobile Identity 1 and 2 IEs shall not
>> refer to IMEI.". So a standard compliant network should never do that.

> "The reason why you see paging by IMSI in real-world GSM networks"

Sorry, I confused IMEI/IMSI. Forget about my last message, although
Haralds blogpost may still be interesting in the context of this thread.

Regards,
Steve



From mad at auth.se  Sun Jan 30 19:21:37 2011
From: mad at auth.se (mad at auth.se)
Date: Sun, 30 Jan 2011 20:21:37 +0100
Subject: Channel info
In-Reply-To: <4D45AEA4.60303@steve-m.de>
References: "<4f0edf47b8a7fc2386e51a0bdf7f9934@auth.se>	<208279.7000.qm@web46202.mail.sp1.yahoo.com>	<AANLkTi=nNG4rhXNChQEN_CT41WHuk_uQN1R7xJ3vu-9e@mail.gmail.com>"
	<8f992ce37c57dad330e67d4d0ee6fdb8@auth.se>
	<4D45A84E.1000204@steve-m.de> <4D45AEA4.60303@steve-m.de>
Message-ID: <be22a83f1d9248efeed1f71bfe637fdf@auth.se>

 On Sun, 30 Jan 2011 19:32:04 +0100, Steve Markgraf wrote:
> Hi again,
>
> On 30.01.2011 19:05, Steve Markgraf wrote:
>
>>> In gsm 04.08 9.1.22.3 it says "The Mobile Identity 1 and 2 IEs 
>>> shall not
>>> refer to IMEI.". So a standard compliant network should never do 
>>> that.
>
>> "The reason why you see paging by IMSI in real-world GSM networks"
>
> Sorry, I confused IMEI/IMSI. Forget about my last message, although
> Haralds blogpost may still be interesting in the context of this 
> thread.
>

 No, you were right about that, second part of my post was about imsis 
 on air.

 I already had read Haralds post but I'm not fully convinced of all of 
 his
 explainations. At least not on modern state-of-the-art core networks.
 Too less ram or volatile storage on restarting VLRs, is that really 
 still an
 issue there?

 The third point, that expired tmsis on unreachable phones with a 
 fallback on
 imsi paging as the main cause sounds much more convincing to me.

 But as David pointed out, 10-25% imsi paging is a lot, even about 
 constant
 2-5% as I observed are much for a location area or whole msc area.
 Did anyone do some research on that?

 Regards,
   Mad




From john at epiq-solutions.com  Sun Jan 30 18:28:03 2011
From: john at epiq-solutions.com (John Orlando)
Date: Sun, 30 Jan 2011 12:28:03 -0600
Subject: Channel info
In-Reply-To: <8f992ce37c57dad330e67d4d0ee6fdb8@auth.se>
References: <4f0edf47b8a7fc2386e51a0bdf7f9934@auth.se>
	<208279.7000.qm@web46202.mail.sp1.yahoo.com>
	<AANLkTi=nNG4rhXNChQEN_CT41WHuk_uQN1R7xJ3vu-9e@mail.gmail.com>
	<8f992ce37c57dad330e67d4d0ee6fdb8@auth.se>
Message-ID: <AANLkTinAXUnm0Mu5WZo14WrPxxf6WvrT04OM5KkpT_gu@mail.gmail.com>

On Sun, Jan 30, 2011 at 11:59 AM, <mad at auth.se> wrote:

> On Sun, 30 Jan 2011 11:34:01 -0600, John Orlando wrote:
>
>>
>> It is up to the network to decide what ID type it wants to use to page
>> a mobile, and this is dependent on a number of factors.  Almost
>> always it uses the TMSI, sometimes IMSI, and _very_ rarely an IMEI.
>>
>
> In gsm 04.08 9.1.22.3 it says "The Mobile Identity 1 and 2 IEs shall  not
> refer to IMEI.". So a standard compliant network should never do that.
>
> Have you actually seen that on any live network?
>

Hmm...I stand corrected regarding the use of IMEI to page the mobile in
GSM.  It should only be TMSI or IMSI.  I was mixing up the GSM paging
options with the Iridium satellite phone paging options (where the IMEI can
be used to page the mobile in some situations).  Too many standards to
remember...

-- 
John Orlando
CEO/System Architect
Epiq Solutions
www.epiq-solutions.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/18d3ba88/attachment.htm>

From dburgess at jcis.net  Sun Jan 30 18:22:39 2011
From: dburgess at jcis.net (David A. Burgess)
Date: Sun, 30 Jan 2011 10:22:39 -0800
Subject: Channel info
In-Reply-To: <AANLkTi=nNG4rhXNChQEN_CT41WHuk_uQN1R7xJ3vu-9e@mail.gmail.com>
References: <4f0edf47b8a7fc2386e51a0bdf7f9934@auth.se>
	<208279.7000.qm@web46202.mail.sp1.yahoo.com>
	<AANLkTi=nNG4rhXNChQEN_CT41WHuk_uQN1R7xJ3vu-9e@mail.gmail.com>
Message-ID: <603006E4-FCD6-4762-8513-D20FEA9B6E85@jcis.net>


I find that real-world networks page by IMSI 10%-25% of the time,  
depending on the operator and location.  According to Harald's blog  
post on this topic, recently referenced on this list, he has made  
similar observations and offers some possibilities as to why.

Also, as Steve Markgraf pointed out, GSM 04.08 9.1.22.3 explicitly  
disallows paging by IMEI.  Networks are not supposed to do it and  
phones are not supposed to respond to it.  It would be easy for  
someone to hack OpenBTS or OpenBSC to see how phones respond to this  
type of paging, but I have never seen it in a real network.  I doubt  
seriously if any phone will respond, but I do wonder how many will  
crash their baseband stacks when presented with these messages.

On Jan 30, 2011, at 9:34 AM, John Orlando wrote:

>
> It is up to the network to decide what ID type it wants to use to  
> page a mobile, and this is dependent on a number of factors.   
> Almost always it uses the TMSI, sometimes IMSI, and _very_ rarely  
> an IMEI.  It is certainly possible that the network can also  
> request identity info (IMSI, IMEI) from the mobile on the dedicated  
> channel, as well as a whole host of other message requests while on  
> the dedicated channel.
>


David A. Burgess
Kestrel Signal Processing, Inc.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/baca3ca1/attachment.htm>

From b.alecu at yahoo.com  Mon Jan 31 04:35:10 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Sun, 30 Jan 2011 20:35:10 -0800 (PST)
Subject: Channel info
Message-ID: <716556.94776.qm@web46208.mail.sp1.yahoo.com>

When I look in the output of the mobile app I see that IMSI paging goes almos up to 50%. It's almost like for every TMSI I get below a IMSI paging. That's why I asked from the beginning because I get a lot of IMSI there.


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/c1b927a4/attachment.htm>

From dburgess at jcis.net  Mon Jan 31 05:21:57 2011
From: dburgess at jcis.net (David A. Burgess)
Date: Sun, 30 Jan 2011 21:21:57 -0800
Subject: Channel info
In-Reply-To: <716556.94776.qm@web46208.mail.sp1.yahoo.com>
References: <716556.94776.qm@web46208.mail.sp1.yahoo.com>
Message-ID: <4006A3DA-71AF-45BC-B97B-AD976916F1FC@jcis.net>


Wow.  That's a lot.  What network is this?  In what area?

On Jan 30, 2011, at 8:35 PM, Bogdan Alecu wrote:

> When I look in the output of the mobile app I see that IMSI paging  
> goes almos up to 50%. It's almost like for every TMSI I get below a  
> IMSI paging. That's why I asked from the beginning because I get a  
> lot of IMSI there.
>


David A. Burgess
Kestrel Signal Processing, Inc.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/0ee82284/attachment.htm>

From b.alecu at yahoo.com  Mon Jan 31 05:30:20 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Sun, 30 Jan 2011 21:30:20 -0800 (PST)
Subject: Channel info
In-Reply-To: <4006A3DA-71AF-45BC-B97B-AD976916F1FC@jcis.net>
Message-ID: <499915.83969.qm@web46201.mail.sp1.yahoo.com>

Vodafone, Romania - 226-01

--- On Mon, 1/31/11, David A. Burgess <dburgess at jcis.net> wrote:


From: David A. Burgess <dburgess at jcis.net>
Subject: Re: Channel info
To: "Bogdan Alecu" <b.alecu at yahoo.com>
Cc: mad at auth.se, baseband-devel at lists.osmocom.org
Date: Monday, January 31, 2011, 5:21 AM




Wow. ?That's a lot. ?What network is this? ?In what area?



On Jan 30, 2011, at 8:35 PM, Bogdan Alecu wrote:





When I look in the output of the mobile app I see that IMSI paging goes almos up to 50%. It's almost like for every TMSI I get below a IMSI paging. That's why I asked from the beginning because I get a lot of IMSI there.





David A. Burgess
Kestrel Signal Processing, Inc.








      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/e09bc602/attachment.htm>

From b.alecu at yahoo.com  Mon Jan 31 06:00:03 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Sun, 30 Jan 2011 22:00:03 -0800 (PST)
Subject: Channel info
Message-ID: <466690.46895.qm@web46211.mail.sp1.yahoo.com>

When I look in the output of the mobile app I see that IMSI paging goes almos up to 50%. It's almost like for every TMSI I get below a IMSI paging. That's why I asked from the beginning because I get a lot of IMSI there.


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/af830c77/attachment.htm>

From laforge at gnumonks.org  Sun Jan 30 20:12:42 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Sun, 30 Jan 2011 23:12:42 +0300
Subject: [RFC] simplify intra-mobile event passing
Message-ID: <20110130201241.GA5292@prithivi.gnumonks.org>

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 at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)

From laforge at gnumonks.org  Sun Jan 30 19:26:11 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Sun, 30 Jan 2011 22:26:11 +0300
Subject: [PATCH 1/3] [mobile] simplify code to send events into GSM 3.22 code
Message-ID: <mailman.17.1641743546.42824.baseband-devel@lists.osmocom.org>

instead of gsm322_msgb_alloc() followed by a sendmsg
with intermittent error checks we now have only a single
function call.
---
 .../layer23/include/osmocom/bb/mobile/gsm322.h     |    7 +-
 src/host/layer23/src/mobile/app_mobile.c           |   13 +--
 src/host/layer23/src/mobile/gsm322.c               |   69 ++++++++++++++-
 src/host/layer23/src/mobile/gsm48_mm.c             |   88 +++++---------------
 src/host/layer23/src/mobile/gsm48_rr.c             |   33 +++-----
 src/host/layer23/src/mobile/vty_interface.c        |   31 +++----
 6 files changed, 118 insertions(+), 123 deletions(-)

diff --git a/src/host/layer23/include/osmocom/bb/mobile/gsm322.h b/src/host/layer23/include/osmocom/bb/mobile/gsm322.h
index 467ff39..3cd275f 100644
--- a/src/host/layer23/include/osmocom/bb/mobile/gsm322.h
+++ b/src/host/layer23/include/osmocom/bb/mobile/gsm322.h
@@ -172,10 +172,9 @@ struct gsm322_msg {
 
 int gsm322_init(struct osmocom_ms *ms);
 int gsm322_exit(struct osmocom_ms *ms);
-struct msgb *gsm322_msgb_alloc(int msg_type);
-int gsm322_plmn_sendmsg(struct osmocom_ms *ms, struct msgb *msg);
-int gsm322_cs_sendmsg(struct osmocom_ms *ms, struct msgb *msg);
-int gsm322_c_event(struct osmocom_ms *ms, struct msgb *msg);
+int gsm322_makesend_plmn_msg(struct osmocom_ms *ms, int msg_type, uint8_t *data, unsigned int len);
+int gsm322_makesend_cs_event(struct osmocom_ms *ms, int msg_type, uint8_t *data, unsigned int len);
+int gsm322_makesend_c_event(struct osmocom_ms *ms, int msg_type, uint8_t *data, unsigned int len);
 int gsm322_plmn_dequeue(struct osmocom_ms *ms);
 int gsm322_cs_dequeue(struct osmocom_ms *ms);
 int gsm322_add_forbidden_la(struct osmocom_ms *ms, uint16_t mcc,
diff --git a/src/host/layer23/src/mobile/app_mobile.c b/src/host/layer23/src/mobile/app_mobile.c
index 822ea64..3d2100c 100644
--- a/src/host/layer23/src/mobile/app_mobile.c
+++ b/src/host/layer23/src/mobile/app_mobile.c
@@ -79,7 +79,6 @@ int mobile_signal_cb(unsigned int subsys, unsigned int signal,
 {
 	struct osmocom_ms *ms;
 	struct gsm_settings *set;
-	struct msgb *nmsg;
 
 	if (subsys != SS_L1CTL)
 		return 0;
@@ -105,14 +104,10 @@ int mobile_signal_cb(unsigned int subsys, unsigned int signal,
 			break;
 		default:
 			/* no SIM, trigger PLMN selection process */
-			nmsg = gsm322_msgb_alloc(GSM322_EVENT_SWITCH_ON);
-			if (!nmsg)
-				return -ENOMEM;
-			gsm322_plmn_sendmsg(ms, nmsg);
-			nmsg = gsm322_msgb_alloc(GSM322_EVENT_SWITCH_ON);
-			if (!nmsg)
-				return -ENOMEM;
-			gsm322_cs_sendmsg(ms, nmsg);
+			gsm322_makesend_plmn_msg(ms, GSM322_EVENT_SWITCH_ON,
+						 NULL, 0);
+			gsm322_makesend_cs_event(ms, GSM322_EVENT_SWITCH_ON,
+						 NULL, 0);
 		}
 
 		ms->started = 1;
diff --git a/src/host/layer23/src/mobile/gsm322.c b/src/host/layer23/src/mobile/gsm322.c
index 3c920e4..1429737 100644
--- a/src/host/layer23/src/mobile/gsm322.c
+++ b/src/host/layer23/src/mobile/gsm322.c
@@ -45,6 +45,8 @@ static void gsm322_cs_loss(void *arg);
 static int gsm322_cs_select(struct osmocom_ms *ms, int any, int plmn_allowed);
 static int gsm322_m_switch_on(struct osmocom_ms *ms, struct msgb *msg);
 
+static int gsm322_c_event(struct osmocom_ms *ms, struct msgb *msg);
+
 #define SKIP_MAX_PER_BAND
 
 #warning HACKING!!!
@@ -182,7 +184,7 @@ const char *get_event_name(int value)
 
 
 /* allocate a 03.22 event message */
-struct msgb *gsm322_msgb_alloc(int msg_type)
+static struct msgb *gsm322_msgb_alloc(int msg_type)
 {
 	struct msgb *msg;
 	struct gsm322_msg *gm;
@@ -198,7 +200,7 @@ struct msgb *gsm322_msgb_alloc(int msg_type)
 }
 
 /* queue PLMN selection message */
-int gsm322_plmn_sendmsg(struct osmocom_ms *ms, struct msgb *msg)
+static int gsm322_plmn_sendmsg(struct osmocom_ms *ms, struct msgb *msg)
 {
 	struct gsm322_plmn *plmn = &ms->plmn;
 
@@ -208,7 +210,7 @@ int gsm322_plmn_sendmsg(struct osmocom_ms *ms, struct msgb *msg)
 }
 
 /* queue cell selection message */
-int gsm322_cs_sendmsg(struct osmocom_ms *ms, struct msgb *msg)
+static int gsm322_cs_sendmsg(struct osmocom_ms *ms, struct msgb *msg)
 {
 	struct gsm322_cellsel *cs = &ms->cellsel;
 
@@ -3304,7 +3306,7 @@ static struct cellselstatelist {
 #define CELLSELSLLEN \
 	(sizeof(cellselstatelist) / sizeof(struct cellselstatelist))
 
-int gsm322_c_event(struct osmocom_ms *ms, struct msgb *msg)
+static int gsm322_c_event(struct osmocom_ms *ms, struct msgb *msg)
 {
 	struct gsm322_cellsel *cs = &ms->cellsel;
 	struct gsm322_msg *gm = (struct gsm322_msg *) msg->data;
@@ -3602,4 +3604,63 @@ int gsm322_exit(struct osmocom_ms *ms)
 	return 0;
 }
 
+int gsm322_makesend_c_event(struct osmocom_ms *ms, int msg_type,
+			    uint8_t *data, unsigned int len)
+{
+	struct msgb *nmsg = gsm322_msgb_alloc(msg_type);
+	int rc;
 
+	if (!nmsg)
+		return -ENOMEM;
+
+	if (data && len) {
+		uint8_t *cur = msgb_push(nmsg, len);
+		if (!cur) {
+			msgb_free(nmsg);
+			return -EIO;
+		}
+		memcpy(cur, data, len);
+	}
+	rc = gsm322_c_event(ms, nmsg);
+	msgb_free(nmsg);
+
+	return rc;
+}
+
+int gsm322_makesend_cs_event(struct osmocom_ms *ms, int msg_type,
+			     uint8_t *data, unsigned int len)
+{
+	struct msgb *nmsg = gsm322_msgb_alloc(msg_type);
+
+	if (!nmsg)
+		return -ENOMEM;
+
+	if (data && len) {
+		uint8_t *cur = msgb_push(nmsg, len);
+		if (!cur) {
+			msgb_free(nmsg);
+			return -EIO;
+		}
+		memcpy(cur, data, len);
+	}
+	return  gsm322_cs_sendmsg(ms, nmsg);
+}
+
+int gsm322_makesend_plmn_msg(struct osmocom_ms *ms, int msg_type,
+			     uint8_t *data, unsigned int len)
+{
+	struct msgb *nmsg = gsm322_msgb_alloc(msg_type);
+
+	if (!nmsg)
+		return -ENOMEM;
+
+	if (data && len) {
+		uint8_t *cur = msgb_push(nmsg, len);
+		if (!cur) {
+			msgb_free(nmsg);
+			return -EIO;
+		}
+		memcpy(cur, data, len);
+	}
+	return gsm322_plmn_sendmsg(ms, nmsg);
+}
diff --git a/src/host/layer23/src/mobile/gsm48_mm.c b/src/host/layer23/src/mobile/gsm48_mm.c
index 15bbd27..58253bd 100644
--- a/src/host/layer23/src/mobile/gsm48_mm.c
+++ b/src/host/layer23/src/mobile/gsm48_mm.c
@@ -1118,33 +1118,23 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg)
 	 && cs->sel_lac == subscr->lac
 	 && !mm->lupd_periodic) {
 		if (subscr->imsi_attached) {
-			struct msgb *nmsg;
-
 			LOGP(DMM, LOGL_INFO, "Valid in location area.\n");
 			new_mm_state(mm, GSM48_MM_ST_MM_IDLE,
 				GSM48_MM_SST_NORMAL_SERVICE);
 
 			/* send message to PLMN search process */
-			nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_SUCCESS);
-			if (!nmsg)
-				return -ENOMEM;
-			gsm322_plmn_sendmsg(ms, nmsg);
-
+			gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS,
+						 NULL, 0);
 			return 0;
 		}
 		if (!s->att_allowed) {
-			struct msgb *nmsg;
-
 			LOGP(DMM, LOGL_INFO, "Attachment not required.\n");
 			new_mm_state(mm, GSM48_MM_ST_MM_IDLE,
 				GSM48_MM_SST_NORMAL_SERVICE);
 
 			/* send message to PLMN search process */
-			nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_SUCCESS);
-			if (!nmsg)
-				return -ENOMEM;
-			gsm322_plmn_sendmsg(ms, nmsg);
-
+			gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS,
+						 NULL, 0);
 			return 0;
 		}
 		/* else, continue */
@@ -1155,17 +1145,13 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg)
 	 && (gsm_subscr_is_forbidden_plmn(subscr, cs->sel_mcc, cs->sel_mnc)
 	  || gsm322_is_forbidden_la(ms, cs->sel_mcc, cs->sel_mnc,
 	 	cs->sel_lac))) {
-		struct msgb *nmsg;
-
 		LOGP(DMM, LOGL_INFO, "Selected cell is forbidden.\n");
 		new_mm_state(mm, GSM48_MM_ST_MM_IDLE,
 			GSM48_MM_SST_LIMITED_SERVICE);
 
 		/* send message to PLMN search process */
-		nmsg = gsm322_msgb_alloc(GSM322_EVENT_ROAMING_NA);
-		if (!nmsg)
-			return -ENOMEM;
-		gsm322_plmn_sendmsg(ms, nmsg);
+		gsm322_makesend_plmn_msg(ms, GSM322_EVENT_ROAMING_NA,
+					 NULL, 0);
 
 		return 0;
 	}
@@ -1174,17 +1160,12 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg)
 	if (set->plmn_mode == PLMN_MODE_MANUAL
 	 && (plmn->mcc != cs->sel_mcc
 	  || plmn->mnc != cs->sel_mnc)) {
-		struct msgb *nmsg;
-
 		LOGP(DMM, LOGL_INFO, "Selected cell not found.\n");
 		new_mm_state(mm, GSM48_MM_ST_MM_IDLE,
 			GSM48_MM_SST_LIMITED_SERVICE);
 
 		/* send message to PLMN search process */
-		nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_FAILED);
-		if (!nmsg)
-			return -ENOMEM;
-		gsm322_plmn_sendmsg(ms, nmsg);
+		gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_FAILED, NULL, 0);
 
 		return 0;
 	}
@@ -1729,7 +1710,6 @@ static int gsm48_mm_imsi_detach_end(struct osmocom_ms *ms, struct msgb *msg)
 {
 	struct gsm48_mmlayer *mm = &ms->mmlayer;
 	struct gsm_subscriber *subscr = &ms->subscr;
-	struct msgb *nmsg;
 
 	LOGP(DMM, LOGL_INFO, "IMSI has been detached.\n");
 
@@ -1753,10 +1733,7 @@ static int gsm48_mm_imsi_detach_end(struct osmocom_ms *ms, struct msgb *msg)
 	}
 
 	/* send SIM remove event to gsm322 */
-	nmsg = gsm322_msgb_alloc(GSM322_EVENT_SIM_REMOVE);
-	if (!nmsg)
-		return -ENOMEM;
-	gsm322_plmn_sendmsg(ms, nmsg);
+	gsm322_makesend_plmn_msg(ms, GSM322_EVENT_SIM_REMOVE, NULL, 0);
 
 	/* CS process will trigger return to MM IDLE / No SIM */
 	return 0;
@@ -1999,7 +1976,6 @@ static int gsm48_mm_loc_upd(struct osmocom_ms *ms, struct msgb *msg)
 	struct gsm48_sysinfo *s = &cs->sel_si;
 	struct gsm_subscriber *subscr = &ms->subscr;
 	struct gsm_settings *set = &ms->settings;
-	struct msgb *nmsg;
 	int msg_type;
 	
 	/* (re)start only if we still require location update */
@@ -2017,10 +1993,7 @@ static int gsm48_mm_loc_upd(struct osmocom_ms *ms, struct msgb *msg)
 		_stop:
 		mm->lupd_pending = 0;
 		/* send message to PLMN search process */
-		nmsg = gsm322_msgb_alloc(msg_type);
-		if (!nmsg)
-			return -ENOMEM;
-		gsm322_plmn_sendmsg(ms, nmsg);
+		gsm322_makesend_plmn_msg(ms, msg_type, NULL, 0);
 		return 0;
 	}
 
@@ -2076,7 +2049,6 @@ static int gsm48_mm_loc_upd_normal(struct osmocom_ms *ms, struct msgb *msg)
 	struct gsm_subscriber *subscr = &ms->subscr;
 	struct gsm322_cellsel *cs = &ms->cellsel;
 	struct gsm48_sysinfo *s = &cs->sel_si;
-	struct msgb *nmsg;
 
 	/* in case we already have a location update going on */
 	if (mm->lupd_pending) {
@@ -2090,10 +2062,7 @@ static int gsm48_mm_loc_upd_normal(struct osmocom_ms *ms, struct msgb *msg)
 		LOGP(DMM, LOGL_INFO, "Loc. upd. not allowed.\n");
 
 		/* send message to PLMN search process */
-		nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_FAILED);
-		if (!nmsg)
-			return -ENOMEM;
-		gsm322_plmn_sendmsg(ms, nmsg);
+		gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_FAILED, NULL, 0);
 
 		return 0;
 	}
@@ -2114,10 +2083,7 @@ static int gsm48_mm_loc_upd_normal(struct osmocom_ms *ms, struct msgb *msg)
 				GSM48_MM_SST_NORMAL_SERVICE);
 
 		/* send message to PLMN search process */
-		nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_SUCCESS);
-		if (!nmsg)
-			return -ENOMEM;
-		gsm322_plmn_sendmsg(ms, nmsg);
+		gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS, NULL, 0);
 
 		return 0;
 	}
@@ -2256,7 +2222,6 @@ static int gsm48_mm_rx_loc_upd_acc(struct osmocom_ms *ms, struct msgb *msg)
 	struct gsm48_loc_area_id *lai = (struct gsm48_loc_area_id *) gh->data;
 	unsigned int payload_len = msgb_l3len(msg) - sizeof(*gh);
 	struct tlv_parsed tp;
-	struct msgb *nmsg;
 
 	if (payload_len < sizeof(struct gsm48_loc_area_id)) {
 		short_read:
@@ -2353,10 +2318,7 @@ static int gsm48_mm_rx_loc_upd_acc(struct osmocom_ms *ms, struct msgb *msg)
 	}
 
 	/* send message to PLMN search process */
-	nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_SUCCESS);
-	if (!nmsg)
-		return -ENOMEM;
-	gsm322_plmn_sendmsg(ms, nmsg);
+	gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS, NULL, 0);
 
 	/* follow on proceed */
 	if (TLVP_PRESENT(&tp, GSM48_IE_MOBILE_ID))
@@ -2408,8 +2370,8 @@ static int gsm48_mm_rel_loc_upd_rej(struct osmocom_ms *ms, struct msgb *msg)
 {
 	struct gsm48_mmlayer *mm = &ms->mmlayer;
 	struct gsm_subscriber *subscr = &ms->subscr;
-	struct msgb *nmsg;
-	struct gsm322_msg *ngm;
+	struct gsm322_msg ngm;
+	int msg_type;
 	
 	LOGP(DMM, LOGL_INFO, "Loc. upd. rejected (cause %d)\n",
 		mm->lupd_rej_cause);
@@ -2450,23 +2412,21 @@ static int gsm48_mm_rel_loc_upd_rej(struct osmocom_ms *ms, struct msgb *msg)
 	}
 
 	/* send event to PLMN search process */
-	switch(mm->lupd_rej_cause) {
+	switch (mm->lupd_rej_cause) {
 	case GSM48_REJECT_ROAMING_NOT_ALLOWED:
-		nmsg = gsm322_msgb_alloc(GSM322_EVENT_ROAMING_NA);
+		msg_type = GSM322_EVENT_ROAMING_NA;
 		break;
 	case GSM48_REJECT_IMSI_UNKNOWN_IN_HLR:
 	case GSM48_REJECT_ILLEGAL_MS:
 	case GSM48_REJECT_ILLEGAL_ME:
-		nmsg = gsm322_msgb_alloc(GSM322_EVENT_INVALID_SIM);
+		msg_type = GSM322_EVENT_INVALID_SIM;
 		break;
 	default:
-		nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_FAILED);
+		msg_type = GSM322_EVENT_REG_FAILED;
 	}
-	if (!nmsg)
-		return -ENOMEM;
-	ngm = (struct gsm322_msg *)nmsg->data;
-	ngm->reject = mm->lupd_rej_cause;
-	gsm322_plmn_sendmsg(ms, nmsg);
+	memset(&ngm, 0, sizeof(ngm));
+	ngm.reject = mm->lupd_rej_cause;
+	gsm322_makesend_plmn_msg(ms, msg_type, NULL, 0);
 
 	/* forbidden list */
 	switch (mm->lupd_rej_cause) {
@@ -4106,13 +4066,9 @@ static int gsm48_mm_ev(struct osmocom_ms *ms, int msg_type, struct msgb *msg)
 static int gsm48_mmr_reg_req(struct osmocom_ms *ms)
 {
 	struct gsm48_mmlayer *mm = &ms->mmlayer;
-	struct msgb *nmsg;
 
 	/* schedule insertion of SIM */
-	nmsg = gsm322_msgb_alloc(GSM322_EVENT_SIM_INSERT);
-	if (!nmsg)
-		return -ENOMEM;
-	gsm322_plmn_sendmsg(ms, nmsg);
+	gsm322_makesend_plmn_msg(ms, GSM322_EVENT_SIM_INSERT, NULL, 0);
 
 	/* 4.2.1.2 SIM is inserted in state NO IMSI */
 	if (mm->state == GSM48_MM_ST_MM_IDLE
diff --git a/src/host/layer23/src/mobile/gsm48_rr.c b/src/host/layer23/src/mobile/gsm48_rr.c
index dc2226a..4a48dc8 100644
--- a/src/host/layer23/src/mobile/gsm48_rr.c
+++ b/src/host/layer23/src/mobile/gsm48_rr.c
@@ -375,8 +375,8 @@ static void new_rr_state(struct gsm48_rrlayer *rr, int state)
 	rr->state = state;
 
 	if (state == GSM48_RR_ST_IDLE) {
-		struct msgb *msg, *nmsg;
-		struct gsm322_msg *em;
+		struct msgb *msg;
+		struct gsm322_msg em;
 
 		/* release dedicated mode, if any */
 		l1ctl_tx_dm_rel_req(rr->ms);
@@ -403,16 +403,13 @@ static void new_rr_state(struct gsm48_rrlayer *rr, int state)
 		 * cell selection process returned to camping state
 		 * again. (after cell reselection)
 		 */
-		nmsg = gsm322_msgb_alloc(GSM322_EVENT_RET_IDLE);
-		if (!nmsg)
-			return;
 		/* return to same cell after LOC.UPD. */
 		if (rr->est_cause == RR_EST_CAUSE_LOC_UPD) {
-			em = (struct gsm322_msg *) nmsg->data;
-			em->same_cell = 1;
+			memset(&em, 0, sizeof(em));
+			em.same_cell = 1;
 		}
-		gsm322_c_event(rr->ms, nmsg);
-		msgb_free(nmsg);
+		gsm322_makesend_c_event(rr->ms, GSM322_EVENT_RET_IDLE,
+					(uint8_t *)&em, sizeof(em));
 		/* reset any BA range */
 		rr->ba_ranges = 0;
 	}
@@ -1192,11 +1189,7 @@ static int gsm48_rr_chan_req(struct osmocom_ms *ms, int cause, int paging)
 	 * NOTE: this must be sent unbuffered, because the state may not
 	 * change until idle mode is left
 	 */
-	nmsg = gsm322_msgb_alloc(GSM322_EVENT_LEAVE_IDLE);
-	if (!nmsg)
-		return -ENOMEM;
-	rc = gsm322_c_event(ms, nmsg);
-	msgb_free(nmsg);
+	rc = gsm322_makesend_c_event(ms, GSM322_EVENT_LEAVE_IDLE, NULL, 0);
 	if (rc) {
 		if (paging)
 			return rc;
@@ -1567,7 +1560,7 @@ static int gsm48_new_sysinfo(struct osmocom_ms *ms, uint8_t type)
 {
 	struct gsm48_sysinfo *s = ms->cellsel.si;
 	struct msgb *nmsg;
-	struct gsm322_msg *em;
+	struct gsm322_msg em;
 
 	/* update list of measurements, if BA(SACCH) is complete and new */
 	if (s
@@ -1600,12 +1593,10 @@ static int gsm48_new_sysinfo(struct osmocom_ms *ms, uint8_t type)
 	}
 
 	/* send sysinfo event to other layers */
-	nmsg = gsm322_msgb_alloc(GSM322_EVENT_SYSINFO);
-	if (!nmsg)
-		return -ENOMEM;
-	em = (struct gsm322_msg *) nmsg->data;
-	em->sysinfo = type;
-	gsm322_cs_sendmsg(ms, nmsg);
+	memset(&em, 0, sizeof(em));
+	em.sysinfo = type;
+	gsm322_makesend_cs_event(ms, GSM322_EVENT_SYSINFO,
+				 (uint8_t *)&em, sizeof(em));
 
 	/* send timer info to location update process */
 	nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_SYSINFO);
diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c
index 4cc2209..e3e7c47 100644
--- a/src/host/layer23/src/mobile/vty_interface.c
+++ b/src/host/layer23/src/mobile/vty_interface.c
@@ -658,8 +658,7 @@ DEFUN(network_select, network_select_cmd, "network select MS_NAME MCC MNC",
 {
 	struct osmocom_ms *ms;
 	struct gsm322_plmn *plmn;
-	struct msgb *nmsg;
-	struct gsm322_msg *ngm;
+	struct gsm322_msg ngm;
 	struct gsm322_plmn_list *temp;
 	uint16_t mcc = gsm_input_mcc((char *)argv[1]),
 		 mnc = gsm_input_mnc((char *)argv[2]);
@@ -687,13 +686,11 @@ DEFUN(network_select, network_select_cmd, "network select MS_NAME MCC MNC",
 		return CMD_WARNING;
 	}
 
-	nmsg = gsm322_msgb_alloc(GSM322_EVENT_CHOOSE_PLMN);
-	if (!nmsg)
-		return CMD_WARNING;
-	ngm = (struct gsm322_msg *) nmsg->data;
-	ngm->mcc = mcc;
-	ngm->mnc = mnc;
-	gsm322_plmn_sendmsg(ms, nmsg);
+	memset(&ngm, 0, sizeof(ngm));
+	ngm.mcc = mcc;
+	ngm.mnc = mnc;
+	gsm322_makesend_plmn_msg(ms, GSM322_EVENT_CHOOSE_PLMN,
+				 (uint8_t *)&ngm, sizeof(ngm));
 
 	return CMD_SUCCESS;
 }
@@ -818,16 +815,12 @@ DEFUN(network_search, network_search_cmd, "network search MS_NAME",
 	"Network ...\nTrigger network search\nName of MS (see \"show ms\")")
 {
 	struct osmocom_ms *ms;
-	struct msgb *nmsg;
 
 	ms = get_ms(argv[0], vty);
 	if (!ms)
 		return CMD_WARNING;
 
-	nmsg = gsm322_msgb_alloc(GSM322_EVENT_USER_RESEL);
-	if (!nmsg)
-		return CMD_WARNING;
-	gsm322_plmn_sendmsg(ms, nmsg);
+	gsm322_makesend_plmn_msg(ms, GSM322_EVENT_USER_RESEL, NULL, 0);
 
 	return CMD_SUCCESS;
 }
@@ -1256,7 +1249,7 @@ DEFUN(cfg_ms_mode, cfg_ms_mode_cmd, "network-selection-mode (auto|manual)",
 {
 	struct osmocom_ms *ms = vty->index;
 	struct gsm_settings *set = &ms->settings;
-	struct msgb *nmsg;
+	int msg_type = -1;
 
 	if (!ms->plmn.state) {
 		if (argv[0][0] == 'a')
@@ -1267,12 +1260,12 @@ DEFUN(cfg_ms_mode, cfg_ms_mode_cmd, "network-selection-mode (auto|manual)",
 		return CMD_SUCCESS;
 	}
 	if (argv[0][0] == 'a')
-		nmsg = gsm322_msgb_alloc(GSM322_EVENT_SEL_AUTO);
+		msg_type = GSM322_EVENT_SEL_AUTO;
 	else
-		nmsg = gsm322_msgb_alloc(GSM322_EVENT_SEL_MANUAL);
-	if (!nmsg)
+		msg_type = GSM322_EVENT_SEL_MANUAL;
+	if (msg_type < 0)
 		return CMD_WARNING;
-	gsm322_plmn_sendmsg(ms, nmsg);
+	gsm322_makesend_plmn_msg(ms, msg_type, NULL, 0);
 
 	return CMD_SUCCESS;
 }
-- 
1.7.2.3


--Kj7319i9nmIyA2yE
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="0002-mobile-replace-3-different-gsm322_makesend_-function.patch"


From laforge at gnumonks.org  Sun Jan 30 19:43:38 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Sun, 30 Jan 2011 22:43:38 +0300
Subject: [PATCH 2/3] [mobile] replace 3 different gsm322_makesend_* functions with one
Message-ID: <mailman.18.1641743546.42824.baseband-devel@lists.osmocom.org>

The new function is gsm322_event_input() and uses the event type
as a function argument.
---
 .../layer23/include/osmocom/bb/mobile/gsm322.h     |   12 +++-
 src/host/layer23/src/mobile/app_mobile.c           |    8 ++--
 src/host/layer23/src/mobile/gsm322.c               |   56 +++++---------------
 src/host/layer23/src/mobile/gsm48_mm.c             |   34 +++++++-----
 src/host/layer23/src/mobile/gsm48_rr.c             |    9 ++--
 src/host/layer23/src/mobile/vty_interface.c        |    9 ++--
 6 files changed, 57 insertions(+), 71 deletions(-)

diff --git a/src/host/layer23/include/osmocom/bb/mobile/gsm322.h b/src/host/layer23/include/osmocom/bb/mobile/gsm322.h
index 3cd275f..30d96ee 100644
--- a/src/host/layer23/include/osmocom/bb/mobile/gsm322.h
+++ b/src/host/layer23/include/osmocom/bb/mobile/gsm322.h
@@ -32,6 +32,13 @@
 #define GSM322_PLMN_SEARCH		10
 #define GSM322_HPLMN_SEARCH		11
 
+/* GSM 03.22 event types */
+enum gsm322_evt_type {
+	GSM322_EVT_C,		/* direct cell event, no queue */
+	GSM322_EVT_CS,		/* enqueue cs->event_queue */
+	GSM322_EVT_PLMN,	/* enqueue plmn->event_queue */
+};
+
 /* GSM 03.22 events */
 #define	GSM322_EVENT_SWITCH_ON		1
 #define	GSM322_EVENT_SWITCH_OFF		2	
@@ -172,9 +179,8 @@ struct gsm322_msg {
 
 int gsm322_init(struct osmocom_ms *ms);
 int gsm322_exit(struct osmocom_ms *ms);
-int gsm322_makesend_plmn_msg(struct osmocom_ms *ms, int msg_type, uint8_t *data, unsigned int len);
-int gsm322_makesend_cs_event(struct osmocom_ms *ms, int msg_type, uint8_t *data, unsigned int len);
-int gsm322_makesend_c_event(struct osmocom_ms *ms, int msg_type, uint8_t *data, unsigned int len);
+int gsm322_event_input(struct osmocom_ms *ms, enum gsm322_evt_type type,
+		       int msg_type, uint8_t *data, unsigned int len);
 int gsm322_plmn_dequeue(struct osmocom_ms *ms);
 int gsm322_cs_dequeue(struct osmocom_ms *ms);
 int gsm322_add_forbidden_la(struct osmocom_ms *ms, uint16_t mcc,
diff --git a/src/host/layer23/src/mobile/app_mobile.c b/src/host/layer23/src/mobile/app_mobile.c
index 3d2100c..b3c3284 100644
--- a/src/host/layer23/src/mobile/app_mobile.c
+++ b/src/host/layer23/src/mobile/app_mobile.c
@@ -104,10 +104,10 @@ int mobile_signal_cb(unsigned int subsys, unsigned int signal,
 			break;
 		default:
 			/* no SIM, trigger PLMN selection process */
-			gsm322_makesend_plmn_msg(ms, GSM322_EVENT_SWITCH_ON,
-						 NULL, 0);
-			gsm322_makesend_cs_event(ms, GSM322_EVENT_SWITCH_ON,
-						 NULL, 0);
+			gsm322_event_input(ms, GSM322_EVT_PLMN,
+					   GSM322_EVENT_SWITCH_ON, NULL, 0);
+			gsm322_event_input(ms, GSM322_EVT_CS,
+					   GSM322_EVENT_SWITCH_ON, NULL, 0);
 		}
 
 		ms->started = 1;
diff --git a/src/host/layer23/src/mobile/gsm322.c b/src/host/layer23/src/mobile/gsm322.c
index 1429737..3243afc 100644
--- a/src/host/layer23/src/mobile/gsm322.c
+++ b/src/host/layer23/src/mobile/gsm322.c
@@ -3604,8 +3604,8 @@ int gsm322_exit(struct osmocom_ms *ms)
 	return 0;
 }
 
-int gsm322_makesend_c_event(struct osmocom_ms *ms, int msg_type,
-			    uint8_t *data, unsigned int len)
+int gsm322_event_input(struct osmocom_ms *ms, enum gsm322_evt_type type,
+		       int msg_type, uint8_t *data, unsigned int len)
 {
 	struct msgb *nmsg = gsm322_msgb_alloc(msg_type);
 	int rc;
@@ -3621,46 +3621,18 @@ int gsm322_makesend_c_event(struct osmocom_ms *ms, int msg_type,
 		}
 		memcpy(cur, data, len);
 	}
-	rc = gsm322_c_event(ms, nmsg);
-	msgb_free(nmsg);
-
-	return rc;
-}
-
-int gsm322_makesend_cs_event(struct osmocom_ms *ms, int msg_type,
-			     uint8_t *data, unsigned int len)
-{
-	struct msgb *nmsg = gsm322_msgb_alloc(msg_type);
-
-	if (!nmsg)
-		return -ENOMEM;
-
-	if (data && len) {
-		uint8_t *cur = msgb_push(nmsg, len);
-		if (!cur) {
-			msgb_free(nmsg);
-			return -EIO;
-		}
-		memcpy(cur, data, len);
+	switch (type) {
+	case GSM322_EVT_C:
+		rc = gsm322_c_event(ms, nmsg);
+		msgb_free(nmsg);
+		break;
+	case GSM322_EVT_CS:
+		rc = gsm322_cs_sendmsg(ms, nmsg);
+		break;
+	case GSM322_EVT_PLMN:
+		rc = gsm322_plmn_sendmsg(ms, nmsg);
+		break;
 	}
-	return  gsm322_cs_sendmsg(ms, nmsg);
-}
-
-int gsm322_makesend_plmn_msg(struct osmocom_ms *ms, int msg_type,
-			     uint8_t *data, unsigned int len)
-{
-	struct msgb *nmsg = gsm322_msgb_alloc(msg_type);
-
-	if (!nmsg)
-		return -ENOMEM;
 
-	if (data && len) {
-		uint8_t *cur = msgb_push(nmsg, len);
-		if (!cur) {
-			msgb_free(nmsg);
-			return -EIO;
-		}
-		memcpy(cur, data, len);
-	}
-	return gsm322_plmn_sendmsg(ms, nmsg);
+	return rc;
 }
diff --git a/src/host/layer23/src/mobile/gsm48_mm.c b/src/host/layer23/src/mobile/gsm48_mm.c
index 58253bd..4652f34 100644
--- a/src/host/layer23/src/mobile/gsm48_mm.c
+++ b/src/host/layer23/src/mobile/gsm48_mm.c
@@ -1123,8 +1123,8 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg)
 				GSM48_MM_SST_NORMAL_SERVICE);
 
 			/* send message to PLMN search process */
-			gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS,
-						 NULL, 0);
+			gsm322_event_input(ms, GSM322_EVT_PLMN,
+					   GSM322_EVENT_REG_SUCCESS, NULL, 0);
 			return 0;
 		}
 		if (!s->att_allowed) {
@@ -1133,8 +1133,8 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg)
 				GSM48_MM_SST_NORMAL_SERVICE);
 
 			/* send message to PLMN search process */
-			gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS,
-						 NULL, 0);
+			gsm322_event_input(ms, GSM322_EVT_PLMN,
+					   GSM322_EVENT_REG_SUCCESS, NULL, 0);
 			return 0;
 		}
 		/* else, continue */
@@ -1150,8 +1150,8 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg)
 			GSM48_MM_SST_LIMITED_SERVICE);
 
 		/* send message to PLMN search process */
-		gsm322_makesend_plmn_msg(ms, GSM322_EVENT_ROAMING_NA,
-					 NULL, 0);
+		gsm322_event_input(ms, GSM322_EVT_PLMN,
+				   GSM322_EVENT_ROAMING_NA, NULL, 0);
 
 		return 0;
 	}
@@ -1165,7 +1165,8 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg)
 			GSM48_MM_SST_LIMITED_SERVICE);
 
 		/* send message to PLMN search process */
-		gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_FAILED, NULL, 0);
+		gsm322_event_input(ms, GSM322_EVT_PLMN,
+				   GSM322_EVENT_REG_FAILED, NULL, 0);
 
 		return 0;
 	}
@@ -1733,7 +1734,8 @@ static int gsm48_mm_imsi_detach_end(struct osmocom_ms *ms, struct msgb *msg)
 	}
 
 	/* send SIM remove event to gsm322 */
-	gsm322_makesend_plmn_msg(ms, GSM322_EVENT_SIM_REMOVE, NULL, 0);
+	gsm322_event_input(ms, GSM322_EVT_PLMN,
+			   GSM322_EVENT_SIM_REMOVE, NULL, 0);
 
 	/* CS process will trigger return to MM IDLE / No SIM */
 	return 0;
@@ -1993,7 +1995,7 @@ static int gsm48_mm_loc_upd(struct osmocom_ms *ms, struct msgb *msg)
 		_stop:
 		mm->lupd_pending = 0;
 		/* send message to PLMN search process */
-		gsm322_makesend_plmn_msg(ms, msg_type, NULL, 0);
+		gsm322_event_input(ms, GSM322_EVT_PLMN, msg_type, NULL, 0);
 		return 0;
 	}
 
@@ -2062,7 +2064,8 @@ static int gsm48_mm_loc_upd_normal(struct osmocom_ms *ms, struct msgb *msg)
 		LOGP(DMM, LOGL_INFO, "Loc. upd. not allowed.\n");
 
 		/* send message to PLMN search process */
-		gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_FAILED, NULL, 0);
+		gsm322_event_input(ms, GSM322_EVT_PLMN,
+				   GSM322_EVENT_REG_FAILED, NULL, 0);
 
 		return 0;
 	}
@@ -2083,7 +2086,8 @@ static int gsm48_mm_loc_upd_normal(struct osmocom_ms *ms, struct msgb *msg)
 				GSM48_MM_SST_NORMAL_SERVICE);
 
 		/* send message to PLMN search process */
-		gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS, NULL, 0);
+		gsm322_event_input(ms, GSM322_EVT_PLMN,
+				   GSM322_EVENT_REG_SUCCESS, NULL, 0);
 
 		return 0;
 	}
@@ -2318,7 +2322,8 @@ static int gsm48_mm_rx_loc_upd_acc(struct osmocom_ms *ms, struct msgb *msg)
 	}
 
 	/* send message to PLMN search process */
-	gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS, NULL, 0);
+	gsm322_event_input(ms, GSM322_EVT_PLMN,
+			   GSM322_EVENT_REG_SUCCESS, NULL, 0);
 
 	/* follow on proceed */
 	if (TLVP_PRESENT(&tp, GSM48_IE_MOBILE_ID))
@@ -2426,7 +2431,7 @@ static int gsm48_mm_rel_loc_upd_rej(struct osmocom_ms *ms, struct msgb *msg)
 	}
 	memset(&ngm, 0, sizeof(ngm));
 	ngm.reject = mm->lupd_rej_cause;
-	gsm322_makesend_plmn_msg(ms, msg_type, NULL, 0);
+	gsm322_event_input(ms, GSM322_EVT_PLMN, msg_type, &ngm, sizeof(ngm));
 
 	/* forbidden list */
 	switch (mm->lupd_rej_cause) {
@@ -4068,7 +4073,8 @@ static int gsm48_mmr_reg_req(struct osmocom_ms *ms)
 	struct gsm48_mmlayer *mm = &ms->mmlayer;
 
 	/* schedule insertion of SIM */
-	gsm322_makesend_plmn_msg(ms, GSM322_EVENT_SIM_INSERT, NULL, 0);
+	gsm322_event_input(ms, GSM322_EVT_PLMN,
+			   GSM322_EVENT_SIM_INSERT, NULL, 0);
 
 	/* 4.2.1.2 SIM is inserted in state NO IMSI */
 	if (mm->state == GSM48_MM_ST_MM_IDLE
diff --git a/src/host/layer23/src/mobile/gsm48_rr.c b/src/host/layer23/src/mobile/gsm48_rr.c
index 4a48dc8..177b272 100644
--- a/src/host/layer23/src/mobile/gsm48_rr.c
+++ b/src/host/layer23/src/mobile/gsm48_rr.c
@@ -408,8 +408,8 @@ static void new_rr_state(struct gsm48_rrlayer *rr, int state)
 			memset(&em, 0, sizeof(em));
 			em.same_cell = 1;
 		}
-		gsm322_makesend_c_event(rr->ms, GSM322_EVENT_RET_IDLE,
-					(uint8_t *)&em, sizeof(em));
+		gsm322_event_input(rr->ms, GSM322_EVT_C, GSM322_EVENT_RET_IDLE,
+				   (uint8_t *)&em, sizeof(em));
 		/* reset any BA range */
 		rr->ba_ranges = 0;
 	}
@@ -1189,7 +1189,8 @@ static int gsm48_rr_chan_req(struct osmocom_ms *ms, int cause, int paging)
 	 * NOTE: this must be sent unbuffered, because the state may not
 	 * change until idle mode is left
 	 */
-	rc = gsm322_makesend_c_event(ms, GSM322_EVENT_LEAVE_IDLE, NULL, 0);
+	rc = gsm322_event_input(ms, GSM322_EVT_C, GSM322_EVENT_LEAVE_IDLE,
+				NULL, 0);
 	if (rc) {
 		if (paging)
 			return rc;
@@ -1595,7 +1596,7 @@ static int gsm48_new_sysinfo(struct osmocom_ms *ms, uint8_t type)
 	/* send sysinfo event to other layers */
 	memset(&em, 0, sizeof(em));
 	em.sysinfo = type;
-	gsm322_makesend_cs_event(ms, GSM322_EVENT_SYSINFO,
+	gsm322_event_input(ms, GSM322_EVT_CS, GSM322_EVENT_SYSINFO,
 				 (uint8_t *)&em, sizeof(em));
 
 	/* send timer info to location update process */
diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c
index e3e7c47..d83dae8 100644
--- a/src/host/layer23/src/mobile/vty_interface.c
+++ b/src/host/layer23/src/mobile/vty_interface.c
@@ -689,8 +689,8 @@ DEFUN(network_select, network_select_cmd, "network select MS_NAME MCC MNC",
 	memset(&ngm, 0, sizeof(ngm));
 	ngm.mcc = mcc;
 	ngm.mnc = mnc;
-	gsm322_makesend_plmn_msg(ms, GSM322_EVENT_CHOOSE_PLMN,
-				 (uint8_t *)&ngm, sizeof(ngm));
+	gsm322_event_input(ms, GSM322_EVT_PLMN, GSM322_EVENT_CHOOSE_PLMN,
+			   (uint8_t *)&ngm, sizeof(ngm));
 
 	return CMD_SUCCESS;
 }
@@ -820,7 +820,8 @@ DEFUN(network_search, network_search_cmd, "network search MS_NAME",
 	if (!ms)
 		return CMD_WARNING;
 
-	gsm322_makesend_plmn_msg(ms, GSM322_EVENT_USER_RESEL, NULL, 0);
+	gsm322_event_input(ms, GSM322_EVT_PLMN,
+			   GSM322_EVENT_USER_RESEL, NULL, 0);
 
 	return CMD_SUCCESS;
 }
@@ -1265,7 +1266,7 @@ DEFUN(cfg_ms_mode, cfg_ms_mode_cmd, "network-selection-mode (auto|manual)",
 		msg_type = GSM322_EVENT_SEL_MANUAL;
 	if (msg_type < 0)
 		return CMD_WARNING;
-	gsm322_makesend_plmn_msg(ms, msg_type, NULL, 0);
+	gsm322_event_input(ms, GSM322_EVT_PLMN, msg_type, NULL, 0);
 
 	return CMD_SUCCESS;
 }
-- 
1.7.2.3


--Kj7319i9nmIyA2yE
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="0003-mobile-introduce-and-use-gsm48_mmevevent_input.patch"


From laforge at gnumonks.org  Sun Jan 30 19:58:47 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Sun, 30 Jan 2011 22:58:47 +0300
Subject: [PATCH 3/3] [mobile] introduce and use gsm48_mmevevent_input()
Message-ID: <mailman.19.1641743546.42824.baseband-devel@lists.osmocom.org>

... instead of using sequences of gsm48_mmevent_msgb_alloc() followed by
gsm48_mmevent_msg()
---
 .../layer23/include/osmocom/bb/mobile/gsm48_mm.h   |    4 +-
 src/host/layer23/src/mobile/app_mobile.c           |    5 +--
 src/host/layer23/src/mobile/gsm322.c               |   41 +++-----------------
 src/host/layer23/src/mobile/gsm48_mm.c             |   41 ++++++++++++--------
 src/host/layer23/src/mobile/gsm48_rr.c             |    6 +--
 src/host/layer23/src/mobile/subscriber.c           |   31 +++------------
 6 files changed, 41 insertions(+), 87 deletions(-)

diff --git a/src/host/layer23/include/osmocom/bb/mobile/gsm48_mm.h b/src/host/layer23/include/osmocom/bb/mobile/gsm48_mm.h
index 447dc95..c141d5c 100644
--- a/src/host/layer23/include/osmocom/bb/mobile/gsm48_mm.h
+++ b/src/host/layer23/include/osmocom/bb/mobile/gsm48_mm.h
@@ -210,8 +210,8 @@ struct gsm48_mm_conn {
 int gsm48_mm_init(struct osmocom_ms *ms);
 int gsm48_mm_exit(struct osmocom_ms *ms);
 struct msgb *gsm48_mmr_msgb_alloc(int msg_type);
-struct msgb *gsm48_mmevent_msgb_alloc(int msg_type);
-int gsm48_mmevent_msg(struct osmocom_ms *ms, struct msgb *msg);
+int gsm48_mmevent_input(struct osmocom_ms *ms, int msg_type,
+			const uint8_t *data, unsigned int len);
 int gsm48_mmr_downmsg(struct osmocom_ms *ms, struct msgb *msg);
 int gsm48_rr_dequeue(struct osmocom_ms *ms);
 int gsm48_mmxx_dequeue(struct osmocom_ms *ms);
diff --git a/src/host/layer23/src/mobile/app_mobile.c b/src/host/layer23/src/mobile/app_mobile.c
index b3c3284..4e6a803 100644
--- a/src/host/layer23/src/mobile/app_mobile.c
+++ b/src/host/layer23/src/mobile/app_mobile.c
@@ -124,10 +124,7 @@ int mobile_exit(struct osmocom_ms *ms, int force)
 		struct msgb *nmsg;
 
 		ms->shutdown = 1; /* going down */
-		nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_IMSI_DETACH);
-		if (!nmsg)
-			return -ENOMEM;
-		gsm48_mmevent_msg(mm->ms, nmsg);
+		gsm48_mmevent_input(ms, GSM48_MM_EVENT_IMSI_DETACH, NULL, 0);
 
 		return -EBUSY;
 	}
diff --git a/src/host/layer23/src/mobile/gsm322.c b/src/host/layer23/src/mobile/gsm322.c
index 3243afc..60b24cb 100644
--- a/src/host/layer23/src/mobile/gsm322.c
+++ b/src/host/layer23/src/mobile/gsm322.c
@@ -1174,17 +1174,12 @@ static int gsm322_a_hplmn_search_start(struct osmocom_ms *ms, struct msgb *msg)
 /* manual mode selected */
 static int gsm322_a_sel_manual(struct osmocom_ms *ms, struct msgb *msg)
 {
-	struct msgb *nmsg;
-
 	/* restart state machine */
 	gsm322_a_switch_off(ms, msg);
 	ms->settings.plmn_mode = PLMN_MODE_MANUAL;
 	gsm322_m_switch_on(ms, msg);
 
-	nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_USER_PLMN_SEL);
-	if (!nmsg)
-		return -ENOMEM;
-	gsm48_mmevent_msg(ms, nmsg);
+	gsm48_mmevent_input(ms, GSM48_MM_EVENT_USER_PLMN_SEL, NULL, 0);
 
 	return 0;
 }
@@ -1461,17 +1456,12 @@ static int gsm322_m_choose_plmn(struct osmocom_ms *ms, struct msgb *msg)
 /* auto mode selected */
 static int gsm322_m_sel_auto(struct osmocom_ms *ms, struct msgb *msg)
 {
-	struct msgb *nmsg;
-
 	/* restart state machine */
 	gsm322_m_switch_off(ms, msg);
 	ms->settings.plmn_mode = PLMN_MODE_AUTO;
 	gsm322_a_switch_on(ms, msg);
 
-	nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_USER_PLMN_SEL);
-	if (!nmsg)
-		return -ENOMEM;
-	gsm48_mmevent_msg(ms, nmsg);
+	gsm48_mmevent_input(ms, GSM48_MM_EVENT_USER_PLMN_SEL, NULL, 0);
 
 	return 0;
 }
@@ -2684,14 +2674,8 @@ static int gsm322_c_any_cell_sel(struct osmocom_ms *ms, struct msgb *msg)
 	/* after re-selection, indicate no cell found */
 	if (cs->state == GSM322_C6_ANY_CELL_SEL
 	 || cs->state == GSM322_C8_ANY_CELL_RESEL) {
-		struct msgb *nmsg;
-
 		/* tell that we have no cell found */
-		nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_NO_CELL_FOUND);
-		if (!nmsg)
-			return -ENOMEM;
-		gsm48_mmevent_msg(ms, nmsg);
-
+		gsm48_mmevent_input(ms, GSM48_MM_EVENT_NO_CELL_FOUND, NULL, 0);
 	} else { 
 		new_c_state(cs, GSM322_C6_ANY_CELL_SEL);
 	}
@@ -2737,7 +2721,6 @@ static int gsm322_c_any_cell_resel(struct osmocom_ms *ms, struct msgb *msg)
 static int gsm322_c_camp_normally(struct osmocom_ms *ms, struct msgb *msg)
 {
 	struct gsm322_cellsel *cs = &ms->cellsel;
-	struct msgb *nmsg;
 
 	LOGP(DSUM, LOGL_INFO, "Camping normally on cell (arfcn=%d mcc=%s "
 		"mnc=%s  %s, %s)\n", cs->sel_arfcn, gsm_print_mcc(cs->sel_mcc),
@@ -2745,10 +2728,7 @@ static int gsm322_c_camp_normally(struct osmocom_ms *ms, struct msgb *msg)
 		gsm_get_mnc(cs->sel_mcc, cs->sel_mnc));
 
 	/* tell that we have selected a (new) cell */
-	nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_CELL_SELECTED);
-	if (!nmsg)
-		return -ENOMEM;
-	gsm48_mmevent_msg(ms, nmsg);
+	gsm48_mmevent_input(ms, GSM48_MM_EVENT_CELL_SELECTED, NULL, 0);
 
 	new_c_state(cs, GSM322_C3_CAMPED_NORMALLY);
 
@@ -2759,7 +2739,6 @@ static int gsm322_c_camp_normally(struct osmocom_ms *ms, struct msgb *msg)
 static int gsm322_c_camp_any_cell(struct osmocom_ms *ms, struct msgb *msg)
 {
 	struct gsm322_cellsel *cs = &ms->cellsel;
-	struct msgb *nmsg;
 
 	LOGP(DSUM, LOGL_INFO, "Camping on any cell (arfcn=%d mcc=%s "
 		"mnc=%s  %s, %s)\n", cs->sel_arfcn, gsm_print_mcc(cs->sel_mcc),
@@ -2768,10 +2747,7 @@ static int gsm322_c_camp_any_cell(struct osmocom_ms *ms, struct msgb *msg)
 
 
 	/* tell that we have selected a (new) cell */
-	nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_CELL_SELECTED);
-	if (!nmsg)
-		return -ENOMEM;
-	gsm48_mmevent_msg(ms, nmsg);
+	gsm48_mmevent_input(ms, GSM48_MM_EVENT_CELL_SELECTED, NULL, 0);
 
 	new_c_state(cs, GSM322_C7_CAMPED_ANY_CELL);
 
@@ -2878,8 +2854,6 @@ static int gsm322_c_choose_cell(struct osmocom_ms *ms, struct msgb *msg)
 
 	/* After location updating, we choose the last cell */
 	if (gm->same_cell) {
-		struct msgb *nmsg;
-
 		if (!cs->selected) {
 			printf("No cell selected when ret.idle, please fix!\n");
 			exit(0L);
@@ -2896,10 +2870,7 @@ static int gsm322_c_choose_cell(struct osmocom_ms *ms, struct msgb *msg)
 		new_c_state(cs, GSM322_C3_CAMPED_NORMALLY);
 
 		/* tell that we have selected the cell, so RR returns IDLE */
-		nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_CELL_SELECTED);
-		if (!nmsg)
-			return -ENOMEM;
-		gsm48_mmevent_msg(ms, nmsg);
+		gsm48_mmevent_input(ms, GSM48_MM_EVENT_CELL_SELECTED, NULL, 0);
 
 		return 0;
 	}
diff --git a/src/host/layer23/src/mobile/gsm48_mm.c b/src/host/layer23/src/mobile/gsm48_mm.c
index 4652f34..6400373 100644
--- a/src/host/layer23/src/mobile/gsm48_mm.c
+++ b/src/host/layer23/src/mobile/gsm48_mm.c
@@ -658,7 +658,7 @@ struct msgb *gsm48_mmxx_msgb_alloc(int msg_type, uint32_t ref,
 }
 
 /* allocate MM event message */
-struct msgb *gsm48_mmevent_msgb_alloc(int msg_type)
+static struct msgb *gsm48_mmevent_msgb_alloc(int msg_type)
 {
 	struct msgb *msg;
 	struct gsm48_mm_event *mme;
@@ -710,7 +710,7 @@ int gsm48_mmr_downmsg(struct osmocom_ms *ms, struct msgb *msg)
 }
 
 /* queue MM event message */
-int gsm48_mmevent_msg(struct osmocom_ms *ms, struct msgb *msg)
+static int gsm48_mmevent_msg(struct osmocom_ms *ms, struct msgb *msg)
 {
 	struct gsm48_mmlayer *mm = &ms->mmlayer;
 
@@ -905,14 +905,10 @@ static void new_mm_state(struct gsm48_mmlayer *mm, int state, int substate)
 
 	/* resend detach event, if flag is set */
 	if (state == GSM48_MM_ST_MM_IDLE && mm->delay_detach) {
-		struct msgb *nmsg;
-
 		mm->delay_detach = 0;
 
-		nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_IMSI_DETACH);
-		if (!nmsg)
-			return;
-		gsm48_mmevent_msg(mm->ms, nmsg);
+		gsm48_mmevent_input(mm->ms, GSM48_MM_EVENT_IMSI_DETACH,
+				    NULL, 0);
 	}
 
 	/* 4.4.2 start T3212 in MM IDLE mode if not started or has expired */
@@ -2431,7 +2427,8 @@ static int gsm48_mm_rel_loc_upd_rej(struct osmocom_ms *ms, struct msgb *msg)
 	}
 	memset(&ngm, 0, sizeof(ngm));
 	ngm.reject = mm->lupd_rej_cause;
-	gsm322_event_input(ms, GSM322_EVT_PLMN, msg_type, &ngm, sizeof(ngm));
+	gsm322_event_input(ms, GSM322_EVT_PLMN, msg_type,
+			   (uint8_t *)&ngm, sizeof(ngm));
 
 	/* forbidden list */
 	switch (mm->lupd_rej_cause) {
@@ -4088,13 +4085,7 @@ static int gsm48_mmr_reg_req(struct osmocom_ms *ms)
 /* trigger detach of sim card */
 static int gsm48_mmr_nreg_req(struct osmocom_ms *ms)
 {
-	struct gsm48_mmlayer *mm = &ms->mmlayer;
-	struct msgb *nmsg;
-
-	nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_IMSI_DETACH);
-	if (!nmsg)
-		return -ENOMEM;
-	gsm48_mmevent_msg(mm->ms, nmsg);
+	gsm48_mmevent_input(ms, GSM48_MM_EVENT_IMSI_DETACH, NULL, 0);
 
 	return 0;
 }
@@ -4121,4 +4112,22 @@ static int gsm48_rcv_mmr(struct osmocom_ms *ms, struct msgb *msg)
 	return rc;
 }
 
+int gsm48_mmevent_input(struct osmocom_ms *ms, int msg_type,
+			const uint8_t *data, unsigned int len)
+{
+	struct msgb *nmsg = gsm48_mmevent_msgb_alloc(msg_type);
+	int rc;
+
+	if (!nmsg)
+		return -ENOMEM;
 
+	if (data && len) {
+		uint8_t *cur = msgb_push(nmsg, len);
+		if (!cur) {
+			msgb_free(nmsg);
+			return -EIO;
+		}
+		memcpy(cur, data, len);
+	}
+	return gsm48_mmevent_msg(ms, nmsg);
+}
diff --git a/src/host/layer23/src/mobile/gsm48_rr.c b/src/host/layer23/src/mobile/gsm48_rr.c
index 177b272..afb53cb 100644
--- a/src/host/layer23/src/mobile/gsm48_rr.c
+++ b/src/host/layer23/src/mobile/gsm48_rr.c
@@ -1560,7 +1560,6 @@ fail:
 static int gsm48_new_sysinfo(struct osmocom_ms *ms, uint8_t type)
 {
 	struct gsm48_sysinfo *s = ms->cellsel.si;
-	struct msgb *nmsg;
 	struct gsm322_msg em;
 
 	/* update list of measurements, if BA(SACCH) is complete and new */
@@ -1600,10 +1599,7 @@ static int gsm48_new_sysinfo(struct osmocom_ms *ms, uint8_t type)
 				 (uint8_t *)&em, sizeof(em));
 
 	/* send timer info to location update process */
-	nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_SYSINFO);
-	if (!nmsg)
-		return -ENOMEM;
-	gsm48_mmevent_msg(ms, nmsg);
+	gsm48_mmevent_input(ms, GSM48_MM_EVENT_SYSINFO, NULL, 0);
 
 	return 0;
 }
diff --git a/src/host/layer23/src/mobile/subscriber.c b/src/host/layer23/src/mobile/subscriber.c
index 3ba78f3..24d7f94 100644
--- a/src/host/layer23/src/mobile/subscriber.c
+++ b/src/host/layer23/src/mobile/subscriber.c
@@ -855,25 +855,16 @@ int gsm_subscr_generate_kc(struct osmocom_ms *ms, uint8_t key_seq,
 	if ((subscr->sim_type != GSM_SIM_TYPE_READER
 	  && subscr->sim_type != GSM_SIM_TYPE_TEST)
 	 || !subscr->sim_valid || no_sim) {
-		struct gsm48_mm_event *nmme;
+		uint8_t dummy_sres[4] = { 0x12, 0x34, 0x56, 0x78 };
 
 		LOGP(DMM, LOGL_INFO, "Sending dummy authentication response\n");
-		nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_AUTH_RESPONSE);
-		if (!nmsg)
-			return -ENOMEM;
-		nmme = (struct gsm48_mm_event *) nmsg->data;
-		nmme->sres[0] = 0x12;
-		nmme->sres[1] = 0x34;
-		nmme->sres[2] = 0x56;
-		nmme->sres[3] = 0x78;
-		gsm48_mmevent_msg(ms, nmsg);
-
+		gsm48_mmevent_input(ms, GSM48_MM_EVENT_AUTH_RESPONSE,
+				    dummy_sres, sizeof(dummy_sres));
 		return 0;
 	}
 
 	/* test SIM */
 	if (subscr->sim_type == GSM_SIM_TYPE_TEST) {
-		struct gsm48_mm_event *nmme;
 		uint8_t sres[4];
 		struct gsm_settings *set = &ms->settings;
 
@@ -885,12 +876,8 @@ int gsm_subscr_generate_kc(struct osmocom_ms *ms, uint8_t key_seq,
 		subscr->key_seq = key_seq;
 
 		LOGP(DMM, LOGL_INFO, "Sending authentication response\n");
-		nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_AUTH_RESPONSE);
-		if (!nmsg)
-			return -ENOMEM;
-		nmme = (struct gsm48_mm_event *) nmsg->data;
-		memcpy(nmme->sres, sres, 4);
-		gsm48_mmevent_msg(ms, nmsg);
+		gsm48_mmevent_input(ms, GSM48_MM_EVENT_AUTH_RESPONSE,
+				    sres, sizeof(sres));
 
 		return 0;
 	}
@@ -924,7 +911,6 @@ static void subscr_sim_key_cb(struct osmocom_ms *ms, struct msgb *msg)
 	uint16_t payload_len = msg->len - sizeof(*sh);
 	struct msgb *nmsg;
 	struct sim_hdr *nsh;
-	struct gsm48_mm_event *nmme;
 	uint8_t *data;
 
 	/* error handling */
@@ -961,12 +947,7 @@ static void subscr_sim_key_cb(struct osmocom_ms *ms, struct msgb *msg)
 	sim_job(ms, nmsg);
 
 	/* return signed response */
-	nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_AUTH_RESPONSE);
-	if (!nmsg)
-		return;
-	nmme = (struct gsm48_mm_event *) nmsg->data;
-	memcpy(nmme->sres, payload, 4);
-	gsm48_mmevent_msg(ms, nmsg);
+	gsm48_mmevent_input(ms, GSM48_MM_EVENT_AUTH_RESPONSE, payload, 4);
 
 	msgb_free(msg);
 }
-- 
1.7.2.3


--Kj7319i9nmIyA2yE--



From ml at mail.tsaitgaist.info  Sun Jan 30 22:05:59 2011
From: ml at mail.tsaitgaist.info (tsaitgaist)
Date: Sun, 30 Jan 2011 23:05:59 +0100
Subject: SIMtrace issues
Message-ID: <4D45E0C7.4070201@mail.tsaitgaist.info>

hi,

I'll be listing some issues I found in SIMtrace.
This is to warn future users.
I don't have time now, but I intend to work on this project in 1 or 2
weeks and correct these bugs.

1. when starting host program simtrace, the firmware will first return
ATR. This is an error if simtrace is started after the card has been
reseted. The program should use the state of the reset and vcc lines to
know the state.

2. when using a usb hub, having a lot of USB traffic, or poor USB signal
quality (I don't know exactly), bulk read timeouts can occur in host program
simtrace/at91sam7/host/main.c line 230:
rc = usb_bulk_read(udev, SIMTRACE_IN_EP, buf, sizeof(buf), 100000);

rc is -110 (REQUEST_TIMEOUT). I increased the timeout (100000) so to
have less errors (but they still occur), and I ignore this error instead
of exiting (tracing still works).

3. it seems simtrace can loose track of the I/O stream after some
traffic. see pcsc_apdu.log to see the original, and simtrace_apdu.log
for the captured traffic.
in the end, simtrace misses:
APDU: A0 C0 00 00 0F
and does a wrong following APDU parsing

The problem occurs when using a OmniKey CardMan 5321 and Alcor Micro
AU9520. Thus the reader should not be the origin.
Also, if only the command where the error occurs is sent, no bytes are
skipped. But another error occurs (see next bug)

4. when executing only the last commands, then it is wrongly interpreted
(as ATR), but no bytes are skipped
ATR (12):  3b 0a 41 00 3f 43 00 01 50 29 01 02
ATR (66):  a0 a4 00 00 02 a4 7f 20 9f 17 a0 a4 00 00 02 a4 6f ad 9f 0f
a0 c0 00 00 0f c0 00 00 00 03 6f ad 04 00 04 f0 44 01 02 00 00 90 00 a0
b0 00 00 03 b0 00 00 00 90 00 3b 0a 41 00 3f 43 00 01 50 29 01 02

I already wrote a SIM traffic parser for the PC before simtrace
appeared. I used a logic analyzer to record the traffic.
I will integrate the ATR and APDU parsing/checking into the simtrace
firmware. Wrong recorded traffic will be discarded instead of affecting
the rest of the parsing.

thanks,
kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pcsc_apdu.log
Type: text/x-log
Size: 4408 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/bd6c402b/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: simtrace_apdu.log
Type: text/x-log
Size: 3711 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/bd6c402b/attachment-0001.bin>

From laforge at gnumonks.org  Mon Jan 31 15:08:16 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Mon, 31 Jan 2011 18:08:16 +0300
Subject: SIMtrace issues
In-Reply-To: <4D45E0C7.4070201@mail.tsaitgaist.info>
References: <4D45E0C7.4070201@mail.tsaitgaist.info>
Message-ID: <20110131150816.GF3786@prithivi.gnumonks.org>

Hi Kevin,

On Sun, Jan 30, 2011 at 11:05:59PM +0100, tsaitgaist wrote:
 
> I'll be listing some issues I found in SIMtrace.
> This is to warn future users.
> I don't have time now, but I intend to work on this project in 1 or 2
> weeks and correct these bugs.
> 
> 1. when starting host program simtrace, the firmware will first return
> ATR. This is an error if simtrace is started after the card has been
> reseted. The program should use the state of the reset and vcc lines to
> know the state.

this is unfortunately not possible.  You _have_ to start your phone
after you have started simtrace.  Otherwise we would not observe PPS
and thus not know which bit/baud rates to use.  

> 2. when using a usb hub, having a lot of USB traffic, or poor USB signal
> quality (I don't know exactly), bulk read timeouts can occur in host program
> simtrace/at91sam7/host/main.c line 230:
> rc = usb_bulk_read(udev, SIMTRACE_IN_EP, buf, sizeof(buf), 100000);

ok, interesting.  I think its not really something we need to care about,
if it works reliably using good cables/hubs.

> I already wrote a SIM traffic parser for the PC before simtrace
> appeared. I used a logic analyzer to record the traffic.
> I will integrate the ATR and APDU parsing/checking into the simtrace
> firmware. Wrong recorded traffic will be discarded instead of affecting
> the rest of the parsing.

ok, great. I'm looking forward to any contributions / bug fixes.  Thanks
 a lot!
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From peter at stuge.se  Mon Jan 31 15:46:32 2011
From: peter at stuge.se (Peter Stuge)
Date: Mon, 31 Jan 2011 16:46:32 +0100
Subject: SIMtrace issues
In-Reply-To: <20110131150816.GF3786@prithivi.gnumonks.org>
References: <4D45E0C7.4070201@mail.tsaitgaist.info>
	<20110131150816.GF3786@prithivi.gnumonks.org>
Message-ID: <20110131154632.27701.qmail@stuge.se>

Harald Welte wrote:
> > 2. when using a usb hub, having a lot of USB traffic, or poor USB
> > signal quality (I don't know exactly), bulk read timeouts can
> > occur in host program simtrace/at91sam7/host/main.c line 230:
> > rc = usb_bulk_read(udev, SIMTRACE_IN_EP, buf, sizeof(buf), 100000);
> 
> ok, interesting.  I think its not really something we need to care
> about, if it works reliably using good cables/hubs.

The issue is probably with the fact that bulk transfers are used for
the data.

Bulk transfers have no bound latency, they will be delivered "as soon
as possible" but this can very well mean indefinite delay on a loaded
bus. Interrupt transfers and isochronous transfer both have
guaranteed bus time, the latter are lossy (think UDP) so I'd suggest
using interrupt transfer if there's a choice.

Programmatically they work very much like bulk so switching over
should be simple.

Oh, and in host programs please don't use the old libusb-0.1 API with
usb_ functions as it has been deprecated and unmaintained for years,
please start using the libusb-1.0 API with libusb_ functions instead;
it fixes bugs, has better performance and is actually being worked
on. :)


//Peter



From ml at mail.tsaitgaist.info  Sun Jan 30 23:07:30 2011
From: ml at mail.tsaitgaist.info (tsaitgaist)
Date: Mon, 31 Jan 2011 00:07:30 +0100
Subject: osmocomSIM
Message-ID: <4D45EF32.3000602@mail.tsaitgaist.info>

Hi,

how about opening the sub-project osmocomSIM ?
This could include:
- SIMtrace from Harald
- SAP server from Andreas
- SIM on javacard from S?bastien
- future software/virtual SIM which could use SAP server
- speaking about A38, Ki, SIM features, ...

kevin



From laforge at gnumonks.org  Mon Jan 31 15:10:39 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Mon, 31 Jan 2011 18:10:39 +0300
Subject: [ADM] osmocomSIM split?
In-Reply-To: <4D45EF32.3000602@mail.tsaitgaist.info>
References: <4D45EF32.3000602@mail.tsaitgaist.info>
Message-ID: <20110131151039.GG3786@prithivi.gnumonks.org>

Hi Kevin,

On Mon, Jan 31, 2011 at 12:07:30AM +0100, tsaitgaist wrote:
 
> how about opening the sub-project osmocomSIM ?

what exactly do you mean by subproject?  Using a separate trac installation,
mailing list, ...?  I think that might be a bit too much fragmentation.

But then, I'm not very clearly decided on this.  SIM card tracing/emulation
clearly is not a 'baseband' related task, so it may be an option to do
this independently.

At least I like the idea of splitting SIM card and OsmocomBB related stuff
much better than the recently proposed user/developer split of the list.

What do others think?
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From ml at mail.tsaitgaist.info  Mon Jan 31 15:43:30 2011
From: ml at mail.tsaitgaist.info (tsaitgaist)
Date: Mon, 31 Jan 2011 16:43:30 +0100
Subject: [ADM] osmocomSIM split?
In-Reply-To: <20110131151039.GG3786@prithivi.gnumonks.org>
References: <4D45EF32.3000602@mail.tsaitgaist.info>
	<20110131151039.GG3786@prithivi.gnumonks.org>
Message-ID: <4D46D8A2.2080300@mail.tsaitgaist.info>

hi Harald,

On 31.01.2011 16:10, Harald Welte wrote
>  
>> how about opening the sub-project osmocomSIM ?
> 
> what exactly do you mean by subproject?  Using a separate trac installation,
> mailing list, ...?  I think that might be a bit too much fragmentation.
> 
> But then, I'm not very clearly decided on this.  

I meant only a new address (sim.osmocom.org) and new "trac". So to have
a separate project page/wiki.
I don't see the need to have separate mailing-list,git,... for now
because the traffic is low.

thanks,
kevin



From b.alecu at yahoo.com  Mon Jan 31 04:49:49 2011
From: b.alecu at yahoo.com (Bogdan Alecu)
Date: Sun, 30 Jan 2011 20:49:49 -0800 (PST)
Subject: Reading / sending SMS
Message-ID: <633426.92120.qm@web46215.mail.sp1.yahoo.com>

Hello,
?
Has anyone managed to read (receive) or to send an SMS to Osmocom phone? I haven't found?any vty command that would allow this. Also if I send an SMS to Osmocom the phone starts a location update every 1 minute or so and on the phone that sent the message I get the non-delivery report. Could someone give me some tips on how to send/receive SMS?


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110130/523aaace/attachment.htm>

From holger at freyther.de  Mon Jan 31 08:19:14 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Mon, 31 Jan 2011 09:19:14 +0100
Subject: Reading / sending SMS
In-Reply-To: <633426.92120.qm@web46215.mail.sp1.yahoo.com>
References: <633426.92120.qm@web46215.mail.sp1.yahoo.com>
Message-ID: <4D467082.4070904@freyther.de>

On 01/31/2011 05:49 AM, Bogdan Alecu wrote:
> Hello,
>  
> Has anyone managed to read (receive) or to send an SMS to Osmocom phone? I
> haven't found any vty command that would allow this. Also if I send an SMS to
> Osmocom the phone starts a location update every 1 minute or so and on the
> phone that sent the message I get the non-delivery report. Could someone give
> me some tips on how to send/receive SMS?

Write the code, take the formating and parsing code from OpenBSC, put it into
libosmocore, reimplement the statemachine and SMSqueue from the MS point of view.

z.



From zecke at selfish.org  Mon Jan 31 12:54:09 2011
From: zecke at selfish.org (Holger Freyther)
Date: Mon, 31 Jan 2011 13:54:09 +0100
Subject: [PATCH] Two minor patches for the firmware
Message-ID: <4D46B0F1.6000001@selfish.org>

Hi laf0rge,

I was building the firmware with a GCC 4.5.2 created by Steve-m's script and
had to include limits.h for UINT_MAX. While reading the code I stumbled across
a typo... I think the patches can be picked to master as well.

holger

From zecke at selfish.org  Mon Jan 31 10:47:38 2011
From: zecke at selfish.org (Holger Hans Peter Freyther)
Date: Mon, 31 Jan 2011 11:47:38 +0100
Subject: [PATCH 1/2] vsprintf.c: Fix compilation by including limits.h
Message-ID: <mailman.20.1641743546.42824.baseband-devel@lists.osmocom.org>

The INT_MAX define was not known to this code with a
GCC 4.5.2/binutils 2.21/newlib 1.19.0 toolchain as
build for osmocomBB. Include limits.h to fix that.
---
 firmware/lib/vsprintf.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/firmware/lib/vsprintf.c b/firmware/lib/vsprintf.c
index 5da7c02..799eb78 100644
--- a/firmware/lib/vsprintf.c
+++ b/firmware/lib/vsprintf.c
@@ -17,6 +17,7 @@
  */
 
 #include <stdarg.h>
+#include <limits.h>
 #include <sys/types.h>
 #include <string.h>
 #include <asm/ctype.h>
-- 
1.7.3.5


--------------090305060903020708070409
Content-Type: text/x-patch;
 name="0002-typo-Fix-typo-transform-reqyests-to-requests.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename*0="0002-typo-Fix-typo-transform-reqyests-to-requests.patch"


From zecke at selfish.org  Mon Jan 31 10:49:47 2011
From: zecke at selfish.org (Holger Hans Peter Freyther)
Date: Mon, 31 Jan 2011 11:49:47 +0100
Subject: [PATCH 2/2] typo: Fix typo, transform reqyests to requests.
Message-ID: <mailman.21.1641743546.42824.baseband-devel@lists.osmocom.org>

---
 firmware/src/pcd/main_dumbreader.c    |    2 +-
 firmware/src/pcd/main_hid.c           |    2 +-
 firmware/src/pcd/main_presence.c      |    2 +-
 firmware/src/pcd/main_pwm.c           |    2 +-
 firmware/src/pcd/main_usb.c           |    2 +-
 firmware/src/picc/main_openpicc.c     |    2 +-
 firmware/src/simtrace/main_simtrace.c |    2 +-
 7 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/firmware/src/pcd/main_dumbreader.c b/firmware/src/pcd/main_dumbreader.c
index 62695f0..9c8dd13 100644
--- a/firmware/src/pcd/main_dumbreader.c
+++ b/firmware/src/pcd/main_dumbreader.c
@@ -88,7 +88,7 @@ void _main_func(void)
 	/* first we try to get rid of pending to-be-sent stuff */
 	usb_out_process();
 
-	/* next we deal with incoming reqyests from USB EP1 (OUT) */
+	/* next we deal with incoming requests from USB EP1 (OUT) */
 	usb_in_process();
 
 	rc632_unthrottle();
diff --git a/firmware/src/pcd/main_hid.c b/firmware/src/pcd/main_hid.c
index 9735c3d..c9d8fd1 100644
--- a/firmware/src/pcd/main_hid.c
+++ b/firmware/src/pcd/main_hid.c
@@ -50,7 +50,7 @@ void _main_func(void)
 	/* first we try to get rid of pending to-be-sent stuff */
 	usb_out_process();
 
-	/* next we deal with incoming reqyests from USB EP1 (OUT) */
+	/* next we deal with incoming requests from USB EP1 (OUT) */
 	usb_in_process();
 
 	/* try unthrottling sources since we now are [more] likely to
diff --git a/firmware/src/pcd/main_presence.c b/firmware/src/pcd/main_presence.c
index f61878f..4ead264 100644
--- a/firmware/src/pcd/main_presence.c
+++ b/firmware/src/pcd/main_presence.c
@@ -157,7 +157,7 @@ void _main_func(void)
 	
 	/* first we try to get rid of pending to-be-sent stuff */
 	usb_out_process();
-	/* next we deal with incoming reqyests from USB EP1 (OUT) */
+	/* next we deal with incoming requests from USB EP1 (OUT) */
 	usb_in_process();
 	rc632_unthrottle();
 }
diff --git a/firmware/src/pcd/main_pwm.c b/firmware/src/pcd/main_pwm.c
index 7db6b72..50fd363 100644
--- a/firmware/src/pcd/main_pwm.c
+++ b/firmware/src/pcd/main_pwm.c
@@ -262,7 +262,7 @@ void _main_func(void)
 	/* first we try to get rid of pending to-be-sent stuff */
 	usb_out_process();
 
-	/* next we deal with incoming reqyests from USB EP1 (OUT) */
+	/* next we deal with incoming requests from USB EP1 (OUT) */
 	usb_in_process();
 
 	/* try unthrottling sources since we now are [more] likely to
diff --git a/firmware/src/pcd/main_usb.c b/firmware/src/pcd/main_usb.c
index fcd3306..7892e77 100644
--- a/firmware/src/pcd/main_usb.c
+++ b/firmware/src/pcd/main_usb.c
@@ -35,7 +35,7 @@ void _main_func(void)
 	/* first we try to get rid of pending to-be-sent stuff */
 	usb_out_process();
 
-	/* next we deal with incoming reqyests from USB EP1 (OUT) */
+	/* next we deal with incoming requests from USB EP1 (OUT) */
 	usb_in_process();
 
 	/* try unthrottling sources since we now are [more] likely to
diff --git a/firmware/src/picc/main_openpicc.c b/firmware/src/picc/main_openpicc.c
index 74700f8..93ca4b6 100644
--- a/firmware/src/picc/main_openpicc.c
+++ b/firmware/src/picc/main_openpicc.c
@@ -251,7 +251,7 @@ void _main_func(void)
 	/* first we try to get rid of pending to-be-sent stuff */
 	usb_out_process();
 
-	/* next we deal with incoming reqyests from USB EP1 (OUT) */
+	/* next we deal with incoming requests from USB EP1 (OUT) */
 	usb_in_process();
 
 	udp_unthrottle();
diff --git a/firmware/src/simtrace/main_simtrace.c b/firmware/src/simtrace/main_simtrace.c
index 5e4302e..740d35d 100644
--- a/firmware/src/simtrace/main_simtrace.c
+++ b/firmware/src/simtrace/main_simtrace.c
@@ -95,7 +95,7 @@ void _main_func(void)
 	/* first we try to get rid of pending to-be-sent stuff */
 	usb_out_process();
 
-	/* next we deal with incoming reqyests from USB EP1 (OUT) */
+	/* next we deal with incoming requests from USB EP1 (OUT) */
 	usb_in_process();
 
 	udp_unthrottle();
-- 
1.7.3.5


--------------090305060903020708070409--



From laforge at gnumonks.org  Mon Jan 31 15:12:08 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Mon, 31 Jan 2011 18:12:08 +0300
Subject: [PATCH] Two minor patches for the firmware
In-Reply-To: <4D46B0F1.6000001@selfish.org>
References: <4D46B0F1.6000001@selfish.org>
Message-ID: <20110131151208.GH3786@prithivi.gnumonks.org>

Zecke,

On Mon, Jan 31, 2011 at 01:54:09PM +0100, Holger Freyther wrote:
 
> I was building the firmware with a GCC 4.5.2 created by Steve-m's script and
> had to include limits.h for UINT_MAX. While reading the code I stumbled across
> a typo... I think the patches can be picked to master as well.

sure, feel free to just commit them to master. no need to ask for such
trivial compile and typo fixes.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From zecke at selfish.org  Mon Jan 31 15:26:29 2011
From: zecke at selfish.org (Holger Freyther)
Date: Mon, 31 Jan 2011 16:26:29 +0100
Subject: [PATCH] Two minor patches for the firmware
In-Reply-To: <20110131151208.GH3786@prithivi.gnumonks.org>
References: <4D46B0F1.6000001@selfish.org>
	<20110131151208.GH3786@prithivi.gnumonks.org>
Message-ID: <4D46D4A5.2020103@selfish.org>

On 01/31/2011 04:12 PM, Harald Welte wrote:
> Zecke,

> 
> sure, feel free to just commit them to master. no need to ask for such
> trivial compile and typo fixes.

You will have to grant me access first.




From dmytrop at mail.ru  Mon Jan 31 14:10:27 2011
From: dmytrop at mail.ru (=?koi8-r?Q?=F0=C1=CE=C6=C9=CC=CF=D7_=E4=CD=C9=D4=D2=C9=CA?=)
Date: Mon, 31 Jan 2011 17:10:27 +0300
Subject: =?koi8-r?Q?What_I_am_doing_wrong=3F_G2?=
Message-ID: <E1PjuSZ-0007ve-00.dmytrop-mail-ru@f44.mail.ru>

Hi!
So, I decide to play with my G2 SciPhone
(My phone has configuration as follows: 512Mb (64MB) NAND + 32MB RAM)
But I could not run U-Boot...

The first step seems to be good. I run Osmocon and download "loader" to the phone.
I got "Running on mt62xx in environment mtkram HW_CODE = 0x6235" message.

After executing $ ./osmoload memload 0x500000 u-boot.bin
I can see progress and successfull download of u-boot.bin

First of all I tried to use u-boot from here
 http://downloads.qi-hardware.com/people/marcin/g2_uboot.bin (http://downloads.qi-hardware.com/people/marcin/g2_uboot.bin) 

Executing $ ./osmoload jump 0x500000 leads to... nothing. I can see black screen. That's all.

Also I compilled u-boot from git using toolchain kindly given by Andrew :-)

$ ./osmoload jump 0x500000 leads to gray screen after flashing white for a moment.
It looks like wrong LCD controller or driver.

So... The simple question. What I am doing wrong? :)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110131/0754db27/attachment.htm>

From squalyl at gmail.com  Mon Jan 31 16:25:32 2011
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Mon, 31 Jan 2011 17:25:32 +0100
Subject: thinking about the sim
Message-ID: <AANLkTikj38Yg5770nbxh9QnOYGC2Wze5eu5RjooGbGT6@mail.gmail.com>

Hello,

I was walking through trac while I came across this file:
http://bb.osmocom.org/trac/browser/src/host/layer23/src/common/sim.c

I see here:
183	/* send APDU to card reader */
184	static int sim_apdu_send(struct osmocom_ms *ms, uint8_t *data,
uint16_t length)
185	{
186	        LOGP(DSIM, LOGL_INFO, "sending APDU (class 0x%02x, ins 0x%02x)\n",
187	                data[0], data[1]);
188	        l1ctl_tx_sim_req(ms, data, length);
189	        return 0;
190	}

ohoh, that's hardcoded.

If we would like to have a software SIM, a SIM in a card reader on the
PC, or a real sim in the MS, I think this would this be the correct
place to plug a modular sim implementation.

I mean something that looks like:

struct osmocom_sim_ops {
int (*sim_apdu_init)(.....);
int (*sim_apdu_fini)(.....);
void (*sim_op_reset)(.....);
void (*sim_apdu_send)(.....);
void (*sim_response_callback)(.....);
};

void ms_register_sim_driver(struct osmocom_ms *ms, struct osmocom_sim_ops *ops);

this could be a part of struct osmocom_ms.

I would be easy to have 3 implementations:
-sim in the mobile, using the current calls 'l1ctl_tx_sim_req'
'l1ctl_tx_sim_conf'
-sim in PCSC using pcsclite or winscard, and a command-line option to
select the reader (by index, by name, or first reader with a card
inside for simple setups)
-virtual sim using pure software

What do you think about this?

Regards
Sebastien



From 246tnt at gmail.com  Mon Jan 31 17:36:14 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Mon, 31 Jan 2011 18:36:14 +0100
Subject: thinking about the sim
In-Reply-To: <AANLkTikj38Yg5770nbxh9QnOYGC2Wze5eu5RjooGbGT6@mail.gmail.com>
References: <AANLkTikj38Yg5770nbxh9QnOYGC2Wze5eu5RjooGbGT6@mail.gmail.com>
Message-ID: <AANLkTinV4DFFABhypUhbZ-0kz7int3PyaSrJT4t4cOQ0@mail.gmail.com>

Hi,

There was some plan to use BTSAP as an internal interface to allow
plugging of SIM interface .. not sure where it's at.

What's for sure is that what's in sylvain/testing is a hack, that's
why all that is not in master.

Cheers,

    Sylvain



From squalyl at gmail.com  Mon Jan 31 22:02:30 2011
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Mon, 31 Jan 2011 23:02:30 +0100
Subject: thinking about the sim
In-Reply-To: <AANLkTinV4DFFABhypUhbZ-0kz7int3PyaSrJT4t4cOQ0@mail.gmail.com>
References: <AANLkTikj38Yg5770nbxh9QnOYGC2Wze5eu5RjooGbGT6@mail.gmail.com>
	<AANLkTinV4DFFABhypUhbZ-0kz7int3PyaSrJT4t4cOQ0@mail.gmail.com>
Message-ID: <AANLkTinv=cAYAQxE23yj2G3Zeekuyxz=MaFq-_y5aCeZ@mail.gmail.com>

Not sure to understand what you mean.

src/host/layer23/src/common/sim.c is the same in both branches.

we also have a struct gsm_sim in struct osmocom_ms.

Would that struct be the place to store the sim callbacks?

Sebastien



From 246tnt at gmail.com  Mon Jan 31 23:11:38 2011
From: 246tnt at gmail.com (246tnt at gmail.com)
Date: Mon, 31 Jan 2011 23:11:38 +0000
Subject: thinking about the sim
In-Reply-To: <AANLkTinv=cAYAQxE23yj2G3Zeekuyxz=MaFq-_y5aCeZ@mail.gmail.com>
Message-ID: <0016e65aea84b59098049b2c8901@google.com>

On Jan 31, 2011 11:02pm, S?bastien Lorquet <squalyl at gmail.com> wrote:
> Not sure to understand what you mean.

> src/host/layer23/src/common/sim.c is the same in both branches.

I meant it was an idea discussed here ... I didn't say _any_ of it had ever  
been implemented ... anywhere.

See mailing list archives for details.

Cheers,

Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110131/bdc00cd1/attachment.htm>

From steve at steve-m.de  Mon Jan 31 23:36:01 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Tue, 01 Feb 2011 00:36:01 +0100
Subject: thinking about the sim
In-Reply-To: <AANLkTinV4DFFABhypUhbZ-0kz7int3PyaSrJT4t4cOQ0@mail.gmail.com>
References: <AANLkTikj38Yg5770nbxh9QnOYGC2Wze5eu5RjooGbGT6@mail.gmail.com>
	<AANLkTinV4DFFABhypUhbZ-0kz7int3PyaSrJT4t4cOQ0@mail.gmail.com>
Message-ID: <4D474761.3040505@steve-m.de>

Hi,

[just for completeness]

On 31.01.2011 18:36, Sylvain Munaut wrote:

> There was some plan to use BTSAP as an internal interface to allow
> plugging of SIM interface .. not sure where it's at.

Yeah, prom started to work on this some months back, the unfinished
target-side code is in the prom/simaccess branch.

Regards,
Steve