Difference between revisions of "STM32 Jump to System Memory Bootloader"

From Stm32World Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
[[Category:STM32]][[Category:STM32 Development]][[Category:STM32CubeMX]][[Category:STM32CubeIde]][[Category:STM32 HAL]][[Category:Black Pill]][[Category:C]]{{metadesc|Jump to builtin bootloader from application}}
 
[[Category:STM32]][[Category:STM32 Development]][[Category:STM32CubeMX]][[Category:STM32CubeIde]][[Category:STM32 HAL]][[Category:Black Pill]][[Category:C]]{{metadesc|Jump to builtin bootloader from application}}
 
All [[STM32]] [[MCU]]s has a builtin bootloader stored in so-called system memory.  The system memory is a [[ROM]] (read-only memory) which is created during the production of the [[MCU]] and can never be changed.  When the [[MCU]] startup the [[Boot0]] pin is asserted and if high (pulled up to VCC) the [[MCU]] will execute the bootloader.
 
All [[STM32]] [[MCU]]s has a builtin bootloader stored in so-called system memory.  The system memory is a [[ROM]] (read-only memory) which is created during the production of the [[MCU]] and can never be changed.  When the [[MCU]] startup the [[Boot0]] pin is asserted and if high (pulled up to VCC) the [[MCU]] will execute the bootloader.
 +
 +
But what if we would like to execute this bootloader programmatically based on some other event for example the press of a user button.
  
 
== Miscellaneous Links ==
 
== Miscellaneous Links ==

Revision as of 05:41, 16 March 2022

All STM32 MCUs has a builtin bootloader stored in so-called system memory. The system memory is a ROM (read-only memory) which is created during the production of the MCU and can never be changed. When the MCU startup the Boot0 pin is asserted and if high (pulled up to VCC) the MCU will execute the bootloader.

But what if we would like to execute this bootloader programmatically based on some other event for example the press of a user button.

Miscellaneous Links