Hi,
I had some spare time the last days and put together a first attempt
at a framebuffer for the OSMOCOM mobiles.
It currently supports the C123 and the C155, the only two
phones I own.
> On Sat, 10 Apr 2010 10:26:05 +0300, Harald Welte
> >1) we need a way to select between individual fonts
...
> > Something like display_select_font(FONT_5x8) to be called
> > before a display_puts() sounds like a reasonable API for this.
the current API looks like this:
fb_clear();
fb_setfg(FB_COLOR_GREEN);
fb_setbg(FB_COLOR_WHITE);
fb_setfont(FB_FONT_HELVB14);
fb_gotoxy(2,20);
fb_putstr("Hello World!",framebuffer->width-4);
fb_setfg(FB_COLOR_RED);
fb_setbg(FB_COLOR_BLUE);
fb_gotoxy(2,25);
fb_boxto(framebuffer->width-3,38);
fb_setfg(FB_COLOR_WHITE);
fb_setfont(FB_FONT_5X8);
fb_gotoxy(8,33);
fb_putstr("osmocom-bb",framebuffer->width-4);
fb_flush();
Which results in an output such as:
http://vogel.cx/git/20101011_hello_world_c123.jpghttp://vogel.cx/git/20101011_hello_world_c155.jpg
> - If we want to support arbitrary sized fonts, we either should buffer
> the display in RAM (might be wasteful on high res color displays?)
...
This patch keeps a image of the LCD in a RAM and only copies
"dirty" parts upon changes.
> >2) Removing all the special characters might not be the best idea to do.
> > If at all, it should be a compile time option whether or not to drop
> > the special characters.
> > Also, the check for replacing a character with '?' needs to be
> > a font-specific and not a global decision.
This patch currently encodes only #32..#127 to conserve space, but
it supports leaving out arbitrary characters. When the data is actually
put into ROM we can spare additional space on more glyphs and/or fonts.
I currently don't have commit access to the git-repo, so I couldn't
upload my vogelchr/framebuffer branch. Please have a look at the patch
you can download from http://vogel.cx/git/20101011_framebuffer.diff
It removes the old display code completely and replaces it with
the framebuffer, but currently only "hello world" makes use of it
by creating the image in the photographs linked above.
It should apply cleanly to today's master (11.Oct.2010) as it doesn't
touch anything where currently work is being done.
Please send me your comments on that patch.
Greetings from the Dillberg,
Chris
Hello Mihai,
On Thu, 7 Oct 2010 05:25:27 -0700 (PDT), "eisencah eisenach" <wbg_1000(a)yahoo.com> wrote:
>
> PS. The thing is I've done windows programming up until now, but maybe I
> should adapt instead of trying to the sw :)
I am mainly doing Windows software development, but I don't see any
benefits from spending lots of time to adopt C language specific things
in the source code so that it compiles with the MS compiler (be it either
gcc specific language features or missing language features in the MS
compiler).
So I use Cygwin which also emulates at least those Unix specific features
used in OpenBSC/OsmocomBB/Airprobe. And the C standard libraries are not
that different that you won't understand what is going on.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello Marten,
just some basic technical note about what you are planning to do.
The following _could_ work (to be sure if this is really usable
in the planed environment much more research has to be investigated):
- The BTS is based on a modified version of OpenBTS which allows to
send a TCH without the need for signalling to setup the TCH. Similar
everything on the uplink TCH will be played back.
- The phones are based on OsmocomBB and receive the TCH from the BTS
and play it back, they do not send anything on the TCH yet.
- If you make sure that only one phone at once will send, it would
be possible to press a button on the phone which will start
transmitting on the TCH and then talk, similar to simple CB Radio
handsets. On the BTS side you will hear the result.
However all the adjustments to OpenBTS and OsmocomBB, even for a simple
"Proof of concecpt" are not trivial. So you have to understand OpenBTS
and OsmocomBB to make the required changes, you cannot expect that
a short answere here on the list is the solution for the problem.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
On Thu, 7 Oct 2010 02:22:52 -0700 (PDT), "eisencah eisenach" <wbg_1000(a)yahoo.com> wrote:
>
> I would like to compile the hole thing for windows (change in the osmocore
> lib the suport functions - use maybe pipes instead of sockets).
What is the whole thing ? The phone firmware has to be compiled by an
ARM compiler, and if you use GNU ARM, you need Cygwin anyway.
If you want to use a different compiler for the host software, you most
certainly have to adjust quite a lot of the source code, expecially
when using the Microsoft C compiler.
And why use pipes instead of sockets, Windows has sockets.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello everybody.
I've done my reading on GSM these last months and have a general ideea how it works.
I would like to try to run osmocom on Windows (hope don't get stoned for this :) )
I've been going throgh the files and see how interprocess communication is done (between osmocom and osmoload for example).
Do you have any recommendation about what to use on windows as the interface between the 2 programs? Has anyone else tried it?
Cheers,
Mihai.
>
> Hello All,
>
> How can i download the source code for sylvain/testing branch .
> to my PC ?
>
> I just downloaded git://git.osmocom.org/osmocom-bb.git,
> but it is not reflecting / having the file addition and modification or
> the changes sylvain/testing branch commited one hour before.
>
> is there any new trunck for this. or other command then git clone git://
> git.osmocom.org/osmocom-bb.git,
>
> Kind Regards,
>
>
>
Hello Sylvain,
On Mon, 4 Oct 2010 22:13:13 +0200, "Sylvain Munaut" <246tnt(a)gmail.com> wrote:
>
> And Dieter's code probably worked on some internal version of the code
> that were never even commited on the public tree and he may not even
> have any more ...
Yes, exactly, this code was never commited. Its main purpose was to
get the TCH up and running.
BTW, I still do not fully understand what Marten wants to do:
- send a TCH ? If yes, with which device, a BTS or a GSM testset
like I did with the HP8922 ? If it is the HP8922, this sending of
audio data over one the external connectors of the testset also works
with a full MOC or MTC, so no need to hack anything. Just use Sylvain's
TCH testing branch and perform a MOC or MTC. This of course works with
any GSM phone, so no need to use OsmocomBB at all...
- something else I have not understand yet which requires just TCH
receiving and no signalling ? Or recieve the same TCH on multiple
phones ?
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello Nordin,
On Mon, 04 Oct 2010 09:43:36 +0200, "Nordin" <bouchtaoui(a)gmail.com> wrote:
> Maybe he needs just a simple example how you guys do that. That might
> help him to see some logic in the code and can pick it up quickly. Also,
> you never know what experience he has, maybe with some help he can help
> you back more. But than again, it's all up to your free time, which is
> always too short.
The code I used when I started to implement the TCH in Layer-1 will
no longer work with the current version of OsmocomBB so it is of
no help. This means I have to rewrite it and test it to be sure
that it works as expected which will take some time, time as you
already mentioned, is my free time and this free time is valuable.
I have the impression that in this case a quite detailed explanation
including a working example is necessary and some hints won't help
but only result in more questions. Although it might sound harsh,
but knowledge in GSM and being able to read/understand/modify foreign
source code is necessary, noone can expect this to learn here by
asking the list.
If one takes OsmocomBB as it is and registers to a cell and
makes a call, the logging output should give a lot of hints
what calls to L1CTL have to be done.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello Marten,
First of all please be aware that OsmocomBB is now in a state where it
can be used for voice calls without any special tricks so there is no
need to tune on the voice traffic of the HP8922 GSM testset, you can use
the GSM testset as a normal basestation.
On Wed, 29 Sep 2010 23:00:44 +0000, "Marten Christophe" <technosabby(a)gmail.com> wrote:
>
> Q.1) i learned from wiki how to change ARFCN from Layer on application by
> using below command, but how to tune right TS ?
>
> ./layer23 -a 871 -i 127.0.0.1
For my inital TCH testing I did not use Layer23 at all, I only used Layer1
in the phone with special test code using a fixed ARFCN.
> Q.2) even If OsmocomBB Layer1 CTL is able to tune to right ARFCN and Time
> Slot, will i be able to listen what so ever broadcasting from HP8922 from
> C123 speaker or PC speaker. non-encrypted, debugging non-hopping)
Yes.
> Q.3) what command and interface will be used to enter the frequency hoping
> parameter, in case i will use FH option? to tune OsmocomBB l1CTL
You have to write your one code if you want to do this without Signalling
beeing involved.
> Q.4) How to enter Minimalistic L1 interface, what is interface available to
> insert theses command to layer1
You can use the L1CTL API to setup a TCH with your own code, but its
probably easier to setup the TCH with signalling (either MOC or MTC),
this way you don't need to modify the code and still get the TCH running.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
