we have configured a splash screen for u-boot on Apalis imx8 following the guide (Splash Screen on U-Boot | Toradex Developer Center) but no image is displayed.
Our panel uses dual lvds with DE mode. How can we set mode and timings for our panel in u-boot?
yes, we are using an AUO G215HAN01.2 which uses a dual channel interface.
The panel works well with Linux. We just want to add an splash screen with u-boot.
it takes a few seconds till the Linux splash screen is displayed. We would like to avoid the black screen after switching on the device before Linux takes over.
For i.mx8 there is no display_info_t in u-boot’s apalis-imx8.c or can I set the values via u-boot environment?
Hi @ floji
I’m curious about your progress ,
I have a similar ( a bit ) system and a similar problem (colibri imx8x+ lvds)
I have the impression that the information on the toradex site is for old systems
, the descriptions do not work on imx8x (in my opinion)
When I see on TORADEX youtuber channel u-boot logo on colibri IMX8X , I will believe it !
I see some people asking about it, but I don’t see any solutions
since splash screen support for kernel has been dropped with BSP 6 we are now running out of options. Running a user space splash application takes way too long.
Is there any chance we might get U-Boot splash support on iMX8 or at least get the kernel splash screen back? Other SOM manufacturers do support splash screens for U-Boot and kernel.
the earlier a splash screen is shown the better. I think 1.5 (2s max) would be good. Customers start to get nervous if a blank screen is shown longer.
Our current unit (iMX6) shows boot loader splash screen almost instantly and then blends over to kernel splash screen. Loading our application takes a few seconds so early feedback is required.
sorry for the late reply.
I’ve installed psplash using initramfs. Currently it takes around 6,5s for the splash screen to appear.
I tried all the “low-hanging fruit” from the links you provided. There are a few things left that I can do (e.g. further reducing kernel size) but I doubt that I can save more than additional 0,5-1,0s.
Could you please tell us more about this? Which exact strategy was used here? Also, if possible share the version of software used (e.g. kernel - upstream or downstream? -, u-boot, psplash). Also, how the handover was implemented?
If you prefer, we can make this thread non-public, so you can share more details.
I was informed you were in touch via email with the Toradex team and got the recent update related to this thread.
For completeness, I will add it here in the Community as well.
The current state of Splash Screen:
Different modules have different requirements/limitations, and no one-size-fits-all solution;
Not to mention that Toradex is concerned about supporting several different display interfaces and each of them would need some kind of tweaking.
Mainline U-boot doesn’t support video displays on i.MX8-based modules. It’s not clear if it’s supported downstream;
U-boot Splash Screen is very static and requires U-boot recompilation;
Linux Kernel Splash Screen is also very limited, static, and requires Kernel recompilation;
There seems to be no mechanism for a smooth transition of the video handling between U-boot and the Linux Kernel.
The discussion about what is going to be done and research about the topic is still ongoing. I can say that we are at least going to have some documentation showing methods for enabling it.