Hi All,
Do I need to prepare my phone for uploading the firmware with osmocon tool?
I tried to load firmware on Motorola C118 and C115 with Prolific PL2303 USB
to serial adaptor (computer->usb->com->3.5mm jack->2.5mm jack->phone) and
when I briefly press the power-on button of my phone as it's stated in
manual - I got no response from phone. Seems it does nothing. Cable seems to
be working, because it detect contact with phone's 2.5mm socket when I plug
it into phone as - 'got 1 bytes from modem, data looks like: 00 .'.
Thanks,
Pavel
Hi,
When building osmocombb with an updated src/shared/libosmocore (0.3.6)
the build fails due to make attempting to build utils/osmo-arfcn.c for
build-target which does not have stdio.
I have no patch as I was not sure what the preferred way to solve it is.
Maybe a --disable-utils like for tests?
Best regards,
Job
make[3]: Entering directory
`osmocom-bb/src/shared/libosmocore/build-target/utils'
CC osmo-arfcn.o
../../utils/osmo-arfcn.c: In function 'arfcn2freq':
../../utils/osmo-arfcn.c:43: warning: incompatible implicit declaration
of built-in function 'fprintf'
../../utils/osmo-arfcn.c:43: error: 'stderr' undeclared (first use in
this function)
is it possible to tune or use osmocombb to use 2.4 ghz.
whole idea is using OpenBTS on 2.4 ghz on BTS side .and osmocombb on 2.4ghz
on phone side
will it work??
--
Akib Sayyed
Matrix-Shell
akibsayyed(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
I keep forgetting how to make this work, and it just came up in IRC
again, so I thought I would archive the answer to the list:
per tnt:
in src/target/firmware/board/compal/rffe_dualband.c , the
rffe_get_rx_ports might need to have PCS1900 instead of DCS1800
Some phones have different RF wiring and we can't autodetect it ...
(the thing is that unless you try manually or look at the PCB you
can't really tell ... some PCS phones have it wired to the DCS input
...)
Hello every,
I recently set up the equipment and tried to communicate with the public
PLMN and it worked well at that stage. Then I tried to camp on the OpenBTS
after switching on the SIM card. When it progressed to location updating
request step, the OpenBTS can not receive identity response from MS. The
timer t3210 was fired as long as passing a certain period of time and
location updating request was sending again iteratively. Anyway location
updating was failed. I checked through wireshark from the mobile phone side,
showing that MS did send the response however OpenBTS did not receive
somehow. Also the timing advance (ta) during that process became 127 which
was abnormal, out of the maximum value of 63. I suspected it was also caused
by the failure of reception.
Is there something wrong about the decoding at OpenBTS side or data packing
error at MS side? Is there any way to fix it?
Many thanks,
Li
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/interact-osmocombb-with-OpenBTS-…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hello,
I noticed some issues in the following situation, I used the "testing"
branch (I think it affects both current "testing" branches):
- the signalling channel is an SDCCH/8 on a timeslot different from
TS0, for example on TS4
- an ASSIGNMENT COMMAND switches to another channel on a different TS
than the SDCCH/8, e.g. to TS2
Now the following two problems can happen:
1.) The ASSIGNMENT COMMAND releases the SDCCH/8 with an L1CTL_DM_REL_REQ.
Depending on when the L1CTL_DM_REL_REQ is received, it could be that
there are still burst scheduled for transmit (e.g. for the SACCH). Due
to the L1CTL_DM_REL_REQ, rfch_get_params() will return wrong data
(l1s.dedicated.type is now set to GSM_DCHAN_NONE) and the transmit
of the bursts happens on the wrong ARFCN and/or TS.
My temporary workaround is to clear every item in the scheduler including
the current bucket when a L1CTL_DM_REL_REQ is received, this action
requires to disable the FIQ, otherwise problems might happen.
2.) There is some code to check for a switch to a lower timeslot in
check_lost_frame(). However it can happen that this code gets not
triggered although it should: The ASSIGNMENT COMMAND causes a
L1CTL_DM_REL_REQ, l1s.dedicated.type is now GSM_DCHAN_NONE ("0").
The next call to check_lost_frame() resets "last_ts" to 0. Now the
new channel is assigned (in the example from above its a switch
from TS4 to TS 2) and a "LOST" occures, however the required
increment of the GSM time does not happen because "last_ts" is 0
although it should be 4.
My current workaround is to not reset "last_ts" to 0 in check_lost_frame()
but during "L1CTL_RESET_REQ: FULL!".
I don't post any patches because my changes are really just ugly workaround
which seem to work in (most) situations where it I otherwise observe failures.
To really solve this issues something else should be done, maybe put
the whole switch of a channel into an atomic operation instead of
doing several operations (this is just an idea, maybe there are
better solutions).
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hi all,
I work in a research lab and we're interested in using your stack to send
SMS. I've got some time on my hands and a working OpenBTS stack (USRP), so I
will probably go ahead and start implementing it in the mobile app. Before I
start I just wanted to ask first about the status of mobile-originated SMS?
I saw some traffic in the archives a few months back from Gianni about
mobile-terminated SMS, but nothing recent about mobile-originated SMS.
Barring that, any suggestions on where to start? :) I'm kinda new here.
Assuming I get something solid working, I'd of course be willing to
contribute it back to the codebase.
Thanks,
Andrew
Hi all,
I'm new in these forums and osmocomBB.
I was wondering, how does osmocomBB work. install 2 packages, one on the phone and the other on a PC Host?
And then you are able to call/sms and anything a GSM phone can do?
And you can change the GSM protocol/stack if you want to?
So pretty much your PC becomes a GSM terminal?
also
Are there any simple guides to setup the whole thing?
Ahmed
Hi all,
I'm using Motorola C118 and Prolific PL2303 USB to serial adaptor on Ubuntu
10.10. I'm trying to run
$ ./osmocon -p /dev/ttyUSB0 -m c123xor
../../target/firmware/board/compal_e88/loader.compalram.bin
and I got
got 1 bytes from modem, data looks like: 00 .
I press power button and nothing happens. If rub the connector - lines such
as I provided above are appears. Is it means that cable is ok?
And what could be the problem?
Thanks,
Pavel
