i.MX 8QuadXPlus - MEK Default configuration and files "out-of-the-box" Hello, I would like some help to find/have the files and the setup procedure to return my development board as it was "out-of-the-box": i.MX 8QuadXPlus Multisensory Enablement Kit | NXP Semiconductors I couldn't find the files and the procedure to do it. I have a HW B0 revision/version. I'm trying to make it run with a LVDS-TO-HDMI bridge but I get no video output (nothing, no console, no blink, no noise, nothing). I would like to test if the LVDS-TO-HDMI bridge is burned or if I'm missing some configuration. I already sent succefully the NXP image for Embedded Linux, Android and Android Automotive OS that are compatible with B0 revision. The LVDS-TO-HDMI bridge is keeping the RED LED always ON and the GREEN LED after the kernel starts up. From the COMM port I can see the "lvds-to-hdmi-bridge@4c" is being recognized by U-Boot. On Embedded Linux, running on SD CARD, the kernel is initializing until it requests the login/password (root by default with blank password). I can navigate into the folders "/dev", etc ... no problem. Can anyone help me with that? Thank you very much! Re: i.MX 8QuadXPlus - MEK Default configuration and files "out-of-the-box" In the fast-evolving world of digital finance, 2026 has brought Bitcoin, Ethereum, USDT, and other digital assets further into the mainstream. Unfortunately, increased adoption has also attracted sophisticated scammers and cybercriminals. Crypto can be lost through investment scams, phishing, hacked wallets, fraudulent trading platforms, exchange issues, hardware failures, or human error. For victims, losing digital assets can be financially and emotionally devastating. At TECHY FORCE CYBER RETRIEVAL (TFCR), our approach is built around one principle: blockchain transactions may be irreversible, but they are often traceable. How We Work We begin by reviewing the circumstances surrounding the loss and gathering available evidence such as wallet addresses, transaction hashes, communications, and platform information. We then analyze blockchain activity to identify transaction flows, connected addresses, and potential leads. Our investigations are conducted with an emphasis on lawful, ethical, and evidence-based practices. We explain our findings clearly and help clients understand the options available for reporting, tracing, and pursuing potential recovery. No Recovery, No Upfront Fees TFCR believes clients should not be pressured into paying simply because they have already suffered a loss. Our service is based on a no-recovery, no-upfront-fee approach, subject to the specific terms of an individual case. While  legitimate recovery service can guarantee you  that cryptocurrency can be recovered, careful investigation can help establish what happened, where assets moved, and what steps may be available next. TECHY FORCE CYBER RETRIEVAL — Follow the blockchain. Understand the trail. Explore the possibilities. Re: i.MX 8QuadXPlus - MEK Default configuration and files "out-of-the-box" In my case I can't see any video output, not even noises on the screen. Re: i.MX 8QuadXPlus - MEK Default configuration and files "out-of-the-box" No, I bought a new LVDS-TO-HDMI converter to test it. But, I don't think that the problem is the HW. Re: i.MX 8QuadXPlus - MEK Default configuration and files "out-of-the-box" facing the same issue with imx8qxp c0 mek. android boots fine facing display not coming up only with android automotive Re: i.MX 8QuadXPlus - MEK Default configuration and files "out-of-the-box" Hi , I'm facing the same issue here. Im using IMX8QUADXPLUS  and HDMI output is not showing . Is the issue resolved for you? @viniciuscarvalho  Re: i.MX 8QuadXPlus - MEK Default configuration and files "out-of-the-box" Hello, thanks for replying. Android Automotive OS: automotive-12.0.0_2.1.0_image_8qmek_car2 If I perform the boot procedure without setting: setenv bootargs console=ttyLP0,115200 earlycon init=/init androidboot.fbTileSupport=enable cma=928M@0x960M-0xfc0M androidboot.primary_display=imx-drm firmware_class.path=/vendor/firmware loop.max_part=7 transparent_hugepage=never moal.mod_para=wifi_mod_para.conf androidboot.lcd_density=240 bootconfig The kernel starts and the LVDS-TO-HDMI bridge is turning the led green (but nothing is being display on the HDMI monitor connected to the bridge). After the kernel finishes the initialization I can navigate through the files/folders on the COMM (serial port)... but without video. If I setenv as ANDROID_QUICK_START_GUIDE I don't have video, the LVDS-TO-HDMI bridge green led doesn't turn ON and the board keeps restarting during the kernel start-up (please see attached log). I don't know what to do. I would like to have the default files and configuration as "out-of-the-box" to check if my HW is OK. Like this video: Get Started with the MCIMX8QXP-CPU | NXP Semiconductors Thank you! Re: i.MX 8QuadXPlus - MEK Default configuration and files "out-of-the-box" This is what I get when I try to boot using Linux (L5.4.24-2.1.0_images_MX8QXPMEK): U-Boot 2020.04-5.4.24-2.1.0+g4979a99482 (May 30 2020 - 16:14:50 +0000) CPU: NXP i.MX8QXP RevB A35 at 1200 MHz at 25C Model: NXP i.MX8QXP MEK Board: iMX8QXP MEK BuildInfo: - SCFW 4a1654e0, SECO-FW 376e3c15, IMX-MKIMAGE 6745ccdc, ATF b0a00f2 - U-Boot 2020.04-5.4.24-2.1.0+g4979a99482 Boot: MMC0 DRAM: 3 GiB TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50] MMC: FSL_SDHC: 0, FSL_SDHC: 1 Loading Environment from MMC... *** Warning - bad CRC, using default environment [*]-Video Link 0i2c: Error check busy bus: 0x8 it6263_i2c_reg_read, read err -102 faill to read from it6263 revision, ret -102 (1280 x 720) [0] dpu@56180000, video [1] lvds-channel@0, display [2] lvds-to-hdmi-bridge@4c, video_bridge In: serial Out: serial Err: serial switch to partitions #0, OK mmc0(part 0) is current device flash target is MMC:0 Net: Warning: ethernet@5b040000 using MAC address from ROM eth0: ethernet@5b040000 [PRIME] Warning: ethernet@5b050000 (eth1) using random MAC address - da:dd:53:ac:0a:62 , eth1: ethernet@5b050000 Fastboot: Normal Normal Boot Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0(part 0) is current device 28021248 bytes read in 125 ms (213.8 MiB/s) Booting from mmc ... 97270 bytes read in 9 ms (10.3 MiB/s) ## Flattened Device Tree blob at 83000000 Booting using the fdt blob at 0x83000000 Using Device Tree in place at 0000000083000000, end 000000008301abf5 Disable clock-controller@5a4d0000 rsrc 62 not owned Disable clock-controller@5ac90000 rsrc 102 not owned Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd042] [ 0.000000] Linux version 5.4.24-2.1.0+gbabac008e5cf (oe-user@oe-host) (gcc version 9.2.0 (GCC)) #1 SMP PREEMPT Sat May 30 14:53:48 UTC 2020 [ 0.000000] Machine model: Freescale i.MX8QXP MEK [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] efi: UEFI not found. [ 0.000000] Reserved memory: created CMA memory pool at 0x0000000096000000, size 960 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x0000000090000000, size 0 MiB [ 0.000000] OF: reserved mem: initialized node vdev0vring0@90000000, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x0000000090008000, size 0 MiB [ 0.000000] OF: reserved mem: initialized node vdev0vring1@90008000, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x0000000090010000, size 0 MiB [ 0.000000] OF: reserved mem: initialized node vdev1vring0@90010000, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x0000000090018000, size 0 MiB [ 0.000000] OF: reserved mem: initialized node vdev1vring1@90018000, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x0000000090400000, size 1 MiB [ 0.000000] OF: reserved mem: initialized node vdevbuffer, compatible id shared-dma-pool [ 0.000000] earlycon: lpuart32 at MMIO 0x000000005a060000 (options '') [ 0.000000] printk: bootconsole [lpuart32] enabled [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000080200000-0x00000008bfffffff] [ 0.000000] NUMA: NODE_DATA [mem 0x8bf9f8500-0x8bf9f9fff] [ 0.000000] Zone ranges: [ 0.000000] DMA32 [mem 0x0000000080200000-0x00000000ffffffff] [ 0.000000] Normal [mem 0x0000000100000000-0x00000008bfffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000080200000-0x0000000083ffffff] [ 0.000000] node 0: [mem 0x0000000086200000-0x0000000087ffffff] [ 0.000000] node 0: [mem 0x0000000090020000-0x00000000901fffff] [ 0.000000] node 0: [mem 0x0000000090500000-0x0000000091ffffff] [ 0.000000] node 0: [mem 0x0000000094c00000-0x00000000ffffffff] [ 0.000000] node 0: [mem 0x0000000880000000-0x00000008bfffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000080200000-0x00000008bfffffff] [ 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: MIGRATE_INFO_TYPE not supported. [ 0.000000] psci: SMC Calling Convention v1.1 [ 0.000000] percpu: Embedded 24 pages/cpu s58904 r8192 d31208 u98304 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] Speculative Store Bypass Disable mitigation not required [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 720940 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: console=ttyLP0,115200 earlycon root=/dev/mmcblk0p2 rootwait rw [ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] software IO TLB: mapped [mem 0xfbfff000-0xfffff000] (64MB) [ 0.000000] Memory: 1790216K/2929536K available (16444K kernel code, 1444K rwdata, 6472K rodata, 2944K init, 1017K bss, 156280K reserved, 983040K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4. [ 0.000000] 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: 512 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] GICv3: Distributor has no Range Selector support [ 0.000000] GICv3: 16 PPIs implemented [ 0.000000] GICv3: no VLPI support, no direct LPI support [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000051b00000 [ 0.000000] random: get_random_bytes called from start_kernel+0x2b8/0x44c with crng_init=0 [ 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.000005] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns [ 0.008872] Console: colour dummy device 80x25 [ 0.013060] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000) [ 0.023230] pid_max: default: 32768 minimum: 301 [ 0.027918] LSM: Security Framework initializing [ 0.032505] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 0.039834] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 0.071738] ASID allocator initialised with 32768 entries [ 0.084833] rcu: Hierarchical SRCU implementation. [ 0.099670] EFI services will not be available. [ 0.111906] smp: Bringing up secondary CPUs ... [ 0.148534] Detected VIPT I-cache on CPU1 [ 0.148565] GICv3: CPU1: found redistributor 1 region 0:0x0000000051b20000 [ 0.148605] CPU1: Booted secondary processor 0x0000000001 [0x410fd042] [ 0.180577] Detected VIPT I-cache on CPU2 [ 0.180599] GICv3: CPU2: found redistributor 2 region 0:0x0000000051b40000 [ 0.180623] CPU2: Booted secondary processor 0x0000000002 [0x410fd042] [ 0.212640] Detected VIPT I-cache on CPU3 [ 0.212660] GICv3: CPU3: found redistributor 3 region 0:0x0000000051b60000 [ 0.212682] CPU3: Booted secondary processor 0x0000000003 [0x410fd042] [ 0.212753] smp: Brought up 1 node, 4 CPUs [ 0.268647] SMP: Total of 4 processors activated. [ 0.273335] CPU features: detected: 32-bit EL0 Support [ 0.278474] CPU features: detected: CRC32 instructions [ 0.290675] CPU: All CPU(s) started at EL2 [ 0.294472] alternatives: patching kernel code [ 0.300146] devtmpfs: initialized [ 0.319080] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.328506] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.367350] pinctrl core: initialized pinctrl subsystem [ 0.373390] DMI not present or invalid. [ 0.377222] NET: Registered protocol family 16 [ 0.389977] DMA: preallocated 256 KiB pool for atomic allocations [ 0.395772] audit: initializing netlink subsys (disabled) [ 0.401409] audit: type=2000 audit(0.344:1): state=initialized audit_enabled=0 res=1 [ 0.408886] cpuidle: using governor menu [ 0.413831] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.422292] Serial: AMBA PL011 UART driver [ 0.426131] imx mu driver is registered. [ 0.429972] imx rpmsg driver is registered. [ 0.496753] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 0.503138] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages [ 0.509814] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 0.516505] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages [ 0.525270] cryptd: max_cpu_qlen set to 1000 [ 0.537123] ACPI: Interpreter disabled. [ 0.543164] iommu: Default domain type: Translated [ 0.547922] vgaarb: loaded [ 0.550772] SCSI subsystem initialized [ 0.554688] usbcore: registered new interface driver usbfs [ 0.559885] usbcore: registered new interface driver hub [ 0.565199] usbcore: registered new device driver usb [ 0.572898] mc: Linux media interface: v0.10 [ 0.576885] videodev: Linux video capture interface: v2.00 [ 0.582395] pps_core: LinuxPPS API ver. 1 registered [ 0.587257] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 0.596389] PTP clock support registered [ 0.600743] EDAC MC: Ver: 3.0.0 [ 0.605347] No BMan portals available! [ 0.609150] QMan: Allocated lookup table at (____ptrval____), entry count 65537 [ 0.616839] No QMan portals available! [ 0.621296] No USDPAA memory, no 'fsl,usdpaa-mem' in device-tree [ 0.628185] FPGA manager framework [ 0.631355] Advanced Linux Sound Architecture Driver Initialized. [ 0.637828] Bluetooth: Core ver 2.22 [ 0.641084] NET: Registered protocol family 31 [ 0.645497] Bluetooth: HCI device and connection manager initialized [ 0.651843] Bluetooth: HCI socket layer initialized [ 0.656705] Bluetooth: L2CAP socket layer initialized [ 0.661752] Bluetooth: SCO socket layer initialized [ 0.667999] imx-scu scu: NXP i.MX SCU Initialized [ 0.678174] random: fast init done [ 0.719262] imx8qxp-pinctrl scu:pinctrl: Invalid fsl,pins or pins property in node /scu/pinctrl/wifi_initgrp [ 0.728777] imx8qxp-pinctrl scu:pinctrl: initialized IMX pinctrl driver [ 0.737610] clocksource: Switched to clocksource arch_sys_counter [ 0.743591] VFS: Disk quotas dquot_6.6.0 [ 0.747718] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.755268] pnp: PnP ACPI: disabled [ 0.789569] thermal_sys: Registered thermal governor 'step_wise' [ 0.789575] thermal_sys: Registered thermal governor 'power_allocator' [ 0.795834] NET: Registered protocol family 2 [ 0.806800] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear) [ 0.815053] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 0.823130] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear) [ 0.830716] TCP: Hash tables configured (established 32768 bind 32768) [ 0.837043] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear) [ 0.843679] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear) [ 0.850934] NET: Registered protocol family 1 [ 0.855525] RPC: Registered named UNIX socket transport module. [ 0.861123] RPC: Registered udp transport module. [ 0.865802] RPC: Registered tcp transport module. [ 0.870495] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.877402] PCI: CLS 0 bytes, default 64 [ 0.881870] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available [ 0.890601] kvm [1]: IPA Size Limit: 40bits [ 0.895219] kvm [1]: GICv3: no GICV resource entry [ 0.899681] kvm [1]: disabling GICv2 emulation [ 0.904126] kvm [1]: GIC system register CPU interface enabled [ 0.910005] kvm [1]: vgic interrupt IRQ1 [ 0.913966] kvm [1]: Hyp mode initialized successfully [ 0.926125] Initialise system trusted keyrings [ 0.930390] workingset: timestamp_bits=44 max_order=20 bucket_order=0 [ 0.944394] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.950728] NFS: Registering the id_resolver key type [ 0.955483] Key type id_resolver registered [ 0.959614] Key type id_legacy registered [ 0.963616] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.970316] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.976857] 9p: Installing v9fs 9p2000 file system support [ 0.999298] Key type asymmetric registered [ 1.003064] Asymmetric key parser 'x509' registered [ 1.007978] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244) [ 1.015310] io scheduler mq-deadline registered [ 1.019824] io scheduler kyber registered [ 1.046186] imx6q-pcie 5f010000.pcie: couldn't get pcie-phy [ 1.050524] pwm-backlight lvds_backlight@0: lvds_backlight@0 supply power not found, using dummy regulator [ 1.061291] pwm-backlight lvds_backlight@1: lvds_backlight@1 supply power not found, using dummy regulator [ 1.072160] EINJ: ACPI disabled. [ 1.161746] mxs-dma 5b810000.dma-apbh: initialized [ 1.169968] Bus freq driver module loaded [ 1.183629] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.195746] 5a060000.serial: ttyLP0 at MMIO 0x5a060010 (irq = 58, base_baud = 5000000) is a FSL_LPUAR[ 1.204922] printk: console [ttyLP0] enabled [ 1.204922] printk: console [ttyLP0] enabled [ 1.213343] printk: bootconsole [lpuart32] disabled [ 1.213343] printk: bootconsole [lpuart32] disabled [ 1.223483] fsl-lpuart 5a060000.serial: DMA tx channel request failed, operating without tx DMA [ 1.232207] fsl-lpuart 5a060000.serial: DMA rx channel request failed, operating without rx DMA [ 1.241455] 5a070000.serial: ttyLP1 at MMIO 0x5a070010 (irq = 59, base_baud = 5000000) is a FSL_LPUART [ 1.251803] 5a080000.serial: ttyLP2 at MMIO 0x5a080010 (irq = 60, base_baud = 5000000) is a FSL_LPUART [ 1.262129] 5a090000.serial: ttyLP3 at MMIO 0x5a090010 (irq = 61, base_baud = 5000000) is a FSL_LPUART [ 1.340037] loop: module loaded [ 1.349120] imx ahci driver is registered. [ 1.364158] spi-nor spi0.0: mt35xu512aba (65536 Kbytes) [ 1.377753] libphy: Fixed MDIO Bus: probed [ 1.382873] tun: Universal TUN/TAP device driver, 1.6 [ 1.390820] thunder_xcv, ver 1.0 [ 1.394107] thunder_bgx, ver 1.0 [ 1.397372] nicpf, ver 1.0 [ 1.402370] pps pps0: new PPS source ptp0 [ 1.413037] libphy: fec_enet_mii_bus: probed [ 1.418871] fec 5b040000.ethernet eth0: registered PHC device 0 [ 1.427186] Freescale FM module, FMD API version 21.1.0 [ 1.433462] Freescale FM Ports module [ 1.437182] fsl_mac: fsl_mac: FSL FMan MAC API based driver [ 1.443474] fsl_dpa: FSL DPAA Ethernet driver [ 1.448292] fsl_advanced: FSL DPAA Advanced drivers: [ 1.453267] fsl_proxy: FSL DPAA Proxy initialization driver [ 1.459276] fsl_oh: FSL FMan Offline Parsing port driver [ 1.467583] hclge is initializing [ 1.470921] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [ 1.478153] hns3: Copyright (c) 2017 Huawei Corporation. [ 1.483552] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [ 1.490618] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 1.496410] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [ 1.502259] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 1.508248] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k [ 1.515226] igb: Copyright (c) 2007-2014 Intel Corporation. [ 1.520848] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k [ 1.528689] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 1.535181] sky2: driver version 1.30 [ 1.541882] VFIO - User Level meta-driver version: 0.3 [ 1.554342] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.560898] ehci-pci: EHCI PCI platform driver [ 1.565427] ehci-platform: EHCI generic platform driver [ 1.571434] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.577658] ohci-pci: OHCI PCI platform driver [ 1.582178] ohci-platform: OHCI generic platform driver [ 1.589778] usbcore: registered new interface driver usb-storage [ 1.595898] usbcore: registered new interface driver usbserial_generic [ 1.602463] usbserial: USB Serial support registered for generic [ 1.608507] usbcore: registered new interface driver ftdi_sio [ 1.614338] usbserial: USB Serial support registered for FTDI USB Serial Device [ 1.621725] usbcore: registered new interface driver usb_serial_simple [ 1.628290] usbserial: USB Serial support registered for carelink [ 1.634409] usbserial: USB Serial support registered for zio [ 1.640100] usbserial: USB Serial support registered for funsoft [ 1.646137] usbserial: USB Serial support registered for flashloader [ 1.652525] usbserial: USB Serial support registered for google [ 1.658475] usbserial: USB Serial support registered for libtransistor [ 1.665034] usbserial: USB Serial support registered for vivopay [ 1.671070] usbserial: USB Serial support registered for moto_modem [ 1.677371] usbserial: USB Serial support registered for motorola_tetra [ 1.684015] usbserial: USB Serial support registered for novatel_gps [ 1.690399] usbserial: USB Serial support registered for hp4x [ 1.696177] usbserial: USB Serial support registered for suunto [ 1.702131] usbserial: USB Serial support registered for siemens_mpi [ 1.720209] input: sc-powerkey as /devices/platform/sc-powerkey/input/input0 [ 1.732194] imx-sc-rtc scu:rtc: registered as rtc0 [ 1.738335] i2c /dev entries driver [ 1.751798] Bluetooth: HCI UART driver ver 2.3 [ 1.756286] Bluetooth: HCI UART protocol H4 registered [ 1.761449] Bluetooth: HCI UART protocol BCSP registered [ 1.766797] Bluetooth: HCI UART protocol LL registered [ 1.771952] Bluetooth: HCI UART protocol ATH3K registered [ 1.777382] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 1.784026] Bluetooth: HCI UART protocol Broadcom registered [ 1.789732] Bluetooth: HCI UART protocol QCA registered [ 1.802167] sdhci: Secure Digital Host Controller Interface driver [ 1.808412] sdhci: Copyright(c) Pierre Ossman [ 1.813512] Synopsys Designware Multimedia Card Interface Driver [ 1.821872] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.829915] mmc0: CQHCI version 5.10 [ 1.865060] mmc0: SDHCI controller on 5b010000.mmc [5b010000.mmc] using ADMA [ 1.873271] mmc1: CQHCI version 5.10 [ 1.883133] ledtrig-cpu: registered to indicate activity on CPUs [ 1.892104] caam 31400000.crypto: device ID = 0x0a16040000000100 (Era 9) [ 1.898859] caam 31400000.crypto: job rings = 2, qi = 0 [ 1.931611] caam algorithms registered in /proc/crypto [ 1.940053] caam 31400000.crypto: caam pkc algorithms registered in /proc/crypto [ 1.948347] caam_jr 31430000.jr: registering rng-caam [ 1.960345] usbcore: registered new interface driver usbhid [ 1.965977] usbhid: USB HID core driver [ 1.970540] mxc-md bus@58000000:camera: deferring cap_device device registration [ 1.981711] mxc-isi 58100000.isi: mxc_isi.0 registered successfully [ 1.989159] mxc-isi 58110000.isi: mxc_isi.1 registered successfully [ 1.996587] mxc-isi 58120000.isi: mxc_isi.2 registered successfully [ 2.004015] mxc-isi 58130000.isi: mxc_isi.3 registered successfully [ 2.011437] mxc-isi 58140000.isi: mxc_isi.4 registered successfully [ 2.037641] mxc-mipi-csi2 58227000.csi: lanes: 4, name: mxc-mipi-csi2.0 [ 2.044296] mmc0: new HS400 MMC card at address 0001 [ 2.046334] mxc-parallel-csi 58261000.pcsi: mxc_parallel_csi_probe probe successfully [ 2.049961] mmcblk0: mmc0:0001 R1J57L 29.1 GiB [ 2.059618] No fsl,qman node [ 2.061973] mmcblk0boot0: mmc0:0001 R1J57L partition 1 8.00 MiB [ 2.064562] Freescale USDPAA process driver [ 2.070727] mmcblk0boot1: mmc0:0001 R1J57L partition 2 8.00 MiB [ 2.074668] fsl-usdpaa: no region found [ 2.074671] Freescale USDPAA process IRQ driver [ 2.078387] imx-rproc imx8x_cm4@0: failed to find syscon [ 2.080798] mmcblk0rpmb: mmc0:0001 R1J57L partition 3 4.00 MiB, chardev (237:0) [ 2.084581] remoteproc remoteproc0: releasing imx-rproc [ 2.107070] mmcblk0: p1 p2 [ 2.121685] Galcore version 6.4.0.234062 [ 2.328553] imx-cs42888 sound-cs42888: failed to find codec platform device [ 2.336238] imx-wm8960 sound-wm8960: failed to find codec platform device [ 2.345067] fsl-audmix 59840000.amix: DAI FE name:HiFi-AUDMIX-FE-ai@59820000 [ 2.352207] fsl-audmix 59840000.amix: DAI FE name:HiFi-AUDMIX-FE-ai@59830000 [ 2.359511] debugfs: Directory '59820000.sai' with parent 'imx-audmix' already present! [ 2.367615] debugfs: Directory '59830000.sai' with parent 'imx-audmix' already present! [ 2.375888] imx-audmix imx-audmix.0: snd-soc-dummy-dai <-> 59820000.sai mapping ok [ 2.383604] imx-audmix imx-audmix.0: snd-soc-dummy-dai <-> 59830000.sai mapping ok [ 2.391266] imx-audmix imx-audmix.0: snd-soc-dummy-dai <-> audmix-0 mapping ok [ 2.398556] imx-audmix imx-audmix.0: snd-soc-dummy-dai <-> audmix-1 mapping ok [ 2.405834] imx-audmix imx-audmix.0: ASoC: no DMI vendor name! [ 2.417722] pktgen: Packet Generator for packet performance testing. Version: 2.75 [ 2.425861] NET: Registered protocol family 26 [ 2.431124] NET: Registered protocol family 10 [ 2.436421] Segment Routing with IPv6 [ 2.440178] NET: Registered protocol family 17 [ 2.444764] Bluetooth: RFCOMM TTY layer initialized [ 2.449668] Bluetooth: RFCOMM socket layer initialized [ 2.454920] Bluetooth: RFCOMM ver 1.11 [ 2.458696] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 2.464024] Bluetooth: BNEP filters: protocol multicast [ 2.469266] Bluetooth: BNEP socket layer initialized [ 2.474237] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 2.480190] Bluetooth: HIDP socket layer initialized [ 2.485208] 8021q: 802.1Q VLAN Support v1.8 [ 2.489417] lib80211: common routines for IEEE802.11 drivers [ 2.495236] 9pnet: Installing 9P2000 support [ 2.499581] tsn generic netlink module v1 init... [ 2.504397] Key type dns_resolver registered [ 2.509195] registered taskstats version 1 [ 2.513312] Loading compiled-in X.509 certificates [ 2.545141] mxs_phy 5b100000.usbphy: 5b100000.usbphy supply phy-3p0 not found, using dummy regulator [ 2.572502] usb_phy_generic bus@5b000000:usb3-phy: bus@5b000000:usb3-phy supply vcc not found, using dummy regulator [ 2.584056] gpio-42 (scl): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 2.592974] imx-lpi2c 37230000.i2c: using scl,sda for recovery [ 2.606398] ov5640 16-003c: 16-003c supply DOVDD not found, using dummy regulator [ 2.613986] ov5640 16-003c: 16-003c supply AVDD not found, using dummy regulator [ 2.621447] ov5640 16-003c: 16-003c supply DVDD not found, using dummy regulator [ 2.676333] ov5640 16-003c: ov5640_read_reg: error: reg=300a [ 2.682037] ov5640 16-003c: ov5640_check_chip_id: failed to read chip identifier [ 2.690503] ov5640: probe of 16-003c failed with error -5 [ 2.696007] i2c i2c-16: LPI2C adapter registered [ 2.703029] max732x 18-0068: failed reading [ 2.707275] max732x: probe of 18-0068 failed with error -5 [ 2.712923] i2c i2c-17: Added multiplexed i2c bus 18 [ 2.718142] i2c i2c-17: Added multiplexed i2c bus 19 [ 2.724431] input: fxos8700 as /devices/platform/bus@5a000000/5a810000.i2c/i2c-17/i2c-20/20-001e/input/input1 [ 2.736249] fxos8700 device driver probe successfully [ 2.737061] input: fxas2100x as /devices/platform/bus@5a000000/5a810000.i2c/i2c-17/i2c-20/20-0021/input/input2 [ 2.752880] fxas2100x 20-0021: fxas2100x device driver probe successfully [ 2.760300] read mpl3115 chip id 0xc4 [ 2.764114] input: mpl3115 as /devices/virtual/input/input3 [ 2.770405] mpl3115 device driver probe successfully [ 2.770467] i2c i2c-17: Added multiplexed i2c bus 20 [ 2.783443] isl29023 21-0044: 21-0044 supply vdd not found, using dummy regulator [ 2.797243] input: isl29023 light sensor as /devices/virtual/input/input4 [ 2.804457] isl29023 21-0044: driver version 1.0 enabled [ 2.809874] i2c i2c-17: Added multiplexed i2c bus 21 [ 2.814866] pca954x 17-0071: registered 4 multiplexed busses for I2C switch pca9646 [ 2.823506] OF: graph: no port node found in /bus@5a000000/i2c@5a810000/tcpc@50 [ 2.831708] i2c i2c-17: LPI2C adapter registered [ 2.849776] max9286_mipi 22-006a: max9286_read_reg:read reg error: reg=1e [ 2.856619] max9286 is not found, chip id reg 0x1e = 0x(ffffffff) [ 2.862849] i2c i2c-22: LPI2C adapter registered [ 2.868014] imx-lpi2c 56226000.i2c: can't get irq number [ 2.875075] imx-lpi2c 56246000.i2c: can't get irq number [ 2.884591] pwm-backlight lvds_backlight@0: lvds_backlight@0 supply power not found, using dummy regulator [ 2.884720] imx6q-pcie 5f010000.pcie: couldn't get pcie-phy [ 2.895743] pwm-backlight lvds_backlight@1: lvds_backlight@1 supply power not found, using dummy regulator [ 2.901055] imx6q-pcie 5f010000.pcie: 5f010000.pcie supply epdev_on not found, using dummy regulator [ 2.916663] dpu-core 56180000.dpu: driver probed [ 2.918941] imx6q-pcie 5f010000.pcie: No cache used with register defaults set! [ 2.925286] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.931993] imx6q-pcie 5f010000.pcie: host bridge /bus@5f000000/pcie@0x5f010000 ranges: [ 2.937320] [drm] No driver support for vblank timestamp query. [ 2.937404] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops) [ 2.945387] imx6q-pcie 5f010000.pcie: IO 0x7ff80000..0x7ff8ffff -> 0x00000000 [ 2.951663] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops) [ 2.959401] imx6q-pcie 5f010000.pcie: MEM 0x70000000..0x7fefffff -> 0x70000000 [ 2.967149] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops) [ 2.989036] imx-drm display-subsystem: failed to bind bus@56220000:ldb@562210e0 (ops imx8qxp_ldb_ops): -517 [ 2.999041] imx-drm display-subsystem: master bind failed: -517 [ 3.013849] mmc1: CQHCI version 5.10 [ 3.017487] sdhci-esdhc-imx 5b020000.mmc: Got CD GPIO [ 3.022589] sdhci-esdhc-imx 5b020000.mmc: Got WP GPIO [ 3.059322] mmc1: SDHCI controller on 5b020000.mmc [5b020000.mmc] using ADMA [ 3.073188] mx8-img-md: Registered mxc_isi.0.capture as /dev/video0 [ 3.079815] mx8-img-md: Registered mxc_isi.1.capture as /dev/video1 [ 3.081644] imx6q-pcie 5f010000.pcie: PCIe PLL locked after 0 us. [ 3.086383] mx8-img-md: Registered mxc_isi.2.capture as /dev/video2 [ 3.098768] mx8-img-md: Registered mxc_isi.3.capture as /dev/video3 [ 3.105346] mx8-img-md: Registered mxc_isi.4.capture as /dev/video4 [ 3.112019] unregister ISI channel: mxc_isi.0 [ 3.116498] unregister ISI channel: mxc_isi.1 [ 3.120967] unregister ISI channel: mxc_isi.2 [ 3.125434] unregister ISI channel: mxc_isi.3 [ 3.129969] unregister ISI channel: mxc_isi.4 [ 3.135397] imx-rproc imx8x_cm4@0: failed to find syscon [ 3.140901] imx-rproc imx8x_cm4@0: mbox_request_channel_byname() could not locate channel named "txdb" [ 3.150230] imx-rproc imx8x_cm4@0: No txdb, ret 0 [ 3.155569] remoteproc remoteproc0: imx-rproc is available [ 3.162433] imx-cs42888 sound-cs42888: failed to find codec platform device [ 3.171030] debugfs: Directory '59050000.sai' with parent 'wm8960-audio' already present! [ 3.179365] imx-wm8960 sound-wm8960: wm8960-hifi <-> 59050000.sai mapping ok [ 3.186482] imx-wm8960 sound-wm8960: ASoC: no DMI vendor name! [ 3.306581] can-stby: supplied by can-en [ 3.330531] cs42xx8 16-0048: failed to get device ID, ret = -5 [ 3.336673] cs42xx8: probe of 16-0048 failed with error -5 [ 3.343957] OF: graph: no port node found in /bus@5a000000/i2c@5a810000/tcpc@50 [ 4.085706] imx6q-pcie 5f010000.pcie: Phy link never came up [ 4.091482] imx6q-pcie 5f010000.pcie: failed to initialize host [ 4.097424] imx6q-pcie 5f010000.pcie: unable to add pcie port. [ 4.421875] it6263 23-004c: Probe failed. Remote port 'lvds-channel@0' disabled [ 4.429639] adv7511 23-003d: 23-003d supply avdd not found, using dummy regulator [ 4.437220] adv7511 23-003d: 23-003d supply dvdd not found, using dummy regulator [ 4.444778] adv7511 23-003d: 23-003d supply pvdd not found, using dummy regulator [ 4.452334] adv7511 23-003d: 23-003d supply a2vdd not found, using dummy regulator [ 4.459969] adv7511 23-003d: 23-003d supply v3p3 not found, using dummy regulator [ 4.467552] adv7511 23-003d: 23-003d supply v1p2 not found, using dummy regulator [ 5.481659] adv7511 23-003d: Probe failed. Remote port 'dsi_host@56228000' disabled [ 5.489418] i2c i2c-23: LPI2C adapter registered [ 5.551051] it6263 24-004c: Probe failed. Remote port 'lvds-channel@0' disabled [ 5.558727] adv7511 24-003d: 24-003d supply avdd not found, using dummy regulator [ 5.566303] adv7511 24-003d: 24-003d supply dvdd not found, using dummy regulator [ 5.574390] adv7511 24-003d: 24-003d supply pvdd not found, using dummy regulator [ 5.581935] adv7511 24-003d: 24-003d supply a2vdd not found, using dummy regulator [ 5.589572] adv7511 24-003d: 24-003d supply v3p3 not found, using dummy regulator [ 5.597123] adv7511 24-003d: 24-003d supply v1p2 not found, using dummy regulator [ 5.605101] adv7511 24-003d: Probe failed. Remote port 'dsi_host@56248000' disabled [ 5.612850] i2c i2c-24: LPI2C adapter registered [ 5.618726] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 5.625362] [drm] No driver support for vblank timestamp query. [ 5.631370] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops) [ 5.639653] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops) [ 5.647034] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops) [ 5.654690] imx-drm display-subsystem: bound bus@56220000:ldb@562210e0 (ops imx8qxp_ldb_ops) [ 5.663182] imx-drm display-subsystem: bound 56228000.dsi_host (ops nwl_dsi_component_ops) [ 5.671830] imx-drm display-subsystem: bound bus@56220000:ldb@562410e0 (ops imx8qxp_ldb_ops) [ 5.680336] imx-drm display-subsystem: bound 56248000.dsi_host (ops nwl_dsi_component_ops) [ 5.689052] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 0 [ 5.706243] imx-cs42888 sound-cs42888: failed to find codec platform device [ 5.715330] imx-cs42888 sound-cs42888: failed to find codec platform device [ 5.725333] debugfs: Directory 'lvds1' with parent 'pm_genpd' already present! [ 5.733074] debugfs: Directory 'mipi1-i2c1' with parent 'pm_genpd' already present! [ 5.740759] debugfs: Directory 'mipi1-i2c0' with parent 'pm_genpd' already present! [ 5.748451] debugfs: Directory 'mipi1-pwm0' with parent 'pm_genpd' already present! [ 5.756127] debugfs: Directory 'mipi1' with parent 'pm_genpd' already present! [ 5.771793] imx-sc-rtc scu:rtc: setting system clock to 2022-08-05T07:41:59 UTC (1659685319) [ 5.782447] isi-m2m 58100000.isi:m2m_device: Register m2m success for ISI.0 [ 5.790803] imx-cs42888 sound-cs42888: failed to find codec platform device [ 5.798014] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 5.807018] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 5.813673] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 5.822311] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db [ 5.840383] ALSA device list: [ 5.843373] #0: imx-audmix [ 5.846273] #1: wm8960-audio [ 5.856806] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 5.865055] VFS: Mounted root (ext4 filesystem) on device 179:2. [ 5.871534] devtmpfs: mounted [ 5.875498] Freeing unused kernel memory: 2944K [ 5.880153] Run /sbin/init as init process [ 5.988919] systemd[1]: systemd 243.2+ running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN -PCRE2 default-hierarchy=hybrid) [ 6.011170] systemd[1]: Detected architecture arm64. Welcome to NXP i.MX Release Distro 5.4-zeus (zeus)! [ 6.066612] systemd[1]: Set hostname to . [ 6.076339] random: systemd: uninitialized urandom read (16 bytes read) [ 6.083100] systemd[1]: Initializing machine ID from random generator. [ 6.310989] systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. [ 6.341216] systemd[1]: /lib/systemd/system/syslogd.service:8: PIDFile= references a path below legacy directory /var/run/, updating /var/run/syslogd.pid → /run/syslogd.pid; please update the unit file accordingly. [ 6.375021] systemd[1]: /lib/systemd/system/rpcbind.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/rpcbind.sock → /run/rpcbind.sock; please update the unit file accordingly. [ 6.399483] systemd[1]: /lib/systemd/system/klogd.service:8: PIDFile= references a path below legacy directory /var/run/, updating /var/run/klogd.pid → /run/klogd.pid; please update the unit file accordingly. [ 6.540814] random: systemd: uninitialized urandom read (16 bytes read) [ 6.547713] systemd[1]: system-getty.slice: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling. [ 6.560124] systemd[1]: (This warning is only shown for the first unit using IP firewalling.) [ OK ] Created slice system-getty.slice. [ 6.581777] random: systemd: uninitialized urandom read (16 bytes read) [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Created slice User and Session Slice. [ OK ] Started Dispatch Password …ts to Console Directory Watch. [ OK ] Started Forward Password R…uests to Wall Directory Watch. [ OK ] Reached target Host and Network Name Lookups. [ OK ] Reached target Paths. [ OK ] Reached target Remote File Systems. [ OK ] Reached target Slices. [ OK ] Reached target Swap. [ OK ] Listening on Syslog Socket. [ OK ] Listening on initctl Compatibility Named Pipe. [ OK ] Listening on Journal Audit Socket. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on Journal Socket. [ OK ] Listening on Network Service Netlink Socket. [ OK ] Listening on udev Control Socket. [ OK ] Listening on udev Kernel Socket. Mounting Huge Pages File System... Mounting POSIX Message Queue File System... Mounting Kernel Debug File System... Mounting Temporary Directory (/tmp)... Starting Create list of st…odes for the current kernel... Starting Journal Service... Mounting Kernel Configuration File System... Starting Remount Root and Kernel File Systems... Starting Apply Kernel Variables... [ 6.954566] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Starting udev Coldplug all Devices... Starting Setup Virtual Console... [ OK ] Mounted Huge Pages File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Kernel Debug File System. [ OK ] Started Journal Service. [ OK ] Mounted Temporary Directory (/tmp). [ OK ] Started Create list of sta… nodes for the current kernel. [ OK ] Mounted Kernel Configuration File System. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Apply Kernel Variables. [ OK ] Started Setup Virtual Console. Starting Flush Journal to Persistent Storage... [ 7.170503] systemd-journald[460]: Received client request to flush runtime journal. Starting Create System Users... [ OK ] Started Flush Journal to Persistent Storage. [ OK ] Started Create System Users. Starting Create Static Device Nodes in /dev... [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Reached target Local File Systems (Pre). Mounting /var/volatile... Starting udev Kernel Device Manager... [ OK ] Mounted /var/volatile. Starting Load/Save Random Seed... [ OK ] Reached target Local File Systems. Starting Rebuild Dynamic Linker Cache... Starting Create Volatile Files and Directories... [ OK ] Started udev Kernel Device Manager. [ OK ] Started Create Volatile Files and Directories. Starting Run pending postinsts... Starting Rebuild Journal Catalog... Starting Network Time Synchronization... Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Started Rebuild Journal Catalog. [ OK ] Started Network Time Synchronization. [ OK ] Started udev Coldplug all Devices. [ OK ] Reached target System Time Set. [ OK ] Reached target System Time Synchronized. Starting Start Psplash Boot Screen... [ OK ] Started Start Psplash Boot Screen. [ OK ] Started Run pending postinsts. [ 8.178399] [VPU Encoder] enable mu for core[0] [ 8.191465] [VPU Encoder] vpu encoder core[0] firmware version is 1.2.7 [ 8.267610] mxc-jpeg 58400000.jpegdec: decoder device registered as /dev/video1 (81,3) [ 8.279693] imx-cs42888 sound-cs42888: failed to find codec platform device [ OK ] Started Rebuild Dynamic Linker Cache. Starting Update is Completed... [ OK ] Started Update is Completed. [ 8.337660] CAN device driver interface [ 8.337936] mxc-jpeg 58450000.jpegenc: encoder device registered as /dev/video2 (81,4) [ OK ] Reached target System Initialization. [ 8.351349] imx-cs42888 sound-cs42888: failed to find codec platform device [ OK ] Started Daily apt download activities. [ 8.372537] imx-cs42888 sound-cs42888: failed to find codec platform device [ OK ] Started Daily rotation of log files. [ OK ] Started Daily Cleanup of Temporary Directories. [ 8.403290] imx-cs42888 sound-cs42888: failed to find codec platform device [ OK ] Reached target Timers. [ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Listening on dropbear.socket. [ OK ] Listening on RPCbind Server Activation Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. [ OK ] Started Job spooling tools. Starting Console System Startup Logging... [ OK ] Started Periodic Command Scheduler. [ OK ] Started D-Bus System Message Bus. [ OK ] Started Configuration for i.MX GPU (Former rc_gpu.S). Starting Packet Filtering Framework... Starting Network Time Service (one-shot ntpdate mode)... Starting Telephony service... [ OK ] Started Updates psplash to basic. [ OK ] Started User Space Regulatory Firmware Loading. Starting RPC Bind Service... [ OK ] Started User Space SDMA Firmware Loading. Starting System Logging Service... Starting Login Service... [ OK ] Started TEE Supplicant. [ OK ] Started Console System Startup Logging. [ OK ] Started Packet Filtering Framework. [ OK ] Started Network Time Service (one-shot ntpdate mode). [ OK ] Started RPC Bind Service. [ OK ] Started System Logging Service. [ OK ] Started Telephony service. [ OK ] Started Login Service. [ OK ] Created slice system-systemd\x2dbacklight.slice. [ OK ] Created slice system-weston.slice. [ OK ] Reached target Network (Pre). Starting Save/Restore Sound Card State... Starting Connection service... Starting Kernel Logging Service... Starting Load/Save Screen … backlight:lvds_backlight@0... Starting Load/Save Screen … backlight:lvds_backlight@1... Starting Network Service... [ OK ] Started Save/Restore Sound Card State. [ OK ] Started Load/Save Screen B…of backlight:lvds_backlight@0. [ OK ] Started Load/Save Screen B…of backlight:lvds_backlight@1. [ OK ] Started Connection service. [ OK [ 9.585955] Atheros 8031 ethernet 5b040000.ethernet-1:00: attached PHY driver [Atheros 8031 ethernet] (mii_bus:phy_addr=5b040000.ethernet-1:00, irq=POLL) ] Started Network Service. [ OK ] Created slice system-systemd\x2dfsck.slice. [ OK ] Reached target Sound Card. Starting Avahi mDNS/DNS-SD Stack... Starting Hostname Service... Starting WPA supplicant... [ OK ] Found device /dev/mmcblk0p1. [ OK ] Started Avahi mDNS/DNS-SD Stack. [ OK ] Started WPA supplicant. [ OK ] Reached target Network. [ OK ] Started NFS status monitor for NFSv2/3 locking.. [ OK ] Started Update psplash to network. Starting Terminate Psplash Boot Screen... Starting /etc/rc.local Compatibility... Starting File System Check on /dev/mmcblk0p1... Starting Permit User Sessions... [ OK ] Started Kernel Logging Service. [FAILED] Failed to start Terminate Psplash Boot Screen. See 'systemctl status psplash-quit.service' for details. [ OK ] Started /etc/rc.local Compatibility. [ OK ] Started Permit User Sessions. [ OK ] Started Hostname Service. [ OK ] Started Getty on tty1. [ OK ] Started Serial Getty on ttyLP0. [ OK ] Reached target Login Prompts. [ OK ] Reached target Multi-User System. Starting Update UTMP about System Runlevel Changes... Starting Weston Wayland Compositor (on tty7)... [ OK ] Started Weston Wayland Compositor (on tty7). [ OK ] Started File System Check on /dev/mmcblk0p1. Mounting /run/media/mmcblk0p1... [ OK ] Mounted /run/media/mmcblk0p1. [ OK ] Started Update UTMP about System Runlevel Changes. [ OK ] Created slice User Slice of UID 0. Starting User Runtime Directory /run/user/0... [ OK ] Started User Runtime Directory /run/user/0. Starting User Manager for UID 0... [ 10.312617] audit: type=1006 audit(1659685324.036:2): pid=751 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=1 res=1 [ OK ] Started User Manager for UID 0. [ OK ] Started Session c1 of user root. [ 12.017655] random: crng init done [ 12.021074] random: 7 urandom warning(s) missed due to ratelimiting [ OK ] Started Load/Save Random Seed. NXP i.MX Release Distro 5.4-zeus imx8qxpmek ttyLP0 imx8qxpmek login: root Last login: Fri Aug 5 07:42:03 UTC 2022 on tty7 root@imx8qxpmek:~# root@imx8qxpmek:~# root@imx8qxpmek:~# root@imx8qxpmek:~# root@imx8qxpmek:~# root@imx8qxpmek:~# root@imx8qxpmek:~# [ 35.893655] SD1_SPWR: disabling [ 35.896813] can-en: disabling [ 35.899825] can-stby: disabling [ 35.903011] usb_otg1_vbus: disabling ^C root@imx8qxpmek:~# The LVDS-TO-HDMI bridge green LED turns ON but nothing is happening on the HDMI monitor. Re: i.MX 8QuadXPlus - MEK Default configuration and files "out-of-the-box" Hello, thanks for replying. Android Automotive OS: automotive-12.0.0_2.1.0_image_8qmek_car2 If I perform the boot procedure without setting: setenv bootargs console=ttyLP0,115200 earlycon init=/init androidboot.fbTileSupport=enable cma=928M@0x960M-0xfc0M androidboot.primary_display=imx-drm firmware_class.path=/vendor/firmware loop.max_part=7 transparent_hugepage=never moal.mod_para=wifi_mod_para.conf androidboot.lcd_density=240 bootconfig The kernel starts and the LVDS-TO-HDMI bridge is turning the led green (but nothing is being display on the HDMI monitor connected to the bridge). After the kernel finishes the initialization I can navigate through the files/folders on the COMM (serial port)... but without video. If I setenv as ANDROID_QUICK_START_GUIDE I don't have video, the LVDS-TO-HDMI bridge green led doesn't turn ON and the board keeps restarting during the kernel start-up (please see attached log). I don't know what to do. I would like to have the default files and configuration as "out-of-the-box" to check if my HW is OK. Like this video: Get Started with the MCIMX8QXP-CPU | NXP Semiconductors Thank you! Re: i.MX 8QuadXPlus - MEK Default configuration and files "out-of-the-box" Hi Can you share which BSP you are facing this issue? For Android OS, please refer 9.4.1 Booting with single LVDS-to-HDMI/MIPI-DSI-to-HDMI or dual LVDS-to-HDMI displays in  https://www.nxp.com/docs/en/quick-reference-guide/ANDROID_QUICK_START_GUIDE.pdf

