<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Required Boot animation shows in multiple display in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Required-Boot-animation-shows-in-multiple-display/m-p/2132766#M239215</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/34846"&gt;@Bio_TICFSL&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your support but the issue is different. We are working on&amp;nbsp;&lt;SPAN&gt;"enabling the Multiple-Display" and we have implemented this feature successfully. The problem here is that we are getting&amp;nbsp;Android boot animation in main display (DSI MIPI) but in LVDS display&amp;nbsp;Android boot animation is not coming and directly home screen is appearing after booting completion.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Here I need to get the Android boot animation in both displays. How can I get the solution for this?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 12 Jul 2025 09:18:22 GMT</pubDate>
    <dc:creator>Manoj_Kumar</dc:creator>
    <dc:date>2025-07-12T09:18:22Z</dc:date>
    <item>
      <title>Required Boot animation shows in multiple display</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Required-Boot-animation-shows-in-multiple-display/m-p/2128693#M238999</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&amp;nbsp; 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.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Here I need to get the Android boot animation in both displays. How can I get the solution for this?&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jul 2025 13:55:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Required-Boot-animation-shows-in-multiple-display/m-p/2128693#M238999</guid>
      <dc:creator>Manoj_Kumar</dc:creator>
      <dc:date>2025-07-04T13:55:06Z</dc:date>
    </item>
    <item>
      <title>Re: Required Boot animation shows in multiple display</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Required-Boot-animation-shows-in-multiple-display/m-p/2129389#M239048</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2" style="animation: none !important;"&gt;
