July 2011 - baseband-devel - lists.osmocom.org

Engagetted !

by Sébastien Lorquet

http://www.engadget.com/2010/12/29/researchers-eavesdrop-on-encrypted-gsm-c… Congrats!

6 months, 3 weeks

5
5
0 0

Please can anyone advise me - FMTOOL Error and no further processing

by Raz Sharif

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

7 years, 11 months

5
6
0 0

cell re-selection

by Andreas.Eversberg

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

8 years, 2 months

3
3
0 0

AW: The call has been rejected

by Andreas.Eversberg

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

11 years

3
2
0 0

status report layer1 and layer23

by Andreas.Eversberg

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

11 years

2
1
0 0

Receiving on TS=1 ?

by Sylvain Munaut

Hi, I've hacked something together to quickly test non-combined CCCH. However, I've hit a problem when trying to receive anything on another timeslot than 0. The TX side seems to work fine as the BTS can see my location update request and answers with a reject, but on the MS side, I never see the reject and wireshark only shows invalid incohrent data on the RX. The frames for SDCCH/8 show really nothing valid (looks like random bytes), things like 09 80 7f 47 49 06 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 09 00 47 d5 2d 06 1e 00 00 69 7c a0 91 3d 22 ff ab fe 6c 4f 56 4f 36 ... while the frames for the associated SAACH show at least something gsm-like : 03 03 01 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b but that's not quite a SI5/6 ... To RX/TX on TS=1, I just delayed the RX/TX window by 625 bits (4 * 156.25) when I'm in dedicated channel mode by chaning the 'start' in l1s_tx_win_ctrl / l1s_rx_win_ctrl Is there something else that should be done ? Cheers, Sylvain

11 years, 9 months

2
5
0 0

burst_ind and TCH

by Mad

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

11 years, 10 months

4
5
0 0

bursts****.dat

by Victor P

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.

11 years, 11 months

5
6
0 0

Use OsmocomBB as OpenBTS / airprobe clock generator

by Harald Welte

Hi! Recently we've had the idea of using OsmocomBB with a simple firmware that synchronizes to an existing GSM networks FCCH and use the resulting 13MHz clock to drive the USRP for airprobe or OpenBTS. Ideally, we would even use the Calypso-internal PLL (for ARM or DSP) to multiply it up to the required 52 MHz. However, neither the Openmoko nor the Compal/Motorola phones expose any of the 3 clock output pads :( So the only choice is to use something along the lines of the http://focus.ti.com/docs/prod/folders/print/cdcvf25084.html as a quad clock multiplier and attach it to the CLK13OUT signal of the phone. The chip is available for 9 USD in single quantities at digikey, and possibly cheaper at other sources. Combined with a sub-20EUR phone it might be a very cheap but still accurate frequency source for OpenBTS - at least as long as there are any commercial gsm networks available. 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)

12 years, 1 month

8
17
0 0

Linux + u-boot port to MT6235

by Marcin Mielczarczyk

Hi All! That's true, I managed to run U-Boot on MT6235, but linux kernel is not fully functional yet (it's fresh stuff as I managed to ran it on Tuesday and then I was off to conference). For MT6235 development I chose Sciphone G2, which is pretty cheap. After some time I managed to download code to SRAM (just 64KB) using MTK's FlashTool. MTK FlashTool communicates over UART directly with MT6235 bootloader and sends its own chunk of code (about 58KB) which is executed in SRAM and communicates with FlashTool. I found on pudn.com some pack to customize code loaded by FlashTool, thanks to which I could download my own code to SRAM (without JTAG). The problem was that it had to be linked with some security libraries which occupied about 56KB and not much memory left for my own code. Then I decided to try find JTAG pins to get all control on MT6235. That took me sometime, but finally I succeeded. The other bigger issue was initializing DRAM controller to be able to download bigger code (linux kernel + uboot) to external RAM. In sciphone there is problem that all interesting chips are under metal shield which is pretty havily soldered. In this case I couldn't read what kind of RAM memory is mounted without destroying the board (I don't have such soldering machine which could unsolder so big metal shield). Thanks to JTAG I could attach to target and then dump DRAM controller registers from processor running MTK's software, but setting these values after processor start and configuration of PLL didn't work. I decided to disassemble bootloader which could show me how DRAM controller is initialized and how code fron NAND is loaded (to be able to flash U-Boot and kernel to NAND so MT6235 will start my code automatically and I will not have to use JTAG). Currently I have knowledge how internal MT6235 bootloader is loading code from memory during startup and I also extracted procedure of DRAM controller initialization. Thanks to that I'm able to run U-Boot from the very begining of processor startup. The problem is that I have just one piece of Sciphone G2 and I don't want to flash it yet to not break existing code in it. Thanks to running device I'm able to attach with JTAG and check how peripherals are configured (i.e. LCD, MMC, etc.). I have backup of flash, but I'm not 100% sure if I will flash it back, phone will startup. That's why I bought second piece of Sciphone G2 and should receive it today or on Tuesday (this Monday is holiday in Poland). In this case I'll flash U-Boot to NAND and try to make it working. Then we could load the rest of code from U-Boot (to RAM or NAND over serial). You can see how my setup looks on attached picture. The good thing about it is that the same bootloader is used in MT622x, so it should be fairly easy to do the same on phones based on that SoCs (but unfortuantely it's just ARM7). If it comes to code, of course I can share it on "git.osmocom.org". Currently it's just basic port of U-Boot and not much for linux kernel, but I'm working on this now so I'll push it when it'll be ready. Currently I'm working on driver for NAND memory for U-Boot, so we could flash linux kernel. When that will be ready I'll push the code. Then I'll switch to linux kernel and when it'll be functional I also push the code. At this stage you will not need to have JTAG and you could load the code over serial in U-Boot. If it comes to GSM I didn't work with it before. I actualy worked 6 months in L2/3 team for LTE (on RRC) but it's different story. That could be really outstanding thing if we could run first phone ever with whole code open (from BB up to APP). BR, Marcin

