Ghani Lawal- SWD does NOT use the bootloader to access the flash memory when programming the STM32 microcontroller, it is able to do so directly
- https://www.st.com/resource/en/reference_manual/rm0444-stm32g0x1-advanced-armbased-32bit-mcus-stmicroelectronics.pdf
- SWCLK has an internal pulldown resistor, so no need to add an external one
- Only need to worry about changing the state of BOOT0 when programming with a communication protocol like CAN, USB, UART etc., also need to change User bytes which I won't be doing
- Since BOOT0 and SWCLK share a pin, BOOT0 also pulled down
- https://www.reddit.com/r/embedded/comments/1ec59iw/shared_boot0_and_swclk/
- https://community.st.com/t5/stm32-mcus-boards-and-hardware/shared-swclk-pin-with-boot0-pin-would-i-need-to-connect-nrst-too/m-p/148981#M4883
- If SWCLK is shared with another pin, then NRST must be connected to debugger interface when programming/debugging
Booting and Debugging
A project log for SurvBot
Remote controlled robot that surveys the environment it is travelling in. PCBs for the Robot and Remote Controller will be original designs
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.