<?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 Real-time Edge yocto  -- IGH TEST in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Real-time-Edge-yocto-IGH-TEST/m-p/1863226#M223544</link>
    <description>&lt;P&gt;When I tested the IGH master station using the i.MX 8M Mini LPDDR4 EVK development board, I encountered the following issues. When master station MASTER0-DEVICE configured as “generic”，everything is normal，slave can be detected. However ,When master station MASTER0-DEVICE configured as “fec”&amp;nbsp;&amp;nbsp;but it cannot run. The experimental results are as follows.&lt;/P&gt;&lt;P&gt;root@imx8mm-lpddr4-evk:/# cat /etc/ethercat.conf&lt;BR /&gt;#------------------------------------------------------------------------------&lt;BR /&gt;#&lt;BR /&gt;# EtherCAT master configuration file for use with ethercatctl.&lt;BR /&gt;#&lt;BR /&gt;# $Id$&lt;BR /&gt;#&lt;BR /&gt;#------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Master devices.&lt;BR /&gt;#&lt;BR /&gt;# The MASTER&amp;lt;X&amp;gt;_DEVICE variable specifies the Ethernet device for a master&lt;BR /&gt;# with index 'X'.&lt;BR /&gt;#&lt;BR /&gt;# Specify the MAC address (hexadecimal with colons) of the Ethernet device to&lt;BR /&gt;# use. Example: "00:00:08:44:ab:66"&lt;BR /&gt;#&lt;BR /&gt;# The broadcast address "ff:ff:ff:ff:ff:ff" has a special meaning: It tells&lt;BR /&gt;# the master to accept the first device offered by any Ethernet driver.&lt;BR /&gt;#&lt;BR /&gt;# The MASTER&amp;lt;X&amp;gt;_DEVICE variables also determine, how many masters will be&lt;BR /&gt;# created: A non-empty variable MASTER0_DEVICE will create one master, adding a&lt;BR /&gt;# non-empty variable MASTER1_DEVICE will create a second master, and so on.&lt;BR /&gt;#&lt;BR /&gt;MASTER0_DEVICE="00:04:9f:06:1b:63"&lt;BR /&gt;#MASTER1_DEVICE=""&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Ethernet driver modules to use for EtherCAT operation.&lt;BR /&gt;#&lt;BR /&gt;# Specify a non-empty list of Ethernet drivers, that shall be used for EtherCAT&lt;BR /&gt;# operation.&lt;BR /&gt;#&lt;BR /&gt;# Except for the generic Ethernet driver module, the init script will try to&lt;BR /&gt;# unload the usual Ethernet driver modules in the list and replace them with&lt;BR /&gt;# the EtherCAT-capable ones. If a certain (EtherCAT-capable) driver is not&lt;BR /&gt;# found, a warning will appear.&lt;BR /&gt;#&lt;BR /&gt;# Possible values: 8139too, e100, e1000, e1000e, r8169, fec, enetc, dpaa1, generic.&lt;BR /&gt;# Separate multiple drivers with spaces.&lt;BR /&gt;#&lt;BR /&gt;# Note: The e100, e1000, e1000e, fec and r8169 drivers are not built by default.&lt;BR /&gt;# Enable them with the --enable-&amp;lt;driver&amp;gt; configure switches.&lt;BR /&gt;#&lt;BR /&gt;DEVICE_MODULES="generic"&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Flags for loading kernel modules.&lt;BR /&gt;#&lt;BR /&gt;# This can usually be left empty. Adjust this variable, if you have problems&lt;BR /&gt;# with module loading.&lt;BR /&gt;#&lt;BR /&gt;#MODPROBE_FLAGS="-b"&lt;/P&gt;&lt;P&gt;#------------------------------------------------------------------------------&lt;BR /&gt;root@imx8mm-lpddr4-evk:/# ethercat slaves&lt;BR /&gt;0 1:0 PREOP + IS620N_ECAT_v2.5.7&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When master station MASTER0-DEVICE configured as “fec” ,as flows&lt;/P&gt;&lt;P&gt;root@imx8mm-lpddr4-evk:~# cat /etc/ethercat.conf&lt;BR /&gt;#------------------------------------------------------------------------------&lt;BR /&gt;#&lt;BR /&gt;# EtherCAT master configuration file for use with ethercatctl.&lt;BR /&gt;#&lt;BR /&gt;# $Id$&lt;BR /&gt;#&lt;BR /&gt;#------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Master devices.&lt;BR /&gt;#&lt;BR /&gt;# The MASTER&amp;lt;X&amp;gt;_DEVICE variable specifies the Ethernet device for a master&lt;BR /&gt;# with index 'X'.&lt;BR /&gt;#&lt;BR /&gt;# Specify the MAC address (hexadecimal with colons) of the Ethernet device to&lt;BR /&gt;# use. Example: "00:00:08:44:ab:66"&lt;BR /&gt;#&lt;BR /&gt;# The broadcast address "ff:ff:ff:ff:ff:ff" has a special meaning: It tells&lt;BR /&gt;# the master to accept the first device offered by any Ethernet driver.&lt;BR /&gt;#&lt;BR /&gt;# The MASTER&amp;lt;X&amp;gt;_DEVICE variables also determine, how many masters will be&lt;BR /&gt;# created: A non-empty variable MASTER0_DEVICE will create one master, adding a&lt;BR /&gt;# non-empty variable MASTER1_DEVICE will create a second master, and so on.&lt;BR /&gt;#&lt;BR /&gt;MASTER0_DEVICE="00:04:9f:06:1b:63"&lt;BR /&gt;#MASTER1_DEVICE=""&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Ethernet driver modules to use for EtherCAT operation.&lt;BR /&gt;#&lt;BR /&gt;# Specify a non-empty list of Ethernet drivers, that shall be used for EtherCAT&lt;BR /&gt;# operation.&lt;BR /&gt;#&lt;BR /&gt;# Except for the generic Ethernet driver module, the init script will try to&lt;BR /&gt;# unload the usual Ethernet driver modules in the list and replace them with&lt;BR /&gt;# the EtherCAT-capable ones. If a certain (EtherCAT-capable) driver is not&lt;BR /&gt;# found, a warning will appear.&lt;BR /&gt;#&lt;BR /&gt;# Possible values: 8139too, e100, e1000, e1000e, r8169, fec, enetc, dpaa1, generic.&lt;BR /&gt;# Separate multiple drivers with spaces.&lt;BR /&gt;#&lt;BR /&gt;# Note: The e100, e1000, e1000e, fec and r8169 drivers are not built by default.&lt;BR /&gt;# Enable them with the --enable-&amp;lt;driver&amp;gt; configure switches.&lt;BR /&gt;#&lt;BR /&gt;DEVICE_MODULES="fec"&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Flags for loading kernel modules.&lt;BR /&gt;#&lt;BR /&gt;# This can usually be left empty. Adjust this variable, if you have problems&lt;BR /&gt;# with module loading.&lt;BR /&gt;#&lt;BR /&gt;#MODPROBE_FLAGS="-b"&lt;/P&gt;&lt;P&gt;#------------------------------------------------------------------------------&lt;BR /&gt;root@imx8mm-lpddr4-evk:~# ethercat slaves&lt;BR /&gt;&lt;A href="mailto:root@imx8mm-lpddr4-evk:~" target="_blank"&gt;root@imx8mm-lpddr4-evk:~#&lt;/A&gt;&lt;/P&gt;&lt;P&gt;no servo driver is detected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 10 May 2024 08:02:22 GMT</pubDate>
    <dc:creator>lanxiqing</dc:creator>
    <dc:date>2024-05-10T08:02:22Z</dc:date>
    <item>
      <title>Real-time Edge yocto  -- IGH TEST</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Real-time-Edge-yocto-IGH-TEST/m-p/1863226#M223544</link>
      <description>&lt;P&gt;When I tested the IGH master station using the i.MX 8M Mini LPDDR4 EVK development board, I encountered the following issues. When master station MASTER0-DEVICE configured as “generic”，everything is normal，slave can be detected. However ,When master station MASTER0-DEVICE configured as “fec”&amp;nbsp;&amp;nbsp;but it cannot run. The experimental results are as follows.&lt;/P&gt;&lt;P&gt;root@imx8mm-lpddr4-evk:/# cat /etc/ethercat.conf&lt;BR /&gt;#------------------------------------------------------------------------------&lt;BR /&gt;#&lt;BR /&gt;# EtherCAT master configuration file for use with ethercatctl.&lt;BR /&gt;#&lt;BR /&gt;# $Id$&lt;BR /&gt;#&lt;BR /&gt;#------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Master devices.&lt;BR /&gt;#&lt;BR /&gt;# The MASTER&amp;lt;X&amp;gt;_DEVICE variable specifies the Ethernet device for a master&lt;BR /&gt;# with index 'X'.&lt;BR /&gt;#&lt;BR /&gt;# Specify the MAC address (hexadecimal with colons) of the Ethernet device to&lt;BR /&gt;# use. Example: "00:00:08:44:ab:66"&lt;BR /&gt;#&lt;BR /&gt;# The broadcast address "ff:ff:ff:ff:ff:ff" has a special meaning: It tells&lt;BR /&gt;# the master to accept the first device offered by any Ethernet driver.&lt;BR /&gt;#&lt;BR /&gt;# The MASTER&amp;lt;X&amp;gt;_DEVICE variables also determine, how many masters will be&lt;BR /&gt;# created: A non-empty variable MASTER0_DEVICE will create one master, adding a&lt;BR /&gt;# non-empty variable MASTER1_DEVICE will create a second master, and so on.&lt;BR /&gt;#&lt;BR /&gt;MASTER0_DEVICE="00:04:9f:06:1b:63"&lt;BR /&gt;#MASTER1_DEVICE=""&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Ethernet driver modules to use for EtherCAT operation.&lt;BR /&gt;#&lt;BR /&gt;# Specify a non-empty list of Ethernet drivers, that shall be used for EtherCAT&lt;BR /&gt;# operation.&lt;BR /&gt;#&lt;BR /&gt;# Except for the generic Ethernet driver module, the init script will try to&lt;BR /&gt;# unload the usual Ethernet driver modules in the list and replace them with&lt;BR /&gt;# the EtherCAT-capable ones. If a certain (EtherCAT-capable) driver is not&lt;BR /&gt;# found, a warning will appear.&lt;BR /&gt;#&lt;BR /&gt;# Possible values: 8139too, e100, e1000, e1000e, r8169, fec, enetc, dpaa1, generic.&lt;BR /&gt;# Separate multiple drivers with spaces.&lt;BR /&gt;#&lt;BR /&gt;# Note: The e100, e1000, e1000e, fec and r8169 drivers are not built by default.&lt;BR /&gt;# Enable them with the --enable-&amp;lt;driver&amp;gt; configure switches.&lt;BR /&gt;#&lt;BR /&gt;DEVICE_MODULES="generic"&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Flags for loading kernel modules.&lt;BR /&gt;#&lt;BR /&gt;# This can usually be left empty. Adjust this variable, if you have problems&lt;BR /&gt;# with module loading.&lt;BR /&gt;#&lt;BR /&gt;#MODPROBE_FLAGS="-b"&lt;/P&gt;&lt;P&gt;#------------------------------------------------------------------------------&lt;BR /&gt;root@imx8mm-lpddr4-evk:/# ethercat slaves&lt;BR /&gt;0 1:0 PREOP + IS620N_ECAT_v2.5.7&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When master station MASTER0-DEVICE configured as “fec” ,as flows&lt;/P&gt;&lt;P&gt;root@imx8mm-lpddr4-evk:~# cat /etc/ethercat.conf&lt;BR /&gt;#------------------------------------------------------------------------------&lt;BR /&gt;#&lt;BR /&gt;# EtherCAT master configuration file for use with ethercatctl.&lt;BR /&gt;#&lt;BR /&gt;# $Id$&lt;BR /&gt;#&lt;BR /&gt;#------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Master devices.&lt;BR /&gt;#&lt;BR /&gt;# The MASTER&amp;lt;X&amp;gt;_DEVICE variable specifies the Ethernet device for a master&lt;BR /&gt;# with index 'X'.&lt;BR /&gt;#&lt;BR /&gt;# Specify the MAC address (hexadecimal with colons) of the Ethernet device to&lt;BR /&gt;# use. Example: "00:00:08:44:ab:66"&lt;BR /&gt;#&lt;BR /&gt;# The broadcast address "ff:ff:ff:ff:ff:ff" has a special meaning: It tells&lt;BR /&gt;# the master to accept the first device offered by any Ethernet driver.&lt;BR /&gt;#&lt;BR /&gt;# The MASTER&amp;lt;X&amp;gt;_DEVICE variables also determine, how many masters will be&lt;BR /&gt;# created: A non-empty variable MASTER0_DEVICE will create one master, adding a&lt;BR /&gt;# non-empty variable MASTER1_DEVICE will create a second master, and so on.&lt;BR /&gt;#&lt;BR /&gt;MASTER0_DEVICE="00:04:9f:06:1b:63"&lt;BR /&gt;#MASTER1_DEVICE=""&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Ethernet driver modules to use for EtherCAT operation.&lt;BR /&gt;#&lt;BR /&gt;# Specify a non-empty list of Ethernet drivers, that shall be used for EtherCAT&lt;BR /&gt;# operation.&lt;BR /&gt;#&lt;BR /&gt;# Except for the generic Ethernet driver module, the init script will try to&lt;BR /&gt;# unload the usual Ethernet driver modules in the list and replace them with&lt;BR /&gt;# the EtherCAT-capable ones. If a certain (EtherCAT-capable) driver is not&lt;BR /&gt;# found, a warning will appear.&lt;BR /&gt;#&lt;BR /&gt;# Possible values: 8139too, e100, e1000, e1000e, r8169, fec, enetc, dpaa1, generic.&lt;BR /&gt;# Separate multiple drivers with spaces.&lt;BR /&gt;#&lt;BR /&gt;# Note: The e100, e1000, e1000e, fec and r8169 drivers are not built by default.&lt;BR /&gt;# Enable them with the --enable-&amp;lt;driver&amp;gt; configure switches.&lt;BR /&gt;#&lt;BR /&gt;DEVICE_MODULES="fec"&lt;/P&gt;&lt;P&gt;#&lt;BR /&gt;# Flags for loading kernel modules.&lt;BR /&gt;#&lt;BR /&gt;# This can usually be left empty. Adjust this variable, if you have problems&lt;BR /&gt;# with module loading.&lt;BR /&gt;#&lt;BR /&gt;#MODPROBE_FLAGS="-b"&lt;/P&gt;&lt;P&gt;#------------------------------------------------------------------------------&lt;BR /&gt;root@imx8mm-lpddr4-evk:~# ethercat slaves&lt;BR /&gt;&lt;A href="mailto:root@imx8mm-lpddr4-evk:~" target="_blank"&gt;root@imx8mm-lpddr4-evk:~#&lt;/A&gt;&lt;/P&gt;&lt;P&gt;no servo driver is detected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 08:02:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Real-time-Edge-yocto-IGH-TEST/m-p/1863226#M223544</guid>
      <dc:creator>lanxiqing</dc:creator>
      <dc:date>2024-05-10T08:02:22Z</dc:date>
    </item>
    <item>
      <title>Re: Real-time Edge yocto  -- IGH TEST</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Real-time-Edge-yocto-IGH-TEST/m-p/1863509#M223566</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You are missconfigured the ethernet, make sure you have fec in your image.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 13:26:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Real-time-Edge-yocto-IGH-TEST/m-p/1863509#M223566</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2024-05-10T13:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: Real-time Edge yocto  -- IGH TEST</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Real-time-Edge-yocto-IGH-TEST/m-p/1863725#M223581</link>
      <description>&lt;P&gt;As described in the document “ Real-time Edge Software User Guide”&lt;/P&gt;&lt;P&gt;&lt;EM&gt;The native Ethernet driver "ec_fec" is enabled on Real-time Edge images by default for i.MX 8M Mini&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;LPDDR4 EVK. And it can be specified by setting "DEVICE_MODULES" variable to "fec" as below on "/etc/&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;ethercat.conf" file.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DEVICE_MODULES="fec"&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;But note that the original Ethernet fec driver must be compiled to modules by reconfiguring Linux menuconfig&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;when the native Ethernet driver "ec_fec" is enabled. On Real-time Edge, the original fec Ethernet driver has&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;been configured as a module by default.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Do you mean that the fec driver is compiled into the kernel, rather than being compiled into a module that automatically loads at startup?&lt;/P&gt;&lt;P&gt;At present, the fec driver should be compiled into modules.&lt;/P&gt;&lt;P&gt;root@imx8mm-lpddr4-evk:~# lsmod&lt;BR /&gt;Module Size Used by&lt;BR /&gt;ec_fec 45056 0&lt;BR /&gt;ec_master 274432 1 ec_fec&lt;BR /&gt;overlay 122880 0&lt;BR /&gt;fsl_jr_uio 16384 0&lt;BR /&gt;caam_jr 176128 0&lt;BR /&gt;caamkeyblob_desc 16384 1 caam_jr&lt;BR /&gt;caamhash_desc 16384 1 caam_jr&lt;BR /&gt;caamalg_desc 36864 1 caam_jr&lt;BR /&gt;crypto_engine 20480 1 caam_jr&lt;BR /&gt;authenc 16384 1 caam_jr&lt;BR /&gt;libdes 24576 1 caam_jr&lt;BR /&gt;crct10dif_ce 16384 1&lt;BR /&gt;polyval_ce 16384 0&lt;BR /&gt;polyval_generic 16384 1 polyval_ce&lt;BR /&gt;snd_soc_imx_spdif 16384 0&lt;BR /&gt;snd_soc_imx_card 20480 0&lt;BR /&gt;snd_soc_ak4458 24576 0&lt;BR /&gt;snd_soc_ak5558 28672 0&lt;BR /&gt;caam 28672 1 caam_jr&lt;BR /&gt;secvio 20480 0&lt;BR /&gt;error 24576 7 caamalg_desc,secvio,caamkeyblob_desc,caamhash_desc,caam,caam_jr,fsl_jr_uio&lt;BR /&gt;snd_soc_fsl_micfil 24576 2&lt;BR /&gt;snd_soc_fsl_spdif 24576 2&lt;BR /&gt;snd_soc_fsl_sai 36864 4&lt;BR /&gt;snd_soc_fsl_utils 16384 3 snd_soc_fsl_spdif,snd_soc_fsl_micfil,snd_soc_fsl_sai&lt;BR /&gt;gpio_ir_recv 16384 0&lt;BR /&gt;rc_core 36864 2 gpio_ir_recv&lt;BR /&gt;fuse 135168 1&lt;/P&gt;</description>
      <pubDate>Sat, 11 May 2024 01:01:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Real-time-Edge-yocto-IGH-TEST/m-p/1863725#M223581</guid>
      <dc:creator>lanxiqing</dc:creator>
      <dc:date>2024-05-11T01:01:49Z</dc:date>
    </item>
    <item>
      <title>Re: Real-time Edge yocto  -- IGH TEST</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Real-time-Edge-yocto-IGH-TEST/m-p/1863971#M223602</link>
      <description>&lt;P&gt;Using the official image of IMX8 MINI, the fec module has started running, but the main station still hasn't started and has been waiting for the device.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;root@imx8mm-lpddr4-evk:~# ethercatctl restart&lt;BR /&gt;[ 30.905175] ec_master: loading out-of-tree module taints kernel.&lt;BR /&gt;[ 30.908677] EtherCAT: Master driver 1.5.2 unknown&lt;BR /&gt;[ 30.908995] EtherCAT: 1 master waiting for devices.&lt;BR /&gt;root@imx8mm-lpddr4-evk:~# ethercat master&lt;BR /&gt;Master0&lt;BR /&gt;Phase: Waiting for device(s)...&lt;BR /&gt;Active: no&lt;BR /&gt;Slaves: 0&lt;BR /&gt;Ethernet devices:&lt;BR /&gt;Main: 00:01:02:03:04:06 (waiting...)&lt;BR /&gt;Link: DOWN&lt;BR /&gt;Tx frames: 0&lt;BR /&gt;Tx bytes: 0&lt;BR /&gt;Rx frames: 0&lt;BR /&gt;Rx bytes: 0&lt;BR /&gt;Tx errors: 0&lt;BR /&gt;Tx frame rate [1/s]: 0 0 0&lt;BR /&gt;Tx rate [KByte/s]: 0.0 0.0 0.0&lt;BR /&gt;Rx frame rate [1/s]: 0 0 0&lt;BR /&gt;Rx rate [KByte/s]: 0.0 0.0 0.0&lt;BR /&gt;Common:&lt;BR /&gt;Tx frames: 0&lt;BR /&gt;Tx bytes: 0&lt;BR /&gt;Rx frames: 0&lt;BR /&gt;Rx bytes: 0&lt;BR /&gt;Lost frames: 0&lt;BR /&gt;Tx frame rate [1/s]: 0 0 0&lt;BR /&gt;Tx rate [KByte/s]: 0.0 0.0 0.0&lt;BR /&gt;Rx frame rate [1/s]: 0 0 0&lt;BR /&gt;Rx rate [KByte/s]: 0.0 0.0 0.0&lt;BR /&gt;Loss rate [1/s]: 0 0 0&lt;BR /&gt;Frame loss [%]: 0.0 0.0 0.0&lt;BR /&gt;Distributed clocks:&lt;BR /&gt;Reference clock: None&lt;BR /&gt;Application time: 0&lt;BR /&gt;2000-01-01 00:00:00.000000000&lt;BR /&gt;root@imx8mm-lpddr4-evk:~# lsmod&lt;BR /&gt;Module Size Used by&lt;BR /&gt;ec_fec 45056 0&lt;BR /&gt;ec_master 274432 1 ec_fec&lt;BR /&gt;overlay 122880 0&lt;BR /&gt;fsl_jr_uio 16384 0&lt;BR /&gt;caam_jr 176128 0&lt;BR /&gt;caamkeyblob_desc 16384 1 caam_jr&lt;BR /&gt;caamhash_desc 16384 1 caam_jr&lt;BR /&gt;caamalg_desc 36864 1 caam_jr&lt;BR /&gt;crypto_engine 20480 1 caam_jr&lt;BR /&gt;authenc 16384 1 caam_jr&lt;BR /&gt;libdes 24576 1 caam_jr&lt;BR /&gt;crct10dif_ce 16384 1&lt;BR /&gt;polyval_ce 16384 0&lt;BR /&gt;polyval_generic 16384 1 polyval_ce&lt;BR /&gt;snd_soc_imx_spdif 16384 0&lt;BR /&gt;snd_soc_imx_card 20480 0&lt;BR /&gt;snd_soc_ak4458 24576 0&lt;BR /&gt;snd_soc_ak5558 28672 0&lt;BR /&gt;caam 28672 1 caam_jr&lt;BR /&gt;snd_soc_fsl_spdif 24576 2&lt;BR /&gt;snd_soc_fsl_micfil 24576 2&lt;BR /&gt;snd_soc_fsl_sai 36864 4&lt;BR /&gt;snd_soc_fsl_utils 16384 3 snd_soc_fsl_spdif,snd_soc_fsl_micfil,snd_soc_fsl_sai&lt;BR /&gt;secvio 20480 0&lt;BR /&gt;error 24576 7 caamalg_desc,secvio,caamkeyblob_desc,caamhash_desc,caam,caam_jr,fsl_jr_uio&lt;BR /&gt;gpio_ir_recv 16384 0&lt;BR /&gt;rc_core 36864 2 gpio_ir_recv&lt;BR /&gt;fuse 135168 1&lt;/P&gt;&lt;P&gt;Where is the possible reason? How to solve it?&lt;/P&gt;</description>
      <pubDate>Mon, 13 May 2024 03:00:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Real-time-Edge-yocto-IGH-TEST/m-p/1863971#M223602</guid>
      <dc:creator>lanxiqing</dc:creator>
      <dc:date>2024-05-13T03:00:52Z</dc:date>
    </item>
  </channel>
</rss>

