[riot-notifications] [RIOT-OS/RIOT] boards/stm32: generalize use of connect_assert_srst for flashing (#12158)

Thomas Stilwell notifications at github.com
Fri Sep 20 11:24:52 CEST 2019


> > You mean setting pm?
> 
> I tried that but I'm not able to reproduce whatever state the board was in where it couldn't be flashed

I think that's from one of two reasons:
1) some mcus keep the SWD hardware powered on until the next power-on-reset any time the SWD hardware has been utilized since the last power-on-reset (efm32 does this)
1) some mcus don't power off the SWD hardware even in low power modes for your convenience (kinetis won't de-power SWD in pm 1 but it does in pm 0)

It's a bit of a crap shoot in that there is no standard among the variety of mcus in terms of when SWD should be powered versus not. I don't have experience with stm32 but I'd suggest power-cycling after flashing a firmware that calls pm_set(0) in case it behaves like efm32. If that doesn't do the trick, only the reference manual can say what will.


-- 
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/pull/12158#issuecomment-533479841
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190920/118837ce/attachment.htm>


More information about the notifications mailing list