baseband-devel September 2011

baseband-devel@lists.osmocom.org

31 participants
44 discussions

Comprehensive User Directive Manual Needed

by rola

Hi all, I am really thrill to set up OsmocomBB program single handedly after scourging through mailing list and crash learning linux environment from online tutorials. This is an amazing project with a lot of concept and idea that can only be acquired through years of working as a developer. I really appreciate the great work each and everyone put into this project and I am taking advantage of this to set myself back as a programmer. Could there be a comprehensive documentation on how to setup the the project from the first stage of firmware download to the linking of various applications to the running osmocon program. It took a lot of time to get myself around the project before I could finally set it up. Beside the core participant programmers and those that were previously familiar with this nature of application many of the interested enthusiast like me are left in the dark on what to do at one point or the other during the set up of the project. For an instance after successfully setting up the osmocomBB, I couldn't run the program with my C155 just for the fact that I mistakenly took the passing parameter for C155 for "C155xor" following the given example based on C123. It took me over two days to realized where the error was all because I was having legitimate error report of "NACK" that was explained on the blog to be due to different transmission rate between the hosting system and the MS onboard chip. By stroke of luck, I removed the "xor" based on solution suggested for similar issue on different Motorola model and VIOLA !!! firmware completes downloading and I'm set on track . The funniest thing is that it was after I've resolved the problem that I later read the reference to the C155 parameter passing. Secondly, setting up config file for MOBILE APP was like searching for needle in the hail. My thought was that the file needed to contain a written configuration of VTY with telnet parameters. That took me on a journey of learning what telnet is, what Virtual Terminal is. Anyway, I learn a lot from googling here and there before I finally read in some solution that the file is just an empty file. I know that it might be trivial issue to many of the grounded programmers but to some like me it was really a big issue. Right now I am running the Mobile App and about to setup the patch wireshark but still have no clue of what command to send through the telnet interface or what next to do on the Mobile prompt section. It will be a nice to have a compiled possible errors that newbies might encounter and as well a basic step on what to do at each stage of setting up and running of the programs. Just to give a little background about myself; I have a two semester of wireless technology as part of my graduate study and I intend to use OsmocomBB as the basis of my thesis on analyzing GSM Um interface. Great work guys and God bless. Rasak -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Comprehensive-User-Directive-Man… Sent from the baseband-devel mailing list archive at Nabble.com.

13 years, 11 months

Patch suggestion for wireshark's LAPDm dissector

by iZsh

Hello, (my first post to this ML) Sylvain told me it might be a good place to post this. Please find attached a small patch for wireshark's LAPDm dissector. It currently fails at reassembling LAPDm packets when processing multiple streams at the same time insofar as it always assume the fragmented type I LAPDm frames belong to the same stream. This is of course wrong if you process, for instance, all the timeslots of a S{D,A}CCH channel. The proposed patch, which might not be ideal but seems to work better with my testcase (and not worse), identifies the stream using the tuple (link direction, timeslot, subslot). I reused the packet_info's circuit_id field for this, which should be safe enough to use. Let me know if you have any comments., hopefully this could be committed upstream by someone with commit access. Best Regards, iZsh

13 years, 11 months

difference between ft232 and max 232?

by labad jala

Hello techies. Is there a big difference between ft232 and max232? I have taken apart this cable : http://www.cellcorner.com/xshp/unlock-phone-codes/motorola-t190-t191-t193-u… and a picture is attached. By the way, the pinout and voltage (+4v) doesn't seem to match so I'd like to solder it the proper way..Any advise welcome. Cheers.

13 years, 11 months

Not able to download the sources from git clone git://git.osmocom.org/osmocom-bb.git

by karnatinagesh＠gmail.com

Hi, currently i am not able to download the sources from the git repository. git clone git://git.osmocom.org/osmocom-bb.git is there some issues with the git repository ?. regards, nageswara reddy. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Not-able-to-download-the-sources… Sent from the baseband-devel mailing list archive at Nabble.com.

13 years, 11 months

Not able to connect to Network using C-115 devices.

by nageswara reddy

Hi, Finally i am able to compile the GSM Stack code and flash into the Motorol Device C-115. i can see the "layer1.bin" on the display, but my device is not latched on to the N/W. - When i ran the HOST software of Mobile. i can see that SIM reader code is not working, and i can see the IMEI is hardcoded to "0000000000000000". - i captured the response of FBSB(Frequency and Time synchronization Burst), the result is comming as "255". can any one please help me how to resolve these issues so that i can latch on to the N/W. regards, nageswara reddy.

13 years, 11 months

Osmocom + USRP

by Alexander Chemeris

Hi Harald and all, I have a client who is interested in an USRP-based MS side implementation. I think that that OsmocomBB is a natural choice for the higher-level stack, but I have only vague idea about its current state. As I understand, burst coding/modulation, reference clock management and GSM clock management should be implemented to get a working MS. Is there anything else to implement? How well is API to Calypso DSP is abstracted in OsmocomBB? (Sorry for my brevity and no googling, I'm abroad on GPRS for few weeks)

13 years, 11 months

How to change the log setting through vty?

by josephli

Hello, I have got the logging details of all c files in the directory ../layer23/src/mobile. And now I also want to check the log in the directory of layer23/src/common/lapdm.c. I found the file logging_vty.c is similar to interface_vty.c so I tried several times but it didnt work. Can any one guide me how to use the vty to change the logging setting? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/How-to-change-the-log-setting-th… Sent from the baseband-devel mailing list archive at Nabble.com.

13 years, 11 months

Motorola C119

by Basem Ahmed

Hi All, I got new Motorola phone modeled "C119" Its shape like feature Motorola C118 but i tried to programmed with OSMOCON utility with the loader or with the simtest applications but it did not work ,So any help please ? Thanks

13 years, 12 months

serial issues on fast PC

by Job

Hi, While testing on a new PC I ran into the following issue. Same phone (C115), same USB cable FTDI RS232 + RS232 -> 3v3, works on a slow Atom PC with latest osmocom-bb git, but fails with fmtool error on a fast i7 core PC. The fail happens after sending the first 4096 bytes with a NACK from the phone. Once in many tries it actually does download something but then fails to run the image. Has anyone seen such behaviour? Any ideas on what might go wrong? If not I'll spend some time to debug it. Best regards, Job

13 years, 12 months

[PATCH 0/2] Adding embedded and utilities to configure options

by Job

Hi, Attached are the patches to update configure.ac and some Makefile.am to use more default option selection style. I commented the docdir var in the main Makefile.am. The second patch contains the addition of --disable-utilities and --enable-embedded options. I never made a patch mail before so let me know if anything is missing. Best regards, Job ==== job (2): Adapted configure options to autoconf default behaviour Added autoconf option for utilities and embedded Makefile.am | 2 +- configure.ac | 55 ++++++++++++++++++++++++++++++++++++++-------------- utils/Makefile.am | 2 + 3 files changed, 43 insertions(+), 16 deletions(-) -- 1.7.4.1

13 years, 12 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel September 2011