Re: [PATCH] mtk: fix firmware makefile to work with current osmocom-bb makefile system

2017-12-06 Thread Vadim Yanitskiy
Hi Craig,

> It seems the existing Makefile.mtk isn't compatible with the
> current makefile scheme so nothing would happen when it was called.

Your change is in Gerrit now: https://gerrit.osmocom.org/5217

> There are some compiler warnings that may need fixing or maybe the
> code needs more fundamental change after rotting a bit.

Sure, feel free to send new patches ;)

> Some good news, I played around with the device and the loader and
> found that things work "as they did" if I follow the instructions
> more carefully...

My congratulations! Could you please write a brief (or more detailed,
if you wish) description of the work you're doing, so I could create
a dedicated wiki page? Or is one already there?

With best regards,
Vadim Yanitskiy.


Re: [PATCH] mtk: fix firmware makefile to work with current osmocom-bb makefile system

2017-12-06 Thread Craig Comstock
> My congratulations! Could you please write a brief (or more detailed,
> if you wish) description of the work you're doing, so I could create
> a dedicated wiki page? Or is one already there?

https://osmocom.org/projects/baseband/wiki/SciphoneDreamG2

This wiki page would probably be good. It needs updating for sure since some of 
the git links for u-boot, linux kernel, initramfs image are dead. It seems they 
referred to git.osmocom.org projects which no longer exist. Not sure if those 
could be restored or not.

I would be happy to make very small changes to that page. When I get something 
working on fernvale and others we could probably create a wiki page for mt6260 
mt6261 fernvale and whatever others make sense.

https://osmocom.org/projects/baseband/wiki/MT6235

Thanks,
Craig


Tx support in MS with a virtual SIM

2017-12-06 Thread Ravi Shankar
Hello Community

Can we make usrp to behave like a normal MS with parameters of SIM in "test
sim" feature from telnet. I am not using any real SIM or writer.

As we pass the make command as " make nofirmware"  from osmocombb/src
directory after enabling the " CFLAGS += -DCONFIG_TX_ENABLE " in
osmocom-bb/src/target/firmware, will it still be able to transmit ?


--
Best Regards.

Ravi


Re: TX SUPPORT

2017-12-06 Thread Harald Welte
On Thu, Dec 07, 2017 at 12:41:55AM +0700, Felix Angga wrote:
> Hi,
> 
> I already uncomment the tx support in Makefile file. But when I run on
> phone, it said this firmware was compiled without tx support.
> 
> How to fix this?

did you do "make clean"?  Did you verify that you actually loaded the re-built 
file?

-- 
- Harald Welte    http://laforge.gnumonks.org/

"Privacy in residential applications is a desirable marketing option."
  (ETSI EN 300 175-7 Ch. A6)


Re: TX SUPPORT

2017-12-06 Thread Felix Angga
Resolved, I recloned the git and it work fine (y)
Thanks

On Dec 7, 2017 1:20 AM, "Harald Welte"  wrote:

> On Thu, Dec 07, 2017 at 12:41:55AM +0700, Felix Angga wrote:
> > Hi,
> >
> > I already uncomment the tx support in Makefile file. But when I run on
> > phone, it said this firmware was compiled without tx support.
> >
> > How to fix this?
>
> did you do "make clean"?  Did you verify that you actually loaded the
> re-built file?
>
> --
> - Harald Welte 
> http://laforge.gnumonks.org/
> 
> 
> "Privacy in residential applications is a desirable marketing option."
>   (ETSI EN 300 175-7 Ch.
> A6)
>


TX SUPPORT

2017-12-06 Thread Felix Angga
Hi,

I already uncomment the tx support in Makefile file. But when I run on
phone, it said this firmware was compiled without tx support.

How to fix this?


Re: OsmoDevCon 2018 schedule planning

2017-12-06 Thread Harald Welte
Dear Osmocom Community,

On Mon, Dec 04, 2017 at 01:23:47PM +0100, Harald Welte wrote:
> == When, Who, Where ==
> 
> I propose the following date for OsmoDevCon 2018: 
>   April 20 - April 23rd, 2018
> 
> * Who: Active developers/contributors of Osmocom projects (as usual)
> * Where: IN-Berlin, Berlin (as usual)
> 
> Please let me know ASAP if that proposed date works for everyone who'd
> want to attend.  We can still change it now, but I would want to nail
> down the date pretty soon.
>
despite Holger indicating April would be difficult for him, I would
still suggest to stay with the current proposed date:
* nobody else has raised any concerns
* several people have sent positive feedback
* it's the usual time-frame as in previous years
* IN-Berlin has already reserved that time slot without any conflict

