An5307 Getting Started With Stm32h7a37b3 Line and stm32h7b0 Value Line Microcontroller Hardware Development Stmicroelectronics
An5307 Getting Started With Stm32h7a37b3 Line and stm32h7b0 Value Line Microcontroller Hardware Development Stmicroelectronics
Application note
Introduction
This application note is intended for system designers developing applications based on STM32H7A3/7B3 line and
STM32H7B0 Value line microcontrollers (referred to as STM32H7A3/7B3/7B0 in this document), and provides an
implementation overview of the following hardware features:
• Power supply
• Package selection
• Clock management
• Reset control
• Boot mode settings
• Debug management.
This document describes the minimum hardware resources required to develop an application based on the
STM32H7A3/7B3/7B0 microcontrollers. It must be used as reference when starting a new design with these microcontroller
lines.
1 General information
• STM32H7A3xx, 32-bit Arm® Cortex®-M7280 MHz MCUs, up to 2-Mbyte Flash memory, 1.4 Mbyte
RAM, 46 com. and analog interfaces, SMPS. Datasheet (DS13195)
• STM32H7B3xx, 32-bit Arm® Cortex®-M7 280MHz MCUs, 2-Mbyte Flash memory, 1.4-Mbyte RAM,
[1]
46 com. and analog interfaces, SMPS, crypto. Datasheet (DS13139)
• STM32H7B0xx, 32-bit Arm® Cortex®-M7 280 MHz MCUs, 128-Kbyte Flash memory, 1.4-Mbyte
RAM, 46 com. and analog interfaces, SMPS, crypto. Datasheet (DS13196).
STM32H7A3/B3 and STM32H7B0 Value line advanced Arm®-based 32-bit MCUs, reference manual
[2]
(RM0455).
[3] STM32H7A3xI/G, STM32H7B0xB and STM32H7B3xI device errata (ES0478).
[4] Oscillator design guide for STM8AF/AL/S, STM32 MCUs and MPUs, application note (AN2867).
[5] STM32 microcontroller system memory boot mode, application note (AN2606).
Migration guide from STM32F7 Series and STM32H743/H753 line to STM32H7A3/7B3 line devices,
[6]
application note (AN5293).
[7] Thermal management guidelines for STM32 applications, application note (AN5036).
2 Power supplies
2.1 Introduction
STM32H7A3/7B3/7B0 microcontrollers are a highly integrated microcontroller that combines the 32-bit
Arm® Cortex®-M7 core running up to 280 MHz with up to 2 Mbytes dual-bank Flash memories and 1.4 Mbytes of
RAM (including 192 Kbytes of TCM RAM, 1.18 Mbytes of user RAM and 4 Kbytes of backup SRAM).
STM32H7A3/7B3/7B0 microcontrollers require at least one single power supply to be fully operational.
Additional power supplies or voltage references are required for some use cases. The general design guidelines
are explained in the following sections. The figure below illustrates the power supply layout.
In all the diagrams, the gray boxes represent power domains.
VDDSMPS SMPS*
VLXSMPS switched mode
power supply
VFBSMPS step down
converter
VSSSMPS
VCAP
LDO Core domain VCORE
VDDLDO Voltage
regulator
(retention, RAM
Always ON
retention)
Power
switch
DStop2
arrays)
(deep
PDR_ON POR/PDR
SRD
Indep.
IOs SmartRun
domain CD
VDDMMC CPU domain
Ios VSS
VSS
VDD50USB USB regulator
VDD33USB
USB
FS IOs
VDD Supply input Main I/O and VDD domain supply input.
VDDSMPS Supply input Supply for switch mode power supply (SMPS) step down converter.
VLXSMPS Supply output SMPS step down converter output.
Supply regulation
VFBSMPS SMPS feedback voltage sense.
input
VSSSMPS Supply input Ground for SMPS step down converter.
VDDLDO Supply input Supply for the integrated low drop out regulator.
Figure 2. System supply configurations for devices with SMPS shows the different
possible regulator supply configurations: using one, both or none.
VCAP Supply input/output
Digital Core supply input / output pin. Is either provided by the embedded regulator or
from an external source.(2)
VDD50USB Supply input Supply for USB regulator.
Embedded USB regulator output or external USB supply when the internal regulator is
VDD33USB Supply input/output
not used.
Reference voltage for ADCs and DACs. Can be generated through the internal
VREF+ Supply input/output
VREFBUF or provided by an external source.
VREF- Supply input Ground reference for ADCs and DACs.
PDR_ON Digital input Control signal to switch the integrated POR/PDR circuitry ON/OFF.
BKUP I/Os GPIOs Driving and performance limitation, see Section 2.1.5 Battery backup domain(3)
VLXSMPS
VLXSMPS SMPS SMPS
VFBSMPS (off) VFBSMPS (on)
VSSSMPS VSSSMPS
VCAP VCAP
VCAP VCAP
3. SMPS supplies LDO (no external supply) 4. External SMPS supply, supplies LDO
VDDLDO VDDLDO
V reg V reg
VSS (on) VSS (off)
To ensure correct device power-up, it is very important that the external component connections are made
according to Figure 2 or Figure 3, depending on the required power scheme.
At power-up the power supply configuration is undefined.
Both regulators (SMPS and LDO) are operational until the system clock starts and the power configuration code
is executed. During this configuration period, the core voltage is regulated to 1.0 V (VOS3) if supplied by LDO, or
1.2 V if supplied by SMPS (see section System supply startup in RM0455 [2]).
This power configuration code programs the power control registers and defines which regulator (or both)
continues to run, and in which configuration. The wanted VOS core voltage is then also programmed. The
regulator (LDO or SMPS) defined to supply the core voltage stabilizes this supply to the new chosen VOS voltage
level. This core supply level must be aligned with the chosen system clock frequency and flash wait state.
See also table Flash recommended number of wait states and programming delay in RM0455 [2]).
Package pin/
Voltage range External components Comments
ball
1.8 to 3.6 V 1 μF ceramic and 100 nF as close as possible Restriction if a DAC or VREFBUF is used.
VDDA
2.0 to 3.6 V to the pin. Restriction if an OPAMP used.
0 to 3.6 V DAC, ADC, OPAMP, COMP, VREFBUF are not used.
Can be connected directly to an external battery or supply.
The external battery can be charged through the internal
5 kΩ or 1.5 kΩ resistor (see the reference manual RM0455
[2].
1 μF ceramic and 100 nF close to the VBAT
VBAT 1.2 to 3.6 V
pin. To be connected to VDD when not used.
When the PDR_ON pin is set to VSS the VBAT pin must
be connected to VDD since this functionality is no longer
available.
Can be higher than VDD supply.
It should be tied to VDD when this dedicated supply is not
needed.
1 μF ceramic and
VDDMMC 1.2 to 3.6 V Internally tied to VDD when this pin is not present in a
100nF as close as possible to the pin.
specific package.
Some warnings are related to this supply, refer to
Section 4 for more details.
VDDSMPS connected to VSS when the converter is not
1.62 to 3.6 V Four different solutions advised:
used.
• 10 μF (best cost trade off), ESR 10mΩ
For SMPS output regulated to 1.8 V.
2.3 to 3.6 V • 2x 10 μF (best area/perf trade off)
VDDSMPS
• 10 μF + 100 nF close from pin (best SMPS supplies the LDO regulator or an external regulator.
cost/perf trade off)
For SMPS output regulated to 2.5 V.
3 to 3.6 V • 10 μF + 4.7 μF (best perf).
SMPS supplies the LDO regulator or an external regulator.
When the SMPS is used:
• 2.2 μH (DCR 110mΩ, Isat 1.7 A,
Itemp 1.4 A) as close as possible to
VLXSMPS. Depending on the use case, the SMPS provides the digital
Vcore or 1.8 V or • LQFP packages: 220 pF ceramic core supply or a supply provided to another regulator
VLXSMPS (external or internal LDO).
2.5 V capacitor on VLXSMPS.
• BGA package: 100 pF ceramic capacitor See Figure 2 for connection details.
on VLXSMPS pin.
• 2x 4.7 μF (ESR 5 mΩ) close to the
inductor on VFBSMPS connection side.
Vcore or 1.8 V or
VFBSMPS - Refer to Figure 2 for the use case dependency of this pin.
2.5 V
VDDLDO ≤ VDD.
For each VDDLDOx pin: 100 nF close to the
VDDLDO 1.62 to 3.6 V Up to three VDDLDO pins available depending on the
pin.
package specification.
Package pin/
Voltage range External components Comments
ball
1 μF ceramic and 100 nF ceramic (USB reg When the regulator is enabled its output is provided
not used) directly to the VDD33USB through the internal connection.
3.0 V to 3.6 V
VDD33USB This pin is internally tied to VDD when it is not present in
1 μF max ESR 600 mΩ (USB reg used).
some specific packages. In consequence, the VDD supply
level must be compliant with VDD33 if the USB is used for
these packages.
0 V to 3.6 V - When USB is not used.
VREF+ is provided externally.
1.62 V to
1 μF ceramic and 100 nF ceramic close to the In some packages, the VREF+ pin is not available
≤ VDDA
pin or connected to VDDA through a resistor (internally connected to VDDA).
2 V to (typically 47 Ω).
VREF+ External VREF+ with VDDA>2 V and ADC used.
≤ VDDA
VREF+ is provided by the embedded VREFBUF regulator.
VREFBUF spec 1 μF Important do not activate the internal VREFBUF when
VREF+ is provided externally.
Only available in some packages
VREF- VSSA Tied to VSSA
Internally tied to VSSA when this pin is not present.
VDDSMPS STM32H7A3/7B3/7B0
VDDSMPS
10 μF 4.7 μ F 2.2 μH SMPS
VLXSMPS Switched Mode
4.7 μF 4.7 μF
100 pF or 200 pF Power Supply
step down
VFBSMPS converter
SMPS enabled SMPS disabled VSSSMPS
VCAP1/2
2.2 μF 100 nF
VCAP3 Core domain
LDO
LDO enabled LDO disabled Voltage
Refer to figure 2 for the use cases dependent VDDLDO regulator
VDDLDO connections (no additional components)
100nF
VDD
Two different possible use cases PDR_ON
POR/PDR
VDDMMC VDDMMC
1 μF
100 nF VDDMMC
100 nF
IOs
BKUP
IOs
VDD50USB
5V
USB regulator
3.3V
4.7 μF VDD33USB
1 μF
1 μF 100 nF USB FS
IOs
Two different possible use cases
VDDA VDDA
Analog domain
1 μF 100 nF
47W
VREF+ VREF+
1 μF 1 μF 100 nF VREF-
VSSA
Three different possible use cases
On some packages neither the VDD33USB pin, nor the VDD50USB pin are available, it is the VDD pin which
supplies the VDD33USB through an internal connection. In this case, VDD is constrained by VDD33USB and must
range between 3.0 V and 3.6 V.
VDD33USB_MAX
=VDD_MAX
VDD= VDD33USB
USB
VDDUSB_MIN functional
VDD_MIN
time
Power-
Power-on Operating mode down
VDD33USB_MAX
USB functional area
VDD33USB
VDD33USB_MIN
VDD USB non
USB non
Functional Functional
area area
VDD_MIN
time
Power-
Power-on Operating mode down
VDD50USB
VDD50USB_MAX = 5.5 V
VDD
VDD50USB_MIN = 4.0 V
time
Power-
Power-on Operating mode down
Battery charging
When VDD is present, the external battery connected to VBAT can be charged through an internal resistance.
This operation can be performed either through an internal 5 kΩ or 1.5 kΩ resistor. The resistor value can be
configured by software.
Battery charging is automatically disabled in VBAT mode.
• In Stop mode :
– The LDO regulator output level is reduced to the state programmed before entering stop mode (SVOS3
to SVOS5). The register and the SRAM content is kept.
– For SVOS3, further power reduction can be achieved by setting the regulator in low power deep sleep
mode (for SVO4 and SVOS5 the low power deep sleep mode is set automatically).
• In Standby mode:
– The regulator is powered down. The registers and SRAM content are lost except for those related to
the standby circuitry and the backup domain.
VDD/VDDA
VPOR/PDR PDR
rising edge
40 mV (min.)
VPOR/PDR hysteresis
falling edge PDR
Temporization
tRSTTEMPO
Reset
For the tRSTTEMPO and VPOR/VPDR threshold value refer to the Reset and power control block characteristics
table in the applicable STM32H7A3/7B3/7B0 datasheet [1].
For packages embedding the PDR_ON pin, the power supply supervisor is enabled by holding PDR_ON high. On
other packages, the power supply supervisor is always enabled.
The power supply supervisor is switched off by connecting the PDR_ON pin to VSS, required to run the devices at
VDD < 1.71 V.
In this case, an external power supply supervisor has to monitor VDD and control the NRST pin.
The device must be maintained in reset mode as long as VDD is below 1.62 V. The implemented circuit is
illustrated in Figure 9. Power supply supervisor interconnection with internal reset OFF.
PDR_ON Reset
controller
VDD
STM1061N16
40 kΩ
Voltage supervisor NRST
OUT
Active-low and open-drain
output
0.1 µF STM32H7
VSS/VSSA
The supply ranges which never go below the 1.71 V are managed more effectively using the internal circuitry (no
additional components are needed, thanks to the fully embedded reset controller).
When the embedded power supply supervisor is off, the following integrated features are no longer supported:
• the brown out reset (BOR) circuitry must be disabled
• the embedded programmable voltage detector (PVD) is disabled
• VBAT functionality is no longer available and VBAT pin must be connected to VDD.
RCC
VDD
Filter nreset (System Reset)
RPU
pwr_bor_rst
NRST
(External reset) pwr_por_rst
CR iwdg1_out_rst
Pulse generator OR
(20 µs min) wwdg1_out_rst
lpwr_rst
SFTRESET
3 Clocks
3.1 Introduction
STM32H7A3/7B3/7B0 microcontrollers support several possible clock sources:
• Two external oscillators (this requires external components):
– High-speed external oscillator (HSE)
– Low-speed external oscillator (LSE).
• Four internal oscillators:
– High-speed internal oscillator (HSI)
– High-speed internal 48 MHz oscillator (HSI48)
– Low-power internal oscillator (CSI)
– Low speed internal oscillator (LSI).
• Three embedded PLLs can be used to generate the high frequency clocks for the system and peripherals.
For both the HSE and LSE, the clock can also be provided from an external source using the OCS_IN and
OSC32_IN pins (HSE bypass and LSE bypass modes).
The Figure 11. Clock generation and clock tree schematic shows the clock generation and clock tree architecture.
For detail explanation refer to the STM32H7A3/7B3/7B0 reference manual [2].
The choice of clocks depends strongly on the application use case .
Refer to the applicable STM32H7A3/7B3/7B0 datasheet [1] for the electrical characteristics (range and accuracy).
VDD Domain
To
LSI IWDG
RTCPRE MCO1SEL
÷ 2 to 63 hsi_ck 0 MCO1PRE
lse_ck 1
hse_ck 2 ÷ 1 to15 MCO1
VDD Domain pll1_q_ck 3
hsi48_ck 4
OSC_IN hse_ck
HSE MCO2SEL
OSC_OUT
sys_ck 0 MCO2PRE
pll2_p_ck 1
HSIDIV hse_ck 2 ÷ 1 to15 MCO2
pll1_p_ck 3
hsi_ck
HSI ÷1,2,4,8 csi_ck 4
lsi_ck 5
hsi_ker_ck
SW
csi_ck
CSI
hsi_ck
0 To CPU,
csi_ker_ck csi_ck sys_ck
1 busses and
hse_ck
HSI48 hsi48_ck 2 peripherals
pll1_p_ck 3
SYNC CKPERSRC
hsi_ker_ck
0 pll[3:1]_q_ck
csi_ker_ck
1 per_ck
pll[3:2]_p_ck
PKSU (Peripheral Kernel clock Selection)
hse_ck
2
PLLSRC pll[3:2]_r_ck
hsi_ck sys_ck
0 PLL1
csi_ck ref1_ck per_ck
1 ÷ DIVM1 pll1_p_ck
hse_ck VCO DIVP1 hse_ck
2 1 to 16 pll1_q_ck To
MHz DIVN1 DIVQ1 hsi_ker_ck
peripherals
DIVR1 pll1_r_ck csi_ker_ck
FRACN1
lsi_ck
lse_ck
PLL2 hsi48_ck
ref2_ck pll2_p_ck
÷ DIVM2 DIVP2
1 to 16 VCO
MHz pll2_q_ck
DIVN2 DIVQ2
pll2_r_ck
DIVR2
FRACN2
I2S_CKIN
PLL3
ref3_ck pll3_p_ck
÷ DIVM3
1 to 16 VCO DIVP3 USB_PHY
MHz pll3_q_ck
DIVN3 DIVQ3
pll3_r_ck
DIVR3
FRACN3
LSE oscillator output(1)(2). The external capacitor must be tuned because it is strongly dependent on the
OSC32_OUT Unconnected in Bypass PCB design.
mode. Not used in Bypass mode.
1. Typical example: (LSE), crystal: 32.768 kHz (6 pF, 50 kΩ), capacitor: 2 x 1.5 pF. All components to be placed as close as
possible from the pins.
2. See application note, AN2867[4].
3. Typical example: (HSE), crystal: 24 MHz (6 pF, 80 Ω), capacitor: 2 x 33 pF. All components to be placed as close as
possible from the pins.
(HiZ)
External clock
source CL1 CL2
Load
capacitors
external
Source frequency range Comments
component
To optimize power consumption, each clock source can be switched on or off independently when it is not used.
Refer to the STM32H7A3/7B3/7B0 reference manual [2] for a detailed description of the clock tree. This
document provides a complete view of clock usage by peripheral is provided in the Kernel clock distribution
overview.
RCC
LSEEXT
clock squarer HSEEXT LSEBYP
HSEBYP LSERDY
0 HSERDY
1 1 Ready logic ck_lse
0 for LSE/HSE ck_hse
LSE_OSC
HSE_OSC LSE_CSS
HSE_CSS rcc_lsecss_fail
rcc_hsecss_fail
OSC32_IN OSC32_OUT
OSC_IN OSC_OUT
To effectively explore the alternate peripheral function pin mapping refer to the STM32CubeMX tool available on
www.st.com.
PC2_C
PC3_C
PA0_C
PA1_C
To ADC
MODERy [1:0] in
GPIOx_MODER PxySO bit in
(reset state: open) SYSCFG_PMCR
(reset state: closed)
To ADC
Alternate Function Input
To on-chip peripherals
Input data register
VDD or
On/off VDD VDD_FT(1)
Read
Pull-up
Schmitt
Trigger On/off
Input Driver
GPIO
PC2
PC3
PA0
PA1
Pull-down
VDD On/off
Output data register
Bit Set/Reset
register
Write
OUTPUT
CONTROL VSS VSS
Read / Write
VSS
Push -Pull
Output Driver Open Drain
From on-chip peripherals Alternate Function Output
Disabled
Analog
From analog peripherals
Each ADC has 6 inputs optimized for high performance INP0 to INP5 and INN0 to INN5 (fast channels).Refer to
the ADC connectivity figure in the STM32H7A3/7B3/7B0 reference manual [2].
The other 14 channels have lower performance (slow channels)
STM32CubeMX and the Pin/ball definition table in the applicable STM32H7A3/7B3/7B0 datasheet [1] show the
availability of the Pxy_C and Pxy depending on the package.
4.2.3 Package having Pxy available but not the peer Pxy_C
Closing the switch in the pad (GPIOx_MODER bit) connects an ADC slow input to the Pxy pad (See the figure
ADC connectivity in the STM32H7A3/7B3/7B0 reference manual [2]). Refer also to the ADC characteristic table
Sampling rate for Slow channels in the appicable datasheet [1].
Another solution is to close the switch between the two peer pads (PxySO bit) instead of closing the switch in the
pad. In this way, an ADC fast input is connected to the Pxy pad. The performance is improved but is not however
as high as for a package having a direct input from a Pxy_C pad. (See the datasheet Sampling rate for Medium
speed channels ADC characteristic table.)
STM32H7A3/7B3/B0
SPI3
VDDMMC
SAI1
UART2
DFSDM1
VDDMMC
OCTOSPIM_P1 Mux PD6 VSS
FMC Mux PD7
SDMMC2
DCMI/PSSI Mux PG9
LCD Mux PG10
Mux PG11
Mux PG12
Mux PG13
Mux PG14
Mux PB8
Mux PB9
5 Boot configuration
The BOOT_ADD0 and BOOT_ADD1 address option bytes allow the boot to be programmed to any boot memory
address from 0x0000 0000 to 0x3FFF 0000 which includes:
• all the Flash memory address space mapped on the AXIM interface
• all the RAM address space: ITCM, DTCM RAMs and SRAMs mapped on the AXIM interface
• the system memory bootloader.
The BOOT_ADD0/BOOT_ADD1 option bytes can be modified after the reset in order to boot from any other boot
address after the next reset.
If the programmed boot memory address is out of the memory mapped area or a reserved area, the default boot
fetch address is programmed as follows:
• Boot address 0: Flash memory at 0x0800 0000
• Boot address 1: ITCM-RAM at 0x0000 0000
When the Flash level 2 protection is enabled, only boot from Flash memory is available. If the boot address
programmed in the BOOT_ADD0 / BOOT_ADD1 option bytes is out of the memory range or belongs to the RAM
address range, the default fetch is forced to the Flash memory at address 0x0800 0000.
Note: When the secure access mode is enabled through option bytes, the boot behavior differs from the above
description (refer to section Root secure services of the product reference manual).
STM32H7
VDD
10 kΩ
BOOT
6 Debug management
6.1 Introduction
The host / target interface is the hardware equipment that connects the host to the application board. This
interface is made of three components: a hardware debug tool, a JTAG or SW connector and a cable connecting
the host to the debug tool. Figure 17 illustrates the connection of the host to the evaluation board.
For more details on how to disable SWJ-DP port pins, refer to the STM32H7A3/7B3/7B0 reference manual [2] I/O
pin alternate function multiplexer and mapping section.
7 Recommendations
7.5 Decoupling
All the power supply and ground pins must be properly connected to the power supplies. These connections,
including pads, tracks and vias should have lowest possible impedance. This is typically achieved with thick track
widths and, preferably, the use of dedicated power supply planes in multilayer PCBs.
In addition, each power supply pair should be decoupled with filtering ceramic capacitors (100 nF) and one single
ceramic capacitor (minimum 4.7 μF) connected in parallel. These capacitors need to be placed as close as
possible to, or below, the appropriate pins on the underside of the PCB. Typical values are 10 nF to 100 nF, but
the exact values depends on the application needs. Figure 19 shows the typical layout of such a VDD/VSS pair.
Cap.
Cap.
VDD VSS
STM32H7xx
8 Reference design
The Evaluation board (STM32H7B3I-EVAL), Discovery kit (STM32H7B3I-DK) and Nucleo board (NUCLEO-
H7A3ZI-Q) are proven designs and must be used as foundations for specific application development.
All the board details are available on www.st.com
Solder Mask
Layer_1 (Top) High Speed Signals+GND
Prepeg
Layer_2 (Inner1) GND Plane
Core
Solder Mask
Layer_1 (Top) High Speed Signals+GND
Prepeg
Layer_2 (Inner1) GND Plane
Core
Core
GND Plane
Layer_5 (Inner4)
Prepeg
Layer_6 (Bottom) High Speed Signals+GND
Solder Mask
PCB PCB
Decoupling
capacitor
Interface connectivity
The SD/SDIO MMC card host interface (SDMMC) provides an interface between the AHB peripheral bus and
Multi Media Cards (MMCs), SD memory cards and SDIO cards. The SDMMC interface is a serial data bus
interface, that consists of a clock (CK), command signal (CMD) and 8 data lines (D[0:7]).
VDD_ SD
10k
SD Card
Level Translator
(e.g. IP4856CX25)
VDD_SD
STM32H7 VDD VDD > 2.9 V SD Card
VDD
VDD
Socket
RPU
10k
RPU
PC12 SDMMC1_CK
CLK
PD2 SDMMC1_CMD
CMD
PB9 SDMMC1_CDIR Open (toggles during
SD-card boot)
SDMMC1 PC8 SDMMC1_D0
EMIF06-
USD05F3
DAT0
PC9 SDMMC1_D1
DAT1
PC10 SDMMC1_D2
DAT2
PC11 SDMMC1_D3
DAT3
DATA_OUT
Filter 3 Transceiver 3
Filter 4 Transceiver 4
Filter 5 Transceiver 5
DATIN6
Filter 6 Transceiver 6
Filter 7 Transceiver 7 DATIN7
DFSDM1
The VDD_MMC pad can supply the SDIO2 I/Os with a dedicated voltage level which can be dynamically
switched, for instance from 3.3 V to 1.8 V (valid only for the SDMMC2 I/Os listed in this schematic (see also
Table 2. PWR input/output signals connected to package pins/ball).
Interface connectivity
The FMC controller and in particular SDRAM memory controller are composed of many signals, most of them
have a similar functionality and work together. The controller I/O signals could be split in four groups as follow:
• An address group which consists of row/column address and bank address.
• A command group which includes the row address strobe (NRAS), the column address strobe (NCAS), and
the write enable (SDWE).
• A control group which includes a chip select bank1 and bank2 (SDNE0/1), a clock enable bank1 and bank2
(SDCKE0/1), and an output byte mask for the write access (DQM).
• A data group/lane which contains 8 signals.
Note: This is depends on the memory specification: SDRAM with x8 bus widths have only one data group, while x16
and x32 bus-width SDRAM have two and four lanes, respectively.
Interface connectivity
The Octo-SPI is a specialized communication interface targeting single, dual, quad and octal communication.
Refer to the STM32H7A3/7B3/7B0 reference manual [2] for details, and to the applicable STM32H7A3/7B3/7B0
datasheet [1] for the full electrical characteristics.
• Match the trace lengths for the data group within ± 10 mm of each other to reduce any excessive skew.
Serpentine traces (this is an “S” shape pattern to increase trace length) can be used to match the lengths.
• Avoid using a serpentine routing for the clock signal and use via(s) as little as possible for the whole path. A
via alters the impedance and adds a reflection to the signal.
• Avoid discontinuities on high speed traces (vias, SMD components).
• If the interface runs below 2.7 V, special care has to be taken when choosing the package pads (see
Section 4.1 I/O speed at low voltage).
Figure 27 and Figure 28 illustrate possible interconnection examples.
If SMD components are needed, place these components symmetrically to ensure good signal quality.
VDD
STM32H7A3/7B3/7B0 VDD VDDVDD
Octo-SPI memory
VDD
VCC
RPU
x8
10k
PC11 OCSPI1_NCS
CS
PC5 OCSPI1_DQS
RWDS (=DQSM)
Port1
PB2 OCSPI1_CLK
22 CK
PB12 OCSPI1_NCLK
22 CK#
OCTOSPI I/O Manager (OCTOSPIM)
PD11/PC10/PE2/PA1 8 bits
PC1/PE8/PE9/PE10 OCSPI1_IO0….IO7
DQ[0:7]
GPIO RSTO
op
GPIO tio INT
OCTOSPI1 na
l
NRST RESET#
OCTOSPI2
VDD VDDVDD
Octo-SPI memory
VCC
RPU
x8
10k
PG12 OCSPI2_NCS
CS
PG15 OCSPI2_DQS
RWDS (=DQSM)
Port2
PF4 OCSPI2_CLK
PF5
22 CK
OCSPI2_NCLK
PF0/PF1/PF2/PF3
22 CK#
OCSPI2_IO0….IO7 8 bits
PG0/PG1/ PG10/PG11
DQ[0:7]
GPIO RSTO
op
GPIO tio
na INT
l
RESET#
STM32H7A3/7B3/7B0 VDD
VDD VDD VDD
Octo-SPI memory
VDD
VCC
RPU
x8
10k
PC11 OCSPI1_NCS
CS
PC5 OCSPI1_DQS
RWDS (=DQSM)
Port1
PB2 OCSPI1_CLK
22 CK
OCTOSPI IO Manager (OCTOSPIM)
PB12 OCSPI1_NCLK
PD11/PC10/PE2/PA1
22 CK#
PC1/PE8/PE9/PE10 OCSPI1_IO0….IO7 8 bits
DQ[0:7]
GPIO RSTO
OCTOSPI1 GPIO op
tio
n
INT
al
NRST RESET#
OCTOSPI2
VDD VDD
Octo-SPI memory
VCC
10k
PG12 OCSPI2_NCS
CS
RWDS (=DQSM)
Port2
CK
CK#
8 bits
DQ[0:7]
GPIO RSTO
op
GPIO tio
n al INT
RESET#
In multiplexed mode, the same bus can be shared between two external Octo-SPI memories. The multiplexed
mode must be configured to avoid unwanted transactions when the OCTOSPIs are disabled.
Note: The multiplexed mode can be very useful for some packages where the port2 is not mapped.
Caution: PG12 is not available in all packages.
This single microphone is then reallocated to DFSDM1. The set of PDM microphones connected to the DFSDM1
can for instance perform beam forming and voice recognition.
This example can be transposed to any other kind of external sensors.
STM32H7A3/7B3/7B0
PB0 (AF06) Digital PDM Microphone
CKOUT
DATIN0
Filter 0 Transceiver 0 CKIN0 CK
DATIN1 PB12 (AF06)
Filter 1 Transceiver 1 CKIN1
Filter 2 Transceiver 2 Beam
Channel Mux
DATA_OUT
Filter 4 Transceiver 4
Filter 5 Transceiver 5
Filter 6 Transceiver 6 DATIN7
Filter 7 Transceiver 7 CKIN7
DFSDM1
CD Domain
CKOUT PB0 (AF04)
DATIN0
Channel Mux
Transceiver 0 CKIN0
Filter 0 DATIN1 PB12 (AF11)
Transceiver 1 CKIN1
DFSDM2
SRD Domain
PDM stereo microphones can use both clock edges for data sampling. One edge for the left channel and the
other for the right channel.
Two DFSDM filters share the same DATIN input.
Two consecutive DATINx inputs cannot be used in such a case (refer to the STM32H7A3/7B3/7B0 reference
manual [2] for details).
Figure 30. Stereo microphone interconnection shows an example of a stereo microphone interconnection.
This example can be transposed to other kinds of external sensors.
DATA_OUT
Filter 3 Transceiver 3
Filter 4 Transceiver 4
Filter 5 Transceiver 5
DATIN6
Filter 6 Transceiver 6
Filter 7 Transceiver 7 DATIN7
DFSDM1
Interface connectivity
The ETM enables the reconstruction of the program execution. The data is traced using the data watchpoint
and trace (DWT) component or the instruction trace macrocell (ITM) whereas instructions are traced using the
embedded trace macrocell (ETM). The ETM interface is synchronous with the four data bus lines D[0:3] and the
clock signal CLK.
STM32CubeMX must be used to determine the most appropriate package for a given use case.
Table 12 gives some typical use case examples. It defines the package which supports a specific use case and
identifies the peripherals that are available. All the examples below are also supported on larger packages.
LQFP100 Camera, Display and µSD DCMI 14 bit parallel camera interface
USB-FS -
SDMMC2 µSD (4 bit mode)
GPIO µSD detection
Memory interface used to drive a display (up to 16 bit
FMC
parallel)
WLCSP132 Camera, Display, OCTOSPI and µSD
I2C2 Touch screen or communication interface
Revision history
Contents
1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1 Reference documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 Power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1.1 External power supplies and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 Clocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2 LSE oscillator clock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.3 Clock security system (CSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.4 Clock recovery system (CRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.2.3 Package having Pxy available but nor the peer Pxy_C . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7 Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
7.1 Printed circuit board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.2 Component position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.3 Temperature dissipation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.4 Ground and power supply (VSS,VDD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.5 Decoupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.6 Other signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.7 Unused I/Os and features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
List of tables
Table 1. Referenced documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Table 2. PWR input/output signals connected to package pins/ball . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Table 3. Power supply connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Table 4. Clock connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 5. Clock source generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table 6. Boot modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 7. STM32H7A3/7B3/7B0 microcontroller bootloader communication peripherals . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 8. TPIU trace pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table 9. External debug trigger pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 10. SWJ debug port pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 11. Flexible SWJ-DP assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table 12. Use case examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 13. Document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
List of figures
Figure 1. Power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 2. System supply configurations for devices with SMPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 3. System supply configurations for devices without SMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 4. Power supply component layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 5. VDD33USB connected to VDD power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 6. VDD33USB connected to external power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 7. VDD50USB power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 8. Power on reset/power down reset waveform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 9. Power supply supervisor interconnection with internal reset OFF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 10. Reset circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 11. Clock generation and clock tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 12. HSE/LSE clock source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 13. HSE/LSE bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 14. Analog inputs for ADC1 and ADC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 15. VDDMMC supplied pads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 16. Boot mode selection implementation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 17. Host to board connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 18. JTAG connector implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 19. Typical layout for VDD/VSS pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 20. Four layer PCB stack-up example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 21. Six layer PCB stack-up example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 22. Decoupling capacitor placement depending on package type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 23. Example of decoupling capacitor placed underneath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 24. µSDCard interconnection example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 25. SDCard interconnection example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 26. eMMC interconnection example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 27. Octo-SPI interconnection example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 28. Octo-SPI multiplexed interconnection example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 29. DSFDM interconnection example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 30. Stereo microphone interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42