Hi lists!
It's no secret for everyone, that today OsmocomBB is not actively maintained
as well as OpenBSC, for example. I think it's mostly due to supported
hardware
limitations. Currently supported platforms is still a bit of 'black box'.
Moreover every day it's harder to find and buy a new one.
Fortunately, there are many SDR platforms available now. Especially
interesting
devices are USRP, UmTRX, bladeRF, and recently introduced LimeSDR. They can
be
easily programmed to support just about any type of wireless standard, of
course,
including some mobile telecommunication stacks. As well as for network side
back-end,
they can be used to perform MS side operations, excepting frequency-hopping
and some
phone specific features (like SIM I/O).
So, I think there is a way to bring a new live to, amazing child of the
Osmocom
umbrella, OsmocomBB. We can make one work on SDR hardware platforms
implementing
a 'bridge' between both already implemented L2/L3 and OsmoTRX. I know that
there
already was some attempts (see sylvain/ms-sdr branch) to make described
dreams
come true, but development was stopped. And now I am going to start to work
around
this direction.
What for?
- GPRS and EDGE support
- More flexible voice routing
- Multi SIM support
- Next generation networks support (UMTS, LTE)
- ...
Currently I am looking for developers interested in this subject. So, any
ideas
and contributions are welcome! Together we can realize all the things
faster and
create a new area of research and development. Also for me it's very
important to
know opinions of Osmocom community members and exactly OsmocomBB
founders/developers.
Thanks!
С наилучшими пожеланиями,
Яницкий Вадим.
Hi all,
I have been using C123 for a long time with FTDI cable.
I recently bought a C139 on which I wanted to run layer1 fw, i check the SW
version using #02# and software version is "1.3.29", UART Flag is "0"
On going through the mailing list I found these to be sufficient for using
osmocom-bb but some how there is a problem on loading.
When I use the fwg command
./osmocon -p /dev/ttyUSB0 -m c140 -c
../../target/firmware/board/compal_e86/layer1.highram.bin
I get the following
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
read_file(chainloader): file_size=32, hdr_len=4, dnload_len=15341
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/15341)
handle_write(): 4096 bytes (8192/15341)
handle_write(): 4096 bytes (12288/15341)
handle_write(): 3053 bytes (15341/15341)
handle_write(): finished
It receives prompt2 and loads the file but doesn't move ahead, the phone
does not show layer1 on the screen either.
when i use fwg command (add -m c140xor )
./osmocon -p /dev/ttyUSB0 -m c140xor -c
../../target/firmware/board/compal_e86/layer1.highram.bin
I get the fwg:
got 1 bytes from modem, data looks like: 04 .
got 1 bytes from modem, data looks like: 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
read_file(chainloader): file_size=32, hdr_len=4, dnload_len=15341
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/15341)
handle_write(): 4096 bytes (8192/15341)
handle_write(): 4096 bytes (12288/15341)
handle_write(): 3053 bytes (15341/15341)
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: 57 W
Received MAGIC NACK from phone, you need to have "1003" at 0x803ce0
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
It now move ahead and says the received MAGIC NACK and also that you need
to have "1003" at 0x803ce0, this is a documented problem and i believe in
compal_e86 binaries must have been taken care of.
Any ideas on how can I get around this and load the firmware on my c139 ? I
am again usung the same cable FTDI which works perfectly with c123.
My setup is native Ubuntu 14.04 , host machine and Intel i5.. (hw does not
seem to be the problem)
Looking forward to hear from you guys. Thanks in advance.
Regards,
Ajay
merlinsignals.blogspot.in
Hi all,
I have been using C123 for a long time with FTDI cable.
I recently bought a C139 on which I wanted to run layer1 fw, i check the SW
version using #02# and software version is "1.3.29", UART Flag is "0"
On going through the mailing list I found these to be sufficient for using
osmocom-bb but some how there is a problem on loading.
When I use the fwg command
./osmocon -p /dev/ttyUSB0 -m c140 -c
../../target/firmware/board/compal_e86/layer1.highram.bin
I get the following
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
read_file(chainloader): file_size=32, hdr_len=4, dnload_len=15341
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/15341)
handle_write(): 4096 bytes (8192/15341)
handle_write(): 4096 bytes (12288/15341)
handle_write(): 3053 bytes (15341/15341)
handle_write(): finished
It receives prompt2 and loads the file but doesn't move ahead, the phone
does not show layer1 on the screen either.
when i use fwg command (add -m c140xor )
./osmocon -p /dev/ttyUSB0 -m c140xor -c
../../target/firmware/board/compal_e86/layer1.highram.bin
I get the fwg:
got 1 bytes from modem, data looks like: 04 .
got 1 bytes from modem, data looks like: 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
read_file(chainloader): file_size=32, hdr_len=4, dnload_len=15341
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/15341)
handle_write(): 4096 bytes (8192/15341)
handle_write(): 4096 bytes (12288/15341)
handle_write(): 3053 bytes (15341/15341)
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: 57 W
Received MAGIC NACK from phone, you need to have "1003" at 0x803ce0
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
It now move ahead and says the received MAGIC NACK and also that you need
to have "1003" at 0x803ce0, this is a documented problem and i believe in
compal_e86 binaries must have been taken care of.
Any ideas on how can I get around this and load the firmware on my c139 ? I
am again usung the same cable FTDI which works perfectly with c123.
My setup is native Ubuntu 14.04 , host machine and Intel i5.. (hw does not
seem to be the problem)
Looking forward to hear from you guys. Thanks in advance.
Regards,
Ajay
merlinsignals.blogspot.in
I am the project lead for the SHAKTI open source processor project.
See bitbucket.org/casl
This is a large Indian processor development effort that aims to develop
a range of processors (from uController to high end servers) based
on the RISCV ISA. We work closely with UCB and Cambridge as part of this
effort.
As part of our processor family, we have just started on a mobile SoC.
The goal is to have an octa core SoC with the performance of a
snapdragon 820 or the Apple A9. the CPU core is pretty much under
control but we are exploring the DSP needed for running the lower levels
of the 3G/LTE stack.
Another group does LTE stacks and so we have complete testing equipment
available to test for compliance.
I am basically looking for co-conspirators who can help identify the
components
I can use from the osmocom stack and figure out what else we need to
develop.
Then of course we need to develop the DSP core. We are currently reusing
the UCB vector processor and we are trying to figure out if a vector thread
processor or
a conventional DSP will do the trick.
Our goal is to have am SoC that will the functionality of a basic smart
phone
but we do not intend to focus only on a basic phone with voice/data
ca[ability but with basic display (even 4 line display is OK). Plan to use
the
AD SDR board for the SDR section. So it will be a large board that is
not optimized for size.
Any comments, thoughts appreciated . In case you are wondering, yes we
realize
this a mammoth task but we are well funded ! This is part of the India
processor project. And most importantly all our work will be patent free
open source. HW will be BSD, SW will be GPL3/2
--
Regards,
Madhu
I found a 1900 band analog booster/repeater to try.
> On Jun 20, 2016, at 2:32 PM, Erich Dachleger <edachleger(a)yahoo.com> wrote:
>
> Does anybody know if it would be possible to use some of the old vodaphone-femtocells together with openbsc/osmo-bts?
> RegardsErich
>
> Den Mandag, 23. mai 2016 11.46 skrev etienne . <etiennehelluy(a)gmail.com>:
>
>
> Short answer: no & no
> 1 - A gsm repeater is an analog device. With osmocom-bb phones you would need to demodulate/remodulate bursts.
> This wi
Hi guys,
I have a lot of problems using osmocom-bb with an Openmoko GTA02. First of all, I followed all the instructions from here [1] and uploaded layer1.highram.bin via external jack serial port (second tutorial). Well, after the firmware is downloaded on the phone osmocon prints:
"
Finished, sent 54 blocks in total
Received branch ack, your code is running now!
"
and nothing is printed anymore. Moreover, I see no activity on the serial port, all LEDs on my USB adapter being off.
When I try to run cell_log from my PC, it prints the following error message and blocks / does nothing:
"
Failed to connect to '/tmp/osmocom_sap'.
Failed during sap_open(), no SIM reader
<000e> cell_log.c:804 Scanner initialized
Mobile initialized, please start phone now!
"
I've read about this error and figured out that it is not fatal, but still cell_log doesn't work, nor does the 'mobile' application. I tried the code from master and from sylvain/testing branch and I uncommented "CONFIG_TX_ENABLE". I even tried hello_world.highram.bin and that doesn't print anything after loading it. I don't know what to do anymore.
[1] http://bb.osmocom.org/trac/wiki/OpenMoko#no1
Hello everyone!
During power measurement process we can see some messages like:
PM MEAS: ARFCN=8, 55 dBm at baseband, -83 dBm at RF
If I understood correctly, in this example received signal has
-83 dBm (about 5e-12 W) strength before amplifier and 55 dBm
(about 316.2 W) strength after one. It looks like the strength
of amplified signal should be printed as -55 (about 3.2e-9 W),
because 316.2 W is very high value. Am I right? Or is it internal
signal strength representation used by DSP?
С наилучшими пожеланиями,
Яницкий Вадим.
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
> What are your ideas to make this database alive?
I think we can make it more friendly to user. What do you think about
merging both TAC and terminal-profile databases? One common DB
and one web-interface seems good for me.
Also I am thinking about implementation of a simple Java cardlet
which will be aimed to extract device's profile and provide the results
through SIM-menu. In this case everything that user need is get one
programmable SIM and install this app.
С наилучшими пожеланиями,
Яницкий Вадим.
2016-05-21 10:13 GMT+06:00 Kévin Redon <kevredon(a)mail.tsaitgaist.info>:
> What are your ideas to make this database alive?
>
> The easiest way to get the terminal profile of a phone is to monitor the
> SIM interface. To automate that a script to be used along with SIMtrace is
> provided. Alternatively you can use the email address.
> Currently the database it is not very active because no one is submitting
> entries since it's not as easy as getting a TAC/IMEI.
> I also kind of like read only. It keeps external from messing around with
> it.
> But I'm happy to here what you have to propose.
>
> On Sat, May 21, 2016 at 12:13:56AM +0600, Вадим Яницкий wrote:
> > Hi,
> >
> > I think it would be cool to "make alive" the terminal-profile database.
> > Currently it can be visited in readonly mode:
> >
> > https://terminal-profile.osmocom.org/
> >
> > I can make a page simular to http://tacdb.osmocom.org/ where
> > anybody will be abble to contribute and download the lastest
> > version of database.
> >
> > But before I begin, I would like to know your opinions.
> >
> > С наилучшими пожеланиями,
> > Яницкий Вадим.
>
Hi,
I think it would be cool to "make alive" the terminal-profile database.
Currently it can be visited in readonly mode:
https://terminal-profile.osmocom.org/
I can make a page simular to http://tacdb.osmocom.org/ where
anybody will be abble to contribute and download the lastest
version of database.
But before I begin, I would like to know your opinions.
С наилучшими пожеланиями,
Яницкий Вадим.