12 years, 4 months

13
37
0 0

calypso SIM driver on c139 (also: l1ctl SIM APDU)

by Gianni Tedesco

The SIM and the SIM reader in the phone and the mechanical contact between them are definitely working because the SIM can be accessed from the motorola firmware, from another phone and from a PC smartcard reader with no PIN or anything. However, under simtest firmware no data is received by the phone, even the ATR is zero bytes... Anybody had this problem? Also, is l1CTL SIM APDU command not implemented in the layer1 firmware? How are people making calls without a SIM? :P Gianni ----------------SIMTEST----8<----------------- Initializing driver: SIM: Registering interrupt handler for simcard-interface ====================== CALYPSO SIM REGISTER DUMP ===================== Reg_sim_cmd register (R/W) - FFFE:0000 |-REG_SIM_CMD = 0000 | |-REG_SIM_CMD_CMDCARDRST = 0 ==> SIM card reset sequence disabled. | |-REG_SIM_CMD_CMDIFRST = 0 | |-REG_SIM_CMD_CMDSTOP = 0 | |-REG_SIM_CMD_CMDSTART = 0 | |-REG_SIM_CMD_MODULE_CLK_EN = 0 ==> Clock of the module disabled. |-REG_SIM_STAT = 000b | |-REG_SIM_STAT_STATNOCARD = 1 ==> No card! | |-REG_SIM_STAT_STATTXPAR = 1 ==> Parity ok! | |-REG_SIM_STAT_STATFIFOFULL = 0 | |-REG_SIM_STAT_STATFIFOEMPTY = 1 ==> Fifo empty! |-REG_SIM_CONF1 = 000c | |-REG_SIM_CONF1_CONFCHKPAR = 0 ==> Parity check on reception disabled. | |-REG_SIM_CONF1_CONFCODCONV = 0 ==> Coding convention is direct (normal). | |-REG_SIM_CONF1_CONFTXRX = 1 ==> SIO line direction is in transmit mode. | |-REG_SIM_CONF1_CONFSCLKEN = 1 ==> SIM clock in normal mode. | |-REG_SIM_CONF1_reserved = 0 ==> ETU period is CONFETUPERIOD. | |-REG_SIM_CONF1_CONFSCLKDIV = 0 ==> SIM clock frequency is 13/4 Mhz. | |-REG_SIM_CONF1_CONFSCLKLEV = 0 ==> SIM clock idle level is low. | |-REG_SIM_CONF1_CONFETUPERIOD = 0 ==> ETU period is 372/8*1/Fsclk. | |-REG_SIM_CONF1_CONFBYPASS = 0 ==> Hardware timers and start and stop sequences are normal. | |-REG_SIM_CONF1_CONFSVCCLEV = 0 ==> SVCC Level is low (Only valid when CONFBYPASS = 1). | |-REG_SIM_CONF1_CONFSRSTLEV = 0 ==> SRST Level is low (Only valid when CONFBYPASS = 1). | |-REG_SIM_CONF1_CONFTRIG = 0x0 (FIFO trigger level) | |-REG_SIM_CONF1_CONFSIOLOW = 0 |-REG_SIM_CONF2 = 0940 | |-REG_SIM_CONF2_CONFTFSIM = 0x0 (time delay for filtering of SIM_CD) | |-REG_SIM_CONF2_CONFTDSIM = 0x4 (time delay for contact activation/deactivation) | |-REG_SIM_CONF2_CONFWAITI = 0x9 (CONFWAITI overflow wait time between two received chars) |-REG_SIM_IT = 0000 | |-REG_SIM_IT_SIM_NATR = 0 ==> On read access to REG_SIM_IT. | |-REG_SIM_IT_SIM_WT = 0 ==> On read access to REG_SIM_IT. | |-REG_SIM_IT_SIM_OV = 0 ==> On read access to REG_SIM_IT. | |-REG_SIM_IT_SIM_TX = 0 ==> On write access to REG_SIM_DTX or on switching | | from transmit to receive mode (CONFTXRX bit) | |-REG_SIM_IT_SIM_RX = 0 ==> On read access to REG_SIM_DRX. |-REG_SIM_DRX = 0100 | |-REG_SIM_DRX_SIM_DRX = 0x0 (next data byte in FIFO available for reading) | |-REG_SIM_DRX_STATRXPAR = 1 ==> Parity Ok. |-REG_SIM_DTX = 00 (next data byte to be transmitted) |-REG_SIM_MASKIT = 003f | |-REG_SIM_MASKIT_MASK_SIM_NATR = 1 ==> No-answer-to-reset interrupt is masked. | |-REG_SIM_MASKIT_MASK_SIM_WT = 1 ==> Character wait-time overflow interrupt is masked. | |-REG_SIM_MASKIT_MASK_SIM_OV = 1 ==> Receive overflow interrupt is masked. | |-REG_SIM_MASKIT_MASK_SIM_TX = 1 ==> Waiting characters to be transmit interrupt is masked. | |-REG_SIM_MASKIT_MASK_SIM_RX = 1 ==> Waiting characters to be read interrupt is masked. | |-REG_SIM_MASKIT_MASK_SIM_CD = 1 ==> SIM card insertion/extraction interrupt is masked. |-REG_SIM_IT_CD = fffe0010 |-REG_SIM_IT_CD_IT_CD = 0 ==> SIM card insertion/extraction interrupt is unmasked. Power up simcard: * Power enabled! * Clock enabled! * Reset released! SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Character underflow! (0 bytes) Reset simcard: * Reset pulled down! * Reset released! SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Character underflow! (0 bytes) SIM-T0: Transceiving APDU-Header: (a0 a4 00 00 02) SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-T0: Case 2: No input / Output of known length (See also GSM 11.11 Page 34) SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Character underflow! SIM-T0: T0 Protocol error: Missing ACK byte -- aborting! SIM-T0: Transceiving APDU-Header: (a0 c0 00 00 0f) SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-T0: Case 4: Input / No output (See also GSM 11.11 Page 34) SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Character underflow! SIM-T0: T0 Protocol error: Incorrect or missing answer -- aborting! e0 73 d7 b9 ae ea bf 7e f7 3b 7f 6f 32 fe 25 (15 bytes) Test Phase 1: Testing bare sim commands... * Testing SELECT: Selecting MF SIM-T0: Transceiving APDU-Header: (a0 a4 00 00 02) SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-T0: Case 2: No input / Output of known length (See also GSM 11.11 Page 34) SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Character underflow! SIM-T0: T0 Protocol error: Missing ACK byte -- aborting! ==> Status word: ffff * Testing SELECT: Selecting DF_GSM SIM-T0: Transceiving APDU-Header: (a0 a4 00 00 02) SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... At this point it hangs "forever" - well at least half hour.

