$ BOARD=samr21-xpro make flash
2015-03-27 20:39:53,328 - INFO # > nc ff02::1 1234 test
2015-03-27 20:39:53,329 - INFO #
2015-03-27 20:39:53,333 - INFO # Trying to send 5 bytes to ff02::1:1234
[board never comes back]
Stepping through the code has led my to thread_yield_higher, where the board appears to stop responding, but I'm not sure whether this is due to my non-existant gdb skills or if its related to the actual problem :D
PS: This does not seem to be related to UDP on the SAM R21 in general, since sending UDP packets with pretty much the same code works when taken out of the sixlowapp example. Also, the UDP server seems to work, as UDP packets sent from another app (i.e. not sixlowapp) can be received by the sixlowapp UDP server.
This seems to be memory related. Increasing the KERNEL_CONF_STACKSIZE_DEFAULT by 512 byte "fixed" it, but not sure what implications that might have. Will open an issue in the main RIOT repo.
E.g.
Stepping through the code has led my to
thread_yield_higher
, where the board appears to stop responding, but I'm not sure whether this is due to my non-existant gdb skills or if its related to the actual problem :DPS: This does not seem to be related to UDP on the SAM R21 in general, since sending UDP packets with pretty much the same code works when taken out of the sixlowapp example. Also, the UDP server seems to work, as UDP packets sent from another app (i.e. not sixlowapp) can be received by the sixlowapp UDP server.