<?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: Kernel crashed when power by USBC PD in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-crashed-when-power-by-USBC-PD/m-p/1498503#M193240</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/197016"&gt;@thanhle1990&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;From the logs, it seems that there is no crash in the kernel, but it is rebooting continuously.&lt;/P&gt;
&lt;P&gt;One possible reason can be improper power input. Due to insufficient power, the processor might get rebooted.&lt;/P&gt;
&lt;P&gt;Are you booting the processor with the pre-build images provided by the NXP, or are you using your custom images?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Dhruvit.&lt;/P&gt;</description>
    <pubDate>Fri, 05 Aug 2022 08:53:00 GMT</pubDate>
    <dc:creator>Dhruvit</dc:creator>
    <dc:date>2022-08-05T08:53:00Z</dc:date>
    <item>
      <title>Kernel crashed when power by USBC PD</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-crashed-when-power-by-USBC-PD/m-p/1488049#M192424</link>
      <description>&lt;P&gt;Hi support team,&lt;BR /&gt;I'm using the USBC PSU to power the iMX8MQ dev kit&amp;nbsp;&lt;BR /&gt;&lt;A href="https://www.amazon.com/Mackertop-Charger-Adapter-Latitude-Inspiron/dp/B07VV4HB1V" target="_blank" rel="noopener"&gt;https://www.amazon.com/Mackertop-Charger-Adapter-Latitude-Inspiron/dp/B07VV4HB1V&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Uboot was able to detect PD and boot kernel&lt;BR /&gt;&lt;BR /&gt;```&lt;/P&gt;&lt;P&gt;U-Boot 2020.04-5.4.24-2.1.0+g4979a99482 (Jun 22 2022 - 19:25:19 +0000)&lt;/P&gt;&lt;P&gt;CPU: i.MX8MQ rev2.1 1500 MHz (running at 1000 MHz)&lt;BR /&gt;CPU: Commercial temperature grade (0C to 95C) at 35C&lt;BR /&gt;Reset cause: POR&lt;BR /&gt;Model: NXP i.MX8MQ EVK&lt;BR /&gt;DRAM: 3 GiB&lt;BR /&gt;TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C0 0x50]&lt;BR /&gt;SNK.Power3.0 on CC2&lt;BR /&gt;PDO 0: type 0, 5000 mV, 3000 mA [DE]&lt;BR /&gt;PDO 1: type 0, 9000 mV, 3000 mA []&lt;BR /&gt;PDO 2: type 0, 15000 mV, 3000 mA []&lt;BR /&gt;PDO 3: type 0, 20000 mV, 2250 mA []&lt;BR /&gt;Requesting PDO 3: 20000 mV, 750 mA&lt;BR /&gt;Source accept request&lt;BR /&gt;PD source ready!&amp;nbsp;&amp;lt;============================ PD ready&lt;BR /&gt;tcpc_pd_receive_message: Polling ALERT register, TCPC_ALERT_RX_STATUS bit failed, ret = -62&lt;BR /&gt;MMC: FSL_SDHC: 0, FSL_SDHC: 1&lt;BR /&gt;Loading Environment from MMC... *** Warning - bad CRC, using default environment&lt;/P&gt;&lt;P&gt;[*]-Video Link 0imx8m_hdmi_probe&lt;BR /&gt;(1280 x 720)&lt;BR /&gt;[0] display-controller@32e00000, video&lt;BR /&gt;[1] hdmi@32c00000, display&lt;BR /&gt;In: serial&lt;BR /&gt;Out: serial&lt;BR /&gt;Err: serial&lt;/P&gt;&lt;P&gt;BuildInfo:&lt;BR /&gt;- ATF b0a00f2&lt;BR /&gt;- U-Boot 2020.04-5.4.24-2.1.0+g4979a99482&lt;/P&gt;&lt;P&gt;switch to partitions #0, OK&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;```&lt;/P&gt;&lt;P&gt;But the kernel was crashed&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;```&lt;/P&gt;&lt;P&gt;[ 2.982299] mmcblk0rpmb: mmc0:0001 DG4016 partition 3 4.00 MiB, chardev (237:0)&lt;BR /&gt;[ 3.053150] mmcblk0: p1 p2&lt;BR /&gt;[ 3.062677] [drm] Initialized vivante 1.0.0 20170808 for 38000000.gpu3d on minor 1&lt;BR /&gt;[ 3.073029] hantrodec: module inserted. Major = 236&lt;BR /&gt;[ 3.081941] debugfs: Directory '308c0000.sai' with parent 'bt-sco-audio' already present!&lt;BR /&gt;[ 3.090199] asoc-simple-card sound-bt-sco: bt-sco-pcm-wb &amp;lt;-&amp;gt; 308c0000.sai mapping ok&lt;BR /&gt;[ 3.097957] asoc-simple-card sound-bt-sco: ASoC: no DMI vendor name!&lt;BR /&gt;[ 3.104349] debugfs: File 'Playback' in directory 'dapm' already present!&lt;BR /&gt;[ 3.111143] debugfs: File 'Capture' in directory 'dapm' already present!&lt;BR /&gt;[ 3.121044] debugfs: Directory '308b0000.sai' with parent 'wm8524-audio' already present!&lt;BR /&gt;[ 3.129319] asoc-simple-card sound-wm8524: wm8524-hifi &amp;lt;-&amp;gt; 308b0000.sai mapping ok&lt;BR /&gt;[ 3.136921] asoc-simple-card sound-wm8524: ASoC: no DMI vendor name!&lt;BR /&gt;[ 3.149905] ak4458 2-0010: ASoC: failed to probe component -6&lt;BR /&gt;[ 3.155700] imx-ak4458 sound-ak4458: ASoC: failed to instantiate card -6&lt;BR /&gt;[ 3.162484] imx-ak4458 sound-ak4458: snd_soc_register_card failed (-6)&lt;BR /&gt;[ 3.170001] ak5558 2-0013: ASoC: failed to probe component -6&lt;BR /&gt;[ 3.175776] imx-ak5558 sound-ak5558: ASoC: failed to instantiate card -6&lt;BR /&gt;[ 3.182520] imx-ak5558 sound-ak5558: snd_soc_register_card failed (-6)&lt;BR /&gt;[ 3.189593] debugfs: Directory '30050000.sai' with parent 'imx-audio-hdmi' already present!&lt;BR /&gt;[ 3.198025] imx-cdnhdmi sound-hdmi: i2s-hifi &amp;lt;-&amp;gt; 30050000.sai mapping ok&lt;BR /&gt;[ 3.198784] random: fast init done&lt;BR /&gt;[ 3.204749] imx-cdnhdmi sound-hdmi: ASoC: no DMI vendor name!&lt;BR /&gt;[ 3.213913] debugfs: File 'Capture' in directory 'dapm' already present!&lt;BR /&gt;[ 3.221957] input: imx-audio-hdmi HDMI Jack as /devices/platform/sound-hdmi/sound/card4/input1&lt;BR /&gt;� &amp;lt;============================ CRASHED HERE&lt;BR /&gt;U-Boot SPL 2020.04-5.4.24-2.1.0+g4979a99482 (Jun 22 2022 - 19:25:19 +0000)&lt;BR /&gt;PMIC: PFUZE100 ID=0x10&lt;BR /&gt;DDRINFO: start DRAM init&lt;BR /&gt;DDRINFO: DRAM rate 3200MTS&lt;BR /&gt;DDRINFO:ddrphy calibration done&lt;BR /&gt;DDRINFO: ddrmix config done&lt;BR /&gt;Normal Boot&lt;BR /&gt;Trying to boot from MMC1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;U-Boot 2020.04-5.4.24-2.1.0+g4979a99482 (Jun 22 2022 - 19:25:19 +0000)&lt;/P&gt;&lt;P&gt;```&lt;/P&gt;&lt;P&gt;The issue did not happen if I use the PSU from the dev kit, could you please take a look.&lt;BR /&gt;Thank you&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jul 2022 10:31:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-crashed-when-power-by-USBC-PD/m-p/1488049#M192424</guid>
      <dc:creator>thanhle1990</dc:creator>
      <dc:date>2022-07-12T10:31:03Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel crashed when power by USBC PD</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-crashed-when-power-by-USBC-PD/m-p/1498503#M193240</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/197016"&gt;@thanhle1990&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;From the logs, it seems that there is no crash in the kernel, but it is rebooting continuously.&lt;/P&gt;
