Re: [riot-devel] UDP datagram sending

2016-06-10 Thread Peter Kietzmann

Hi Mateusz,

nice! I was just about to start looking into it. For the next time I 
recommend to work in branches. (i) It is the "RIOT-way" and (ii) it 
makes reviewing your changes a lot easier.


Cheers
Peter

Am 10.06.2016 um 11:17 schrieb Mateusz Kubaszek:

Problem solved,

It was caused by netreg registering. The msg queue initialization is
performed inside the thread, so if it has lower priority or the
scheduler is not called after thread creation the gnrc_netreg_register()
fails.

The solution was to register this thread after message queue
initialization. So after i placed the gnrc_netreg_register() inside the
thread function all works fine.

Many thanks :)
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


--
Peter Kietzmann

Hamburg University of Applied Sciences
Dept. Informatik, Internet Technologies Group
Berliner Tor 7, 20099 Hamburg, Germany
Fon: +49-40-42875-8426
Web: http://www.haw-hamburg.de/inet
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


[riot-devel] UDP datagram sending

2016-06-10 Thread Mateusz Kubaszek

Problem solved,

It was caused by netreg registering. The msg queue initialization is 
performed inside the thread, so if it has lower priority or the 
scheduler is not called after thread creation the gnrc_netreg_register() 
fails.


The solution was to register this thread after message queue 
initialization. So after i placed the gnrc_netreg_register() inside the 
thread function all works fine.


Many thanks :)
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


[riot-devel] UDP datagram sending

2016-06-10 Thread Mateusz Kubaszek

Hi Peter,
Thank you for your reply.

Hi Mateusz,

hard to figure out from afar. Do you have your code available on github?


https://github.com/mathirkub/RIOT/blob/master/sys/udp_test/udp_test.c#L267-L269



Regarding 1): I don't know how this should be related to you memory 
violation issue.


Regarding 2): AFAIK your thread will have the priority that you give 
on initialization, no matter from where  it is created.


Best
Peter 
I have tested the same scenario (thread creation with higher priority 
and with THREAD_CREATE_WOUT_YIELD) in /test/xtimer_msg project. All 
worked fine. So this could be a specific problem with my project or it 
could be connected with another threads running in this specific program.


It is not caused by insufficient stack size.
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel