baseband-devel

baseband-devel@lists.osmocom.org

2022 discussions

problems to run ./mobile app
by josephli 15 Jul '11

15 Jul '11

Hello every: When I tried to run ./mobile -i 127.0.0.1, the words Failed to parse the config file: '/root/.osmocom/bb/mobile.cfg' Please check or create config file using:'touch /root/osmocom/bb/mobile.cfg' came out. I checked my directory /ect and there is nothing there. It seems that network between my PC and phone is block so that the application ./mobile can not communicate with phone. However the layer1 can load on the phone and work properly. Can any one tell my how to fix this problem? Cheers, Li -- View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-to-run-mobile-app-tp316… Sent from the baseband-devel mailing list archive at Nabble.com.

2 8

Help me I have a difficult problem
by adel 13 Jul '11

13 Jul '11

Hello I'm having a problem in the start mobile application ~/osmocom-bb$ cd src/host/layer23/src/mobile ~/osmocom-bb/src/host/layer23/src/mobile$ ./mobile Copyright (C) 2008-2010 ... Contributions by ... License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Failed to parse the config file: '/etc/osmocom/osmocom.cfg' Please check or create config file using: 'touch /etc/osmocom/osmocom.cfg' ~/osmocom-bb/src/host/layer23/src/mobile$ Please help me as soon as -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Help-me-I-have-a-difficult-probl… Sent from the baseband-devel mailing list archive at Nabble.com.

11 17

Is data actually sent if "COMPILED WITHOUT TX SUPPORT"?
by Sergey 08 Jul '11

08 Jul '11

Hello! Is any way that data is actually sent to air if on loading "layer1.compalram.bin" 'osmocon' says: "THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!! " ? E.g. when 'mobile' says "sending page response" does it really communicate with the BTS? I'm talking about main branch (not testing) and compiled without TX support. Sorry if it's obvious, I just dont want to find "the very extent permittable by law".

2 1

gsm specifications
by Sergey 07 Jul '11

07 Jul '11

Hello, everyone! I've got c123-compatible phone, the firmware is running and that's really cool. Testing branch even sometimes says that a call has been released, but it doesn't seem to reach the target (no ringing). I would like to debug and maybe contribute, but... But here is a problem: I don't understand GSM and can't find reasonable documents to read. I've looked through a book on gsm "GSM and Personal Communications Handbook", but it doesn't seem to provide enough info. Specifications of GSM I found at http://www.3gpp.org/specification-numbering are too plentiful. Could you please advise some books to understand the protocols? Or could you tell me where to look for specifications and which should be read first (an what to be read at all) ?

4 5

Bounce action notification
by mailman＠lists.osmocom.org 06 Jul '11

06 Jul '11

This is a Mailman mailing list bounce action notice: List: baseband-devel Member: andre(a)ac.nl.eu.org Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman(a)lists.osmocom.org.

1 0

GPSD support
by Victor P 06 Jul '11

06 Jul '11

Hello.I have been trying to use cell_log with bluetooth GPS. I used gpsd v 2.37 and v 2.95, but in both cases I had the error "Osmocom was compiled without gpsd support". Should I use another version of gpsd or mistake in compilation (any patch?)? thank you for helpWith best wishes,Victor

2 1

Success at last - C139 now working Layer1.bin displayed on phone :)
by Raz Sharif 05 Jul '11

05 Jul '11

Dear all, the last few days I have as you know sent a few mails in my quest to delve into the Osmocomm GSM stack. A few problems later and a few substitutes later such as a C139 phone versus the C115 am I now good to go it would appear. Please see below. I did a lot of RTFM and would also like to to thank the folks who provided me with pointers. I will no doubt have a few more issues so lets see. In summary - The Prolific cable works fine albeit a small cut back on the connector - 2.5mm side C115 is supported but if you can go for the C139 - Too many issues to resolve with C115 maybe due to a specific Firmware variant. If you have the time to hack around I am sure it not difficult to work. Here's my Boot loader dump. Please see below. Thanks Raz http://pastebin.com/A1xf8Wkt

