Multi Source Translation Content

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Multi Source Translation Content

Discussions

Sort by:
SJA1110A DSA 上电:100BASE-TX TX 故障和 T1 链路培训问题 你好 我正在使用 Linux DSA 通过 SPI 将一个 SJA1110AEL 交换机连接到 Microchip PolarFire SoC 上 sja1105驱动程序,通过 SPI 将 SJA1110AEL 开关连接到 Microchip PolarFire SoC: https://github.com/linux4microchip/linux/tree/linux-6.12-mchp%2Bfpga/drivers/net/dsa/sja1105 交换机配置为 SPI 启动模式(BOOT_OPTION=11),静态配置上传看起来很成功。 [ 2.546758] sja1105 spi9.0: Probed switch chip: SJA1110A [ 2.546777] sja1105 spi9.0: max_xfer_len = 256 bytes [ 2.549576] sja1105 spi9.0: Config buffer length: 1776 bytes [ 2.549605] sja1105 spi9.0: Config buffer device_id at offset 0: 0x0f0300b7 [ 2.742531] sja1105 status decoded: CONFIGS=1 CRCCHKL=0 IDS=0 CRCCHKG=0 NSLOT=9 [ 2.742563] sja1105 spi9.0: sja1105_static_config_load done [ 2.742579] sja1105 spi9.0: sja1105_clocking done [ 2.742592] sja1105 spi9.0: sja1105_TAS and flower setup done [ 2.743823] sja1105 spi9.0: sja1105_ptp_clock_register done [ 2.888661] sja1105 spi9.0: sja1105_mdiobus_register done [ 2.888699] sja1105 spi9.0: sja1105_devlink_setup done [ 2.902778] sja1105 spi9.0: dsa_tag_8021q_register and rtnl_unlockdone [ 2.904141] sja1105 spi9.0: configuring for fixed/sgmii link mode [ 2.909745] sja1105 spi9.0: Link is Up - 1Gbps/Full - flow control off [ 2.964511] sja1105 spi9.0 rj45 (uninitialized): PHY [spi9.0-base-tx:01] driver [NXP CBTX (SJA1110)] (irq=POLL) [ 2.973125] sja1105 spi9.0 t1-1 (uninitialized): PHY [spi9.0-base-t1:01] driver [Generic Clause 45 PHY] (irq=POLL) [ 2.976322] sja1105 spi9.0 t1-2 (uninitialized): PHY [spi9.0-base-t1:02] driver [Generic Clause 45 PHY] (irq=POLL) [ 2.979382] sja1105 spi9.0 t1-3 (uninitialized): PHY [spi9.0-base-t1:03] driver [Generic Clause 45 PHY] (irq=POLL) [ 2.982622] sja1105 spi9.0 t1-4 (uninitialized): PHY [spi9.0-base-t1:04] driver [Generic Clause 45 PHY] (irq=POLL) [ 2.985855] sja1105 spi9.0 t1-5 (uninitialized): PHY [spi9.0-base-t1:05] driver [Generic Clause 45 PHY] (irq=POLL) [ 2.989002] sja1105 spi9.0 t1-6 (uninitialized): PHY [spi9.0-base-t1:06] driver [Generic Clause 45 PHY] (irq=POLL) [ 2.991420] macb 20110000.ethernet eth0: entered promiscuous mode [ 2.991540] DSA: tree 0 setup [ 2.993156] clk: Disabling unused clocks ############################################## *************** FSW-PIXXEL *************** *************** IN_xPC *************** ############################################## # ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host proto kernel_lo valid_lft forever preferred_lft forever 2: bond0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 4e:0a:f0:7b:bc:e0 brd ff:ff:ff:ff:ff:ff 3: can0: mtu 16 qdisc noop state DOWN group default qlen 10 link/can 4: can1: mtu 16 qdisc noop state DOWN group default qlen 10 link/can 5: eth0: mtu 1536 qdisc noop state DOWN group default qlen 1000 link/ether 5e:78:8f:24:86:53 brd ff:ff:ff:ff:ff:ff 6: eth1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:04:a3:61:cc:6f brd ff:ff:ff:ff:ff:ff 7: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 8: rj45@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 5e:78:8f:24:86:53 brd ff:ff:ff:ff:ff:ff 9: interswitch@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 5e:78:8f:24:86:53 brd ff:ff:ff:ff:ff:ff 10: epc2-uplink@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 5e:78:8f:24:86:53 brd ff:ff:ff:ff:ff:ff 11: t1-1@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 5e:78:8f:24:86:53 brd ff:ff:ff:ff:ff:ff 12: t1-2@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 5e:78:8f:24:86:53 brd ff:ff:ff:ff:ff:ff 13: t1-3@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 5e:78:8f:24:86:53 brd ff:ff:ff:ff:ff:ff 14: t1-4@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 5e:78:8f:24:86:53 brd ff:ff:ff:ff:ff:ff 15: t1-5@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 5e:78:8f:24:86:53 brd ff:ff:ff:ff:ff:ff 16: t1-6@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 目前的观察结果: CPU 端口 (SGMII) 启动正常。 我可以从连接到 RJ45 100BASE-TX 端口的笔记本电脑接收 ARP 数据包。 板上的 tcpdump 确认来自笔记本电脑的 ARP 请求。 当从主板发送(ping/arping)时,笔记本电脑不会收到任何东西。 笔记本电脑 tcpdump 未显示来自主板的 RX 数据包。 我的问题是 要使 TX 流量在 SJA1110 DSA 端口上正常工作,是否需要任何额外的运行时 MAC 配置/转发/路由表设置? 是否可以预期 100BASE-T1 PHY 在此驱动程序树 中仅作为 通用条款 45 PHY 出现 ? 当前的 Linux 6.12 Microchip 树中是否缺少专用 BASE-T1 PHY 驱动程序? 为了进行测试,我尝试在两个 T1 端口之间进行直接环回 (T1-1<-> T1-2) 之间的直接环回,方法是连接:(TRX_1_P<->TRX_2_P 和 TRX_2_P<->TRX_2_N )。 SJA1110 BASE-T1 PHY 是否需要为链路训练进行明确的主/从配置? 8: rj45@eth0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 5e:78:8f:24:86:53 brd ff:ff:ff:ff:ff:ff inet6 fe80::5c78:8fff:fe24:8653/64 scope link proto kernel_ll valid_lft forever preferred_lft forever 11: t1-1@eth0: mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default qlen 1000 link/ether 5e:78:8f:24:86:53 brd ff:ff:ff:ff:ff:ff inet 192.168.10.1/24 scope global t1-1 valid_lft forever preferred_lft forever 12: t1-2@eth0: mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default qlen 1000 link/ether 5e:78:8f:24:86:53 brd ff:ff:ff:ff:ff:ff inet 192.168.10.2/24 scope global t1-2 valid_lft forever preferred_lft forever [ 133.739306] macb 20110000.ethernet eth0: configuring for fixed/sgmii link mode [ 133.739364] MACB : HWSTAMP check running [ 133.739414] MACB : HWSTAMP check passed found tsu_clk [ 133.741036] macb 20110000.ethernet: gem-ptp-timer ptp clock registered. [ 133.742794] sja1105 spi9.0 t1-1: configuring for phy/internal link mode [ 149.008075] sja1105 spi9.0 t1-2: configuring for phy/internal link mode [ 543.849763] sja1105 spi9.0 rj45: configuring for phy/internal link mode [ 545.889486] sja1105 spi9.0 rj45: Link is Up - 100Mbps/Full - flow control off   硬件表带配置: 全部 PHY_MS引脚均为低电平(从属模式)。 PHY_AUTO_MODE= 高 AUTO_POL_DET= 高电平 PHY 地址从 0x09. 没有 T1 链路的原因会不会是两个 PHY 都绑定为 SLAVE,因此没有用于链路训练的主时钟源? 有关以下方面的任何指导: 正确的 T1 启动、 主/从配置、 或预期 PHY 驱动程序支持 将不胜感激。 这是用于以太网交换机的 DTSI。 /* MAC0 : DSA master into SJA1110A SGMII4 */ &mac0 { /delete-property/ phy-handle; clocks = <&clkcfg CLK_MAC0>, <&clkcfg CLK_AHB>, <&fabric_fic3_clk>; clock-names = "pclk", "hclk", "tsu_clk"; phy-mode = "sgmii"; status = "okay"; dma-noncoherent; fixed-link { speed = <1000>; full-duplex; }; }; /* * SPI9: SJA1110A Host Access Port (HAP) * CS0 (reg=0) -> SS0_N -> Switch AP endpoint (DSA driver) * CS1 (reg=1) -> SS1_N -> Cortex-M7 uC endpoint (unused) * * BOOT_OPTION=11 (serial SPI boot): * SJA1110A waits for host config at power-on. * DSA driver sends static config tables at probe via CS0. * Cortex-M7 is disabled by driver : CS1/SS1 never used. * * SPI mode: CPOL=1 CPHA=0 (mode 2) : as per sja1105.yaml * SPI mode: CPOL=1 CPHA=1 (mode 3) : as per s32gxxxa-rdb.dtsi */ &spi9 { microchip,motorola-mode = <3>; /* mode 3: CPOL=1 CPHA=1 */ num-cs = <2>; status = "okay"; /* * SJA1110A : DSA switch (mainline driver) * reg=0 -> CS0 -> SS0_N -> switch AP endpoint * ethernet-switch@0 uses reg=<0> (SS0 = switch AP) * sja1110-uc@1 uses reg=<1> (SS1 = uC, disabled here) * * Port map * port@0 RevMII Cortex-M7 uC (disabled by driver) * port@1 100BASE-TX RJ45 diagnostic jack * port@2 RGMII2 inter-switch trunk -> SJA port2 * port@3 SGMII3 EPC-2 MAC1 relay uplink * port@4 SGMII4 EPC-1 MAC0 CPU port (this board) * Confirm is actual physical address needs to be added here * port@5 100BASE-T1 TRX_1 (PHY addr 9 on mdio@0) * port@6 100BASE-T1 TRX_2 (PHY addr 10 on mdio@0) * port@7 100BASE-T1 TRX_3 (PHY addr 11 on mdio@0) * port@8 100BASE-T1 TRX_4 (PHY addr 12 on mdio@0) * port@9 100BASE-T1 TRX_5 (PHY addr 13 on mdio@0) * port@a 100BASE-T1 TRX_6 (PHY addr 14 on mdio@0) */ sja1110a: ethernet-switch@0 { compatible = "nxp,sja1110a"; reg = <0>; spi-max-frequency = <1000000>; interrupt-parent = <&gpio8>; interrupts = <9 IRQ_TYPE_LEVEL_LOW>; mdios { #address-cells = <1>; #size-cells = <0>; mdio_t1: mdio@0 { compatible = "nxp,sja1110-base-t1-mdio"; reg = <0>; #address-cells = <1>; #size-cells = <0>; port5_base_t1_phy: ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c45"; reg = <0x01>; }; port6_base_t1_phy: ethernet-phy@2 { compatible = "ethernet-phy-ieee802.3-c45"; reg = <0x02>; }; port7_base_t1_phy: ethernet-phy@3 { compatible = "ethernet-phy-ieee802.3-c45"; reg = <0x03>; }; port8_base_t1_phy: ethernet-phy@4 { compatible = "ethernet-phy-ieee802.3-c45"; reg = <0x04>; }; port9_base_t1_phy: ethernet-phy@5 { compatible = "ethernet-phy-ieee802.3-c45"; reg = <0x05>; }; port10_base_t1_phy: ethernet-phy@6 { compatible = "ethernet-phy-ieee802.3-c45"; reg = <0x06>; }; }; mdio_tx: mdio@1 { compatible = "nxp,sja1110-base-tx-mdio"; reg = <1>; #address-cells = <1>; #size-cells = <0>; txphy1: ethernet-phy@1 { reg = <1>; }; }; }; ethernet-ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; status = "disabled"; }; /* ------------------------------------- * RJ45 diagnostic port * ------------------------------------- */ port@1 { reg = <1>; label = "rj45"; phy-mode = "internal"; phy-handle = <&txphy1>; }; port@2 { reg = <2>; label = "interswitch"; phy-mode = "rgmii"; rx-internal-delay-ps = <0>; tx-internal-delay-ps = <0>; fixed-link { speed = <1000>; full-duplex; }; }; port@3 { reg = <3>; label = "epc2-uplink"; phy-mode = "sgmii"; fixed-link { speed = <1000>; full-duplex; }; }; /* ------------------------------------- * CPU port * MAC0 <-> SGMII4 <-> port4 * ------------------------------------- */ port@4 { reg = <4>; label = "cpu"; ethernet = <&mac0>; phy-mode = "sgmii"; fixed-link { speed = <1000>; full-duplex; }; }; port@5 { reg = <5>; label = "t1-1"; phy-mode = "internal"; phy-handle = <&port5_base_t1_phy>; }; port@6 { reg = <6>; label = "t1-2"; phy-mode = "internal"; phy-handle = <&port6_base_t1_phy>; }; port@7 { reg = <7>; label = "t1-3"; phy-mode = "internal"; phy-handle = <&port7_base_t1_phy>; }; port@8 { reg = <8>; label = "t1-4"; phy-mode = "internal"; phy-handle = <&port8_base_t1_phy>; }; port@9 { reg = <9>; label = "t1-5"; phy-mode = "internal"; phy-handle = <&port9_base_t1_phy>; }; port@a { reg = <10>; label = "t1-6"; phy-mode = "internal"; phy-handle = <&port10_base_t1_phy>; }; }; }; /* SPIDEV for testing SPI lines using CS1 lines*/ sja110_spidev: spidev@1 { compatible = "microchip,mpfs-spidev"; reg = <1>; status = "okay"; spi-max-frequency = <1000000>; }; }; -- 安库尔 Re: SJA1110A DSA bring UP : 100BASE-TX TX failure and T1 link training issues 你好@Ankur_pixl、 感谢您一次性分享所有细节。 请在下面找到您问题的答案。 Q1.要使 TX 流量在 SJA1110 DSA 端口上正常工作,是否需要任何额外的运行时 MAC 配置/转发/路由表设置? A1.是的,请见下文。 Q2.100BASE-T1 PHY 在此驱动程序树中是否只能作为通用第 45 条 PHY 出现?当前的 Linux 6.12 Microchip 树中是否缺少专用 BASE-T1 PHY 驱动程序? A2.A2. Q3.为进行测试,我尝试在两个 T1 端口(t1-1<-> t1-2)之间直接环回,方法是连接:(TRX_1_P<->TRX_2_P 和 TRX_2_P<->TRX_2_N )。 A3:是的,没错。 Q4.SJA1110 BASE-T1 PHY 是否需要为链路训练进行明确的主/从配置? A4.是的,100BASE-T1 需要明确的主/从设置。仅供参考,驱动器中的"AUTO" 选项通常意味着"按照引脚捆绑" 。 要实现有效链接,必须通过硬件捆绑或 PHY 配置,将一个 PHY 配置为 MASTER(主设备),另一个 PHY 配置为 SLAVE(从设备)。 根据日志和 DT,交换机初始化和 PHY 绑定看起来是正确的。 如果 Linux 中没有配置网桥,就会出现 RX 可以工作而 TX 不能工作的情况。在 DSA 中,CPU 端口和用户端口之间不会自动转发流量。 DSA 交换机的行为类似于硬件交换机,但除非显式创建了网桥或 VLAN 配置,否则 Linux 不会在端口之间启用转发功能。 请创建一个网桥,同时连接 CPU 端口(eth0)和用户端口(rj45): ip link set eth0 up ip link set rj45 up ip link add br0 type bridge ip link set br0 up ip link set eth0 master br0 ip link set rj45 master br0 ip addr add 192.168.1.2/24dev br0 顺祝商祺! 帕维尔 Re: SJA1110A DSA bring UP : 100BASE-TX TX failure and T1 link training issues 您好, 我试过做同样的事情,但仍然没有看到笔记本电脑从 板上收到任何数据包。以下是我遵循的具体步骤: ------------------- ip link set eth0 up ip link set rj45 up ip link add br0 type bridge ip link set br0 type bridge ip link set br0 up ip link set rj45 master br0 ip addr add 192.168.1.1/24dev br0 ping 192.168.1.2 ------------------- 为了提供更多信息:RJ45 连接器已返工,芯片 TX 对的 P/N 端口与 RJ45 连接错误,这也可能是造成问题的原因。但是,链接总是会出现。 有什么我遗漏的吗?我附上了与 ETH 和 PHY 相关的内核配置。请检查是否有遗漏。 # ------------------------------ # Networking / HSR / QoS / PTP # ------------------------------ CONFIG_HSR=y CONFIG_PTP_1588_CLOCK=y CONFIG_POSIX_TIMERS=y CONFIG_BONDING=y CONFIG_NET_SCHED=y CONFIG_NET_SCH_FIFO=y CONFIG_NET_SCH_HTB=y CONFIG_NET_SCH_FQ_CODEL=y CONFIG_NET_SCH_MQPRIO=y CONFIG_NET_SCH_ETF=y CONFIG_NET_SCH_TAPRIO=y CONFIG_NET_CLS=y CONFIG_NET_CLS_U32=y CONFIG_NET_ACT_MIRRED=y CONFIG_MACB_USE_HWSTAMP=y CONFIG_NETWORK_PHY_TIMESTAMPING=y # ----------------------------- # SJA1110 Ethernet Switch support # ----------------------------- CONFIG_PHYLINK=y CONFIG_PCS_MARVELL=y CONFIG_SWPHY=y CONFIG_BRIDGE_VLAN_FILTERING=y CONFIG_VLAN_8021Q=y CONFIG_NET_DSA=y CONFIG_NET_DSA_TAG_8021Q=y CONFIG_NET_DSA_SJA1105=y CONFIG_NET_DSA_SJA1105_PTP=y CONFIG_NET_DSA_SJA1105_TAS=y CONFIG_NET_SWITCHDEV=y CONFIG_NET_DSA_TAG_OCELOT_8021Q=y CONFIG_MDIO_BUS=y CONFIG_MDIO_DEVICE=y CONFIG_NET_SCH_CBS=y CONFIG_BRIDGE=y CONFIG_OF_MDIO=y CONFIG_MDIO_DEVRES=y CONFIG_NET_DSA_SJA1105_VL=y CONFIG_PHYLIB_10G=y # ----------------------------- # PHY support for direct ETH link (MAC0 - OBC) # Fixed link - no PHY driver needed for MAC0 # MAC1 - SJA1110 also uses fixed link to switch CPU port # ----------------------------- CONFIG_FIXED_PHY=y CONFIG_PHYLIB=y CONFIG_NXP_CBTX_PHY=y CONFIG_NXP_C45_TJA11XX_PHY=y CONFIG_NXP_TJA11XX_PHY=y CONFIG_MARVELL_88Q2XXX_PHY=y CONFIG_AQUANTIA_PHY=y CONFIG_MICREL_PHY=y 我还尝试用 T1-1 和 T1-2 进行 100BASE-T1 环回,将 T1-1 设置为 PHY_MS = 1(主站),T1-2 设置为 PHY_MS = 0(从站)。我调出了两个界面,但链接始终没有出现。这在意料之中吗?我错过了什么?环回是双绞线(P/N)上的简单有线连接。 ------------------- ip link set eth0 up ip link set rj45 up ip link set t1-1 up ip link set t1-2 up ------------------- Re: SJA1110A DSA bring UP : 100BASE-TX TX failure and T1 link training issues 你好@Ankur_pixl、 不知怎么的,你漏了一行: ip link set eth0 up ip link set rj45 up   ip link add br0 type bridge ip link set br0 up   ip link set eth0 master br0 ip link set rj45 master br0   ip addr add 192.168.1.1/24开发周期 内核配置似乎正确。 关于 T1 100BASE-T1 的简单布线连接应该可以正常工作,我一直使用这种连接方式。是否使用 PHY_ADDR* 引脚绑扎? 请分享: ethtool t1-1 ethtool t1-2 dmesg | grep -iE"t1-|phy|sja1105" 在链接启动之后 顺祝商祺! 帕维尔 Re: SJA1110A DSA bring UP : 100BASE-TX TX failure and T1 link training issues 你好@PavelL, 感谢您的回答。 将 eth0 连接到 br0 后,当尝试连接 rj45 时,我看到如下错误。 # ip link set eth0 up [ 20.561460] macb 20110000.ethernet eth0: configuring for fixed/sgmii link mode [ 20.561554] MACB : HWSTAMP check running # [ 20.561605] MACB : HWSTAMP check passed found tsu_clk [ 20.562612] macb 20110000.ethernet: gem-ptp-timer ptp clock registered. ip link set rj45 up # [ 25.693665] sja1105 spi9.0 rj45: configuring for phy/internal link mode [ 27.746002] sja1105 spi9.0 rj45: Link is Up - 100Mbps/Full - flow control off # ip link add br0 type bridge # ip link set br0 up # ip link set eth0 master br0 # [ 43.053547] br0: port 1(eth0) entered blocking state [ 43.053590] br0: port 1(eth0) entered disabled state [ 43.053666] macb 20110000.ethernet eth0: entered allmulticast mode ip link set rj45 master br0 [ 49.972011] br0: port 2(rj45) entered blocking state [ 49.972214] br0: port 2(rj45) entered disabled state [ 49.972288] sja1105 spi9.0 rj45: entered allmulticast mode RTNETLINK answer[ 50.005003] sja1105 spi9.0 rj45: left allmulticast mode s: Invalid argument 关于 T1 端口,请参见以下答复 # ip link set eth0 up [ 305.486294] macb 20110000.ethernet eth0: configuring for fixed/sgmii link mode [ 305.486405] MACB : HWSTAMP check running [ 305.486456] MACB : HWSTAMP check passed found tsu_clk [ 305.487476] macb 20110000.ethernet: gem-ptp-timer ptp clock registered. # ip link set rj45 up # [ 311.277622] sja1105 spi9.0 rj45: configuring for phy/internal link mode [ 313.313486] sja1105 spi9.0 rj45: Link is Up - 100Mbps/Full - flow control off # ip link set t1-1 up # [ 326.282210] sja1105 spi9.0 t1-1: configuring for phy/internal link mode # ip link set t1-2 up [ 330.126681] sja1105 spi9.0 t1-2: configuring for phy/internal link mode # ethtool t1-1 Settings for t1-1: Supported ports: [ ] Supported link modes: 100baseT1/Full Supported pause frame use: No Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: 100baseT1/Full Advertised pause frame use: No Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: external Auto-negotiation: off Supports Wake-on: d Wake-on: d Link detected: no # ethtool t1-2 Settings for t1-2: Supported ports: [ ] Supported link modes: 100baseT1/Full Supported pause frame use: No Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: 100baseT1/Full Advertised pause frame use: No Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: 100Mb/s Duplex: Full Duplex: Full Port: MII PHYAD: 2 Transceiver: external Auto-negotiation: off Wake-on: d Link detected: no # [ 365.547745] power_supply bq34z100-0: driver failed to report `time_to_empty_avg' property: -22 dmesg | grep -iE "t1-|phy|sja1105" [ 2.250188] u-dma-buf udmabuf-ddr-c0: phys address = 0x0000000088000000 [ 2.995658] u-dma-buf udmabuf-ddr-nc0: phys address = 0x00000000c8000000 [ 3.012712] u-dma-buf udmabuf-ddr-nc-wcb0: phys address = 0x00000000d8000000 [ 3.081775] sja1105 spi9.0: Probed switch chip: SJA1110A [ 3.081796] sja1105 spi9.0: max_xfer_len = 256 bytes [ 3.233399] sja1105 spi9.0: Probed switch chip: SJA1110A [ 3.233418] sja1105 spi9.0: max_xfer_len = 256 bytes [ 3.236047] sja1105 spi9.0: Config buffer length: 1776 bytes [ 3.236072] sja1105 spi9.0: Config buffer device_id at offset 0: 0x0f0300b7 [ 3.429135] sja1105 status decoded: CONFIGS=1 CRCCHKL=0 IDS=0 CRCCHKG=0 NSLOT=5 [ 3.429165] sja1105 spi9.0: sja1105_static_config_load done [ 3.429181] sja1105 spi9.0: sja1105_clocking done [ 3.429194] sja1105 spi9.0: sja1105_TAS and flower setup done [ 3.430339] sja1105 spi9.0: sja1105_ptp_clock_register done [ 3.572901] sja1105 spi9.0: sja1105_mdiobus_register done [ 3.572938] sja1105 spi9.0: sja1105_devlink_setup done [ 3.586915] sja1105 spi9.0: dsa_tag_8021q_register and rtnl_unlockdone [ 3.588440] sja1105 spi9.0: configuring for fixed/sgmii link mode [ 3.593936] sja1105 spi9.0: Link is Up - 1Gbps/Full - flow control off [ 3.652480] sja1105 spi9.0 rj45 (uninitialized): PHY [spi9.0-base-tx:01] driver [NXP CBTX (SJA1110)] (irq=POLL) [ 3.661033] sja1105 spi9.0 t1-1 (uninitialized): PHY [spi9.0-base-t1:01] driver [Generic Clause 45 PHY] (irq=POLL) [ 3.664058] sja1105 spi9.0 t1-2 (uninitialized): PHY [spi9.0-base-t1:02] driver [Generic Clause 45 PHY] (irq=POLL) [ 3.667342] sja1105 spi9.0 t1-3 (uninitialized): PHY [spi9.0-base-t1:03] driver [Generic Clause 45 PHY] (irq=POLL) [ 3.670592] sja1105 spi9.0 t1-4 (uninitialized): PHY [spi9.0-base-t1:04] driver [Generic Clause 45 PHY] (irq=POLL) [ 3.673818] sja1105 spi9.0 t1-5 (uninitialized): PHY [spi9.0-base-t1:05] driver [Generic Clause 45 PHY] (irq=POLL) [ 3.676972] sja1105 spi9.0 t1-6 (uninitialized): PHY [spi9.0-base-t1:06] driver [Generic Clause 45 PHY] (irq=POLL) [ 311.277622] sja1105 spi9.0 rj45: configuring for phy/internal link mode [ 313.313486] sja1105 spi9.0 rj45: Link is Up - 100Mbps/Full - flow control off [ 326.282210] sja1105 spi9.0 t1-1: configuring for phy/internal link mode [ 330.126681] sja1105 spi9.0 t1-2: configuring for phy/internal link mode 是的,我确实使用了 PHY_ADDR 带,PHY_ADDR[4:0] 设置为 5'b010001。( 0x09 至 0x14 ) 与https://github.com/nxp-auto-linux/linux/blob/810f396375526c11989bd1a296d2f9959de9392f/arch/arm64/boot/dts/freescale/s32gxxxa-rdb.dtsi#L141和 S32G-VNP-RDB3 原理图相同。 -- 安库尔 Re: SJA1110A DSA bring UP : 100BASE-TX TX failure and T1 link training issues 你好@Ankur_pixl、 感谢您的更新 - 目前,我认为我们最好从头开始调试,使用最小的确定性设置,因为我们现在有几个相互影响的变量(DSA 拓扑、网桥行为和 PHY 访问路径),我们需要隔离 RJ45 问题是软件(Linux/DSA/网桥/VLAN)问题还是硬件(TX 对/磁性元件)问题。 从你最初的描述中,我们可以看出一个清晰的症状模式: RJ45 RX 正常工作(可以看到来自笔记本电脑的 ARP 请求)。 RJ45 TX 不能(笔记本电脑看不到板上的任何框架)。 100BASE‑T1 仍处于关闭状态,目前我们没有足够的证据来得出结论,这是否与配置/管理路径有关,还是与物理层/训练问题有关。 这是第一步: 第 1 步 - 在不使用任何桥接器的情况下确认 RJ45 上的基本 TX ip link set eth0 up ip link set rj45 up   # 重要:移除其他设备上的 IP 以避免混乱路由 ip addr flush dev eth0 IP 地址 flush dev rj45 IP 地址 flush dev br0 2>/dev/null   # 将 IP 直接接入 RJ45 DSA 端口 ip addr add 192.168.1.1/24dev rj45   # 显示路由和地址以保持理智 ip addr show rj45 ip route show   # 产生流量 arping -I rj45 192.168.1.2 ping -I rj45 192.168.1.2 同时,在板上捕获 tcpdump -i rj45 -e -nn arp 或 icmp 笔记本电脑 tcpdump -i -e -nn arp 或 icmp 顺祝商祺! 帕维尔 Re: SJA1110A DSA bring UP : 100BASE-TX TX failure and T1 link training issues 你好, ,我还发现 eth0 链接没有显示 RUNNING,这会是问题之一吗?在进行 PING 时,RJ45 的 txbytes 会增加,但 eth0 发送的所有信息都会被丢弃。 eth0 Link encap:Ethernet HWaddr 92:56:D3:62:3D:60 UP BROADCAST MULTICAST MTU:1536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:10 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:33 rj45 Link encap:Ethernet HWaddr 92:56:D3:62:3D:60 inet6 addr: fe80::9056:d3ff:fe62:3d60/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:796 (796.0 B) # ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host proto kernel_lo valid_lft forever preferred_lft forever 2: bond0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether ee:06:ea:10:7f:d4 brd ff:ff:ff:ff:ff:ff 3: can0: mtu 16 qdisc noop state DOWN group default qlen 10 link/can 4: can1: mtu 16 qdisc noop state DOWN group default qlen 10 link/can 5: eth0: mtu 1536 qdisc mq state DOWN group default qlen 1000 link/ether 92:56:d3:62:3d:60 brd ff:ff:ff:ff:ff:ff 6: eth1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:04:a3:61:cc:6f brd ff:ff:ff:ff:ff:ff 7: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 8: rj45@eth0: mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000 link/ether 92:56:d3:62:3d:60 brd ff:ff:ff:ff:ff:ff inet6 fe80::9056:d3ff:fe62:3d60/64 scope link proto kernel_ll valid_lft forever preferred_lft forever 9: interswitch@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 92:56:d3:62:3d:60 brd ff:ff:ff:ff:ff:ff 10: epc2-uplink@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 92:56:d3:62:3d:60 brd ff:ff:ff:ff:ff:ff 11: t1-1@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 92:56:d3:62:3d:60 brd ff:ff:ff:ff:ff:ff 12: t1-2@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 92:56:d3:62:3d:60 brd ff:ff:ff:ff:ff:ff 13: t1-3@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 92:56:d3:62:3d:60 brd ff:ff:ff:ff:ff:ff 14: t1-4@eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 92:56:d3:62:3d:60 brd ff:ff:ff:ff:ff:ff 15: t1-5@eth0: mtu 1500 qdisc noqueue master br0 state LOWERLAYERDOWN group default qlen 1000 link/ether 92:56:d3:62:3d:60 brd ff:ff:ff:ff:ff:ff 16: t1-6@eth0: mtu 1500 qdisc noqueue master br0 state LOWERLAYERDOWN group default qlen 1000 link/ether 92:56:d3:62:3d:60 brd ff:ff:ff:ff:ff:ff 17: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 92:56:d3:62:3d:60 brd ff:ff:ff:ff:ff:ff inet 192.168.10.1/24 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::9056:d3ff:fe62:3d60/64 scope link proto kernel_ll valid_lft forever preferred_lft forever -- 安库尔 Re: SJA1110A DSA bring UP : 100BASE-TX TX failure and T1 link training issues 您好 1.)我尝试了同样的测试,还检查了其他一些东西来验证问题。CPU 端口 (p04) 和 RJ45 之间似乎没有编程 L2 转发路径。 以下是整个日志 ////////////////// AFTER BOOT ////////////////// # ethtool -S eth0 NIC statistics: tx_octets: 0 tx_frames: 0 tx_broadcast_frames: 0 tx_multicast_frames: 0 tx_pause_frames: 0 tx_64_byte_frames: 0 tx_65_127_byte_frames: 0 tx_128_255_byte_frames: 0 tx_256_511_byte_frames: 0 tx_512_1023_byte_frames: 0 tx_1024_1518_byte_frames: 0 tx_greater_than_1518_byte_frames: 0 tx_underrun: 0 tx_single_collision_frames: 0 tx_multiple_collision_frames: 0 tx_excessive_collisions: 0 tx_late_collisions: 0 tx_deferred_frames: 0 tx_carrier_sense_errors: 0 rx_octets: 0 rx_frames: 0 rx_broadcast_frames: 0 rx_multicast_frames: 0 rx_pause_frames: 0 rx_64_byte_frames: 0 rx_65_127_byte_frames: 0 rx_128_255_byte_frames: 0 rx_256_511_byte_frames: 0 rx_512_1023_byte_frames: 0 rx_1024_1518_byte_frames: 0 rx_greater_than_1518_byte_frames: 0 rx_undersized_frames: 0 rx_oversize_frames: 0 rx_jabbers: 0 rx_frame_check_sequence_errors: 0 rx_length_field_frame_errors: 0 rx_symbol_errors: 0 rx_alignment_errors: 0 rx_resource_errors: 0 rx_overruns: 0 rx_ip_header_checksum_errors: 0 rx_tcp_checksum_errors: 0 rx_udp_checksum_errors: 0 q0_rx_packets: 0 q0_rx_bytes: 0 q0_rx_dropped: 0 q0_tx_packets: 0 q0_tx_bytes: 0 q0_tx_dropped: 0 q1_rx_packets: 0 q1_rx_bytes: 0 q1_rx_dropped: 0 q1_tx_packets: 0 q1_tx_bytes: 0 q1_tx_dropped: 0 q2_rx_packets: 0 q2_rx_bytes: 0 q2_rx_dropped: 0 q2_tx_packets: 0 q2_tx_bytes: 0 q2_tx_dropped: 0 q3_rx_packets: 0 q3_rx_bytes: 0 q3_rx_dropped: 0 q3_tx_packets: 0 q3_tx_bytes: 0 q3_tx_dropped: 0 p04_: 0 p04_n_runt: 0 p04_n_soferr: 0 p04_n_alignerr: 0 p04_n_miierr: 0 p04_typeerr: 0 p04_sizeerr: 0 p04_tctimeout: 0 p04_priorerr: 0 p04_nomaster: 0 p04_memov: 0 p04_memerr: 0 p04_invtyp: 0 p04_intcyov: 0 p04_domerr: 0 p04_pcfbagdrop: 0 p04_spcprior: 0 p04_ageprior: 0 p04_portdrop: 0 p04_lendrop: 0 p04_bagdrop: 0 p04_policeerr: 0 p04_drpnona664err: 0 p04_spcerr: 0 p04_agedrp: 0 p04_n_n664err: 0 p04_n_vlanerr: 0 p04_n_unreleased: 0 p04_n_sizeerr: 0 p04_n_crcerr: 0 p04_n_vlnotfound: 0 p04_n_ctpolerr: 0 p04_n_polerr: 0 p04_n_rxfrm: 0 p04_n_rxbyte: 0 p04_n_txfrm: 0 p04_n_txbyte: 0 p04_n_qfull: 0 p04_n_part_drop: 0 p04_n_egr_disabled: 0 p04_n_not_reach: 0 p04_n_drops_nolearn: 0 p04_n_drops_noroute: 0 p04_n_drops_ill_dtag: 0 p04_n_drops_dtag: 0 p04_n_drops_sotag: 0 p04_n_drops_sitag: 0 p04_n_drops_utag: 0 p04_n_tx_bytes_1024_2047: 0 p04_n_tx_bytes_512_1023: 0 p04_n_tx_bytes_256_511: 0 p04_n_tx_bytes_128_255: 0 p04_n_tx_bytes_65_127: 0 p04_n_tx_bytes_64: 0 p04_n_tx_mcast: 0 p04_n_tx_bcast: 0 p04_n_rx_bytes_1024_2047: 0 p04_n_rx_bytes_512_1023: 0 p04_n_rx_bytes_256_511: 0 p04_n_rx_bytes_128_255: 0 p04_n_rx_bytes_65_127: 0 p04_n_rx_bytes_64: 0 p04_n_rx_mcast: 0 # ethtool -S rj45 NIC statistics: tx_packets: 0 tx_bytes: 0 rx_packets: 0 rx_bytes: 0 : 0 n_runt: 0 n_soferr: 0 n_alignerr: 0 n_miierr: 0 typeerr: 0 sizeerr: 0 tctimeout: 0 priorerr: 0 nomaster: 0 memov: 0 memerr: 0 invtyp: 0 intcyov: 0 domerr: 0 pcfbagdrop: 0 spcprior: 0 ageprior: 0 portdrop: 0 lendrop: 0 bagdrop: 0 policeerr: 0 drpnona664err: 0 spcerr: 0 agedrp: 0 n_n664err: 0 n_vlanerr: 0 n_unreleased: 0 n_sizeerr: 0 n_crcerr: 0 n_vlnotfound: 0 n_ctpolerr: 0 n_polerr: 0 n_rxfrm: 0 n_rxbyte: 0 n_txfrm: 0 n_txbyte: 0 n_qfull: 0 n_part_drop: 0 n_egr_disabled: 0 n_not_reach: 0 n_drops_nolearn: 0 n_drops_noroute: 0 n_drops_ill_dtag: 0 n_drops_dtag: 0 n_drops_sotag: 0 n_drops_sitag: 0 n_drops_utag: 0 n_tx_bytes_1024_2047: 0 n_tx_bytes_512_1023: 0 n_tx_bytes_256_511: 0 n_tx_bytes_128_255: 0 n_tx_bytes_65_127: 0 n_tx_bytes_64: 0 n_tx_mcast: 0 n_tx_bcast: 0 n_rx_bytes_1024_2047: 0 n_rx_bytes_512_1023: 0 n_rx_bytes_256_511: 0 n_rx_bytes_128_255: 0 n_rx_bytes_65_127: 0 n_rx_bytes_64: 0 n_rx_mcast: 0 ////////////////// Link UP ////////////////// # ip link set eth0 up [ 69.576075] macb 20110000.ethernet eth0: configuring for fixed/sgmii link mode [ 69.576204] MACB : HWSTAMP check running # [ 69.576257] MACB : HWSTAMP check passed found tsu_clk [ 69.577736] macb 20110000.ethernet: gem-ptp-timer ptp clock registered. # ip link set rj45 up # [ 73.786469] sja1105 spi9.0 rj45: configuring for phy/internal link mode [ 75.841723] sja1105 spi9.0 rj45: Link is Up - 100Mbps/Full - flow control off # ip addr add 192.168.1.1/24 dev rj45 # ip link set rj45 up # ip addr show rj45 8: rj45@eth0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether e6:e8:ae:30:6b:84 brd ff:ff:ff:ff:ff:ff inet 192.168.1.1/24 scope global rj45 valid_lft forever preferred_lft forever inet6 fe80::e4e8:aeff:fe30:6b84/64 scope link proto kernel_ll valid_lft forever preferred_lft forever # ethtool -S rj45 NIC statistics: tx_packets: 10 tx_bytes: 796 rx_packets: 0 rx_bytes: 0 : 0 n_runt: 0 n_soferr: 0 n_alignerr: 0 n_miierr: 0 typeerr: 0 sizeerr: 0 tctimeout: 0 priorerr: 0 nomaster: 0 memov: 0 memerr: 0 invtyp: 0 intcyov: 0 domerr: 0 pcfbagdrop: 0 spcprior: 0 ageprior: 0 portdrop: 0 lendrop: 0 bagdrop: 0 policeerr: 0 drpnona664err: 0 spcerr: 0 agedrp: 0 n_n664err: 0 n_vlanerr: 0 n_unreleased: 0 n_sizeerr: 0 n_crcerr: 0 n_vlnotfound: 0 n_ctpolerr: 0 n_polerr: 0 n_rxfrm: 8 n_rxbyte: 1690 n_txfrm: 0 n_txbyte: 0 n_qfull: 0 n_part_drop: 0 n_egr_disabled: 0 n_not_reach: 8 n_drops_nolearn: 0 n_drops_noroute: 0 n_drops_ill_dtag: 0 n_drops_dtag: 0 n_drops_sotag: 0 n_drops_sitag: 0 n_drops_utag: 0 n_tx_bytes_1024_2047: 0 n_tx_bytes_512_1023: 0 n_tx_bytes_256_511: 0 n_tx_bytes_128_255: 0 n_tx_bytes_65_127: 0 n_tx_bytes_64: 0 n_tx_mcast: 0 n_tx_bcast: 0 n_rx_bytes_1024_2047: 0 n_rx_bytes_512_1023: 2 n_rx_bytes_256_511: 0 n_rx_bytes_128_255: 0 n_rx_bytes_65_127: 0 n_rx_bytes_64: 6 n_rx_mcast: 8 # ethtool -S eth0 NIC statistics: tx_octets: 0 tx_frames: 0 tx_broadcast_frames: 0 tx_multicast_frames: 0 tx_pause_frames: 0 tx_64_byte_frames: 0 tx_65_127_byte_frames: 0 tx_128_255_byte_frames: 0 tx_256_511_byte_frames: 0 tx_512_1023_byte_frames: 0 tx_1024_1518_byte_frames: 0 tx_greater_than_1518_byte_frames: 0 tx_underrun: 0 tx_single_collision_frames: 0 tx_multiple_collision_frames: 0 tx_excessive_collisions: 0 tx_late_collisions: 0 tx_deferred_frames: 0 tx_carrier_sense_errors: 0 rx_octets: 0 rx_frames: 0 rx_broadcast_frames: 0 rx_multicast_frames: 0 rx_pause_frames: 0 rx_64_byte_frames: 0 rx_65_127_byte_frames: 0 rx_128_255_byte_frames: 0 rx_256_511_byte_frames: 0 rx_512_1023_byte_frames: 0 rx_1024_1518_byte_frames: 0 rx_greater_than_1518_byte_frames: 0 rx_undersized_frames: 0 rx_oversize_frames: 0 rx_jabbers: 0 rx_frame_check_sequence_errors: 0 rx_length_field_frame_errors: 0 rx_symbol_errors: 0 rx_alignment_errors: 0 rx_resource_errors: 0 rx_overruns: 0 rx_ip_header_checksum_errors: 0 rx_tcp_checksum_errors: 0 rx_udp_checksum_errors: 0 q0_rx_packets: 0 q0_rx_bytes: 0 q0_rx_dropped: 0 q0_tx_packets: 0 q0_tx_bytes: 0 q0_tx_dropped: 0 q1_rx_packets: 0 q1_rx_bytes: 0 q1_rx_dropped: 0 q1_tx_packets: 0 q1_tx_bytes: 0 q1_tx_dropped: 0 q2_rx_packets: 0 q2_rx_bytes: 0 q2_rx_dropped: 0 q2_tx_packets: 0 q2_tx_bytes: 0 q2_tx_dropped: 0 q3_rx_packets: 0 q3_rx_bytes: 0 q3_rx_dropped: 0 q3_tx_packets: 0 q3_tx_bytes: 0 q3_tx_dropped: 0 p04_: 0 p04_n_runt: 0 p04_n_soferr: 0 p04_n_alignerr: 0 p04_n_miierr: 0 p04_typeerr: 0 p04_sizeerr: 0 p04_tctimeout: 0 p04_priorerr: 0 p04_nomaster: 0 p04_memov: 0 p04_memerr: 0 p04_invtyp: 0 p04_intcyov: 0 p04_domerr: 0 p04_pcfbagdrop: 0 p04_spcprior: 0 p04_ageprior: 0 p04_portdrop: 0 p04_lendrop: 0 p04_bagdrop: 0 p04_policeerr: 0 p04_drpnona664err: 0 p04_spcerr: 0 p04_agedrp: 0 p04_n_n664err: 0 p04_n_vlanerr: 0 p04_n_unreleased: 0 p04_n_sizeerr: 0 p04_n_crcerr: 0 p04_n_vlnotfound: 0 p04_n_ctpolerr: 0 p04_n_polerr: 0 p04_n_rxfrm: 0 p04_n_rxbyte: 0 p04_n_txfrm: 8 p04_n_txbyte: 1722 p04_n_qfull: 0 p04_n_part_drop: 0 p04_n_egr_disabled: 0 p04_n_not_reach: 0 p04_n_drops_nolearn: 0 p04_n_drops_noroute: 0 p04_n_drops_ill_dtag: 0 p04_n_drops_dtag: 0 p04_n_drops_sotag: 0 p04_n_drops_sitag: 0 p04_n_drops_utag: 0 p04_n_tx_bytes_1024_2047: 0 p04_n_tx_bytes_512_1023: 2 p04_n_tx_bytes_256_511: 0 p04_n_tx_bytes_128_255: 0 p04_n_tx_bytes_65_127: 6 p04_n_tx_bytes_64: 0 p04_n_tx_mcast: 8 p04_n_tx_bcast: 0 p04_n_rx_bytes_1024_2047: 0 p04_n_rx_bytes_512_1023: 0 p04_n_rx_bytes_256_511: 0 p04_n_rx_bytes_128_255: 0 p04_n_rx_bytes_65_127: 0 p04_n_rx_bytes_64: 0 p04_n_rx_mcast: 0 ////////////////// PING BOARD TO Laptop ////////////////// # arping -I rj45 192.168.1.2 ARPING 192.168.1.2 from 192.168.1.1 rj45 ^CSent 9 probe(s) (9 broadcast(s)) Received 0 response(s) (0 request(s), 0 broadcast(s)) # ethtool -S eth0 NIC statistics: tx_octets: 0 tx_frames: 0 tx_broadcast_frames: 0 tx_multicast_frames: 0 tx_pause_frames: 0 tx_64_byte_frames: 0 tx_65_127_byte_frames: 0 tx_128_255_byte_frames: 0 tx_256_511_byte_frames: 0 tx_512_1023_byte_frames: 0 tx_1024_1518_byte_frames: 0 tx_greater_than_1518_byte_frames: 0 tx_underrun: 0 tx_single_collision_frames: 0 tx_multiple_collision_frames: 0 tx_excessive_collisions: 0 tx_late_collisions: 0 tx_deferred_frames: 0 tx_carrier_sense_errors: 0 rx_octets: 0 rx_frames: 0 rx_broadcast_frames: 0 rx_multicast_frames: 0 rx_pause_frames: 0 rx_64_byte_frames: 0 rx_65_127_byte_frames: 0 rx_128_255_byte_frames: 0 rx_256_511_byte_frames: 0 rx_512_1023_byte_frames: 0 rx_1024_1518_byte_frames: 0 rx_greater_than_1518_byte_frames: 0 rx_undersized_frames: 0 rx_oversize_frames: 0 rx_jabbers: 0 rx_frame_check_sequence_errors: 0 rx_length_field_frame_errors: 0 rx_symbol_errors: 0 rx_alignment_errors: 0 rx_resource_errors: 0 rx_overruns: 0 rx_ip_header_checksum_errors: 0 rx_tcp_checksum_errors: 0 rx_udp_checksum_errors: 0 q0_rx_packets: 0 q0_rx_bytes: 0 q0_rx_dropped: 0 q0_tx_packets: 0 q0_tx_bytes: 0 q0_tx_dropped: 0 q1_rx_packets: 0 q1_rx_bytes: 0 q1_rx_dropped: 0 q1_tx_packets: 0 q1_tx_bytes: 0 q1_tx_dropped: 0 q2_rx_packets: 0 q2_rx_bytes: 0 q2_rx_dropped: 0 q2_tx_packets: 0 q2_tx_bytes: 0 q2_tx_dropped: 0 q3_rx_packets: 0 q3_rx_bytes: 0 q3_rx_dropped: 0 q3_tx_packets: 0 q3_tx_bytes: 0 q3_tx_dropped: 0 p04_: 0 p04_n_runt: 0 p04_n_soferr: 0 p04_n_alignerr: 0 p04_n_miierr: 0 p04_typeerr: 0 p04_sizeerr: 0 p04_tctimeout: 0 p04_priorerr: 0 p04_nomaster: 0 p04_memov: 0 p04_memerr: 0 p04_invtyp: 0 p04_intcyov: 0 p04_domerr: 0 p04_pcfbagdrop: 0 p04_spcprior: 0 p04_ageprior: 0 p04_portdrop: 0 p04_lendrop: 0 p04_bagdrop: 0 p04_policeerr: 0 p04_drpnona664err: 0 p04_spcerr: 0 p04_agedrp: 0 p04_n_n664err: 0 p04_n_vlanerr: 0 p04_n_unreleased: 0 p04_n_sizeerr: 0 p04_n_crcerr: 0 p04_n_vlnotfound: 0 p04_n_ctpolerr: 0 p04_n_polerr: 0 p04_n_rxfrm: 0 p04_n_rxbyte: 0 p04_n_txfrm: 8 p04_n_txbyte: 1722 p04_n_qfull: 0 p04_n_part_drop: 0 p04_n_egr_disabled: 0 p04_n_not_reach: 0 p04_n_drops_nolearn: 0 p04_n_drops_noroute: 0 p04_n_drops_ill_dtag: 0 p04_n_drops_dtag: 0 p04_n_drops_sotag: 0 p04_n_drops_sitag: 0 p04_n_drops_utag: 0 p04_n_tx_bytes_1024_2047: 0 p04_n_tx_bytes_512_1023: 2 p04_n_tx_bytes_256_511: 0 p04_n_tx_bytes_128_255: 0 p04_n_tx_bytes_65_127: 6 p04_n_tx_bytes_64: 0 p04_n_tx_mcast: 8 p04_n_tx_bcast: 0 p04_n_rx_bytes_1024_2047: 0 p04_n_rx_bytes_512_1023: 0 p04_n_rx_bytes_256_511: 0 p04_n_rx_bytes_128_255: 0 p04_n_rx_bytes_65_127: 0 p04_n_rx_bytes_64: 0 p04_n_rx_mcast: 0 # ping -I rj45 192.168.1.2 PING 192.168.1.2 (192.168.1.2): 56 data bytes ^C --- 192.168.1.2 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss # ethtool -S eth0 NIC statistics: tx_octets: 0 tx_frames: 0 tx_broadcast_frames: 0 tx_multicast_frames: 0 tx_pause_frames: 0 tx_64_byte_frames: 0 tx_65_127_byte_frames: 0 tx_128_255_byte_frames: 0 tx_256_511_byte_frames: 0 tx_512_1023_byte_frames: 0 tx_1024_1518_byte_frames: 0 tx_greater_than_1518_byte_frames: 0 tx_underrun: 0 tx_single_collision_frames: 0 tx_multiple_collision_frames: 0 tx_excessive_collisions: 0 tx_late_collisions: 0 tx_deferred_frames: 0 tx_carrier_sense_errors: 0 rx_octets: 0 rx_frames: 0 rx_broadcast_frames: 0 rx_multicast_frames: 0 rx_pause_frames: 0 rx_64_byte_frames: 0 rx_65_127_byte_frames: 0 rx_128_255_byte_frames: 0 rx_256_511_byte_frames: 0 rx_512_1023_byte_frames: 0 rx_1024_1518_byte_frames: 0 rx_greater_than_1518_byte_frames: 0 rx_undersized_frames: 0 rx_oversize_frames: 0 rx_jabbers: 0 rx_frame_check_sequence_errors: 0 rx_length_field_frame_errors: 0 rx_symbol_errors: 0 rx_alignment_errors: 0 rx_resource_errors: 0 rx_overruns: 0 rx_ip_header_checksum_errors: 0 rx_tcp_checksum_errors: 0 rx_udp_checksum_errors: 0 q0_rx_packets: 0 q0_rx_bytes: 0 q0_rx_dropped: 0 q0_tx_packets: 0 q0_tx_bytes: 0 q0_tx_dropped: 0 q1_rx_packets: 0 q1_rx_bytes: 0 q1_rx_dropped: 0 q1_tx_packets: 0 q1_tx_bytes: 0 q1_tx_dropped: 0 q2_rx_packets: 0 q2_rx_bytes: 0 q2_rx_dropped: 0 q2_tx_packets: 0 q2_tx_bytes: 0 q2_tx_dropped: 0 q3_rx_packets: 0 q3_rx_bytes: 0 q3_rx_dropped: 0 q3_tx_packets: 0 q3_tx_bytes: 0 q3_tx_dropped: 0 p04_: 0 p04_n_runt: 0 p04_n_soferr: 0 p04_n_alignerr: 0 p04_n_miierr: 0 p04_typeerr: 0 p04_sizeerr: 0 p04_tctimeout: 0 p04_priorerr: 0 p04_nomaster: 0 p04_memov: 0 p04_memerr: 0 p04_invtyp: 0 p04_intcyov: 0 p04_domerr: 0 p04_pcfbagdrop: 0 p04_spcprior: 0 p04_ageprior: 0 p04_portdrop: 0 p04_lendrop: 0 p04_bagdrop: 0 p04_policeerr: 0 p04_drpnona664err: 0 p04_spcerr: 0 p04_agedrp: 0 p04_n_n664err: 0 p04_n_vlanerr: 0 p04_n_unreleased: 0 p04_n_sizeerr: 0 p04_n_crcerr: 0 p04_n_vlnotfound: 0 p04_n_ctpolerr: 0 p04_n_polerr: 0 p04_n_rxfrm: 0 p04_n_rxbyte: 0 p04_n_txfrm: 8 p04_n_txbyte: 1722 p04_n_qfull: 0 p04_n_part_drop: 0 p04_n_egr_disabled: 0 p04_n_not_reach: 0 p04_n_drops_nolearn: 0 p04_n_drops_noroute: 0 p04_n_drops_ill_dtag: 0 p04_n_drops_dtag: 0 p04_n_drops_sotag: 0 p04_n_drops_sitag: 0 p04_n_drops_utag: 0 p04_n_tx_bytes_1024_2047: 0 p04_n_tx_bytes_512_1023: 2 p04_n_tx_bytes_256_511: 0 p04_n_tx_bytes_128_255: 0 p04_n_tx_bytes_65_127: 6 p04_n_tx_bytes_64: 0 p04_n_tx_mcast: 8 p04_n_tx_bcast: 0 p04_n_rx_bytes_1024_2047: 0 p04_n_rx_bytes_512_1023: 0 p04_n_rx_bytes_256_511: 0 p04_n_rx_bytes_128_255: 0 p04_n_rx_bytes_65_127: 0 p04_n_rx_bytes_64: 0 p04_n_rx_mcast: 0 # ethtool -S rj45 NIC statistics: tx_packets: 26 tx_bytes: 1496 rx_packets: 0 rx_bytes: 0 : 0 n_runt: 0 n_soferr: 0 n_alignerr: 0 n_miierr: 0 typeerr: 0 sizeerr: 0 tctimeout: 0 priorerr: 0 nomaster: 0 memov: 0 memerr: 0 invtyp: 0 intcyov: 0 domerr: 0 pcfbagdrop: 0 spcprior: 0 ageprior: 0 portdrop: 0 lendrop: 0 bagdrop: 0 policeerr: 0 drpnona664err: 0 spcerr: 0 agedrp: 0 n_n664err: 0 n_vlanerr: 0 n_unreleased: 0 n_sizeerr: 0 n_crcerr: 0 n_vlnotfound: 0 n_ctpolerr: 0 n_polerr: 0 n_rxfrm: 9 n_rxbyte: 1781 n_txfrm: 0 n_txbyte: 0 n_qfull: 0 n_part_drop: 0 n_egr_disabled: 0 n_not_reach: 9 n_drops_nolearn: 0 n_drops_noroute: 0 n_drops_ill_dtag: 0 n_drops_dtag: 0 n_drops_sotag: 0 n_drops_sitag: 0 n_drops_utag: 0 n_tx_bytes_1024_2047: 0 n_tx_bytes_512_1023: 0 n_tx_bytes_256_511: 0 n_tx_bytes_128_255: 0 n_tx_bytes_65_127: 0 n_tx_bytes_64: 0 n_tx_mcast: 0 n_tx_bcast: 0 n_rx_bytes_1024_2047: 0 n_rx_bytes_512_1023: 2 n_rx_bytes_256_511: 0 n_rx_bytes_128_255: 0 n_rx_bytes_65_127: 1 n_rx_bytes_64: 6 n_rx_mcast: 9 ////////////////// PING Laptop TO Board ////////////////// # ethtool -S rj45 NIC statistics: tx_packets: 26 tx_bytes: 1496 rx_packets: 0 rx_bytes: 0 : 0 n_runt: 0 n_soferr: 0 n_alignerr: 0 n_miierr: 0 typeerr: 0 sizeerr: 0 tctimeout: 0 priorerr: 0 nomaster: 0 memov: 0 memerr: 0 invtyp: 0 intcyov: 0 domerr: 0 pcfbagdrop: 0 spcprior: 0 ageprior: 0 portdrop: 0 lendrop: 0 bagdrop: 0 policeerr: 0 drpnona664err: 0 spcerr: 0 agedrp: 0 n_n664err: 0 n_vlanerr: 0 n_unreleased: 0 n_sizeerr: 0 n_crcerr: 0 n_vlnotfound: 0 n_ctpolerr: 0 n_polerr: 0 n_rxfrm: 15 n_rxbyte: 2165 n_txfrm: 0 n_txbyte: 0 n_qfull: 0 n_part_drop: 0 n_egr_disabled: 0 n_not_reach: 9 n_drops_nolearn: 0 n_drops_noroute: 0 n_drops_ill_dtag: 0 n_drops_dtag: 0 n_drops_sotag: 0 n_drops_sitag: 0 n_drops_utag: 0 n_tx_bytes_1024_2047: 0 n_tx_bytes_512_1023: 0 n_tx_bytes_256_511: 0 n_tx_bytes_128_255: 0 n_tx_bytes_65_127: 0 n_tx_bytes_64: 0 n_tx_mcast: 0 n_tx_bcast: 0 n_rx_bytes_1024_2047: 0 n_rx_bytes_512_1023: 2 n_rx_bytes_256_511: 0 n_rx_bytes_128_255: 0 n_rx_bytes_65_127: 1 n_rx_bytes_64: 12 n_rx_mcast: 9 2.)在 T1 端口上,我检查错了 T1 端口;T1 端口环回上也出现了链接,但 ping 却无法正常工作。 同样的日志。 ======================================== SJA1110 T1 Loopback Test Thu Jan 1 00:03:16 UTC 1970 ======================================== === Bring Interfaces Up === === Configure IP Addresses === 15: t1-5@eth0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether e6:e8:ae:30:6b:84 brd ff:ff:ff:ff:ff:ff inet 192.168.10.1/24 scope global t1-5 valid_lft forever preferred_lft forever 16: t1-6@eth0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether e6:e8:ae:30:6b:84 brd ff:ff:ff:ff:ff:ff inet 192.168.10.2/24 scope global t1-6 valid_lft forever preferred_lft forever === Link Status === Settings for t1-5: Supported ports: [ ] Supported link modes: 100baseT1/Full Supported pause frame use: No Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: 100baseT1/Full Advertised pause frame use: No Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 5 Transceiver: external Auto-negotiation: off Supports Wake-on: d Wake-on: d Link detected: yes Settings for t1-6: Supported ports: [ ] Supported link modes: 100baseT1/Full Supported pause frame use: No Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: 100baseT1/Full Advertised pause frame use: No Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 6 Transceiver: external Auto-negotiation: off Supports Wake-on: d Wake-on: d Link detected: yes === VLAN Configuration === port vlan-id === FDB Before Traffic === 33:33:00:00:00:01 dev bond0 self permanent 33:33:00:00:00:01 dev eth0 self permanent 01:00:5e:00:00:01 dev eth0 self permanent 33:33:00:00:00:01 dev eth1 self permanent === Interface Counters BEFORE === 5: eth0: mtu 1536 qdisc mq state DOWN mode DEFAULT group default qlen 1000 link/ether e6:e8:ae:30:6b:84 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped missed mcast 0 0 0 0 0 0 TX: bytes packets errors dropped carrier collsns 0 0 0 16 0 0 15: t1-5@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether e6:e8:ae:30:6b:84 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped missed mcast 0 0 0 0 0 0 TX: bytes packets errors dropped carrier collsns 696 8 0 0 0 0 16: t1-6@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether e6:e8:ae:30:6b:84 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped missed mcast 0 0 0 0 0 0 TX: bytes packets errors dropped carrier collsns 696 8 0 0 0 0 === Ethtool Stats BEFORE === NIC statistics: tx_octets: 0 tx_frames: 0 tx_broadcast_frames: 0 tx_multicast_frames: 0 tx_pause_frames: 0 tx_64_byte_frames: 0 tx_65_127_byte_frames: 0 tx_128_255_byte_frames: 0 tx_256_511_byte_frames: 0 tx_512_1023_byte_frames: 0 tx_1024_1518_byte_frames: 0 tx_greater_than_1518_byte_frames: 0 tx_underrun: 0 tx_single_collision_frames: 0 tx_multiple_collision_frames: 0 tx_excessive_collisions: 0 tx_late_collisions: 0 tx_deferred_frames: 0 tx_carrier_sense_errors: 0 rx_octets: 0 rx_frames: 0 rx_broadcast_frames: 0 rx_multicast_frames: 0 rx_pause_frames: 0 rx_64_byte_frames: 0 rx_65_127_byte_frames: 0 rx_128_255_byte_frames: 0 rx_256_511_byte_frames: 0 rx_512_1023_byte_frames: 0 rx_1024_1518_byte_frames: 0 rx_greater_than_1518_byte_frames: 0 rx_undersized_frames: 0 rx_oversize_frames: 0 rx_jabbers: 0 rx_frame_check_sequence_errors: 0 rx_length_field_frame_errors: 0 rx_symbol_errors: 0 rx_alignment_errors: 0 rx_resource_errors: 0 rx_overruns: 0 rx_ip_header_checksum_errors: 0 rx_tcp_checksum_errors: 0 rx_udp_checksum_errors: 0 q0_rx_packets: 0 q0_rx_bytes: 0 q0_rx_dropped: 0 q0_tx_packets: 0 q0_tx_bytes: 0 q0_tx_dropped: 0 q1_rx_packets: 0 q1_rx_bytes: 0 q1_rx_dropped: 0 q1_tx_packets: 0 q1_tx_bytes: 0 q1_tx_dropped: 0 q2_rx_packets: 0 q2_rx_bytes: 0 q2_rx_dropped: 0 q2_tx_packets: 0 q2_tx_bytes: 0 q2_tx_dropped: 0 q3_rx_packets: 0 q3_rx_bytes: 0 q3_rx_dropped: 0 q3_tx_packets: 0 q3_tx_bytes: 0 q3_tx_dropped: 0 p04_: 0 p04_n_runt: 0 p04_n_soferr: 0 p04_n_alignerr: 0 p04_n_miierr: 0 p04_typeerr: 0 p04_sizeerr: 0 p04_tctimeout: 0 p04_priorerr: 0 p04_nomaster: 0 p04_memov: 0 p04_memerr: 0 p04_invtyp: 0 p04_intcyov: 0 p04_domerr: 0 p04_pcfbagdrop: 0 p04_spcprior: 0 p04_ageprior: 0 p04_portdrop: 0 p04_lendrop: 0 p04_bagdrop: 0 p04_policeerr: 0 p04_drpnona664err: 0 p04_spcerr: 0 p04_agedrp: 0 p04_n_n664err: 0 p04_n_vlanerr: 0 p04_n_unreleased: 0 p04_n_sizeerr: 0 p04_n_crcerr: 0 p04_n_vlnotfound: 0 p04_n_ctpolerr: 0 p04_n_polerr: 0 p04_n_rxfrm: 0 p04_n_rxbyte: 0 p04_n_txfrm: 0 p04_n_txbyte: 0 p04_n_qfull: 0 p04_n_part_drop: 0 p04_n_egr_disabled: 0 p04_n_not_reach: 0 p04_n_drops_nolearn: 0 p04_n_drops_noroute: 0 p04_n_drops_ill_dtag: 0 p04_n_drops_dtag: 0 p04_n_drops_sotag: 0 p04_n_drops_sitag: 0 p04_n_drops_utag: 0 p04_n_tx_bytes_1024_2047: 0 p04_n_tx_bytes_512_1023: 0 p04_n_tx_bytes_256_511: 0 p04_n_tx_bytes_128_255: 0 p04_n_tx_bytes_65_127: 0 p04_n_tx_bytes_64: 0 p04_n_tx_mcast: 0 p04_n_tx_bcast: 0 p04_n_rx_bytes_1024_2047: 0 p04_n_rx_bytes_512_1023: 0 p04_n_rx_bytes_256_511: 0 p04_n_rx_bytes_128_255: 0 p04_n_rx_bytes_65_127: 0 p04_n_rx_bytes_64: 0 p04_n_rx_mcast: 0 NIC statistics: tx_packets: 8 tx_bytes: 696 rx_packets: 0 rx_bytes: 0 : 0 n_runt: 0 n_soferr: 0 n_alignerr: 0 n_miierr: 0 typeerr: 0 sizeerr: 0 tctimeout: 0 priorerr: 0 nomaster: 0 memov: 0 memerr: 0 invtyp: 0 intcyov: 0 domerr: 0 pcfbagdrop: 0 spcprior: 0 ageprior: 0 portdrop: 0 lendrop: 0 bagdrop: 0 policeerr: 0 drpnona664err: 0 spcerr: 0 agedrp: 0 n_n664err: 0 n_vlanerr: 0 n_unreleased: 0 n_sizeerr: 0 n_crcerr: 0 n_vlnotfound: 0 n_ctpolerr: 0 n_polerr: 0 n_rxfrm: 0 n_rxbyte: 0 n_txfrm: 0 n_txbyte: 0 n_qfull: 0 n_part_drop: 0 n_egr_disabled: 0 n_not_reach: 0 n_drops_nolearn: 0 n_drops_noroute: 0 n_drops_ill_dtag: 0 n_drops_dtag: 0 n_drops_sotag: 0 n_drops_sitag: 0 n_drops_utag: 0 n_tx_bytes_1024_2047: 0 n_tx_bytes_512_1023: 0 n_tx_bytes_256_511: 0 n_tx_bytes_128_255: 0 n_tx_bytes_65_127: 0 n_tx_bytes_64: 0 n_tx_mcast: 0 n_tx_bcast: 0 n_rx_bytes_1024_2047: 0 n_rx_bytes_512_1023: 0 n_rx_bytes_256_511: 0 n_rx_bytes_128_255: 0 n_rx_bytes_65_127: 0 n_rx_bytes_64: 0 n_rx_mcast: 0 NIC statistics: tx_packets: 8 tx_bytes: 696 rx_packets: 0 rx_bytes: 0 : 0 n_runt: 0 n_soferr: 0 n_alignerr: 0 n_miierr: 0 typeerr: 0 sizeerr: 0 tctimeout: 0 priorerr: 0 nomaster: 0 memov: 0 memerr: 0 invtyp: 0 intcyov: 0 domerr: 0 pcfbagdrop: 0 spcprior: 0 ageprior: 0 portdrop: 0 lendrop: 0 bagdrop: 0 policeerr: 0 drpnona664err: 0 spcerr: 0 agedrp: 0 n_n664err: 0 n_vlanerr: 0 n_unreleased: 0 n_sizeerr: 0 n_crcerr: 0 n_vlnotfound: 0 n_ctpolerr: 0 n_polerr: 0 n_rxfrm: 0 n_rxbyte: 0 n_txfrm: 0 n_txbyte: 0 n_qfull: 0 n_part_drop: 0 n_egr_disabled: 0 n_not_reach: 0 n_drops_nolearn: 0 n_drops_noroute: 0 n_drops_ill_dtag: 0 n_drops_dtag: 0 n_drops_sotag: 0 n_drops_sitag: 0 n_drops_utag: 0 n_tx_bytes_1024_2047: 0 n_tx_bytes_512_1023: 0 n_tx_bytes_256_511: 0 n_tx_bytes_128_255: 0 n_tx_bytes_65_127: 0 n_tx_bytes_64: 0 n_tx_mcast: 0 n_tx_bcast: 0 n_rx_bytes_1024_2047: 0 n_rx_bytes_512_1023: 0 n_rx_bytes_256_511: 0 n_rx_bytes_128_255: 0 n_rx_bytes_65_127: 0 n_rx_bytes_64: 0 n_rx_mcast: 0 === ARP Test === ARPING 192.168.10.2 from 192.168.10.1 t1-5 Sent 10 probe(s) (0 broadcast(s)) Received 0 response(s) (0 request(s), 0 broadcast(s)) === Neighbor Table === === Interface Counters AFTER === 5: eth0: mtu 1536 qdisc mq state DOWN mode DEFAULT group default qlen 1000 link/ether e6:e8:ae:30:6b:84 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped missed mcast 0 0 0 0 0 0 TX: bytes packets errors dropped carrier collsns 0 0 0 26 0 0 15: t1-5@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether e6:e8:ae:30:6b:84 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped missed mcast 0 0 0 0 0 0 TX: bytes packets errors dropped carrier collsns 1116 18 0 0 0 0 16: t1-6@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether e6:e8:ae:30:6b:84 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped missed mcast 0 0 0 0 0 0 TX: bytes packets errors dropped carrier collsns 696 8 0 0 0 0 === Ethtool Stats AFTER === NIC statistics: tx_octets: 0 tx_frames: 0 tx_broadcast_frames: 0 tx_multicast_frames: 0 tx_pause_frames: 0 tx_64_byte_frames: 0 tx_65_127_byte_frames: 0 tx_128_255_byte_frames: 0 tx_256_511_byte_frames: 0 tx_512_1023_byte_frames: 0 tx_1024_1518_byte_frames: 0 tx_greater_than_1518_byte_frames: 0 tx_underrun: 0 tx_single_collision_frames: 0 tx_multiple_collision_frames: 0 tx_excessive_collisions: 0 tx_late_collisions: 0 tx_deferred_frames: 0 tx_carrier_sense_errors: 0 rx_octets: 0 rx_frames: 0 rx_broadcast_frames: 0 rx_multicast_frames: 0 rx_pause_frames: 0 rx_64_byte_frames: 0 rx_65_127_byte_frames: 0 rx_128_255_byte_frames: 0 rx_256_511_byte_frames: 0 rx_512_1023_byte_frames: 0 rx_1024_1518_byte_frames: 0 rx_greater_than_1518_byte_frames: 0 rx_undersized_frames: 0 rx_oversize_frames: 0 rx_jabbers: 0 rx_frame_check_sequence_errors: 0 rx_length_field_frame_errors: 0 rx_symbol_errors: 0 rx_alignment_errors: 0 rx_resource_errors: 0 rx_overruns: 0 rx_ip_header_checksum_errors: 0 rx_tcp_checksum_errors: 0 rx_udp_checksum_errors: 0 q0_rx_packets: 0 q0_rx_bytes: 0 q0_rx_dropped: 0 q0_tx_packets: 0 q0_tx_bytes: 0 q0_tx_dropped: 0 q1_rx_packets: 0 q1_rx_bytes: 0 q1_rx_dropped: 0 q1_tx_packets: 0 q1_tx_bytes: 0 q1_tx_dropped: 0 q2_rx_packets: 0 q2_rx_bytes: 0 q2_rx_dropped: 0 q2_tx_packets: 0 q2_tx_bytes: 0 q2_tx_dropped: 0 q3_rx_packets: 0 q3_rx_bytes: 0 q3_rx_dropped: 0 q3_tx_packets: 0 q3_tx_bytes: 0 q3_tx_dropped: 0 p04_: 0 p04_n_runt: 0 p04_n_soferr: 0 p04_n_alignerr: 0 p04_n_miierr: 0 p04_typeerr: 0 p04_sizeerr: 0 p04_tctimeout: 0 p04_priorerr: 0 p04_nomaster: 0 p04_memov: 0 p04_memerr: 0 p04_invtyp: 0 p04_intcyov: 0 p04_domerr: 0 p04_pcfbagdrop: 0 p04_spcprior: 0 p04_ageprior: 0 p04_portdrop: 0 p04_lendrop: 0 p04_bagdrop: 0 p04_policeerr: 0 p04_drpnona664err: 0 p04_spcerr: 0 p04_agedrp: 0 p04_n_n664err: 0 p04_n_vlanerr: 0 p04_n_unreleased: 0 p04_n_sizeerr: 0 p04_n_crcerr: 0 p04_n_vlnotfound: 0 p04_n_ctpolerr: 0 p04_n_polerr: 0 p04_n_rxfrm: 0 p04_n_rxbyte: 0 p04_n_txfrm: 0 p04_n_txbyte: 0 p04_n_qfull: 0 p04_n_part_drop: 0 p04_n_egr_disabled: 0 p04_n_not_reach: 0 p04_n_drops_nolearn: 0 p04_n_drops_noroute: 0 p04_n_drops_ill_dtag: 0 p04_n_drops_dtag: 0 p04_n_drops_sotag: 0 p04_n_drops_sitag: 0 p04_n_drops_utag: 0 p04_n_tx_bytes_1024_2047: 0 p04_n_tx_bytes_512_1023: 0 p04_n_tx_bytes_256_511: 0 p04_n_tx_bytes_128_255: 0 p04_n_tx_bytes_65_127: 0 p04_n_tx_bytes_64: 0 p04_n_tx_mcast: 0 p04_n_tx_bcast: 0 p04_n_rx_bytes_1024_2047: 0 p04_n_rx_bytes_512_1023: 0 p04_n_rx_bytes_256_511: 0 p04_n_rx_bytes_128_255: 0 p04_n_rx_bytes_65_127: 0 p04_n_rx_bytes_64: 0 p04_n_rx_mcast: 0 NIC statistics: tx_packets: 18 tx_bytes: 1116 rx_packets: 0 rx_bytes: 0 : 0 n_runt: 0 n_soferr: 0 n_alignerr: 0 n_miierr: 0 typeerr: 0 sizeerr: 0 tctimeout: 0 priorerr: 0 nomaster: 0 memov: 0 memerr: 0 invtyp: 0 intcyov: 0 domerr: 0 pcfbagdrop: 0 spcprior: 0 ageprior: 0 portdrop: 0 lendrop: 0 bagdrop: 0 policeerr: 0 drpnona664err: 0 spcerr: 0 agedrp: 0 n_n664err: 0 n_vlanerr: 0 n_unreleased: 0 n_sizeerr: 0 n_crcerr: 0 n_vlnotfound: 0 n_ctpolerr: 0 n_polerr: 0 n_rxfrm: 0 n_rxbyte: 0 n_txfrm: 0 n_txbyte: 0 n_qfull: 0 n_part_drop: 0 n_egr_disabled: 0 n_not_reach: 0 n_drops_nolearn: 0 n_drops_noroute: 0 n_drops_ill_dtag: 0 n_drops_dtag: 0 n_drops_sotag: 0 n_drops_sitag: 0 n_drops_utag: 0 n_tx_bytes_1024_2047: 0 n_tx_bytes_512_1023: 0 n_tx_bytes_256_511: 0 n_tx_bytes_128_255: 0 n_tx_bytes_65_127: 0 n_tx_bytes_64: 0 n_tx_mcast: 0 n_tx_bcast: 0 n_rx_bytes_1024_2047: 0 n_rx_bytes_512_1023: 0 n_rx_bytes_256_511: 0 n_rx_bytes_128_255: 0 n_rx_bytes_65_127: 0 n_rx_bytes_64: 0 n_rx_mcast: 0 NIC statistics: tx_packets: 8 tx_bytes: 696 rx_packets: 0 rx_bytes: 0 : 0 n_runt: 0 n_soferr: 0 n_alignerr: 0 n_miierr: 0 typeerr: 0 sizeerr: 0 tctimeout: 0 priorerr: 0 nomaster: 0 memov: 0 memerr: 0 invtyp: 0 intcyov: 0 domerr: 0 pcfbagdrop: 0 spcprior: 0 ageprior: 0 portdrop: 0 lendrop: 0 bagdrop: 0 policeerr: 0 drpnona664err: 0 spcerr: 0 agedrp: 0 n_n664err: 0 n_vlanerr: 0 n_unreleased: 0 n_sizeerr: 0 n_crcerr: 0 n_vlnotfound: 0 n_ctpolerr: 0 n_polerr: 0 n_rxfrm: 0 n_rxbyte: 0 n_txfrm: 0 n_txbyte: 0 n_qfull: 0 n_part_drop: 0 n_egr_disabled: 0 n_not_reach: 0 n_drops_nolearn: 0 n_drops_noroute: 0 n_drops_ill_dtag: 0 n_drops_dtag: 0 n_drops_sotag: 0 n_drops_sitag: 0 n_drops_utag: 0 n_tx_bytes_1024_2047: 0 n_tx_bytes_512_1023: 0 n_tx_bytes_256_511: 0 n_tx_bytes_128_255: 0 n_tx_bytes_65_127: 0 n_tx_bytes_64: 0 n_tx_mcast: 0 n_tx_bcast: 0 n_rx_bytes_1024_2047: 0 n_rx_bytes_512_1023: 0 n_rx_bytes_256_511: 0 n_rx_bytes_128_255: 0 n_rx_bytes_65_127: 0 n_rx_bytes_64: 0 n_rx_mcast: 0 === FDB After Traffic === 33:33:00:00:00:01 dev bond0 self permanent 33:33:00:00:00:01 dev eth0 self permanent 01:00:5e:00:00:01 dev eth0 self permanent 33:33:00:00:00:01 dev eth1 self permanent === Dmesg Link Events === [ 3.602806] sja1105 spi9.0: Link is Up - 1Gbps/Full - flow control off [ 3.678860] sja1105 spi9.0 t1-5 (uninitialized): PHY [spi9.0-base-t1:05] driver [Generic Clause 45 PHY] (irq=POLL) [ 3.682052] sja1105 spi9.0 t1-6 (uninitialized): PHY [spi9.0-base-t1:06] driver [Generic Clause 45 PHY] (irq=POLL) [ 196.222060] sja1105 spi9.0 t1-5: configuring for phy/internal link mode [ 196.224821] sja1105 spi9.0 t1-5: Link is Up - 100Mbps/Full - flow control off [ 196.229425] sja1105 spi9.0 t1-6: configuring for phy/internal link mode [ 196.231212] sja1105 spi9.0 t1-6: Link is Up - 100Mbps/Full - flow control off Re: SJA1110A DSA bring UP : 100BASE-TX TX failure and T1 link training issues 你好 @PavelL 即使在网桥创建之后,我也看到没有字节离开交换机。 # ip link set eth0 up [ 78.263728] macb 20110000.ethernet eth0: configuring for fixed/sgmii link mode [ 78.263859] MACB : HWSTAMP check running # [ 78.263911] MACB : HWSTAMP check passed found tsu_clk [ 78.265094] macb 20110000.ethernet: gem-ptp-timer ptp clock registered. ip addr flush dev rj45 # ip link add name br0 type bridge # ip link set br0 type bridge vlan_filtering 0 # ip link set rj45 master br0 [ 119.331341] br0: port 1(rj45) entered blocking state [ 119.331506] br0: port 1(rj45) entered disabled state [ 119.331588] sja1105 spi9.0 rj45: entered allmulticast mode # [ 119.331615] macb 20110000.ethernet eth0: entered allmulticast mode [ 119.339852] sja1105 spi9.0 rj45: entered promiscuous mode ip addr add 192.168.1.1/24 dev br0 # ip link set rj45 up # [ 130.485390] sja1105 spi9.0 rj45: configuring for phy/internal link mode [ 132.518207] sja1105 spi9.0 rj45: Link is Up - 100Mbps/Full - flow control off ip link set br0 up # [ 137.057392] br0: port 1(rj45) entered blocking state [ 137.057430] br0: port 1(rj45) entered forwarding state # ethtool -S rj45 | grep -E "n_txfrm|n_rxfrm|n_not_reach" n_rxfrm: 7 n_txfrm: 0 n_not_reach: 7 # ping -c 5 -I br0 192.168.1.2 PING 192.168.1.2 (192.168.1.2): 56 data bytes --- 192.168.1.2 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss # ethtool -S rj45 | grep -E "n_txfrm|n_rxfrm|n_not_reach" n_rxfrm: 14 n_txfrm: 0 n_not_reach: 14 这是配置问题吗? -- 安库尔 Re: SJA1110A DSA bring UP : 100BASE-TX TX failure and T1 link training issues 你好@Ankur_pixl、 感谢您提供的详细日志。请随时纠正我的解释。 您的最新结果非常有用,因为它们表明这很可能不再是一个单纯的桥梁问题。 对于 RJ45 直接 L3 测试(IP 直接分配到 rj45,无网桥),Linux netdev TX 计数器会增加,但 RJ45 端口的硬件交换机出口计数器仍为 0(`n_txfrm = 0`,`n_txbyte = 0`)。同时,RJ45 上的入口计数器也会增加,这表明前端 PHY/链路正在正确接收帧。 T1 回环结果也指向同一方向:两个 T1 端口都成功链接,因此 PHY 培训本身似乎有效,但流量仍无法通过。 这两种情况的共同点是 CPU/主控路径: - `eth0` 保持 `NO-CARRIER` - `eth0` 保持 `state DOWN` - MACB TX/RX 硬件计数器保持为 0 - `eth0` 的 TX 丢弃数据包增加 由此看来,主要问题是 SoC MAC (`eth0`)和 SJA1110 CPU 端口 (p04) 之间的 CPU 导管路径,而不是前 RJ45 或 T1 PHY 端口本身。 换句话说,交换机侧端口可以启动,但面向主机的 SGMII/CPU 端口数据路径似乎无法运行。 在现阶段,我建议将重点放在 SoC MAC / PCS / SGMII 的 "eth0 "配置以及相应的 CPU 端口配置上,而不是进一步进行桥接实验。 请分享: 1. ethtool eth0 2. ip-d link show eth0 3. 连接到交换机 CPU 端口的 SoC MAC/PCS/SGMII 端的完整设备树片段 4. SoC 端任何可用的 PCS/SGMII 链接状态信息 eth0` 从未达到 RUNNING / carrier-up(运行/载波启动)是一个强有力的指标,很可能与流量故障有关。 我再次查看了你的 DT 片段,设备树的 DSA/SJA1110 部分在逻辑上看起来是一致的: -MAC0 配置为 “sgmii”,具有固定的 1 Gbps 全双工链路-SJA1110 CPU 端口也被配置为 “sgmii”,带有固定的 1 Gbps 全双工链路 ——内部 PHY 端口映射看起来也正确 因此,目前我看不出这个片段本身存在明显的 DSA DT 错误。 然而,仅凭这个 DT 片段并不能证明 SoC 端 SGMII/PCS/SerDes 通路确实在运行。根据您的计数器,交换机 CPU 端口在交换机一侧似乎处于活动状态,但 `eth0` 仍处于 `NO-CARRIER` / DOWN 状态,没有真正的 MAC RX/TX 流量。 这表明面向 SoC 的 SGMII/PCS/SerDes 路径(或其低级初始化)存在问题,而不是前面的 RJ45 或 T1 端口。 能否请您分享完整的 MAC0 / PCS / SerDes 相关配置,以及初始化 SGMII 通道的任何引导加载程序/底层配置? 顺祝商祺! 帕维尔 Re: SJA1110A DSA bring UP : 100BASE-TX TX failure and T1 link training issues 你好@PavelL 是的,在仔细查看原理图后,我发现从 SoC 到交换机的 SGMII TX P/N 线路被调换了。此外,相同的 SGMII 线路连接到了另一个端点,导致以太网链路无法连接。 我们目前正在修复这些问题,并将向您提供最新结果。 -- 安库尔
View full article
GD3160 writing registers through SPI and distorted Gate output Good Morning, I have had hard time with configuring NXP's GD3160 through SPI, I have been through the datasheet for long time now but still can't get my grip of the GD3160 behavior of SPI and control. My two main problems summed up: 1- I can successfully read (at least what I think) from a daisy chain of 2 GDs, but I can't write anything, specially the MODE2 register CONFIG_EN bit. I am using Arduino uno. I tried many approaches and tests of my code, simplest, cleanest and yet failing test code is attached. Can you please point out what is wrong? is it CRC although i doubled check its calculation? is it SPI config? MSB first as per specs. 2- Also, the GD PWM signal at gate is clean at around duty cycle of 50% only, no MOSFET attached, default config, changing the duty cycle up or down leads to phase shifted and much smaller duty cycle signal measured by oscilloscope. any idea where I shall start looking? H-Bridge Driver HS|LS Configurable Driver Isolated Gate Drivers Re: GD3160 writing registers through SPI and distorted Gate output Dear Mahmoud, please share your schematic with voltage levels and part values.  To confirm that your SPI is correctly set, please connect oscilloscope probes to CS, MISO, MOSI and SCLK pins and please share the scopes. For the SPI timing requirements please refer to the Figure 35. in the GD3160 full datasheet. The clock must be low on idle (CPOL=0), the data must be switched on SCLK falling edge and sampled on SCLK rising edge (CPHA=0). Resulting in SPI mode 0.  Please also download and refer to AN13167. There you can find some hints about GD3160 SPI interface. With Best Regards, Jozef Re: GD3160 writing registers through SPI and distorted Gate output Thanks for your response, I totally forgot to get back. I have to ask the hardware team for schematics, but anyway, I could bring it up to work as per specs, the issue was not knowing that writing it locked at loss of HV side power or at case of latched faults. My concern now is regarding CONFIG_EN bit: Simply writing it and reading fails to activate the config mode, i tried many things, only thing that worked is to write to config_bit and RESET bit simultaneously. Why am i experiencing that? why do i have to write both config_bit and reset bit? writing to reset bit alone has no effect of driving INTB low as per specs, but writing to both bits gives the effect. I made sure SPI comm is correct, and values to write are not shifted (like i am sure of bit indices and offsets). What do you think? Re: GD3160 writing registers through SPI and distorted Gate output Dear Mahmoud, the reset bit just clears the faults and resets the registers to default condition. It looks a fault is blocking to enter configuration mode. This suggest, that after resetting the GD3160 the fault/faults are cleared and allowing you to enter configuration mode.  Please check the STATUS registers for a fault. STATUS1, STATUS2 and STATUS3 register. With Best Regards, Jozef
View full article
i.MX RT1176 中外部闪存执行冻结 你好!我正在为 i.MX RT1176 开发代码。我的代码通过外部闪存(型号 MX25UM51345G)和 XIP 运行,某些功能通过 RAM 运行。 启动工作正常,但执行大约 30 秒后处理器会死机。在连接调试器时,我发现 PC 被外部闪存中的一条指令卡住了(不一定是同一条指令或功能),而步进/恢复执行也无济于事(仍然卡在同一个 PC 上)。不产生故障。 我读取了 FlexSPI、SEMC 和 Cortex M-7 寄存器寄存器,但似乎一切正常。 核心冻结后,我可以强制 PC 进入 RAM(使用调试器),代码执行正常,直到代码尝试跳回闪存。 此外,在这种状态下从 RAM 执行的代码似乎能够读取闪存数据。 既然从闪存中读取数据是正常的,我想这可能是从闪存中获取指令的问题,但我不能肯定。即使是从闪存获取指令的问题,我也不知道该如何调试。 如有任何帮助,将不胜感激。 i.MX-RT1170 i.MXRT Re: External flash execution freeze in i.MX RT1176 谢谢您的建议。 我研究过是否可能存在你所说的冲突,但我的代码都没有向外部闪存写入、配置、发送 IP 命令等。 我还检查了 FLEXSPI 模块中的 INTR 寄存器,以确保在系统试图执行闪存中的指令时卡住之前没有产生错误,结果也没有产生错误。有没有办法(寄存器或位)检查是否发生了碰撞?在我不修改闪存的情况下,会发生这种碰撞吗(比如说预取和指令取入碰撞?) 谢谢 Re: External flash execution freeze in i.MX RT1176 嗨,@isstivenalive、 感谢您对 NXP MIMXRT 系列的关注! 根据您描述的症状,MCU 似乎运行正常。RAM 中的代码运行正常,系统可以从闪存读取数据和向闪存写入数据,但 XIP 却卡住了。 我认为目前最可能的根本原因是 AHB 预取/缓存与运行期间在同一 XIP 闪存上执行的 IP 命令、LUT/模式更新或擦除/写入操作之间发生了冲突。请检查是否在类似操作中出现问题。 如果需要在系统运行时对同一 XIP Flash 进行任何 IP 命令或配置更改,则必须将代码加载到 SRAM 中才能执行。 使用单个闪存设备时,闪存在繁忙时不会对进一步的访问做出响应。它还指出,与闪存写入相关的代码应从内部 SRAM 运行,应禁用中断以避免意外访问 Flash,并且 LUT 更新需要重置软件以避免冲突问题。 有一个最简单的故障排除方法:首先禁用所有闪存操作,然后只运行 XIP,看看是否能解决之前的问题。有关详情,请参阅此 AN:https://www.nxp.com/docs/en/application-note/AN12564.pdf。 致以最诚挚的问候, Gavin Re: External flash execution freeze in i.MX RT1176 嗨,@isstivenalive、 我不知道有专用 FlexSPI 寄存器位报告 “预取/指令提取冲突”。INTR 只报告已定义的错误/超时,因此干净的 INTR 并不能完全排除 XIP 读路径问题。 在这种情况下,下一个疑点应该是纯 XIP 读路径条件:FlexSPI AHB 预取/缓存行为、Cortex-M7 推测/缓存行取回、MPU 内存属性、FlexSPI 采样时钟/DQS/DLL 时序余量,以及八进制 DDR 闪存的 LUT/虚拟/模式配置。 为了缩小范围,请尝试以下测试。 禁用 FlexSPI AHB 预取 这只是为了先进行调试,检查挂起是否与 AHB 预取/缓冲区行为有关。 减少 FlexSPI 根时钟/串行时钟 如果问题在较低的时钟消失,则更多地指向 DQS/DLL 采样余量、电路板级信号完整性或虚拟周期时序。 暂时禁用指令缓存/数据缓存或查看 MPU 属性 重新检查 AHB 读取 LUT 和闪存时序配置 检查挂起后的 FlexSPI 状态 致以最诚挚的问候, Gavin
View full article
S32K566 IMCR Confilct 错误 MCU: S32K566 MCAL 套餐:RTD 0.8.0 (S32K5_RTD_0_8_0_D2512_ASR_REL_4_9_REL_4_9_REV_0000_20251205) 端口插件:端口_TS_T40D85M8I0R0 工具:EB Tresos / NXP MCAL 生成器 (McalGenerator_Nxp_S32K5-0.8.0) 说明: 我正在尝试使用端口 MCAL 插件在 S32K566 上配置多个 ADC0 模拟输入引脚。当我配置多个 ADC0 输入通道时,代码生成器会报告 IMCR 冲突错误。 配置: PCR 209 → 模式: ADC0_ADC0_CH2_P2_IN (映射到 SIUL2_3 上的 PORT209) PCR 226 → 模式: ADC0_ADC0_CH4_P4_IN (映射到 SIUL2_3 上的 PORT226) 问题 当仅配置一个 ADC 引脚时,代码生成成功,但 IMCR 索引报告为 0。 当添加第二个 ADC 引脚时,会出现 IMCR 冲突错误,因为两个引脚都映射到 SIUL2_3 上的同一个 IMCR 索引 0。 我调查了 port_s32K5_resource.m 文件,发现所有 ADC0 模拟输入通道都是使用 IMCR 映射 0 定义的 需要更改哪些配置才能解决这个问题? 如果这是一个已确认的错误,有没有已知的解决方法? Re: S32K566 IMCR Confilct Error 你好@JaeHeonJeong 由于 S32K5 仍处于 NPI 状态,我建议使用专用的支持渠道——要么直接 FAE 支持,要么在此处输入票证 (https://support.nxp.com/s/?language=en_US),这样它就会分配给区域 FAE 团队。也可能有专门针对贵公司的私人社区空间,但我不确定,因为我没有访问权限。 该社区尚未支持 S32K5。感谢您的理解。 此致, Lukas Re: S32K566 IMCR Confilct Error ADC0 通道可能基于不同的 IO 引脚和不同的 IMCR。而每个 IO 引脚都专用于一个 IMCR 不确定 K556 设置是关于什么的,因为它是一款非常新的设备。您能提供截图吗?
View full article
What Are the Best IPTV Providers in 2026? The way people watch television has changed faster than ever. Cable bills keep rising, viewers want more flexibility, and streaming has become the new normal. That is why many users now ask, What Are the Best IPTV Providers in 2026? They want better channel choices, smoother playback, and access to entertainment without the limits of traditional TV. 🛰️ Explore Best IPTV Providers IPTV stands for Internet Protocol Television. It delivers live TV channels, movies, sports, and on-demand content through an internet connection. Instead of using satellite or cable lines, users stream content directly on Smart TVs, Firestick, Android devices, tablets, and laptops. In 2026, IPTV services continue to grow because they offer convenience, value, and modern viewing features. This guide explains what makes a provider stand out and how to find the best IPTV solution for your needs. What Are the Best IPTV Providers in 2026 Known For? The best IPTV providers in 2026 are not only about having many channels. Quality matters more than quantity. A top provider should deliver stable streams, easy navigation, and strong customer support. Reliable IPTV services invest in better servers to reduce buffering. They also refresh channel lists regularly and maintain smooth access during busy hours. This is especially important for sports fans and live event viewers. Another sign of a strong provider is a user-friendly setup process. Good IPTV platforms make activation simple and compatible with popular apps and streaming devices. Why IPTV Is More Popular in 2026 Many households now prefer streaming because it matches modern lifestyles. Users want entertainment on their schedule, not fixed cable packages. Flexible Viewing on Any Device One major reason IPTV is growing is device freedom. Users can switch between Smart TVs, phones, tablets, and streaming sticks with ease. This creates a seamless entertainment experience. Better Value Than Traditional TV Many people search for affordable IPTV providers because they want more content without paying high monthly cable fees. IPTV often includes global channels, sports, and movies in one package. On-Demand Convenience Viewers no longer want to wait for scheduled broadcasts. IPTV often offers replay options, catch-up TV, and video-on-demand content that fits busy routines. Key Features of the Best IPTV Providers in 2026 Choosing the right service becomes easier when you know what to look for. Stable Streaming Quality The best IPTV providers in 2026 focus on fast servers and high uptime. Smooth playback matters more than long channel lists that do not work properly. Broad Channel Selection Top providers often include entertainment, news, sports, kids content, and international networks. A balanced lineup gives more value to subscribers. HD and 4K Support Many users now expect high-resolution streaming. Premium IPTV services often include HD, Full HD, and 4K options for supported channels. Responsive Customer Support Fast support helps when login issues, setup errors, or app problems happen. Reliable customer service is a major factor when choosing an IPTV provider. How to Choose the Best IPTV Provider for You Every viewer has different priorities. Some want sports coverage, while others focus on movies or family entertainment. If live sports matter most, look for stable event streams and wide sports channel coverage. If you enjoy films and series, choose a provider with a strong VOD library and updated content. Families may prefer multi-device access and children’s channels. Travelers may want worldwide compatibility and flexible login options. Testing before subscribing is also wise. Many users search for IPTV free trial services to check quality before purchasing a long plan. SEO Trends Driving IPTV Searches Search phrases like best IPTV providers in 2026, top IPTV services, premium IPTV plans, and no buffering IPTV are becoming more common. This reflects growing demand for flexible streaming solutions. As internet speeds improve worldwide, IPTV becomes easier to use. Smart TVs and streaming devices are also more affordable, which helps IPTV adoption rise. People want personalized entertainment, and IPTV gives them more control than standard television packages. Mistakes to Avoid When Choosing IPTV Some users choose only the cheapest option. Low prices can be attractive, but poor stream quality and weak support may lead to frustration. Another mistake is ignoring compatibility. Always confirm the provider works on your preferred device. Skipping research can also cause problems. Reading recent reviews and testing a trial can help avoid unreliable services. The Future of IPTV in 2026 IPTV is expected to become smarter and more user-focused. Faster networks, improved apps, and better content libraries will continue to shape the market. Many providers are improving interfaces, search tools, and streaming stability. This means users can expect smoother experiences in the future. As demand rises, competition among IPTV providers may also improve pricing and service quality. Conclusion So, What Are the Best IPTV Providers in 2026? They are the services that combine stable streaming, quality content, easy setup, and strong support. The best option depends on your viewing habits, devices, and budget. When choosing an IPTV provider, focus on performance rather than promises. A service with reliable playback and useful features will always offer better value. If you are ready to upgrade your entertainment experience, explore trusted IPTV providers and enjoy smarter streaming in 2026. Re: What Are the Best IPTV Providers in 2026? Looking for the best way to enjoy premium content without an immediate commitment? In 2026, the most effective way to find a high-quality provider is through a free IPTV trial. Why Start with a Free Test? A free trial allows you to verify several critical factors before subscribing: Stability: Ensure the service offers buffer-free streaming and high uptime (ideally 99% or more). Content Variety: Check for access to over 20,000+ live channels, including premium sports, news, and international networks. Quality: Verify support for HD, Full HD, and 4K streaming. Device Compatibility: Confirm it works on your preferred hardware, such as Amazon Firestick, Smart TVs, Android/iOS devices, or PCs. Top Recommendation for 2026 For a premium experience with a vast selection of channels and reliable performance, we recommend testing GoldCard TV. It is designed to provide a seamless entertainment solution with minimal downtime. 👉 Start your free trial now at: https://omeulink.com/GoldCardTv Re: What Are the Best IPTV Providers in 2026? I’ve tested several IPTV providers over the past few months, and in my experience, HypoTV is one of the best overall for stability, streaming quality, and everyday entertainment. If you’re looking for sports-focused streaming, BekuTV performs really well with smooth live channels and minimal buffering. For adult content and large VOD libraries, PillowIPTV is a strong option. I’ve also seen many users recommend MomIPTV for its reliable international channel selection and multi-device support. Overall, each service has its strengths depending on what type of content you watch most. Re: What Are the Best IPTV Providers in 2026? I’ve tested many IPTV services, and NexusIPTV honestly surprised me with its stability and picture quality. Fast channels, almost no buffering, and a huge selection of sports, movies, and international content in HD/4K. Works perfectly on Firestick, Smart TVs, Android, iPhone, and PC. If you want a reliable IPTV service in 2026, NexusIPTV is definitely worth trying. www.nexusiptv.live  Re: What Are the Best IPTV Providers in 2026? I’ve tested a few services recently mainly for live sports, and UHDSports has honestly been one of the smoother ones so far. What I liked most is that it didn’t feel overloaded or messy. The setup was simple, the channels opened quickly on my device, and the sports streams were stable during peak hours, which is usually where most providers start buffering. I also tested it on a Smart TV and Android device, and both worked fine. The VOD side is decent too, but for me the main reason to use it is live sports. If you’re choosing a provider, I’d still recommend asking for a free trial first and testing it during an actual live match, not just during quiet hours. That’s the real test. Not saying it’s perfect, but from my experience UHDSports is worth checking if your priority is stable live sports and quick support. Re: What Are the Best IPTV Providers in 2026? If you’re tired of hunting for links, switching apps, or dealing with lag during big matches, tvaccess.xyz is the platform built for you. This premium paid service delivers every major sport in the world — all in HD, Full HD, and 4K Ultra Quality with smooth, stable streaming. Watch every sport live in HD/4K tvaccess.xyz Re: What Are the Best IPTV Providers in 2026? I agree that choosing an IPTV provider in 2026 really comes down to reliability, channel selection, and streaming quality. I also like services that make it easy to verify information before making a decision. For unrelated research, I recently found Franklin Property Data useful for checking property related details. It’s always worth comparing options carefully and choosing a service that fits your needs.
View full article
[iMX93AUTO EVK] SPI Configuration for QCA7006AQ with imx93AUTO EVK is not working Hi Team, I am working on iMX93 Auto EVK and enabling the communication between iMX93 and QCA7006AQ vi SPI. I am connecting QCA chip on lpspi3 and did following device tree changes in imx93-14x14-evk.dts - &lpspi3 { fsl,spi-num-chipselects = <1>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_lpspi3>; cs-gpios = <&gpio2 8 GPIO_ACTIVE_LOW>; status = "okay"; qca7006aq: ethernet@0 { compatible = "qca,qca7006aq"; reg = <0x0>; interrupt-parent = <&gpio2>; /* GPIO Bank 2 */ interrupts = <17 IRQ_TYPE_LEVEL_HIGH>; /* Index: 17, level triggered */ spi-cpha; /* SPI mode: CPHA=1 */ spi-cpol; /* SPI mode: CPOL=1 */ spi-max-frequency = <14000000>; /* freq: 14 MHz */ local-mac-address = [ A0 B0 C0 D0 E0 F0 ]; }; }; pinctrl_lpspi3: lpspi3grp { fsl,pins = < MX93_PAD_GPIO_IO08__GPIO2_IO08 0x31e /* Chip Select */ MX93_PAD_GPIO_IO09__LPSPI3_SIN 0x3fe MX93_PAD_GPIO_IO10__LPSPI3_SOUT 0x3fe MX93_PAD_GPIO_IO11__LPSPI3_SCK 0x3fe MX93_PAD_GPIO_IO17__GPIO2_IO17 0x31e  /* Interrupt*/ >; }; I am sending command 0xDA00 to read the signature register value but not getting any response on MISO line. we have followed the below link to come out with above mentioned DTS Configuration  https://coral.googlesource.com/linux-imx/+/refs/heads/codeaurora-linux-4.19.y/Documentation/devicetree/bindings/net/qca%2Cqca7000.txt?autodive=0%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F Please help us to understand what we are missed to configure.  Re: [iMX93AUTO EVK] SPI Configuration for QCA7006AQ with imx93AUTO EVK is not working I have made changes in dts after that QCA7000 chip is working fine.... You can find below changes required in device tree: bacancy@bacancy-ASUS-EXPERTBOOK-B1403CVA-B1403CVAB:~/home/imx93-yocto/imx-yocto-bsp/sources/meta-qca/recipes-kernel/linux/linux-imx$ cat bac_qca7k.patch diff --git a/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts b/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts index 3684f23042dc..1f61cadaf512 100644 --- a/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts +++ b/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts @@ -818,7 +818,53 @@ &wdog3 { status = "okay"; }; +&lpspi3 { + #address-cells = <1>; + #size-cells = <0>; + compatible = "fsl,imx93-spi", "fsl,lpspi"; + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_lpspi3_qca>; + + fsl,spi-num-chipselects = <1>; + + /* Correct CS → GPIO_IO08 */ + cs-gpios = <&gpio2 8 GPIO_ACTIVE_LOW>; + + status = "okay"; + + qca7000: ethernet@0 { + compatible = "qca,qca7000"; + reg = <0>; + + spi-max-frequency = <12000000>; + + /* SPI MODE 3 */ + spi-cpha; + spi-cpol; + + interrupt-parent = <&gpio2>; + interrupts = <12 IRQ_TYPE_LEVEL_LOW>; + + local-mac-address = [A0 B0 C2 D0 E0 F0]; + + status = "okay"; + }; +}; + &iomuxc { + pinctrl_lpspi3_qca: lpspi3grp { + fsl,pins = < + /* SPI signals (CORRECTED) */ + MX93_PAD_GPIO_IO11__LPSPI3_SCK 0x3fe + MX93_PAD_GPIO_IO10__LPSPI3_SOUT 0x3fe + MX93_PAD_GPIO_IO09__LPSPI3_SIN 0x3fe + MX93_PAD_GPIO_IO08__LPSPI3_PCS0 0x3fe + + /* INT → GPIO23 */ + MX93_PAD_GPIO_IO12__GPIO2_IO12 0x1d6 + >; + }; + pinctrl_eqos: eqosgrp { fsl,pins = < MX93_PAD_ENET1_MDC__ENET_QOS_MDC 0x57e diff --git a/arch/arm64/configs/imx_v8_defconfig b/arch/arm64/configs/imx_v8_defconfig index 6e3754f5be47..9dbef1aa8671 100644 --- a/arch/arm64/configs/imx_v8_defconfig +++ b/arch/arm64/configs/imx_v8_defconfig @@ -1199,3 +1199,11 @@ CONFIG_MEMTEST=y CONFIG_VHOST_NET=m CONFIG_IMX_ISPMU=m CONFIG_IMX_ISP_REMOTEPROC=m +CONFIG_NETDEVICES=y +CONFIG_ETHERNET=y +CONFIG_NET_VENDOR_QUALCOMM=y +CONFIG_SPI=y +CONFIG_SPI_MASTER=y +CONFIG_OF=y +CONFIG_QCA7000=y +CONFIG_QCA7000_SPI=y Next step you can check eth0 using plctool command. I hope this information proves useful in resolving similar issues and enables smooth and reliable system operation. Thanks & Regards, Kanji. Re: [iMX93AUTO EVK] SPI Configuration for QCA7006AQ with imx93AUTO EVK is not working Hi @rohitcs0089  From the qca driver function qcaspi_read_register() "https://github.com/qca/qca7000/blob/master/qca-spi/qca_7k.c"   It seems there is no special requirement for CS signal, it used two transfers to read the register, between two transfer, the CS pin will be pulled to invalid. So I think both "MX93_PAD_GPIO_IO08__GPIO2_IO08" and "MX93_PAD_GPIO_IO08__LPSPI3_PCS0" can work for the qca device. Re: [iMX93AUTO EVK] SPI Configuration for QCA7006AQ with imx93AUTO EVK is not working Hi @rohitcs0089, The MISO signal should be generated by slave and it is QCA7006AQ in your design. You need to ask Qualcomm. Best Regards, Richard
View full article
U4N-如何设置 Aion 2 私人服务器进行测试 为什么要设置私人服务器? 私人服务器可让您完全控制游戏环境。你可以 在没有时间压力的情况下,测试班级技能、轮换和连击。 尝试装备升级或强化。 反复运行 PvP 或 PvE 场景。 通过观察受控环境中的行为,更快地学习游戏机制。 对于许多玩家来说,这尤其有助于他们尝试在官方服务器上有风险或昂贵的策略。 开始前的准备工作 在建立私人服务器之前,您需要做好以下准备: 体面的电脑 私人服务器可以在本地运行,但性能取决于 CPU 和内存。配备至少 8GB 内存和现代 CPU 的中档机器足以进行小规模测试。 Aion 2 客户端副本 您需要游戏客户端来连接服务器。确保它与您计划运行的服务器版本一致。 服务器文件 Aion 2 的私人服务器文件经常在社区论坛中共享。查找明确标注用于测试或开发的版本。避免未知来源,降低恶意软件风险。 数据库软件 大多数私人服务器使用 MySQL 或 MariaDB 来存储游戏数据。您需要安装和配置其中一个数据库。 基本网络知识 你不需要成为一名网络工程师,但了解端口、IP 地址和防火墙的工作原理非常重要。客户端必须可以连接到服务器。 步骤 1:安装服务器软件 拿到服务器文件后,第一步就是安装: 提取文件将它们 放在计算机上的专用文件夹中。避免使用系统目录,以减少潜在冲突。 配置服务器设置 打开配置文件。最重要的设置包括 IP 地址:将其设置为本地计算机的 IP 或 127.0.0.1(仅用于本地测试)。 端口号:确保这些端口空闲。典型的 Aion 2 端口通常都包含在文档中。 数据库连接:输入数据库用户名、密码和数据库名称。 运行安装脚本 许多私有服务器包都附带用于初始化数据库的脚本。运行这些操作可创建必要的表格和默认数据。 启动服务器 执行服务器程序。监测控制台是否有任何错误消息。常见问题包括数据库凭证错误或端口已在使用中。 步骤 2:连接客户端 服务器运行后,您需要告诉您的 Aion 2 客户端与其连接。 修改客户端配置 查找配置文件,通常命名为 Aion2.ini 或类似文件。将服务器 IP 更改为您的私人服务器使用的 IP。 测试连接 启动游戏客户端并登录。如果遇到连接错误,请检查防火墙设置并确保服务器正在运行。 创建测试账户 在私人服务器上,您可以创建无限账户进行测试。使用这些账户来尝试不同的版本和装备设置。 步骤 3:使用服务器进行测试 连接后,您就可以开始使用服务器进行任何测试,而不会产生任何后果。一些实用的方法包括 技能轮换测试:运行假人或小怪来测量技能时机和伤害输出。 齿轮实验:测试不同的齿轮组合和升级。许多玩家还会模拟市场,查看物品对游戏进程的影响。 经济模拟:有些玩家喜欢模拟贸易、手工艺和基纳积累。如果您想测试 kinah 获取策略,私人服务器是最佳选择,因为您可以模拟大规模交易、物品种植,甚至使用 Aion 2 kinah 快速交付功能等快捷方式进行受控实验。 步骤 4:常见问题和解决方案 即使是经验丰富的玩家也会遇到常见问题。下面是几个问题及解决方法: 服务器崩溃:通常是由于服务器文件过时或不匹配造成的。确保服务器文件与客户端版本完全一致。 数据库错误:检查凭证和数据库名称。有时会丢失表结构;请重新运行初始化脚本。 延迟或性能缓慢:减少同时在线玩家或 NPC 的数量,并确保电脑符合推荐的规格。 连接问题:验证 IP 地址,在防火墙中打开端口,并确认客户端配置与服务器设置相匹配。 步骤 5:维护服务器 即使是测试,正确维护服务器也是非常有用的: 经常备份:定期备份数据库,避免丢失进度。 谨慎更新服务器文件:如果您下载了更新的版本,请在将其应用到主测试环境之前对其进行单独测试。 记录更改:记录对设置、技能或数据库所做的任何修改。这有助于排除意外行为的故障。 法律和道德方面的考虑 重要的是要记住,私人服务器存在于灰色地带。它们只能用于个人测试和学习,不得用于公开传播或商业目的。避免将私人服务器连接到官方账户,以保护您的数据并遵守游戏的服务条款。 建立一个私人 Aion 2 服务器是一种有效的学习和测试方法,而不会给您的主账户带来风险。按照这些步骤--准备正确的工具、安装服务器文件、配置客户端和维护服务器--您就可以安全地尝试使用技能、装备和游戏中的策略。对于对实际测试感兴趣的玩家来说,即使是像经济模拟这样复杂的过程,也可以在受控环境中进行处理,包括尝试有效管理游戏内货币的概念,如 Aion 2 kinah 快速交付。 私人服务器不仅有助于测试,还有助于更深入地了解游戏。只要有耐心、精心设置并注重细节,您就能在 Aion 2 中创造出改进游戏的宝贵工具。
View full article
UART プロトコル テスト MCXN546VKL で、while (0U == (base->STAT & LPUART_STAT_TDRE_MASK)) で停止しました。 こんにちは。私は NXP の初心者です。IoT モジュールへの UART PIO8 および PIO9 ピンを備えた MCXN546VKL PCB を使用して、MCUXpresso IDE で LPUART プロトコルをテストしようとしています。その前に、UART ポーリングと DMA の TX および RX 機能をテストしようとしています。ポーリングモードのシンプルなループバックUARTテストで、UART TX経由でサンプルデータを送信しようとすると、fsl_lpuart.cファイルの「while (0U == (base->STAT & LPUART_STAT_TDRE_MASK))」で停止してしまいます。FLEXCOMM4に12MHz、システムクロックに150MHzを指定しているのですが、なぜこのようなことが起こるのでしょうか。設定のスクリーンショットの.pngファイルをこの投稿に添付しましたので、ご確認の上、詳細をお知らせください。ありがとうございます。 クロック|タイマー 通信と制御(I3C | I2C | SPI | FlexCAN | イーサネット | FlexIO) 開発ボード MCX N 回复: In UART protocol test MCXN546VKL, it stuck at while (0U == (base->STAT & LPUART_STAT_TDRE こんにちは@Elakiya   MCXN デバイスでは、UART モジュールが実際にクロックされ、TX FIFO レベルが構成された TX ウォーターマーク以下の場合にのみ、TDRE ビットが 1 になります。 FlexComm クロックを有効にしていただいてもよろしいでしょうか? mcxn547 sdk lpuart デモを参照できると思います。   BR ハリー 回复: In UART protocol test MCXN546VKL, it stuck at while (0U == (base->STAT & LPUART_STAT_TDRE こんにちは@Harry_Zhang 、私は MCXN546VKL PCB ボードを持っていますが、あなたの指示に従って、MCXN547V の SDK からの LPUART ポーリングのサンプル ファイルを使用して、uart ピンの同じピン PIO8 と PIO9 を使用し、clock_config.c 内でプロセッサのGlobalInfoと package_id を MCXN456VKL に手動で変更しました。そして pin_mux.c。 プロセッサ: MCXN546 パッケージID: MCXN546VKL プロジェクトをビルドすると、エラーは発生せず、UART ポーリング操作の送受信は正常に行われますが、それでもピン構成設定内でエラー通知が表示されます。問題ツール: MCUconfiguration に表示される通知とエラーの問題のスクリーンショットを共有しました。 構成ページからエラー通知を削除するには、構成でプロセッサ設定も MCXN547 から MCXN546 に変更して、エラーをすばやく修正するにはどうすればよいですか。スクリーンショットを確認し、解決策を更新してください。前もって感謝します。 回复: In UART protocol test MCXN546VKL, it stuck at while (0U == (base->STAT & LPUART_STAT_TDRE こんにちは@Elakiya あなたの以前の投稿を確認しました。 clock_config.c 内のプロセッサの GlobalInfo と package_id を MCXN456VKL に手動で変更しました。および pin_mux.c。 プロセッサ: MCXN546 パッケージID: MCXN546VKL" この方法は間違っているため、エラーが報告されます。現時点では、このエラーを防ぐ方法はありません。 まず、MCXN546とMCXN547は、GPIOの数とフラッシュRAMのサイズ以外はほとんど同じです。 上記のメッセージに基づきます。私には2つの提案があります。 1.MCXN546 SDKをベースにプロジェクトを作成する場合は、mcxn5xxevk_lpuart_pollingをベースにいくつかのファイルを変更するだけで、設定ツールを直接使用できます。 2. mcxn5xxevk_lpuart_polling をベースとして使用する場合は、config tool を直接使用することはできません。しかし、別のmcxn546プロジェクトを作成し、設定ツールを使用して必要なピンとクロックを設定し、生成されたコードをプロジェクトmcxn5xxevk_lpuart_pollingにコピーすることもできます。 BR ハリー 回复: In UART protocol test MCXN546VKL, it stuck at while (0U == (base->STAT & LPUART_STAT_TDRE こんにちは@Elakiya 返信が遅くなり申し訳ありません。mcxn946 SDKパッケージをベースにしたFreeRTOSプロジェクトを作成してみましたか?   BR ハリー 回复: In UART protocol test MCXN546VKL, it stuck at while (0U == (base->STAT & LPUART_STAT_TDRE こんにちは、 @Harry_Zhang さん。上記の問題について、アップデートと解決策を教えていただけないでしょうか。startup_mcxn546_cm33_core0.c でプロジェクトを実行する必要があります。startup_mcxn547_cm33_core0.c で実行する代わりに。手動で作成すると、UARTとMCUでクロック設定の問題が発生します。プロセッサとクロックをmcxn547からmcxn546に手動で変更しましたが、起動ファイルに変更を加えることができず、チップ構成ページにもプロセッサのエラー警告が表示されました。もしくは、mcxn546構成でFreeRTOSを使用したUARTポーリングおよびDMA動作のテストコードを含む、私のシンプルなプロジェクトを提供してください。上記の件について、最新情報をお知らせください。ありがとう。 回复: In UART protocol test MCXN546VKL, it stuck at while (0U == (base->STAT & LPUART_STAT_TDRE こんにちは、 @Harry_Zhang さん。mcxn546 や mcxn946 では作成していませんが、最初に mcxn546 で基本的な UART 操作を実行しようとしましたが、動作せず、UART と MCU でクロックの問題が発生しました。そこで、SDKからmcxn547のUARTポーリングのサンプルプロジェクトを作成し、pin_mux.cでプロセッサとパッケージIDを手動で変更しました。および clock_config.cmcxn546 MCU向けに構築・製造する。私のmcxn546ボードでは、UARTデータの送受信が行われています。しかし、startup_mcxn547_cm33_core0.c で実行されており、.mex のピン構成ページに表示されます。下記にファイルを示します。 startup_mcxn546_cm33_core0.c で実行して、config のこのエラーを解消する必要があります。この投稿にプロジェクトを添付しましたので、ご確認ください。 問題: MCUXpresso_IDE プロジェクトで検出されたプロセッサ「MCXN547」が、現在選択されている「MCXN546」と一致しません。 レベル: エラー
View full article
FRDM-MCXW71 调试问题 您好,NXP团队: 我正在开发 FRDM-MCXW71 板,正在尝试调试 m cxw71_evk_cmsis_button_toggle_led 的示例和一些使用 mcuxPresso 编写 Visual Studio Code(版本 26.2.46)的 BLE 示例。但是,调试会话没有启动。 它显示了以下错误 无法启动:远程连接已关闭 (从目标选择扩展远程 172.0.0. 1:2356) 我还尝试过使用 LinkFlash(Linkflash v25.12.83)对板进行编程,但它显示了这个错误: 无法连接到核心 Et:31:无法连接到芯片的调试端口 PC: (100) 目标操作失败 在硬件方面,USB_ACT 绿色 LED 亮起,ISP_EN_MLINK 红色 LED 闪烁,USB LED 也亮起。 之前开发板运行良好,但现在我无法调试或刷新任何示例。 请问如何解决这个问题? 我附上了屏幕截图以供参考。#mcxw71 #FRDMMXCW71 模拟(ADC|CMP|DAC|OPAMPS) 核心与内存 FRDM 培训 MCXA MCXC MCX N USB Re: FRDM-MCXW71 debug issue 你好,希望你一切都好。 你能否确认一下你是否能够构建和调试这个之前的任何其他示例?您使用的是哪个版本的 SDK?您能够运行的最后一个示例是什么? 由于您使用的是 MCXW71-EVK 示例,能否请您尝试导入 FRDM-MCXW71 示例(标有"frdmmcxw71_cmsis_button_toggle_led" ),并告诉我是否有效?   谨致问候, Ana Sofia。 Re: FRDM-MCXW71 debug issue 你好, 感谢您的答复。 我使用的是 SDK 25.12 版本。早些时候,示例 mcxw71_evk_cmsis_button_toggle_led 在 FRDM-MCXW71 板上运行,BLE 示例也能正常运行。 收到您的回复后,我再次下载了 FRDM-MCXW71 SDK 25.12 版,并尝试调试和运行 frdmmcxw71_cmsis_button_toggle_led 示例。但是,我还是遇到了同样的问题:,同样的问题出现在 " 启动 GDB 服务器:"C:\\NXP\\LinkServer_25.12.83\\LinkServer.exe"-l5 gdbserver " mcxw716cxxxa: frdm-mcxw71 "--probe U04N4UXLTCAYZ--gdb-port 2330--no-boot--core primary--redlink-port 2440 请查看终端选项卡(GDB 服务器控制台)查看 " C:\NXP\LinkServer_25.12.83\ LinkServer.exe " 的输出 输出基数现在设置为十进制 10、十六进制 a、八进制 12。 输入基数现在设置为十进制 10,十六进制 a,八进制 12。 错误 103:无法启动 GDB:远程连接已关闭(从目标选择扩展远程 127.0.0. 1:2330)",你 能帮我理解如何解决这个问题吗? Re: FRDM-MCXW71 debug issue 恩智浦团队您好, ,能否请您在方便时提供最新信息? 如果需要我提供任何补充信息,请告诉我。 谨致 Ramdev Re: FRDM-MCXW71 debug issue 恩智浦团队您好, ,能否请您在方便时提供最新信息? 如果需要我提供任何补充信息,请告诉我。 谨致 Ramdev Re: FRDM-MCXW71 debug issue 你好   如果启动时发生错误,D7 LED 会快速闪烁。你能否尝试使用第 3.4 节使用 UM12063 FRDM-MCXW71 板用户手册的固件更新实用程序更新 MCU‑Link 固件中所述的步骤更新 MCU‑Link 调试固件?   使用 MCU-Link 调试 MCXW71 MCU 所需的跳线和连接器设置,请参见第 3.2 节 "支持的调试方案"。你能否帮我验证一下你的 FRDM 板上的这些设置,以及 JP5 是否已打开,这样 MCU‑Link 就可以正常启动。当 JP5 短路时,MCU‑Link 将被迫进入互联网服务提供商模式,无法遵循其标准启动顺序。   另外,为了确认一下,您之前运行的是哪个 BLE 示例?您测试过低功耗的例子吗?设备也有可能进入低功耗状态。   致以最诚挚的问候, Ana Sofia。 Re: FRDM-MCXW71 debug issue 你好@sofiaurueta, 1) D7 LED 以 1 秒间隔闪烁。我参考了用户手册第 3.4 和 3.2 节,并验证了跳线和连接设置。但是,使用 LinkFlash 和 VS Code 调试时,板仍然无法闪烁。前面提到的问题依然存在。 我只启动了 adv_ext_central_freertos 示例和按钮切换 LED 示例。我没有闪存过任何低功耗示例。 请问如何解决这个问题? Re: FRDM-MCXW71 debug issue 您好 , 能否请您在方便时提供最新信息? 如果需要我提供任何补充信息,请告诉我。 谨致 Ramdev Re: FRDM-MCXW71 debug issue 您好 , 能否请您在方便时提供最新信息? 如果需要我提供任何补充信息,请告诉我。 谨致 Ramdev Re: FRDM-MCXW71 debug issue 你好 你能试着进行一次大规模清除吗?在 J-Link Commander 中使用"unlock kinetis" 命令,或通过 MCUXpresso(使用图形用户界面闪存工具)使用大量擦除命令,同样有效。 之后,你可以尝试运行 hello_world 或 BLE 示例,以确保板正常运行。   如果还不行,我会尝试使用外部调试器。 希望这能帮到您。 致以最诚挚的问候, Ana Sofia。
View full article
S32G3 は RGMII を使用して、RGMII チャネルを持つ別の MCU と相互接続します。 こんにちは S32G399のRGMIIチャネルを使って、別のMCUのRGMIIと通信したいのですが、これは可能ですか?相互接続時にTXチャネルとRXチャネルをクロス接続する必要がありますか?       ゴールドVIP Re: S32G3使用RGMII与另一个具有RGMII通道的MCU互联通讯 こんにちは、 @MichaelTao こんにちは 1. 理論的には、これは実現可能です。 2. 相互接続する場合はクロス接続が必要です。 BR チェイン
View full article
blkwfdll not working in certain machines with Windows 11 I use flashFirmware in blkwfdll. We have a build of the dll that I call from a .net application. The same .dll has worked since 2018, but recently it's been failling in Windows 11. A machine was updated to windows 11 enterprise build 26200.7705. After that, a new instantiation of Updater threw a "could not connect" error. The machine previously had no issues using blfwkdll.dll. The device instance of the the HID-compliant vendor-defined device that blfwkdll.dll connects can be seen properly connected in device manager. Another laptop with build 26200.7705 works fine with blfwkdll.dll. Are there other reports of issues? Is there a new version blfwkdll.dll I could try? I found the source code, but I'm having trouble building the .dll in such a way that my .net application can use it as a reference, as it has before. Thanks! Re: blkwfdll not working in certain machines with Windows 11 Hello @ryan_pearson , Thanks for your post. Sorry, blfwkdll is no longer maintained. You can try the blfwkdll located under the blhost directory. I'm not sure whether it is newer than the version you are currently using, but you can give it a try. blhost download link: https://www.nxp.com/webapp/Download?colCode=blhost_2.6.7&appType=license&location=null PATH: path\to\blhost\blhost_2.6.7\blhost_2.6.7\tools\common\blfwkdll BR Celeste Re: blkwfdll not working in certain machines with Windows 11 If blkfdll is no longer maintained, is there an alternative? Re: blkwfdll not working in certain machines with Windows 11 Hello @ryan_pearson , Thanks for your sharing, I am glad to hear that.  Wish a happy day. BR Celeste Re: blkwfdll not working in certain machines with Windows 11 I was able to fix this issue by changing Line 236 of hid-windows.c from: DWORD share_mode = (enumerate) ? FILE_SHARE_READ | FILE_SHARE_WRITE : FILE_SHARE_READ; to DWORD share_mode = FILE_SHARE_READ | FILE_SHARE_WRITE; This matches hidapi.
View full article
Consulting on the compatibility of FS27 RTD and BMS GEN2 RTD Hi Experts, The customer's new BMS project wants to use S32K358 + FS27 + BMS GEN2 SDK. I learned from the BMS team that: BMS GEN2 SDK AUTOSAR 4.4 R21-11 Version 0.9.1 CD05 and BMS GEN2 SL SDK AUTOSAR 4.4 R21-11 Version 0.9.1 CD05 will be available next week. This supports S32K3 RTD 6.0.0 integration. The BMS GEN2 SDK will be migrated to S32K3 RTD 6.0.0 in BMS release v1.0.0 somewhere in Q1 '26. In other words, the BMS GEN2 SDK will be compatible with S32K3 RTD 6.0.0 in the near future. The customer needs a 24V platform and therefore wants to use FS27 instead of FS26. I found the following two versions of FS27 from Automotive SW - SBC/PMIC - Real Time Drivers: S32K3xx SBC FS27 R21-11 0.8.0 based on S32K3 RTD 5.0.0 SBC FS27 R23-11 1.0.0 based on S32K3 RTD 7.0.0 Q1. The customer is concerned that the drivers for FS27 and BMS GEN2 SDK are incompatible because the S32K3 RTD versions do not appear to be consistent.  If S32K3 RTD 6.0.0 is selected in the BMS GEN2 SDK, will there be any problems if the customer uses S32K3xx SBC FS27 R21-11 0.8.0 or SBC FS27 R23-11 1.0.0? Q2. Does the FS27 have a driver based on S32K3 RTD 6.0.0? Would you please help me? Thank you for the help in advance! Best Regards, Robin Here is the information of customer: Contact Name                TengHsaing Wen Email (Contact)              [email protected] Company                        XINGMOBILITY AA SW - External Device Priority: MEDIUM Source: Direct Customer Re: Consulting on the compatibility of FS27 RTD and BMS GEN2 RTD Hi Viktor, Thank you for your information. The "BMS GEN2 SDK AUTOSAR 4.4 R21-11 Version 0.9.1 CD05" based on S32K3 RTD 6.0.0 is not yet available for download. Once it becomes available for download, I will at least test whether it can be compiled successfully. Best Regards, Robin Re: Consulting on the compatibility of FS27 RTD and BMS GEN2 RTD Hello Robin, there is no dedicated release for RTD 6.0.0, but the latest version (FS27 1.0.0) should be backwards compatible with it. In case of any issues, please let us know. Best regards, Viktor Re: Consulting on the compatibility of FS27 RTD and BMS GEN2 RTD The topic has been redirect to the team to investigate it. Contact point: Razvan Tilimpea / Cristian Durla or Viktor Obr Re: Consulting on the compatibility of FS27 RTD and BMS GEN2 RTD Hi Viktor, "BMS GEN2 SDK AUTOSAR 4.4 R21-11 Version 0.9.1 CD05" is now available for download.  The customer questioned whether the AUTOSAR versions of the two drivers, R23-11 and R21-11, would differ significantly and cause compatibility issues if they were paired with SBC FS27 R23-11 1.0.0. Best Regards, Robin Re: Consulting on the compatibility of FS27 RTD and BMS GEN2 RTD Hi @viktorobr , "BMS GEN2 SDK AUTOSAR 4.4 R21-11 Version 0.9.1 CD06" is now available for download.  The customer questioned whether the AUTOSAR versions of the two drivers, R23-11 and R21-11, would differ significantly and cause compatibility issues if they were paired with SBC FS27 R23-11 1.0.0. Best Regards, Robin Re: Consulting on the compatibility of FS27 RTD and BMS GEN2 RTD Hi Robin, compatibility between different Autosar versions is tricky, we would have to compare all of the drivers used by both of the components you try to integrate and I'm not 100% familiar with the BMS SDK. I can tell you that between the FS27 versions and the drivers it uses we didn't notice major changes between R21-11 and R23-11, there might be some minor differences that will appear right away when you combine the components in one project (version specific macros etc.), but from functional point of view it should still behave the same. Best regards, Viktor
View full article
SDK 2.2.0 MKL16Z128xxx4 和 McuXpresso IDE V25.6 你好,我以前使用过 McuXpresso V19.xxx 和上述 SDK,在构建时没有问题。 将集成开发环境升级到 V25.6 后,fsl_common.c 出现问题,错误信息是 构建目标:MKL16_BLE_CLIENT_V1_0.axf 调用:MCU 连接器 arm-none-eabi-gcc-nostdlib-Xlinker-Map= " mkl16_ble_client_v1_0.map "-Xlinker --gc-sections -Xlinker -print-memory-usage -Xlinker --sort-section=alignment -Xlinker --cref -mcpu=cortex-m0plus -mthumb -T MKL16_BLE_CLIENT_V1_0_Debug.ld -o"MKL16_BLE_CLIENT_V1_0.axf"./source/LPS22HH_driver.o ./source/LSM6DS3_driver.o ./source/STHS34PF80TR_driver.o ../source/VL53L1_driver.o ./source/adc_driver.o ./source/batt_driver.o ./source/ble_driver.o ./source/cop_driver.o ./source/eeprom_driver.o ./source/fonts.o./source/i2c_driver.o ./source/init_dev_from_struct.o ./source/irq_driver.o ./source/led_driver.o ./source/lptmr_driver.o ./source/main.o ./source/mode_driver.o ./source/mtb.o。/source/oled_driver.o。/来源/semihost_hardfault.o。/source/spi_driver.o。/source/swd_driver.o。/source/uart_driver.o。/drivers/fsl_adc16.o。/drivers/fsl_clock.o。/drivers/fsl_cmp.o。/drivers/fsl_common.o。/drivers/fsl_dac.o。/drivers/fsl_dma.o。/drivers/fsl_dmamux.o。/drivers/fsl_flash.o。/drivers/fsl_gpio.o。/drivers/fsl_i2c.o。/drivers/fsl_i2c_dma.o。/drivers/fsl_llwu.o。/drivers/fsl_lpsci.o。/drivers/fsl_lpsci_dma.o。/drivers/fsl_lptmr.o。/drivers/fsl_pit.o。/drivers/fsl_pmc.o。/drivers/fsl_rcm.o。/drivers/fsl_rtc.o。/drivers/fsl_sim.o。/drivers/fsl_smc.o。/drivers/fsl_spi.o。/drivers/fsl_spi_dma.o。/drivers/fsl_tpm.o。/drivers/fsl_tsi_v4.o。/drivers/fsl_uart.o。/drivers/fsl_uart_dma.o。/board/clock_config.o。/board/peripherals.o。/board/pin_mux.o。/cmsis/system_mkl16z4.o C: /nxp/mcuxpressoide_25.6.136/ide/plugins/com.nxp.mcuxpresso.tools.win32_25.6.0.202501151204/Tools/bin/.../lib/gcc/arm-none-eabi/14.2.1/../../../../../../arm-none-eabi/bin/ld.exe:。/drivers/fsl_common.o:在函数 `__assertion_failed' 中: C:\Software Projects\ConSyTech\MKL16_BLE_CLIENT_V1_0\workspace\MKL16_BLE_CLIENT_V1_0\Debug/../drivers/fsl_common.c:49:(.text.__assertion_failed+0x10):对 “dbgConsole_printf” 的未定义引用 已用内存区域大小 区域大小%已用内存年龄 程序闪存: 12728B 128KB 9.71% Sram: 2968 B 16 KB 18.12% collect2.exe:错误:LD 返回 1 退出状态 make[1]:*** [makefile:48: MKL16_BLE_CLIENT_V1_0.axf] (译注:MKL16_BLE_CLIENT_V1_0.axf)。错误 1 make:*** [makefile:39: all] 错误 2 " make-r-j8 all " 以退出代码 2 终止。版本可能不完整。 08:49:54 版本失败。3 个错误,0 个警告。(耗时 430 毫秒) 请教如何纠正。 克莱斯 Re: SDK 2.2.0 MKL16Z128xxx4 and McuXpresso IDE V25.6 你好@claeskjellstrom 请添加 debug_console 和 serial_manager 元器件。如果问题仍然存在,请分享您的项目,我将帮助您进行检查。   谢谢!   BR 爱丽丝 Re: SDK 2.2.0 MKL16Z128xxx4 and McuXpresso IDE V25.6 嗨,Alice,因为时间有点紧,我又换回了 11.9.1Build 2710 版的集成开发环境,但现在的问题似乎是我根本看不到"Clocks Diagram" ,MKL02 和 MKL16 MCU 都是如此。它们之前一直在工作,但无论" 关于透视" ,我都看不到它们,而且由于它是一个裸金属项目,一直在低功耗(不同的时钟设置)下运行,所以非常依赖它们。说来话长,我尝试了各种方法,最后在 MKL02 项目中,通过更改 mexfile,我现在可以看到它们了。 如果我从一个完全空白的项目开始,除了某些文件外,总是看不到时钟图? 此致 克莱斯       Re: SDK 2.2.0 MKL16Z128xxx4 and McuXpresso IDE V25.6 通过删除 x:// Program Data 文件夹/NXP/!!!!!!!!!delete 下以前版本的所有安装文件解决了这个问题。 Re: SDK 2.2.0 MKL16Z128xxx4 and McuXpresso IDE V25.6 您好, 谁能描述一下 mcuXpresso 版本和 mcu 配置工具之间的关系?如前所述,我使用的是 IDE 11.9.1,并尝试了不同版本的配置工具。我用 MKL16Z128xxx 的正确 SDK 制作了一个干净的项目,调用了所有驱动程序(fsl)等。据我所知,如果你有很久以前的配置工具生成的 mex 文件,你就不需要下载它,但显然版本真的很糟糕。当我运行配置工具作为独立组网 (SA)时,我收到的消息要么是太旧的版本,要么是更新版本。似乎什么都不合适。 Re: SDK 2.2.0 MKL16Z128xxx4 and McuXpresso IDE V25.6 您好, 对所附的屏幕转储有何评论?
View full article
S32K388 上的 V11_STANDBY 您好, 我正在研究 S32K388 电源管理单元,我有一些问题: 1.V11_STANDBY 是否与 V11_RUN 隔离?进入待机状态时,将选择 V11_STANDBY 作为待机功率域,这是正确的吗? 2.V11_STANDBY 的来源是什么?我查看了电源管理单元图,看起来 V11_STANDBY 有两个可用的电源,即 VDD_HV_A 和 V15。如果 V11_STANDBY 信号源确实有两个选项,那么如何确定应用哪个? 非常感谢、 南 Re: V11_STANDBY on S32K388 @namnguyenviet_001 你好、 1.是的。 在运行模式下,将使用 启动 和 FPM(最后一英里分布式稳压器)创建 V11_ STANDBY 电源。 在待机模式下,不必提供 V15,因为备用功能域电源 V11_SANDBY 将使用 LPM 创建。 2。对于S32K38x,来自V15电源的电流将流过V11调节阶段的外部NMOS,并流入该器件的V11引脚。V15 可由内部 SMPS 或线性稳压器产生,两者均由VDD_HV_A或VDD_HV_B 供电。 您可以参考 硬件设计指南 和 S32K3xx 参考手册第 41.1.4 章如需更多信息,请联系 致以最诚挚的问候, Julián
View full article
Ultra low power accelerometer The FRDM-KL05Z board comes with a built in MMA8451Q accelerometer with I2C interface. In general I2C isn't the best idea for ultra low power demo, because it is so slow. We need to run the processor at least 100 to 200 usec to get the accelerometer readout (6 Bytes + overhead). Then i connected a LIS331HH SPI/I2C accelerometer and implemented SPI at 24 MHz/4 to get the readout within 12 usec, which is a lot better. I can get this down to about 8 usec with 20 MHz/2. But the SPI accelerometer has much more noise (650 versus 130 or 100 ug/sqrt(Hz)). This means the onboard accelerometer of the FRDM-KL05Z is a lot better concerning noise. Is this because it is I2C? Can we use the MMA8451Q with SPI? Is there/will there be a SPI version of the MMA8451Q that serves better for ultra low power applications? Re: Ultra low power accelerometer Dieter, Regarding your last question, we are planning to launch such a part in June with full production. It will be basically the same device as the MMA8451Q, but now including the SPI. Have you considered using the embedded FIFO buffer on the MMA8451Q? It is very useful for system power savings and minimizing traffic across the I2C bus. Look at our AN4073 for more information on the embedded FIFO buffer. Regards, Tomas Re: Ultra low power accelerometer Hi, Dieter Yes, I think you can use KL15 and analog sensor for your application. Thanks. Best Regards Paul Re: Ultra low power accelerometer Thanks for your response. I could not find a noise spec of the MMA745xL. It has a consumption of 400 uA and 10 bits of resolution. As far as i understand, with a Kinetis KL device onboard i can as well try an analog accelerometer. For example with a LIS344ALH, at 50 Hz x 2 msec usage, the current consumption could be as low as 70 uA plus the consumption of 150 ADC conversions per second in the KL15. I mean from the low power point of view the analog transfer of acceleration measurements could be the best solution. And the LIS344ALH has a noise spec of 50 ug/sqrt(Hz), which is even better than the MMA8451Q. Re: Ultra low power accelerometer Hi, Dieter The I2C interface in KL series is designed to operate up to 400 kbit/s with maximum bus loading and timing. The I2C device is capable of operating at higher baud rates, up to a maximum of clock/20, with reduced bus loading. I find a g-sensor with SPI interface for your reference. Please check if MMA745xL series meet your requirement. You can find some material from link. http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MMA745xL&fpsp=1&tab=Documentation_Tab Hope my reply can help you. Best Regards Paul
View full article
FXPS7140P4 un-programmed default PSI5 communication Hi Can I communicate with FXPS7140P4 sensor with default setting? or it has to be programmed through PSI5 first in order to receive sensor data from it? If I can communicate with default setting then what is the default mode? asynchronous, synchronous, 10bit/16bit data, parity or CRC ? Regards, J Pressure Sensors Re: FXPS7140P4 un-programmed default PSI5 communication Hi Joe, Yes, but it can be shared under NDA only. If you have not signed the NDA with NXP yet, please create a standard case for my colleagues who are in charge of the NDA process and can eventually help you with that. Best regards, Tomas Re: FXPS7140P4 un-programmed default PSI5 communication Hi @TomasVaverka : Hope you are doing good. Is the official datasheet for FXPS7140P4 released yet ? We are waiting for it. You mentioned about the release date is around end of January 2022.  Best Regards, Joe Re: FXPS7140P4 un-programmed default PSI5 communication Hi Thomas, I got one more question for you. Can I set value 0x1A to register $25. Especially, the DATA_EXT bit, it allows us to read data range between -480 to +480 LSB according to the draft document(negative 16% to positive 16% for relative pressure). I have tried writing value 0x8A to register $25, it is working fine but again according to the draft document, it only allows us to read -102 to +307 LSB (which I can only read 3% of negative pressure change and 10% of positive pressure change ). Regards, Joe Re: FXPS7140P4 un-programmed default PSI5 communication Hi Tomas, Thank you for the detailed explanation and the pressure range again. With your word, I can rest assured that there is not thing bad happening during the programming. It was me changing the value in register $40 which resulted in OTP MEM fault. Although I have broken some samples here, you save me some samples that I was going to test. Thank you. I will look forward to the release of the document for this pressure sensor. Best Regards, Joe Re: FXPS7140P4 un-programmed default PSI5 communication Hi Joe, The pressure range cannot be changed in this device otherwise it will set the errors. The intension initially was to be able to change the range if a large opportunity presented itself and this can be evaluated on a case by case bases. With this said $40, range has been revised to "Reserved". This will be updated in a future release of the datasheet which I am guessing should be ready in the end of January 22. The datasheet will have the following for this register: The pressure range should be 40 kPa to 140 kPa. Best regards, Tomas Re: FXPS7140P4 un-programmed default PSI5 communication Hi Thomas,  We got a few samples here from local NXP, I cannot seem to understand the register 0x40. Whenever I set USER RANGE[1:0] bit to 0x01, and programed the chip with the rest of register setting indicated by programming manual. It resulted in MEMTEMP_ERR and U_OTP_ERR, which I cannot read sensor value. (would always read 0x1EB). However, if we set the USER RANGE[1:0] to 0x00 with the same setting of the other registers (again specified by programming manual and not modifying the 0x16 COMM bit), it would read pressure value just fine, and there is no MEMTEMP_ERR & U_OTP_ERR bits set. (the voltage setting and sync pulse width all conform to the sensor manual ) As our manual dose not elaborate on USER RANGE bit, we just want to confirm that the setting of 0x00 for register 0x40 can read the range as document specified 50kPA to 126 kPA for sensor FXPS7140P4. Regards, Joe Re: FXPS7140P4 un-programmed default PSI5 communication Hi Tomas, Thanks for your reply Regards, Joe Re: FXPS7140P4 un-programmed default PSI5 communication Hi Joe, All registers are set to 0 for any PSI5 configuration. So register 25 is 00 (PSI5_CFG). If you have a PSI5 device (FXPS7140P4), then you have to use PSI5 to use/comm to the device. With this said, the COMMTYPE bit field is set to 1 in register 16. If you try to changes this, it will produce an error so caution must be taken if you want do any over writes to the UF2 region in that this should be masked. Best regards, Tomas
View full article
Android 11で拡張されたOV5640カメラのプレビュー Android 11 (android-11.0.0_2.6.0) を実行している i.MX8MP を搭載した OV5640 カメラ (MIPI-CSI) を使用しています。カメラは正常に動作しますが、カメラ アプリケーションのプレビューが引き伸ばされます。カメラで撮影した写真は正しいアスペクト比を持ち、プレビューのみが引き伸ばされます。1280x720 ディスプレイを使用しています。 何が問題なのか、何かアイデアはありますか?カーネルドライバー?Libcamera? Re: OV5640 Camera Preview Stretched in Android 11 こんにちは、 これはプレビュー間のアスペクト比の不一致です。Android カメラのソースコードでカメラ パラメータを変更することをお勧めします。これについては、「Android ユーザー ガイド」のセクション 8.1 カメラ設定で確認できます。 よろしくお願いいたします。 Re: OV5640 Camera Preview Stretched in Android 11 どのカメラパラメータを変更すればよいですか?Android ユーザーズ ガイドのセクション 8.1 でカメラの設定について説明されていますが、プレビューの問題が発生しています。撮影された画像のアスペクト比は正しく、カメラの設定が正確であることを示しています。この問題はアプリケーション内のカメラ プレビューに限定されており、カメラ自体ではなく、ディスプレイのサイズやスケーリングに関連している可能性があることを示しています。何か提案はありますか? Re: OV5640 Camera Preview Stretched in Android 11 この問題は、HAL(ハードウェア抽象化レイヤー)またはcamera_config.xmlのアスペクト比の不一致が原因である可能性があります。要求されているプレビュー解像度がディスプレイの 16:9 比率と一致しない場合。カメラの HIDL 実装をチェックして、StreamConfigurationMap が切り取りや伸縮なしでセンサの出力と一致するプレビュー サイズを提供していることを確認します。 Re: OV5640 Camera Preview Stretched in Android 11 カメラの設定を確認しましたが、すべて問題ないようです。一つ気づいた点があります。カメラのプレビュー画面は、カメラの向きとディスプレイの向きが異なる場合にのみ引き伸ばされます。画面の向きを0に設定すると、プレビューは正常に表示されます。しかし、私たちのデザインではカメラを回転させる必要があるため、90度に設定しています。 Camera2アプリ内の問題のようですが、原因について何かアイデアはありますか?
View full article
S32K144 unlock Secure debug Hi, We are attempting to unlock secure debug on an S32K144 device using winIDEA. According to iSYSTEM documentation  NXP S32: Unlocking secure debug on NXP S32G2/3xx and S32R45x secure debug unlocking is supported for S32G2 and S32K3 devices with password parameters. However, when configuring the S32K144 in winIDEA CPU Options, the security unlock parameters (Protection, Password, SmartCardPassword) that are available for S32G2/S32K3 devices are not present. **The connection script $(SFR_FILE_DIR)/S32K1xx_ConnectToSoC.cpp contains no unlock parameters or security-related functions for S32K144 devices** Questions: 1. Does S32K144 support secure debug unlocking? 2. If yes, what is the proper procedure for S32K144? 3. Are there alternative methods or tools for S32K144 secure debug unlock? Re: S32K144 unlock Secure debug Hi, Thank you for the references provided. We have reviewed: - S32DS1.3 Backdoor Access Key example - winIDEA S32K1xx JTAG Lock blog The winIDEA blog shows how to lock S32K1xx devices using Flash Security byte (0x40C), but we need the procedure to UNLOCK an already secured S32K1xx device via winIDEA. The iSYSTEM unlock documentation only covers S32K3xx and S32G2xx devices with password parameters, which are not available for S32K1xx in winIDEA. Could you please provide: 1. The specific winIDEA procedure to unlock a secured S32K1xx device? 2. How to configure the backdoor access key method in winIDEA for S32K1xx? Re: S32K144 unlock Secure debug Hi @Kishore_14, 1. Yes. However, it is somewhat different than S32K3xx procedures. The JTAG/SWD interface will be disabled when the part is secured. This means that a debug controller cannot read or write to SOC memory mapped addresses when the part is in this state. The part is secure when the FTFC_FSEC byte is in a secure state in the flash configuration field.  2. Please refer to AN12130 & Example S32K144 Verify Backdoor Access Key S32DS1.3. Also, chapter 5.2.1 Flash memory security from S32K1xx reference manual also explains how the FSEC field works. 3. There is also the JTAG Lock procedure on NXP S32K1xx blog from winIDEA. It is the same documentation as the S32K/G/R link you've shared, but focused on the K1 devices. Best regards, Julián Re: S32K144 unlock Secure debug Hi @Kishore_14, I am not sure what is the specific procedure to unlock the S32K device through winIDEA. Since this SW is not from NXP, rather from a third-party, could you try contacting them instead? Online Help - iSYSTEM. In order to unlock the S32K1xx, you either need to enable and enter the backdoor key or mass erase must be enabled. The backdoor key can be used to unlock the MCU by the FTFC command only. (Unlock flash on S32K144W from firmware - NXP Community) If you want to unlock the MCU from outside, you need to mass erase the whole chip.  I've found this post explaining the same thing, using winIDEA: Arm Cortex-M: Locked/secured device - TASKING Knowledge Base. Best regards, Julián Re: S32K144 unlock Secure debug We have an additional question regarding S32K1xx secure debug unlock: Hardware Debugger Support: 1. S32 Debugger- Shows "Secure debugging" option in S32DS: - "Enable secure debugging" checkbox available - "Debugging type: Password" dropdown available -  We don't have S32 debugger hardware   2. PEMicro Debugger - No secure debugging option visible: -  We have PEMicro hardware -  No secure debugging options in S32DS interface -  We don't have PEMicro license 1. Does PEMicro debugger support S32K1xx secure debug unlock? 2. Is the secure debugging feature only available with S32 debugger hardware? 3. If PEMicro supports it, how do we enable secure debugging options for S32K1xx with PEMicro? Re: S32K144 unlock Secure debug Hi @Kishore_14, 1. Does PEMicro debugger support S32K1xx secure debug unlock? Not as far as I'm aware.  2. Is the secure debugging feature only available with S32 debugger hardware? Secure debugging is only available for S32G/R/Z devices. You can see that selecting the S32K144 device disables the "Secure debugging" option: 3. If PEMicro supports it, how do we enable secure debugging options for S32K1xx with PEMicro? If they support any kind of scripts, you can ask their support page: PEmicro Support Home. However, as I've mentioned, you have two methods: backdoor key by the FTFC command or mass erase the whole chip (if mass erase is enabled). Best regards, Julián Re: S32K144 unlock Secure debug Hi Julian, Following up on your previous response about "backdoor key by FTFC command" for S32K1xx: 1. When you mention "backdoor key by FTFC command," do you mean using the example project Example_S32K144_Verify_Backdoor_Access_Key_S32DS1.3_v2 approach with FTFC command 0x45? 2. If I'm using a different project (like a bootloader), do I need to hardcode the backdoor key unlock code into every project? Thanks. Re: S32K144 unlock Secure debug Hi @Kishore_14, 1. Yes.  2. I'm not sure if I understood the question correctly. The FSEC register is a read-only register and is loaded with the content of the flash security byte in the Flash Configuration Field located in program flash memory during the reset sequence. The configuration field holds the Backdoor comparison key as well and is configurable in startup_S32K1XX.S file. If you are referring to loading the key through FTFC, you can create a routine which receives the key through UART, CAN, SPI, etc. (except JTAG/SWD) and loads the key, thus un-securing the device and unlocking JTAG/SWD interface as well until the next reset. Best regards, Julián
View full article
(88w8897) is disabling 2.4GHz capabilities possible? Dear NXP, Is it possible to switch off the 2.4GHz completely? We want to disable the support for the 2.4GHz at the driver level. From this link: Disable 5GHz band for 88W8987, we can see that during driver load, the dev_cap_mask can be used to enable support for specific bands. However, there is no documentation that explains how each bit of dev_cap_mask should be configured. If we only want to switch off the 2.4GHz, what value should dev_cap_mask be set to? Re: (88w8897) is disabling 2.4GHz capabilities possible? Hi, You can refer to https://community.nxp.com/t5/Wi-Fi-Bluetooth-802-15-4/How-to-disable-the-2-4GHz-band-on-the-88W8897/td-p/2047926. Regards, Daniel. Re: (88w8897) is disabling 2.4GHz capabilities possible? Hi, We would like to use dev_cap_mask to disable 2.4GHz capabilities. Could you please provide us with more information about dev_cap_mask? BR, Peter
View full article
从中断处理程序进行 I/O 操作 本问题的相关参数如下: 1。IDE:适用于 ARM v 2.2 的 S32 DS(是的,我知道这个已经过时了,但是有问题的产品也是;我们需要支持现有代码) 2.芯片:S32K148 3.操作系统视窗 11 4.系统操作系统:裸机 在 ISR 中尝试执行任何类型的 SPI 主传输都会挂起,通常被中断的 API 是阻塞 I/O(I2C 或 SPI)调用。 在阻塞调用(调用 LPSPI_DRV_MasterTransferBlocking())中,通话挂起是因为 SysTick 中断似乎没有发生,因此 MCU 无法感知时间流逝。 在非阻塞调用(LPSPI_DRV_MasterTransfer(),然后是 LPSPI_DRV_MasterGetTransferStatus(SPI1,&byte_remaining))中,byte_remaining 保持原值。我尝试在调用 LPSPI_DRV_MasterAbortTransfer() 进行异步传输之前,添加对 LPSPI_DRV_MasterAbortTransfer(SPI1) 的调用,但结果还是一样。 关于一个半相关的问题,是什么触发了 SysTick_Handler()?我的直觉告诉我,它应该一直运行,每 1 毫秒增加一次刻度计数,但在其正文中设置一个断点似乎只能在某些时间触发。奇怪的是,即使阻塞性 SPI 传输成功,有时也不会触发,如果系统定时器之前未触发,则应触发系统定时器。 另一个半相关的问题是,在 SPI 的 S32 Cookbook 示例代码中,没有使用 SDK 提供的应用程序接口;这些示例直接完成了所有寄存器位操作。是否有更接近生产价值代码的示例,因为它们至少调用了恩智浦的应用程序接口,而不是重新发明轮子? Re: Doing I/O from an interrupt handler 你好@PetrS 非常感谢。中断优先级确实解决了这个问题。不过,我有一个问题: 我同意在 ISR 中阻塞不是一个好主意,但在单线程应用程序中又有什么办法呢?我可以在应用程序上下文中旋转,直到 SPI 传输完成。这将允许其他 I/O 中断发生(我的理解是,负优先级中断无论如何都会触发;当进入正优先级 ISR 时,它们不会被禁用)。但是在我的情况下,进行重叠的 I/O 既不可能,也不可取。 1.这是不可能的,因为 S32K148 是所有总线的总线主控器。因此,如果它在 ISR 中进行 SPI 传输,则可能无法驱动另一条 I/O 总线,因此无法触发中断。 2.这并不可取,因为 ISR 之间可能存在共享全局,所以我不想在当前 I/O 完成之前启动新的 I/O。 对于单线程裸机应用程序,您建议如何处理这种情况? Re: Doing I/O from an interrupt handler 您好, 好吧,那么只需中断优先级就能导致这种行为。阻塞 API 会挂起的原因很简单,如果两个中断具有相同的优先级,那么当 GPIO ISR 处于活动状态时,LPSPI ISR 就无法运行。阻塞调用等待 ISR 完成传输并发布信号,但在 GPIO ISR 退出之前,ISR 永远不会获得 CPU 时间。SDK 的驱动程序确实在 LPSPI 中断中完成传输,然后才发布信号量以释放屏蔽调用,因此同等优先级 ISR 将以这种方式使传输陷入僵局。 非阻塞 API 的行为相同:如果从具有相同优先级的 GPIO ISR 调用,LPSPI ISR 无法抢占它的优先级,因此 byte_remaining 永远不会改变,因为驱动程序状态机永远不会被 LPSPI IRQ 服务。只有将 LPSPI 提高到更高优先级(数值较低)后,LPSPI 中断才会立即触发,完成传输,并允许阻塞和非阻塞 API 按预期工作。尝试 /* 在 Cortex-M 上,数字越小优先级越高 */ INT_SYS_SetPriority(SysTick_IRQn, 0); // 如果依赖于 tick 超时 INT_SYS_SetPriority(LPSPI1_IRQn, 1); // 必须高于 GPIO INT_SYS_SetPriority(PORTC_IRQn, 2); // 您按钮的 PORTx IRQ   注意:无论优先级如何修正,建议还是不要在 ISR 中使用阻塞的 SPI API,同样也不要在 ISR 中等待非阻塞传输完成。S32K LPSPI 驱动程序在其中断处理程序中进行传输,长时间的 ISR 会阻止其他中断运行。   BR, Petr Re: Doing I/O from an interrupt handler 您好, S32K1 SDK 无法阻止 ISR 的 I/O。LPSPI_DRV_MasterTransferBlocking() 等待 OSIF semaphore;在 ISR 上下文中,没有地方可以阻塞,也没有 tick/time base 可以前进,因此会挂起。使用非阻塞 API(LPSPI_DRV_MasterTransfer),在 LPSPI ISR/回调中完成传输,然后向任务/主循环发出信号。此外,SysTick 会在定时器结束时触发,但其处理程序只有在未被屏蔽且具有足够的 NVIC 优先级时才会运行--因此,如果设置了 PRIMASK 或处于更高优先级的 ISR 中,它将被推迟。 烹饪手册项目特意采用轻量级设计,直接展示外围设备的使用,而不使用更高级别的驱动程序抽象;这些项目旨在作为学习的起点,而非生产使用。如果您需要恩智浦驱动程序风格的示例,请参考 SDK 或 RTD 驱动程序/示例项目,而不是烹饪手册。   BR, Petr Re: Doing I/O from an interrupt handler 您好, 即使它现在 "工作 "了,你仍然不应该在 ISR 内进行 SPI 传输。 如果你以后改变了优先级,或添加了另一个外设,你可以很容易地重新创建刚刚诊断出的死锁状态。 最安全的设计是始终缩短 ISR,将真正的工作推迟到主循环。 仅将 ISR 用作触发信号;在 main () 中同步执行 SPI 传输,或者在 ISR 中启动但由 LPSPI ISR 完成的非阻塞传输,主等待完成标志。 BR, Petr
View full article