OpenOCD Connection Error Possibly Caused by Usage of k_msleep Function

[FlameKm]

I was burning stm32f103c8t6, ​​and after burning once, I found that there is no SWD configured, and the OPENOCD cannot be connected under normal operation. Only when the OPENOCD is connected at the moment of reset, can the burning be performed.
I found a way to use CONFIG_GPIO_STM32_SWJ_DISABLE, but I can't use it after configuring
Next I checked the docs and found this

Here I found that there is no relevant description information in the device tree "st, stm32-gpio.yaml" file, and I have no choice
Hoping to provide me with a way to configure swd in the device tree

The environment I use is:
Board: stm32f103c8t6
Board file: stm32f103_mini
Burning tool: OPENOCD+DAP

[FlameKm]

I have repositioned the problem. The issue lies in the usage of k_msleep. After adding this line of code, I encounter an inability to reprogram the device a second time. I need to press the reset button and only then, during the split second of initiating the reprogramming, am I able to proceed. This problem doesn't occur when using other kernel functions. Clearly, the issue is not related to enabling SWJ as mentioned above.

[GeorgeCGV]

SWJ can be configured in DTS within pinctrl:

zephyr/dts/bindings/pinctrl/st,stm32f1-pinctrl.yaml

Lines 20 to 39 in 77698e8

	swj-cfg:
	type: string
	default: "full" # reset state
	enum:
	- "full"
	- "no-njtrst"
	- "jtag-disable"
	- "disable"
	description: |
	Configures number of pins assigned to the SWJ debug port.
	* full - Full SWJ (JTAG-DP + SW-DP).
	* no-njtrst - Full SWJ (JTAG-DP + SW-DP) but without NJTRST.
	Releases: PB4.
	* jtag-disable - JTAG-DP Disabled and SW-DP Enabled.
	Releases: PA15 PB3 PB4.
	* disable - JTAG-DP Disabled and SW-DP Disabled.
	Releases: PA13 PA14 PA15 PB3 PB4.
	If absent, then Full SWJ (JTAG-DP + SW-DP) is used (reset state).

You might have a look into #56096.

[FlameKm]

Thank you very much, I solved the problem that I had configured the swd, but still didn't solve my inability to burn. A day ago, though, suddenly it worked, and I still haven't found out what caused it, but the burn prompts as

Warn : could not read product string for device 0x0d28:0x0204: Operation timed out

After a while it will go to normal burn state No cause of the problem has been found, but now there is no longer a problem of not being able to burn.