s32k388のマスタースレーブモードの使用に関する相談 6953956c0a213afc6de89697c3d0e88f.png ここで必要な要件は、2つのS32k388がSPI通信を使用して相互に通信することです。どちらかが主人にも奴隷にもなれるのでしょうか?例えば、チップAをホストとして使用する場合、IOMUXテーブルのI項目はMISOのホスト入力を表します。チップAをスレーブとして使用する場合、このOという項はMISOのスレーブ出力を表していますか？現在のプロジェクトで使用しているピンは固定されています。例えば、SOUT: PTA18+ GPIO_ALT_FUNC_4は MOSI で使用され、SIN: PTA20+239+ GPIO_ALT_FUNC_4は MISO で使用されます。これは、現在使用しているホストモードに基づいています。ピンを変えなくてもスレーブモードに切り替えても正常に動作しますか?CFGR0のHRDIRとCFGR1のMASTERを変更するだけでスレーブモードに切り替えるだけで十分でしょうか? Re: Consultation on using the master-slave mode of s32k388 こんにちは、 @xlele さん、 マスターモードとスレーブモードを切り替えるのにハードウェアの変更は必要ありません。 標準的な2チップSPI構成では、ピンは常に2つのデバイス間でクロスコッキングされています。 チップA SOUT → チップB SIN (MOSIライン) チップA SIN ← チップB SOUT（味噌ライン） SOUTピンは常にシリアルデータ出力であり、SINピンは常にシリアルデータ入力です。これは、デバイスがマスターとして動作しているかスレーブとして動作しているかに関係なく適用されます。そのため、チップAがスレーブモードに切り替わっても、SIN(PTA20)は新しいマスターから正しくデータを受信し、SOUT(PTA18)も正しくデータをドライブします。配線のやり直しは必要ありません。 登録変更について： CFGR1[MASTER] = 0 — これはモジュールをスレーブモードに切り替えるためのキービットです。 CFGR0[HRDIR] — このビットは、PCS[1]と多重化されているHREQ（ホスト要求）ピンの方向を制御します。SOUT/SINデータラインには影響しません。スレーブモードでは、HRDIRを1(出力)に設定し、スレーブがHREQピンを駆動してデータ送信準備ができていることをマスターに伝えます。S32K388には専用の外部LPSPI_HREQピンがないことに注意してください。ホスト要求機能はLPSPI_PCS[1]マルチプレクサ（CFGR0[HREN]で有効化）を使用します。ホストリクエスト機能(CFGR0[HREN] = 0)を使っていない場合、HRDIRはユースケースには関係なく、CFGR1[MASTER]だけで十分です。 よろしくお願いいたします。 パベル

