baseband-devel November 2013

baseband-devel@lists.osmocom.org

18 participants
30 discussions

Query on flashing the loader
by Bhaskar11 08 Nov '13

08 Nov '13

This is my first attempt to flash the loader. 1) The instructions on http://bb.osmocom.org/trac/wiki/flashing require loading the file named "target/firmware/board/compal_e88/loader.*e88loader* .bin". Strangely I do not have this file after compilation. I have loader.compalram.bin and loader.highram.bin. I also have layer1.e88loader.bin and rssi.e88loader.bin. Can you please guide me? 2) The guide for flashing an application says to use rssi.e88flash.bin. Does that mean if I want to flash "layer1" as my application, then I must use layer1.*e88flash*.bin at that point? Thank you for your help. B.

2 2

Re: Error... any can help me, please?
by Cristine 08 Nov '13

08 Nov '13

ok, i am i***t... thread can be closed, solution for fix is: git clean -dfx -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Error-any-can-help-me-please-tp4… Sent from the baseband-devel mailing list archive at Nabble.com.

1 0

Error... any can help me, please?
by Cristine 07 Nov '13

07 Nov '13

root@debian:~/osmocom-bb/src# make cd shared/libosmocore/build-target && ../configure \ --host=arm-none-eabi --enable-embedded --disable-shared \ --disable-tests ac_cv_header_sys_select_h=no \ --disable-tests ac_cv_header_sys_socket_h=no \ CFLAGS="-Os -ffunction-sections -I/root/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs" configure: WARNING: unrecognized options: --disable-shared, --disable-tests, --disable-tests checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-none-eabi-strip... no checking for strip... strip checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether make sets $(MAKE)... (cached) yes checking for arm-none-eabi-gcc... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... yes checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 ../configure: line 3803: syntax error near unexpected token `pic-only' ../configure: line 3803: `LT_INIT(pic-only)' make: *** [shared/libosmocore/build-target/Makefile] Error 2 -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Error-any-can-help-me-please-tp4… Sent from the baseband-devel mailing list archive at Nabble.com.

1 0

Multislot transmit power - possible to reduce it? (plain text)
by Steve Harrison 04 Nov '13

04 Nov '13

Sorry, forgot to tick the "plain text mode" box on my previous mail... Hi all, In the "EMI" application's main.c is an interesting comment: /* hack: because we cannot control power of multiple burst, * we just force power to 1w, as it is fixed in dsp_extcode If I understand this correctly, the 'C54 code in src/target/firmware/calypso/dsp_extcode.c sets the transmit power to maximum (1W) for all multi-slot transmissions. Would it be possible to fix the multislot transmit power (for the TRX app as well as EMI) at some lower value instead (e.g. 100mW) by modifying dsp_extcode.c? Three reasons: 1. Play nicely with "other users" of the GSM band, by transmitting the same as a "proper" picocell, 2. not draw such a high current from the phone's tiny battery, and 3. avoid overheating the phone's RF power amp and other circuitry - I left my S-E J100 transmitting for about 5 minutes, then noticed that the LCD display was starting to "white out" with the heat! I've achieved a similar result by a hardware modification (added a resistor to reduce the power-control voltage going into the PA), but it's a brutal process - requires prying open a screening can and soldering an 0402 resistor, then trying to get the screening can lid to go back without too much deformation. A software mod would be much more elegant, but I don't know C54 DSP code. Sylvain? thanks, Steve

2 1

COMP128v23
by Kevin Redon 04 Nov '13

04 Nov '13

I tested the reserved COMP128v23 code from www.hackingprojects.net the values in the python file match the ones outputed by the sysmoSIM-GR1 (which also supports COMP128 v2 and v3) so I implemented it in C, and added it to libosmocore I then checked the output from osmo-auc-gen again the values provided also the python code and all values matched Here are te patched WARNING: I also renamed COMP128 to COMP128v1, but don't know if this breaks any compatibility with other projects kevin

4 6

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel November 2013