<?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のトピックimx8qxpmek can device activation problem</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/imx8qxpmek-can-device-activation-problem/m-p/1152866#M161750</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I'm trying to activate can devices on my i.mx8qxp board. I'm using the command "bitbake -c menuconfig linux-imx" in order to make necessary changes to activate can function. But I can't see any can devices on the board. And some strange messages which are related to cpu frequencies and power management features also appear on dmesg command output. But those messages didn't appeared before can case.&lt;/P&gt;&lt;P&gt;Here are some of my yocto configuration details:&lt;/P&gt;&lt;P&gt;repo init -u &lt;A href="https://source.codeaurora.org/external/imx/imx-manifest" target="_blank"&gt;https://source.codeaurora.org/external/imx/imx-manifest&lt;/A&gt; -b imx-linux-zeus -m imx-5.4.24-2.1.0.xml&lt;/P&gt;&lt;P&gt;DISTRO=fsl-imx-wayland MACHINE=imx8qxpmek source imx-setup-release.sh -b build-wayland&lt;/P&gt;&lt;P&gt;bitbake fsl-image-qt5-validation-imx&lt;/P&gt;&lt;P&gt;Build Configuration:&lt;BR /&gt;BB_VERSION = "1.44.0"&lt;BR /&gt;BUILD_SYS = "x86_64-linux"&lt;BR /&gt;NATIVELSBSTRING = "ubuntu-18.04"&lt;BR /&gt;TARGET_SYS = "aarch64-poky-linux"&lt;BR /&gt;MACHINE = "imx8qxpmek"&lt;BR /&gt;DISTRO = "fsl-imx-wayland"&lt;BR /&gt;DISTRO_VERSION = "5.4-zeus"&lt;BR /&gt;TUNE_FEATURES = "aarch64 cortexa35 crc crypto"&lt;BR /&gt;TARGET_FPU = ""&lt;BR /&gt;---&lt;/P&gt;&lt;P&gt;a part of dmesg output:&lt;/P&gt;&lt;P&gt;[ 4963.628287] imx-scu-clk sdhc1_clk: genpd_runtime_suspend()&lt;BR /&gt;[ 4963.934577] imx8qxp-lpcg-clk 5b210000.clock-controller: genpd_runtime_suspend()&lt;BR /&gt;[ 4966.496753] cpu cpu0: dev_pm_opp_set_rate: switching OPP: 900000000 Hz --&amp;gt; 1200000000 Hz&lt;BR /&gt;[ 4966.497926] sdhci-esdhc-imx 5b020000.mmc: genpd_runtime_resume()&lt;BR /&gt;[ 4966.497994] imx8qxp-lpcg-clk 5b210000.clock-controller: genpd_runtime_resume()&lt;BR /&gt;[ 4966.498013] imx-scu-clk sdhc1_clk: genpd_runtime_resume()&lt;BR /&gt;[ 4966.506793] cpu cpu0: dev_pm_opp_set_rate: switching OPP: 1200000000 Hz --&amp;gt; 900000000 Hz&lt;BR /&gt;[ 4966.518749] cpu cpu0: dev_pm_opp_set_rate: switching OPP: 900000000 Hz --&amp;gt; 1200000000 Hz&lt;BR /&gt;[ 4966.566568] sdhci-esdhc-imx 5b020000.mmc: genpd_runtime_suspend()&lt;BR /&gt;[ 4966.566663] imx-scu-clk sdhc1_clk: genpd_runtime_suspend()&lt;BR /&gt;[ 4966.592597] sdhci-esdhc-imx 5b020000.mmc: genpd_runtime_resume()&lt;BR /&gt;[ 4966.592630] imx-scu-clk sdhc1_clk: genpd_runtime_resume()&lt;BR /&gt;[ 4966.626641] cpu cpu0: dev_pm_opp_set_rate: switching OPP: 1200000000 Hz --&amp;gt; 900000000 Hz&lt;BR /&gt;[ 4966.675862] sdhci-esdhc-imx 5b020000.mmc: genpd_runtime_suspend()&lt;BR /&gt;[ 4966.675956] imx-scu-clk sdhc1_clk: genpd_runtime_suspend()&lt;BR /&gt;[ 4967.058556] imx8qxp-lpcg-clk 5b210000.clock-controller: genpd_runtime_suspend()&lt;BR /&gt;[ 4968.122874] sdhci-esdhc-imx 5b020000.mmc: genpd_runtime_resume()&lt;BR /&gt;[ 4968.122942] imx8qxp-lpcg-clk 5b210000.clock-controller: genpd_runtime_resume()&lt;BR /&gt;[ 4968.122965] imx-scu-clk sdhc1_clk: genpd_runtime_resume()&lt;BR /&gt;[ 4968.188445] sdhci-esdhc-imx 5b020000.mmc: genpd_runtime_suspend()&lt;BR /&gt;[ 4968.188530] imx-scu-clk sdhc1_clk: genpd_runtime_suspend()&lt;BR /&gt;[ 4968.722560] imx8qxp-lpcg-clk 5b210000.clock-controller: genpd_runtime_suspend()&lt;BR /&gt;[ 4971.194537] imx-lpi2c 56246000.i2c: genpd_runtime_resume()&lt;BR /&gt;[ 4971.194586] imx8qxp-lpcg-clk 56243010.clock-controller: genpd_runtime_resume()&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Yusuf.&lt;/P&gt;</description>
    <pubDate>Mon, 14 Sep 2020 11:08:07 GMT</pubDate>
    <dc:creator>ykupeli</dc:creator>
    <dc:date>2020-09-14T11:08:07Z</dc:date>
    <item>
      <title>imx8qxpmek can device activation problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx8qxpmek-can-device-activation-problem/m-p/1152866#M161750</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I'm trying to activate can devices on my i.mx8qxp board. I'm using the command "bitbake -c menuconfig linux-imx" in order to make necessary changes to activate can function. But I can't see any can devices on the board. And some strange messages which are related to cpu frequencies and power management features also appear on dmesg command output. But those messages didn't appeared before can case.&lt;/P&gt;&lt;P&gt;Here are some of my yocto configuration details:&lt;/P&gt;&lt;P&gt;repo init -u &lt;A href="https://source.codeaurora.org/external/imx/imx-manifest" target="_blank"&gt;https://source.codeaurora.org/external/imx/imx-manifest&lt;/A&gt; -b imx-linux-zeus -m imx-5.4.24-2.1.0.xml&lt;/P&gt;&lt;P&gt;DISTRO=fsl-imx-wayland MACHINE=imx8qxpmek source imx-setup-release.sh -b build-wayland&lt;/P&gt;&lt;P&gt;bitbake fsl-image-qt5-validation-imx&lt;/P&gt;&lt;P&gt;Build Configuration:&lt;BR /&gt;BB_VERSION = "1.44.0"&lt;BR /&gt;BUILD_SYS = "x86_64-linux"&lt;BR /&gt;NATIVELSBSTRING = "ubuntu-18.04"&lt;BR /&gt;TARGET_SYS = "aarch64-poky-linux"&lt;BR /&gt;MACHINE = "imx8qxpmek"&lt;BR /&gt;DISTRO = "fsl-imx-wayland"&lt;BR /&gt;DISTRO_VERSION = "5.4-zeus"&lt;BR /&gt;TUNE_FEATURES = "aarch64 cortexa35 crc crypto"&lt;BR /&gt;TARGET_FPU = ""&lt;BR /&gt;---&lt;/P&gt;&lt;P&gt;a part of dmesg output:&lt;/P&gt;&lt;P&gt;[ 4963.628287] imx-scu-clk sdhc1_clk: genpd_runtime_suspend()&lt;BR /&gt;[ 4963.934577] imx8qxp-lpcg-clk 5b210000.clock-controller: genpd_runtime_suspend()&lt;BR /&gt;[ 4966.496753] cpu cpu0: dev_pm_opp_set_rate: switching OPP: 900000000 Hz --&amp;gt; 1200000000 Hz&lt;BR /&gt;[ 4966.497926] sdhci-esdhc-imx 5b020000.mmc: genpd_runtime_resume()&lt;BR /&gt;[ 4966.497994] imx8qxp-lpcg-clk 5b210000.clock-controller: genpd_runtime_resume()&lt;BR /&gt;[ 4966.498013] imx-scu-clk sdhc1_clk: genpd_runtime_resume()&lt;BR /&gt;[ 4966.506793] cpu cpu0: dev_pm_opp_set_rate: switching OPP: 1200000000 Hz --&amp;gt; 900000000 Hz&lt;BR /&gt;[ 4966.518749] cpu cpu0: dev_pm_opp_set_rate: switching OPP: 900000000 Hz --&amp;gt; 1200000000 Hz&lt;BR /&gt;[ 4966.566568] sdhci-esdhc-imx 5b020000.mmc: genpd_runtime_suspend()&lt;BR /&gt;[ 4966.566663] imx-scu-clk sdhc1_clk: genpd_runtime_suspend()&lt;BR /&gt;[ 4966.592597] sdhci-esdhc-imx 5b020000.mmc: genpd_runtime_resume()&lt;BR /&gt;[ 4966.592630] imx-scu-clk sdhc1_clk: genpd_runtime_resume()&lt;BR /&gt;[ 4966.626641] cpu cpu0: dev_pm_opp_set_rate: switching OPP: 1200000000 Hz --&amp;gt; 900000000 Hz&lt;BR /&gt;[ 4966.675862] sdhci-esdhc-imx 5b020000.mmc: genpd_runtime_suspend()&lt;BR /&gt;[ 4966.675956] imx-scu-clk sdhc1_clk: genpd_runtime_suspend()&lt;BR /&gt;[ 4967.058556] imx8qxp-lpcg-clk 5b210000.clock-controller: genpd_runtime_suspend()&lt;BR /&gt;[ 4968.122874] sdhci-esdhc-imx 5b020000.mmc: genpd_runtime_resume()&lt;BR /&gt;[ 4968.122942] imx8qxp-lpcg-clk 5b210000.clock-controller: genpd_runtime_resume()&lt;BR /&gt;[ 4968.122965] imx-scu-clk sdhc1_clk: genpd_runtime_resume()&lt;BR /&gt;[ 4968.188445] sdhci-esdhc-imx 5b020000.mmc: genpd_runtime_suspend()&lt;BR /&gt;[ 4968.188530] imx-scu-clk sdhc1_clk: genpd_runtime_suspend()&lt;BR /&gt;[ 4968.722560] imx8qxp-lpcg-clk 5b210000.clock-controller: genpd_runtime_suspend()&lt;BR /&gt;[ 4971.194537] imx-lpi2c 56246000.i2c: genpd_runtime_resume()&lt;BR /&gt;[ 4971.194586] imx8qxp-lpcg-clk 56243010.clock-controller: genpd_runtime_resume()&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Yusuf.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2020 11:08:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx8qxpmek-can-device-activation-problem/m-p/1152866#M161750</guid>
      <dc:creator>ykupeli</dc:creator>
      <dc:date>2020-09-14T11:08:07Z</dc:date>
    </item>
    <item>
      <title>Re: imx8qxpmek can device activation problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx8qxpmek-can-device-activation-problem/m-p/1153084#M161780</link>
      <description>&lt;P&gt;Hi ykupeli&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;can can be used by m4 (assigned to m4 partition), one can look at&lt;/P&gt;
&lt;P&gt;below link&amp;nbsp; "Modifying default configuration" and assign can interface to A core partition :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/System-Controller-Firmware-101-Resource-management-service/ta-p/1123227" target="_blank"&gt;https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/System-Controller-Firmware-101-Resource-management-service/ta-p/1123227&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2020 00:34:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx8qxpmek-can-device-activation-problem/m-p/1153084#M161780</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2020-09-15T00:34:36Z</dc:date>
    </item>
    <item>
      <title>Re: imx8qxpmek can device activation problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx8qxpmek-can-device-activation-problem/m-p/1153256#M161807</link>
      <description>&lt;P&gt;Hi Igor,&lt;/P&gt;&lt;P&gt;Thank you for your quick response. But I'm newbie to the imx platform. It's too diffucult for me to understand all those instructions at once. I can just use yocto platform in order to produce whole image for the platform. Are there any other easier instructions to follow that I can use with yocto for the case? Or any other examples to fix that?&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Yusuf.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2020 06:18:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx8qxpmek-can-device-activation-problem/m-p/1153256#M161807</guid>
      <dc:creator>ykupeli</dc:creator>
      <dc:date>2020-09-15T06:18:52Z</dc:date>
    </item>
  </channel>
</rss>