&lt;P&gt;One possible reason can be improper power input. Due to insufficient power, the processor might get rebooted.&lt;/P&gt;
&lt;P&gt;Are you booting the processor with the pre-build images provided by the NXP, or are you using your custom images?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Dhruvit.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 08:53:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-crashed-when-power-by-USBC-PD/m-p/1498503#M193240</guid>
      <dc:creator>Dhruvit</dc:creator>
      <dc:date>2022-08-05T08:53:00Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel crashed when power by USBC PD</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-crashed-when-power-by-USBC-PD/m-p/1499166#M193279</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;Dhruvit&lt;/P&gt;&lt;P&gt;As I had some investigation before, the issue ware caused by missing of power supply for HDMI.&amp;nbsp;&lt;BR /&gt;The power from USBC PD did not become the main power source, as I read from another post, USBC PD on this board was not designed for power supply, so I gave up the idea.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Aug 2022 03:11:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-crashed-when-power-by-USBC-PD/m-p/1499166#M193279</guid>
      <dc:creator>thanhle1990</dc:creator>
      <dc:date>2022-08-02T03:11:34Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel crashed when power by USBC PD</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-crashed-when-power-by-USBC-PD/m-p/1501700#M193488</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/197016"&gt;@thanhle1990&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As indicated in the Power topology (image attached below), After the VSYS is generated, there is a common power path going ahead in power sequence irrespective of the power source. So, DCDC_5V rail will be genrated in both the cases (DC jack power source or USB Type C power source).&lt;/P&gt;
&lt;DIV id="tinyMceEditorDhruvit_0" class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image.png" style="width: 217px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/189245i3C3EF3419628A19E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you.&lt;BR /&gt;Best Regards,&lt;BR /&gt;Dhruvit.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 08:55:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-crashed-when-power-by-USBC-PD/m-p/1501700#M193488</guid>
      <dc:creator>Dhruvit</dc:creator>
      <dc:date>2022-08-05T08:55:27Z</dc:date>
    </item>
  </channel>
</rss>

