[riot-notifications] [RIOT-OS/RIOT] boards/stm32f103c8: fix openocd config (#9760)

Marian Buschsieweke notifications at github.com
Wed May 8 12:23:20 CEST 2019


maribu commented on this pull request.



> +set WORKAREASIZE 0x5000
+
+set CHIPNAME STM32F103C8Tx
+
+# Enable debug when in low power modes
+set ENABLE_LOW_POWER 1
+
+# Stop Watchdog counters when halt
+set STOP_WATCHDOG 1
+
+# STlink Debug clock frequency
+set CLOCK_FREQ 4000
+
+# use hardware reset, connect under reset
+# connect_assert_srst needed if low power mode application running (WFI...)
+reset_config srst_only srst_nogate connect_assert_srst

@MrKevinWeiss: I think that this change is kind of a regression when having the common Blue Pill and Black Pill user in mind: Most users likely just connect SWDIO, SWDCLK, GND and 3.3V to the device. In that case the user will now have to press the reset button manually to trigger flashing and once again after flashing to boot the new firmware.

Would it not make more sense to keep the default reset config, unless e.g. an environment variable like `STM32F103_USE_HW_RESET` is set to `1`?

Alternatively giving a hint in the documentation of the Blue Pill in the flash section that the debugger needs to be connected not only to SWDIO and SWDCLK, but also to the reset pin of the board would solve the issue to me. That way users won't start wondering why flashing using this OpenOCD config won't work without the debugger connected to the reset pin, while it does work fine with the default config of OpenOCD.

-- 
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/9760#pullrequestreview-234979065
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190508/82f14a0a/attachment.html>


More information about the notifications mailing list