The STM32MP135 Discovery kit (STM32MP135F-DK) is designed as a complete demonstration and development platform for
the STMicroelectronics Arm®-based single Cortex®‑A7 32-bit STM32MP135 microcontrollers and their STPMIC1 companion
chip. It leverages the capabilities of the 1 GHz STM32MP135 microprocessors to allow users to develop easily applications
using STM32 MPU OpenSTLinux Distribution software (such as STM32MP1Starter).
It features 16-bit DDR3L 4 Gbits at 533 MHz, MIPI CSI-2® bridge with dual lanes up to 1.6 Gbit/s, USB Type-C® DRP port, USB
Type-A Host HS ports, microSD™ card high-speed mode up to 50 MHz, dual 10/100 Mbit/s Ethernet, 40-pin extended GPIOs,
Wi‑Fi® 802.11b/g/n, Bluetooth® Low Energy 4.1, and STLINK-V3E (UART console).
The STM32MP135F-DK, shown in Figure 1 and Figure 2, is used as a reference design for the user application development. It
cannot be considered as the hardware design of a final application.
The hardware features of the Discovery kit are available for users to develop their applications: USB, dual Ethernet, LCD,
microSD™ card, user buttons, Wi‑Fi®, Bluetooth® Low Energy, and a 2-megapixel CMOS camera module. Extension headers
allow the easy connection of a third-party board for a specific application.
An STLINK-V3E is integrated on the board, as an embedded in-circuit debugger and programmer for the STM32 MPU and the
USB Virtual COM port bridge.
Figure 1. STM32MP135F-DK top view
DT71719V1
Pictures are not contractual.
Figure 2. STM32MP135F-DK bottom view
DT71720V1
UM2993 - Rev 2 - March 2023
For further information contact your local STMicroelectronics sales office.
www.st.com
1Features
•STM32MP135FAF7 MPU with an Arm® Cortex®‑A7 32-bit processor at 1 GHz, in a TFBGA320 package
•ST PMIC STPMIC1
•4-Gbit DDR3L, 16 bits, 533 MHz
•4.3" 480×272 pixels LCD display module with capacitive touch panel and RGB interface
•UXGA 2-megapixel CMOS camera module (included) with MIPI CSI-2® / SMIA CCP2 deserializer
•Wi‑Fi® 802.11b/g/n
•Bluetooth® Low Energy 4.1
•Dual 10/100 Mbit/s Ethernet (RMII) compliant with IEEE-802.3u, one with Wake on LAN (WoL) support
•USB Host 4-port hub
•
USB Type-C® DRP based on an STM32G0 device
•4 user LEDs
•4 push-buttons (2× user, tamper, and reset)
•1 wake-up button
•Board connectors:
–
Dual-lane MIPI CSI-2® camera module expansion
–2× Ethernet RJ45
–4× USB Type-A
–USB Micro-B
–USB Type-C
–microSD™ card holder
–GPIO expansion
–5 V / 3 A USB Type-C® power supply input (charger not provided)
–VBAT for power backup
•On-board current measurement
•On-board STLINK-V3E debugger/programmer with USB re-enumeration capability: mass storage, Virtual
COM port, and debug port
•Full mainline open-source Linux® STM32 MPU OpenSTLinux Distribution (such as STM32MP1Starter)
software and examples
•Support of several Integrated Development Environments (IDEs) including STM32CubeIDE
•Bare metal support for RTOS (Microsoft® Azure®)
Note:Arm is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere.
®
UM2993
Features
UM2993 - Rev 2
page 2/42
2Ordering information
To order the STM32MP135 Discovery kit, refer to Table 1. Additional information is available from the datasheet
and reference manual of the target STM32.
Order codeBoard referenceTarget STM32
STM32MP135F-DK
1. Main board.
2. Camera module board.
2.1Codification
The meaning of the codification is explained in Table 2.
Table 1. List of available products
•MB1635
•MB1897
(1)
(2)
Table 2. Codification explanation
UM2993
Ordering information
STM32MP135FAF7
STM32TTTXXY-ZZDescriptionExample: STM32MP135F-DK
STM32TTTMPU series in STM32 Arm Cortex MPUsSTM32MP1 series
XXMPU product line in the seriesSTM32MP135
ZZ
Options:
Y
•F: Secure boot, cryptography hardware, 1 GHz
frequency
Toolkit configuration:
•DK: Discovery kit with LCD, Wi‑Fi®, and Bluetooth® Low
Energy
Secure boot, cryptography hardware,
1 GHz frequency
LCD, Wi‑Fi®, and Bluetooth® Low
Energy
UM2993 - Rev 2
page 3/42
3Development environment
3.1System requirements
•Multi‑OS support: Windows® 10, Linux® 64-bit, or macOS
•USB Type-C® to USB Type-C® charger 5 V / 3 A
•USB Type-A or USB Type-C® to USB Type-C® cable
•USB Type-A or USB Type-C® to Micro-B cable
Note:
3.2Development toolchains
macOS® is a trademark of Apple Inc., registered in the U.S. and other countries and regions.
Linux® is a registered trademark of Linus Torvalds.
Windows is a trademark of the Microsoft group of companies.
•STMicroelectronics - STM32CubeIDE
•GCC-based IDEs
UM2993
Development environment
®
3.3Demonstration software
The STM32 MPU OpenSTLinux Distribution base demonstration software is preloaded in the microSD™ for easy
demonstration of the device peripherals in standalone mode. The latest versions of the demonstration source
code and associated documentation can be downloaded from www.st.com.
UM2993 - Rev 2
page 4/42
4Conventions
Table 3 provides the conventions used for the ON and OFF settings in the present document.
Resistor Rx ONResistor soldered
Resistor Rx OFFResistor not soldered
UM2993
Conventions
Table 3. ON/OFF convention
ConventionDefinition
UM2993 - Rev 2
page 5/42
5Safety recommendations
5.1Targeted audience
This product targets users with at least basic electronics or embedded software development knowledge like
engineers, technicians, or students.
This board is not a toy and is not suited for use by children.
UM2993
Safety recommendations
5.2
Handling the board
This product contains a bare printed circuit board. As for all products of this type, the user must be careful about
the following points:
•The connection pins on the board might be sharp. Handle the board carefully to avoid getting hurt.
•This board contains static-sensitive devices. To avoid damaging it, handle the board in an ESD-proof
environment.
•While powered, do not to touch the electric connections on the board with fingers or anything conductive.
The board operates at voltage levels that are not dangerous, but some components might be damaged
when shorted.
•Do not put any liquid on the board; avoid operating it close to water or at high humidity level.
•Do not operate the board if it is dirty or dusty.
5.3Battery
This product does not include a battery.
5.4
5.5
Laser
This product does not include a laser.
Power supply
This product is not delivered with a power supply.
The equipment must be powered by a power supply unit or an auxiliary equipment complying with the standard
EN 60950-1 (2006+A11/2009+A1/2010+A12/2011+A2/2013) / EN 62368-1 (2014+A11/2017), which must be
Safety Extra Low Voltage (SELV/ES1) with limited power capability (LPS/PS2).
UM2993 - Rev 2
page 6/42
6Quick start
This chapter describes how to start a development quickly using the STM32MP135F-DK.
Before installing and using the product, accept the evaluation product license agreement from the www.st.com/
epla webpage.
Before the first use, make sure that no damage occurred to the product during shipment and check that:
•All socketed components are firmly secured in their sockets
•Nothing is loose in the board plastic bag or in the box
The STM32MP135 Discovery kit is a low-cost and easy-to-use development kit to quickly evaluate and start a
development with an STM32MP135 microprocessor in a TFBGA320 package.
To start using the STM32MP135F-DK, follow the steps below:
1.Check the boot mode switch positions on the board, as shown in Table 5.
2.For a correct identification among the host PC device interfaces, before connecting the board, install the
USB driver available on the www.st.com website.
3.
To power the board, connect its USB Type-C® connector CN12 to a 5 V / 3 A USB Type-C® charger with its
cable. As a result, the green LED LD1 (5 V PWR LED) and the blue LED LD3 light up, and the LED LD5
(ST-LINK LED) blinks.
4.The software demonstration and the several software examples that allow the user to use the Discovery kit
features are available at the www.st.com/stm32mp1 webpage.
5.Develop an application using the available examples.
UM2993
Quick start
UM2993 - Rev 2
page 7/42
7Hardware layout and configuration
7.1Hardware layout
The STM32MP135F-DK is designed around the STM32MP135FAF7 microprocessor (320 pins in a TFBGA
package). The hardware block diagram (see Figure 3) illustrates the connection between the STM32MP135FAF7
microprocessor and the peripherals (such as dual Ethernet, MIPI CSI-2® camera module connector, USB TypeC® DRP and USB Type-A connectors, GPIO expansion, and embedded ST-LINK).
Figure 3. STM32MP135F-DK hardware block diagram
UM2993
Hardware layout and configuration
32 kHz crystal
24 MHz crystal
DDR3L
4.3" TFT 480×272
Capacitive
touch panel
Hub: 4× USB Type-A
USB OTG Type-C
16-bit I/O expander
®
STM32MP135F
RTC
HSI
DDR
LTDC
I2C
USB
HOST HS
USB
OTG HS
I2C
USB Type-C
connector
I2CSTPMIC1
Wake-up button
2 user LEDs
GPIO
DCMI
SDMMC
2 user buttons
Tamper button
Reset button
MIPI CSI-2
Camera module
microSD™ card
connector
5V_VIN
®
®
bridge
UM2993 - Rev 2
Ethernet 1
Ethernet 2
STLINK-V3E
USB Micro-B
RMII
RMII
JTAG/
SWD
SDMMC
UART
GPIOs
®
Wi-Fi
802.11 b/g/n
Bluetooth
energy V4.1
GPIO 40-pin
connector
®
low
DT71708V1
page 8/42
Figure 4 and Figure 5 show the locations of these features on the STM32MP135F-DK.
Figure 4. STM32MP135F-DK PCB layout: top side
UM2993
Hardware layout
ST-LINK USB
(CN10)
ST-LINK LED
(LD5)
User LED
(LD7)
40-pin connector
(CN8)
User button 1
(B1)
User LED
(LD3)
User LED
(LD4)
User button 2
(B2)
4.3" LCD display
(U35)
VBAT
(CN11)
5 V power in
(LD1)
Wake up
(B3)
Reset
(B5)
(LD6)
Tamper
(B4)
User
LED
Boot mode
(SW1)
Power measurement
(CN14)
DT71709V1
UM2993 - Rev 2
page 9/42
CSI connector
(CN1)
Figure 5. STM32MP135F-DK PCB layout: bottom side
STMIPID02
de-serializer
(U2)
LCD backlight power supply
(U9)
UM2993
Hardware layout
®
Wi-Fi
/ BLE
(U1)
Ethernet 2
(CN15)
Ethernet 2 PHY
(U7)
Ethernet 1 PHY
(U13)
Ethernet 1
(CN4)
5 V power in
(CN12)
STPMIC1
(U19)
USB hub
(U33)
STM32MP135
(U14)
USB Host
(CN5)
USB Host
(CN6)
USB Type-C
(CN7)
®
microSD™
card
(CN3)
STM32
ST-LINK
(U12)
DDR3L
(U17)
STM32G0
(U21)
DRP
DT71710V1
UM2993 - Rev 2
page 10/42
Hardware configuration
7.2Hardware configuration
7.2.1Ethernet configuration
The board embeds dual 10/100 MBit/s Ethernet ports, Ethernet 1 and Ethernet 2, with one featuring Wake on LAN
(WoL).
The WoL feature is configured by default and is only available for the Ethernet 1 port. The Ethernet reference
clock must be taken from the crystal X3 and the resistor R107 must be OFF.
If the WoL feature is not needed, the reference clock can be directly taken from the MPU pin PA11 by having
resistor R107 ON, and resistors R105 and R106 OFF.
7.2.2VBAT configuration
The VBAT feature is available to maintain critical operations when a power loss occurs on VDD. In the default
configuration with the resistor R192 ON and the resistor R191 OFF, theVBAT feature is not available.
To enable the VBAT mode, swap the resistors R192 and R191, and connect a backup power source to the VBAT
connector.
7.2.3STLINK-V3E configuration
The embedded STLINK-V3, STLINK-V3E, proposes only the SWD interface.
Restriction:The STLINK_JTDI signal is shared with the μSD_DETECT signal. It is reserved for internal use only.
UM2993
7.3Embedded STLINK-V3E
7.3.1Description
To debug the on-board STM32 MPU, the STLINK-V3E programming and debugging tool is integrated in the
STM32MP135F-DK Discovery kit. The embedded STLINK-V3E supports only SWD and VCP for STM32 devices.
For information about the debugging and programming features of STLINK-V3E, refer to the ST-LINK in-circuitdebugger/programmer for STM8 and STM32 user manual (UM1075) and Overview of ST-LINK derivatives
technical note (TN1235).
It is recommended to power the board (CN12, 5 V power in connector, PWR_IN) before plugging the USB debug
cable to the Micro-B connector.
7.3.2Drivers
Before connecting STM32MP135F-DK to a Windows® (7, 8, or 10) PC via the USB, a driver for STLINK-V3 must
be installed (not required for Windows® 10). It is available from the www.st.com website.
In cases where the STM32MP135F-DK Discovery kit is connected to the PC before the driver is installed, some
STM32MP135F-DK interfaces may be declared as “Unknown” in the PC device manager. In this case, the user
must install the dedicated driver files, and update the driver of the connected device from the device manager.
7.3.3STLINK-V3 firmware upgrade
The STLINK-V3 embeds a firmware upgrade mechanism for in place upgrade through the USB port. As firmware
may evolve during the lifetime of the STLINK-V3 product (addition of new functionalities, bug fixes, or support
of new microprocessor families), visiting the www.st.com website is recommended before starting to use the
STM32MP135F-DK Discovery kit, then periodically to stay up-to-date with the latest firmware version.
7.3.4Using the STLINK-V3 to program and debug the on-board STM32
To program the on-board STM32, no specific hardware configuration is required.
UM2993 - Rev 2
page 11/42
7.4Power supply
7.4.15 V power supply
The STM32MP135F-DK Discovery kit is designed to be powered by a 5 V DC power source at 3 A maximum
such as:
•5V_VBUS connected to the CN12 connector through a USB Type-C® to USB Type-C® cable
The two lines USB_PWR_CC1 and USB_PWR_CC2 are connected to PF12 and PA3 respectively to check
what is connected to CN12 and control features enabling:
–Legacy cable
–Personal computer
–5 V DC power source at 3 A
Depending on the current needed on the devices connected to the USB port, and the board itself, power
limitations can prevent the system from working as expected. The user must ensure that the STM32MP135F-DK
Discovery kit is supplied with the correct power source depending on the current needed. It is recommended to
use a USB Type-C® to USB Type-C® 5 V / 3 A charger.
7.4.2STPMIC1 power supply
For general information concerning the STPMIC1, refer to the datasheet on the www.st.com website.
STPMIC1 supply
UM2993
Power supply
•VDD_CORE (BUCK1) used to supply the CPU of the STM32MP135F
–Value: 1.35 V
•VDD_DDR (BUCK2) used to supply the DDR core and I/Os
–Value: 1.35 V
•VDD (BUCK3) used to supply the VDD domain of the STM32MP135F
–Value: 3.3 V
•VDD_CORE (BUCK4) used to supply the core of the STM32MP135F
–Value: 1.2 V
•3V3_SW (PWR_SW) used to supply some of the 3V3 domains of the STM32MP135F-DK peripherals
–Value: 3.3 V
•VREF_DDR (LDO3) used to supply the DDR reference voltage
–Value: 0.675 V
•VDD_ADC (LDO1) used to supply the VDDA domains of the STM32MP135F
–Value: 3.3 V
•1V8_PERIPH (LDO6) used to supply the digital core and I/Os of the CSI bridge
–Value: 1.8 V
•VDD_SD (LDO5) used to supply the microSD™ card part
–Value: 3.3 V
•VDD_USB (LDO4) used to supply the USB PHY of the STM32MP135F
–Value: 3.3 V
7.5
Clock sources
7.5.1LSE clock references
The LSE clock reference on the STM32MP135F microprocessor is provided by the external crystal X2:
•32.768 kHz crystal
7.5.2HSE clock references
The HSE clock reference on the STM32MP135F microprocessor is provided by the external crystal X4:
•24 MHz crystal
UM2993 - Rev 2
page 12/42
7.6Reset sources
The reset signal of STM32MP135F-DK is active low. The internal PU forces the RST signal to a high level.
The sources of reset are:
•Reset button B5 (black button)
•STPMIC1
•Embedded STLINK-V3
•STM32MP135F-DK
7.7Boot mode
7.7.1Description
At startup, the boot pins select the boot source used by the internal boot ROM. Table 4 describes the
configurations of the boot pins.
Boot 0Boot 1Boot 2Boot mode
000Forced USB boot for programming.
001Reserved.
101
UM2993
Reset sources
Table 4. Boot mode pins
SD™ card on SDMMC1.
Other combinationsNot supported.
Table 5 shows the configurations of the boot mode switch SW1.
Table 5. Boot mode switch SW1
Switch positions
Boot0
1. Not connected.
2. X is either 1 or 0.
Boot1
(1)
Boot2
NC
Boot0: 0
Boot1: 0
Boot2: 0
(2)
NC: X
Boot0: 0
Boot1: 0
Boot2: 1
(2)
NC: X
Boot0: 1
Boot1: 0
Boot2: 1
(2)
NC: X
Boot pin selectionBoot mode
Forced USB boot for programming.
Reserved.
SD™ card on SDMMC1.
UM2993 - Rev 2
page 13/42
7.8USB Host
7.8.1Description
The STM32MP135F-DK provides four USB Host ports (dual-USB Type-A sockets CN5 and CN6) through the
use of the USB hub. The USB hub has a full power management for each USB port: no I/O is needed from the
STM32MP135FAF7.
7.8.2USB Host interface
Table 6 describes the I/O configuration for the USB Host interface.
I/OConfiguration
PD1
PH6
USB_PD1USB1_P
USB_DM1USB1_N
1. I2C5 not connected by default (R166 and R167 OFF).
Table 6. I/O configuration for the USB Host interface
PD1 used as I2C5_SCL shared between LCD and MIPI CSI-2
PH6 used as I2C5_SDA shared between LCD and MIPI CSI-2
UM2993
USB Host
®(1)
®(1)
Figure 6 shows the CN5 and CN6 USB Type-A connectors pinout.
Figure 6. CN5 and CN6 USB Type-A connector pinout
Table 7 describes the CN5 and CN6 USB Host connectors pinout.
Table 7. CN5 and CN6 USB Host connectors pinout
Pin
T1T1VBUSVBUS
T2T2USB1CN26_NDM
T3T3USB1CN26_PDP
T4T4GNDGND
B1B1VBUSVBUS
B2B2USB1CN26_NDM
Pin nameSignal nameFunction
CN5
UM2993 - Rev 2
page 14/42
USB Type-C® HS
PinPin nameSignal nameFunction
B3B3USB1CN26_PDP
B4B4GNDGND
CN6
T1T1VBUSVBUS
T2T2USB1CN25_NDM
T3T3USB1CN25_PDP
T4T4GNDGND
B1B1VBUSVBUS
B2B2USB1CN25_NDM
B3B3USB1CN25_PDP
B4B4GNDGND
UM2993
7.9
USB Type-C® HS
7.9.1Description
The STM32MP135F-DK Discovery kit supports USB high speed (HS) communication. USB connector CN7 is a
USB Type-C® connector.
The STM32MP135F-DK Discovery kit supports the USB Type-C® Source mode.
7.9.2Operating voltage
The STM32MP135F-DK Discovery kit supports 5 V USB voltage from 4.75 V to 5.25 V.
7.9.3USB HS Source
When a USB Device connection to the CN7 USB Type-C® connector of STM32MP135F-DK is detected, the
Discovery kit starts behaving as a USB Host.
7.9.4
USB Type-C® connector
Figure 7 shows the pinout of USB Type-C® connector CN7.
A1A2A3A4A5A6A7A8A9A10A11A12
GND
TX1+TX1-VBUSCC1D+D-SBU1VBUSRX2-RX2+GND
Figure 7. CN7 USB Type-C® connector pinout
UM2993 - Rev 2
GNDRX1+RX1-VBUSSBU2D-D+CC2VBUSTX2-TX2+GND
B12B11B10B9B8B7B6B5B4B3B2B1
page 15/42
Table 8 describes the pinout of USB Type-C® connector CN7.
Table 8. CN7 USB Type-C® connector pinout
UM2993
microSD™ card
FunctionSTM32 pinSignal name
GND-GNDGNDA1 B12GNDGND-GND
TX1+--TX1+A2 B11RX1+--RX1+
TX1---TX1-A3 B10RX1---RX1-
VBUS--VBUSA4B9VBUS--VBUS
CC1--CC1A5B8SBU2--SBU2
D+USB_DP2USB_DP2D+A6B7D-USB_DM2USB_DM2D-
D-USB_DM2USB_DM2D-A7B6D+USB_DP2USB_DP2D+
SBU1--SBU1A8B5CC2--CC2
VBUS--VBUSA9B4VBUS--VBUS
RX2---RX2-A10 B3TX2---TX2-
RX2+--RX2+A11 B2TX2+--TX2+
GND-GNDGNDA12 B1GNDGND-GND
7.10
microSD™ card
7.10.1Description
The CN3 slot for the microSD™ card is routed to the STM32MP135F SDIO port (SDMMC1). This interface is
compliant with SD Memory Card Specification Version 3.01: High Speed.
Pin
name
Pin Pin
Pin
name
Signal nameSTM32 pinFunction
7.10.2Operating voltage
The microSD™ card interface is only compatible with the 3.3 V voltage range: from 2.7 V to 3.6 V. All microSD
card types are supported (including SDHC and SDXC), but only Default and High-Speed modes (3V3) are
supported on STM32MP135F-DK. UHS-I modes (1.8 V) are not supported on this Discovery kit.
7.10.3
microSD™ card interface
The microSD™ card interface is used in the four data lines D[0:3] with one clock (CLK), one command line (CMD),
and one card detection signal (CARD_DETECT).
The SDMMC1 is a bootable interface.
Table 9 describes the I/O configuration for the SDIO interface.
I/O
PH4PH4 is connected to µSD_DETECT
PC8PC8 is connected to SDMMC1_D0
PC9PC9 is connected to SDMMC1_D1
PC10PC10 is connected to SDMMC1_D2
PC11PC11 is connected to SDMMC1_D3
PC12PC12 is connected to SDMMC1_CLK
PD2PD2 is connected to SDMMC1_CMD
™
Table 9. I/O configuration for the SDIO interface
Configuration
UM2993 - Rev 2
page 16/42
Figure 8 shows the pinout of the microSD™ card connector CN3.
Figure 8. microSD™ card connector CN3
Table 10 describes the pinout of the microSD™ card connector CN3.
Table 10. CN3 microSD™ card connector pinout
UM2993
LEDs
PinPin nameSignal nameSTM32 pinFunction
1DAT2SDMMC1_D2PC10SDIO.D2
2DAT3_CDSDMMC1_D3PC11SDIO.D3
3CMDSDMMC1_CMDPD2SDIO.CMD
4VDDVDD_SD-VDD_SDCARD
5CLKSDMMC1_CLKPC12SDIO.CLK
6VSSGND-GND
7DAT0SDMMC1_D0PC8SDIO.D0
8DAT1SDMMC_D1PC9SDIO.D1
9CARD_DETECTμSD_DETECTPH4μSD_DETECT active low
10GNDGND-GND
11GNDGND-GND
12GNDGND-GND
13NCNCNCNC
7.11LEDs
7.11.1Description
The LD1 LED turns green when the power cable is inserted in connector CN12.
Two general-purpose LED color LEDs (LD3 and LD6) are available as light indicators:
•The LD3 blue LED is used as Linux® Heartbeat LED, which is blinking as long as Linux® is alive on the
Cortex®-A.
•The LD6 orange LED is used as STM32Cube examples verdict LED.
The two indicator LEDs, the red LD4 and green LD7 LEDs, are respectively connected to the STM32MP135 MPU
and to the MCP series I/O expander.
UM2993 - Rev 2
page 17/42
7.11.2Operating voltage
All LEDs are driven by the I/O level; they are operating in the 3.3 V voltage range.
7.11.3LED interface
Table 11 describes the I/O configuration of the LED interface.
I/OConfiguration
PA14PA14 is connected to the blue LED LD3. Active Low.
PA13PA13 is connected to the red LED LD4. Active Low.
MCP IO14MCP IO14 is connected to the green LED LD7. Active High.
MCP IO15MCP IO15 is connected to the orange LED LD6. Active High.
7.12Buttons
7.12.1Description
The STM32MP135F-DK Discovery kit provides five buttons:
•USER1 button (B1)
–Used at boot time by U-Boot to enter the USB programming mode
•USER2 button (B2)
–Used at boot time by U-Boot to enter the Android™ Fastboot mode
•Wake-up button (B3)
–Allows the platform to be woken up from any low-power mode
–Connected to STPMIC1 PONKEY, which generates a wake-up signal on STM32MP135FAF7 pin PF8
•Tamper button (B4)
–Allows the detection of case opening as a security event
•Reset button (B5)
–Used to reset the Discovery kit
UM2993
Buttons
Table 11. I/O configuration of the LED interfaces
7.12.2I/O interface
Table 12 describes the I/O configuration for the physical user interface.
I/O
PA14USER1 button (B1)
PA13USER2 button (B2)
-Wake-up button (B3). Connected to the PONKEY pin of the STPMIC1
PA6Tamper button (B4)
NRSTReset button (B5). Active Low.
UM2993 - Rev 2
Table 12. I/O configuration for the physical user interface
Configuration
page 18/42
7.13CSI-DCMI
7.13.1Description
The STM32MP135F-DK Discovery kit provides an external camera module with a 1/4" color CMOS UXGA
2-megapixel image sensor. A CSI-DCMI bridge deserializes data from the camera module, which are then
transmitted to the MPU.
The resolution is up to 1600 x 1200 with 20 frames per second.
Output signals are 8-bit RGB RAW.
The control signals are I2C5.
7.13.2DCMI I/O interface
Table 13 describes the I/O configuration for the DCMI interface.
I/OConfiguration
PA9PA9 is connected to DCMI_D0
PD0PD0 is connected to DCMI_D1
PG10PG10 is connected to DCMI_D2
PE4PE4 is connected to DCMI_D3
PD11PD11 is connected to DCMI_D4
PD3PD3 is connected to DCMI_D5
PB8PB8 is connected to DCMI_D6
PE14PE14 is connected to DCMI_D7
PB7PB7 is connected to DCMI_PIXCLK
PG9PG9 is connected to DCMI_VSYNC
PH8PH8 is connected to DCMI_HSYNC
MCP_IO1MCP_IO1 is connected to STMIPI_ERROR
MCP_IO0MCP_IO0 is connected to STMIPI_INT
PD7PD7 is connected to STMIPI_EXTCLK
MCP_IO2MCP_IO2 is connected to STMIPI_XSDN
PD1PD1 is used as I2C5_SCL shared between USB and touch panel
PH6PH6 is used as I2C5_SDA shared between USB and touch panel
UM2993
CSI-DCMI
Table 13. I/O configuration for the DCMI interface
UM2993 - Rev 2
page 19/42
Figure 9 shows the pinout of CSI connector CN1.
Figure 9. CN1 CSI connector pinout
UM2993
CSI-DCMI
Table 14
describes the CSI interface and pinout of CSI connector CN1.
Table 14. CSI interface and CN1 connector pinout
PinSTM32 pinSignal nameFunction
1-GNDGND
2-DATA1_N
3-DATA1_P
4-GNDGND
5-DATA2_N
6-DATA2_P
7-GNDGND
8-CKL_NNegative clock lane
9-CKL_PPositive clock lane
10-GNDGND
11MCP_IO3CAM_ENABLECamera shutdown
12MCP_IO4CAM_RESETCamera reset
13PD1I2C5_SCL
14PH6I2C5_SDA
15-3V3_SW3V3
Negative data lane 1 from MIPI-CSI
receiver 1
Positive data lane 1 from MIPI-CSI
receiver 1
Negative data lane 2 from MIPI-CSI
receiver 1
Positive data lane 2 from MIPI-CSI
receiver 1
I2C5_SCL shared between USB and
touch panel
I2C5_SDA shared between USB and
touch panel
UM2993 - Rev 2
page 20/42
UM2993
Wi‑Fi® and Bluetooth® Low Energy
7.14
Wi‑Fi® and Bluetooth® Low Energy
7.14.1Description
The STM32MP135F-DK Discovery kit supports Wi‑Fi® 802.11b/g/n and Bluetooth® Low Energy (BLE) V4.1. This
module is driven by an SDIO for the Wi‑Fi® interface, and a USART for the Bluetooth®. The PCM format is used
for audio data.
7.14.2Operating voltage
The Wi‑Fi®/BLE module supports the 3.3 V voltage range.
7.14.3
Wi‑Fi® I/O interface
Table 15 describes the I/O configuration for the Wi‑Fi® interface.
I/OConfiguration
PB4PB4 is connected to SDMMC2_D3
PB3PB3 is connected to SDMMC2_D2
PB15PB15 is connected to SDMMC2_D1
PB14PB14 is connected to SDMMC2_D0
PG6PG6 is connected to SDMMC2_CMD
PE3PE3 is connected to SDMMC2_CK
MCP_IO11MCP_IO11 is connected to WL_REG_ON
PF0PF0 is connected to WL_HOST_WAKE
Table 15. I/O configuration for the Wi‑Fi® interface
7.14.4
Bluetooth® Low Energy I/O interface
Table 16 describes the I/O configuration for the Bluetooth® Low Energy interface.
Table 16. I/O configuration for the Bluetooth® Low Energy interface
I/O
PH12PD5 is connected to USART2_TX
PD15PD6 is connected to USART2_RX
PD4PD4 is connected to USART2_RTS
PE11PD3 is connected to USART2_CTS
PB13PZ3 is connected to BT_PCM_WS
PH10PZ2 is connected to BT_PCM_SDO
PB5PZ1 is connected to BT_PCM_SDI
PB10PZ0 is connected to BT_PCM_CK
MCP_IO13PZ6 is connected to BT_REG_ON
PE10PH5 is connected to BT_HOST_WAKE
MCP_IO12PZ7 is connected to BT_DEV_WAKE
PI1LP0_32
Configuration
UM2993 - Rev 2
page 21/42
7.15LCD
The LCD is provided and mounted with the STM32MP135F-DK Discovery kit.
7.15.1Description
The TFT LCD module is connected to the board through the 40-pin connector CN16. The touch panel is
embedded in the LCD module.
The LCD module is composed of a TFT LCD module with an LCD driver. The 4.3" LCD supports a resolution of
480 × 272 dots in 262K colors (RGB). The touch panel drive works with a self-capacitive controller.
7.15.2Operating voltage
The LCD module with its touch panel power supply is connected to 3V3_SW.
The backlight of the LCD is driven by a dedicated circuit connected to 5V_VIN.
7.15.3LCD interface
Table 17 describes the I/O configuration of the LCD and CTP interfaces.
I/OConfiguration
PD10PD10 is connected to LTDC_B2
PF2PF2 is connected to LTDC_B3
PH14PH14 is connected to LTDC_B4
PE0PE0 is connected to LTDC_B5
PB6PB6 is connected to LTDC_B6
PF1PF1 is connected to LTDC_B7
PH13PH13 is connected to LTDC_G2
PF3PF3 is connected to LTDC_G3
PD5PD5 is connected to LTDC_G4
PG0PG0 is connected to LTDC_G5
PC7PC7 is connected to LTDC_G6
PA15PA15 is connected to LTDC_G7
PG7PG7 is connected to LTDC_R2
PB12PB12 is connected to LTDC_R3
PD14PD14 is connected to LTDC_R4
PE7PE7 is connected to LTDC_R5
PE13PE13 is connected to LTDC_R6
PE9PE9 is connected to LTDC_R7
PD9PD9 is connected to LTDC_CLK
PH9PH9 is connected to LTDC_DE
PC6PC6 is connected to LTDC_HSYNC
PG4PG4 is connected to LTDC_VSYNC
PF5PF5 is connected to LCD_INT
PD1PD1 is used as I2C5_SCL shared between USB and CSI
PH6PH6 is used as I2C5_SDA shared between USB and CSI
PH2PH2 is connected to LCD_NRST
UM2993
LCD
Table 17. I/O configuration of the LCD and CTP interfaces
UM2993 - Rev 2
page 22/42
7.16Dual 10/100Mbit/s Ethernet
7.16.1Description
The STM32MP135F-DK Discovery kit provides a reduced media-independent interface (RMII).
The STM32MP135FAF7 requires an external physical interface device (PHY) for each RMII. The Ethernet PHY
on the Discovery kit is connected to the physical LAN bus using 10 or 11 signals for RMII on Wake on LAN (WoL)
support.
The main Ethernet port, Ethernet 1, can be clocked using the 25 MHz from the STM32MP135FAF7 or from a
crystal (X3) as it supports Wake on LAN (WoL) operation. The default configuration is 25 MHz from the X3 crystal.
The second Ethernet port, Ethernet 2, can only be clocked using the 25 MHz from the STM32MP135FAF7 as it
does not support Wake on LAN (WoL) operation.
The Ethernet connector embedded LED blink to indicate data transmission.
For more details about the Ethernet PHY (such as clocking or configuration), refer to the bill of material and to the
corresponding datasheet from the PHY provider.
7.16.2Operating voltage
The Ethernet PHYs are supplied with 3V3_AO for Ethernet 1 and with 3V3_SW for Ethernet 2.
7.17GPIO expansion connector
UM2993
Dual 10/100Mbit/s Ethernet
7.17.1Description
•The GPIO pins can be used as GPIOs or alternate functions. The available alternate functions are listed in
The VBAT connector allows a power mode that maintains critical operations when a power loss occurs on VDD.
The VBAT power domain contains the RTC, the backup registers, the retention RAM, and the backup SRAM. To
enable VBAT mode, a back-up power source must be connected to the VBAT connector.
7.18.2Operating voltage
The VBAT connector allows external supply from 1.2 V to 3.6 V.
7.18.3VBAT interface
Table 19 describes the I/O configuration of the VBAT interface.
Table 19. I/O configuration of the CN11 VBAT interface
I/O
1VBAT
2GND
Configuration
UM2993 - Rev 2
page 25/42
Figure 11 shows the pinout of the CN11 VBAT connector.
Figure 11. CN11 VBAT connector pinout
UM2993
VBAT connector
Table 20
describes the VBAT interface and pinout of connector CN11.
Table 20. CN11 VBAT connector pinout
PinPin nameFunction
1VBATVBAT supply.
2GNDGround.
UM2993 - Rev 2
page 26/42
8STM32MP135F-DK product information
8.1Product marking
The stickers located on the top or bottom side of all PCBs provide product information:
•First sticker: product order code and product identification, generally placed on the main board featuring
the target device.
Example:
Product order code
Product identification
•Second sticker: board reference with revision and serial number, available on each PCB.
Example:
MBxxxx-Variant-yzz
syywwxxxxx
On the first sticker, the first line provides the product order code, and the second line the product identification.
On the second sticker, the first line has the following format: “MBxxxx-Variant-yzz”, where “MBxxxx” is the board
reference, “Variant” (optional) identifies the mounting variant when several exist, “y” is the PCB revision, and “zz”
is the assembly revision, for example B01. The second line shows the board serial number used for traceability.
Parts marked as “ES” or “E” are not yet qualified and therefore not approved for use in production. ST is not
responsible for any consequences resulting from such use. In no event will ST be liable for the customer using
any of these engineering samples in production. ST’s Quality department must be contacted prior to any decision
to use these engineering samples to run a qualification activity.
“ES” or “E” marking examples of location:
•On the targeted STM32 that is soldered on the board (for an illustration of STM32 marking, refer to the
STM32 datasheet Package information paragraph at the www.st.com website).
•Next to the evaluation tool ordering part number that is stuck, or silk-screen printed on the board.
Some boards feature a specific STM32 device version, which allows the operation of any bundled commercial
stack/library available. This STM32 device shows a “U” marking option at the end of the standard part number
and is not available for sales.
To use the same commercial stack in their applications, the developers might need to purchase a part number
specific to this stack/library. The price of those part numbers includes the stack/library royalties.
Federal Communications Commission (FCC) and ISED Canada Compliance Statements
10Federal Communications Commission (FCC) and ISED Canada
Compliance Statements
10.1FCC Compliance Statement
Part 15.19
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1)
this device may not cause harmful interference, and (2) this device must accept any interference received,
including interference that may cause undesired operation.
Part 15.21
Any changes or modifications to this equipment not expressly approved by STMicroelectronics may cause
harmful interference and void the user's authority to operate this equipment.
Part 15.105
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part
15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference
when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate
radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause
harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause
harmful interference in which case the user will be required to correct the interference at his own expense.
Note:
Use only shielded cables for USB, Ethernet, HDMI® cables. Use added ferrite clamp on audio cable (one turn).
10.2
Responsible party (in the USA)
Terry Blanchard
Americas Region Legal | Group Vice President and Regional Legal Counsel, The Americas
STMicroelectronics, Inc.
750 Canyon Drive | Suite 300 | Coppell, Texas 75019
USA
Telephone: +1 972-466-7845
ISED Compliance Statement
This device complies with FCC and ISED Canada RF radiation exposure limits set forth for general population for
mobile application (uncontrolled exposure). This device must not be collocated or operating in conjunction with
any other antenna or transmitter.
Compliance Statement
Notice: This device complies with ISED Canada licence-exempt RSS standard(s). Operation is subject to the
following two conditions: (1) this device may not cause interference, and (2) this device must accept any
interference, including interference that may cause undesired operation of the device.
Avis: Le présent appareil est conforme aux CNR d'ISDE Canada applicables aux appareils radio exempts
de licence. L'exploitation est autorisée aux deux conditions suivantes : (1) l'appareil ne doit pas produire de
brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage
est susceptible d'en compromettre le fonctionnement.
Étiquette de conformité à la NMB-003 d'ISDE Canada: CAN ICES-3 (A) / NMB-3 (A).
UM2993 - Rev 2
page 33/42
Additional FCC and ISED Canada Compliance Statements
10.3Additional FCC and ISED Canada Compliance Statements
This device contains license-exempt transmitter(s)/receiver(s) that comply with Innovation, Science and Economic
Development Canada’s license-exempt RSS(s). Operation is subject to the following two conditions:
1.This device may not cause interference.
2.This device must accept any interference, including interference that may cause undesired operation of the
device.
Appareils radio exempts de licence ISDE
L’émetteur/récepteur exempt de licence contenu dans le présent appareil est conforme aux CNR d’Innovation,
Sciences et Développement économique Canada applicables aux appareils radio exempts de licence.
L’exploitation est autorisée aux deux conditions suivantes :
1.L’appareil ne doit pas produire de brouillage ;
2.L'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en
compromettre le fonctionnement.
UM2993
Radio Frequency (RF) Exposure Compliance of Radiocommunication Apparatus
To satisfy FCC and ISED Canada RF Exposure requirements for mobile devices, a separation distance of 20
cm or more should be maintained between the antenna of this device and persons during operation. To ensure
compliance, operation at closer than this distance is not recommended. This transmitter must not be co-located or
operating in conjunction with any other antenna or transmitter.
Pour satisfaire aux exigences FCC et ISDE Canada concernant l'exposition aux champs RF pour les appareils
mobile, une distance de séparation de 20 cm ou plus doit être maintenu entre l'antenne de ce dispositif et les
personnes pendant le fonctionnement. Pour assurer la conformité, il est déconseillé d'utiliser cet équipement
à une distance inférieure. Cet émetteur ne doit pas être co-situé ou fonctionner conjointement avec une autre
antenne ou un autre émetteur.
UM2993 - Rev 2
page 34/42
11CE conformity
11.1Warning
EN 55032 / CISPR32 (2012) Class A product
Warning: this device is compliant with Class A of EN55032 / CISPR32. In a residential environment, this
equipment may cause radio interference.
11.2Simplified declaration of conformity
Hereby, STMicroelectronics declares that the radio equipment types and STM32MP135F-DK are in compliance
with Directive 2014/53/EU. The full text of the EU declaration of conformity is available from their product web
page.
UM2993
CE conformity
UM2993 - Rev 2
page 35/42
Revision history
Table 24. Document revision history
DateRevisionChanges
01-Mar-20231Initial release.
Updated cover pictures.
06-Mar-20232
Updated board variant references in Table 21. Product history and
Table 22. Board revision history.
Updated Section 10 Federal Communications Commission (FCC) and ISED
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 acknowledgment.
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. For additional information about ST trademarks, refer to www.st.com/trademarks. 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.