12 years, 6 months

7
11
0 0

Problems while building osmocomBB

by Begerad Stefan

Hi guys, I dunno if that is the right place for my concern about building the osmocomBB source. Here is what I already have done: - downloading the sources for osmocomBB and GNU toolchain for ARM, - setting the PATH for the arm-elf-* executables, - calling make in the src directory. Now, this appears as response of the make command in the terminal: cd shared/libosmocore/build-host && ../configure configure: error: cannot find install-sh, install.sh, or shtool in ".." "../.." "../../.." make: *** [shared/libosmocore/build-host/Makefile] Error 1. If you need details about my system, you can look at the following snippet from the config.log file: This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by libosmocore configure UNKNOWN, which was generated by GNU Autoconf 2.65. Invocation command line was $ ../configure ## --------- ## ## Platform. ## ## --------- ## hostname = ubuntu-stefan uname -m = x86_64 uname -r = 2.6.32-24-generic uname -s = Linux uname -v = #41-Ubuntu SMP Thu Aug 19 01:38:40 UTC 2010 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin PATH: /usr/games PATH: /home/stefan/osmocomBB/gnuarm-4.0.2/bin ## ----------- ## ## Core tests. ## ## ----------- ## configure:2032: error: cannot find install-sh, install.sh, or shtool in ".." "../.." "../../..". So, I would be very glad, if someone could give me a hint to solve the problem. Thank you in advance. Regards, begy

12 years, 6 months

2
2
0 0

Re: neighbour cell measurement

by Dieter Spaar

Hello Andreas, hello Harald, On Thu, 14 Jul 2011 13:44:16 +0200, "Harald Welte" <laforge(a)gnumonks.org> wrote: > > The patches look fine to me. I'd wait for another day if Sylvain or > Dieter have any comments, but otherwise they can be merged. The patches are fine for me. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

12 years, 8 months

3
2
0 0

C115 using loader.compalram.bin

by Bruce, Bryan

