- baseband-devel - lists.osmocom.org

AW: Order of functions to transmit and receive using layer1
by Andreas.Eversberg 14 Mar '11

14 Mar '11

hi, > 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? there are only two types of data between L1 and L2: data frames and channel request burst. all the other functions control the radio and the channel in which to communicate. the layer 1 is controlled by the radio ressource protocol (gsm48_rr.c). in order to understand the channel multiplexing, you should read GSM TS 05.02. > Is there any way to send > a text message to a different phone by simulating a base station? osmocom is not (yet) able to control baseband hardware to act as a BTS. > Do I > need two phones or one phone to transmit and receive as a base station? in order to have more than a BCCH, you need two phones. one phone is not able to send and receive at a time. continuouly transmission is required for other phones to find a cell. > 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? you can limit the number of active calls by limiting the number of channels on the BTS, but you cannot limit the number of phones camping on the BTS. > Would it be legal to run a very low power base station in the USA on a different unused cellular band/frequency? you need to check the FCC for laws and test licenses. > 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. if you are really interested. you should start reading with TS 04.08. this is what i did. it describes all the three "layer 3" protocols. Thank you for helping, Calvin E. Balke

1 0

DSP dump from C116
by Henk 14 Mar '11

14 Mar '11

Hi all, I am trying to get a dump of the DSP code, but after 2 lines of hex the device seems to get stuck. Some watchdog or so, missing something in the initialization sequence? According to the docs the cDSP ID seems to indicate a version B dsp... Any ideas what I can do to investigate? - Henk ./osmocon -p /dev/ttyS0 -m c123 ../../target/firmware/board/compal_e88/compal_dsp_dump.compalram.bin Output: (I had commented the register locations to see if it helped...) OSMOCOM Compal DSP Dumper (revision osmocon_v0.0.0-780-gb7a4d8d-modified) ====================================================================== Device ID code: 0xb4fb ==> CalypsoLite Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 ==> Version B Die ID code: 168f2c10cb001251 ====================================================================== Assert DSP into Reset Releasing DSP from Reset DSP bootloader version 0x0100 DSP dump: DROM [09000-0dfff] 09000 : 0006 0052 ff7d 009a ffc8 fd21 00b7 ffbf fef7 0009 ff2e fe97 0071 02ce 0719 03f2 09010 : 04be 0625 0359 0535 08e4 033b 0620 078d 02cd 07c5 089e 0346 0494 071f 02d1 03e8

3 3

hi all
by 麦田守望 13 Mar '11

13 Mar '11

can you tell me the osmocom is a free phone software Project or other is it make a GSM Network for free ? i think to make a samll GSM network for free i think use usb interface phone

3 2

c123 boot wihtout battery
by its sead 13 Mar '11

13 Mar '11

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

3 2

Order of functions to transmit and receive using layer1
by Calvin Balke 13 Mar '11

13 Mar '11

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

2 1

Sorry for this kind of mail: but please help||
by royfarji india 12 Mar '11

12 Mar '11

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.

2 2

compile errors
by royfarji india 12 Mar '11

12 Mar '11

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

1 0

AW: no reception, 3 bars on original firmware
by Andreas.Eversberg 11 Mar '11

11 Mar '11

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

1 0

no reception, 3 bars on original firmware
by Calvin Balke 11 Mar '11

11 Mar '11

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

2 1

Re: how to decompile a linux kernel zImage
by burebista 11 Mar '11

11 Mar '11

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.

1 0