FYI
---------- Forwarded message ----------
From: Gregory Nutt <spudarnia(a)yahoo.com>
Date: Sun, 15 May 2011 07:52:18 -0700 (PDT)
Subject: Re: Fwd: RFC: RTOS for Calypso
To: Alan Carvalho de Assis <acassis(a)gmail.com>
Hi Alan,
I also notice that they are using a TI dual core, ARM7TDMI and C5 DSP.
I already have support for a TI chip like that (the C5471) and also
for an ARM9 with C5 DSP (DM320).
See http://focus.ti.com.cn/cn/lit/ml/sprt239/sprt239.pdf
I have a c5 DSP bridge driver somewhere around on my backup disks as
well. I never released it into NuttX because there was never any
need. Perhaps that could be useful now.
Somewhere I also have tools that will convert the TI proprietary
object files and logic to manage loading different programs into the
DSP. The bridge also supports communication channels to communicate
with the DSP.
Greg
Hi!
Is AreasOfWork in the wiki still up to date? I intend to work on the UI
(Sorry Dieter, GSM testset too expensive at the moment :( ) and want to
choose a RTOS. A small collection that I came across:
FreeRTOS
What is the problem?
TNKernel
http://www.tnkernel.com/tn_description.html
Scheduler, Mutexes, Queues, etc. available
strange (at least unfamiliar) API for memory
eCos
http://ecos.sourceware.org/about.html
many target MCUs but are their any other than ARM in BB chipsets?
powerful but complex (at least at first glance)
NUT/OS
http://www.ethernut.de/en/
minimalistic RTOS, easy to port
seems to have sound community
familiar APIs: malloc, fopen's devices, ...
cooperative multithreading: Is that OK? We still have IRQs for
realtime...
Since we seem to barely need an OS, a full-blown OS like eCos seems
excessive. For compatibility with MT6235 user space, malloc and fopen is
the right direction. Hence, my favourite is NUT/OS. In fact, I tried
porting it to calypso just for fun. With some wrappers, Osmocom's
platform files can be used. Only turns on the backlight and occasionally
outputs some bytes on the UART at the moment. However, I still call this
success. It took me just a day from knowing nothing about NUT/OS and
very little about calypso and ARM to do this. Seems promising in terms
of portability and documentation to me.
Open question: How much overhead can we afford, i.e., how much spare
time is there on the CPU? Does "Disable RTC interrupt as it causes lost
TDMA frames" (layer1/init.c) indicate issues? (Yes, sorry, haven't read
GSM specs yet...) If yes, is it reasonable to independently handle GSM
stuff with FIQ and only give IRQ to whatever OS we choose?
Regards,
Stefan
So any ideea where to look for the answer to the UPDATE_BINARY message?
Can I have a buffer overflow on UART RX? Is the buffer size selectable
somewhere?
--- On Wed, 5/4/11, eisencah eisenach <wbg_1000(a)yahoo.com> wrote:
From: eisencah eisenach <wbg_1000(a)yahoo.com>
Subject: Re: mobile - making a call
To: baseband-devel(a)lists.osmocom.org
Date: Wednesday, May 4, 2011, 4:58 PM
Done some more digging in the logs and it seems the sim state machine has locked earlier (when attaching to the network) while waiting for some response on UPDATE BINARY. Does this sounds familiar to anyone? :)
GOOD CASE:
[0;m[1;32m<0004> gsm48_mm.c:1557 AUTHENTICATION RESPONSE
[0;m[1;34m<0001> gsm48_rr.c:4904 (ms 1) Message 'RR_DATA_REQ' received in state dedicated
[0;m[1;34m<0001> gsm48_rr.c:235 Using and incrementing V(SD) = 0 (pdisc 5)
[0;m[0;35m<000e> sim.c:209 got new job: SIM_JOB_UPDATE_BINARY (handle=00000005)
[0;m[0;35m<000e> sim.c:241 SELECT (file=0x6f20)
[0;m[0;35m<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)
[0;m[0;35m<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)
[0;m[0;35m<000e> sim.c:949 command
successfull
[0;m[0;35m<000e> sim.c:571 GET RESPONSE (len=15)
[0;m[0;35m<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)
[0;m[0;35m<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)
[0;m[0;35m<000e> sim.c:949 command successfull
[0;m[0;35m<000e> sim.c:294 UPDATE BINARY (offset=0 len=9)
[0;m[0;35m<000e> sim.c:187 sending APDU (class 0xa0, ins 0xd6)
[0;m[0;35m<000e> sim.c:876 received APDU (len=0 sw1=0x90 sw2=0x00)
[0;m[0;35m<000e> sim.c:949 command successfull
[0;m[0;35m<000e> sim.c:151 sending result to callback function (type=0)
[0;m[1;34m<0001> gsm48_rr.c:4488 Indicated ta 0 (actual ta 0)
BAD CASE:
[0;m[1;32m<0004> gsm48_mm.c:1557 AUTHENTICATION RESPONSE
[0;m[1;34m<0001> gsm48_rr.c:4904 (ms 1) Message 'RR_DATA_REQ' received in state dedicated
[0;m[1;34m<0001> gsm48_rr.c:235 Using and
incrementing V(SD) = 0 (pdisc 5)
[0;m[0;35m<000e> sim.c:209 got new job: SIM_JOB_UPDATE_BINARY (handle=00000005)
[0;m[0;35m<000e> sim.c:241 SELECT (file=0x6f20)
[0;m[0;35m<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)
[0;m[0;35m<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)
[0;m[0;35m<000e> sim.c:949 command successfull
[0;m[0;35m<000e> sim.c:571 GET RESPONSE (len=15)
[0;m[0;35m<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)
[0;m[0;35m<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)
[0;m[0;35m<000e> sim.c:949 command successfull
[0;m[0;35m<000e> sim.c:294 UPDATE BINARY (offset=0 len=9)
[0;m[0;35m<000e> sim.c:187 sending APDU (class 0xa0, ins 0xd6)
[0;m[1;32m<0004> gsm48_mm.c:3695 (ms 1) Received 'RR_DATA_IND' from RR in state location updating initiated
--- On Wed, 5/4/11, Harald
Welte <laforge(a)gnumonks.org> wrote:
From: Harald Welte <laforge(a)gnumonks.org>
Subject: Re: mobile - making a call
To: "eisencah eisenach" <wbg_1000(a)yahoo.com>
Date: Wednesday, May 4, 2011, 11:59 AM
On Tue, May 03, 2011 at 03:02:58AM -0700, eisencah eisenach wrote:
> So is as if the message for the sim job doesn't get pulled from the
> queue, "got new job: SIM_JOB_RUN_GSM_ALGO " never appears. Must say
> the computer I use osmocom on is not exactly a rocket :) (is a 500Mhz
> celeron with ubuntu 6.10) , and It gets slowed down when running the
> hole thing. Can that be the cause? Mihai.
The L1CTL protocol goes through a unix domain socket, and you can trace
it in either osmocon or in the mobile program itself. It should
be
relatively easy to detect if the RUN_GSM_ALGO is transmitted by mobile,
or if it is lost, where it is lost.
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi,
I have a problem with the DP-L10.
The upload the firmware in the phone is not succesfull.
I have made following steps:
- change the UART number in the two header files
- compile the source
- connected the phone with laptop
- run the command "./host/osmocon/osmocon -p /dev/ttyUSB0 -m romload
./target/firmware/board/pirelli_dpl10/layer1.highram.bin"
- put the accu in the mobile phone
the upload the firmware start and the last message from osmocon is:
handle_write_block(): 64 bytes (1024/1024)
handle_write_block(): Block 51 finished
Finished, sent 51 blocks in total
Received block ack from phone
Sending checksum: 0x55
I have follow message expected:
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!
I see not the error.
Can you please a idea give.
Marco
Hi,
when compiling the firmware I get the following error:
make[2]: Entering directory
`/home/hoffmaje/proseminar/install/osmocom-bb/src/target/firmware'
LD board/mt62xx/loader_mtk.mtkram.elf
arm-elf-ld: region LRAM is full (board/mt62xx/loader_mtk.mtkram.elf
section .rodata)
arm-elf-ld: region LRAM is full (board/mt62xx/loader_mtk.mtkram.elf
section .rodata)
I used a tool-chain mentioned in a post from 18. January 2011:
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
I read the PreliminaryRequirements
<http://www.osmocom.org/trac/wiki/PreliminaryRequirements>, the archives
and I did a google search; I would be even glad just to understand what
this error is about.
Thanks for your help,
Jens
Hello Gianni,
On Fri, 13 May 2011 11:41:35 +0100, "Gianni Tedesco" <gianni(a)scaramanga.co.uk> wrote:
>
> Any idea of model numbers? The ones I've looked at have been > $1,000
> and only do calls, not SMS for example.
The Racal 6103E can do SMS and sometimes is available for less than
$US 500 (a few cheap ones were sold in the UK a while ago). Be aware
of the 6103G or the "Anite" variant, they cannot be used "standalone".
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hi.
I'm trying to follow the logic described in app_ccch_scan to send RACH bursts to my
openbts.
First 2-2 goes fine but after that I got constant errors - see below.
It looks like after I've sent couple of packets something got corrupted in L1.
How can I debug this and understand what causing all the errors?
LOG:
<0001> app_rach_send.c:227 registering signal handler...
<0001> app_rach_send.c:229 resetting L1...
<0001> app_rach_send.c:231 L3 init...
<0001> app_rach_send.c:190 requesting FBSB from L1...
<0001> app_rach_send.c:200 unhandled callback 1 <S_L1CTL_FBSB_RESP> fired...
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:73 SI2 on the wrong TC: 0
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:75 SI3 on the wrong TC: 0
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:75 SI3 on the wrong TC: 0
<0001> app_rach_send.c:200 unhandled callback 5 <S_L1CTL_CCCH_MODE_CONF> fired...
<0001> app_rach_send.c:200 unhandled callback 5 <S_L1CTL_CCCH_MODE_CONF> fired...
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:86 SI4 on the wrong TC: 0
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:86 SI4 on the wrong TC: 0
...
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:86 SI4 on the wrong TC: 0
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:70 SI1 received.
<0001> app_rach_send.c:127 sending RACH #0 on ARFCN 21...
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:127 sending RACH #1 on ARFCN 21...
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:127 sending RACH #2 on ARFCN 21...
<0000> rslms.c:136 unknown RSLms msg_discr 0x0c
<0000> rslms.c:136 unknown RSLms msg_discr 0x0c
<0000> rslms.c:136 unknown RSLms msg_discr 0x0c
<000b> l1ctl.c:210 Dropping frame with 80 bit errors
<000b> l1ctl.c:210 Dropping frame with 80 bit errors
<000b> l1ctl.c:210 Dropping frame with 80 bit errors
<000b> l1ctl.c:210 Dropping frame with 59 bit errors
<000b> l1ctl.c:210 Dropping frame with 59 bit errors
<000b> l1ctl.c:210 Dropping frame with 59 bit errors
<000b> l1ctl.c:210 Dropping frame with 58 bit errors
<000b> l1ctl.c:210 Dropping frame with 58 bit errors
<000b> l1ctl.c:210 Dropping frame with 58 bit errors
<000b> l1ctl.c:210 Dropping frame with 61 bit errors
<000b> l1ctl.c:210 Dropping frame with 61 bit errors
<000b> l1ctl.c:210 Dropping frame with 61 bit errors
<000b> l1ctl.c:210 Dropping frame with 62 bit errors
<000b> l1ctl.c:210 Dropping frame with 60 bit errors
<000b> l1ctl.c:210 Dropping frame with 61 bit errors
<000b> l1ctl.c:210 Dropping frame with 61 bit errors
Hi all!
As some of you already know, Holger and I have recently started a new
company called "sysmocom - systems for mobile communications GmbH".
The process of establishing the new company has now formally concluded.
Before some rumours start to spread, we would like to clarify some
points and make sure there is mutual understanding between the Osmocom
community and the sysmocom company.
sysmocom is intended to provide commercial offerings related to the
Osmocom projects. This is not entirely new. Especially on the network
side, people like Holger and I have been doing quite a lot of paid
development to bring those projects forward. We would not have many of
the features we have today, if it wasn't for customers who actually pay
us for development of OpenBSC, OsmoBSC, OsmoSGSN and the various side
projects more targetted at a real network operator like cellmgr-ng,
bsc-nat, gb_proxy - just to name a few.
However, this has always only been freelancing development of Software.
With sysmocom, we want to go one step further and work on hardware
products related to the various Free Software projects. Right now I
don't want to talk too much about unfinished products, but we are
working towards an inexpensive BTS product, we are funding the
prototypes for Osmocom SIMtrace, and we will likely also see stuff like
OpenBSC appliances.
Given our past involvement and exposure into other projects that share
a split Free Software / business set-up, we think we understand very
well where potential issues of conflict between the two sides may be.
Let me make some more clarification what this is not about:
* sysmocom is not about creating proprietary derivates of Osmocom
software. We work on Free Software which is publicly available under
OSI approved and FSF endorsed licenses. We may offer proprietary
hardware and sometimes software - but those are independent projects
from existing Osmocom software.
* we specifically will not have a public and a non-public version of
the same program with differences in features.
* sysmocom is not a VC-funded startup. It's a very small company
run out of personal funds with no intention to take external funding
or grow rapidly. Nobody but Holger and I determine where it goes
and what it does.
* sysmocom does not hold any copyright on the Free Software projects.
The copyrights stay distributed with the major authors such as Holger,
Onwaves, Sylvain, Dieter, Andreas and myself. None of the others have
any affiliation with sysmocom. I have (personally, unrelated to
sysmocom) asked some of the smaller contributors for a copyright
transfer to make sure we could do the AGPLv3 transition, or future
re-licensing decisions without having to ask dozens and dozens of
people. sysmocom does not seek to control the Free Software projects.
* we will maintain a strict separation between the community side of
things and the business side. Unlike some other popular projects, we
will not end up in a situation where the osmocom.org websites will be
full of advertisements and hidden links that lure you on the company
website.
* we will keep a strict separation of naming. Osmocom is for the FOSS
projects, sysmocom for the business. The company will use the term
"Osmocom" only in descriptive context, not as a product name, brand
or for advertisement.
If you do have any concerns, please feel free to share them. However,
I'd like to avoid cross-posting them throguh different mailing lists.
Please follow-up-to openbsc(a)lists.osmocom.org
Regards,
Harald
--
- Harald Welte <hwelte(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Schivelbeiner Str. 5
* 10439 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte
Hi,
It seems like a BTS is required in order to really debug anything one
develops with osmocombb. I'm still looking at implementing SMS. However
the only off-the-shelf option seems to be USRP which is about $1,000
right? Is this going to become a very expensive hobby or are there
cheaper options here?
Is there a way to bypass L1CTL on the phone and feed the data in to,
say, openBTS? If not, it would seem useful to hack such a thing up...
Gianni
Hi all!
[This message is cross-posted to many lists, please be careful when
replying to it! Think twice if your respones really matters to all
those projects...]
In order to do some better planning for our Camp activities this summer,
I would like to request all people who intend to participate in the
radio village to add themselves to the wiki:
https://events.ccc.de/camp/2011/wiki/index.php/RadioVillage
The list of citizens is auto-generated if you use Person template like
I have done in my user page at
https://events.ccc.de/camp/2011/wiki/index.php/User:LaForge
The large main tent is not really intended as a place to sleep, but more
like a place where we set up our gear and work on the various projects,
similar to what happened at HAR.
Thanks in advance!
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
hello,
I am not quite sure if this is the right place to ask, so sorry in
advance for spamming ir i'm in the wrong place.
I have build and run osmocom on my C123. I am using it for a university
project and we try to read parameters from surrounding BTS. The final
goal will be to separate real bts from imsi catchers.
So my question is, can I use the osmocom library to gather some data
from surrounding BTS? Are there some example programs? Would anyone know
a good way to read the SIM data from the connected C123?
Thanks in advance!
Cheers
Tom
----------------------------------------------------------------------------
Short example scenario: A very obvious catcher fault would be not having
set the regional code or having set a wrong regional code. So it would
theoretically be possible to read the regional code from the own SIM
card and the regional code of the transmitting BTS and compare those.
Hi list,
while studing burst_ind (I know that burst_ind must be used in a own controlled
network) i see that one SDCCH for a specific operator has been shared by more
than one MS (different TMSIs), some MS use for SMS other use for calls. Is that
an interpratation error (due the fact of using burst_ind in real networks) or
that could be possible? i didn't find explanations on sepcs.
TIA
Hi all!
I think now that the namespace issues in libosmocore have been resolved,
we seriously have to think of maintaining a stable API and ABI. This
allows us to have truly independent library and application releases,
and the dynamic linker library versioning support should ensure
compatibility.
So please think twice about any modifying libosmocore. It is safe to
add new functions, but we cannot change the prototypes (number of
arguments) for existing functions.
As soon as new functions are introduced, we should increment the library
interface number.
For more information, see
http://www.gnu.org/software/libtool/manual/libtool.html#Versioning
especially the rules in Chapter 7.3:
# If the library source code has changed at all since the last update,
then increment revision (‘c:r:a’ becomes ‘c:r+1:a’).
# If any interfaces have been added, removed, or changed since the last
update, increment current, and set revision to 0.
# If any interfaces have been added since the last public release, then
increment age.
# If any interfaces have been removed or changed since the last public
release, then set age to 0.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi all,
JFYI: For a couple of days, *.osmocom.org is reachable via IPv6.
I've had native IPv6 at my co-located servers for more than 10 years,
but somehow never configured it for the virtual machines like
*.osmocom.org - this is now fixed.
If you encounter any difficulties, please let me know.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Thanks Sylvain, Harald and Alex,
>
>Can you please verify this? If you do have a listener on the UDP port
>and still get write errors, we need to fix something in 'mobile'.
>Otherwise, no need for that...
>
I was using nc -u -l 4729 > /dev/null I added the -p option and tried again:
as you said this solved the problem!!!
Thanks again,
Loretta
Hi all!
Since Kevin and I are trying to re-vitalize the simtrace project, I have
decided to create a new simtrace(a)lists.osmocom.org mailing list
dedicated to this project.
Yesterday at a meeting we have discussed
* to use a digitally-controlled analog switch to select sniffing /
emulation mode (i.e. to do a software-controlled 'cut' the electrical
connection between the SIM card and the phone)
* to add a header next to the USB socket so we can attach a battery pack
for autonomous operation
* to add a SPI NOR flash (for storage of data in autonomous operation)
* to not care about 1.8V-only SIM cards and make it a 3.3V-only device
We expect to do a bit more schematics review and component placement +
routing as well as a prototype PCB in the next couple of weeks.
Kevin is in charge of the hardware prototype, while I will look at the
firmware side as well as provide funding for the PCB manufacturing and
prototype components.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Thanks Alex,
I actually played a bit with the code and found out that exactly half of the
times the write() call in the function
gsmtap_fd_cb() (gsmtap_util.c) fails because of EAGAIN or EWOULDBLOCK.
I implemented a retransmission in this case and this solve the problem: all
the gsmtap are successfully sent and received.
Though, I suspect is impacting negatively on the rest of the mobile program.
Anyway I do not have a real evidence of this only the fact that after the
modification I have never had a successful location update.
Do you think this is plausible? am I degrading the overall performances when
trying to get all the gsmtap? Can i solve this problem?
Thanks Alex and list,
Loretta
>----Messaggio originale----
>Da: vamposdecampos(a)gmail.com
>Data: 6-mag-2011 8.35
>A: "screaming-pain(a)libero.it"<screaming-pain(a)libero.it>
>Cc: <baseband-devel(a)lists.osmocom.org>
>Ogg: Re: lost dump ?!?!?
>
>On Thu, May 5, 2011 at 5:28 PM, screaming-pain(a)libero.it
><screaming-pain(a)libero.it> wrote:
>> Hi list,
>>
>> I know I am very slow in understanding osmocom-bb, anyway this is just a
quick
>> question.
>> Is it possible that some of the gsmtap messages are getting lost?
>> For example I can see a LOCATION UPDATE and a LOCATION ACCEPT from the
>> 'mobile' application log but there aren't the corresponding messages in the
>> wireshark capture,
>> though this does not always happen, I mean I had captures of location
updates
>> other times, this is why I am wondering if they are getting lost and what
it
>> does depend on.
>> for what I understood the gsmtap functions utilities are in gsmtap_util.c
and
>> the one to send the messages on the socket is called by l1ctl.c am I right?
>> Can you help me understanding why I cannot see all the messages?
>>
>> thank you in advance
>> Loretta
>
>Hi,
>
>I've had this happen to me when I wasn't receiving the gsmtap packets.
>
>Specifically, I had the gsmtap packets sent over the network (i.e.,
>non-localhost). There was no UDP listener on the receiving end, such
>that ICMP port-unreachable replies were being sent back. It would
>appear that this causes the sender's kernel to snub some of the
>outgoing packets. I don't know if the same happens on localhost.
>
>If this is your case, you can try "iptables -I INPUT -p udp -d 4729 -j
>DROP", or something like "nc -l -u 4729 > /dev/null".
>
>Cheers,
>Alex
>
>
Hi list,
I know I am very slow in understanding osmocom-bb, anyway this is just a quick
question.
Is it possible that some of the gsmtap messages are getting lost?
For example I can see a LOCATION UPDATE and a LOCATION ACCEPT from the
'mobile' application log but there aren't the corresponding messages in the
wireshark capture,
though this does not always happen, I mean I had captures of location updates
other times, this is why I am wondering if they are getting lost and what it
does depend on.
for what I understood the gsmtap functions utilities are in gsmtap_util.c and
the one to send the messages on the socket is called by l1ctl.c am I right?
Can you help me understanding why I cannot see all the messages?
thank you in advance
Loretta
Some questions about Sylvain testing branch:
why is not merged SIMreader into master branch?
is planned for mobile aplication to support SMS (sending/receiving)?
Thank you,
ArMaND VanHell
I'm looking for somebody in India who has a deep GSM interest and who
is preferrably a student. If you're quick, I have a free giveaway for
you.
Please simply e-mail me, details will follow.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Done some more digging in the logs and it seems the sim state machine has locked earlier (when attaching to the network) while waiting for some response on UPDATE BINARY. Does this sounds familiar to anyone? :)
GOOD CASE:
[0;m[1;32m<0004> gsm48_mm.c:1557 AUTHENTICATION RESPONSE
[0;m[1;34m<0001> gsm48_rr.c:4904 (ms 1) Message 'RR_DATA_REQ' received in state dedicated
[0;m[1;34m<0001> gsm48_rr.c:235 Using and incrementing V(SD) = 0 (pdisc 5)
[0;m[0;35m<000e> sim.c:209 got new job: SIM_JOB_UPDATE_BINARY (handle=00000005)
[0;m[0;35m<000e> sim.c:241 SELECT (file=0x6f20)
[0;m[0;35m<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)
[0;m[0;35m<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)
[0;m[0;35m<000e> sim.c:949 command successfull
[0;m[0;35m<000e> sim.c:571 GET RESPONSE (len=15)
[0;m[0;35m<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)
[0;m[0;35m<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)
[0;m[0;35m<000e> sim.c:949 command successfull
[0;m[0;35m<000e> sim.c:294 UPDATE BINARY (offset=0 len=9)
[0;m[0;35m<000e> sim.c:187 sending APDU (class 0xa0, ins 0xd6)
[0;m[0;35m<000e> sim.c:876 received APDU (len=0 sw1=0x90 sw2=0x00)
[0;m[0;35m<000e> sim.c:949 command successfull
[0;m[0;35m<000e> sim.c:151 sending result to callback function (type=0)
[0;m[1;34m<0001> gsm48_rr.c:4488 Indicated ta 0 (actual ta 0)
BAD CASE:
[0;m[1;32m<0004> gsm48_mm.c:1557 AUTHENTICATION RESPONSE
[0;m[1;34m<0001> gsm48_rr.c:4904 (ms 1) Message 'RR_DATA_REQ' received in state dedicated
[0;m[1;34m<0001> gsm48_rr.c:235 Using and incrementing V(SD) = 0 (pdisc 5)
[0;m[0;35m<000e> sim.c:209 got new job: SIM_JOB_UPDATE_BINARY (handle=00000005)
[0;m[0;35m<000e> sim.c:241 SELECT (file=0x6f20)
[0;m[0;35m<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)
[0;m[0;35m<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)
[0;m[0;35m<000e> sim.c:949 command successfull
[0;m[0;35m<000e> sim.c:571 GET RESPONSE (len=15)
[0;m[0;35m<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)
[0;m[0;35m<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)
[0;m[0;35m<000e> sim.c:949 command successfull
[0;m[0;35m<000e> sim.c:294 UPDATE BINARY (offset=0 len=9)
[0;m[0;35m<000e> sim.c:187 sending APDU (class 0xa0, ins 0xd6)
[0;m[1;32m<0004> gsm48_mm.c:3695 (ms 1) Received 'RR_DATA_IND' from RR in state location updating initiated
--- On Wed, 5/4/11, Harald Welte <laforge(a)gnumonks.org> wrote:
From: Harald Welte <laforge(a)gnumonks.org>
Subject: Re: mobile - making a call
To: "eisencah eisenach" <wbg_1000(a)yahoo.com>
Date: Wednesday, May 4, 2011, 11:59 AM
On Tue, May 03, 2011 at 03:02:58AM -0700, eisencah eisenach wrote:
> So is as if the message for the sim job doesn't get pulled from the
> queue, "got new job: SIM_JOB_RUN_GSM_ALGO " never appears. Must say
> the computer I use osmocom on is not exactly a rocket :) (is a 500Mhz
> celeron with ubuntu 6.10) , and It gets slowed down when running the
> hole thing. Can that be the cause? Mihai.
The L1CTL protocol goes through a unix domain socket, and you can trace
it in either osmocon or in the mobile program itself. It should be
relatively easy to detect if the RUN_GSM_ALGO is transmitted by mobile,
or if it is lost, where it is lost.
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
Some months ago, Richard Stallman (rms) has contacted me regarding
my work with OsmocomBB. As it is not a big surprise to us, he is
really interested in the project. After all, it would be the first
mobile phone that he himself would be able to use, given that there
is no proprietary software on the baseband anymore. And of course
it would enable loads of other freedom-loving users to finally have
an alternative to the proprietary telephony world.
Here in Morocco, I've had some further discussion on the topic face to
face with him, and he is sort of unhappy with the fact that nobody is
working on making an actual self-contained phone (no matter how simple
or limited in features) that can be used by a regular user as 'just a
phone'.
I explained to him that our motivation is mostly a different one
(research, security, GSM-attached PBX, etc.) and thus there is no
intrinsic motivation to work towards a more user-friendly version.
Furthermore, we are system level hackers with an interest in
communications, not particularly people who like to work on a UI
or usability.
So we agreed to make a public call for volunteers to wokr on that aspect
of the phone. I understand this will likely cause some effort on our
side (fencing off poeple who don't have the neccessary skills,
integrating such code, finally deciding on a RTOS to use, etc.).
However, I more or less see it as my (and our?) duty to realize the
potential of our protocol stack and baseband firmware. Next to all
our own self-motivated personal interestes, there is a bigger cause
that we can help along: Free Software based telephony. So the least
we can do is to try to find somebody who can work on that part, and
help developer[s] to interact with our code.
It's the question of whether we are just hacking away on our personal
little pet, or if we try to achieve something bigger.
I've already drafted a version of the 'job description' and with some
luck the FSF will soon publish it, reaching out beyond our existing
small Osmocom community.
e will try to draft a similar job description related to MS-side GPRS
support (L1, RLC/MAC, ..). That would be yet another area where we
would appreciate some contribution, and which eventually be important
beyond our existing voice telephony capabilities.
Regards,
Harald
- --
- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iD8DBQFNvs0JXaXGVTD0i/8RArkDAKCONleE9HJ2i1jp7L/XnMY0YweIjACbB8Lz
puH7X4lkqY8AqzU0SAlOAxM=
=Cmo8
-----END PGP SIGNATURE-----
Fixes a couple of warnings like this:
In file included from ../../shared/libosmocore/include/osmocom/core/msgb.h:24:0,
from include/comm/sercomm.h:6,
from apps/loader/main.c:41:
../../shared/libosmocore/include/osmocom/core/linuxlist.h: In function 'prefetch':
../../shared/libosmocore/include/osmocom/core/linuxlist.h:10:41: warning: unused parameter 'x'
Signed-off-by: Wolfram Sang <wolfram(a)the-dreams.de>
---
.../libosmocore/include/osmocom/core/linuxlist.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/shared/libosmocore/include/osmocom/core/linuxlist.h b/src/shared/libosmocore/include/osmocom/core/linuxlist.h
index fb99c5e..ff2c491 100644
--- a/src/shared/libosmocore/include/osmocom/core/linuxlist.h
+++ b/src/shared/libosmocore/include/osmocom/core/linuxlist.h
@@ -7,7 +7,7 @@
#define inline __inline__
#endif
-static inline void prefetch(const void *x) {;}
+static inline void prefetch(__attribute__((unused)) const void *x) {;}
/**
* container_of - cast a member of a structure out to the containing structure
--
1.7.2.5