Hello, I am using a C115 with a t191 cable. We have completed the "Getting Started" steps and have compiled all the necessary code. I are currently trying to run osmocon to download code onto the phone. The following output appears when we run the script: bruceb@ubuntu:~/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 1 bytes from modem, data looks like: 2d - got 1 bytes from modem, data looks like: 34 4 got 1 bytes from modem, data looks like: 29 ) got 1 bytes from modem, data looks like: 28 ( got 1 bytes from modem, data looks like: 32 2 got 1 bytes from modem, data looks like: 39 9 got 1 bytes from modem, data looks like: 30 0 got 1 bytes from modem, data looks like: 20 got 1 bytes from modem, data looks like: 2d - got 1 bytes from modem, data looks like: 34 4 got 1 bytes from modem, data looks like: 29 ) got 1 bytes from modem, data looks like: 0a . got 1 bytes from modem, data looks like: 0d . got 1 bytes from modem, data looks like: 02 . These lines continue and no script indicates anything is being downloaded, as shown on the wiki site. I have unlocked the phone and put it in "earphone" mode beforehand. I have also tried to press the power button as directed to. Are there any suggestions on how to fix this problem? Thank you, Bryan Bruce

12 years, 9 months

2
1
0 0

OT: GTA04 - Openmoko

by Benjamin Hagemann

Hello, a german news website gave me the hint to new infos about the GTA04. english sites: http://projects.goldelico.com/p/gta04-main/ http://lists.goldelico.com/pipermail/gta04-owner/2011-July/000185.html http://www.handheld-linux.com/wiki.php?page=GTA04-Early-Adopter&referer=Neo… and the german news about this topic: pro-linux: OpenMoko GTA04 bald bereit zum Test http://www.pro-linux.de/news/1/17318/openmoko-gta04-bald-bereit-zum-test.ht… -- Have a nice day, Benny gpg 0xFC505AB0 jabber benny(a)benny.de sip benny(a)benny.de

12 years, 9 months

2
1
0 0

IMEI numbers, signal strength

by miprom68＠gmail.com

Can someone help with these? 1) With the GSM debugger phone, how difficult is it to get only IMEI numbers of received packets? 2) Can the debugger phone report the signal strength of received packets? If not, is it possible? 3) Is there any way with mods to get I/Q out of the DSP? 4) Is there any work going on to make a CDMA debugger phone? 5) Are there any GSM phones that have an option to force calls to be made only on 3G/4G? Thank you, Ben

12 years, 9 months

5
13
0 0

Tx Support

by iBruno

Hello community After making the changes to Makefile.inc (src/target/firmware) -include Makefile.inc # Uncomment this line if you want to enable Tx (Transmit) Support. -CFLAGS += -DCONFIG_TX_ENABLE +CFLAGS += -DCONFIG_TX_ENABLE # Uncomment this line if you want to write to flash. #CFLAGS += -DCONFIG_FLASH_WRITE I'm trying to figure out, what to do with this part: enable CONFIG_TX_ENABLE diff --git a/src/target/firmware/Makefile b/src/target/firmware/Makefile index 56e0068..c69aab7 100644 --- a/src/target/firmware/Makefile +++ b/src/target/firmware/Makefile @@ -73,7 +73,7 @@ ANY_APP_LIBS+=calypso/libcalypso.a layer1/liblayer1.a lib/libmini.a comm/libcomm ...Meanwhile I tried to compile, and at the time Makefile.inc is callled starts looping forever.... Makefile.inc:135: warning: overriding commands for target `board/compal_e99/loader.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/loader.highram.size' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.map' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.size' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.map' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.size' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.size' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.size' Makefile.inc:171: warning: overriding commands for target `calypso/libcalypso.a' Makefile.inc:171: warning: ignoring old commands for target `calypso/libcalypso.a' Makefile.inc:171: warning: overriding commands for target `layer1/liblayer1.a' Makefile.inc:171: warning: ignoring old commands for target `layer1/liblayer1.a' Makefile.inc:171: warning: overriding commands for target `comm/libcomm.a' Makefile.inc:171: warning: ignoring old commands for target `comm/libcomm.a' Makefile.inc:171: warning: overriding commands for target `lib/libmini.a' Makefile.inc:171: warning: ignoring old commands for target `lib/libmini.a' Makefile.inc:208: warning: overriding commands for target `clean' Makefile.inc:208: warning: ignoring old commands for target `clean' Makefile.inc:212: warning: overriding commands for target `distclean' Makefile.inc:212: warning: ignoring old commands for target `distclean' ^Cmake: *** [firmware] Interrupt After reviewing the groups & googing, didn't came out with understanding/solution Very appreciated, if help can be given. Thank you Bruno.

12 years, 9 months

1
0
0 0

positioning

by Matzi Kratzi

