HDP internal peripheral

Revision as of 15:05, 15 February 2019 by Gerald Baeza (talk | contribs)

Template:ArticleMainWriter Template:ArticleApprovedVersion

1 Article purpose[edit]

The purpose of this article is to

  • briefly introduce the HDP peripheral (hardware debug port) and its main features
  • indicate the level of security supported by this hardware block
  • explain how each instance can be allocated to the three runtime contexts and linked to the corresponding software components
  • explain, when needed, how to configure the HDP peripheral.

2 Peripheral overview[edit]

The HDP peripheral is used to output some internal signals on up to 8 GPIO pins.

Follow the sequence below to connect a GPIO to an internal signal via the HDP:

  • First of all, look for the internal signal you want to monitor in the HDP signal multiplexing table of the STM32MP15 reference manuals:
    • Search for the HDP signal on which you can get it among eight possible choices.
    • Note the corresponding HDPx multiplexing value to select.
  • Then, look for the most suitable GPIO pin on which you can output HDPx in the data brief:
    • Note the GPIO bank and pin.
    • Note the corresponding GPIO alternate function (AF) to select.

The GPIO bank, pin, alternate function and HDPx multiplexing value are the information required to configure each HDP signal.

2.1 Features[edit]

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

2.2 Security support[edit]

The HDP is a non-secure peripheral.

3 Peripheral usage and associated software[edit]

3.1 Boot time[edit]

The HDP is not used at boot time.

3.2 Runtime[edit]

3.2.1 Overview[edit]

The HDP can be allocated to the Arm® Cortex®-A7 non-secure core to be used under Linux®HDP driver.

3.2.2 Software frameworks[edit]

Internal peripherals software table template

| Trace & Debug
| HDP Linux 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 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.

3.2.4 Peripheral assignment[edit]

Internal peripherals assignment table template

| rowspan="1" | Trace & Debug
| rowspan="1" | HDP