1 0

C139 confirmation of operation from Users please.
by Raz Sharif 05 Jul '11

05 Jul '11

Hi Folks, I recently mailed the group to discuss issue with the C115 Phone and am now trying the C139. It appears to load and i get :- ./osmocon -p /dev/ttyUSB0 -m c140 -c ../../target/firmware/board/compal_e86/layer1.highram.bin ../../target/firmware/board/compal_e86/chainload.compalram.bin read_file(../../target/firmware/board/compal_e86/chainload.compalram.bin): file_size=4132, hdr_len=4, dnload_len=15341 read_file(../../target/firmware/board/compal_e86/chainload.compalram.bin): file_size=4132, hdr_len=4, dnload_len=15341 got 2 bytes from modem, data looks like: 2e c8 .. got 1 bytes from modem, data looks like: 1b . got 4 bytes from modem, data looks like: 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 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/15341) handle_write(): 4096 bytes (8192/15341) handle_write(): 4096 bytes (12288/15341) handle_write(): 3053 bytes (15341/15341) 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 . kbuildsycoca4 running... Also when i run the Mobile app i get :- telnet localhost 4247 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Welcome to the OsmocomBB control interface OsmocomBB> enable OsmocomBB# exit Exit current mode and down to previous mode help Description of the interactive help system list Print command list write Write running configuration to memory, network, or terminal show Show running system information disable Turn off privileged mode command configure Configuration from vty interface copy Copy configuration terminal Set terminal line parameters echo Echo a message back to the vty who Display who is on vty monitor Monitor... no Negate a command or set its defaults off Turn mobiles off (shutdown) and exit sim SIM actions network Network ... call Make a call OsmocomBB# sim % Command incomplete. OsmocomBB# show % Command incomplete. OsmocomBB# Thanks and would be grateful for your support as I appear to be edging forwards. :) and hopefully not backwards. Raz

1 0

Osmocom Loading Issues - TTYUSB0 loopback
by Raz Sharif 05 Jul '11

05 Jul '11

Hi folks, further to my previous email i now ran : I simply pressed the Power Switch a few times but not power on. This is what is recorded. As you will recall i get the FMTool Error and aborted message and never see Prompt2. With no Osmocom programs running can someone please confirm that this output is correct or indeed suggests that the Phones Serial Line or other Firmware or Phone Hardware is causing this error please - would be grateful. Thanks Raz _________________________________________- cat < /dev/ttyUSB0 >| rs.txt 00000000 00 2e 00 1b f6 02 00 41 01 40 66 74 6d 74 6f 6f |.......A.@ftmtoo| 00000010 6c 65 72 72 6f 72 00 00 2f 00 1b f6 02 00 41 01 |lerror../.....A.| 00000020 40 66 74 6d 74 6f 6f 6c 65 72 72 6f 72 00 00 2f |@ftmtoolerror../| 00000030 00 1b f6 02 00 41 01 40 66 74 6d 74 6f 6f 6c 65 |.....A.@ftmtoole| 00000040 72 72 6f 72 00 00 2f 00 1b f6 02 00 41 01 40 66 |rror../.....A.@f| 00000050 74 6d 74 6f 6f 6c 00 00 00 00 00 00 00 00 00 00 |tmtool..........| 00000060 00 00 00 00 00 2f 00 1b f6 02 00 41 01 40 66 74 |...../.....A.@ft| 00000070 6d 74 6f 6f 6c 65 72 72 6f 72 00 |mtoolerror.|

1 0

osmocn question
by eisencah eisenach 04 Jul '11

04 Jul '11

Hi everyone. One remark regarding osmocon : it seems to me that we're reading one byte at the time from the serial port once we're done with downloading code into RAM. That seems quite on overhead (specially on slow machines like mine). I believe we should modify that once dnload.expect_hdlc == 0 we can free up the entire buffer. Is that so or I'm missing something? Mihai.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel