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
Hi Joël,
ad NFC:
I got me some NXP pn532 modules some time ago as I heard there is work
on specifying 6LoWPAN over ISO 14443 (which NFC is part of). Beside this
there are a lot of interesting applications you could build in combination
with constraint networks.
Sadly, I didn’t come too far with
Hello,
I'm also interesting in AT86RF212B driver.
Ashkay has already done some improvements with this driver.
Does anybody have a WIP branch to try this driver?
Cheers,
2015-03-18 22:14 GMT+01:00 Joakim Gebart joakim.geb...@eistec.se:
Hello,
On Wed, Mar 18, 2015 at 10:08 PM, Craig Younkins
Hi,
On 19 Mar 2015, at 10:54, Oleg Hahm oliver.h...@inria.fr wrote:
Sadly, I didn’t come too far with the driver, as it includes a (more) complex
communication with the module, at least for the pn532, and it was kind of a
private side project. My initial work can be found in [1].
Link
Hi Otmane,
welcome to the RIOT community! Please go a bit through the wiki pages
and checkout the open issues list [1]. There you can find some issues
labeled Newbie-Task-Candidate. Would be nice if you work on one (or
more) issues and make a PR for your fixes. This is a good point to start
Yes I tried to compile the rpl_udp example for the samr21-xpro but it
did not have enough RAM. Even with RPL in non-storing mode and a very
small routing table it would not fit.
Ultimately we would be looking to run UDP/RPL/COAP on top of the
IPv6/6lowpan/802.15.4 stack.
For the evaluation
My colleague Nidhya should be posting on this. Expect EoD India time.
Akshay
On Thursday, 19 March 2015, Baptiste Clenet bapcle...@gmail.com wrote:
Hello,
I'm also interesting in AT86RF212B driver.
Ashkay has already done some improvements with this driver.
Does anybody have a WIP branch
Hello Vivien Co.,
and welcome to RIOT! Let my try to bring some light into the dark :-) .
You'll find my comments inline. The general idea of the periph_conf.h
is a RIOT specific hardware/pin abstraction. Is it correct assuming you
have a stm32 nucleo-l1 board?
Am 17.03.2015 um 14:50
Hi Rioters,
This question is not particularly about Riot but it makes sense to ask you
since future Riot device might use one of this high level protocol
(Iotivity, AllJoyn, Thread, Ipso Alliance).
What do you think about them? In your opinion, which one will be mostly
used?
Is there any future
Hi Thomas!
I got me some NXP pn532 modules some time ago as I heard there is work
on specifying 6LoWPAN over ISO 14443 (which NFC is part of).
Indeed, there is. See https://tools.ietf.org/html/draft-ietf-6lo-nfc-00
Sadly, I didn’t come too far with the driver, as it includes a (more)
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
Hi Simon!
Yes I tried to compile the rpl_udp example for the samr21-xpro but it did
not have enough RAM. Even with RPL in non-storing mode and a very small
routing table it would not fit.
Well, in non-storing you basically don't need any routing table (except for
the root node), but still it
Hi Dinuka,
welcome to RIOT!
I would like to know whether for what platform(ARM,Intel Galileo) we have to
develop the applications?
You can target any platform you want, as long as it runs RIOT. If you want
adapt the project idea as is, the biggest constraint for target hardware is
memory
Hi AAshish,
Thanks for your interest!
On 03/12/15 19:36, Regmi, Aashish wrote:
I was wondering if you could provide more information about the project
so that I can get a clear understanding about the project and about how
to get started with project.
Well, some of us think that it would be
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
X-GOOGLE-CALID:k3ql8setv7l48ofnol0tfuu...@group.calendar.google.com
BEGIN:VTIMEZONE
TZID:Europe/Berlin
X-LIC-LOCATION:Europe/Berlin
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
Hi Oleg,
I think it's a good idea, it will allow easier runnig RIOT code on the
platform.
I will write feedback directly on the PR.
Regards,
Gaëtan
On 03/18/2015 07:23 PM, Oleg Hahm wrote:
Dear rewewing IoTlers,
I just opened a pull request in RIOT that should ease the work with RIOT
Hi Thomas,
Thanks for your informations.
I'm checking the NXP NFC components and need a feedback from the NXP supplier
for the best version. It's seems the NTAG I2C has interested functions.
When we will get the complet datasheet we will check the job we have to do.
Joël
-Message
17 matches
Mail list logo
