Re: [riot-devel] [GSOC] Introduction

[Francesco Ermini]

The aim of the project is to avoid the use of hardcoded keys inside the
firmware and add more flexibility in keys management.
So we need an API that performs the following tasks:
1. Wait for an input that just says "hey, install a new key"
i.e  the NFC gateway detects an NFC device in his range or an UART device
has been plug.
2. Check the security parameters.
i.e a device identifier, a timeout for reading the payload,the protocol to
use...other parameters and finally the key
3. Create a database of all the informations received and guarantee that
nobody steels them!
In case of 802.15.4, since the encryption is done by the hardware of the
Xbee, the best solution consists of get rid   of the key right
after the key is set into the Xbee.
In case of RPL and CoAP the idea is to store the key in a secure storage or
a volatile area so that a device   tampering could lead
to key deletion
4. Implement the functions that will set the security keys into the desired
protocol/device

 Finally at the end of the project we'll test the encrypted communications
of the nodes

I hope I was clear, best regards Francesco


2015-03-19 10:57 GMT+01:00 Hauke Petersen :

>  HI Francesco,
>
> On 18.03.2015 19:07, Francesco Ermini wrote:
>
>  Thanks for the Xbee driver,I'll wait the PR for testing!
>
>  The security aspect is about including in RIOT the possibility to
> dynamically insert a set of encryption keys at run time through an external
> channel (I have a collegue working on NFC driver on  RIOT). Basically,the
> keys I want to exchange are those concering the 802.15.4 protocol,but we
> can use the same technique for RPL or CoAP.
>
> Sounds very interesting! There is quite some demand for this inside (and
> outside) of our community. Regarding GSOC - do you have already a rough
> idea about an architecture and a high-level project plan on how you would
> like to structure this as a GSOC project? I encourage you to share this
> with us, so we can help you to improve it!
>
> Cheers,
> Hauke
>
>
>
>
>
> 2015-03-16 19:21 GMT+01:00 Hauke Petersen :
>
>>  Hi Francesco,
>>
>> welcome to RIOT first of all.
>>
>> Cool that you are working with the UDOO boards! BLE development with
>> these boards would indeed be a little difficult, as I don't know any
>> shields without fully integrated network stack, that would allow for access
>> to the BLE link layer.
>>
>> Porting the Xbee device to RIOT is unfortunately already almost finished
>> [1] - I am just sitting on the last fixes and will release a PR in the next
>> couple of days...
>>
>> The security aspect however is not yet included. Taking this to a more
>> general approach (valid for not only the xbee device) is however a very hot
>> topic. Here I would indeed see a project for GSOC. Do you have already any
>> further ideas what you would like to do in this direction? It would be
>> nice, if you could roughly sketch our your ideas, so we can discuss them
>> further.
>>
>> Cheers,
>> Hauke
>>
>> [1] https://github.com/haukepetersen/RIOT/tree/add_driver_xbee
>>
>>
>>
>>
>> On 12.03.2015 15:46, Francesco Ermini wrote:
>>
>>
>>  Hi,
>>
>>  my name is Francesco Ermini, and I'm student in electronics  and
>> telecommunication engineering at the University of Florence,Italy.
>>
>>  My current Ms.C. thesis is about IoT secure communications. Our testbed
>> is made by some UDOO Quad boards, with Linux + RiOT as operating systems
>> (the UDOO can host two OSes at once).
>> I checked the GSOC ideas page, and I found the Bluetooth Low Energy
>> driver one. Although interesting, using BTLE wouldn't rally match my
>> current work.
>> However, we also found that the XBee shield is not yet supported in RiOT
>> (open bug / feature request). This would match a bit more my thesis work,
>> and my (evil) tutor would be happier.
>>
>>  My question is: what about implementing the XBee driver (including the
>> dynamic security keys setup) ?
>>
>>  Best regards,
>>
>>  Francesco
>>
>>
>>  ___
>> devel mailing 
>> listdevel@riot-os.orghttp://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>>
>
>
>  --
> Francesco Ermini
> Via Abebe Bikila, 8 50012 (FI)
> cell. 3338710609
> tell. 055642820
>
>
>


-- 
Francesco Ermini
Via Abebe Bikila, 8 50012 (FI)
cell. 3338710609
tell. 055642820
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [GSOC] Introduction

