- baseband-devel - lists.osmocom.org

[PATCH 2/2] layer1/rssi: Adding battery status and rx-level symbol to RSSI.
by Andreas Eversberg 30 Mar '12

30 Mar '12

--- 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--

1 0

[PATCH 1/2] layer1/fb: Adding new font for symbols
by Andreas Eversberg 30 Mar '12

30 Mar '12

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"

1 0

Please Stream it LIVE ---> Re: Regular Osmocom meeting in Berlin?
by Martin O'Shield 30 Mar '12

30 Mar '12

Hello All, "People who cannot participate please make some arrangement for them like live streaming and chat support. <http://www.ustream.tv/ support free live streaming> " I'd like to vote for this point as I wont be able to attend either but love to be there. Sincerely, Martin On Friday, March 30, 2012, Akib Sayyed <akibsayyed(a)gmail.com> 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> > > On Fri, Mar 30, 2012 at 5:07 PM, Sergio 'shadown' Alvarez > <shadown(a)gmail.com> wrote: >> The idea sounds great to me too. >> >> On Mar 30, 2012, at 12:06 PM, Tobias Engel wrote: >> >>> On 29.03.2012 21:41, Peter Stuge wrote: >>>> Harald Welte wrote: >>>>> I was pondering to start a regular Osmocom meeting (monthly or >>>>> bi-weekly) in Berlin. >>>> .. >>>>> What do you generally think about this? >>>> >>>> I say go for it. Bi-weekly sounds good. >>> >>> I would say monthly is more realistic. But I'm also fine with bi-weekly. >> >> Bi-weekly would give more chances to people who travel a lot, to at least make it to it once a month. >> >>>>> What day of the week should we be aiming at? >>>> >>>> I like Wednesday. >>> >>> Me too. >>> >>> -Tobias >>> >> >> > > > > -- > Akib Sayyed > Matrix-Shell > akibsayyed(a)gmail.com > akibsayyed(a)matrixshell.com > Mob:- +91-966-514-2243 > >

1 0

Re: Regular Osmocom meeting in Berlin?
by Zsombor 30 Mar '12

30 Mar '12

Can you record the video about the presentations and upload to some video sharing site ? I'm certain, that there would be some interest watching it :) Thanks, Zsombor On 2012.03.30. 13:33, "Tobias Engel" <t-openbsc(a)tobias.org> wrote: On 29.03.2012 21:41, Peter Stuge wrote: > Harald Welte wrote: >> I was pondering to start a regular ... I would say monthly is more realistic. But I'm also fine with bi-weekly. >> What day of the week should we be aiming at? > > I like Wednesday. Me too. -Tobias

1 0

DOS in Cellular network
by Chengcheng Gou 30 Mar '12

30 Mar '12

Hello I want to know how to implement a real DOS in the real cellular network using RACH Flood.As you know, using OsmocomBB ,you can only send flood to one ARFCN at one time, so the phone can seaching for another ARFCN. So I think the RACH Flood is less effective in practice, how about it? and if not,a better suggestion on DOS in Cellular network? Thanks!

5 4

Syntax error - LIBOSMOCORE
by alfonso caponi 29 Mar '12

29 Mar '12

Hi list, sorry for this tedious question. I've already read a previous post about my problem but has not been useful ( http://lists.osmocom.org/pipermail/baseband-devel/2011-October/002351.html) I've this error after the make: checking for ranlib... ranlib ./configure: line 3508: syntax error near unexpected token `LIBOSMOCORE,' ./configure: line 3508: `PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore)' make: *** [host/layer23/Makefile] Error 2 My settings with the last versions of sources: - Linux ubuntu 2.6.38-11-generic-pae #50-Ubuntu SMP Mon Sep 12 22:21:04 UTC 2011 i686 i686 i386 GNU/Linux - PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/root/cell_logger/tool-chain/install/bin - arm-elf-gcc -v (installed with http://bb.osmocom.org/trac/wiki/GnuArmToolchain) Using built-in specs. Target: arm-elf Configured with: ./configure elf Thread model: single gcc version 4.2.3 - Makefile: # this is the host tuple of your cross-toolchain CROSS_HOST ?= $(shell which arm-elf-gcc >/dev/null 2>&1 && echo arm-elf || echo arm-none-eabi) # this is the prefix of your cross-toolchain programs CROSS_TOOL_PREFIX=$(CROSS_HOST)- Any tips? :) Thank you very much, AL

3 3

Call for participation LSM/RMLL
by Mathias Coinchon 29 Mar '12

29 Mar '12

Dear Osmocom community, This email to inform you that the call for participation for the next Libre Software Meeting (LSM or RMLL: Rencontres Mondiales du Logiciel Libre) ends on 31st March: http://2012.rmll.info/en/participate/call-for-papers This edition will take place in Geneva from 7th to 12th July 2012 (7-8 general public days, 9-12 theme focused, professional). It would be of great interest for the communities to learn about the Osmocom projects in presentations or workshop. Real world applications would be interesting too. So please don't hesitate to directly submit. Don't hesitate also to contact me for more information. Mathias Coinchon

1 0

RSSI Firmware of OpenMoko GTA02
by saad_aol 28 Mar '12

28 Mar '12

Hi; I am trying to run rssi.highram.bin on gta02(openmoko) following this [1] gta02 is running SHR-lite distro So far I have 1. cross-compiled rssi firmware using arm-elf- toolchain 2. cross-compiled osmocon for phone using arm-angstrom-linux-gnueabi- [2] make -e CROSS_TOOL_PREFIX=arm-angstrom-linux-gnueabi- HOST_CONFARGS="--host=armv4t-angstrom-linux-gnueabi" 3. Make sure that nothing else is using /dev/ttySAC0 4. loaded rssi firmware on gta02 by running on gta02 ./osmocon -i 13 -m romload -p /dev/ttySAC0 rssi.highram.bin Firmware loads succesfully when I toggle power of baseband using echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on && echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on but it scans only ARFCN 1 :< SIM is present but since /dev/ttySAC0 is only claimed by osmocon, I dont think it can be used by ogsmd [1] http://bb.osmocom.org/trac/wiki/OpenMoko http://bb.osmocom.org/trac/wiki/OpenMoko [2] http://wiki.openmoko.org/wiki/Toolchain http://wiki.openmoko.org/wiki/Toolchain My QUESTIONS are: ================= 1. How can I Scan all ARFCN? 2. Can we use /dev/ttySAC0 for gsm & other things after the firmware is loaded on baseband? LOG FILE: http://baseband-devel.722152.n3.nabble.com/file/n3863628/log log -- View this message in context: http://baseband-devel.722152.n3.nabble.com/RSSI-Firmware-of-OpenMoko-GTA02-… Sent from the baseband-devel mailing list archive at Nabble.com.

1 0

Re: baseband-devel Digest, Vol 26, Issue 15
by Akib Sayyed 27 Mar '12

27 Mar '12

i am assuming that you are using one osmocom phone setup and one normal phone. try to do as follows take 3 osmocom phones then try dos with 2 phones and put sim in 3rd and lock to same arfcn and then see what happens. cheeers On Tue, Mar 27, 2012 at 3:30 PM, <baseband-devel-request(a)lists.osmocom.org> wrote: > Send baseband-devel mailing list submissions to > baseband-devel(a)lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osmocom.org/mailman/listinfo/baseband-devel > or, via email, send a message with subject or body 'help' to > baseband-devel-request(a)lists.osmocom.org > > You can reach the person managing the list at > baseband-devel-owner(a)lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of baseband-devel digest..." > > Today's Topics: > > 1. about RACH DOS (gcc) > > > ---------- Forwarded message ---------- > From: gcc <gouchengcheng(a)gmail.com> > To: baseband-devel(a)lists.osmocom.org > Cc: > Date: Mon, 26 Mar 2012 23:44:16 -0700 (PDT) > Subject: about RACH DOS > I am a student in a University studying on the security of GSM, recently I > want use osmocomBB to realize the RACH DOS attack mentioned in Dieter > Spaar`s speech. but I meet some difficulty. > > I do as follow: > > continuely sending RACH to a cell,and ignore the GSM48_MT_RR_IMM_ASS > message ,also i lock my phone to the attacked cell,but after some time,the > phone can still call to some phone ,why? > > can anyone help me? > > thanks! > > -- > View this message in context: http://baseband-devel.722152.n3.nabble.com/about-RACH-DOS-tp3860492p3860492… > Sent from the baseband-devel mailing list archive at Nabble.com. > > > > _______________________________________________ > baseband-devel mailing list > baseband-devel(a)lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/baseband-devel > -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

1 0

about RACH DOS
by gcc 27 Mar '12

27 Mar '12

I am a student in a University studying on the security of GSM, recently I want use osmocomBB to realize the RACH DOS attack mentioned in Dieter Spaar`s speech. but I meet some difficulty. I do as follow: continuely sending RACH to a cell,and ignore the GSM48_MT_RR_IMM_ASS message ,also i lock my phone to the attacked cell,but after some time,the phone can still call to some phone ,why? can anyone help me? thanks! -- View this message in context: http://baseband-devel.722152.n3.nabble.com/about-RACH-DOS-tp3860492p3860492… Sent from the baseband-devel mailing list archive at Nabble.com.

1 0