[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
Wed Jul 10 17:52:20 CEST 2019


I remember that debugging with sleep mode could require some debugger special operation.

For the IoT-LAB tutorials we were recommending to remove `wfi` as it was turning the `JTAG` off https://www.iot-lab.info/tutorials/debugger-on-m3-nodes/
And we never put a workaround by default due to not really understanding the consequence.

It could be configured in the `openocd` script and they configure the `CR` register in this example as you do:
https://sourceforge.net/p/openocd/mailman/message/33251349/

And to connect to a sleeping device it may need to `reset` the device. `connect_assert_srst` This is why it fixes the flasher getting stuck I guess. https://visualgdb.com/tutorials/arm/stm32/sleep/

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/issues/11820#issuecomment-510120203
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190710/5f303f09/attachment.html>


More information about the notifications mailing list