Hi, this lines should give you a hint ;-) 2017-06-14 10:48 GMT+02:00 Robert Hartung <[email protected]>: > 2017-06-14 10:42:13,188 - INFO # sys/net/gnrc/netreg/gnrc_netreg.c:49 => n/a > 2017-06-14 10:42:13,203 - INFO # *** RIOT kernel panic: > 2017-06-14 10:42:13,204 - INFO # FAILED ASSERTION.
The thread you register to netreg needs to have a message queue initialized [1]. This can be done using `msg_init_queue()` [2] Cheers, Martine 2017-06-14 10:48 GMT+02:00 Robert Hartung <[email protected]>: > Hello everyone, > > I started to pull the latest RIOT release (actually it's the latest > master for now) into my local repo that has my own board in it. However, > after merging I am not able to run the default example. > I had this problem several months ago but I cannot recall how I solved > it. The problem is that the message queue (msg_array of the thread) is > NULL and thus the netreg throws an error here. > > 2017-06-14 10:42:13,172 - INFO # main(): This is RIOT! (Version: > 2017.01-devel-2165-g39e9b-rhpc-hartung/boards/inga) > 2017-06-14 10:42:13,188 - INFO # sys/net/gnrc/netreg/gnrc_netreg.c:49 => > n/a > 2017-06-14 10:42:13,203 - INFO # *** RIOT kernel panic: > 2017-06-14 10:42:13,204 - INFO # FAILED ASSERTION. > 2017-06-14 10:42:13,204 - INFO # > 2017-06-14 10:42:13,257 - INFO # pid | name | state > Q | pri | stack ( used) | base | current > 2017-06-14 10:42:13,302 - INFO # - | isr_stack | - > - | - | 128 ( -1) | 0xffff | 0xffff > 2017-06-14 10:42:13,350 - INFO # 1 | idle | > pending > Q | 15 | 128 ( 66) | 0x187c | 0x18b9 > 2017-06-14 10:42:13,396 - INFO # 2 | main | > running > Q | 7 | 384 ( 322) | 0x18fc | 0x1a39 > 2017-06-14 10:42:13,444 - INFO # 3 | pktdump | > pending > Q | 6 | 384 ( 66) | 0x1aee | 0x1c2b > 2017-06-14 10:42:13,492 - INFO # 4 | at86rf2xx | > pending > Q | 2 | 256 ( 66) | 0x1cb1 | 0x1d6e > 2017-06-14 10:42:13,523 - INFO # | SUM | > | | 1280 ( 520) > 2017-06-14 10:42:13,523 - INFO # > 2017-06-14 10:42:13,523 - INFO # *** halted. > > Has anyone encountered this issue or can tell me when msg_array of the > thread is initialized? Is this a CPU problem or a board problem? > > Best Regards and Thanks, > Robert Hartung > > -- > Robert Hartung, M.Sc. > > Technische Universität Braunschweig > Institut für Betriebssysteme und Rechnerverbund > Mühlenpfordtstr. 23, Raum 115 > 38106 Braunschweig > > Fon: +49 (531) 391 - 3264 > Fax: +49 (531) 391 - 5936 > E-Mail: [email protected] > _______________________________________________ > users mailing list > [email protected] > https://lists.riot-os.org/mailman/listinfo/users >
_______________________________________________ users mailing list [email protected] https://lists.riot-os.org/mailman/listinfo/users
