[riot-devel] Contribute to RIOT OS

[Parthiv Parikh]

Sir,

 This is Parthiv Parikh from Dwarkadas J Sanghvi College of Engineering,
India.

I'm interested in contributing for RIOT OS. How should I proceed?
I have seen RIOT OS's projects in Google Summer of Code 2015, and I found
some of them to be really interesting. (BLE project). I am personally
interested in contributing towards embedded projects.
I was wondering if there similar projects in Google Summer of Code 2016
which I could contribute to.

Thank you.
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Event Driven Button

[Sugang Li]

Dear all,

I notice that button function has been added to the latest version of RIOT.
  Basically, it gives 0 on pressing and 1 on releasing. Is there an event
driven implementation for this button such onClick() or onPress()?

Thanks,

Sugang

-- 

*WINLAB, Department of Electrical and Computer Engineering*

*Rutgers,the State University of New Jersey*
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Event Driven Button

[Hauke Petersen]

Hi,

I am not quite sure which button function you are referring to. If you 
mean the buttons mapped via SAUL, then there is no event drive API, yet. 
Though this is being worked on and will hopefully be introduced to RIOT 
soon...


Cheers,
Hauke


On 05.02.2016 17:37, Sugang Li wrote:

Dear all,

I notice that button function has been added to the latest version of 
RIOT.   Basically, it gives 0 on pressing and 1 on releasing. Is there 
an event driven implementation for this button such onClick() or 
onPress()?


Thanks,

Sugang

--

