From odongotdan at yahoo.com  Tue Mar 22 22:06:13 2011
From: odongotdan at yahoo.com (odongotdan)
Date: Tue, 22 Mar 2011 15:06:13 -0700 (PDT)
Subject: Linux + u-boot port to MT6235
In-Reply-To: <20101028135643.GE26901@prithivi.gnumonks.org>
References: <20101028135643.GE26901@prithivi.gnumonks.org>
Message-ID: <1300831573690-2717489.post@n3.nabble.com>

Hi,
I have a chinese iphone 4 which operates with this processor ( MT6235 ) and
i would like to upgrade it to other os such as linux, ios, android etc. What
is the extent of that pocibility?

--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Linux-u-boot-port-to-MT6235-tp1786527p2717489.html
Sent from the baseband-devel mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110322/7a0655e6/attachment.htm>

From blassmegod at yahoo.com  Fri Mar  4 08:59:29 2011
From: blassmegod at yahoo.com (burebista)
Date: Fri, 4 Mar 2011 00:59:29 -0800 (PST)
Subject: MT6235/6140 and MT6516?
Message-ID: <587830.76887.qm@web130221.mail.mud.yahoo.com>

Hy, do you have the MT6516 processors datasheet, could you please send it to me too? I tried asking MediaTek and Gigabyte (my pocket pc developer) but they refused me, I'm trying to port Haret to work on a pocket pc with this processor to boot linux. And another question: in the latest linux kernel i saw that the match_type for the MT65xx is there, but this processor is supported by the linux kernel?
Thank You,



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110304/c3b0dab5/attachment.htm>

From laforge at gnumonks.org  Wed Mar  2 09:37:57 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Wed, 2 Mar 2011 10:37:57 +0100
Subject: [PATCH] Re: mobile: config file in /etc/osmocom/osmocom.cfg
In-Reply-To: <4D441144.3000304@defora.org>
References: <20110129061850.GD5546@prithivi.gnumonks.org>
	<4D440E64.5000500@defora.org> <4D441144.3000304@defora.org>
Message-ID: <20110302093757.GM3859@prithivi.gnumonks.org>

Hi khorben,

> It was missing two additional #include.

after some delay, I took the liberty of applying your patch to master,
adding the followign changes:
 * coding style "if(" vs "if ("
 * use .osmocom/bb/mobile.cfg instead of .osmocom
 * use talloc instead of malloc

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From wpatan at gmail.com  Sat Mar 26 06:35:18 2011
From: wpatan at gmail.com (wpatan)
Date: Fri, 25 Mar 2011 23:35:18 -0700 (PDT)
Subject: begginer problem
In-Reply-To: <5411d56b8ae04513087bfdf44f0d368e@auth.se>
References: <AANLkTi=U_LEqVju-o-btpuOR1JP+h7anNPCp3SJ2K_4z@mail.gmail.com>
	<5411d56b8ae04513087bfdf44f0d368e@auth.se>
Message-ID: <1301121318347-2734704.post@n3.nabble.com>

I was able to fix the problem. It seems that the cable is ok but the earphone
jack did not fit properly ( i used a modified headset that will exactly fit
on the phone).
BTW, you can test if your cable is functional by using minicom and shorting
the tx/rx part of the cable... if you see echoes of your keystrokes on
minicom.. then your cable is good.

Tnks!

--
View this message in context: http://baseband-devel.722152.n3.nabble.com/begginer-problem-tp2423389p2734704.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From dario.lombardo at libero.it  Wed Mar  2 10:11:36 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Wed, 02 Mar 2011 11:11:36 +0100
Subject: Fwd: gpsd support
In-Reply-To: <4D662666.4060006@libero.it>
References: <AANLkTikMofb0sE62MgOF5qOWaj3LsCeDajCHoZ8q5LEK@mail.gmail.com>	<AANLkTimdKLUp0U_oq36+KKdBamvQbRBtoZRvuVDVWdvr@mail.gmail.com>	<20110217170842.GH1002@prithivi.gnumonks.org>	<4D637C11.2060307@libero.it>
	<20110222135857.5874.qmail@stuge.se> <4D662666.4060006@libero.it>
Message-ID: <4D6E17D8.4030909@libero.it>

Last (hope definitive) patch for gpsd support that should include every 
suggestion.
Feel free to comment.
Dario.

From dario.lombardo at libero.it  Tue Mar  1 09:18:29 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Tue, 1 Mar 2011 10:18:29 +0100
Subject: [PATCH 2/2] Added cmdline message when gpsd support is not compiled.
Message-ID: <mailman.28.1641743547.42824.baseband-devel@lists.osmocom.org>

---
 src/host/layer23/src/misc/app_cell_log.c |   20 +++++++++++---------
 1 files changed, 11 insertions(+), 9 deletions(-)

diff --git a/src/host/layer23/src/misc/app_cell_log.c b/src/host/layer23/src/misc/app_cell_log.c
index 7030abf..92fc4c0 100644
--- a/src/host/layer23/src/misc/app_cell_log.c
+++ b/src/host/layer23/src/misc/app_cell_log.c
@@ -110,10 +110,8 @@ static int l23_cfg_print_help()
 	printf("  -l --logfile LOGFILE	Logfile for the cell log.\n");
 	printf("  -r --rach RACH	Nr. of RACH bursts to send.\n");
 	printf("  -n --no-rach		Send no rach bursts.\n");
-#ifdef _HAVE_GPSD
 	printf("  -g --gpsd-host HOST	127.0.0.1. gpsd host.\n");
 	printf("  -p --port PORT	2947. gpsd port\n");
-#endif
 	printf("  -f --gps DEVICE	/dev/ttyACM0. GPS serial device.\n");
 	printf("  -b --baud BAUDRAT	The baud rate of the GPS device\n");
 
@@ -132,8 +130,8 @@ static int l23_cfg_handle(int c, const char *optarg)
 	case 'n':
 		RACH_MAX = 0;
 		break;
-#ifdef _HAVE_GPSD
 	case 'g':
+#ifdef _HAVE_GPSD
 		snprintf(g.gpsd_host, ARRAY_SIZE(g.gpsd_host), "%s", optarg);
 		/* force string terminator */
 		g.gpsd_host[ARRAY_SIZE(g.gpsd_host) - 1] = '\0';
@@ -141,15 +139,23 @@ static int l23_cfg_handle(int c, const char *optarg)
 			goto cmd_line_error;
 		g.gps_type = GPS_TYPE_GPSD;
 		LOGP(DGPS, LOGL_INFO, "Using gpsd host %s\n", g.gpsd_host);
+#else
+		printf("Gpsd support not compiled.\n");
+		exit(1);
+#endif
 		break;
 	case 'p':
+#ifdef _HAVE_GPSD
 		snprintf(g.gpsd_port, ARRAY_SIZE(g.gpsd_port), "%s", optarg);
 		/* force string terminator */
 		g.gpsd_port[ARRAY_SIZE(g.gpsd_port) - 1] = '\0';
 		g.gps_type = GPS_TYPE_GPSD;
 		LOGP(DGPS, LOGL_INFO, "Using gpsd port %s\n", g.gpsd_port);
+#else
+		printf("Gpsd support not compiled.\n");
+		exit(1);
+#endif
 		break;
-#endif
 	case 'f':
 		snprintf(g.device, ARRAY_SIZE(g.device), "%s", optarg);
 		/* force string terminator */
@@ -174,11 +180,7 @@ cmd_line_error:
 
 static struct l23_app_info info = {
 	.copyright	= "Copyright (C) 2010 Andreas Eversberg\n",
-	.getopt_string	=
-#ifdef _HAVE_GPSD
-	"g:p:"
-#endif
-	"l:r:nf:b:",
+	.getopt_string	= "g:p:l:r:nf:b:",
 	.cfg_supported	= l23_cfg_supported,
 	.cfg_getopt_opt = l23_getopt_options,
 	.cfg_handle_opt	= l23_cfg_handle,
-- 
1.7.4


--------------000704030406060303040102--



From dario.lombardo at libero.it  Tue Mar  8 15:29:56 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Tue, 08 Mar 2011 16:29:56 +0100
Subject: Fwd: gpsd support
In-Reply-To: <4D6E17D8.4030909@libero.it>
References: <AANLkTikMofb0sE62MgOF5qOWaj3LsCeDajCHoZ8q5LEK@mail.gmail.com>	<AANLkTimdKLUp0U_oq36+KKdBamvQbRBtoZRvuVDVWdvr@mail.gmail.com>	<20110217170842.GH1002@prithivi.gnumonks.org>	<4D637C11.2060307@libero.it>
	<20110222135857.5874.qmail@stuge.se>
	<4D662666.4060006@libero.it> <4D6E17D8.4030909@libero.it>
Message-ID: <4D764B74.7000604@libero.it>

Hi Andreas
Please find attached the last version of the patch for gpsd support that 
incorporates the changes we said.
Let me know if something needs to be changed.
Bye
Dario.

From dario.lombardo at libero.it  Tue Mar  8 15:22:14 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Tue, 8 Mar 2011 16:22:14 +0100
Subject: [PATCH] Added runtime selection of gps device.
Message-ID: <mailman.29.1641743547.42824.baseband-devel@lists.osmocom.org>

---
 src/host/layer23/configure.ac                    |    2 +-
 src/host/layer23/include/osmocom/bb/common/gps.h |   15 ++-
 src/host/layer23/src/common/gps.c                |  116 +++++++++++++--------
 src/host/layer23/src/misc/app_cell_log.c         |   76 ++++++++------
 src/host/layer23/src/misc/cell_log.c             |   28 +++---
 src/host/layer23/src/mobile/vty_interface.c      |   72 +++++++-------
 6 files changed, 177 insertions(+), 132 deletions(-)

diff --git a/src/host/layer23/configure.ac b/src/host/layer23/configure.ac
index e1c718e..05c6d24 100644
--- a/src/host/layer23/configure.ac
+++ b/src/host/layer23/configure.ac
@@ -15,7 +15,7 @@ AC_PROG_RANLIB
 dnl checks for libraries
 PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore)
 PKG_CHECK_MODULES(LIBOSMOVTY, libosmovty)
-AC_CHECK_LIB(gps, gps_open, CFLAGS+=" -D_USE_GPSD" LDFLAGS+=" -lgps",,)
+AC_CHECK_LIB(gps, gps_waiting, CFLAGS+=" -D_HAVE_GPSD" LDFLAGS+=" -lgps",,)
 
 dnl checks for header files
 AC_HEADER_STDC
diff --git a/src/host/layer23/include/osmocom/bb/common/gps.h b/src/host/layer23/include/osmocom/bb/common/gps.h
index b7500db..58c0c53 100644
--- a/src/host/layer23/include/osmocom/bb/common/gps.h
+++ b/src/host/layer23/include/osmocom/bb/common/gps.h
@@ -19,17 +19,24 @@
  *
  */
 
+enum {
+	GPS_TYPE_UNDEF,
+	GPS_TYPE_GPSD,
+	GPS_TYPE_SERIAL
+};
+
 struct osmo_gps {
 	/* GPS device */
 	uint8_t		enable;
+	uint8_t		gps_type;
 
-#ifdef _USE_GPSD
+#ifdef _HAVE_GPSD
 	char		gpsd_host[32];
 	char		gpsd_port[6];
-#else
+#endif
+
 	char		device[32];
 	uint32_t	baud;
-#endif
 
 	/* current data */
 	uint8_t		valid; /* we have a fix */
@@ -37,7 +44,7 @@ struct osmo_gps {
 	double		latitude, longitude;
 };
 
-extern struct osmo_gps gps;
+extern struct osmo_gps g;
 
 int osmo_gps_open(void);
 void osmo_gps_close(void);
diff --git a/src/host/layer23/src/common/gps.c b/src/host/layer23/src/common/gps.c
index 55dd239..07bc460 100644
--- a/src/host/layer23/src/common/gps.c
+++ b/src/host/layer23/src/common/gps.c
@@ -26,8 +26,9 @@
 #include <stdlib.h>
 #include <errno.h>
 #include <time.h>
+#include <stdbool.h>
 
-#ifdef _USE_GPSD
+#ifdef _HAVE_GPSD
 #include <gps.h>
 #endif
 
@@ -37,15 +38,15 @@
 #include <osmocom/bb/common/logging.h>
 #include <osmocom/bb/common/gps.h>
 
-struct osmo_gps gps = {
+struct osmo_gps g = {
 	0,
-#ifdef _USE_GPSD
+	GPS_TYPE_UNDEF,
+#ifdef _HAVE_GPSD
     "localhost",
 	"2947",
-#else
+#endif
 	"/dev/ttyACM0",
 	0,
-#endif
 	0,
 	0,
 	0,0
@@ -53,16 +54,16 @@ struct osmo_gps gps = {
 
 static struct bsc_fd gps_bfd;
 
-#ifdef _USE_GPSD
+#ifdef _HAVE_GPSD
 
 static struct gps_data_t* gdata;
 
-int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what)
+int osmo_gpsd_cb(struct bsc_fd *bfd, unsigned int what)
 {
 	struct tm *tm;
 	unsigned diff = 0;
 
-	gps.valid = 0;
+	g.valid = 0;
 
 	/* gps is offline */
 	if (gdata->online)
@@ -78,21 +79,21 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what)
 
 	/* data are valid */
 	if (gdata->set & LATLON_SET) {
-		gps.valid = 1;
-		gps.gmt = gdata->fix.time;
-		tm = localtime(&gps.gmt);
-		diff = time(NULL) - gps.gmt;
-		gps.latitude = gdata->fix.latitude;
-		gps.longitude = gdata->fix.longitude;
+		g.valid = 1;
+		g.gmt = gdata->fix.time;
+		tm = localtime(&g.gmt);
+		diff = time(NULL) - g.gmt;
+		g.latitude = gdata->fix.latitude;
+		g.longitude = gdata->fix.longitude;
 
 		LOGP(DGPS, LOGL_INFO, " time=%02d:%02d:%02d %04d-%02d-%02d, "
 			"diff-to-host=%d, latitude=%do%.4f, longitude=%do%.4f\n",
 			tm->tm_hour, tm->tm_min, tm->tm_sec, tm->tm_year + 1900,
 			tm->tm_mday, tm->tm_mon + 1, diff,
-			(int)gps.latitude,
-			(gps.latitude - ((int)gps.latitude)) * 60.0,
-			(int)gps.longitude,
-			(gps.longitude - ((int)gps.longitude)) * 60.0);
+			(int)g.latitude,
+			(g.latitude - ((int)g.latitude)) * 60.0,
+			(int)g.longitude,
+			(g.longitude - ((int)g.longitude)) * 60.0);
 	}
 
 	return 0;
@@ -102,15 +103,15 @@ gps_not_ready:
 	return -1;
 }
 
-int osmo_gps_open(void)
+int osmo_gpsd_open(void)
 {
-	LOGP(DGPS, LOGL_INFO, "Connecting to gpsd at '%s:%s'\n", gps.gpsd_host, gps.gpsd_port);
+	LOGP(DGPS, LOGL_INFO, "Connecting to gpsd at '%s:%s'\n", g.gpsd_host, g.gpsd_port);
 
 	gps_bfd.data = NULL;
 	gps_bfd.when = BSC_FD_READ;
-	gps_bfd.cb = osmo_gps_cb;
+	gps_bfd.cb = osmo_gpsd_cb;
 
-	gdata = gps_open(gps.gpsd_host, gps.gpsd_port);
+	gdata = gps_open(g.gpsd_host, g.gpsd_port);
 	if (gdata == NULL) {
 		LOGP(DGPS, LOGL_ERROR, "Can't connect to gpsd\n");
 		return -1;
@@ -129,7 +130,7 @@ int osmo_gps_open(void)
 	return 0;
 }
 
-void osmo_gps_close(void)
+void osmo_gpsd_close(void)
 {
 	if (gps_bfd.fd <= 0)
 		return;
@@ -142,11 +143,11 @@ void osmo_gps_close(void)
 	gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */
 }
 
-#else
+#endif
 
 static struct termios gps_termios, gps_old_termios;
 
-static int osmo_gps_line(char *line)
+static int osmo_serialgps_line(char *line)
 {
 	time_t gps_now, host_now;
 	struct tm *tm;
@@ -164,10 +165,10 @@ static int osmo_gps_line(char *line)
 	/* valid position */
 	if (line[36] != 'A') {
 		LOGP(DGPS, LOGL_INFO, "%s (invalid)\n", line);
-		gps.valid = 0;
+		g.valid = 0;
 		return 0;
 	}
-	gps.valid = 1;
+	g.valid = 1;
 
 	/* time stamp */
 	gps_now = line[30] - '0';
@@ -185,7 +186,7 @@ static int osmo_gps_line(char *line)
 		diff -= 86400;
 	/* apply the "date" part to the GPS time */
 	gps_now = host_now - diff;
-	gps.gmt = gps_now;
+	g.gmt = gps_now;
 	tm = localtime(&gps_now);
 
 	/* position */
@@ -199,7 +200,7 @@ static int osmo_gps_line(char *line)
 	latitude += (double)(line[8] - '0') / 600000.0;
 	if (line[10] == 'S')
 		latitude = 0.0 - latitude;
-	gps.latitude = latitude;
+	g.latitude = latitude;
 	longitude = (double)(line[12] - '0') * 100.0;
 	longitude += (double)(line[13] - '0') * 10.0;
 	longitude += (double)(line[14] - '0');
@@ -211,17 +212,17 @@ static int osmo_gps_line(char *line)
 	longitude += (double)(line[21] - '0') / 600000.0;
 	if (line[23] == 'W')
 		longitude = 360.0 - longitude;
-	gps.longitude = longitude;
+	g.longitude = longitude;
 	
 	LOGP(DGPS, LOGL_DEBUG, "%s\n", line);
 	LOGP(DGPS, LOGL_INFO, " time=%02d:%02d:%02d %04d-%02d-%02d, "
 		"diff-to-host=%d, latitude=%do%.4f, longitude=%do%.4f\n",
 		tm->tm_hour, tm->tm_min, tm->tm_sec, tm->tm_year + 1900,
 		tm->tm_mday, tm->tm_mon + 1, diff,
-		(int)gps.latitude,
-		(gps.latitude - ((int)gps.latitude)) * 60.0,
-		(int)gps.longitude,
-		(gps.longitude - ((int)gps.longitude)) * 60.0);
+		(int)g.latitude,
+		(g.latitude - ((int)g.latitude)) * 60.0,
+		(int)g.longitude,
+		(g.longitude - ((int)g.longitude)) * 60.0);
 	return 0;
 }
 
@@ -241,7 +242,7 @@ static int nmea_checksum(char *line)
 	return (strtoul(line+1, NULL, 16) == checksum);
 }
 
-int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what)
+int osmo_serialgps_cb(struct bsc_fd *bfd, unsigned int what)
 {
 	char buff[128];
 	static char line[128];
@@ -265,7 +266,7 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what)
 			if (!nmea_checksum(line))
 				fprintf(stderr, "NMEA checksum error\n");
 			else
-				osmo_gps_line(line);
+				osmo_serialgps_line(line);
 			continue;
 		}
 		line[lpos++] = buff[i++];
@@ -276,23 +277,23 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what)
 	return 0;
 }
 
-int osmo_gps_open(void)
+int osmo_serialgps_open(void)
 {
 	int baud = 0;
 
 	if (gps_bfd.fd > 0)
 		return 0;
 
-	LOGP(DGPS, LOGL_INFO, "Open GPS device '%s'\n", gps.device);
+	LOGP(DGPS, LOGL_INFO, "Open GPS device '%s'\n", g.device);
 
 	gps_bfd.data = NULL;
 	gps_bfd.when = BSC_FD_READ;
-	gps_bfd.cb = osmo_gps_cb;
-	gps_bfd.fd = open(gps.device, O_RDONLY);
+	gps_bfd.cb = osmo_serialgps_cb;
+	gps_bfd.fd = open(g.device, O_RDONLY);
 	if (gps_bfd.fd < 0)
 		return gps_bfd.fd;
 
-	switch (gps.baud) {
+	switch (g.baud) {
 	case   4800:
 		baud = B4800;      break;
 	case   9600:
@@ -327,7 +328,7 @@ int osmo_gps_open(void)
 	return 0;
 }
 
-void osmo_gps_close(void)
+void osmo_serialgps_close(void)
 {
 	if (gps_bfd.fd <= 0)
 		return;
@@ -343,11 +344,38 @@ void osmo_gps_close(void)
 	gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */
 }
 
-#endif
-
 void osmo_gps_init(void)
 {
 	memset(&gps_bfd, 0, sizeof(gps_bfd));
 }
 
+int osmo_gps_open(void)
+{
+	switch (g.gps_type) {
+#ifdef _HAVE_GPSD
+		case GPS_TYPE_GPSD:
+			return osmo_gpsd_open();
+#endif
+		case GPS_TYPE_SERIAL:
+			return osmo_serialgps_open();
+
+		default:
+			return 0;
+	}
+}
+
+void osmo_gps_close(void)
+{
+	switch (g.gps_type) {
+#ifdef _HAVE_GPSD
+		case GPS_TYPE_GPSD:
+			return osmo_gpsd_close();
+#endif
+		case GPS_TYPE_SERIAL:
+			return osmo_serialgps_close();
+
+		default:
+			return;
+	}
+}
 
diff --git a/src/host/layer23/src/misc/app_cell_log.c b/src/host/layer23/src/misc/app_cell_log.c
index 7a2c67a..fdecc63 100644
--- a/src/host/layer23/src/misc/app_cell_log.c
+++ b/src/host/layer23/src/misc/app_cell_log.c
@@ -92,13 +92,12 @@ static int l23_getopt_options(struct option **options)
 		{"logfile", 1, 0, 'l'},
 		{"rach", 1, 0, 'r'},
 		{"no-rach", 1, 0, 'n'},
-#ifdef _USE_GPSD
+#ifdef _HAVE_GPSD
 		{"gpsd-host", 1, 0, 'g'},
-		{"gpsd-port", 1, 0, 'p'}
-#else
+		{"gpsd-port", 1, 0, 'p'},
+#endif
 		{"gps", 1, 0, 'g'},
 		{"baud", 1, 0, 'b'}
-#endif
 	};
 
 	*options = opts;
@@ -109,15 +108,13 @@ static int l23_cfg_print_help()
 {
 	printf("\nApplication specific\n");
 	printf("  -l --logfile LOGFILE	Logfile for the cell log.\n");
-	printf("  -r --rach    RACH		Nr. of RACH bursts to send.\n");
-	printf("  -n --no-rach			Send no rach bursts.\n");
-#ifdef _USE_GPSD
+	printf("  -r --rach RACH	Nr. of RACH bursts to send.\n");
+	printf("  -n --no-rach		Send no rach bursts.\n");
 	printf("  -g --gpsd-host HOST	127.0.0.1. gpsd host.\n");
-	printf("  -p --port PORT		2947. gpsd port\n");
-#else
-	printf("  -g --gps DEVICE		/dev/ttyACM0. GPS device.\n");
-	printf("  -b --baud BAUDRAT		The baud rate of the GPS device\n");
-#endif
+	printf("  -p --port PORT	2947. gpsd port\n");
+	printf("  -f --gps DEVICE	/dev/ttyACM0. GPS serial device.\n");
+	printf("  -b --baud BAUDRAT	The baud rate of the GPS device\n");
+
 	return 0;
 }
 
@@ -133,42 +130,57 @@ static int l23_cfg_handle(int c, const char *optarg)
 	case 'n':
 		RACH_MAX = 0;
 		break;
-#ifdef _USE_GPSD
 	case 'g':
-		snprintf(gps.gpsd_host, ARRAY_SIZE(gps.gpsd_host), "%s", optarg);
+#ifdef _HAVE_GPSD
+		snprintf(g.gpsd_host, ARRAY_SIZE(g.gpsd_host), "%s", optarg);
 		/* force string terminator */
-		gps.gpsd_host[ARRAY_SIZE(gps.gpsd_host) - 1] = '\0';
-		LOGP(DGPS, LOGL_INFO, "Using gpsd host %s\n", gps.gpsd_host);
+		g.gpsd_host[ARRAY_SIZE(g.gpsd_host) - 1] = '\0';
+		if (g.gps_type != GPS_TYPE_UNDEF)
+			goto cmd_line_error;
+		g.gps_type = GPS_TYPE_GPSD;
+		LOGP(DGPS, LOGL_INFO, "Using gpsd host %s\n", g.gpsd_host);
+#else
+		printf("Gpsd support not compiled.\n");
+		exit(1);
+#endif
 		break;
 	case 'p':
-		snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "%s", optarg);
+#ifdef _HAVE_GPSD
+		snprintf(g.gpsd_port, ARRAY_SIZE(g.gpsd_port), "%s", optarg);
 		/* force string terminator */
-		gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0';
-		LOGP(DGPS, LOGL_INFO, "Using gpsd port %s\n", gps.gpsd_port);
-		break;
+		g.gpsd_port[ARRAY_SIZE(g.gpsd_port) - 1] = '\0';
+		g.gps_type = GPS_TYPE_GPSD;
+		LOGP(DGPS, LOGL_INFO, "Using gpsd port %s\n", g.gpsd_port);
 #else
-	case 'g':
-		snprintf(gps.device, ARRAY_SIZE(gps.device), "%s", optarg);
+		printf("Gpsd support not compiled.\n");
+		exit(1);
+#endif
+		break;
+	case 'f':
+		snprintf(g.device, ARRAY_SIZE(g.device), "%s", optarg);
 		/* force string terminator */
-		gps.device[ARRAY_SIZE(gps.device) - 1] = '\0';
-		LOGP(DGPS, LOGL_INFO, "Using GPS device %s\n", gps.device);
+		g.device[ARRAY_SIZE(g.device) - 1] = '\0';
+		if (g.gps_type != GPS_TYPE_UNDEF)
+			goto cmd_line_error;
+		g.gps_type = GPS_TYPE_SERIAL;
+		LOGP(DGPS, LOGL_INFO, "Using GPS serial device %s\n", g.device);
 		break;
 	case 'b':
-		gps.baud = atoi(optarg);
-		LOGP(DGPS, LOGL_INFO, "Setting GPS baudrate to %u\n", gps.baud);
+		g.baud = atoi(optarg);
+		g.gps_type = GPS_TYPE_SERIAL;
+		LOGP(DGPS, LOGL_INFO, "Setting GPS baudrate to %u\n", g.baud);
 		break;
-#endif
 	}
 	return 0;
+
+cmd_line_error:
+	printf("\nYou can't specify both gpsd and serial gps!!\n\n");
+	exit(1);
 }
 
 static struct l23_app_info info = {
 	.copyright	= "Copyright (C) 2010 Andreas Eversberg\n",
-#ifdef _USE_GPSD
-	.getopt_string	= "l:r:ng:p:",
-#else
-	.getopt_string	= "l:r:ng:b:",
-#endif
+	.getopt_string	= "g:p:l:r:nf:b:",
 	.cfg_supported	= l23_cfg_supported,
 	.cfg_getopt_opt = l23_getopt_options,
 	.cfg_handle_opt	= l23_cfg_handle,
diff --git a/src/host/layer23/src/misc/cell_log.c b/src/host/layer23/src/misc/cell_log.c
index a0f9769..7de2c40 100644
--- a/src/host/layer23/src/misc/cell_log.c
+++ b/src/host/layer23/src/misc/cell_log.c
@@ -119,17 +119,17 @@ static void start_pm(void);
 
 static void log_gps(void)
 {
-	if (!gps.enable || !gps.valid)
+	if (!g.enable || !g.valid)
 		return;
-	LOGFILE("position %.8f %.8f\n", gps.longitude, gps.latitude);
+	LOGFILE("position %.8f %.8f\n", g.longitude, g.latitude);
 }
 
 static void log_time(void)
 {
 	time_t now;
 
-	if (gps.enable && gps.valid)
-		now = gps.gmt;
+	if (g.enable && g.valid)
+		now = g.gmt;
 	else
 		time(&now);
 	LOGFILE("time %lu\n", now);
@@ -317,15 +317,15 @@ static void start_sync(void)
 		}
 	}
 	/* if GPS becomes valid, like after exitting a tunnel */
