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.
Hi,
I have a git clone from 23.01.2012 and a current git clone.
When I compile both and use the mobile appliation, I have a strange
problem in the current code. Very often I can't send USSD codes (and maybe
also can't communicate in other ways; USSD is the costless way to check
whether I am connected or not).
Ok, this is what I do: I send "service 1 *#21#", wait the answer and the
string "% On Network, normal service: Germany, O2". Then send it again and
so on.
With the old code, I reliable get the answer e.g. "% Status: deactivated".
With the new code, I very often (sometime already when trying first time)
get nothing back and after some seconds only "% Service connection
terminated.".
Can someone confirm this behavior?
Thanks
Tim
Hi!
Recently we've had the idea of using OsmocomBB with a simple firmware
that synchronizes to an existing GSM networks FCCH and use the resulting
13MHz clock to drive the USRP for airprobe or OpenBTS.
Ideally, we would even use the Calypso-internal PLL (for ARM or DSP) to
multiply it up to the required 52 MHz. However, neither the Openmoko
nor the Compal/Motorola phones expose any of the 3 clock output pads :(
So the only choice is to use something along the lines of the
http://focus.ti.com/docs/prod/folders/print/cdcvf25084.html
as a quad clock multiplier and attach it to the CLK13OUT signal of the
phone.
The chip is available for 9 USD in single quantities at digikey, and
possibly cheaper at other sources. Combined with a sub-20EUR phone it
might be a very cheap but still accurate frequency source for OpenBTS -
at least as long as there are any commercial gsm networks available.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi,
Nuttx is BSD licensed while osmocom-bb's src/target/firmware is GPLv2(or
later).
Mixing GPlv2 and BSD code is legally possible.
As I understand it the whole work becomes GPLv2 when the code is mixed,
the BSD part however can be used independently of the GPL part if you strip
out the GPL part and the BSD copyright headers have to remain intact.
The problem is that upstream(nuttx) will unlikely accept GPL code as-is for
inclusion in nuttx.
However there is a misc directory for software made under different licenses
such as applications or drivers(there is one GPL driver for the rtl8187x wifi
chipsets).
To use the driver the user is expected to run a script that install the driver
in nuttx normal source code directory.
The list of files touched by the patches mades on top of nuttx and their
licenses is listed here:
http://bb.osmocom.org/trac/wiki/nuttx-bb/code-audit
Basically the GPL parts are composed by :
* the irq
* the timer
* the clock
* the uart
some of the related files have the following authors(can be combined
together):
* Harald Welte
* Stefan Richter
* Ingo Albrecht
I guess Stefan Richter and Ingo Albrecht will be hard to reach.
So I wonder what's the best thing to do.
Denis.
hi,
i improved the generation of neighbour cells of openbsc. the patch is
committed at origin/jolly/rtpmux.
it generated the system information messages of neighbour cells in the
same and in other bands. depending on the location of the bcch and the
neighbour cells, the messages SI 2/5 and optionally SI 2bis/5bis and SI
2ter/5ter are generated.
i have tested it with several configurations. i would like to commit it
to master. any suggestions?
regards,
andreas
Hi,
Alan Carvalho de Assis and me have been working on making nuttx-bb
work on our phones( I've a gta02 and he has a Motorola W220) and
here are the patches(against nuttx-bb).
To try it, clone nuttx-bb and osmocom-bb, put it in the same
directory and keep the name of the osmocom-bb directory.
Then put the gnuarm(for 64bit) or the codesourcery(for 32bit)
in your path(there is a problem with gnuarm for 32bit).
Compile osmocom-bb as usual(cd osmocom-bb/src && make).
Then go in nuttx-bb directory and do:
cd nuttx/tools/
./configure.sh compal_e88/nsh #for for compal_e88( gta02 and Motorola W220).
./configure.sh compal_e99/nsh #we need testers for compal_e99, we don't have one.
cd ../
make
That will create a nuttx.bin, load it as usual(like any other firmware for
your calypso).
Then the following will appear:
Finished, sent 63 blocks in total
Received block ack from phone
Sending checksum: 0x66
Checksum on phone side matches, let's branch to your code
Branching to 0x00820000
Received branch ack, your code is running now!
NuttShell (NSH)
To send commands to the shell you need to run loadwriter.py
that is included in the source code at:
nuttx/drivers/sercomm/loadwriter.py
The list of commands can be found by typing help.
Denis.
Hello,
I need to set originating address in MO SMS (SM submit, SM-RP-OA field)... I found this field in src/host/layer23/src/mobile/gsm411_sms.c -->
/* no orig Address */
data = (uint8_t *)msgb_put(msg, 1);
data[0] = 0x00; /* originator length == 0 */
Field has 0 length. Can anybody pleas help me how to set this field to some MSISDN...I know that there must be some fields for TON,NPI, number ... but I don't know how to write these fields into source code...
With this change i want to find out how MSC behave when is field SM-RP-OA set to some real MSISDN.
Thank you!
Andrew
Hello,
I need to set originating address in MO SMS (SM-RP-OA)... I found this field in src/host/layer23/src/mobile/gsm411_sms.c -->
/* no orig Address */
data = (uint8_t *)msgb_put(msg, 1);
data[0] = 0x00; /* originator length == 0 */
Field has 0 length. Can anybody pleas help me how to set this field to some MSISDN...I know that there must be some fields for TON,NPI, number ... but I don't know how to write these fields into source code...
With this change i want to find out how MSC behave when is field SM-RP-OA set to some real MSISDN.
Thank you!
Andrew
hi,
Me and Alan Carvalho de Assis tried nuttx-bb on the calypso and we failed to
get any serial or sercomm output.
The setup:
------------
1) clone the following repository(or add as remote and checkout the correct
branch):
git://git.osmocom.org/osmocom-bbgit://gitorious.org/gnutoo-s-for-upstream-osmocom-bb-and-nuttx-bb/nuttx-bb-
gta02.git
osmocom-bb and nuttx-bb-gta02 must be in the same directory.
nuttx-bb-gta02 has 2 small patches made by me.
One is for fixing compilation.
And the other one is the result of a diff between compal_e99's init.c and the
gta02's init.c
2) setup the toolchain:
we didn't use gnuarm toolchain because it gave that when compiling nuttx-bb:
arm-elf-ld: ERROR: /home/gnutoo/temp/osmo/nuttx-bb-gta02/nuttx/../../osmocom-
bb/src/target/firmware/comm/libcomm.a(sercomm.o) uses hardware FP, whereas
/home/gnutoo/temp/osmo/nuttx-bb-gta02/nuttx/nuttx uses software FP
So we tried the arm-2010.09 codesourcey
we put it in the path.
3) compile osmocom-bb:
cd osmocom-bb/src
make clean
make
cd ../../
3) compile nuttx-bb:
cd nuttx-bb-gta02/nuttx
cd tools
./configure.sh compal_e99/nsh
cd ../
make CROSSDEV="arm-none-eabi-" clean
make CROSSDEV="arm-none-eabi-"
that gives a file named nuttx.bin
Then I tried it to load on my om-gta02:
scp nuttx.bin root(a)192.168.7.2:
ssh root(a)192.168.7.2
root@om-gta02:~# /etc/init.d/dbus-1 stop
Stopping system message bus: root@om-gta02:~# /etc/init.d/xserver-nodm stop
Stopping XServer
root@om-gta02:~# osmocon -i 13 -m romload -p /dev/ttySAC0 nuttx.bin
and on another console:
ssh root(a)192.168.7.2
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/gta02-pm-gsm.0/download
root@om-gta02:~# echo 0 >/sys/bus/platform/devices/gta02-pm-gsm.0/power_on
root@om-gta02:~# echo 1 >/sys/bus/platform/devices/gta02-pm-gsm.0/power_on
which results in the following on the first console:
[...]
Finished, sent 63 blocks in total
Received block ack from phone
Sending checksum: 0xf6
Checksum on phone side matches, let's branch to your code
Branching to 0x00820000
Received branch ack, your code is running now!
but nothing on sercomm.
And nothing on IRDA serial port either....
and IRDA serial cable works too:
if I do that again:
root@om-gta02:~# echo 0 >/sys/bus/platform/devices/gta02-pm-gsm.0/power_on
root@om-gta02:~# echo 1 >/sys/bus/platform/devices/gta02-pm-gsm.0/power_on
I get the default modem software messages on the serial port...
Previously I tried to print on the IRDA serial port with:
cons_puts("HELLO WORLD\n\n");
in apps/examples/hello/main.c and of course enabling the hello world
application in the apps config.
Nothing was printed either....
here's the app config:
CONFIGURED_APPS += examples/hello
in apps/.config
And here's the diff for the application:
diff --git a/apps/examples/hello/main.c b/apps/examples/hello/main.c
index 308603f..db55ac3 100644
--- a/apps/examples/hello/main.c
+++ b/apps/examples/hello/main.c
@@ -58,7 +58,10 @@
int user_start(int argc, char *argv[])
{
- printf("Hello, World!!\n");
- return 0;
+ while (1){
+ cons_puts("HELLO WORLD\n");
+ printf("Hello, World!!\n");
+ }
+ return 0;
}
Alan Carvalho de Assis tried on features phones and not on the gta02 with the
same result...
Denis.