<?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: Unable to load images onto imx8mm-evk in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Unable-to-load-images-onto-imx8mm-evk/m-p/1667744#M207443</link>
    <description>&lt;P&gt;Was an actual solution ever found or presented?&amp;nbsp; How does one disable typec and tcpc in uboot? (or the Kernel for that matter)&amp;nbsp; Its four year later, and the solution seems to have been "it works now" I have a custom board with the IMX8MP, and our linux guys (extremely limited BSP knowledge) are getting the error below when running uuu. UUU works fine up to this point. The board is setup for USB boot mode, and uuu finds the USB device and downloads uboot with no problem. But then, when uboot tries to (re) initialize USB so that uuu can continue with the script, it fails because it want to talk to the type c power controller before initializing USB.&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;tcpc_init: Can't find bus&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;setup_typec: tcpc port2 init failed, err=-22&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;tcpc_init: Can't find device id=0x50&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;setup_typec: tcpc port1 init failed, err=-19&lt;/FONT&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I should point out that 0x50 isn't even the correct address of the type c power controller on the IMX8MP MEK that we're based on, so the code is looking for the wrong device on the wrong I2C port, neither of which we actually have or need. It's just a basic USB mini connector, so the processor only sees the VBUS and the data pair. The IMX8MP doesn't even have an ID pin for OTG or DR unless you implement one as a GPIO. We only have the USB connector there for uuu flashing, and since uboot loads from uuu cleanly, we know the hardware is fine.&lt;/P&gt;</description>
    <pubDate>Mon, 12 Jun 2023 22:12:14 GMT</pubDate>
    <dc:creator>lcotten</dc:creator>
    <dc:date>2023-06-12T22:12:14Z</dc:date>
    <item>
      <title>Unable to load images onto imx8mm-evk</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unable-to-load-images-onto-imx8mm-evk/m-p/898552#M135607</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;H1 style="color: #646464; background-color: #ffffff; border: 0px; font-weight: 200; font-size: 2rem;"&gt;Has anybody ever had following problem?&lt;/H1&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;U-Boot SPL 2018.03-imx-linux-sumo-ritu+g72bb67f (May 16 2019 - 07:01:38 +0000)&lt;BR /&gt;power_bd71837_init&lt;BR /&gt;DDRINFO: start lpddr4 ddr init&lt;BR /&gt;DRAM PHY training for 3000MTS&lt;BR /&gt;check ddr4_pmu_train_imem code&lt;BR /&gt;check ddr4_pmu_train_imem code pass&lt;BR /&gt;check ddr4_pmu_train_dmem code&lt;BR /&gt;check ddr4_pmu_train_dmem code pass&lt;BR /&gt;Training PASS&lt;BR /&gt;DRAM PHY training for 3000MTS&lt;BR /&gt;check ddr4_pmu_train_imem code&lt;BR /&gt;check ddr4_pmu_train_imem code pass&lt;BR /&gt;check ddr4_pmu_train_dmem code&lt;BR /&gt;check ddr4_pmu_train_dmem code pass&lt;BR /&gt;Training PASS&lt;BR /&gt;DRAM PHY training for 400MTS&lt;BR /&gt;check ddr4_pmu_train_imem code&lt;BR /&gt;check ddr4_pmu_train_imem code pass&lt;BR /&gt;check ddr4_pmu_train_dmem code&lt;BR /&gt;check ddr4_pmu_train_dmem code pass&lt;BR /&gt;Training PASS&lt;BR /&gt;DRAM PHY training for 100MTS&lt;BR /&gt;check ddr4_pmu_train_imem code&lt;BR /&gt;check ddr4_pmu_train_imem code pass&lt;BR /&gt;check ddr4_pmu_train_dmem code&lt;BR /&gt;check ddr4_pmu_train_dmem code pass&lt;BR /&gt;Training PASS&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 USB SDP&lt;BR /&gt;SDP: initialize...&lt;BR /&gt;SDP: handle requests...&lt;BR /&gt;Downloading file of size 1042456 to 0x40400000... done&lt;BR /&gt;Jumping to header at 0x40400000&lt;BR /&gt;Header Tag is not an IMX image&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;U-Boot 2018.03-imx-linux-sumo-ritu+g72bb67f (May 16 2019 - 07:01:38 +0000)&lt;/P&gt;&lt;P&gt;CPU: Freescale i.MX8MMQL rev1.0 1800 MHz (running at 1200 MHz)&lt;BR /&gt;CPU: Commercial temperature grade (0C to 95C) at 51C&lt;BR /&gt;Reset cause: POR&lt;BR /&gt;Model: FSL i.MX8MM EVK board&lt;BR /&gt;DRAM: 2 GiB&lt;BR /&gt;tcpc_init: Can't find device id=0x52&lt;BR /&gt;setup_typec: tcpc port2 init failed, err=-19&lt;BR /&gt;tcpc_init: Can't find device id=0x50&lt;BR /&gt;setup_typec: tcpc port1 init failed, err=-19&lt;BR /&gt;MMC: FSL_SDHC: 0, FSL_SDHC: 1&lt;BR /&gt;Loading Environment from MMC... Card did not respond to voltage select!&lt;BR /&gt;*** Warning - No block device, using default environment&lt;/P&gt;&lt;P&gt;Failed (-5)&lt;BR /&gt;No panel detected: default to MIPI2HDMI&lt;BR /&gt;adv7535_init: Can't find device id=0x3d, on bus 1&lt;BR /&gt;Display: MIPI2HDMI (1920x1080)&lt;BR /&gt;Video: 1920x1080x24&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 d6451cc&lt;BR /&gt; - U-Boot 2018.03-imx-linux-sumo-ritu+g72bb67f&lt;/P&gt;&lt;P&gt;Card did not respond to voltage select!&lt;BR /&gt;Detect USB boot. Will enter fastboot mode!&lt;BR /&gt;Net: No ethernet found.&lt;BR /&gt;Fastboot: Normal&lt;BR /&gt;Boot from USB for mfgtools&lt;BR /&gt;Use default environment for mfgtools&lt;BR /&gt;Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot 0; fi;&lt;BR /&gt;Hit any key to stop autoboot: 0&lt;/P&gt;&lt;P&gt;## Checking Image at 43800000 ...&lt;BR /&gt;Unknown image format!&lt;BR /&gt;Run fastboot ...&lt;BR /&gt;dev_get_parent_platdata: null device&lt;BR /&gt;"Synchronous Abort" handler, esr 0x96000004&lt;BR /&gt;elr: 0000000040230944 lr : 0000000040230938 (reloc)&lt;BR /&gt;elr: 00000000bdf61944 lr : 00000000bdf61938&lt;BR /&gt;x0 : 0000000014000280 x1 : 00000000308900b4&lt;BR /&gt;x2 : 00000000bdf52460 x3 : 0000000000000001&lt;BR /&gt;x4 : 00000000ffffffff x5 : 0000000000000000&lt;BR /&gt;x6 : 00000000bc929220 x7 : 00000000ffffffd0&lt;BR /&gt;x8 : 0000000000000000 x9 : 0000000000000008&lt;BR /&gt;x10: 0060009000000200 x11: 00000000bd1225e0&lt;BR /&gt;x12: 0000000000000002 x13: 0000000000000004&lt;BR /&gt;x14: 00000000bc92960c x15: 0000000000000008&lt;BR /&gt;x16: 0000000000001080 x17: 0000000000000000&lt;BR /&gt;x18: 00000000bc930da0 x19: 0000000000000000&lt;BR /&gt;x20: 0000000000000001 x21: 00000000bc9292ff&lt;BR /&gt;x22: 0000000000000000 x23: 000000000000001d&lt;BR /&gt;x24: 0000000000000002 x25: 0000000000000001&lt;BR /&gt;x26: 0000000000000000 x27: 0000000000000000&lt;BR /&gt;x28: 00000000bd122700 x29: 00000000bc929230&lt;/P&gt;&lt;P&gt;Resetting CPU ...&lt;/P&gt;&lt;P&gt;resetting ...&lt;/P&gt;&lt;P&gt;U-Boot SPL 2018.03-imx-linux-sumo-ritu+g72bb67f (May 16 2019 - 07:01:38 +0000)&lt;BR /&gt;power_bd71837_init&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 May 2019 06:40:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unable-to-load-images-onto-imx8mm-evk/m-p/898552#M135607</guid>
      <dc:creator>nicklau</dc:creator>
      <dc:date>2019-05-17T06:40:54Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to load images onto imx8mm-evk</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unable-to-load-images-onto-imx8mm-evk/m-p/898553#M135608</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Disable the typec function in uboot&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 May 2019 09:28:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unable-to-load-images-onto-imx8mm-evk/m-p/898553#M135608</guid>
      <dc:creator>传策薛</dc:creator>
      <dc:date>2019-05-17T09:28:48Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to load images onto imx8mm-evk</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unable-to-load-images-onto-imx8mm-evk/m-p/898554#M135609</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;u-boot中的DTS给落下了，那天已经改好了。多谢！&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 May 2019 06:03:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unable-to-load-images-onto-imx8mm-evk/m-p/898554#M135609</guid>
      <dc:creator>nicklau</dc:creator>
      <dc:date>2019-05-20T06:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to load images onto imx8mm-evk</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unable-to-load-images-onto-imx8mm-evk/m-p/898555#M135610</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How to disable typec function in uboot?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Jun 2019 08:07:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unable-to-load-images-onto-imx8mm-evk/m-p/898555#M135610</guid>
      <dc:creator>jefferyli</dc:creator>
      <dc:date>2019-06-04T08:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to load images onto imx8mm-evk</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unable-to-load-images-onto-imx8mm-evk/m-p/1667744#M207443</link>
      <description>&lt;P&gt;Was an actual solution ever found or presented?&amp;nbsp; How does one disable typec and tcpc in uboot? (or the Kernel for that matter)&amp;nbsp; Its four year later, and the solution seems to have been "it works now" I have a custom board with the IMX8MP, and our linux guys (extremely limited BSP knowledge) are getting the error below when running uuu. UUU works fine up to this point. The board is setup for USB boot mode, and uuu finds the USB device and downloads uboot with no problem. But then, when uboot tries to (re) initialize USB so that uuu can continue with the script, it fails because it want to talk to the type c power controller before initializing USB.&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;tcpc_init: Can't find bus&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;setup_typec: tcpc port2 init failed, err=-22&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;tcpc_init: Can't find device id=0x50&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;setup_typec: tcpc port1 init failed, err=-19&lt;/FONT&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I should point out that 0x50 isn't even the correct address of the type c power controller on the IMX8MP MEK that we're based on, so the code is looking for the wrong device on the wrong I2C port, neither of which we actually have or need. It's just a basic USB mini connector, so the processor only sees the VBUS and the data pair. The IMX8MP doesn't even have an ID pin for OTG or DR unless you implement one as a GPIO. We only have the USB connector there for uuu flashing, and since uboot loads from uuu cleanly, we know the hardware is fine.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jun 2023 22:12:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unable-to-load-images-onto-imx8mm-evk/m-p/1667744#M207443</guid>
      <dc:creator>lcotten</dc:creator>
      <dc:date>2023-06-12T22:12:14Z</dc:date>
    </item>
  </channel>
</rss>

