Registered User mNo edit summary |
Registered User m (Undo revision 90926 by Registered User (-)) Tag: Undo |
||
(14 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
<noinclude>{{ApplicableFor | <noinclude>{{ApplicableFor | ||
|MPUs list=STM32MP15x | |MPUs list=STM32MP13x,STM32MP15x | ||
|MPUs checklist=STM32MP13x, STM32MP15x | |MPUs checklist=STM32MP13x, STM32MP15x | ||
}}</noinclude> | }}</noinclude> | ||
Line 17: | Line 17: | ||
===Features=== | ===Features=== | ||
The '''DFSDM''' peripheral provides several features, among which: | The '''DFSDM''' peripheral provides several features, among which: | ||
* | |||
* | * Serial or parallel input '''channels''': | ||
* | ** External analog frontend serial interfaces (SPI, manchester coded single wire interface, clock output), for various sigma-delta modulators | ||
** Alternative Internal digital parallel interfaces (from internal ADC<ref name="ADC internal peripheral">[[ADC internal peripheral]]</ref> or memory data stream via DMA<ref name="DMA internal peripheral">[[DMA internal peripheral]]</ref> or CPU) | |||
* Digital '''filters''', that offers up to 24-bit final ADC resolution | |||
* Conversions that can be launched continuously, or using various triggers: by software, TIM<ref name="TIM internal peripheral">[[TIM internal peripheral]]</ref>, LPTIM<ref name="LPTIM internal peripheral">[[LPTIM internal peripheral]]</ref>, EXTI<ref name="EXTI internal peripheral">[[EXTI internal peripheral]]</ref> or synchronously with DFSDM filter 0 | * Conversions that can be launched continuously, or using various triggers: by software, TIM<ref name="TIM internal peripheral">[[TIM internal peripheral]]</ref>, LPTIM<ref name="LPTIM internal peripheral">[[LPTIM internal peripheral]]</ref>, EXTI<ref name="EXTI internal peripheral">[[EXTI internal peripheral]]</ref> or synchronously with DFSDM filter 0 | ||
* Event detectors: analog watchdog high/low thresholds, short-circuit detector, extremes detector | * Event detectors: analog watchdog high/low thresholds, short-circuit detector, extremes detector | ||
* Break generation to TIM<ref name="TIM internal peripheral"/> on analog watchdog or short-circuit detector events | * Break generation to TIM<ref name="TIM internal peripheral"/> on analog watchdog or short-circuit detector events | ||
Refer to [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]] for the complete features list, and to the software components, introduced below, to know which features are really implemented. | |||
{| class="st-table" style="width: 100%;" | |||
|- style="background: {{STLightGrey}};" | |||
! style="width:40%; | DFSDM features | |||
! style="width:20%; | Number of channels | |||
! style="width:20%;" | Number of filters | |||
|- | |||
| {{MicroprocessorDevice | device=13}} | |||
| 4 | |||
| 2 | |||
|- | |||
| {{MicroprocessorDevice | device=15}} | |||
| 8 | |||
| 6 | |||
|- | |||
|} | |||
Refer to [[STM32MP13 resources#Reference manuals|STM32MP13 reference manuals]] or [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]] for the complete features list, and to the software components, introduced below, to know which features are really implemented. | |||
===Security support=== | ===Security support=== | ||
Line 37: | Line 56: | ||
* the Arm<sup>®</sup> Cortex<sup>®</sup>-A7 non-secure core to be used under Linux<sup>®</sup> by the [[IIO overview|IIO]] or [[ALSA overview|ALSA]] framework | * the Arm<sup>®</sup> Cortex<sup>®</sup>-A7 non-secure core to be used under Linux<sup>®</sup> by the [[IIO overview|IIO]] or [[ALSA overview|ALSA]] framework | ||
or | or | ||
* the Arm<sup>®</sup> Cortex<sup>®</sup>-M4 for using in STM32Cube by [[STM32CubeMP1 architecture|STM32Cube DFSDM driver]]. | * the Arm<sup>®</sup> Cortex<sup>®</sup>-M4 for using in STM32Cube by [[STM32CubeMP1 architecture|STM32Cube DFSDM driver]] (on {{MicroprocessorDevice | device=15}}). | ||
The [[#Peripheral assignment|peripheral assignment]] chapter describes which peripheral instance can be assigned to which context. | The [[#Peripheral assignment|peripheral assignment]] chapter describes which peripheral instance can be assigned to which context. | ||
====Software frameworks==== | ====Software frameworks==== | ||
===== On {{MicroprocessorDevice | device=13}} ===== | |||
{{:STM32MP13_internal_peripherals_software_table_template}} | |||
| Analog | |||
| [[DFSDM internal peripheral|DFSDM]] | |||
| | |||
| [[IIO overview|Linux IIO framework]]<br>[[ALSA overview|Linux ALSA framework]] | |||
| | |||
|- | |||
|} | |||
===== On {{MicroprocessorDevice | device=15}} ===== | |||
{{:STM32MP15_internal_peripherals_software_table_template}} | {{:STM32MP15_internal_peripherals_software_table_template}} | ||
| Analog | | Analog | ||
| [[ | | [[DFSDM internal peripheral|DFSDM]] | ||
| | | | ||
| [[IIO overview|Linux IIO framework]]<br>[[ALSA overview|Linux ALSA framework]] | | [[IIO overview|Linux IIO framework]]<br>[[ALSA overview|Linux ALSA framework]] | ||
Line 58: | Line 88: | ||
====Peripheral assignment==== | ====Peripheral assignment==== | ||
===== On {{MicroprocessorDevice | device=13}} ===== | |||
{{:STM32MP13_internal_peripherals_assignment_table_template}} | |||
<section begin=stm32mp13 /> | |||
| rowspan="1" | Analog | |||
| rowspan="1" | [[DFSDM internal peripheral|DFSDM]] | |||
| DFSDM | |||
| | |||
| <span title="assignable peripheral" style="font-size:21px">☐</span> | |||
| Assignment (single choice) | |||
|- | |||
<section end=stm32mp13 /> | |||
|} | |||
===== On {{MicroprocessorDevice | device=15}} ===== | |||
{{:STM32MP15_internal_peripherals_assignment_table_template}} | {{:STM32MP15_internal_peripherals_assignment_table_template}} | ||
< | <section begin=stm32mp15 /> | ||
| rowspan="1" | Analog | | rowspan="1" | Analog | ||
| rowspan="1" | [[ | | rowspan="1" | [[DFSDM internal peripheral|DFSDM]] | ||
| DFSDM | | DFSDM | ||
| | | | ||
Line 68: | Line 112: | ||
| Assignment (single choice) | | Assignment (single choice) | ||
|- | |- | ||
</ | <section end=stm32mp15 /> | ||
|} | |} | ||
Line 81: | Line 125: | ||
<noinclude> | <noinclude> | ||
[[Category:Analog peripherals | [[Category:Analog peripherals]] | ||
[[Category:Audio peripherals | [[Category:Audio peripherals]] | ||
{{PublicationRequestId | 8311 | 2018-08-07 | AlainF}} | {{PublicationRequestId | 8311 | 2018-08-07 | AlainF}} | ||
{{ArticleBasedOnModel| Internal peripheral article model}} | {{ArticleBasedOnModel| Internal peripheral article model}} |
Latest revision as of 12:28, 2 March 2023
1. Article purpose[edit source]
The purpose of this article is to
- briefly introduce the DFSDM peripheral and its main features
- indicate the level of security supported by this hardware block
- explain how each instance can be allocated to the runtime contexts and linked to the corresponding software components
- explain, when needed, how to configure the DFSDM peripheral.
2. Peripheral overview[edit source]
The DFSDM peripheral (Digital Filter for Sigma-Delta Modulator) is used as a generic ADC. It benefits from external analog frontend interfaces and internal digital filters.
It can be used in various applications[1] such as: audio record with MEMS microphones, energy measurement with STPMS2[2] for electricity meters or motor control...
2.1. Features[edit source]
The DFSDM peripheral provides several features, among which:
- Serial or parallel input channels:
- Digital filters, that offers up to 24-bit final ADC resolution
- Conversions that can be launched continuously, or using various triggers: by software, TIM[5], LPTIM[6], EXTI[7] or synchronously with DFSDM filter 0
- Event detectors: analog watchdog high/low thresholds, short-circuit detector, extremes detector
- Break generation to TIM[5] on analog watchdog or short-circuit detector events
Refer to STM32MP13 reference manuals or STM32MP15 reference manuals for the complete features list, and to the software components, introduced below, to know which features are really implemented.
2.2. Security support[edit source]
The DFSDM is a non-secure peripheral.
3. Peripheral usage and associated software[edit source]
3.1. Boot time[edit source]
The DFSDM is not used at boot time.
3.2. Runtime[edit source]
3.2.1. Overview[edit source]
The DFSDM can be allocated to:
or
- the Arm® Cortex®-M4 for using in STM32Cube by STM32Cube DFSDM driver (on STM32MP15x lines
).
The peripheral assignment chapter describes which peripheral instance can be assigned to which context.
3.2.2. Software frameworks[edit source]
3.2.2.1. On STM32MP13x lines
[edit source]
Domain | Peripheral | Software components | Comment | |
---|---|---|---|---|
OP-TEE | Linux | |||
Analog | DFSDM | Linux IIO framework Linux ALSA framework |
3.2.2.2. On STM32MP15x lines
[edit source]
Domain | Peripheral | Software components | Comment | ||
---|---|---|---|---|---|
OP-TEE | Linux | STM32Cube | |||
Analog | DFSDM | Linux IIO framework Linux ALSA framework |
STM32Cube DFSDM driver |
3.2.3. Peripheral configuration[edit source]
The configuration is applied by the firmware running in the context to which the peripheral is assigned. The configuration by itself can be performed via the STM32CubeMX tool for all internal peripherals. It can then be manually completed (especially for external peripherals) according to the information given in the corresponding software framework article.
For the Linux kernel configuration, please refer to DFSDM device tree configuration and DFSDM Linux driver articles.
3.2.4. Peripheral assignment[edit source]
3.2.4.1. On STM32MP13x lines
[edit source]
Click on the right to expand the legend...
Check boxes illustrate the possible peripheral allocations supported by STM32 MPU Embedded Software:
- ☐ means that the peripheral can be assigned (☑) to the given runtime context.
- ⬚ means that the peripheral can be assigned to the given runtime context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
- ✓ is used for system peripherals that cannot be unchecked because they are statically connected in the device.
Refer to How to assign an internal peripheral to a runtime context for more information on how to assign peripherals manually or via STM32CubeMX.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possiblities might be described in STM32MP13 reference manuals.
Domain | Peripheral | Runtime allocation | Comment | ||
---|---|---|---|---|---|
Instance | Cortex-A7 secure (OP-TEE) |
Cortex-A7 non-secure (Linux) | |||
Analog | DFSDM | DFSDM | ☐ | Assignment (single choice) |
3.2.4.2. On STM32MP15x lines
[edit source]
Check boxes illustrate the possible peripheral allocations supported by STM32 MPU Embedded Software:
- ☐ means that the peripheral can be assigned (☑) to the given runtime context.
- ✓ is used for system peripherals that cannot be unchecked because they are statically connected in the device.
Refer to How to assign an internal peripheral to a runtime context for more information on how to assign peripherals manually or via STM32CubeMX.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possiblities might be described in STM32MP15 reference manuals.
Domain | Peripheral | Runtime allocation | Comment | |||
---|---|---|---|---|---|---|
Instance | Cortex-A7 secure (OP-TEE) |
Cortex-A7 non-secure (Linux) |
Cortex-M4 (STM32Cube) | |||
Analog | DFSDM | DFSDM | ☐ | ☐ | Assignment (single choice) |
4. How to go further[edit source]
See:
- STM32L4 System Digital Filter for SD Modulators interface[1], online DFSDM training with application examples from STMicroelectronics
- Getting started with sigma-delta digital interface[8], application note from STMicroelectronics
5. References[edit source]
- ↑ Jump up to: 1.0 1.1 STM32L4 System Digital Filter for SD Modulators interface, online DFSDM training from STMicroelectronics
- ↑ STPMS2 "Smart sensor" device
- ↑ ADC internal peripheral
- ↑ DMA internal peripheral
- ↑ Jump up to: 5.0 5.1 TIM internal peripheral
- ↑ LPTIM internal peripheral
- ↑ EXTI internal peripheral
- ↑ Getting started with sigma-delta digital interface, application note from STMicroelectronics