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,
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.
So far three persons have indicated their interest to join
a meeting at my place.
Considering the time it takes to drive to my place, it
probably makes sense to have the meeting at the weekend
(either Saturday or Sunday) so that there is more time
for the meeting itself. I can suggest one of the following
dates for the first meeting, somewhere between 10:00 to
18:00 on each day:
25.8. (Sa) or 26.8. (Su)
1.9. (Sa) or 2.9. (Su)
8.9. (Sa) or 9.9. (Su)
So please let me know when you have time and also make
suggestions in which Osmocom topic you are interested
in so that we can have some sort of agenda for the
meeting to make best use of the time.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello.
I'm having troubles compiling asn.1 files from
http://www.3gpp.org/ftp/Specs/archive/24_series/24.080/ASN.1/
I'm getting syntax error (syntax error at line 264 in module SS-Operations.asn: got
'SEQUENCE' expected ':') while running
erlc SS-Operations.asn
using Erlang version 15.b.1
As far as I recall Harald has done this for MAP asn.1
Are there any hints on what might be wrong?
Tried online compiler but it gives different errors in different places.
Should I use different version? Compile smth else before attempting to compile this
file? Fix syntax using some clever trick? Do some rtfm?
Any advices would be greatly appreciated.
--
best regards,
Max, http://fairwaves.ru
hi josephli,
> Read stored BA list mnc=01
the mobile application stores the last cells and neighbour cells (band
allocation) of each network. this way the scanning is much
faster when restarting. because you use the SIM card with MNC == 02 the
first time, there is no band allocation stored for that. the mobile will
do a full scan in this case.
> while the sim card service I am tesing is actually with mnc 00 and 02.
i know that MNC == 0 will not work until i commited improvements of cell
selection process last sunday. you should retry that, but first try with
an MNC > 0.
can you provide debug output when trying a call?
also can you provide VTY output of "show ms" before you make the call?
regards,
andreas
hi,
i just fixed some locking issues the last days. fix will follow. it took
a bit longer, because there were some race conditions. it took up to
about one hour until it crashed. my way to detect the area where the
crash happened, was to turn on buzzer before that area, and turn it off
after that area. after many hours of approximation, i finally found out
that the major crash happend during _talloc_zero. (first it looks for a
free memory chunk, then it allocates it.) since it can be called from
all contexts (main, irq, fiq), it need to be locked against any
interrupt, otherwise the memory chunk can be assigned multiple times.
(the process of _talloc_free is "atomic" and requires no locking.)
because it seems pretty stable, i think it is time to merge some
branches into the master. (i made a 6 hours call yesterday. and no crash
after bugfix ever since.) i will do that together with sylvain, if we
find the time this weekend.
currently i use the jolly/voice together with the sylvain/traffic
branch. i am able to use an isdn phone togehter with linux-call-router
and make/receive calls. audio is passed both ways. i think this is a
stage where it actually become "usable". (if not moving arround.)
one of my major work for the next weeks/months will be the neighbour
cell measurement, cell re-selection, and handover. this is essential
when moving with the phone.
regards,
andreas
Hello All,
I can't compile after the last pull. I know that it is an error with
toolchain detection but I have tried almost everything.
-------------------------------
As you can see the $PATH variable has the address to gnu-arm-elf binary :
arslan@arslan-Lenovo-B575:~/osmocom-bb/src$ echo $PATH
/home/arslan/arm-elf/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
-------------------------------
and when I list the items in that directory I can clearly see that the
binary is there :
arslan@arslan-Lenovo-B575:~/arm-elf/bin$ ls
arm-elf-addr2line arm-elf-cpp arm-elf-ld arm-elf-size
arm-elf-ar arm-elf-g++ arm-elf-nm arm-elf-strings
arm-elf-as arm-elf-gcc arm-elf-objcopy arm-elf-strip
arm-elf-c++ arm-elf-gcc-4.0.4 arm-elf-objdump
arm-elf-cc arm-elf-gccbug arm-elf-ranlib
arm-elf-c++filt arm-elf-gcov arm-elf-readelf
-------------------------------
But I still get the following error:
/home/arslan/osmocom-bb/src/target/firmware/include/asm/swab.h:
Assembler messages:
/home/arslan/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/arslan/osmocom-bb/src/shared/libosmocore/build-target/src'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/home/arslan/osmocom-bb/src/shared/libosmocore/build-target/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/arslan/osmocom-bb/src/shared/libosmocore/build-target'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/arslan/osmocom-bb/src/shared/libosmocore/build-target'
make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] Error 2
Regards,
Arslan Anjum
Research Assitant
Lahore University of Management Sciences, Pakistan
Dear Sylvain
While Decoding AMR do need to just decode and pack it into raw amr frames
or we need to think about hysterasis and all parts also
also there are total 8 codec modes
but in band data have details of on 4 codec modes
which one to choose out of 8 codec modes from those 8 modes.
--
Akib Sayyed
Matrix-Shell
akibsayyed(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
Hi list,
I am trying, with no success so far ,to chain-load the trx-firmware on my c118 with usb-serial-cable.:
------output-----
./osmocon -p /dev/ttyUSB0 -m
c123xor -c ../ ../target/firmware/board/compal_e88/trx.compalram.bin ../ ../target/firmware/board/compal_e88/chainload.highram.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
opening file: No such file or directory
------------------------------------
I also tried switching highram-compalram:
./osmocon -p /dev/ttyUSB0 -m
c123xor -c ../ ../target/firmware/board/compal_e88/trx.highram.bin ../ ../target/firmware/board/compal_e88/chainload.compalram.bin
And also
./osmocon -p /dev/ttyUSB0 -m
c123xor -c target/firmware/board/compal_e88/trx.compalram.bin target/firmware/board/compal_e88/chainload.highram.bin
but got same errors. I used the script in the wiki for building the toolchain prior to building the code.
----------------------------------
Any ideas what might be wrong?
Regards erich
Hi list,
Attached 3 patches for decoding UCS2 MT-SMS and incoming USSD.
Main idea: convert UCS2 text to UTF-8, check if terminal supports
UTF-8 and if yes - print, otherwise - print in hex, and notify VTY to
check mobile log (since we can't send UTF text to VTY, if someone
knows how to do it - please tell me).
Waiting for comments.
Thanks,
Pavel
Dear fellow Osmcoom developers,
it is my pleasure to finally announce the date + venue of OsmoDevCon
2013:
Date: April 04 through April 07, 2013
Place: IN-Berlin, Lehrter Str. 53, Berlin
Like last year, this is an event for developers of the various Osmocom
proejects. Reservation and confirmation of reservation is required.
The event is free of charge. The Room is made available by IN-Berlin
e.V., an Internet related non-profit organization. Lunch catering will
be sponsored (so far by sysmocom GmbH, but if any other sponsors come
up, we are happy to share the cost).
So all you have to cover is your own travel + accomodation costs, as
well as breakfast and dinner. If you are an active developer and cannot
afford travel/accomodation, please let me know and I'll see if we can do
something about it.
If you would like to attend, please send a message to
laforge(a)gnumonks.org applying for registration of the event. The
registration deadline is March 5, i.e. one week from now.
There is no detailed schedule of talks yet. I will start a separate
discussion suggesting / collecting topics in the next couple of days.
More information is (and will be made) available at
http://openbsc.osmocom.org/trac/wiki/OsmoDevCon2013
Further discussion regarding the event should be directed at the
osmocom-event-orga(a)lists.osmocom.org mailing list, to avoid
cross-posting over the various project-specific lists.
Best regards and happy hacking,
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,
I'm having a try with your software. A small suggestion I can give you
is about the chapter "Starting OpenBTS" of your howto: a better way to
host the transceiver script is to create a new dir under the openbts
root (lets call it TransceiverOSMOCOM) that hosts your script. Then to
create a link in the apps dir that point to the new transceiver, to
follow the model openbts uses. This allows the user to switch between
many hardware pieces using the same openbts installation (if
compilation flags apply), avoiding to overwrite your script if openbts
compilation instructions are literally followed.
Just my 2 cents.
Dario.
On Sun, Feb 24, 2013 at 3:33 PM, Sylvain Munaut <246tnt(a)gmail.com> wrote:
>> PS: Any news on the "emulated BTS" that has been presented at last years chaos communication congress?
>
> http://bb.osmocom.org/trac/wiki/Software/Transceiver
>
> Cheers,
>
> Sylvain
>
hi all
i cant understand where i am wrong
when i run this command this is the response which i get
root@shahzeb-laptop:~/Desktop/toolchain/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c140xor -c ../../target/firmware/board/se_j100/layer1.highram.bin
got 1 bytes from modem, data looks like: 00 .
and then it gets hanged and nothing happens.
i have checked the cable aswell it seems like cable is working
i have consulted J100i_cable.pdf for the data cable.
i would really appreciate your help
thanks
shahzeb
Hi,
I have about 8 broken C118 and wonder if someone would be interested
to save them from the recycling system. The defects vary but in some
cases it is a broken buzzer, issues with the SIM card holder, missing
or broken audio socket. This will just be the phone, no battery, no
charger.
I would like to get rid of them in batches of two. Is anyone interested?
The postage should be paid by the receiver.
cheers
holger
Hi ,List:
search some materials, find that the decode method of AFS convolutional
code is different from the EFS`, it use RSC, and need SOVA(soft output
viterbi algorithm). am i right?
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/is-the-Viterbi-decode-for-the-AF…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hi all,
I am facing an error while trying to make a call from vty
here is my mobile.cfg output
!
! OsmocomBB () configuration saved from vty
!!
!
line vty
no login
!
gps device /dev/ttyACM0
gps baudrate default
gps enable
!
no hide-default
!
ms 1
layer2-socket /tmp/osmocom_l2
sap-socket /tmp/osmocom_sap
sim reader
network-selection-mode auto
imei 415239521974659 0
imei-random 15
no emergency-imsi
no sms-service-center
no call-waiting
no auto-answer
no force-rekey
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
no gsm-850
dcs
no 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 -100
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
!
the debbuging output is
<0009> mnccms.c:570 Make call to 123456789
<0009> mnccms.c:150 support TCH/H also
<0009> mnccms.c:174 support full rate v2
<0009> mnccms.c:178 support full rate v1
<0009> mnccms.c:187 support half rate v1
<0006> transaction.c:76 ms 1 allocates transaction (proto 3 trans_id 255
callref 1 mem 0xf408d0)
<0006> gsm48_cc.c:243 new state NULL -> MM_CONNECTION_PEND
<0006> gsm48_cc.c:507 Sending MMCC_EST_REQ
<0005> gsm48_mm.c:3783 (ms 1) Received 'MMCC_EST_REQ' event in state MM idle
<0005> gsm48_mm.c:3786 -> substate PLMN search
<0005> gsm48_mm.c:3788 -> callref 1, transaction_id 255
<0005> gsm48_mm.c:3051 Init MM Connection, not in normal state.
<0006> gsm48_cc.c:2161 (ms 1) Received 'MMCC_REL_IND' in CC state
MM_CONNECTION_PEND
<0006> gsm48_cc.c:196 (ms 1 ti ff) Sending 'MNCC_REL_IND' to MNCC.
<0006> gsm48_cc.c:243 new state MM_CONNECTION_PEND -> NULL
<0006> transaction.c:104 ms 1 frees transaction (mem 0xf408d0)
<0009> mnccms.c:372 Call has been released (cause 21)
<0009> mnccms.c:71 (call 1) Call removed.
and also my ms output from vty
OsmocomBB> enable
OsmocomBB# show ms
MS '1' is up, service is limited
IMEI: 418873812577882
IMEISV: 4188738125778820
IMEI generation: random (15 trailing digits)
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 subsccriber 1
% Unknown command.
OsmocomBB# show sub
OsmocomBB# show subscriber 1
OsmocomBB# show subscriber 1
Mobile Subscriber of MS '1':
IMSI: 405025012498239
ICCID: 89910255110124982391
Status: U1_UPDATED IMSI detached TMSI 0x1d315a07
LAI: MCC 405 MNC 025 LAC 0x42d8 (405, TATA DOCOMO)
Key: sequence 2 a6 78 30 12 22 45 0b 03
Access barred cells: no
Access classes:
Kindly assist me with some suggestions.
Regards,
Cris
*Dear folks,*
Recently I tried to compile osmocomBB on ubuntu 120.10 and arch linux.
I always run into problems trying to get the arm toolchain. I can't
reach gnuarch.com because it is down, nor get the paket from the
ubuntu ppa because it is also down or corrupted. Is there any other
source where I can get the arm toolchain or any howto wich could help
me?
Thanks :)
hi everyone.is it possible to
connect motorola c118 to the
raspberry
GPIO pins,since they are 3v3 logic?
What is the current limitation as
the GPIO pins can provide only
8mA?
Is it possible to use the lcd of the
c118 or the RTC on the raspberry
pi via the GPIO pins?
Can i use the connection via the
GPIO Instead of the pl2303 based
cable.
Thanks.
*Dear folks,*
Recently I tried to compile osmocomBB on ubuntu 120.10 and arch linux.
I always run into problems trying to get the arm toolchain. I can't
reach gnuarch.com because it is down, nor get the paket from the
ubuntu ppa because it is also down or corrupted. Is there any other
source where I can get the arm toolchain or any howto wich could help
me?
Thanks :)
The code for rxlev2dbm refers to TS 08.05 Chapter 8.1.4, but TS 08.05 is
now marked as "withdrawn".
Can you please point me to the correct reference for this?
Thx.
OK am testing the mobile app with C123 using real sim but getting some odd
behaviour
(have tested with main branch & sylvian testing branch and results have been
similar to this)
The results below are from using sylvian testing branch build as described
here http://bb.osmocom.org/trac/wiki/SIMReader
<http://bb.osmocom.org/trac/wiki/SIMReader> config tx is enabled etc
I can download the layer1 firmware to the phone ok - mobile app seems to run
ok aswell but when I try to make a call or sms this is where there's some
odd behaviour .
On my first attempt to make a call I can hear the call trying to be made but
an automated message is played saying I have dialed an incorrect number
(this normally happens if the number is dialed in an incorrect format)
In previous attempts I have tried all the formats I can think of but have
never been able to get a successful call to go through as of yet but if I
dial it through the phone (without osmocom) normally everything works fine..
07780000000
+447780000000
447780000000
00447780000000
Usually after the first call the phone then mysteriously deregisters from
the network there is no service and when I restart osmocon/mobile etc I
still cannot register on the network it just keeps scannning frequenceies
and failing to connect with the network.
On my first osmocon log when i managed to connect to the network after the
call was released there were alot of DSP Error Status: 32 messages and then
no service.
I have gone through the logs but I still can't figure out why
a) the call is failing to go through correctly
b) why it seems like I get kicked of the network if I try to make a call
Here are my full outputs
1ST ATTEMPT - MANAGED TO PLACE CALL THEN CONNECTION DROPPED
Osmocon output - https://www.box.com/s/xdqi7azezprf4g7erz9h
<https://www.box.com/s/xdqi7azezprf4g7erz9h>
Mobile output - https://www.box.com/s/gqcdas9eqso0nchat011
<https://www.box.com/s/gqcdas9eqso0nchat011>
Telnet output - https://www.box.com/s/lcazgabtmous0xheklmc
<https://www.box.com/s/lcazgabtmous0xheklmc>
2ND ATTEMPT - FAILED TO CONNECT
Osmocon output - https://www.box.com/s/c42vi7ows8p14h0hr45m
<https://www.box.com/s/c42vi7ows8p14h0hr45m>
Mobile output - https://www.box.com/s/eqygysqommur46ywgqrs
<https://www.box.com/s/eqygysqommur46ywgqrs>
Telnet output - https://www.box.com/s/kmympl0g0l8zb3xjyu8d
<https://www.box.com/s/kmympl0g0l8zb3xjyu8d>
3RD ATTEMPT - FAILED TO CONNECT
Osmocon output - https://www.box.com/s/gb9aw9p05pqy1v5fpxke
<https://www.box.com/s/gb9aw9p05pqy1v5fpxke>
Mobile output - https://www.box.com/s/llo751tuvvu1p5v31eur
<https://www.box.com/s/llo751tuvvu1p5v31eur>
Telnet output - https://www.box.com/s/t8e63lqrad87f35uylge
<https://www.box.com/s/t8e63lqrad87f35uylge>
Extract from telnet
OsmocomBB#
% (MS 1)
% Trying to registering with network...
% (MS 1)
% On Network, normal service: Guernsey, T-Mobile
show ms
MS '1' is up, service is normal
IMEI: 35972800609####
IMEISV: 359728006093####
IMEI generation: fixed
automatic network selection state: A2 on PLMN
MCC=234 MNC=30 (Guernsey, T-Mobile)
cell selection state: C3 camped normally
ARFCN=628(DCS) MCC=234 MNC=30 LAC=0x084f
CELLID=0xf65d
(Guernsey, T-Mobile)
radio ressource layer state: idle
mobility management layer state: MM idle, normal service
OsmocomBB# call 1 +44772228####
OsmocomBB#
% (MS 1)
% Call has been released
% (MS 1)
% On Network, normal service: Guernsey, T-Mobile
call 1 +44772228####
% (MS 1)
% Searching network...
show ms
% (MS 1)
% On Network, normal service: Guernsey, T-Mobile
call 1 44772228####
OsmocomBB#
% (MS 1)
% Call is proceeding
% (MS 1)
% Call is alerting
% (MS 1)
% Call: Remote hangs up
% (MS 1)
% Trying to registering with network...
% (MS 1)
% Trying to registering with network...
% (MS 1)
% Searching network...
% (MS 1)
% No service.
% (MS 1)
% Power off!
CALL SETUP EXTRACT FROM 1ST MOBILE APP OUTPUT
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/OsmocomBB-Mobile-Call-Setup-Weir…
Sent from the baseband-devel mailing list archive at Nabble.com.
I'm experimenting with burst-ind branch and am able to track control
messages in ccch_scan.
I then send an Assignment Command to change to a traffic channel. I can see
the bursts come in, but cannot make out the format of the data.
If I understand right, the burst_ind structure holds 15 bytes of data, but
the traffic data should be 33 bytes. I assume the traffic data is spread
across several burst-ind messages.
Can you please clarify how to re-assemble the full 33-byte traffic data
structure from the burst_ind messages?
Thanks.
B.
While playing with ccch_scan, I came across a strange problem.
At some point the code uses:
/* Convert to softbits */
for (i=0; i<116; i++)
bursts[(116*bid)+i] = bt[i] ? - (bi->snr >> 1) : (bi->snr >> 1);
After this, "xcch_decode()" works ok and "osmo_ubit2pbit_ext()" also works
ok. But "osmo_ubit2pbit()" fails as it converts almost all softbits to 0xFF.
Is this a bug or a "feature"? Do we need to recode "osmo_ubit2pbit" so that
its bit-checking is more robust as in "osmo_ubit2pbit_ext"?
Sylvain, can you explain the idea of using softbits instead of hard binary?
Is it for GSMTAP to represent signal strength?
Thanks in advance for your help.
B
While studying FS coding, I created the attached drawing. The code used for
de-interleaving is:
void tch_fr_deinterleave313(ubit_t *mC, int blockoffset) //see 3GPP TS
05.03 / 3.1.3
{
for (int k = 0; k < 456; k++) {
int B = ( k + blockoffset ) % 8;
int j = 2 * ((49 * k) % 57) + ((k % 8) / 4);
mC[k] = mI[B][j];
}
}
Now I want to study HS coding and de-interleaving. The GSM specs 05.03 /
3.2.3 only mentions a table for interleave coding and not a formula for
matching j with k. Why is that?
I tried to find a formula by looking a the table pattern, but it looks
quite inconsistent.
If there is no formula for coding/decoding HS, then do we have to use table
lookup for each bit? Sounds very inefficient. Or am I missing something?
B
Hi,
my problem is, that I can download the firmware on the motorola c123, but I
can't send a DOWNLOAD ACK.
The Firmware is on the Phone, because I see the "HELLO WORLD" example on the
phone screen.
I build my own "RS232-to-2.5mm"-Cable and I think it works....
Another thing is, at the end of the download I become permanently the INFO "
got 1 bytes ...".
Can anybody help me?
(Sorry my english is very sad :( )
Here is the output:
root@debian:./osmocon -p /dev/ttyS0 -d t -m c123xor
../../target/firmware/board/compal_e88/hello_world.compalram.bin
got 2 bytes from modem, data looks like: 06 c1 ..
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/hello_world.compalram.bin):
file_size=25108, hdr_len=4, dnload_len=25115
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(): 4095 bytes (4095/25115)
handle_write(): 3840 bytes (7935/25115)
handle_write(): 3840 bytes (11775/25115)
handle_write(): 3840 bytes (15615/25115)
handle_write(): 3840 bytes (19455/25115)
handle_write(): 3840 bytes (23295/25115)
handle_write(): 1820 bytes (25115/25115)
handle_write(): finished
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: ff .
got 1 bytes from modem, data looks like: bf .
got 1 bytes from modem, data looks like: ff .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: ff .
got 1 bytes from modem, data looks like: ff .
got 1 bytes from modem, data looks like: ff .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: dc .
got 1 bytes from modem, data looks like: 98 .
got 1 bytes from modem, data looks like: 9f .
got 1 bytes from modem, data looks like: ff .
got 1 bytes from modem, data looks like: 9f .
.....
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/C123-can-t-send-DOWNLOAD-ACK-tp4…
Sent from the baseband-devel mailing list archive at Nabble.com.
Can you please clarify what kind of preprocessing has been done for bursts
in burst_ind data?
Does TCH/F data come through with block-diagonal de-interleaved? Or does
come as 8 interleaved bursts?
I think all the intra-burst de-interleaving has already been done at DSP
level. Is this correct?
B
Hi Everyone,
When i tried to install the osmocombb for the first time which was a couple of days back i encountered with a problem and did some minor modification in the code.
>gsm411_sms.c: In function ‘gsm411_tx_sms_submit’:>gsm411_sms.c:657: warning: passing argument 4 of ‘gsm411_smc_init’ from incompatible pointer type>/usr/local/include/osmocom/gsm/gsm0411_smc.h:46: note: expected ‘int (*)(struct gsm411_smc_inst *, int, struct msgb *, int)’ but argument is of type ‘int (*)(struct gsm411_smc_inst *, int, struct msgb *)’>gsm411_sms.c:657: error: too many arguments to function ‘gsm411_smc_init’>gsm411_sms.c:659: error: too many arguments to function ‘gsm411_smr_init’>gsm411_sms.c: In function ‘gsm411_rcv_sms’:>gsm411_sms.c:911: warning: passing argument 4 of ‘gsm411_smc_init’ from incompatible pointer type>/usr/local/include/osmocom/gsm/gsm0411_smc.h:46: note: expected ‘int (*)(struct gsm411_smc_inst *, int, struct msgb *, int)’ but argument is of type ‘int (*)(struct gsm411_smc_inst *, int, struct msgb *)’
by seeing this error i opened the respective file(gsm411_sms.c) in my local pc and i observed that the lines which was mentioned as error and find the below .
gsm411_smc_init(&trans->sms.smc_inst, transaction_id, 0, gsm411_mn_recv, gsm411_mm_send);
but in the header file (gsm0411_smc.h) only four arguments are defined
void gsm411_smc_init(struct gsm411_smc_inst *inst, int network, int (*mn_recv) (struct gsm411_smc_inst *inst, int msg_type, struct msgb *msg),
so i removed the extra argument transaction_id in the function(gsm411_smc_init) and also did the same with the respective lines where i was getting an error (from the file gsm411_sms.c).
i have done a change like the below by assuming thatevery msg is a mobile originated mesage
gsm411_smc_init(&trans->sms.smc_inst, transaction_id, 0, gsm411_mn_recv, gsm411_mm_send);
Kindly assist me if i was doing wrong.
Thanks in advance and Apologies if my observation was wrong.
Regards,Bharath
Hi Everyone,
When i tried to install the osmocombb for the first time which was a couple of days back i encountered with a problem and did some minor modification in the code.
>gsm411_sms.c: In function ‘gsm411_tx_sms_submit’:
>gsm411_sms.c:657: warning: passing argument 4 of ‘gsm411_smc_init’ from incompatible pointer type
>/usr/local/include/osmocom/gsm/gsm0411_smc.h:46: note: expected ‘int (*)(struct gsm411_smc_inst *, int, struct msgb *, int)’ but argument is of type ‘int (*)(struct gsm411_smc_inst *, int, struct msgb *)’
>gsm411_sms.c:657: error: too many arguments to function ‘gsm411_smc_init’
>gsm411_sms.c:659: error: too many arguments to function ‘gsm411_smr_init’
>gsm411_sms.c: In function ‘gsm411_rcv_sms’:
>gsm411_sms.c:911: warning: passing argument 4 of ‘gsm411_smc_init’ from incompatible pointer type
>/usr/local/include/osmocom/gsm/gsm0411_smc.h:46: note: expected ‘int (*)(struct gsm411_smc_inst *, int, struct msgb *, int)’ but argument is of type ‘int (*)(struct gsm411_smc_inst *, int, struct msgb *)’
by seeing this error i opened the respective file(gsm411_sms.c) in my local pc and i observed that the lines which was mentioned as error and find the below .
gsm411_smc_init(&trans->sms.smc_inst, transaction_id, 0,
gsm411_mn_recv, gsm411_mm_send);
but in the header file (gsm0411_smc.h) only four arguments are defined
void gsm411_smc_init(struct gsm411_smc_inst *inst, int network,
int (*mn_recv) (struct gsm411_smc_inst *inst, int msg_type,
struct msgb *msg),
so i removed the extra argument transaction_id in the function(gsm411_smc_init) and also did the same with the respective lines where i was getting an error (from the file gsm411_sms.c).
i have done a change like the below by assuming thatevery msg is a mobile originated mesage
gsm411_smc_init(&trans->sms.smc_inst, transaction_id, 0,
gsm411_mn_recv, gsm411_mm_send);
Kindly assist me if i was doing wrong.
Thanks in advance and Apologies if my observation was wrong.
Regards,
Bharath
I tried to dump some parts of memory using osmoload. Here is my problem,
When I tried to dump from 0x0, there is a piece of memory filled up with
"f". I guess maybe it's ROM and when I call the memcpy in RAM, I actually
cannot read things in ROM. Can anyone confirm my guess?
Then I found there is a memory protection unit (ti-calypso2.pdf). Then I
dumped the values from FFFF FF00 (registers of MPU), I got all zeros... Does
this mean there is no memory protection active?
Or maybe because actually the phone is not turned on. So there would be some
flash which don't have electricity on...
Anyone can help me?
Thank you in advance.
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Problems-about-analysis-of-conte…
Sent from the baseband-devel mailing list archive at Nabble.com.
