cancel
Showing results for 
Search instead for 
Did you mean: 

Able to program board despite "Debug: Disable" setting

zzzaizz
Associate III

Please use English on this forum.

Translated: The development board is STM32H723, using stm32cubemx for development, debug is disabled, using stlink to burn found that it can be burned, and it can also be debugged, which is very strange! (The development board is STM32H723.) It was developed using STM32CUBEMX. The debugging option is set to "Disabled". Programming with stlink, discovering that it can be programmed and debugged. It's weird! )

Original:

开发板为STM32H723,使用stm32cubemx进行开发,debug勾选禁用,使用stlink烧录发现可以烧录,并且还可以调试,非常奇怪!(开发板是STM32H723。它是使用stm32cubemx开发的。调试选项设置为“禁用”。使用stlink进行编程,发现可以编程,也可以调试。这很奇怪!)

 

1 ACCEPTED SOLUTION

Accepted Solutions

Simply MX debug enabled only block generator use this pins as GPIO or other alternate. With disabled this is unlocked to use , but nothink as debug protect is real here. Exist two ways to prohibit debug . A configure pins on code start to other func in your code. B ...

View solution in original post

11 REPLIES 11
TDK
Super User

> The development board is STM32H723, using stm32cubemx for development, debug is disabled, using stlink to burn found that it can be burned, and it can also be debugged, which is very strange! (The development board is STM32H723.) It was developed using STM32CUBEMX. The debugging option is set to "Disabled". Programming with stlink, discovering that it can be programmed and debugged. It's weird! )

This is not a bug. The pins are set to SWD by default.

The "Disabled" setting doesn't disable the interface, it just fails to initialize the pins. But they are already initialized after reset.

If you feel a post has answered your question, please click "Accept as Solution".
zzzaizz
Associate III

I didn't understand your meaning. I'm sorry. Why is the F1 series selection disabled? Once it is burned, it becomes impossible to re-burn and debug again?

zzzaizz
Associate III

You mean that in CubeMX, "Debug Disabled" only skips the software initialization of the pins. After the STM32H723 is reset, the SWD pins are automatically initialized by the hardware. Even if it is skipped, they will still be automatically initialized by the hardware, so it is still possible to program/debug. Am I understanding correctly?

You mean that in CubeMX, "Debug Disabled" only skips the software initialization of the pins. After the STM32H723 is reset, the SWD pins are automatically initialized by the hardware. Even if it is skipped, they will still be automatically initialized by the hardware, so it is still possible to program/debug. Am I understanding correctly?

Yes, exactly this. The pins are in SWD mode after reset.

If you feel a post has answered your question, please click "Accept as Solution".

Simply MX debug enabled only block generator use this pins as GPIO or other alternate. With disabled this is unlocked to use , but nothink as debug protect is real here. Exist two ways to prohibit debug . A configure pins on code start to other func in your code. B ...

zzzaizz
Associate III

May I ask why the F1 series is not like this?

Sorry, I set it as the answer for you. It should have been set as the answer for the first friend. Although what you both said is correct.

zzzaizz
Associate III

Sorry, I accidentally set it as the answer for another helpful friend instead of you. It should have been set as your answer. Thank you very much for your responses. However, this also brings up the question: Why is it that for the F1 series, setting it as disabled makes it impossible to burn the code and debug?

Why is it that for the F1 series, setting it as disabled makes it impossible to burn the code and debug?