evilgenius

I ran into some trouble when I tried to build osmocom under Mac OS X. This is how I made it work. Thanks to the guys at #osmocom.

First: Make sure the complete build environment comes from within one source. For example from MacPorts. You will need following packages:

• arm-elf-binutils
• arm-elf-gcc
• automake
• autoconf

Second: Make sure your $PATH variable includes the executable of your build environment. For MacPorts this is usually /opt/local/bin. The path for MacPorts executables should be before the path of the native Mac OS X executables to make sure MacPorts executables are used:
mort:osmocon martin$ echo $PATH
/Library/Frameworks/Python.framework/Versions/2.7/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin


Thats it. You now should be ready to compile your osmocom.

There have been some comments about bricked Bluetooth dongles after flashing Frontline firmware on it. FTE seems to have modified the firmware layout of the Frontline dongles which will leads to bricked Bluetooth dongles when you try to flash them with this firmware.

Till now I didn’t had the time to take a closer look on this. Anyway for unbricking your dongles have a look at this post. I used the SPI interface and a Bluetooth Casira Development board to unbrick the dongle. Unfortunately you need the quite expense develpment board and the software to fix the dongle, but in theory it should be possible to fix this with homebrew software and hardware.

If a have some free time during the next month I will take a closer look on this topic.