Difference between revisions of "SYSCFG internal peripheral"

[quality revision] [quality revision]
m
 
 
Template:ArticleMainWriter Template:ArticleApprovedVersion

1 Article purpose[edit]

The purpose of this article is to:

  • briefly introduce the SYSCFG peripheral and its main features
  • indicate the level of security supported by this hardware block
  • explain how it can be allocated to the three runtime contexts and linked to the corresponding software components
  • explain, when necessary, how to configure the SYSCFG peripheral.

2 Peripheral overview[edit]

The SYSCFG peripheral is used to configure various system aspects like IOs compensation, Ethernet clocking path, …

2.1 Features[edit]

Refer to the STM32MP15 reference manuals for the complete list of features, and to the software components, introduced below, to see which features are really implemented in ST software.

2.2 Security support[edit]

The SYSCFG is a non secure peripheral.

3 Peripheral usage and associated software[edit]

3.1 Boot time[edit]

The SYSCFG peripheral is configured by TF-A and U-Boot at boot time.

3.2 Runtime[edit]

3.2.1 Overview[edit]

Linux and STM32Cube can directly change the SYSCFG at runtime from various drivers.

For instance, I2C fast mode plus (FM+) can be enabled for each instance in the SYSCFG so:

3.2.2 Software frameworks[edit]

Domain Peripheral Software frameworks Comment
Cortex-A7
secure
(OP-TEE)
Cortex-A7
non-secure
(Linux)
Cortex-M4

(STM32Cube)
Core SYSCFG Linux syscon framework[1] STM32Cube SYSCFG driver

3.2.3 Peripheral configuration[edit]

The configuration is applied by the firmware running in the context to which the peripheral is assigned. The configuration can be done alone via the STM32CubeMX tool for all internal peripherals, and then manually completed (particularly for external peripherals), according to the information given in the corresponding software framework article.

3.2.4 Peripheral assignment[edit]

Internal peripherals

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)
Core SYSCFG SYSCFG

4 References[edit]


<noinclude>

{{ArticleBasedOnModel | [[Internal peripheral article model]]}}
{{ArticleMainWriter | GeraldB}}
{{ArticleApprovedVersion | GeraldB | AlexandreT | No previous approved version | AlainF - 17Oct'18 - 9289 | 22'May18}}
[[Category:Core peripherals]]</noinclude>

==Article purpose==
The purpose of this article is to:
* briefly introduce the SYSCFG peripheral and its main features
* indicate the level of security supported by this hardware block
* explain how it can be allocated to the three runtime contexts and linked to the corresponding software components
* explain, when necessary, how to configure the SYSCFG peripheral.

==Peripheral overview==
The '''SYSCFG''' peripheral is used to configure various system aspects like IOs compensation, Ethernet clocking path, …

===Features===
Refer to the [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]] for the complete list of features, and to the software components, introduced below, to see which features are really implemented in ST software.

===Security support===
The SYSCFG is a '''non secure''' peripheral.

==Peripheral usage and associated software==
===Boot time===
The SYSCFG peripheral is configured by [[TF-A overview|TF-A]] and [[U-Boot overview|U-Boot]] at boot time.

===Runtime===
====Overview====
[[STM32MP15 Linux kernel overview|Linux]] and [[STM32CubeMP1 architecture|STM32Cube]] can directly change the SYSCFG at runtime from various drivers.<br />


For instance, I2C fast mode plus (FM+) can be enabled for each instance in the SYSCFG so:
* [[I2C overview|Linux I2C driver]] uses syscon <ref name="syscon">{{CodeSource | Linux kernel | Documentation/devicetree/bindings/mfd/syscon.txt}}</ref> to enable this mode in the SYSCFG for the instances allocated to itself
* [[STM32CubeMP1 architecture|STM32Cube I2C HAL driver]] uses its [[STM32CubeMP1 architecture|SYSCFG HAL driver]] to do the same on the instances allocated to itself

====Software frameworks====
{{:Internal_peripherals_software_table_template}}
 | Core
 | [[SYSCFG_internal_peripheral|SYSCFG]]
 | 
 | Linux syscon framework<ref name="syscon"/>

 | [[STM32CubeMP1 architecture|STM32Cube SYSCFG driver]]
 |
 |-
 |}

====Peripheral configuration====
The configuration is applied by the firmware running in the context to which the peripheral is assigned. The configuration can be done alone via the [[STM32CubeMX]] tool for all internal peripherals, and then manually completed (particularly for external peripherals), according to the information given in the corresponding software framework article.

====Peripheral assignment====
{{:Internal_peripherals_assignment_table_template}}<onlyinclude>

 | rowspan="1" | Core
 | rowspan="1" | [[SYSCFG_internal_peripheral|SYSCFG]]
 | SYSCFG
 | 
 | <span title="system peripheral" style="font-size:21px"></span>

 | <span title="system peripheral" style="font-size:21px"></span>

 |
 |-</onlyinclude>

 |}

==References==<references/>

<noinclude>

[[Category:Core peripherals]]
{{PublicationRequestId | 9289 | 2018-10-17 | AlainF}}
{{ArticleBasedOnModel | Internal peripheral article model}}</noinclude>
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
<noinclude>
 
{{ArticleBasedOnModel | [[Internal peripheral article model]]}}
 
{{ArticleMainWriter | GeraldB}}
 
{{ArticleApprovedVersion | GeraldB | AlexandreT | No previous approved version | AlainF - 17Oct'18 - 9289 | 22'May18}}
 
[[Category:Core peripherals]]
 
</noinclude>
 
 
 
==Article purpose==
 
==Article purpose==
 
The purpose of this article is to:
 
The purpose of this article is to:
Line 24: Line 17:
 
==Peripheral usage and associated software==
 
==Peripheral usage and associated software==
 
===Boot time===
 
===Boot time===
The SYSCFG peripheral is configured by [[U-Boot overview|U-Boot]] at boot time.
+
The SYSCFG peripheral is configured by [[TF-A overview|TF-A]] and [[U-Boot overview|U-Boot]] at boot time.
   
 
===Runtime===
 
===Runtime===
Line 64: Line 57:
 
==References==
 
==References==
 
<references/>
 
<references/>
  +
  +
<noinclude>
  +
[[Category:Core peripherals]]
  +
{{PublicationRequestId | 9289 | 2018-10-17 | AlainF}}
  +
{{ArticleBasedOnModel | Internal peripheral article model}}
  +
</noinclude>

Attachments

Discussions