<?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>i.MX Processors中的主题 Re: IMX8QX memory overlap and VPU init fail</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/IMX8QX-memory-overlap-and-VPU-init-fail/m-p/1303495#M176489</link>
    <description>&lt;P&gt;what imx8qxp board version do you use? c0 or B0? did this demo images booting up? or your own built images?pls share with more detailed information&lt;/P&gt;</description>
    <pubDate>Wed, 07 Jul 2021 02:36:30 GMT</pubDate>
    <dc:creator>joanxie</dc:creator>
    <dc:date>2021-07-07T02:36:30Z</dc:date>
    <item>
      <title>IMX8QX memory overlap and VPU init fail</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX8QX-memory-overlap-and-VPU-init-fail/m-p/1299659#M176183</link>
      <description>&lt;P&gt;Hi nxp,&lt;/P&gt;&lt;P&gt;In kernel 5.10.35, I found log&amp;nbsp;&lt;/P&gt;&lt;P&gt;[ 0.000000] efi: UEFI not found.&lt;BR /&gt;[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'm4@0x88000000': base 0x0000000088000000, size 128 MiB&lt;BR /&gt;[ 0.000000] OF: reserved mem: OVERLAP DETECTED!&lt;BR /&gt;[ 0.000000] vdev0vring0@90000000 (0x0000000090000000--0x0000000090008000) overlaps with rsc_table@90000000 (0x0000000090000000--0x0000000090008000)&lt;BR /&gt;[ 0.000000] Reserved memory: created CMA memory pool at 0x00000000c0000000, size 960 MiB&lt;BR /&gt;[ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool&lt;BR /&gt;[ 0.000000] Reserved memory: created DMA memory pool at 0x0000000090400000, size 1 MiB&lt;BR /&gt;[ 0.000000] OF: reserved mem: initialized node vdevbuffer, compatible id shared-dma-pool&lt;BR /&gt;[ 0.000000] earlycon: lpuart32 at MMIO32 0x000000005a060000 (options '')&lt;BR /&gt;[ 0.000000] printk: bootconsole [lpuart32] enabled&lt;BR /&gt;[ 0.000000] NUMA: No NUMA configuration found&lt;BR /&gt;[ 0.000000] NUMA: Faking a node at [mem 0x0000000080200000-0x00000000ffffffff]&lt;BR /&gt;[ 0.000000] NUMA: NODE_DATA [mem 0xffbc1700-0xffbc3fff]&lt;BR /&gt;[ 0.000000] Zone ranges:&lt;BR /&gt;[ 0.000000] DMA [mem 0x0000000080200000-0x00000000ffffffff]&lt;BR /&gt;[ 0.000000] DMA32 empty&lt;BR /&gt;[ 0.000000] Normal empty&lt;BR /&gt;[ 0.000000] Movable zone start for each node&lt;BR /&gt;[ 0.000000] Early memory node ranges&lt;BR /&gt;[ 0.000000] node 0: [mem 0x0000000080200000-0x0000000083ffffff]&lt;BR /&gt;[ 0.000000] node 0: [mem 0x0000000084000000-0x00000000861fffff]&lt;BR /&gt;[ 0.000000] node 0: [mem 0x0000000086200000-0x000000008fffffff]&lt;BR /&gt;[ 0.000000] node 0: [mem 0x0000000090000000-0x000000009001ffff]&lt;BR /&gt;[ 0.000000] node 0: [mem 0x0000000090020000-0x00000000900fefff]&lt;BR /&gt;[ 0.000000] node 0: [mem 0x00000000900ff000-0x00000000900fffff]&lt;BR /&gt;[ 0.000000] node 0: [mem 0x0000000090100000-0x00000000901fffff]&lt;BR /&gt;[ 0.000000] node 0: [mem 0x0000000090200000-0x00000000904fffff]&lt;BR /&gt;[ 0.000000] node 0: [mem 0x0000000090500000-0x0000000091ffffff]&lt;BR /&gt;[ 0.000000] node 0: [mem 0x0000000092000000-0x0000000094bfffff]&lt;BR /&gt;[ 0.000000] node 0: [mem 0x0000000094c00000-0x00000000ffffffff]&lt;BR /&gt;[ 0.000000] Initmem setup node 0 [mem 0x0000000080200000-0x00000000ffffffff]&lt;BR /&gt;[ 0.000000] psci: probing for conduit method from DT.&lt;BR /&gt;[ 0.000000] psci: PSCIv1.1 detected in firmware.&lt;BR /&gt;[ 0.000000] psci: Using standard PSCI v0.2 function IDs&lt;BR /&gt;[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.&lt;BR /&gt;[ 0.000000] psci: SMC Calling Convention v1.1&lt;BR /&gt;[ 0.000000] percpu: Embedded 25 pages/cpu s62104 r8192 d32104 u102400&lt;BR /&gt;[ 0.000000] Detected VIPT I-cache on CPU0&lt;BR /&gt;[ 0.000000] CPU features: detected: GIC system register CPU interface&lt;BR /&gt;[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 515592&lt;BR /&gt;[ 0.000000] Policy zone: DMA&lt;/P&gt;&lt;P&gt;and in DTB file is&lt;/P&gt;&lt;P&gt;reserved-memory {&lt;BR /&gt;#address-cells = &amp;lt;2&amp;gt;;&lt;BR /&gt;#size-cells = &amp;lt;2&amp;gt;;&lt;BR /&gt;ranges;&lt;/P&gt;&lt;P&gt;rsc_table: rsc_table@90000000 {&lt;BR /&gt;reg = &amp;lt;0 0x90000000 0 0x8000&amp;gt;;&lt;BR /&gt;no-map;&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;vdev0vring0: vdev0vring0@90000000 {&lt;BR /&gt;reg = &amp;lt;0 0x90000000 0 0x8000&amp;gt;;&lt;BR /&gt;no-map;&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;This config is correctly or not?&amp;nbsp;&lt;/P&gt;&lt;P&gt;And It make VPU init fail or not?&lt;/P&gt;&lt;P&gt;[ 1.825604] [VPU Decoder] warning: init rtx channel failed, ret: -517&lt;BR /&gt;[ 1.832119] [VPU Decoder] failed to request mailbox, ret = -517&lt;BR /&gt;[ 1.844521] [VPU Encoder] warning: init rtx channel failed, ret: -517&lt;BR /&gt;[ 1.851133] [VPU Encoder] fail to request mailbox, ret = -517&lt;BR /&gt;[ 5.048018] [VPU Encoder] enable mu for core[0]&lt;BR /&gt;[ 5.061240] [VPU Encoder] vpu encoder core[0] firmware version is 1.3.0&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jun 2021 11:21:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX8QX-memory-overlap-and-VPU-init-fail/m-p/1299659#M176183</guid>
      <dc:creator>thepnimit</dc:creator>
      <dc:date>2021-06-29T11:21:33Z</dc:date>
    </item>
    <item>
      <title>Re: IMX8QX memory overlap and VPU init fail</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX8QX-memory-overlap-and-VPU-init-fail/m-p/1303495#M176489</link>
      <description>&lt;P&gt;what imx8qxp board version do you use? c0 or B0? did this demo images booting up? or your own built images?pls share with more detailed information&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jul 2021 02:36:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX8QX-memory-overlap-and-VPU-init-fail/m-p/1303495#M176489</guid>
      <dc:creator>joanxie</dc:creator>
      <dc:date>2021-07-07T02:36:30Z</dc:date>
    </item>
    <item>
      <title>Re: IMX8QX memory overlap and VPU init fail</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX8QX-memory-overlap-and-VPU-init-fail/m-p/1303507#M176494</link>
      <description>&lt;P&gt;Hi&amp;nbsp;joanxie,&lt;/P&gt;&lt;P&gt;I use image from NXP official&amp;nbsp;LF_v5.10_2.0.0_images_IMX8QXPC0MEK.zip&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.nxp.com/webapp/Download?colCode=L5.10.35_2.0.0_MX8QXPC0&amp;amp;appType=license" target="_blank"&gt;https://www.nxp.com/webapp/Download?colCode=L5.10.35_2.0.0_MX8QXPC0&amp;amp;appType=license&lt;/A&gt;&lt;/P&gt;&lt;P&gt;my board chip's: B0&lt;/P&gt;&lt;P&gt;u-boot:&amp;nbsp;imx-boot-imx8qxpmek-sd.bin-flash&lt;/P&gt;&lt;P&gt;dtb:&amp;nbsp;imx8qxp-mek.dtb&lt;/P&gt;&lt;P&gt;Kernel image:&amp;nbsp;Image-imx8_all.bin&lt;/P&gt;&lt;P&gt;os:&amp;nbsp;imx-image-multimedia-imx8qxpc0mek.tar.bz2&lt;/P&gt;&lt;P&gt;dtb code I see in&amp;nbsp;&lt;A href="https://source.codeaurora.org/external/imx/linux-imx/tree/arch/arm64/boot/dts/freescale/imx8x-mek.dtsi?h=lf-5.10.y" target="_blank"&gt;https://source.codeaurora.org/external/imx/linux-imx/tree/arch/arm64/boot/dts/freescale/imx8x-mek.dtsi?h=lf-5.10.y&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jul 2021 02:51:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX8QX-memory-overlap-and-VPU-init-fail/m-p/1303507#M176494</guid>
      <dc:creator>thepnimit</dc:creator>
      <dc:date>2021-07-07T02:51:32Z</dc:date>
    </item>
    <item>
      <title>Re: IMX8QX memory overlap and VPU init fail</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX8QX-memory-overlap-and-VPU-init-fail/m-p/1317710#M177850</link>
      <description>&lt;P&gt;I have tested on my B0 board successfully, I attached the uuu.auto script, you can put it with your demo images, and use the command "uuu.exe uuu.auto" to download to the board and test again&lt;/P&gt;</description>
      <pubDate>Wed, 04 Aug 2021 04:16:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX8QX-memory-overlap-and-VPU-init-fail/m-p/1317710#M177850</guid>
      <dc:creator>joanxie</dc:creator>
      <dc:date>2021-08-04T04:16:26Z</dc:date>
    </item>
    <item>
      <title>Re: IMX8QX memory overlap and VPU init fail</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX8QX-memory-overlap-and-VPU-init-fail/m-p/1363513#M182279</link>
      <description>&lt;P&gt;I built an image for iMX8QM with the same kernel 5.10.35, and got the same warnings:&lt;/P&gt;&lt;P&gt;failed to reserve memory for node m4 and memory overlap.&lt;/P&gt;&lt;P&gt;Not sure if "failed to reserve memory for node m4" will impact the Cortex-M4 and the FPU operations, such as camera or audio?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'm4@0x88000000': base 0x0000000088000000, size 128 MiB&lt;BR /&gt;[ 0.000000] OF: reserved mem: OVERLAP DETECTED!&lt;BR /&gt;[ 0.000000] vdev0vring0@90000000 (0x0000000090000000--0x0000000090008000) overlaps with rsc_table0@90000000 (0x0000000090000000--0x000)&lt;BR /&gt;[ 0.000000] OF: reserved mem: OVERLAP DETECTED!&lt;BR /&gt;[ 0.000000] vdev0vring0@90100000 (0x0000000090100000--0x0000000090108000) overlaps with rsc_table1@90100000 (0x0000000090100000--0x000)&lt;BR /&gt;[ 0.000000] Reserved memory: created CMA memory pool at 0x00000000c0000000, size 960 MiB&lt;BR /&gt;[ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool&lt;BR /&gt;[ 0.000000] Reserved memory: created DMA memory pool at 0x0000000090400000, size 1 MiB&lt;BR /&gt;[ 0.000000] OF: reserved mem: initialized node vdevbuffer, compatible id shared-dma-pool&lt;/P&gt;</description>
      <pubDate>Thu, 28 Oct 2021 23:19:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX8QX-memory-overlap-and-VPU-init-fail/m-p/1363513#M182279</guid>
      <dc:creator>lchen</dc:creator>
      <dc:date>2021-10-28T23:19:21Z</dc:date>
    </item>
  </channel>
</rss>