*/WINLAB, Department of Electrical and Computer Engineering/*
*/Rutgers,the State University of New Jersey
/*


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


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

Re: [riot-devel] Ethos_BR

[Kaspar Schleiser]

Hey Ilias,

it is best to ask these questions on devel@riot-os.org...

On 02/03/2016 12:28 PM, Ilias Seitanidis wrote:
> I am currently working on RIOT with Atmel R21 boards. I want to 
> ask you which branch should I use for my BR and if its possible 
> some tips for the configuration.I tried the ethos_br branch [1],
> I configured based on [2].After that I was able to ping only the
> interface 6,serial and not the interface 5,wireless. In the fibroute I
> added  default route pointing affe::1(my computers interface) and still
> nothing.In my Computers routing table there are records for both affe::
> and abcd:: .

Please my current "implified border router" branch [1].

Compile, flash, then start "start_network.sh" as follows:
sudo sh start_network.st /dev/ttyXXX tap0 affe::/64

Make sure your Linux node has any non-link-local address configured on
any interface. If in doubt, add e.g., beef::1 to "lo".

Then, once running, at the ethos shell, configure affe::/64 on the
router's 6lowpan interface. Make sure to use the node's eui64 as last
64bit of its address.

E.g., my node has "fe80::5855:4443:9918:b576" on interface 5, so I
configure the prefix as "ifconfig 5 add affe::5855:4443:9918:b576".

RIOT still won't aswer pings to "affe::5855:4443:9918:b576" unless they
come from interface 5, but now other RIOT nodes should be pingable.

Kaspar
https://github.com/RIOT-OS/RIOT/pull/4725


[1] https://github.com/RIOT-OS/RIOT/pull/4725
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT-Os support for ESP8266

[Drasko DRASKOVIC]

Hi,

> On 5 Feb 2016 14:28, "David Lyon"  wrote:
>> My understanding is that there is a C SDK for the ESP8266 and you could
easily* port RIOT onto the ESP8266.

Espressif backs-up ESP8266 with their SDK bare-metal, as well as SDK based
on FreeRTOS. Both have shady licensing of several components.

I suggest you to take a look at community SDK based on GCC maintained by
pfalcon, which does effort to replace proprietary components with open ones.

A step forward is an modification of pfalcons SDK with adds FreeRTOS
support, called and adds ports for some useful some blocks, like mbedTLS. I
think that this can be good starting point.

I do not have links because I am writing from my phone, but they will be
easy to find...

BR,
Drasko
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Event Driven Button

[Sugang Li]

Thanks Hauke!  That explanation helps.

On Fri, Feb 5, 2016 at 12:36 PM, Hauke Petersen  wrote:

> Hi,
>
> I am not quite sure which button function you are referring to. If you
> mean the buttons mapped via SAUL, then there is no event drive API, yet.
> Though this is being worked on and will hopefully be introduced to RIOT
> soon...
>
> Cheers,
> Hauke
>
>
>
> On 05.02.2016 17:37, Sugang Li wrote:
>
> Dear all,
>
> I notice that button function has been added to the latest version of
> RIOT.   Basically, it gives 0 on pressing and 1 on releasing. Is there an
> event driven implementation for this button such onClick() or onPress()?
>
> Thanks,
>
> Sugang
>
> --
>
> *WINLAB, Department of Electrical and Computer Engineering*
>
> *Rutgers,the State University of New Jersey *
>
>
> ___
> devel mailing 
> listdevel@riot-os.orghttps://lists.riot-os.org/mailman/listinfo/devel
>
>
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>


-- 

*WINLAB, Department of Electrical and Computer Engineering*

*Rutgers,the State University of New Jersey*
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Tunslip6 in BR

[Ilias Seitanidis]

Dear all,

I followed the [1]{a} . But I get the following error:

tunslip6: serial_to_tun: write: Invalid argument
ifconfig tu323 down
netstat -nr | awk '{ if ($2 == "tu323") print "route delete -net "$1; }' |
sh


then after a small search I found this on Contiki page(Given that is ported
by Contiki):
tunslip6 -L -B 115200 -v5 -s /dev/ttyACM0 ::1/64
{b}
but still :

tunslip6: serial_to_tun: write: Invalid argument
0033.032 ifconfig tun0 down
0033.044 netstat -nr | awk '{ if ($2 == "tun0") print "route delete -net
"$1; }' | sh


The only difference was that in {b} I received that error after a few
seconds and not immediately as in {a}.


Thank you in advance!!!


[1] https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_border_router
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Tunslip6 in BR

[Ilias Seitanidis]

Hello Cenk,
Thank you for your reply!
I use Ubuntu 14.04 .
When I use the [1] it stops immediately so there is no fun interface when I
type ifconfig.On the other hand when I type :

tunslip6 -L -B 115200 -v5 -s /dev/ttyACM0 ::1/64, the interface exists
when I type ifconfig. With the second one I can also see some activity ,
write slip/write tun0, but after a few seconds it stops working , interface
down.
Thank you!
Best,
Ilias


On Feb 5, 2016 1:07 PM, "Cenk Gündogan"  wrote:

> Hello Ilias,
>
> * What kind of operating system do you use?
> * Can you verify after calling the tunslip6 tool that the tun interface
> was created successfully?
>You can verify by typing `ifconfig` or `ip a`.
>
> Best,
> Cenk
>
> On 05.02.2016 10:59, Ilias Seitanidis wrote:
>
>
> Dear all,
>
> I followed the [1]{a} . But I get the following error:
>
> tunslip6: serial_to_tun: write: Invalid argument
> ifconfig tu323 down
> netstat -nr | awk '{ if ($2 == "tu323") print "route delete -net "$1; }' |
> sh
>
>
> then after a small search I found this on Contiki page(Given that is
> ported by Contiki):
> tunslip6 -L -B 115200 -v5 -s /dev/ttyACM0 ::1/64
> {b}
> but still :
>
> tunslip6: serial_to_tun: write: Invalid argument
> 0033.032 ifconfig tun0 down
> 0033.044 netstat -nr | awk '{ if ($2 == "tun0") print "route delete -net
> "$1; }' | sh
>
>
> The only difference was that in {b} I received that error after a few
> seconds and not immediately as in {a}.
>
>
> Thank you in advance!!!
>
>
> [1]
> https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_border_router
>
>
>
> ___
> devel mailing 
> listdevel@riot-os.orghttps://lists.riot-os.org/mailman/listinfo/devel
>
>
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT-Os support for ESP8266

[David Lyon]

 

Hi Martine, 

My understanding is that there is a C SDK for the ESP8266 and you could
easily* port RIOT onto the ESP8266. 

You might be layering ontop of what's there already just like what's
being done on Linux but it would be satisfactory I think for a lot of
people. 

Just my 2c 

David 

On 2016-02-05 23:35, Martine Lenders wrote: 

> Hi,
> I'm sorry, but I'm really no expert regarding porting of boards. It is 
> propably best to refer to the (hopefully not so outdated) porting guide [1], 
> but I'm forwarding your message to the devel mailinglist, so people that have 
> a better idea of it can read it. Regarding posting to a RIOT mailing list: 
> just write an E-Mail to devel@riot-os.org as I did with this mail and it will 
> be posted to the mailing list. For subscribing go to [2] and enter the 
> necessary information in the "Subscribe" section.
> 
> Hope I could help,
> Martine
> 
> [1] https://github.com/RIOT-OS/RIOT/wiki/Porting-Guide [2]
> [2] https://lists.riot-os.org/mailman/listinfo/devel [1]
> 
> Am 05.02.2016 11:53 schrieb "Michael Kasperovich" : >
>> Hello Martine,
>> 
>> I would really appreciate if you outline necessary steps for support ESP8266 
>> board.
>> How much time it can take?
>> By the way, what should I do to post to riot-os mailing lists?
>> 
>> Thank you,
>> Mike 
> 
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel [1]

 

Links:
--
[1] https://lists.riot-os.org/mailman/listinfo/devel
[2] https://github.com/RIOT-OS/RIOT/wiki/Porting-Guide
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel