baseband-devel

baseband-devel@lists.osmocom.org

2022 discussions

AW: Some refactoring proposals
by Andreas.Eversberg 28 Jul '10

28 Jul '10

>> Here's a few refactoring proposal that I'd like to get done. But >> before I invest too much time in them I'd like to be sure there are no >> objections ... (I hate implementing stuff for nothing). >> >> * Split layer23/src into >> - common: what makes liblayer23, purely generic stuff that needs >> binding together to define an app >> - mobile: The real complete mobile application >> - misc: The test applications and their support code layer23 (which >> I'd rename bcch_dump since that's what it does), echo_test, bcch_scan) > > Sounds fine with me. If Andreas doesn't mind, I'm happy to merge a branch > containing this split i don't mind!

1 0

Progress..
by Dev Purohit 26 Jul '10

26 Jul '10

Hi All, I just want to elaborate it my question is is there is some down link traffic between MS and a testing BTS , let say on ARFCN # 13 and Time slot 3 this traffic channel is non encrypted A5/0 , is osmocom BB or airprob is become to capable to tune to that particular ARFC in this case ARFCN no. 13 and time slot 3 and fetch the traffic channel data process it and convert it to pure voice or encode speech signals ( (CELP) or PCM format ) i specifically request to Harald as he is taking care for airprob also. If these projects need more development to get this extent kindly guide me so that i can start my work and contribute to this project , why taken I have taken this approach is 1) will clarify other aspects and errors in this package to make a working, ready to use package. after wards we will start for transition section. 2) will confirm the feasibility and give all contributor a enthusiasm that we are developing significantly and can get at least any output from moths of hard work 3) will apply the changes and correct for the errors( instability) other developer and contributor will face or report during their voice reception. i feel reception of voice , then transition of voice is very basic requirement of any mobile software, then we can add on other features like channel hoping , cell handovers, other UI features , various multimedia and messaging features.. thanks for your great work and wish to contribute at my best abilities.. --- On Fri, 7/23/10, Dev Purohit <devpurohit19(a)yahoo.com> wrote: From: Dev Purohit <devpurohit19(a)yahoo.com> Subject: progress.. To: baseband-devel(a)lists.osmocom.org Date: Friday, July 23, 2010, 12:49 PM Hello All, My basic question is related to progress and accomplishment of this project and related project like airprob. 1 if any of these project have reached up to the point where Um or Abis interface traffic can be change to voice or at least to the stage where it can get PCM or ISDN level voice data let say through layer1application we change synthesizer frequency to specific ARFCN, and tune to a specific TS. can it fetch traffic( without encryption, a5/0, testing down link traffic between MS and testing BTS ) channel and after base-band processing can it give voice data (either PCM o, analogue format, digital voice coding) if so what all sections/ applications will involve of this application or if this is possible through airprob so for now. Thank you in advance..

2 1

progress..
by Dev Purohit 23 Jul '10

23 Jul '10

Hello All, My basic question is related to progress and accomplishment of this project and related project like airprob. 1 if any of these project have reached up to the point where Um or Abis interface traffic can be change to voice or at least to the stage where it can get PCM or ISDN level voice data let say through layer1application we change synthesizer frequency to specific ARFCN, and tune to a specific TS. can it fetch traffic( without encryption, a5/0, testing down link traffic between MS and testing BTS ) channel and after base-band processing can it give voice data (either PCM o, analogue format, digital voice coding) if so what all sections/ applications will involve of this application or if this is possible through airprob so for now. Thank you in advance..

1 0

socket running problem
by Dev Purohit 18 Jul '10

18 Jul '10

Hello Mr.Holger, Thank you so much for help, but i'm not expert with linux system yet kindly help me to interpret. where is problem ? thank you in advance xx@ubuntu:~/osmocom-bb/src/host/osmocon$ strace -Ff -tt osmoload 2>&1 | tee strace-osmoload.log04:36:51.842667 execve("/usr/local/sbin/osmoload", ["osmoload"], [/* 38 vars */]) = 0 04:36:51.877698 brk(0) = 0x9b95000 04:36:51.877918 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) 04:36:51.878154 mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb78f9000 04:36:51.878338 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) 04:36:51.878657 open("/etc/ld.so.cache", O_RDONLY) = 3 04:36:51.878810 fstat64(3, {st_mode=S_IFREG|0644, st_size=82613, ...}) = 0 04:36:51.879022 mmap2(NULL, 82613, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb78e4000 04:36:51.879105 close(3) = 0 04:36:51.879221 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) 04:36:51.879384 open("/lib/tls/i686/cmov/libc.so.6", O_RDONLY) = 3 04:36:51.879554 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0000m\1\0004\0\0\0"..., 512) = 512 04:36:51.879724 fstat64(3, {st_mode=S_IFREG|0755, st_size=1405508, ...}) = 0 04:36:51.879956 mmap2(NULL, 1415592, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xe50000 04:36:51.880093 mprotect(0xfa3000, 4096, PROT_NONE) = 0 04:36:51.880219 mmap2(0xfa4000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x153) = 0xfa4000 04:36:51.880373 mmap2(0xfa7000, 10664, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xfa7000 04:36:51.880540 close(3) = 0 04:36:51.880681 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb78e3000 04:36:51.880837 set_thread_area({entry_number:-1 -> 6, base_addr:0xb78e38d0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0 04:36:51.881137 mprotect(0xfa4000, 8192, PROT_READ) = 0 04:36:51.881301 mprotect(0x8050000, 4096, PROT_READ) = 0 04:36:51.881443 mprotect(0x319000, 4096, PROT_READ) = 0 04:36:51.881572 munmap(0xb78e4000, 82613) = 0 04:36:51.881845 socket(PF_FILE, SOCK_STREAM, 0) = 3 04:36:51.882040 connect(3, {sa_family=AF_FILE, path="/tmp/osmocom_loader"}, 21) = -1 ENOENT (No such file or directory) 04:36:51.882323 write(2, "Failed to connect to '/tmp/osmoc"..., 44Failed to connect to '/tmp/osmocom_loader'. ) = 44 04:36:51.882700 exit_group(1) = ? xx@ubuntu:~/osmocom-bb/src/host/osmocon$

