Everyone,
I have been able to extend the Wakaama example to build for lwIP sock
IPv4 and IPv6 [1]. This extension builds on the great recent work by
@gchorcht, @wosym, and others to enable IPv4 for lwIP.
I decided to just post a notice rather than create a WIP PR. I had to
#ifdef-out code
, @leandrolanzieri, and @smlng.
Your friendly neighborhood release manager,
Ken Bannister
[1] https://github.com/RIOT-OS/RIOT/tree/2019.10
[2] https://github.com/RIOT-OS/RIOT/archive/2019.10.tar.gz
[3] https://github.com/RIOT-OS/RIOT/releases/tag/2019.10
___
devel
|Dear RIOTers, We've created the 2019.10 release branch, so we are now
officially in feature freeze. This means from now only bugfixes will be
backported to the `2019.10-branch`. If anyone has any bugfixes or
documentation improvements that they feel should be part of this
release, please let
|Dear RIOTeers, The soft feature freeze (for high impact PRs) is now
effective. I have advanced the milestone for the designated high impact
PRs to 2020.01 [1]. As a gentle reminder: the final feature freeze (for
all PRs) is 10 October. As I write this, there are 70 open PRs tagged
for the
like to see
merged during this release cycle. I'm also happy to discuss with those
at the summit over the next couple of days.
Best regards, and happy hacking!
Ken Bannister|
pEpkey.asc
Description: application/pgp-keys
___
devel mailing list
devel
regards
Ashim Asharaph
Ken Bannister 06/22/19 1:34 PM >>>
[The e-mail server of the sender could not be verified (SPF Record)]
I forgot one other thing. You'll need the header for SLIP parameters.
Grab the one from gcoap and copy it to the location of your Makefile [1].
[1]
https://g
I forgot one other thing. You'll need the header for SLIP parameters.
Grab the one from gcoap and copy it to the location of your Makefile [1].
[1]
https://github.com/RIOT-OS/RIOT/blob/master/examples/gcoap/slipdev_params.h
On 6/22/19 7:23 AM, Ken Bannister wrote:
Hi Ashim,
I tried to get
Hi Ashim,
I tried to get ethos to work with a samr21-xpro, but failed. I was not
permitted to assign an IP address to the wired interface. Rather than
pursue that, I was successful with SLIP, the legacy border router tool.
See the gist for the Wakaama Makefile modified for SLIP [1]. Compile
Ashim, Brenton and I were able to resolve the issues they experienced.
The issue link below includes examples to test reception of a large
payload with gcoap PR #11057.
Ken
On 5/9/19 6:21 PM, Ken Bannister wrote:
Sorry to hear you're having issues. It will be easier to track this
problem
n is
used, the success rate is about 5%. Are there any parameters or code
that could be tweaked on either the RIOT application or on the
Californium file server to improve the success rate? What could be
causing the issue or how can I try to determine the problem?
Kind regards
Ashim Asharaph
>>>
Hi Ashim and welcome to RIOT!
As you say, we have two CoAP tools -- nanocoap and gcoap. Here are your
options.
In the latest release, 2019.04, nanocoap has server-based block
capabilities. So, it would work if Californium acted as a client and
PUT/POSTed the file contents to your nanocoap
Thanks, José. I have been reviewing the PR, and I agree it definitely is
usable. I think Leandro has addressed everything to this point.
Brenton, as you can see on the PR, you should be able to build and run
the example. Please add your comments on that PR as well.
Thanks,
Ken
On 4/10/19
I replaced the package using this same approach. [1]
Ken
[1] https://github.com/RIOT-OS/RIOT/issues/9248#issuecomment-416532408
On 12/6/18 8:11 PM, Kees Bakker wrote:
For Ubuntu 18.04 there is a possibility to install the PPA. See [1].
What I did was to first remove (uninstall) all
Martine and I discussed this over a PR a few months ago. The outcome was
to update the Good Pull Request wiki page [1], which basically says what
has just been discussed on this thread. Good to spread the word and
share the link. :-)
Ken
[1]
Everyone,
I was inspired from the talks at the RIOT summit by Jaime Jiménez and
Christian Amsüss to organize a top-level link on the wiki about
standards based application development [1]. It will provide new users
with an entry point to our implementations and packages. The CoAP page
goes
[reposting my last message; apologies for the annoying HTML link line --
Ken]
On 05/07/2018 02:41 AM, David Lyon wrote:
On 2018-05-07 03:51, Mario Hoss wrote:
Hi,
could you give more information on your setup? This is a rather broad
question.
Which temperature sensor are you using on
On 05/07/2018 02:41 AM, David Lyon wrote:
On 2018-05-07 03:51, Mario Hoss wrote:
Hi,
could you give more information on your setup? This is a rather broad
question.
Which temperature sensor are you using on which board?
Cheers
Forgive my popping in on the list with idea's but I'm
Today I described the gcoap API at the Thing-to-Thing Research Group
meeting [1]. Of course, any description of gcoap also includes nanocoap,
the lower level API on which gcoap depends. A question was raised at the
meeting to evaluate the relationship between the two and how they can
evolve
On Thu, Mar 2, 2017 at 5:00 PM, Ken Bannister <kb...@runbox.com
<mailto:kb...@runbox.com>> wrote:
Is there any thought ongoing toward a second RIOT Summit this year?
Thanks,
Ken
___
devel mailing list
devel@riot-os
Is there any thought ongoing toward a second RIOT Summit this year?
Thanks,
Ken
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
going to look at the code in the next few weeks when I have time.
Besides the work for coap observe, what would be the priority to work on?
Koen
On 01/10/2017 12:31 PM, Ken Bannister wrote:
Hi Koen,
Thanks for your interest! I am working actively on Observe support for
gcoap/nanocoap. I don't see
Hi Koen,
Thanks for your interest! I am working actively on Observe support for
gcoap/nanocoap. I don't see a technical difficulty -- the biggest issue
for me is time to work on it. :-/ My first goal is server-side support.
I plan to create a WIP PR within a week or two, so at least there
Aaron,
Great idea to improve the OpenMote integration! Have you tried
contacting the OpenMote developers for guidance? In my experience they
have been very helpful and accommodating. I expect they would appreciate
your effort.
Ken
On 12/12/2015 10:06 PM, Aaron Sowry wrote:
Hi,
I'd like
Oleg,
I'm a contributor to OpenWSN, making a first post here based on your
mention below.
On 03/17/2015 02:58 PM, Oleg Hahm wrote:
Hi Joakim!
What is the current state of radio duty cycling in RIOT?
I know that radio drivers implement on and off functions for the chip, but
how do we make
24 matches
Mail list logo
