Dear RIOTers,
Last friday we merged [1] which refactored the default location where package
sources are fetched. Until then, they were fetched in the application build
directory, e.g. in "/bin/pkg//". This was
inefficient because packages were fetched each time the application was built
for a
here
> part of the output is missing (and thus I get test timeouts).
> -- Kees
>
> On 31-05-2020 21:40, Alexandre Abadie wrote:
>> Hi Kees,
>>
>> Indeed that's a lot of failures!
>>
>> Regarding the failures during flash, the flashing over USB workflow is rat
ests/vfs_plus_stdio](tests/vfs_plus_stdio/test.flash.failed)
> -
> [tests/xtimer_mutex_lock_timeout](tests/xtimer_mutex_lock_timeout/test.flash.failed)
> -
> [tests/xtimer_periodic_wakeup](tests/xtimer_periodic_wakeup/test.flash.failed)
>
>
> On 30-05-2020 22:19, Kees Bakker
ore to come.
>
> On 30-05-2020 21:27, Alexandre Abadie wrote:
>> Hi Kees,
>>
>> To my knowledge, there is no wiki page for this kind of thing.
>> The simplest is probably to open an issue and list there the failures with
>> their
>> output. This way we c
Hi Kees,
To my knowledge, there is no wiki page for this kind of thing.
The simplest is probably to open an issue and list there the failures with
their output. This way we can easily track the on going work to fix them.
See [1] as an example.
Alex
[1]
Ok, I replied in the meantime :)
Good to know that you solved your issue!
- Le 27 Mai 20, à 22:04, Kees Bakker k...@ijzerbout.nl a écrit :
> Found it.
>
> There is a MAKE_TERM_CONNECT_DELAY that defaults to 0. This is the time
> between "make reset" and "make cleanterm".
>
> In my case
Hi,
There's the TESTRUNNER_CONNECT_DELAY environnement variable that can be set for
this purpose from the board Makefile.include file.
This is normally used for any samd21 based board with an Arduino bootloader.
Maybe increase the TERM_DELAY variable from the command line or in the
Hi Kees,
This is not normal, they should appear. This is a bug in the build system. I
tried locally and could reproduce.
The best would be to open an issue on GitHub that describes the problem.
Alex
- Le 24 Mai 20, à 23:32, Kees Bakker k...@ijzerbout.nl a écrit :
> Hey,
>
> I want to
Hi,
While browsing the opened PRs, I think the USB support for STM32 should also go
in that release: [1]
Alex
[1] https://github.com/RIOT-OS/RIOT/pull/12556
- Le 13 Déc 19, à 14:15, Francois-Xavier Molina
a écrit :
> Dear RIOTers,
> This is a friendly reminder for you to send
Hi there,
Sorry for the late reply.
I have some suggestions of new features that I'd like to see in the release:
- add the arduino bootloader feature to samd21 based boards (arduino-mkr, sodaq
and feather-m0). That would improve a lot the user experience with these
boards. See [1] for
Hi,
USB support would be a major milestone for RIOT. It would be awesome to have it
in the next release.
I would like to see the following things in the next release:
- LwM2M support, see [1]
- Support for WolfSSL (provides secure sockets, DTLS, etc), see [2]
I think both are already in a
Dear RIOTers,
we are happy to announce the 18th official release of RIOT:
--- * RIOT 2019.01 * ---
The 2019.01 release includes a number of new features including DMA support on
all STM32 boards, WiFi with IP connectivity on ESP32 and ESP8266, and
Hi,
> Who's interested in collaborating on bringing RIOT onto the thing?
I also received mine today so I can also help. Maybe one day there will be some
in IoT-LAB.
Alex
- Le 12 Fév 19, à 12:53, Kaspar Schleiser kas...@schleiser.de a écrit :
> Hey fellow RIOT'ers,
>
> I've just received
Dear RIOTers,
We've created the 2019.01 release branch, so we are now officially in
feature freeze. This means from now only bugfixes will be backported to
the `2019.01-branch`.
New features can still be merged into master during this period.
The tracking issue of Release candidate 1 [1] is
Here is the missing link for [1]: https://github.com/RIOT-OS/RIOT/milestone/25
Alex
- Le 19 Déc 18, à 11:39, Alexandre Abadie alexandre.aba...@inria.fr a écrit
:
> Dear RIOTers,
>
> Release 2019.01 is coming very soon but Emmanuel and I will be taking care of
> the release pro
Dear RIOTers,
Release 2019.01 is coming very soon but Emmanuel and I will be taking care of
the release process to make this one another success.
The important dates are fixed as follows:
- pre-feature freeze for high impact features: January 11th, 2018
- final feature freeze: January 18th,
Hi Robin,
Thanks for your interest into RIOT and STM32 boards.
There is an (old) existing PR [1] that tries to add an Ethernet driver for
stm32f4. Maybe it's not very different for F7 and you could use it as a
starting point ?
Regards,
Alex
[1] https://github.com/RIOT-OS/RIOT/pull/5643
Hi Kees,
You need a more recent version of the GNU ARM compiler, 7.x, and you only have
6.3. The recommended toolchain is the official one from ARM that can be
downloaded at [1].
Just uncompress the archive somewhere in your filesystem (in /opt for example)
and update your PATH variable. This
Dear RIOT users and developpers,
Today the IoT-LAB team released multiple types of open nodes on the Saclay
site. You can find the details on the IoT-LAB website [1].
These new nodes should simplify the testing on heterogeneous hardware and help
in verifing their interoperability. Most of them
Hi,
Not M33, but Microchip is also selling an evaluation board with an M23.
See
https://uk.farnell.com/microchip/dm320205/kit-eval-xplained-pro-32-bits/dp/2901261
Alex
PS: I'm not working on it.
- Le 17 Oct 18, à 14:17, Juan Ignacio Carrano j.carr...@fu-berlin.de a
écrit :
> Hi
- Le 26 Sep 18, à 13:44, Gunar Schorcht gu...@schorcht.net a écrit :
> Cool, that's exactly what I was looking for.
>
> Unfortunaly, it seem not to be reachable from the top level wiki page or
> I missed it. The only way to find is to use a search engine.
Maybe it could be moved in a
Hi,
The jitsi link doesn't work.
Alex
- Le 24 Sep 18, à 15:46, francisco acosta francisco.aco...@inria.fr a écrit
:
> Hi RIOTers!
>
> Well, there’s the developers meeting today, and I’d like to
> take the opportunity to talk about some recent things on RIOT,
> e.g. build system and
Hi Kees,
- Le 16 Sep 18, à 12:47, Kees Bakker k...@sodaq.com a écrit :
> It was nice to meet you at the RIOT event.
Same here, unfortunately we couldn't discuss more. At least now I can put a
face on your name :)
> Thanks for all the work you put into this. For me it was also beneficial
Hi,
- Le 22 Aoû 18, à 12:31, Kaspar Schleiser kas...@schleiser.de a écrit :
> On 8/21/18 11:28 AM, Jose wrote:
>> I personally think 2. (put them in the RIOT wiki) is the fastest way to
>> go and doesn't bloat the RIOT repository. But I would like to hear some
>> comments about this topic.
>
Wonderful news!
Many thanks a lot Dylan for managing this huge rework and also to all people
involved.
Alex
- Le 2 Aoû 18, à 12:49, Dylan Laduranty a écrit
:
> Dear RIOTers,
> The I2C rework is now merged into RIOT's master branch, then I am really happy
> to announce you the end of
Dear RIOTers,
We are organizing a 4 days hackathon, May 22-25th in Paris.
Information about this event can be found on the wiki [1].
Everyone is welcome to participate!
Attendance is free, but registration is mandatory on the wiki.
To register, put your name on the list, and either add
Hi,
Not sure it will help but I recently tried to use a Semtech LoRa radio with an
Arduino Zero and using a second SPI (for the radio) was working with the
following configuration:
{
.dev = >SPI,
.miso_pin = GPIO_PIN(PA, 19),
.mosi_pin = GPIO_PIN(PA, 16),
.clk_pin = GPIO_PIN(PA, 17),
Hi,
Interesting and promising project.
I have some experience in Qt development, is there a GitHub or something for
the project ?
Alex
- Mail original -
> Hi Everyone,
> I've been on the mailing list for a while and recently have been
> revisiting my own projects and have started
Hi devs,
During the last few days, I worked on a small command line interface tool [1]
for generating starting code for application, test and board support. The idea
came out from a discussion with Jose (@jia200x) in one of his PR [2].
Basically, this tool is meant for simplifying the bootstrap
Hi,
For this board, I think the default UART for stdio is available directly via
the USB port. You just need to open /dev/ttyACM0 (on Linux) at 115200baud.
Alex
- Mail original -
> Hi guys,
> I'm wondering if you guys can help me out with the default UART device for
> the
Hi,
- Mail original -
> Hi,
> as hinted yesterday, I usually need to go around 5:30pm. So I was wondering
> if we can move the meeting to 4pm.
+1
> Cheers,
> Martine
> 2017-11-27 16:33 GMT+01:00 Francisco Javier Acosta Padilla <
> francisco.aco...@inria.fr > :
> > RIOT developers
Hi,
I'll also attend.
Alex
- Mail original -
> Hi Paco,
> I'm in as well.
> Cheers,
> Martine
> 2017-11-04 1:03 GMT+01:00 Thomas Eichinger < tho...@riot-os.org > :
> > Hi Paco,
>
> > Thanks for the initiative!
>
> > I will try to tune in.
>
> > Without wanting to start a
Hi,
- Mail original -
> Dear all,
> I want to use the microlectronik lora flip and click with a samr21 xplained
> pro board in order to transfer the ieee802.15.4 traffic over lora to the
> internet.
The mikrolectronika lora flip and click is based on a microchip rn2483 module
so, with
Dear RIOTers,
we are happy to announce the 12th official release of RIOT:
--- * RIOT 2017.07 * ---
This release provides fixes, code cleanup and improved documentation,
as well as enhancements.
New features brought by this release include:
- CAN bus
Dear RIOT'ers,
I've just tagged the second release candidate of the next release 2017.07 [1].
There is an issue for tracking the testing progress at [2]. If you have some
hardware required for testing (sensors, radios, boards), please try the related
test applications and raise issues if you
Hi,
Are you porting this board [1], then this CPU family is already supported by
RIOT [2] (It's not M0 but M4). You'll just have to add the specific ldscript
for the CPU (STM32L476VG), see [3] for examples. Finally, you'll have to add
the board specific configuration in the board directory.
Dear RIOT'ers,
I've just created the 2017.07 branch and tagged the first release
candidate [1], which means we're now in feature freeze.
Final 2017.07 release is still planned for the 14th of July.
Theres an issue for tracking the testing progress at [2]. Any help is
highly appreciated!
Best,
Dear RIOTers,
Here is reminder about the decided planning for the next release:
- Feature freeze is next friday, 30th of June
- Release is still planned 2 weeks after, the 14th of July
Next week there will be the monthly Hack'n'ACK which is the good time to have
pending PRs merged before the
Dear RIOTers,
The next release, 2017.07, is now on its way!
For this release, we've decided to keep the anticipated merge window for "high
impact"-changes introduced for 2017.04 planning. By high impact, we can think
of low-level/complex changes, features with very large changeset (example:
Hi,
- Mail original -
> This sounds great!
Indeed. I just gave it a try on IoT-LAB (only available on one of the
development server for the moment) and it works very well. The
gnrc_border_router application has to be built using a BAUDRATE of 50 but
otherwise there's nothing
Hi Neo,
Looking at the configuration you provide, it's hard to tell exactly what is the
problem. How did you configure the clock for APB1 and APB2 in periph.conf ?
If you set them to use highest speed (32MHz for this MCU), then the
spi_divtable is wrong and you can reuse the values used for
Hi Neo,
- Mail original -
> Hello RIOT developers,
>
> is anyone working on a STM32F7 port of RIOT OS?
Not that I know. Are you interested in working on that ? That would be very
much appreciated.
Cheers,
Alex
>
> Regards,
>
> Neo
>
>
Well done !
Congrats to everybody and mainly to Peter for driving this release :)
Cheers,
Alex
- Mail original -
> Dear RIOTers,
>
> we are happy to announce the tenth official release of RIOT:
>
>
> --- * RIOT 2017.01 * ---
>
> This release
Hi,
- Mail original -
> Hello!
> Congrats! Looking forward for the complete support on your board, thanks and
> I think we’ll see soon the Arduino Zero on the list ;)
It should arrive soon...
2016-09-30 12:48:03,162 - INFO # main(): This is RIOT! (Version:
Hi Alessandro,
Unfortunately, the current I2C API in RIOT only supports the master mode so you
won't be able to use your samr21-xpro as slave on this kind of bus.
I don't know how complex it is to add support for this feature btw.
Cheers,
Alex
- Mail original -
> Hi all,
> There
Hi,
Unfortunately, I won't be available tomorrow. It will be for next time.
Cheers,
Alex
- Mail original -
> Hi,
> tomorrow we have our monthly Hack'n'ACK again. Oleg and I will most
> likely sit together at FU Berlin and are happy about any other dev
> from Berlin that likes to join.
i with Openlabs
> transceiver running netcat on latest Raspbian-Linux.
>
> Could you clarify which RIOT branch/commit you use?
Latest master. From what you say, the problem comes from the RIOT BR.
Cheers,
Alex
>
> Best,
> Sebastian
>
> > Am 21.06.2016 um 21:42 schrieb Alexa
FYI
By the way, it seems that with the latest version of master, the UDP connection
is not working any more, although ping is still working.
Alex
- Mail transféré -
> Hi devs,
>
> I wrote two new tutorials describing the configuration of a border router and
> CoAP on iotlab with RIOT.
Hi,
Following this thread, I better understand the problems I had when I tried to
port RIOT on Arduino/Genuino Zero in [1]. I'll test your changes in
cpu/samd21/periph/uart.c to see if they fix them. Note that it uses an Atmel
ATSAMD21G18 MCU which is again another variant of samd21.
Alex
Hi,
If someone wants to have a look, here is the PR :
https://github.com/RIOT-OS/RIOT/pull/5462
> > For samr21-xpro, as it is not supported by openlab, we thought it would be
> > a
> > good idea to write this firmware using RIOT.
Note that we can already write RIOT based firmwares for m3 and
Hi devs,
Don't know if it's the best place for asking this.
I recently worked on several things on iotlab:
- adding support of samr21-xpro boards as new custom nodes. Of course, I wrote
a firmware code based on RIOT for the continuous integration system ;). But to
make it fully compatible with
Hi,
I have one so I'll be able to give a try and test. As a side note, the
atmega328p has very limited ressources (32KB flash, 2KB SRAM) so this will
limit the use cases with RIOT (no network stack, etc).
Alex
- Mail original -
> On Thu, May 12, 2016 at 11:01 PM, Martine Lenders
Dear Rioters,
I started to use riot-os a few weeks ago now and I'd like to tell you that your
project is totally awesome and quite well documented.
I first began to write some sample applications with in mind the idea of
providing some easy to use/understand starter tutorials showing the
53 matches
Mail list logo
