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@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
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/
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
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
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(a)lists.osmocom.org
[mailto:baseband-devel-bounces@lists.osmocom.org] Im Auftrag von
Sebastian ---
Gesendet: Mittwoch, 5. Januar 2011 21:57
An: baseband-devel(a)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 :)
Hi,
I use Ubuntu 9.10, when i try to Compile Osmocom, i get this:
root@r00t-laptop:~# cd /home/r00t/install/osmocom-bb/src
root@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@r00t-laptop:~/install/osmocom-bb/src#
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 :)
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(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