3 2

socket running problem
by Dev Purohit 18 Jul '10

18 Jul '10

Hi all i run command osmocom-bb/src/host/osmocon# ./osmoload Failed to connect to '/tmp/osmocom_loader' and osmocom-bb/src/host/layer23/src# ./layer23 Failed to connect to '/tmp/osmocom_l2'. Failed during layer2_open() kindly help me out with this i'm stuck.. Dev.

2 1

kernel choice
by Scott Weisman 14 Jul '10

14 Jul '10

Hi all. I just swallowed the Osmocom red pill and am awaiting my Motorola V171 which I just bought on eBay (it was the cheapest option). I was interested in what people thought of the Contiki OS. I'm not an expert, but this seems like a good option, since it's very compact, and has been ported to many ARM-based devices. Scott

2 1

AW: OsmocomBB Layer1 progress
by Andreas.Eversberg 06 Jul '10

06 Jul '10

> JFYI: The AGC control in L1 is now active. At least it didn't make things > worse for me. Maybe people who have had problems acquiring weak cells > should give it a try again. > I suggest to add the L1CTL_DM_REL_REQ into the state machine, I suppose > it should avoid that problem. hi, i will check this issue about releasing and establishment of dedicated mode. also i will do the power control thing from L3. i got stuck while transcoding RACH request / confirm from L1CTL into RSL_CHAN_RQD/RSL_CHAN_CONF. the goal is to have pure RSL between layer 3 and layer 2. the biggest problem are things like power measurement, sync requests and other L1CTL messages, all which are not defined for RSL SAP. i don't like the idea about converting everything from L1CTL to RSL and parsing it and vice versa. this take allot of time to implement, also we would need to add several new messages and information elements. my suggestion is to leave L1CTL as it is. currently i think about how to control tx_power and TA (timing advance/delay) from layer 3. it is not possible to set them in every layer 3 message, because this message may be splitted or repeated or layer 2 may send responses without interaction of layer 3. therefore we must store the tx_power and TA at layer 2, and it must be sent with every frame then. since we don't send any idle frame to layer 1 (this is actually generated there), we can only give tx_power and TA at frames with content. the values must be stored at L1 for idle frames. therefore it think it would be much easier to use something like L1CTL_POWER_REQ to set the current tx_power and a L1CTL_POWER_CONF to get the actual (closest) power set. (also includes the TA). these values are stored and for every frame sent afterwards until L1CTL_POWER_REQ is sent with different values. regards, andreas

1 0

Running osmocombb on a Motorol C118
by Maciej Grela 02 Jul '10

02 Jul '10

