Hello,
I'm currently trying to use a Pirelli DP-L10 calypso phone as a rudimentary BTS.
I have followed the instructions on http://openbsc.osmocom.org/trac/wiki/network_from_scratch, I'm using the jolly/testing branch of osmocom-bb and I've enabled TX support in the Makefile.
The software runs on an xubuntu 14.04 x64 machine.
After uploading the firmware to the phones RAM via osmocon, it shows that it's running osmocom-bb on the display, when I then try to run transceiver with the following parameters: -e 5 -r 99 (or alternativly -e 5 -a 958 to sync with german provider O2) the phone just reboots and goes into a state where the keyboard backlight is blinking with 0.5 hertz.
The last thing "transceiver" says is: <0012> l1ctl.c:383 Reset received: Starting sync. <000c> l1ctl.c:95 Sync Req <000c> l1ctl_link.c:171 Sending: '01 00 00 00 83 be 00 64 27 10 03 20 03 07 00 00 00 '
and the last log messages from osmocon are: DSP API Version: 0x3606 0x0000 LOST 7200! L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=33726, flags=0x7) Dropping sample ':'
I'm not sure if I have configured the correct bands for synchronization. I think it might have to do something with that. I copy'd the default configuration from the osmocom-page stating DCS1800. The only base station I'm seeing here is 958, which is in the GSM900R range. Could this be the problem?
Have I overseen something simple? Have I provided all necessary information about my setup? Any ideas?
It's probably not a power issue, I have tested it with a lab power supply for providing the USB 5V and battery 4.2V, which resulted in the same behavior.
Thanks, Tobias
Hi,
in response to my last email to the list, I got into contact with steve-m via another means of communication.
For future reference: osmocom-bb on the DP-L10 phone needs this patch to be successfully compiled on GCC newer then 4.8:
http://git.osmocom.org/osmocom-bb/commit/?id=a903b3c1ee27047c79728b18ff6340d...
The jolly/testing branch doesn't contain that fix. It can be added/hacked in via "git cherry-pick a903b3c1ee27047c79728b18ff6340d23d1aad2e"
Many thanks to steve-m for pointing me to this patch in his first response email and absolutly nailing the bug :)
So long, Tobias
baseband-devel@lists.osmocom.org