[riot-notifications] [RIOT-OS/RIOT] stm32l152re: hard-fault unless power-cycled after flash, or depending on optimization (#11820)

Gaëtan Harter notifications at github.com
Tue Jul 9 19:13:38 CEST 2019

Ideas for bisecting, as you said it changes with optimization

* did you compare the generated low level code to find the difference ?
* does it also crash when compiling only the low level with optimization (by manually adding CFLAGS in the module Makefile)

Note as I just thought about it, if there is re-ordering, a memory barrier may be necessary `__asm__ volatile ("" : : : "memory");`
It was the case in https://github.com/RIOT-OS/RIOT/pull/9068 where waiting on a variable was ignored. It was solved through a function call instead of the mem barrier there.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190709/8a917ae3/attachment.html>

More information about the notifications mailing list