rt1186 デバッグの問題 FRDM-IMXRT1186開発ボードでOEM_CLOSEを有効にした後、デバイスのデバッグができなくなりました。リファレンス・マニュアルでnxpdebugmboxを使ってデバッグを再有効にできると見ましたが、試してみてうまくいきませんでした。 yanyanwang_0-1788347257012.pngyanyanwang_0-1788347257012.pngyanyanwang_0-1788347257012.png 開発ボード MCX C セキュリティ（EdgeLock | セキュアブート | OTP） Re: rt1186 debug issues ご提供いただいたリンクを確認し、推奨された手順に従いましたが、依然として同じ問題が発生しています。 私は画像に署名しただけで、暗号化はしていません。OEM_CLOSEも設定しました。 nxpdebugmboxは、デバッグ機能を再度有効にするためだけに使用しています。 SECプロジェクトと関連ログを添付ファイルとしてアップロードしました。プロジェクトとログの分析を手伝って、問題の原因を特定していただけませんか? Re: rt1186 debug issues こんにちは、 @yanyanwangさん SECツールのドキュメントには、デバッグ認証のトラブルシューティングが掲載されています: https://docs.mcuxpresso.nxp.com/secure/latest/09_troubleshooting.html#debug-authentication 役立つヒントも以下に掲載されています https://docs.mcuxpresso.nxp.com/secure/latest/07_generic_workflows.html#debug-authentication-workflow もしこれで役に立たなければ、設定の詳細を教えてもらえますか?SECツールのワークスペース設定を共有してもらえますか? Re: rt1186 debug issues @yanyanwang この問題はSEC 26.03に関連しているようです。SEC 26.06へのアップデートをお勧めします。 ご迷惑をおかけして申し訳ございません。 注：SEC 26.06には、SPARSEイメージフォーマットの修正も含まれています。 Re: rt1186 debug issues はい、ありがとうございます。認証は成功しましたが、それでもデバイスのデバッグはできません。 手順は以下の通りです。 1. 認証を行うためにSECツールを使用します。 2. 認証が成功した。 3. 次に「Debug」ボタンをクリックしてデバッグを開始します。 4.しかし、デバッグは失敗に終わった。

