[riot-devel] 2016.04-RC3
Hi everyone, by enabling NHC for RC2 we run into problems (e.g. broken UDP), so we decided to disable it again for the release. After reverting it [1], I created another release candidate [2], so please base all your testing efforts on RC3 [3]. Cheers, Hauke [1] https://github.com/RIOT-OS/RIOT/pull/5385 [2] https://github.com/RIOT-OS/RIOT/releases/tag/2016.04-RC3 [3] https://github.com/RIOT-OS/Release-Specs/issues/20 ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] PowerProfiler
I would be more than happy to start it up again and maintain it if it would
be of use to the community. I'll do so as soon as I finish my post-IPSN
Vienna tour :)
On Apr 21, 2016 3:46 PM, "Emmanuel Baccelli"
wrote:
> Great, and overlooked indeed.
> Is this setup still up and running?
> Cheers,
> Emmanuel
>
> On Thu, Apr 21, 2016 at 3:43 PM, Oleg Hahm wrote:
>
>> Dear really-low-power IOTlers,
>>
>> reading through https://github.com/RIOT-OS/RIOT/pull/2309 I stumbled
>> across
>> Michael Andersen's PowerProfiler [1] and was literally shocked that such a
>> nice tool/setup has been gone unnoticed for so long. At least I was not
>> aware
>> of this setup and checking with some other people on IM, it seems that
>> I'm not
>> alone.
>>
>> This looks like a really cool and promising solution to get an
>> understanding
>> of the power consumption for RIOT applications. Great work, Michael!
>>
>> Cheers,
>> Oleg
>>
>> [1] https://github.com/PowerProfiler/TestApplications
>> --
>> panic("Yeee, unsupported cache architecture.");
>> linux-2.6.6/arch/mips/mm/cache.c
>>
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] PowerProfiler
Great, and overlooked indeed.
Is this setup still up and running?
Cheers,
Emmanuel
On Thu, Apr 21, 2016 at 3:43 PM, Oleg Hahm wrote:
> Dear really-low-power IOTlers,
>
> reading through https://github.com/RIOT-OS/RIOT/pull/2309 I stumbled
> across
> Michael Andersen's PowerProfiler [1] and was literally shocked that such a
> nice tool/setup has been gone unnoticed for so long. At least I was not
> aware
> of this setup and checking with some other people on IM, it seems that I'm
> not
> alone.
>
> This looks like a really cool and promising solution to get an
> understanding
> of the power consumption for RIOT applications. Great work, Michael!
>
> Cheers,
> Oleg
>
> [1] https://github.com/PowerProfiler/TestApplications
> --
> panic("Yeee, unsupported cache architecture.");
> linux-2.6.6/arch/mips/mm/cache.c
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] PowerProfiler
Dear really-low-power IOTlers,
reading through https://github.com/RIOT-OS/RIOT/pull/2309 I stumbled across
Michael Andersen's PowerProfiler [1] and was literally shocked that such a
nice tool/setup has been gone unnoticed for so long. At least I was not aware
of this setup and checking with some other people on IM, it seems that I'm not
alone.
This looks like a really cool and promising solution to get an understanding
of the power consumption for RIOT applications. Great work, Michael!
Cheers,
Oleg
[1] https://github.com/PowerProfiler/TestApplications
--
panic("Yeee, unsupported cache architecture.");
linux-2.6.6/arch/mips/mm/cache.c
signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] STM32+CC1101+Border Router error
Hi, make sure you really have the newest master. A fix for that [1] was just merged yesterday. Cheers, Martine [1] https://github.com/RIOT-OS/RIOT/commit/8968b7602f3422 2016-04-21 12:29 GMT+02:00 Viet Hoang : > Hello Riot. > I was cloned newest version of RIOT and build gnrc_border[1] router example > with ethos. Initially it was nice, i was able to ping between my PC and > border router (2001:db8::ff:fe00:2b), In other board (gnrc_networking) it > configure the global address automatically (2001:db8::ff:fe00:5). But when i > ping to the other board form my PC i always received Hop limit ?. > So i'm trying to ping between border_router and other board using global > address (2001), the result is same. But when I change to the local address > (fe80), it ping normally so the local address is working and global address > is not with my board ?. > I was enabled debug with gnrc_ipv6.c and cc110x_rx_tx and I found: > - At the first time ping gnrc_ipv6 pass the packet to 6lowpan as normally, > the cc110x_rx_tx snd packet to 0, and border router send packet back to 1 > (wrong address expected = 5)? > - Next time I ping gnrc_ipv6.c doesn't pass the packet to 6lowpan it say: > ipv6: error determining next hop's link layer address > Please help, thanks. > p/s hwaddr of border router is 2b and gnrc_networking is 5. > > [1]: https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_border_router > > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] STM32+CC1101+Border Router error
Hello Riot. I was cloned newest version of RIOT and build gnrc_border[1] router example with ethos. Initially it was nice, i was able to ping between my PC and border router (2001:db8::ff:fe00:2b), In other board (gnrc_networking) it configure the global address automatically (2001:db8::ff:fe00:5). But when i ping to the other board form my PC i always received Hop limit ?. So i'm trying to ping between border_router and other board using global address (2001), the result is same. But when I change to the local address (fe80), it ping normally so the local address is working and global address is not with my board ?. I was enabled debug with gnrc_ipv6.c and cc110x_rx_tx and I found: - At the first time ping gnrc_ipv6 pass the packet to 6lowpan as normally, the cc110x_rx_tx snd packet to 0, and border router send packet back to 1 (wrong address expected = 5)? - Next time I ping gnrc_ipv6.c doesn't pass the packet to 6lowpan it say: ipv6: error determining next hop's link layer address Please help, thanks. p/s hwaddr of border router is 2b and gnrc_networking is 5. [1]: https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_border_router ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] 2016.04-RC2
Dear RIOTers, I am happy to pronounce the 2nd (and hopefully last) release candidate towards the 2016.04 release [1]. All that is left todo is to go through another round of heavy testing. So please make sure that your setups behave as expected and if possible pitch in with completing the release specs [2]. If you have not already done so, please check also the release note draft [3] and fill in any gaps that you see. Thanks everyone for the great effort so far and let's get this release out! Cheers, Hauke [1] https://github.com/RIOT-OS/RIOT/releases/tag/2016.04-RC2 [2] https://github.com/RIOT-OS/Release-Specs/issues/19 [3] http://www.yourpart.eu/p/oCGClz07sh ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