[Hauke Petersen]

HI Francesco,

On 18.03.2015 19:07, Francesco Ermini wrote:

Thanks for the Xbee driver,I'll wait the PR for testing!

The security aspect is about including in RIOT the possibility to 
dynamically insert a set of encryption keys at run time through an 
external channel (I have a collegue working on NFC driver on  RIOT). 
Basically,the keys I want to exchange are those concering the 802.15.4 
protocol,but we can use the same technique for RPL or CoAP.
Sounds very interesting! There is quite some demand for this inside (and 
outside) of our community. Regarding GSOC - do you have already a rough 
idea about an architecture and a high-level project plan on how you 
would like to structure this as a GSOC project? I encourage you to share 
this with us, so we can help you to improve it!


Cheers,
Hauke





2015-03-16 19:21 GMT+01:00 Hauke Petersen >:


Hi Francesco,

welcome to RIOT first of all.

Cool that you are working with the UDOO boards! BLE development
with these boards would indeed be a little difficult, as I don't
know any shields without fully integrated network stack, that
would allow for access to the BLE link layer.

Porting the Xbee device to RIOT is unfortunately already almost
finished [1] - I am just sitting on the last fixes and will
release a PR in the next couple of days...

The security aspect however is not yet included. Taking this to a
more general approach (valid for not only the xbee device) is
however a very hot topic. Here I would indeed see a project for
GSOC. Do you have already any further ideas what you would like to
do in this direction? It would be nice, if you could roughly
sketch our your ideas, so we can discuss them further.

Cheers,
Hauke

[1] https://github.com/haukepetersen/RIOT/tree/add_driver_xbee




On 12.03.2015 15:46, Francesco Ermini wrote:


Hi,

my name is Francesco Ermini, and I'm student in electronics  and
telecommunication engineering at the University of Florence,Italy.

My current Ms.C. thesis is about IoT secure communications. Our
testbed is made by some UDOO Quad boards, with Linux + RiOT as
operating systems (the UDOO can host two OSes at once).
I checked the GSOC ideas page, and I found the Bluetooth Low
Energy driver one. Although interesting, using BTLE wouldn't
rally match my current work.
However, we also found that the XBee shield is not yet supported
in RiOT (open bug / feature request). This would match a bit more
my thesis work, and my (evil) tutor would be happier.

My question is: what about implementing the XBee driver
(including the dynamic security keys setup) ?

Best regards,

Francesco


___
devel mailing list
devel@riot-os.org  
http://lists.riot-os.org/mailman/listinfo/devel





--
Francesco Ermini
Via Abebe Bikila, 8 50012 (FI)
cell. 3338710609
tell. 055642820


___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [GSOC] Introduction

[Francesco Ermini]

Thanks for the Xbee driver,I'll wait the PR for testing!

The security aspect is about including in RIOT the possibility to
dynamically insert a set of encryption keys at run time through an external
channel (I have a collegue working on NFC driver on  RIOT).
Basically,the keys I want to exchange are those concering the 802.15.4
protocol,but we can use the same technique for RPL or CoAP.


2015-03-16 19:21 GMT+01:00 Hauke Petersen :

>  Hi Francesco,
>
> welcome to RIOT first of all.
>
> Cool that you are working with the UDOO boards! BLE development with these
> boards would indeed be a little difficult, as I don't know any shields
> without fully integrated network stack, that would allow for access to the
> BLE link layer.
>
> Porting the Xbee device to RIOT is unfortunately already almost finished
> [1] - I am just sitting on the last fixes and will release a PR in the next
> couple of days...
>
> The security aspect however is not yet included. Taking this to a more
> general approach (valid for not only the xbee device) is however a very hot
> topic. Here I would indeed see a project for GSOC. Do you have already any
> further ideas what you would like to do in this direction? It would be
> nice, if you could roughly sketch our your ideas, so we can discuss them
> further.
>
> Cheers,
> Hauke
>
> [1] https://github.com/haukepetersen/RIOT/tree/add_driver_xbee
>
>
>
>
> On 12.03.2015 15:46, Francesco Ermini wrote:
>
>
>  Hi,
>
>  my name is Francesco Ermini, and I'm student in electronics  and
> telecommunication engineering at the University of Florence,Italy.
>
>  My current Ms.C. thesis is about IoT secure communications. Our testbed
> is made by some UDOO Quad boards, with Linux + RiOT as operating systems
> (the UDOO can host two OSes at once).
> I checked the GSOC ideas page, and I found the Bluetooth Low Energy driver
> one. Although interesting, using BTLE wouldn't rally match my current work.
> However, we also found that the XBee shield is not yet supported in RiOT
> (open bug / feature request). This would match a bit more my thesis work,
> and my (evil) tutor would be happier.
>
>  My question is: what about implementing the XBee driver (including the
> dynamic security keys setup) ?
>
>  Best regards,
>
>  Francesco
>
>
> ___
> devel mailing 
> listdevel@riot-os.orghttp://lists.riot-os.org/mailman/listinfo/devel
>
>
>