LPC1347 USB Control Transfer Our customer SIGMATEK wants to implement USB Control Transfers on the LPC1347. This works nice as long as they have a data length of less than 64 or more than 64 Bytes. If the data length is exactly 64 Bytes (or a multiple of 64 bytes) then this does not work anymore. What do they need to do to get this working?? Regards, Peter Re: LPC1347 USB Control Transfer Hello, When USB data payloads equal an exact multiple of the endpoint's maximum packet size (64 bytes for Full-Speed), the receiver hangs because there is no short packet to signal the end of the transfer; to fix this on the LPC1347, SIGMATEK must check if the payload length is a non-zero multiple of 64 and, if so, manually send a Zero-Length Packet (ZLP) with a length of zero right after the main data block to flush the buffer, signal completion, and successfully terminate the transfer. Best Regards

NXP i.MX93 EVK 実行時の消費電力 私はNXP i.MX93 EVKを使っていて、実行時の消費電力を監視したいのですが、このデータをどうやって取得すればいいですか? 目的はAIモデルの推論中のパワーを監視することです。電力指標はどうやって監視できますか? 外部ハードウェアを使わずにソフトウェアだけで電力指標を監視するにはどうすればいいですか? Re: NXP i.MX93 EVK POWER consumption at runtime i.MX93 EVKはオンボードの電力監視回路を搭載し、ソフトウェアツールによる電力測定もサポートしています。 i.MX93 EVK については、NXP は AN13917: i.MX 93 消費電力測定を提供しています。 https://docs.nxp.com/bundle/AN13917/page/topics/power_measurement_of_the_imx_93_processor.html 本書では、オンボード測定回路とBCU（ボード制御ユーティリティ）ツールを組み合わせて消費電力を測定する方法について説明します。 よろしくお願いします。

哪家公司最擅长开发智能体人工智能？ 根据本次对比中评估的功能，JPLoft 是智能体人工智能开发的一个强有力的选择。该公司致力于定制人工智能代理、多代理系统、RAG（红黄绿）、企业集成、工作流自动化、治理、监控和人机交互控制。 然而，最好的智能体人工智能开发公司取决于您的用例、现有技术、网络安全要求、所需的集成以及您希望赋予人工智能系统的自主程度。

PTN5150AHXMP IBIS 型号 您好， 我是 Krithikka Jayamurthi，我需要 IBIS 模型文件来进行信号完整性仿真。 Re: PTN5150AHXMP IBIS model 你好， Krithikka， 目前还没有针对该设备或其系列部件创建 IBIS 仿真模型。 USB Type-C 接口上的 CC 线以相对较低的信号速度运行（USB PD BMC 信号速度为 300 kbps），这意味着它们通常不会受到高频信号完整性问题的影响，而这些问题通常是导致需要 IBIS 型号的原因。通常情况下，数据手册中的标准 I²C 电平或低速 I/O 特性（电气规格：VOL/VOH、IOL/IOH、上升/下降时间、电容）足以评估 CC 引脚上的信号质量。 如果您对信号完整性的担忧具体与 USB 数据路径（USB 2.0 D+/D−）有关，请注意 PTN5150AHXMP 本身并不路由或缓冲 USB 数据线 - 它纯粹是一个 CC 逻辑控制器。USB 数据信号完全绕过设备，直接在连接器和插座处处理。 BRs，托马斯

