STMicroelectronics STM32F401 STM32F401 microcontroller, STM32F411 STM32F411 microcontroller Application note

Below you will find brief information for STM32F401, STM32F411. STM32F401 and STM32F411 microcontrollers provide features that allow for communication between peripherals without any need for CPU involvement, improving real-time performance and reducing energy consumption. This capability can be used to enhance a wide range of applications.

PDF

Document

AN4646
Application note
Peripheral interconnections on STM32F401 and STM32F411 lines
Introduction
On top of the highest performance and the lowest power consumption of the STM32F4
family, STM32F401/411 peripherals can communicate autonomously, without any
intervention from the CPU, via a network known as peripheral interconnect matrix.
This STM32F401/411 feature enhances CPU real-time performance while substantially
reducing its energy consumption.
The present document first describes the peripheral interconnect matrix features and then
provides an overview on the peripheral interconnections and on how to configure them
depending on your application. This description is completed by a detailed application
example.
This application note must be read in conjunction with STM32F401 line reference manual
(RM0383) and STM32F411 line reference manual (RM0368). Both documents are available
from http://www.st.com/stm32.
Table 1. Applicable products
March 2015
Type
Product lines
Microcontrollers
STM32F401
STM32F411
DocID027369 Rev 1
1/17
www.st.com
1
Contents
AN4646
Contents
1
Module overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2
Peripheral interconnect matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1
2.2
2.3
2.4
2.5
2.6
3
Timers block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.1
From TIM to TIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.2
From TIM to ADC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.3
From TIM to DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Analog block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.1
From temperature sensor to ADC1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.2
From Analog block to DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Clocks block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.1
From CSS to TIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.2
From LSE, LSI, RTC to TIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
System block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
2.4.1
From VBAT, VREFINT to ADC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4.2
From EXTI to analog block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Communication interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
2.5.1
From USB block to TIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5.2
From Communication interfaces to DMA . . . . . . . . . . . . . . . . . . . . . . . . 12
DMA block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Application example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1
Hardware description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2
Software description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4
Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2/17
DocID027369 Rev 1
AN4646
List of tables
List of tables
Table 1.
Table 2.
Table 3.
Table 4.
Applicable products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
STM32F401/411 peripheral interconnect matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Peripheral interconnect configuration detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
DocID027369 Rev 1
3/17
3
List of figures
AN4646
List of figures
Figure 1.
Figure 2.
Figure 3.
Figure 4.
Figure 5.
4/17
STM32F401/411 peripheral interconnection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Master/Slave timer overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Master TIM/Slave ADC overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
SOF connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Application overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
DocID027369 Rev 1
AN4646
1
Module overview
Module overview
Several peripherals can be directly interconnected and configured to send/respond to event
signals that can be internally routed to/from other peripherals in the device.
The STM32F401/411 autonomous peripherals include:
•
Timers that can either be internally connected to each other or connected to the DMA
or to the analog block.
•
Analog block that can receive events from a timer or send events to the DMA.
•
Clocks block that can send events to timers.
•
System block that can send events to the analog block.
•
Communication interfaces that can send events to the timers or to the DMA.
An overview of STM32F401/411 peripheral interconnections is given in Figure 1:
STM32F401/411 peripheral interconnection overview.
DocID027369 Rev 1
5/17
16
7LPHUV
95(),1
9%$7
$GYDQFHGFRQWUROWLPHUV
(;7,
6WDUWWULJHU
LQMHFWHGJURXS
6\VWHP
7,0
$QDORJ
9%$7
95(),1
7,0[B75*2,75[
$'&amp;
96(16(
(;7,
7,0;B%.,1
Module overview
6/17
Figure 1. STM32F401/411 peripheral interconnection overview
6WDUWWULJHU
UHJXODUJURXS
(;7,
7HPSHUDWXUH
VHQVRU
*HQHUDOSXUSRVHWLPHUV
'0$
DocID027369 Rev 1
7,0
&amp;ORFNV
7,0
7,0
7,0
7,0[B75*2,75[
/6,
57&amp;
5(4B675($0[
62),75[
7,0B&amp;+
7,0
7,0
7,0[B75*2
,75[
7,0
*HQHUDOSXUSRVHWLPHUV
2QO\RQ670)[
'0$
'0$
7,0[B83
&amp;66
/6(
7,0[&amp;+[
7,0[B75*2
&amp;RPPXQLFDWLRQLQWHUIDFHV
,&amp;
86$57
63,
,6
,&amp;
86$57
63,
,6
,&amp;
86$57
63,
,6
6',2
27*)6
63,
,6
63,
,6
06Y9
AN4646
AN4646
2
Peripheral interconnect matrix
Peripheral interconnect matrix
STM32F401/411 peripherals are interconnected through the peripheral interconnect matrix
that allows to directly connect one peripheral to another without waking up the CPU.
These interconnections can operate in Run, Sleep or Stop modes, depending on
peripherals.
Peripherals that respond to events are referred to as users while peripherals that send
events are referred to as generators.
Table 2. STM32F401/411 peripheral interconnect matrix(1)
Users
Timers
DMA
Analog
DMA1 DMA2
ADC1
Generators
Timers
TIM 1
TIM 2
TIM 3
TIM 4
TIM 5
TIM 11
TIM1
-
X
X
X
-
-
-
X
X
TIM2
X
-
X
X
X
-
X
-
X
TIM3
X
X
-
X
X
-
X
-
X
TIM4
X
X
X
-
X
-
X
-
X
TIM5
X
-
X
-
-
-
X
-
X
ADC1
-
-
-
-
-
-
-
X
-
VSENSE
-
-
-
-
-
-
-
-
X
LSI
-
-
-
-
X
-
-
-
-
LSE
-
-
-
-
X
-
-
-
-
RTC
-
-
-
-
X
X
-
-
-
CSS
X
-
-
-
-
-
-
-
-
Analog
Clocks
DocID027369 Rev 1
7/17
16
Peripheral interconnect matrix
AN4646
Table 2. STM32F401/411 peripheral interconnect matrix(1) (continued)
Users
Timers
DMA
Analog
DMA1 DMA2
ADC1
Generators
Communication
interfaces
System
TIM 1
TIM 2
TIM 3
TIM 4
TIM 5
TIM 11
OTG FS
-
X
-
-
-
-
-
-
-
SPI1/I2S1
-
-
-
-
-
-
-
X
-
SPI2/I2S2
-
-
-
-
-
-
X
-
-
SPI3/I2S3
-
-
-
-
-
-
X
-
-
SPI4/I2S4
-
-
-
-
-
-
-
X
-
SPI5/I2S5
-
-
-
-
-
-
-
X
-
I2C1
-
-
-
-
-
-
X
-
-
I2C2
-
-
-
-
-
-
X
-
-
I2C3
-
-
-
-
-
-
X
-
-
USART1
-
-
-
-
-
-
-
X
-
USART2
-
-
-
-
-
-
X
-
-
USART6
-
-
-
-
-
-
-
X
-
SDIO
-
-
-
-
-
-
-
X
-
VBAT
-
-
-
-
-
-
-
-
X
VREFINT
-
-
-
-
-
-
-
-
X
EXTI
-
-
-
-
-
-
-
-
X
1. In gray, the peripherals that are available only on STM32F411 line.
2.1
Timers block
2.1.1
From TIM to TIM
Some timers are linked together internally for timer synchronization or chaining. When one
timer (TIMx) is configured in Master mode, it can reset, start, stop or clock the counter of
any other timer configured in Slave mode (TIMy).
The master output is TIMx_TRGO signal. This output is configured as a timer event through
TIMx_CR2 register. It is sent to TIMy_ITR0/ITR1/ITR2/ITR3 inputs.
Figure 2: Master/Slave timer overview gives an overview of the trigger selection and the
master mode selection blocks.
8/17
DocID027369 Rev 1
AN4646
Peripheral interconnect matrix
Figure 2. Master/Slave timer overview
0DVWHU7,0
6ODYH7,0
&amp;ORFN
006
606
76
8(9
3UHVFDOHU
0DVWHU
PRGH
FRQWURO
&amp;RXQWHU
75*2
,75
6ODYH
PRGH
FRQWURO
&amp;.B36&amp;
3UHVFDOHU
&amp;RXQWHU
069
A description of this feature is provided in the Timer synchronization section on RM0368
and RM0383 reference manuals, while all the possible master/slave connections are
described in the TIMx internal trigger connection tables.
2.1.2
From TIM to ADC
Some timers can be used to generate an ADC trigger event.
The timer output can be either TIMx_TRGO signal or TIMx_CHx event. It is input to ADC
EXTSEL[3:0] and JEXTSEL [3:0] signals.
Figure 3: Master TIM/Slave ADC overview gives an overview of the trigger selection and
master mode selection blocks.
Figure 3. Master TIM/Slave ADC overview
0DVWHU7,0
6ODYH$'&amp;
(;76(/&gt;@ELWV
&amp;ORFN
006
8(9
3UHVFDOHU
&amp;RXQWHU
0DVWHU
PRGH
FRQWURO
75*2
-(;76(/&gt;@ELWV
$QDORJWR
GLJLWDO
FRQYHUWHU
7,0[B&amp;+[
069
ADC synchronization is described in the Conversion on external trigger and trigger polarity
section of RM0368 and RM0383 reference manuals. The connection between timers and
ADCs regular and injected channels is described in External trigger for regular channels and
External trigger for injected channels tables.
2.1.3
From TIM to DMA
Refer to Section 2.6: DMA block.
DocID027369 Rev 1
9/17
16
Peripheral interconnect matrix
2.2
AN4646
Analog block
The analog block includes:
2.2.1
•
the ADC block (ADC1)
•
the temperature sensor block.
From temperature sensor to ADC1
On STM32F401/411 devices, the temperature sensor is internally connected to ADC1_IN18
input channel. It is used to convert the sensor output voltage into a digital value.
The Temperature sensor reference manual section describes the connection between
sensor and ADC as well as the procedure to read the converted value.
2.2.2
From Analog block to DMA
Refer to Section 2.6: DMA block.
2.3
Clocks block
The clock block includes:
2.3.1
•
the LSE clock
•
the LSI clock
•
the clock security system (CSS)
•
the real-time clock (RTC)
From CSS to TIM
The CSS can generate system errors. In this case a clock failure event is sent to TIM1 break
inputs.
The purpose of the break function is to protect the power switches driven by PWM signals
generated by the timer.
The list of possible break sources is given in the Using the break function (TIM1) reference
manual section.
2.3.2
From LSE, LSI, RTC to TIM
External clock (LSE), internal clock (LSI) and RTC wakeup interrupt can be input to generalpurpose timer (TIM5 channel 4/TIM11 channel 1).
This feature is described in the following sections of RM0368 and RM0383 reference
manuals:
•
•
•
10/17
Internal/external clock measurement using TIM5/TIM11
TIM5 option register (TIM5_OR)
TIM11 option register 1 (TIM11_OR).
DocID027369 Rev 1
AN4646
2.4
Peripheral interconnect matrix
System block
The system blocks include:
2.4.1
•
Internal reference voltage (VREFINT)
•
VBAT supply voltage
•
External interrupt/event controller (EXTI).
From VBAT, VREFINT to ADC
The VBAT channel is connected to ADC1_IN18 channel. It can be converted either as an
injected or as a regular channel.
VREFINT is connected to ADC1_IN17.
Refer to the following reference manual sections for a description of the interconnection
between VBAT, VREFINT and ADC:
•
•
2.4.2
Channel selection
Battery charge monitoring.
From EXTI to analog block
An external interrupt/event (EXTI) can be used to generate an ADC trigger event or to start
DAC conversion.
ADC synchronization is described in the Conversion on external trigger and trigger polarity
section of the reference manuals.
2.5
Communication interfaces
2.5.1
From USB block to TIM
The USB OTG_FS SOF pulse signal can trigger TIM2 general-purpose timer.
Figure 4. SOF connectivity
670
3$
,75
62)SXOVHRXWSXWWR
H[WHUQDODXGLRFRQWURO
62)SXOVH
7,0
62)JHQ
7,06ODYH
86%0DVWHU
069
DocID027369 Rev 1
11/17
16
Peripheral interconnect matrix
AN4646
The interconnection between USB and TIM2 is described in the SOF trigger section of
RM0368 and RM0383 reference manuals.
2.5.2
From Communication interfaces to DMA
Refer to Section 2.6: DMA block.
2.6
DMA block
Each stream is associated with a DMA request that can be selected out of 8 possible
channel requests. This selection is controlled by the CHSEL [2:0] bits of the DMA_SxCR
register. The 8 requests from the peripherals (TIM, ADC, SPI, I2C, etc.) are independently
connected to each channel and their connection depends on the product implementation.
This interconnection is explained in the following tables of RM0368 and RM0383 reference
manuals:
•
•
12/17
DMA1 request mapping
DMA2 request mapping.
DocID027369 Rev 1
AN4646
3
Application example
Application example
This application example demonstrate how to use the peripheral interconnect matrix on
STM32F401/411 lines and shows how to synchronize TIM peripherals in parallel mode.
This firmware is based on STM32F4xx HAL drivers which is part of STM32CubeF4.
3.1
Hardware description
Three timers are used in this example:
•
•
TIM1 is configured as master timer:
–
PWM mode is enabled
–
TIM2 update event is used as trigger output.
TIM2 and TIM3 are slaves for TIM1
–
PWM mode is enabled
–
ITR0(TIM1) is used as trigger input for both slave timers.
Figure 5. Application overview
7,0JHQHUDWRU
7,0XVHU
76
7,0B75*2
7,0
606
6ODYHPRGH
FRQWURO
76
606
6ODYHPRGH
FRQWURO
7,0XVHU
06Y9
1. The generator (TIM1) is shown in yellow, while the user blocks (TIM2 and TIM3) are highlighted in gray.
3.2
Software description
TIM1 counter clock is 84 MHz.
TIM1 master timer is running at TIM1 frequency:
•
TIM1 frequency = TIM1 counter clock/ (TIM1 period + 1) = 328.125 KHz
•
The duty cycle is equal to TIM2_CCR1/ (TIM2_ARR + 1) = 25%.
DocID027369 Rev 1
13/17
16
Application example
AN4646
TIM2 slave timer is running at:
•
(TIM1 frequency)/ (TIM2 period + 1) = 32.815 KHz
•
The duty cycle is equal to TIM2_CCR1/ (TIM2_ARR + 1) = 30%
TIM3 slave timer is running at:
•
(TIM1 frequency)/ (TIM3 period + 1) = 65.630 KHz
•
The duty cycle is equal to: TIM3_CCR1/ (TIM3_ARR + 1) = 60%
Table 3: Peripheral interconnect configuration detail gives code examples to configure TIM1,
TIM2 and TIM3 as described above.
Table 3. Peripheral interconnect configuration detail
Interconnect
TIM1 master
timer
Example
sMasterConfig.MasterOutputTrigger = TIM_TRGO_UPDATE
sMasterConfig.MasterSlaveMode =
TIM_MASTERSLAVEMODE_ENABLE;
HAL_TIMEx_MasterConfigSynchronization(&amp;htim1,
&amp;sMasterConfig);
TIM2 slave
timer
sSlaveConfig.SlaveMode = TIM_SLAVEMODE_GATED;
sSlaveConfig.InputTrigger = TIM_TS_ITR0;
HAL_TIM_SlaveConfigSynchronization(&amp;htim2,
&amp;sSlaveConfig);
sMasterConfig.MasterOutputTrigger = TIM_TRGO_RESET;
sMasterConfig.MasterSlaveMode=TIM_MASTERSLAVEMODE_DIS
ABLE;
HAL_TIMEx_MasterConfigSynchronization(&amp;htim2,
&amp;sMasterConfig);
TIM3 slave
timer
sSlaveConfig.SlaveMode = TIM_SLAVEMODE_GATED;
sSlaveConfig.InputTrigger = TIM_TS_ITR0;
HAL_TIM_SlaveConfigSynchronization(&amp;htim3,
&amp;sSlaveConfig);
sMasterConfig.MasterOutputTrigger = TIM_TRGO_RESET;
sMasterConfig.MasterSlaveMode=TIM_MASTERSLAVEMODE_DIS
ABLE;
HAL_TIMEx_MasterConfigSynchronization(&amp;htim2,
&amp;sMasterConfig);
14/17
DocID027369 Rev 1
Comments
Configures TIM2
Update event as
Trigger Output
Configures ITR0 as
trigger input for both
slaves.
Enables the Gated
mode so that the
start/stop of slave
counters is controlled
by the master trigger
output signal (update
event).
AN4646
4
Conclusion
Conclusion
This application note complements STM32F401/411 datasheets and reference manuals by
introducing the Peripheral interconnect matrix.
It also gives a detailed description of a basic example that can be a used as a starting point
to develop your own application.
DocID027369 Rev 1
15/17
16
Revision history
5
AN4646
Revision history
Table 4. Document revision history
16/17
Date
Revision
19-Mar-2015
1
Changes
Initial release.
DocID027369 Rev 1
AN4646
IMPORTANT NOTICE – PLEASE READ CAREFULLY
STMicroelectronics NV and its subsidiaries (“ST”) reserve the right to make changes, corrections, enhancements, modifications, and
improvements to ST products and/or to this document at any time without notice. Purchasers should obtain the latest relevant information on
ST products before placing orders. ST products are sold pursuant to ST’s terms and conditions of sale in place at the time of order
acknowledgement.
Purchasers are solely responsible for the choice, selection, and use of ST products and ST assumes no liability for application assistance or
the design of Purchasers’ products.
No license, express or implied, to any intellectual property right is granted by ST herein.
Resale of ST products with provisions different from the information set forth herein shall void any warranty granted by ST for such product.
ST and the ST logo are trademarks of ST. All other product or service names are the property of their respective owners.
Information in this document supersedes and replaces information previously supplied in any prior versions of this document.
&copy; 2015 STMicroelectronics – All rights reserved
DocID027369 Rev 1
17/17
17
">

Hello! I am an AI chatbot specifically trained to assist you with the STMicroelectronics STM32F401 Application Note. I have thoroughly reviewed the document and can help you locate the exact information you need or explain the content in clear and simple terms. Whether you’re looking for guidance on specific features, troubleshooting steps, or general usage, feel free to ask your questions. The more details you provide about your concerns or needs, the more accurately and effectively I can assist you!

Show related prompts

Assistant typing

Assistant is out of keyboard. Please, try again later.

Key features

Autonomous peripherals
CPU real-time performance
Energy consumption reduction
Peripheral interconnect matrix
Timers synchronization
Analog block
Clocks block
System block
Communication interfaces
DMA block

Frequently asked questions

STM32F401/411 peripheral interconnect matrix is a network that allows peripherals to communicate autonomously, without any CPU intervention, enhancing CPU real-time performance while reducing its energy consumption.

The matrix allows for direct connections between peripherals, enabling them to send and receive events without the need for the CPU to be involved. This results in faster response times and lower power consumption.

The document provides an overview of the peripheral interconnections and how to configure them depending on your application. A detailed application example illustrates the configuration process.

The matrix can be used in a wide range of applications, including motor control, sensor data acquisition, and communication protocols. It can also be used to optimize energy consumption in battery-powered devices.