baseband-devel June 2010

baseband-devel@lists.osmocom.org

23 participants
28 discussions

Re: Trouble building Osmocom
by Holger Freyther 08 Jun '10

08 Jun '10

On 06/08/2010 09:24 PM, Huseyin Turan wrote: > name1@name1-desktop:~/osmocom/gnuarm-4.0.2/bin$ ./arm-elf-gcc > bash: ./arm-elf-gcc: cannot execute binary file Why is that the case? The basic checks are a.) did the +x bit go missing on that file? b.) file ./arm-elf-gcc tells you what architecture is that? uname -a tells you what architecture are you running on? c.) when the above fails, we will talk about it...

1 0

Re: Trouble building Osmocom
by Holger Freyther 08 Jun '10

08 Jun '10

On 06/08/2010 09:01 PM, Huseyin Turan wrote: > checking for gcc... gcc > checking for C compiler default output file name... > configure: error: in > `/home/name1/osmocom/osmocom-bb/src/shared/libosmocore/build-host': > configure: error: C compiler cannot create executables > See `config.log' for more details. Looking at the log file is always a good idea. It might have an eye opening effect.... > > That is; in gnuarm-4.0.2/arm-elf/bin there are executables like > gcc,g++,etc. which can be executed. > in gnuarm-4.0.2/bin there are executables like > arm-elf-gcc,arm-elf-g++,etc. which can not be executed. > > Which path is true? You want to use your normal gcc and such, so putting gnuarm-4.0.2/arm-elf/bin in your path is not that clever. What is the issue with arm-elf-gcc? What happens when you try to execute it?

1 0

Trouble building Osmocom
by Zaki Ud Din 08 Jun '10

08 Jun '10

Hello, Thank you very much for your reply. I am using ,"* binutils-2.16.1, gcc-4.0.2-c-c++, newlib-1.14.0, insight-6.4, TAR BZ2 [65.5MB]*" under GCC-4.0 toolchain from www.gnuarm.com. I then extracted to the folder named "Zaki". I did export the path using the following line "export PATH=$PATH:/home/zaki/gnuarm- 4.0.2/arm-elf/bin/ " and afterwards I typed "make firmware" and then got the errors I told you. Awaiting your response, Zaki.

2 1

Trouble building Osmocom
by Zaki Ud Din 08 Jun '10

08 Jun '10

Hello, I have been trying to build osmocom but have been getting errors in doing so. Firstly, I downloaded the following file,"* binutils-2.16.1, gcc-4.0.2-c-c++, newlib-1.14.0, insight-6.4, TAR BZ2 [65.5MB]*" under GCC-4.0 toolchain from www.gnuarm.com and extracted this to my home folder. Secondly, I gave the following path "export PATH=/gnuarm-4.0.2/arm-elf/ bin:$PATH" in terminal window. Afterwards when I entered "make" under "/osmosom-bb/src", I got the following errors zaki@zaki-desktop:~/osmocom-bb/src$ make cd shared/libosmocore/build-host && make make[1]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host' make all-recursive make[2]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host' Making all in include make[3]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include' Making all in osmocore make[4]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore' Making all in protocol make[5]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol' make[5]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore' make[4]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore' make[4]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include' make[3]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/include' Making all in src make[3]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/src' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/src' Making all in tests make[3]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests' Making all in timer make[4]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests/timer' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests/timer' Making all in sms make[4]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests/sms' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests/sms' make[4]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests' make[3]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host/tests' make[3]: Entering directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host' make[3]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host' make[2]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host' make[1]: Leaving directory `/home/zaki/osmocom-bb/src/shared/libosmocore/build-host' cd shared/libosmocore/build-target && ../configure \ --host=arm-elf-linux --disable-shared --disable-talloc --disable-tests \ CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections -I../../../../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 a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking for arm-elf-linux-strip... no checking for strip... strip checking whether make sets $(MAKE)... (cached) yes checking for arm-elf-linux-gcc... arm-elf-gcc checking for C compiler default output file name... configure: error: in `/home/zaki/osmocom-bb/src/shared/libosmocore/build-target': configure: error: C compiler cannot create executables See `config.log' for more details. make: *** [shared/libosmocore/build-target/Makefile] Error 77 I shall be grateful to you if you could help me on this. Awaiting your Response, Zaki.

5 8

Re: Trouble building Osmocom
by Sylvain Munaut 08 Jun '10

08 Jun '10

This seems pretty clear : > ../configure: line 2939: arm-elf-gcc: command not found Make sure you have a good ARM toolchain installed ... (look it up on google, plenty of doc on how to install one). Sylvain

1 0

General Info
by Micheal Johnson 07 Jun '10

07 Jun '10

Hello, Can this project be used to transmit gsm packets from the mobile phone? Regards, Micheal.

1 0

state of layer23
by Andreas.Eversberg 07 Jun '10

07 Jun '10

hi, if you pull the git, you will notice that i submitted the lapdm code i was working on. location update with app_mobile works now. (at least for the combined BCCH+CCCH+SDCCH4) the best way to test the location update is to setup a mobile test card to manual network selection, and to set the registered PLMN to the tester's network. see VTY interface for more. what happens: - the previously store ba-list of frequencies is used to search for the registered PLMN. since there is only one frequency on a tester, the power measurement is done on this frequency only. - the power measurement result is positive, so a sync request is made to that channel. - the sync is indicated by layer 1. - the BCCH data is received. the cell is "suitable and allowable". - a sync request is done again, because this cell is the one to "camp on". - a sync request is done again, because the mobility management process makes a location update and requests a channel from the radio ressource. - the sync is confirmed by layer 1. - after syncing to the channel the layer 2 is activated by the BTS. - the location updating request is sent and messages are exchanged until the location update is complete. - the layer 2 is de-activated by the BTS. - the release of layer 2 is currently not processed by RR, so the timout aborts the radio link. (but this is fixed soon) but there are problem: 1. the layer 1 sometimes crashes when sending frames. i guess there is no queue inside... i currently don't care about any confirm of a frame, so i send all frames i need to send. i would like to get a confirm when a frame is sent, so i can send the next frame without making layer 1 overflow. this confirm would also be handy for RACH requests when they are sent. since there are only few message during a location update or a call, i think this is not much overhead. when requesting sync/rach again, all pending frames (RACH request / transmit data) shall be removed inside layer 1. 2. when sending two sync requests to layer 1 without a delay, the layer 1 crashes. i expect to do a sync request at any time. also when sending a sync request before i got a response, i do not know to which the response belongs to which request. (delayed on the serial line) a confirm of every sync request would be handy, so i can wait for this confirm until i make another sync request to a different channel. this confirm just tells me that the layer 1 has received the sync request and is able to receive another sync request. also when syncing to a different channel, i skip any sync result or received frames until i get the confirm, so i can skip any data from the last channel i was synced to. andreas

1 0

Building Osmocom
by Zaki Ud Din 06 Jun '10

06 Jun '10

Hello, I am a little new to ubuntu and am trying to build osmocom-bb but i am facing some problems in doing so. I found your emial address in the .c files present in the Osmocom-bb folder. I have downloaded the GNU toolchain for ARM which is the first step in building Osmocom. But I am not able to understand the second step in which I have to set a path to include the arm-elf-* executables of the toolchain. Would you please help me on this? Awaiting your response, Zaki.

4 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel June 2010