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.
Hello,
Hopefully this question is appropriate on this list (please let me
know otherwise).
Running ccch_scan or bcch_scan in the sylvain/burst_ind branch, I keep
getting this error:
<000c> l1ctl.c:114 FBSB RESP: result=255
I tried checking the code, but I can't quite figure out what's going on. It
looks like 255 is an error code, but I don't know where to go from there.
This may be related to my SIM card being locked (I think). Running mobile on
the sylvain/testing branch, I get:
<0005> subscriber.c:625 PIN is required, 3 tries left
Will not having the PIN intefere with ccch_scan as well?
Thanks,
Josh Pereyda
Hi,
I have a question.
When using osmocombb with C118, we are getting error when SIM tries to authenticate itself to the network.
Here are the messages:
<0005> gsm48_mm.c:3902 (ms 1) Received 'RR_DATA_IND' from RR in state location updating initiated (sapi 0)
<0005> gsm48_mm.c:4091 (ms 1) Received 'MT_MM_AUTH_REQ' in MM state location updating initiated
<0005> gsm48_mm.c:1637 AUTHENTICATION REQUEST (seq 2)
<0005> subscriber.c:955 Generating KEY at SIM
<000f> sim.c:209 got new job: SIM_JOB_RUN_GSM_ALGO (handle=00000006)
<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:990 key generation on SIM failed (cause 2)
SIM is new. It works if you start phone without osmocom. And It also works if you start without osmocom and when SIM logs into network you restart the phone with osmocom.
We tried several new cards and there was always same result. There is also no PIN set up (SIM is not locked). We tried with USIM.
When we try old cards (>2 years old) osmocom works without problem.
Have you ever encountered this kind of trouble? Is there any fix for it?
Thank you.
Regards,
Alojzij
Hi all!
Thanks to a generous donor, we have received a couple of OT-290 trace
phones. These are commercial products intended for taking L2/L3 air
interface traces. If you've read any of the fabulous GSM papers by
Prof. Dr.-Ing. Joachim Goeller: The OT-phones is what he used to
generate all his traces.
The majority of what those phones can do is now also possible with
OsmocomBB.
However, OT-290 support GPRS tracing/testing - for CS-1 throguh CS-4.
I would be willing to give away one of the two remaining OT-290 (for
free) to anyone who would in return commit to developing a GSMTAP
interface for it.
The message format on the serial UART between phone and PC is documented
(PDF documentation by Sagem included with the phones). So based on this
documentation and an OT-290 phone, it should be possible to write a
small command-line program that receives the GSM/GPRS messages from the
OT-290 and sends them via GSMTAP into wireshark.
The result would then be similar to what
http://cgit.osmocom.org/cgit/dct3-gsmtap/ is for DCT-3 phones.
If you're interested, please respond to this message. Please don't
apply for the phone if you are not able to find the required time and
interest for actually doing the GSMTAP integration.
Thanks!
--
- 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)
The other day on IRC I was told that:
>Apr 29 00:34:36 <Hoernchen> last thing i heard was that nuttx was
superseded in favor of a more lightweight solution
And:
>Apr 29 00:41:03 <steve|m>
http://openbsc.osmocom.org/trac/wiki/OsmoDevCon2012/Minutes#a18:30roundtabl…
which was made back in march(we also started working on nuttx near march) and
contains the following:
>laf: summary we could not gain much from nuttx, rockbox could provide use
with UI (inspiration)? steve: framebuffer is mosly compatible
I wasn't aware of all that.
Also I don't have much details on what was said since I wans't there...
Should me and Alan Carvalho de Assis continue the work we are doing?
What is the current plan?
our status is here: http://bb.osmocom.org/trac/wiki/nuttx-bb/drivers
The current work on my side is to:
* make serial work without sercomm(done locally,just some configuration
change)
* unbreak the booting of the calypso(require serial to work without
sercomm,the commit that created the problem has been identified, how to fix is a
work in progress)
* I also tried to change toolchain(I generated a toolchain with openembedded)
to see if it fixed the issue but according to Gregory it's not the right fix.
* I also identified some dummy functions in the nuttx version of sercomm that
we should get rid of.
On Alan Carvalho de Assis side :
he's trying to make the keypad work but he has some difficulties with it.
Denis.
Hi
I am trying to use an Arkmicro Technologies ARK3116 USB to serial cable to communicate with my C118. I have compiled Osmocom-bb successfully on my Debian Squeeze laptop.
When I try to run the osmocon utility I get an error "Cannot open serial device /dev/ttyUSB0"
My dmesg etc output is:
[ 769.752182] usb 5-2: new full speed USB device using uhci_hcd and address 5
[ 769.908979] usb 5-2: New USB device found, idVendor=6547, idProduct=0232
[ 769.908988] usb 5-2: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[ 769.908995] usb 5-2: Product: USB-UART Controller
[ 769.909000] usb 5-2: Manufacturer: ArkMicroChips
[ 769.909192] usb 5-2: configuration #1 chosen from 1 choice
[ 770.029492] usbcore: registered new interface driver usbserial
[ 770.029740] USB Serial support registered for generic
[ 770.030002] usbcore: registered new interface driver usbserial_generic
[ 770.030005] usbserial: USB Serial Driver core
[ 770.047650] USB Serial support registered for ark3116
[ 770.048263] ark3116 5-2:1.0: ark3116 converter detected
[ 770.076254] usb 5-2: ark3116 converter now attached to ttyUSB0
[ 770.076305] usbcore: registered new interface driver ark3116
ls -l /dev/tty*
crw-rw---- 1 root dialout 4, 64 Apr 27 21:01 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 Apr 27 21:01 /dev/ttyS1
crw-rw---- 1 root dialout 4, 66 Apr 27 21:01 /dev/ttyS2
crw-rw---- 1 root dialout 4, 67 Apr 27 21:01 /dev/ttyS3
crw-rw---- 1 root dialout 188, 0 Apr 27 21:14 /dev/ttyUSB0
lsusb
Bus 005 Device 005: ID 6547:0232 Arkmicro Technologies Inc. ARK3116 Serial
Bus 005 Device 004: ID 09da:0006 A4 Tech Co., Ltd Optical Mouse WOP-35 / Trust 450L Optical Mouse
Bus 005 Device 003: ID 1631:5002 Good Way Technology
Bus 005 Device 002: ID 1631:5400 Good Way Technology
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
So I am assuming the drivers are installed correctly but if I run osmocon I get:
./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin
Cannot open serial device /dev/ttyUSB0
My Question is, does anyone here have any experience with the Arkmicro Technologies ARK3116 Serial cable?
Is there something I have missed?
Thanks
Tokala
hello,
I have the problem ,such as how to get the address of the functions
and Variables in the DSP assemble code,such as in
+; DSP Sniffing task patch
+; ----------------------------------------------------------------------------
+; Known symbols
+; ----------------------------------------------------------------------------
+
+ ; Variables
+patch_install_fptr .equ 0x3F6B ; Patch install function ptr
+dsp_page .equ 0x3FB0 ; Current ndb.d_dsp_page
+task_fn_entry .equ 0x4387 + 23 ; Task 23 index in JT_4387
+
+ ; Functions
+a5_setup .equ 0xB12C
+dma_queue_setup .equ 0xB74C
+
+jt4387_exec .equ 0xA9EA
+
+fq_4320_push .equ 0xAA9F
+fq_4330_push .equ 0xAA6C
+fq_4340_push .equ 0xAAC3
+
Can anyone tell me the way to do that?!
thanks!
Hello everybody
What happens when a mobile station is in a cell that uses hopping, but the
mobile locks to that cell (for instance using the function of the
engineering menu of a BB)? Is the hopping mandatory or the ms can continue
working also without it?
Does osmocom support hopping? What are the commands of the mobile interface
(if they exist) to show how the hopping is going? Is it possible to lock
with osmocom too?
Thanks for the answers.
Dario.
Hello All,
What is the preferred Sim Card Reader/Writer for the SysmoSim Card,
A.K.A., the GrCard Sim?
And is the following known to work reliably with the SysmoSim Card?
SIM Reader kit - v1.0http://www.adafruit.com/products/101I contacted
Adafruit.com yesterday and they explained that their device
doesn't work on all Sim Cards.
Any assistance would be greatly appreciated.
Sincerely,
Martin