SC16IS740 Maximum Crystal Frequency Dear NXP Technical Support Team, We are using the SC16IS740 with a 3.3 V supply. Could you please confirm the maximum external crystal oscillator frequency that can be connected directly between XTAL1 and XTAL2? The datasheet mentions: Applies to external clock, crystal oscillator max 24 MHz. Thank you for your support. Regards, Abishek Re: SC16IS740 Maximum Crystal Frequency Hello AbishekDevan Good day! Yes, you are correct; the limit with an external crystal is 24 MHz. Have a great day and best of luck.

LPC1347 USB 控制传输 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我们的客户 SIGMATEK 希望在 LPC1347 上实现 USB 控制传输。 只要数据长度小于 64 字节或大于 64 字节，这种方法就很好用。 如果数据长度正好是 64 字节（或 64 字节的倍数），则此方法不再有效。 他们需要做些什么才能让这个功能正常运行？ 此致， Peter Re: LPC1347 USB Control Transfer 你好， 当 USB 数据有效载荷恰好等于端点最大数据包大小（全速为 64 字节）的倍数时，接收器会挂起，因为没有短数据包来表示传输结束；为了在 LPC1347 上解决此问题，SIGMATEK 必须检查有效载荷长度是否为 64 的非零倍数，如果是，则在主数据块之后立即手动发送长度为零的零长度数据包 (ZLP)，以刷新缓冲区、表示完成并成功终止传输。 此致

PTN5150AHXMP IBISモデル こんにちは、 私はKrithikka Jayamurthiです。信号整合性シミュレーションを行うためにIBISモデルファイルが必要です。 Re: PTN5150AHXMP IBIS model こんにちは、クリティッカさん。 この装置やそのファミリ部品については、IBISシミュレーションモデルは作成されていません。 USB Type-Cインターフェース上のCCラインは比較的低い信号速度(USB PD BMC信号は300 kbps)で動作するため、IBISモデルに通常求められる高周波信号の整合性問題には一般的に影響されません。データシートの標準I²Cレベルまたは低速I/O特性評価(電気仕様:VOL/VOH、IOL/IOH、昇降時間、静電容量)で、通常はCCピンの信号品質を評価するのに十分です。 もし信号の整合性に関する懸念がUSBデータパス(USB 2.0 D+/D−)に特化している場合、PTN5150AHXMP自体はUSBデータラインをルーティングやバッファリングするものではなく、純粋にCCロジックコントローラであることにご注意ください。USBデータ信号はデバイスを完全にバイパスし、コネクタとレセプタクルで直接処理されます。 BRs、トーマス

NXP i.MX93 EVK 运行时功耗 我正在使用NXP i.MX93 EVK，想要监控运行时功耗，请问如何获取这些数据？ 议程是监测人工智能模型推理过程中的功率使用情况。如何监测功率指标？ 如何仅使用软件（无需任何外部硬件）来监测功率指标？ Re: NXP i.MX93 EVK POWER consumption at runtime i.MX93 EVK 包含板载功率监控电路，并支持通过软件工具进行功率测量。 针对 i.MX93 EVK，NXP 提供了 AN13917：i.MX 93 功耗测量， https://docs.nxp.com/bundle/AN13917/page/topics/power_measurement_of_the_imx_93_processor.html 它描述了如何使用板载测量电路和 BCU（板载控制实用程序）工具来测量功耗。 谢谢！

关于使用S32K388主从模式的咨询 6953956c0a213afc6de89697c3d0e88f.png 我们这里有一个要求，即两个 S32k388 使用 SPI 通信相互通信。两者之间可以既是主人又是奴隶吗？例如，当我使用芯片 A 作为主机时，IOMUX 表中的 I 项描述了 MISO 的主机输入。如果芯片 A 用作从设备，那么这个 O 项是否描述了 MISO 的从设备输出？我们当前项目中的引脚是固定的。例如，SOUT：MOSI 上使用 PTA18+ GPIO_ALT_FUNC_4 ，SIN：MISO 上使用 PTA20+239+ GPIO_ALT_FUNC_4 。这是基于我们当前使用的主机模式。切换到从属模式而不改变引脚，它还能正常工作吗？是否只需更改 CFGR0 的 HRDIR 和 CFGR1 的 MASTER 即可切换从属模式？ Re: Consultation on using the master-slave mode of s32k388 你好@xlele ， 无需任何硬件改动即可在主模式和从模式之间切换。 在标准的双芯片SPI设置中，两个设备的引脚始终是交叉连接的： 芯片A SOUT→芯片B SIN（MOSI线） 芯片 A SIN ← 芯片 B SOUT（MISO 线） 无论设备是作为主机还是从设备运行，SOUT 引脚始终是串行数据输出，SIN 引脚始终是串行数据输入。因此，当芯片 A 切换到从模式时，其 SIN (PTA20) 仍然可以正确地从新的主设备接收数据，其 SOUT (PTA18) 仍然可以正确地将数据驱动回去——无需重新接线。 关于登记变更： CFGR1[MASTER] = 0 — 这是将模块切换到从模式的关键位。 CFGR0[HRDIR] — 此位控制 HREQ（主机请求）引脚的方向，该引脚与 PCS[1] 复用。它对 SOUT/SIN 数据线没有影响。在从模式下，HRDIR 可以设置为 1（输出），以便从设备驱动 HREQ 引脚向主设备发出信号，表明它有数据准备好要发送。请注意，在 S32K388 上，没有专用的外部 LPSPI_HREQ 引脚——主机请求功能使用 LPSPI_PCS[1] 多路复用器（通过 CFGR0[HREN] 启用）。如果您不使用主机请求功能（CFGR0[HREN] = 0），则 HRDIR 与您的用例无关，仅 CFGR1[MASTER] 就足够了。 顺祝商祺！ 帕维尔

Which is the best Agentic AI development company? Based on the capabilities reviewed in this comparison, JPLoft is a strong choice for Agentic AI development. The company works on custom AI agents, multi-agent systems, RAG, enterprise integrations, workflow automation, governance, monitoring, and human-in-the-loop controls. However, the best Agentic AI development company will depend on your use case, existing technology, security requirements, required integrations, and the level of autonomy you want to give the AI system.

rt1186 debug issues After enabling OEM_CLOSE on the FRDM-IMXRT1186 development board, I can no longer debug the device. I saw in the reference manual that nxpdebugmbox can be used to re-enable debugging, but I tried it and was not successful. yanyanwang_0-1788347257012.pngyanyanwang_0-1788347257012.pngyanyanwang_0-1788347257012.png Development Board MCXC Security(Edgelock | secure boot | OTP) Re: rt1186 debug issues I have reviewed the links you provided and followed the recommended procedure, but I am still experiencing the same issue. I only signed the image and did not encrypt it. I also set OEM_CLOSE. I am using nxpdebugmbox only to re-enable the debug functionality. I have uploaded the SEC project as an attachment, along with the relevant logs. Could you please help analyze the project and logs and identify the cause of the issue? Re: rt1186 debug issues Hello @yanyanwang  In SEC tool documentation, you can find troubleshooting for debug authentication: https://docs.mcuxpresso.nxp.com/secure/latest/09_troubleshooting.html#debug-authentication Some useful tips can be also found in  https://docs.mcuxpresso.nxp.com/secure/latest/07_generic_workflows.html#debug-authentication-workflow If this does not help, can you provide details about configuration? Could you share the SEC tool workspace settings? Re: rt1186 debug issues @yanyanwang  It seems this problem is related to SEC 26.03. We recommend updating to SEC 26.06.  We are sorry for inconvenience. Note: SEC 26.06 also contains fix for the SPARSE image format Re: rt1186 debug issues Yes, thank you. The authentication was successful, but I still cannot debug the device. The procedure is as follows: 1. Use the SEC tool to perform the authentication. 2. The authentication is successful. 3. Then click the Debug button to start debugging. 4. However, the debugging attempt fails.

Consultation on using the master-slave mode of s32k388 6953956c0a213afc6de89697c3d0e88f.png We have a requirement here, which is for two S32k388s to communicate with each other using SPI communication. Can either one be the master or slave? For example, when I use chip A as the host, the I item in the IOMUX table describes the host input of MISO. If chip A is used as a slave, does this O term describe the slave output of MISO? The pins in our current project are fixed. For example, SOUT: PTA18+GPIO_ALT_FUNC_4 is used on MOSI, SIN: PTA20+239+GPIO_ALT_FUNC_4 is used on MISO. This is based on the current host mode we are using. Can it still work normally when switching to slave mode without changing the pins? Is it sufficient to switch slave mode by simply changing the HRDIR of CFGR0 and the MASTER of CFGR1? Re: Consultation on using the master-slave mode of s32k388 Hello @xlele , You do not need any hardware changes to switch between master and slave mode. In a standard two-chip SPI setup, the pins are always cross-connected between the two devices: Chip A SOUT → Chip B SIN (MOSI line) Chip A SIN ← Chip B SOUT (MISO line) The SOUT pin is always a serial data output and SIN is always a serial data input, regardless of whether the device is operating as master or slave. So when Chip A switches to slave mode, its SIN (PTA20) still correctly receives data from the new master and its SOUT (PTA18) still correctly drives data back — no rewiring needed. Regarding the register changes: CFGR1[MASTER] = 0 — this is the key bit to switch the module into slave mode. CFGR0[HRDIR] —  this bit controls the direction of the HREQ (Host Request) pin, which is multiplexed with PCS[1]. It has no effect on the SOUT/SIN data lines. In slave mode, HRDIR can be set to 1 (output) so that the slave drives the HREQ pin to signal the master that it has data ready to transmit. Note that on S32K388, there is no dedicated external LPSPI_HREQ pin — the host request function uses the LPSPI_PCS[1] mux (enabled via CFGR0[HREN]). If you are not using the host request feature (CFGR0[HREN] = 0), HRDIR is not relevant to your use case and CFGR1[MASTER] alone is sufficient. Best regards, Pavel

rt1186 调试问题 在 FRDM-IMXRT1186 开发板上启用 OEM_CLOSE 后，我无法再调试该设备。我在参考手册中看到可以使用 nxpdebugmbox 重新启用调试功能，但我尝试后没有成功。 yanyanwang_0-1788347257012.pngyanyanwang_0-1788347257012.pngyanyanwang_0-1788347257012.png 开发板 MCXC 安全（Edgelock | 安全启动 | OTP） Re: rt1186 debug issues 我已查看您提供的链接并按照推荐的步骤操作，但我仍然遇到同样的问题。 我只对图像进行了签名，并没有对其进行加密。我还设置了 OEM_CLOSE。 我使用 nxpdebugmbox 只是为了重新启用调试功能。 我已将高效密码学标准\\(SEC\\)项目及其相关日志作为附件上传。请您帮忙分析项目和日志，找出问题的原因吗？ Re: rt1186 debug issues 你好@yanyanwang 在 高效密码学标准\\(SEC\\) 工具文档中，您可以找到有关调试身份验证的故障排除信息： https://docs.mcuxpresso.nxp.com/secure/latest/09_troubleshooting.html#debug-authentication 您还可以在以下位置找到一些有用的技巧： https://docs.mcuxpresso.nxp.com/secure/latest/07_generic_workflows.html#debug-authentication-workflow 如果这样还是不行，能否提供详细的配置信息？能否分享一下高效密码学标准(SEC)工具的工作区设置？ Re: rt1186 debug issues @yanyanwang 这个问题似乎与 高效密码学标准\\(SEC\\) 26.03 有关。我们建议更新至高效密码学标准(SEC) 26.06版本。 给您带来的不便，我们深表歉意。 注：高效密码学标准(SEC) 26.06 还包含对 SPARSE 映像格式的修复。 Re: rt1186 debug issues 是的，谢谢。身份验证成功，但我仍然无法调试设备。 具体步骤如下： 1. 使用高效密码学标准(SEC)工具执行身份验证。 2. 身份验证成功。 3. 然后点击调试按钮开始调试。 4.然而，调试尝试失败了。

Guideline for Porting a New YOLO Variant - YOLO26 on Ara2 This slides firstly introduce the YOLO26 model, and NXP Ara2 Model Zoo, Ara2 SDK/Runtime. Then it explains the CNN model compilation flow with Ara2 toolchain in SDK package, how to compile the newly added model - Yolo26n, how to setup the inference environment in i.MX95FRDM+Ara2-240 board. Finally present the inference result. Patches and user guide are provided in attachment as well.

CircO2 Nitric Oxide Tablets Review: A Complete Buyer's Guide CircO2 is a nitric oxide support supplement made by Advanced Bionutritionals. Unlike a lot of pills you swallow with water, CircO2 comes in a quick-dissolving tablet (sometimes called a lozenge) that melts in your mouth. This is one of the things that makes it stand out from other CircO2 Tablets on the market. The main idea behind CircO2 Oxygen Booster and Circulation Support is simple: help your body make more nitric oxide, so your blood vessels can relax and widen. When that happens, blood (and the oxygen it carries) can move more freely through your body. That can mean more energy, warmer hands and feet, and better stamina during the day.   Re: CircO2 Nitric Oxide Tablets Review: A Complete Buyer's Guide CircO2 is a nitric oxide support supplement in USA, Canada, UK, Australia and New Zealand from Advanced Bionutritionals designed to promote healthy circulation. Unlike traditional supplements that you swallow with water, ORIGINAL CircO2 comes as a fast-dissolving tablet, or lozenge, that melts in your mouth. This convenient format helps set it apart from many other circulation-support tablets. The goal of CircO2 Oxygen Booster and Circulation Support is to support the body’s natural production of nitric oxide. Nitric oxide helps blood vessels relax and expand, which may allow blood and oxygen to circulate more efficiently throughout the body. By supporting healthy blood flow, CircO2 may help promote everyday energy, stamina, and circulation, including helping hands and feet feel warmer.

S32k344 MBIST LBIST 我正在 Green Hills 的一个项目中实施 S32k344 BIST。由于我不使用 Tresos 或 NXP DS，所以我使用的是源代码形式的 SW32K3_SPD_1.0.6_D2512。我能够导入大部分 bist 函数，但有一些我不确定的定义（到处都找不到它们）。请问有人能回答以下问题吗？ 1. 当 S32k344 处于锁定步进模式时，我可以运行 LBIST MBIST 吗？ 2. 我通过检查代码猜测以下定义是否正确？ #define BIST_MBIST_0 1U #define BIST_MBIST_1 2U #define BIST_MBIST_2 3U #define BIST_MBIST_3 4U #define BIST_MBIST_4 5U #define BIST_MBIST_5 6U #define BIST_MBIST_6 7U #define BIST_MBIST_7 8U #define BIST_MBIST_8 9U #define BIST_MBIST_9 10U #define BIST_MBIST_10 11U #define BIST_LBIST_0 0U 我使用的配置数据如下： static const BIST_CHANNEL_CONFIG_TYPE BistConfig[BIST_SAFETYBOOTCFG_NB] = { { （BIST_CHANNEL_TYPE）BIST_MBIST_0， (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_1)) }, { （BIST_CHANNEL_TYPE）BIST_MBIST_1， (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_2)) }, { （BIST_CHANNEL_TYPE）BIST_MBIST_2， (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_3)) }, { （BIST_CHANNEL_TYPE）BIST_MBIST_3， (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_4)) }, { （BIST_CHANNEL_TYPE）BIST_MBIST_4， (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_5)) }, { （BIST_CHANNEL_TYPE）BIST_MBIST_5， (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_6)) }, { （BIST_CHANNEL_TYPE）BIST_MBIST_6， (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_7)) }, { （BIST_CHANNEL_TYPE）BIST_MBIST_7， (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_8)) }, { （BIST_CHANNEL_TYPE）BIST_MBIST_8， (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_9)) }, //#endif { （BIST_CHANNEL_TYPE）BIST_MBIST_9， (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_10)) }, { （BIST_CHANNEL_TYPE）BIST_MBIST_10， (BIST_CONTROL_TYPE)(0x00100000U) }, { （BIST_CHANNEL_TYPE）BIST_LBIST_0， (BIST_CONTROL_TYPE)((0x00001108U) | BIST_LBIST_PTR_VAL(BIST_NIL)) } }; Re: S32k344 MBIST LBIST 你好， 1. 当 S32k344 处于锁定步进模式时，我可以运行 LBIST MBIST 吗？ 是的。S32K344 锁步架构不会阻止 STCU2 LBIST/MBIST 的执行。BIST 机制是设备功能安全基础设施的一部分，旨在测试由 STCU2 管理的逻辑和存储器。The S32K3 功能安全 Manual explicitly lists both lockstep and STCU2 LBIST/MBIST as safety mechanisms of the 设备. 2. 我通过检查代码猜测以下定义是否正确？ 对于 S32K344 来说，这些数值基本正确，但从功能安全角度来看，在功能安全启动配置中包含 MBIST_10 (HSE_ROM) 并非必需，建议直接使用经过验证的 SPD 配置。 顺祝商祺！ Peter Re: S32k344 MBIST LBIST 彼得 非常感谢您的回复。我这几天一直被BIST测试问题困扰着。我正在使用 S32k344 白板进行测试，代码是用 Green Hills Multi IDE rev 8.1 版本 的。安全靴自检未通过。我确信核心和外设都满足最大时钟频率要求。我的核心时钟频率为 160MHz，来自外部晶振 16MHz 和 PLL，AIPS_PLAT_CLK 为 80MHz，AIPS_SLOW_CLK 为 40MHz，DCM_CLK 为 40MHz，LBIST_CLK 为 40MHz，QSPI_MEM_CLK 为 160MHz。当设备从 BIST 运行复位时，出现以下错误：DES 寄存器为 0x00408175，一些保留位被设置，FES 寄存器为 0x2000（这没有意义）。请问您能否回答以下问题？ 1. 对于上面提到的所有时钟信号，是否应该通过 MC_CGM->MUX_0_DC_x 寄存器启用它们？我正在获得 信息相互矛盾，目前这些功能已启用。 2. 在参考手册的 STCU2 章节中，有这样一段话：“在 EMAC 时间戳存储器上运行 MBIST 时，应适当配置 MC_CGM.MUX_9_DC_0[DIV]，以确保 EMAC_CLK_TS 至少是 AIPS_SLOW_CLK 频率的 1.5 倍。”那是不是意味着我必须配置时钟并在 MC_CGM->MUX_9_DC_0 寄存器中启用它？ 3. 如果我想查看 SW32K3_SPD_1.0.6_D2512 软件包中的示例代码 S32_SPD_Demo，我猜我需要安装最新的 NXP Design Studio，将 spd zip 文件作为更新站点导入，还需要 RTD 软件包，是这样吗？ 4. 我认为 MBIST 10 是 HSE_RAMS，MBIST 11 是 HSE_ROMS，请参阅 SPD 文档文件夹中的下表。 MBIST BIST ID BIST实例名称 RESET 功能域 安全靴 功能安全诊断 0 SYS0_RAMS 主要 ü ü 1 SYS1_RAMS 主要 ü ü 2 DMA_TCD_RAM 主要 ü ü 3 CM7_0_TOP 主要 ü ü 4 CM7_1_TOP 主要 ü ü 5 FLEX_CAN_RAMS 主要 ü ü 6 QSPI_PERI_RAMS 主要 ü ü 7 EMAC_TSN_RAM 主要 ü ü 8 EMAC_RAMS 主要 ü ü 9 b03_ETF_RAMS 主要 ü ü 10 HSE_RAMS 主要 ü ü 11 HSE_ROMS 主要   ü Re: S32k344 MBIST LBIST 我的问题有了新的进展，在我启用 STCU_RUNSW_REG 中的第 8 位和第 9 位以使用 PLL 之后，我一直看到 DES 寄存器为 0x11，FES 寄存器为 0x10。bist_get_exec_status(BIST_SAFETYBOOT_CFG) 返回值为 NOT RUN (0x03)。BIST ERR_STAT 寄存器中没有任何内容，END 标志也没有设置。FCCU NCF_S0 寄存器中的第 2 位已设置。BIST 似乎没有启动，但我确实看到了 RESET。我通过写入另一侧银行的闪存来捕获寄存器设置。 Re: S32k344 MBIST LBIST 我检查了所有可能的时钟，我相信它们是正确的。我还将寄存器中的配置数据与 NXP studio spd 示例项目中的值进行了比较，它们也是正确的。一条新信息。系统从 BIST RESET 后，我在 DCMROD3 寄存器中看到值 0x18。我该如何解决这个错误？谢谢。 XRen_Parker_0-1788544110794.pngXRen_Parker_0-1788544110794.pngXRen_Parker_0-1788544110794.pngXRen_Parker_0-1788544110794.pngXRen_Parker_0-1788544110794.png Re: S32k344 MBIST LBIST 你好， STCU 自检序列正在进入并到达 ST_DONE RESET 阶段。但是，STCU 还报告了一个不可恢复的故障 (STCU_URF)，这就解释了为什么 SAF BIST 驱动程序随后报告 BIST_NORUN。因此，问题似乎是 STCU 执行/配置失败，而不是 BIST 从未触发信号的情况。 在 S32K3 上，同时看到破坏性复位和功能性复位指示通常表明您正在查看复位历史记录，而不是当前的复位源。 既然你在移植软件，我建议先从仅进行 MBIST 测试开始，看看它是否能从 PLL 源通过。 另外，我建议你再检查一下测试的时钟设置。 顺祝商祺！ Peter Re: S32k344 MBIST LBIST 你好， 在 S32K344 上，RCCU 报告锁步不匹配，并且当连接到调试器时，经常会出现与 RCCU 相关的故障，而这些故障在独立执行中永远不会发生。 如果您按照示例中的设置进行操作，您将看到完整的 BIST（内置自测试）。 示例已测试，默认情况下完全可用。 但是您的端口报告 URF 故障，这说明并非所有部件都相同。 查阅STCU文档，用户可以设置指向测试的指针。 54.9.4 STCU2 配置 (CFG) petervlna_0-1788766597312.pngpetervlna_0-1788766597312.pngpetervlna_0-1788766597312.png 您可以先尝试减少测试用例，然后慢慢添加更多测试用例。 在 MBIST 和 LBIST 控制寄存器中，您可以设置哪个测试将是最后一个： petervlna_1-1788766735386.pngpetervlna_1-1788766735386.pngpetervlna_1-1788766735386.png 例如，通过指向 CFG 寄存器中的某个位置，您可以执行单个 MBIST 分区： petervlna_2-1788766853581.pngpetervlna_2-1788766853581.pngpetervlna_2-1788766853581.png petervlna_3-1788766973925.pngpetervlna_3-1788766973925.pngpetervlna_3-1788766973925.png 顺祝商祺！ Peter Re: S32k344 MBIST LBIST 我尝试按顺序运行 mbist，也尝试过单独运行 mbist 测试 ID。结果相同，未观察到新的状态。能否在触发之前确认以下用于安全启动的 SCU2 寄存器设置？谢谢。 XRen_Parker_0-1788899133217.pngXRen_Parker_0-1788899133217.png Re: S32k344 MBIST LBIST 这是为社区中在 S32k344 微控制器中实现 LBIST/MBIST 时遇到困难的人们准备的。经过数日毫无进展后，我终于看到测试通过了。我通过对 SPD 驱动程序 1.06 进行自定义移植实现了这一点。驱动程序代码运行正常，只是需要将故障配置为不可恢复故障。以下是需要配置的时钟，如果其中任何一个没有正确设置，测试将失败，状态为 BIST_NORUN(0x03)，因为测试序列是并发运行的，看不到其他状态，也没有设置完成位。 1. 配置 FXOSC 模块 CTRL 寄存器以使用外部振荡器或晶体，这是获得 160MHz（S32k344 的最大频率）的唯一方法。 2. 配置 PLL 电路的 PLLDIG 模块，通过配置 PLLDV 寄存器中的 rdiv、mfi 和 odiv2 位，确保输出最大频率。 3. 按照参考手册中的步骤，设置 MC_CGM_MUX_x 寄存器，为 core_clk 和 emac_clk 切换 PLL 时钟。 4. 配置 MC_CGM-MUX_0 和 MC_CGM-MUX_9 寄存器以获取以下时钟信号。 AIPS_PLAT_CLK 设置为 80 MHz AIPS_SLOW_CLK 设置为 40 MHz HSE_CLK 设置为 80 MHz DCM_CLK 设置为 40 MHz LBIST_CLK 设置为 40MHz QSPI_MEM_CLK 设置为 160MHz EMAC_CLK 设置为 80MHz 注意：不要设置 RUNSW 寄存器中的第 8 位和第 9 位，如果设置了它们，测试将失败。SPD驱动程序代码中没有实现这一点。我之所以提到这一点，是因为参考手册中存在相互矛盾的信息。

PCF85263AT/AJ -- Minutes value displayed on the screen is showing an arbitrary value As part of the code migration task, we are facing an issue where the BSF flag is being set. Due to the BSF flag being set, the EMON bit in the Minutes register is also getting set. As a result, the Minutes value displayed on the screen is showing an arbitrary value. Additionally, the Year value is not being saved correctly and continuously shows 2000 even after setting the RTC date and time. I tried to test the condition mentioned below, but the problem still persists.  I set the flag register (0x43) to 0x00 and read it immediately; it showed 0x00. However, when I read the register again after 3 seconds, the value was set again to 0x08 (or 0x00).   Re: PCF85263AT/AJ -- Minutes value displayed on the screen is showing an arbitrary value Hello Ris_eek Good day! The BSF flag is not simply failing to clear. Instead, the RTC is detecting a new battery switch-over event and setting BSF again. According to the datasheet, BSF is set whenever the battery switch-over logic detects a power transition event The fact that it re-asserts after ~3 seconds means the VDD supply is repeatedly dropping below the battery switch-over threshold causing repeated VDD>VBAT>VDD transitions. Each transition re-sets the BSF. RafaR_0-1788887610951.pngRafaR_0-1788887610951.pngRafaR_0-1788887610951.pngRafaR_0-1788887610951.png This constant voltage fluctuation causes the RTC to constantly reset, which is why it only shows the year 2000. I recommend checking if there's a problem with the power supply signal. I hope this information has helped you, please let me know if you need help with anything else. Have a great day and best of luck. Re: PCF85263AT/AJ -- Minutes value displayed on the screen is showing an arbitrary value Dear Rafar; Thanks for your mail.    In the hardware, the VDD (4.93 VDC) and VBAT (3.02 VDC) voltages are constant. As a precaution against voltage fluctuations, a 100 nF capacitor is connected across the battery supply. The Battery Switch Register (26h) is set to 0x00. Therefore, the BSM (Battery Switch Mode) is configured to switch at the Vth level. The Vth level is 1.5 V because the BSTH (Battery Switch Threshold Voltage) bit is set to 0. As per Figure 25, referenced in previous email: When VDD < Vth, the BSF is set to 1. When VDD > VBAT, the BSF should be cleared. However, under the power-ON condition, the measured voltage is VDD = 4.93 VDC, which is greater than VBAT = 3.02 V. Even then, the BSF is not cleared. Could you please clarify why the BSF remains set even though VDD is greater than VBAT? Re: PCF85263AT/AJ -- Minutes value displayed on the screen is showing an arbitrary value Hello Ris_eek Good day! The datasheet says the following: The assertion of the flag BSF (register Flags, address 2Bh) can be used to generate an interrupt at pins INTA and INTB. The interrupt can be generated as a pulsed signal or alternatively as a permanently active signal, which follows the condition of bit BSF. BSF remains set until cleared by command. The reference image I sent also indicates the following: "cleared via interface." It’s not automatically, you have to cleared I hope this information has helped you, please let me know if you need help with anything else. Have a great day and best of luck. Re: PCF85263AT/AJ -- Minutes value displayed on the screen is showing an arbitrary value Okay RafaR Thank you for this. But the BSF flag is cleared in software, but after some time, it is set again, as described in my previous post.