- baseband-devel - lists.osmocom.org

Patch suggestion for wireshark's LAPDm dissector
by iZsh 15 Sep '11

15 Sep '11

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

1 0

difference between ft232 and max 232?
by labad jala 14 Sep '11

14 Sep '11

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.

5 4

Not able to download the sources from git clone git://git.osmocom.org/osmocom-bb.git
by karnatinagesh＠gmail.com 13 Sep '11

13 Sep '11

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.

2 2

Not able to connect to Network using C-115 devices.
by nageswara reddy 08 Sep '11

08 Sep '11

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.

4 3

Osmocom + USRP
by Alexander Chemeris 08 Sep '11

08 Sep '11

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)

2 2

How to change the log setting through vty?
by josephli 08 Sep '11

08 Sep '11

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.

1 0

Motorola C119
by Basem Ahmed 04 Sep '11

04 Sep '11

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

3 3

serial issues on fast PC
by Job 03 Sep '11

03 Sep '11

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

2 2

[PATCH 0/2] Adding embedded and utilities to configure options
by Job 02 Sep '11

02 Sep '11

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

3 6

Re: Bug in frequency list generation of libosmocore
by Dieter Spaar 01 Sep '11

01 Sep '11

Hello, appended is another patch for fixing a bug in the calculation of the frequency lists. This time the patch is for the "Range 256 format". The problem is that the operand for the "smod" operation might be negative, in this case the simplified version won't work as expected. In the patch I introduced a separate function for "smod" which takes care of the sign. I have not yet checked if the other formats are also affected, this would be the case if the "smod" operand can be negative. There might be other solutions to fix the problem without the need for a separate function, however I have not thought further about it. A test vector is the following frequency list ("Range 256 format", first byte is the length): 09 8b 1c 83 8c 15 ef 02 2d 30 The correct ARFCNs are 569 571 576 578 586 608 712 715 719 The uncorrected version would instead return: 444 457 460 464 569 576 578 586 608 This means four ARFCNs are wrong which will cause problems if for example the frequency list contains the ARFCNs for hopping. Best regards, Dieter Dieter Spaar, Germany spaar(a)mirider.augusta.de

2 1