baseband-devel

baseband-devel@lists.osmocom.org

2023 discussions

R: Re: Problem with osmocon (beginner)
by screaming-pain＠libero.it 11 Apr '11

11 Apr '11

Thank you Sylvain and Dario! It was a cable problem, I bought a usb one and It works, the only problem is that now I get a NACK, I read it could be a timing problem and I tried to comment the printf as suggested in a recent post, but it did not work. This is what happens: loretta@loretta-laptop:~/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/hello_world. e88loader.bin got 2 bytes from modem, data looks like: 2f c8 /. got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(../../target/firmware/board/compal_e88/hello_world.e88loader.bin): file_size=19560, hdr_len=4, dnload_len=19567 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(): 1023 bytes (1023/19567) handle_write(): 768 bytes (1791/19567) handle_write(): 768 bytes (2559/19567) handle_write(): 768 bytes (3327/19567) handle_write(): 768 bytes (4095/19567) handle_write(): 768 bytes (4863/19567) handle_write(): 768 bytes (5631/19567) handle_write(): 768 bytes (6399/19567) handle_write(): 768 bytes (7167/19567) handle_write(): 768 bytes (7935/19567) handle_write(): 768 bytes (8703/19567) handle_write(): 768 bytes (9471/19567) handle_write(): 768 bytes (10239/19567) handle_write(): 768 bytes (11007/19567) handle_write(): 768 bytes (11775/19567) handle_write(): 768 bytes (12543/19567) handle_write(): 768 bytes (13311/19567) handle_write(): 768 bytes (14079/19567) handle_write(): 768 bytes (14847/19567) handle_write(): 768 bytes (15615/19567) handle_write(): 768 bytes (16383/19567) handle_write(): 768 bytes (17151/19567) handle_write(): 768 bytes (17919/19567) handle_write(): 768 bytes (18687/19567) handle_write(): 768 bytes (19455/19567) handle_write(): 112 bytes (19567/19567) 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: 45 E got 1 bytes from modem, data looks like: 53 S got 1 bytes from modem, data looks like: 16 . Received DOWNLOAD NACK from phone, something went wrong :( got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 00 . Most of the times though it just arrives to the handle_write():finished prints out few "got 1 bytes from modem, data looks like: " lines and it stops there Do you have any suggestion? What should I check? Thanks for your help, Loretta >----Messaggio originale---- >Da: dario.lombardo(a)libero.it >Data: 4-apr-2011 18.01 >A: "screaming-pain(a)libero.it"<screaming-pain(a)libero.it> >Ogg: Re: Problem with osmocon (beginner) > >On 04/04/2011 05:33 PM, screaming-pain(a)libero.it wrote: >> what is going on? can anyone help me to understand how to proceed? >> >Sometimes it happens that moving slightly the jack is enough to break >the serial line. Sometimes I have to try many times, without touching >the phone before the fw loads. Try to insist without moving the phone, >and If you are not lucky try to change cable. >

2 1

Any plan to fork OpenBTS and/or merge with Osmocom code?
by Fabio Pietrosanti (naif) 11 Apr '11

11 Apr '11

Hi all, this email don't want to be a provocative email but just an opinion related to the creation of value for GSM TLC stack into the opensource environment. As we know currently there are several different projects growing into the GSM (then tetra and in future 3G?) opensource ecosystem. The first "pratical" base has been OpenBTS as a simplified GSM um interface for VoIP. The second major implementations was around the osmocom project that build-up a complete and well designed GSM stack with all the modular interfaces and protocols for communications between BTS and BSC, with MSC, HLR, GGSN, SGSN and major GSM network components. Additionally, if i understood correctly osmocom is much more advanced with broad scope and better design than OpenBTS. It seems to me that OpenBTS it's almost stalled due to the "commercial fork" of the OpenSource project and only fairwaves is contributing to the opensource branch. I personally really dislike the "Commercial fork" approach where the community is used only in the early phase of the project to improve it and from a certain point the community doesn't get almost any added value. I like much more the dual-licensed approach like AGPL/Commercial (like http://pjsip.org) where all the value of the code is publicly released. However, my post was related to a question: - How complex would be, leveraging existing public OpenBTS code, to integrate into the Osmocom project? I mean, having a sort of lightweight BTS component speaking A-Bis over IP to OpenBSC like the cheap nano ip.access BTS does. For what i read now Osmocom have 2 software BTS (Osmo-BTS and Soft-BTS), communicating with the A-BIS over IP interface to OpenBSC: http://lists.gnumonks.org/pipermail/openbsc/2011-March/002529.html http://lists.gnumonks.org/pipermail/openbsc/2010-April/001508.html I've read that only a lot of time ago (2009) there was a discussion about OpenBTS to OpenBSC integration: http://lists.gnumonks.org/pipermail/openbsc/2009-October/000955.html At the current stage of development (2011), with Osmocom finally getting a Software-BTS part communicating to the Software-BSC side, how really complex it would be to integrate the GSM-um related part of OpenBTS into the project? With that approach the 'GSM-um' interface would be a very simplified module of the overall system and osmocom would completely replace OpenBTS all-in-one project. Am i right? -naif p.s. Sorry for the cross-posting, i just wanted to explain the idea and get the communities feedbacks to understand 'at which point' we are in order to think 'what would be required to be done' to achieve that goal.

5 9

hi everyone
by 麦田守望 10 Apr '11

10 Apr '11

i find a moto software it can Connection the motorola phone RF Bottom so we only use crack the moto software and Written weself openbts

1 0

a bit of help
by royfarji india 09 Apr '11

09 Apr '11

Hi all, Finally I was able to compile osmocombb with much debugging. Next,how exactly can we build the cable"T191".I was unable to find it on the web.Can anyone help with a schematics and a procedure of how to do it. I would be grateful for it. cheers

2 1

Problem with osmocon (beginner)
by screaming-pain＠libero.it 04 Apr '11

04 Apr '11

Hi all, I have been trying to load "hello world" for hours with no joy so far :( I am using Ubuntu Karmic and a motorola c115 my with a usb to serial and mot T191 cable. I tried different -m options, most of the times nothing happens, though if I play a bit with the earphone jack and the c115 start button it seems some sort of communication starts and the each time I press the start button I can read the following got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: f1 . got 1 bytes from modem, data looks like: 06 . got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 82 . got 1 bytes from modem, data looks like: bf . got 1 bytes from modem, data looks like: 7d } got 1 bytes from modem, data looks like: fd . got 1 bytes from modem, data looks like: 7f . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: a6 . got 1 bytes from modem, data looks like: 51 Q got 1 bytes from modem, data looks like: d2 . got 1 bytes from modem, data looks like: 51 Q got 1 bytes from modem, data looks like: 0a . got 1 bytes from modem, data looks like: 3a : got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 4d M got 1 bytes from modem, data looks like: a3 . got 1 bytes from modem, data looks like: 14 . got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . what is going on? can anyone help me to understand how to proceed? I got once during my trials the message: Received PROMPT1 from phone, responding with CMD but I had a wrong file name so it just wrote it could not find the file :( I know I am a disaster but I would appreciate if someone could give a hint Thanks you very much, Loretta

2 1

R: another compiling problem (beginner)
by screaming-pain＠libero.it 04 Apr '11

04 Apr '11

Hi all, I found out the -nodefaultlibs option is due to a recent patch, so it seems it is solving someone's problem, but it may not be good for everyone. I could compile osmocon-bb without -nodefaultlibs and I found out it compiles without -nostartfiles as well. May be this two options should not be hardcoded, because someone else could have my same problem with the -nodefaultlibs (the -nodefaultfiles did not cause problems to me but seems not to be essential) Regards, Loretta >----Messaggio originale---- >Da: screaming-pain(a)libero.it >Data: 1-apr-2011 13.14 >A: <baseband-devel(a)lists.osmocom.org> >Ogg: another compiling problem (beginner) > >Hi all, > >Sorry for bothering with another compiling problem. >I had the following error while compiling osmocom-bb: > >configure:3246: arm-elf-gcc -Os -ffunction-sections -I/home/loretta/osmocom- >bb/src/target/firmware/include -nostartfiles -nodefaultlibs conftest.c >&5 >conftest.c: In function `main': >conftest.c:15: warning: initialization makes pointer from integer without a >cast >/home/loretta/install/gnuarm-3.4.3/bin/../lib/gcc/arm-elf/3.4.3/../../../.. >/arm-elf/bin/ld: warning: cannot find entry symbol _start; defaulting to >00008000 >/tmp/ccgIuxoW.o(.text.main+0x14): In function `main': >: undefined reference to `fopen' >/tmp/ccgIuxoW.o(.text.main+0x1c): In function `main': >: undefined reference to `ferror' >/tmp/ccgIuxoW.o(.text.main+0x30): In function `main': >: undefined reference to `fclose' >collect2: ld returned 1 exit status >configure:3250: $? = 1 >configure:3287: result: >configure: failed program was: >| /* confdefs.h */ >| #define PACKAGE_NAME "libosmocore" >| #define PACKAGE_TARNAME "libosmocore" >| #define PACKAGE_VERSION "UNKNOWN" >| #define PACKAGE_STRING "libosmocore UNKNOWN" >| #define PACKAGE_BUGREPORT "openbsc-devel(a)lists.openbsc.org" >| #define PACKAGE_URL "" >| #define PACKAGE "libosmocore" >| #define VERSION "UNKNOWN" >| /* end confdefs.h. */ >| #include <stdio.h> >| int >| main () >| { >| FILE *f = fopen ("conftest.out", "w"); >| return ferror (f) || fclose (f) != 0; >| >| ; >| return 0; >| } > > >after hours of trying to understand how to fix this, I figured out that >without the option -nodefaultlibs everything run smoothly. >Now, the problem is that I do not understand much of what is going on and I >wonder, do I need that option and hence should look for a different way of >fixing the problem? > >Thanks for your help, >Loretta > >

1 0

Airprob gsm-tvoid error
by Marten Christophe 04 Apr '11

04 Apr '11

Hello Harald, While running ./go.sh i come across below error there no one on airprob lis now a days plz help why i'm getting that error ======== root@ubuntu:/home/xx/6jan/airprobe/gsm-tvoid/src/python# ./go.sh GSMSP_940.8Mhz_118.cfile go.sh <file.cfile> [decim==112] % offset = 0.0 clock = 64000000.0 Reading data from: GSMSP_940.8Mhz_118.cfile >>> gr_fir_ccc: using SSE >>> gr_fir_ccf: using SSE (python:7893): Gtk-CRITICAL **: gtk_window_resize: assertion `width > 0' failed <<<<<<<<<<<<<<<< ======= Kind Regards,

1 1

NCC alocation
by eisencah eisenach 04 Apr '11

04 Apr '11

I'm having this question about NCC allocation. Is this unique for an operator inside a country? And how it goes if you travel abroad ? (Will the phone look for a network with the same NCC at the begining?) After that it will look at sysinfo and the other stuff but I was wondering how it goes at power up? Thanks.

3 2

CCCH question
by eisencah eisenach 03 Apr '11

03 Apr '11

Hi. In its current stage osmocom makes full use of CCCH-CONF and BS-AG-BLK_RES fields of CCCH description? If a block is reserved for access grant it won't be used on paging? Is there anyway of calling "gsm48_sysinfo_dump" to print on the console? Cheers, Mihai.

2 1

unknown error
by royfarji india 01 Apr '11

01 Apr '11

while compiling i am getting the following error: "libosmocore.a" file in wrong format. arm-elf-objcopy --gap-fill=0xff -O binary board/pirelli_dpl10/layer1.highram.elf board/pirelli_dpl10/layer1.highram.bin arm-elf-ld -nostartfiles -nostdlib -nodefaultlibs --gc-sections --cref -T board/compal/ram.lds -Bstatic -Map board/compal_e88/loader.compalram.map -o board/compal_e88/loader.compalram.elf --start-group apps/loader/main.o abb/twl3025.o rf/trf6151.o display/font_r8x8.o display/font_r8x8_horiz.o display/st7558.o display/td014.o display/ssd1783.o display/display.o flash/cfi_flash.o board/common/calypso_uart.o board/common/calypso_pwl.o board/compal/rffe_dualband.o board/compal/rf_power.o board/compal_e88/init.o board/compal_e88/loader.compalram.manifest.o board/compal/start.ram.o board/compal/exceptions_redirected.o board/compal/handlers.o calypso/libcalypso.a layer1/liblayer1.a lib/libmini.a comm/libcomm.a ../../shared/libosmocore/build-target/src/.libs/libosmocore.a --end-group arm-elf-ld: ../../shared/libosmocore/build-target/src/.libs/libosmocore.a(crc16.o): Relocations in generic ELF (EM: 3) ../..*/shared/libosmocore/build-target/src/.libs/libosmocore.a: could not read symbols: File in wrong format*make[1]: *** [board/compal_e88/loader.compalram.elf] Error 1 make[1]: Leaving directory `/home/roy/osmocom-bb/src/target/firmware' make: *** [firmware] Error 2 roy@roy:~/osmocom-bb/src$ PLEASE HELP!!!!!!!!

3 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel