baseband-devel January 2011

baseband-devel@lists.osmocom.org

71 participants
98 discussions

[PATCH] Two minor patches for the firmware
by Holger Freyther 02 Feb '11

02 Feb '11

Hi laf0rge, I was building the firmware with a GCC 4.5.2 created by Steve-m's script and had to include limits.h for UINT_MAX. While reading the code I stumbled across a typo... I think the patches can be picked to master as well. holger

2 3

SIMtrace issues
by tsaitgaist 02 Feb '11

02 Feb '11

hi, I'll be listing some issues I found in SIMtrace. This is to warn future users. I don't have time now, but I intend to work on this project in 1 or 2 weeks and correct these bugs. 1. when starting host program simtrace, the firmware will first return ATR. This is an error if simtrace is started after the card has been reseted. The program should use the state of the reset and vcc lines to know the state. 2. when using a usb hub, having a lot of USB traffic, or poor USB signal quality (I don't know exactly), bulk read timeouts can occur in host program simtrace/at91sam7/host/main.c line 230: rc = usb_bulk_read(udev, SIMTRACE_IN_EP, buf, sizeof(buf), 100000); rc is -110 (REQUEST_TIMEOUT). I increased the timeout (100000) so to have less errors (but they still occur), and I ignore this error instead of exiting (tracing still works). 3. it seems simtrace can loose track of the I/O stream after some traffic. see pcsc_apdu.log to see the original, and simtrace_apdu.log for the captured traffic. in the end, simtrace misses: APDU: A0 C0 00 00 0F and does a wrong following APDU parsing The problem occurs when using a OmniKey CardMan 5321 and Alcor Micro AU9520. Thus the reader should not be the origin. Also, if only the command where the error occurs is sent, no bytes are skipped. But another error occurs (see next bug) 4. when executing only the last commands, then it is wrongly interpreted (as ATR), but no bytes are skipped ATR (12): 3b 0a 41 00 3f 43 00 01 50 29 01 02 ATR (66): a0 a4 00 00 02 a4 7f 20 9f 17 a0 a4 00 00 02 a4 6f ad 9f 0f a0 c0 00 00 0f c0 00 00 00 03 6f ad 04 00 04 f0 44 01 02 00 00 90 00 a0 b0 00 00 03 b0 00 00 00 90 00 3b 0a 41 00 3f 43 00 01 50 29 01 02 I already wrote a SIM traffic parser for the PC before simtrace appeared. I used a logic analyzer to record the traffic. I will integrate the ATR and APDU parsing/checking into the simtrace firmware. Wrong recorded traffic will be discarded instead of affecting the rest of the parsing. thanks, kevin

3 3

osmocomSIM
by tsaitgaist 31 Jan '11

31 Jan '11

Hi, how about opening the sub-project osmocomSIM ? This could include: - SIMtrace from Harald - SAP server from Andreas - SIM on javacard from Sébastien - future software/virtual SIM which could use SAP server - speaking about A38, Ki, SIM features, ... kevin

2 2

What I am doing wrong? G2
by Панфилов Дмитрий 31 Jan '11

31 Jan '11

Hi! So, I decide to play with my G2 SciPhone (My phone has configuration as follows: 512Mb (64MB) NAND + 32MB RAM) But I could not run U-Boot... The first step seems to be good. I run Osmocon and download "loader" to the phone. I got "Running on mt62xx in environment mtkram HW_CODE = 0x6235" message. After executing $ ./osmoload memload 0x500000 u-boot.bin I can see progress and successfull download of u-boot.bin First of all I tried to use u-boot from here http://downloads.qi-hardware.com/people/marcin/g2_uboot.bin (http://downloads.qi-hardware.com/people/marcin/g2_uboot.bin) Executing $ ./osmoload jump 0x500000 leads to... nothing. I can see black screen. That's all. Also I compilled u-boot from git using toolchain kindly given by Andrew :-) $ ./osmoload jump 0x500000 leads to gray screen after flashing white for a moment. It looks like wrong LCD controller or driver. So... The simple question. What I am doing wrong? :)

1 0

[PATCH 2/2] typo: Fix typo, transform reqyests to requests.
by Holger Hans Peter Freyther 31 Jan '11

31 Jan '11

--- firmware/src/pcd/main_dumbreader.c | 2 +- firmware/src/pcd/main_hid.c | 2 +- firmware/src/pcd/main_presence.c | 2 +- firmware/src/pcd/main_pwm.c | 2 +- firmware/src/pcd/main_usb.c | 2 +- firmware/src/picc/main_openpicc.c | 2 +- firmware/src/simtrace/main_simtrace.c | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/firmware/src/pcd/main_dumbreader.c b/firmware/src/pcd/main_dumbreader.c index 62695f0..9c8dd13 100644 --- a/firmware/src/pcd/main_dumbreader.c +++ b/firmware/src/pcd/main_dumbreader.c @@ -88,7 +88,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); rc632_unthrottle(); diff --git a/firmware/src/pcd/main_hid.c b/firmware/src/pcd/main_hid.c index 9735c3d..c9d8fd1 100644 --- a/firmware/src/pcd/main_hid.c +++ b/firmware/src/pcd/main_hid.c @@ -50,7 +50,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); /* try unthrottling sources since we now are [more] likely to diff --git a/firmware/src/pcd/main_presence.c b/firmware/src/pcd/main_presence.c index f61878f..4ead264 100644 --- a/firmware/src/pcd/main_presence.c +++ b/firmware/src/pcd/main_presence.c @@ -157,7 +157,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); rc632_unthrottle(); } diff --git a/firmware/src/pcd/main_pwm.c b/firmware/src/pcd/main_pwm.c index 7db6b72..50fd363 100644 --- a/firmware/src/pcd/main_pwm.c +++ b/firmware/src/pcd/main_pwm.c @@ -262,7 +262,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); /* try unthrottling sources since we now are [more] likely to diff --git a/firmware/src/pcd/main_usb.c b/firmware/src/pcd/main_usb.c index fcd3306..7892e77 100644 --- a/firmware/src/pcd/main_usb.c +++ b/firmware/src/pcd/main_usb.c @@ -35,7 +35,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); /* try unthrottling sources since we now are [more] likely to diff --git a/firmware/src/picc/main_openpicc.c b/firmware/src/picc/main_openpicc.c index 74700f8..93ca4b6 100644 --- a/firmware/src/picc/main_openpicc.c +++ b/firmware/src/picc/main_openpicc.c @@ -251,7 +251,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); udp_unthrottle(); diff --git a/firmware/src/simtrace/main_simtrace.c b/firmware/src/simtrace/main_simtrace.c index 5e4302e..740d35d 100644 --- a/firmware/src/simtrace/main_simtrace.c +++ b/firmware/src/simtrace/main_simtrace.c @@ -95,7 +95,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); udp_unthrottle(); -- 1.7.3.5 --------------090305060903020708070409--

1 0

[PATCH 1/2] vsprintf.c: Fix compilation by including limits.h
by Holger Hans Peter Freyther 31 Jan '11

31 Jan '11

The INT_MAX define was not known to this code with a GCC 4.5.2/binutils 2.21/newlib 1.19.0 toolchain as build for osmocomBB. Include limits.h to fix that. --- firmware/lib/vsprintf.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/firmware/lib/vsprintf.c b/firmware/lib/vsprintf.c index 5da7c02..799eb78 100644 --- a/firmware/lib/vsprintf.c +++ b/firmware/lib/vsprintf.c @@ -17,6 +17,7 @@ */ #include <stdarg.h> +#include <limits.h> #include <sys/types.h> #include <string.h> #include <asm/ctype.h> -- 1.7.3.5 --------------090305060903020708070409 Content-Type: text/x-patch; name="0002-typo-Fix-typo-transform-reqyests-to-requests.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0="0002-typo-Fix-typo-transform-reqyests-to-requests.patch"

1 0

Reading / sending SMS
by Bogdan Alecu 31 Jan '11

31 Jan '11

Hello, Has anyone managed to read (receive) or to send an SMS to Osmocom phone? I haven't found any vty command that would allow this. Also if I send an SMS to Osmocom the phone starts a location update every 1 minute or so and on the phone that sent the message I get the non-delivery report. Could someone give me some tips on how to send/receive SMS?

2 1

track ticket
by tsaitgaist 31 Jan '11

31 Jan '11

Hi, Could it be possible to enable the ticket system in trac ? It could be used to add suggestions/bugs/todo/..., avoid overloading the mailing list, and keep trac of them. For example, how about changing the mobile welcome message from: Welcome to the OpenBSC Control interface to: Welcome to the osmocom Control interface it makes more sense when using osmocomBB. thanks, kevin

4 4

Re: Channel info
by Bogdan Alecu 31 Jan '11

31 Jan '11

When I look in the output of the mobile app I see that IMSI paging goes almos up to 50%. It's almost like for every TMSI I get below a IMSI paging. That's why I asked from the beginning because I get a lot of IMSI there.

1 0

Re: Channel info
by Bogdan Alecu 31 Jan '11

31 Jan '11

2 2

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel January 2011