<?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 Porting u-boot-imx, UUU issue in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Porting-u-boot-imx-UUU-issue/m-p/1752906#M215317</link>
    <description>&lt;P&gt;I recently ported the i.MX8MM EVK to our own board in u-boot-imx/added our own board, according to this thread:&amp;nbsp;&lt;A href="https://community.nxp.com/t5/i-MX-Processors/U-boot-porting-for-custom-board-based-on-imx8M-nano-processor/td-p/1479072" target="_self"&gt;U-boot porting for custom board based on imx8M nano processor&lt;/A&gt;&lt;/P&gt;&lt;P&gt;That was working well, but when I changed the files to our own vendor folder (e.g. board/{vendor}/imx8mm_evk/), u-boot doesn't compile anymore, complaining about&amp;nbsp;&lt;/P&gt;&lt;P&gt;/u-boot-imx/2022.04-r0/git/boot/image-android.c:195: undefined reference to `mmc_map_to_kernel_blk'&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I set CONFIG_ANDROID_BOOT_IMAGE=n, I can compile it, but get a segmentation fault when trying to flash that image to the emmc.&lt;/P&gt;</description>
    <pubDate>Mon, 06 Nov 2023 15:09:21 GMT</pubDate>
    <dc:creator>dpog</dc:creator>
    <dc:date>2023-11-06T15:09:21Z</dc:date>
    <item>
      <title>Porting u-boot-imx, UUU issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Porting-u-boot-imx-UUU-issue/m-p/1752906#M215317</link>
      <description>&lt;P&gt;I recently ported the i.MX8MM EVK to our own board in u-boot-imx/added our own board, according to this thread:&amp;nbsp;&lt;A href="https://community.nxp.com/t5/i-MX-Processors/U-boot-porting-for-custom-board-based-on-imx8M-nano-processor/td-p/1479072" target="_self"&gt;U-boot porting for custom board based on imx8M nano processor&lt;/A&gt;&lt;/P&gt;&lt;P&gt;That was working well, but when I changed the files to our own vendor folder (e.g. board/{vendor}/imx8mm_evk/), u-boot doesn't compile anymore, complaining about&amp;nbsp;&lt;/P&gt;&lt;P&gt;/u-boot-imx/2022.04-r0/git/boot/image-android.c:195: undefined reference to `mmc_map_to_kernel_blk'&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I set CONFIG_ANDROID_BOOT_IMAGE=n, I can compile it, but get a segmentation fault when trying to flash that image to the emmc.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Nov 2023 15:09:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Porting-u-boot-imx-UUU-issue/m-p/1752906#M215317</guid>
      <dc:creator>dpog</dc:creator>
      <dc:date>2023-11-06T15:09:21Z</dc:date>
    </item>
    <item>
      <title>Re: Porting u-boot-imx, UUU issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Porting-u-boot-imx-UUU-issue/m-p/1753120#M215331</link>
      <description>&lt;P&gt;Which version BSP are you using?&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 02:16:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Porting-u-boot-imx-UUU-issue/m-p/1753120#M215331</guid>
      <dc:creator>Rita_Wang</dc:creator>
      <dc:date>2023-11-07T02:16:42Z</dc:date>
    </item>
  </channel>
</rss>

