Yocto STM32MP157 DK2 - Display not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-29 4:31 PM
Hello
I use https://github.com/STMicroelectronics/meta-st-stm32mp with the stm32mp15-disco machine.
It boots fine, I can access the shell via USB-UART. But the display just shows an STM Logo from the Bootloader. What do I need to change, so the display works in Linux?
This is the error when trying to start X:
root@stm32mp15-disco:~# startx
xauth: file /home/root/.serverauth.724 does not exist
X.Org X Server 1.21.1.8
X Protocol Version 11, Revision 0
Current Operating System: Linux stm32mp15-disco 6.1.28 #1 SMP PREEMPT Thu May 11 14:04:52 UTC 2023 armv7l
Kernel command line: root=PARTUUID=e91c4e10-16e6-4c0e-bd0e-77becf4a3582 rootwait rw console=ttySTM0,115200
Current version of pixman: 0.42.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 9 21:17:20 2018
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
- Labels:
-
STM32MP15 Lines
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-05-03 5:19 AM
Hi @kbch n
Can you please share version you are using and all details about yocto build config ?
Thanks
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
‎2024-05-03 5:58 AM
I'm using this branch of the meta repo, commit 5e5b99ba054276d10b4afec2b80962de3455b0a1
➜ meta-st-stm32mp git:(mickledore) ✗ git status
On branch mickledore
Your branch is up to date with 'origin/mickledore'.
bblayers and machine config:
➜ conf cat bblayers.conf
# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/bmarty/mp1/poky/meta \
/home/bmarty/mp1/poky/meta-poky \
/home/bmarty/mp1/poky/meta-yocto-bsp \
${TOPDIR}/../meta-st-stm32mp \
${TOPDIR}/../meta-openembedded/meta-oe \
${TOPDIR}/../meta-openembedded/meta-networking \
${TOPDIR}/../meta-openembedded/meta-multimedia \
${TOPDIR}/../meta-openembedded/meta-python \
"
➜ conf cat local.conf | grep MACHINE | grep stm
MACHINE = "stm32mp15-disco"
Do you need something else?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-05-03 7:02 AM
Hi @kbch ,
Which image ?
I understand that Startx may depends on X11 .. which is not supported in our distribution.
I guess you might have to check all startx dependences and manage to add them to your distribution.
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
‎2024-05-03 7:12 AM
I'm using a customized image based on core-image:
IMAGE_FEATURES += " \
dev-pkgs \
hwcodecs \
package-management \
x11-base \
"
IMAGE_INSTALL += "\
packagegroup-base \
packagegroup-core-base-utils \
packagegroup-core-boot \
packagegroup-core-full-cmdline \
packagegroup-core-tools-debug \
packagegroup-core-x11 \
${CORE_IMAGE_EXTRA_INSTALL} \
"
inherit core-image features_check
Can I somehow check within the Shell if the display got initialized to rule out any X11 specific issue?
