FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Device Tree (.dts) Configuration and SDK Compatibility (STM32MP157F-DK2)

kampl
Associate

‎2026-03-09 4:41 AM - last edited on ‎2026-03-13 3:15 AM by

Dear ST Support Team,

 

I am seeking technical assistance for two critical issues I am encountering while developing on the STM32MP157F-DK2 (Kernel 5.10.61, Ecosystem v3.1).

 

Issue 1: GLIBC Compatibility When running applications compiled on my host machine, I receive the error: /lib/libc.so.6: version 'GLIBC_2.34' not found. I am attempting to cross-compile using the correct SDK for Ecosystem v3.1, but I am struggling to locate the compatible toolchain/environment for my specific kernel version (5.10.61).

 

Issue 2: Device Tree (.dts) Configuration I am unable to enable additional peripherals (specifically UART7). Despite updating the .dts file to set status = "okay", the peripheral remains disabled on the target board (verified via cat /sys/firmware/devicetree/base/soc/.../status). It appears the system is ignoring my device tree updates and defaulting to the internal bootloader configuration.

 

Attachments:

  1. Screenshot showing the GLIBC error on the board.

  2. Screenshot of the current Device Tree status check showing "disabled".

Could you please provide:

  1. A direct link to the correct SDK/Toolchain compatible with Ecosystem v3.1 for Kernel 5.10.61.

  2. Guidance on how to correctly force the target to load a custom .dtb file, as my current manual overwrites of the file on the SD card are being ignored by the bootloader.

Your assistance in helping me align my development environment and device tree configuration is greatly appreciated.

Labels:
Preview file
133 KB
Preview file
211 KB
0 Kudos
2 REPLIES 2
Christophe Guibout
ST Employee

‎2026-03-13 3:13 AM

Hello @kampl,

Regarding the Ecosystem-v3.1, I would recommand to have a look into the release note available in the wiki : link.

About the second issue, if you set a peripheral to "okay" in the DT and it is not available, it means an error occured, so you need to check the kernel logs (dmesg).

BR,

Christophe

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
0 Kudos
kampl
Associate
In response to Christophe Guibout

‎2026-03-16 11:25 PM

Dear Christophe,

 

Thank you for your previous guidance regarding the Ecosystem-v3.1 release notes.

 

I am currently working with the STM32MP157F-DK2 board and have successfully flashed a Linux Kernel 5.10 image. However, I am facing persistent issues with the HDMI and CAN ports. Despite setting the status to "okay" in my Device Tree (.dts), these peripherals are not initializing correctly.

 

Current Issues -

  1. HDMI Port -  The display remains inactive. In my dmesg logs, I am seeing i2c bus busy errors and the sii902x (or adv7511) transmitter is failing to read status (Error -110). I have attempted to disable DSI to prioritize the HDMI pipeline, but the LTDC driver does not seem to bind correctly.

 

     2.CAN Port - Even though m_can1 and m_can2 are enabled in the DT, they do not appear as network interfaces.

 

Request for Guidance -  Could you provide the specific steps or a reference configuration for the STM32MP157F-DK2 on New Kernel version to ensure

  • The correct clock and power regulator settings for the HDMI bridge on this specific board revision.

  • The required pinctrl and transceiver configuration for the CAN FD ports.

  • Any specific Kernel Config (defconfig) symbols that must be enabled for the LTDC-to-HDMI path in this version of the ecosystem.

I am struggling to find a working example for Kernel that reconciles these specific hardware paths on the DK2. Any specific documentation or DT snippets for this board would be greatly appreciated.

 

Best regards,

Prateek

0 Kudos
Top