Dear all,
I suggest to change a stock Redmine theme to something more beautiful,
for example gitmike: https://github.com/makotokw/redmine-theme-gitmike
which used by srlabs.de and looks like pretty. Furthermore, the Osmocom
logo will look better on light background.
Opinions?
С наилучшими пожеланиями,
Яницкий Вадим.
Hallo zusammen,
ich wollte toolchain auf meinem Backtrack5r3 als VM installieren, dabei sind
Fehler aufgetreten die ich nicht verstehe.
Wie kann ich da Abhilfe schaffen?
Bis hierhin war noch alles gut.
GNU ARM toolchain
This page will describe the procedure for compiling a GNU ARM toolchain. We
will build a toolchain consisting of:
* GCC 4.8.2
* Binutils 2.21.1
* Newlib 1.19
Getting the buildscript
First of all, create a directory you want to use for building the toolchain,
and download the buildscript
<http://bb.osmocom.org/trac/raw-attachment/wiki/GnuArmToolchain/gnu-arm-buil
d.3.sh> gnu-arm-build.3.sh there. You will need to make it executable:
$ chmod +x gnu-arm-build.3.sh
Dependencies
In order to build the toolchain, you will need to install the following
packages (assuming you're using a Debian-based distribution):
$ sudo apt-get install build-essential libgmp3-dev libmpfr-dev libx11-6
libx11-dev texinfo flex bison libncurses5 \
libncurses5-dbg libncurses5-dev libncursesw5 libncursesw5-dbg
libncursesw5-dev zlibc zlib1g-dev libmpfr4 libmpc-dev
Preparation
Open a shell in the directory of gnu-arm-build.sh and create the following
directories:
$ mkdir build install src
Download the needed sources to src/:
$ cd src/
$ wget http://ftp.gnu.org/gnu/gcc/gcc-4.8.2/gcc-4.8.2.tar.bz2
$ wget http://ftp.gnu.org/gnu/binutils/binutils-2.21.1a.tar.bz2
$ wget ftp://sources.redhat.com/pub/newlib/newlib-1.19.0.tar.gz
Building the toolchain
$ cd ..
$ ./gnu-arm-build.3.sh
I will build an arm-none-eabi cross-compiler:
Prefix: <YOURPATH>/install
Sources: <YOURPATH>/src
Build files: <YOURPATH>/build
Press ^C now if you do NOT want to do this.
Dann kam folgendes, als wenn er Probleme mit den Ordnern hatte.
cid:image001.jpg@01D17613.420C17C0
Könnt ihr mir weiterhelfen?
Gruß Peseta3
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,
I would first like to thank all those who participated in this nice
project.
I recently started working with osmocombb and was able to have it working
fine on a motorola c118.
However, I noticed that some sim cards can connect normally to the BTS, can
make calls and send SMS but can’t receive anything. They simply don't get
paged. While for some other sim cards everything seems to be working fine.
Does anyone know what might be causing this issue ?
thanks,
Robert
Can it be done without using LCR ?
On Mar 4, 2016, at 10:21 AM, Dennis Eisenbarth <dennis.eisenbarth(a)gmail.com> wrote:
> It should not be a problem.
>
> Have a nice day,
> Dennis
>
> On 03.03.2016 18:47, robert wrote:
>> Hi,
>>
>> Is is possible to record a specific call using osmocombb? I want to record a call being made on the osmocombb phone not to sniff calls over the air.
>>
>>
>> Best regards,
>> Robert,
>
On Mar 4, 2016, at 10:21 AM, Dennis Eisenbarth <dennis.eisenbarth(a)gmail.com> wrote:
> It should not be a problem.
>
> Have a nice day,
> Dennis
>
> On 03.03.2016 18:47, robert wrote:
>> Hi,
>>
>> Is is possible to record a specific call using osmocombb? I want to record a call being made on the osmocombb phone not to sniff calls over the air.
>>
>>
>> Best regards,
>> Robert,
>
Hello,
I hope that this email finds you in good health. I am working on
implementing the call handover part of mobility management in the OsmocomBB
code as part of my Senior Year Project in University. I would like to ask
you a few things about what you have implemented. Your help will guide me a
lot in my endeavor. Please let me know whenever we can skype or call.
Thanks and Regards,
Ahmed
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
Look at this strings from your log:
<0005> subscriber.c:601 Requesting SIM file 0x2fe2
<000f> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)
<000f> sim.c:697 go MF
<000f> sim.c:241 SELECT (file=0x3f00)
<000f> sim.c:187 sending APDU (class 0xa0, ins 0xa4)
<000f> sim.c:876 received APDU (len=0 sw1=0x00 sw2=0x00)
<000f> sim.c:952 command failed
<000f> sim.c:151 sending result to callback function (type=1)
<0005> subscriber.c:657 SIM reading failed
Maybe something wrong with your SIM? Try another one.
Are you at the master branch?
С наилучшими пожеланиями,
Яницкий Вадим.
Hi,
Can someone confirm if the steps described in http://bb.osmocom.org/trac/wiki/flashing are still valid, as I can’t find “loader.e88loader.bin”. I’m using sylvain/testing branch.
Best regards,
Robert,
