<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.somlabs.com/index.php?action=history&amp;feed=atom&amp;title=Yocto_Scarthgap_OpenSTLinux_for_VisionSOM-STM32MP1</id>
	<title>Yocto Scarthgap OpenSTLinux for VisionSOM-STM32MP1 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.somlabs.com/index.php?action=history&amp;feed=atom&amp;title=Yocto_Scarthgap_OpenSTLinux_for_VisionSOM-STM32MP1"/>
	<link rel="alternate" type="text/html" href="https://wiki.somlabs.com/index.php?title=Yocto_Scarthgap_OpenSTLinux_for_VisionSOM-STM32MP1&amp;action=history"/>
	<updated>2026-04-28T10:16:47Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.42.3</generator>
	<entry>
		<id>https://wiki.somlabs.com/index.php?title=Yocto_Scarthgap_OpenSTLinux_for_VisionSOM-STM32MP1&amp;diff=4081&amp;oldid=prev</id>
		<title>KrzysztofChojnowski at 08:13, 19 December 2024</title>
		<link rel="alternate" type="text/html" href="https://wiki.somlabs.com/index.php?title=Yocto_Scarthgap_OpenSTLinux_for_VisionSOM-STM32MP1&amp;diff=4081&amp;oldid=prev"/>
		<updated>2024-12-19T08:13:53Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;table style=&quot;background-color: #fff; color: #202122;&quot; data-mw=&quot;interface&quot;&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;tr class=&quot;diff-title&quot; lang=&quot;en&quot;&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;← Older revision&lt;/td&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;Revision as of 08:13, 19 December 2024&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot; id=&quot;mw-diff-left-l10&quot;&gt;Line 10:&lt;/td&gt;
&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot;&gt;Line 10:&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;Meta-somlabs layer should be used in order to build the st-image-weston image.&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;Meta-somlabs layer should be used in order to build the st-image-weston image.&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-side-deleted&quot;&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-side-deleted&quot;&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;&#039;&#039;&#039;NOTE&#039;&#039;&#039; The device-tree files in the scarthgap release were not generated by STM32CubeMX tool.&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;== Building the system image ==&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;== Building the system image ==&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/table&gt;</summary>
		<author><name>KrzysztofChojnowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.somlabs.com/index.php?title=Yocto_Scarthgap_OpenSTLinux_for_VisionSOM-STM32MP1&amp;diff=4079&amp;oldid=prev</id>
		<title>KrzysztofChojnowski: Created page with &quot;{{PageHeader|Yocto Scarthgap OpenSTLinux for VisionSOM-STM32MP1}} __toc__  == Introduction ==  This tutorial explains how to build a Yocto-based OpenSTLinux system for VisionSOM-STM32MP1 modules with VisionCB-STM32MP1-STD carrier board and meta-somlabs support layer.   * meta-somlabs (scarthgap): https://github.com/SoMLabs/openst-meta-somlabs/tree/scarthgap  == meta-somlabs ==  Meta-somlabs layer should be used in order to build the st-image-weston image.  == Building th...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.somlabs.com/index.php?title=Yocto_Scarthgap_OpenSTLinux_for_VisionSOM-STM32MP1&amp;diff=4079&amp;oldid=prev"/>
		<updated>2024-12-18T15:53:05Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{PageHeader|Yocto Scarthgap OpenSTLinux for VisionSOM-STM32MP1}} __toc__  == Introduction ==  This tutorial explains how to build a Yocto-based OpenSTLinux system for VisionSOM-STM32MP1 modules with VisionCB-STM32MP1-STD carrier board and meta-somlabs support layer.   * meta-somlabs (scarthgap): https://github.com/SoMLabs/openst-meta-somlabs/tree/scarthgap  == meta-somlabs ==  Meta-somlabs layer should be used in order to build the st-image-weston image.  == Building th...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{PageHeader|Yocto Scarthgap OpenSTLinux for VisionSOM-STM32MP1}} __toc__&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This tutorial explains how to build a Yocto-based OpenSTLinux system for VisionSOM-STM32MP1 modules with VisionCB-STM32MP1-STD carrier board and meta-somlabs support layer. &lt;br /&gt;