-	if (!pm_gps_valid && gps.valid) {
+	if (!pm_gps_valid && g.valid) {
 		pm_gps_valid = 1;
-		geo2space(&pm_gps_x, &pm_gps_y, &pm_gps_z, gps.longitude,
-			gps.latitude);
+		geo2space(&pm_gps_x, &pm_gps_y, &pm_gps_z, g.longitude,
+			g.latitude);
 	}
-	if (pm_gps_valid && gps.valid) {
+	if (pm_gps_valid && g.valid) {
 		double x, y, z;
 
-		geo2space(&x, &y, &z, gps.longitude, gps.latitude);
+		geo2space(&x, &y, &z, g.longitude, g.latitude);
 		dist = distinspace(pm_gps_x, pm_gps_y, pm_gps_z, x, y, z);
 		sprintf(dist_str, "  dist %d", (int)dist);
 	}
@@ -357,10 +357,10 @@ static void start_pm(void)
 
 	if (from == 0 && to == 0) {
 		LOGP(DSUM, LOGL_INFO, "Measurement done\n");
-		pm_gps_valid = gps.enable && gps.valid;
+		pm_gps_valid = g.enable && g.valid;
 		if (pm_gps_valid)
 			geo2space(&pm_gps_x, &pm_gps_y, &pm_gps_z,
-				gps.longitude, gps.latitude);
+				g.longitude, g.latitude);
 		log_pm();
 		start_sync();
 		return;
@@ -786,10 +786,10 @@ int scan_init(struct osmocom_ms *_ms)
 	register_signal_handler(SS_L1CTL, &signal_cb, NULL);
 	memset(&timer, 0, sizeof(timer));
 	osmol2_register_handler(ms, &rcv_rsl);
-	gps.enable = 1;
+	g.enable = 1;
 	osmo_gps_init();
 	if (osmo_gps_open())
-		gps.enable = 0;
+		g.enable = 0;
 
 	if (!strcmp(logname, "-"))
 		logfp = stdout;
@@ -808,7 +808,7 @@ int scan_init(struct osmocom_ms *_ms)
 int scan_exit(void)
 {
 	LOGP(DSUM, LOGL_INFO, "Scanner exit\n");
-	if (gps.valid)
+	if (g.valid)
 		osmo_gps_close();
 	if (logfp)
 		fclose(logfp);
diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c
index 7888f01..b93248d 100644
--- a/src/host/layer23/src/mobile/vty_interface.c
+++ b/src/host/layer23/src/mobile/vty_interface.c
@@ -836,11 +836,11 @@ DEFUN(cfg_gps_enable, cfg_gps_enable_cmd, "gps enable",
 	"GPS receiver")
 {
 	if (osmo_gps_open()) {
-		gps.enable = 1;
+		g.enable = 1;
 		vty_out(vty, "Failed to open GPS device!%s", VTY_NEWLINE);
 		return CMD_WARNING;
 	}
-	gps.enable = 1;
+	g.enable = 1;
 
 	return CMD_SUCCESS;
 }
@@ -848,31 +848,32 @@ DEFUN(cfg_gps_enable, cfg_gps_enable_cmd, "gps enable",
 DEFUN(cfg_no_gps_enable, cfg_no_gps_enable_cmd, "no gps enable",
 	NO_STR "Disable GPS receiver")
 {
-	if (gps.enable)
+	if (g.enable)
 		osmo_gps_close();
-	gps.enable = 0;
+	g.enable = 0;
 
 	return CMD_SUCCESS;
 }
 
-#ifdef _USE_GPSD
+#ifdef _HAVE_GPSD
 DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT",
 	"GPS receiver\nSelect gpsd host and port\n"
 	"IP and port (optional) of the host running gpsd")
 {
 	char* colon = strstr(argv[0], ":");
 	if (colon != NULL) {
-		memcpy(gps.gpsd_host, argv[0], colon - argv[0] - 1);
-		gps.gpsd_host[colon - argv[0]] = '\0';
-		memcpy(gps.gpsd_port, colon, strlen(colon));
-		gps.gpsd_port[strlen(colon)] = '\0';
+		memcpy(g.gpsd_host, argv[0], colon - argv[0] - 1);
+		g.gpsd_host[colon - argv[0]] = '\0';
+		memcpy(g.gpsd_port, colon, strlen(colon));
+		g.gpsd_port[strlen(colon)] = '\0';
 	} else {
-		snprintf(gps.gpsd_host, ARRAY_SIZE(gps.gpsd_host), "%s", argv[0]);
-		gps.gpsd_host[ARRAY_SIZE(gps.gpsd_host) - 1] = '\0';
-		snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "2947");
-		gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0';
+		snprintf(g.gpsd_host, ARRAY_SIZE(g.gpsd_host), "%s", argv[0]);
+		g.gpsd_host[ARRAY_SIZE(g.gpsd_host) - 1] = '\0';
+		snprintf(g.gpsd_port, ARRAY_SIZE(g.gpsd_port), "2947");
+		g.gpsd_port[ARRAY_SIZE(g.gpsd_port) - 1] = '\0';
 	}
-	if (gps.enable) {
+	g.gps_type = GPS_TYPE_GPSD;
+	if (g.enable) {
 		osmo_gps_close();
 		if (osmo_gps_open()) {
 			vty_out(vty, "Failed to connect to gpsd host!%s",
@@ -883,14 +884,16 @@ DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT",
 
 	return CMD_SUCCESS;
 }
-#else
+#endif
+
 DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE",
 	"GPS receiver\nSelect serial device\n"
 	"Full path of serial device including /dev/")
 {
-	strncpy(gps.device, argv[0], sizeof(gps.device));
-	gps.device[sizeof(gps.device) - 1] = '\0';
-	if (gps.enable) {
+	strncpy(g.device, argv[0], sizeof(g.device));
+	g.device[sizeof(g.device) - 1] = '\0';
+	g.gps_type = GPS_TYPE_SERIAL;
+	if (g.enable) {
 		osmo_gps_close();
 		if (osmo_gps_open()) {
 			vty_out(vty, "Failed to open GPS device!%s",
@@ -901,21 +904,19 @@ DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE",
 
 	return CMD_SUCCESS;
 }
-#endif
 
-#ifndef _USE_GPSD
 DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate "
 	"(default|4800|""9600|19200|38400|57600|115200)",
 	"GPS receiver\nSelect baud rate\nDefault, don't modify\n\n\n\n\n\n")
 {
 	if (argv[0][0] == 'd')
-		gps.baud = 0;
+		g.baud = 0;
 	else
-		gps.baud = atoi(argv[0]);
-	if (gps.enable) {
+		g.baud = atoi(argv[0]);
+	if (g.enable) {
 		osmo_gps_close();
 		if (osmo_gps_open()) {
-			gps.enable = 0;
+			g.enable = 0;
 			vty_out(vty, "Failed to open GPS device!%s",
 				VTY_NEWLINE);
 			return CMD_WARNING;
@@ -924,7 +925,6 @@ DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate "
 
 	return CMD_SUCCESS;
 }
-#endif
 
 /* per MS config */
 DEFUN(cfg_ms, cfg_ms_cmd, "ms MS_NAME",
@@ -1204,17 +1204,16 @@ static int config_write(struct vty *vty)
 {
 	struct osmocom_ms *ms;
 
-#ifdef _USE_GPSD
-	vty_out(vty, "gpsd host %s%s", gps.gpsd_host, VTY_NEWLINE);
-	vty_out(vty, "gpsd port %s%s", gps.gpsd_port, VTY_NEWLINE);
-#else
-	vty_out(vty, "gps device %s%s", gps.device, VTY_NEWLINE);
-	if (gps.baud)
-		vty_out(vty, "gps baudrate %d%s", gps.baud, VTY_NEWLINE);
+#ifdef _HAVE_GPSD
+	vty_out(vty, "gpsd host %s%s", g.gpsd_host, VTY_NEWLINE);
+	vty_out(vty, "gpsd port %s%s", g.gpsd_port, VTY_NEWLINE);
+#endif
+	vty_out(vty, "gps device %s%s", g.device, VTY_NEWLINE);
+	if (g.baud)
+		vty_out(vty, "gps baudrate %d%s", g.baud, VTY_NEWLINE);
 	else
 		vty_out(vty, "gps baudrate default%s", VTY_NEWLINE);
-#endif
-	vty_out(vty, "%sgps enable%s", (gps.enable) ? "" : "no ", VTY_NEWLINE);
+	vty_out(vty, "%sgps enable%s", (g.enable) ? "" : "no ", VTY_NEWLINE);
 	vty_out(vty, "!%s", VTY_NEWLINE);
 
 	llist_for_each_entry(ms, &ms_list, entity)
@@ -2305,12 +2304,11 @@ int ms_vty_init(void)
 	install_element(ENABLE_NODE, &call_retr_cmd);
 	install_element(ENABLE_NODE, &call_dtmf_cmd);
 
-#ifdef _USE_GPSD
+#ifdef _HAVE_GPSD
 	install_element(CONFIG_NODE, &cfg_gps_host_cmd);
-#else
+#endif
 	install_element(CONFIG_NODE, &cfg_gps_device_cmd);
 	install_element(CONFIG_NODE, &cfg_gps_baud_cmd);
-#endif
 	install_element(CONFIG_NODE, &cfg_gps_enable_cmd);
 	install_element(CONFIG_NODE, &cfg_no_gps_enable_cmd);
 
-- 
1.7.4


--------------090001080502050109060706--



From Andreas.Eversberg at versatel.de  Wed Mar  2 13:56:41 2011
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Wed, 2 Mar 2011 14:56:41 +0100
Subject: AW: Fwd: gpsd support
Message-ID: <B16317F2B1592B4492FC414114171CE6051E9F3F@FLBVEXCH01.versatel.local>

hi dario,

thanx for you work. here i still got problems, if i use gpsd 2.32:

laptop src # make
Making all in common
make[1]: Entering directory
`/root/osmocom-bb/src/host/layer23/src/common'
  CC     gps.o
gps.c: In function 'osmo_gpsd_cb':
gps.c:73: warning: implicit declaration of function 'gps_waiting'
gps.c: In function 'osmo_gpsd_open':
gps.c:135: warning: implicit declaration of function 'gps_stream'
gps.c:135: error: 'WATCH_ENABLE' undeclared (first use in this function)
gps.c:135: error: (Each undeclared identifier is reported only once
gps.c:135: error: for each function it appears in.)
make[1]: *** [gps.o] Error 1
make[1]: Leaving directory
`/root/osmocom-bb/src/host/layer23/src/common'
make: *** [all-recursive] Error 1

also the patch will not work with the current head. the app_cell_log.c
will fail to patch, but this is a minor problem.

regards,

andreas



From b8.adel at gmail.com  Tue Mar  1 18:21:12 2011
From: b8.adel at gmail.com (adel)
Date: Tue, 1 Mar 2011 10:21:12 -0800 (PST)
Subject: Help me I have a difficult problem
Message-ID: <1299003672779-2605211.post@n3.nabble.com>

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-problem-tp2605211p2605211.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From holger at freyther.de  Tue Mar  1 18:58:45 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 01 Mar 2011 19:58:45 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <1299003672779-2605211.post@n3.nabble.com>
References: <1299003672779-2605211.post@n3.nabble.com>
Message-ID: <4D6D41E5.1040904@freyther.de>

On 03/01/2011 07:21 PM, adel wrote:

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

What do you think this could mean? What do you plan to do about it?



From shadown at gmail.com  Tue Mar  1 19:00:15 2011
From: shadown at gmail.com (Sergio 'shadown' Alvarez)
Date: Tue, 01 Mar 2011 20:00:15 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <1299003672779-2605211.post@n3.nabble.com>
References: <1299003672779-2605211.post@n3.nabble.com>
Message-ID: <1299006015.6744.21.camel@chakrita>

the difficult problem you are having is that you can't read,
unfortunately we can't fix that for you.

>>>>>> Please check or create config file using:
'touch /etc/osmocom/osmocom.cfg' <<<<<<

On Tue, 2011-03-01 at 10:21 -0800, adel wrote:
> 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
> 




From holger at freyther.de  Tue Mar  1 19:29:05 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Tue, 01 Mar 2011 20:29:05 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <1299006015.6744.21.camel@chakrita>
References: <1299003672779-2605211.post@n3.nabble.com>
	<1299006015.6744.21.camel@chakrita>
Message-ID: <4D6D4901.3000604@freyther.de>

On 03/01/2011 08:00 PM, Sergio 'shadown' Alvarez wrote:
> the difficult problem you are having is that you can't read,
> unfortunately we can't fix that for you.

We need to be more friendly, comprehensive reading in a foreign language can
be difficult, maybe he tried the command and failed as he has no permission
for /etc and does not really know how to continue.



From b8.adel at gmail.com  Wed Mar  2 03:09:37 2011
From: b8.adel at gmail.com (adel)
Date: Tue, 1 Mar 2011 19:09:37 -0800 (PST)
Subject: Help me I have a difficult problem
In-Reply-To: <1299006015.6744.21.camel@chakrita>
References: <1299003672779-2605211.post@n3.nabble.com>
	<1299006015.6744.21.camel@chakrita>
Message-ID: <1299035377327-2608520.post@n3.nabble.com>

This is a problem faced by
~$ touch /etc/osmocom/osmocom.cfg
touch: cannot touch `/etc/osmocom/osmocom.cfg': No such file or directory
Does someone has a solution to this problem

-- 
View this message in context: http://baseband-devel.722152.n3.nabble.com/Help-me-I-have-a-difficult-problem-tp2605211p2608520.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From shadown at gmail.com  Wed Mar  2 07:04:57 2011
From: shadown at gmail.com (Sergio Alvarez)
Date: Wed, 2 Mar 2011 08:04:57 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <1299035377327-2608520.post@n3.nabble.com>
References: <1299003672779-2605211.post@n3.nabble.com>
	<1299006015.6744.21.camel@chakrita>
	<1299035377327-2608520.post@n3.nabble.com>
Message-ID: <B0C0E4B3-7F73-43BF-A25D-7CF6DAF2E571@gmail.com>

You have to create the directory first, as in "mkdir /etc/osmocom" as root (or appending sudo to your commands).

-sergio


On Mar 2, 2011, at 4:09, adel <b8.adel at gmail.com> wrote:

> This is a problem faced by
> ~$ touch /etc/osmocom/osmocom.cfg
> touch: cannot touch `/etc/osmocom/osmocom.cfg': No such file or directory
> Does someone has a solution to this problem
> 
> -- 
> View this message in context: http://baseband-devel.722152.n3.nabble.com/Help-me-I-have-a-difficult-problem-tp2605211p2608520.html
> Sent from the baseband-devel mailing list archive at Nabble.com.
> 



From sim at ijskes.org  Wed Mar  2 07:56:46 2011
From: sim at ijskes.org (Sim IJskes)
Date: Wed, 02 Mar 2011 08:56:46 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <1299035377327-2608520.post@n3.nabble.com>
References: <1299003672779-2605211.post@n3.nabble.com>	<1299006015.6744.21.camel@chakrita>
	<1299035377327-2608520.post@n3.nabble.com>
Message-ID: <4D6DF83E.4050201@ijskes.org>

On 02-03-11 04:09, adel wrote:
> This is a problem faced by
> ~$ touch /etc/osmocom/osmocom.cfg
> touch: cannot touch `/etc/osmocom/osmocom.cfg': No such file or directory
> Does someone has a solution to this problem
>

Please try:

sudo mkdir /etc/osmocom
sudo touch /etc/osmocom/osmocom.cfg

Gr. Sim

-------------- next part --------------
A non-text attachment was scrubbed...
Name: sim.vcf
Type: text/x-vcard
Size: 113 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110302/1ed78c53/attachment.vcf>

From holger at freyther.de  Wed Mar  2 08:34:26 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 02 Mar 2011 09:34:26 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <4D6DF83E.4050201@ijskes.org>
References: <1299003672779-2605211.post@n3.nabble.com>	<1299006015.6744.21.camel@chakrita>	<1299035377327-2608520.post@n3.nabble.com>
	<4D6DF83E.4050201@ijskes.org>
Message-ID: <4D6E0112.4010905@freyther.de>

On 03/02/2011 08:56 AM, Sim IJskes wrote:
> On 02-03-11 04:09, adel wrote:
>> This is a problem faced by
>> ~$ touch /etc/osmocom/osmocom.cfg
>> touch: cannot touch `/etc/osmocom/osmocom.cfg': No such file or directory
>> Does someone has a solution to this problem


Hey Andreas,
would you mind if we don't require special privileges to start mobile? E.g.
the below patch?

diff --git a/src/host/layer23/src/mobile/main.c
b/src/host/layer23/src/mobile/main.c
index 87aa4c6..283e3c6 100644
--- a/src/host/layer23/src/mobile/main.c
+++ b/src/host/layer23/src/mobile/main.c
@@ -44,7 +44,7 @@
 struct log_target *stderr_target;

 void *l23_ctx = NULL;
-static const char *config_file = "/etc/osmocom/osmocom.cfg";
+static const char *config_file = "osmocom.cfg";
 struct llist_head ms_list;
 static uint32_t gsmtap_ip = 0;
 unsigned short vty_port = 4247;



From 246tnt at gmail.com  Wed Mar  2 08:38:57 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Wed, 2 Mar 2011 09:38:57 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <4D6E0112.4010905@freyther.de>
References: <1299003672779-2605211.post@n3.nabble.com>
	<1299006015.6744.21.camel@chakrita>
	<1299035377327-2608520.post@n3.nabble.com>
	<4D6DF83E.4050201@ijskes.org> <4D6E0112.4010905@freyther.de>
Message-ID: <AANLkTik7z7wBmLAS7rK5v3YUbAshFUcE52A0m-eMz2b_@mail.gmail.com>

Hi,

> Hey Andreas,
> would you mind if we don't require special privileges to start mobile? E.g.
> the below patch?

Probably not sufficient. There is a 'cache' file created in
/etc/osmocom somewhere ...

    Sylvain



From holger at freyther.de  Wed Mar  2 08:50:25 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 02 Mar 2011 09:50:25 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <AANLkTik7z7wBmLAS7rK5v3YUbAshFUcE52A0m-eMz2b_@mail.gmail.com>
References: <1299003672779-2605211.post@n3.nabble.com>	<1299006015.6744.21.camel@chakrita>	<1299035377327-2608520.post@n3.nabble.com>	<4D6DF83E.4050201@ijskes.org>
	<4D6E0112.4010905@freyther.de>
	<AANLkTik7z7wBmLAS7rK5v3YUbAshFUcE52A0m-eMz2b_@mail.gmail.com>
Message-ID: <4D6E04D1.6000103@freyther.de>

On 03/02/2011 09:38 AM, Sylvain Munaut wrote:
> Hi,
> 
>> Hey Andreas,
>> would you mind if we don't require special privileges to start mobile? E.g.
>> the below patch?
> 
> Probably not sufficient. There is a 'cache' file created in
> /etc/osmocom somewhere ...

Ah thanks.



From dario.lombardo at libero.it  Wed Mar  2 08:56:01 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Wed, 02 Mar 2011 09:56:01 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <AANLkTik7z7wBmLAS7rK5v3YUbAshFUcE52A0m-eMz2b_@mail.gmail.com>
References: <1299003672779-2605211.post@n3.nabble.com>	<1299006015.6744.21.camel@chakrita>	<1299035377327-2608520.post@n3.nabble.com>	<4D6DF83E.4050201@ijskes.org>
	<4D6E0112.4010905@freyther.de>
	<AANLkTik7z7wBmLAS7rK5v3YUbAshFUcE52A0m-eMz2b_@mail.gmail.com>
Message-ID: <4D6E0621.1020508@libero.it>



On 03/02/2011 09:38 AM, Sylvain Munaut wrote:
> Hi,
>
>> Hey Andreas,
>> would you mind if we don't require special privileges to start mobile? E.g.
>> the below patch?
> Probably not sufficient. There is a 'cache' file created in
> /etc/osmocom somewhere ...
>
>      Sylvain
>
There are also the permissions on the tty file (/dev/ttyUSB0 for me). On 
my system it belongs to root/dialout. I know that it can be fixed 
changing the groups for my user, but if we want binaries to be run 
without root permissions, that should be explained somewhere. My opinion.



From khorben at defora.org  Wed Mar  2 09:02:16 2011
From: khorben at defora.org (Pierre Pronchery)
Date: Wed, 02 Mar 2011 10:02:16 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <4D6E0112.4010905@freyther.de>
References: <1299003672779-2605211.post@n3.nabble.com>	<1299006015.6744.21.camel@chakrita>	<1299035377327-2608520.post@n3.nabble.com>	<4D6DF83E.4050201@ijskes.org>
	<4D6E0112.4010905@freyther.de>
Message-ID: <4D6E0798.4050605@defora.org>

On 02/03/2011 09:34, Holger Hans Peter Freyther wrote:
> 
> Hey Andreas,
> would you mind if we don't require special privileges to start mobile? E.g.
> the below patch?

I proposed one already, that creates $HOME/osmocom.cfg instead:
Message-ID: <4D441144.3000304 at defora.org>

About cache files, if any, they should never be stored in /etc IMHO.

HTH,
-- 
khorben



From alexander.chemeris at gmail.com  Wed Mar  2 09:12:31 2011
From: alexander.chemeris at gmail.com (Alexander Chemeris)
Date: Wed, 2 Mar 2011 12:12:31 +0300
Subject: Help me I have a difficult problem
In-Reply-To: <4D6E0798.4050605@defora.org>
References: <1299003672779-2605211.post@n3.nabble.com>
	<1299006015.6744.21.camel@chakrita>
	<1299035377327-2608520.post@n3.nabble.com>
	<4D6DF83E.4050201@ijskes.org>
	<4D6E0112.4010905@freyther.de> <4D6E0798.4050605@defora.org>
Message-ID: <AANLkTimaYpX_HfpQ-mzEzFQK42axpSt7UrMDizLS9HNG@mail.gmail.com>

On Wed, Mar 2, 2011 at 12:02, Pierre Pronchery <khorben at defora.org> wrote:
> On 02/03/2011 09:34, Holger Hans Peter Freyther wrote:
>>
>> Hey Andreas,
>> would you mind if we don't require special privileges to start mobile? E.g.
>> the below patch?
>
> I proposed one already, that creates $HOME/osmocom.cfg instead:
> Message-ID: <4D441144.3000304 at defora.org>
>
> About cache files, if any, they should never be stored in /etc IMHO.

Well, Linux has a special /var/cache for caches of daemons. And from
my experience user-run programs usually store caches under ~/.smth

And I saw some Linux systems, where /etc was placed on a read-only FS,
as it's not supposed to be changed frequently.


-- 
Regards,
Alexander Chemeris.
http://www.fairwaves.ru



From shadown at gmail.com  Wed Mar  2 09:27:23 2011
From: shadown at gmail.com (Sergio 'shadown' Alvarez)
Date: Wed, 02 Mar 2011 10:27:23 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <4D6E0798.4050605@defora.org>
References: <1299003672779-2605211.post@n3.nabble.com>
	<1299006015.6744.21.camel@chakrita>
	<1299035377327-2608520.post@n3.nabble.com>	<4D6DF83E.4050201@ijskes.org>
	<4D6E0112.4010905@freyther.de>  <4D6E0798.4050605@defora.org>
Message-ID: <1299058043.6744.25.camel@chakrita>

This sound as a better solution, although I would suggest a .osmocom
directory and everything else as cache/whatever inside that directory,
otherwise it would be pretty dirty and messy as the project grows.

On Wed, 2011-03-02 at 10:02 +0100, Pierre Pronchery wrote:
> On 02/03/2011 09:34, Holger Hans Peter Freyther wrote:
> > 
> > Hey Andreas,
> > would you mind if we don't require special privileges to start mobile? E.g.
> > the below patch?
> 
> I proposed one already, that creates $HOME/osmocom.cfg instead:
> Message-ID: <4D441144.3000304 at defora.org>
> 
> About cache files, if any, they should never be stored in /etc IMHO.
> 
> HTH,




From 246tnt at gmail.com  Wed Mar  2 09:34:04 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Wed, 2 Mar 2011 10:34:04 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <1299058043.6744.25.camel@chakrita>
References: <1299003672779-2605211.post@n3.nabble.com>
	<1299006015.6744.21.camel@chakrita>
	<1299035377327-2608520.post@n3.nabble.com>
	<4D6DF83E.4050201@ijskes.org> <4D6E0112.4010905@freyther.de>
	<4D6E0798.4050605@defora.org> <1299058043.6744.25.camel@chakrita>
Message-ID: <AANLkTi=+1gTt7YcqfeGsV6ba+7NHpMn1Sm7pYX2i0sDj@mail.gmail.com>

On Wed, Mar 2, 2011 at 10:27 AM, Sergio 'shadown' Alvarez
<shadown at gmail.com> wrote:
> This sound as a better solution, although I would suggest a .osmocom
> directory and everything else as cache/whatever inside that directory,
> otherwise it would be pretty dirty and messy as the project grows.

I'd even recommend ${HOME}/.config/osmocom/ (which seem to be the new
standard) and have the osmocom-bb.cfg and cell cache file in there.

Cheers,

    Sylvain



From laforge at gnumonks.org  Wed Mar  2 10:40:13 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Wed, 2 Mar 2011 11:40:13 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <1299058043.6744.25.camel@chakrita>
References: <1299003672779-2605211.post@n3.nabble.com>
	<1299006015.6744.21.camel@chakrita>
	<1299035377327-2608520.post@n3.nabble.com>
	<4D6DF83E.4050201@ijskes.org> <4D6E0112.4010905@freyther.de>
	<4D6E0798.4050605@defora.org> <1299058043.6744.25.camel@chakrita>
Message-ID: <20110302104013.GO3859@prithivi.gnumonks.org>

On Wed, Mar 02, 2011 at 10:27:23AM +0100, Sergio 'shadown' Alvarez wrote:
> This sound as a better solution, although I would suggest a .osmocom
> directory and everything else as cache/whatever inside that directory,
> otherwise it would be pretty dirty and messy as the project grows.

check the git tree, I have just done that (~/.osmocom/bb/)


-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From b8.adel at gmail.com  Wed Mar  2 21:50:36 2011
From: b8.adel at gmail.com (adel)
Date: Wed, 2 Mar 2011 13:50:36 -0800 (PST)
Subject: Help me I have a difficult problem
In-Reply-To: <4D6DF83E.4050201@ijskes.org>
References: <1299003672779-2605211.post@n3.nabble.com>
	<1299006015.6744.21.camel@chakrita>
	<1299035377327-2608520.post@n3.nabble.com>
	<4D6DF83E.4050201@ijskes.org>
Message-ID: <1299102636623-2620895.post@n3.nabble.com>

mr.Sim IJskes 
Thank you for the assistance provided to me to solve the problem
We have succeeded him your idea
Accept my sincere greetings and gratitude with my hope to cooperate more
Thank you

--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Help-me-I-have-a-difficult-problem-tp2605211p2620895.html
Sent from the baseband-devel mailing list archive at Nabble.com.



From Andreas.Eversberg at versatel.de  Wed Mar  2 09:37:45 2011
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Wed, 2 Mar 2011 10:37:45 +0100
Subject: AW: Help me I have a difficult problem
Message-ID: <B16317F2B1592B4492FC414114171CE6051E9CD3@FLBVEXCH01.versatel.local>

> This sound as a better solution, although I would suggest a .osmocom
> directory and everything else as cache/whatever inside that directory,
> otherwise it would be pretty dirty and messy as the project grows.

what about this? :

$HOME/.osmocom/mobile.cfg

and for the stored band allocations:

$HOME/.osmocom/xxxx.ba






From holger at freyther.de  Wed Mar  2 10:33:22 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Wed, 02 Mar 2011 11:33:22 +0100
Subject: AW: Help me I have a difficult problem
In-Reply-To: <B16317F2B1592B4492FC414114171CE6051E9CD3@FLBVEXCH01.versatel.local>
References: <B16317F2B1592B4492FC414114171CE6051E9CD3@FLBVEXCH01.versatel.local>
Message-ID: <4D6E1CF2.1060709@freyther.de>

On 03/02/2011 10:37 AM, Andreas.Eversberg wrote:

> $HOME/.osmocom/xxxx.ba


To be XDG compliant it would need to be ~/.config and ~/.cache (but these can
be redefined via environment variables). I just saw tnt's mail so let me point
to the spec[1].

holger

[1] http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html



From laforge at gnumonks.org  Wed Mar  2 13:57:32 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Wed, 2 Mar 2011 14:57:32 +0100
Subject: AW: Help me I have a difficult problem
In-Reply-To: <4D6E1CF2.1060709@freyther.de>
References: <B16317F2B1592B4492FC414114171CE6051E9CD3@FLBVEXCH01.versatel.local>
	<4D6E1CF2.1060709@freyther.de>
Message-ID: <20110302135732.GE5524@prithivi.gnumonks.org>

Holger,

On Wed, Mar 02, 2011 at 11:33:22AM +0100, Holger Hans Peter Freyther wrote:

> To be XDG compliant it would need to be ~/.config and ~/.cache (but these can
> be redefined via environment variables). I just saw tnt's mail so let me point
> to the spec[1].

to be honest, I don't think a free"desktop"org spec really matters much to us.
I would much rather have ~/.osmocom/{bb,...} for the various projects and
sub-projects we have.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From laforge at gnumonks.org  Wed Mar  2 10:42:41 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Wed, 2 Mar 2011 11:42:41 +0100
Subject: Help me I have a difficult problem
In-Reply-To: <B16317F2B1592B4492FC414114171CE6051E9CD3@FLBVEXCH01.versatel.local>
References: <B16317F2B1592B4492FC414114171CE6051E9CD3@FLBVEXCH01.versatel.local>
Message-ID: <20110302104241.GP3859@prithivi.gnumonks.org>

Hi Andreas,
On Wed, Mar 02, 2011 at 10:37:45AM +0100, Andreas.Eversberg wrote:

> what about this? :
> 
> $HOME/.osmocom/mobile.cfg
> $HOME/.osmocom/xxxx.ba
 
It's now $HOME/.osmocom/bb/{mobile.cfg,xxxx.ba} in the master branch.

Regards,
	Harald

p.s.: Eventually, I would like to see this become part of libosmocore, i.e.
having a global data structure or a function how to obtain the application
specific .osmocom - subdirectory for a given program.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From suraev at stud.ntnu.no  Wed Mar  2 01:42:10 2011
From: suraev at stud.ntnu.no (suraev at stud.ntnu.no)
Date: Wed, 02 Mar 2011 02:42:10 +0100
Subject: openmoko test
Message-ID: <4D6DA072.2070905@stud.ntnu.no>

Hello.

I'm trying to run osmocom on neo freerunner (gta02) with shr-unstable.

I've stopped fso framework and disabled fsogsmd, checked that nobody is using modem:
fuser /dev/ttySAC0

After this I issue following:

echo 1 > /sys/bus/platform/devices/gta02-pm-gsm.0/download

./osmocon -m romload -p /dev/ttySAC0 hello_world.highram.bin
Sending Calypso romloader beacon...
Sending Calypso romloader beacon...
Sending Calypso romloader beacon...
Sending Calypso romloader beacon...
Sending Calypso romloader beacon...

In separate console I run:
echo 0 >/sys/bus/platform/devices/gta02-pm-gsm.0/power_on
echo 1 >/sys/bus/platform/devices/gta02-pm-gsm.0/power_on

but I keep getting "Sending Calypso romloader beacon..." on 1st one.

Any ideas what am I doing wrong?

Note: I got osmocon and hello_world.highram.bin at the same directory on moko to
which I'm connected via ssh.

Btw, do I need debug board in order to get /dev/ttyUSB0 when I connect freerunner to
my laptop?

best regards,
Max.




From suraev at stud.ntnu.no  Thu Mar  3 17:19:50 2011
From: suraev at stud.ntnu.no (suraev at stud.ntnu.no)
Date: Thu, 03 Mar 2011 18:19:50 +0100
Subject: openmoko problem
Message-ID: <4D6FCDB6.6080607@stud.ntnu.no>

Hi fellows.

I'm having troubles running osmocom on neo freerunner:

When I execure fluid flasher it works just fine, here is part of strace captured
while it was waiting for me to power cycle modem:

gettimeofday({1298877354, 793367}, NULL) = 0
gettimeofday({1298877354, 794341}, NULL) = 0
select(5, [4], NULL, NULL, {0, 12026})  = 0 (Timeout)
ioctl(4, TCFLSH, 0)                     = 0
write(4, "<i\0", 3)                     = 3
gettimeofday({1298877354, 813368}, NULL) = 0
gettimeofday({1298877354, 814343}, NULL) = 0
select(5, [4], NULL, NULL, {0, 12025})  = 0 (Timeout)
ioctl(4, TCFLSH, 0)                     = 0
write(4, "<i\0", 3)                     = 3

When I run osmocon - it waits endlessly completely ignoring power cycle:

gettimeofday({1298875477, 254494}, NULL) = 0
gettimeofday({1298875477, 255514}, NULL) = 0
select(6, [3 4 5], [], [], {0, 48980})  = 0 (Timeout)
gettimeofday({1298875477, 310972}, NULL) = 0
write(1, "Sending Calypso romloader beacon"..., 36) = 36
write(3, "<i", 2)                       = 2
gettimeofday({1298875477, 314494}, NULL) = 0
gettimeofday({1298875477, 315513}, NULL) = 0
select(6, [3 4 5], [], [], {0, 48981})  = 0 (Timeout)
gettimeofday({1298875477, 370973}, NULL) = 0
write(1, "Sending Calypso romloader beacon"..., 36) = 36
write(3, "<i", 2)                       = 2

Can you help me to figure out what's wrong?

Somebody succeeded in executing osmocon on moko?

thanks,
Max.



From khorben at defora.org  Thu Mar  3 19:02:40 2011
From: khorben at defora.org (Pierre Pronchery)
Date: Thu, 03 Mar 2011 20:02:40 +0100
Subject: openmoko problem
In-Reply-To: <4D6FCDB6.6080607@stud.ntnu.no>
References: <4D6FCDB6.6080607@stud.ntnu.no>
Message-ID: <4D6FE5D0.9060302@defora.org>

			Hi,

On 03/03/2011 18:19, suraev at stud.ntnu.no wrote:
> 
> I'm having troubles running osmocom on neo freerunner:

make sure you check this page:
http://bb.osmocom.org/trac/wiki/CalypsoRomloader

> When I run osmocon - it waits endlessly completely ignoring power cycle:

In my case I found that it was enough to use two separate terminals, and
then:
1. # echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
1. # osmocon -p /dev/ttySAC0 -m romload firmware.bin
2. # echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on

(actually you can even adapt this to use only one terminal with some
shell trickery)

anyway, with this done, in my case the modem was catching up the magic
sequence and downloading code as required.

Here, I've been using the internal serial connectivity to the
Freerunner; it works through the headphones port the same way if you prefer.

HTH,
-- 
khorben



From suraev at stud.ntnu.no  Thu Mar  3 19:38:37 2011
From: suraev at stud.ntnu.no (suraev at stud.ntnu.no)
Date: Thu, 03 Mar 2011 20:38:37 +0100
Subject: openmoko problem
In-Reply-To: <4D6FE5D0.9060302@defora.org>
References: <4D6FCDB6.6080607@stud.ntnu.no> <4D6FE5D0.9060302@defora.org>
Message-ID: <4D6FEE3D.2080405@stud.ntnu.no>

03.03.2011 20:02, Pierre Pronchery ?????:

> make sure you check this page:
> http://bb.osmocom.org/trac/wiki/CalypsoRomloader

I did.

> In my case I found that it was enough to use two separate terminals, and
> then:
> 1. # echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
> 1. # osmocon -p /dev/ttySAC0 -m romload firmware.bin
> 2. # echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on

Is this exact command you're executing?
Where did you got firmware.bin from?
I use
./osmocon -m romload -p /dev/ttySAC0 hello_world.highram.bin
(binary and osmocon are placed into the same directory).

> (actually you can even adapt this to use only one terminal with some
> shell trickery)

I connect via ssh so I can have as many terminals as I please :)

> anyway, with this done, in my case the modem was catching up the magic
> sequence and downloading code as required.

can you prepent osmocon with "strace -o /tmp/osmocon.log" so we can compare execution
traces?

thanks,
Max.



From vamposdecampos at gmail.com  Sun Mar  6 10:08:03 2011
From: vamposdecampos at gmail.com (Alex Badea)
Date: Sun, 06 Mar 2011 12:08:03 +0200
Subject: openmoko problem
In-Reply-To: <4D6FCDB6.6080607@stud.ntnu.no>
References: <4D6FCDB6.6080607@stud.ntnu.no>
Message-ID: <4D735D03.2060407@gmail.com>

On 2011-03-03 19:19, suraev at stud.ntnu.no wrote:
> Somebody succeeded in executing osmocon on moko?

I've found that the gta02 calypso chip was more timing-sensitive[1]. 
You can try a "-i 13" argument to osmocon -- possibly try other delay 
values if that doesn't work.

Cheers,
Alex

[1] 
http://lists.osmocom.org/pipermail/baseband-devel/2010-November/000772.html



From suraev at stud.ntnu.no  Sun Mar  6 16:00:58 2011
From: suraev at stud.ntnu.no (suraev at stud.ntnu.no)
Date: Sun, 06 Mar 2011 17:00:58 +0100
Subject: openmoko problem
In-Reply-To: <4D735D03.2060407@gmail.com>
References: <4D6FCDB6.6080607@stud.ntnu.no> <4D735D03.2060407@gmail.com>
Message-ID: <4D73AFBA.2020200@stud.ntnu.no>

06.03.2011 11:08, Alex Badea ?????:

> I've found that the gta02 calypso chip was more timing-sensitive[1]. You can try a
> "-i 13" argument to osmocon -- possibly try other delay values if that doesn't work.

Awesome!
Just the thing I was missing - works like a charm now :)

Thanks a lot,
Max.



From jakob at weite-welt.com  Thu Mar  3 20:00:50 2011
From: jakob at weite-welt.com (Leif Jakob)
Date: Thu, 3 Mar 2011 21:00:50 +0100
Subject: [PATCH] support for device specific setup (no need to patch UARTs
	for Pirelli DPL10)
Message-ID: <20110303200050.GM15313@aegir.asgard.sol>

Hi,

attached is a small patch to make board specific overrides (change UARTs).

I'm experiencing some stability issues on my pirelli phone, sooner or
later the layer1 resets and the phone boots again.

Ah by the way: the wiki says "send and receive SMS". Did I miss
something or is this not yet implemented (at least in "mobile")?

Cheers Leif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: board_setup.patch
Type: text/x-diff
Size: 4441 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110303/707bba90/attachment.bin>

From kktmp1 at gmail.com  Sun Mar  6 10:52:58 2011
From: kktmp1 at gmail.com (David Ortega)
Date: Sun, 6 Mar 2011 11:52:58 +0100
Subject: Newbie questions: Kc thru vty and CHAN_REQ
Message-ID: <AANLkTimu+UUO6swYDHrA5JsvuCcFRt1VeMsxPd_D9AWf@mail.gmail.com>

Hi list !!
Three newbie questions:

1.- What is the correct way to put Kc in the the sim-test ?

the help command says:
ki             Set Key (Kc) on test card

there are two options:
   - ki comp128 HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX
HEX
   (i think this is to fix the Ki value - 16bytes)
   - ki xor HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX HEX
   (this one need 12 bytes, when Kc it's only 8)

2.- In both calls type MOC and MTC i can't see the CHAN_REQ frame from MS in
wireshark. I only get the RR IMM_ASS_CMD from BTS and the rest of the
traffic:

    (from wireshark)
    to_MS    12:34:38.411650             GSMTAP   (CCCH) (RR) Immediate
Assignment
    from-MS 12:34:38.411675             LAPDm    U, func=UI(DTAP) (RR)
Measurement Report
    from-MS 12:34:38.411695             LAPDm    U P, func=SABM(DTAP) (MM)
CM Service Request
    to-MS     12:34:38.431273             GSMTAP   (CCCH) (RR) Immediate
Assignment

    (from my mobile app logs)
    Sun Mar  6 12:34:38 2011 <0001> gsm48_rr.c:363 new state idle ->
connection pending
    Sun Mar  6 12:34:38 2011 <0001> gsm48_rr.c:1313 CHANNEL REQUEST: e0
(Orig TCH/F)
    (but i don't see this one in wireshark)
    Sun Mar  6 12:34:38 2011 <0004> gsm48_mm.c:887 new state MM IDLE, normal
service -> wait for RR connection (MM connection)

3.- How must I activate the timestamp in the logs ?

    I'm using:
       //target->print_timestamp = 0;
        target->print_timestamp = 1;
    But i guess that there is an easy way without recompile...

Thanx in advance !!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110306/dac31b81/attachment.htm>

From 775725965 at qq.com  Mon Mar  7 05:49:46 2011
From: 775725965 at qq.com (=?gbk?B?wvPM78rYzfs=?=)
Date: Mon, 7 Mar 2011 13:49:46 +0800
Subject: hi all
Message-ID: <tencent_78E20836379C82906BE67EF8@qq.com>

who tell me the osmocom  .what is it    i say it not to use
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110307/aeefa6bf/attachment.htm>

From xiangfu.z at gmail.com  Mon Mar  7 07:22:11 2011
From: xiangfu.z at gmail.com (Xiangfu Liu)
Date: Mon, 07 Mar 2011 15:22:11 +0800
Subject: hi all
In-Reply-To: <tencent_78E20836379C82906BE67EF8@qq.com>
References: <tencent_78E20836379C82906BE67EF8@qq.com>
Message-ID: <4D7487A3.3020102@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi ????

(better don't use [hi all] in subject, it's meaningless)

I highly advice you read this web page:)
  http://linuxmafia.com/faq/Essays/smart-questions.html#translations
here is the Chinese version:
  http://www.beiww.com/doc/oss/smart-questions.html
you can send Chinese email to me :).

On 03/07/2011 01:49 PM, ???? wrote:
> 
> who tell me the osmocom  .what is it    i say it not to use

quote from http://bb.osmocom.org/trac/
~~~~
Welcome to the OsmocomBB project ?

OsmocomBB is an Free Software / Open Source GSM Baseband software implementation.

It intends to completely replace the need for a proprietary GSM baseband software, such as

    * drivers for the GSM analog and digital baseband (integrated and external) peripherals
    * the GSM phone-side protocol stack, from layer 1 up to layer 3 

In short: By using OsmocomBB on a compatible phone, you are able to make and receive phone calls, send and receive SMS, etc. based on Free Software only.

Over the past 12 months, we've been making very good progress. Most of the hardware drivers have been written, and a relatively complete layer1, layer2 and layer3 exist.

No work has yet been done on any sort of UI on the phone. The only user interface is a telnet-based command line.

To get started, checkout the PreliminaryRequirements and then GettingStarted 
~~~

- -- 
Best Regards
Xiangfu Liu
http://www.openmobilefree.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk10h6IACgkQRRAEFRxkgLSJ5gCfWl89Dmg/XvLwR9bgmitTPpsV
aloAoIzQOwJMbHzeVbmWUsXZ34YXVbIA
=BnP6
-----END PGP SIGNATURE-----



From dburgess at jcis.net  Mon Mar  7 18:49:29 2011
From: dburgess at jcis.net (David A. Burgess)
Date: Mon, 7 Mar 2011 10:49:29 -0800
Subject: SIM-Max Tech's Super-SIM
Message-ID: <3E071D93-78CC-43D4-8830-7334F4C9AC9F@jcis.net>

Hi -

I apologize if this is slightly off topic, but has anyone here used a SIM-MaxTechnology "Super SIM" and its associated USB programmed to generate SIMs with a known A3/A8 and a known Ki?  (I have been trying, but without success.)

-- David





From 246tnt at gmail.com  Mon Mar  7 19:01:20 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Mon, 7 Mar 2011 20:01:20 +0100
Subject: SIM-Max Tech's Super-SIM
In-Reply-To: <3E071D93-78CC-43D4-8830-7334F4C9AC9F@jcis.net>
References: <3E071D93-78CC-43D4-8830-7334F4C9AC9F@jcis.net>
Message-ID: <AANLkTi=PVKkq=jjrJFa3dh=3CJZZXAJMEUvbbwsovZyd@mail.gmail.com>

Hi,


> I apologize if this is slightly off topic, but has anyone here used a SIM-MaxTechnology "Super SIM" and its associated USB programmed to generate SIMs with a known A3/A8 and a known Ki?  (I have been trying, but without success.)

Have you tried pysim ?

http://git.osmocom.org/gitweb?p=pysim.git;a=summary

It's a utility I wrote to deak with those programmable sims.

Cheers,

    Sylvain



From laforge at gnumonks.org  Tue Mar  8 09:40:44 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 8 Mar 2011 10:40:44 +0100
Subject: SIM-Max Tech's Super-SIM
In-Reply-To: <AANLkTi=PVKkq=jjrJFa3dh=3CJZZXAJMEUvbbwsovZyd@mail.gmail.com>
References: <3E071D93-78CC-43D4-8830-7334F4C9AC9F@jcis.net>
	<AANLkTi=PVKkq=jjrJFa3dh=3CJZZXAJMEUvbbwsovZyd@mail.gmail.com>
Message-ID: <20110308094044.GH2980@prithivi.gnumonks.org>

Hi David,

On Mon, Mar 07, 2011 at 08:01:20PM +0100, Sylvain Munaut wrote:

> > I apologize if this is slightly off topic, but has anyone here used a SIM-MaxTechnology "Super SIM" and its associated USB programmed to generate SIMs with a known A3/A8 and a known Ki?  (I have been trying, but without success.)
> 
> Have you tried pysim ?
> 
> http://git.osmocom.org/gitweb?p=pysim.git;a=summary
> 
> It's a utility I wrote to deak with those programmable sims.

Please note that there are various different card types being sold in different
packaging, sometimes even different card types in the same packaging.  Pysim
can program all that we've encountered so far.

Btw: As a coincidence, I just received another 1000-unit batch of 16in1
SuperSIM cards from the chinese supplier that I'm buying from.  I'm happy
to introduce you if you ever need quantities.  Not sure if they are able
to offer it with non-standard print on the plastic, but I'd assume that
would be possible for a surcharge.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From adg at crypto.lo.gy  Mon Mar  7 19:04:39 2011
From: adg at crypto.lo.gy (Alfonso De Gregorio)
Date: Mon, 7 Mar 2011 20:04:39 +0100
Subject: SIM-Max Tech's Super-SIM
In-Reply-To: <3E071D93-78CC-43D4-8830-7334F4C9AC9F@jcis.net>
References: <3E071D93-78CC-43D4-8830-7334F4C9AC9F@jcis.net>
Message-ID: <AANLkTimYNfkaFoUZaMBbW4ujgFnjFtHTgdPi9bPVOhnH@mail.gmail.com>

On Mon, Mar 7, 2011 at 7:49 PM, David A. Burgess <dburgess at jcis.net> wrote:
> Hi -
>
> I apologize if this is slightly off topic, but has anyone here used a SIM-MaxTechnology "Super SIM" and its associated USB programmed to generate SIMs with a known A3/A8 and a known Ki? ?(I have been trying, but without success.)
>
> -- David

On a related note, does anyone have any SIMs for sale, implementing
A3/A8 with COMP128-2, still to be provisioned with its Ki or already
provisioned with a known Ki?

I apologize as well for going a somehow off topic, but the David's
question couldn't be more timely.

Cheers,

alfonso

-- 
? Alfonso De Gregorio,? blogs at http://Plaintext.crypto.lo.gy/



From 246tnt at gmail.com  Mon Mar  7 19:38:29 2011
From: 246tnt at gmail.com (246tnt at gmail.com)
Date: Mon, 07 Mar 2011 19:38:29 +0000
Subject: SIM-Max Tech's Super-SIM
In-Reply-To: <AANLkTimYNfkaFoUZaMBbW4ujgFnjFtHTgdPi9bPVOhnH@mail.gmail.com>
Message-ID: <0023545bdc18e7a258049de9a302@google.com>

> On a related note, does anyone have any SIMs for sale, implementing
> A3/A8 with COMP128-2, still to be provisioned with its Ki or already
> provisioned with a known Ki?

Comp128v2 ?
I don't think so ...

All the cards we have use COMP128 v1, the spec for v2 have not been leaked  
(yet ?).

For those, you best bet is ebay, search for "super sim" / 16-in-1 / "magic  
sim" things like that.
Dealextreme also has some.

If you need more quantity, you can often contact those vendor directly and  
they'll be happy to send you a bunch.
I myself bought a lot directly emailing the guys at magicsim.com

Cheers,

Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110307/f2a7d50d/attachment.htm>

From adg at crypto.lo.gy  Mon Mar  7 20:12:45 2011
From: adg at crypto.lo.gy (Alfonso De Gregorio)
Date: Mon, 7 Mar 2011 21:12:45 +0100
Subject: SIM-Max Tech's Super-SIM
In-Reply-To: <0023545bdc18e7a258049de9a302@google.com>
References: <AANLkTimYNfkaFoUZaMBbW4ujgFnjFtHTgdPi9bPVOhnH@mail.gmail.com>
	<0023545bdc18e7a258049de9a302@google.com>
Message-ID: <AANLkTi=gmzcXjR1dXvgfkVs2=eSbbng-CD4XsTMK9VDG@mail.gmail.com>

Hi Sylvain,

thanks for your prompt reply.

On Mon, Mar 7, 2011 at 8:38 PM,  <246tnt at gmail.com> wrote:
> All the cards we have use COMP128 v1, the spec for v2 have not been leaked
> (yet ?).

Exactly. The specs for the second version(s) of COMP128 operators
ended up to adopt has not leaked. Depending on the actual design of
the algorithm at hand, an oracle may get us closer to understand
something more about this.

I'm not suggesting here the algorithm can be reversed looking to the
image and input quantities. Still...

Cheers,

alfonso



From adg at crypto.lo.gy  Mon Mar  7 22:02:01 2011
From: adg at crypto.lo.gy (Alfonso De Gregorio)
Date: Mon, 7 Mar 2011 23:02:01 +0100
Subject: SIM-Max Tech's Super-SIM
In-Reply-To: <0023545bdc18e7a258049de9a302@google.com>
References: <AANLkTimYNfkaFoUZaMBbW4ujgFnjFtHTgdPi9bPVOhnH@mail.gmail.com>
	<0023545bdc18e7a258049de9a302@google.com>
Message-ID: <AANLkTi=bDh8o1OiL928hNOQyegAp+BRLJGgnuKQRZ84K@mail.gmail.com>

Hi Sylvain,

thanks for your prompt reply.

On Mon, Mar 7, 2011 at 8:38 PM,  <246tnt at gmail.com> wrote:
> All the cards we have use COMP128 v1, the spec for v2 have not been leaked
> (yet ?).

Exactly. The specs for the second version(s) of COMP128 that operators
ended up to adopt have not leaked. Notwithstanding this and depending on
the actual design of the algorithm at hand, an oracle may get us closer to
understanding something more about this.

I'm not suggesting here that the algorithm can be reversed looking at its
images and input quantities. Still...

Cheers,

alfonso


-- 
? Alfonso De Gregorio,? blogs at http://Plaintext.crypto.lo.gy/



From henk.vergonet at gmail.com  Tue Mar  8 14:28:46 2011
From: henk.vergonet at gmail.com (Henk)
Date: Tue, 08 Mar 2011 15:28:46 +0100
Subject: SIM-Max Tech's Super-SIM
Message-ID: <bkopuwcpsjwpki057950sxgs.1299594526923@email.android.com>

Actually comp128-2 has a 54bit Kc it seems.

246tnt at gmail.comschreef:

>> On a related note, does anyone have any SIMs for sale, implementing
>> A3/A8 with COMP128-2, still to be provisioned with its Ki or already
>> provisioned with a known Ki?
>
>Comp128v2 ?
>I don't think so ...
>
>All the cards we have use COMP128 v1, the spec for v2 have not been leaked  
>(yet ?).
>
>For those, you best bet is ebay, search for "super sim" / 16-in-1 / "magic  
>sim" things like that.
>Dealextreme also has some.
>
>If you need more quantity, you can often contact those vendor directly and  
>they'll be happy to send you a bunch.
>I myself bought a lot directly emailing the guys at magicsim.com
>
>Cheers,
>
>Sylvain

From adg at crypto.lo.gy  Tue Mar  8 15:31:47 2011
From: adg at crypto.lo.gy (Alfonso De Gregorio)
Date: Tue, 8 Mar 2011 16:31:47 +0100
Subject: SIM-Max Tech's Super-SIM
In-Reply-To: <bkopuwcpsjwpki057950sxgs.1299594526923@email.android.com>
References: <bkopuwcpsjwpki057950sxgs.1299594526923@email.android.com>
Message-ID: <AANLkTi=5wCHzTE_Q7Y631o2NWeSPESXiimzjpd22amz0@mail.gmail.com>

On Tue, Mar 8, 2011 at 3:28 PM, Henk <henk.vergonet at gmail.com> wrote:
> Actually comp128-2 has a 54bit Kc it seems.

Have you observed a COMP128-2 implementation returning a 54bit long
Kc?, or have you heard about this from somebody else?
Can you please disclose more about the SIM model and the operator
running this A3/A8 implementation?

One more weakened key derivation function (after the first version)
would be interesting per se. Still, it would be even more interesting
to give a closer look at this obscure cipher we carry in our
pockets...

A programmable SIM with COMP128v2 would be valuable for a project I'd
like to contribute.

Cheers,

alfonso


> 246tnt at gmail.comschreef:
>
>>> On a related note, does anyone have any SIMs for sale, implementing
>>> A3/A8 with COMP128-2, still to be provisioned with its Ki or already
>>> provisioned with a known Ki?
>>
>>Comp128v2 ?
>>I don't think so ...
>>
>>All the cards we have use COMP128 v1, the spec for v2 have not been leaked
>>(yet ?).
>>
>>For those, you best bet is ebay, search for "super sim" / 16-in-1 / "magic
>>sim" things like that.
>>Dealextreme also has some.
>>
>>If you need more quantity, you can often contact those vendor directly and
>>they'll be happy to send you a bunch.
>>I myself bought a lot directly emailing the guys at magicsim.com
>>
>>Cheers,
>>
>>Sylvain
>



--



From mad at auth.se  Tue Mar  8 17:01:43 2011
From: mad at auth.se (Mad)
Date: Tue, 08 Mar 2011 18:01:43 +0100
Subject: SIM-Max Tech's Super-SIM
In-Reply-To: <AANLkTi=5wCHzTE_Q7Y631o2NWeSPESXiimzjpd22amz0@mail.gmail.com>
References: <bkopuwcpsjwpki057950sxgs.1299594526923@email.android.com>
	<AANLkTi=5wCHzTE_Q7Y631o2NWeSPESXiimzjpd22amz0@mail.gmail.com>
Message-ID: <b48bd1dcffe92b1ee3948cab98e66619@auth.se>

 On Tue, 8 Mar 2011 16:31:47 +0100, Alfonso De Gregorio wrote:
>> Actually comp128-2 has a 54bit Kc it seems.
>
> Have you observed a COMP128-2 implementation returning a 54bit long
> Kc?, or have you heard about this from somebody else?
> Can you please disclose more about the SIM model and the operator
> running this A3/A8 implementation?

 Interesting question, how do we know if it's comp128-2 what is being
 used by a specific operator?
 They can use whatever algo they want - or their equipment vendor 
 provides
 - in their sims and auth infrastructure producing deliberately weakened
 Kcs.

>
> One more weakened key derivation function (after the first version)
> would be interesting per se. Still, it would be even more interesting
> to give a closer look at this obscure cipher we carry in our
> pockets...
>

 No question, there still are given out sims weakening the anyway broken
 a5/1.
 Interestingly I observed that operators have mixed occurrence of weak 
 for
 one and non-weak Kcs for another sim.
 Another possibility is that they are able to determine that for all 
 sims
 by choice of the RAND the network sends. So some people, contract-wise,
 phone-wise or regions could be easier tapped than others.
 But it's just speculation...

 The most promising approach after (really) good cryptologists looking 
 at
 in- and output is to open up and grinding down a sim chip and taking
 pictures to reconstruct its logic, as it has been done with mifare etc.
 Aren't there people reading this who are experienced in the latter?

 Regards,
   Mad



From adg at crypto.lo.gy  Tue Mar  8 19:09:55 2011
From: adg at crypto.lo.gy (Alfonso De Gregorio)
Date: Tue, 8 Mar 2011 20:09:55 +0100
Subject: SIM-Max Tech's Super-SIM
In-Reply-To: <b48bd1dcffe92b1ee3948cab98e66619@auth.se>
References: <bkopuwcpsjwpki057950sxgs.1299594526923@email.android.com>
	<AANLkTi=5wCHzTE_Q7Y631o2NWeSPESXiimzjpd22amz0@mail.gmail.com>
	<b48bd1dcffe92b1ee3948cab98e66619@auth.se>
Message-ID: <AANLkTimrApXF10wHpws44Q1=ph6nZSWG4r9-jbzo5BEM@mail.gmail.com>

On Tue, Mar 8, 2011 at 6:01 PM, Mad <mad at auth.se> wrote:
> On Tue, 8 Mar 2011 16:31:47 +0100, Alfonso De Gregorio wrote:
>>>
>>> Actually comp128-2 has a 54bit Kc it seems.
>>
>> Have you observed a COMP128-2 implementation returning a 54bit long
>> Kc?, or have you heard about this from somebody else?
>> Can you please disclose more about the SIM model and the operator
>> running this A3/A8 implementation?
>
> Interesting question, how do we know if it's comp128-2 what is being
> used by a specific operator?

You need to gain access to EFkey. In theory access to this file should
be forbidden. Yet, it already happened in the past to observe failures
in the way the access control mechanism have been engineered - I'd
love to have with me a link to a research about this, but I'm on the
move and can't find it at the moment.

With the card provisioning, operators store in EFkey: the
authentication algorithm identifier, the key value, a key mask, and an
integrity checksum.

The file format is defined by the manufacturer and varies from model to model.

Looking to the GemXplore 3G reference manual is possible to know that
Gemalto assigns the following algorithm identifiers:

COMP128_V1    0x0040
COMP128_V2    0x00F8
COMP128_V3    0x0044

and stores the EFKey quantities according to the following format:

byte# description
1-2      Algo ID of the algorithm to use
3-18     Key value
19-34    Key mask value
35-36    Integrity checksum =( SUM(byte 1? byte 34) XOR FF)(*)


Access to Ki, via other means, would not be sufficient to distinguish
(by keying a reference implementation) between v2 and v3 of COMP128,
unless the SIM card support only one of them. All other authentication
algorithm in use on second generation networks are public or leaked in
the past, namely: COMP128, Milenage 2G, CAVE, DES, 3DES, XOR.


> They can use whatever algo they want - or their equipment vendor provides
> - in their sims and auth infrastructure producing deliberately weakened
> Kcs.

Yes, they can use whatever key derivation they want and deploy in
their SIM cards and core network, indeed. As a matter of fact,
COMP128-v1 itself was not intended to be prescriptive. Telcos were
expected to select their A3/A8 algorithm of choice. Of course they
didn't, as incentives were no incentives to select anything different
from the algorithm considered during the standardization efforts.

>> One more weakened key derivation function (after the first version)
>> would be interesting per se. Still, it would be even more interesting
>> to give a closer look at this obscure cipher we carry in our
>> pockets...
>>
>
> No question, there still are given out sims weakening the anyway broken
> a5/1.
> Interestingly I observed that operators have mixed occurrence of weak for
> one and non-weak Kcs for another sim.
> Another possibility is that they are able to determine that for all sims
> by choice of the RAND the network sends. So some people, contract-wise,
> phone-wise or regions could be easier tapped than others.
> But it's just speculation...
>
> The most promising approach after (really) good cryptologists looking at
> in- and output is to open up and grinding down a sim chip and taking
> pictures to reconstruct its logic, as it has been done with mifare etc.
> Aren't there people reading this who are experienced in the latter?

Some alternatives exist to the approaches outlined above. But we would
need a programmable smart card with support for COMP128-v2.
I've found online some resellers and integrators I'd love to inquire.
I'll do it, when I have time.

>> Regards,
> ?Mad
>
>

Cheers,

alfonso

-- 
  Alfonso De Gregorio
  BeeWise - Security Event Futures - http://beewise.org/



From mad at auth.se  Tue Mar 15 15:22:59 2011
From: mad at auth.se (Mad)
Date: Tue, 15 Mar 2011 16:22:59 +0100
Subject: SIM-Max Tech's Super-SIM
In-Reply-To: <AANLkTimrApXF10wHpws44Q1=ph6nZSWG4r9-jbzo5BEM@mail.gmail.com>
References: <bkopuwcpsjwpki057950sxgs.1299594526923@email.android.com>
	<AANLkTi=5wCHzTE_Q7Y631o2NWeSPESXiimzjpd22amz0@mail.gmail.com>
	<b48bd1dcffe92b1ee3948cab98e66619@auth.se>
	<AANLkTimrApXF10wHpws44Q1=ph6nZSWG4r9-jbzo5BEM@mail.gmail.com>
Message-ID: <423f693750ce37a31a56ec085e894d77@auth.se>

 On Tue, 8 Mar 2011 20:09:55 +0100, Alfonso De Gregorio wrote:
>
> You need to gain access to EFkey. In theory access to this file 
> should
> be forbidden. Yet, it already happened in the past to observe 
> failures
> in the way the access control mechanism have been engineered - I'd
> love to have with me a link to a research about this, but I'm on the
> move and can't find it at the moment.
>

 That's quite interesting, because from what I knew by now is that you 
 have
 to do a - proprietary but known for some cards - ADM code verify to 
 read or
 write to that file.

 Would be nice if you could post this if you get hold of it again or if
 you remember some keywords like author or organization etc., so we have 
 a
 chance finding it.


 Regards,
   Mad
 



From henk.vergonet at gmail.com  Wed Mar  9 20:38:32 2011
From: henk.vergonet at gmail.com (Henk)
Date: Wed, 9 Mar 2011 21:38:32 +0100
Subject: SIM-Max Tech's Super-SIM
In-Reply-To: <AANLkTi=5wCHzTE_Q7Y631o2NWeSPESXiimzjpd22amz0@mail.gmail.com>
References: <bkopuwcpsjwpki057950sxgs.1299594526923@email.android.com>
	<AANLkTi=5wCHzTE_Q7Y631o2NWeSPESXiimzjpd22amz0@mail.gmail.com>
Message-ID: <AANLkTinO7d7tPo52u7sTF4KhR=n_fPnNkfsfZTx6uFwK@mail.gmail.com>

On Tue, Mar 8, 2011 at 4:31 PM, Alfonso De Gregorio wrote:
> On Tue, Mar 8, 2011 at 3:28 PM, Henk wrote:
>> Actually comp128-2 has a 54bit Kc it seems.
>
> Have you observed a COMP128-2 implementation returning a 54bit long
> Kc?, or have you heard about this from somebody else?
> Can you please disclose more about the SIM model and the operator
> running this A3/A8 implementation?
>

I found it in a some vendor related 3G spec some while ago, can't
remember which one.

After some googling I found the reference below, which also confirm a
Kc of 54 bits, unfortunately I don't have access to the algorithm.
This seems to indicate a completely new algorithm, some others suggest
its a "patched" version of comp128.

- henk

"Quirke (2004). Security in the GSM system."
...
Implementations of A3, A8

Although the design of the GSM system allows an operator to choose any
algorithm they
like for A3 & A8, many decided on the one that was developed in secret
by the GSM
association, COMP128.

COMP128 eventually ended up in public knowledge due to a combination
of reverse engineering and leaked documents, and serious flaws were
discovered (as discussed below).

Some GSM operators have moved to a newer A3/A8 implementation, COMP128-2, a
completely new algorithm which was also developed in secret. This
algorithm for now
seems to have addressed the faults of the COMP128 algorithm, although
since it has yet
to come under public scrutiny it may potentially be discovered via
reverse-engineering
and any possible flaws could be learned.

Finally, the COMP128-3 algorithm can also be used, it is simply the COMP128-2
algorithm, however all 64-bits of the Kc are generated, allowing
maximal possible
strength from the A5 ciphering algorithm (COMP128-2 still sets the 10
rightmost bits of
the Kc to 0), deliberately weakening the A5 ciphering.
?



From adg at crypto.lo.gy  Wed Mar  9 20:53:42 2011
From: adg at crypto.lo.gy (Alfonso De Gregorio)
Date: Wed, 9 Mar 2011 21:53:42 +0100
Subject: SIM-Max Tech's Super-SIM
In-Reply-To: <AANLkTinO7d7tPo52u7sTF4KhR=n_fPnNkfsfZTx6uFwK@mail.gmail.com>
References: <bkopuwcpsjwpki057950sxgs.1299594526923@email.android.com>
	<AANLkTi=5wCHzTE_Q7Y631o2NWeSPESXiimzjpd22amz0@mail.gmail.com>
	<AANLkTinO7d7tPo52u7sTF4KhR=n_fPnNkfsfZTx6uFwK@mail.gmail.com>
Message-ID: <AANLkTi=buGE8VSw+wOejyr-im253bNAbUMWCJXVkraA8@mail.gmail.com>

On Wed, Mar 9, 2011 at 9:38 PM, Henk <henk.vergonet at gmail.com> wrote:
> On Tue, Mar 8, 2011 at 4:31 PM, Alfonso De Gregorio wrote:
>> On Tue, Mar 8, 2011 at 3:28 PM, Henk wrote:
>>> Actually comp128-2 has a 54bit Kc it seems.
>>
>> Have you observed a COMP128-2 implementation returning a 54bit long
>> Kc?, or have you heard about this from somebody else?
>> Can you please disclose more about the SIM model and the operator
>> running this A3/A8 implementation?
>>
>
> I found it in a some vendor related 3G spec some while ago, can't
> remember which one.
>
> After some googling I found the reference below, which also confirm a
> Kc of 54 bits, unfortunately I don't have access to the algorithm.
> This seems to indicate a completely new algorithm, some others suggest
> its a "patched" version of comp128.
>
> - henk

Thanks for the reference below. I didn't figured out before 10bits are
stuck at zero also with the v2 of COMP128.

Cheers,

alfonso

> "Quirke (2004). Security in the GSM system."
> ...
> Implementations of A3, A8
>
> Although the design of the GSM system allows an operator to choose any
> algorithm they
> like for A3 & A8, many decided on the one that was developed in secret
> by the GSM
> association, COMP128.
>
> COMP128 eventually ended up in public knowledge due to a combination
> of reverse engineering and leaked documents, and serious flaws were
> discovered (as discussed below).
>
> Some GSM operators have moved to a newer A3/A8 implementation, COMP128-2, a
> completely new algorithm which was also developed in secret. This
> algorithm for now
> seems to have addressed the faults of the COMP128 algorithm, although
> since it has yet
> to come under public scrutiny it may potentially be discovered via
> reverse-engineering
> and any possible flaws could be learned.
>
> Finally, the COMP128-3 algorithm can also be used, it is simply the COMP128-2
> algorithm, however all 64-bits of the Kc are generated, allowing
> maximal possible
> strength from the A5 ciphering algorithm (COMP128-2 still sets the 10
> rightmost bits of
> the Kc to 0), deliberately weakening the A5 ciphering.
> ?



-- 
? Alfonso De Gregorio
  BeeWise - Security Event Futures - http://beewise.org/



From blassmegod at yahoo.com  Tue Mar  8 13:51:55 2011
From: blassmegod at yahoo.com (burebista)
Date: Tue, 8 Mar 2011 05:51:55 -0800 (PST)
Subject: how to decompile a linux kernel zImage
Message-ID: <79812.64953.qm@web130220.mail.mud.yahoo.com>

Does anybody know how to decompile a linux kernel zImage file, I need to extract 
some info about MT6516 processor from there. I successfully extracted the 
.config make file, but want to see other parameters too.
Thanks,



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110308/17c6c044/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mt6516.config.tar.gz
Type: application/x-gzip
Size: 10292 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110308/17c6c044/attachment.bin>

From laforge at gnumonks.org  Tue Mar  8 16:31:20 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 8 Mar 2011 17:31:20 +0100
Subject: how to decompile a linux kernel zImage
In-Reply-To: <79812.64953.qm@web130220.mail.mud.yahoo.com>
References: <79812.64953.qm@web130220.mail.mud.yahoo.com>
Message-ID: <20110308163120.GP2980@prithivi.gnumonks.org>

On Tue, Mar 08, 2011 at 05:51:55AM -0800, burebista wrote:
> Does anybody know how to decompile a linux kernel zImage file, I need to extract 
> some info about MT6516 processor from there. I successfully extracted the 
> .config make file, but want to see other parameters too.

why don't you simply contact the manufacturer of the phone?  Which exact
vendor + model is that?  As the Linux kernel is GPL licensed, they _have to_
release the source code to it.

It is not MTK who needs to release it, but the phone manufacturer.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From mforce2 at gmail.com  Tue Mar  8 16:44:38 2011
From: mforce2 at gmail.com (Marius Cirsta)
Date: Tue, 8 Mar 2011 09:44:38 -0700
Subject: how to decompile a linux kernel zImage
In-Reply-To: <20110308163120.GP2980@prithivi.gnumonks.org>
References: <79812.64953.qm@web130220.mail.mud.yahoo.com>
	<20110308163120.GP2980@prithivi.gnumonks.org>
Message-ID: <AANLkTi=e26k-JOhnevRgWunqLDyEggkoSgZ+rpUKwB2Z@mail.gmail.com>

 From what I know the manufacturer is a no-name Chinese one just like
in the case of so many Wondermedia tablets. They don't really care
about the GPL so unless Mediatek releases the kernel there's not much
chance in getting it. If Wondermedia wouldn't have been nice and
hadn't released the WM8505 kernel we could have still waited for Eken
or some others to release do so. Btw thanks for that Harald.

 I agree that Mediatek doesn't have to but it would be nice of them,
maybe someone could ask nicely.

Other then that the best way to look in a binary that I know of is
with IDA Pro ... That and the datasheets should help.

On Tue, Mar 8, 2011 at 9:31 AM, Harald Welte <laforge at gnumonks.org> wrote:
> On Tue, Mar 08, 2011 at 05:51:55AM -0800, burebista wrote:
>> Does anybody know how to decompile a linux kernel zImage file, I need to extract
>> some info about MT6516 processor from there. I successfully extracted the
>> .config make file, but want to see other parameters too.
>
> why don't you simply contact the manufacturer of the phone? ?Which exact
> vendor + model is that? ?As the Linux kernel is GPL licensed, they _have to_
> release the source code to it.
>
> It is not MTK who needs to release it, but the phone manufacturer.
>
> --
> - Harald Welte <laforge at gnumonks.org> ? ? ? ? ? http://laforge.gnumonks.org/
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?(ETSI EN 300 175-7 Ch. A6)
>
>



From laforge at gnumonks.org  Tue Mar  8 17:24:08 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 8 Mar 2011 18:24:08 +0100
Subject: how to decompile a linux kernel zImage
In-Reply-To: <AANLkTi=e26k-JOhnevRgWunqLDyEggkoSgZ+rpUKwB2Z@mail.gmail.com>
References: <79812.64953.qm@web130220.mail.mud.yahoo.com>
	<20110308163120.GP2980@prithivi.gnumonks.org>
	<AANLkTi=e26k-JOhnevRgWunqLDyEggkoSgZ+rpUKwB2Z@mail.gmail.com>
Message-ID: <20110308172408.GQ2980@prithivi.gnumonks.org>

The original poster previously referred to Gigabyte as the manfuacutrer/brand.

If that is the case, I have pre-existing contacts to Gigabyte legal due to
past gpl-violations.org work.  The same is true for pretty much all of the
large Taiwanese brand names.

So if somebody can provide me actual evidence _whcih_ vendor is selling _which_
particular model without providing source code to the GPL licensed components,
I think chances are pretty good that a (non-legal) complaint that I send
to the respective legal department has the desired impact.

Talking to MTK: I could do it.  But past experience shows that they are
unlikely to do something beyond their obligations.  But I still think
the phone makers should be the first "target", before asknig MTK to do
something that they are not required to.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From blassmegod at yahoo.com  Tue Mar  8 18:42:43 2011
From: blassmegod at yahoo.com (BlassMeGod)
Date: Tue, 8 Mar 2011 10:42:43 -0800 (PST)
Subject: how to decompile a linux kernel zImage
Message-ID: <817161.49420.qm@web130224.mail.mud.yahoo.com>

The phone is a Star A3000 made in China, but i can't find their website, or the manufacturer, i have only an Android ROM downloaded from a forum, and from there I extracted the compiled kernel, and now I'm trying to find more info, but I don't know ho made this phone, my phone is Gigabyte Gsmart S1205 with the MT6516 processor, but runs WM6.5 and I want to make it run Linux or Android, I know that it wont be easy, but it keeps my mind occupied. 


From: "Harald Welte" <laforge at gnumonks.org> 
To: "burebista" <blassmegod at yahoo.com> 
Cc: baseband-devel at lists.osmocom.org 
Sent: Tuesday, March 8, 2011 6:31:20 PM 
Subject: Re: how to decompile a linux kernel zImage 

On Tue, Mar 08, 2011 at 05:51:55AM -0800, burebista wrote: 
> Does anybody know how to decompile a linux kernel zImage file, I need to extract 
> some info about MT6516 processor from there. I successfully extracted the 
> .config make file, but want to see other parameters too. 

why don't you simply contact the manufacturer of the phone? Which exact 
vendor + model is that? As the Linux kernel is GPL licensed, they _have to_ 
release the source code to it. 

It is not MTK who needs to release it, but the phone manufacturer. 

-- 
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/ 
============================================================================ 
"Privacy in residential applications is a desirable marketing option." 
(ETSI EN 300 175-7 Ch. A6) 



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110308/81df39bf/attachment.htm>

From blassmegod at yahoo.com  Wed Mar  9 06:54:10 2011
From: blassmegod at yahoo.com (burebista)
Date: Tue, 8 Mar 2011 22:54:10 -0800 (PST)
Subject: how to decompile a linux kernel zImage
Message-ID: <158699.62230.qm@web130202.mail.mud.yahoo.com>

Hy, I have the datasheet, but it will get me a while before I will finish to 
read it (1500 pages), but first i thought that would be great if I can get as 
much already done data from the compiled kernel, I will see if I can manage to 
decompile it, maybe get the make file off it. I have sent 3 or 4 email to MTK 
with no response, Gigabyte answered me and they said that they don't plan to 
make an Android or Linux ROM form GSmart S1205 (witch like I said runs on 
Windows Mobile 6.5); but for the Star A3000 I'm still looking for the 
manufacturer, so, if I find it I will post the name here and I will try to ask 
them nicely if they can give it to me too.
Thanks to all,
Getting back to decompiling and looking at hex...



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110308/6f9e5943/attachment.htm>

From blassmegod at yahoo.com  Wed Mar  9 09:07:35 2011
From: blassmegod at yahoo.com (burebista)
Date: Wed, 9 Mar 2011 01:07:35 -0800 (PST)
Subject: how to decompile a linux kernel zImage
Message-ID: <727447.25377.qm@web130210.mail.mud.yahoo.com>

Found who is the manufacturer (but didn't find a website or email address) SZ 
PXHT  Inc., I attached a picture from an Star A3000 sticker. Hope this helps.



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110309/fe9ac051/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: StarA3000-1.jpg
Type: image/jpeg
Size: 64103 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110309/fe9ac051/attachment.jpg>

From blassmegod at yahoo.com  Fri Mar 11 10:20:25 2011
From: blassmegod at yahoo.com (burebista)
Date: Fri, 11 Mar 2011 02:20:25 -0800 (PST)
Subject: how to decompile a linux kernel zImage
Message-ID: <604340.22659.qm@web130220.mail.mud.yahoo.com>

I found another phone witch looks like it runs Android OS on a MT6516 processor, 
you can find it here 
http://www.voldltd.com/sdp/1100371/4/pd-5258987/7588204-2080998/H6_Android_2_1_OS_Wifi_Analog_TV_Java_Trackball_Sm.html,
 it's a VOLD VD-H6. I send them an email but for now no response, I haven't 
found a ROM to look into it, but the manufacturer is "VOLD Company Limited" and 
on their website it says that is Android on MT6516, so they need to have the 
driver for it.


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110311/6287c62c/attachment.htm>

From zhengfanf at hotmail.com  Wed Mar  9 15:53:53 2011
From: zhengfanf at hotmail.com (zhengfanf)
Date: Wed, 9 Mar 2011 23:53:53 +0800
Subject: I wanna make sure why LOCATION UPDATE REQUEST is always faild
Message-ID: <BLU0-SMTP20602BAD1847A94C3D63C3BBEC90@phx.gbl>



hello, when i run osmocom i meet a problem that LOCATION UPDATE REQUEST is always faild,
the details are in the following:

1, my hardware environment: 
a Moto C118 mobile;
a cheap RS232 com port to jack port data cable (unkown chip);
a USB2 to RS232 converter using FTDI chip;
i5 CPU with GIGABYTE motherbord running with Ubuntu 9.04;

2, i run the command osmocon, mobile, and telnet as below in seprate terminals in order.
./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/layer1.compalram.bin 
./mobile -i 127.0.0.1
telnet localhost 4247 
en
sim reader 1

3, after that osmocom is working, but things doesn't happed what i wish, LOCATION UPDATE REQUEST is always faild so that the phone can not make calls.
-in command mobile running terminial i grubbed the following log:

"
<0001> gsm48_rr.c:2006 PAGING ignored, we are not camping.
writing msgb to gsmtap fd: Connection refused
<0001> gsm48_rr.c:694 timer T3126 has fired
<000d> gsm48_rr.c:699 Requesting channel failed
<0001> gsm48_rr.c:363 new state connection pending -> idle
<0003> gsm322.c:3318 (ms 1) Event 'EVENT_RET_IDLE' for Cell selection in state 'C3 camped normally'
<0003> gsm322.c:2889 Selecting frequency 22. after LOC.UPD.
<0003> gsm322.c:251 Sync to ARFCN=22 rxlev=-56 (Sysinfo, ccch mode NON-COMB)
<0003> gsm322.c:540 new state 'C3 camped normally' -> 'C3 camped normally'
<0004> gsm48_mm.c:3695 (ms 1) Received 'RR_REL_IND' from RR in state wait for RR connection (location updating)
<0004> gsm48_mm.c:2589 RR link released after loc. upd.
<000d> gsm48_mm.c:2533 Location update failed
<000d> gsm48_mm.c:2543 Try location update later
<0004> gsm48_mm.c:2545 Loc. upd. failed, retry #0
<0004> gsm48_mm.c:391 starting T3211 (loc. upd. retry delay) with 15.0 seconds
<0004> gsm48_mm.c:4083 (ms 1) Received 'MM_EVENT_CELL_SELECTED' event in state wait for RR connection (location updating)
<0004> gsm48_mm.c:1055 We are in registered LAI as returning to MM IDLE
<0004> gsm48_mm.c:892 new state wait for RR connection (location updating) -> MM IDLE, normal service
<0003> gsm322.c:2433 Channel synched. (ARFCN=22, snr=13, BSIC=10)
<0001> gsm322.c:2460 using DSC of 90
<0003> gsm48_rr.c:4548 Channel provides data.
writing msgb to gsmtap fd: Connection refused
writing msgb to gsmtap fd: Connection refused
<0001> gsm48_rr.c:609 MON: f=22 lev=-52 snr= 0 ber= 62 LAI=460 00 11a5 ID=629a
writing msgb to gsmtap fd: Connection refused
<0001> gsm48_rr.c:2265 IMMEDIATE ASSIGNMENT:
<0001> gsm48_rr.c:2286  (ta 1/553m ra 0x7f chan_nr 0x0e ARFCN 22 TS 6 SS 0 TSC 2)
<0001> gsm48_rr.c:2291 Not for us, no request.
"

-it shows that LOCATION UPDATE REQUEST is faild and it will be retry, and use command "OsmocomBB# show ms" also can find that the mobile is trying hard to get location update successfully:

"
OsmocomBB# show ms
MS '1' is up, MM connection active
  IMEI: 000000000000000
     IMEISV: 0000000000000000
     IMEI generation: fixed
  automatic network selection state: A1 trying RPLMN
  cell selection state: C3 camped normally
  radio ressource layer state: connection pending
  mobility management layer state: wait for RR connection (location updating)
OsmocomBB# show ms
MS '1' is up, service is normal
  IMEI: 000000000000000
     IMEISV: 0000000000000000
     IMEI generation: fixed
  automatic network selection state: A1 trying RPLMN
  cell selection state: C3 camped normally (ARFCN 22)
  radio ressource layer state: idle
  mobility management layer state: MM idle, normal service
OsmocomBB# show ms
MS '1' is up, service is normal
  IMEI: 000000000000000
     IMEISV: 0000000000000000
     IMEI generation: fixed
  automatic network selection state: A1 trying RPLMN
  cell selection state: C3 camped normally (ARFCN 22)
  radio ressource layer state: idle
  mobility management layer state: MM idle, normal service
OsmocomBB# show ms
MS '1' is up, MM connection active
  IMEI: 000000000000000
     IMEISV: 0000000000000000
     IMEI generation: fixed
  automatic network selection state: A1 trying RPLMN
  cell selection state: C3 camped normally
  radio ressource layer state: connection pending
  mobility management layer state: wait for RR connection (location updating)
"

-and in command osmocon terminal, i found the log may show the  LOCATION UPDATE REQUEST faild reasons.

"
Received PROMPT1 from phone, responding with CMD
read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): file_size=53948, hdr_len=4, dnload_len=53955
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/53955)
handle_write(): 4096 bytes (8192/53955)
handle_write(): 4096 bytes (12288/53955)
handle_write(): 4096 bytes (16384/53955)
handle_write(): 4096 bytes (20480/53955)
handle_write(): 4096 bytes (24576/53955)
handle_write(): 4096 bytes (28672/53955)
handle_write(): 4096 bytes (32768/53955)
handle_write(): 4096 bytes (36864/53955)
handle_write(): 4096 bytes (40960/53955)
handle_write(): 4096 bytes (45056/53955)
handle_write(): 4096 bytes (49152/53955)
handle_write(): 4096 bytes (53248/53955)
handle_write(): 707 bytes (53955/53955)
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: 41  A
got 1 bytes from modem, data looks like: 03  .
got 1 bytes from modem, data looks like: 42  B
Received DOWNLOAD ACK from phone, your code is running now!
OSMOCOM Layer 1 (revision osmocon_v0.0.0-757-gc4483bf-modified)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: 71c60b1d89021625
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
======================================================================
Power up simcard:
THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!!
Assert DSP into Reset
Releasing DSP from Reset
Setting some dsp_api.ndb values
Setting API NDB parameters
DSP Download Status: 0x0001
DSP API Version: 0x0000 0x0000
Finishing download phase
DSP Download Status: 0x0002
DSP API Version: 0x3606 0x0000
LOST 1634!
"

"
SB2 (2663816:2): TOA=   26, Power= -60dBm, Angle=  132Hz
=> SB 0x003cf629: BSIC=10 fn=1331917(1004/15/ 1)=> DSP reports SB in bit that is 965199799 bits in the future?!?
Synchronize_TDMA
=> DSP reports FB in bit that is 965199776 bits in the future?!?
LOST 1908!
nb_cmd(0) and rxnb.msg != NULLL1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0a, offset=8 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0a, offset=236 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0d, offset=248 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x06, offset=240 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x04, offset=217 combined=0)
L1CTL_DM_REL_REQL1CTL_RESET_REQ: FULL!L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=22, flags=0x7)
Starting FCCH RecognitionEMPTY
FB0 (1334018:5): TOA= 5040, Power= -57dBm, Angle= 2049Hz
FB1 (1334028:8): TOA= 8755, Power= -57dBm, Angle=  223Hz
  fn_offset=1334026 (fn=1334028 + attempt=8 + ntdma = 6)m  delay=8 (fn_offset=1334026 + 11 - fn=1334028 - 1
  scheduling next FB/SB detection task with delay 8
=>FB @ FNR 1334026 fn_offset=1334026 qbits=4836
Synchronize_TDMA
LOST 3717!
SB1 (2668059:1): TOA=   27, Power= -59dBm, Angle=   -9Hz
=> SB 0x0111f729: BSIC=10 fn=1334038(1006/ 4/31)=> DSP reports SB in bit that is 959894800 bits in the future?!?
Synchronize_TDMA
=> DSP reports FB in bit that is 959894777 bits in the future?!?
LOST 1909!
nb_cmd(0) and rxnb.msg != NULLL1CTL_RESET_REQ: FULL!EMPTY
L1CTL_FBSB_REQ (arfcn=22, flags=0x7)
Starting FCCH RecognitionFB0 (1337271:8): TOA= 9312, Power= -56dBm, Angle=-3405Hz
FB1 (1337282:9): TOA= 9999, Power= -56dBm, Angle= 5216Hz
  fn_offset=1337280 (fn=1337282 + attempt=9 + ntdma = 7)m  delay=8 (fn_offset=1337280 + 11 - fn=1337282 - 1
  scheduling next FB/SB detection task with delay 8
FB1 (1337302:11): TOA=12507, Power= -56dBm, Angle=  431Hz
  fn_offset=1337300 (fn=1337302 + attempt=11 + ntdma = 9)m  delay=8 (fn_offset=1337300 + 11 - fn=1337302 - 1
  scheduling next FB/SB detection task with delay 8
=>FB @ FNR 1337300 fn_offset=1337300 qbits=4844
Synchronize_TDMA
LOST 3719!
SB1 (2674604:1): TOA=   24, Power= -56dBm, Angle=  263Hz
=> SB 0x000af829: BSIC=10 fn=1337312(1008/ 2/41)=> DSP reports SB in bit that is 951713547 bits in the future?!?
Synchronize_TDMA
=> DSP reports FB in bit that is 951713524 bits in the future?!?
LOST 1905!
nb_cmd(0) and rxnb.msg != NULLL1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0f, offset=13 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0a, offset=233 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0a, offset=237 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x0e, offset=240 combined=0)
L1CTL_PARAM_REQ (ta=0, tx_power=5)
L1CTL_RACH_REQ (ra=0x04, offset=241 combined=0)
L1CTL_DM_REL_REQL1CTL_RESET_REQ: FULL!L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=22, flags=0x7)
Starting FCCH RecognitionFB0 (1339424:4): TOA= 3792, Power= -53dBm, Angle= 2044Hz
FB1 (1339434:8): TOA= 8755, Power= -52dBm, Angle=  295Hz
  fn_offset=1339432 (fn=1339434 + attempt=8 + ntdma = 6)m  delay=8 (fn_offset=1339432 + 11 - fn=1339434 - 1
  scheduling next FB/SB detection task with delay 8
=>FB @ FNR 1339432 fn_offset=1339432 qbits=4836
Synchronize_TDMA
LOST 3717!
"

-i found the value of LOST is too big, and i tried to look for reasons in codes and found  function "check_lost_frame()" below (in sync.c, lines 180 to 205). After read this code, i think it's delays of physical layer caused so so much LOST value.

"
/* Lost TDMA interrupt detection.  This works by starting a hardware timer
 * that is clocked by the same master clock source (VCTCXO).  We expect
 * 1875 timer ticks in the duration of a TDMA frame (5000 qbits / 1250 bits) */
/* Timer for detecting lost IRQ */
#define TIMER_TICKS_PER_TDMA 1875
#define TIMER_TICK_JITTER 1
static int last_timestamp;
static inline void check_lost_frame(void)
{
int diff, timestamp = hwtimer_read(1);
if (last_timestamp < timestamp)
last_timestamp += (4*TIMER_TICKS_PER_TDMA);
diff = last_timestamp - timestamp;
/* allow for a bit of jitter */
if (diff < TIMER_TICKS_PER_TDMA - TIMER_TICK_JITTER ||
    diff > TIMER_TICKS_PER_TDMA + TIMER_TICK_JITTER)
printf("LOST %d!\n", diff);
last_timestamp = timestamp;
}
"

4, here, i want some help to figure out whether physical delays caused big LOST value, and big LOST value caused LOCATION UPDATE REQUEST failed?
if it's the problem of the physical layer, i want to make sure which part should be held responsible:
-is that the cheap RS232 com port to jack port data cable caused the delays?
-or is the USB2 to RS232 converter caused the delays?
-or is that some bugs in layer1.compalram.bin caused the delays?
i really want some experienced engineer to help me fix up the problem.

Thanks!
Best Regards!
zheng


2011-03-09 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110309/e3a29411/attachment.htm>

From 246tnt at gmail.com  Wed Mar  9 16:11:52 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Wed, 9 Mar 2011 17:11:52 +0100
Subject: I wanna make sure why LOCATION UPDATE REQUEST is always faild
In-Reply-To: <BLU0-SMTP20602BAD1847A94C3D63C3BBEC90@phx.gbl>
References: <BLU0-SMTP20602BAD1847A94C3D63C3BBEC90@phx.gbl>
Message-ID: <AANLkTi=-rSST=gjvRPhpw8uJ5msNDEiPPGG5=MvM4KvQ@mail.gmail.com>

> THIS?FIRMWARE?WAS?COMPILED?WITHOUT?TX?SUPPORT!!!

Well ... what does that tell you ?
Re-read the wiki ...


> -i found the value of LOST is too big, ...[snip]

The "LOST" messages are normal during a cell resync.


Cheers,

    Sylvain



From zhengfanf at hotmail.com  Thu Mar 10 03:18:44 2011
From: zhengfanf at hotmail.com (zhengfanf)
Date: Thu, 10 Mar 2011 11:18:44 +0800
Subject: I wanna make sure why LOCATION UPDATE REQUEST is always faild
References: <BLU0-SMTP20602BAD1847A94C3D63C3BBEC90@phx.gbl>
Message-ID: <BLU0-SMTP134DEA35C2C0081E4864255BEC80@phx.gbl>


Sylvain, thanks a lot for your reply

Problem solved!
It just need to enable CONFIG_TX_ENABLE in /src/target/firmware/Makefile, which can be found at http://bb.osmocom.org/trac/wiki/SIMReader
I am ashamed that i have not pay high attention to it

Thanks a lot!

Regards,
zheng


2011-03-10 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110310/50c87702/attachment.htm>

From 775725965 at qq.com  Thu Mar 10 11:41:39 2011
From: 775725965 at qq.com (=?gbk?B?wvPM78rYzfs=?=)
Date: Thu, 10 Mar 2011 19:41:39 +0800
Subject: MTK RF 
Message-ID: <tencent_5FDC9F804AA0F0877A29482B@qq.com>

can you help me  what is the mtk  RF  chip  MT6219   3  wire   Control   word   ? what is it mean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110310/13783132/attachment.htm>

From laforge at gnumonks.org  Thu Mar 10 14:48:08 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 10 Mar 2011 15:48:08 +0100
Subject: MTK RF
In-Reply-To: <tencent_5FDC9F804AA0F0877A29482B@qq.com>
References: <tencent_5FDC9F804AA0F0877A29482B@qq.com>
Message-ID: <20110310144808.GC2980@prithivi.gnumonks.org>

On Thu, Mar 10, 2011 at 07:41:39PM +0800, ???? wrote:
> can you help me  what is the mtk  RF  chip  MT6219   3  wire   Control   word
> ? what is it mean

"Control Word" is used for a multi-byte write command that is issued over the
3wire interface to re-configure somethin inside the RF transciever, such as
the PLL multiplier/divider or power up/power down, VGA gain, etc.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From vplrt at yahoo.com  Thu Mar 10 15:09:01 2011
From: vplrt at yahoo.com (Victor P)
Date: Thu, 10 Mar 2011 07:09:01 -0800 (PST)
Subject: bursts****.dat
Message-ID: <296655.56965.qm@web45801.mail.sp1.yahoo.com>

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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110310/b3bbd12c/attachment.htm>

From 246tnt at gmail.com  Thu Mar 10 15:32:04 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Thu, 10 Mar 2011 16:32:04 +0100
Subject: bursts****.dat
In-Reply-To: <296655.56965.qm@web45801.mail.sp1.yahoo.com>
References: <296655.56965.qm@web45801.mail.sp1.yahoo.com>
Message-ID: <AANLkTi=OceKLfc+U-c++KfWrVjadZg7=8La+7RVPqPyg@mail.gmail.com>

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

The burst raw data ... look in the sources where there are written and
you'll figure out how the data is organized.

> what should I use to see its data

Nothing.
You'll have to write your own tools. (possibly derived from airprobe).

Which requires a fair understanding of how GSM works at those levels,
so it's time to read GSM 05.01 / 05.02 / 05.03


Cheers,

    Sylvain



From holger at freyther.de  Thu Mar 10 15:34:00 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 10 Mar 2011 16:34:00 +0100
Subject: bursts****.dat
In-Reply-To: <296655.56965.qm@web45801.mail.sp1.yahoo.com>
References: <296655.56965.qm@web45801.mail.sp1.yahoo.com>
Message-ID: <4D78EF68.2000805@freyther.de>

On 03/10/2011 04:09 PM, Victor P wrote:
> 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.

These should be the 'raw' bursts on this timeslot. Reading GSM 05.02 should
get you started about the format, also airprobe should have code that can
handle raw bursts and convert them into the 'MAC' block.



From blassmegod at yahoo.com  Thu Mar 10 18:09:13 2011
From: blassmegod at yahoo.com (burebista)
Date: Thu, 10 Mar 2011 10:09:13 -0800 (PST)
Subject: MT6516 processor Android / Linux kernel driver
Message-ID: <551363.77173.qm@web130207.mail.mud.yahoo.com>

I found another mobile witch run Android on a MT6516 processor, you can find it 
here 
http://www.voldltd.com/sdp/1100371/4/pd-5258987/7588204-2080998/H6_Android_2_1_OS_Wifi_Analog_TV_Java_Trackball_Sm.html,
 it's a VOLD VD-H6, I'm still trying to get as much info from the Star A3000 
Android ROM and from the datasheet. I hope that in the near future this 
processor will be supported by Linux/Android. For now you can find the A3000 
kernel config file on the thread "Re: how to decompile a linux kernel zImage". 
Help is welcomed.



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110310/7b26ffd8/attachment.htm>

From mforce2 at gmail.com  Thu Mar 10 19:21:43 2011
From: mforce2 at gmail.com (Marius Cirsta)
Date: Thu, 10 Mar 2011 21:21:43 +0200
Subject: MT6516 processor Android / Linux kernel driver
In-Reply-To: <551363.77173.qm@web130207.mail.mud.yahoo.com>
References: <551363.77173.qm@web130207.mail.mud.yahoo.com>
Message-ID: <AANLkTinz6OmM7H8VC1o95U2bFm=cMj+G11U=kew_6D3-@mail.gmail.com>

 I created a special google group for this , you can find it here :
http://groups.google.com/group/mt6516-linux .  There we can talk
further about this because as Harald pointed out Osmocom is only about
running free software on the baseband CPU.
 Thanks.

On Thu, Mar 10, 2011 at 8:09 PM, burebista <blassmegod at yahoo.com> wrote:
> I found another mobile witch run Android on a MT6516 processor, you can find
> it here
> http://www.voldltd.com/sdp/1100371/4/pd-5258987/7588204-2080998/H6_Android_2_1_OS_Wifi_Analog_TV_Java_Trackball_Sm.html,
> it's a VOLD VD-H6, I'm still trying to get as much info from the Star A3000
> Android ROM and from the datasheet. I hope that in the near future this
> processor will be supported by Linux/Android. For now you can find the A3000
> kernel config file on the thread "Re: how to decompile a linux kernel
> zImage". Help is welcomed.
>
>



From 775725965 at qq.com  Fri Mar 11 02:43:52 2011
From: 775725965 at qq.com (=?gbk?B?wvPM78rYzfs=?=)
Date: Fri, 11 Mar 2011 10:43:52 +0800
Subject: hi all
Message-ID: <tencent_2E6FE9FD6DEC3BEA4254A58A@qq.com>

can you tell me the osmocom  is a free phone software Project or other   is it make a  GSM  Network for free ?   
 i think to make a samll GSM network for free  i think use usb interface phone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110311/d0233a76/attachment.htm>

From maciej.grela at gmail.com  Sun Mar 13 21:35:12 2011
From: maciej.grela at gmail.com (Maciej Grela)
Date: Sun, 13 Mar 2011 22:35:12 +0100
Subject: hi all
In-Reply-To: <tencent_2E6FE9FD6DEC3BEA4254A58A@qq.com>
References: <tencent_2E6FE9FD6DEC3BEA4254A58A@qq.com>
Message-ID: <AANLkTinpAGXQCDO7rDje7U5NHqVzYt0LNqG7TKzJ88aP@mail.gmail.com>

2011/3/11 ???? <775725965 at qq.com>:
> can you tell me the osmocom? is a free phone software Project or
> other???is?it make a? GSM? Network for free??
> i think to make a samll GSM network for free? i think use usb interface
> phone

This mailing list deals with the development of an open source phone
firmware (also called "baseband"). Osmocom-bb itself doesn't allow you
to make a "GSM network for free". To do that you would need
additionally:

- a BSC (look to http://openbsc.osmocom.org/trac/wiki/OpenBSC)
- a BTS (some BTS hardware is supported by OpenBSC)
- an MSC (no free implementation AFAIK)
- an HLR (also no free implementation)

Hope this helps.

Best regards,
Maciej Grela



From suraev at stud.ntnu.no  Sun Mar 13 22:33:09 2011
From: suraev at stud.ntnu.no (suraev at stud.ntnu.no)
Date: Sun, 13 Mar 2011 23:33:09 +0100
Subject: hi all
In-Reply-To: <AANLkTinpAGXQCDO7rDje7U5NHqVzYt0LNqG7TKzJ88aP@mail.gmail.com>
References: <tencent_2E6FE9FD6DEC3BEA4254A58A@qq.com>
	<AANLkTinpAGXQCDO7rDje7U5NHqVzYt0LNqG7TKzJ88aP@mail.gmail.com>
Message-ID: <4D7D4625.9050508@stud.ntnu.no>

13.03.2011 22:35, Maciej Grela ?????:

> - a BTS (some BTS hardware is supported by OpenBSC)
> - an MSC (no free implementation AFAIK)
> - an HLR (also no free implementation)

All 3 are implemented within OpenBTS project: http://openbts.sourceforge.net/

Using USRP as a hardware plus OpenBTS will give you gsm network almost for free
(excluding cost of usrp hardware).

This setup was used several times in production already.

In fact it's very useful to play with osmocom too :)

cheers,
Max.



From cbalke at charter.net  Fri Mar 11 06:11:22 2011
From: cbalke at charter.net (Calvin Balke)
Date: Thu, 10 Mar 2011 22:11:22 -0800
Subject: no reception, 3 bars on original firmware
Message-ID: <4D79BD0A.9060701@charter.net>

You don't have to answer this right now if you don't want to, it can 
wait.  I have been working on this for a few months.  I have never 
posted on this mailing list before, but I have read many of the other posts.
Just so you know, I am currently 14 years old and I have autism(which is 
the reason why I am obsessed with computers and electronics).

I am having trouble getting any signal at all. the signal is around -111 
dBm on every channel with the rf gain set on high.  The original 
firmware works fine with an at&t sim card and has 3 bars.  The linux 
distro that I am running is backtrack 4.  While trying to diagnose this, 
I tried mobile and layer23 on a known good channel from a nokia 3100 
series phone in netmonitor mode. and in scanning mode on most of the 
branches that I compiled.  I have looked on the wiki and google.  I have 
also tried to figure out how parts of the source code work.  I have even 
tried this on two different boards, the compal_e88 and compal_e86.  Has 
anybody else had this problem?  Where exactly is the antenna switch?  
That could be the problem, if it connects to the headset slot.  I have a 
homemade t191 cable, that uploads the firmware just fine, but I am 
wondering about the LOST message after the dsp download.  What does the 
LOST message mean?

Thank you for your help,
Calvin



From laforge at gnumonks.org  Fri Mar 11 10:42:24 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 11 Mar 2011 11:42:24 +0100
Subject: no reception, 3 bars on original firmware
In-Reply-To: <4D79BD0A.9060701@charter.net>
References: <4D79BD0A.9060701@charter.net>
Message-ID: <20110311104224.GW2980@prithivi.gnumonks.org>

Hi Calvin,

On Thu, Mar 10, 2011 at 10:11:22PM -0800, Calvin Balke wrote:
> I am having trouble getting any signal at all. the signal is around
> -111 dBm on every channel with the rf gain set on high.  The
> original firmware works fine with an at&t sim card and has 3 bars.

I think your problems may relate to the RF bands, as you seem to be
located in the US.   Most of our developers are in Europe and work
with GSM 900 + GSM 1800 bands.  Now if your phone hardware is a
GSM 850 + GSM 1900 model, and your layer23 is configured to scan
in European 900/1800 bands, you will of course never receive any signal.

This is just a guess, some people on this list have used OsmocomBB in
the US before, maybe they can comment.

The LOST message is about a lost interrupt.  There is some timer-based
code that helps us to debug problems in our layer1 code.  Loosing interrupts
means that there were TDMA frames at which we did not get or server an
interrupt, i.e. somehow the CPU / L1 was stuck and too busy to process
the next TDMA frame.

Some of those messages showing up during phone boot/start is OK, but during
normal operation they are a pretty strong indication of some bugs in our code.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From Andreas.Eversberg at versatel.de  Fri Mar 11 14:29:09 2011
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Fri, 11 Mar 2011 15:29:09 +0100
Subject: AW: no reception, 3 bars on original firmware
Message-ID: <B16317F2B1592B4492FC414114171CE605301DDD@FLBVEXCH01.versatel.local>

 
hi calvin,

> I am having trouble getting any signal at all. the signal is around
-111
> dBm on every channel with the rf gain set on high.  The original 

as harald said, it seems that your phone uses 850 and 1900mhz bands. the
filters inside only pass these frequencies. the BTS' in europe use
different frequencies than in the US. the current layer23 will only
support 900mhz and 1800mhz bands so far. i didn't care about other
bands, because i have no way to test it. i can add new bands to layer23.
your mail gives me some motivation to implement this finally. the
support of DCS and PCS in parallel is quite tricky. maybe i will finish
this weekend and you may try that out.

regards,

andreas



From roy.techie at gmail.com  Fri Mar 11 14:26:39 2011
From: roy.techie at gmail.com (royfarji india)
Date: Fri, 11 Mar 2011 19:56:39 +0530
Subject: Sorry for this kind of mail: but please help||
Message-ID: <AANLkTikbPdS5tMsYLiVUkpE6gYACfbfdwVBHntyp=GEo@mail.gmail.com>

Hello everyone,
Sorry to bother you all.I am a student and desire to become researchers like
you all out there.
While building the project osmocom I got an unique error which no-one in the
mailing lists have got yet.It says that the header file 'signal.h' is
missing in osmocore.I am just uanble to figure it how it is unable to
include the header file. please help.Also I am attaching the file of
compilation.By the way I am using the gnuarm-3.4.3 as shown on the
osmocom-bb website.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110311/5e63d3de/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: output.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 6366 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110311/5e63d3de/attachment.bin>

From peter at stuge.se  Sat Mar 12 12:53:22 2011
From: peter at stuge.se (Peter Stuge)
Date: Sat, 12 Mar 2011 13:53:22 +0100
Subject: Sorry for this kind of mail: but please help||
In-Reply-To: <AANLkTikbPdS5tMsYLiVUkpE6gYACfbfdwVBHntyp=GEo@mail.gmail.com>
References: <AANLkTikbPdS5tMsYLiVUkpE6gYACfbfdwVBHntyp=GEo@mail.gmail.com>
Message-ID: <20110312125322.17454.qmail@stuge.se>

royfarji india wrote:
> Sorry to bother you all. I am a student and desire to become
> researchers like you all out there.

I understand. There are several things that I think you need to spend
time studying, to make the most out of the community. Some are
trivial (write useful email subjects, never send Microsoft Office
files) and others require understanding of a fairly big topic, such
as the problem you met, because the cross-compilation is not being
done correctly. The GNU toolchain is not too simple, so it's a big
topic even for native compilation. It becomes even more important to
know many details in order to firmly grasp cross-compilation.

Toolchain education is not the topic of the project. I would
recommend experimenting with some other ARM microcontrollers first.


> It says that the header file 'signal.h' is missing in osmocore. I
> am just uanble to figure it how it is unable to include the header
> file. please help.

The fact that noone else had the problem could (and should) suggest
that there is a greater error than something related to the header
file.


> Also I am attaching the file of compilation.

Microsoft Office is a proprietary program. The open source community
by definition dislikes proprietary programs. Please keep this in
mind. Please keep the logic in mind.

Even if Word is a big part of your other activities it is important
to speak with fools the way fools understand. (Swedish proverb.) When
working in an open source project, Word is not an appropriate tool,
because you can not know if everyone else has Word, and furthermore,
because you are sending text via email then the simplest method is to
put the text directly in the email. That way everyone receiving your
email can also read the text directly in their email programs. Try it
also with your colleagues. Maybe they will be shocked by having text
available immediately in the email program.


> By the way I am using the gnuarm-3.4.3 as shown on the osmocom-bb
> website.

I believe this toolchain has a bug, and the osmocom build system
currently relies on this bug. With experience from the GNU toolchain
and embedded software development using open source tools the bug is
obvious and trivial to work around. Without that experience it's not
easy to spot. I've sent a patch which makes osmocom assume a bug-free
toolchain, but still be compatible with the old behavior, but it has
not been included yet.


> roy at roy:~/osmocom-bb$ cd src
> roy at roy:~/osmocom-bb/src$ make
> cd shared/libosmocore/build-target && ../configure \
> 	--host=arm-elf-linux --disable-vty --enable-panic-infloop \
> 	--disable-shared --disable-talloc --disable-tests \
> 	CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections -I/home/roy/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs"

The error is with --host and the gnuarm toolchain. The specified
target system (arm-elf-linux) would Linux on the phone, which is
incorrect. A more correct prefix tuple for an ARM CPU without
operating system would be arm-elf, arm-none-elf or arm-none-eabi.


> checking for arm-elf-linux-gcc... arm-elf-gcc

osmocom configure expects an arm-elf-linux C compiler, but CC= on the
command line overrides it. This might seem like an acceptable
solution, but in fact the configure script and other toolchain
commands may still rely on the fact that the target system will be
running Linux as specified with --host.


Could try patch v4 in old thread:

http://baseband-devel.722152.n3.nabble.com/PATCH-Adjust-top-level-Makefile-for-arm-none-eabi-toolchain-td2334319.html


//Peter



From peter at stuge.se  Sat Mar 12 12:57:22 2011
From: peter at stuge.se (Peter Stuge)
Date: Sat, 12 Mar 2011 13:57:22 +0100
Subject: Sorry for this kind of mail: but please help||
In-Reply-To: <20110312125322.17454.qmail@stuge.se>
References: <AANLkTikbPdS5tMsYLiVUkpE6gYACfbfdwVBHntyp=GEo@mail.gmail.com>
	<20110312125322.17454.qmail@stuge.se>
Message-ID: <20110312125722.18060.qmail@stuge.se>

Peter Stuge wrote:
> The fact that noone else had the problem could (and should) suggest
> that there is a greater error than something related to the header
> file.
..

> > roy at roy:~/osmocom-bb$ cd src
> > roy at roy:~/osmocom-bb/src$ make
> > cd shared/libosmocore/build-target && ../configure \
> > 	--host=arm-elf-linux --disable-vty --enable-panic-infloop \
> > 	--disable-shared --disable-talloc --disable-tests \
> > 	CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections -I/home/roy/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs"
> 
> The error is with --host and the gnuarm toolchain.

While this is indeed an error it should work with gnuarm thinking a
bit more. Is your problem simply missing files? Did you prepare all
of the sourcecode dependencies, specifically libosmocore, in the
right place, so that it can be found?


//Peter



From roy.techie at gmail.com  Sat Mar 12 10:12:45 2011
From: roy.techie at gmail.com (royfarji india)
Date: Sat, 12 Mar 2011 15:42:45 +0530
Subject: compile errors
Message-ID: <AANLkTimQR1JygvPG2d0VeKnpRdE_e44yWmUr6v6jPoy5@mail.gmail.com>

Hello everyone,
Sorry to bother you all.I am a student and desire to become researchers like
you all out there.
While building the project osmocom I got an unique error which no-one in the
mailing lists have got yet.It says that the header file 'signal.h' is
missing in osmocore.I am just uanble to figure it how it is unable to
include the header file. please help.By the way I am using the gnuarm-3.4.3
as shown on the osmocom-bb website.



 roy at roy:~/osmocom-bb$ cd src
roy at roy:~/osmocom-bb/src$ make
cd shared/libosmocore/build-target && ../configure \
			--host=arm-elf-linux --disable-vty --enable-panic-infloop \
			--disable-shared --disable-talloc --disable-tests \
		CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections
-I/home/roy/osmocom-bb/src/target/firmware/include -nostartfiles
-nodefaultlibs"
configure: WARNING: if you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-elf-linux-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 sets $(MAKE)... (cached) yes
checking for arm-elf-linux-gcc... arm-elf-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 arm-elf-gcc accepts -g... yes
checking for arm-elf-gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of arm-elf-gcc... gcc3
checking build system type... i686-pc-linux-gnu
checking host system type... arm-elf-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by arm-elf-gcc...
/home/roy/osmocom-bb/gnuarm-3.4.3/arm-elf/bin/ld
checking if the linker
(/home/roy/osmocom-bb/gnuarm-3.4.3/arm-elf/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... no
checking for arm-elf-linux-dumpbin... no
checking for arm-elf-linux-link... no
checking for dumpbin... no
checking for link... link -dump -symbols
configure: WARNING: using cross tools not prefixed with host triplet
checking the name lister (link -dump -symbols) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 805306365
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /home/roy/osmocom-bb/gnuarm-3.4.3/arm-elf/bin/ld option
to reload object files... -r
checking for arm-elf-linux-objdump... no
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for arm-elf-linux-ar... no
checking for ar... ar
checking for arm-elf-linux-strip... strip
checking for arm-elf-linux-ranlib... no
checking for ranlib... ranlib
checking command to parse link -dump -symbols output from arm-elf-gcc
object... failed
checking how to run the C preprocessor... arm-elf-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... no
checking for inttypes.h... no
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... no
checking for objdir... .libs
checking if arm-elf-gcc supports -fno-rtti -fno-exceptions... no
checking for arm-elf-gcc option to produce PIC... -fPIC -DPIC
checking if arm-elf-gcc PIC flag -fPIC -DPIC works... yes
checking if arm-elf-gcc static flag -static works... yes
checking if arm-elf-gcc supports -c -o file.o... yes
checking if arm-elf-gcc supports -c -o file.o... (cached) yes
checking whether the arm-elf-gcc linker
(/home/roy/osmocom-bb/gnuarm-3.4.3/arm-elf/bin/ld) supports shared
libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for ANSI C header files... (cached) yes
checking execinfo.h usability... no
checking execinfo.h presence... no
checking for execinfo.h... no
checking sys/select.h usability... no
checking sys/select.h presence... no
checking for sys/select.h... no
checking if arm-elf-gcc supports -fvisibility=hidden... no
configure: creating ./config.status
config.status: creating libosmocore.pc
config.status: creating libosmocodec.pc
config.status: creating libosmovty.pc
config.status: creating include/osmocom/Makefile
config.status: creating include/osmocom/vty/Makefile
config.status: creating include/osmocom/codec/Makefile
config.status: creating include/osmocom/crypt/Makefile
config.status: creating include/osmocore/Makefile
config.status: creating include/osmocore/protocol/Makefile
config.status: creating include/Makefile
config.status: creating src/Makefile
config.status: creating src/vty/Makefile
config.status: creating src/codec/Makefile
config.status: creating tests/Makefile
config.status: creating tests/timer/Makefile
config.status: creating tests/sms/Makefile
config.status: creating tests/msgfile/Makefile
config.status: creating tests/ussd/Makefile
config.status: creating tests/smscb/Makefile
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
cd shared/libosmocore/build-target && make
make[1]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
make  all-recursive
make[2]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
Making all in include
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'
Making all in osmocom
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
Making all in codec
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec'
Making all in crypt
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt'
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
Making all in osmocore
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
Making all in protocol
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol'
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'
Making all in src
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'
Making all in .
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'
Making all in vty
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty'
Making all in codec
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'
Making all in tests
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
make[2]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
make[1]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
cd shared/libosmocore/build-host && ../configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
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 sets $(MAKE)... (cached) yes
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... no
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
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 805306365
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for ANSI C header files... (cached) yes
checking execinfo.h usability... yes
checking execinfo.h presence... yes
checking for execinfo.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking if gcc supports -fvisibility=hidden... yes
configure: creating ./config.status
config.status: creating libosmocore.pc
config.status: creating libosmocodec.pc
config.status: creating libosmovty.pc
config.status: creating include/osmocom/Makefile
config.status: creating include/osmocom/vty/Makefile
config.status: creating include/osmocom/codec/Makefile
config.status: creating include/osmocom/crypt/Makefile
config.status: creating include/osmocore/Makefile
config.status: creating include/osmocore/protocol/Makefile
config.status: creating include/Makefile
config.status: creating src/Makefile
config.status: creating src/vty/Makefile
config.status: creating src/codec/Makefile
config.status: creating tests/Makefile
config.status: creating tests/timer/Makefile
config.status: creating tests/sms/Makefile
config.status: creating tests/msgfile/Makefile
config.status: creating tests/ussd/Makefile
config.status: creating tests/smscb/Makefile
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
cd shared/libosmocore/build-host && make
make[1]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
make  all-recursive
make[2]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
Making all in include
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include'
Making all in osmocom
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom'
Making all in vty
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/vty'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/vty'
Making all in codec
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/codec'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/codec'
Making all in crypt
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/crypt'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/crypt'
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom'
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom'
Making all in osmocore
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
Making all in protocol
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol'
make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include'
Making all in src
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src'
Making all in .
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src'
Making all in vty
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/vty'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/vty'
Making all in codec
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/codec'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/codec'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src'
Making all in tests
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests'
Making all in timer
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/timer'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/timer'
Making all in sms
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/sms'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/sms'
Making all in ussd
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/ussd'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/ussd'
Making all in smscb
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/smscb'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/smscb'
Making all in msgfile
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/msgfile'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/msgfile'
make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests'
make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
make[2]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
make[1]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
make -C host/layer23
make[1]: Entering directory `/home/roy/osmocom-bb/src/host/layer23'
Making all in include
make[2]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include'
Making all in osmocom
make[3]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom'
Making all in bb
make[4]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb'
Making all in common
make[5]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/common'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/common'
Making all in misc
make[5]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/misc'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/misc'
Making all in mobile
make[5]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/mobile'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/mobile'
make[5]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb'
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb'
make[4]: Entering directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom'
make[3]: Leaving directory
`/home/roy/osmocom-bb/src/host/layer23/include/osmocom'
make[3]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include'
make[2]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include'
Making all in src
make[2]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/src'
Making all in common
make[3]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/src/common'
  CC     l1ctl.o
l1ctl.c:33: fatal error: osmocore/signal.h: No such file or directory
compilation terminated.
make[3]: *** [l1ctl.o] Error 1
make[3]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/src/common'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23'
make: *** [host/layer23/layer23] Error 2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110312/3de9f06a/attachment.htm>

From its_sead at gmx.de  Sat Mar 12 11:33:33 2011
From: its_sead at gmx.de (its sead)
Date: Sat, 12 Mar 2011 12:33:33 +0100
Subject: c123 boot wihtout battery
Message-ID: <20110312113333.19880@gmx.net>

hi list,

I would like to run the c123(s) without the LI battery with direct
5V power supply only. Without battery the c123 display just blinks
and no PROMPT1 can be received.

Anyone knows a way how this might work ? (- like bypass or bridge
this 3 pin battery pins)

thanks for your help

(sorry for the lame add)
-- 
Schon geh?rt? GMX hat einen genialen Phishing-Filter in die
Toolbar eingebaut! http://www.gmx.net/de/go/toolbar



From lbernal at gmail.com  Sat Mar 12 12:06:18 2011
From: lbernal at gmail.com (n0p [Luis Bernal])
Date: Sat, 12 Mar 2011 13:06:18 +0100
Subject: c123 boot wihtout battery
In-Reply-To: <20110312113333.19880@gmx.net>
References: <20110312113333.19880@gmx.net>
Message-ID: <AANLkTinBPPdFqSY0yR28mxAo9zXH99WnNDGGabQ1szKe@mail.gmail.com>

Try to add a capacitor between the + and -
Sometimes it works
El 12/03/2011 13:01, "its sead" <its_sead at gmx.de> escribi?:
> hi list,
>
> I would like to run the c123(s) without the LI battery with direct
> 5V power supply only. Without battery the c123 display just blinks
> and no PROMPT1 can be received.
>
> Anyone knows a way how this might work ? (- like bypass or bridge
> this 3 pin battery pins)
>
> thanks for your help
>
> (sorry for the lame add)
> --
> Schon geh?rt? GMX hat einen genialen Phishing-Filter in die
> Toolbar eingebaut! http://www.gmx.net/de/go/toolbar
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110312/7a3015b4/attachment.htm>

From 246tnt at gmail.com  Sun Mar 13 13:38:07 2011
From: 246tnt at gmail.com (246tnt at gmail.com)
Date: Sun, 13 Mar 2011 13:38:07 +0000
Subject: c123 boot wihtout battery
In-Reply-To: <20110312113333.19880@gmx.net>
Message-ID: <00504502cc7d2b77bb049e5d4e7e@google.com>

Hi,

> I would like to run the c123(s) without the LI battery with direct
> 5V power supply only. Without battery the c123 display just blinks
> and no PROMPT1 can be received.

That won't work via the power plug ... (at least with osmocom, with the  
default FW it may works if you have a big cap instead of the battery).

You can inject 3.7v directly at the battery pins with a big cap close to  
the phone and that should work fine.

Check the C118 schematics to understand why.

Cheers,

Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110313/52ea5ce5/attachment.htm>

From henk.vergonet at gmail.com  Sat Mar 12 14:44:40 2011
From: henk.vergonet at gmail.com (Henk)
Date: Sat, 12 Mar 2011 15:44:40 +0100
Subject: DSP dump from C116
Message-ID: <AANLkTi=3uDRSs_Dmo3SPwGn1qLQVi3y6RZNcrSnqGRXz@mail.gmail.com>

Hi all,

I am trying to get a dump of the DSP code, but after 2 lines of hex
the device seems to get stuck.

Some watchdog or so, missing something in the initialization sequence?
According to the docs the cDSP ID seems to indicate a version B dsp...

Any ideas what I can do to investigate?

- Henk

./osmocon -p /dev/ttyS0 -m c123
../../target/firmware/board/compal_e88/compal_dsp_dump.compalram.bin

Output: (I had commented the register locations to see if it helped...)

OSMOCOM Compal DSP Dumper (revision osmocon_v0.0.0-780-gb7a4d8d-modified)
======================================================================
Device ID code: 0xb4fb                    ==> CalypsoLite
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128                     ==> Version B
Die ID code: 168f2c10cb001251
======================================================================
Assert DSP into Reset
Releasing DSP from Reset
DSP bootloader version 0x0100
DSP dump: DROM [09000-0dfff]
09000 : 0006 0052 ff7d 009a ffc8 fd21 00b7 ffbf fef7 0009 ff2e fe97
0071 02ce 0719 03f2
09010 : 04be 0625 0359 0535 08e4 033b 0620 078d 02cd 07c5 089e 0346
0494 071f 02d1 03e8



From 246tnt at gmail.com  Sun Mar 13 13:35:48 2011
From: 246tnt at gmail.com (246tnt at gmail.com)
Date: Sun, 13 Mar 2011 13:35:48 +0000
Subject: DSP dump from C116
In-Reply-To: <AANLkTi=3uDRSs_Dmo3SPwGn1qLQVi3y6RZNcrSnqGRXz@mail.gmail.com>
Message-ID: <002215975beeea2906049e5d4544@google.com>

> Any ideas what I can do to investigate?

Add a delay after each printf ...

The serial console buffer gets filled faster than it empties and it leads  
to a panic() condition because there is no more buffer space.


Cheers,

Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110313/04a29688/attachment.htm>

From henk.vergonet at gmail.com  Mon Mar 14 11:39:54 2011
From: henk.vergonet at gmail.com (Henk)
Date: Mon, 14 Mar 2011 12:39:54 +0100
Subject: DSP dump from C116
In-Reply-To: <002215975beeea2906049e5d4544@google.com>
References: <AANLkTi=3uDRSs_Dmo3SPwGn1qLQVi3y6RZNcrSnqGRXz@mail.gmail.com>
	<002215975beeea2906049e5d4544@google.com>
Message-ID: <AANLkTi=S6KzmoFivmz3-Nd_iP0eML2FzahY75OMiw4_E@mail.gmail.com>

Thanks, I will check it out

Maybe we may need to add some mutex mechanism between printf routine,
and the serial output.

Let me see if I can fix this...

Regards,
Henk


On Sun, Mar 13, 2011 at 2:35 PM,  <246tnt at gmail.com> wrote:
>> Any ideas what I can do to investigate?
>
> Add a delay after each printf ...
>
> The serial console buffer gets filled faster than it empties and it leads to
> a panic() condition because there is no more buffer space.
>
>
> Cheers,
>
> Sylvain



From andre at ac.nl.eu.org  Mon Mar 14 08:02:31 2011
From: andre at ac.nl.eu.org (=?UTF-8?B?QW5kcsOpIMSMZXJuw6Jr?=)
Date: Mon, 14 Mar 2011 09:02:31 +0100
Subject: DSP dump from C116
In-Reply-To: <AANLkTi=3uDRSs_Dmo3SPwGn1qLQVi3y6RZNcrSnqGRXz@mail.gmail.com>
References: <AANLkTi=3uDRSs_Dmo3SPwGn1qLQVi3y6RZNcrSnqGRXz@mail.gmail.com>
Message-ID: <4D7DCB97.3080602@ac.nl.eu.org>

I got the same with c121. Apparently some dependencies of 
compal_dsp_dump target application was broken since this application was 
last updated. I hadn't time to pinpoint, what exactly was broken, but 
dsp dumping in version 4829...e844 works:

http://bb.osmocom.org/trac/browser/src?rev=48298d17fea548956c8fde2a1121c52f92e6e844

Regards,
Andr?

On 12/03/11 15:44, Henk wrote:
> Hi all,
>
> I am trying to get a dump of the DSP code, but after 2 lines of hex
> the device seems to get stuck.
>
> Some watchdog or so, missing something in the initialization sequence?
> According to the docs the cDSP ID seems to indicate a version B dsp...
>
> Any ideas what I can do to investigate?
>
> - Henk
>
> ./osmocon -p /dev/ttyS0 -m c123
> ../../target/firmware/board/compal_e88/compal_dsp_dump.compalram.bin
>
> Output: (I had commented the register locations to see if it helped...)
>
> OSMOCOM Compal DSP Dumper (revision osmocon_v0.0.0-780-gb7a4d8d-modified)
> ======================================================================
> Device ID code: 0xb4fb                    ==>  CalypsoLite
> Device Version code: 0x0000
> ARM ID code: 0xfff3
> cDSP ID code: 0x0128                     ==>  Version B
> Die ID code: 168f2c10cb001251
> ======================================================================
> Assert DSP into Reset
> Releasing DSP from Reset
> DSP bootloader version 0x0100
> DSP dump: DROM [09000-0dfff]
> 09000 : 0006 0052 ff7d 009a ffc8 fd21 00b7 ffbf fef7 0009 ff2e fe97
> 0071 02ce 0719 03f2
> 09010 : 04be 0625 0359 0535 08e4 033b 0620 078d 02cd 07c5 089e 0346
> 0494 071f 02d1 03e8
>




From cbalke at charter.net  Sat Mar 12 22:33:32 2011
From: cbalke at charter.net (Calvin Balke)
Date: Sat, 12 Mar 2011 14:33:32 -0800
Subject: Order of functions to transmit and receive using layer1
Message-ID: <4D7BF4BC.6040302@charter.net>

     I was wondering how to transmit and receive using layer1.  I have 
been reading some of the gsm specs.   I have been looking around in the 
source code a lot, and there many functions that are used for transmit 
and receive.  Which are the right few to use?  Is there any way to send 
a text message to a different phone by simulating a base station?  Do I 
need two phones or one phone to transmit and receive as a base station?  
Is there any way to make a half duplex base station on a BCCH channel 
with only one subscriber phone at a time, and what would that entail 
code-wise?  Would it be legal to run a very low power base station in 
the USA on a different unused cellular band/frequency?  I have a lot of 
free time since I do school at home and I could probably help develop 
some new parts of the osmocom-bb project if you want me to.  I know C, 
some x86 assembly, and a few other languages.  I have also had practice 
fixing compile-time errors, and bugs in code.  I apologize if this is 
too many questions. You don't have to answer them all if you don't want to.

Thank you for helping,
Calvin E. Balke



From 246tnt at gmail.com  Sun Mar 13 13:34:29 2011
From: 246tnt at gmail.com (246tnt at gmail.com)
Date: Sun, 13 Mar 2011 13:34:29 +0000
Subject: Order of functions to transmit and receive using layer1
In-Reply-To: <4D7BF4BC.6040302@charter.net>
Message-ID: <0015174c1a382af189049e5d41ab@google.com>

Hi,

> I have been looking around in the source code a lot, and there many  
> functions that are used for transmit and receive.

Yes there are ... The actual submission of L2 packets for TX to the DSP is  
in prim_tx_nb.c.
This is what gives the DSP the command. But if _all_ the rest of the  
environment (basically all the rest of L1) is not in the exact right  
state ... it won't do what you ask.

There is no way around it, you have to see L1 in its globality to  
understand.

Now if you want the higher function (from the host side), then it's the  
L1CTL_DATA_REQ message you must look at.


> Which are the right few to use?

Well they all have their role to play. It's not at all like network where  
you have 'send a packet' ... here there is a whole context that matters.


> Is there any way to send a text message to a different phone by  
> simulating a base station?

No.


> Do I need two phones or one phone to transmit and receive as a base  
> station?

You need much more than that. And before you even think about this, get  
more familiar about of a phone works as designed before trying to make it  
do stuff it's not designed to do.


> Is there any way to make a half duplex base station on a BCCH channel  
> with only one subscriber phone at a time, and what would that entail  
> code-wise?

There is no way to make a 'half duplex' base station, it just won't work.  
It's been tried with a modified OpenBTS and without a continuous RF power  
signal on C0, the phones won't lock to it.


> Would it be legal to run a very low power base station in the USA on a  
> different unused cellular band/frequency?

No.
And since the phone can blast > 1W of RF power, you can easily disrupt  
stuff so be careful.

For any testing of undesigned functions you should connect the phone in a  
closed loop to some testing equipement (network analyzer / MS testers /  
spectum analyzers ...).
Or at the very least disconnect the antenna, put a dummy load in its place  
and test in a deep basement or something.


Cheers,

Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110313/97fa05b7/attachment.htm>

From Andreas.Eversberg at versatel.de  Mon Mar 14 10:34:49 2011
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Mon, 14 Mar 2011 11:34:49 +0100
Subject: AW: Order of functions to transmit and receive using layer1
Message-ID: <B16317F2B1592B4492FC414114171CE605302113@FLBVEXCH01.versatel.local>

hi,

>     I was wondering how to transmit and receive using layer1.  I have 
> been reading some of the gsm specs.   I have been looking around in
the 
> source code a lot, and there many functions that are used for transmit

> and receive.  Which are the right few to use?

there are only two types of data between L1 and L2: data frames and
channel request burst. all the other functions control the radio and the
channel in which to communicate. the layer 1 is controlled by the radio
ressource protocol (gsm48_rr.c). in order to understand the channel
multiplexing, you should read GSM TS 05.02.

> Is there any way to send
> a text message to a different phone by simulating a base station?

osmocom is not (yet) able to control baseband hardware to act as a BTS.

> Do I 
> need two phones or one phone to transmit and receive as a base
station?  

in order to have more than a BCCH, you need two phones. one phone is not
able to send and receive at a time. continuouly transmission is required
for other phones to find a cell.

> Is there any way to make a half duplex base station on a BCCH channel 
> with only one subscriber phone at a time, and what would that entail 
> code-wise?

you can limit the number of active calls by limiting the number of
channels on the BTS, but you cannot limit the number of phones camping
on the BTS.

> Would it be legal to run a very low power base station in 
the USA on a different unused cellular band/frequency?

you need to check the FCC for laws and test licenses.

> I have a lot of 
> free time since I do school at home and I could probably help develop 
> some new parts of the osmocom-bb project if you want me to.  I know C,

> some x86 assembly, and a few other languages.  I have also had
practice 
> fixing compile-time errors, and bugs in code.  I apologize if this is 
> too many questions. You don't have to answer them all if you don't
want to.

if you are really interested. you should start reading with TS 04.08.
this is what i did. it describes all the three "layer 3" protocols. 

Thank you for helping,
Calvin E. Balke




From roy.techie at gmail.com  Tue Mar 15 16:11:34 2011
From: roy.techie at gmail.com (royfarji india)
Date: Tue, 15 Mar 2011 09:11:34 -0700
Subject: compile problems using patch
Message-ID: <AANLkTik5_hVNeSkDQEh4YtZpTYA81O-8WeGTuJN6DkYs@mail.gmail.com>

I had some compilation problems in buiding osmocom-bb using gnuarm-3.4.3. I
have used the patch present at:
http://baseband-devel.722152.n3.nabble.com/PATCH-Adjust-top-level-Makefile-for-arm-none-eabi-toolchain-td2334319.html

please help






roy at roy:~$ cd osmocom-bb

roy at roy:~/osmocom-bb$ cd src

roy at roy:~/osmocom-bb/src$ make

cd shared/libosmocore/build-target && make

make[1]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'

make  all-recursive

make[2]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'

Making all in include

make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'

Making all in osmocom

make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'

Making all in codec

make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec'

make[5]: Nothing to be done for `all'.

make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec'

Making all in crypt

make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt'

make[5]: Nothing to be done for `all'.

make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt'

make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'

make[5]: Nothing to be done for `all-am'.

make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'

make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'

Making all in osmocore

make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'

Making all in protocol

make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol'

make[5]: Nothing to be done for `all'.

make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol'

make[5]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'

make[5]: Nothing to be done for `all-am'.

make[5]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'

make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'

make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'

make[4]: Nothing to be done for `all-am'.

make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'

make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'

Making all in src

make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'

Making all in .

make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'

make[4]: Nothing to be done for `all-am'.

make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'

Making all in vty

make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty'

make[4]: Nothing to be done for `all'.

make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty'

Making all in codec

make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec'

make[4]: Nothing to be done for `all'.

make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec'

make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'

Making all in tests

make[3]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'

Making all in timer

make[4]: Entering directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer'

  CCLD   timer_test

timer_test.o: In function `main':

/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer/../../../tests/timer/timer_test.c:66:
undefined reference to `bsc_schedule_timer'

/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer/../../../tests/timer/timer_test.c:67:
undefined reference to `bsc_schedule_timer'

/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer/../../../tests/timer/timer_test.c:68:
undefined reference to `bsc_schedule_timer'

timer_test.o: In function `timer_fired':

/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer/../../../tests/timer/timer_test.c:51:
undefined reference to `bsc_schedule_timer'

/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer/../../../tests/timer/timer_test.c:52:
undefined reference to `bsc_del_timer'

../../src/.libs/libosmocore.so: undefined reference to `msgb_dequeue'

../../src/.libs/libosmocore.so: undefined reference to `bsc_nearest_timer'

../../src/.libs/libosmocore.so: undefined reference to `msgb_enqueue'

../../src/.libs/libosmocore.so: undefined reference to `bsc_prepare_timers'

../../src/.libs/libosmocore.so: undefined reference to `bsc_timer_check'

../../src/.libs/libosmocore.so: undefined reference to `msgb_free'

../../src/.libs/libosmocore.so: undefined reference to `msgb_alloc'

../../src/.libs/libosmocore.so: undefined reference to `get_string_value'

../../src/.libs/libosmocore.so: undefined reference to `get_value_string'

../../src/.libs/libosmocore.so: undefined reference to `bsc_update_timers'

collect2: ld returned 1 exit status

make[4]: *** [timer_test] Error 1

make[4]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer'

make[3]: *** [all-recursive] Error 1

make[3]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'

make[2]: *** [all-recursive] Error 1

make[2]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'

make[1]: *** [all] Error 2

make[1]: Leaving directory
`/home/roy/osmocom-bb/src/shared/libosmocore/build-target'

make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] Error 2

roy at roy:~/osmocom-bb/src$
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110315/2fbf1343/attachment.htm>

From mad at auth.se  Tue Mar 15 17:02:09 2011
From: mad at auth.se (Mad)
Date: Tue, 15 Mar 2011 18:02:09 +0100
Subject: =?UTF-8?Q?burst=5Find=20and=20TCH?=
Message-ID: <b1e1e2adfb4c588640460f8647169ac3@auth.se>


 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



From 246tnt at gmail.com  Tue Mar 15 18:48:48 2011
From: 246tnt at gmail.com (246tnt at gmail.com)
Date: Tue, 15 Mar 2011 18:48:48 +0000
Subject: burst_ind and TCH
In-Reply-To: <b1e1e2adfb4c588640460f8647169ac3@auth.se>
Message-ID: <0022158df35bf87df5049e89e0c2@google.com>

> After receiving an Assignment Command for a hopping TCH/FI
> call l1ctl_tx_dm_est_req_h1() with all necessary parameters

IIRC, the L1 in burst_ind mode doesn't support changing channel assignement  
without first resyncing to the C0.

So you can not do BCCH -> SDCCH -> TCH
you have to do BCCH -> SDCCH -> BCCH (wait for sync) -> TCH

It's a limitation of the current public code in burst_ind mode.


> and tch_mode GSM48_CMODE_SPEECH_V1 or _EFR.

tch_mode is useless for burst_ind


Cheers,

Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110315/e81c91b7/attachment.htm>

From mad at auth.se  Wed Mar 16 16:15:55 2011
From: mad at auth.se (Mad)
Date: Wed, 16 Mar 2011 17:15:55 +0100
Subject: =?UTF-8?Q?burst=5Find=20and=20TCH?=
In-Reply-To: <0022158df35bf87df5049e89e0c2@google.com>
References: <0022158df35bf87df5049e89e0c2@google.com>
Message-ID: <dd855ebf5bf77c16b935374f52c3e7dd@auth.se>

 On Tue, 15 Mar 2011 18:48:48 +0000, 246tnt at gmail.com wrote:
>
> IIRC, the L1 in burst_ind mode doesnt support changing channel
> assignement without first resyncing to the C0.
>
> So you can not do BCCH -> SDCCH -> TCH
> you have to do BCCH -> SDCCH -> BCCH (wait for sync) -> TCH
>

 Ah ok, thank you, now I see frames... :-)

 What does the current master layer1 do to be able to change from
 SDCCH to TCH without loosing sync?
 I didn't found it resyncing to SCH/FCCH somewhere, but perhaps I
 overlooked it.

 BTW, after some time on a TCH it seem to loose the channel,
 resulting in frame loss and even complete break of reception.
 Am I guessing right that the missing feed of dsp measurements
 into afc and setting of RF gain - like it's done in prim_tch -
 is the cause?


 Regards,
   Mad



From suraev at stud.ntnu.no  Wed Mar 16 00:51:33 2011
From: suraev at stud.ntnu.no (suraev at stud.ntnu.no)
Date: Wed, 16 Mar 2011 01:51:33 +0100
Subject: cell_log and kalibrator
Message-ID: <4D800995.1040705@stud.ntnu.no>

Hey.

Did I got it right that instead of using at commands and gprs-capable modem for clock
calibration (as in http://gnuradio.org/redmine/wiki/1/OpenBTSClockCalibration) we can
use output of [power] section of cell_log?

Have somebody tried this?

Above-mentioned page says that it "is obvious how the values were obtained" for
executing ./kal script. As a matter of fact - it's not, at least not for newbies :(

For example I got following in cell_log:
arfcn 740 -99 -105 -109 -108 -110 -107 -108 -103 -109 -108 -110 -100
Seems like pretty good signal strength.

No I should run ./kal -f NNN -u
adjust clock in my usrp and run ./kal again.

But what's the formula for obtaining NNN from arfcn 740?

Can you advise me on some improving reading?

thank you,
Max.



From mad at auth.se  Wed Mar 16 16:37:41 2011
From: mad at auth.se (Mad)
Date: Wed, 16 Mar 2011 17:37:41 +0100
Subject: =?UTF-8?Q?cell=5Flog=20and=20kalibrator?=
In-Reply-To: <4D800995.1040705@stud.ntnu.no>
References: <4D800995.1040705@stud.ntnu.no>
Message-ID: <a4ca39efa63ad92915bdd67b9c9f05c7@auth.se>

 On Wed, 16 Mar 2011 01:51:33 +0100, suraev at stud.ntnu.no wrote:
> Hey.
>
> Did I got it right that instead of using at commands and gprs-capable
> modem for clock
> calibration (as in
> http://gnuradio.org/redmine/wiki/1/OpenBTSClockCalibration) we can
> use output of [power] section of cell_log?

 Like any other method to view surrounding cells broadcast arfcns and
 its signal levels, like a netmonitor on some phones.

> For example I got following in cell_log:
> arfcn 740 -99 -105 -109 -108 -110 -107 -108 -103 -109 -108 -110 -100
> Seems like pretty good signal strength.

 No, it's not. Notice the "-" in front of the value. This means the 
 higher
 the value ("less negative"), the stronger the signal.


 Regards,
   Mad



From Andreas.Eversberg at versatel.de  Wed Mar 16 08:14:50 2011
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Wed, 16 Mar 2011 09:14:50 +0100
Subject: quad-band support
Message-ID: <B16317F2B1592B4492FC414114171CE605302A80@FLBVEXCH01.versatel.local>

hi,
 
i like to introduce support for additional bands for osmocom/layer23:
 
- GSM 850
- PCS (1900)
- GSM 480 and GSM 450
 
all bands can be enabled/disabled individually via VTY settings. by
default, only 900 and DCS (1800) are enabled. note that the bands must
be supported by the phone's tranceiver in order use them.
 
to test it in the US, change your VTY settings like this:
 
enable
configure terminal
ms 1  (or whatever your instance name is)
 support
  no p-gsm
  no e-gsm
  no r-gsm
  gsm-850
  no dcs
  pcs
end
write

of course you may enable all four bands, but this makes no sense,
because your hardware does not support all bands.

you will find the support in the jolly/quadband branch. it will be
merged, if it is fully tested. 

be sure to set "ulimit unlimited" in your shell to get a core dump in
case of a crash, so you can use gdb to locate where it happened:
"gdb ./mobile core"

everything else should work as usual.

regards,

andreas



From Andreas.Eversberg at versatel.de  Wed Mar 16 08:48:07 2011
From: Andreas.Eversberg at versatel.de (Andreas.Eversberg)
Date: Wed, 16 Mar 2011 09:48:07 +0100
Subject: AW: quad-band support
Message-ID: <B16317F2B1592B4492FC414114171CE605302AD7@FLBVEXCH01.versatel.local>

please note: remove the ".ba" files from your osmocom config dir when
switching back to mobile of master branch. this is because the structure
of the band allocation file has changed. the new file includes a version
string that must match, so there is no need to remove the file when
upgrading in the future or when changing to the quadband branch.



From 246tnt at gmail.com  Wed Mar 16 08:57:36 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Wed, 16 Mar 2011 09:57:36 +0100
Subject: quad-band support
In-Reply-To: <B16317F2B1592B4492FC414114171CE605302A80@FLBVEXCH01.versatel.local>
References: <B16317F2B1592B4492FC414114171CE605302A80@FLBVEXCH01.versatel.local>
Message-ID: <AANLkTi=sZOVm2F0m4vwuR1Fv5TByLJwANZD_Q5QoE9WL@mail.gmail.com>

Hi

> i like to introduce support for additional bands for osmocom/layer23:
>
> - GSM 850
> - PCS (1900)
> - GSM 480 and GSM 450

Pretty cool !

I'll implement the few missing bits in layer 1 to properly support
those tonight. (just rita pll config missing).


The patch seems to have a few typo/debug stuff that slipped:

 * 399 referenced sometime instead of 299
 * a "+// JOLLY" debug marker inserted around line 143
 * LOGP replaced by printf at line 289


Cheers,

    Sylvain



From el.panzerito at gmail.com  Thu Mar 17 18:36:55 2011
From: el.panzerito at gmail.com (Sergio Basan)
Date: Thu, 17 Mar 2011 20:36:55 +0200
Subject: Vcc c155?
Message-ID: <AANLkTi=ahVh+ANOiE1PAe1poASW8ZMhdR+=2zoY7ggf0@mail.gmail.com>

Hi

I want to join the team. But, What is the Vcc of motorola c155? Sorry,
I could not find this trifling matter on the Internet.



From el.panzerito at gmail.com  Thu Mar 17 18:40:49 2011
From: el.panzerito at gmail.com (Sergio Basan)
Date: Thu, 17 Mar 2011 20:40:49 +0200
Subject: Vcc c155?
Message-ID: <AANLkTi=0JwP9zrcyHpv_hR8ZVUBKNnEq2qnj+fPCOa2m@mail.gmail.com>

Hi

I want to join the team. But, What is the Vcc of motorola c155? Sorry,
I could not find this trifling matter on the Internet.



From henk.vergonet at gmail.com  Thu Mar 17 21:33:29 2011
From: henk.vergonet at gmail.com (Henk)
Date: Thu, 17 Mar 2011 22:33:29 +0100
Subject: Vcc c155?
Message-ID: <ve0ia0ledv9ssb54p8h4xdxv.1300397609340@email.android.com>

Well the datacable for c155 is a T191 so 3.3v. This is not the answer to your question but i hope it helps. ;)

From el.panzerito at gmail.com  Thu Mar 17 22:47:00 2011
From: el.panzerito at gmail.com (Sergio Basan)
Date: Fri, 18 Mar 2011 00:47:00 +0200
Subject: Vcc c155?
In-Reply-To: <ve0ia0ledv9ssb54p8h4xdxv.1300397609340@email.android.com>
	(Henk's message of "Thu, 17 Mar 2011 22:33:29 +0100")
References: <ve0ia0ledv9ssb54p8h4xdxv.1300397609340@email.android.com>
Message-ID: <877hbx8ivv.fsf@sinica.com>

Henk <henk.vergonet at gmail.com> writes:

> Well the datacable for c155 is a T191 so 3.3v. This is not the answer to your question but i hope it helps. ;)
I have not charger. Information from NCP345-D.PDF: Vcc no more than 5 volts. But... 



From el.panzerito at gmail.com  Fri Mar 18 19:05:53 2011
From: el.panzerito at gmail.com (Sergio Basan)
Date: Fri, 18 Mar 2011 21:05:53 +0200
Subject: Vcc c155?
In-Reply-To: <877hbx8ivv.fsf@sinica.com> (Sergio Basan's message of "Fri,
	18 Mar 2011 00:47:00 +0200")
References: <ve0ia0ledv9ssb54p8h4xdxv.1300397609340@email.android.com>
	<877hbx8ivv.fsf@sinica.com>
Message-ID: <87hbb0p7u6.fsf@sinica.com>


What voltage is written on the charger?



From vogelchr at vogel.cx  Sat Mar 19 12:04:54 2011
From: vogelchr at vogel.cx (Christian Vogel)
Date: Sat, 19 Mar 2011 13:04:54 +0100
Subject: Vcc c155?
In-Reply-To: <87hbb0p7u6.fsf@sinica.com>
References: <ve0ia0ledv9ssb54p8h4xdxv.1300397609340@email.android.com>
	<877hbx8ivv.fsf@sinica.com> <87hbb0p7u6.fsf@sinica.com>
Message-ID: <op.vslaigl6unbdei@mischief.dillberg.com>


Am 18.03.2011, 20:05 Uhr, schrieb Sergio Basan <el.panzerito at gmail.com>:
> What voltage is written on the charger?

230V? :-)




... and 3.6V, 600mA

	Chris




From steve at steve-m.de  Sat Mar 19 12:24:34 2011
From: steve at steve-m.de (Steve Markgraf)
Date: Sat, 19 Mar 2011 13:24:34 +0100
Subject: Vcc c155?
In-Reply-To: <op.vslaigl6unbdei@mischief.dillberg.com>
References: <ve0ia0ledv9ssb54p8h4xdxv.1300397609340@email.android.com>	<877hbx8ivv.fsf@sinica.com>
	<87hbb0p7u6.fsf@sinica.com>
	<op.vslaigl6unbdei@mischief.dillberg.com>
Message-ID: <4D84A082.4040800@steve-m.de>

Hi,

On 19.03.2011 13:04, Christian Vogel wrote:
>> What voltage is written on the charger?
>
> 230V? :-)
> ... and 3.6V, 600mA

But well, that is not really true. There are 2 versions of the charger, 
the normal heavy one with transformer, and a light SMPS-one.
The first one delivers 5.94V without load, and the SMPS-version even 
6.38V. The SMPS-one states "5.0V 350mA".

You need at least > 4.2V, since that's the voltage the battery is being 
charged to.

And of course the datasheet of the used charging regulator, Intersil 
ISL6292C states:

 > Supply Voltage, VIN . . . 4.3V to 6.5V

Regards,
Steve



From lbernal at gmail.com  Sat Mar 19 12:30:57 2011
From: lbernal at gmail.com (n0p [Luis Bernal])
Date: Sat, 19 Mar 2011 13:30:57 +0100
Subject: Vcc c155?
In-Reply-To: <4D84A082.4040800@steve-m.de>
References: <ve0ia0ledv9ssb54p8h4xdxv.1300397609340@email.android.com>
	<877hbx8ivv.fsf@sinica.com> <87hbb0p7u6.fsf@sinica.com>
	<op.vslaigl6unbdei@mischief.dillberg.com>
	<4D84A082.4040800@steve-m.de>
Message-ID: <AANLkTimOTQR3jdm3s8MGPEH=F83B5+Qf2XLF+2D8HTfL@mail.gmail.com>

the charger works @5V, but I recall that a resistor is needed for the phone
to detect the charger as an original charger

I think your best choice is buying one off ebay

2011/3/19 Steve Markgraf <steve at steve-m.de>

> Hi,
>
>
> On 19.03.2011 13:04, Christian Vogel wrote:
>
>> What voltage is written on the charger?
>>>
>>
>> 230V? :-)
>> ... and 3.6V, 600mA
>>
>
> But well, that is not really true. There are 2 versions of the charger, the
> normal heavy one with transformer, and a light SMPS-one.
> The first one delivers 5.94V without load, and the SMPS-version even 6.38V.
> The SMPS-one states "5.0V 350mA".
>
> You need at least > 4.2V, since that's the voltage the battery is being
> charged to.
>
> And of course the datasheet of the used charging regulator, Intersil
> ISL6292C states:
>
> > Supply Voltage, VIN . . . 4.3V to 6.5V
>
> Regards,
> Steve
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110319/c9b3adbe/attachment.htm>

From laforge at gnumonks.org  Tue Mar 22 09:17:18 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 22 Mar 2011 10:17:18 +0100
Subject: Vcc c155?
In-Reply-To: <AANLkTimOTQR3jdm3s8MGPEH=F83B5+Qf2XLF+2D8HTfL@mail.gmail.com>
References: <ve0ia0ledv9ssb54p8h4xdxv.1300397609340@email.android.com>
	<877hbx8ivv.fsf@sinica.com> <87hbb0p7u6.fsf@sinica.com>
	<op.vslaigl6unbdei@mischief.dillberg.com>
	<4D84A082.4040800@steve-m.de>
	<AANLkTimOTQR3jdm3s8MGPEH=F83B5+Qf2XLF+2D8HTfL@mail.gmail.com>
Message-ID: <20110322091718.GE9858@prithivi.gnumonks.org>

On Sat, Mar 19, 2011 at 01:30:57PM +0100, n0p [Luis Bernal] wrote:
> the charger works @5V, but I recall that a resistor is needed for the phone
> to detect the charger as an original charger

The charger uses a 2-pin connector, so where do you think an ID resistor should
be used?  Motorola uses ID resistors in their mini-USB based chargers, but for
a 2-pin connector, I don't think that is true.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From lbernal at gmail.com  Tue Mar 22 10:55:28 2011
From: lbernal at gmail.com (n0p [Luis Bernal])
Date: Tue, 22 Mar 2011 11:55:28 +0100
Subject: Vcc c155?
In-Reply-To: <20110322091718.GE9858@prithivi.gnumonks.org>
References: <ve0ia0ledv9ssb54p8h4xdxv.1300397609340@email.android.com>
	<877hbx8ivv.fsf@sinica.com> <87hbb0p7u6.fsf@sinica.com>
	<op.vslaigl6unbdei@mischief.dillberg.com>
	<4D84A082.4040800@steve-m.de>
	<AANLkTimOTQR3jdm3s8MGPEH=F83B5+Qf2XLF+2D8HTfL@mail.gmail.com>
	<20110322091718.GE9858@prithivi.gnumonks.org>
Message-ID: <AANLkTik90SG-HxSaxOWhXiNXi8jKy93zu2GeAxd3bKGX@mail.gmail.com>

we are sucessfully charging our mobiles with a 100ohm resistor in parallel
to a 5V supply, so like galileo said, "but it moves" xD

2011/3/22 Harald Welte <laforge at gnumonks.org>

> On Sat, Mar 19, 2011 at 01:30:57PM +0100, n0p [Luis Bernal] wrote:
> > the charger works @5V, but I recall that a resistor is needed for the
> phone
> > to detect the charger as an original charger
>
> The charger uses a 2-pin connector, so where do you think an ID resistor
> should
> be used?  Motorola uses ID resistors in their mini-USB based chargers, but
> for
> a 2-pin connector, I don't think that is true.
>
> --
> - Harald Welte <laforge at gnumonks.org>
> http://laforge.gnumonks.org/
>
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
>                                                  (ETSI EN 300 175-7 Ch. A6)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110322/0bfa0f2c/attachment.htm>

From henk.vergonet at gmail.com  Thu Mar 17 22:25:22 2011
From: henk.vergonet at gmail.com (Henk)
Date: Thu, 17 Mar 2011 23:25:22 +0100
Subject: require your help
In-Reply-To: <AANLkTikkFe=WmZanHdRGOemdYucV_HCffxaP7+sEM+Si@mail.gmail.com>
References: <AANLkTikkFe=WmZanHdRGOemdYucV_HCffxaP7+sEM+Si@mail.gmail.com>
Message-ID: <AANLkTinjRABOOfRX=5nzZ4-x-o3t26WpQh3sAkMkZotE@mail.gmail.com>

Hmm lets continue on the list...

Well try to keep it simple, probably some config is needed from top
level makefiles.

This is what i use:

export PATH=$PATH:/home/xxxyyyx/prj/toolchain/arm-elf/bin
cd src
make -e CROSS_TOOL_PREFIX=arm-elf-


On Thu, Mar 17, 2011 at 1:16 PM, royfarji india <roy.techie at gmail.com> wrote:
> Hello henk,
> Sorry to bother you for this.I am a student and have little trouble in
> building osmocom.I require your help please.
> While building the project osmocom I get this error? saying? that the header
> file 'signal.h' is missing in osmocore.I am just uanble to figure it how it
> is unable to include the header file.By the way I am using the gnuarm-3.4.3
> as shown on the osmocom-bb website.One more query please - as to exactly
> where do we have to put the armtoolchain(meaning which directory).Waiting
> eagerly for your reply.
>
>
>
> roy at roy:~/osmocom-bb$ cd src
> roy at roy:~/osmocom-bb/src$ make
> cd shared/libosmocore/build-
> target && ../configure \
> ??????????? --host=arm-elf-linux --disable-vty --enable-panic-infloop \
> ??????????? --disable-shared --disable-talloc --disable-tests \
> ??????? CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections
> -I/home/roy/osmocom-bb/src/target/firmware/include -nostartfiles
> -nodefaultlibs"
> configure: WARNING: if you wanted to set the --build type, don't use --host.
> ??? If a cross compiler is detected then cross compile mode will be used
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for arm-elf-linux-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 sets $(MAKE)... (cached) yes
> checking for arm-elf-linux-gcc... arm-elf-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 arm-elf-gcc accepts -g... yes
> checking for arm-elf-gcc option to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of arm-elf-gcc... gcc3
> checking build system type... i686-pc-linux-gnu
> checking host system type... arm-elf-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by arm-elf-gcc...
> /home/roy/osmocom-bb/gnuarm-3.4.3/arm-elf/bin/ld
> checking if the linker (/home/roy/osmocom-bb/gnuarm-3.4.3/arm-elf/bin/ld) is
> GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... no
> checking for arm-elf-linux-dumpbin... no
> checking for arm-elf-linux-link... no
> checking for dumpbin... no
> checking for link... link -dump -symbols
> configure: WARNING: using cross tools not prefixed with host triplet
> checking the name lister (link -dump -symbols) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 805306365
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /home/roy/osmocom-bb/gnuarm-3.4.3/arm-elf/bin/ld option to
> reload object files... -r
> checking for arm-elf-linux-objdump... no
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for arm-elf-linux-ar... no
> checking for ar... ar
> checking for arm-elf-linux-strip... strip
> checking for arm-elf-linux-ranlib... no
> checking for ranlib... ranlib
> checking command to parse link -dump -symbols output from arm-elf-gcc
> object... failed
> checking how to run the C preprocessor... arm-elf-gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... no
> checking for inttypes.h... no
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... no
> checking for objdir... .libs
> checking if arm-elf-gcc supports -fno-rtti -fno-exceptions... no
> checking for arm-elf-gcc option to produce PIC... -fPIC -DPIC
> checking if arm-elf-gcc PIC flag -fPIC -DPIC works... yes
> checking if arm-elf-gcc static flag -static works... yes
> checking if arm-elf-gcc supports -c -o file.o... yes
> checking if arm-elf-gcc supports -c -o file.o... (cached) yes
> checking whether the arm-elf-gcc linker
> (/home/roy/osmocom-bb/gnuarm-3.4.3/arm-elf/bin/ld) supports shared
> libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... no
> checking whether to build static libraries... yes
> checking for ANSI C header files... (cached) yes
> checking execinfo.h usability... no
> checking execinfo.h presence... no
> checking for execinfo.h... no
> checking sys/select.h usability... no
> checking sys/select.h presence... no
> checking for sys/select.h... no
> checking if arm-elf-gcc supports -fvisibility=hidden... no
> configure: creating ./config.status
> config.status: creating libosmocore.pc
> config.status: creating libosmocodec.pc
> config.status: creating libosmovty.pc
> config.status: creating include/osmocom/Makefile
> config.status: creating include/osmocom/vty/Makefile
> config.status: creating include/osmocom/codec/Makefile
> config.status: creating include/osmocom/crypt/Makefile
> config.status: creating include/osmocore/Makefile
> config.status: creating include/osmocore/protocol/Makefile
> config.status: creating include/Makefile
> config.status: creating src/Makefile
> config.status: creating src/vty/Makefile
> config.status: creating src/codec/Makefile
> config.status: creating tests/Makefile
> config.status: creating tests/timer/Makefile
> config.status: creating tests/sms/Makefile
> config.status: creating tests/msgfile/Makefile
> config.status: creating tests/ussd/Makefile
> config.status: creating tests/smscb/Makefile
> config.status: creating Makefile
> config.status: creating config.h
> config.status: config.h is unchanged
> config.status: executing depfiles commands
> config.status: executing libtool commands
> cd shared/libosmocore/build-target && make
> make[1]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
> make? all-recursive
> make[2]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
> Making all in include
> make[3]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'
> Making all in osmocom
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
> Making all in codec
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec'
> Making all in crypt
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt'
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
> make[5]: Nothing to be done for `all-am'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom'
> Making all in osmocore
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
> Making all in protocol
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol'
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
> make[5]: Nothing to be done for `all-am'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore'
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'
> make[4]: Nothing to be done for `all-am'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'
> make[3]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include'
> Making all in src
> make[3]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'
> Making all in .
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'
> make[4]: Nothing to be done for `all-am'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'
> Making all in vty
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty'
> Making all in codec
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec'
> make[3]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src'
> Making all in tests
> make[3]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'
> make[4]: Nothing to be done for `all-am'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'
> make[3]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests'
> make[3]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
> make[3]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
> make[2]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
> make[1]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-target'
> cd shared/libosmocore/build-host && ../configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> 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 sets $(MAKE)... (cached) yes
> 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... no
> 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
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 805306365
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for ar... ar
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC
> checking if gcc PIC flag -fPIC -DPIC works... yes
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether the gcc linker (/usr/bin/ld) supports shared libraries...
> yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> checking for ANSI C header files... (cached) yes
> checking execinfo.h usability... yes
> checking execinfo.h presence... yes
> checking for execinfo.h... yes
> checking sys/select.h usability... yes
> checking sys/select.h presence... yes
> checking for sys/select.h... yes
> checking if gcc supports -fvisibility=hidden... yes
> configure: creating ./config.status
> config.status: creating libosmocore.pc
> config.status: creating libosmocodec.pc
> config.status: creating libosmovty.pc
> config.status: creating include/osmocom/Makefile
> config.status: creating include/osmocom/vty/Makefile
> config.status: creating include/osmocom/codec/Makefile
> config.status: creating include/osmocom/crypt/Makefile
> config.status: creating include/osmocore/Makefile
> config.status: creating include/osmocore/protocol/Makefile
> config.status: creating include/Makefile
> config.status: creating src/Makefile
> config.status: creating src/vty/Makefile
> config.status: creating src/codec/Makefile
> config.status: creating tests/Makefile
> config.status: creating tests/timer/Makefile
> config.status: creating tests/sms/Makefile
> config.status: creating tests/msgfile/Makefile
> config.status: creating tests/ussd/Makefile
> config.status: creating tests/smscb/Makefile
> config.status: creating Makefile
> config.status: creating config.h
> config.status: config.h is unchanged
> config.status: executing depfiles commands
> config.status: executing libtool commands
> cd shared/libosmocore/build-host && make
> make[1]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
> make? all-recursive
> make[2]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
> Making all in include
> make[3]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include'
> Making all in osmocom
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom'
> Making all in vty
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/vty'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/vty'
> Making all in codec
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/codec'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/codec'
> Making all in crypt
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/crypt'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/crypt'
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom'
> make[5]: Nothing to be done for `all-am'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom'
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom'
> Making all in osmocore
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
> Making all in protocol
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol'
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
> make[5]: Nothing to be done for `all-am'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore'
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include'
> make[4]: Nothing to be done for `all-am'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include'
> make[3]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include'
> Making all in src
> make[3]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src'
> Making all in .
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src'
> make[4]: Nothing to be done for `all-am'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src'
> Making all in vty
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/vty'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/vty'
> Making all in codec
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/codec'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/codec'
> make[3]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src'
> Making all in tests
> make[3]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests'
> Making all in timer
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/timer'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/timer'
> Making all in sms
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/sms'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/sms'
> Making all in ussd
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/ussd'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/ussd'
> Making all in smscb
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/smscb'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/smscb'
> Making all in msgfile
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/msgfile'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/msgfile'
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests'
> make[4]: Nothing to be done for `all-am'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests'
> make[3]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests'
> make[3]: Entering directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
> make[3]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
> make[2]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
> make[1]: Leaving directory
> `/home/roy/osmocom-bb/src/shared/libosmocore/build-host'
> make -C host/layer23
> make[1]: Entering directory `/home/roy/osmocom-bb/src/host/layer23'
> Making all in include
> make[2]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include'
> Making all in osmocom
> make[3]: Entering directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom'
> Making all in bb
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb'
> Making all in common
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/common'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/common'
> Making all in misc
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/misc'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/misc'
> Making all in mobile
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/mobile'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/mobile'
> make[5]: Entering directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb'
> make[5]: Nothing to be done for `all-am'.
> make[5]: Leaving directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb'
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb'
> make[4]: Entering directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom'
> make[4]: Nothing to be done for `all-am'.
> make[4]: Leaving directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom'
> make[3]: Leaving directory
> `/home/roy/osmocom-bb/src/host/layer23/include/osmocom'
> make[3]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include'
> make[3]: Nothing to be done for `all-am'.
> make[3]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include'
> make[2]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include'
> Making all in src
> make[2]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/src'
> Making all in common
> make[3]: Entering directory
> `/home/roy/osmocom-bb/src/host/layer23/src/common'
> ? CC???? l1ctl.o
> l1ctl.c:33: fatal error: osmocore/signal.h: No such file or directory
> compilation terminated.
> make[3]: *** [l1ctl.o] Error 1
> make[3]: Leaving directory
> `/home/roy/osmocom-bb/src/host/layer23/src/common'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23'
> make: *** [host/layer23/layer23] Error 2
>



From turuwhiska at hotmail.com  Thu Mar 17 22:42:39 2011
From: turuwhiska at hotmail.com (francisco flores)
Date: Thu, 17 Mar 2011 22:42:39 +0000
Subject: problem with dream g2
Message-ID: <BLU157-w551864102D07A45CBC4C5EC6B10@phx.gbl>


hi im francisco from argentina . i can compiled the code for sciphone dream g2 . i make the serial cable but no work
is necesary configuration phone? o the conversor usb to serial? because i conect the cable a usb from mi pc and no work
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110317/8cb71430/attachment.htm>

From suraev at stud.ntnu.no  Mon Mar 21 03:07:13 2011
From: suraev at stud.ntnu.no (suraev at stud.ntnu.no)
Date: Mon, 21 Mar 2011 04:07:13 +0100
Subject: osmocon on gta02
Message-ID: <4D86C0E1.6060105@stud.ntnu.no>

Hello.

I've updated & rebuilt osmocom and now I can't use osmocon on gta02 anymore :(

Previously I started it like:

./osmocon -i 13 -m romload -p /dev/ttySAC0 layer1.highram.bin

power-cycle modem and it started to load firmware.

However with recent version firmware is loaded even without power-cycle!

When I use hello_world.highram.bin I got exactly the same output as before.
But when I use layer1.highram.bin I have problems running
osmoload -l /tmp/loader ping
Query timed out.

What went wrong and how do I fix it?

best regards,
Max.





From suraev at stud.ntnu.no  Mon Mar 21 03:52:15 2011
From: suraev at stud.ntnu.no (suraev at stud.ntnu.no)
Date: Mon, 21 Mar 2011 04:52:15 +0100
Subject: osmocon on gta02
In-Reply-To: <4D86C0E1.6060105@stud.ntnu.no>
References: <4D86C0E1.6060105@stud.ntnu.no>
Message-ID: <4D86CB6F.6010809@stud.ntnu.no>

I just realized that it looks like I just unable to power-down modem on shr:
# echo 0> /sys/bus/platform/devices/gta02-pm-gsm.0/power_on
# cat /sys/bus/platform/devices/gta02-pm-gsm.0/power_on
1

I'm not sure if it's really so and how can I fix this...

Here is the dump I got with compal_dsp_dump.highram.bin payload:

OSMOCOM Compal DSP Dumper (revision osmocon_v0.0.0-780-gb7a4d8d-modified)
======================================================================
Device ID code: 0xb496
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: e4942706e4949b52
======================================================================
Assert DSP into Reset
Releasing DSP from Reset
DSP bootloader version 0x0100
DSP dump: Registers [00000-0005f]
00000 : fe77 0008 0008 0008 8030 8030 181f 2900 0000 0000 0000 0060 0000 0000 0000 f45f
00010 : 73be 005f 0813 0014 0003 0014 dff2 ff8e 1100 feff dee3 0000 1fd5 ffa8 0000 0000

Btw, where can I get documentation which will help to interpret those values properly?

looking forward for your advice,
Max.



From suraev at stud.ntnu.no  Mon Mar 21 12:03:25 2011
From: suraev at stud.ntnu.no (suraev at stud.ntnu.no)
Date: Mon, 21 Mar 2011 13:03:25 +0100
Subject: osmocon on gta02
In-Reply-To: <4D86C0E1.6060105@stud.ntnu.no>
References: <4D86C0E1.6060105@stud.ntnu.no>
Message-ID: <4D873E8D.60309@stud.ntnu.no>

False alarm - mistake on my part: not all modem-related services were disabled.
Problem solved, wiki updated.

sorry for all the fuzz,
Max.



From cyrus104 at gmail.com  Tue Mar 22 19:40:05 2011
From: cyrus104 at gmail.com (Derek Murphy)
Date: Tue, 22 Mar 2011 15:40:05 -0400
Subject: Compiling issue
Message-ID: <AANLkTi=YGztq79nU-2GAGMqd4452E6UMX5M5qS2M0LQN@mail.gmail.com>

I'm running Ubuntu 10.10 and having a couple of issues.

I've got both options for the toolchain work, only one is in the path at a
time while testing.

With one of them it seems to compile fine: I can use ./osmocom with
something like hello world and this works. However when I go to look at
layer23 the binary has not been compiled and I have this error in the
conf.log:

configure:3833: checking for gps_waiting in -lgps
configure:3858: gcc -o conftest -g -O2   conftest.c -lgps   >&5
/usr/bin/ld: cannot find -lgps
collect2: ld returned 1 exit status
configure:3858: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| #define PACKAGE "layer23"
| #define VERSION "0.0.0"
| /* end confdefs.h.  */


I'm sure most of these are environment error but wanted to check. In the
update-libosmocore.sh I get an error that git-subtree doesn't exist. I found
git subtree as a third party install that was not in the documentation but
it's command is git subtree versus being git-subtree.

Any thoughts would be appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110322/023f19b7/attachment.htm>

From cyrus104 at gmail.com  Tue Mar 22 20:12:59 2011
From: cyrus104 at gmail.com (Derek Murphy)
Date: Tue, 22 Mar 2011 16:12:59 -0400
Subject: Compiling issue
In-Reply-To: <AANLkTi=YGztq79nU-2GAGMqd4452E6UMX5M5qS2M0LQN@mail.gmail.com>
References: <AANLkTi=YGztq79nU-2GAGMqd4452E6UMX5M5qS2M0LQN@mail.gmail.com>
Message-ID: <AANLkTi=ZVdELT+ZQ=qU7fOKv8igfR7PVT2cqNk2hiL=8@mail.gmail.com>

Of course after I wrote that I figured I'd look into the mobile application
and can load that just fine. I'm having an issue with not actually have a
sim card in it yet as they are much harder to come by if your provider
doesn't use them.


I'm running Ubuntu 10.10 and having a couple of issues.
>
> I've got both options for the toolchain work, only one is in the path at a
> time while testing.
>
> With one of them it seems to compile fine: I can use ./osmocom with
> something like hello world and this works. However when I go to look at
> layer23 the binary has not been compiled and I have this error in the
> conf.log:
>
> configure:3833: checking for gps_waiting in -lgps
> configure:3858: gcc -o conftest -g -O2   conftest.c -lgps   >&5
> /usr/bin/ld: cannot find -lgps
> collect2: ld returned 1 exit status
> configure:3858: $? = 1
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME ""
> | #define PACKAGE_TARNAME ""
> | #define PACKAGE_VERSION ""
> | #define PACKAGE_STRING ""
> | #define PACKAGE_BUGREPORT ""
> | #define PACKAGE_URL ""
> | #define PACKAGE "layer23"
> | #define VERSION "0.0.0"
> | /* end confdefs.h.  */
>
>
> I'm sure most of these are environment error but wanted to check. In the
> update-libosmocore.sh I get an error that git-subtree doesn't exist. I found
> git subtree as a third party install that was not in the documentation but
> it's command is git subtree versus being git-subtree.
>
> Any thoughts would be appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110322/c4eca296/attachment.htm>

From laforge at gnumonks.org  Wed Mar 23 17:39:03 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Wed, 23 Mar 2011 18:39:03 +0100
Subject: [PATCH OSMOCOM-BB] src: use new libosmogsm and
	include/osmocom/[gsm|core] path to headers
In-Reply-To: <1300810618-13712-1-git-send-email-pablo@gnumonks.org>
References: <1300810618-13712-1-git-send-email-pablo@gnumonks.org>
Message-ID: <20110323173903.GE20261@prithivi.gnumonks.org>

Hi Pablo,

On Tue, Mar 22, 2011 at 05:16:58PM +0100, pablo at gnumonks.org wrote:
 
> This patch also renames hexdump in osmocon.c and osmoload.c
> to avoid clashing with hexdump defined in libosmocore. This
> is a workaround, it's planned to fix the namespace pollution
> of the library soon.
 
how did you test this patch?  Did you first update the libosmocore copy
inside osmocom-bb.git using 'git-subtree', and then apply + test your patch?

Did you make sure that new libosmocore will also build using the cross-compiler
for the phone firmware (see + use the osmocom-bb/src/Makefile) ?

Also, for the future: please note the mailing list for osmocom-bb is
'baseband-deve at lists.osmocom.org', not the openbsc list...

Thanks,
	Harald

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From pablo at gnumonks.org  Thu Mar 24 00:03:41 2011
From: pablo at gnumonks.org (Pablo Neira Ayuso)
Date: Thu, 24 Mar 2011 01:03:41 +0100
Subject: [PATCH OSMOCOM-BB] src: use new libosmogsm
	and	include/osmocom/[gsm|core] path to headers
In-Reply-To: <20110323173903.GE20261@prithivi.gnumonks.org>
References: <1300810618-13712-1-git-send-email-pablo@gnumonks.org>
	<20110323173903.GE20261@prithivi.gnumonks.org>
Message-ID: <4D8A8A5D.7070206@gnumonks.org>

Hi Harald,

On 23/03/11 18:39, Harald Welte wrote:
> Hi Pablo,
> 
> On Tue, Mar 22, 2011 at 05:16:58PM +0100, pablo at gnumonks.org wrote:
>  
>> This patch also renames hexdump in osmocon.c and osmoload.c
>> to avoid clashing with hexdump defined in libosmocore. This
>> is a workaround, it's planned to fix the namespace pollution
>> of the library soon.
>  
> how did you test this patch?  Did you first update the libosmocore copy
> inside osmocom-bb.git using 'git-subtree', and then apply + test your patch?

I compiled it, only compile-tested. I got an openmoko phone so now I'll
be able to perform further testing.

> Did you make sure that new libosmocore will also build using the cross-compiler
> for the phone firmware (see + use the osmocom-bb/src/Makefile) ?

Yes, I modified the Makefile to get it working with the new changes.

> Also, for the future: please note the mailing list for osmocom-bb is
> 'baseband-deve at lists.osmocom.org', not the openbsc list...

I see I'll use the appropriate mailing list next time, sorry.



From weberbe at ee.ethz.ch  Wed Mar 23 18:14:29 2011
From: weberbe at ee.ethz.ch (weberbe at ee.ethz.ch)
Date: Wed, 23 Mar 2011 19:14:29 +0100
Subject: bcch_scan initialization and L1
Message-ID: <20110323191429.92534myk321bcccl@email.ee.ethz.ch>

Hi everbody

I'm currently working on a project at our university where we are  
trying to connect bcch_scan with our existing hardware/software. The  
latter consists of L1 implementation partly in hardware and partly in  
software. The software part is also used to provide the interface  
towards bcch_scan. So far, the software interface does not do much it  
just provides the necessary domain sockets and dumps everything it  
receives from bcch_scan.
Now, my question is whether there is some kind of initialization  
sequences sent from bcch_scan to the phone. And is there any other  
info you can provide about the messages sent from bcch_scan to the  
phone and the other way round? Naturally, I tried to find this out  
myself by looking though the source but didn't get very far.

Oh and by the way, the ultimate goal of this project is that we can  
use bcch_scan to test our L1 hardware. This would be pretty cool

Thanks in advance
Benjamin





From laforge at gnumonks.org  Wed Mar 23 22:35:39 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Wed, 23 Mar 2011 23:35:39 +0100
Subject: bcch_scan initialization and L1
In-Reply-To: <20110323191429.92534myk321bcccl@email.ee.ethz.ch>
References: <20110323191429.92534myk321bcccl@email.ee.ethz.ch>
Message-ID: <20110323223539.GF4534@prithivi.gnumonks.org>

Hi!

On Wed, Mar 23, 2011 at 07:14:29PM +0100, weberbe at ee.ethz.ch wrote:
 
> Now, my question is whether there is some kind of initialization
> sequences sent from bcch_scan to the phone. And is there any other
> info you can provide about the messages sent from bcch_scan to the
> phone and the other way round? Naturally, I tried to find this out
> myself by looking though the source but didn't get very far.

I suggest you look at the L1CTL header file and simply monitor the serial
communication on the UART while bcch_scan is talking to the phone.

> Oh and by the way, the ultimate goal of this project is that we can
> use bcch_scan to test our L1 hardware. This would be pretty cool

is that hardware an open hardware design, i.e. are/will the schematics or even
gerber files be publicly available?

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From weberbe at ee.ethz.ch  Fri Mar 25 15:06:11 2011
From: weberbe at ee.ethz.ch (weberbe at ee.ethz.ch)
Date: Fri, 25 Mar 2011 16:06:11 +0100
Subject: bcch_scan initialization and L1
In-Reply-To: <20110323223539.GF4534@prithivi.gnumonks.org>
References: <20110323191429.92534myk321bcccl@email.ee.ethz.ch>
	<20110323223539.GF4534@prithivi.gnumonks.org>
Message-ID: <20110325160611.150944x2i9kft5cz@email.ee.ethz.ch>

Hi Harald




Quoting "Harald Welte" <laforge at gnumonks.org>:

> Hi!
>
> On Wed, Mar 23, 2011 at 07:14:29PM +0100, weberbe at ee.ethz.ch wrote:
>
>> Now, my question is whether there is some kind of initialization
>> sequences sent from bcch_scan to the phone. And is there any other
>> info you can provide about the messages sent from bcch_scan to the
>> phone and the other way round? Naturally, I tried to find this out
>> myself by looking though the source but didn't get very far.
>
> I suggest you look at the L1CTL header file and simply monitor the serial
> communication on the UART while bcch_scan is talking to the phone.
>

Thanks for the quick reply, it helped a lot.

>> Oh and by the way, the ultimate goal of this project is that we can
>> use bcch_scan to test our L1 hardware. This would be pretty cool
>
> is that hardware an open hardware design, i.e. are/will the  
> schematics or even
> gerber files be publicly available?
>

Well our project is currently just a simulation in Simulink, so no  
real hardware.

> --
> - Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
>                                                   (ETSI EN 300 175-7 Ch. A6)
>






From laforge at gnumonks.org  Thu Mar 24 10:43:13 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 24 Mar 2011 11:43:13 +0100
Subject: [ADM] Problems with osmocom git server
Message-ID: <20110324104313.GJ4534@prithivi.gnumonks.org>

Hi all!

We're sorry to report that there are some problems with our git repositories at
the moment, resulting in 'early EOF / index-pack failed' messages when users
are attempting to clone one of our repositories.

The problem has been thoroughly analyzed, but even after many hours of
analysis, no solution has been found yet. Your best chance is to keep re-trying
the clone, in 5-10% of the cases it will succeed.

More technical details are available at this posting to the git mailing list:
http://article.gmane.org/gmane.comp.version-control.git/169909

Sorry for the inconvenience.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From holger at freyther.de  Sat Mar 26 17:43:21 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sat, 26 Mar 2011 18:43:21 +0100
Subject: [ADM] Problems with osmocom git server
In-Reply-To: <20110324104313.GJ4534@prithivi.gnumonks.org>
References: <20110324104313.GJ4534@prithivi.gnumonks.org>
Message-ID: <4D8E25B9.4090201@freyther.de>

On 03/24/2011 11:43 AM, Harald Welte wrote:
> Hi all!

> 
> More technical details are available at this posting to the git mailing list:
> http://article.gmane.org/gmane.comp.version-control.git/169909

Hey,
this seems to be either a race condition in git or in the kernel. I have a
workaround that issues a sleep(1) in the upload-pack program and it seems to
fix the issue. I don't understand how this is changing things (it delays
closing the socket a bit due being the last app to close it).

Right now the git-daemon runs in a thread, I could build a lenny package with
my hack if you want to.

holger



From holger at freyther.de  Sat Mar 26 22:51:35 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sat, 26 Mar 2011 23:51:35 +0100
Subject: [ADM] Problems with osmocom git server
In-Reply-To: <4D8E25B9.4090201@freyther.de>
References: <20110324104313.GJ4534@prithivi.gnumonks.org>
	<4D8E25B9.4090201@freyther.de>
Message-ID: <4D8E6DF7.4020200@freyther.de>

On 03/26/2011 06:43 PM, Holger Hans Peter Freyther wrote:

> Right now the git-daemon runs in a thread, I could build a lenny package with
> my hack if you want to.

I re-built git-core with my patch and installed it on the machine. I have set
all of my packages to hold. Is anyone still getting premature EOF errors?

holger



From Marcin.Mielczarczyk at tieto.com  Thu Mar 24 12:24:42 2011
From: Marcin.Mielczarczyk at tieto.com (Marcin.Mielczarczyk at tieto.com)
Date: Thu, 24 Mar 2011 14:24:42 +0200
Subject: Mediatek RF development informations
Message-ID: <8716C48654180249A0941A44457B9075146DECB68D@EXMB02.eu.tieto.com>

Hi list,

I'd like to give you some informations about findings on Mediatek's RF.
Sciphone G2 has MT6140 transceiver which seems to be different than MT6139.
MT6140 has much more registers to configure at init time (CW0 - CW12, CW15) while MT6139 has just 5 registers (CW0, CW1, CW2, CW9 and CW11).
Common registers for MT6140 and MT6139 has also different fields (i.e. register CW0 has reset bit on different offset on MT6140).
These findings where first discovered during sniffing of BSI interface.
After some time I also found source code for Mediatek's SoCs family on Google Code pages:

http://code.google.com/p/mobile-phone-mtk-project/

You can find there source code with drivers for Mediatek RF part (MT6139, MT6140, Murata antenna switches and Mediatek Power Amplifiers).
Source code is located under "l1/l1d" directory. This part is delivered as source code because Mediatek wants to give customers chance to change RF electronic components (customers are able to write thair own drivers).
The rest of layer 1 code (code which calls RF drivers and uses DSP) is delivered as library "l1.lib".
Thanks to above code I confirmed my concernings about difference between MT6139 and MT6140.

I prepared initial version of drivers for BPI, BSI, BFE (Baseband Front End) and MT6140 and placed them in U-Boot.
MT6140 driver is based on Harald's MT6139 driver from OsmocomBB.
It's initial driver which just configures needed peripherals (BSI, BPI, BFE, TDMA, APC, MT6140, MURA465 and RF3159) and performs TX on given ARFCN channel.
U-Boot command for that is following:

Rf_tx <arfcn>

After execution, using spectrum analyzer you should see transmission on given frequency (so far I just tested on low band).
This code doesn't use APC yet, but driver is already written, it just needs to be tested (it means that TX has currently very low power).
If it comes to RF part, documentation which is available is sufficient, I already know how to configure hardware and I don't expect bigger problems here, that's why I started investigations on DSP.

MT6235 has two DSP processors (master and slave).
These procesors are from Analog Devices family ADSP-218x. Most probably it's ADSP-2181 (it's just assumption, I haven't found any statement about it).
Thanks to code mentioned above it's possible to identify DSP functions and disassemble them.
Above code is compiled for MT6223 (ARM7) SoC and it provides symbols table (file: BIRDCELLTEL23_08B_NEP_162_PCB01_gsm_MT6223_S00.sym).
Most of this code is also available on Sciphone G2 (comparing binary files) and I'm able to identify addresses of functions and break in these functions using JTAG. It means that I can debug on real hardware, that's really convenient and easy to understand what's going on.
I already disassembled functions for DSP init and patch loading over IDMA port (probably DSP code is executed from ROM) and I'll continue this task. Hopefully we'll be able to start sending real TX data soon.

--

Recently I received patches with Linux drivers for Sciphone's USB port from Krzysztof Antonowicz and I wanted to thank for his effort.
Right now it's possible to use Sciphone as Mass Storage device and it'll be possible to run Ethernet gadget.

Unfortunatelly I can't clone Linux/Uboot repository right now and I didn't deliver patches for RF and USB. As soon as I'll succeed cloning of repository, I'll deliver functionality which I described above.
I'll also backport drivers I'm writing now to OsmocomBB.

Best regards,
Marcin


From laforge at gnumonks.org  Fri Mar 25 13:00:42 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 25 Mar 2011 14:00:42 +0100
Subject: [ADM] New commitlog mailing list
Message-ID: <20110325130042.GP12584@prithivi.gnumonks.org>

Hi all!

We haven't had a functioning commit log mailinglist since mid-2009, when the
revision control system of openbsc was converted from svn to git.

Especially today, with the large number of separate git repositories on
http://cgit.osmocom.org/, it is very easy to loose track of what other
developers are doing.

The new mailing list 'osmocom-commitlog' (renamed from openbsc-commits) will
receive updates from all repositories on git.osmocom.org.

Feel free to subscribe at
http://lists.osmocom.org/mailman/listinfo/osmocom-commitlog

Cheers,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From dario.lombardo at libero.it  Sat Mar 26 21:37:02 2011
From: dario.lombardo at libero.it (Dario Lombardo)
Date: Sat, 26 Mar 2011 22:37:02 +0100
Subject: [ADM] New commitlog mailing list
In-Reply-To: <20110325130042.GP12584@prithivi.gnumonks.org>
References: <20110325130042.GP12584@prithivi.gnumonks.org>
Message-ID: <AANLkTi=6zXvc2-yHa22-sD=1gVN+QuKGyuKL4D2s0VBY@mail.gmail.com>

On Fri, Mar 25, 2011 at 2:00 PM, Harald Welte <laforge at gnumonks.org> wrote:
>
> The new mailing list 'osmocom-commitlog' (renamed from openbsc-commits) will
> receive updates from all repositories on git.osmocom.org.
>

Another way to be kept up-to-date with bb commits (and other changes
too) is to subscribe to the RSS feed that trac exports, and that can
be found at

http://bb.osmocom.org/trac/timeline

Dario.



From laforge at gnumonks.org  Sat Mar 26 22:57:00 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Sat, 26 Mar 2011 23:57:00 +0100
Subject: [ADM] New commitlog mailing list
In-Reply-To: <AANLkTi=6zXvc2-yHa22-sD=1gVN+QuKGyuKL4D2s0VBY@mail.gmail.com>
References: <20110325130042.GP12584@prithivi.gnumonks.org>
	<AANLkTi=6zXvc2-yHa22-sD=1gVN+QuKGyuKL4D2s0VBY@mail.gmail.com>
Message-ID: <20110326225700.GL22508@prithivi.gnumonks.org>

Hi Dario,

On Sat, Mar 26, 2011 at 10:37:02PM +0100, Dario Lombardo wrote:
> On Fri, Mar 25, 2011 at 2:00 PM, Harald Welte <laforge at gnumonks.org> wrote:
> >
> > The new mailing list 'osmocom-commitlog' (renamed from openbsc-commits) will
> > receive updates from all repositories on git.osmocom.org.
> >
> 
> Another way to be kept up-to-date with bb commits (and other changes
> too) is to subscribe to the RSS feed that trac exports, and that can
> be found at
> 
> http://bb.osmocom.org/trac/timeline

unfortunately this only works for one repository (osmocom-bb.git), and
not for all the other repositories visible on http://cgit.osmocom.org/

The trac (version we use) does not support multiple repositories associated
with one trac instance :/

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From bch2011 at sina.cn  Sat Mar 26 14:54:42 2011
From: bch2011 at sina.cn (bch2011 at sina.cn)
Date: Sat, 26 Mar 2011 22:54:42 +0800 
Subject: git error
Message-ID: <20110326145442.D45491929C8@mail0.webapp.51uc.com>

$ git clone git://git.osmocom.org/osmocom-bb.git
Cloning into osmocom-bb...
remote: Counting objects: 10960, done.
remote: Compressing objects: 100% (2599/2599), done.
fatal: The remote end hung up unexpectedly8 MiB | 23 KiB/s
fatal: early EOF
fatal: index-pack failed

&nbsp;
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110326/307ef1de/attachment.htm>

From laforge at gnumonks.org  Sat Mar 26 15:21:42 2011
From: laforge at gnumonks.org (Harald Welte)
Date: Sat, 26 Mar 2011 16:21:42 +0100
Subject: git error
In-Reply-To: <20110326145442.D45491929C8@mail0.webapp.51uc.com>
References: <20110326145442.D45491929C8@mail0.webapp.51uc.com>
Message-ID: <20110326152142.GK22508@prithivi.gnumonks.org>

On Sat, Mar 26, 2011 at 10:54:42PM +0800, bch2011 at sina.cn wrote:

> fatal: early EOF
> fatal: index-pack failed

http://bb.osmocom.org/trac/blog/git_eof

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



From bch2011 at sina.cn  Sat Mar 26 14:57:12 2011
From: bch2011 at sina.cn (bch2011 at sina.cn)
Date: Sat, 26 Mar 2011 22:57:12 +0800 
Subject: git help
Message-ID: <20110326145712.204991929C2@mail0.webapp.51uc.com>

$ git clone git://git.osmocom.org/osmocom-bb.git
Cloning into osmocom-bb...
remote: Counting objects: 10960, done.
remote: Compressing objects: 100% (2599/2599), done.
fatal: The remote end hung up unexpectedly8 MiB | 23 KiB/s
fatal: early EOF
fatal: index-pack failed
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110326/cd9607eb/attachment.htm>

From holger at freyther.de  Sat Mar 26 15:28:46 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Sat, 26 Mar 2011 16:28:46 +0100
Subject: git help
In-Reply-To: <20110326145712.204991929C2@mail0.webapp.51uc.com>
References: <20110326145712.204991929C2@mail0.webapp.51uc.com>
Message-ID: <4D8E062E.3060607@freyther.de>

On 03/26/2011 03:57 PM, bch2011 at sina.cn wrote:
> $ git clone git://git.osmocom.org/osmocom-bb.git
> Cloning into osmocom-bb...
> remote: Counting objects: 10960, done.
> remote: Compressing objects: 100% (2599/2599), done.
> fatal: The remote end hung up unexpectedly8 MiB | 23 KiB/s
> fatal: early EOF
> fatal: index-pack failed

Please see
http://lists.osmocom.org/pipermail/baseband-devel/2011-March/001553.html



From cbalke at charter.net  Mon Mar 28 01:54:27 2011
From: cbalke at charter.net (cbalke at charter.net)
Date: Sun, 27 Mar 2011 21:54:27 -0400 (EDT)
Subject: Does the jolly/bts tree work?
Message-ID: <3326c2c5.1d69e.12efa2b5450.Webtop.42@charter.net>


I got two phones working with osmocom-bb.  I compiled jolly/bts and it 
runs with two phones.  I also compiled openbsc and connected the bts 
application to it.  The problem is that timer T200 expires.  I also get 
TX TCH/F errors before the timer expires on the bts application side.  I 
am not sure if this is because of a configuration error on my part, or 
if the code was never completed enough to link a phone to it.  I have 
tried using the default nanobts configuration file, but it does not 
work.  If it isn't completed yet, what needs to be done?  Is there 
anything that needs to be changed in the default nanobts configuration 
file?  Just so you know,  The reason why my email display name is not 
here, is because I am using backtrack linux and webmail to post this.

Thank you for taking the time to help me,
Calvin E. Balke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110327/83e0b2fa/attachment.htm>

From 246tnt at gmail.com  Mon Mar 28 06:05:24 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Mon, 28 Mar 2011 08:05:24 +0200
Subject: Does the jolly/bts tree work?
In-Reply-To: <3326c2c5.1d69e.12efa2b5450.Webtop.42@charter.net>
References: <3326c2c5.1d69e.12efa2b5450.Webtop.42@charter.net>
Message-ID: <AANLkTi=mEAbHmaLKnJwZYTsPRX3cBFgfSsyuKdZ8xuuW@mail.gmail.com>

> I am not sure if this
> is because of a configuration error on my part, or if the code was never
> completed enough to link a phone to it.? I have tried using the default
> nanobts configuration file, but it does not work.

It's not supposed to work.


> If it isn't completed
> yet, what needs to be done?

L1 ... pretty much all of it, including all the DSP hacks.


    Sylvain



From osmocom-announce-bounces at lists.osmocom.org  Mon Mar 28 09:42:08 2011
From: osmocom-announce-bounces at lists.osmocom.org (osmocom-announce-bounces at lists.osmocom.org)
Date: Mon, 28 Mar 2011 11:42:08 +0200
Subject: Forward of moderated message
Message-ID: <mailman.1.1301305328.569.osmocom-announce@lists.osmocom.org>

An embedded message was scrubbed...
From: "Nahuel" <inthemix84 at gmail.com>
Subject: Hello, I'm new member
Date: Mon, 21 Mar 2011 07:16:15 -0300
Size: 7834
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110328/ab94ac65/attachment.eml>

From khorben at defora.org  Tue Mar 29 10:51:40 2011
From: khorben at defora.org (Pierre Pronchery)
Date: Tue, 29 Mar 2011 12:51:40 +0200
Subject: Funding from CELF to work on Osmocom integration
Message-ID: <4D91B9BC.2010201@defora.org>

			Hi baseband-developers,

I am looking for a freelance developer, preferably (provably)
knowledgeable about the Osmocom project, to work together on a project
potentially funded by CELF; the objective is to use Osmocom through a
telephony GUI to make regular phone calls. I would like to use the
"Phone" project from DeforaOS as the GUI, but feel free to mention if
you are from a different project and want to step in.

Some background information: CELF is otherwise known as the CE Linux
Forum. It's supposed to merge with the Linux foundation eventually:
http://www.linuxfoundation.org/news-media/announcements/2010/10/linux-foundation-and-consumer-electronics-linux-forum-merge

What brings me here is their "CELF Open Project Proposal 2011":
http://elinux.org/CELF_Open_Project_Proposal_2011

? The CELF Open Project Proposal is a process whereby members of the
public can submit to the CE Linux Forum ideas and proposals for projects
that they think should be worked on to enhance embedded Linux ?

FWIW, it was mentioned in the Openmoko Community Updates for February 2011:
http://wiki.openmoko.org/wiki/Community_Updates/2011-02-01#General_News

This is how I got to know about it right before the deadline, and had to
rush to submit my current project idea, which is to integrate Osmocom
with a Linux-based telephony GUI:
http://elinux.org/Add_Osmocore_support_to_the_DeforaOS_Phone_GSM_stack

About Osmocom:
http://bb.osmocom.org/trac/

? OsmocomBB is an Free Software / Open Source GSM Baseband software
implementation ?

The submission was accepted, and I am now required to send a bid for the
project. Needs to be estimated:
- how much time would be needed (and availabilities),
- how much money would be needed,
- which issues can be anticipated.

I will also welcome suggestions as to which hardware to use for this
task. Technically, the proposal is about integrating Osmocom with a
Linux-based smartphone environment, so I'm not speaking about improving
the LCD support for feature phones. Something like the Openmoko
Freerunner is closer to what I have in mind, which is also what
I'm currently using (and as you may know, it has a Calypso-based GSM
baseband, which is supported by Osmocom already).

Before I conclude, let me mention that I want definite answers about
people who will be serious about this. Feel free to forward this message
to anyone else whom you know and should also participate to this project.

My current estimation is that three to four weeks should be sufficient
for two people to:
- expose and glue a more "UI-developer-friendly" API, probably closer
  to the Telnet interface (see layer23/src/mobile/vty_interface.c)
- make sure everything is as reliable as possible (eg baseband
  initialization...)
- likewise, make sure the GUI and Osmocom are integrated correctly
- test, test, test.

HTH,
-- 
khorben



From 246tnt at gmail.com  Tue Mar 29 11:11:03 2011
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Tue, 29 Mar 2011 13:11:03 +0200
Subject: Funding from CELF to work on Osmocom integration
In-Reply-To: <4D91B9BC.2010201@defora.org>
References: <4D91B9BC.2010201@defora.org>
Message-ID: <AANLkTi=zp_tN-T=CqYM6BaFGO7acigrf0VsKmtBfEMN=@mail.gmail.com>

Hi,


Just some quick notes to whoever will apply for the task :

> - expose and glue a more "UI-developer-friendly" API, probably closer
> ?to the Telnet interface (see layer23/src/mobile/vty_interface.c)

I think Andreas has worked on a external MNCC interface, so that's
probably what would be use to drive it externally.

Maybe some other glue (either through the vty, or some other like the
danielif branch of openbsc) for the debug info and things not really
call interface would still be needed (network scan / status / ...)


> - make sure everything is as reliable as possible (eg baseband
> ?initialization...)

There is still a lot that the L1 doesn't do properly (and that it's
hard to do properly without some serious change in the way we do
things), like DRX, DTX, proper/reliable TS change, handovers,
neighbour monitoring (actually in-call pwr monitoring is in progress,
but you'd need sch/bcch probing of neigh in IDLE mode as well).


Cheers,

   Sylvain



From dvsm89 at gmx.com  Tue Mar 29 11:51:27 2011
From: dvsm89 at gmx.com (Dave Schmidt)
Date: Tue, 29 Mar 2011 11:51:27 +0000
Subject: How to build osmocon for the target?
Message-ID: <20110329115127.314270@gmx.com>

Hello everyone!

I'm trying to run osmocombb on Neo Freerunner. Read and hopefully understood
http://bb.osmocom.org/trac/wiki/{CalypsoRomloader,osmocon,OpenMoko}.

One thing I completely miss is how to build osmocon for the target phone to be able to run
./osmocon -i 13 -m romload -p /dev/ttySAC0 layer1.highram.bin
In the source tree, osmocon is built only for the host, and I do not see any configuration options to enable it also for the phone...

Thanks in advance,

D.



From squalyl at gmail.com  Tue Mar 29 12:32:35 2011
From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=)
Date: Tue, 29 Mar 2011 14:32:35 +0200
Subject: How to build osmocon for the target?
In-Reply-To: <20110329115127.314270@gmx.com>
References: <20110329115127.314270@gmx.com>
Message-ID: <AANLkTimAwHDNyvzQjd7bCJ8NdfgG_AGuCxRhgP6zFW9Q@mail.gmail.com>

isn't that ./configure --host=arm-proper-triplet?

you may need to update your $PATH.

that seems too simple, am I missing something?

Sebastien

On Tue, Mar 29, 2011 at 1:51 PM, Dave Schmidt <dvsm89 at gmx.com> wrote:

> Hello everyone!
>
> I'm trying to run osmocombb on Neo Freerunner. Read and hopefully
> understood
> http://bb.osmocom.org/trac/wiki/{CalypsoRomloader,osmocon,OpenMoko}.
>
> One thing I completely miss is how to build osmocon for the target phone to
> be able to run
> ./osmocon -i 13 -m romload -p /dev/ttySAC0 layer1.highram.bin
> In the source tree, osmocon is built only for the host, and I do not see
> any configuration options to enable it also for the phone...
>
> Thanks in advance,
>
> D.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110329/d56acb63/attachment.htm>

From khorben at defora.org  Tue Mar 29 14:05:05 2011
From: khorben at defora.org (Pierre Pronchery)
Date: Tue, 29 Mar 2011 16:05:05 +0200
Subject: How to build osmocon for the target?
In-Reply-To: <20110329115127.314270@gmx.com>
References: <20110329115127.314270@gmx.com>
Message-ID: <4D91E711.5080908@defora.org>

			Hi Dave, list,

On 29/03/2011 13:51, Dave Schmidt wrote:
> 
> I'm trying to run osmocombb on Neo Freerunner. Read and hopefully understood
> http://bb.osmocom.org/trac/wiki/{CalypsoRomloader,osmocon,OpenMoko}.
> 
> One thing I completely miss is how to build osmocon for the target phone to be able to run
> ./osmocon -i 13 -m romload -p /dev/ttySAC0 layer1.highram.bin
> In the source tree, osmocon is built only for the host, and I do not see any configuration options to enable it also for the phone...

The Openmoko Freerunner has two CPUs: one for the main operating system
(the host), and one for the baseband (the target). Here osmocon is
running on the host as usual.

So technically, you either need to:
- compile osmocombb with a native ARM compiler, possibly on the
  Openmoko (can be slow though)
- cross-compile osmocombb for Openmoko, which may require a different
  compiler than the one recommended for the target.

Alternatively, you can use the Debian packages from the hackable:1 project:
http://trac.hackable1.org/
http://build.hackable1.org/debian/dists/wip-squeeze/main/binary-armel/

HTH,
-- 
khorben



From vamposdecampos at gmail.com  Tue Mar 29 19:01:25 2011
From: vamposdecampos at gmail.com (Alex Badea)
Date: Tue, 29 Mar 2011 22:01:25 +0300
Subject: How to build osmocon for the target?
In-Reply-To: <20110329115127.314270@gmx.com>
References: <20110329115127.314270@gmx.com>
Message-ID: <4D922C85.2060705@gmail.com>

Hi,

On 2011-03-29 14:51, Dave Schmidt wrote:
> I'm trying to run osmocombb on Neo Freerunner. Read and hopefully understood
> http://bb.osmocom.org/trac/wiki/{CalypsoRomloader,osmocon,OpenMoko}.
>
> One thing I completely miss is how to build osmocon for the target phone to be able to run
> ./osmocon -i 13 -m romload -p /dev/ttySAC0 layer1.highram.bin
> In the source tree, osmocon is built only for the host, and I do not see any configuration options to enable it also for the phone...

You can cross-compile the osmocon and layer 2/3 binaries on a PC.

You'll need an additional toolchain [1], then to build osmocom-bb:

$ make HOST_CONFARGS="--host=arm-angstrom-linux-gnueabi"


On my machine this ends up using:

$ arm-angstrom-linux-gnueabi-gcc -v
Using built-in specs.
Target: arm-angstrom-linux-gnueabi
Configured with: 
/home/walkingice/moko/build/omdev/work/i686-armv4t-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.1.2-r8/gcc-4.1.2/configure 
--build=i686-linux --host=i686-linux --target=arm-angstrom-linux-gnueabi 
--prefix=/usr/local/openmoko/arm --exec_prefix=/usr/local/openmoko/arm 
--bindir=/usr/local/openmoko/arm/bin 
--sbindir=/usr/local/openmoko/arm/bin 
--libexecdir=/usr/local/openmoko/arm/libexec 
--datadir=/usr/local/openmoko/arm/share 
--sysconfdir=/usr/local/openmoko/arm/etc 
--sharedstatedir=/usr/local/openmoko/arm/share/com 
--localstatedir=/usr/local/openmoko/arm/var 
--libdir=/usr/local/openmoko/arm/lib 
--includedir=/usr/local/openmoko/arm/include 
--oldincludedir=/usr/local/openmoko/arm/include 
--infodir=/usr/local/openmoko/arm/share/info 
--mandir=/usr/local/openmoko/arm/share/man --with-gnu-ld --enable-shared 
--enable-target-optspace --enable-languages=c,c++ --enable-threads=posix 
--enable-multilib --enable-c99 --enable-long-long --enable-symvers=gnu 
--enable-libstdcxx-pch --program-prefix=arm-angstrom-linux-gnueabi- 
--disable-libssp --disable-libmudflap --with-float=soft 
--with-local-prefix=/home/walkingice/moko/build/omdev/staging/arm-angstrom-linux-gnueabi/usr 
--with-gxx-include-dir=/home/walkingice/moko/build/omdev/staging/arm-angstrom-linux-gnueabi//usr/include/c++ 
--with-sysroot=/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi 
--with-build-time-tools=/home/walkingice/moko/build/omdev/cross/arm-angstrom-linux-gnueabi/bin 
--with-build-sysroot=/home/walkingice/moko/build/omdev/staging/arm-angstrom-linux-gnueabi 
--disable-libunwind-exceptions 
--with-mpfr=/home/walkingice/moko/build/omdev/staging/i686-linux/usr 
--enable-__cxa_atexit
Thread model: posix
gcc version 4.1.2



Cheers,
Alex

[1] http://wiki.openmoko.org/wiki/Toolchain



From technosabby at gmail.com  Thu Mar 31 09:20:05 2011
From: technosabby at gmail.com (Marten Christophe)
Date: Thu, 31 Mar 2011 14:50:05 +0530
Subject: Airprob compiling error
Message-ID: <AANLkTinxM=4At7x2MtBJKbP-JwffN5fjaHeghKjWk1F4@mail.gmail.com>

Hello All,

while I'm configuring airprobe/gsm-receiver i'm getting error, plz help me
=====
checking for libosmocore >= 0.1.13... Requested 'libosmocore >=
0.1.13' but version of Osmocom Core Library is UNKNOWN  <<<<<<

=====
configure: error: Library requirements (libosmocore >= 0.1.13) not
met; consider adjusting the PKG_CONFIG_PATH environment variable if
your libraries are in a nonstandard prefix so pkg-config can find
them.   <<<<<<<<
=========
plz help me to tell how i can set PKG_CONFIG_PATH  for libosmocore

Kind Regards,



From meierk at informatik.uni-freiburg.de  Thu Mar 31 10:38:51 2011
From: meierk at informatik.uni-freiburg.de (Konrad Meier)
Date: Thu, 31 Mar 2011 12:38:51 +0200
Subject: Airprob compiling error
In-Reply-To: <AANLkTinxM=4At7x2MtBJKbP-JwffN5fjaHeghKjWk1F4@mail.gmail.com>
References: <AANLkTinxM=4At7x2MtBJKbP-JwffN5fjaHeghKjWk1F4@mail.gmail.com>
Message-ID: <4D9459BB.4090200@informatik.uni-freiburg.de>

Am 31.03.2011 11:20, schrieb Marten Christophe:
> Hello All,
>
> while I'm configuring airprobe/gsm-receiver i'm getting error, plz help me
> =====
> checking for libosmocore>= 0.1.13... Requested 'libosmocore>=
> 0.1.13' but version of Osmocom Core Library is UNKNOWN<<<<<<
>
> =====
> configure: error: Library requirements (libosmocore>= 0.1.13) not
> met; consider adjusting the PKG_CONFIG_PATH environment variable if
> your libraries are in a nonstandard prefix so pkg-config can find
> them.<<<<<<<<
> =========
> plz help me to tell how i can set PKG_CONFIG_PATH  for libosmocore
>
> Kind Regards,
>

Hi Marten,

This is the wrong mailing list. Airprobe mailing list ist here: 
main at lists.airprobe.org

Regarding your question:
Libosmocore is required to be installed on your system.
You can find it here: http://bb.osmocom.org/trac/wiki/libosmocore

Regards Konrad



From holger at freyther.de  Thu Mar 31 10:54:40 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 31 Mar 2011 12:54:40 +0200
Subject: Airprob compiling error
In-Reply-To: <AANLkTinxM=4At7x2MtBJKbP-JwffN5fjaHeghKjWk1F4@mail.gmail.com>
References: <AANLkTinxM=4At7x2MtBJKbP-JwffN5fjaHeghKjWk1F4@mail.gmail.com>
Message-ID: <4D945D70.3050000@freyther.de>

On 03/31/2011 11:20 AM, Marten Christophe wrote:
> Hello All,
> 
> while I'm configuring airprobe/gsm-receiver i'm getting error, plz help me
> =====
> checking for libosmocore >= 0.1.13... Requested 'libosmocore >=
> 0.1.13' but version of Osmocom Core Library is UNKNOWN  <<<<<<

This is a problem with the libosmocore bundled in osmocom-bb (patches welcome)
it does not find the version in the git tag (and we didn't put a static
version file in the source).

Your best option is to git clone the real libosmocore and build it from there.



From roy.techie at gmail.com  Thu Mar 31 10:06:31 2011
From: roy.techie at gmail.com (royfarji india)
Date: Thu, 31 Mar 2011 15:36:31 +0530
Subject: unknown error
Message-ID: <AANLkTikcDM0OQYY=nnnNs9GeLe-0L9k-4oHhS=GjfPqk@mail.gmail.com>

while compiling i am getting the following error: "libosmocore.a" file
in wrong format.

arm-elf-objcopy --gap-fill=0xff -O binary
board/pirelli_dpl10/layer1.highram.elf
board/pirelli_dpl10/layer1.highram.bin
arm-elf-ld -nostartfiles -nostdlib -nodefaultlibs --gc-sections --cref
-T board/compal/ram.lds -Bstatic -Map
board/compal_e88/loader.compalram.map -o
board/compal_e88/loader.compalram.elf --start-group apps/loader/main.o
abb/twl3025.o rf/trf6151.o display/font_r8x8.o
display/font_r8x8_horiz.o display/st7558.o display/td014.o
display/ssd1783.o display/display.o flash/cfi_flash.o
board/common/calypso_uart.o board/common/calypso_pwl.o
board/compal/rffe_dualband.o board/compal/rf_power.o
board/compal_e88/init.o board/compal_e88/loader.compalram.manifest.o
board/compal/start.ram.o board/compal/exceptions_redirected.o
board/compal/handlers.o calypso/libcalypso.a layer1/liblayer1.a
lib/libmini.a comm/libcomm.a
../../shared/libosmocore/build-target/src/.libs/libosmocore.a
--end-group
arm-elf-ld: ../../shared/libosmocore/build-target/src/.libs/libosmocore.a(crc16.o):
Relocations in generic ELF (EM: 3)
../..*/shared/libosmocore/build-target/src/.libs/libosmocore.a: could
not read symbols: File in wrong format*make[1]: ***
[board/compal_e88/loader.compalram.elf] Error 1
make[1]: Leaving directory `/home/roy/osmocom-bb/src/target/firmware'
make: *** [firmware] Error 2
roy at roy:~/osmocom-bb/src$


PLEASE HELP!!!!!!!!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110331/d6ab3d99/attachment.htm>

From holger at freyther.de  Thu Mar 31 10:52:57 2011
From: holger at freyther.de (Holger Hans Peter Freyther)
Date: Thu, 31 Mar 2011 12:52:57 +0200
Subject: unknown error
In-Reply-To: <AANLkTikcDM0OQYY=nnnNs9GeLe-0L9k-4oHhS=GjfPqk@mail.gmail.com>
References: <AANLkTikcDM0OQYY=nnnNs9GeLe-0L9k-4oHhS=GjfPqk@mail.gmail.com>
Message-ID: <4D945D09.6090301@freyther.de>

On 03/31/2011 12:06 PM, royfarji india wrote:
> while compiling i am getting the following error: "libosmocore.a" file in wrong format.
> 
> arm-elf-objcopy --gap-fill=0xff -O binary board/pirelli_dpl10/layer1.highram.elf board/pirelli_dpl10/layer1.highram.bin
> arm-elf-ld -nostartfiles -nostdlib -nodefaultlibs --gc-sections --cref -T board/compal/ram.lds -Bstatic -Map board/compal_e88/loader.compalram.map -o board/compal_e88/loader.compalram.elf --start-group apps/loader/main.o abb/twl3025.o rf/trf6151.o display/font_r8x8.o display/font_r8x8_horiz.o display/st7558.o display/td014.o display/ssd1783.o display/display.o flash/cfi_flash.o board/common/calypso_uart.o board/common/calypso_pwl.o board/compal/rffe_dualband.o board/compal/rf_power.o board/compal_e88/init.o board/compal_e88/loader.compalram.manifest.o board/compal/start.ram.o board/compal/exceptions_redirected.o board/compal/handlers.o calypso/libcalypso.a layer1/liblayer1.a lib/libmini.a comm/libcomm.a ../../shared/libosmocore/build-target/src/.libs/libosmocore.a --end-group
> arm-elf-ld: ../../shared/libosmocore/build-target/src/.libs/libosmocore.a(crc16.o): Relocations in generic ELF (EM: 3)
> ../..*/shared/libosmocore/build-target/src/.libs/libosmocore.a: could not read symbols: File in wrong format
> *make[1]: *** [board/compal_e88/loader.compalram.elf] Error 1
> make[1]: Leaving directory `/home/roy/osmocom-bb/src/target/firmware'
> make: *** [firmware] Error 2


How do you compile? What toolchain are you using? What does file crc16.o say
on the file for thet target?