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
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
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
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.
I've pulled git repo today, but the RSSI firmware gets an error.
apps/rssi/main.c: In function `main':
apps/rssi/main.c:896: warning: 'a' might be used uninitialized in this
function
apps/rssi/main.c:896: warning: 'e' might be used uninitialized in this
function
CC board/compal_e88/rssi.compalram.manifest.o
LD board/compal_e88/rssi.compalram.elf
OBJ board/compal_e88/rssi.compalram.bin
CC board/compal_e88/rssi.highram.manifest.o
LD board/compal_e88/rssi.highram.elf
OBJ board/compal_e88/rssi.highram.bin
CC board/compal_e88/rssi.e88loader.manifest.o
LD board/compal_e88/rssi.e88loader.elf
OBJ board/compal_e88/rssi.e88loader.bin
CC board/compal_e88/rssi.e88flash.manifest.o
LD board/compal_e88/rssi.e88flash.elf
OBJ board/compal_e88/rssi.e88flash.bin
CC board/compal_e86/rssi.compalram.manifest.o
LD board/compal_e86/rssi.compalram.elf
arm-elf-ld: region LRAM is full (board/compal_e86/rssi.compalram.elf
section .data)
make[1]: *** [board/compal_e86/rssi.compalram.elf] Error 1
make[1]: Leaving directory src/target/firmware'
make: *** [firmware] Error 2
$ git pull
Already up-to-date.
$
Anyone experiencing the same issue?
Hi list,
I'm an information engineering student interested in working on
embedded systems and tlc (especially I would like to get deep into
firmware coding and dsp). In the last years I have been an active
member of the italian openmoko community so I'm familiar with gta0X
phones (I owned a gta02, now I have only a gta01). Two years ago I've
worked at the Trento's research center on the n900 while today I'm
working at a tlc company in Padua.
Even if it's not what I'm working on at the moment, I'd like to spend
some of my time by working on the GSMTAP integration of the Sagem
OT-290.
Is there any news about that? Since the last message on this thread
was posted more than 2 months ago I wanted to know whether anyone was
already working on it.
Thanks,
Thomas Bertani
Hi,
I flashed the rssi application into my C118. The app is really great. But
now I want to flash the original fireware back.
I saved the orignal loader by
host/osmocon/osmoload memdump 0x000000 0x20000 compal_loader_orignal.bin
But when I tried to flash this loader back using
host/osmocon/osmoload fprogram 0 0x000000 compal_loader_orignal.bin,
The phone can't power on.
What did I do wrong?
regards,
wenyao
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/How-to-flash-the-original-firewa…
Sent from the baseband-devel mailing list archive at Nabble.com.
As already mentioned, the Osmocom Meeting will
take place this Saturday, 1.9.2012 at 10:00.
Three people have confirmed that they will come,
I have send them an email with the location details.
Harald is not yet sure if he can attend.
A few suggestions for the meeting:
- I will run a GSM-1800 network with my test license so
you can try out OsmocomBB. If you are interested to
do so please bring your Osmocom phone plus Laptop with
the already installed OsmocomBB software.
- We can do some experiments with SIMtrace if there is any
interest.
- There should still be enough time for other things, we
can decide what to do during the meeting.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
I have now selected the day for the meeting which should
match for all who have send me their preferred days. The
first Osmocom meeting in Bavaria near Pfarrkirchen will
be held on:
Saturday, 1. September, starting at 10:00
If you are going to come, please let me know until
next Wednesday (29. August). I will then send you
a private email with the details of the location.
The agenda is not yet set, but it seems that at least
those who send me their areas of interest are mainly
targeted towards GMS (OpenBSC/OsmocomBB). We can
of course also talk about other stuff, e.g. RTL-SDR,
but for this it would be nice if one of the RTL-SDR
experts would join us (here you have the chance to
receive a nearly clean/empty spectrum without much
noise from other sources ;-).
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hi all!
This is the announcement for the next Osmocom Berlin meeting.
Aug 22, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin
There is no formal presentation scheduled for this meeting. However,
updates will be provided on various current developments, such as
* Progress on the CC32RS512 smart card (osmo-cos)
* Possibly: Status of current attempts to get CSD implemented in OpenBSC
If you are interested to show up, feel free to do so. There is no
registration required. The meeting is free as in "free beer", despite
no actual free beer being around.
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)
Dear Ellen,
On Mon, Aug 20, 2012 at 04:26:04PM +0200, Ellen Apolinar wrote:
> btw. where is the location when it is 630 km away from Berlin?
As Dieter wrote in his original post:
> at my place in the south-east of Bavaria near Pfarrkirchen
So if you just type "Pfarrkirchen, Germany" into your favorite internet
map service, you should get a pretty clear idea.
As there seems to be frequent misconception: This is _not_ a developer
conference or anything like that. Just an informal user group meeting,
like those we have in Berlin every two weeks.
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!
There are some signs that the supply of Motola C1xx phones is not
endless, after all.
As such, sysmocom has decided to manufacture some custom boards with the
typical TI Calypso/Iota/Rita design. The RF PA will be RFMD RF3166, and
the combined NOR + SRAM will be a Samsung K5A3281. All parts are
still available from the surplus market.
Schematics will be published in PDF form only, Gerber/PCB files will not
be released (so basically the same like the OsmoSDR situation). All
software used is already available as OsmocomBB under a *GPL license.
Any help and input from the community will of course be appreciated.
The design will be more or less a standard tri-band calypso phone design
(900/1800/1900), with possibly a placement option for having
850/1800/1900. We'll be targetting a modem as opposed to a phone
design, so no built-in keypad / display / battery, but external
connections.
At one edge there should be a PCB edge connector, possibly with
mechanical form-factor of PCIe (sinc they're cheap). This connector
should allow the module to be plugged into a back-plane with a number of
other modems.
I've crated an initial Wiki page about the possible / intended
modifications from a classic phoned design at
http://bb.osmocom.org/trac/wiki/Custom_Calypso_Board :
* expose JTAG
* board-edge connector for plugging many boards into one backplane
* external clock input / buffered clock output
* RF connector standard u.fl or SMA or optionally separate Rx/Tx?
* I2C/SPI and both UARTs available on headers
* on-board EEPROM for storing persistent data, even beyond NOR flashing
* SIM card slot, SIM interface also present on header
* additional / unused TPU ports
* header for TSP / TPU and all data/control interfaces between iota/rita/calypso
* RTC crystal and footprint for lithium backup battery
* version of the board with uplink / downlink filters switched
Feel free to discuss other extensions/modifications you may have in
mind. Please note that fundamentally we are still heading for a calypso
based design, so this will not be a board that just contains the
Iota/Rita and some FPGA or general purpose DSP, as some people have
proposed in the past. However, it may be possible to have connector
footprints for the TSP / BSP interfaces and make some boarde that don't
contain the calypso/ram/nor parts.
Pricing will definitely not be anywhere near to the price of current
phones. You cannot even source all the components for the price of
those refurbished phones, let alone the fairly complex 6-layer PCB.
Also, the quantities will be low, we may be manufacturing something like
100 units a batch only.
This is a low-effort / side project, so I'm conservative with any
estimates and would say that we're happy to have boards shipping by the
end of this year.
Regards,
Harald (waiting for the e-mail flood)
--
- 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)
Hello everyone
In one of the ML I have read that, BCCH-SDCCH-BCCH-TCH is required for
listen to the TCH.
In my case(Test N/w) I receive an IMM ASS, go to (SDCCH/4 + SACCH/4) TS:0
subchannel 2.
As soon as I find an ASS_CMD I send a l1ctl_tx_dm_est_req with new channel
parameters and jump to a TCH/F+SACCH/F+FACCH/F TS 4. I am receiving bursts
after this.
They contain SACCH SI5/6 as I see them in Wireshark and also some bursts (I
hope a mix of FACCH and TCH). Is it necessary to do BCCH again. If I don't
do Won't I receive TCH frames.? Will the be good TCH frames. ?
But I see the tch_schedule_set working good. I receive once UL and next DL
bursts. and sometimes SACCH.
Can someone explain me.
Thank You
Altaf
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Moving-to-TCH-without-doing-a-BC…
Sent from the baseband-devel mailing list archive at Nabble.com.
hello list
i have been trying to sniff FR codec traffic from OpenBTS network.i tried
to modify patch of bob with little help of airprobe.
but when i try to play file toast says bad frame no.
can any one help me with that
here is app link
http://pastebin.com/GwmB7UGK
--
Akib Sayyed
Matrix-Shell
akibsayyed(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
Hi,
I have make a patch for the Pirelli DP-L10 created. You can enable and
disable the patch in the makefile (src/target/firmware/Makefile).
The Keypad layout is tested with rssi.bin app. Only the power button
is not available.
regards
Marco
Hi,
Christian Vogel commited the battery charging capability for the C123.
I wanted to know if someone also looked at the Pirelli DP-L10 (maybe steve|m), which uses the USB port for charging (also used serial communication)?
Or maybe it could be possible to use the USB power instead (or along) of the battery, which would be enough for RX only.
thanks,
kevin
Hi, List.
I am studying the IMSI Detach attack now. I have some doubt.
1. if the victim is already off-line, what is the effect of the attack?
2. In my network, I send the IMSI detach Indication, and the base station
sends me
the Channel Release. but the victims is still online,why? I am confused!
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/about-the-IMSI-Detach-in-various…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hello Alexander,
On Wed, 8 Aug 2012 20:44:12 +0400, "Alexander Chemeris" <alexander.chemeris(a)gmail.com> wrote:
>
> I'd love to join, but it strongly depends on the exact dates of the
> meeting. I have very tight travel schedule in the next months.
Just to avoid any misunderstanding: Those meetings are not supposed
to be something similar to the Osmocom Developer Conference earlier
this year. The idea is to have a regular or "on demand" oportunity to
meet with people for a few hours and demonstrate or talk about
the Osmocom projects or share new ideas.
Its comparable to the regular Berlin meetings, you can get an idea
of what goes on there:
http://openbsc.osmocom.org/trac/blog/osmug-20120808
Of course you can attend, if you are close (Munich airport is 120 km
away) but I would expect that Berlin is more convenient if you come
from really far away and Berlin already has regular meetings.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
As a quick follow up: The proposal for the meeting is intended
for everyone interested in the various Osmocom projects (e.g.
OpenBSC, OsmocomBB, TETRA, SimTrace, OsmoSDR). The meeting is
not limited to only those who are actively participating.
I will wait until next week to see how many people are
interested, so far I am aware of two persons.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello Sylvain
I am using the burst_ind branch and have some doubts.
I am using a test network, and it has no encryption. Usually the n/w has a
low load and the channel structure followed during the assignment is
SDCCH/4 + SACCH/C4 or CBCH(SDCCH/4). and timeslot 0 . SDCCH is assigned on
timeslot 0..
The ccch_scan is able to capture the SMS sent on timeslot 0 and also only
one of the subchannel as per the above assignment.
Just for testing, When I use two phones and send an SMS from both of them
simultaneously both are assigned timeslot 0 and different subchannels.
CCCH_scan could capture only one SMS. meaning that it could only get one
subchannel.
Am I right about ccch_scan or does it have the capability to get a complete
timeslot. ?
Thank you
Altaf
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Working-of-ccch-scan-and-capturi…
Sent from the baseband-devel mailing list archive at Nabble.com.
I would like to ask if there is interest to have some kind
of Osmocom meetings in Bavaria. Suggested location is here
at my place in the south-east of Bavaria near Pfarrkirchen.
There are no large cities close, but the location is still
in reach with a car, some examples (single distance):
- from Munich: 130 km
- from Passau: 55 km
- from Salzburg: 90 km
- from Linz: 140 km
Why at my place ? There is some GSM/3G/TETRA equipment
and RF measurement gear around which could be demonstrated.
It is not yet decided when and how (regular or "on demand")
this meeting should take place. Before that I want to find out
if there is interest at all and how many people are interested.
So please write to the list what you think.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hi all!
This is the announcement for the next Osmocom Berlin meeting.
Aug 08, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin
Harald will be giving a short presentation on contemporary smartphone
hardware architecture.
Furthermore, updates and discussions on various current developments
will be exchanged, such as
* Demo of OsmoPCU on sysmoBTS
* Status of new SMSC
* Planning phase of custom calypso board
If you are interested to show up, feel free to do so. There is no
registration required. The meeting is free as in "free beer", despite
no actual free beer being around.
Updates and the blog post can be found here:
http://openbsc.osmocom.org/trac/blog/osmug-20120808
--
- 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)
Hello !
Although not entirely on topic, Harold is happy for me to post to
these lists about an event I've been involved in.
Electromagnetic Field is a UK hacker/maker camp that is occurring in
just under a months time. In case you haven't, here's the gist:
Electromagnetic Field is a non-profit three day camping festival for
people with an inquisitive mind or an interest in making things:
hackers, geeks, scientists, engineers, artists, and craftspeople.
It's taking place in Milton Keynes between the 31st August and the 2nd
September and is inspired by European camps such as the Chaos
Communication Camp and Hacking At Random, which means that we have an
absurd internet connection to a field, and power to every tent.
There will be talks and workshops on everything from genetic
modification to lockpicking, blacksmithing to high-energy physics,
reverse engineering to electronic engineering, quadcopters to beer
brewing and crocheting to carpentry. If you decide to talk about
something, there's space for you to do so, and plenty of people who
want to listen.
The campsite will be littered with interesting things to play with and
explore, from ride-on tanks to giant dinosaurs. And more lasers than
you can shake a laser-covered stick at.
Attendees are encouraged to form villages and put on activities for
other people around the camp, and we're going to have villages
covering everything from gaming to 3D printing. If you'd like to form
a village, get in touch!
https://www.emfcamp.org/tickets
Your ticket will give you the following things:
* A secure place to camp for three days.
* Power to your tent.
* Very fast internet access (both wired and wireless).
* Access to running water and hot showers.
* A whole pile of awesome talks and workshops by amazing people.
* A full bar.
* One fully programmable camp badge, equipped with wireless communications.
* A campsite equipped with weird and wonderful things to play with.
* A weekend unlike any other in the UK.
If we've still not sold you, maybe you should read our website and blog,
which have exhaustive information about the camp:
https://www.emfcamp.orghttp://blog.emfcamp.org
If you've got any questions feel free to email me or the team!
Paul