Thanks Oleg for your input!
2016-03-01 20:23 GMT+01:00 Oleg Hahm :
> Hi Baptiste!
>
> On Tue, Mar 01, 2016 at 07:14:50PM +0100, Baptiste Clenet wrote:
>> This is just to know your opinion about this OS:
>> https://www.mbed.com/en/
>> Why RIOT is better than mbed (apar
Hi all,
This is just to know your opinion about this OS:
https://www.mbed.com/en/
Why RIOT is better than mbed (apart from being a multi thread OS)? It
seems to support lot of boards and has a rich network stack.
Cheers,
--
Baptiste
___
devel mailing
Ok I edit my question:
How to add a global unique IPV6 address to RIOT iface? (IPV6 will be
built from a unique EUI64)
2015-11-04 16:35 GMT+01:00 Baptiste Clenet :
> 2015-11-04 16:31 GMT+01:00 Baptiste Clenet :
>> Oleg, where did RIOT find those values for CPUID:
>> #define SAM
2015-11-04 16:31 GMT+01:00 Baptiste Clenet :
> Oleg, where did RIOT find those values for CPUID:
> #define SAMD21_CPUID_WORD0 (*(volatile uint32_t *)0x0080A00C)
> #define SAMD21_CPUID_WORD1 (*(volatile uint32_t *)0x0080A040)
> #define SAMD21_CPUID_WORD2 (*(volatile uint32_t *)0x0080A04
Long HWaddr: 5a:5a:XX
inet addr fe80::585a:XX
If I've got a global EUI64, not local, how should I proceed to tell
RIOT to not create local address? Or did I misunderstand something?
Baptiste
2015-11-04 11:40 GMT+01:00 Baptiste Clenet :
> Thanks Oleg, I will have a look at it.
>
>
Thanks Oleg, I will have a look at it.
2015-11-04 10:05 GMT+01:00 Oleg Hahm :
> Baptiste,
>
>> I wanted to update all ifconfig (Pv6 link-local address, Short
>> address, Long HW address) information from a new EUI-64.
>> I see that it's what RIOT does at build time then. So I should edit
>> the EU
> Not sure, what you're trying to achieve. The IPv6 link-local address is
> calculated at boot time from the node's EUI-64 address and won't be updated
> automatically by just changing the node's HW addresses later on. You can
> however remove the IPv6 address from the given interface and add a new
Hi,
I want to edit the IPV6 address with a new EUI64. Which is the correct
way to edit the IPV6 address? I tried to edit the Long HWaddr with
gnrc_netapi_set but it doesn't automatically update inet6 addr.
Do I have to update each value (ie Short/Long addr and inet6 addr) or
is there a way to prov
Hi Lennart,
>Also, you'd probably have to port it to RIOT first
Just to let you know, libcoap has already been ported to RIOT (as a
pkg as microcoap) [1]
Yes it does network registering automatically but I don't if this port
does it with the new network stack, need testing.
[1] https://github.com
ste
2015-10-29 15:02 GMT+01:00 Ilias Seitanidis :
> Hi Baptiste,
> do you know if libcoap is working on the new stack?
> Best,
> Ilias
>
> 2015-10-29 14:56 GMT+01:00 Baptiste Clenet :
>>
>> Hi Illias,
>>
>> There is an example of the use of microcoap [1] bu
Hi,
Most RIOT cpu use 32bit system or less, in 2038, 32bit system will get
an overflow if they use epoch system and it will comes back to year
1900.
How to avoid this problem, is there a solution with RIOT?
Example:
int date = 2147483649;
struct tm now;
now = *localtime((time_t*)&date);
printf("N
Hi Illias,
There is an example of the use of microcoap [1] but it hasn't been
updated with the new network stack so it might not work.
No microcoap doesn't take care about socket so you have to register a
new UDP socket which will be redirected to your microcoap handle
function.
[1] https://gith
from - but maybe you can measure your board and share your results with us?
>
> Cheers,
> Hauke
>
>
>
> On 26.10.2015 10:59, Baptiste Clenet wrote:
>>
>> @Illias, the current monitor header pins are the only way I know to
>> measure the current consumption. If
@Illias, the current monitor header pins are the only way I know to
measure the current consumption. If you see a better way to do that,
It would be great to try it, let us know.
Baptiste
2015-10-23 11:37 GMT+02:00 Peter Kietzmann :
> Hi Ilias,
>
> I'd love to have such possibility, but from my k
gt;
> This way all code in `app` should form one module.
> Let me know if this helps.
>
> Best,
> Thomas
>
> On 14 Oct 2015, at 9:05 CEST(+0200), Baptiste Clenet wrote:
>
>> Anyone? @OlegHahm , @daniel-k ?
>>
>> 2015-10-09 16:50 GMT+02:00 Baptiste Clen
nclude $(RIOTBASE)/Makefile.base
>
>
> Something like that should work ... but if there is a better solution nice
> to know!
>
> greetings
> Attilio
>
>
> On Fri, Oct 9, 2015 at 4:50 PM, Baptiste Clenet wrote:
>>
>> Hi all,
>>
>> I'm bui
Anyone? @OlegHahm , @daniel-k ?
2015-10-09 16:50 GMT+02:00 Baptiste Clenet :
> Hi all,
>
> I'm building an example (let's called it "app") for RIOT with the
> following structure:
> app/*.c
> app/include/*.h
> app/thingA/*.c
> app/thingA/include*.h
>
Hi all,
I'm building an example (let's called it "app") for RIOT with the
following structure:
app/*.c
app/include/*.h
app/thingA/*.c
app/thingA/include*.h
app/thingB/*.c
app/thingB/include*.h
How to add the required path in the Makefile? Should I add
Makefile.base in each folder or is there anot
2015-08-27 11:50 GMT+02:00 Kaspar Schleiser :
> Hey,
>
> On 08/27/2015 11:39 AM, Baptiste Clenet wrote:
>
>> By the way, flashrom.h should provide a flashrom_read() function or I
>> don't see the utility.
>>
>
> Flash is usually directly accessible, no ne
Sounds great Hauke! I like the multiplexing, it will allow all kind of
storage to be implemented and to separate device driver and the "user
space" (API).
This could be used by OTAU as well!
By "config module for the msba2 and msb-430", did you mean [1]?
Frank, flashrom.h is for me one part of t
Hi,
I know that Riot hasn't got a file system but I'm wondering if we could
still save some raw data in the ROM which would be available after reset?
Could we allow some space in the ROM and write some data?
By the way, have you planned to design a file system for Riot?
--
Baptiste
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
* POSSIBILITY OF SUCH DAMAGE.
2015-06-16 21:10 GMT+02:00 Adam Hunt :
> What license have they released their code under? I'd look myself but I'm
> away from my desk.
>
> Adam
>
> On Tue, Jun 16, 2015, 7:41
; Emmanuel
>
> On Tue, Jun 16, 2015 at 10:34 AM, Baptiste Clenet
> wrote:
>
>> By the way, ATMEL has just released an app with OTA on its last Atmel
>> Studio version. I think iit could be a good start to develop RIOT's
>> OTA.
>>
>> Baptiste
>>
&
By the way, ATMEL has just released an app with OTA on its last Atmel
Studio version. I think iit could be a good start to develop RIOT's
OTA.
Baptiste
2015-06-09 15:16 GMT+02:00 Kaspar Schleiser :
> Hey,
>
> On 06/09/2015 01:37 PM, Baptiste Clenet wrote:
>>
>> - Take
2015-06-09 12:28 GMT+02:00 Kaspar Schleiser :
> Hi,
>
> On 06/09/15 12:06, Baptiste Clenet wrote:
>> IMO, OTA is mandatory for IOT's OS and we should consider it seriously
>> as soon as the network stack will be done/stable.(People can work on in
>> parallel of th
Hi Rioters,
We've talked about OTA at some point earlier and lot of people are
interested in it but is there some people currently working on? (Daniel
Krebs?)
As a reminder, here are some information previously discussed:
- https://github.com/RIOT-OS/RIOT/wiki/minutes-OTA-meetup-13.2.2015
-
https
I would add that we all want this feature to be added to RIOT and we are
pleased for any help to implement it :-)
2015-05-08 6:50 GMT+02:00 Ludwig Ortmann :
> Hi,
>
> This is often called "firmware update" or "OTA" for "(firmware) over the
> air".
>
> We don't have support for this yet, but it is
Hauke, have you found some time to create those diagram?
2015-04-20 9:29 GMT+02:00 Baptiste Clenet :
> Thank you Martine,
> It might be a bit too precise, but it can be useful in term of debugging.
> What I meant was one diagram which sums up the new network stack.
>
> Baptiste,
that it is always a good idea to check if the returned values
> are not NULL (in case of a full packet buffer). Also: I did not compile
> this, so be warned of syntax errors ;-)
>
> Cheers,
> Martine
>
> 2015-04-28 13:54 GMT+02:00 Baptiste Clenet :
>
>> Great Hauke! I
the
> watchdog.
>
> Best regards,
> Joakim Gebart
> Eistec AB
> www.eistec.se
> On Apr 29, 2015 2:43 PM, "Baptiste Clenet" wrote:
>
>> Hi,
>>
>> I've got two questions concerning WDT:
>> - Why do we disable it on the samr21 at
Hi,
I've got two questions concerning WDT:
- Why do we disable it on the samr21 at launch time?
- Why doesn't RIOT provide a wdt.h in drivers/include/periph?
Cheers,
--
*Clenet Baptiste*
___
devel mailing list
devel@riot-os.org
https://lists.riot-o
ed fashion (as in auto_init). But I
> have already a concept in mind, hopefully I will get it done tomorrow - and
> with that I will update the example for UDP. So stay tuned :-)
>
> Cheers,
> Hauke
>
>
> On 28.04.2015 10:10, Baptiste Clenet wrote:
>
> Hi,
>
> Coul
Hi,
Could you add an example/test for the new ng_udp? It will be easier to use
it then.
*@haukepetersen @authmillenon *
Cheers,
--
*Clenet Baptiste*
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
but I drew up some
> (preliminary) activity diagrams for my parts (IPv6 and 6LoWPAN) [1].
>
> Cheers,
> Martine
>
> [1]
> https://www.dropbox.com/sh/rn750v8r8ezszqw/AABKpegFODterMuE6X4g0kQSa?dl=0
>
> 2015-04-17 13:22 GMT+02:00 Baptiste Clenet :
>
>> Thanks Hauke,
ou know once we have
> something.
>
> Cheers,
> Hauke
>
>
>
> On 17.04.2015 12:20, Baptiste Clenet wrote:
>
> Hi,
>
> Is there any diagram somewhere to get an overview of the New Network
> Stack? (How it works, how it is connected from transceiver to UDP)
&
Hi,
Is there any diagram somewhere to get an overview of the New Network Stack?
(How it works, how it is connected from transceiver to UDP)
The links provided in [1] can't be read by draw io.
Cheers,
[1] https://github.com/RIOT-OS/RIOT/wiki/Model-for-the-network-stack
--
*Clenet Baptiste*
__
Thank you Oleg for this complete response!
I agree with you about IETF protocols, everybody should use them and it
will make communication easier.
Concerning IoTBase, I would add that they're thinking about a stack for
constrained devices [1] so it might be easier to implement on RIOT. As you
said,
Thanks a lot!
As soon as I've got this transceiver, I will try it.
2015-03-19 15:09 GMT+01:00 nidhya elango :
> Dear RIOTers,
>
> Further to a few queries, the following PR has been made for the addition
> of a driver for the at86rf212b transceiver from atmel.
> https://github.com/RIOT-OS/RIOT/pu
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 d
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 :
> Hello,
>
> On Wed, Mar 18, 2015 at 10:08 PM, Craig Younkins
> wrote:
> > I think
, so please bear with me ;)
> An update will follow soonish.
>
> If you're on a deadline say so and I can look if I can squeeze it in
> somehow.
>
> Cheers,
> Ludwig
>
> Baptiste Clenet schrieb:
> > Arvid, Ludwig, any improvements concerning OTA?
> >
&g
Arvid, Ludwig, any improvements concerning OTA?
Cheers,
2015-03-09 15:12 GMT+01:00 Baptiste Clenet :
> Hi,
>
> Ludwig, how is the planning going ?
> Could you create a wiki page (like [1]) or an issue (like [2]) with
> description of the work to do as well as assignmen
coap application,
> but I tried to compile it against current master and it worked. Did you try
> a `make distclean` before `make`? Sometimes the checkout points for the pkg
> repositories get a little deprecated.
>
> Cheers,
> Martine
>
> 2015-03-16 10:26 GMT+01:00 Bapt
Hello,
I'm trying to build the microcoap app on Native.
Here is what I get:
workspace/applications-master/microcoap$ make
...
gcc: error: workspace/applications-master/microcoap/bin/native/microcoap.a:
Aucun fichier ou dossier de ce type
make: *** [all] Erreur 1
RIOT folder is in workspace as w
ore/Mutex lockup bug, because the
> Uart output is never garbled, is complete, and in my case always ended
> with
> sec=31 min=5 hour=1
> sec=32 min=5 hour=1
> these lines suspiciously missing from the final lines of output. But
> who knows...
>
> wish you all luck. Karel
>
Hello Karel,
Have you managed to solve your vtimer problem? I've got a similar problem
(different time) on the SAMR21. Look at Jan second answer.
Best,
2015-02-26 9:53 GMT+01:00 Cenk Gündogan :
> I am not certain if Karel joined the mailing list here yet.. you might
> want to include him direc
Hi,
Ludwig, how is the planning going ?
Could you create a wiki page (like [1]) or an issue (like [2]) with
description of the work to do as well as assignment for each task?
Everybody will know how it is going then.
What do you think about it?
Cheers,
[1] https://github.com/RIOT-OS/RIOT/wiki/T
Kévin ;)
> Are you going?
>
> Concerning the next meeting, let's decide early next week if we do it next
> Wednesday or in 2 weeks?
>
> Best,
>
> Emmanuel
>
>
>
> On Wed, Feb 11, 2015 at 10:11 AM, Baptiste Clenet
> wrote:
>
>> Ok, thank yo
is cancelled.
> Best,
> Emmanuel
>
> On Wed, Feb 11, 2015 at 9:56 AM, Baptiste Clenet
> wrote:
>
>> Hi,
>>
>> Is there a meeting today?
>> Could you provide the PlaceCam link of it (10am today)?
>>
>> Cheers,
>>
>> --
>> *Cl
Hi,
Is there a meeting today?
Could you provide the PlaceCam link of it (10am today)?
Cheers,
--
*Clenet Baptiste*
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
d from openocd’s shell output when executing `make
> flash`.
>
> Best, Thomas
>
> On 10 Feb 2015, at 13:41, Baptiste Clenet wrote:
>
> Hi,
>
> I tried the patch Thomas mentioned, it works great! Much faster.
> I only wonder how you get this:
> wrot
gt; verified 16892 bytes in 1.505869s (10.955 KiB/s)
> >>
> >> Cheers,
> >> Lucas
> >>
> >> On 13 Jan 2015, at 11:18, Martin
> wrote:
> >>
> >>> Hi,
> >>>
> >>> my flashing speed is roughly equal to Thomas'
Yes sure
2015-02-06 15:07 GMT+01:00 Ludwig Ortmann :
> Hi Baptiste,
>
> could you open an issue please?
>
> Cheers, Ludwig
>
> On Fri, Feb 06, 2015 at 03:05:05PM +0100, Baptiste Clenet wrote:
> > After pluging a second sender, I got the problem:
> &
#6 0x147a in ?? ()
2015-02-06 15:05 GMT+01:00 Baptiste Clenet :
> After pluging a second sender, I got the problem:
> if ((socket > MAX_SOCKETS) || (socket_base_sockets[socket -
> 1].socket_id == 0)) {
> return false;
> }
> socket = 11534388
> socket
+01:00 Baptiste Clenet :
> I have let my program running with two boards: one sender and one
> receiver. It seems to work for the moment (longer than with three sender
> boards)
>
> 2015-02-06 10:53 GMT+01:00 Baptiste Clenet :
>
>> Hi Oleg,
>>
>> I tried on nat
I have let my program running with two boards: one sender and one receiver.
It seems to work for the moment (longer than with three sender boards)
2015-02-06 10:53 GMT+01:00 Baptiste Clenet :
> Hi Oleg,
>
> I tried on native by simulating the value from sensor and it works after
>
Hi Oleg,
I tried on native by simulating the value from sensor and it works after
one hour of running.
So it seems to be a platform specific problem.
Any clues? Which test shoud I do then? and where the variable socket is
incremented?
Cheers,
2015-02-06 8:18 GMT+01:00 Oleg Hahm :
> Hi Maxence!
You mean than I should slow down the number of transmission? I send a
packet every second on three boards which means that the other board
receives three packets a second.
How may I check apart from slowing down the rate of the transmission?
Baptiste,
2015-02-05 17:36 GMT+01:00 Oleg Hahm :
> Hi
Hello,
I encounter a problem after lot of transmission in UDP.
I use the SAMR21, example RPL_UDP + my application (3 boards send values
from sensor to one board). The 3 boards works fine, the problem occurs on
the board which gathers all the data.
It works for more or less 20 minutes and then I re
I tried the examples:
vtimer_msg_diff:
kernel_init(): jumping into first task...
This is thread 3
Sending timer msg 0...
Initializing "T1".
now=00:8441 -> every 0.10s: T1 diff=ld
Sending timer msg 1...
Initializing "T2".
now=00:17643 -> every 0.20s: T2 diff=ld
Sending timer msg 2...
Initia
Hello,
I use the sleep function and it seems that it blocks the other threads
while sleeping. Has someone got the same problem?
I use sleep in the main thread with RPL_UDP example.
Regards,
--
*Clenet Baptiste*
___
devel mailing list
devel@riot-os.o
Flashing is slow for us too, how do you get the speed?
2015-01-12 11:13 GMT+01:00 Lucas Jenß :
> Hi Thomas,
>
> verification was much faster as 0.4KiB/s, I think around 10 or so for me.
> I checked out OpenOCD on the 9th. I’m also running Linux inside VMware
> though, so maybe it’s just caused by
information:
> https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation
>
> Cheers, Ludwig
>
> On Wed, Jan 07, 2015 at 09:36:20AM +0100, Baptiste Clenet wrote:
> > Hi,
> >
> > I would like to attend the meeting in order to see the progress and ask
> &
Hi,
I would like to attend the meeting in order to see the progress and ask
some questions, if necessary, at the end of the meeting.
When is it planned?
Btw, is PlaceCam a free software? It seems to have only 30 days trial ...
2015-01-06 5:59 GMT+01:00 Martine Lenders :
> Hi,
> Am 05.01.2015 1
Hello RIOTers,
Concerning the network refactoring, do you have a TODO list which lets us
see the progress? We're looking forward to using it with the SAMR21 board
and hope it will be finished soon.
Is there a deadline set for this?
Best,
Baptiste
___
d
Thanks for the answer.
I'm going to implement RNG for the SAMR21 then.
Ok for the RTC.
How about the Energy Saving (MCU) for the SAMR21?
Cheers,
Baptiste
2014-12-04 9:58 GMT+01:00 Ludwig Ortmann :
> Hi,
>
> On Thu, Dec 04, 2014 at 09:07:31AM +0100, Baptiste Clenet wrote:
>
I've got some questions about the implementation of RIOT on the SAMR21:
- RNG: There is no HW module in samd21 but the transceiver at86rf233
provides one (see 40.2 in datasheet). Should we implement it anyway?
- Concerning the MCU, I've seen that "Energy saving modes not fully
utilized
Ashkay,
Here are the PRs:
- I2C: https://github.com/RIOT-OS/RIOT/pull/2016
- SPI: https://github.com/RIOT-OS/RIOT/pull/1997
Best,
2014-11-20 10:22 GMT+01:00 Akshay Mishra :
> Hello Baptiste,
>
> On 13 November 2014 21:52, Baptiste Clenet wrote:
>
>> Hi,
>>
>> I h
Thank you for your answers.
I think we should follow the Hauke's idea with a flag to select the 233 and
a common driver for 23x.
Best,
Le 13 nov. 2014 19:32, "Hauke Petersen" a
écrit :
> Hi Baptiste,
>
> On 13.11.2014 17:22, Baptiste Clenet wrote:
>
> Hi,
>
Hi,
I have seen the pull request from Troels51 concerning the SAMR21.
Is that normal that it uses the transceiver at86rf231 instead of the
at86rf233? The SAMR21 Explained pro board uses the *at86rf233 *transceiver
so something should be changed.
By the way, Rane implemented the SPI here:
https://
Thanks a lot for your answer, that's good to know!
I think someone should add it to the programming rules in the wiki.
Best,
Baptiste
Le 31 oct. 2014 07:55, "Martine Lenders" a écrit :
> Hi,
>
> 2014-10-30 23:47 GMT+01:00 Baptiste Clenet :
>
>> Thank you. Do y
ewlib (or clib on native or avr-clib on arduino or
> msb430-clib on msb-430 ;-)) and afaik this is the consensus.
>
> Best,
> Martine
>
> 2014-10-30 15:01 GMT+01:00 Baptiste Clenet :
>
>> Hello,
>>
>> I'm wondering if RIOT has got Status error code def
Hello,
I'm wondering if RIOT has got Status error code definitions? It would be
useful when using I2C or any communication protocol.
Best,
Baptiste
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
t;
> Currently SERCOM0 is assigned for UART but others are free and I'd take
> SERCOM1 for SPI for now and hence sending out this mail to stay consistent
> if there is any other approach to the driver.
>
> -Akshay
>
> On 27 October 2014 19:09, Baptiste Clenet wrote:
>
Hi Rane,
I'm also very interesting about the adc, uart, spi and transceiver that you
have developped.
When will you add your contributions to the main RIOT repo?
Best,
Baptiste
2014-10-24 18:48 GMT+02:00 Akshay Mishra :
>
>
> On 24 October 2014 18:31, Rane Balslev wrote:
>
>> Hi guys
>>
>>
>
Thanks a lot!
So I'm going to let uart.c like this and begin I2C.c right now.
Best,
2014-10-22 15:35 GMT+02:00 Thomas Eichinger :
> Hi Baptiste,
>
> > On 22 Oct 2014, at 15:08, Baptiste Clenet wrote:
> > Thomas, I'm looking at the uart.c that you wrote. Why did
Hi,
Thank you for your answer Thomas, Akshay.
Akshay, which part are you working on then?
Thomas, I'm looking at the uart.c that you wrote. Why did you only develop
one UART?
After reading the datasheet, I see that the samd21 has got 5 SERCOM which
can be used by USART, I2C, SPI and LIN slave.
Wi
101 - 177 of 177 matches
Mail list logo
