1. Article purpose[edit source]
This article explains how to configure the HASH using the device tree mechanism (DT), relying on the bindings documentation, which is the description of the required and optional device tree properties.
The peripheral can be assigned to different contexts and software components, depending on the final product needs. Refer to How to assign an internal peripheral to a runtime context article for guidelines on this configuration.
2. DT bindings documentation[edit source]
The device tree bindings documents are stored either in the given applicable components listed below, or in the Linux® kernel repository:
- OP-TEE, Linux® Kernel:
- HASH device tree bindings: Documentation/devicetree/bindings/crypto/st,stm32-hash.yaml
3. DT configuration[edit source]
This hardware description is a combination of the STM32 microprocessor device tree files (.dtsi extension) and board device tree files (.dts extension). See the Device tree for an explanation of the device tree file organization.
STM32CubeMX can be used to generate the board device tree. Refer to How to configure the DT using STM32CubeMX for more details.
3.1. DT configuration (STM32/SoC level)[edit source]
The HASH node is located in the device tree file for the software components, supporting the peripheral and listed in the above DT bindings documentation paragraph.
3.2. DT configuration (board level)[edit source]
This chapter explains how to enable and configure the HASH DT nodes for a board.
The peripheral configuration must be done in the specific board device tree files (board dts file).
3.3. DT configuration examples[edit source]
&hash {
status = "okay";
};
4. How to configure the DT using STM32CubeMX[edit source]
The STM32CubeMX tool can be used to configure the STM32MPU device and get the corresponding platform configuration device tree files.
STM32CubeMX might not support all the properties described in the DT binding files listed in the above DT bindings documentation paragraph. In such cases, the tool inserts user sections in the generated device tree. These sections can then be edited to add some properties; They are preserved from one generation to another. Refer to STM32CubeMX user manual for further information.