&lt;DIV class="rPeykc" data-hveid="CAQQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQo_EKegQIBBAB"&gt;&lt;SPAN data-huuid="4397855884548189713"&gt;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. &lt;/SPAN&gt;&lt;SPAN data-huuid="4397855884548186262"&gt;This involves modifying device tree files (DTB/DTBO) and potentially adjusting boot arguments in U-Boot. &lt;/SPAN&gt;&lt;SPAN data-huuid="4397855884548186907"&gt;Additionally, ensuring the kernel is compiled with the correct display drivers and configurations for both monitors is crucial.&lt;SPAN class="pjBG2e" data-cid="713f07c4-e777-4d90-a389-b875f45334ab" data-ih=""&gt;&lt;SPAN class="UV3uM"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;DIV class="NPrrbc" data-cid="713f07c4-e777-4d90-a389-b875f45334ab" data-uuids="4397855884548189713,4397855884548186262,4397855884548186907"&gt;
&lt;DIV class="BMebGe btku5b fCrZyc LwdV0e FR7ZSc qVhvac OJeuxf" tabindex="0" role="button" aria-label="Ver vínculos relacionados" data-hveid="CAUQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQ3fYKegQIBRAB"&gt;
&lt;DIV class="niO4u"&gt;
&lt;DIV class="kHtcsd"&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2" style="animation: none !important;"&gt;
&lt;DIV class="rPeykc pyPiTc" data-hveid="CAkQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQo_EKegQICRAB"&gt;&lt;SPAN data-huuid="6423838145736350246"&gt;1. U-Boot Configuration: &lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2" style="animation: none !important;"&gt;
&lt;UL data-hveid="CBwQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQm_YKegQIHBAB"&gt;
&lt;LI class="K3KsMc"&gt;
&lt;DIV class="zMgcWd dSKvsb" data-il=""&gt;
&lt;DIV data-crb-p=""&gt;
&lt;DIV class="xFTqob"&gt;
&lt;DIV class="Gur8Ad"&gt;&lt;SPAN data-huuid="6423838145736350393"&gt;&lt;STRONG&gt;Device Tree:&lt;/STRONG&gt; &lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="vM0jzc"&gt;&lt;SPAN data-huuid="6423838145736350442"&gt;The device tree (DTB or DTBO) needs to be updated to reflect the presence of both displays. &lt;/SPAN&gt;&lt;SPAN data-huuid="6423838145736350491"&gt;This includes enabling the appropriate display controllers (e.g., LVDS, HDMI, MIPI-DSI) and configuring their settings for each display.&lt;SPAN class="pjBG2e" data-cid="6b9febd4-a5ab-4c26-9235-7b8fad143c43"&gt;&lt;SPAN class="UV3uM"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;DIV class="NPrrbc" data-cid="6b9febd4-a5ab-4c26-9235-7b8fad143c43" data-uuids="6423838145736350393,6423838145736350442,6423838145736350491"&gt;
&lt;DIV class="BMebGe btku5b fCrZyc LwdV0e FR7ZSc qVhvac OJeuxf" tabindex="0" role="button" aria-label="Ver vínculos relacionados" data-hveid="CBUQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQ3fYKegQIFRAB"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV data-crb-p=""&gt;
&lt;DIV class="xFTqob"&gt;
&lt;DIV class="vM0jzc"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV data-crb-p=""&gt;
&lt;DIV class="xFTqob"&gt;
&lt;DIV class="Gur8Ad"&gt;&lt;SPAN data-huuid="6423838145736350589"&gt;&lt;STRONG&gt;Boot Arguments:&lt;/STRONG&gt; &lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="vM0jzc"&gt;&lt;SPAN data-huuid="6423838145736350638"&gt;In U-Boot, you might need to modify the &lt;CODE class="mv6bHd"&gt;bootargs&lt;/CODE&gt; to specify the correct display configuration and potentially load the correct DTB/DTBO file for the dual display setup.&lt;SPAN class="pjBG2e" data-cid="18ad5f05-84dc-404e-bf72-de391a4f2d32"&gt;&lt;SPAN class="UV3uM"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;DIV class="NPrrbc" data-cid="18ad5f05-84dc-404e-bf72-de391a4f2d32" data-uuids="6423838145736350589,6423838145736350638"&gt;
&lt;DIV class="BMebGe btku5b fCrZyc LwdV0e FR7ZSc qVhvac OJeuxf" tabindex="0" role="button" aria-label="Ver vínculos relacionados" data-hveid="CBgQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQ3fYKegQIGBAB"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV data-crb-p=""&gt;
&lt;DIV class="xFTqob"&gt;
&lt;DIV class="vM0jzc"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2" style="animation: none !important;"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2" style="animation: none !important;"&gt;
&lt;DIV class="rPeykc pyPiTc" data-hveid="CCMQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQo_EKegQIIxAB"&gt;&lt;SPAN data-huuid="1724230830822710535"&gt;2. Kernel Configuration:&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="K3KsMc"&gt;
&lt;DIV class="zMgcWd dSKvsb" data-il=""&gt;
&lt;DIV data-crb-p=""&gt;
&lt;DIV class="xFTqob"&gt;
&lt;DIV class="Gur8Ad"&gt;&lt;SPAN data-huuid="1724230830822710761"&gt;&lt;STRONG&gt;Device Tree:&lt;/STRONG&gt; &lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="vM0jzc"&gt;&lt;SPAN data-huuid="1724230830822710116"&gt;The kernel's device tree (often found under &lt;CODE class="mv6bHd"&gt;arch/arm64/boot/dts/&lt;/CODE&gt;) should also be updated to reflect the dual display setup, similar to the U-Boot changes.&lt;SPAN class="pjBG2e" data-cid="a813d0c9-eff7-42eb-b058-5aca428f2971"&gt;&lt;SPAN class="UV3uM"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;DIV class="NPrrbc" data-cid="a813d0c9-eff7-42eb-b058-5aca428f2971" data-uuids="1724230830822710761,1724230830822710116"&gt;
&lt;DIV class="BMebGe btku5b fCrZyc LwdV0e FR7ZSc qVhvac OJeuxf" tabindex="0" role="button" aria-label="Ver vínculos relacionados" data-hveid="CC0QAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQ3fYKegQILRAB"&gt;
&lt;DIV class="niO4u"&gt;
&lt;DIV class="kHtcsd"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV data-crb-p=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI class="K3KsMc"&gt;
&lt;DIV class="zMgcWd dSKvsb" data-il=""&gt;
&lt;DIV data-crb-p=""&gt;
&lt;DIV class="xFTqob"&gt;
&lt;DIV class="Gur8Ad"&gt;&lt;SPAN data-huuid="1724230830822708826"&gt;&lt;STRONG&gt;Display Selection:&lt;/STRONG&gt; &lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="vM0jzc"&gt;&lt;SPAN data-huuid="1724230830822708181"&gt;The kernel needs to know which display controller to use for each display, and this is often done through the device tree.&lt;SPAN class="pjBG2e" data-cid="82a36a01-47e6-4092-9305-450e6bc1bd38"&gt;&lt;SPAN class="UV3uM"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;DIV class="NPrrbc" data-cid="82a36a01-47e6-4092-9305-450e6bc1bd38" data-uuids="1724230830822708826,1724230830822708181"&gt;
&lt;DIV class="BMebGe btku5b fCrZyc LwdV0e FR7ZSc qVhvac OJeuxf" tabindex="0" role="button" aria-label="Ver vínculos relacionados" data-hveid="CC4QAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQ3fYKegQILhAB"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV data-crb-p=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2" style="animation: none !important;"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2" style="animation: none !important;"&gt;
&lt;DIV class="rPeykc pyPiTc" data-hveid="CDUQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQo_EKegQINRAB"&gt;&lt;SPAN data-huuid="1724230830822708021"&gt;3. Android-Specific Steps: &lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2" style="animation: none !important;"&gt;
&lt;UL data-hveid="CEAQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQm_YKegQIQBAB"&gt;
&lt;LI class="K3KsMc"&gt;
&lt;DIV class="zMgcWd dSKvsb" data-il=""&gt;
&lt;DIV data-crb-p=""&gt;
&lt;DIV class="xFTqob"&gt;
&lt;DIV class="Gur8Ad"&gt;&lt;SPAN data-huuid="1724230830822710182"&gt;&lt;STRONG&gt;Boot Image:&lt;/STRONG&gt; &lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="vM0jzc"&gt;&lt;SPAN data-huuid="1724230830822709537"&gt;The Android boot image (boot.img) needs to be rebuilt after making the necessary changes to the kernel and device tree. &lt;/SPAN&gt;&lt;SPAN data-huuid="1724230830822708892"&gt;This image contains the kernel, ramdisk, and potentially other binaries.&lt;SPAN class="pjBG2e" data-cid="eb499c73-55dc-49b4-98ea-21bdeee03e0a"&gt;&lt;SPAN class="UV3uM"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;DIV class="NPrrbc" data-cid="eb499c73-55dc-49b4-98ea-21bdeee03e0a" data-uuids="1724230830822710182,1724230830822709537,1724230830822708892"&gt;
&lt;DIV class="BMebGe btku5b fCrZyc LwdV0e FR7ZSc qVhvac OJeuxf" tabindex="0" role="button" aria-label="Ver vínculos relacionados" data-hveid="CDsQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQ3fYKegQIOxAB"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV data-crb-p=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="K3KsMc"&gt;
&lt;DIV class="zMgcWd dSKvsb" data-il=""&gt;
&lt;DIV data-crb-p=""&gt;
&lt;DIV class="xFTqob"&gt;
&lt;DIV class="Gur8Ad"&gt;&lt;SPAN data-huuid="1724230830822707602"&gt;&lt;STRONG&gt;Display Initialization:&lt;/STRONG&gt; &lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="vM0jzc"&gt;&lt;SPAN data-huuid="1724230830822711053"&gt;The Android system will need to initialize both displays during boot, which might involve specific calls to the display drivers and configuration settings.&lt;SPAN class="pjBG2e" data-cid="a1bd7302-dff4-45f6-9e35-29eefb7686e9"&gt;&lt;SPAN class="UV3uM"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;DIV class="NPrrbc" data-cid="a1bd7302-dff4-45f6-9e35-29eefb7686e9" data-uuids="1724230830822707602,1724230830822711053"&gt;
&lt;DIV class="BMebGe btku5b fCrZyc LwdV0e FR7ZSc qVhvac OJeuxf" tabindex="0" role="button" aria-label="Ver vínculos relacionados" data-hveid="CDwQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQ3fYKegQIPBAB"&gt;
&lt;DIV class="niO4u"&gt;
&lt;DIV class="kHtcsd"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV data-crb-p=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2" style="animation: none !important;"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2" style="animation: none !important;"&gt;
&lt;DIV class="rPeykc pyPiTc" data-hveid="CEUQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQo_EKegQIRRAB"&gt;&lt;SPAN data-huuid="6423838145736348012"&gt;4. Testing:&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2" style="animation: none !important;"&gt;
&lt;UL data-hveid="CEkQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQm_YKegQISRAB"&gt;
&lt;LI class="K3KsMc"&gt;
&lt;DIV class="zMgcWd dSKvsb" data-il=""&gt;
&lt;DIV data-crb-p=""&gt;
&lt;DIV class="xFTqob"&gt;
&lt;DIV class="Gur8Ad"&gt;&lt;SPAN data-huuid="6423838145736348159"&gt;&lt;STRONG&gt;Initial Boot:&lt;/STRONG&gt; &lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="vM0jzc"&gt;&lt;SPAN data-huuid="6423838145736348208"&gt;After flashing the new boot image, start the system and observe the boot process. &lt;/SPAN&gt;&lt;SPAN data-huuid="6423838145736348257"&gt;You should see the boot logo and any other boot messages on both displays.&lt;SPAN class="pjBG2e" data-cid="674d984a-7461-49d7-b909-42ea3fc3d2c6"&gt;&lt;SPAN class="UV3uM"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;DIV class="NPrrbc" data-cid="674d984a-7461-49d7-b909-42ea3fc3d2c6" data-uuids="6423838145736348159,6423838145736348208,6423838145736348257"&gt;
&lt;DIV class="BMebGe btku5b fCrZyc LwdV0e FR7ZSc qVhvac OJeuxf" tabindex="0" role="button" aria-label="Ver vínculos relacionados" data-hveid="CEsQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQ3fYKegQISxAB"&gt;
&lt;DIV class="niO4u"&gt;
&lt;DIV class="kHtcsd"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV data-crb-p=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="K3KsMc"&gt;
&lt;DIV class="zMgcWd dSKvsb" data-il=""&gt;
&lt;DIV data-crb-p=""&gt;
&lt;DIV class="xFTqob"&gt;
&lt;DIV class="Gur8Ad"&gt;&lt;SPAN data-huuid="6423838145736348355"&gt;&lt;STRONG&gt;Display Functionality:&lt;/STRONG&gt; &lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="vM0jzc"&gt;&lt;SPAN data-huuid="6423838145736348404"&gt;Verify that both displays are working correctly after the system boots into Android, and that you can interact with the system on both.&lt;SPAN class="pjBG2e" data-cid="692968a1-84e8-438b-b4bf-abe55a66fd8c"&gt;&lt;SPAN class="UV3uM"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;DIV class="NPrrbc" data-cid="692968a1-84e8-438b-b4bf-abe55a66fd8c" data-uuids="6423838145736348355,6423838145736348404"&gt;
&lt;DIV class="BMebGe btku5b fCrZyc LwdV0e FR7ZSc qVhvac OJeuxf" tabindex="0" role="button" aria-label="Ver vínculos relacionados" data-hveid="CFEQAQ" data-ved="2ahUKEwiEvu32-aqOAxUZ5ckDHRJGJfoQ3fYKegQIURAB"&gt;
&lt;DIV class="niO4u"&gt;
&lt;DIV class="kHtcsd"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="kHtcsd"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="kHtcsd"&gt;Regards&lt;/DIV&gt;
&lt;DIV class="kHtcsd"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV data-crb-p=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV data-crb-p=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2" style="animation: none !important;"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="WaaZC"&gt;
&lt;DIV class="RJPOee EIJn2"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Mon, 07 Jul 2025 14:28:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Required-Boot-animation-shows-in-multiple-display/m-p/2129389#M239048</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2025-07-07T14:28:33Z</dc:date>
    </item>
    <item>
      <title>Re: Required Boot animation shows in multiple display</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Required-Boot-animation-shows-in-multiple-display/m-p/2132766#M239215</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/34846"&gt;@Bio_TICFSL&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your support but the issue is different. We are working on&amp;nbsp;&lt;SPAN&gt;"enabling the Multiple-Display" and we have implemented this feature successfully. The problem here is that we are getting&amp;nbsp;Android boot animation in main display (DSI MIPI) but in LVDS display&amp;nbsp;Android boot animation is not coming and directly home screen is appearing after booting completion.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Here I need to get the Android boot animation in both displays. How can I get the solution for this?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 12 Jul 2025 09:18:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Required-Boot-animation-shows-in-multiple-display/m-p/2132766#M239215</guid>
      <dc:creator>Manoj_Kumar</dc:creator>
      <dc:date>2025-07-12T09:18:22Z</dc:date>
    </item>
    <item>
      <title>Re: Required Boot animation shows in multiple display</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Required-Boot-animation-shows-in-multiple-display/m-p/2144874#M239761</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/34846"&gt;@Bio_TICFSL&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please help us to solve this problem?&lt;/P&gt;</description>
      <pubDate>Fri, 01 Aug 2025 04:34:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Required-Boot-animation-shows-in-multiple-display/m-p/2144874#M239761</guid>
      <dc:creator>Manoj_Kumar</dc:creator>
      <dc:date>2025-08-01T04:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: Required Boot animation shows in multiple display</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Required-Boot-animation-shows-in-multiple-display/m-p/2146619#M239849</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/34846"&gt;@Bio_TICFSL&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kindly provide a solution for this issue at your earliest convenience. We have been awaiting your response for quite some time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Manoj kumar&lt;/P&gt;</description>
      <pubDate>Tue, 05 Aug 2025 06:30:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Required-Boot-animation-shows-in-multiple-display/m-p/2146619#M239849</guid>
      <dc:creator>Manoj_Kumar</dc:creator>
      <dc:date>2025-08-05T06:30:22Z</dc:date>
    </item>
  </channel>
</rss>