Hi, I've recently bought two Motorolas C118 with the intent of trying osmocombb. I have trouble running the firmware correctly however. Here are the steps I'm taking: 1. Run osmocom: thermal@richese:~/Publiczny/devel/osmocombb/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123 /home/thermal/Publiczny/devel/osmocombb/osmocom-bb/src/target/firmware/board/compal_e88/layer1.ramload.bin 2. Press power on the phone. 3. Phone boots and downloads code from osmocon (this code lands in RAM I presume) Received PROMPT1 from phone, responding with CMD read_file(/home/thermal/Publiczny/devel/osmocombb/osmocom-bb/src/target/firmware/board/compal_e88/layer1.ramload.bin): file_size=40232, hdr_len=4, dnload_len=40239 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(): 1087 bytes (1087/40239) handle_write(): 768 bytes (1855/40239) handle_write(): 768 bytes (2623/40239) handle_write(): 768 bytes (3391/40239) handle_write(): 768 bytes (4159/40239) handle_write(): 768 bytes (4927/40239) handle_write(): 768 bytes (5695/40239) handle_write(): 768 bytes (6463/40239) handle_write(): 768 bytes (7231/40239) handle_write(): 768 bytes (7999/40239) handle_write(): 768 bytes (8767/40239) handle_write(): 768 bytes (9535/40239) handle_write(): 768 bytes (10303/40239) handle_write(): 768 bytes (11071/40239) handle_write(): 768 bytes (11839/40239) handle_write(): 768 bytes (12607/40239) handle_write(): 768 bytes (13375/40239) handle_write(): 768 bytes (14143/40239) handle_write(): 768 bytes (14911/40239) handle_write(): 768 bytes (15679/40239) handle_write(): 768 bytes (16447/40239) handle_write(): 768 bytes (17215/40239) handle_write(): 768 bytes (17983/40239) handle_write(): 768 bytes (18751/40239) handle_write(): 768 bytes (19519/40239) handle_write(): 768 bytes (20287/40239) handle_write(): 768 bytes (21055/40239) handle_write(): 768 bytes (21823/40239) handle_write(): 768 bytes (22591/40239) handle_write(): 768 bytes (23359/40239) handle_write(): 768 bytes (24127/40239) handle_write(): 768 bytes (24895/40239) handle_write(): 768 bytes (25663/40239) handle_write(): 768 bytes (26431/40239) handle_write(): 768 bytes (27199/40239) handle_write(): 768 bytes (27967/40239) handle_write(): 768 bytes (28735/40239) handle_write(): 768 bytes (29503/40239) handle_write(): 768 bytes (30271/40239) handle_write(): 768 bytes (31039/40239) handle_write(): 768 bytes (31807/40239) handle_write(): 768 bytes (32575/40239) handle_write(): 768 bytes (33343/40239) handle_write(): 768 bytes (34111/40239) handle_write(): 768 bytes (34879/40239) handle_write(): 768 bytes (35647/40239) handle_write(): 768 bytes (36415/40239) handle_write(): 768 bytes (37183/40239) handle_write(): 768 bytes (37951/40239) handle_write(): 768 bytes (38719/40239) handle_write(): 768 bytes (39487/40239) handle_write(): 752 bytes (40239/40239) 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: 42 B Received DOWNLOAD ACK from phone, your code is running now! Hello World from apps/layer1/main.c program code ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: 058d320a9e039bfc ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!! Assert DSP into Reset Releasing DSP from Reset Setting some dsp_api.ndb values Setting API NDB parameters DSP Downlad Status disabledDSP API Version: 0x0000 0x0000 Finishing download phase DSP Downlad Status disabledDSP API Version: 0x3606 0x0000 What is the layer1 firmware supposed to do now ? I've tried to run layer23/bcch_scan and layer23/layer23 but they don't print any messages and so does the firmware itself. I'm under the impression that the firmware freezes. Have you tested the firmware on a C118 phone ? I will try to find out why it's freezing but maybe I'm missing something obvious ? Best regards, Maciej Grela

2 2

Project hardware question
by Drasko DRASKOVIC 01 Jul '10

01 Jul '10

Hi, I have been looking for sometime at OsmocomBB project, but haven't tied it yet. I have seen that software supports a number of Compal phones : Supported Phone hardware Information specific to certain Calypso based phones that we support Designed + Manufactured by Compal, OEM by Motorola MotorolaC115/C117 (E87) MotorolaC123/C121/C118 (E88) -- our primary target MotorolaC140/C139 (E86) MotorolaC155 (E99) -- our secondary target MotorolaV171 (E68/E69) SonyEricssonJ100i So, I was wondering: 1) Which would be best to have to start with, as the most supported target ? 2) Where I can get this phone quickly and easily ? 3) What additional equipment is needed (how do you flash the software and how do you debug) ? 4) Is there some software simulator in which I could see what is happening and how the SW works without actual HW equipment ? Best regards, Drasko

2 1

RSL of Osmocom
by Andreas.Eversberg 30 Jun '10

30 Jun '10

hi, i like to do extensions to the RSLms layer of osmocom. before that i like to ask and discuss if this would be the correct way: instead directly of calling l1ctl_* functions of l1ctl.c, i would like to use RSL messages between layer 2 and layer 3. the lapdm.c would then convert these messages and call l1ctl_* functions. (maybe i could split up lapdm.c into lapdm.c and layer2.c. the selecting the handler for an RSL request could be made at layer2.c, as well as selecting the right handler for the frames received from layer1. only the lapdm part could be handled in lapdm.c. ) the RACH request could be sent using RSL_MT_CHAN_RQD, the confirm could be the same message type, but i prefer to invent a new one: 0x18, but using the same IE layout. also including RSL_IE_MS_POWER_PARAM with the RACH request, could tell the layer 1 about usage of power and TA (which is normally 0 for RACH request). the (UNIT) DATA request may also include RSL_IE_MS_POWER_PARAMS. if omitted, the stored value from the last message with RSL_IE_MS_POWER_PARAMS could used. the (UNIT) DATA indication and request of SACCH may include RSL_IE_L1_INFO IE to receive power and timing control as well as send the actual power and timing advance. i could handle these IE at layer 3 (radio ressource) and forward them to layer 1 (RSL_IE_MS_POWER_PARAM) depending on the supported radio power and on special VTY settings to mess with power and fake timing advance. regards, andreas

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel