S32G-PROCEVB3-S board Hello,  In S32G-PROCEVB3-S board – REV A Schematics.pdf p. 17 U140 and U143 Multiplexer both have SD_MUX_TXN signals to A0_P. Q1: SD_MUX_TXN is a signal input to Multiplexer, is that correct? Q2: what is SD_MUX_TXN? where is it from S32G? I cannot find it in other pages. Thanks Re: S32G-PROCEVB3-S board "connecting the output of U140 to the input of U143" Thanks Daniel, it is clear. Re: S32G-PROCEVB3-S board Hi, As told before, the signal is a point-to-point connection between U140 and U143. There is no purpose other than connecting the output of U140 to the input of U143. As of who provides it, the specific signal of SD_MUX_TXN, it is being provided by the output of the multiplexer/demultiplexer U140. Depending on the setting of the multiplexer, can be either being routed to B0 or C0 of U140. More information on regards of U140, we can recommend opening a ticket under the NXP online services, since this community is related to S32G rather than multiplexer/demultiplexer technology. We do apologize. Please, let us know. Re: S32G-PROCEVB3-S board Hello Daniel, What is the purpose of this signal? Where/who provide it? Thanks Re: S32G-PROCEVB3-S board Hi, For the information provided under the schematic, since the signals are the transmission lines (TX), and the signals shown at the right side of the image go to the physical connector, we can say that the signals are seen as an output from U140. Please, let us know. Re: S32G-PROCEVB3-S board Hello Daniel, Thanks for the update. What is the purpose of this signal? From U140 perspective, is it a input signal? Thanks Re: S32G-PROCEVB3-S board Hi, We might be misunderstanding the overall inquiry, if so we apologize. The signal you are referring to is a point-to-point connection between U140 and U143, as shown under the schematic: These are not directly connected to the S32G. Please, let us know.

Nitrogen8M fails to detect Wi-Fi module Hi, I am working on a project using the Nitrogen8M Plus SMARC and the M2-JODY-W3 Wi-Fi 6 module. I am experiencing difficulty in getting the Nitrogen8M board to recognize the Wi-Fi module. I have successfully loaded the NXP drivers (moal and mlan, available at http://github.com/nxp-imx/mwifiex.git) for the module based on the NXP 88W9098 chipset. Additionally, I have used the 88W9098 firmware from https://github.com/NXP/imx-firmware.   After running the command "modprobe moal mod_para=nxp/wifi_mod_para.conf," the drivers were successfully installed into the kernel. However, the mlan0 interface remains down. The configuration file wifi_mod_para.conf is set with the following parameters:   PCIE9098_0 = { cfg80211_wext=0xf wfd_name=p2p max_vir_bss=1 cal_data_cfg=none drv_mode=7 ps_mode=2 auto_ds=2 mac_addr=00:50:43:20:12:34 fw_name=nxp/pcieuart9098_combo_v0.bin }   PCIE9098_1 = { cfg80211_wext=0xf wfd_name=p2p max_vir_bss=1 cal_data_cfg=none drv_mode=7 ps_mode=2 auto_ds=2 mac_addr=00:50:43:20:52:56 fw_name=nxp/pcieuart9098_combo_v0.bin }   I would appreciate any assistance you can provide in resolving this issue.   Best regards Re: Nitrogen8M fails to detect Wi-Fi module Hi, @SimaoLeite  Thanks for your reply and congratulations for your great job! Such a good news to hear. Have a nice day. Best regards, Christine. Re: Nitrogen8M fails to detect Wi-Fi module Hi, @Christine_Li I have solved my issue by updating my Linux Kernel to version 6.1.22. It appears that Linux Kernel version 5.15.71 does not support the new generation of PCIe. Thank you for all your replies. Best regards, Simão Leite Re: Nitrogen8M fails to detect Wi-Fi module Hi, @Christine_Li The default device tree source file I am using is imx8mp-nitrogen_smarc.dts. I have also tested another DTS file, particularly imx8mp-nitrogen8mp.dts, and encountered the same issue. While I observed some differences between these two files, none seemed significant. Attached are all the relevant DTS files and the dmesg logs from the imx8mp-nitrogen8mp.dts file (The logs previously provided are the result of using the imx8mp-nitrogen_smarc.dts file). Concerning my host platform, I am also confused by the "imx6q" output. However, I can ensure that I am working with the Nitrogen8M board. The Linux Kernel repository I am using is available at "https://github.com/boundarydevices/linux/tree/boundary-imx_5.15.y" Thanks, Simão Re: Nitrogen8M fails to detect Wi-Fi module Hi, @SimaoLeite  From your given logs, I saw some PCIE error logs. It seems that your PCIE driver has problem, then Wi-Fi driver can not be loaded successfully. ====== [ 2.564136] pcie phy pipe clk is not ready [ 2.568247] phy phy-32f00000.pcie-phy.4: phy init failed --> -110 [ 2.568255] imx6q-pcie 33800000.pcie: Waiting for PHY PLL ready timeout! [ 2.588773] imx6q-pcie 33800000.pcie: PCIe PLL lock timeout [ 2.602304] Console: switching to colour frame buffer device 100x37 [ 2.629670] imx6q-pcie 33800000.pcie: iATU unroll: enabled [ 2.631690] imx-drm display-subsystem: [drm] fb0: imx-drmdrmfb frame buffer device [ 2.637264] imx6q-pcie 33800000.pcie: Detected iATU regions: 4 outbound, 4 inbound [ 2.664168] imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges: [ 2.668723] pps pps0: new PPS source ptp0 [ 2.671429] imx6q-pcie 33800000.pcie: No bus range found for /soc@0/pcie@33800000, using [bus 00-ff] [ 2.684784] imx6q-pcie 33800000.pcie: IO 0x001ff80000..0x001ff8ffff -> 0x0000000000 [ 2.692998] imx6q-pcie 33800000.pcie: MEM 0x0018000000..0x001fefffff -> 0x0018000000 [ 2.701303] imx6q-pcie 33800000.pcie: iATU unroll: enabled [ 2.706815] imx6q-pcie 33800000.pcie: Detected iATU regions: 4 outbound, 4 inbound ========== Please check your dts, especially PCIE part. Also, I am confused with this print: "imx6q", it is not matched with your host platform: "Nitrogen8M" Can you please help to double confirm your host platform? And also please share to me your device tree file, so that I can check it further. Best regards, Christine. Re: Nitrogen8M fails to detect Wi-Fi module Hi, @Christine_Li First of all, thanks for the reply. I am using the Linux Kernel 5.15.71, and my full dmesg log is shown below root@nitrogen8mp:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.15.71-2.2.0+yocto+gaaf028b285b7+p0 (oe-user@oe-host) (aarch64-agl-linux-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Tue Feb 27 02:13:20 UTC 2024 [ 0.000000] Machine model: Boundary i.MX8MPlus nitrogen8mp smarc board [ 0.000000] efi: UEFI not found. [ 0.000000] Reserved memory: created CMA memory pool at 0x00000000e0000000, size 512 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x0000000094300000, size 1 MiB [ 0.000000] OF: reserved mem: initialized node vdev0buffer@94300000, compatible id shared-dma-pool [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000040000000-0x00000000ffffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal [mem 0x0000000100000000-0x000000023fffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000040000000-0x0000000055ffffff] [ 0.000000] node 0: [mem 0x0000000058000000-0x00000000923fffff] [ 0.000000] node 0: [mem 0x0000000092400000-0x00000000a43fffff] [ 0.000000] node 0: [mem 0x00000000a4400000-0x000000023fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000023fffffff] [ 0.000000] On node 0, zone DMA: 8192 pages in unavailable ranges [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS migration not required [ 0.000000] psci: SMC Calling Convention v1.2 [ 0.000000] percpu: Embedded 28 pages/cpu s74200 r8192 d32296 u114688 [ 0.000000] pcpu-alloc: s74200 r8192 d32296 u114688 alloc=28*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: ARM erratum 845719 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 2056192 [ 0.000000] Kernel command line: console=ttymxc1,115200 vmalloc=400M consoleblank=0 rootwait fixrtc cpu=8MP[8] board=nitrogen_smarc uboot_release=2022.04-63881-g325116286aa root=/dev/mmcblk0p2 snd.slots=,snd-soc-imx-hdmi [ 0.000000] Unknown kernel command line parameters "fixrtc vmalloc=400M cpu=8MP[8] board=nitrogen_smarc uboot_release=2022.04-63881-g325116286aa", will be passed to user space. [ 0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [ 0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] software IO TLB: mapped [mem 0x00000000dc000000-0x00000000e0000000] (64MB) [ 0.000000] Memory: 7279232K/8355840K available (17664K kernel code, 2470K rwdata, 6004K rodata, 4224K init, 433K bss, 552320K reserved, 524288K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] trace event string verifier disabled [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU event tracing is enabled. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: 160 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] GICv3: Distributor has no Range Selector support [ 0.000000] Root IRQ handler: gic_handle_irq [ 0.000000] GICv3: 16 PPIs implemented [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000 [ 0.000000] ITS: No ITS available, not enabling LPIs [ 0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns [ 0.000001] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns [ 0.000589] Console: colour dummy device 80x25 [ 0.000632] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000) [ 0.000645] pid_max: default: 32768 minimum: 301 [ 0.000728] LSM: Security Framework initializing [ 0.000753] Yama: becoming mindful. [ 0.000816] AppArmor: AppArmor initialized [ 0.000906] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.000934] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.002359] rcu: Hierarchical SRCU implementation. [ 0.004624] EFI services will not be available. [ 0.004934] smp: Bringing up secondary CPUs ... [ 0.005458] Detected VIPT I-cache on CPU1 [ 0.005485] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000 [ 0.005522] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.006028] Detected VIPT I-cache on CPU2 [ 0.006048] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000 [ 0.006066] CPU2: Booted secondary processor 0x0000000002 [0x410fd034] [ 0.006565] Detected VIPT I-cache on CPU3 [ 0.006585] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000 [ 0.006603] CPU3: Booted secondary processor 0x0000000003 [0x410fd034] [ 0.006670] smp: Brought up 1 node, 4 CPUs [ 0.006697] SMP: Total of 4 processors activated. [ 0.006703] CPU features: detected: 32-bit EL0 Support [ 0.006707] CPU features: detected: 32-bit EL1 Support [ 0.006717] CPU features: detected: CRC32 instructions [ 0.014192] CPU: All CPU(s) started at EL2 [ 0.014233] alternatives: patching kernel code [ 0.015945] devtmpfs: initialized [ 0.029223] Registered cp15_barrier emulation handler [ 0.029248] Registered setend emulation handler [ 0.029258] KASLR disabled due to lack of seed [ 0.029390] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.029407] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.043291] pinctrl core: initialized pinctrl subsystem [ 0.043801] DMI not present or invalid. [ 0.044376] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.045719] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations [ 0.045983] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [ 0.046323] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [ 0.046369] audit: initializing netlink subsys (disabled) [ 0.046486] audit: type=2000 audit(0.044:1): state=initialized audit_enabled=0 res=1 [ 0.046898] thermal_sys: Registered thermal governor 'step_wise' [ 0.047186] cpuidle: using governor menu [ 0.047402] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.047488] ASID allocator initialised with 65536 entries [ 0.048793] imx mu driver is registered. [ 0.048812] imx rpmsg driver is registered. [ 0.061977] imx8mp-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver [ 0.081372] platform 32fd8000.hdmi: Fixing up cyclic dependency with 32fc6000.lcd-controller [ 0.098882] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 0.098900] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages [ 0.098907] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 0.098914] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages [ 0.100858] cryptd: max_cpu_qlen set to 1000 [ 0.104879] imx_dev_clk_hw_pll14xx: audio_pll2 en:1, sel:2, mf:30000, mr:2 [ 0.104907] imx_dev_clk_hw_pll14xx: video_pll1 en:1, sel:2, mf:30000, mr:5 [ 0.116449] ACPI: Interpreter disabled. [ 0.120011] debugfs: Directory 'vref-3v3' with parent 'regulator' already present! [ 0.120671] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 35, base_baud = 5000000) is a IMX [ 0.120787] serial serial0: tty port ttymxc0 registered [ 0.121268] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 36, base_baud = 5000000) is a IMX [ 0.121738] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 37, base_baud = 1500000) is a IMX [ 0.865923] printk: console [ttymxc1] enabled [ 0.870787] 30a60000.serial: ttymxc3 at MMIO 0x30a60000 (irq = 45, base_baud = 5000000) is a IMX [ 0.880470] iommu: Default domain type: Translated [ 0.885362] iommu: DMA domain TLB invalidation policy: strict mode [ 0.891647] max77958:max77958_i2c_init [ 0.895633] SCSI subsystem initialized [ 0.899562] libata version 3.00 loaded. [ 0.899759] usbcore: registered new interface driver usbfs [ 0.905288] usbcore: registered new interface driver hub [ 0.910634] usbcore: registered new device driver usb [ 0.916493] imx-i2c 30a20000.i2c: stop-delay=0, inter-byte-delay=0 [ 0.923176] i2c i2c-0: IMX I2C adapter registered [ 0.928238] imx-i2c 30a30000.i2c: stop-delay=0, inter-byte-delay=0 [ 0.935079] i2c i2c-1: IMX I2C adapter registered [ 0.940497] imx-i2c 30a40000.i2c: stop-delay=0, inter-byte-delay=0 [ 0.947137] i2c i2c-2: IMX I2C adapter registered [ 0.952142] imx-i2c 30a50000.i2c: stop-delay=0, inter-byte-delay=0 [ 0.958508] i2c i2c-3: IMX I2C adapter registered [ 0.963379] imx-i2c 30ae0000.i2c: stop-delay=0, inter-byte-delay=0 [ 1.031272] i2c i2c-5: IMX I2C adapter registered [ 1.036754] mc: Linux media interface: v0.10 [ 1.041061] videodev: Linux video capture interface: v2.00 [ 1.046711] pps_core: LinuxPPS API ver. 1 registered [ 1.051684] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 1.060853] PTP clock support registered [ 1.065570] Advanced Linux Sound Architecture Driver Initialized. [ 1.072266] Bluetooth: Core ver 2.22 [ 1.075874] NET: Registered PF_BLUETOOTH protocol family [ 1.081194] Bluetooth: HCI device and connection manager initialized [ 1.087556] Bluetooth: HCI socket layer initialized [ 1.092442] Bluetooth: L2CAP socket layer initialized [ 1.097509] Bluetooth: SCO socket layer initialized [ 1.102403] NetLabel: Initializing [ 1.105803] NetLabel: domain hash size = 128 [ 1.110165] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 1.115891] NetLabel: unlabeled traffic allowed by default [ 1.122277] clocksource: Switched to clocksource arch_sys_counter [ 1.157189] VFS: Disk quotas dquot_6.6.0 [ 1.161190] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 1.168497] AppArmor: AppArmor Filesystem Enabled [ 1.173269] pnp: PnP ACPI: disabled [ 1.183027] NET: Registered PF_INET protocol family [ 1.188160] IP idents hash table entries: 131072 (order: 8, 1048576 bytes, linear) [ 1.198534] tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear) [ 1.207142] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 1.214900] TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear) [ 1.223244] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear) [ 1.231541] TCP: Hash tables configured (established 65536 bind 65536) [ 1.238228] UDP hash table entries: 4096 (order: 5, 131072 bytes, linear) [ 1.245170] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear) [ 1.252673] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 1.258739] RPC: Registered named UNIX socket transport module. [ 1.264691] RPC: Registered udp transport module. [ 1.269404] RPC: Registered tcp transport module. [ 1.274115] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.280568] PCI: CLS 0 bytes, default 64 [ 1.285143] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available [ 1.294172] kvm [1]: IPA Size Limit: 40 bits [ 1.299841] kvm [1]: GICv3: no GICV resource entry [ 1.304645] kvm [1]: disabling GICv2 emulation [ 1.309109] kvm [1]: GIC system register CPU interface enabled [ 1.315039] kvm [1]: vgic interrupt IRQ9 [ 1.319111] kvm [1]: Hyp mode initialized successfully [ 1.327889] Initialise system trusted keyrings [ 1.332405] Key type blacklist registered [ 1.336551] workingset: timestamp_bits=46 max_order=21 bucket_order=0 [ 1.348632] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 1.355396] NFS: Registering the id_resolver key type [ 1.360500] Key type id_resolver registered [ 1.364695] Key type id_legacy registered [ 1.368773] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 1.375481] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... [ 1.382894] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 1.389343] 9p: Installing v9fs 9p2000 file system support [ 1.395151] integrity: Platform Keyring initialized [ 1.436171] Key type asymmetric registered [ 1.440282] Asymmetric key parser 'x509' registered [ 1.445216] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243) [ 1.452724] io scheduler mq-deadline registered [ 1.457268] io scheduler kyber registered [ 1.474178] imx6q-pcie 33800000.pcie: supply epdev_on not found, using dummy regulator [ 1.482288] imx6_pcie_probe: reset gp 117 [ 1.486364] imx6q-pcie 33800000.pcie: pcie_ext_src clk src missing or invalid [ 1.488156] imx-sdma 30bd0000.dma-controller: firmware found. [ 1.493552] imx6q-pcie 33800000.pcie: Failed to get PCIEPHY perst control [ 1.499436] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5 [ 1.515489] mxs-dma 33000000.dma-apbh: initialized [ 1.521635] SoC: i.MX8MP revision 1.1 [ 1.525331] imx-sdma 30e10000.dma-controller: firmware found. [ 1.526928] Bus freq driver module loaded [ 1.545196] nxp-pca9450 0-0025: pca9450bc probed. [ 1.553867] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 1.573451] brd: module loaded [ 1.581095] loop: module loaded [ 1.586456] imx ahci driver is registered. [ 1.591357] slram: not enough parameters. [ 1.599305] tun: Universal TUN/TAP device driver, 1.6 [ 1.604540] CAN device driver interface [ 1.610903] e1000e: Intel(R) PRO/1000 Network Driver [ 1.615880] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 1.621841] igb: Intel(R) Gigabit Ethernet Network Driver [ 1.627248] igb: Copyright (c) 2007-2014 Intel Corporation. [ 1.632858] igbvf: Intel(R) Gigabit Virtual Function Network Driver [ 1.639134] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 1.645091] sky2: driver version 1.30 [ 1.651210] platform 38100000.usb: Fixing up cyclic dependency with connector [ 1.660551] dwc3 38200000.usb: vbus regulator failed -19 [ 1.668507] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.675089] ehci-pci: EHCI PCI platform driver [ 1.679573] ehci-platform: EHCI generic platform driver [ 1.685063] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.691258] ohci-pci: OHCI PCI platform driver [ 1.695739] ohci-platform: OHCI generic platform driver [ 1.701923] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ 1.707435] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1 [ 1.715447] xhci-hcd xhci-hcd.0.auto: hcc params 0x0220fe6d hci version 0x110 quirks 0x0000002001010010 [ 1.724889] xhci-hcd xhci-hcd.0.auto: irq 247, io mem 0x38200000 [ 1.731026] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ 1.736526] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2 [ 1.744200] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed [ 1.751245] hub 1-0:1.0: USB hub found [ 1.755030] hub 1-0:1.0: 1 port detected [ 1.759270] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 1.767774] hub 2-0:1.0: USB hub found [ 1.771554] hub 2-0:1.0: 1 port detected [ 1.775822] usbcore: registered new interface driver usb-storage [ 1.781877] usbcore: registered new interface driver usb_ehset_test [ 1.790437] init [ 1.790973] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0 [ 1.806127] i2c_dev: i2c /dev entries driver [ 1.813353] i2c i2c-1: Added multiplexed i2c bus 6 [ 1.818509] i2c 7-0060: Fixing up cyclic dependency with 38100000.usb [ 1.825010] i2c 7-0060: Fixing up cyclic dependency with connector [ 1.832816] i2c i2c-1: Added multiplexed i2c bus 7 [ 1.838163] i2c i2c-1: Added multiplexed i2c bus 8 [ 1.843153] i2c i2c-1: Added multiplexed i2c bus 9 [ 1.847971] pca954x 1-0073: registered 4 multiplexed busses for I2C switch pca9546 [ 1.857012] i2c i2c-2: Added multiplexed i2c bus 10 [ 1.862092] i2c i2c-2: Added multiplexed i2c bus 11 [ 1.867192] i2c i2c-2: Added multiplexed i2c bus 12 [ 1.872255] i2c i2c-2: Added multiplexed i2c bus 13 [ 1.877155] pca954x 2-0073: registered 4 multiplexed busses for I2C switch pca9546 [ 1.886241] i2c 14-0010: Fixing up cyclic dependency with 32e40000.csi [ 1.892998] i2c i2c-5: Added multiplexed i2c bus 14 [ 1.898171] i2c 15-0010: Fixing up cyclic dependency with 32e50000.csi [ 1.904932] i2c i2c-5: Added multiplexed i2c bus 15 [ 1.910005] i2c i2c-5: Added multiplexed i2c bus 16 [ 1.915073] i2c i2c-5: Added multiplexed i2c bus 17 [ 1.919971] pca954x 5-0070: registered 4 multiplexed busses for I2C switch pca9546 [ 1.942520] rtc-rv3028 6-0052: registered as rtc0 [ 1.949106] rtc-rv3028 6-0052: setting system clock to 2024-05-20T08:47:55 UTC (1716194875) [ 1.959740] check_alarm_past: alarm in the past [ 1.964416] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc1 [ 1.975161] sdhci: Secure Digital Host Controller Interface driver [ 1.981368] sdhci: Copyright(c) Pierre Ossman [ 1.985845] Synopsys Designware Multimedia Card Interface Driver [ 1.992091] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.999312] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO [ 2.005050] ledtrig-cpu: registered to indicate activity on CPUs [ 2.011803] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping .... [ 2.018619] usb 1-1: new high-speed USB device number 2 using xhci-hcd [ 2.019481] caam 30900000.crypto: device ID = 0x0a16040100000100 (Era 9) [ 2.031882] caam 30900000.crypto: job rings = 1, qi = 0 [ 2.036255] mmc0: SDHCI controller on 30b40000.mmc [30b40000.mmc] using ADMA [ 2.038237] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA [ 2.048221] caam algorithms registered in /proc/crypto [ 2.057474] caam 30900000.crypto: caam pkc algorithms registered in /proc/crypto [ 2.065013] caam 30900000.crypto: rng crypto API alg registered prng-caam [ 2.071831] caam 30900000.crypto: registering rng-caam [ 2.077470] random: crng init done [ 2.078653] Device caam-keygen registered [ 2.085338] caam-snvs 30370000.caam-snvs: violation handlers armed - non-secure state [ 2.093525] hid: raw HID events driver (C) Jiri Kosina [ 2.099158] usbcore: registered new interface driver usbhid [ 2.104758] usbhid: USB HID core driver [ 2.109464] mxc-mipi-csi2-sam 32e40000.csi: supply mipi-phy not found, using dummy regulator [ 2.118351] : mipi_csis_imx8mp_phy_reset, No remote pad found! [ 2.119708] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA [ 2.124291] mipi_csis_subdev_init: mxc-mipi-csi2.0 [ 2.136123] mxc-mipi-csi2-sam 32e40000.csi: lanes: 2, hs_settle: 13, clk_settle: 2, wclk: 1, freq: 500000000 [ 2.146013] mipi_csis_probe: success ffff0000c0a7b810 [ 2.151457] mxc-mipi-csi2-sam 32e50000.csi: supply mipi-phy not found, using dummy regulator [ 2.160373] : mipi_csis_imx8mp_phy_reset, No remote pad found! [ 2.166295] mipi_csis_subdev_init: mxc-mipi-csi2.1 [ 2.171108] mxc-mipi-csi2-sam 32e50000.csi: lanes: 2, hs_settle: 13, clk_settle: 2, wclk: 1, freq: 266000000 [ 2.180980] mipi_csis_probe: success ffff0000c0a7cc10 [ 2.187595] deferring isp device registration [ 2.193071] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 2.195408] optee: probing for conduit method. [ 2.200619] mmcblk0: mmc0:0001 TB2916 14.6 GiB [ 2.203939] optee: revision 3.17 (98499642) [ 2.209969] mmcblk0: p1 p2 [ 2.209982] optee: dynamic shared memory is enabled [ 2.215361] mmcblk0boot0: mmc0:0001 TB2916 4.00 MiB [ 2.217327] optee: initialized driver [ 2.223491] mmcblk0boot1: mmc0:0001 TB2916 4.00 MiB [ 2.228816] hantrodec 0 : module inserted. Major = 238 [ 2.232674] mmcblk0rpmb: mmc0:0001 TB2916 4.00 MiB, chardev (240:0) [ 2.235771] hub 1-1:1.0: USB hub found [ 2.236065] hantrodec 1 : module inserted. Major = 238 [ 2.237333] hantroenc: HW at base <0000000038320000> with ID <0x80006200> [ 2.237457] hx280enc: module inserted. Major <237> [ 2.245177] wm8962 8-001a: customer id 0 revision F [ 2.250771] hub 1-1:1.0: 4 ports detected [ 2.292637] imx-hdmi sound-hdmi: snd_soc_register_card failed (-517) [ 2.299556] NET: Registered PF_LLC protocol family [ 2.304833] NET: Registered PF_INET6 protocol family [ 2.311900] Segment Routing with IPv6 [ 2.315605] In-situ OAM (IOAM) with IPv6 [ 2.319584] NET: Registered PF_PACKET protocol family [ 2.324655] can: controller area network core [ 2.329069] NET: Registered PF_CAN protocol family [ 2.333899] can: raw protocol [ 2.336934] can: broadcast manager protocol [ 2.341162] can: netlink gateway - max_hops=1 [ 2.341451] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd [ 2.346290] Bluetooth: RFCOMM TTY layer initialized [ 2.357004] Bluetooth: RFCOMM socket layer initialized [ 2.362191] Bluetooth: RFCOMM ver 1.11 [ 2.365972] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 2.371308] Bluetooth: BNEP filters: protocol multicast [ 2.376570] Bluetooth: BNEP socket layer initialized [ 2.381562] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 2.387557] Bluetooth: HIDP socket layer initialized [ 2.393067] 9pnet: Installing 9P2000 support [ 2.397408] Key type dns_resolver registered [ 2.402453] Loading compiled-in X.509 certificates [ 2.411045] Key type encrypted registered [ 2.415101] AppArmor: AppArmor sha1 policy hashing enabled [ 2.438983] hub 2-1:1.0: USB hub found [ 2.442834] hub 2-1:1.0: 4 ports detected [ 2.445759] imx6q-pcie 33800000.pcie: supply epdev_on not found, using dummy regulator [ 2.446377] dwhdmi-imx 32fd8000.hdmi: Detected HDMI TX controller v2.13a with HDCP (samsung_dw_hdmi_phy2) [ 2.447342] dwhdmi-imx 32fd8000.hdmi: registered DesignWare HDMI I2C bus driver [ 2.454965] imx6_pcie_probe: reset gp 117 [ 2.465832] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops 0xffff80000926d968) [ 2.471790] imx6q-pcie 33800000.pcie: pcie_ext_src clk src missing or invalid [ 2.475871] imx-drm display-subsystem: bound 32fd8000.hdmi (ops 0xffff80000925ad78) [ 2.484019] imx6q-pcie 33800000.pcie: EXT REF_CLK is used!. [ 2.491298] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 0 [ 2.499236] imx6q-pcie 33800000.pcie: PCIe PHY PLL clock is locked. [ 2.522909] mmc2: new ultra high speed SDR104 SDIO card at address 0001 [ 2.564136] pcie phy pipe clk is not ready [ 2.568247] phy phy-32f00000.pcie-phy.4: phy init failed --> -110 [ 2.568255] imx6q-pcie 33800000.pcie: Waiting for PHY PLL ready timeout! [ 2.588773] imx6q-pcie 33800000.pcie: PCIe PLL lock timeout [ 2.602304] Console: switching to colour frame buffer device 100x37 [ 2.629670] imx6q-pcie 33800000.pcie: iATU unroll: enabled [ 2.631690] imx-drm display-subsystem: [drm] fb0: imx-drmdrmfb frame buffer device [ 2.637264] imx6q-pcie 33800000.pcie: Detected iATU regions: 4 outbound, 4 inbound [ 2.664168] imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges: [ 2.668723] pps pps0: new PPS source ptp0 [ 2.671429] imx6q-pcie 33800000.pcie: No bus range found for /soc@0/pcie@33800000, using [bus 00-ff] [ 2.684784] imx6q-pcie 33800000.pcie: IO 0x001ff80000..0x001ff8ffff -> 0x0000000000 [ 2.692998] imx6q-pcie 33800000.pcie: MEM 0x0018000000..0x001fefffff -> 0x0018000000 [ 2.701303] imx6q-pcie 33800000.pcie: iATU unroll: enabled [ 2.706815] imx6q-pcie 33800000.pcie: Detected iATU regions: 4 outbound, 4 inbound [ 2.710697] fec 30be0000.ethernet eth0: registered PHC device 0 [ 2.721079] imx-dwmac 30bf0000.ethernet: IRQ eth_lpi not found [ 2.727493] imx-dwmac 30bf0000.ethernet: User ID: 0x10, Synopsys ID: 0x51 [ 2.734311] imx-dwmac 30bf0000.ethernet: DWMAC4/5 [ 2.739111] imx-dwmac 30bf0000.ethernet: DMA HW capability register supported [ 2.746255] imx-dwmac 30bf0000.ethernet: RX Checksum Offload Engine supported [ 2.753395] imx-dwmac 30bf0000.ethernet: TX Checksum insertion supported [ 2.760102] imx-dwmac 30bf0000.ethernet: Wake-Up On Lan supported [ 2.766246] imx-dwmac 30bf0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 2.773919] imx-dwmac 30bf0000.ethernet: Enabled L3L4 Flow TC (entries=8) [ 2.780714] imx-dwmac 30bf0000.ethernet: Enabled RFS Flow TC (entries=8) [ 2.787431] imx-dwmac 30bf0000.ethernet: Enabling HW TC (entries=256, max_off=256) [ 2.795007] imx-dwmac 30bf0000.ethernet: Using 34 bits DMA width [ 2.813131] hd3ss3220 7-0060: probed revision=0x0 [ 2.818382] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 5 mkt segment 0 supported-hw 0x20 0x1 [ 2.828737] deferring isp device registration [ 2.834193] input: WM8962 Beep Generator as /devices/platform/soc@0/30800000.bus/30a30000.i2c/i2c-1/i2c-8/8-001a/input/input1 [ 2.890014] input: audio-hdmi HDMI Jack as /devices/platform/sound-hdmi/sound/card1/input2 [ 2.899789] deferring isp device registration [ 2.904985] deferring isp device registration [ 2.919052] input: gpio-keys-batt as /devices/platform/gpio-keys-batt/input/input3 [ 2.929838] input: gpio-keys as /devices/platform/gpio-keys/input/input4 [ 2.929876] deferring isp device registration [ 2.941477] deferring isp device registration [ 2.967396] input: gpio-keys-can as /devices/platform/gpio-keys-can/input/input5 [ 2.977245] deferring isp device registration [ 2.998910] ALSA device list: [ 3.001897] #0: wm8962-audio [ 3.004975] #1: audio-hdmi [ 3.714073] imx6q-pcie 33800000.pcie: Phy link never came up [ 3.719833] imx6q-pcie: probe of 33800000.pcie failed with error -110 [ 3.749845] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [ 3.759665] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [ 3.766798] devtmpfs: mounted [ 3.770547] Freeing unused kernel memory: 4224K [ 3.782625] Run /sbin/init as init process [ 3.786736] with arguments: [ 3.786740] /sbin/init [ 3.786743] fixrtc [ 3.786746] with environment: [ 3.786748] HOME=/ [ 3.786751] TERM=linux [ 3.786754] vmalloc=400M [ 3.786756] cpu=8MP[8] [ 3.786759] board=nitrogen_smarc [ 3.786761] uboot_release=2022.04-63881-g325116286aa [ 3.925864] systemd[1]: systemd 250.5+ running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA -SMACK +SECCOMP -GCRYPT -GNUTLS -OPENSSL +ACL +BLKID -CURL -ELFUTILS -FIDO2 -IDN2 -IDN +IPTC +KMOD -LIBCRYPTSETUP +LIBFDISK -PCRE2 -PWQUALITY -P11KIT -QRENCODE -BZIP2 -LZ4 -XZ -ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=hybrid) [ 3.957720] systemd[1]: Detected architecture arm64. [ 4.041150] systemd[1]: Hostname set to . [ 4.050406] systemd[1]: Initializing machine ID from random generator. [ 4.057418] systemd[1]: Installed transient /etc/machine-id file. [ 4.307371] systemd[1]: Queued start job for default target Multi-User System. [ 4.346939] systemd[1]: Created slice Slice /system/getty. [ 4.360661] systemd[1]: Created slice Slice /system/modprobe. [ 4.384346] systemd[1]: Created slice Slice /system/serial-getty. [ 4.408230] systemd[1]: Created slice User and Session Slice. [ 4.430768] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ 4.454689] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 4.478685] systemd[1]: Reached target Host and Network Name Lookups. [ 4.502774] systemd[1]: Reached target Path Units. [ 4.522396] systemd[1]: Reached target Remote File Systems. [ 4.547046] systemd[1]: Reached target Slice Units. [ 4.566725] systemd[1]: Reached target Swaps. [ 4.603618] systemd[1]: Listening on Process Core Dump Socket. [ 4.626697] systemd[1]: Listening on initctl Compatibility Named Pipe. [ 4.651229] systemd[1]: Listening on Journal Audit Socket. [ 4.675016] systemd[1]: Listening on Journal Socket (/dev/log). [ 4.699008] systemd[1]: Listening on Journal Socket. [ 4.723237] systemd[1]: Listening on Network Service Netlink Socket. [ 4.763771] systemd[1]: Listening on udev Control Socket. [ 4.787260] systemd[1]: Listening on udev Kernel Socket. [ 4.811311] systemd[1]: Listening on User Database Manager Socket. [ 4.838633] systemd[1]: Mounting Huge Pages File System... [ 4.862215] systemd[1]: Mounting POSIX Message Queue File System... [ 4.885706] systemd[1]: Mounting Kernel Debug File System... [ 4.910376] systemd[1]: Mounting Kernel Trace File System... [ 4.949532] systemd[1]: Mounting Temporary Directory /tmp... [ 4.969956] systemd[1]: Starting Create List of Static Device Nodes... [ 4.998679] systemd[1]: Starting Load Kernel Module configfs... [ 5.022049] systemd[1]: Starting Load Kernel Module drm... [ 5.046628] systemd[1]: Starting Load Kernel Module fuse... [ 5.060733] fuse: init (API version 7.34) [ 5.069228] systemd[1]: Starting SELinux autorelabel service loading... [ 5.093365] systemd[1]: Starting SELinux init for /dev service loading... [ 5.117985] systemd[1]: Starting File System Check on Root Device... [ 5.138975] systemd[1]: systemd-journald.service: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling. [ 5.151925] systemd[1]: (This warning is only shown for the first unit using IP firewalling.) [ 5.164135] systemd[1]: Starting Journal Service... [ 5.173957] systemd[1]: Starting Load Kernel Modules... [ 5.182570] systemd[1]: Starting Generate network units from Kernel command line... [ 5.195804] galcore: loading out-of-tree module taints kernel. [ 5.208525] deferring isp device registration [ 5.209918] Galcore version 6.4.3.p4.398061 [ 5.233254] systemd[1]: Starting Coldplug All udev Devices... [ 5.260955] systemd[1]: Mounted Huge Pages File System. [ 5.273059] systemd[1]: Mounted POSIX Message Queue File System. [ 5.289459] [drm] Initialized vivante 1.0.0 20170808 for 40000000.mix_gpu_ml on minor 1 [ 5.298186] deferring isp device registration [ 5.306947] systemd[1]: Started Journal Service. [ 5.327047] audit: type=1130 audit(1716194878.876:2): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.410803] audit: type=1130 audit(1716194878.960:3): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=kmod-static-nodes comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.447294] audit: type=1130 audit(1716194878.996:4): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=modprobe@configfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.467589] audit: type=1131 audit(1716194878.996:5): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=modprobe@configfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.506790] audit: type=1130 audit(1716194879.056:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.526651] audit: type=1131 audit(1716194879.056:7): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.563394] audit: type=1130 audit(1716194879.112:8): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=modprobe@fuse comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.583344] audit: type=1131 audit(1716194879.112:9): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=modprobe@fuse comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.622812] audit: type=1130 audit(1716194879.172:10): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=selinux-autorelabel comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.643364] audit: type=1131 audit(1716194879.172:11): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=selinux-autorelabel comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.683411] audit: type=1130 audit(1716194879.232:12): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=selinux-labeldev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.703717] audit: type=1131 audit(1716194879.232:13): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=selinux-labeldev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.852994] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null). Quota mode: none. [ 5.961069] systemd-journald[283]: Received client request to flush runtime journal. [ 6.722763] Bluetooth: HCI UART driver ver 2.3 [ 6.736344] Bluetooth: HCI UART protocol H4 registered [ 6.738933] deferring isp device registration [ 6.744181] Bluetooth: HCI UART protocol BCSP registered [ 6.759654] Bluetooth: HCI UART protocol ATH3K registered [ 6.772226] hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator [ 6.781824] hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator [ 6.795486] Bluetooth: HCI UART protocol Broadcom registered [ 6.855725] imx219 14-0010: supply VANA not found, using dummy regulator [ 6.864576] Bluetooth: HCI UART protocol QCA registered [ 7.025046] imx219 14-0010: supply VDIG not found, using dummy regulator [ 7.032328] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 7.073636] imx219 14-0010: supply VDDL not found, using dummy regulator [ 7.082134] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 7.083381] deferring isp device registration [ 7.091599] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 7.104535] cfg80211: failed to load regulatory.db [ 7.186202] imx219 14-0010: failed to read chip id 219 [ 7.212100] Bluetooth: hci0: BCM: chip id 135 [ 7.217062] Bluetooth: hci0: BCM: features 0x0f [ 7.223020] Bluetooth: hci0: BCM4373A0 [ 7.227012] Bluetooth: hci0: BCM4373A0 (001.001.025) build 0000 [ 7.233073] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 7.239745] Bluetooth: hci0: BCM: 'brcm/BCM4373A0.hcd' [ 7.244989] Bluetooth: hci0: BCM: 'brcm/BCM.hcd' [ 7.273105] imx219: probe of 14-0010 failed with error -5 [ 7.280748] deferring isp device registration [ 7.284090] brcmfmac: brcmf_fw_alloc_request: using cypress/cyfmac4373-sdio for chip BCM4373/0 [ 7.290602] imx219 15-0010: supply VANA not found, using dummy regulator [ 7.293925] brcmfmac mmc2:0001:1: Direct firmware load for cypress/cyfmac4373-sdio.boundary,imx8mp-nitrogen-smarc.bin failed with error -2 [ 7.316486] deferring isp device registration [ 7.317794] brcmfmac mmc2:0001:1: Direct firmware load for cypress/cyfmac4373-sdio.bin failed with error -2 [ 7.350563] imx219 15-0010: supply VDIG not found, using dummy regulator [ 7.358179] imx219 15-0010: supply VDDL not found, using dummy regulator [ 7.378851] imx219 15-0010: failed to read chip id 219 [ 7.384971] imx219: probe of 15-0010 failed with error -5 [ 8.338351] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 [ 8.443600] IPv6: ADDRCONF(NETDEV_CHANGE): can1: link becomes ready [ 8.450954] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready [ 8.682664] Micrel KSZ9031 Gigabit PHY 30be0000.ethernet-1:07: attached PHY driver (mii_bus:phy_addr=30be0000.ethernet-1:07, irq=93) [ 8.789444] imx-dwmac 30bf0000.ethernet eth1: PHY [stmmac-0:07] driver [Micrel KSZ9031 Gigabit PHY] (irq=89) [ 8.808085] imx-dwmac 30bf0000.ethernet eth1: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 8.822348] imx-dwmac 30bf0000.ethernet eth1: No Safety Features support found [ 8.829658] imx-dwmac 30bf0000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported [ 8.843207] imx-dwmac 30bf0000.ethernet eth1: registered PTP clock [ 8.862347] imx-dwmac 30bf0000.ethernet eth1: FPE workqueue start [ 8.868515] imx-dwmac 30bf0000.ethernet eth1: configuring for phy/rgmii-id link mode [ 13.200889] fec 30be0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 13.208941] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 13.230843] 8021q: 802.1Q VLAN Support v1.8 [ 13.236988] 8021q: adding VLAN 0 to HW filter on device eth1 [ 34.126325] vref-1v8: disabling [ 293.030168] wlan: Loading MWLAN driver [ 293.034357] wlan: Register to Bus Driver... [ 293.038657] wlan: Register to Bus Driver Done [ 293.043044] wlan: Driver loaded successfully Thanks. Simão Re: Nitrogen8M fails to detect Wi-Fi module Hi, @SimaoLeite  Can you please let  me know your kernel version? Are you using Linux kernel 6.6.3? And also, please share me your full dmesg logs so that I can check what happened on your side. Thanks. Christine.

s32k312 spi2 clock wire ouput extra pulse at begining. Hi Nxp,     i am using s32k312 spi2 to send  data. and found spi2 clk line always output extra one pulse  as  pic below(blue waveform is clock line),  how's that happen. it not happened in spi1. attached is a sample project. 回复： s32k312 spi2 clock wire ouput extra pulse at begining. 1. sck pull-up resistor cause this problem. 2. spi-sd need send data with CS high, so manually control cs instead of lpspi2_pcs0. 回复： s32k312 spi2 clock wire ouput extra pulse at begining. I tested your attached project and did not see the waveform mentioned in your screenshot(I don't see any SPI data at all). Please re-upload the test project. In addition, why do you use PTE11 as GPIO(PCS) instead of configuring PTE11 as lpspi2_pcs0? Also, why call IP_LPSPI_2->TCR |= speed << 27; instead of using the S32 Configuration Tool to configure SpiBaudrate? It is recommended to refer to the Lpspi_Flexio_Ip_Transfer_S32K344, Lpspi_Ip_HalfDuplexTransfer_S32K344 projects in S32K3 RTD 4.0.0 or Example S32K312 SPI Transmit & Receive Using DMA DS3.5 RTD300 回复： s32k312 spi2 clock wire ouput extra pulse at begining. attached files Re: s32k312 spi2 clock wire ouput extra pulse at begining. Hello, The extra clock pulse on the SPI2 clock line is definitely interesting, especially since it doesn’t happen on SPI1. This could be caused by a configuration mismatch in SPI2 settings, such as clock polarity, phase, or transfer mode. It’s also worth checking if SPI2 handles idle states differently or if there’s a subtle difference in how the driver or SDK is managing it. Hardware issues like signal integrity could also play a role, though it’s less likely.

S32K3 MCAL CANFDマスク設定のバグ 皆さん、こんにちは EDFビット、標準CANFDはビット14である必要がありますが、現在は30です。バグですか?そして、それはまだRTD5.0.0に存在します。 MCALコードでは、CANFDフレームを送信する場合、着信パラメータのCANFDメッセージIDのFDFバイトを1にする必要があります。つまり、CANFD標準フレームのBit14は1です。バグがあります。CANFD フレーム形式に従ってCAN_43_FLEXCAN_FD_FRAME_U32ビット 14 をマスクする必要があります。現在はビット 30 に設定されています。 BRs、 仙龍 Re:S32K3 MCAL CANFDマスク設定のバグ Hi@武仙龍 こちらの記事を参考にしてください。 https://community.nxp.com/t5/S32K/Use-S32K358-flexcan-to-sent-extended-ID/td-p/1993198https://nxp.lightning.force.com/lightning/r/Case/500KA0000039pXzYAI/view Re:S32K3 MCAL CANFDマスク設定のバグ こんにちは すみません、よく見てしまいました。これはバグではなく、ソフトウェア設計です。CANFD_ID伝送パラメータでは、ユーザーは最大2ビットの32Uを埋める必要があります。 /** * @{ ※@brief Can_IdType * @detailsはL-PDUの識別子を表します。最上位 2 ビットは、フレーム タイプを指定します。 * -00 標準 CAN ID の CAN メッセージ * -01 標準CAN ID付きCAN FDフレーム * -10 CANメッセージ(拡張CAN ID付き) * -11 CAN FDフレーム(拡張CAN ID付き) ※@implements Can_IdType_type */ /* Can_CreatePduInfo(id |CAN Can_IdType_type、swPduハンドル、長さ、sdu) */ Can_PduInfo = Can_CreatePduInfo(0U |CAN_43_FLEXCAN_FD_FRAME_U32、0U、16U、Can_au8Sdu8bytes);

RW612 zigbee サポート こんにちは RW612システムにZigBeeサポートを追加する予定はありますか?コーディネーターの役割です。最大64ノードまでの小さなネットワークでこのタスクを行うには十分強力だと思います 日時:RW612 zigbeeサポート それを見つけました。 感謝 日時:RW612 zigbeeサポート 申し訳ありませんが、このファイルとフォルダが見つかりません。 このファイルをRW612用にダウンロードする方法を教えてください。 日時:RW612 zigbeeサポート ありがとうございます！ 確認してみます

K144 is stuck in the ESD test The customer's engineer is doing the ESD test, and the external equipment is stuck, and the hardware reset on the board cannot be reset normally, and can only work normally if it is powered on again.The output interface is connected to the TVS tube,Whether the MCU is protected and cannot be reset by hardware?Thanks！ Re: K144 is stuck in the ESD test HELLO, You can try with below Steps to Troubleshoot and Resolve: Check the TVS Tube: Ensure the TVS tube is correctly rated for your circuit. Its breakdown voltage should be slightly above your operating voltage, and its clamping voltage must protect your components during an ESD event. Inspect the Reset Circuit: Take a close look at the MCU’s reset pin. Make sure the pull-up or pull-down resistors and any timing capacitors are properly set up. Also, confirm the reset signal lasts long enough to fully restart the CLIC AQUÍ MCU. Use Decoupling Capacitors: Add small, high-frequency capacitors (e.g., 0.1 µF) near the MCU’s power pins. This helps smooth out any voltage spikes caused by ESD. Verify Proper Grounding: Ensure the PCB design has a solid ground plane. The TVS tube needs a good ground connection to divert ESD energy effectively. Test for Latch-Up: After an ESD event, check the MCU’s current draw. If it’s unusually high, the MCU might be in a "latch-up" state, which often requires power cycling to fix. Adding resistors or improving bypass capacitors can help prevent this. Check Power Stability: Make sure your power supply doesn’t dip or spike during an ESD event. A stable supply ensures the MCU and other components can recover properly without needing a full power cycle.

Need help witn I2C code (using Peripheral Config Tool) I need to use the I2C1 peripheral. I checked the example programs. But I must say that is not really example code. Because with example code I expect good comments explaining the why's and how's. But there is zero comments! As a programmer I would never write such code, and certainly not example code! But what is worst, the examples do not use the Peripheral and Clock Config Tools while that is said to be the preferred way of working! So I have to figure everything out myself. But without good examples that is hard. Very hard. For instance: one can choose one of the modes: Polling, Interrupts, Transfer, eDMA and RTOS. Is there any explanation somewhere what they exactly mean? Is a programmer I think I have an idea of Polling, Interrupt and eDMA. But what is Transfer? They all transfer data. And why is RTOS is separate mode. Isn't RTOS also eDMA or Interrupts? If I choose one of these modes, which function am I supposed to use? Are those the same as the examples that are not based on the Peripheral Config Tools? What is the expected way to find you way around? (And please, please, please, give us example code that uses the Config Tools!) Re: Need help witn I2C code (using Peripheral Config Tool) Hi @simmania , Thanks for your reply. I did a validation as you do.  I create a new project, and set pin in Config Tool, I use the I2C pins just as you do. and copy driver files from  evkmimxrt1010_lpi2c_interrupt_b2b_transfer_master to the new project, also I copy code from evkmimxrt1010_lpi2c_interrupt_b2b_transfer_master.c to the new project file MIMXRT1011_Project.c I use MIMXRT1064-EVK board as I 2C slave.  I test that I2C can work normal. Wish it helps you. If you still have question about it, please kindly let me know. BR mayliu Re: Need help witn I2C code (using Peripheral Config Tool) No, I did not copy the mex file, but I configured the I2C IO pins properly and checked for correct clock in the Clock Config tool. Re: Need help witn I2C code (using Peripheral Config Tool) Hi @simmania , Thank you so much for your interest in our products and for using our community. I'm sorry that you have  problem while using the NXP config tool. I want to know did you copy  evkmimxrt1010_lpi2c_interrupt_b2b_transfer_master.mex file   into your new project? If you change I2C pin, Please double check I2C PIN configuration. Especially  Software Input On and Open drain need to be set enable. If you want to know more about NXP Config Tool, maybe you refer "MCUXpresso_IDE_ConfigTools_User_Guide.pdf",  This file is in your MCUXPresso IDE installed path. Wish it helps you. If you still have question about it, please kindly let me know. Best Regards mayliu Re: Need help witn I2C code (using Peripheral Config Tool) Update: When create a new project and copy the whole file with the main function of the working example into this new project, it gives the same problem! So only a start condition on the I2C bus and then it stops. What is different from a example and a new project that can cause this? Re: Need help witn I2C code (using Peripheral Config Tool) I'm using the MIMXRT1010-EVK board. I copied some code from the example 'evkmimxrt1010_lpi2c_interrupt_b2b_transfer_master' into a new project. I did configure the Pins, Clock and Peripheral for the LPI2C1 port with the config tools, so I removed that code from the main function. But it does not work. While the example project did work. So what am I doing wrong? The clock for the LPI2C is configured for 10MHz, The pins GPIO_01 and GPIO_02 are assigned to the LPI2C1. And the peripheral is configured as shown in the attached picture. The main code is listed below. Note that when I run this program I do see activity on the I2C lines. It looks like the start condition is generated and then immediately both lines go high and stay high. The interrupt routine is called with status != kStatus_Success. The value is 905, but I can not found out what that means. #include #include "board.h" #include "peripherals.h" #include "pin_mux.h" #include "clock_config.h" #include "fsl_debug_console.h" #include #include "fsl_lpi2c.h" #define EXAMPLE_I2C_MASTER_BASE (LPI2C1_BASE) #define EXAMPLE_I2C_MASTER ((LPI2C_Type *)EXAMPLE_I2C_MASTER_BASE) #define I2C_MASTER_SLAVE_ADDR_7BIT 0x1AU // // Global variables // lpi2c_master_handle_t g_m_handle; volatile bool g_MasterCompletionFlag = false; volatile bool g_MasterNackFlag = false; static void lpi2c_master_callback(LPI2C_Type *base, lpi2c_master_handle_t *handle, status_t status, void *userData) { PRINTF("\r\n*** INT\r\n"); if (status == kStatus_LPI2C_Nak) {     g_MasterNackFlag = true; } else {     g_MasterCompletionFlag = true;     /* Display failure information when status is not success. */     if (status != kStatus_Success)     {         PRINTF("\r\n*** Error occured during transfer! status = %d\r\n", status);     } } } /* * @brief Application entry point. */ int main(void) { /* Init board hardware. */ BOARD_ConfigMPU(); BOARD_InitBootPins(); BOARD_InitBootClocks(); BOARD_InitBootPeripherals(); #ifndef BOARD_INIT_DEBUG_CONSOLE_PERIPHERAL /* Init FSL debug console. */ BOARD_InitDebugConsole(); #endif lpi2c_master_transfer_t masterXfer = {0}; status_t reVal = kStatus_Fail; /* Create the LPI2C handle for the non-blocking transfer */ LPI2C_MasterTransferCreateHandle(EXAMPLE_I2C_MASTER, &g_m_handle, lpi2c_master_callback, NULL); PRINTF("\r\nSend data to slave...\r\n"); uint8_t deviceAddress = 0x01U; uint8_t data[1] = {0xAA}; masterXfer.slaveAddress = I2C_MASTER_SLAVE_ADDR_7BIT; masterXfer.direction = kLPI2C_Write; masterXfer.subaddress = (uint32_t)deviceAddress; masterXfer.subaddressSize = 1; masterXfer.data = data; masterXfer.dataSize = 1; masterXfer.flags = kLPI2C_TransferDefaultFlag; /* Send master non-blocking data to slave */ reVal = LPI2C_MasterTransferNonBlocking(EXAMPLE_I2C_MASTER, &g_m_handle, &masterXfer); if (reVal != kStatus_Success) {     PRINTF("\r\nI2C transfer error!\r\n");     return -1; } /* Wait for transfer completed. */ while ((!g_MasterCompletionFlag) && (!g_MasterNackFlag)) { } if (g_MasterNackFlag) {     PRINTF("- Master nacked by slave!\r\n");     g_MasterNackFlag = false; } g_MasterCompletionFlag = false; PRINTF("\r\nEnd of LPI2C example.\r\n"); while (1) { } return 0 ; } Re: Need help witn I2C code (using Peripheral Config Tool) Hi @simmania  Please let us know your chip part number thus we can assign right engineer to answer your questions. Thanks, Jun Zhang

I2Cコードに関するヘルプが必要(Peripheral Config Toolを使用) I2C1 周辺機器を使用する必要があります。サンプルプログラムを確認しました。しかし、それは実際にはサンプルコードではないと言わざるを得ません。サンプルコードでは、なぜとどのように説明するための良いコメントを期待しているからです。しかし、コメントはゼロです!プログラマーとして、私はそのようなコードを書くことは決してありませんし、ましてやサンプルコードも書きません。 しかし、最悪なことに、この例では、ペリフェラルツールとクロックコンフィグツールを使用しませんが、それが好ましい作業方法と言われています。 だから、自分ですべてを理解しなければなりません。しかし、良い例がなければ、それは難しいことです。とても難しいです。 たとえば、ポーリング、割り込み、転送、eDMA、RTOSのいずれかのモードを選択できます。それらが正確に何を意味するのか、どこかに説明はありますか? プログラマーですが、ポーリング、割り込み、eDMAのアイデアがあると思います。しかし、転送とは何ですか?それらはすべてデータを転送します。そして、なぜRTOSは別のモードなのか。RTOSはeDMAや割り込みもしないの? これらのモードのいずれかを選択した場合、どの機能を使用することになっていますか?これらは、Peripheral Config Tools に基づいていない例と同じですか。 あなたの道を見つけるための期待される方法は何ですか? (そして、どうか、どうか、Config Toolsを使用したサンプルコードを教えてください! Re:I2Cコードに関するヘルプが必要(Peripheral Config Toolを使用) いいえ、mex ファイルはコピーしていませんが、I2C IO ピンを適切に構成し、Clock Config ツールで正しいクロックを確認しました。

需要 I2C 代码帮助（使用外围配置工具） 我需要使用 I2C1 外围设备。我检查了示例程序。但我必须说这不是真正的示例代码。因为我希望通过示例代码得到很好的注释来解释原因和方法。但没有任何评论！作为一名程序员，我永远不会编写这样的代码，当然也不会编写示例代码！ 但最糟糕的是，这些示例不使用外围设备和时钟配置工具，而据说这是首选的工作方式！ 所以我必须自己解决所有问题。但如果缺乏好的例子，那就很难。非常困难。 例如：可以选择以下模式之一：轮询、中断、传输、eDMA 和 RTOS。有没有什么地方可以解释它们到底是什么意思？ 作为一名程序员，我认为我对轮询、中断和 eDMA 有所了解。但是转移是什么？它们都传输数据。为什么 RTOS 是独立模式？RTOS 不也是 eDMA 或中断吗？ 如果我选择其中一种模式，我应该使用哪个函数？这些函数与非基于外设配置工具的示例相同吗？ 预计用什么方式可以找到路？ （并且请，请，请给我们提供使用配置工具的示例代码！） 回复：需要 I2C 代码帮助（使用外围配置工具） 不，我没有复制 mex 文件，但我正确配置了 I2C IO 引脚并在时钟配置工具中检查了正确的时钟。

K144在ESD测试中卡住了 客户工程师在做ESD测试，外部设备卡死，板子上的硬件复位无法正常复位，需要重新上电才能正常工作。输出接口接了TVS管，请问MCU是否做了保护，无法硬件复位？谢谢！

K144がESDテストで動かなくなる お客様のエンジニアがESDテストを行っており、外部機器が動かなくなり、ボード上のハードウェアリセットは正常にリセットできず、再度電源を入れた場合にのみ正常に動作します。出力インターフェースはTVSチューブに接続されていますが、MCUは保護されており、ハードウェアでリセットできないかどうか?感謝！

S32K3 MCAL CANFD mask setting bug Hi, All The EDF bit the standard CANFD should be bit 14.but now it is 30. Is it a bug ? and it still exists in rtd5.0.0. In the MCAL code, if you want to send a CANFD frame, you need to have the FDF byte of the CANFD message ID of the incoming parameter to be 1, that is, the Bit14 of the CANFD standard frame is 1. There is a Bug. According to the CANFD frame format CAN_43_FLEXCAN_FD_FRAME_U32 should mask bit 14. Now it is set to bit 30. BRs, xianlong Re: S32K3 MCAL CANFD mask setting bug Hi@wuxianlong Please refer to this post. https://community.nxp.com/t5/S32K/Use-S32K358-flexcan-to-sent-extended-ID/td-p/1993198https://nxp.lightning.force.com/lightning/r/Case/500KA0000039pXzYAI/view Re: S32K3 MCAL CANFD mask setting bug Hi, Sorry, I took a closer look. This is not a BUG, it is a software design. The CANFD_ID transmission parameter requires the user to fill in the maximum two bits of 32U. /** * @{ * @brief Can_IdType * @details Represents the Identifier of an L-PDU. The two most significant bits specify theframe type: * -00 CAN message with Standard CAN ID * -01 CAN FD frame with Standard CAN ID * -10 CAN message with Extended CAN ID * -11 CAN FD frame with Extended CAN ID * @implements Can_IdType_type */ /* Can_CreatePduInfo(id | CAN Can_IdType_type, swPduHandle,length, sdu) */ Can_PduInfo = Can_CreatePduInfo(0U | CAN_43_FLEXCAN_FD_FRAME_U32, 0U, 16U, Can_au8Sdu8bytes); Re: S32K3 MCAL CANFD mask setting bug DataInfo.fd_enable = ((PduInfo->id & CAN_43_FLEXCAN_FD_FRAME_U32) != 0U) ? TRUE : FALSE;

16位总线和IVT数据的并行NOR-Flash 你好。 在 i.MX7D 参考手册第 1241 页上，IVT 头格式图表明要设置的值为 0xD1-0x0020-0x40 到 .word0xD1002040，但在20132年“i.MX6 IVT结构”中Anson Huang回答说应该是.word0x402000D1。 我认为手册上说的是 0x400 = 0xD100 0x402 = 0x2040 但这是错误的吗？ 谢谢！ 回复：16位总线和IVT数据的并行NOR闪存 谢谢 Harvey021。 那么安森用小端方式解释了吗？ 我很困惑，因为参考手册说它是大端的。

S32K3 MCAL CANFD 掩码设置错误 大家好 标准 CANFD 的 EDF 位应该是位 14，但现在是位 30。这是一个错误吗？并且它仍然存在于 rtd5.0.0 中。 在MCAL代码中，如果要发送CANFD帧，需要让传入参数的CANFD报文ID的FDF字节为1，也就是CANFD标准帧的Bit14为1。有一个 Bug。根据 CANFD 帧格式，CAN_43_FLEXCAN_FD_FRAME_U32 应该屏蔽位 14。现在它被设置为位 30。 BRs， 显龙 回复：S32K3 MCAL CANFD 掩码设置错误 嗨@吴贤龙 请参考此帖子。 https://community.nxp.com/t5/S32K/Use-S32K358-flexcan-to-sent-extended-ID/td-p/1993198https://nxp.lightning.force.com/lightning/r/Case/500KA0000039pXzYAI/view 回复：S32K3 MCAL CANFD 掩码设置错误 你好， 抱歉，我仔细看了看。这不是一个BUG，而是一个软件设计。CANFD_ID传输参数需要用户填写最大两位32U。 /** * @{ * @brief Can_Id类型 * @details 表示 L-PDU 的标识符。两个最高有效位指定帧类型： * -00 带有标准 CAN ID 的 CAN 消息 * -01 带有标准 CAN ID 的 CAN FD 帧 * -10 带有扩展 CAN ID 的 CAN 消息 * -11 带有扩展 CAN ID 的 CAN FD 帧 * @implementsCan_IdType_type */ /*Can_CreatePduInfo（id | CAN Can_IdType_type，swPduHandle，长度，sdu）*/ Can_PduInfo = Can_CreatePduInfo(0U | CAN_43_FLEXCAN_FD_FRAME_U32, 0U, 16U, Can_au8Sdu8字节);

RW612 zigbee support Hello Are there time-specific plans to add ZigBee support for the RW612 system? I mean the role of coordinator. I think it is powerful enough for this task for small network up to 64 nodes Re: RW612 zigbee support I found it. Thanks Re: RW612 zigbee support Hello, You can download the SDK for FRDM-RW612 here: MCUXpresso SDK Builder Regards, Ricardo Re: RW612 zigbee support Sorry but I con't find this file and folder. Could You advise how to download this files for RW612 ? Re: RW612 zigbee support Thank You! I will check it Re: RW612 zigbee support Hello, Hope you are doing well. Could you please check the following document? SDK\middleware\wireless\zigbee\examples\zigbee_coordinator\README.md. Hope this helps! Regards, Ricardo

RW612 Zigbee 支持 你好 是否有具体时间计划为 RW612 系统添加 ZigBee 支持？我指的是协调员的角色。我认为对于最多 64 个节点的小型网络来说，它足以完成这项任务 回复：RW612 Zigbee 支持 我找到了。 谢谢 回复：RW612 Zigbee 支持 抱歉，我找不到这个文件和文件夹。 您能否建议如何下载 RW612 的这些文件？ 回复：RW612 Zigbee 支持 谢谢你！ 我会检查

[Security] Clear ALL Keys Dear NXPs： uSFE = false; The Key attribute of MASTER_ECE_KEY is set to: Write Prot = 0; Boot Prot = 1; Debugger Prot = 1; KeyUsage = 1; Wild card = 1; Then I want to call the bool eraseKeys(void) interface (csec_utils.h) to Clear all keys. But when The bool getUID(uint8_t *uid) function returned a STATUS_SEC_KEY_NOT_AVAILABLE error when calling the CSEC_DRV_GetID interface. What should I do to erase all keys? Re: [Security] Clear ALL Keys Dear lukaszadrapa: Got it, thanks for the reply. Is there any way I can erase all keys? Re: [Security] Clear ALL Keys Hi @Gideon  it makes sense. If you used: Boot Prot = 1; Debugger Prot = 1; ... then: So, the secure boot must be successful and debugger can't be connected to be able to use the key. Regards, Lukas

s32g sja1110 startup Hi, I am developing the functions of SJA1110 recently, and I know very little about it. Currently, the SJA1110 S32 SDK is being applied for by the supplier. I can only learn about the functions of SJA1110 through "S32G2_LinuxBSP_39.0_User_Manual.pdf" and posts on the forum. So I have the following questions: 1. What are the functions of SJA1110 S32 SDK? Can I use this SDK to configure the port functions of SJA1110 on S32DS? Because the network interface of our customized version is slightly different from that of S32G2-VNP-RDB2 2. At present, because the SJA1110 S32 SDK is being applied for, I downloaded Godvip1.1.0 from the official website. From the user manual, I saw that the supported linux bsp version is 39, and extracted the sja1110 firmware from it. So I also downloaded yocto's bsp39 in my linux environment, and modified the build/conf/local.conf file, added the paths of sja1110_uc.bin and sja1110_switch.bin, and finally compiled and generated the .sdcard file, burned the image to my SD card, and finally loaded it in S32G2-VNP-RDB2. I set SW12 to 1-0 and started from norflash. Finally, I found from the serial port log that the SJA1110 function was not enabled. I put the log in the attachment. Please help me analyze the reason and give suggestions. Thank you 3. Finally, I would like to ask, for the development of SJA1110, my understanding is that data is written to SJA1110 through SPI, so it should be feasible for A core or M core control; 3.1 But why do I see in the forum that everyone is basically developing based on A core? 3.2 If you want to modify the port function of SJA1110, how should you modify it? Please give me some suggestions, thank you~ SJA1110 S32G2 S32G-VNP-RDB2  回复： s32g sja1110 startup hi，jiajun_cheng Thank you for your reply. For details, see 4. SJA1110 Port4 PHY Speed Configuration in the S32G-VNP-RDB2 Reference Design Ethernet Enablement Guide (download link：S32G-VNP-RDB2 Reference Design Ethernet Enablement Guide) In addition, “Upload successfully verified” means SJA1110 image loaded successfully, and SJA1110 Port will work on your configuration Hope it can help you. BR Joey 回复： s32g sja1110 startup Hi， @Joey_z : In the afternoon, my SJA1110 SDK application was approved, and I followed" S32G-VNP-RDB3 Ethernet Enablement Guide"Loaded switch_uc.bin.For the configuration of sja1110, is there any article for RDB2 development board.Is there any article that explains it in more detail? s32g274ardb2 login: root root@s32g274ardb2:~# dmesg | grep sja1110 [ 0.548540] gpio-24 (sja1110-rst-phy-t1): hogged as output/low [ 0.553963] gpio-81 (sja1110-rst-core): hogged as output/low [ 0.619550] sja1110-sw@1 enforce active low on chipselect handle [ 8.417247] sja1110: loading out-of-tree module taints kernel. [ 8.417843] SPI driver sja1110 has no spi_device_id for nxp,sja1110-switch [ 8.417852] SPI driver sja1110 has no spi_device_id for nxp,sja1110-uc [ 8.417961] sja1110 spi5.0: probing uc [ 8.418121] sja1110 spi5.1: probing switch [ 8.418445] sja1110 spi5.1: Could not get GPIO from device tree [ 8.418473] sja1110 spi5.1: [sja1110_post_probe_upload_worker] Trying to initialize switch [ 8.418628] sja1110 spi5.1: Direct firmware load for sja1110_switch.bin failed with error -2 [ 8.418641] sja1110 spi5.1: request_firmware failed with -2 [ 8.418648] sja1110 spi5.0: [sja1110_post_probe_upload_worker] Trying to initialize uC [ 8.425720] sja1110 spi5.0: [sja1110_init_hw] loaded fw 'sja1110_uc.bin' [ 8.425740] sja1110 spi5.0: [sja1110_pre_uc_upload] Found firmware of size 126400 [ 8.425844] sja1110 spi5.0: [sja1110_pre_uc_upload] firmware appears to be valid [ 8.425896] sja1110 spi5.0: [sja1110_pre_uc_upload] \xc2\xb5C not ready for download (Status=0x31) [ 8.426017] sja1110 spi5.0: Uploading firmware... [ 8.733955] sja1110 spi5.0: Upload successfully verified! 回复： s32g sja1110 startup hi，jiajun_cheng Thank you for contacting us. 1. I will further test the problems encountered in put sja1110_uc.bin and sja1110_switch.bin in /lib/firmwarene.Thank you  for your information. 2. In addition, Refer to UGS32G-VNP-RDB3-ethernet-enablem-guide.pdf (3.sJA1110 Port Configuration) Section 3 (download link S32G-VNP-RDB3 Ethernet:S32G-VNP-RDB3 Ethernet Enablement User Guide). The  User Guide describes how to configure port functionality for SJA1110 using the S32DS. 3. I think data is written to SJA1110 through SPI, and it should be ok to control SJA1110 with A core or M core. I will conduct internal consultation on the specific reasons and reply to you as soon as possible after getting the result. Hope it can help you. BR Joey 回复： s32g sja1110 startup After reading this article, I chose to put sja1110_uc.bin and sja1110_switch.bin in /lib/firmware, and the log is as follows root@s32g274ardb2:~# dmesg | grep sja [ 0.544308] gpio-345 (sja1110-rst-phy-t1): hogged as output/low [ 0.549823] gpio-402 (sja1110-rst-core): hogged as output/low [ 0.615697] sja1110-sw@1 enforce active low on chipselect handle [ 7.283003] sja1110: loading out-of-tree module taints kernel. [ 7.290192] SPI driver sja1110 has no spi_device_id for nxp,sja1110-switch [ 7.290198] SPI driver sja1110 has no spi_device_id for nxp,sja1110-uc [ 7.290309] sja1110 spi5.0: probing uc [ 7.290468] sja1110 spi5.1: probing switch [ 7.290781] sja1110 spi5.1: Could not get GPIO from device tree [ 7.290809] sja1110 spi5.1: [sja1110_post_probe_upload_worker] Trying to initializ e switch [ 7.294511] sja1110 spi5.1: [sja1110_init_hw] loaded fw 'sja1110_switch.bin' [ 7.294621] sja1110 spi5.1: [sja1110_pre_switch_upload] Found switch config of siz e 2236 [ 7.294768] sja1110 spi5.1: Uploading config... [ 7.373625] sja1110 spi5.1: Successfully configured! [ 7.373655] sja1110 spi5.0: [sja1110_post_probe_upload_worker] Trying to initializ e uC [ 7.394231] sja1110 spi5.0: [sja1110_init_hw] loaded fw 'sja1110_uc.bin' [ 7.394252] sja1110 spi5.0: [sja1110_pre_uc_upload] Found firmware of size 320280 [ 7.394370] sja1110 spi5.0: [sja1110_pre_uc_upload] firmware appears to be valid [ 7.394422] sja1110 spi5.0: [sja1110_pre_uc_upload] µC not ready for download (Sta tus=0x31) [ 7.394649] sja1110 spi5.0: Uploading firmware... [ 8.200328] sja1110 spi5.0: Upload successfully verified!

[i.MX93][thermal] i.MX93 cpu tthermal trip is wrong Hi, i.MX93 thermal trip is wrong in imx93.dtsi thermal-zones { cpu-thermal { polling-delay-passive = <250>; polling-delay = <2000>; thermal-sensors = <&tmu 0>; trips { cpu_alert: cpu-alert { temperature = <80000>; hysteresis = <2000>; type = "passive"; }; cpu_crit: cpu-crit { temperature = <90000>; hysteresis = <2000>; type = "critical"; }; }; cooling-maps { map0 { trip = <&cpu_alert>; cooling-device = <&A55_0 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>, <&A55_1 THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; }; }; }; }; It's 80 degree on alert, 90 degree on crit. It's different from u-boot log u32 get_cpu_temp_grade(int *minc, int *maxc) { int ret; u32 val; ret = fuse_read(2, 3, &val); if (ret) val = 0; /* If read fuse failed, return as blank fuse */ val >>= 4; val &= 0x3; if (minc && maxc) { if (val == TEMP_AUTOMOTIVE) { *minc = -40; *maxc = 125; } else if (val == TEMP_INDUSTRIAL) { *minc = -40; *maxc = 105; } else if (val == TEMP_EXTCOMMERCIAL) { if (is_imx93()){ /* imx93 only has extended industrial*/ *minc = -40; *maxc = 125; } else { *minc = -20; *maxc = 105; } } else { *minc = 0; *maxc = 95; } } return val; } Which i.MX8M PLUS remains the same as commercial grade. ------- This leads to kernel reboot when it reach to 90 degree. And branch 'lf-6.6.y' is not change yet. Does this setting has some consideration? Or I can just modify by my self? Re: [i.MX93][thermal] i.MX93 cpu tthermal trip is wrong Hi, @yoooh8668! Thank you for contacting NXP Support! For alert and critical temperatures you have to adjust the temperatures on iMX93.dtsi or iMX8MP.dtsi. By default, we configure the device at a temperature that we consider safe to use the processor but you can modify the Thermal zones in the device tree. Best Regards! Chavira

How to convert MCUXpresso project into cmake project Hi,  Currenlty i am trying to convert MXRT1050 led blink SDK example into cmake project. I've got everything compiling and linking, but the code fails to run properly. i cant able to see any led blinks on my MXRT1050 evk board. Please find the attached cmake template project. And help me to solve this issue. When i flash example project console output looks below, starting address was 0x60000000.  when i flash my cmake generated axf file, its starting address shows 0x60002000. #MXRT1050 #CMAKE Re: How to convert MCUXpresso project into cmake project Hi @ganes_rames  My apologies for the delayed response.  I have been checking your source code, and it seems that the IVT is not placed at 0x6000_1000 as the bootROM requires I comparted the .map file from your project to the .map  file from the RT1060 led_blinky SDK example (  image configuration is the same for RT1050) . T Here is how a map file with the  IVT and the bootheaders well defined look like By inspecting closely with a map file viewer, I did not saw the IVT or FCB defined somewhere or the FCB. I I hope this explains the issue.  Diego Re: How to convert MCUXpresso project into cmake project Hi @diego_charles,                  Thanks for response. Actually your correct. The issue is XIP related object files contents are not linked, while inspecting my genrated map file i found XIP related object files contents are not placed in .boot_hdr section. Here i am sharing my build folder also, hope it will be more helpful to understand the issue. The reason I suspect I'm doing something wrong with XIP, is because I include the xip-directory & source files in the build, but I fail to see how they are used or referenced in the code or linker file. In my main cmakelist.txt i have added compile definitions related XIP folders, -DXIP_EXTERNAL_FLASH=1 -DXIP_BOOT_HEADER_ENABLE=1 am i missing anything ?? Can someone clarify this for me? Any ideas? xip folder contains: - fsl_flexspi_nor_boot.c & .h - evkbimxrt1050_flexspi_nor_config.c & .h Re: How to convert MCUXpresso project into cmake project Hi @ganes_rames , Thank you for your interest in our products. Could you check the images created in the debug folder? I did not saw them in your rar file, let me explain what I mean below.  A bootable image generated by the MCUXpresso should contain the FCB ( for the FlexSPI and flash configuration ) at 0x6000_0000, the IVT (  image vector table to let the bootROM know where is the image entry: vector table or resetISR address) and the code, starting at 0x6000_2000, at least. The bootROM does need those contents in order to boot an  XIP image from FlexSPI NOR flash, if not it will not boot anything.  Based on the above, it migth be the that your image at 0x6000_2000 does not contain the FCB and IVT. If it does not  you will need to add them to your image, in a tipical RT1050 MCUXpresso IDE project they are contained in the XIP folder.  I recommend  you using an hexadecimal editor or viewer, I use hexedit a lot. Another suggestion is to use our MCUXpresso Secure Provisioning Tool to create a bootable image with the IVT at 0x6000_1000 and program the FCB too at 0x6000_0000. This is quick way to create a bootable image without having to worry about the XIP folder contents. Plus making code more generic without having a dedicated flash configuration or FCB for an specific memory.  I hope this could help you! Diegom Re: How to convert MCUXpresso project into cmake project Here i am sharing my cmake template project