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 studying the GSM voice interception of airprobe,and want to port
to BB,using
the ccch_scan.c .the problem is that,
the airprobe is written by C++,and the BB is C;
I find the useful part of airport is
airprobe/gsm-receiver/src/lib/decoder/openbtsstuff,
and how to modify the makefile of BB to use the source of openbtsstuff?
Thanks!
i am trying to understand talloc* functions. in layer23 app. i want to know
what exact role they perform in these apps.
its ok about allocating memory and freeing them but logically why they are
used.
--
Akib Sayyed
Matrix-Shell
akibsayyed(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
Hi all!
This is the announcement for the next Osmocom Berlin meeting.
Jun 27, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin
Nico will talk about SAP (SIM Access Profile) in osmocomBB.
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[1].
Regards,
Holger
[1] http://openbsc.osmocom.org/trac/blog/osmug-20120627
i am trying to port mobile app on phone it self as a firmware but unable to
find out how exactly L1 on phone communicate with L2 L3 on pc.
please help me with that.
--
Akib Sayyed
Matrix-Shell
akibsayyed(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
i have been trying to load RSSI and run it. all went well. but after all of
sudden LCD went off tried to debug but didnt understand much.
here is log
OSMOCOM Loader (revision osmocon_v0.0.0-1347-g4f0acac)
======================================================================
Running on compal_e88 in environment compalram
Found flash of 2097152 bytes at 0x0 with 2 regions
fb_td014_init: initializing LCD.
//after above msg LCD is going off and firmware is giving output correct as
it was giving before
then i created custom program kept only board_init(); then compiled and
uploaded in phone and started but still same issue.
then fetched fresh git and tried to compile then also same issue.
steps taken to compile test.c
created folder test in target/firmware/apps/
added test in make file application list
renamed test.c to main.c
steps taken to load code in c118
./host/osmocon/osmoload memload 0x820000
./target/firmware/board/compal_e86/test.highram.bin
./host/osmocon/osmoload jump 0x820000
please help me with that
--
Akib Sayyed
Matrix-Shell
akibsayyed(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
A Motorola C155 is hooked up to my computer via a bus pirate as per the
official instructions, everything is properly wired and the phone seems to
work. However, Osmocon neither indicates the presence of any data being
sent or received when attempting to communicate with the phone; it just
idles. Is there any extra logic in the cable? Any help would be appreciated.
Hello everyone!
I got osmocom-bb running on a gta02 with a self-built Debian image.
osmocon-bb was compiled natively on the gta02. Everything works great using:
$ ./osmocon -i 13 -m romload -p /dev/ttySAC0 layer1.highram.bin
as described at:
http://bb.osmocom.org/trac/wiki/OpenMoko
It bugs me, however, that the proprietary openmoko 11 firmware is still
lingering in the baseband flash. So I would like to replace it
permanently with the osmocom-bb layer 1 firmware. That didn't work so far.
First, I attempted to use the FLUID binary to flash layer1.highram.bin.
The manual firmware update that is described at:
http://wiki.openmoko.org/wiki/Flashing_the_GSM_Firmware
suggests to use the FLUID binary from the package:
http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_a…
I tried to run:
$ FLUID_PORT=/dev/ttySAC0 ./fluid.exe -oo -od13,13 -b 115200 -f
layer1.highram.bin
This gives me:
FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004.
Reading image file:
'/usr/local/src/osmocom-bb/src/target/firmware/board/gta0x/layer1.highram.bin'WARNING:
Illegal hex line:
ERROR(55): File format/syntax error
I also played with the options but to no avail. So apparently fluid
expects the firmware image to be in a particular format.
Then I tried the osmoload utility. For that I started osmocon with:
$ ./osmocon -i 13 -l /tmp/osmocom_loader -m romload -p /dev/ttySAC0
loader.highram.bin
osmocon then says:
Sending Calypso romloader beacon...
On another console I then turned on the GSM device and tried to request
information about flash using:
$ ./osmoload -l /tmp/osmocom_loader finfo
This gives me:
Requesting flash layout info
Query timed out.
What am I doing wrong? Are there fundamental reasons why this cannot
work? Any hints would be much appreciated!
Thanks,
Arno