Hi Kevin,
I think we had that discussion before, have a look at the CPUID
peripheral driver as well as this PR [1]. I also commented this into the
your PR..
Cheers,
Hauke
[1] https://github.com/RIOT-OS/RIOT/pull/2963
On 19.06.2015 14:15, ROUSSEL Kévin wrote:
There: PR #3223.
Le 19/06/20
There: PR #3223.
Le 19/06/2015 14:09, ROUSSEL Kévin a écrit :
Hello,
I've just made a branch with this.
I'll PR it, so everyone can see what I mean.
And indeed, I think it's related to #3221, since it would be way to have
a seed (hopefully) unique for every mote/device.
Regards,
--
Hello,
I've just made a branch with this.
I'll PR it, so everyone can see what I mean.
And indeed, I think it's related to #3221, since it would be way to have
a seed (hopefully) unique for every mote/device.
Regards,
Le 19/06/2015 14:05, Emmanuel Baccelli a écrit :
Hi Kevin
On Fri, Jun
Hi Kevin
On Fri, Jun 19, 2015 at 1:05 PM, ROUSSEL Kévin
wrote:
> Hello everyone,
>
> I just wanted to know if there was already a feature to determine a mote's
> unique ID (when available) in RIOT.
>
> Such a feature can be highly desirable when running a test on many devices
> (I think about Io
Hello everyone,
I just wanted to know if there was already a feature to determine a
mote's unique ID (when available) in RIOT.
Such a feature can be highly desirable when running a test on many
devices (I think about IoT-LAB testbed, for example), to automatically
assign/compute node address
Hi Michael,
we are using asan with gcc for a c++ project. I also compiled the example in
the wiki and that works as well.
The solution to the undefined reference is as obvious as it sounds, simple link
the asan library. Normally it is linked by default, I guess. To compile a RIOT
native exampl
Hi,
Am Di, 16.06.2015, 16:54, schrieb Hiesgen, Raphael:
> `__asan_â errors when compiling for native. Since I am not familiar
> with the whole RIOT toolchain, are there any modifications that may
> prevent linking to the standard libs?
just out of curiosity - have you tried to use address-