&lt;br /&gt;
* meta-somlabs (scarthgap): https://github.com/SoMLabs/openst-meta-somlabs/tree/scarthgap&lt;br /&gt;
&lt;br /&gt;
== meta-somlabs ==&lt;br /&gt;
&lt;br /&gt;
Meta-somlabs layer should be used in order to build the st-image-weston image.&lt;br /&gt;
&lt;br /&gt;
== Building the system image ==&lt;br /&gt;
&lt;br /&gt;
In order to build the system image a Distribution Package provided by STMicroelectronics is required. The whole building process is described on the ST wiki pages:&lt;br /&gt;
&lt;br /&gt;
https://wiki.st.com/stm32mpu/wiki/STM32MP1_Distribution_Package&lt;br /&gt;
&lt;br /&gt;
Yocto is using absolute directory path to give names to intermediate files. If the path is too long, Yocto build fails because file names exceed the maximum size &lt;br /&gt;
supported by the file system. In that case, installation directory path should be renamed to reduce the overall absolute path name.&lt;br /&gt;
&lt;br /&gt;
The summary of required steps is shown below:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
mkdir st-yocto&lt;br /&gt;
cd st-yocto&lt;br /&gt;
repo init -u https://github.com/STMicroelectronics/oe-manifest -b refs/tags/openstlinux-6.6-yocto-scarthgap-mpu-v24.12.05&lt;br /&gt;
repo sync&lt;br /&gt;
cd layers/meta-st&lt;br /&gt;
git clone -b scarthgap https://github.com/SoMLabs/openst-meta-somlabs.git meta-somlabs&lt;br /&gt;
cd ../../&lt;br /&gt;
DISTRO=openstlinux-weston MACHINE=&amp;lt;MACHINE_NAME&amp;gt; source layers/meta-st/scripts/envsetup.sh&lt;br /&gt;
bitbake st-image-weston&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following VisionSOM machines are available:&lt;br /&gt;
* mp157a-dsi-rvt-emmc-mx VisionSOM-STM32MP1 eMMC module with VisionCB-STM32MP1-STD board and rvt70hsmnwc00 DSI display&lt;br /&gt;
* mp157a-hdmi-lt-emmc-mx VisionSOM-STM32MP1 eMMC module with VisionCB-STM32MP1-STD board and lt8912b HDMI bridge&lt;br /&gt;
&lt;br /&gt;
The compiled image files are located in the directory:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
st-yocto/build-openstlinuxweston-&amp;lt;MACHINE_NAME&amp;gt;/tmp-glibc/deploy/images/&amp;lt;MACHINE_NAME&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installing eMMC image ==&lt;br /&gt;
&lt;br /&gt;
To install the built system on eMMC memory the STM32CubeProgrammer has to be used. It is available to download from the STMicroelectronics website:&lt;br /&gt;
https://www.st.com/en/development-tools/stm32cubeprog.html&lt;br /&gt;
&lt;br /&gt;
In order to program the module on VisionCB-STM32MP1-STD board, the BOOT jumpers need to be set to 000 to enable DFU boot. STM32CubeProgrammer should be connected by the USB cable connected to the USB-OTG socket. After programming the BOOT jumpers need to be set to 010 in order to run the installed system.&lt;br /&gt;
&lt;br /&gt;
The details about using the STM32CubeProgrammer may be found on the ST wiki pages:&lt;br /&gt;
&lt;br /&gt;
https://wiki.st.com/stm32mpu/wiki/STM32CubeProgrammer&lt;br /&gt;
https://wiki.st.com/stm32mpu/wiki/STM32CubeProgrammer_flashlayout&lt;/div&gt;</summary>
		<author><name>KrzysztofChojnowski</name></author>
	</entry>
</feed>