-- 
Francesco Ermini
Via Abebe Bikila, 8 50012 (FI)
cell. 3338710609
tell. 055642820
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [GSOC] Introduction

[Hauke Petersen]

Hi Francesco,

welcome to RIOT first of all.

Cool that you are working with the UDOO boards! BLE development with 
these boards would indeed be a little difficult, as I don't know any 
shields without fully integrated network stack, that would allow for 
access to the BLE link layer.


Porting the Xbee device to RIOT is unfortunately already almost finished 
[1] - I am just sitting on the last fixes and will release a PR in the 
next couple of days...


The security aspect however is not yet included. Taking this to a more 
general approach (valid for not only the xbee device) is however a very 
hot topic. Here I would indeed see a project for GSOC. Do you have 
already any further ideas what you would like to do in this direction? 
It would be nice, if you could roughly sketch our your ideas, so we can 
discuss them further.


Cheers,
Hauke

[1] https://github.com/haukepetersen/RIOT/tree/add_driver_xbee



On 12.03.2015 15:46, Francesco Ermini wrote:


Hi,

my name is Francesco Ermini, and I'm student in electronics  and 
telecommunication engineering at the University of Florence,Italy.


My current Ms.C. thesis is about IoT secure communications. Our 
testbed is made by some UDOO Quad boards, with Linux + RiOT as 
operating systems (the UDOO can host two OSes at once).
I checked the GSOC ideas page, and I found the Bluetooth Low Energy 
driver one. Although interesting, using BTLE wouldn't rally match my 
current work.
However, we also found that the XBee shield is not yet supported in 
RiOT (open bug / feature request). This would match a bit more my 
thesis work, and my (evil) tutor would be happier.


My question is: what about implementing the XBee driver (including the 
dynamic security keys setup) ?


Best regards,

Francesco


___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel


___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] [GSOC] Introduction

[Francesco Ermini]

Hi,

my name is Francesco Ermini, and I'm student in electronics  and
telecommunication engineering at the University of Florence,Italy.

My current Ms.C. thesis is about IoT secure communications. Our testbed is
made by some UDOO Quad boards, with Linux + RiOT as operating systems (the
UDOO can host two OSes at once).
I checked the GSOC ideas page, and I found the Bluetooth Low Energy driver
one. Although interesting, using BTLE wouldn't rally match my current work.
However, we also found that the XBee shield is not yet supported in RiOT
(open bug / feature request). This would match a bit more my thesis work,
and my (evil) tutor would be happier.

My question is: what about implementing the XBee driver (including the
dynamic security keys setup) ?

Best regards,

Francesco
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [GSOC] Introduction

[Alexandru Razvan Caciulescu]

Hi Oliver,

It seems i was connecting to different riot-os channel.

Thanks for the heads up!
Alex


2015-03-06 21:08 GMT+02:00 Oliver Hahm :

> Hi Alexandru!
>
> > My question is if on Sunday there is any chance to catch anyone
> > from RIOT on the IRC channel since so far it's been empty ?
>
> Are you sure you were on the right server and channel (#riot-os on
> Freenode)? Usually there are always between 20 and 30 people in the channel
> (while of course not always active).
>
> Cheers,
> Oleg
> ___
> devel mailing list
> devel@riot-os.org
> http://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [GSOC] Introduction

[Oliver Hahm]

Hi Alexandru!

> My question is if on Sunday there is any chance to catch anyone
> from RIOT on the IRC channel since so far it's been empty ? 