Sorry, Holger, I hope you will still be around as much as possible!

Threfore, I hereby invite everyone interested to attend to register
themselves in the usual fashion at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2018
i.e. by adding your name to the 'Requested' section.

Please also start collecting topics on that same wiki page.

And please do let me know if there is anything we can do to make the
event better.

Regards,
Harald

> == Format ==
> 
> After the experiment of reducing from 4 to 3 days last year (due to
> OsmoCon), we will again go for *four days* in 2018.
> 
> However, we should clearly divide the days in a way that e.g. "GSM/3G"
> topics are on two days, while SDR+Other topics are on the other days, so
> people not interested in some topics can skip one or two days, as
> needed.

Let's collect the suggested topics.  I've added a "Thread" column to
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2018/edit?section=9
so we can see how many days / half-days we need for which thread.

Regards, and looking forward to meeting you [again] in 2018,

-- 
- Harald Welte    http://laforge.gnumonks.org/

"Privacy in residential applications is a desirable marketing option."
  (ETSI EN 300 175-7 Ch. A6)


Re: Classmark Testing

2017-12-06 Thread Vadim Yanitskiy
Hi Max,

This work is a part of "GSM and GPRS Security Using OsmocomBB" thesis
written by Francois Ponsgen and was published a quite time ago.

Moreover, I already have the changes in my local repo, which is
mostly used for research purposes. I can push them, if it's really
required.

BTW: if I remember correctly, this work was done in NTNU ;)

With best regards,
Vadim Yanitskiy.


Re: Classmark Testing

2017-12-06 Thread Max
On 06.12.2017 12:03, Vadim Yanitskiy wrote:
> This work is a part of "GSM and GPRS Security Using OsmocomBB" thesis
> written by Francois Ponsgen and was published a quite time ago.

Mixed up the author, sorry about that.

>
> Moreover, I already have the changes in my local repo, which is
> mostly used for research purposes. I can push them, if it's really
> required.

It's not really required of course - just smth which would be nice to have in
upstream since it's useful to the users.

>
> BTW: if I remember correctly, this work was done in NTNU ;)

I know, read it quite some time ago :)

-- 
Max Suraev  http://www.sysmocom.de/
=== 
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93 
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B 
* Geschaeftsfuehrer / Managing Director: Harald Welte 






Re: [PATCH] mtk: fix firmware makefile to work with current osmocom-bb makefile system

2017-12-06 Thread Craig Comstock
Some good news, I played around with the device and the loader and found that 
things work "as they did" if I follow the instructions more carefully... press 
and hold the button UNTIL LOADING IS FINISHED! ;) It says it there but I didn't 
quite understand I had to hold it down the whole time.

Anyhow... it works and gets to "Running on mt62xx in environment mtkram and 
HW_CODE = 0x6235" So I am back at square one with this small Makefile.mtk 
change and will proceed with experiments on bringing up sciphone and/or 
fernvale and friends.

Thanks
Craig


Re: Classmark Testing

2017-12-06 Thread Vadim Yanitskiy
Hi Sebastian,

> My query is :  my test network is supporting A5/1,2,3. Is it feasible to
> set A5/1 on MS1 (though it supports A5/2 and A5/3 also) and A5/2 for MS2
> (though it supports A5/1 and A5/3 also) for a call in between them using
> "Early Classmark Sending" ???

I think it will work without any problems because the A5/X encryption
is not 'end-to-end' (in our case MS-to-MS), but there are two separate
encrypted sessions between MS1-BTS and MS2-BTS.

With best regards,
Vadim Yanitskiy.


Re: Classmark Testing

2017-12-06 Thread Snehasish Kar
Hello everyone


I have a doubt here from the DSP side, might be a silly one. While transmitting 
the classmark or any message from mobile on SDCCH during a call, does it 
transmit on the frequency we get after converting the ARFCN or is there a 
slight variation ?


BR

Snehasish


From: baseband-devel  on behalf of 
Vadim Yanitskiy 
Sent: Wednesday, December 6, 2017 8:19:55 PM
To: f12.sebast...@gmail.com
Cc: baseband-devel
Subject: Re: Classmark Testing

Hi Sebastian,

> My query is :  my test network is supporting A5/1,2,3. Is it feasible to
> set A5/1 on MS1 (though it supports A5/2 and A5/3 also) and A5/2 for MS2
> (though it supports A5/1 and A5/3 also) for a call in between them using
> "Early Classmark Sending" ???

I think it will work without any problems because the A5/X encryption
is not 'end-to-end' (in our case MS-to-MS), but there are two separate
encrypted sessions between MS1-BTS and MS2-BTS.

With best regards,
Vadim Yanitskiy.