The role of BOOT0 and BOOT1 in STM32 problem set

Publisher:等放假的zr0Latest update time:2018-05-13 Source: eefocusKeywords:stm32  boot0  boot1 Reading articles on mobile phones Scan QR code
Read articles on your mobile phone anytime, anywhere

1. Function and purpose

        There are two pins BOOT0 and BOOT1 on each STM32 chip. The level status of these two pins when the chip is reset determines which area the program starts from after the chip is reset.

BOOT1=x BOOT0=0 // Boot from user flash memory, this is the normal working mode.

BOOT1=0 BOOT0=1 // Boot from system memory. The program function started in this mode is set by the manufacturer.

BOOT1=1 BOOT0=1 // Boot from built-in SRAM. This mode can be used for debugging.


2. Usage


Normally, the BOOT0 and BOOT1 jumpers are both set to 0 (ground). However, in the case of ISP download, BOOT0=1, BOOT1=0. After the download is complete, the BOOT0 jumper is set back to 0, that is, BOOT0=0, BOOT1=0.


3. Notes


Generally, the built-in SRAM is not used for booting (BOOT1=1BOOT0=1), because the data in the SRAM will be lost after the power is off. In most cases, SRAM is only used for debugging, and it can also be used for other purposes. For example, to do local fault diagnosis, write a small program to load it into the SRAM to diagnose other circuits on the board, or use this method to read and write the Flash or EEPROM on the board. This method can also be used to remove the read and write protection of the internal Flash. Of course, when the read and write protection is removed, the content of the Flash is automatically cleared to prevent malicious software from copying.


Keywords:stm32  boot0  boot1 Reference address:The role of BOOT0 and BOOT1 in STM32 problem set

Previous article:STM32 system clock setting, using external active crystal oscillator related configuration issues
Next article:The pins of stm32 have two uses

Latest Microcontroller Articles
  • Learn ARM development(21)
    First, declare the task pointer, because it will be used later. Task pointer volatile TASK_TCB* volatile g_pCurrentTask = NULL;volatile TASK_TCB* vol ...
  • Learn ARM development(20)
    With the previous Tick interrupt, the basic task switching conditions are ready. However, this "easterly" is also difficult to understand. Only through continuous practice can we understand it. ...
  • Learn ARM development(19)
    After many days of hard work, I finally got the interrupt working. But in order to allow RTOS to use timer interrupts, what kind of interrupts can be implemented in S3C44B0? There are two methods in S3C44B0. ...
  • Learn ARM development(14)
    Since development under LINUX is still quite troublesome, is there a more convenient and simple development method under WINDOWS? The answer is yes. Of course, it is not a development tool like ADS, because it ...
  • Learn ARM development(15)
    When using GCC to develop ARM, you will definitely encounter compiler problems. For example, you will encounter various warnings and errors when compiling C code. For example, I encountered several warnings yesterday, so let's take a look at what these warnings are ...
  • Learn ARM development(16)
  • Learn ARM development(17)
  • Learn ARM development(18)
  • Embedded system debugging simulation tool
Change More Related Popular Components

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

About Us Customer Service Contact Information Datasheet Sitemap LatestNews


Room 1530, 15th Floor, Building B, No.18 Zhongguancun Street, Haidian District, Beijing, Postal Code: 100190 China Telephone: 008610 8235 0740

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京ICP证060456号 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号