baseband-devel March 2012

baseband-devel@lists.osmocom.org

36 participants
44 discussions

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.

13 years

Reliablility problem in current git?

by Tim Ehlers

Hi, I have a git clone from 23.01.2012 and a current git clone. When I compile both and use the mobile appliation, I have a strange problem in the current code. Very often I can't send USSD codes (and maybe also can't communicate in other ways; USSD is the costless way to check whether I am connected or not). Ok, this is what I do: I send "service 1 *#21#", wait the answer and the string "% On Network, normal service: Germany, O2". Then send it again and so on. With the old code, I reliable get the answer e.g. "% Status: deactivated". With the new code, I very often (sometime already when trying first time) get nothing back and after some seconds only "% Service connection terminated.". Can someone confirm this behavior? Thanks Tim

13 years, 2 months

Re: Recording / Re: Regular Osmocom meeting in Berlin?

by Katrin Verclas

It was my understanding from your suggestion that there would be presentations and discussions after those presentations at the meetings, making this not just having a beer with friends but more formal affairs. That would be useful for people elsewhere to see, given that this is a global community. Not sure what German law has to do with putting online or streaming such presentations. Cameras off when it comes to the informal part and beer time.. Love this list otherwise. And will come to Berlin this summer so may attend one or two, regardless :) Cheers from New York. K ------Original Message------ From: Harald Welte To: Katrin Verclas Cc: Holger Hans Peter Freyther Cc: Akib Sayyed Cc: baseband-devel(a)lists.osmocom.org Cc: openbsc(a)lists.osmocom.org Subject: Recording / Re: Regular Osmocom meeting in Berlin? Sent: Mar 31, 2012 8:01 AM Hi Katrin, On Fri, Mar 30, 2012 at 07:17:17PM +0000, Katrin Verclas wrote: > Could not disagree more. We live-stream local events all the time with > a very unobtrusive webcam/ustream and it bothers no one who is there > but benefits all who are not. And I couldn't disagree more with you. The mere existance of the two words 'camera' and 'unobtrusive' in one sentence are a contradiction in terms. If I want to meet with a small group of people and informally discuss technical topic, than that is _very_ different from being live streamed to an unknonwn number of people, any of which could make recordings and I would have to very carefully think about each and every word that I'm saying. That's not a particularly relaxed environment and would kill all the fun there is in having the meeting in the first place. Legally, In Germany this corresponds to "not publicly spoken word" (nicht oeffentlich gesprochenes Wort). It is punishable under law to record or broadcast that. (Clause 201 of German criminal code). 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) Sent via mobile. Hence, short.

13 years, 3 months

how to debug the firmware apps

by Chengcheng Gou

Hello I want to write an app in the form of Firmware, and don`t know how to debug it effectively! anyone has good suggestions, please? Thanks!

13 years, 3 months

Re: Regular Osmocom meeting in Berlin?

by Katrin Verclas

Could not disagree more. We live-stream local events all the time with a very unobtrusive webcam/ustream and it bothers no one who is there but benefits all who are not. Best, Katrin ------Original Message------ From: Holger Hans Peter Freyther Sender: baseband-devel-bounces(a)lists.osmocom.org To: Akib Sayyed Cc: baseband-devel(a)lists.osmocom.org Cc: openbsc(a)lists.osmocom.org Subject: Re: Regular Osmocom meeting in Berlin? Sent: Mar 30, 2012 3:13 PM On 03/30/2012 07:27 PM, Akib Sayyed wrote: > even i am in.people who cannot participate please make some > arrangement for them like live streaming and chat support. > <http://www.ustream.tv/ support free live streaming> Hi, I don't think this is a good idea. It kills the local atmosphere without having any real benefit. Every decision/code and most likely slides will be public anyway. z. Sent via mobile. Hence, short.

13 years, 3 months

Older releases OsmocomBB

by ondra2000＠centrum.cz

Hi all, please how can I download some older release of osmocombb source?I have compiled osmocombb source about 3 months ago and everything was ok...now I downloaded using git some new version and compile it and my phone repeatedly register/unregister with network. Sometimes if can call to this phone but I can't send SMS....So I want compile some older version of source code which worked for me. Thanks BR Ondrej

13 years, 3 months

Regular Osmocom meeting in Berlin?

by Harald Welte

Hi all, I was pondering to start a regular Osmocom meeting (monthly or bi-weekly) in Berlin. The idea would be not only to converge the existing developers in Berlin (zecke, roh, prom, tobias, peter, kevin, myself, ...) but to also try to share some knowledge and excitement with other interested hackers in the wider community. A split format for the event might make sense: Have a more or less organized 45min talk about one particular topic + 15min discussion and then switch to an informal meeting style without any particular topic or moderator. For the first half there is a long list of topics intended at informing people about the status and capabilities of the respective projects: OsmocomBB, OsmoTETRA, OsmoGMR, SIMtrace, etc. Regarding the venue, I would suggest to hold it at the Berlin CCC. What do you generally think about this? What day of the week should we be aiming at? Tuesday and Thursday is generally not a good idea, as those are already occupied with other events. If you think it's a good idea, I would request/register the event with the CCC Berlin. 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)

13 years, 3 months

battery and rx-level symbols

by Andreas Eversberg

hi christian, just added a symbol font to display battery level and rx level to layer1. also i added these symbols to rssi. regards, andreas

13 years, 3 months

[PATCH 2/2] layer1/rssi: Adding battery status and rx-level symbol to RSSI.

by Andreas Eversberg

--- src/target/firmware/apps/rssi/main.c | 17 +++++++++++++++-- 1 files changed, 15 insertions(+), 2 deletions(-) diff --git a/src/target/firmware/apps/rssi/main.c b/src/target/firmware/apps/rssi/main.c index a189740..43713db 100644 --- a/src/target/firmware/apps/rssi/main.c +++ b/src/target/firmware/apps/rssi/main.c @@ -50,6 +50,7 @@ #include <osmocom/gsm/rsl.h> #include <osmocom/gsm/protocol/gsm_04_08.h> #include <osmocom/gsm/gsm48_ie.h> +#include <battery/battery.h> enum key_codes key_code = KEY_INV; int key_pressed = 0; @@ -170,6 +171,7 @@ static void print_display(char *text, int *y, int c) static void refresh_display(void) { char text[16]; + int bat = battery_info.battery_percent; fb_clear(); @@ -179,9 +181,20 @@ static void refresh_display(void) fb_setfg(FB_COLOR_BLUE); fb_setfont(FB_FONT_HELVR08); fb_gotoxy(0, 7); - fb_putstr("Osmocom Monitor Tool", -1); - fb_gotoxy(0, 10); + fb_putstr("Osmocom RSSI", -1); + fb_setfg(FB_COLOR_RGB(0xc0, 0xc0, 0x00)); + fb_setfont(FB_FONT_SYMBOLS); + fb_gotoxy(framebuffer->width - 15, 8); + sprintf(text, "@%c%c%cC", (bat >= 30) ? 'B':'A', + (bat >= 60) ? 'B':'A', (bat >= 90) ? 'B':'A'); + fb_putstr(text, framebuffer->width); + fb_gotoxy(0, 8); + sprintf(text, "%c%cE%c%c", (power >= 40) ? 'D':'G', + (power >= 10) ? 'D':'G', (power >= 10) ? 'F':'G', + (power >= 40) ? 'F':'G'); + fb_putstr(text, framebuffer->width); fb_setfg(FB_COLOR_GREEN); + fb_gotoxy(0, 10); fb_boxto(framebuffer->width - 1, 10); } fb_setfg(FB_COLOR_BLACK); -- 1.7.3.4 --------------020300040706040007050809--

13 years, 3 months

[PATCH 1/2] layer1/fb: Adding new font for symbols

by Andreas Eversberg

The first symbols added are special characters to display battery status and receive level. --- src/target/firmware/Makefile | 3 +- src/target/firmware/fb/font.c | 2 + src/target/firmware/fb/symbols.c | 102 +++++++++++++++++++++++++++++++++ src/target/firmware/include/fb/font.h | 1 + 4 files changed, 107 insertions(+), 1 deletions(-) create mode 100644 src/target/firmware/fb/symbols.c diff --git a/src/target/firmware/Makefile b/src/target/firmware/Makefile index 21892a4..a71eef6 100644 --- a/src/target/firmware/Makefile +++ b/src/target/firmware/Makefile @@ -9,7 +9,8 @@ APPLICATIONS?=hello_world compal_dsp_dump layer1 loader chainload rssi # Framebuffer support, board specific drivers # -FB_OBJS=fb/framebuffer.o fb/font.o fb/helvR08.o fb/helvB14.o fb/c64.o +FB_OBJS=fb/framebuffer.o fb/font.o fb/helvR08.o fb/helvB14.o fb/c64.o \ + fb/symbols.o FB_e88_OBJS=$(FB_OBJS) fb/fb_bw8.o fb/fb_st7558.o FB_e99_OBJS=$(FB_OBJS) fb/fb_rgb332.o fb/fb_ssd1783.o diff --git a/src/target/firmware/fb/font.c b/src/target/firmware/fb/font.c index d98096f..18c1bfe 100644 --- a/src/target/firmware/fb/font.c +++ b/src/target/firmware/fb/font.c @@ -32,6 +32,7 @@ extern const struct fb_font font_helvR14; extern const struct fb_font font_helvB14; // extern const struct fb_font font_helvB24; extern const struct fb_font font_c64; +extern const struct fb_font font_symbols; const struct fb_font *fb_fonts[]={ // &font_4x6, @@ -43,6 +44,7 @@ const struct fb_font *fb_fonts[]={ &font_helvB14, // &font_helvB24, &font_c64, + &font_symbols, }; const struct fb_char * diff --git a/src/target/firmware/fb/symbols.c b/src/target/firmware/fb/symbols.c new file mode 100644 index 0000000..5f6c364 --- /dev/null +++ b/src/target/firmware/fb/symbols.c @@ -0,0 +1,102 @@ +#include <fb/font.h> +static const uint8_t font_symbols_data[] = { +/* @ battery - */ + /*0000:*/ 3, 3, 8, 0, 0, /* width and bbox (w,h,x,y) */ + /*0005:*/ 0x60, /* .##..... */ + /*0006:*/ 0x40, /* .#...... */ + /*0007:*/ 0x40, /* .#...... */ + /*0008:*/ 0x40, /* .#...... */ + /*0009:*/ 0x40, /* .#...... */ + /*000a:*/ 0x40, /* .#...... */ + /*000b:*/ 0x40, /* .#...... */ + /*000c:*/ 0x60, /* .##..... */ +/* A battery empty */ + /*000d:*/ 3, 3, 8, 0, 0, /* width and bbox (w,h,x,y) */ + /*0012:*/ 0xe0, /* ###..... */ + /*0013:*/ 0x00, /* ........ */ + /*0014:*/ 0x00, /* ........ */ + /*0015:*/ 0x00, /* ........ */ + /*0016:*/ 0x00, /* ........ */ + /*0017:*/ 0x00, /* ........ */ + /*0018:*/ 0x00, /* ........ */ + /*0019:*/ 0xe0, /* ###..... */ +/* B battery full */ + /*001a:*/ 3, 3, 8, 0, 0, /* width and bbox (w,h,x,y) */ + /*001f:*/ 0xe0, /* ###..... */ + /*0020:*/ 0x00, /* ........ */ + /*0021:*/ 0xc0, /* ##...... */ + /*0022:*/ 0xc0, /* ##...... */ + /*0023:*/ 0xc0, /* ##...... */ + /*0024:*/ 0xc0, /* ##...... */ + /*0025:*/ 0x00, /* ........ */ + /*0026:*/ 0xe0, /* ###..... */ +/* C battery + */ + /*0027:*/ 3, 3, 8, 0, 0, /* width and bbox (w,h,x,y) */ + /*002c:*/ 0x80, /* #....... */ + /*002d:*/ 0x80, /* #....... */ + /*002e:*/ 0xc0, /* ##...... */ + /*002f:*/ 0xc0, /* ##...... */ + /*0030:*/ 0xc0, /* ##...... */ + /*0031:*/ 0xc0, /* ##...... */ + /*0032:*/ 0x80, /* #....... */ + /*0033:*/ 0x80, /* #....... */ +/* D radiation left */ + /*0034:*/ 3, 3, 8, 0, 0, /* width and bbox (w,h,x,y) */ + /*0039:*/ 0x20, /* ..#..... */ + /*003a:*/ 0x40, /* .#...... */ + /*003b:*/ 0x20, /* ..#..... */ + /*003c:*/ 0x00, /* ........ */ + /*003d:*/ 0x00, /* ........ */ + /*003e:*/ 0x00, /* ........ */ + /*003f:*/ 0x00, /* ........ */ + /*0040:*/ 0x00, /* ........ */ +/* E tower */ + /*0041:*/ 5, 5, 8, 0, 0, /* width and bbox (w,h,x,y) */ + /*0046:*/ 0x20, /* ..#..... */ + /*0047:*/ 0x50, /* .#.#.... */ + /*0048:*/ 0x20, /* ..#..... */ + /*0049:*/ 0x20, /* ..#..... */ + /*004a:*/ 0x50, /* .#.#.... */ + /*004b:*/ 0x50, /* .#.#.... */ + /*004c:*/ 0x88, /* #...#... */ + /*004d:*/ 0xf8, /* #####... */ +/* F radiation right */ + /*004e:*/ 3, 3, 8, 0, 0, /* width and bbox (w,h,x,y) */ + /*0053:*/ 0x80, /* #....... */ + /*0054:*/ 0x40, /* .#...... */ + /*0055:*/ 0x80, /* #....... */ + /*0056:*/ 0x00, /* ........ */ + /*0057:*/ 0x00, /* ........ */ + /*0058:*/ 0x00, /* ........ */ + /*0059:*/ 0x00, /* ........ */ + /*005a:*/ 0x00, /* ........ */ +/* G no radiation */ + /*005b:*/ 3, 3, 8, 0, 0, /* width and bbox (w,h,x,y) */ + /*005c:*/ 0x00, /* ........ */ + /*005d:*/ 0x00, /* ........ */ + /*005e:*/ 0x00, /* ........ */ + /*005f:*/ 0x00, /* ........ */ + /*0060:*/ 0x00, /* ........ */ + /*0061:*/ 0x00, /* ........ */ + /*0062:*/ 0x00, /* ........ */ + /*0063:*/ 0x00, /* ........ */ +}; +static const uint16_t font_symbols_offsets[] = { + 0x0000 /* '@' */, + 0x000d /* 'A' */, + 0x001a /* 'B' */, + 0x0027 /* 'C' */, + 0x0034 /* 'D' */, + 0x0041 /* 'E' */, + 0x004e /* 'F' */, + 0x005b /* 'G' */, +}; +const struct fb_font font_symbols = { + .height = 8, + .ascent = 8, + .firstchar = 64, /* '@' */ + .lastchar = 71, + .chardata = font_symbols_data, + .charoffs = font_symbols_offsets, +}; + diff --git a/src/target/firmware/include/fb/font.h b/src/target/firmware/include/fb/font.h index 40a6974..9dee8ff 100644 --- a/src/target/firmware/include/fb/font.h +++ b/src/target/firmware/include/fb/font.h @@ -70,6 +70,7 @@ enum fb_font_id { FB_FONT_HELVB14, // FB_FONT_HELVB24, FB_FONT_C64, + FB_FONT_SYMBOLS, }; extern const struct fb_font *fb_fonts[]; // note: has to match fb_font_id enum! -- 1.7.3.4 --------------020300040706040007050809 Content-Type: text/x-patch; name="0002-layer1-rssi-Adding-battery-status-and-rx-level-symbo.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0="0002-layer1-rssi-Adding-battery-status-and-rx-level-symbo.pa"; filename*1="tch"

13 years, 3 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel March 2012