Hi,
I've hacked something together to quickly test non-combined CCCH.
However, I've hit a problem when trying to receive anything on another
timeslot than 0.
The TX side seems to work fine as the BTS can see my location update
request and answers with a reject, but on the MS side, I never see the
reject and wireshark only shows invalid incohrent data on the RX.
The frames for SDCCH/8 show really nothing valid (looks like random
bytes), things like
09 80 7f 47 49 06 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
09 00 47 d5 2d 06 1e 00 00 69 7c a0 91 3d 22 ff ab fe 6c 4f 56 4f 36
...
while the frames for the associated SAACH show at least something gsm-like :
03 03 01 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
but that's not quite a SI5/6 ...
To RX/TX on TS=1, I just delayed the RX/TX window by 625 bits (4 *
156.25) when I'm in dedicated channel mode by chaning the 'start' in
l1s_tx_win_ctrl / l1s_rx_win_ctrl
Is there something else that should be done ?
Cheers,
Sylvain
Hi Sylvain, hi list!
I'm experimenting with burst_ind and TCHs right now and ran
into some problem I couldn't solve yet.
After receiving an Assignment Command for a hopping TCH/F I
call l1ctl_tx_dm_est_req_h1() with all necessary parameters
and tch_mode GSM48_CMODE_SPEECH_V1 or _EFR.
After that I do get burst indications containing the received
bits on up- and downlink for the active arfcn on each
consecutive frame number.
BUT the rx level measurements are most of the time very low
and sporadic higher, surely not from that nearby bts and the
very close cellphone.
It looks like the layer1 doesn't "hit" the right timeslot
on the right arfcn at the right time.
There are some possible sources of error leading to that, like
hopping parameters, channel number and MA list.
But I checked these and I took all of them directly from the
ASS CMD, the MA as word list in ascending order, like in layer23
IMM ASS handling.
The specific AC doesn't have any specialties like Starting Time
or "before time" parameters.
So my question is if there is some obvious pitfall I'm missing
and are there any suggestions how to debug that?
Regards,
Mad
Hi,
I am trying to use burst_ind branch of osmocom. I have noticed that layer23 creates bursts****.dat files when it indicates uplink. What data are written to these files and what should I use to see its data? Thank you.
Hi!
Recently we've had the idea of using OsmocomBB with a simple firmware
that synchronizes to an existing GSM networks FCCH and use the resulting
13MHz clock to drive the USRP for airprobe or OpenBTS.
Ideally, we would even use the Calypso-internal PLL (for ARM or DSP) to
multiply it up to the required 52 MHz. However, neither the Openmoko
nor the Compal/Motorola phones expose any of the 3 clock output pads :(
So the only choice is to use something along the lines of the
http://focus.ti.com/docs/prod/folders/print/cdcvf25084.html
as a quad clock multiplier and attach it to the CLK13OUT signal of the
phone.
The chip is available for 9 USD in single quantities at digikey, and
possibly cheaper at other sources. Combined with a sub-20EUR phone it
might be a very cheap but still accurate frequency source for OpenBTS -
at least as long as there are any commercial gsm networks available.
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)
Hi All!
That's true, I managed to run U-Boot on MT6235, but linux kernel is
not fully functional yet (it's fresh stuff as I managed to ran it on
Tuesday and then I was off to conference).
For MT6235 development I chose Sciphone G2, which is pretty cheap.
After some time I managed to download code to SRAM (just 64KB) using
MTK's FlashTool.
MTK FlashTool communicates over UART directly with MT6235 bootloader
and sends its own chunk of code (about 58KB) which is executed in SRAM
and communicates with FlashTool.
I found on pudn.com some pack to customize code loaded by FlashTool,
thanks to which I could download my own code to SRAM (without JTAG).
The problem was that it had to be linked with some security libraries
which occupied about 56KB and not much memory left for my own code.
Then I decided to try find JTAG pins to get all control on MT6235.
That took me sometime, but finally I succeeded.
The other bigger issue was initializing DRAM controller to be able to
download bigger code (linux kernel + uboot) to external RAM. In
sciphone there is problem that all interesting chips are under metal
shield which is pretty havily soldered. In this case I couldn't read
what kind of RAM memory is mounted without destroying the board (I
don't have such soldering machine which could unsolder so big metal
shield). Thanks to JTAG I could attach to target and then dump DRAM
controller registers from processor running MTK's software, but
setting these values after processor start and configuration of PLL
didn't work.
I decided to disassemble bootloader which could show me how DRAM
controller is initialized and how code fron NAND is loaded (to be able
to flash U-Boot and kernel to NAND so MT6235 will start my code
automatically and I will not have to use JTAG). Currently I have
knowledge how internal MT6235 bootloader is loading code from memory
during startup and I also extracted procedure of DRAM controller
initialization. Thanks to that I'm able to run U-Boot from the very
begining of processor startup.
The problem is that I have just one piece of Sciphone G2 and I don't
want to flash it yet to not break existing code in it. Thanks to
running device I'm able to attach with JTAG and check how peripherals
are configured (i.e. LCD, MMC, etc.). I have backup of flash, but I'm
not 100% sure if I will flash it back, phone will startup. That's why
I bought second piece of Sciphone G2 and should receive it today or on
Tuesday (this Monday is holiday in Poland). In this case I'll flash
U-Boot to NAND and try to make it working. Then we could load the rest
of code from U-Boot (to RAM or NAND over serial).
You can see how my setup looks on attached picture.
The good thing about it is that the same bootloader is used in MT622x,
so it should be fairly easy to do the same on phones based on that
SoCs (but unfortuantely it's just ARM7).
If it comes to code, of course I can share it on "git.osmocom.org".
Currently it's just basic port of U-Boot and not much for linux
kernel, but I'm working on this now so I'll push it when it'll be
ready.
Currently I'm working on driver for NAND memory for U-Boot, so we
could flash linux kernel. When that will be ready I'll push the code.
Then I'll switch to linux kernel and when it'll be functional I also
push the code. At this stage you will not need to have JTAG and you
could load the code over serial in U-Boot.
If it comes to GSM I didn't work with it before. I actualy worked 6
months in L2/3 team for LTE (on RRC) but it's different story.
That could be really outstanding thing if we could run first phone
ever with whole code open (from BB up to APP).
BR,
Marcin
Hi guys,
I dunno if that is the right place for my concern about building the
osmocomBB source. Here is what I already have done:
- downloading the sources for osmocomBB and GNU toolchain for ARM,
- setting the PATH for the arm-elf-* executables,
- calling make in the src directory.
Now, this appears as response of the make command in the terminal:
cd shared/libosmocore/build-host && ../configure
configure: error: cannot find install-sh, install.sh, or shtool in ".."
"../.." "../../.."
make: *** [shared/libosmocore/build-host/Makefile] Error 1.
If you need details about my system, you can look at the following
snippet from the config.log file:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by libosmocore configure UNKNOWN, which was
generated by GNU Autoconf 2.65. Invocation command line was
$ ../configure
## --------- ##
## Platform. ##
## --------- ##
hostname = ubuntu-stefan
uname -m = x86_64
uname -r = 2.6.32-24-generic
uname -s = Linux
uname -v = #41-Ubuntu SMP Thu Aug 19 01:38:40 UTC 2010
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games
PATH: /home/stefan/osmocomBB/gnuarm-4.0.2/bin
## ----------- ##
## Core tests. ##
## ----------- ##
configure:2032: error: cannot find install-sh, install.sh, or shtool in
".." "../.." "../../..".
So, I would be very glad, if someone could give me a hint to solve the
problem. Thank you in advance.
Regards,
begy
Hi,
I could not resist buying a C116 for 15 euro, so I compiled osmocombb
and connected a 3.3V serial cable.
Of course the C116 was not in the supported list, but I was hoping it
would work as it seems that it is very similar to the C115.
Here is my load attempt: (used -m c123 ) but there's no loading of the image.
I am not using TX mode, also I don't have a SIM installed.
Anything I can try to get it working?
./osmocon -p /dev/ttyS0 -m c123xor
../../target/firmware/board/compal_e88/loader.compalram.bin
got 1 bytes from modem, data looks like: 00 .
got 2 bytes from modem, data looks like: 00 81 ..
got 4 bytes from modem, data looks like: 1b 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
read_file(../../target/firmware/board/compal_e88/loader.compalram.bin):
file_size=16788, hdr_len=4, dnload_le n=16795
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: 1b .
got 1 bytes from modem, data looks like: 66 f
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
Regards,
Henk
Hello
I'm having a problem in the start mobile application
~/osmocom-bb$ cd src/host/layer23/src/mobile
~/osmocom-bb/src/host/layer23/src/mobile$ ./mobile
Copyright (C) 2008-2010 ...
Contributions by ...
License GPLv2+: GNU GPL version 2 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Failed to parse the config file: '/etc/osmocom/osmocom.cfg'
Please check or create config file using: 'touch /etc/osmocom/osmocom.cfg'
~/osmocom-bb/src/host/layer23/src/mobile$
Please help me as soon as
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Help-me-I-have-a-difficult-probl…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hi,
I've put together a small program that puts Nokia 3310 phones into
debug mode (via serial/USB cable) and forwards all sent/received GSM
messages and SIM APDUs via GSMTAP to be viewed realtime in Wireshark.
This allows you to see the message flows for a real phone on a real
network.
Nokia 3310's are very cheap and easy to come by, so should appeal to a
wide audience.
Thought osmocom might be a good home for this utility - could it go
into git, and a short page on bb.osmocom.org?
Duncan
Hello techies!
I am new to the list and I acquired a c139. I'd like to buy a rs232/jack
2,5mm named t191 flash (and not unlock) cable. They look 100% the same (even
stickers). Is this important? I understand that I have also to use a
rs232/usb adapter. The one I have (U232P9 with link/tx/rx leds) gives +/-9,4
v. So my concern is to not fry the Moto..Any advise welcome.
Cheers.
hi all,
About voice,I have one question.
In the latest git code, when I use bb to call other phone, it will product a
file voice.raw.
How I can play the voice.raw?
which kind of format? 16bit or 8 bit pcm?16khz and 8khz?LSE or MSE?
In fact i used the cooledit to play it, both 16khz and 8khz, it has only
noise.
Other question, I want to input voice from pc that run BB, then the voice
can be sent by C123.
But I found the voice that be sent by C123 is C123 input voice.
Can we realize the idea?
Best Regards
Shrek W
Hi!
Is AreasOfWork in the wiki still up to date? I intend to work on the UI
(Sorry Dieter, GSM testset too expensive at the moment :( ) and want to
choose a RTOS. A small collection that I came across:
FreeRTOS
What is the problem?
TNKernel
http://www.tnkernel.com/tn_description.html
Scheduler, Mutexes, Queues, etc. available
strange (at least unfamiliar) API for memory
eCos
http://ecos.sourceware.org/about.html
many target MCUs but are their any other than ARM in BB chipsets?
powerful but complex (at least at first glance)
NUT/OS
http://www.ethernut.de/en/
minimalistic RTOS, easy to port
seems to have sound community
familiar APIs: malloc, fopen's devices, ...
cooperative multithreading: Is that OK? We still have IRQs for
realtime...
Since we seem to barely need an OS, a full-blown OS like eCos seems
excessive. For compatibility with MT6235 user space, malloc and fopen is
the right direction. Hence, my favourite is NUT/OS. In fact, I tried
porting it to calypso just for fun. With some wrappers, Osmocom's
platform files can be used. Only turns on the backlight and occasionally
outputs some bytes on the UART at the moment. However, I still call this
success. It took me just a day from knowing nothing about NUT/OS and
very little about calypso and ARM to do this. Seems promising in terms
of portability and documentation to me.
Open question: How much overhead can we afford, i.e., how much spare
time is there on the CPU? Does "Disable RTC interrupt as it causes lost
TDMA frames" (layer1/init.c) indicate issues? (Yes, sorry, haven't read
GSM specs yet...) If yes, is it reasonable to independently handle GSM
stuff with FIQ and only give IRQ to whatever OS we choose?
Regards,
Stefan
Hi,
good news: mails are back
bad news: phone lost a battery pin :(
Here are two small patches to help the mediatek-branch compile without calypso
references. These were tested before the breakage and 'make all' still builds
fine for compal.
Regards,
Wolfram
Wolfram Sang (2):
comm: msgb: don't set backlight on error
lib: move delay.c from calypso to lib
src/target/firmware/calypso/Makefile | 2 +-
src/target/firmware/calypso/delay.c | 16 ----------------
src/target/firmware/comm/msgb.c | 1 -
src/target/firmware/lib/Makefile | 2 +-
src/target/firmware/lib/delay.c | 16 ++++++++++++++++
5 files changed, 18 insertions(+), 19 deletions(-)
delete mode 100644 src/target/firmware/calypso/delay.c
create mode 100644 src/target/firmware/lib/delay.c
--
1.7.2.5
Hi Sylvain, hi list!
I saw you commiting a generic viterbi de-/encoder in libosmocore core/conv.c. Just when I started to learn how to implement something like that some days ago... :-)
Now I'd like to know if there are also some precomputed tables available for next_output and next_state implementing the convolution codes described in GSM 05.03/3.9.
Regarding the soft input bits to the algo, my guess is when just having hard bits you have to simply convert 1 to 127 and 0 to -127 in sbit_t, right?
And what came to my mind while reading the code is that couldn't you improve its performance on punctured codes by remembering the re-inserted bits and excepting them from next accumulated error calculation (line 291)?
If I'm understanding viterbi the right way, as punctured bits doesn't contain any information and introduce some random additional error, only real input bits should be incorporated in state decisions.
Regards,
Mad
It shows the communication messages like Osmocom? Does it also supports SMS messages?
Maybe you can also write a small wiki on how to use (with Wireshark).
Hi,
do the following assumptions and conclusions make sense?
- The Sciphone G2 is intended as a platform where we want to run L1/2/3
natively on Linux (somewhen).
- Thus, from all the applications in osmocom-bb for the targets, we only
need the loader to get the first bootloader onto the system (in case
JTAG is not available or wanted)
- Being that different, it doesn't make sense to fit the
mediatek-platform into the existing makefile-templates which build all
applications for all boards.
I'd suggest to create a new top-level target "mtk" which only builds the
loaders for mediatek-phones. All unneeded applications and libraries are
skipped. A preview of a possible directory-structure to add mtk-support
could look like this then:
.
├── board
│ ├── mediatek
│ │ ├── exceptions_redirected.S
│ │ ├── exceptions_redirect.S
│ │ ├── handlers.S
│ │ ├── header.S
│ │ ├── macros.S
│ │ ├── ram.lds
│ │ ├── start.ram.S
│ │ ├── start.rom.S
│ │ └── uart.c
│ └── mt62xx
│ └── init.c
└── include
└── mtk
├── bfe.h
├── bpi.h
├── bsi.h
├── emi.h
├── mt6235.h
├── mt6235_sciphone_g2.h
├── system.h
└── tdma_timer.h
It can be cleaned up a bit once there is a working state. Of course, a
few modifications to makefiles are also needed. Note there is now a
seperate uart.c in the mediatek-folder.
Any objections? Anything I missed?
Regards,
Wolfram
Hi All,
I am trying to transmit voice with my GTA02 and Osmocom. Upon looking into code I did not find any code transmitting voice. I have tried to do it myself but without much success.
What have I done:
1. Merge branch "jolly/voice" into main.
2. Add handling of L1CTL_VOICE_REQ at l23_api.c
3. Create additional queue for voice requests to be handled within the scheduler
4. Create "loopback" code, issuing L1CTL_VOICE_REQ each time voice is received at layer23
5. At l1s_tch_cmd, add code, sending the frame from voice request queue, similar to code, sending FACCH frame.
6. During tests against OpenBTS, it appears, that the voice frames are being sent, but all of them have "Stolen" bit turned on, e.g. BTS considers them FACCH frames.
My question is how do I transmit TCH frame with "Stolen" indicator turned off.
Or even better, is there any other implementation of transmitting voice via TCH?
Code fragment from l1s_tch_cmd,
------------------------------------------------------------------------------------------------
if (facch_tx_now) {
uint16_t *info_ptr = dsp_api.ndb->a_fu;
struct msgb *msg;
const uint8_t *data;
/* Pull FACCH data (if ready) */
if (icnt > 26)
{
msg = msgb_dequeue(&l1s.tx_queue[L1S_CHAN_MAIN]);
if(!msg && (tch_mode == TCH_FS_MODE))
{
msg = msgb_dequeue(&l1s.tx_queue[L1S_CHAN_VOICE]);
if(msg && msg->l3h)
{
tx_sent++;
printf("rx_frames: %d tx_recv: %d tx_sent: %d\n", rx_frames, tx_recv, tx_sent);
printf("l1s_tch_cmd: voice data = %s\n", hexdump(msg->l3h, 33));
}
}
}
else
{
msg = NULL;
}
------------------------------------------------------------------------------------------------
Many thanks
Michael
Hello List,
If any one on the list have time to take my assignment to develop tool
to tune C118 to sniff
it must be able to enter/input parameter with full signalling and voice support
also tell me you development Fees and remuneration for this work.
1 ARFCN
2 TS ( time slot)
3 Hoping sequence
I would like students or free time programmers to develop custom
application for sniffing on c118
it should be cable for manually entries for (as option of command line)
means the tool must be able to tune C118 in Mobile application mode(
under full voice function)
the desired parameter of user's choice
1 ARFCN
2 TS ( time slot)
3 Hoping sequence
it is something we can tune C118 in full voice support to our own
choice of AFRCN TS and hopping sequence we must be able to manually
enter these parameter while MS is in mobile application mode( DSP in
full voice support)
I would like you to decide your remunerations /expanses/ development fees.
http://bb.osmocom.org/trac/wiki/Sniffing
Kind Regards,
Maten
On Mon, Apr 25, 2011 at 5:04 AM, Marten Christophe
<technosabby(a)gmail.com> wrote:
> Hello List,
>
> I would like students or free time programmers to develop custom
> application for sniffing
>
> it should be cable for manually entries for (as option of command line)
> means the tool must be able to tune C118 in Mobile application mode(
> under full voice function)
> the desired parameter of user's choice
>
> 1 ARFCN
> 2 TS ( time slot)
> 3 Hoping sequence
>
> it is something we can tune C131 in full voice support to our own
> choice of AFRCN TS and hopping sequence we must be able to manually
> enter these parameter while MS is in mobile application mode( DSP in
> full voice support)
>
> I would like you to decide your remunerations /expanses/ development fees.
>
> http://bb.osmocom.org/trac/wiki/Sniffing
>
> Kind Regards,
> Maten
>
>
> ==========
> ========
> Hi,
>
>
> Since a lot of people are asking the same questions and there seems to
> be a rush on the C123 on ebay I tought some clarification is needed.
>
>
> Short version:
> - The exact tools I used on stage are _not_ and will _not_ be
> released (or sold ... several people asked ...)
> - Any one willing to re-code them without any apriori knowledge of
> GSM would most likely need months to read/understand both the
> specifications and the way the code works. (That's thousands of page
> of GSM spec and thousands of line of code)
> - Osmocom-BB project is not designed to be a sniffer, it's a baseband
> implementation, I just used part of it as a base.
>
> So basically, unless you are really interested in GSM and are willing
> to dedicate time to understand it deeply and to contribute the various
> projects, there is not much point in you buying phones, or hanging out
> in the ml/irc or whatever ...
>
>
> For those who are still reading and interested here's a little more detail:
>
> * The HLR query step:
> -> Go watch the awesome 25C3 talk about it
>
> * The TMSI recovering step
> - Won't be published
> - If you know how paging works, you know what to do anyway and it's
> trivial. Method is in the talk,
> there is nothing to it.
>
> * The targeted sniffing application
> - Won't be published either
> - Some improvements to the layer23 app frame work will be done but
> these are generic framework stuff, not app-specific
> - Again, if you know how L2 works and have looked at several traces,
> it's obvious what to do.
> - The 'DSP' part of the sniffer is public for a while with a small
> demo app (single phone and doesn't exploit the full potential of the
> DSP patch) and it's perfectly sufficient to debug things on your o
> wn controlled network. (This is basically what I showed at Deepsec 2010).
>
> * The tool to generate the input to Kraken
> - Won't be published either
> - Making the guesses is easy for anyone that knows what he's doing.
>
> * The improved Kraken
> - No idea about it, see with Karsten / Sacha / Frank, I only got
> access to it 1 hour or so before the talk :)
>
> * Conversion from burst to audio
> - This was a hacked software mostly with airprobe code.
> - The exact app will not be released but I'd like to see the
> capability put in some clean library we
> can re-use from airprobe and other application without having to
> multiply the code each time.
> - ... But since I'd like it to support AMR and viterbi softoutput
> before that happens, it could take
> some time.
> - Anyone familiar with GSM, airprobe and C could re-hack the same
> thing in an hour ...
>
> As you can see, everything you need to analyze your own network / your
> own traffic, even at the burst level is already published and has been
> for more than a month.
> The other tools have been written only so that we could demonstrate
> that what we _say_ is possible for about year, we can now do it
> _practically_. It's apparently needed to get people attentions,
> "theoretical" attacks are not enough to get the operators / gsma to
> react. We'll see if that did it ...
>
>
> A few advices that are always good:
>
> - Make sure to checkout the a5/1 project ML and airprobe project ML and try
> to ask your questions in the proper mailing list as much as possible.
> - Check the wiki and mailing list archives toroughly before asking questions.
>
>
> Cheers,
>
> Sylvain Munaut
>
>
> PS: I only posted on this list because it seems a lot of people were
> pointed here while in fact airprobe would probably be more appropriate
> to discuss attack scenarios and such, so make sure to answer / start
> new discussion on the right list.
>
From: Pablo Neira Ayuso <pablo(a)gnumonks.org>
This patch gets osmocom-bb in sync with libosmocore 0.2.0.
Basically, I invoked git-subtree to get a fresh libosmocore tree
(currently 0.2.0) and change all the include paths to point to the
new osmocom/[core|gsm] directories.
You can get these changes from the pablo/libosmocore-updates branch.
Please, merge it!
Pablo Neira Ayuso (1):
src: use new libosmogsm and include/osmocom/[gsm|core] path to
headers
Hi,
I'm having the same problem and as far as I've understood, you need a different serial or usb cableThe program is trying to set a high baud rate which is not supported by your cable.To the best of my understanding a FTDI usb to serial cable it's needed, because this supports higher baud rates.
Loretta
----Messaggio originale----
Da: cnwutong(a)gmail.com
Data: 25-apr-2011 6.01
A: <baseband-devel(a)lists.osmocom.org>
Ogg: running error with branch burst_ind
Hi all,
Working with a C118 and everything was fine with the master branch, then switched to the burst_ind branch and complied successfully, when running:
$ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/layer1.compalram.bingot 1 bytes from modem, data looks like: 2f /got 1 bytes from modem, data looks like: 00 .
got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....Agot 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/layer1.compalram.bin): file_size=48564, hdr_len=4, dnload_len=48571got 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 Agot 1 bytes from modem, data looks like: 02 .
got 1 bytes from modem, data looks like: 43 CReceived PROMPT2 from phone, starting downloadhandle_write(): 4096 bytes (4096/48571)handle_write(): 4096 bytes (8192/48571)handle_write(): 4096 bytes (12288/48571)
handle_write(): 4096 bytes (16384/48571)handle_write(): 4096 bytes (20480/48571)handle_write(): 4096 bytes (24576/48571)handle_write(): 4096 bytes (28672/48571)handle_write(): 4096 bytes (32768/48571)
handle_write(): 4096 bytes (36864/48571)handle_write(): 4096 bytes (40960/48571)handle_write(): 4096 bytes (45056/48571)handle_write(): 3515 bytes (48571/48571)handle_write(): finished
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 Agot 1 bytes from modem, data looks like: 03 .got 1 bytes from modem, data looks like: 42 BReceived DOWNLOAD ACK from phone, your code is running now!
ioctl(TIOCSSERIAL): Invalid argument
$ ./mobileCopyright (C) 2008-2010 ...Contributions by ...
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law.
VTY available on port 4247.No Mobile Station defined, creating: MS '1'
<000e> sim.c:1206 init SIM client<0005> gsm48_cc.c:61 init Call Control<0001> gsm48_rr.c:4944 init Radio Ressource process<0004> gsm48_mm.c:1220 init Mobility Management process
<0004> gsm48_mm.c:971 Selecting PLMN SEARCH state, because no SIM.<0002> gsm322.c:3471 init PLMN process<0003> gsm322.c:3472 init Cell Selection process<0003> gsm322.c:3526 No stored BA list
Mobile '1' initialized, please start phone now!
then no reaction with the mobile application either rebooting the phone (press power bottom) or not, for layer23 application acts the same.
tried to search for the message "ioctl(TIOCSSERIAL): Invalid argument" but failed to get any useful information.
could anyone help and many thanks for your time and considerations!
best regards,
flaw
Hi all,
Working with a C118 and everything was fine with the master branch, then
switched to the burst_ind branch and complied successfully, when running:
$ ./osmocon -p /dev/ttyUSB0 -m c123xor
../../target/firmware/board/compal_e88/layer1.compalram.bin
got 1 bytes from modem, data looks like: 2f /
got 1 bytes from modem, data looks like: 00 .
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/layer1.compalram.bin):
file_size=48564, hdr_len=4, dnload_len=48571
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(): 4096 bytes (4096/48571)
handle_write(): 4096 bytes (8192/48571)
handle_write(): 4096 bytes (12288/48571)
handle_write(): 4096 bytes (16384/48571)
handle_write(): 4096 bytes (20480/48571)
handle_write(): 4096 bytes (24576/48571)
handle_write(): 4096 bytes (28672/48571)
handle_write(): 4096 bytes (32768/48571)
handle_write(): 4096 bytes (36864/48571)
handle_write(): 4096 bytes (40960/48571)
handle_write(): 4096 bytes (45056/48571)
handle_write(): 3515 bytes (48571/48571)
handle_write(): finished
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: 03 .
got 1 bytes from modem, data looks like: 42 B
Received DOWNLOAD ACK from phone, your code is running now!
ioctl(TIOCSSERIAL): Invalid argument
$ ./mobile
Copyright (C) 2008-2010 ...
Contributions by ...
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
VTY available on port 4247.
No Mobile Station defined, creating: MS '1'
<000e> sim.c:1206 init SIM client
<0005> gsm48_cc.c:61 init Call Control
<0001> gsm48_rr.c:4944 init Radio Ressource process
<0004> gsm48_mm.c:1220 init Mobility Management process
<0004> gsm48_mm.c:971 Selecting PLMN SEARCH state, because no SIM.
<0002> gsm322.c:3471 init PLMN process
<0003> gsm322.c:3472 init Cell Selection process
<0003> gsm322.c:3526 No stored BA list
Mobile '1' initialized, please start phone now!
then no reaction with the mobile application either rebooting the phone
(press power bottom) or not, for layer23 application acts the same.
tried to search for the message "ioctl(TIOCSSERIAL): Invalid argument" but
failed to get any useful information.
could anyone help and many thanks for your time and considerations!
best regards,
flaw
I have been trying to compile the latest osmocom-bb build target binaries
directly on my Freerunner, which is running Om2008.8.
uname -a // Linux om-gta02 2.6.28-rc4 #1 PREEMPT Mon Mar 2 19:43:22 CET 2009
armv4tl unknown
Unfortunately, I am getting an error during compilation in:
directory // `/src/shared/libosmocore/build-target/src'
GCC output:
make[3]: Entering directory
`/home/root/osmocom/src/shared/libosmocore/build-target/src'
make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] Error 2
> Making all in .
> make[4]: Entering directory
> `/home/root/osmocom/src/shared/libosmocore/build-target/src'
> CC gsmtap_util.lo
> In file included from ../../src/gsmtap_util.c:37:
> /usr/include/netinet/in.h:365: error: expected declaration specifiers or
> '...' before '(' token
-sh: syntax error: "(" unexpected
root@om-gta02 ~/osmocom/src $ /usr/include/netinet/in.h:365: error: expected
')' before '?' token
-sh: /usr/include/netinet/in.h:365:: not found
root@om-gta02 ~/osmocom/src $ /usr/include/netinet/in.h:366: error: expected
declaration specifiers or '...' before '(' token
-sh: /usr/include/netinet/in.h:366:: not found
root@om-gta02 ~/osmocom/src $ /usr/include/netinet/in.h:366: error: expected
')' before '?' token
-sh: /usr/include/netinet/in.h:366:: not found
root@om-gta02 ~/osmocom/src $ /usr/include/netinet/in.h:368: error: expected
declaration specifiers or '...' before '(' token
-sh: /usr/include/netinet/in.h:368:: not found
root@om-gta02 ~/osmocom/src $ /usr/include/netinet/in.h:368: error: expected
')' before '?' token
-sh: /usr/include/netinet/in.h:368:: not found
root@om-gta02 ~/osmocom/src $ /usr/include/netinet/in.h:370: error: expected
declaration specifiers or '...' before '(' token
-sh: /usr/include/netinet/in.h:370:: not found
root@om-gta02 ~/osmocom/src $ /usr/include/netinet/in.h:370: error: expected
')' before '?' token
-sh: /usr/include/netinet/in.h:370:: not found
root@om-gta02 ~/osmocom/src $ ../../src/gsmtap_util.c: In function
'gsmtap_fd_cb':
-sh: ../../src/gsmtap_util.c:: not found
root@om-gta02 ~/osmocom/src $ ../../src/gsmtap_util.c:155: warning: implicit
declaration of function 'perror'
-sh: ../../src/gsmtap_util.c:155:: not found
root@om-gta02 ~/osmocom/src $ make[4]: *** [gsmtap_util.lo] Error 1
A google search for "implicit declaration of function 'perror'" made it look
like I am missing header declarations included in the "build-essential"
packages, but this package does not exist for Om2008.8. I have included my
config.log. Any ideas what I am missing?
-Alex
http://baseband-devel.722152.n3.nabble.com/file/n2851445/config.log
config.log
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Osmocom-Freerunner-compilation-i…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hi all,
i'm selling my Wavetek 4201s.
Unfortunately some days ago i was upgrading the firmware and the power went down.
Now it stucks at initializing process.
http://tinyurl.com/3dnetqu
As you can see was fully working and i used it to make tests with osmocomBB and airprobe.
http://tinyurl.com/43exn2shttp://tinyurl.com/3qlvz52
As i guess, is possible to repair the corrupted firmware through serial or an internal jtag, unfortunately i have no time to do it and i'm buying another one.
I bought it, 3 months ago, fully calibrated and working. (payed 750 €).
About the price i thought around 250 euro (because is only a software problem and on ebay is still around 1500 €).
About the shipping… will be signed-for (from 4 to 7 days Worldwide), around 30 €.
About the payment: Paypal (i'll value other ways, if suggested).
What is included:
- Wavetek 4201s
- Power cable (EU)
- Serial Cable
- Coupler Antenna R&S CMD-z10 (see here: http://tinyurl.com/3fxf4t8 )
- Manual (IT)
- Firmware upgrades by email
If someone is interested, please contact me.
Thank you for attention
Cheers
Luca Bongiorni
P.S: I apologize for the spam, but i thought that here is the right place to find people with enough skills, time and few money to repair and use it, instead to leave him on the desk and accumulating dust.
Hello List,
I would like students or free time programmers to develop custom
application for sniffing
it should be cable for manually entries for (as option of command line)
means the tool must be able to tune C131 in Mobile application mode(
under full voice function)
the desired parameter of user's choice
1 ARFCN
2 TS ( time slot)
3 Hoping sequence
it is something we can tune C131 in full voice support to our own
choice of AFRCN TS and hopping sequence we must be able to manually
enter these parameter while MS is in mobile application mode( DSP in
full voice support)
I would like you to decide your remunerations /expanses/ development fees.
http://bb.osmocom.org/trac/wiki/Sniffing
Kind Regards,
Maten
==========
========
Hi,
Since a lot of people are asking the same questions and there seems to
be a rush on the C123 on ebay I tought some clarification is needed.
Short version:
- The exact tools I used on stage are _not_ and will _not_ be
released (or sold ... several people asked ...)
- Any one willing to re-code them without any apriori knowledge of
GSM would most likely need months to read/understand both the
specifications and the way the code works. (That's thousands of page
of GSM spec and thousands of line of code)
- Osmocom-BB project is not designed to be a sniffer, it's a baseband
implementation, I just used part of it as a base.
So basically, unless you are really interested in GSM and are willing
to dedicate time to understand it deeply and to contribute the various
projects, there is not much point in you buying phones, or hanging out
in the ml/irc or whatever ...
For those who are still reading and interested here's a little more detail:
* The HLR query step:
-> Go watch the awesome 25C3 talk about it
* The TMSI recovering step
- Won't be published
- If you know how paging works, you know what to do anyway and it's
trivial. Method is in the talk,
there is nothing to it.
* The targeted sniffing application
- Won't be published either
- Some improvements to the layer23 app frame work will be done but
these are generic framework stuff, not app-specific
- Again, if you know how L2 works and have looked at several traces,
it's obvious what to do.
- The 'DSP' part of the sniffer is public for a while with a small
demo app (single phone and doesn't exploit the full potential of the
DSP patch) and it's perfectly sufficient to debug things on your o
wn controlled network. (This is basically what I showed at Deepsec 2010).
* The tool to generate the input to Kraken
- Won't be published either
- Making the guesses is easy for anyone that knows what he's doing.
* The improved Kraken
- No idea about it, see with Karsten / Sacha / Frank, I only got
access to it 1 hour or so before the talk :)
* Conversion from burst to audio
- This was a hacked software mostly with airprobe code.
- The exact app will not be released but I'd like to see the
capability put in some clean library we
can re-use from airprobe and other application without having to
multiply the code each time.
- ... But since I'd like it to support AMR and viterbi softoutput
before that happens, it could take
some time.
- Anyone familiar with GSM, airprobe and C could re-hack the same
thing in an hour ...
As you can see, everything you need to analyze your own network / your
own traffic, even at the burst level is already published and has been
for more than a month.
The other tools have been written only so that we could demonstrate
that what we _say_ is possible for about year, we can now do it
_practically_. It's apparently needed to get people attentions,
"theoretical" attacks are not enough to get the operators / gsma to
react. We'll see if that did it ...
A few advices that are always good:
- Make sure to checkout the a5/1 project ML and airprobe project ML and try
to ask your questions in the proper mailing list as much as possible.
- Check the wiki and mailing list archives toroughly before asking questions.
Cheers,
Sylvain Munaut
PS: I only posted on this list because it seems a lot of people were
pointed here while in fact airprobe would probably be more appropriate
to discuss attack scenarios and such, so make sure to answer / start
new discussion on the right list.
Hi all, my name is Jose Pereira, and i'm very interested in helping you with
some code! I've wrote the buzzer driver for calypso, not so sure if will
help you of anything, but was just for experimenting :)
Anyway, i send the patch in attachement. The interface can be simply
#include <calypso/buzzer.h>
buzzer_mode_pwt(1);
buzzer_volume(40);
buzzer_note(NOTE(NOTE_E,OCTAVE_5));
Please let me know what do you think of the code, and in what way i can
further help.
Best regards,
--
José Pereira
http://onaips.blogspot.com
Hi,
i launched following commands:
1) ./osmocon -p /dev/ttyUSB0 -m c140xor -c
../../target/firmware/board/compal_e86/layer1.highram.bin
../../target/firmware/board/compal_e86/chainload.compalram.bin
http://pastebin.com/xcJTuNDF
2) ./mobile -i 127.0.0.1 http://pastebin.com/h3aPFgs1
3) telnet localhost 4247 http://pastebin.com/7nA7KbN8
mobile.cfg: http://pastebin.com/FBM6PCqq
unfortunately wireshark 1.5+ devel) or tcpdump couldn't sniff any traffic on
lo-interface. can anyone find a missconfiguration?
any hint would be awesome! thank you :)
Hi everybody,
I looked a bit more at the code and output of the mobile application, and it
seems the problem is that the connection
is always dropped because of channel sync failure.
Sylvain suggested (to someone having a similar problem) to use the stick
option, and actually after trying this,
I observed a different behavior it seems the phone performed the
identification and the authentication procedures
and during a different trial the location update was performed.
Can someone explain the stick option?
Anyway, I still can't receive or make calls this is what usally happens when
trying to make a call
<0007> mnccms.c:534 Make call to 150
<0007> mnccms.c:150 support TCH/H also
<0007> mnccms.c:174 support full rate v2
<0007> mnccms.c:178 support full rate v1
<0007> mnccms.c:187 support half rate v1
<0005> gsm48_cc.c:496 Sending MMCC_EST_REQ
<0004> gsm48_mm.c:3568 (ms 1) Received 'MMCC_EST_REQ' event in state MM idle
<0004> gsm48_mm.c:3571 -> substate normal service
<0004> gsm48_mm.c:3573 -> callref 8, transaction_id 255
<0004> gsm48_mm.c:2873 Init MM Connection.
<0004> gsm48_mm.c:1332 New MM Connection (proto 0x03 trans_id 255 ref 8)
<0004> gsm48_mm.c:1291 (ref 8) new state IDLE -> CONN_PEND
<0004> gsm48_mm.c:2650 CM SERVICE REQUEST (cause 9)
<0004> gsm48_mm.c:2685 -> Using IMSI 234-------------
<0001> gsm48_rr.c:4911 (ms 1) Message 'RR_EST_REQ' received in state idle
<0001> gsm48_rr.c:4271 Not camping normally, rejecting! (cs->state = 7)
<000d> gsm48_rr.c:4241 Establishing radio link not possible
<0004> gsm48_mm.c:887 new state MM IDLE, normal service -> wait for RR
connection (MM connection)
<0004> gsm48_mm.c:3695 (ms 1) Received 'RR_REL_IND' from RR in state wait for
RR connection (MM connection)
<0004> gsm48_mm.c:1367 Release any MM Connection
<0004> gsm48_mm.c:1348 Freeing MM Connection
<0004> gsm48_mm.c:1291 (ref 8) new state CONN_PEND -> IDLE
<0004> gsm48_mm.c:1055 We are in registered LAI as returning to MM IDLE
<0004> gsm48_mm.c:892 new state wait for RR connection (MM connection) -> MM
IDLE, normal service
<0005> gsm48_cc.c:2122 (ms 1) Received 'MMCC_ERR_IND' in CC state
MM_CONNECTION_PEND
<0005> gsm48_cc.c:189 (ms 1 ti ff) Sending 'MNCC_REL_IND' to MNCC.
<0007> mnccms.c:336 Call has been released (cause 21)
Can someone help me with this? I do not understand why is not possible to
establish the radio link,
and does anyone know where I can find out what 'cause 21' means?
Thanks,
loretta
Sip! Que tal? Pebsaba contactar con los españoles de la lista, pero no he tenido tiempo :P
Enviado desde mi iPhone
El 18/04/2011, a las 06:55, "Pedro Collado" <edrocoyote(a)yahoo.es> escribió:
> por el nombre
>
>
Sorry about that , darn gmail.....
Yes , nuttx seems pretty OK and it's author is very nice , a man to
work with. The problem would be that it's written by just one man and
I don't even know how it's doing on the GUI side.
Nuttx though seems more oriented towards micro controllers and and
targets with less resources.
As for nano-x it's one of the lightest GUIs around and I don't know if
there really are any better options for embedded open source graphics.
It's not really an X11 , not a full one anyway. And from what I've
heard you can get it to about 100 K which is certainly something in my
opinion.
On Tue, Apr 19, 2011 at 9:00 PM, Marius Cirsta <mforce2(a)gmail.com> wrote:
> Yes , nuttx seems pretty OK and it's author is very nice , a man to
> work with. The problem would be that it's written by just one man and
> I don't even know how it's doing on the GUI side.
> Nuttx though seems more oriented towards micro controllers and and
> targets with less resources.
>
> As for nano-x it's one of the lightest GUIs around and I don't know if
> there really are any better options for embedded open source graphics.
> It's not really an X11 , not a full one anyway. And from what I've
> heard you can get it to about 100 K which is certainly something in my
> opinion.
>
> On Tue, Apr 19, 2011 at 5:59 PM, Alan Carvalho de Assis
> <acassis(a)gmail.com> wrote:
>> Hi Harald,
>>
>> On 4/18/11, Harald Welte <laforge(a)gnumonks.org> wrote:
>>>
>>> I have never found the time to actually make that decision/selection,
>>> so there is no status update.
>>>
>>> I'd still like to have a say in the decision, but I'm welcome for the
>>> discussion that has started right now and definitely like to look at
>>> the proposals (like ethernut OS)
>>>
>>
>> I think we could consider NuttX as well:
>>
>> http://nuttx.sourceforge.net
>>
>> This RTOS implements POSIX APIs and have many features "inherited" from Linux.
>> It is completely reconfigurable to fit small foot-print microcontrollers.
>>
>> Just my 2 cents, I hope someone enjoy it.
>>
>> Best Regards,
>>
>> Alan
>>
>>
>
Thanks for your answers.
I assume that the 0.2v instead of the 3.3v at the jack shouldn't fry my GSM,
just wanted to know if someone had the same "issue".
Best regards.
Hello everyone,
> From: Dave Schmidt
> Sent: 04/18/11 04:09 PM
[...]
> Preparing block 45, block checksum is 0x97
> handle_write_block(): 1024 bytes (1024/1024)
> handle_write_block(): Block 45 finished
>
> ...and it stalls at this point.
After re-flashing of the phone, osmocom loads again. So this should be considered as "closed". Sorry for a false alarm.
D.
Hello and sorry to bother you for such little issue:
I finally received the t191 cable and connected it to my rs232/usb
converter. I only get 0.2v out at the 2,5mm jack, is this voltage workable,
does someone faced the same ?... By the way, my Moto c139 is SIM locked, is
this also a problem ?
Thanks for any advices.
Hello everyone,
I have compiled osmocon binary for Neo Freerunner (after receiving explanations from the list - thanks Alex!). It worked... during some time. Now the loading does not finish:
# ./osmocon -i 13 -m romload -p /dev/ttySAC0 layer1.highram.bin
Sending Calypso romloader beacon...
Sending Calypso romloader beacon...
...
Received parameter ack from phone, starting download
...
Preparing block 44, block checksum is 0x8c
handle_write_block(): 1024 bytes (1024/1024)
handle_write_block(): Block 44 finished
Received block ack from phone
Preparing block 45, block checksum is 0x97
handle_write_block(): 1024 bytes (1024/1024)
handle_write_block(): Block 45 finished
...and it stalls at this point. Altogether, there were 47 blocks, if I remember right (so the feeling is that "I'm so close to it" :-))). The phone is otherwise accessible (via ssh).
Any highlights on what could go wrong? I can't remember having "done" anything at all to the phone...
Dave.
Hi all,
I've been trying to connect a phone to the network with the mobile
application, using Sylvain testing.
Anyway it seems I am stuck: the phone can't perform a location update and
can't attach to any network, and I don't understand what is going wrong
can you help me with this?
I attached some of the output from 'mobile', can you see anything wrong with
it?
Thanks,
Loretta
cool. it would help, if you check the debug and especially the cell
infos ("show cell" / "show cell xxx"), if "PCS" is shown behind the
channel number. additionally i would like to know if a 850 cell which
"talks about" PCS neighbour frequencies is shown correctly in the cell
info.
________________________________
Von: 246tnt(a)gmail.com [mailto:246tnt@gmail.com]
Gesendet: Freitag, 15. April 2011 11:31
An: Harald Welte
Cc: Bjoern Heller; baseband-devel(a)lists.osmocom.org; Andreas.Eversberg
Betreff: Re: Re: support for GSM 850 / 1900
Hi,
I'll also try to test it when I'm in the US end of next month, so that
there is multiple networks and neighbour cells and such.
Cheers,
Sylvain
hi,
did anyone ever tested or is willing to test these two bands? i made a
branch "origin/jolly/quadband" some time ago. i would like to merge it,
but i would like to do some tests before.
regards,
andreas
Hi wgb_1000,
I am pasting to this email an example of the mobile config file, anyway if you have problem starting the mobile applicationbecause the file does not exist, just create an empty one. Afterwards, you can save the config file via telnet with the command write.Let's say you want the sim mode to be reader by default, you can type the command 'sim reader' and then the command 'write' and next time you run the mobile application the sim mode will be reader.
Anyway Iam just a beginner, so I hope anyone more expert will correct me if I misunderstood.
Regards,Loretta
!
! OsmocomBB () configuration saved from vty
!!
!
line vty
no login
!
gps device /dev/ttyACM0
gps baudrate default
no gps enable
!
ms 1
layer2-socket /tmp/osmocom_l2
sap-socket /tmp/osmocom_sap
sim none
network-selection-mode auto
imei 000000000000000 0
imei-fixed
no emergency-imsi
no call-waiting
no auto-answer
no clip
no clir
tx-power auto
no simulated-delay
no stick
location-updating
codec full-speed prefer
codec half-speed
no abbrev
support
sms
----Messaggio originale----
Da: wbg_1000(a)yahoo.com
Data: 14-apr-2011 13.20
A: <baseband-devel(a)lists.osmocom.org>
Ogg: mobile application config file
Hi.
I haven't found it documented anywhere, what's the config file for mobile application suppose to contain? It contains commands that you could also send by telnet to the application?
Thanks.
Hi.
I haven't found it documented anywhere, what's the config file for mobile application suppose to contain? It contains commands that you could also send by telnet to the application?
Thanks.
hi all,
I thought this could be of some help.
i bought a usb (not serial, but they have the serial as well) T191 cable from
this online store. It arrived in 3 days.
http://www.fonefunshop.co.uk/datacables/motorola.htm
Hi all,
sorry to bother you for this, but after compiling everything and having the
osmocon and mobile application working,
I found out that the layer23 application is missing.
Can you help me understanding which one are the sources for it and which make
file is responsible for its compilation,
I really can't figure out what went wrong.
Thanks,
Loretta
Hi
>----Messaggio originale----
>Da: wpatan(a)gmail.com
>Data: 13-apr-2011 8.16
>A: <baseband-devel(a)lists.osmocom.org>
>Ogg: Re: online shop for usb T191 cable
>
>Hello. Can you check the chipset being used? Is it based on FTDI or Prolific?
>I have lots of Prolific cables.. but I need FTDI based cables because it's
>the only way where we can run non-standard baud rates.
>
The usb to earphone jack one is prolific, I did not buy the other one so i
don't know
you can try to ask them.
>Thanks!
>
Anyway I have other links for you to try:
http://www.multi-com.co.uk/index.php/en_US,details,id_pr,258,menu_mode,
categories.html
and
http://www.unlockcellular.com/650-motorola-c115a-t191-usb-cbl.html
you could be lucky with one of them but in each case you will need to contact
them
May be this link can be added to the wiki, if someone can confirm they are
good ones