"stm32mp15-no-scmi.dtsi:103.1-5 Label or path dsi not found"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-09-25 9:04 AM
When building a distro for our custom board with a STM32MP153AAC, u-boot-stm32mp fails to build when UBOOT_CONFIG is set to "basic". We would like to do a ddr3 test, this is the reason for the config.
Here is the relevant section from conf/machine/stm32mp1-raichu-v2.conf file
###########################################################################
#
# User machine customization sections
#
###########################################################################
# Boot Scheme
# =========================================================================
BOOTSCHEME_LABELS += "trusted"
# WORKAROUND to generate U-BOOT SPL for DDR Tuning tools usage
UBOOT_CONFIG += "basic"
It seems that the dsi block is defined in arch/arm/dts/stm32mp157.dtsi, but we have a stm32mp153, and the device tree generated by CubeMX only includes stm32mp153.dtsi. So obviously, this isn't going to work:
- Labels:
-
OpenSTLinux
-
STM32MP15 Lines
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-09-28 8:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-09-30 5:22 AM
can you provide .patch file ? I want to see what changed.
I have the same issue, I just added stm32mp157.dtsi to includes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-09-30 5:31 AM
Hi @SMich.1​
yes patch supposed to be attached to my previous answer @AMurr.2282​ .
You don't see it ?
Else a new hot-fix release tag of u-boot is available on github.
Hope it help
Olivier
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-09-30 5:53 AM
no, i see only the source files tat.gz . not the patch .
this wat i have in my Yocto layers:
do i need to update the layers from git source?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-09-30 6:25 AM
Hi @SMich.1​
In order to integrate the u-boot hot-fix in Github in your Ditribution environnement please refer to instruction here :
https://wiki.st.com/stm32mpu/wiki/STM32MP15_OpenSTLinux_release_note#Minor_release_updates
Olivier
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-09-30 6:52 AM
tnx, i have one more question,
If i going through Distribution package installation guide in wiki pages the last minor hot-fixes will be applied?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-10-05 6:05 AM
Hi @SMich.1​ ,
No minor hot-fixes release in BSP components are not integrated in Distribution package.
You need to follow instruction in https://wiki.st.com/stm32mpu/wiki/STM32MP15_OpenSTLinux_release_note#Minor_release_updates.
Olivier
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-10-10 6:14 AM
so the tag that fixes this issue is this: v2020.10-rc5 ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-10-26 7:51 AM
Hi @SMich.1​
Sorry for late reply and error in my communication.
Actually v2020.10-rc5 was a wrong reference.
There is no hotfix tag available for this fix on github.
We will integrate it only in next major release.
So you need to apply manually the patch shared in my first comment.
Olivier
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.