(In a sort-of-answer to the triangulating mail a while ago:) > i wanted to know is it possible to triangulate any gsm cellphone with osmocombb?? Hi, It would be possible triangulate your own position using osmocombb. Assumption 1 (A1): The base stations of GSM are very stable and can keep running for months or years without interruption. Assumption 2 (A2): Osmocombb has a free running quarter bit counter that it never restarts when power is on. The timings of different cells are calculated relative to this free running counter. To be able to triangulate a phone, we need information about the cells in the area: The GSM TDMA system has a periodicity for broadcasted messages such as sync and SI1. The timing of these can be predetermined as an offset relative to the free running counter in A2. Note that the offset includes the propagation time for the signal from the base station to the mobile station. If the position of the mobile phone with osmocombb (MS) is known, one can get the offset for the first base station broadcasts (dt_BS1). If the MS is moved later to at least three other known positions and the same offsets are calculated, one can calculate the actual offset between the MS free running counter and the BS1 without the propagation time included. At the same time the actual position of the BS is calculated. [1] An MS should do measurements on neighbour cells as well, and can therefor do exactly the same calculations for several BS:s at the same time. An interesting aspect of this is that it is then possible to calculate the difference in timing for several BS:s. If the positions and relative timings for the BS:s in an area are known, it is possible to calculate the position of an MS. This time we do the same calculations, but now the relative timings for the BS:s and the position are known and the same for the MS is unknown. An interesting fact is that osmocombb could use the timings for BS:s from several operators to increase the accuracy of the calculations. Assumption 1 can be held for granted. Assumption 2 could be made true if it is not already true. The concept could probably otherwise be used anyway if that is not accepted. 1 http://en.wikipedia.org/wiki/Multilateration MS Mobile station (phone, modem) BS Base station dt_BSx timing offset from the free running timer to base station number x /Matzi

12 years, 9 months

1
0
0 0

Some considerations about IMSI Detach DoS Attack

by Gloria Mazzi

Hi all, as stated on OsmocomSecurity: "A malicious attacker knowing the IMSI or TMSI of a victim can thus send hand-crafted IMSI DETACH messages to a cell, causing the network to assume the MS is no longer present in the network.This will effectively prevent the delivery of all mobile-terminated (MT) services, such as SMS, voice calls, CSD, ...". Following the theory i've better understood how it works [1]*, but still i have some questions for you: - what could happen if i will clone one SIM (Ki, IMSI) and use it to register on the same network, but on different BTS/LAC, two phones? Which will be rejected as first? Or both? - if i will send an IMSI detach with one of them... also the other (that is phisically in another BTS/LAC) will be disconnected? - what could happen if i will connect a C123 with ./mobile to the network using another SIM and then trying to forge IMSI_DET_IND with victim's IMSI/TMSI and send to the network where the victim is connected (that could mean the same network, but different BTS/LAC), this DoS will still be accomplished? What exactly i would like to know is, if someone already made some experiments on it (obviously on private networks, with a legal experimental license.) and eventually if there are any interesting results. Thank you for attention. Cheers Gloria *[1] - http://www.gsmfordummies.com/gsmevents/detach.shtml

12 years, 9 months

4
5
0 0

Telecommunication and Wireless Hacking at CCC CAMP 2011

by Fabio Pietrosanti (naif)

Hi all, i just wanted to send a summary of all most cool talk that will be at CCC CAMP 2011 related to Telecommunications and Wireless Technologies hacking: Open-source 4G radio - It's time to start WiMAX and LTE hacking http://events.ccc.de/camp/2011/Fahrplan/events/4446.en.html Applied Research on security of TETRA radio - Digital radio technology beyond GSM http://events.ccc.de/camp/2011/Fahrplan/events/4496.en.html GPRS Intercept - Wardriving phone networks http://events.ccc.de/camp/2011/Fahrplan/events/4504.en.html Introduction to Satellite Communications - Installation and Operation of Satellite Systems http://events.ccc.de/camp/2011/Fahrplan/events/4442.en.html Transition Telecom - Telecommunications and networking during energy descent http://events.ccc.de/camp/2011/Fahrplan/events/4459.en.html Anyone missing to the list? -naif

12 years, 9 months

1
1
0 0

AW: gpsd and as-needed patches

by Andreas.Eversberg

hi vlatko, thanx for your patches. i don't have knowledge about gpsd api. before i can apply them, i need to know about gps_waiting() function. the osmo_gpsd_cb() function in common/gps.c is called when there is data to be read from gpsd. this function (like any other function) may not delay or block. (except for the CPU processing time of the function.) if no data is available from gpsd, the function must continue with "goto gps_not_ready;" immidately. what will gps_waiting() do in case there is no (complete) information available? regards, andreas

12 years, 9 months

2
1
0 0

gpsd and as-needed patches

by Vlatko Kosturjak

Hello! Hopefully this is right place to send patches since I don't have access to tracker. I'm sending two patches against latest git version. First one is updating gpsd support since new gpsd have few functions changed: I've #ifdefed each offending function, so you can check each function in configure process or just wrap everything inside same #ifdef, depending on your wish. I have #defined timeout, but it can be done as variable if you think 2000 miliseconds is not good for everybody. Other patch is just quick hack to support --as-needed linker flag, so osmocombb can compile fine on distros which enforce such flag. In order, to read more about flag, read here: http://www.gentoo.org/proj/en/qa/asneeded.xml (In short, order of flags do matter) Hope it helps, -- Vlatko Kosturjak - KoSt

12 years, 9 months

1
0
0 0

Is it possible to triangulate cellphone with osmocombb

