[riot-devel] gnrc_minimal with msp430 family

2016-03-13 Thread malo
be build with some 802.15.4 radio support for msp430 hardware? wbr malo ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT: Production ready?

2016-03-10 Thread malo
Hello, when speaking about production ready... just wondering if somebody is running some long term tests? like at least 48 hrs of hard exercises. wbr malo On 9 March 2016 at 18:03, Emmanuel Baccelli <emmanuel.bacce...@inria.fr> wrote: > Hi Baptiste, > > I think you need to s

Re: [riot-devel] Just another good reason not to implement printf() yourself

2016-03-10 Thread malo
ine _PRIi8 PRIi8, that can be easily changed at one place. as for the most un needed option of the year 2016:) - my target is riot running 6lowpan host with 6lowpan ndp support plus coap server on 8kB of ram. so do not have that much memory to waste for printf. Am I the only one? wbr malo On 9

Re: [riot-devel] wrong checksum

2016-03-08 Thread malo
uf + 1); turned to signed math. change to csum += (uint16_t)... solves the problem. btw: do you run inet_csums unitest for some 16bits platform? to find out if is platform or compiler specific. thanks for all the help wbr malo On 8 March 2016 at 09:25, Alexander Aring <alex.ar...@gmail.c

Re: [riot-devel] wrong checksum

2016-03-07 Thread malo
like some overflow somewhere... I'll keep digging this direction, but any hints are highly appreciated. wbr malo On 7 March 2016 at 10:54, smlng <s...@mlng.net> wrote: > Hi Malo, > > First, as you referred to my question on the list: I eventually got my > setup working, so your's

[riot-devel] wrong checksum

2016-03-06 Thread malo
in advance wbr malo ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Just another good reason not to implement printf() yourself

2016-03-06 Thread malo
Hello Oleg, To make it really usable for alternative printf some cleanup in the formatting strings would be desirable as well. since at the mo there is the mix of direct formatting string with macros like PRIi16... wbr malo On 2 March 2016 at 11:47, Oleg Hahm <oliver.h...@inria.fr>

Re: [riot-devel] Networking Module does not appear in process list

2016-03-03 Thread malo
Hello Bernhard, AFAIK autoinit module is enabled by default, just check if you have defined -DMODULE_AT86RF2XX, -DMODULE_AUTO_INIT_GNRC_NETIF and -DMODULE_AUTO_INIT_GNRC_NETIF while compiling. Im not using default toolchain based on Makefiles so Im not that familiar with it... wbr malo On 3

Re: [riot-devel] Networking Module does not appear in process list

2016-03-02 Thread malo
640 ( 312) | 1100 7 | blink | sleeping _ | 7 | 640 ( 180) | 1600 in the function auto_init_at86rf2xx the thread is created only if the radio was successfully initialized. do you have no error return from the at86rf2xx_init? note that im newbie as well:) wbr malo On 2 Ma

Re: [riot-devel] Just another good reason not to implement printf() yourself

2016-03-01 Thread malo
Hello Oleg, that would be even better indeed. something like #define LOG_PRINTF(...) LOG(LOG_PRINTF, __VA_ARGS__) and to forbid to use printf? wbr malo On 1 March 2016 at 20:31, Oleg Hahm <oliver.h...@inria.fr> wrote: > Hey malo! > > On Tue, Mar 01, 2016 at 08:25:23PM +0

Re: [riot-devel] Just another good reason not to implement printf() yourself

2016-03-01 Thread malo
to custom functions, printf no. Thinking at printf.h with PRINTF macro + formatter macros defined - bad idea? wbr malo On 1 March 2016 at 15:23, Oleg Hahm <oliver.h...@inria.fr> wrote: > Dear re-examining IOTlers, > > I know a lot of us have been unhappy with (some aspects of) N

[riot-devel] Odd problems with xtimer

2016-02-24 Thread malo
else { break; } } quite ugly... Sure there should be check in _add_timer_to_long_list and _add_timer_to_list for duplicates and assert in the case that trying to add pointer which is already in - just to warn user that is doing something bad. wbr malo > <https://github.com/RIOT-OS/R