<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>STM32MP157 on Embedded Linux Blog</title><link>https://embeddedlinux.blog/en/stm32mp157/</link><description>Recent content in STM32MP157 on Embedded Linux Blog</description><generator>Hugo</generator><language>en</language><atom:link href="https://embeddedlinux.blog/en/stm32mp157/index.xml" rel="self" type="application/rss+xml"/><item><title>[STM32MP1] 1. Remoteproc: loading Cortex-M4 firmware from Linux on the A7 core</title><link>https://embeddedlinux.blog/en/2026/01/10/stm32mp1-remoteproc-2-nap-firmware-core-m4-tu-core-a7-linux/</link><pubDate>Sat, 10 Jan 2026 07:06:00 +0700</pubDate><guid>https://embeddedlinux.blog/en/2026/01/10/stm32mp1-remoteproc-2-nap-firmware-core-m4-tu-core-a7-linux/</guid><description>&lt;h2 id="1-preparing-the-elf-file-for-the-m4-core"&gt;1. Preparing the elf file for the M4 core&lt;/h2&gt;&#10;&lt;p&gt;Get STM32IDE, downloaded from ST's website &lt;a href="https://www.st.com/en/development-tools/stm32cubeide.html" target="_blank" rel="noopener"&gt;https://www.st.com/en/development-tools/stm32cubeide.html&lt;/a&gt;&#10;&lt;/p&gt;&#10;&lt;p&gt;My machine runs Ubuntu, so it will differ. For this part it is really still just debugging the M4 core, nothing to do with remoteproc yet. You can do this part on a Windows machine, or do something similar with another Arm Cortex-M4 board&lt;/p&gt;</description></item><item><title>[Yocto-STM32MP1] 2. Creating a kernel device tree patch, enabling i2c</title><link>https://embeddedlinux.blog/en/2025/12/13/yocto-stm32mp1-2-tao-patch-device-tree-kernel-mo-i2c/</link><pubDate>Sat, 13 Dec 2025 07:18:00 +0700</pubDate><guid>https://embeddedlinux.blog/en/2025/12/13/yocto-stm32mp1-2-tao-patch-device-tree-kernel-mo-i2c/</guid><description>&lt;p&gt;In this post I show you how to create a kernel device tree patch to enable i2c5 on the board&lt;/p&gt;&#10;&lt;h2 id="1-documents-and-hardware"&gt;1. Documents and hardware&lt;/h2&gt;&#10;&lt;p&gt;Read the vendor's &lt;a href="https://www.st.com/resource/en/user_manual/um2534-discovery-kits-with-stm32mp157-mpus-stmicroelectronics.pdf" target="_blank" rel="noopener"&gt;User Manual&lt;/a&gt;&#10;; page 8 has the Hardware block diagram, showing the connections currently routed out from the chip&lt;/p&gt;</description></item><item><title>[Yocto-STM32MP1] 1. Build and flash core-image-minimal for the STM32MP157</title><link>https://embeddedlinux.blog/en/2025/12/06/yocto-stm32mp1-1-build-va-flash-core-image-minimal-cho-stm32mp157/</link><pubDate>Sat, 06 Dec 2025 07:11:00 +0700</pubDate><guid>https://embeddedlinux.blog/en/2025/12/06/yocto-stm32mp1-1-build-va-flash-core-image-minimal-cho-stm32mp157/</guid><description>&lt;h2 id="1-preparing-the-host-machine"&gt;1. Preparing the host machine&lt;/h2&gt;&#10;&lt;p&gt;My machine runs Ubuntu 22.04.5 LTS (Jammy Jellyfish). I installed it dual boot with windows to make the most of the cores&lt;/p&gt;&#10;&lt;p&gt;Following the &lt;a href="https://docs.yoctoproject.org/2.2.2/ref-manual/ref-manual.html#required-packages-for-the-host-development-system" target="_blank" rel="noopener"&gt;Yocto Project Reference Manual&lt;/a&gt;&#10;, section 1.3.2.1, we install the following packages&lt;/p&gt;</description></item></channel></rss>