by Akib Sayyed

Guys i bit new to osmocombb i wanted to know is it possible to triangulate any gsm cellphone with osmocombb?? -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

12 years, 9 months

1
0
0 0

Motorola C116 experiment

by Henk

Hi, I could not resist buying a C116 for 15 euro, so I compiled osmocombb and connected a 3.3V serial cable. Of course the C116 was not in the supported list, but I was hoping it would work as it seems that it is very similar to the C115. Here is my load attempt: (used -m c123 ) but there's no loading of the image. I am not using TX mode, also I don't have a SIM installed. Anything I can try to get it working? ./osmocon -p /dev/ttyS0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 00 81 .. got 4 bytes from modem, data looks like: 1b 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 read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=16788, hdr_len=4, dnload_le n=16795 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: 1b . got 1 bytes from modem, data looks like: 66 f 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 Regards, Henk

12 years, 9 months

6
7
0 0

AW: GSM 03.22 bug / unreachable code?

by Andreas.Eversberg

> while using Smatch on layer23, I discovered a potential problem in GSM > 03.22: There is a loop with an if-statement, and there might be missing > curly braces. hi harald, you are right. patch is committed. thanx, andreas

12 years, 9 months

1
0
0 0

USB -FTDI 232RL- RS232 Converter

by iBruno

Hello I am having troubles, to find the decent cable/interface to get this working properly!! I bough converter USB -FTDI 232RLChip- RS232, Converter. IS giving me 6.60v Output.. and I needed 3.3v. Electronically, what can I do, to adjust for the correct Voltage? My phone didn't fry, besides I got connection! when I load the hello world or layer one, is not completing the task! I believe is because of the amount of power. If you know a cable that works decently, let me know :-) Big thanks to whole community.

12 years, 9 months

2
1
0 0

GSM 03.22 bug / unreachable code?

by Harald Welte

Hi Andreas, while using Smatch on layer23, I discovered a potential problem in GSM 03.22: There is a loop with an if-statement, and there might be missing curly braces. Do you think this is the correct way to fix it? diff --git a/src/host/layer23/src/mobile/gsm322.c b/src/host/layer23/src/mobile/gsm322.c index 210215e..766ffbf 100644 --- a/src/host/layer23/src/mobile/gsm322.c +++ b/src/host/layer23/src/mobile/gsm322.c @@ -983,9 +983,10 @@ static int gsm322_a_user_resel(struct osmocom_ms *ms, struct msgb *msg) /* search current PLMN in list */ llist_for_each_entry(plmn_entry, &plmn->sorted_plmn, entry) { if (plmn_entry->mcc == plmn->mcc - && plmn_entry->mnc == plmn->mnc) + && plmn_entry->mnc == plmn->mnc) { plmn_found = plmn_entry; break; + } } /* abort if list is empty */ -- - 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)

12 years, 9 months

1
0
0 0

neighbour cell measurement

by Andreas.Eversberg

hi, i would like to commit my well tested neighbour cell measurement code, as well as the improved cell selection / re-selection process soon. with it, it is possible to move with the mobile phone while beeing in idle mode (no call). it tracks neighbour cells and switches if a better cell is detected. i found and fixed many bug issues in mobility management and cell selection process. i did allot of driving tests. in order to do that, the neighbour cell measurement code for layer1 is required. this code must be reviewed first. i splitted it in three patches: neigh_getset.patch [layer1] Adding rffe_set_gain() and rffe_get_gain() to get/set computed gain. rffe_compute_gain() is the new name for rffe_set_gain(). I needed to change this, to solve the name collision with the rffe_set_gain() function, which actually sets the absolute gain. rffe_get_gain() will now read the absolute gain which has been computed by rffe_compute_gain() or set by rffe_set_gain(). neigh_l23.patch [layer23] Adding neighbour cell measurement to L1CTL interface. (layer23) neigh_l1.patch [layer1] Adding neighbour cell measurement code to layer1. When listening to BCCH, layer1 may measure the power level of neighbour cells. A list of neighbour cell frequencies need to be sent to layer1. After the measurement is done, the results are indicated to layer23. andreas

12 years, 9 months

4
3
0 0

AW: neighbour cell measurement

by Andreas.Eversberg

> The patches look fine to me. I'd wait for another day if Sylvain or > Dieter have any comments, but otherwise they can be merged. i will remove some comments and temporary debug prints before committing.

12 years, 9 months

1
0
0 0

problems to run ./mobile app

by josephli

Hello every: When I tried to run ./mobile -i 127.0.0.1, the words Failed to parse the config file: '/root/.osmocom/bb/mobile.cfg' Please check or create config file using:'touch /root/osmocom/bb/mobile.cfg' came out. I checked my directory /ect and there is nothing there. It seems that network between my PC and phone is block so that the application ./mobile can not communicate with phone. However the layer1 can load on the phone and work properly. Can any one tell my how to fix this problem? Cheers, Li -- View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-to-run-mobile-app-tp316… Sent from the baseband-devel mailing list archive at Nabble.com.

12 years, 9 months

