hi list,
I would like to run the c123(s) without the LI battery with direct
5V power supply only. Without battery the c123 display just blinks
and no PROMPT1 can be received.
Anyone knows a way how this might work ? (- like bypass or bridge
this 3 pin battery pins)
thanks for your help
(sorry for the lame add)
--
Schon gehört? GMX hat einen genialen Phishing-Filter in die
Toolbar eingebaut! http://www.gmx.net/de/go/toolbar
I was wondering how to transmit and receive using layer1. I have
been reading some of the gsm specs. I have been looking around in the
source code a lot, and there many functions that are used for transmit
and receive. Which are the right few to use? Is there any way to send
a text message to a different phone by simulating a base station? Do I
need two phones or one phone to transmit and receive as a base station?
Is there any way to make a half duplex base station on a BCCH channel
with only one subscriber phone at a time, and what would that entail
code-wise? Would it be legal to run a very low power base station in
the USA on a different unused cellular band/frequency? I have a lot of
free time since I do school at home and I could probably help develop
some new parts of the osmocom-bb project if you want me to. I know C,
some x86 assembly, and a few other languages. I have also had practice
fixing compile-time errors, and bugs in code. I apologize if this is
too many questions. You don't have to answer them all if you don't want to.
Thank you for helping,
Calvin E. Balke
Hello everyone,
Sorry to bother you all.I am a student and desire to become researchers like
you all out there.
While building the project osmocom I got an unique error which no-one in the
mailing lists have got yet.It says that the header file 'signal.h' is
missing in osmocore.I am just uanble to figure it how it is unable to
include the header file. please help.Also I am attaching the file of
compilation.By the way I am using the gnuarm-3.4.3 as shown on the
osmocom-bb website.
Hello everyone,
Sorry to bother you all.I am a student and desire to become researchers like
you all out there.
While building the project osmocom I got an unique error which no-one in the
mailing lists have got yet.It says that the header file 'signal.h' is
missing in osmocore.I am just uanble to figure it how it is unable to
include the header file. please help.By the way I am using the gnuarm-3.4.3
as shown on the osmocom-bb website.
roy@roy:~/osmocom-bb$ cd src
roy@roy:~/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="arm-elf-gcc" CFLAGS="-Os -ffunction-sections
-I/home/roy/osmocom-bb/src/target/firmware/include -nostartfiles
-nodefaultlibs"
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... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for arm-elf-linux-gcc... 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 arm-elf-gcc accepts -g... yes
checking for arm-elf-gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of arm-elf-gcc... gcc3
checking build system type... i686-pc-linux-gnu
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 arm-elf-gcc...
/home/roy/osmocom-bb/gnuarm-3.4.3/arm-elf/bin/ld
checking if the linker
(/home/roy/osmocom-bb/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/roy/osmocom-bb/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 arm-elf-gcc
object... failed
checking how to run the C preprocessor... 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 arm-elf-gcc supports -fno-rtti -fno-exceptions... no
checking for arm-elf-gcc option to produce PIC... -fPIC -DPIC
checking if arm-elf-gcc PIC flag -fPIC -DPIC works... yes
checking if arm-elf-gcc static flag -static works... yes
checking if arm-elf-gcc supports -c -o file.o... yes
checking if arm-elf-gcc supports -c -o file.o... (cached) yes
checking whether the arm-elf-gcc linker
(/home/roy/osmocom-bb/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 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 tests/smscb/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]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
make all-recursive
make[2]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
Making all in include
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'
Making all in osmocom
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
Making all in codec
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec'
Making all in crypt
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt'
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
Making all in osmocore
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
Making all in protocol
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol'
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'
Making all in src
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'
Making all in .
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'
Making all in vty
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty'
Making all in codec
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'
Making all in tests
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
make[2]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
make[1]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
cd shared/libosmocore/build-host && ../configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for gcc... 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... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-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 gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) 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 /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... 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... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
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... yes
checking whether to build static libraries... yes
checking for ANSI C header files... (cached) yes
checking execinfo.h usability... yes
checking execinfo.h presence... yes
checking for execinfo.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking if gcc supports -fvisibility=hidden... yes
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 tests/smscb/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-host && make
make[1]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
make all-recursive
make[2]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
Making all in include
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include'
Making all in osmocom
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom'
Making all in vty
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/vty'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/vty'
Making all in codec
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/codec'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/codec'
Making all in crypt
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/crypt'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/crypt'
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom'
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom'
Making all in osmocore
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
Making all in protocol
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol'
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include'
Making all in src
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src'
Making all in .
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src'
Making all in vty
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/vty'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/vty'
Making all in codec
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/codec'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/codec'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src'
Making all in tests
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests'
Making all in timer
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/timer'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/timer'
Making all in sms
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/sms'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/sms'
Making all in ussd
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/ussd'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/ussd'
Making all in smscb
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/smscb'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/smscb'
Making all in msgfile
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/msgfile'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/msgfile'
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests'
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
make[2]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
make[1]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
make -C host/layer23
make[1]: Entering directory `/home/roy/osmocom-bb/src/host/layer23'
Making all in include
make[2]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include'
Making all in osmocom
make[3]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom'
Making all in bb
make[4]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb'
Making all in common
make[5]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/common'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/common'
Making all in misc
make[5]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/misc'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/misc'
Making all in mobile
make[5]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/mobile'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/mobile'
make[5]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb'
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb'
make[4]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom'
make[3]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include'
make[2]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include'
Making all in src
make[2]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/src'
Making all in common
make[3]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/src/common'
CC l1ctl.o
l1ctl.c:33: fatal error: osmocore/signal.h: No such file or directory
compilation terminated.
make[3]: *** [l1ctl.o] Error 1
make[3]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/src/common'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23'
make: *** [host/layer23/layer23] Error 2
hi calvin,
> I am having trouble getting any signal at all. the signal is around
-111
> dBm on every channel with the rf gain set on high. The original
as harald said, it seems that your phone uses 850 and 1900mhz bands. the
filters inside only pass these frequencies. the BTS' in europe use
different frequencies than in the US. the current layer23 will only
support 900mhz and 1800mhz bands so far. i didn't care about other
bands, because i have no way to test it. i can add new bands to layer23.
your mail gives me some motivation to implement this finally. the
support of DCS and PCS in parallel is quite tricky. maybe i will finish
this weekend and you may try that out.
regards,
andreas
You don't have to answer this right now if you don't want to, it can
wait. I have been working on this for a few months. I have never
posted on this mailing list before, but I have read many of the other posts.
Just so you know, I am currently 14 years old and I have autism(which is
the reason why I am obsessed with computers and electronics).
I am having trouble getting any signal at all. the signal is around -111
dBm on every channel with the rf gain set on high. The original
firmware works fine with an at&t sim card and has 3 bars. The linux
distro that I am running is backtrack 4. While trying to diagnose this,
I tried mobile and layer23 on a known good channel from a nokia 3100
series phone in netmonitor mode. and in scanning mode on most of the
branches that I compiled. I have looked on the wiki and google. I have
also tried to figure out how parts of the source code work. I have even
tried this on two different boards, the compal_e88 and compal_e86. Has
anybody else had this problem? Where exactly is the antenna switch?
That could be the problem, if it connects to the headset slot. I have a
homemade t191 cable, that uploads the firmware just fine, but I am
wondering about the LOST message after the dsp download. What does the
LOST message mean?
Thank you for your help,
Calvin
I found another phone witch looks like it runs Android OS on a MT6516 processor,
you can find it here
http://www.voldltd.com/sdp/1100371/4/pd-5258987/7588204-2080998/H6_Android_…,
it's a VOLD VD-H6. I send them an email but for now no response, I haven't
found a ROM to look into it, but the manufacturer is "VOLD Company Limited" and
on their website it says that is Android on MT6516, so they need to have the
driver for it.
I found another mobile witch run Android on a MT6516 processor, you can find it
here
http://www.voldltd.com/sdp/1100371/4/pd-5258987/7588204-2080998/H6_Android_…,
it's a VOLD VD-H6, I'm still trying to get as much info from the Star A3000
Android ROM and from the datasheet. I hope that in the near future this
processor will be supported by Linux/Android. For now you can find the A3000
kernel config file on the thread "Re: how to decompile a linux kernel zImage".
Help is welcomed.
hello, when i run osmocom i meet a problem that LOCATION UPDATE REQUEST is always faild,
the details are in the following:
1, my hardware environment:
a Moto C118 mobile;
a cheap RS232 com port to jack port data cable (unkown chip);
a USB2 to RS232 converter using FTDI chip;
i5 CPU with GIGABYTE motherbord running with Ubuntu 9.04;
2, i run the command osmocon, mobile, and telnet as below in seprate terminals in order.
./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/layer1.compalram.bin
./mobile -i 127.0.0.1
telnet localhost 4247
en
sim reader 1
3, after that osmocom is working, but things doesn't happed what i wish, LOCATION UPDATE REQUEST is always faild so that the phone can not make calls.
-in command mobile running terminial i grubbed the following log:
"
<0001> gsm48_rr.c:2006 PAGING ignored, we are not camping.
writing msgb to gsmtap fd: Connection refused
<0001> gsm48_rr.c:694 timer T3126 has fired
<000d> gsm48_rr.c:699 Requesting channel failed
<0001> gsm48_rr.c:363 new state connection pending -> idle
<0003> gsm322.c:3318 (ms 1) Event 'EVENT_RET_IDLE' for Cell selection in state 'C3 camped normally'
<0003> gsm322.c:2889 Selecting frequency 22. after LOC.UPD.
<0003> gsm322.c:251 Sync to ARFCN=22 rxlev=-56 (Sysinfo, ccch mode NON-COMB)
<0003> gsm322.c:540 new state 'C3 camped normally' -> 'C3 camped normally'
<0004> gsm48_mm.c:3695 (ms 1) Received 'RR_REL_IND' from RR in state wait for RR connection (location updating)
<0004> gsm48_mm.c:2589 RR link released after loc. upd.
<000d> gsm48_mm.c:2533 Location update failed
<000d> gsm48_mm.c:2543 Try location update later
<0004> gsm48_mm.c:2545 Loc. upd. failed, retry #0
<0004> gsm48_mm.c:391 starting T3211 (loc. upd. retry delay) with 15.0 seconds
<0004> gsm48_mm.c:4083 (ms 1) Received 'MM_EVENT_CELL_SELECTED' event in state wait for RR connection (location updating)
<0004> gsm48_mm.c:1055 We are in registered LAI as returning to MM IDLE
<0004> gsm48_mm.c:892 new state wait for RR connection (location updating) -> MM IDLE, normal service
<0003> gsm322.c:2433 Channel synched. (ARFCN=22, snr=13, BSIC=10)
<0001> gsm322.c:2460 using DSC of 90
<0003> gsm48_rr.c:4548 Channel provides data.
writing msgb to gsmtap fd: Connection refused
writing msgb to gsmtap fd: Connection refused
<0001> gsm48_rr.c:609 MON: f=22 lev=-52 snr= 0 ber= 62 LAI=460 00 11a5 ID=629a
writing msgb to gsmtap fd: Connection refused
<0001> gsm48_rr.c:2265 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2286 (ta 1/553m ra 0x7f chan_nr 0x0e ARFCN 22 TS 6 SS 0 TSC 2)
<0001> gsm48_rr.c:2291 Not for us, no request.
"
-it shows that LOCATION UPDATE REQUEST is faild and it will be retry, and use command "OsmocomBB# show ms" also can find that the mobile is trying hard to get location update successfully:
"
OsmocomBB# show ms
MS '1' is up, MM connection active
IMEI: 000000000000000
IMEISV: 0000000000000000
IMEI generation: fixed
automatic network selection state: A1 trying RPLMN
cell selection state: C3 camped normally
radio ressource layer state: connection pending
mobility management layer state: wait for RR connection (location updating)
OsmocomBB# show ms
MS '1' is up, service is normal
IMEI: 000000000000000
IMEISV: 0000000000000000
IMEI generation: fixed
automatic network selection state: A1 trying RPLMN
cell selection state: C3 camped normally (ARFCN 22)
radio ressource layer state: idle
mobility management layer state: MM idle, normal service
OsmocomBB# show ms
MS '1' is up, service is normal
IMEI: 000000000000000
IMEISV: 0000000000000000
IMEI generation: fixed
automatic network selection state: A1 trying RPLMN
cell selection state: C3 camped normally (ARFCN 22)
radio ressource layer state: idle
mobility management layer state: MM idle, normal service
OsmocomBB# show ms
MS '1' is up, MM connection active
IMEI: 000000000000000
IMEISV: 0000000000000000
IMEI generation: fixed
automatic network selection state: A1 trying RPLMN
cell selection state: C3 camped normally
radio ressource layer state: connection pending
mobility management layer state: wait for RR connection (location updating)
"
-and in command osmocon terminal, i found the log may show the LOCATION UPDATE REQUEST faild reasons.
"
Received PROMPT1 from phone, responding with CMD
read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): file_size=53948, hdr_len=4, dnload_len=53955
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/53955)
handle_write(): 4096 bytes (8192/53955)
handle_write(): 4096 bytes (12288/53955)
handle_write(): 4096 bytes (16384/53955)
handle_write(): 4096 bytes (20480/53955)
handle_write(): 4096 bytes (24576/53955)
handle_write(): 4096 bytes (28672/53955)
handle_write(): 4096 bytes (32768/53955)
handle_write(): 4096 bytes (36864/53955)
handle_write(): 4096 bytes (40960/53955)
handle_write(): 4096 bytes (45056/53955)
handle_write(): 4096 bytes (49152/53955)
handle_write(): 4096 bytes (53248/53955)
handle_write(): 707 bytes (53955/53955)
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-757-gc4483bf-modified)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: 71c60b1d89021625
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
======================================================================
Power up simcard:
THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!!
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 1634!
"
"
SB2 (2663816:2): TOA= 26, Power= -60dBm, Angle= 132Hz
=> SB 0x003cf629: BSIC=10 fn=1331917(1004/15/ 1)=> DSP reports SB in bit that is 965199799 bits in the future?!?
Synchronize_TDMA
=> DSP reports FB in bit that is 965199776 bits in the future?!?
LOST 1908!
nb_cmd(0) and rxnb.msg != NULLL1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0a, offset=8 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0a, offset=236 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0d, offset=248 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x06, offset=240 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x04, offset=217 combined=0)
L1CTL_DM_REL_REQL1CTL_RESET_REQ: FULL!L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=22, flags=0x7)
Starting FCCH RecognitionEMPTY
FB0 (1334018:5): TOA= 5040, Power= -57dBm, Angle= 2049Hz
FB1 (1334028:8): TOA= 8755, Power= -57dBm, Angle= 223Hz
fn_offset=1334026 (fn=1334028 + attempt=8 + ntdma = 6)m delay=8 (fn_offset=1334026 + 11 - fn=1334028 - 1
scheduling next FB/SB detection task with delay 8
=>FB @ FNR 1334026 fn_offset=1334026 qbits=4836
Synchronize_TDMA
LOST 3717!
SB1 (2668059:1): TOA= 27, Power= -59dBm, Angle= -9Hz
=> SB 0x0111f729: BSIC=10 fn=1334038(1006/ 4/31)=> DSP reports SB in bit that is 959894800 bits in the future?!?
Synchronize_TDMA
=> DSP reports FB in bit that is 959894777 bits in the future?!?
LOST 1909!
nb_cmd(0) and rxnb.msg != NULLL1CTL_RESET_REQ: FULL!EMPTY
L1CTL_FBSB_REQ (arfcn=22, flags=0x7)
Starting FCCH RecognitionFB0 (1337271:8): TOA= 9312, Power= -56dBm, Angle=-3405Hz
FB1 (1337282:9): TOA= 9999, Power= -56dBm, Angle= 5216Hz
fn_offset=1337280 (fn=1337282 + attempt=9 + ntdma = 7)m delay=8 (fn_offset=1337280 + 11 - fn=1337282 - 1
scheduling next FB/SB detection task with delay 8
FB1 (1337302:11): TOA=12507, Power= -56dBm, Angle= 431Hz
fn_offset=1337300 (fn=1337302 + attempt=11 + ntdma = 9)m delay=8 (fn_offset=1337300 + 11 - fn=1337302 - 1
scheduling next FB/SB detection task with delay 8
=>FB @ FNR 1337300 fn_offset=1337300 qbits=4844
Synchronize_TDMA
LOST 3719!
SB1 (2674604:1): TOA= 24, Power= -56dBm, Angle= 263Hz
=> SB 0x000af829: BSIC=10 fn=1337312(1008/ 2/41)=> DSP reports SB in bit that is 951713547 bits in the future?!?
Synchronize_TDMA
=> DSP reports FB in bit that is 951713524 bits in the future?!?
LOST 1905!
nb_cmd(0) and rxnb.msg != NULLL1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0f, offset=13 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0a, offset=233 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0a, offset=237 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0e, offset=240 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x04, offset=241 combined=0)
L1CTL_DM_REL_REQL1CTL_RESET_REQ: FULL!L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=22, flags=0x7)
Starting FCCH RecognitionFB0 (1339424:4): TOA= 3792, Power= -53dBm, Angle= 2044Hz
FB1 (1339434:8): TOA= 8755, Power= -52dBm, Angle= 295Hz
fn_offset=1339432 (fn=1339434 + attempt=8 + ntdma = 6)m delay=8 (fn_offset=1339432 + 11 - fn=1339434 - 1
scheduling next FB/SB detection task with delay 8
=>FB @ FNR 1339432 fn_offset=1339432 qbits=4836
Synchronize_TDMA
LOST 3717!
"
-i found the value of LOST is too big, and i tried to look for reasons in codes and found function "check_lost_frame()" below (in sync.c, lines 180 to 205). After read this code, i think it's delays of physical layer caused so so much LOST value.
"
/* Lost TDMA interrupt detection. This works by starting a hardware timer
* that is clocked by the same master clock source (VCTCXO). We expect
* 1875 timer ticks in the duration of a TDMA frame (5000 qbits / 1250 bits) */
/* Timer for detecting lost IRQ */
#define TIMER_TICKS_PER_TDMA 1875
#define TIMER_TICK_JITTER 1
static int last_timestamp;
static inline void check_lost_frame(void)
{
int diff, timestamp = hwtimer_read(1);
if (last_timestamp < timestamp)
last_timestamp += (4*TIMER_TICKS_PER_TDMA);
diff = last_timestamp - timestamp;
/* allow for a bit of jitter */
if (diff < TIMER_TICKS_PER_TDMA - TIMER_TICK_JITTER ||
diff > TIMER_TICKS_PER_TDMA + TIMER_TICK_JITTER)
printf("LOST %d!\n", diff);
last_timestamp = timestamp;
}
"
4, here, i want some help to figure out whether physical delays caused big LOST value, and big LOST value caused LOCATION UPDATE REQUEST failed?
if it's the problem of the physical layer, i want to make sure which part should be held responsible:
-is that the cheap RS232 com port to jack port data cable caused the delays?
-or is the USB2 to RS232 converter caused the delays?
-or is that some bugs in layer1.compalram.bin caused the delays?
i really want some experienced engineer to help me fix up the problem.
Thanks!
Best Regards!
zheng
2011-03-09
