Hello Harald,
While running ./go.sh i come across below error there no one on
airprob lis now a days plz help why i'm getting that error
========
root@ubuntu:/home/xx/6jan/airprobe/gsm-tvoid/src/python# ./go.sh
GSMSP_940.8Mhz_118.cfile
go.sh <file.cfile> [decim==112]
% offset = 0.0 clock = 64000000.0
Reading data from: GSMSP_940.8Mhz_118.cfile
>>> gr_fir_ccc: using SSE
>>> gr_fir_ccf: using SSE
(python:7893): Gtk-CRITICAL **: gtk_window_resize: assertion `width >
0' failed <<<<<<<<<<<<<<<<
=======
Kind Regards,
I'm having this question about NCC allocation. Is this unique for an operator inside a country? And how it goes if you travel abroad ? (Will the phone look for a network with the same NCC at the begining?)
After that it will look at sysinfo and the other stuff but I was wondering how it goes at power up?
Thanks.
Hi.
In its current stage osmocom makes full use of CCCH-CONF and BS-AG-BLK_RES fields of CCCH description? If a block is reserved for access grant it won't be used on paging?
Is there anyway of calling "gsm48_sysinfo_dump" to print on the console?
Cheers,
Mihai.
> But it is also possible to have two layer 3 messages in the same
LAPDm frame (one ending and one starting for example)?
no, you can't! it could be possible, since there is a length field in
every layer 2 frame, but there is nothing in the specs about it.
Hi all,
Sorry for bothering with another compiling problem.
I had the following error while compiling osmocom-bb:
configure:3246: arm-elf-gcc -Os -ffunction-sections -I/home/loretta/osmocom-
bb/src/target/firmware/include -nostartfiles -nodefaultlibs conftest.c >&5
conftest.c: In function `main':
conftest.c:15: warning: initialization makes pointer from integer without a
cast
/home/loretta/install/gnuarm-3.4.3/bin/../lib/gcc/arm-elf/3.4.3/../../../..
/arm-elf/bin/ld: warning: cannot find entry symbol _start; defaulting to
00008000
/tmp/ccgIuxoW.o(.text.main+0x14): In function `main':
: undefined reference to `fopen'
/tmp/ccgIuxoW.o(.text.main+0x1c): In function `main':
: undefined reference to `ferror'
/tmp/ccgIuxoW.o(.text.main+0x30): In function `main':
: undefined reference to `fclose'
collect2: ld returned 1 exit status
configure:3250: $? = 1
configure:3287: result:
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "libosmocore"
| #define PACKAGE_TARNAME "libosmocore"
| #define PACKAGE_VERSION "UNKNOWN"
| #define PACKAGE_STRING "libosmocore UNKNOWN"
| #define PACKAGE_BUGREPORT "openbsc-devel(a)lists.openbsc.org"
| #define PACKAGE_URL ""
| #define PACKAGE "libosmocore"
| #define VERSION "UNKNOWN"
| /* end confdefs.h. */
| #include <stdio.h>
| int
| main ()
| {
| FILE *f = fopen ("conftest.out", "w");
| return ferror (f) || fclose (f) != 0;
|
| ;
| return 0;
| }
after hours of trying to understand how to fix this, I figured out that
without the option -nodefaultlibs everything run smoothly.
Now, the problem is that I do not understand much of what is going on and I
wonder, do I need that option and hence should look for a different way of
fixing the problem?
Thanks for your help,
Loretta
Thanks.
But it is also possible to have two layer 3 messages in the same LAPDm frame (one ending and one starting for example)?
Cheers.
--- On Fri, 4/1/11, Andreas.Eversberg <Andreas.Eversberg(a)versatel.de> wrote:
From: Andreas.Eversberg <Andreas.Eversberg(a)versatel.de>
Subject: AW: layer3 messages questions
To: "eisencah eisenach" <wbg_1000(a)yahoo.com>, baseband-devel(a)lists.osmocom.org
Date: Friday, April 1, 2011, 12:13 PM
hi,
> One question : are there any layer 3 messages that would span across
multiple LAPDm frames? Or are they chosen such that this
> never happens?
example: in case you dial a long number, the complete L2 message may
exceed 23 bytes. in this case the
message is split into multiple
messages. this is supported by osmocom/lapdm.
Hi everyone.
One question : are there any layer 3 messages that would span across multiple LAPDm frames? Or are they chosen such that this never happens?
Thanks,
Mihai.
hi,
> One question : are there any layer 3 messages that would span across
multiple LAPDm frames? Or are they chosen such that this
> never happens?
example: in case you dial a long number, the complete L2 message may
exceed 23 bytes. in this case the message is split into multiple
messages. this is supported by osmocom/lapdm.
