Hello,
there is a small bug in the calculation of the "Range 1024" format
frequency list. A patch is appended. I post it here because I found
it while working with OsmocomBB.
Best regards,
Dieter
Dieter Spaar, Germany spaar(a)mirider.augusta.de
---------- Forwarded message ----------
From: Alvin Schurman <alvin.schurman(a)gmail.com>
Date: Tue, Aug 9, 2011 at 5:37 PM
Subject: Re: i got C115 device . now i am searching for the cable to flash
the Build on to the device.
To: nagesh reddy <karnatinagesh(a)gmail.com>
I too have a C115 at home. I ordered it to flash and so I could experience
a little hands-on learning with GPRS. The first thing I noticed was that
there was no usb port or data cable input of any kind on the phone. After a
little digging, I found that it has a line of JTAG pads under the battery.
I wasn't equipped or trained to tackle JTAG so I stopped where you are.
Hopefully, you'll get an answer so I can pick up where I left off when I'm
back home with my C115.
Cheers,
Al
On Tue, Aug 9, 2011 at 9:48 AM, nagesh reddy <karnatinagesh(a)gmail.com>wrote:
> Hi Guys,
>
>
> i got the Motorola C115 device and i want to flash the Build into the
> device. from where can i get the cable
> so that i can flash the stack and seee.
>
>
>
> regards,
> nagesh.
>
>
>
Hi Guys,
i got the Motorola C115 device and i want to flash the Build into the
device. from where can i get the cable
so that i can flash the stack and seee.
regards,
nagesh.
i am bit new to GSM and osmocombb.
does osmocombb support RRLP protocol.
@herald i saw in your presentation that we can send custom time advance.
does that related to RRLP.
also can we fake position using osmocombb?
--
Akib Sayyed
Matrix-Shell
akibsayyed(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
Hello Andreas,
there is a small issue with GSM1800/1900 in the mobile application:
When a location update is performed, the wrong power capability is
set in Mobile Station Classmark 1. As a workaround I fixed it this way:
--- ./host/layer23/src/mobile/gsm48_mm.c Mon Jul 25 15:40:50 2011
+++ r:./host/layer23/src/mobile/gsm48_mm.c Thu Aug 04 13:15:09 2011
@@ -2321,7 +2321,11 @@
gsm_print_mcc(subscr->mcc),
gsm_print_mnc(subscr->mnc), subscr->lac);
/* classmark 1 */
+#if 0
pwr_lev = gsm48_current_pwr_lev(set, rr->cd_now.arfcn);
+#else /* cd_now not yet set, take selected cell ARFCN !? */
+ pwr_lev = gsm48_current_pwr_lev(set, rr->ms->cellsel.sel_arfcn);
+#endif
gsm48_encode_classmark1(&nlu->classmark1, sup->rev_lev, sup->es_ind,
set->a5_1, pwr_lev);
/* MI */
The reason for the the wrong power capability comes from the fact that
"rr->cd_now" is not yet set and so the ARFCN is 0 which causes the
GSM900 power capability to be used. It is set to "Class 4" in the
configuration file per default, however this value is not defined for
GSM1800/1900. I am not sure if my workaround is perfect, you are the
expert for "mobile" ;-)
Although this might sound like not that important (networks with OpenBSC
or OpenBTS don't care at all about the value) there are some real networks
out there which don't like it.
On a related note: The default TX power calibration curve for GSM900
causes too less TX power for GSM1800/1900, expecially for low power
settings. I will try to improve my current workaround for this and
provide a patch.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Dear all,
in the if starting at line 1591 in lapdm.c there are two return, maybe you
want to fix this
1591 if (!mctx.dl) {
LOGP(DLAPDM, LOGL_NOTICE, "Received frame for unsupported "
"SAPI %d!\n", sapi);
return -EINVAL;
msgb_free(msg);
return -EIO;
1597 }
Regards,
Loretta
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/returning-twice-in-lapdm-c-tp321…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hi,
I noticed in
src/target/firmware/calypso/dsp.c:
static void dsp_pre_boot(const struct dsp_section *bootcode)
{
dputs("Assert DSP into Reset\n");
calypso_reset_set(RESET_DSP, 1);
if (bootcode) {
dputs("Loading initial DSP bootcode (API boot mode)\n");
dsp_upload_sections_api(dsp_bootcode, DSP_BASE_API_MIRROR);
It seems that the intention is to pass bootcode to
dsp_upload_sections_api, but it is still using the hardcoded dsp_bootcode.
No functional impact as it is nowhere used with any other bootcode.
Best regards,
Job
Hello,
I am using a C115 with a t191 cable. We have completed the "Getting
Started" steps and have compiled all the necessary code. I are
currently trying to run osmocon to download code onto the phone. The
following output appears when we run the script:
bruceb@ubuntu:~/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0
-m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin
got 1 bytes from modem, data looks like: 2d -
got 1 bytes from modem, data looks like: 34 4
got 1 bytes from modem, data looks like: 29 )
got 1 bytes from modem, data looks like: 28 (
got 1 bytes from modem, data looks like: 32 2
got 1 bytes from modem, data looks like: 39 9
got 1 bytes from modem, data looks like: 30 0
got 1 bytes from modem, data looks like: 20
got 1 bytes from modem, data looks like: 2d -
got 1 bytes from modem, data looks like: 34 4
got 1 bytes from modem, data looks like: 29 )
got 1 bytes from modem, data looks like: 0a .
got 1 bytes from modem, data looks like: 0d .
got 1 bytes from modem, data looks like: 02 .
These lines continue and no script indicates anything is being
downloaded, as shown on the wiki site. I have unlocked the phone and
put it in "earphone" mode beforehand. I have also tried to press the
power button as directed to. Are there any suggestions on how to fix
this problem?
Thank you,
Bryan Bruce