- Last edited one year ago ago
STM32MP15 ROM code overview
- 1 ROM Code overview
- 2 Secure boot
- 3 Serial boot
- 4 Flash memory boot
- 5 Engineering boot
- 6 Wake up from low power modes
- 7 Secondary core boot
- 8 RMA boot
- 9 Configuration
- 9.1 Boot device selection via the boot pins and OTP
- 9.2 OTP configuration
- 10 Exported secure services
- 11 System and peripheral registers modification after boot sequence
- 12 Debug and error cases
1 ROM Code overview
ROM code is the first code executed after a reset.
1.1 ROM code features
- The main features of ROM code include:
1.2 Device states
The ROM code behaviour is strongly linked to the device state.
- Open state: By default the device is in open state. Authentication is not mandatory. An authentication error does not prevent FSBL from beeing started.
- Closed state: The device can be closed by writing to bit 6 of OTP WORD0. On closed devices, authentication is mandatory. An authentication error prevents FSBL from beeing started.
- RMA state: A closed device can be put once in RMA state and back again in closed state. On devices in RMA state, all ROM code features, except the one used to go back in closed state are disabled.
2 Secure boot
- it loads FSBL image from selected boot interface
- it authenticates FSBL image
- if image is authenticated, it jumps to FSBL image entry point
2.1 Boot interface selection
As shown in the figure below, the boot interface is determined by the configuration given by boot pins, OTP and a TAMP register.
2.2 Image loading
The ROM code loads the image into SYSRAM internal memory at address 0x2ffc2400.
2.3 FSBL authentication
ROM code implements authentication process as described in STM32MP15 secure boot, Authentication processing chapter.
2.4 Jump to FSBL
If image authentication is successful, the ROM code stores the address of the boot context in r0 register and jumps to the FSBL entry point defined in image header.
The boot context (see boot_api_context_t structure in plat/st/stm32mp1/include/boot_api.h ) is in the first 512 bytes of SYSRAM. It contains information on boot process (such as the selected boot device) and pointers to the ROM code services (used for secure boot authentication).
3 Serial boot
The ROM supports UART and USB serial interfaces.
When serial boot is selected, the ROM code scans in parallel all bootable UART instances and the USB OTG. When an activity is detected on an interface, the boot process goes on with this interface and the others are ignored.
3.1 USB Boot
The ROM supports boot on USB OTG interface with HS PHY.
USB OTG HS is clocked by a 48 MHz and a 60 MHz clock, generated by using HSE clock (from RCC).
The ROM code supports following HSE values:
8, 10, 12, 14, 16, 20, 24, 25, 26, 28, 32, 36, 40, 48 MHz
The ROM code selects which HSE it must use by following these steps:
- If OTP WORD 3.HSE_value is 0b00 (default behaviour), then the ROM code autodetects HSE by using HSI clock (from RCC).
- Recognized values are either 8, 10, 12, 14, 16, 20, 24, 32, 36, 28, 40, or 48 MHz.
- If none of these value can be recognized, the ROM code considers that HSE = 24 MHz.
- If OTP WORD 3.HSE_value is 0b01, then it considers that HSE=24 MHz
- If OTP WORD 3.HSE_value is 0b10, then it considers that HSE=25 MHz
- If OTP WORD 3.HSE_value is 0b11, then it considers that HSE=26 MHz
3.2 UART Boot
The ROM supports the following UART interfaces:
- USART/UART instances:
- USART2, USART3, UART4, UART5, USART6, UART7, UART8
- (one start bit, 8 data bits, even parity bit and one stop bit).
By default the ROM code scans all UARTs listed above. This list may be reduced by blowing fuses in uart_intances_disable field of OTP WORD 3.
In case of serial boot, the ROM code applies the following AFmuxes.
The ROM code first muxes only the RX pins of bootable UART instances and scans in parallel all these RX lines. When an activity is detected on an UART interface, the ROM code muxes the related TX, all others RX are unmuxed, and the boot process goes on with this interface. In case of USB boot detection, all UART RX are unmuxed.
4 Flash memory boot
The ROM supports the following Flash interfaces:
- serial NOR Flash via QUADSPI internal peripheral
- serial NAND Flash via QUADSPI internal peripheral
- parallel NAND Flash via FMC internal peripheral
- SD card via SDMMC internal peripheral
- e•MMC™ via SDMMC internal peripheral
Please refer to STM32MP15 Flash mapping article to see the details about the mapping of each of these memories.
4.1 Boot from NAND
NAND contains n copies of FSBL in n first blocks. The ROM code scans blocks from the first and loads the FSBL contained in the first valid block.
The ROM code supports parallel (via FMC) NANDs and serial (via QSPI) NANDs.
Supported parallel NANDs:
The ROM code supports parallel NAND with the following parameters.
|Data width||ECC1(bits and code)|
|128||2||8, 16||4 (bch), 8 (bch), 1 (hamming)|
|256||4||8, 16||4 (bch), 8 (bch), 1 (hamming)|
|512||4||8, 16||4 (bch), 8 (bch), 1 (hamming)|
|512||8||8, 16||4 (bch), 8 (bch), 1 (hamming)|
- 1: The ROM code supports both parallel NAND with or without on-die ECC. The ECC given here is for NAND without on-die ECC.
Supported serial NANDs:
The ROM code supports serial NAND with the following parameters.
In order to read a NAND flash, the ROM code needs to know the page size, the block size and the number of blocks. For parallel NAND it also needs to know the width and the number of ECC bits.
The ROM code detects NAND parameters storage location by checking OTP WORD9.nand_param_stored_in_otp value.
If OTP WORD9.nand_param_stored_in_otp value is equal to 0 (which is the default) then the NAND shall provide an ONFI compliant parameter table in which the ROM code looks for NAND parameters. “ONFI compliant” means that a NAND provides an ONFI get parameter command that returns a table where at least parameters needed by ROM code are located at standard ONFI offsets.
The number of ECC bits is a particular case, as it can be set by OTP even if OTP WORD9.nand_param_stored_in_otp is equal to 0. This is to allow the user to override the recommanded number of ECC bits given by the parameter table of an ONFI NAND.
In case of serial NAND boot, the ROM code applies the same AFmuxes as the ones for serial NOR.
In case of parallel NAND boot, the ROM code applies the following AFmuxes:
4.2 Boot from NOR
The NOR Flash contains two copies of FSBL. The ROM code tries to load and launch the first copy. In case of failure, it then tries to load the second copy.
The ROM code looks for FSBL1 at offset LBA0 and FSBL2 at offset LBA512.
It is possible to use NOR flash either in single or in dual mode. In dual mode two NOR flashes are connected to the two ports of the NOR interface, and the two memories are used in interlaced mode.
The ROM code uses SPI legacy mode MOSI/MISO only (i.e. uses only 2 pins IO0 and IO1 to transfer data).
The ROM code automatically detects single and dual modes.
In dual mode, BK1_NCS shall be connected to BK2_NCS on board.
By default the ROM code applies the following AFmuxes:
These default AFmux can be overwritten by OTP values defined by OTP WORD 5 to 7.
4.3 Boot from SD
SD cards contain two versions of FSBL. The ROM code tries to load and launch the first copy. In case of failure, it then try to load the second copy.
The ROM code first looks for a GPT. If it finds it, it locates two FSBLs by looking for the two first GPT entries which name begins with "fsbl". If it cannot find a GPT, the ROM code looks for FSBL1 at offset LBA34 and FSBL2 at offset LBA546.
The ROM code uses only one data bit.
By default the ROM code uses SDMMC1 instance.
If OTP WORD 3 sd_if_id field value is not equal to 0, the ROM code uses the value of this field (1 or 2) to determine which SDMMC interface to use.
By default the ROM code applies the following AFmuxes:
|IO name||Pin id (AF mux)|
|SDMMC1_D0DIR||AFMUX OTP needed|
Note that AFmux for SDMMC1_D0DIR has no default value and, if needed, must be applied via OTP WORD 5 to 7.
4.4 Boot from e•MMC™
An e•MMC™ contains two copies of FSBL in its two boot regions, but only one boot region is active at a time. The ROM code tries to load and launch the copy of FSBL contained in the active boot region.
The ROM code uses only one data bit.
By default the ROM code uses SDMMC2 instance.
If OTP WORD 3 emmc_if_id field value is not equal to 0, the ROM code uses the value of this field (1 or 2) to determine which SDMMC interface to use.
By default the ROM code applies following AFmuxes:
|IO name||Pin id (AF mux)|
5 Engineering boot
Engineering boot allows the user to connect a debugger on a opened device, so that it can load and run any software on either the CA7 or the CM4.
The ROM code detects engineering boot when boot pins value is 0b100. The ROM code then simply enters an infinite loop after having:
- re-opened CA7 secure debug,
- started CM4 to run an infinite loop
Engineering boot is not available on closed devices (cf Closing the device)
6 Wake up from low power modes
In case of Standby exit reset, the ROM code proceeds with a "wake up from low power modes" as shown on following figure:
In such resets the Cortex®-M4 is always hold on reset, and only the ROM code on Cortex®-A7 is running. The behavior of the ROM code depends on value of bits MCU_BEN, MPU_BEN of RCC_MP_BOOTCR register.
- Cortex®-M4 wake up
If bit MCU_BEN of RCC_MP_BOOTCR register is set to 1, the ROM proceeds to Cortex®-M4 software wake up.
The ROM code wakes up Cortex®-M4 by releasing it from its "hold on reset" state.
- Cortex®-M4 software integrity check
- Note: if the device is closed, this check is mandatory.
- Cortex®-A7 wake up
The Cortex®-A7 software wake up consists in processing Secure boot.
The ROM will proceed to Cortex®-A7 software wake up in three cases:
- If M4 software wake up is not required (i.e. MCU_BEN=0)
- If M4 software wake up is required (i.e. MCU_BEN=1) but fails,
- If M4 software wake up is required (i.e. MCU_BEN=1), is processed successfully and MPU_BEN is also set to 1
- Cortex®-A7 returns to CStandby low power mode
If Cortex®-M4 software wake up is required (i.e. MCU_BEN=1), is processed successfully and MPU_BEN is set to 0, the ROM enters the Cortex®-A7 in CStandby low power modes.
7 Secondary core boot
At reset, both cores of Cortex-A7 start and run the same instructions.
The ROM code splits the execution flow so that only core0 runs the boot process. The secondary core of the Cortex-A7 is parked in an infinite loop, waiting for a signal from the application to go further. The signal mechanism is based on a secure SGI and the two backup registers
MAGIC_NUMBER and BRANCH_ADDRESS.
To unpark the core1, the application running on core0 shall:
- write jump address into BRANCH_ADDRESS backup register.
- write 0xCA7FACE1 value into MAGIC_NUMBER backup register.
- generate an SGI interrupt to core1
8 RMA boot
RMA boot allow a user to perform a Return Material Authorization (RMA).
- RMA Unlock
- The user can request to put a closed device in RMA state by configuring via Jtag the RMA unlock password in BSEC JTAG_IN register, which the ROM code compares to the password stored in OTP WORD 56
- RMA boot
- When the device is in unlocked for RMA : DFT tests are possible again, but without possibility to access any sensitive data stored in fuses by the user.
- RMA Relock
- The user can request to put a RMA device back in closed state by configuring via Jtag the RMA relock password in BSEC JTAG_IN register, which the ROM code compares to the password stored in OTP WORD 56
9.1 Boot device selection via the boot pins and OTP
|OTP WORD 3
Primary boot source
|OTP WORD 3
Secondary boot source
|Boot source #1||Boot source #2
if #1 fails
if #2 fails
|b000||x (don't care)||x (don't care)||x (don't care)||Serial||-||-|
|b001||!= 0xFF||0 (virgin)||0 (virgin)||QSPI NOR||Serial||-|
|b010||!= 0xFF||0 (virgin)||0 (virgin)||e•MMC™||Serial||-|
|b011||!= 0xFF||0 (virgin)||0 (virgin)||FMC NAND||Serial||-|
|b100||x (don't care)||x (don't care)||x (don't care)||NoBoot||-||-|
|b101||!= 0xFF||0 (virgin)||0 (virgin)||SD-Card||Serial||-|
|b110||!= 0xFF||0 (virgin)||0 (virgin)||Serial||-||-|
|b111||!= 0xFF||0 (virgin)||0 (virgin)||QSPI NAND||Serial||-|
|!= b100||!= 0xFF||Primary1||0 (virgin)||Primary1||Serial||-|
|!= b100||!= 0xFF||0 (virgin)||Secondary1||Secondary1||Serial||-|
|!= b100||!= 0xFF||Primary1||Secondary1||Primary1||Secondary1||Serial|
|!= b100||0xFF||x (don't care)||x (don't care)||Serial||-||-|
1Primary and Secondary are fields of OTP WORD3.
9.2 OTP configuration
The OTP are stored via BSEC internal peripheral.
9.2.1 OTP WORD 0
|6||is_closed||1 bit||Close state|
|0||device is in open state, authentication is optional.|
|1||device is in close state, authentication is mandatory.|
9.2.2 OTP WORD 3
|31-30||HSE_value||2 bits||HSE value|
|0b00||HSE is autodetected|
|0b01||HSE is 24 MHz|
|0b10||HSE is 25 MHz|
|0b11||HSE is 26 MHz|
|29-27||primary_boot_source||3 bits||Primary boot source|
|If different from zero, identifies primary source used for boot|
|0||No primary boot source is defined|
|26-24||secondary_boot_source||3 bits||Secondary boot source|
|If different from zero, identifies secondary source used for boot|
|0||No secondary boot source is defined|
|23-16||boot_source_disable||8 bits||Disable boot source|
|if different from zero each bit disables a boot source|
|0b00000001||disable FMC NAND boot source|
|0b00000010||disable QSPI NOR boot source|
|0b00000100||disable e•MMC™ boot source|
|0b00001000||disable SD boot source|
|0b00010000||disable UART boot source|
|0b00100000||disable USB boot source|
|0b01000000||disable QSPI NAND boot source|
|15-15||no_data_cache||1 bit||Data cache enable enabling|
|If different from zero, data cache is not used by bootrom.|
|0||Data cache is used by bootrom.|
|1||Data cache is not used by bootrom.|
|14-7||uart_intances_disabled||8 bits||Uart instances disabled|
|If different from zero each bit disables an UART instance.|
|If all disable bits are set to 1 then all UARTs are enabled.|
|6||no_usb_dp_pullup||1 bit||USB DP pullup enabling|
|If different from zero, USB DP pull-up is not set|
|0||USB DP pull-up is set|
|1||USB DP pull-up is not set|
|5||no_cpu_pll||1 bit||PLL enabling|
|If different from zero, PLL are not enabled|
|0||PLLs for CPU/AXI are enable for cold boot|
|1||PLLs for CPU/AXI are not enable for cold boot|
|4-3||sd_if_id||2 bits||SD Memory interface|
|If different from zero, identifies the default instance to be used for memory boot|
|0||Source is default one : SDMMC1 with default AFMux|
|1||SDMMC1 (uses non default AFmux defined in OTP)|
|2-1||emmc_if_id||2 bits||e•MMC™ Memory interface|
|If different from zero, identifies the default instance to be used for memory boot|
|0||Source is default one : SDMMC2 with default AFMux|
|2||SDMMC2 (uses non default AFmux defined in OTP)|
|0||qspi_not_default_af||1 bit||QSPI don’t use default AFmux|
|0||QSPI uses default hard coded AFmux|
|1||QSPI uses AFmux defined in OTP|
9.2.3 OTP WORD 4 - Monotonic counter
|31-0||monotonic_val||32 bits||Monotonic counter value|
|Gives the value of monotonic counter|
|0b1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 32|
|0b01xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 31|
|0b001xxxxxxxxxxxxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 30|
|0b0001xxxxxxxxxxxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 29|
|0b00001xxxxxxxxxxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 28|
|0b000001xxxxxxxxxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 27|
|0b0000001xxxxxxxxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 26|
|0b00000001xxxxxxxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 25|
|0b000000001xxxxxxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 24|
|0b0000000001xxxxxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 23|
|0b00000000001xxxxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 22|
|0b000000000001xxxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 21|
|0b0000000000001xxxxxxxxxxxxxxxxxxx||Value of monotonic counter is 20|
|0b00000000000001xxxxxxxxxxxxxxxxxx||Value of monotonic counter is 19|
|0b000000000000001xxxxxxxxxxxxxxxxx||Value of monotonic counter is 18|
|0b0000000000000001xxxxxxxxxxxxxxxx||Value of monotonic counter is 17|
|0b00000000000000001xxxxxxxxxxxxxxx||Value of monotonic counter is 16|
|0b000000000000000001xxxxxxxxxxxxxx||Value of monotonic counter is 15|
|0b0000000000000000001xxxxxxxxxxxxx||Value of monotonic counter is 14|
|0b00000000000000000001xxxxxxxxxxxx||Value of monotonic counter is 13|
|0b000000000000000000001xxxxxxxxxxx||Value of monotonic counter is 12|
|0b0000000000000000000001xxxxxxxxxx||Value of monotonic counter is 11|
|0b00000000000000000000001xxxxxxxxx||Value of monotonic counter is 10|
|0b000000000000000000000001xxxxxxxx||Value of monotonic counter is 9|
|0b0000000000000000000000001xxxxxxx||Value of monotonic counter is 8|
|0b00000000000000000000000001xxxxxx||Value of monotonic counter is 7|
|0b000000000000000000000000001xxxxx||Value of monotonic counter is 6|
|0b0000000000000000000000000001xxxx||Value of monotonic counter is 5|
|0b00000000000000000000000000001xxx||Value of monotonic counter is 4|
|0b000000000000000000000000000001xx||Value of monotonic counter is 3|
|0b0000000000000000000000000000001x||Value of monotonic counter is 2|
|0b00000000000000000000000000000001||Value of monotonic counter is 1|
|0b00000000000000000000000000000000||Value of monotonic counter is 0|
9.2.4 OTP WORD 5 to 7 - AFmux configuration
|31-28||port1[3:0]||4 bits||Bank id|
|27-24||pin1[3:0]||4 bits||0-15||Pin Id|
|23-20||afmux1[3:0]||4 bits||0-15||AFmux value|
|19-16||mode0[3:0]||4 bits||Pin Mode|
|0||AF ; No Pull ; Low Speed|
|1||AF ; No Pull ; Medium Speed|
|2||AF ; No Pull ; High Speed|
|3||AF ; Pull Up ; Low Speed|
|4||AF ; Pull Up ; Medium Speed|
|5||AF ; Pull Up ; High Speed|
|6||AF ; Pull Down ; Low Speed|
|7||AF ; Pull Down ; Medium Speed|
|8||AF ; Pull Down ; High Speed|
|9||GPIO Output High|
|10||GPIO Output Low|
|12||GPIO open drain ; No pull|
|13||GPIO open drain ; Pull Up|
|14||GPIO open drain ; Pull Down|
|15||GPIO analog mode|
|15-12||port0[3:0]||4 bits||Bank id|
|11-8||pin0[3:0]||4 bits||0-15||Pin Id|
|7-4||afmux0[3:0]||4 bits||0-15||AFmux value|
9.2.5 OTP WORD 9 - NAND configuration
|31-31||nand_param_stored_in_otp||1 bit||FMC or serial NAND parameters storage flag|
|0b0||NAND parameters are not stored here in OTP and are available via an ‘ONFI’ compliant get parameter command.|
|0b1||NAND parameters are stored here in OTP|
|30-29||nand_page_size[1:0]||2 bits||FMC or serial NAND page size|
|0||Page size is 2 Kbytes|
|1||Page size is 4 Kbytes|
|2||Page size is 8 Kbytes|
|28-27||nand_block_size[1:0]||2 bits||FMC or serial NAND block size|
|0||Block size is 64 pages|
|1||Block size is 128 pages|
|2||Block size is 256 pages|
|26-19||nand_blocks_nb[7:0]||8 bits||FMC or serial NAND number of blocks|
|N||Number of blocks of NAND in unit of 256 blocks (= N * 256 blocks)|
|18-18||fmc_nand_width||1 bit||FMC NAND width|
|0||FMC NAND is 8 bits|
|1||FMC NAND is 16 bits|
|17-15||fmc_ecc_bit_nb[2:0]||3 bits||FMC NAND number of ECC bits|
|0||No setting. In case on ONFI NAND, means ‘use value defined in parameter table’|
|1||1 bit ECC per 512 bytes, Hamming code|
|2||4 bit ECC per 512 bytes of data, BCH (Bose, Chaudhuri and Hocquenghem) code|
|3||8 bit ECC per 512 bytes of data, BCH (Bose, Chaudhuri and Hocquenghem) code|
|14||spinand_need_plane_select||1 bit||serial NAND need plane select|
|0||serial NAND plane select not needed.|
|1||serial NAND plane select needed.|
|3||disable_ddr_power_optim||1 bit||Disable DDR PLL switch off sequence|
|0||DDR DLL switch off sequence enabled|
|1||DDR DLL switch off sequence disabled.|
|2||disable_hse_bypass_detect||1 bit||Disable HSE bypass detection|
|0||HSE bypass detection enabled.|
|1||HSE bypass detection disabled.|
|1||disable_hse_freq_detect||1 bit||Disable HSE frequency autodetection|
|0||HSE frequency autodetection enabled.|
|1||HSE frequency autodetection disabled.|
|0||disable_traces||1 bit||Disable traces bit|
|0||Bootrom trace are enabled.|
|1||Bootrom trace are disabled.|
9.2.6 OTP WORD 24 to 31 - Public Key Hash (PKH)
OTP WORD 24 to 31 contain the SHA256 hash of ECDSA public key.
|24||31-0||pkh0[31:0]||32 bits||Public Key Hash[31:0]|
|25||31-0||pkh1[31:0]||32 bits||Public Key Hash[63:32]|
|26||31-0||pkh2[31:0]||32 bits||Public Key Hash[95:64]|
|27||31-0||pkh3[31:0]||32 bits||Public Key Hash[128:96]|
|28||31-0||pkh4[31:0]||32 bits||Public Key Hash[159:128]|
|29||31-0||pkh5[31:0]||32 bits||Public Key Hash[191:160]|
|30||31-0||pkh6[31:0]||32 bits||Public Key Hash[223:192]|
|31||31-0||pkh7[31:0]||32 bits||Public Key Hash[255:224]|
9.2.7 OTP WORD 56 - RMA password
|29-15||rma_relock_passwd||15 bits||Password required for RMA ReLock request|
|14-0||rma_passwd||15 bits||Password required for RMA Unlock request|
10 Exported secure services
The ROM exports authentication services to the following stages of the STM32MP15 secure boot.
11 System and peripheral registers modification after boot sequence
11.1.1 All cases except Engineering boot
- PLL1 setting changed from reset values:
- PLL1 clock source is kept as default: HSI (64 MHz)
- DIVM+1 = 5, DIVN+1 = 32
- VCO @819.2 MHz
- PLL1_p @409.6MHz (DIVP+1 = 1)
- Cortex-A7 clocked at 409.6 MHz, using PLL1_p source
- PLL2 setting changed from reset values:
- PLL2 clock source is kept as default: HSI (64 MHz)
- DIVM+1 = 5, DIVN+1 = 35
- VCO @448 MHz
- PLL2_p @448MHz (DIVP+1 = 1)
- AXI (aclk), AHB5 (hclk5) and AHB6 (hclk6) clocked at 149.33 MHz, using PLL2_p source.
- AXIDIV+1 = 3
- APB4 (pclk4) clocked at 74.66 MHz
- APB4DIV = 1 -> pclk4 = aclk/2
- APB5 (pclk5) clocked at 37.33 MHz
- APB5DIV = 2 -> pclk5 = aclk/4
11.1.2 All cases
In all cases, the following clocks are also enabled in RCC
- DDRPHYC pclk4 (DDRPHYCAPBEN = 1), together with DDRPHYC APB reset released (DPHYAPBRST = 0)
- USBPHYC pclk4 and PLL_USB input clock (USBPHYEN = 1)
- STGEN pclk5 and kernel clock (STGENEN = 1)
- ETZPC pclk5 (TZPCEN = 1)
- RTC/TAMP/BackupReg pclk5 (RTCAPBEN = 1)
- HASH1 hclk5 (HASH1EN = 1)
- SYSCFG pclk3 (SYSCFGEN)
- GPIOA hclk4 (GPIOAEN)
In each boot mode, the relevant GPIOA to GPIOZ clocks are enabled depending on interface needed and OTP settings
11.1.3 Engineering boot
- TZEN = 0 (RCC TrustZone security is disabled)
- BOOT_MCU = 1 (MCU is running an infinite loop from RETRAM)
11.1.4 Serial boot
When serial boot (USB/UART) is used:
- The HSE is enabled in crystal, analog bypass or digital bypass according to OSC_OUT setting (refer to the STM32MP15 Reference manuals)
- HSEON = 1
- HSEBYP = 0 or 1
- DIGBYP = 0 or 1
- Relevant UART clocks are enabled on HSI
- STGENC_CNTCR.HLTDBG and EN =1
- STGENC_CNTFID0 = 64000000 (Bootrom uses HSI 64 MHz for STGEN kernel clock)
Depending on Boot interface, GPIOx_MODER, GPIOx_OSPEEDR, GPIOx_PUPDR and GPIOx_AFRH/AFRL are set according to relevant 'Configuration' described above.
12 Debug and error cases
12.1 Debug and Error messages
- PA13 management
- The ROM code uses PA13 pin to communicate some status. On STMicroelectronics boards, PA13 is connected to the red LED, as explained in LEDs and buttons on STM32 MPU boards article.
- in case of boot failure, the PA13 pin is set to low open-drain (i.e. red LED will light bright).
- During UART/USB boot, the PA13 pin will toggle open-drain at a rate of about 5 Hz until a connection is started (i.e. red LED will blink fast).
- With BOOT[2:0] = 0b100 (engineering boot, used for specific debug), PA13 will toggle opendrain at a rate of about 5 kHz (i.e. red LED will light weak).
- In all other cases, the PA13 is kept in it’s reset value, i.e. high-z until software setting.
- During its execution, the ROM writes binary traces in memory.
- Traces can be downloaded from address range 0x2ffc1c00-0x2ffc23ff and analysed with the ROM trace analyser tool.
- In case of internal blocking error, the ROM code writes a uart log error at 9600bauds to PA13 pin.
12.2 Common debug and error cases
- Memory Boot failure
- Secure boot flow always enters the serial boot loop during which the Error LED is blinking. Therefore, observing such blinking when Memory boot is required indicates that Memory boot failed.
- Security issue
- If the bootrom encounters a security issue, it stops immediately the secure boot and sets the Error LED to light bright.