Hey there, I bumped into this error when testing gprsdecode from srldabs.de When I try the sample .dat files provided from srlabs.de it works fine though. Any hints?
Kind Regards
George AndguladzeSenior Software EngineerBusiness Management Technology
www.bmt.ge
Hey, I finally watched Nico's talk "let me answer that for you" and heard him say he ported layer2/3 to target.
Also found a mailing list message about him cleaning it up and putting it up on git and sending it to a few folks.
Did that code ever get shared? Would be cool to play around with and is certainly something I would eventually want to accomplish for my project of making a phone that works by itself.
-Craig
Dear all, I vae the C115 with a T1 USB to Serial cable with the Prolific
chipset.
When i run osmocon i get :- an its just sits there with no further
processing.
./osmocon -p /dev/ttyUSB0 -m c123xor
../../target/firmware/board/compal_e88/loader.compalram.bin
read_file(../../target/firmware/board/compal_e88/loader.compalram.bin):
file_size=17120, hdr_len=4, dnload_len=17127
read_file(../../target/firmware/board/compal_e88/loader.compalram.bin):
file_size=17120, hdr_len=4, dnload_len=17127
got 1 bytes from modem, data looks like: 00 .
got 2 bytes from modem, data looks like: 2f 00 /.
got 1 bytes from modem, data looks like: 1b .
got 3 bytes from modem, data looks like: f6 02 00 ...
got 1 bytes from modem, data looks like: 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
got 1 bytes from modem, data looks like: 66 f
got 1 bytes from modem, data looks like: 74 t
got 1 bytes from modem, data looks like: 6d m
got 1 bytes from modem, data looks like: 74 t
got 1 bytes from modem, data looks like: 6f o
got 1 bytes from modem, data looks like: 6f o
got 1 bytes from modem, data looks like: 6c l
Received FTMTOOL from phone, ramloader has aborted
got 1 bytes from modem, data looks like: 65 e
got 1 bytes from modem, data looks like: 72 r
got 1 bytes from modem, data looks like: 72 r
got 1 bytes from modem, data looks like: 6f o
got 1 bytes from modem, data looks like: 72 r
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 00 .
I think the cable is ok as when i run my fingers on the tip i get random
Zeros so it appears to be talking to the cable.
Also when i tried to run Mobile i get the :- even though i created the
Mobile.cfg file in /etc/osmoco
Failed to parse the config file: '/home/raz/.osmocom/bb/mobile.cfg'
Please check or create config file using: 'touch
/home/raz/.osmocom/bb/mobile.cfg'
I have spent some hours researching the lists and trying various things to
no avail but I want to continue until I resolve this issues and use this
great stack to learn about the GSM network.
Please advise.
Great full for any help or pointers but this maybe a timing issue that is
difficult to debug.
Thanks
Raz
hi,
i did a lot of resarch and testing on cell selection and re-selection
process the last two week.
the cell selection process, network selection process (manual and
automatic) and mobility management process were already implemented in
OsmocomBB a long time, but turned out to be buggy and incomplete. i made
test drives to check the process and debugged it.
the re-selection process is new. it is used to track surrounding cells
while listening to the BCCH of the current cell (camping on a cell).
special extension to the layer1 firmare is used to measure neighbour
cells. if an neighbour cell becomes 'better', the mobile switches to
that cell, depening on different criteria. now it is possible to move
with OsmocomBB.
the re-selection process is not handover! handover is a process where a
phone switches between cells while doing a call. handover is one next
step to implement. the process is a little more complex, because it
requires not only neighbour cell measurements, but also syncing to them
without interrupting the traffic channel. most layer 3 stuff of handover
is already implemented.
if you like to play and test your moving OsmocomBB, you can check out
the "jolly/roaming" branch. it contains the extension to layer1, as well
as sim reader and fixes from "sylvain/testing" branch. use both "mobile"
and "layer1" firmware from this branch.
in order to see some process at VTY, you can do:
enable
monitor network 1 (continously display the strongest cell and neighbour
cells)
show ms 1 (to see current states)
show neighbour-cells 1 (to see a more detailed current list of
neighbours)
andreas
Hi,
in the osmocom bb mobile.cfg I don't see any posibility to set a fixed
Kc encryption key and the tmsi.
How could I achieve that osmocom uses my defined Kc and tmsi?
cheers,
Simian
Hi all,
*I connected, sent and made call successful with osmocombb (with real IMSI
and IMEI).
But, now, I get error, always be rejected:*
OsmocomBB# show ms
MS '1' is up, service is limited
IMEI: 357337016773249
IMEISV: 3573370167732490
IMEI generation: fixed
automatic network selection state: A0 null
cell selection state: PLMN search
radio ressource layer state: idle
mobility management layer state: MM idle, PLMN search
OsmocomBB#
% (MS 1)
% Trying to registering with network...
*in my config file (/root/.osmocom/bb/mobile.cfg)**:*
!
! OsmocomBB () configuration saved from vty
!!
!
line vty
no login
!
gps device /dev/ttyACM0
gps baudrate default
no gps enable
!
no hide-default
!
ms 1
layer2-socket /tmp/osmocom_l2
sap-socket /tmp/osmocom_sap
sim reader
network-selection-mode auto
imei 357337016773249 0
imei-fixed
emergency-imsi 452040399998391
sms-service-center +84980200030
no call-waiting
no auto-answer
no force-rekey
no clip
no clir
tx-power auto
no simulated-delay
no stick
location-updating
neighbour-measurement
codec full-speed prefer
codec half-speed
no abbrev
support
sms
a5/1
a5/2
p-gsm
e-gsm
r-gsm
gsm-850
dcs
pcs
class-900 4
class-850 4
class-dcs 1
class-pcs 1
channel-capability sdcch+tchf+tchh
full-speech-v1
full-speech-v2
half-speech-v1
min-rxlev -106
dsc-max 90
no skip-max-per-band
exit
test-sim
imsi 001010000000000
ki xor 00 00 00 00 00 00 00 00 00 00 00 00
no barred-access
no rplmn
hplmn-search foreign-country
exit
no shutdown
exit
!
Anyone help me???, thanks a lot!
--
Thanks and Best Regards
--
From: Hoàng Mạnh Hùng
Hi,
I'm trying to run the latest osmocom-bb git on a Motorola C118 phone.
After a minor problem with the build (as you may've noticed in the
patch I've sent). I got to the point of successfuly running layer1 on
the phone and the mobile app on the PC (I have also enabled TX). The
process seems to be stuck on trying to perform a location update. The
status of the ms is always either:
show ms
MS '1' is up, MM connection active
IMEI: 000000000000000
IMEISV: 0000000000000000
IMEI generation: fixed
automatic network selection state: A1 trying RPLMN
MCC=104 MNC=002 (104, 002)
cell selection state: connected mode 1
ARFCN=19 MCC=104 MNC=002 LAC=0xb00f CELLID=0x4fd9
(104, 002)
radio ressource layer state: connection pending
mobility management layer state: wait for RR connection (location updating)
OsmocomBB>
or
show ms
MS '1' is up, service is limited (pending)
IMEI: 000000000000000
IMEISV: 0000000000000000
IMEI generation: fixed
automatic network selection state: A1 trying RPLMN
MCC=104 MNC=002 (104, 002)
cell selection state: C3 camped normally
ARFCN=19 MCC=104 MNC=002 LAC=0xb00f CELLID=0x4fd9
(104, 002)
radio ressource layer state: idle
mobility management layer state: MM idle, attempting to update
OsmocomBB>
I think, that because of this I can't make any calls or send sms (all
the requests are being rejected):
OsmocomBB# call 1 <X>
call 1 <X>
OsmocomBB#
% (MS 1)
% Call has been rejected
The log information from mobile when it's trying to do a location
update is show below:
<000b> gsm48_rr.c:2174 PAGING REQUEST 1
<000b> gsm48_rr.c:2141 IMSI 260021964220249 (not for us)
<000b> gsm48_rr.c:2132 TMSI fd82a501 (not for us)
<000e> gsm48_mm.c:344 Location update retry
<0005> gsm48_mm.c:345 timer T3211 (loc. upd. retry delay) has fired
<0005> gsm48_mm.c:4311 (ms 1) Received 'MM_EVENT_TIMEOUT_T3211' event
in state MM IDLE, attempting to update
<000e> gsm48_mm.c:2199 Perform location update (MCC 104, MNC 002 LAC 0xb00f)
<0005> gsm48_mm.c:2333 LOCATION UPDATING REQUEST
<0005> gsm48_mm.c:2355 using LAI (mcc 104 mnc 002 lac 0xb00f)
<0005> gsm48_mm.c:2363 using TMSI 0x28a3d62e
<0005> gsm48_mm.c:914 new state MM IDLE, attempting to update -> wait
for RR connection (location updating)
<0001> gsm48_rr.c:5428 (ms 1) Message 'RR_EST_REQ' received in state
idle (sapi 0)
<000e> gsm48_rr.c:1318 Establish radio link due to mobility management request
<0003> gsm322.c:4037 (ms 1) Event 'EVENT_LEAVE_IDLE' for Cell
selection in state 'C3 camped normally'
<0003> gsm322.c:823 new state 'C3 camped normally' -> 'connected mode 1'
<0003> gsm322.c:3653 Going to camping (normal) ARFCN 19.
<0003> gsm322.c:463 Sync to ARFCN=19 rxlev=-74 (Sysinfo, ccch mode NON-COMB)
<0001> gsm48_rr.c:366 new state idle -> connection pending
<0001> gsm48_rr.c:1465 CHANNEL REQUEST: 00 (Location Update with NECI)
<0003> gsm322.c:2938 Channel synched. (ARFCN=19, snr=16, BSIC=17)
<0001> gsm322.c:2959 using DSC of 90
<0003> gsm48_rr.c:4816 Channel provides data.
<0001> gsm48_rr.c:1601 RANDOM ACCESS (requests left 5)
<0001> gsm48_rr.c:1658 RANDOM ACCESS (Tx-integer 50 combined no
S(lots) 0 ra 0x0e)
<0001> gsm48_rr.c:1697 Use MS-TXPWR-MAX-CCH power value 5 (33 dBm)
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:1601 RANDOM ACCESS (requests left 4)
<0001> gsm48_rr.c:1658 RANDOM ACCESS (Tx-integer 50 combined no
S(lots) 55 ra 0x07)
<0001> gsm48_rr.c:1697 Use MS-TXPWR-MAX-CCH power value 5 (33 dBm)
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2462 (ta 2/1107m ra 0x75 chan_nr 0x0a MAIO 0 HSN 38
TS 2 SS 0 TSC 0)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2462 (ta 2/1107m ra 0x75 chan_nr 0x0a MAIO 0 HSN 38
TS 2 SS 0 TSC 0)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-78 snr= 0 ber= 0 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:1601 RANDOM ACCESS (requests left 3)
<0001> gsm48_rr.c:1658 RANDOM ACCESS (Tx-integer 50 combined no
S(lots) 55 ra 0x0f)
<0001> gsm48_rr.c:1697 Use MS-TXPWR-MAX-CCH power value 5 (33 dBm)
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:1601 RANDOM ACCESS (requests left 2)
<0001> gsm48_rr.c:1658 RANDOM ACCESS (Tx-integer 50 combined no
S(lots) 55 ra 0x01)
<0001> gsm48_rr.c:1697 Use MS-TXPWR-MAX-CCH power value 5 (33 dBm)
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473 (ta 1/553m ra 0x18 chan_nr 0x59 ARFCN 19 TS 1
SS 3 TSC 1)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473 (ta 1/553m ra 0x18 chan_nr 0x59 ARFCN 19 TS 1
SS 3 TSC 1)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:1601 RANDOM ACCESS (requests left 1)
<0001> gsm48_rr.c:1658 RANDOM ACCESS (Tx-integer 50 combined no
S(lots) 55 ra 0x0a)
<0001> gsm48_rr.c:1697 Use MS-TXPWR-MAX-CCH power value 5 (33 dBm)
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-78 snr= 0 ber= 1 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:1601 RANDOM ACCESS (requests left 0)
<0001> gsm48_rr.c:1605 Done with sending RANDOM ACCESS bursts
<0001> gsm48_rr.c:836 starting T3126 with 5.000 seconds
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2225 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-78 snr= 0 ber= 0 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473 (ta 2/1107m ra 0x0a chan_nr 0x41 ARFCN 19 TS 1
SS 0 TSC 1)
<0001> gsm48_rr.c:2393 request 0a matches but not frame number
(IMM.ASS fn=22,6,30 != RACH fn=22,5,25)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473 (ta 2/1107m ra 0x05 chan_nr 0x49 ARFCN 19 TS 1
SS 1 TSC 1)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473 (ta 2/1107m ra 0x05 chan_nr 0x49 ARFCN 19 TS 1
SS 1 TSC 1)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2225 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-77 snr= 0 ber= 6 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473 (ta 2/1107m ra 0x00 chan_nr 0x61 ARFCN 19 TS 1
SS 4 TSC 1)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2473 (ta 2/1107m ra 0x00 chan_nr 0x61 ARFCN 19 TS 1
SS 4 TSC 1)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2462 (ta 2/1107m ra 0x7d chan_nr 0x0b MAIO 0 HSN 38
TS 3 SS 0 TSC 0)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2462 (ta 2/1107m ra 0x7d chan_nr 0x0b MAIO 0 HSN 38
TS 3 SS 0 TSC 0)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-78 snr= 0 ber= 0 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2225 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2225 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-78 snr= 0 ber= 3 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2462 (ta 2/1107m ra 0x77 chan_nr 0x09 MAIO 0 HSN 38
TS 1 SS 0 TSC 0)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2450 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2462 (ta 2/1107m ra 0x77 chan_nr 0x09 MAIO 0 HSN 38
TS 1 SS 0 TSC 0)
<0001> gsm48_rr.c:2503 Request, but not for us.
<0001> gsm48_rr.c:2225 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:2170 PAGING ignored, we are not camping.
<0001> gsm48_rr.c:673 MON: f=19 lev=-78 snr= 0 ber= 6 LAI=104 002 b00f ID=4fd9
<0001> gsm48_rr.c:765 timer T3126 has fired
<000e> gsm48_rr.c:770 Requesting channel failed
<0001> gsm48_rr.c:366 new state connection pending -> idle
<0003> gsm322.c:4037 (ms 1) Event 'EVENT_RET_IDLE' for Cell selection
in state 'connected mode 1'
<0003> gsm322.c:3565 Selecting ARFCN 19. after LOC.UPD.
<0003> gsm322.c:463 Sync to ARFCN=19 rxlev=-74 (Sysinfo, ccch mode NON-COMB)
<0003> gsm322.c:823 new state 'connected mode 1' -> 'C3 camped normally'
<0005> gsm48_mm.c:3902 (ms 1) Received 'RR_REL_IND' from RR in state
wait for RR connection (location updating) (sapi 0)
<0005> gsm48_mm.c:2732 RR link released after loc. upd.
<000e> gsm48_mm.c:2676 Location update failed
<000e> gsm48_mm.c:2686 Try location update later
<0005> gsm48_mm.c:2688 Loc. upd. failed, retry #0
<0005> gsm48_mm.c:413 starting T3211 (loc. upd. retry delay) with 15.0 seconds
<0005> gsm48_mm.c:1143 We are camping normally as returning to MM IDLE
<0005> gsm48_mm.c:1159 Loc. upd. allowed.
<0005> gsm48_mm.c:919 new state wait for RR connection (location
updating) -> MM IDLE, location updating needed
<0005> gsm48_mm.c:909 new MM IDLE state location updating needed ->
attempting to update
<0005> gsm48_mm.c:2215 Loc. upd. already pending.
<0005> gsm48_mm.c:4311 (ms 1) Received 'MM_EVENT_CELL_SELECTED' event
in state MM IDLE, attempting to update
<0005> gsm48_mm.c:2215 Loc. upd. already pending.
<0003> gsm322.c:2938 Channel synched. (ARFCN=19, snr=16, BSIC=17)
<0001> gsm322.c:2959 using DSC of 90
Can you provide me any hints on how to debug this ? Why is the
location update failing constantly ?
Thanks in advance for your help.
Best regards,
Maciej Grela
Hi All
Just wanted to confirm that I got Osmocom-BB up and running on a Raspberry Pi.
I did not use the GPIO UART pins but USB <-> serial converters.
I tried Motorola C118 and C155 with success.
Everything you need is already described:
http://bb.osmocom.org/trac/wiki/GnuArmToolchainhttp://bb.osmocom.org/trac/wiki/libosmocorehttp://bb.osmocom.org/trac/wiki/Software/GettingStarted?redirectedfrom=Gett…
My previous problem seems to have been a not fully compatible crosscompiled toolchain. (it worked mostly, but I could not log-in to a cell and the spectrum view crashed on the RSSI Firmware.
Also if you want transmit capability (or flashing) then you need to activate those features in the makefile.
Thanks Sylvain (confirming c118 will work) and all others who are involved!!
PS: Any news on the "emulated BTS" that has been presented at last years chaos communication congress?
I have 2 C118s + 1 normal USB serial dongle + 1 capable of burst ind.
I hope this will suffice to also run also a possible future 1 trasmit phone + 1 receive phone configuration.
I assume that even without the filter change it should be enough to send a few meters of distance.
I'm at the point w/ flashing firmware where I feel like I need to use a debugger w/ JTAG. I figured I could probably use serial line logging somehow but JTAG seems better and I should learn it anyway.
Has anyone pried open the shield on a c139/c140 and tried attaching to the JTAG test points that are just inside the shield next to the test points which are accessible via the battery compartment?
Attached is simple patch which adds little-endian & big-endian macro to move bytes to
and from multibyte integer types like uint16_t, uint32_t etc.
Some of this code is used right away in msgb.h but it will also be used in kasumi
implementation later on.
--
best regards,
Max, http://fairwaves.ru
Hello.
Attached is a trivial patch which breaks existing GPRS cipher API of libosmocore by
switching from fixed 64-bit length Kc to variable-length.
There are several justifications for that:
- compliance with ETSI TS 155.22 (GEA4 - 128 bits Kc) and all further versions
- similarity to existing auth api (osmocom/crypt/auth.h uses 128 bits as well)
- nobody uses this API anyway (except my other patches with GEA)
- patch breaks nothing within libosmocore (make check succeeds) and openbsc (uses
gea0 only)
That's why I think next libosmocore version should apply this patch and change unused
API before someone actually start using it and makes transition more difficult.
--
best regards,
Max, http://fairwaves.ru
Hello dear osmocom team
first off, thanks for all the work you have
put into this project. Its great to have a starting
point for toying with this new/old technology. ;)
I got myself a C155 and have used osmocom-bb on it
to read some traffic with wireshark. So far everything
works nicely.
Now i wanted to communicate with a second phone and
have tried setting up a BTS following this guide
http://openbsc.osmocom.org/trac/wiki/network_from_scratch
(using a single phone)
My problem is that the phone doesnt transmit anything.
Yes i have enabled the transmitter flag in the Makefile. ;)
When i use osmocon to load the TRX into the phone and start the
osmocom-transceiver i get this debug output from osmocon.
...
Synchronize_TDMA
=>FB @ FNR 26585 fn_offset=2002505 qbits=4924
LOST 1910!
BTS MODE: 255 65535 {0,0,0,0,0,0,0,0} TX 0..7 RX 0..7
After taking a look at the code the values seem weird
and they come from the transceiver function l1ctl_tx_bts_mode()
like that.
/host/layer23/src/transceiver/l1ctl.c:120
As a test i got the phone to transmit something by
overwriting the values on the TRX side.
I havent gone further yet but wanted to ask if someone could
maybe point me to an obvious mistake i did before i
spend more hours on this issue.
A hint as to how i enable the different logging settings
would be great as well.
thanks,
best regards, Christian
Hi everyone,Now I am facing some unknown problem to me.
I am getting the following error messages
(1) on the terminal after uploading layer1:
Failed to write msg to the socket(2) failed to connect to '/tmp/osmocom_sap'
Failed during sap_open (), no SIM reader
<000c> l1ctl.c:118 FBSB RESP: result=255
<000f> sim.c:858 received APDU but no job, please fixShall anyone tell me where I am doing wrong?
What exactly is the problem. Because earlier when I run mobile application then it was working well.Thanks in advance.NeeteshSent from RediffmailNG on Android
From: "neetesh saxena"saxenaneetesh061(a)rediffmail.com
Sent:Wed, 22 Jan 2014 16:51:45 +0530
To: "baseband-devel " baseband-devel(a)lists.osmocom.org
Subject: Query regarding running osmoocomBB
Hi everyone,
>
>Here, i wish to know the answer of a basic question. When I uploaded the firmware onto the mobile phone (with ./osmocon command), I can start other application programs like CCCh program, mobile program in other terminals.
>
>My problem is when I am doing it I can see that the layer1 is uploaded onto the phone but I am not able to switch on my phone. When I again press the red button to start phone, it again starts getting uploaded layer1.
>
>When I terminate the command of uploading firmware and start my phone then I am not able to view of SIM details and it shows me "service is unavailable" or "administratively down".
>
>My question is we need to continue run the terminal with ./osmocon command (for uploading layer1) or i need to stop it after uploading layer1 once onto the phone. When to switched on my phone ?
>
>
>With regards
> Neetesh Saxena...
>
>
>
>Get your own FREE website, FREE domain & FREE mobile app with Company email. Know More >
neetesh saxena wrote:
> My question is we need to continue run the terminal with ./osmocon
> command (for uploading layer1)
Yes.
> or i need to stop it after uploading layer1 once onto the phone.
No.
> When to switched on my phone ?
If layer1 is successfully uploaded then the phone is already switched on.
Just start the layer23 (mobile, ccch_scan, etc..) program on the host.
//Peter
Hi everyone,
Here, i wish to know the answer of a basic question. When I uploaded the firmware onto the mobile phone (with ./osmocon command), I can start other application programs like CCCh program, mobile program in other terminals.
My problem is when I am doing it I can see that the layer1 is uploaded onto the phone but I am not able to switch on my phone. When I again press the red button to start phone, it again starts getting uploaded layer1.
When I terminate the command of uploading firmware and start my phone then I am not able to view of SIM details and it shows me "service is unavailable" or "administratively down".
My question is we need to continue run the terminal with ./osmocon command (for uploading layer1) or i need to stop it after uploading layer1 once onto the phone. When to switched on my phone ?
With regards
Neetesh Saxena...
Dear all,
so far the osmocom.org mailing lists have always been in a 'non-members
are manually moderated' mode. This has created a lot of work for manual
list moderation, where a lot of the messages caught are simply spam, and
only the occasional valid message is being received.
I'd like to thank the list moderators for taking care of this.
However, in more recent discussions, we were considering to move the
lists to a completely closed mode, i.e. postings would automatically be
rejected from non-members.
The automatic response would contain a description of how to subscribe
in 'nomail' mode, i.e. to subscribe in a way to be able to post to the
list, while still not receiving any incoming traffic. The latter should
be fine for occasional posters who don't want the bulk e-mail that goes
with a full/regular subscription.
Please provide feedback in case you disagree with that change. Unless
there is major opposition, we will likely transition to the 'closed'
mode within one month.
Thanks,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi.
While looking at osmocom-bb compilation warnings I've noticed that there are plenty
of those cause by signed-unsigned comparison with msgb-related functions. Attached is
a trivial patch which fixes that by changing int -> uint16_t. For the sake of
completeness I've also changed other functions to explicitly use uint16_t - this is
used for length fields in "struct msgb" anyway.
Although technically it's API change I do not expect any sane code to break. If you
still think it's potentially insecure, this could be applied during next api version
bump alongside with gprs api change.
--
best regards,
Max, http://fairwaves.ru
---
include/osmocom/core/msgb.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/osmocom/core/msgb.h b/include/osmocom/core/msgb.h
index fe2733b..5610a22 100644
--- a/include/osmocom/core/msgb.h
+++ b/include/osmocom/core/msgb.h
@@ -147,7 +147,7 @@ static inline unsigned int msgb_headlen(const struct msgb *msgb)
* This function computes the amount of octets left in the underlying
* data buffer after the end of the message.
*/
-static inline int msgb_tailroom(const struct msgb *msgb)
+static inline unsigned int msgb_tailroom(const struct msgb *msgb)
{
return (msgb->head + msgb->data_len) - msgb->tail;
}
@@ -159,7 +159,7 @@ static inline int msgb_tailroom(const struct msgb *msgb)
* This function computes the amount of bytes left in the underlying
* data buffer before the start of the actual message.
*/
-static inline int msgb_headroom(const struct msgb *msgb)
+static inline unsigned int msgb_headroom(const struct msgb *msgb)
{
return (msgb->data - msgb->head);
}
--
1.8.3.2
--------------070704060003090203050700--
Hi all.
I'd like to see osmocom-bb builds less cluttered by compiler warnings - attached is
(far from complete) attempt to do so. It's tested which means it builds on my machine
and resulting mobile app seems to run fine - no in-depth testing were made.
However I'd like to get some feedback before going further: there seems to be some
evil hackery happening around src/target/firmware/apps/loader/main.c:
Why do we have external "unsigned char _start" which later used as msgb_put_u32(msg,
&_start);
Do we make some assumptions on the size of unsigned char? Is this documented
somewhere by any chance?
Also there are plenty of warnings regarding alignment: some things are marked as
"__attribute__ ((packed))" and some are not which seems to make compiler unhappy. Is
there rule of thumb to decide when we should care about alignment?
--
best regards,
Max, http://fairwaves.ru
Hi,
I am cleaning up my office and would like to get rid of a R&S CTS55.
The device powers up but I have never used it for any development. It
is currently located in Germany and before posting it on eBay I would
be happy to give it someone involved/intersted in the OsmocomBB project.
Please contact me off list in case you would like to have it.
holger
Hi everyone,
I m receiving the following errors:
(I am using the "Ja! Mobil" SIM card with Motorola C118)
root@neetesh-VirtualBox:/opt/osmocom-bb/src/host/osmocon# telnet localhost 4247
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Welcome to the OsmocomBB control interface
OsmocomBB> en
OsmocomBB# conf t
OsmocomBB(config)# ms 1
OsmocomBB(ms)#no shutdown
OsmocomBB(ms)#en
OsmocomBB# write
Configuration saved to /home/neetesh/.osmocom/bb/mobile.cfg
OsmocomBB# show ms 1
MS '1' is down, radio is not started
IMEI: 000000000000000
IMEISV: 0000000000000000
IMEI generation: fixed
automatic network selection state: A0 null
cell selection state: C0 null
radio ressource layer state: idle
mobility management layer state: MM idle, PLMN search
OsmocomBB# show subs 1
Mobile Subscriber of MS '1':
No SIM present.
OsmocomBB# sim read 1
OsmocomBB# show subs
Mobile Subscriber of MS '1':
IMSI:
Status: U2_NOT_UPDATED IMSI detached LAI: invalid
Access barred cells: no
Access classes:
Can anyone tell me whether the problem is related to SIM card or it is related to phone?
Do you have any clue how to fix it?
I tried to fix the patch of SIM, but then I am not able to compile source (errors occurred).
Please let me know your views.
regards,
neetesh
On Thu, Jan 09, 2014 at 04:00:27PM -0000, neetesh saxena wrote:
> Thanks for your help. Now I am able to compile and run the source of
> osmocmBB. The problem was I had not installed toolchain as a root.
Great that it works now.
Just as a side note:
It is not necessary to perform any operation as root.
I assume you installed the toolchain in /usr/local or so which is not
writable as a normal user.
You can have e.g. a ~/install and then add $HOME/install/bin to your
path.
Kind regards,
-Alex
Hi everyone,
Thanks for your help. Now I am able to compile and run the source of osmocmBB.
The problem was I had not installed toolchain as a root.
But unfortunately, now I m receiving the same error as I was getting earlier which is as follows:
(I am using the "Ja! Mobil" SIM card)
root@neetesh-VirtualBox:/opt/osmocom-bb/src/host/osmocon# telnet localhost 4247
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Welcome to the OsmocomBB control interface
OsmocomBB> en
OsmocomBB# conf t
OsmocomBB(config)# ms 1
OsmocomBB(ms)#no shutdown
OsmocomBB(ms)#en
OsmocomBB# write
Configuration saved to /home/neetesh/.osmocom/bb/mobile.cfg
OsmocomBB# show ms 1
MS '1' is down, radio is not started
IMEI: 000000000000000
IMEISV: 0000000000000000
IMEI generation: fixed
automatic network selection state: A0 null
cell selection state: C0 null
radio ressource layer state: idle
mobility management layer state: MM idle, PLMN search
OsmocomBB# show subs 1
Mobile Subscriber of MS '1':
No SIM present.
OsmocomBB# sim read 1
OsmocomBB# show subs
Mobile Subscriber of MS '1':
IMSI:
Status: U2_NOT_UPDATED IMSI detached LAI: invalid
Access barred cells: no
Access classes:
I tried the patches SIM in the firmware provided by Lukas Kuzmiak available at :
http://baseband-devel.722152.n3.nabble.com/patches-for-SIM-in-the-firmware-…
But in my first attempt I am getting some error in l23_api.c while I am compileing the osmocomBB source because I think when I am changing the code then I need to recompile and run it.
Didi anyone help me on this? Has anybody used this patch earlier?
Am i doing something wrong?
With regards
Neetesh Saxena...
Hi everyone,
I installed a fresh Ubuntu and then installed everything related to osmocomBB.
I have added path of arm-elf-gcc using export PATh=$PATH:<path>/install/bin
and also added in bashrc file.
Now when I am compiling it I am receiving the same errors:
/home/saxena/osmocom-bb/src/target/firmware/include/asm/swab.h:
Assembler messages:
/home/saxena/osmocom-bb/src/target/firmware/include/asm/swab.h:32:
Error: no such instruction: `eor %edx,%ecx,%ecx,ror'
make[4]: *** [gsmtap_util.lo] Error 1
make[4]: Leaving directory
`/home/saxena/osmocom-bb/src/shared/libosmocore/build-target/src'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/home/saxena/osmocom-bb/src/shared/libosmocore/build-target/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/saxena/osmocom-bb/src/shared/libosmocore/build-target'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/saxena/osmocom-bb/src/shared/libosmocore/build-target'
make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] Error 2
Can anybody tell me where I am wrong?
With regards
Neetesh Saxena...
On Tue, Jan 07, 2014 at 03:48:21PM -0000, neetesh saxena wrote:
> Hi,
>
> Thanks for your help. But it didn't work for me.
well, it builds on the jenkins[1]. And your error is typical for someone
having compiled parts without the toolchain in the path, getting this
compiler issue, then trying to set path.. but it is too late. it really
is. You need to clean the tree.
[1] http://jenkins.osmocom.org/jenkins/view/OsmocomBB/job/OsmocomBB/
Hi,
Thanks for your help. But it didn't work for me.
With regards
Neetesh Saxena...
From: Holger Hans Peter Freyther <holger(a)freyther.de>
Sent: Tue, 07 Jan 2014 16:16:54
To: neetesh saxena <saxenaneetesh061(a)rediffmail.com>
Cc: baseband-devel <baseband-devel(a)lists.osmocom.org>rg>, Steve Markgraf <steve(a)steve-m.de>
Subject: Re: Osmocom: assembler errors (swab.h)
On Tue, Jan 07, 2014 at 10:33:00AM -0000, neetesh saxena wrote:
> Hi,
Hi,
>
> I have tried everything which I can.
> I removed the installtion (dependencies) and libosmocore, osmocom-bb, gnu-arm.
>
> Now I have installed again all.
> I added the PATH to bashrc (by opening it and paste the path) along with typing it on terminal (as suggested on wiki osmocom-bb). But I am still getting the error.
>
> "swab.h:32: error: no such instruction: 'eor %edx, %ecx, %ecx, ror'" and
> "osmocom-bb/src/shared/libosmocore/build-target/src"
$ git clean -dxf .
make sure your cross compiler is in the toolchain
build again
On Tue, Jan 07, 2014 at 10:33:00AM -0000, neetesh saxena wrote:
> Hi,
Hi,
>
> I have tried everything which I can.
> I removed the installtion (dependencies) and libosmocore, osmocom-bb, gnu-arm.
>
> Now I have installed again all.
> I added the PATH to bashrc (by opening it and paste the path) along with typing it on terminal (as suggested on wiki osmocom-bb). But I am still getting the error.
>
> "swab.h:32: error: no such instruction: 'eor %edx, %ecx, %ecx, ror'" and
> "osmocom-bb/src/shared/libosmocore/build-target/src"
$ git clean -dxf .
make sure your cross compiler is in the toolchain
build again
Hi,
I have tried everything which I can.
I removed the installtion (dependencies) and libosmocore, osmocom-bb, gnu-arm.
Now I have installed again all.
I added the PATH to bashrc (by opening it and paste the path) along with typing it on terminal (as suggested on wiki osmocom-bb). But I am still getting the error.
"swab.h:32: error: no such instruction: 'eor %edx, %ecx, %ecx, ror'" and
"osmocom-bb/src/shared/libosmocore/build-target/src"
any suggestion on it?
With regards
Neetesh Saxena...
From: Steve Markgraf <steve(a)steve-m.de>
Sent: Mon, 06 Jan 2014 00:21:23
To: neetesh saxena <saxenaneetesh061(a)rediffmail.com>om>, Andreas Eversberg <andreas(a)eversberg.eu>
Cc: baseband-devel <baseband-devel(a)lists.osmocom.org>
Subject: Re: Osmocom: assembler errors (swab.h)
Hi,
On 05.01.2014 10:03, neetesh saxena wrote:
> I have already set the path of arm-elf-gcc.
> But I am still getting the same error. Is there any command or procedure
> by which I can completely remove this installation so that I can try as
> a fresh one.
> _Neetesh_
If you tried building without the toolchain in place, you have to do a
fresh clone of the git repo, or make sure to delete everything that
automake and gcc created.
Regards,
Steve
Hi,
On 05.01.2014 10:03, neetesh saxena wrote:
> I have already set the path of arm-elf-gcc.
> But I am still getting the same error. Is there any command or procedure
> by which I can completely remove this installation so that I can try as
> a fresh one.
> _Neetesh_
If you tried building without the toolchain in place, you have to do a
fresh clone of the git repo, or make sure to delete everything that
automake and gcc created.
Regards,
Steve
neetesh saxena wrote:
> */home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/asm/swab.h:32:
> Error: no such instruction: `eor %edx,%ecx,%ecx,ror'*
hi,
are your arm-elf-* executables inside your path?
my executables are inside /usr/bin:
$ which arm-elf-gcc
/usr/bin/arm-elf-gcc
you can add the location of your path using:
export PATH="$PATH:/your/location"
regards,
andreas
what menu.e88loader.bin: No such file or directoryI refer to this article
:http://bb.osmocom.org/trac/wiki/flashing_newBut why can't find
menu.e88loader.bin??Does anyone know?thanks
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/what-menu-e88loader-bin-No-such-…
Sent from the baseband-devel mailing list archive at Nabble.com.
Can anyone help me what to do?
the phone is bricked.C118,I want to brush through the jtag line into the
bootloader,Feasible?
But I can't find the instructions about C118 pin.
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/C118-JTAG-tp4026286.html
Sent from the baseband-devel mailing list archive at Nabble.com.
This is a Mailman mailing list bounce action notice:
List: baseband-devel
Member: luca.bongiorni1(a)studenti.unimi.it
Action: Subscription disabled.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
mailman(a)lists.osmocom.org.
Hi,
I am using Ubuntu 32 bit OS with C118 Motorola phone.
You have written "remember to use 64." in your blog, however you use Kali OS.
Does it mean that osmocom doesn't support 32 bit Ubuntu?
Do I need to switch on 64 bits OS?
With regards
Neetesh Saxena...
From: "LSX" <289039690(a)qq.com>
Sent: Fri, 03 Jan 2014 09:12:06
To: "neetesh saxena" <saxenaneetesh061(a)rediffmail.com>
Subject: 回复：Osmocom: assembler errors (swab.h)
你用的什么系统啊，有些系统好像是有这个问题，好像是版本的问题，不能用太新的版本我用的是kali 64 不存在这个问题还有我的博客 你可以参照一下：blog.lishixin.net
------------------ 原始邮件 ------------------发件人: "neetesh saxena";<saxenaneetesh061@rediffmail.com>;发送时间: 2014年1月2日(星期四) 晚上9:20收件人: "baseband-devel "<baseband-devel(a)lists.osmocom.org>rg>; 主题: Osmocom: assembler errors (swab.h)
Hi everyone,
Next time when I am trying to compile osmocom-bb source using "make" command it is showing two errors.
Even I have removed the complete directory where I had put osmocom-bb, toolchain, libosmocore. I tried two times as a fresh installation but still I am getting the errors.
Can anyone help me what to do? The details of the commands and the generated errors are as:
neetesh@neetesh-VirtualBox:~/GSMP$ git clone git://git.osmocom.org/osmocom-bb.git
Cloning into 'osmocom-bb'...
remote: Counting objects: 19471, done.
remote: Compressing objects: 100% (6037/6037), done.
remote: Total 19471 (delta 13610), reused 18108 (delta 12508)
Receiving objects: 100% (19471/19471), 3.37 MiB | 1.07 MiB/s, done.
Resolving deltas: 100% (13610/13610), done.
neetesh@neetesh-VirtualBox:~/GSMP$ cd osmocom-bb/
neetesh@neetesh-VirtualBox:~/GSMP/osmocom-bb$ git pull --rebase
Current branch master is up to date.
neetesh@neetesh-VirtualBox:~/GSMP/osmocom-bb$ cd src/
neetesh@neetesh-VirtualBox:~/GSMP/osmocom-bb/src$ sudo make
cd shared/libosmocore && autoreconf -fi
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./config.guess'
libtoolize: copying file `./config.sub'
libtoolize: copying file `./install-sh'
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
configure.ac:5: installing `./missing'
src/Makefile.am: installing `./depcomp'
mkdir shared/libosmocore/build-target
cd shared/libosmocore/build-target && ../configure \
--host=arm-none-eabi --enable-embedded --disable-shared \
--disable-tests ac_cv_header_sys_select_h=no \
--disable-tests ac_cv_header_sys_socket_h=no \
CFLAGS="-Os -ffunction-sections -I/home/neetesh/GSMP/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs"
configure: WARNING: unrecognized options: --disable-tests, --disable-tests
configure: WARNING: if you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-none-eabi-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make sets $(MAKE)... (cached) yes
checking for arm-none-eabi-gcc... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu
checking host system type... arm-none-eabi
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... no
checking for arm-none-eabi-dumpbin... no
checking for arm-none-eabi-link... no
checking for dumpbin... no
checking for link... link -dump
configure: WARNING: using cross tools not prefixed with host triplet
checking the name lister (nm) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 805306365
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-linux-gnu file names to arm-none-eabi format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for arm-none-eabi-objdump... no
checking for objdump... objdump
checking how to recognize dependent libraries... unknown
checking for arm-none-eabi-dlltool... no
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for arm-none-eabi-ar... no
checking for ar... ar
checking for archiver @FILE support... @
checking for arm-none-eabi-strip... strip
checking for arm-none-eabi-ranlib... no
checking for ranlib... ranlib
checking command to parse nm output from gcc object... ok
checking for sysroot... no
checking for arm-none-eabi-mt... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... no
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for ANSI C header files... (cached) yes
checking execinfo.h usability... yes
checking execinfo.h presence... yes
checking for execinfo.h... yes
checking for sys/select.h... (cached) no
checking for sys/socket.h... (cached) no
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking for size_t... yes
checking for working alloca.h... no
checking for alloca... no
checking whether `alloca.c' needs Cray hooks... no
checking stack direction for C alloca... 0
checking for library containing dlopen... -ldl
checking for doxygen... false
checking if gcc supports -fvisibility=hidden... yes
checking whether struct tm has tm_gmtoff member... no
configure: creating ./config.status
config.status: creating libosmocore.pc
config.status: creating libosmocodec.pc
config.status: creating libosmovty.pc
config.status: creating libosmogsm.pc
config.status: creating libosmogb.pc
config.status: creating include/Makefile
config.status: creating src/Makefile
config.status: creating src/vty/Makefile
config.status: creating src/codec/Makefile
config.status: creating src/gsm/Makefile
config.status: creating src/gb/Makefile
config.status: creating tests/Makefile
config.status: creating utils/Makefile
config.status: creating Doxyfile.core
config.status: creating Doxyfile.gsm
config.status: creating Doxyfile.vty
config.status: creating Doxyfile.codec
config.status: creating Makefile
config.status: creating config.h
config.status: executing tests/atconfig commands
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-tests, --disable-tests
cd shared/libosmocore/build-target && make
make[1]: Entering directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target'
echo UNKNOWN > ../.version-t && mv ../.version-t ../.version
make all-recursive
make[2]: Entering directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target'
Making all in include
make[3]: Entering directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target/include'
GEN osmocom/core/crc16gen.h
GEN osmocom/core/crc16gen.h
GEN osmocom/core/crc32gen.h
GEN osmocom/core/crc32gen.h
GEN osmocom/core/crc64gen.h
GEN osmocom/core/crc64gen.h
GEN osmocom/core/crc8gen.h
GEN osmocom/core/crc8gen.h
make[3]: Leaving directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target/include'
Making all in src
make[3]: Entering directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target/src'
GEN crc8gen.c
GEN crc16gen.c
GEN crc32gen.c
GEN crc64gen.c
make all-am
make[4]: Entering directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target/src'
CC timer.lo
CC select.lo
CC signal.lo
CC msgb.lo
CC bits.lo
CC bitvec.lo
CC statistics.lo
../../src/statistics.c: In function 'osmo_counter_get_by_name':
../../src/statistics.c:72:3: warning: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration]
CC write_queue.lo
CC utils.lo
../../src/utils.c: In function 'get_string_value':
../../src/utils.c:49:3: warning: implicit declaration of function 'strcasecmp' [-Wimplicit-function-declaration]
CC socket.lo
CC logging.lo
../../src/logging.c: In function 'log_parse_category':
../../src/logging.c:151:3: warning: implicit declaration of function 'strcasecmp' [-Wimplicit-function-declaration]
../../src/logging.c: In function 'log_parse_category_mask':
../../src/logging.c:168:2: warning: implicit declaration of function 'strdup' [-Wimplicit-function-declaration]
../../src/logging.c:168:15: warning: incompatible implicit declaration of built-in function 'strdup' [enabled by default]
../../src/logging.c:175:2: warning: implicit declaration of function 'strtok' [-Wimplicit-function-declaration]
../../src/logging.c:175:17: warning: assignment makes pointer from integer without a cast [enabled by default]
../../src/logging.c:179:4: warning: implicit declaration of function 'strstr' [-Wimplicit-function-declaration]
../../src/logging.c:179:18: warning: incompatible implicit declaration of built-in function 'strstr' [enabled by default]
../../src/logging.c:194:4: warning: implicit declaration of function 'strncasecmp' [-Wimplicit-function-declaration]
../../src/logging.c:205:27: warning: assignment makes pointer from integer without a cast [enabled by default]
../../src/logging.c: In function '_file_output':
../../src/logging.c:446:2: warning: implicit declaration of function 'fprintf' [-Wimplicit-function-declaration]
../../src/logging.c:446:2: warning: incompatible implicit declaration of built-in function 'fprintf' [enabled by default]
../../src/logging.c:447:2: warning: implicit declaration of function 'fflush' [-Wimplicit-function-declaration]
../../src/logging.c: In function 'log_target_create_file':
../../src/logging.c:520:2: warning: implicit declaration of function 'fopen' [-Wimplicit-function-declaration]
../../src/logging.c:520:23: warning: assignment makes pointer from integer without a cast [enabled by default]
../../src/logging.c: In function 'log_target_find':
../../src/logging.c:544:4: warning: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration]
../../src/logging.c: In function 'log_target_destroy':
../../src/logging.c:566:4: warning: implicit declaration of function 'fclose' [-Wimplicit-function-declaration]
../../src/logging.c: In function 'log_target_file_reopen':
../../src/logging.c:579:23: warning: assignment makes pointer from integer without a cast [enabled by default]
CC logging_syslog.lo
CC rate_ctr.lo
../../src/rate_ctr.c: In function 'rate_ctr_get_group_by_name_idx':
../../src/rate_ctr.c:153:3: warning: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration]
CC gsmtap_util.lo
In file included from /home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/swab.h:5:0,
from /home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/byteorder.h:12,
from /home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/arpa/inet.h:2,
from ../../src/gsmtap_util.c:37:
/home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/defines.h:5:0: warning: "__attribute_const__" redefined [enabled by default]
/usr/include/i386-linux-gnu/sys/cdefs.h:241:0: note: this is the location of the previous definition
/home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/asm/swab.h: Assembler messages:
/home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/asm/swab.h:32: Error: no such instruction: `eor %edx,%ecx,%ecx,ror'
make[4]: *** [gsmtap_util.lo] Error 1
make[4]: Leaving directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target/src'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target'
make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] Error 2
With regards
Neetesh Saxena...
Get your own FREE website, FREE domain & FREE mobile app with Company email. Know More >
Hi everyone,
Next time when I am trying to compile osmocom-bb source using "make" command it is showing two errors.
Even I have removed the complete directory where I had put osmocom-bb, toolchain, libosmocore. I tried two times as a fresh installation but still I am getting the errors.
Can anyone help me what to do? The details of the commands and the generated errors are as:
neetesh@neetesh-VirtualBox:~/GSMP$ git clone git://git.osmocom.org/osmocom-bb.git
Cloning into 'osmocom-bb'...
remote: Counting objects: 19471, done.
remote: Compressing objects: 100% (6037/6037), done.
remote: Total 19471 (delta 13610), reused 18108 (delta 12508)
Receiving objects: 100% (19471/19471), 3.37 MiB | 1.07 MiB/s, done.
Resolving deltas: 100% (13610/13610), done.
neetesh@neetesh-VirtualBox:~/GSMP$ cd osmocom-bb/
neetesh@neetesh-VirtualBox:~/GSMP/osmocom-bb$ git pull --rebase
Current branch master is up to date.
neetesh@neetesh-VirtualBox:~/GSMP/osmocom-bb$ cd src/
neetesh@neetesh-VirtualBox:~/GSMP/osmocom-bb/src$ sudo make
cd shared/libosmocore && autoreconf -fi
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./config.guess'
libtoolize: copying file `./config.sub'
libtoolize: copying file `./install-sh'
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
configure.ac:5: installing `./missing'
src/Makefile.am: installing `./depcomp'
mkdir shared/libosmocore/build-target
cd shared/libosmocore/build-target && ../configure \
--host=arm-none-eabi --enable-embedded --disable-shared \
--disable-tests ac_cv_header_sys_select_h=no \
--disable-tests ac_cv_header_sys_socket_h=no \
CFLAGS="-Os -ffunction-sections -I/home/neetesh/GSMP/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs"
configure: WARNING: unrecognized options: --disable-tests, --disable-tests
configure: WARNING: if you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-none-eabi-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make sets $(MAKE)... (cached) yes
checking for arm-none-eabi-gcc... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu
checking host system type... arm-none-eabi
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... no
checking for arm-none-eabi-dumpbin... no
checking for arm-none-eabi-link... no
checking for dumpbin... no
checking for link... link -dump
configure: WARNING: using cross tools not prefixed with host triplet
checking the name lister (nm) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 805306365
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-linux-gnu file names to arm-none-eabi format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for arm-none-eabi-objdump... no
checking for objdump... objdump
checking how to recognize dependent libraries... unknown
checking for arm-none-eabi-dlltool... no
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for arm-none-eabi-ar... no
checking for ar... ar
checking for archiver @FILE support... @
checking for arm-none-eabi-strip... strip
checking for arm-none-eabi-ranlib... no
checking for ranlib... ranlib
checking command to parse nm output from gcc object... ok
checking for sysroot... no
checking for arm-none-eabi-mt... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... no
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for ANSI C header files... (cached) yes
checking execinfo.h usability... yes
checking execinfo.h presence... yes
checking for execinfo.h... yes
checking for sys/select.h... (cached) no
checking for sys/socket.h... (cached) no
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking for size_t... yes
checking for working alloca.h... no
checking for alloca... no
checking whether `alloca.c' needs Cray hooks... no
checking stack direction for C alloca... 0
checking for library containing dlopen... -ldl
checking for doxygen... false
checking if gcc supports -fvisibility=hidden... yes
checking whether struct tm has tm_gmtoff member... no
configure: creating ./config.status
config.status: creating libosmocore.pc
config.status: creating libosmocodec.pc
config.status: creating libosmovty.pc
config.status: creating libosmogsm.pc
config.status: creating libosmogb.pc
config.status: creating include/Makefile
config.status: creating src/Makefile
config.status: creating src/vty/Makefile
config.status: creating src/codec/Makefile
config.status: creating src/gsm/Makefile
config.status: creating src/gb/Makefile
config.status: creating tests/Makefile
config.status: creating utils/Makefile
config.status: creating Doxyfile.core
config.status: creating Doxyfile.gsm
config.status: creating Doxyfile.vty
config.status: creating Doxyfile.codec
config.status: creating Makefile
config.status: creating config.h
config.status: executing tests/atconfig commands
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-tests, --disable-tests
cd shared/libosmocore/build-target && make
make[1]: Entering directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target'
echo UNKNOWN > ../.version-t && mv ../.version-t ../.version
make all-recursive
make[2]: Entering directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target'
Making all in include
make[3]: Entering directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target/include'
GEN osmocom/core/crc16gen.h
GEN osmocom/core/crc16gen.h
GEN osmocom/core/crc32gen.h
GEN osmocom/core/crc32gen.h
GEN osmocom/core/crc64gen.h
GEN osmocom/core/crc64gen.h
GEN osmocom/core/crc8gen.h
GEN osmocom/core/crc8gen.h
make[3]: Leaving directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target/include'
Making all in src
make[3]: Entering directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target/src'
GEN crc8gen.c
GEN crc16gen.c
GEN crc32gen.c
GEN crc64gen.c
make all-am
make[4]: Entering directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target/src'
CC timer.lo
CC select.lo
CC signal.lo
CC msgb.lo
CC bits.lo
CC bitvec.lo
CC statistics.lo
../../src/statistics.c: In function 'osmo_counter_get_by_name':
../../src/statistics.c:72:3: warning: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration]
CC write_queue.lo
CC utils.lo
../../src/utils.c: In function 'get_string_value':
../../src/utils.c:49:3: warning: implicit declaration of function 'strcasecmp' [-Wimplicit-function-declaration]
CC socket.lo
CC logging.lo
../../src/logging.c: In function 'log_parse_category':
../../src/logging.c:151:3: warning: implicit declaration of function 'strcasecmp' [-Wimplicit-function-declaration]
../../src/logging.c: In function 'log_parse_category_mask':
../../src/logging.c:168:2: warning: implicit declaration of function 'strdup' [-Wimplicit-function-declaration]
../../src/logging.c:168:15: warning: incompatible implicit declaration of built-in function 'strdup' [enabled by default]
../../src/logging.c:175:2: warning: implicit declaration of function 'strtok' [-Wimplicit-function-declaration]
../../src/logging.c:175:17: warning: assignment makes pointer from integer without a cast [enabled by default]
../../src/logging.c:179:4: warning: implicit declaration of function 'strstr' [-Wimplicit-function-declaration]
../../src/logging.c:179:18: warning: incompatible implicit declaration of built-in function 'strstr' [enabled by default]
../../src/logging.c:194:4: warning: implicit declaration of function 'strncasecmp' [-Wimplicit-function-declaration]
../../src/logging.c:205:27: warning: assignment makes pointer from integer without a cast [enabled by default]
../../src/logging.c: In function '_file_output':
../../src/logging.c:446:2: warning: implicit declaration of function 'fprintf' [-Wimplicit-function-declaration]
../../src/logging.c:446:2: warning: incompatible implicit declaration of built-in function 'fprintf' [enabled by default]
../../src/logging.c:447:2: warning: implicit declaration of function 'fflush' [-Wimplicit-function-declaration]
../../src/logging.c: In function 'log_target_create_file':
../../src/logging.c:520:2: warning: implicit declaration of function 'fopen' [-Wimplicit-function-declaration]
../../src/logging.c:520:23: warning: assignment makes pointer from integer without a cast [enabled by default]
../../src/logging.c: In function 'log_target_find':
../../src/logging.c:544:4: warning: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration]
../../src/logging.c: In function 'log_target_destroy':
../../src/logging.c:566:4: warning: implicit declaration of function 'fclose' [-Wimplicit-function-declaration]
../../src/logging.c: In function 'log_target_file_reopen':
../../src/logging.c:579:23: warning: assignment makes pointer from integer without a cast [enabled by default]
CC logging_syslog.lo
CC rate_ctr.lo
../../src/rate_ctr.c: In function 'rate_ctr_get_group_by_name_idx':
../../src/rate_ctr.c:153:3: warning: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration]
CC gsmtap_util.lo
In file included from /home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/swab.h:5:0,
from /home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/byteorder.h:12,
from /home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/arpa/inet.h:2,
from ../../src/gsmtap_util.c:37:
/home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/defines.h:5:0: warning: "__attribute_const__" redefined [enabled by default]
/usr/include/i386-linux-gnu/sys/cdefs.h:241:0: note: this is the location of the previous definition
/home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/asm/swab.h: Assembler messages:
/home/neetesh/GSMP/osmocom-bb/src/target/firmware/include/asm/swab.h:32: Error: no such instruction: `eor %edx,%ecx,%ecx,ror'
make[4]: *** [gsmtap_util.lo] Error 1
make[4]: Leaving directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target/src'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/neetesh/GSMP/osmocom-bb/src/shared/libosmocore/build-target'
make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] Error 2
With regards
Neetesh Saxena...
Hi all,
time is moving fast, and I want to start some initial discussion and
planning for OsmoDevCon 2014.
There are basically four questions which I'm raising below. Please
provide your feedback to the osmocom-event-orga mailing list only, to
avoid cross-posting over all the project lists.
= Who? =
My intention is to keep it an 'active developer/contributer only' event,
like we had it before. I would also want to keep the group relatively
small, to keep the 'Osmocom family' atmosphere.
If desired, we could have one half or full day of public prsentations in
a larger auditorium, but the developer meeting should be a close group,
as known so far.
= Where? =
If we keep the number of attendees within the same range as this year,
then I'm sure we could again hold it at the same venue. I know it is
not perfect, but it is a place that we have access to, 24 hours per day,
and free of cost for community projects like osmocom.org.
If the community wants a larger event, then this is something that would
require more funds and much more time organizing. And that is something
that I personally could not offer to take care of, sorry. I'm happy to
attend and support any larger events, but I'm unable to take care of
fundraising and venue research.
= When? =
Q1/2014. In January, I'm not aware of any 'blocker' events. February,
there is Fosdem (Feb 1 + Feb 2), and MWC from Feb 24 through Feb 27. In
March there is CeBIT (March 10-14) and Easter holidays (with EasterHegg
March 17-21). Did I miss any other FOSS / mobile event that might clash
in Q1?
So my preference woudl be to do it either late January (23-26) or in
February (6-9 or 13-16). Any preferences regarding preferred schedule?
Once we have some concencus here on the list [and we want to do it in
the same size / venue], I'll talk to IN-Berlin.
= What? =
I think that question is easy to answer, if we have the above three
figured out... There's no shortage of topics, I suppose.
You can start adding your suggestions to
http://openbsc.osmocom.org/trac/wiki/OsmoDevCon2014
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
