[Gsmmap] OsmocomBB compilation in MacOS

Lukas Kuzmiak lukash at backstep.net
Tue Jan 3 18:24:09 CET 2012


Hey Felipe and others,

I've tried osmocom on my mac os x 10.7 again and i'm not quite sure about
the results, I had to change the type from c123xor to c123 otherwise it
wouldn't init.

Please find the init log attached, the handle_write uploads the firmware in
much smaller blocks than in Linux, something's weird about it.

after running cell_log it saved some bursts but all of them have weird
sizes:

-rw-r--r--   1 lukash  staff    5500 Jan  3 18:18
230_1_4362_032D_20120003_1817_28_2479460_59.dat
-rw-r--r--   1 lukash  staff    1500 Jan  3 18:18
230_1_4362_032D_20120003_1818_28_2481354_41.dat
-rw-r--r--   1 lukash  staff    2100 Jan  3 18:18
230_1_4362_032D_20120003_1818_28_2482170_41.dat

I haven't seen such a precise sizes rounded like that.

If someone's experiencing some different results please let me know.

Cheers,
Lukas

On Sat, Dec 31, 2011 at 5:10 PM, Felipe Zimmerle <felipe at zimmerle.org>wrote:

> Hy Lukas,
>
> On Dec 31, 2011, at 11:52 AM, Lukas Kuzmiak wrote:
>
> I've tried this before (like couple of months) and found there is some
> problem with the serial port custom baudrates, I've managed to compile
> osmocom after all but it wasn't working fine.
>
> Does this setup you've described here capture the bursts alright?
>
>
> I did not tried yet, just compile it few minutes ago and shared the
> information. I don't have a compatible phone yet.
> Mine should arrive shortly.
>
> But I used the MacOS serial for various others proposes and it never
> disappointed me. The way that MacOS
> deals with custom boadrates of the serial ports is different from Linux, i
> was looking for the IOSSIOSPEED when
> i found out this patch:
>
>
> http://lists.osmocom.org/pipermail/baseband-devel/2011-September/002338.html
>
> It is was merged on the commit: 02d469ad67459c8d28c808a19802613a5666364c
> (2011 October 21). According to the author it should solve your problem.
>
> If you can test this newest version will be cool to have a response if it
> is really working or not :)
>
> Br.,
> F.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.srlabs.de/pipermail/gsmmap/attachments/20120103/ef1f18c8/attachment-0003.html>
-------------- next part --------------
Lukass-MacBook-Air:src lukash$ host/osmocon/osmocon -p /dev/tty.usbserial-FTTA1Z3BA -m c123 target/firmware/board/compal_e88/layer1.compalram.bin 
got 2 bytes from modem, data looks like: 04 81  ..
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/layer1.compalram.bin): file_size=48952, hdr_len=4, dnload_len=48959
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(): 1024 bytes (1024/48959)
handle_write(): 1024 bytes (2048/48959)
handle_write(): 1024 bytes (3072/48959)
handle_write(): 1024 bytes (4096/48959)
handle_write(): 1024 bytes (5120/48959)
handle_write(): 768 bytes (5888/48959)
handle_write(): 1024 bytes (6912/48959)
handle_write(): 768 bytes (7680/48959)
handle_write(): 1024 bytes (8704/48959)
handle_write(): 1024 bytes (9728/48959)
handle_write(): 1024 bytes (10752/48959)
handle_write(): 1024 bytes (11776/48959)
handle_write(): 768 bytes (12544/48959)
handle_write(): 1024 bytes (13568/48959)
handle_write(): 1024 bytes (14592/48959)
handle_write(): 1024 bytes (15616/48959)
handle_write(): 1024 bytes (16640/48959)
handle_write(): 1024 bytes (17664/48959)
handle_write(): 1024 bytes (18688/48959)
handle_write(): 1024 bytes (19712/48959)
handle_write(): 1024 bytes (20736/48959)
handle_write(): 1024 bytes (21760/48959)
handle_write(): 1024 bytes (22784/48959)
handle_write(): 768 bytes (23552/48959)
handle_write(): 1024 bytes (24576/48959)
handle_write(): 1024 bytes (25600/48959)
handle_write(): 1024 bytes (26624/48959)
handle_write(): 1024 bytes (27648/48959)
handle_write(): 1024 bytes (28672/48959)
handle_write(): 1024 bytes (29696/48959)
handle_write(): 1024 bytes (30720/48959)
handle_write(): 1024 bytes (31744/48959)
handle_write(): 1024 bytes (32768/48959)
handle_write(): 1024 bytes (33792/48959)
handle_write(): 768 bytes (34560/48959)
handle_write(): 1024 bytes (35584/48959)
handle_write(): 768 bytes (36352/48959)
handle_write(): 1024 bytes (37376/48959)
handle_write(): 1024 bytes (38400/48959)
handle_write(): 1024 bytes (39424/48959)
handle_write(): 1024 bytes (40448/48959)
handle_write(): 1024 bytes (41472/48959)
handle_write(): 1024 bytes (42496/48959)
handle_write(): 1024 bytes (43520/48959)
handle_write(): 1024 bytes (44544/48959)
handle_write(): 1024 bytes (45568/48959)
handle_write(): 1024 bytes (46592/48959)
handle_write(): 1024 bytes (47616/48959)
handle_write(): 1024 bytes (48640/48959)
handle_write(): 319 bytes (48959/48959)
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: 41  A
got 1 bytes from modem, data looks like: 03  .
got 1 bytes from modem, data looks like: 42  B
Received DOWNLOAD ACK from phone, your code is running now!


OSMOCOM Layer 1 (revision osmocon_v0.0.0-1204-g4464996-modified)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: bc420c1ef9039ba3
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
======================================================================
Power up simcard:


THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!!
Assert DSP into Reset
Releasing DSP from Reset
Installing DSP sniff patch
Setting some dsp_api.ndb values
Setting API NDB parameters
DSP Download Status: 0x0001
DSP API Version: 0x0000 0x0000
Finishing download phase
DSP Download Status: 0x0002
DSP API Version: 0x3606 0x0000
LOST 7411!


More information about the Gsmmap mailing list