Are you sure you were on the right server and channel (#riot-os on Freenode)? 
Usually there are always between 20 and 30 people in the channel (while of 
course not always active).

Cheers,
Oleg
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [GSOC] Introduction

[Alexandru Razvan Caciulescu]

Hi Emmanuel and Hauke,

Yes I read the material and submitted a first patch #2547
Regarding the approach Hauke suggested for the project : tomorrow I will be
participating to a 24 hour Hackathon so I will be "radio-silent" until
Sunday.My question is if on Sunday there is any chance to catch anyone from
RIOT on the IRC channel since so far it's been empty ? I will discuss the
main approach on the mailing list but I think it would be more productive
if I can have a live chat with someone to ask for guidelines every now and
then.

Thank you,
Alexandru

2015-03-06 12:41 GMT+02:00 Emmanuel Baccelli :

> Hi Alexandru,
> I suppose you have also looked at the archive of this mailing list, in
> particular to what regards GSOC application process for RIOT:
> http://lists.riot-os.org/pipermail/devel/2015-March/002113.html
> best,
> Emmanuel
>
> On Fri, Mar 6, 2015 at 9:35 AM, Hauke Petersen <
> hauke.peter...@fu-berlin.de> wrote:
>
>>  Hello Alexandru,
>>
>> welcome to RIOT and thanks for your interest in lwm2m.
>>
>> We do not have the final assignment of mentors to projects yet, as we
>> will assign the mentors once we know which projects are gonna be worked on
>> to archive the best possible fit.
>>
>> For discussing your approach, the best thing would be to do it on this
>> mailing list. This way you profit from help by everyone interested in the
>> community - and this is how we discuss our technical problems and ideas
>> anyhow.
>>
>> To approach the project, I would suggest you do the following:
>> 1. get the lwm2m specifications from the oma website [1]
>> 2. read them and try to understand the rough design (third party sources
>> can help a lot here...)
>> 3. try to sketch out an implementation architecture by naming the main
>> modules and interfaces
>> 4. discuss this architecture here at the mailing list
>>
>> When the rough architecture of the implementation becomes clear, it
>> should be easy to derive some milestones and a project plan from it.
>>
>> Let me know if you have questions and looking forward to discuss the
>> project further with you!
>>
>> Cheers,
>> Hauke
>>
>> [1]
>> http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/oma-lightweightm2m-v1-0
>>
>>
>>
>>
>> On 05.03.2015 23:09, Joakim Gebart wrote:
>>
>> I am also interested in lwm2m support in RIOT, professionally. I have
>> colleagues working on an lwm2m implementation for Contiki which can be
>> useful for testing interoperability. I can help with the review and testing
>> of the gsoc implementation, as well as technical discussions.
>>
>> Best regards, Joakim
>> On Mar 5, 2015 9:04 PM, "Alexandru Razvan Caciulescu" <
>> alex.darrede...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>>  I'm a 3rd year student at Politehnica University of Bucharest ,
>>> Romania.
>>>
>>>  I have former experience with communication protocols and worked on a
>>> few college projects involving DNS Resolver and File Sharing protocols for
>>> Linux among others.Currently I am also attending an Operating Systems
>>> course aimed at teaching low level programming which will undoubtedly be of
>>> great help.I would like to apply for GSOC for the "Implementation of LwM2M"
>>> project.
>>>
>>>  If possible I would like to discuss with the mentor for this project
>>> on how to approach it.
>>>
>>>  Thank you,
>>> Alexandru Razvan Caciulescu
>>>
>>>
>>> ___
>>> devel mailing list
>>> devel@riot-os.org
>>> http://lists.riot-os.org/mailman/listinfo/devel
>>>
>>>
>>
>> ___
>> devel mailing 
>> listdevel@riot-os.orghttp://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>>
>> ___
>> devel mailing list
>> devel@riot-os.org
>> http://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>
> ___
> devel mailing list
> devel@riot-os.org
> http://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [GSOC] Introduction and Getting Started

[Emmanuel Baccelli]

Hi James,
Please also look at the mailing list archive concerning GSOC, in particular
at http://lists.riot-os.org/pipermail/devel/2015-March/002113.html
Best,
Emmanuel

On Fri, Mar 6, 2015 at 9:48 AM, Hauke Petersen 
wrote:

>  Hi James,
>
> welcome to RIOT!
>
> Best flesh out your ideas on this mailing list. This is exactly where we
> discuss this kind of ideas and here you will get the best possible
> feedback.
>
> For BLE hardware I would suggest the Nordic SoC (NRF51822). This cpu is
> already supported by RIOT and it allows you to get started with BLE right
> away, without having to port RIOT to some new hardware first. But before
> you actually look into a specific platform, I would highly recommend to
> design and discuss your overall architecture first!
>
> To get started with the code base, I would recommend to look at the Github
> issues labeled as 'Newbie-Task-Candidate' and see if there is something you
> find interesting. Don't hesitate to ask for more information right in the
> Github issue if something is unclear.
>
> Looking forward to hear more about your concrete plans!
>
> Cheers,
> Hauke
>
>
>
>
> On 04.03.2015 20:09, James Hollister wrote:
>
> Hi, my name is James Hollister and I'm interested in applying for Google
> Summer of Code. I'm currently a student at University of California,
> Riverside with an interest in programming for embedded systems.
>
>  I'd like to work on the Support for Bluetooth Low Energy idea, who
> should I talk to in order to flesh out my ideas for getting this done and
> make sure I'm on the right track? Also, what hardware is recommended for
> this? I currently own a STM32F4 Discovery but I do not have any BLE modules
> for it so I'm thinking I should buy an nrf51822 or similar.
>
>  Finally, do you have an issue that you can recommend that would give me
> the best introduction to the code base?
>
>  Thanks,
> James Hollister (IRC: jhollister)
>
>
> ___
> devel mailing 
> listdevel@riot-os.orghttp://lists.riot-os.org/mailman/listinfo/devel
>
>
>
> ___
> devel mailing list
> devel@riot-os.org
> http://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [GSOC] Introduction

[Emmanuel Baccelli]

Hi Alexandru,
I suppose you have also looked at the archive of this mailing list, in
particular to what regards GSOC application process for RIOT:
http://lists.riot-os.org/pipermail/devel/2015-March/002113.html
best,
Emmanuel

On Fri, Mar 6, 2015 at 9:35 AM, Hauke Petersen 
wrote:

>  Hello Alexandru,
>
> welcome to RIOT and thanks for your interest in lwm2m.
>
> We do not have the final assignment of mentors to projects yet, as we will
> assign the mentors once we know which projects are gonna be worked on to
> archive the best possible fit.
>
> For discussing your approach, the best thing would be to do it on this
> mailing list. This way you profit from help by everyone interested in the
> community - and this is how we discuss our technical problems and ideas
> anyhow.
>
> To approach the project, I would suggest you do the following:
> 1. get the lwm2m specifications from the oma website [1]
> 2. read them and try to understand the rough design (third party sources
> can help a lot here...)
> 3. try to sketch out an implementation architecture by naming the main
> modules and interfaces
> 4. discuss this architecture here at the mailing list
>
> When the rough architecture of the implementation becomes clear, it should
> be easy to derive some milestones and a project plan from it.
>
> Let me know if you have questions and looking forward to discuss the
> project further with you!
>
> Cheers,
> Hauke
>
> [1]
> http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/oma-lightweightm2m-v1-0
>
>
>
>
> On 05.03.2015 23:09, Joakim Gebart wrote:
>
> I am also interested in lwm2m support in RIOT, professionally. I have
> colleagues working on an lwm2m implementation for Contiki which can be
> useful for testing interoperability. I can help with the review and testing
> of the gsoc implementation, as well as technical discussions.
>
> Best regards, Joakim
> On Mar 5, 2015 9:04 PM, "Alexandru Razvan Caciulescu" <
> alex.darrede...@gmail.com> wrote:
>
>> Hello,
>>
>>  I'm a 3rd year student at Politehnica University of Bucharest , Romania.
>>
>>  I have former experience with communication protocols and worked on a
>> few college projects involving DNS Resolver and File Sharing protocols for
>> Linux among others.Currently I am also attending an Operating Systems
>> course aimed at teaching low level programming which will undoubtedly be of
>> great help.I would like to apply for GSOC for the "Implementation of LwM2M"
>> project.
>>
>>  If possible I would like to discuss with the mentor for this project on
>> how to approach it.
>>
>>  Thank you,
>> Alexandru Razvan Caciulescu
>>
>>
>> ___
>> devel mailing list
>> devel@riot-os.org
>> http://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>
> ___
> devel mailing 
> listdevel@riot-os.orghttp://lists.riot-os.org/mailman/listinfo/devel
>
>
>
> ___
> devel mailing list
> devel@riot-os.org
> http://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [GSOC] Introduction and Getting Started

[Hauke Petersen]

Hi James,

welcome to RIOT!

Best flesh out your ideas on this mailing list. This is exactly where we 
discuss this kind of ideas and here you will get the best possible 
feedback.


For BLE hardware I would suggest the Nordic SoC (NRF51822). This cpu is 
already supported by RIOT and it allows you to get started with BLE 
right away, without having to port RIOT to some new hardware first. But 
before you actually look into a specific platform, I would highly 
recommend to design and discuss your overall architecture first!


To get started with the code base, I would recommend to look at the 
Github issues labeled as 'Newbie-Task-Candidate' and see if there is 
something you find interesting. Don't hesitate to ask for more 
information right in the Github issue if something is unclear.


Looking forward to hear more about your concrete plans!

Cheers,
Hauke



On 04.03.2015 20:09, James Hollister wrote:
Hi, my name is James Hollister and I'm interested in applying for 
Google Summer of Code. I'm currently a student at University of 
California, Riverside with an interest in programming for embedded 
systems.


I'd like to work on the Support for Bluetooth Low Energy idea, who 
should I talk to in order to flesh out my ideas for getting this done 
and make sure I'm on the right track? Also, what hardware is 
recommended for this? I currently own a STM32F4 Discovery but I do not 
have any BLE modules for it so I'm thinking I should buy an nrf51822 
or similar.


Finally, do you have an issue that you can recommend that would give 
me the best introduction to the code base?


Thanks,
James Hollister (IRC: jhollister)


___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel


___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [GSOC] Introduction

[Hauke Petersen]

Hello Alexandru,

welcome to RIOT and thanks for your interest in lwm2m.

We do not have the final assignment of mentors to projects yet, as we 
will assign the mentors once we know which projects are gonna be worked 
on to archive the best possible fit.


For discussing your approach, the best thing would be to do it on this 
mailing list. This way you profit from help by everyone interested in 
the community - and this is how we discuss our technical problems and 
ideas anyhow.


To approach the project, I would suggest you do the following:
1. get the lwm2m specifications from the oma website [1]
2. read them and try to understand the rough design (third party sources 
can help a lot here...)
3. try to sketch out an implementation architecture by naming the main 
modules and interfaces

4. discuss this architecture here at the mailing list

When the rough architecture of the implementation becomes clear, it 
should be easy to derive some milestones and a project plan from it.


Let me know if you have questions and looking forward to discuss the 
project further with you!


Cheers,
Hauke

[1] 
http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/oma-lightweightm2m-v1-0




On 05.03.2015 23:09, Joakim Gebart wrote:


I am also interested in lwm2m support in RIOT, professionally. I have 
colleagues working on an lwm2m implementation for Contiki which can be 
useful for testing interoperability. I can help with the review and 
testing of the gsoc implementation, as well as technical discussions.


Best regards, Joakim

On Mar 5, 2015 9:04 PM, "Alexandru Razvan Caciulescu" 
mailto:alex.darrede...@gmail.com>> wrote:


Hello,

I'm a 3rd year student at Politehnica University of Bucharest ,
Romania.

I have former experience with communication protocols and worked
on a few college projects involving DNS Resolver and File Sharing
protocols for Linux among others.Currently I am also attending an
Operating Systems course aimed at teaching low level programming
which will undoubtedly be of great help.I would like to apply for
GSOC for the "Implementation of LwM2M" project.

If possible I would like to discuss with the mentor for this
project on how to approach it.

Thank you,
Alexandru Razvan Caciulescu




___
devel mailing list
devel@riot-os.org 
http://lists.riot-os.org/mailman/listinfo/devel



___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel


___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [GSOC] Introduction

[Joakim Gebart]

I am also interested in lwm2m support in RIOT, professionally. I have
colleagues working on an lwm2m implementation for Contiki which can be
useful for testing interoperability. I can help with the review and testing
of the gsoc implementation, as well as technical discussions.

Best regards, Joakim
On Mar 5, 2015 9:04 PM, "Alexandru Razvan Caciulescu" <
alex.darrede...@gmail.com> wrote:

> Hello,
>
> I'm a 3rd year student at Politehnica University of Bucharest , Romania.
>
> I have former experience with communication protocols and worked on a few
> college projects involving DNS Resolver and File Sharing protocols for
> Linux among others.Currently I am also attending an Operating Systems
> course aimed at teaching low level programming which will undoubtedly be of
> great help.I would like to apply for GSOC for the "Implementation of LwM2M"
> project.
>
> If possible I would like to discuss with the mentor for this project on
> how to approach it.
>
> Thank you,
> Alexandru Razvan Caciulescu
>
>
> ___
> devel mailing list
> devel@riot-os.org
> http://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] [GSOC] Introduction

[Alexandru Razvan Caciulescu]

Hello,

I'm a 3rd year student at Politehnica University of Bucharest , Romania.

I have former experience with communication protocols and worked on a few
college projects involving DNS Resolver and File Sharing protocols for
Linux among others.Currently I am also attending an Operating Systems
course aimed at teaching low level programming which will undoubtedly be of
great help.I would like to apply for GSOC for the "Implementation of LwM2M"
project.

If possible I would like to discuss with the mentor for this project on how
to approach it.

Thank you,
Alexandru Razvan Caciulescu
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [GSOC] Introduction and Getting Started

[Murat CAKMAK]

Hi James,

 

I could not see BLE support in RIOT so I was planning to suggest adding BLE 
too. 

I am planning to use PsoC 4 BLE IC.  Click <http://www.cypress.com/psoc4ble/>  
to see PsoC 4BLE details.

PsoC 4BLE is a SoC which contains ARM Cortex M0 core and Bluetooth low energy 
radio (like as nrf51822). And also it contains BLE stack. 

 

I have already ported RIOT to PsoC 4 BLE basically (Initialization, Timer, UART 
etc. ) in my local but I am waiting the result of my another “Pull Request” for 
PsoC 5LP port.  

Because, PsoC IC portings are using PsoC Creator IDE (instead of RIOT build 
system), so if it will be accepted by RIOT maintainers, I will also create a 
pull request for PsoC 4BLE silicon.

 

Expected result for BLE support in the “Idea List”: Connection with a 
smartphone. 

Same functionality can be easily done by PsoC 4BLE Bluetooth stack in ten 
minutes. There are some examples : http://www.cypress.com/?rID=108148 
<http://www.cypress.com/?rID=108148&cache=0> &cache=0

 

My next step was porting BLE stack to RIOT. 

 

I am planning to work on BLE too so we can work together or individually or 
what other RIOTers suggest :)

 

