- baseband-devel - lists.osmocom.org

Re: bad crc in osmoload [SOLVED!]
by Bhaskar11 22 May '13

22 May '13

Solved the "bad crc" problem in Osmoload. The bug was inadvertently introduced in osmoload.c in update SHA ID 6ce46e7a86f4de0b1eef9c641ef6cfb49f1255cd on 9.9..2012 when msgb_get() was replaced by msgb_pull() as part of a large scale change. Looks like no one else had tried a "osmoload memdump" since then. Am enclosing patch to fix this bug. B. On Tue, May 14, 2013 at 5:26 PM, Bhaskar11 <niceguy108(a)gmail.com> wrote: > Hi all, > > I'm trying to flash RSSI app to my C118 following instructions on > http://bb.osmocom.org/trac/wiki/flashing. > > First step Osmocon with loader works fine. > > Second step with "osmoload memdump 0x000000 0x2000 compal_loader.bin" > gives the following output: > > Dumping 8192 bytes of memory at 0x0 to file compal_loader.bin > > bad crc 4190 (not 0000) at offset 0x00000000 > bad crc f041 (not b209) at offset 0x000000f0 > bad crc f041 (not 79d3) at offset 0x000001e0 > ... > bad crc f041 (not fe61) at offset 0x00001e00 > bad crc 8257 (not 4cd6) at offset 0x00001ef0 > bad crc a401 (not 0000) at offset 0x00001fe0done. > > Would appreciate any guidance on what I can do to set this right. > > A general question: > If I flash RSSI app succesfully, can I later restore the original C118 > code and use the cell as before? (assuming I have saved the full memory > dump to disk!) Or is that gone for good? > > Thanks for your guidance. > > B. > > >

1 0

[PATCH] * Bugfix in Firmware: initialising variables
by Bhaskar 22 May '13

22 May '13

Under specific circumstances, these variables would have been used without initialisation. --- src/target/firmware/apps/loader/main.c | 2 +- src/target/firmware/layer1/mframe_sched.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/target/firmware/apps/loader/main.c b/src/target/firmware/apps/loader/main.c index 8bdbc74..c74c045 100644 --- a/src/target/firmware/apps/loader/main.c +++ b/src/target/firmware/apps/loader/main.c @@ -213,7 +213,7 @@ static void cmd_handler(uint8_t dlci, struct msgb *msg) uint8_t command = msgb_pull_u8(msg); - int res; + int res = 0; flash_lock_t lock; diff --git a/src/target/firmware/layer1/mframe_sched.c b/src/target/firmware/layer1/mframe_sched.c index f3a6b43..047d709 100644 --- a/src/target/firmware/layer1/mframe_sched.c +++ b/src/target/firmware/layer1/mframe_sched.c @@ -343,7 +343,7 @@ static const struct mframe_sched_item *sched_set_for_task[32] = { /* encodes a channel number according to 08.58 Chapter 9.3.1 */ uint8_t mframe_task2chan_nr(enum mframe_task mft, uint8_t ts) { - uint8_t cbits; + uint8_t cbits = 0; switch (mft) { case MF_TASK_BCCH_NORM: -- 1.7.9 --047d7bdc15d456c2b204dd61e109 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><font face=3D"courier new, monospace">From d1ad22fa60= e9d52bac246391b2fb6de57fb067b7 Mon Sep 17 00:00:00 2001</font></div><div><f= ont face=3D"courier new, monospace">From: Bhaskar <<a href=3D"mailto:nic= eguy108(a)gmail.com">niceguy108(a)gmail.com</a>></font></div> <div><font face=3D"courier new, monospace">Date: Wed, 22 May 2013 13:08:02 = +0530</font></div><div><font face=3D"courier new, monospace">Subject: [PATC= H] * Bugfix in Firmware: initialising variables</font></div><div><font face= =3D"courier new, monospace"><br> </font></div><div><font face=3D"courier new, monospace">Under specific circ= umstances, these variables would have been used without initialisation.</fo= nt></div><div><font face=3D"courier new, monospace"><br></font></div><div><= font face=3D"courier new, monospace">---</font></div> <div><font face=3D"courier new, monospace">=A0src/target/firmware/apps/load= er/main.c =A0 =A0| =A0 =A02 +-</font></div><div><font face=3D"courier new, = monospace">=A0src/target/firmware/layer1/mframe_sched.c | =A0 =A02 +-</font= ></div><div><font face=3D"courier new, monospace">=A02 files changed, 2 ins= ertions(+), 2 deletions(-)</font></div> <div><font face=3D"courier new, monospace"><br></font></div><div><font face= =3D"courier new, monospace">diff --git a/src/target/firmware/apps/loader/ma= in.c b/src/target/firmware/apps/loader/main.c</font></div><div><font face= =3D"courier new, monospace">index 8bdbc74..c74c045 100644</font></div> <div><font face=3D"courier new, monospace">--- a/src/target/firmware/apps/l= oader/main.c</font></div><div><font face=3D"courier new, monospace">+++ b/s= rc/target/firmware/apps/loader/main.c</font></div><div><font face=3D"courie= r new, monospace">@@ -213,7 +213,7 @@ static void cmd_handler(uint8_t dlci,= struct msgb *msg)</font></div> <div><font face=3D"courier new, monospace">=A0</font></div><div><font face= =3D"courier new, monospace">=A0<span class=3D"" style=3D"white-space:pre"> = </span>uint8_t command =3D msgb_pull_u8(msg);</font></div><div><font face= =3D"courier new, monospace">=A0</font></div> <div><font face=3D"courier new, monospace">-<span class=3D"" style=3D"white= -space:pre"> </span>int res;</font></div><div><font face=3D"courier new, mo= nospace">+<span class=3D"" style=3D"white-space:pre"> </span>int res =3D 0;= </font></div> <div><font face=3D"courier new, monospace">=A0</font></div><div><font face= =3D"courier new, monospace">=A0<span class=3D"" style=3D"white-space:pre"> = </span>flash_lock_t lock;</font></div><div><font face=3D"courier new, monos= pace">=A0</font></div> <div><font face=3D"courier new, monospace">diff --git a/src/target/firmware= /layer1/mframe_sched.c b/src/target/firmware/layer1/mframe_sched.c</font></= div><div><font face=3D"courier new, monospace">index f3a6b43..047d709 10064= 4</font></div> <div><font face=3D"courier new, monospace">--- a/src/target/firmware/layer1= /mframe_sched.c</font></div><div><font face=3D"courier new, monospace">+++ = b/src/target/firmware/layer1/mframe_sched.c</font></div><div><font face=3D"= courier new, monospace">@@ -343,7 +343,7 @@ static const struct mframe_sche= d_item *sched_set_for_task[32] =3D {</font></div> <div><font face=3D"courier new, monospace">=A0/* encodes a channel number a= ccording to 08.58 Chapter 9.3.1 */</font></div><div><font face=3D"courier n= ew, monospace">=A0uint8_t mframe_task2chan_nr(enum mframe_task mft, uint8_t= ts)</font></div> <div><font face=3D"courier new, monospace">=A0{</font></div><div><font face= =3D"courier new, monospace">-<span class=3D"" style=3D"white-space:pre"> </= span>uint8_t cbits;</font></div><div><font face=3D"courier new, monospace">= +<span class=3D"" style=3D"white-space:pre"> </span>uint8_t cbits =3D 0;</f= ont></div> <div><font face=3D"courier new, monospace">=A0</font></div><div><font face= =3D"courier new, monospace">=A0<span class=3D"" style=3D"white-space:pre"> = </span>switch (mft) {</font></div><div><font face=3D"courier new, monospace= ">=A0<span class=3D"" style=3D"white-space:pre"> </span>case MF_TASK_BCCH_N= ORM:</font></div> <div><font face=3D"courier new, monospace">--=A0</font></div><div><font fac= e=3D"courier new, monospace">1.7.9</font></div><div><br></div></div> --047d7bdc15d456c2b204dd61e109--

1 0

Query on TPU doc
by Bhaskar11 18 May '13

18 May '13

The TPU Debugger code lists: static const char *tpu_addr_name[0x1f] = { [0] = "TSP_CTLR1", [1] = "TSP_CTRL2", [*4*] = "TSP_TX_*1*", [*3*] = "TSP_TX_*2*", [*2*] = "TSP_TX_*3*", [5] = "TSP_TX_4", [6] = "TSPACT_L", ...... Was wondering if the numbering is a typo. Could not find documentation online. Just bringing to your notice for check. Could you please confirm that items 2,3,4 are not supposed to be in sequence. Thanks. B.

2 1

Game Snake for OsmocomBB
by Marcel `sdrfnord` McKinnon 17 May '13

17 May '13

Hi everyone I have hacked the game Snake for OsmocomBB. It was mostly for my own education and I thought I make a short announcement on this list that such piece of code also exists. Feel free to play around with it and merge it in the project repository if you want. Code: https://github.com/sdrfnord/osmocom-bb/tree/sdrfnord/ui A picture of the game: http://www.flickr.com/photos/sdrfnord/8626533489/in/photostream I developed and tested it for the C121. During development I also implemented fb_set_p to set one pixel and fb_bw8_line to draw a line. (For the ST7558 LC Display Controller) The code for fb_bw8_line is copied from http://de.wikipedia.org/w/index.php?title=Bresenham-Algorithmus&stable=1#Ko… I hope this does not interfere with the GPL … Another thing I added is twl3025_power_off_now for a fast reboot which I used for development. -- Kind regards Marcel `sdrfnord` McKinnon

1 0

[osmocom] Fucking battery
by choukoumoun 14 May '13

14 May '13

Hello My Motorola batteries are all swollen and therefore defective. anyone has a solution for connecting to power directly to the battery connector by usb? I thought used a 3.7V zener diodes in parallel between the - and + USB power and a series resistor. Thank you.

4 6

Which is the best branch for running mobile on DP-L10?
by ubuntugirl 13 May '13

13 May '13

Hello, I have just got myself a Pirelli DP-L10, and I would like to use it to demonstrate OsmocomBB to my local LUG. I would like to demonstrate mobile, talking to layer1 via osmocon, making and receiving a voice call, sending and receiving SMS. I only have a few basic questions: - Should I use the master branch in osmocom-bb git, or one of the other branches? The Branches page in the wiki is blank. - Am I correct in my understanding that, at least in some branch (see above), osmocom-bb does support this phone well enough to actually make a call? (Yes, I realize that layers 2&3 run on an attached host, hence the phone has to be tethered to a laptop running osmocon and mobile the whole time, and I do know how to enable Tx in the target build. :) - How is the voice routing implemented? Do I need to use lcr integration on the host, or will the audio come out of the phone's own speaker even though all higher layers of the stack are running on the PC? If the voice call audio does go through the phone's own speaker and mic, which ones? This phone model has both an earpiece speaker and a loudspeaker, plus the usual analog headset jack. Which of these audio routing options are supported, if any? Thanks everyone for this awesome project! I can't wait to show it working to my LUG. Kim

5 6

Pirelli DPL-10 nuttx work in progress?
by Craig Comstock 04 May '13

04 May '13

Hi all, So now I have nuttx console working via IRDA on my Pirelli DPL-10 phone. Here are my next steps... I wanted to see if anyone else was working on these? - port the osmocom fb driver over to a nuttx lcd driver - get layer1 + some version of "mobile" working on the device - write a custom UI so this can be my daily driver - and in relation to the last item... send a finished phone w/ firmware to be certified by the FCC? http://transition.fcc.gov/oet/ea/procedures.html Does that sound about right? Anybody working on any of these bits? I'm not expecting this to happen overnight by any means... just expect it to be interesting and a good learning experience. Thanks, Craig

2 1

Pirelli DPL10 - nuttx and dump flash for restore later
by Craig Comstock 02 May '13

02 May '13

Hey folks, I got my Pirelli DPL10 yesterday and was able to get hello world, rssi, layer1 etc up and working pretty easily. It's quite a bit easier than the other phones I was trying to use with my RaspberryPi. I was wondering if someone could give me a nudge on how to get started getting nuttx working on this phone? Also I'd like to ask if there are directions somewhere on how to save the standard software presently on the phone so I can restore it later. I looked at osmoload but didn't quite understand what to do. finfo seemed to come back with all zeros for information and I confirmed that ping received a pong from the phone. My goal is to work towards using osmocom/nuttx to make this phone my daily use phone. Thanks, Craig

3 5

LOGP and Changes to lapdm.c and lapdm.h
by Arslan Anjum 28 Apr '13

28 Apr '13

Good evening all or whatever time it is there! 1. For debugging I have added a FILE* opf; member to lapdm_entity struct in lapdm.h But when I try to initialize this file pointer in mobile_init function in app_mobile.c I get a compile time error that lapdm_entity does not have a member named 'opf'. 2. When I declare the same member in osmocom_ms struct I don't get this error. 3. Furthermore, any changes I make to lapdm.c don't show up on runtime. I can quote specific examples but the mail would get long. Lastly is there any documentation on for LOGP and how to see it's different log levels. Regards, Arslan

2 4

cell_log + gsmmap = KML without positions
by Matthias Meisser 22 Apr '13

22 Apr '13

Hi list, sorry for abusing the list for a somewhat support request but unfortunatly I didn't got answers in the IRC. I'm interested to use BB for some experiments on mapping GSM cells (opencellid.org and similar). So I finally got cell_log to work and my general BB setup works fine here on my laptop. But even with a working GPS, I don't get any positions in the osmocom logfile or the resulting kml by gsmap. Here is what I do: I pair my Bluetooth GPS via sudo rfcomm connect /dev/rfcomm0 00:AA:BB:CC:DD:EE I test it via sudo cat /dev/rfcomm0 and it prints the usual NMEA stuff I connect my mobile C123 and fire up osmocon with L23: sudo ./osmocon -p /dev/ttyUSB0 -m c123xor '/home/matthias/opencellid/osmocom-bb/src/target/firmware/board/compal_e88/layer1.compalram.bin' After upload I start cell_log sudo ./cell_log -f /dev/rfcomm0 which looks ok: <0010> app_cell_log.c:216 Using GPS serial device /dev/rfcomm0 Failed to connect to '/tmp/osmocom_sap'. Failed during sap_open(), no SIM reader <000e> cell_log.c:804 Scanner initialized Mobile initialized, please start phone now! <000e> cell_log.c:368 Measure from 0 to 124 <000e> cell_log.c:368 Measure from 512 to 885 <000e> cell_log.c:368 Measure from 955 to 1023 <000e> cell_log.c:359 Measurement done <000e> cell_log.c:341 Sync ARFCN 17 (rxlev -59, 421 syncs left) <000e> cell_log.c:341 Sync ARFCN 675 (rxlev -62, 420 syncs left) <000e> cell_log.c:341 Sync ARFCN 85 (rxlev -65, 419 syncs left) <000e> cell_log.c:191 Cell: ARFCN=85 MCC=262 MNC=01 (Germany, T-Mobile) <000e> cell_log.c:341 Sync ARFCN 47 (rxlev -66, 418 syncs left) <000e> cell_log.c:191 Cell: ARFCN=47 MCC=262 MNC=01 (Germany, T-Mobile) <000e> cell_log.c:341 Sync ARFCN 6 (rxlev -73, 417 syncs left) <000e> cell_log.c:191 Cell: ARFCN=6 MCC=262 MNC=02 (Germany, Vodafone) <000e> cell_log.c:341 Sync ARFCN 75 (rxlev -73, 416 syncs left) <000e> cell_log.c:191 Cell: ARFCN=75 MCC=262 MNC=02 (Germany, Vodafone) <000e> cell_log.c:341 Sync ARFCN 671 (rxlev -73, 415 syncs left) <000e> cell_log.c:341 Sync ARFCN 22 (rxlev -75, 414 syncs left) <000e> cell_log.c:341 Sync ARFCN 25 (rxlev -75, 413 syncs left) <000e> cell_log.c:341 Sync ARFCN 20 (rxlev -77, 412 syncs left) <000e> cell_log.c:341 Sync ARFCN 90 (rxlev -78, 411 syncs left) But it doesn't write any positions at the logfile nor shows that it got a working GPS position. Only at a few starts I saw this line coming up: <000e> cell_log.c:804 Scanner initialized Mobile initialized, please start phone now! NMEA checksum error So I tried to set the baud rate but this message doesn't seem to be reproducable. Is there anything else I can do, or might it be some kind of software bug for my specific setup? cya, Matthias

1 0