2
8
0 0

Help me I have a difficult problem

by adel

Hello I'm having a problem in the start mobile application ~/osmocom-bb$ cd src/host/layer23/src/mobile ~/osmocom-bb/src/host/layer23/src/mobile$ ./mobile Copyright (C) 2008-2010 ... Contributions by ... License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Failed to parse the config file: '/etc/osmocom/osmocom.cfg' Please check or create config file using: 'touch /etc/osmocom/osmocom.cfg' ~/osmocom-bb/src/host/layer23/src/mobile$ Please help me as soon as -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Help-me-I-have-a-difficult-probl… Sent from the baseband-devel mailing list archive at Nabble.com.

12 years, 9 months

11
17
0 0

Is data actually sent if "COMPILED WITHOUT TX SUPPORT"?

by Sergey

Hello! Is any way that data is actually sent to air if on loading "layer1.compalram.bin" 'osmocon' says: "THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!! " ? E.g. when 'mobile' says "sending page response" does it really communicate with the BTS? I'm talking about main branch (not testing) and compiled without TX support. Sorry if it's obvious, I just dont want to find "the very extent permittable by law".

12 years, 10 months

2
1
0 0

gsm specifications

by Sergey

Hello, everyone! I've got c123-compatible phone, the firmware is running and that's really cool. Testing branch even sometimes says that a call has been released, but it doesn't seem to reach the target (no ringing). I would like to debug and maybe contribute, but... But here is a problem: I don't understand GSM and can't find reasonable documents to read. I've looked through a book on gsm "GSM and Personal Communications Handbook", but it doesn't seem to provide enough info. Specifications of GSM I found at http://www.3gpp.org/specification-numbering are too plentiful. Could you please advise some books to understand the protocols? Or could you tell me where to look for specifications and which should be read first (an what to be read at all) ?

12 years, 10 months

4
5
0 0

Bounce action notification

by mailman＠lists.osmocom.org

This is a Mailman mailing list bounce action notice: List: baseband-devel Member: andre(a)ac.nl.eu.org Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman(a)lists.osmocom.org.

12 years, 10 months

1
0
0 0

GPSD support

by Victor P

Hello.I have been trying to use cell_log with bluetooth GPS. I used gpsd v 2.37 and v 2.95, but in both cases I had the error "Osmocom was compiled without gpsd support". Should I use another version of gpsd or mistake in compilation (any patch?)? thank you for helpWith best wishes,Victor

12 years, 10 months

2
1
0 0

Success at last - C139 now working Layer1.bin displayed on phone :)

by Raz Sharif

Dear all, the last few days I have as you know sent a few mails in my quest to delve into the Osmocomm GSM stack. A few problems later and a few substitutes later such as a C139 phone versus the C115 am I now good to go it would appear. Please see below. I did a lot of RTFM and would also like to to thank the folks who provided me with pointers. I will no doubt have a few more issues so lets see. In summary - The Prolific cable works fine albeit a small cut back on the connector - 2.5mm side C115 is supported but if you can go for the C139 - Too many issues to resolve with C115 maybe due to a specific Firmware variant. If you have the time to hack around I am sure it not difficult to work. Here's my Boot loader dump. Please see below. Thanks Raz http://pastebin.com/A1xf8Wkt

12 years, 10 months

1
0
0 0

C139 confirmation of operation from Users please.

by Raz Sharif

Hi Folks, I recently mailed the group to discuss issue with the C115 Phone and am now trying the C139. It appears to load and i get :- ./osmocon -p /dev/ttyUSB0 -m c140 -c ../../target/firmware/board/compal_e86/layer1.highram.bin ../../target/firmware/board/compal_e86/chainload.compalram.bin read_file(../../target/firmware/board/compal_e86/chainload.compalram.bin): file_size=4132, hdr_len=4, dnload_len=15341 read_file(../../target/firmware/board/compal_e86/chainload.compalram.bin): file_size=4132, hdr_len=4, dnload_len=15341 got 2 bytes from modem, data looks like: 2e c8 .. got 1 bytes from modem, data looks like: 1b . got 4 bytes from modem, data looks like: f6 02 00 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: 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(): 4096 bytes (4096/15341) handle_write(): 4096 bytes (8192/15341) handle_write(): 4096 bytes (12288/15341) handle_write(): 3053 bytes (15341/15341) 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: 45 E got 1 bytes from modem, data looks like: 53 S got 1 bytes from modem, data looks like: 16 . Received DOWNLOAD NACK from phone, something went wrong :( 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 . kbuildsycoca4 running... Also when i run the Mobile app i get :- telnet localhost 4247 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Welcome to the OsmocomBB control interface OsmocomBB> enable OsmocomBB# exit Exit current mode and down to previous mode help Description of the interactive help system list Print command list write Write running configuration to memory, network, or terminal show Show running system information disable Turn off privileged mode command configure Configuration from vty interface copy Copy configuration terminal Set terminal line parameters echo Echo a message back to the vty who Display who is on vty monitor Monitor... no Negate a command or set its defaults off Turn mobiles off (shutdown) and exit sim SIM actions network Network ... call Make a call OsmocomBB# sim % Command incomplete. OsmocomBB# show % Command incomplete. OsmocomBB# Thanks and would be grateful for your support as I appear to be edging forwards. :) and hopefully not backwards. Raz

12 years, 10 months

1
0
0 0

Osmocom Loading Issues - TTYUSB0 loopback

by Raz Sharif

Hi folks, further to my previous email i now ran : I simply pressed the Power Switch a few times but not power on. This is what is recorded. As you will recall i get the FMTool Error and aborted message and never see Prompt2. With no Osmocom programs running can someone please confirm that this output is correct or indeed suggests that the Phones Serial Line or other Firmware or Phone Hardware is causing this error please - would be grateful. Thanks Raz _________________________________________- cat < /dev/ttyUSB0 >| rs.txt 00000000 00 2e 00 1b f6 02 00 41 01 40 66 74 6d 74 6f 6f |.......A.@ftmtoo| 00000010 6c 65 72 72 6f 72 00 00 2f 00 1b f6 02 00 41 01 |lerror../.....A.| 00000020 40 66 74 6d 74 6f 6f 6c 65 72 72 6f 72 00 00 2f |@ftmtoolerror../| 00000030 00 1b f6 02 00 41 01 40 66 74 6d 74 6f 6f 6c 65 |.....A.@ftmtoole| 00000040 72 72 6f 72 00 00 2f 00 1b f6 02 00 41 01 40 66 |rror../.....A.@f| 00000050 74 6d 74 6f 6f 6c 00 00 00 00 00 00 00 00 00 00 |tmtool..........| 00000060 00 00 00 00 00 2f 00 1b f6 02 00 41 01 40 66 74 |...../.....A.@ft| 00000070 6d 74 6f 6f 6c 65 72 72 6f 72 00 |mtoolerror.|

12 years, 10 months

1
0
0 0

osmocn question

by eisencah eisenach

Hi everyone. One remark regarding osmocon : it seems to me that we're reading one byte at the time from the serial port once we're done with downloading code into RAM. That seems quite on overhead (specially on slow machines like mine). I believe we should modify that once dnload.expect_hdlc == 0 we can free up the entire buffer. Is that so or I'm missing something? Mihai.

12 years, 10 months

1
0
0 0

Fwd: Please can anyone advise me - FMTOOL Error and no further processing

by Sébastien Lorquet

Please do not use reply in gmail, but reply to all instead. Otherwise you will only write to the message's author, Sebastien ---------- Forwarded message ---------- From: Raz Sharif <issertiv(a)gmail.com> Date: Sun, Jul 3, 2011 at 9:34 PM Subject: Re: Please can anyone advise me - FMTOOL Error and no further processing To: Sébastien Lorquet <squalyl(a)gmail.com> Sorry yes i did post this message before in an attempt to get some better insight in to the issues. The loopback test i shorted the inside and outermost pins and echo of characters appeared. I think cable is ok. Its a prolific usb to serial. I do not have a serial connector so cannot try the FTD cable option. All software looks ok but the Osmocon.just hangs and FMT tool error. So i am a little stuck to be honest. Sorry for sending this twice. Thanks Raz On 3 Jul 2011 19:29, "Sébastien Lorquet" <squalyl(a)gmail.com> wrote:

12 years, 10 months

4
6
0 0

Osmocom FMTool error

by Raz Sharif

Please could you assist me with some pointers, Good work btw. I am using a C115 with the T191 prolific USB cable. I can talk to the phone but cannot load the Layer1 Stack. I get : ./osmocon -p /dev/ttyUSB0 -m c123 ../../target/firmware/board/compal_e88/layer1.compalram.bin got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 2f / got 1 bytes from modem, data looks like: 00 . got 3 bytes from modem, data looks like: 1b f6 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: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): file_size=51272, hdr_len=4, dnload_len=51279 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 press the switch once and it just jumps and does the same again and again and again. I read that this maybe a timing issue. I have installed on 64 Bit and 32 bit ubunto on a fast machine and the result is the same. Also i do not see Layer23 command during compile. Please advise me i am happy to do the debugging but any pointers would help me as i am willing to learn from this great work that has been done by you and the team. Thanks Raz

12 years, 10 months

1
0
0 0

Please advice - C115 FMTOOL - Ramloader Aborted

by Raz Sharif

Dear Folks, After much deliberation and waiting I finally rxed a C115 and the T1 Cable USB. I am running Backtrack 5 and have compiled the Osmocomm bundles and all executable seem to be present. When i plug om the Jack cable and press the power switch i get this :- ~/osmocom-bb/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/layer1.compalram.bin got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 2f 00 /. got 4 bytes from modem, data looks like: 1b 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 read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): file_size=48808, hdr_len=4, dnload_len=48815 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 . Have have tried with Xor and without. What am I missing folks - please advice as have been at this a while now with same results. Thanks in advance. Raz

12 years, 10 months

4
5
0 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel July 2011