Thanks. 

Murat. 

 

From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of James Hollister
Sent: Wednesday, March 4, 2015 9:10 PM
To: devel@riot-os.org
Subject: [riot-devel] [GSOC] Introduction and Getting Started

 

Hi, my name is James Hollister and I'm interested in applying for Google Summer 
of Code. I'm currently a student at University of California, Riverside with an 
interest in programming for embedded systems. 

 

I'd like to work on the Support for Bluetooth Low Energy idea, who should I 
talk to in order to flesh out my ideas for getting this done and make sure I'm 
on the right track? Also, what hardware is recommended for this? I currently 
own a STM32F4 Discovery but I do not have any BLE modules for it so I'm 
thinking I should buy an nrf51822 or similar.

 

Finally, do you have an issue that you can recommend that would give me the 
best introduction to the code base?

 

Thanks,

James Hollister (IRC: jhollister)

___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] [GSOC] Introduction and Getting Started

[James Hollister]

Hi, my name is James Hollister and I'm interested in applying for Google
Summer of Code. I'm currently a student at University of California,
Riverside with an interest in programming for embedded systems.

I'd like to work on the Support for Bluetooth Low Energy idea, who should I
talk to in order to flesh out my ideas for getting this done and make sure
I'm on the right track? Also, what hardware is recommended for this? I
currently own a STM32F4 Discovery but I do not have any BLE modules for it
so I'm thinking I should buy an nrf51822 or similar.

Finally, do you have an issue that you can recommend that would give me the
best introduction to the code base?

Thanks,
James Hollister (IRC: jhollister)
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel