Required Boot animation shows in multiple display

[Manoj_Kumar]

Hi all,

  Currently, we are working on the NXP MX8MP platform with Android 14 OS "enabling the Multiple-Display" feature, where we are using one DSI MIPI display, which is the primary display, and another one is an LVDS display. We have successfully implemented the Multiple-Display function, but at the time of booting, the Android boot animation is coming only on the DSI MIPI display, and this Android boot animation is not coming on the LVDS display.

Here I need to get the Android boot animation in both displays. How can I get the solution for this?

[Manoj_Kumar]

Hi @Bio_TICFSL 

Thanks for your support but the issue is different. We are working on "enabling the Multiple-Display" and we have implemented this feature successfully. The problem here is that we are getting Android boot animation in main display (DSI MIPI) but in LVDS display Android boot animation is not coming and directly home screen is appearing after booting completion. 

Here I need to get the Android boot animation in both displays. How can I get the solution for this?

[Bio_TICFSL]

Hello,

To have a boot image display on both monitors for an Android MX8 system, you'll need to configure both the U-Boot bootloader and the Linux kernel to support dual displays. This involves modifying device tree files (DTB/DTBO) and potentially adjusting boot arguments in U-Boot. Additionally, ensuring the kernel is compiled with the correct display drivers and configurations for both monitors is crucial. 

1. U-Boot Configuration:

• Device Tree:

  The device tree (DTB or DTBO) needs to be updated to reflect the presence of both displays. This includes enabling the appropriate display controllers (e.g., LVDS, HDMI, MIPI-DSI) and configuring their settings for each display. 

  Boot Arguments:

  In U-Boot, you might need to modify the bootargs to specify the correct display configuration and potentially load the correct DTB/DTBO file for the dual display setup. 

2. Kernel Configuration:

• Device Tree:

  The kernel's device tree (often found under arch/arm64/boot/dts/) should also be updated to reflect the dual display setup, similar to the U-Boot changes. 
• Display Selection:

  The kernel needs to know which display controller to use for each display, and this is often done through the device tree. 

3. Android-Specific Steps:

• Boot Image:

  The Android boot image (boot.img) needs to be rebuilt after making the necessary changes to the kernel and device tree. This image contains the kernel, ramdisk, and potentially other binaries. 

• Display Initialization:

  The Android system will need to initialize both displays during boot, which might involve specific calls to the display drivers and configuration settings. 

4. Testing:

• Initial Boot:

  After flashing the new boot image, start the system and observe the boot process. You should see the boot logo and any other boot messages on both displays. 

• Display Functionality:

  Verify that both displays are working correctly after the system boots into Android, and that you can interact with the system on both. 

  Regards

[Manoj_Kumar]

Hello @Bio_TICFSL 

Kindly provide a solution for this issue at your earliest convenience. We have been awaiting your response for quite some time.

Best regards,

Manoj kumar

[Manoj_Kumar]

Hi @Bio_TICFSL 

Can you please help us to solve this problem?