i.MX8MQ evk can't boot from SD card or eMMC

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

i.MX8MQ evk can't boot from SD card or eMMC

2,732 Views
Derek0902
Contributor II

Hi,

There are some mesg  when I boot from SD card or eMMC.

U-Boot SPL 2023.04-lf_v2023.04+gaf7d004eaf (Jun 06 2023 - 14:59:40 +0000)
PMIC:  PFUZE100 ID=0x10
DDRINFO: start DRAM init
DDRINFO: DRAM rate 3200MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
SEC0:  RNG instantiated
Normal Boot
Trying to boot from MMC1


U-Boot 2023.04-lf_v2023.04+gaf7d004eaf (Jun 06 2023 - 14:59:40 +0000)

CPU:   i.MX8MQ rev2.0 1500 MHz (running at 1000 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 48C
Reset cause: POR
Model: NXP i.MX8MQ EVK
DRAM:  3 GiB
TCPC:  Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C0 0x50]
Core:  169 devices, 31 uclasses, devicetree: separate
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

[*]-Video Link 0 (1280 x 720)
        [0] display-controller@32e00000, video
        [1] hdmi@32c00000, display
In:    serial
Out:   serial
Err:   serial
SEC0:  RNG instantiated
switch to partitions #0, OK
mmc0(part 0) is current device
flash target is MMC:0
Net:   eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot:  0
Working FDT set to 43000000
starting USB...
Bus usb@38100000: Failed to initialize board for imx8m USB
probe failed, error -1
Bus usb@38200000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@38200000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
MMC: no card present
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
48345 bytes read in 2 ms (23.1 MiB/s)
Working FDT set to 43000000
MMC: no card present
Unable to open OP-TEE session (err=-5)
mm_communicate failed!
Error: Cannot initialize UEFI sub-system, r = 3
Running BSP bootcmd ...
switch to partitions #0, OK
mmc0(part 0) is current device
Failed to load 'boot.scr'
32121344 bytes read in 205 ms (149.4 MiB/s)
Booting from mmc ...
48345 bytes read in 2 ms (23.1 MiB/s)
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
Working FDT set to 43000000
clk usb2_phy_root_clk already disabled
   Using Device Tree in place at 0000000043000000, end 000000004300ecd8
Working FDT set to 43000000

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 6.1.22+g66e442bc7fdc (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.40.20230119) #1 SMP PREEMPT Mon Jun 12 12:31:27 UTC 2023
[    0.000000] Machine model: NXP i.MX8MQ EVK
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x0000000080000000, size 896 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x00000000fdffffff]
[    0.000000] NUMA: NODE_DATA [mem 0xfd9ca700-0xfd9ccfff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000040000000-0x00000000fdffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x00000000fdffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000fdffffff]
[    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 20 pages/cpu s44520 r8192 d29208 u81920
[    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] alternatives: applying boot alternatives
[    0.000000] Fallback order for Node 0: 0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 766080
[    0.000000] Policy zone: DMA
[    0.000000] Kernel command line: console=ttymxc0,115200 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:all(zero), heap alloc:off, heap free:off
[    0.000000] Memory: 2101372K/3112960K available (19584K kernel code, 1608K rwdata, 6708K rodata, 3328K init, 644K bss, 94084K reserved, 917504K 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 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]  Tracing 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: 128 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] Root IRQ handler: gic_handle_irq
[    0.000000] GICv3: GICv3 features: 16 PPIs
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000
[    0.000000] ITS: No ITS available, not enabling LPIs
[    0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000000] arch_timer: cp15 timer(s) running at 8.33MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1ec0311ec, max_idle_ns: 440795202152 ns
[    0.000000] sched_clock: 56 bits at 8MHz, resolution 120ns, wraps every 2199023255541ns
[    0.000482] Console: colour dummy device 80x25
[    0.000557] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.66 BogoMIPS (lpj=33333)
[    0.000569] pid_max: default: 32768 minimum: 301
[    0.000633] LSM: Security Framework initializing
[    0.000735] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.000760] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.002324] cblist_init_generic: Setting adjustable number of callback queues.
[    0.002334] cblist_init_generic: Setting shift to 2 and lim to 1.
[    0.002415] cblist_init_generic: Setting shift to 2 and lim to 1.
[    0.002595] rcu: Hierarchical SRCU implementation.
[    0.002598] rcu:     Max phase no-delay instances is 1000.
[    0.003761] EFI services will not be available.
[    0.004035] smp: Bringing up secondary CPUs ...
[    0.004530] Detected VIPT I-cache on CPU1
[    0.004618] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000
[    0.004655] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.005187] Detected VIPT I-cache on CPU2
[    0.005261] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000
[    0.005285] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.005768] Detected VIPT I-cache on CPU3
[    0.005845] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000
[    0.005867] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.005927] smp: Brought up 1 node, 4 CPUs
[    0.005934] SMP: Total of 4 processors activated.
[    0.005939] CPU features: detected: 32-bit EL0 Support
[    0.005942] CPU features: detected: 32-bit EL1 Support
[    0.005946] CPU features: detected: CRC32 instructions
[    0.006016] CPU: All CPU(s) started at EL2
[    0.006037] alternatives: applying system-wide alternatives
[    0.008235] devtmpfs: initialized
[    0.016018] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.016039] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.045516] pinctrl core: initialized pinctrl subsystem
[    0.047779] DMI not present or invalid.
[    0.048475] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.049731] DMA: preallocated 512 KiB GFP_KERNEL pool for atomic allocations
[    0.050013] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.050251] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.050293] audit: initializing netlink subsys (disabled)
[    0.050429] audit: type=2000 audit(0.048:1): state=initialized audit_enabled=0 res=1
[    0.050963] thermal_sys: Registered thermal governor 'step_wise'
[    0.050968] thermal_sys: Registered thermal governor 'power_allocator'
[    0.051003] cpuidle: using governor menu
[    0.051174] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.051254] ASID allocator initialised with 65536 entries
[    0.052256] Serial: AMBA PL011 UART driver
[    0.052325] imx mu driver is registered.
[    0.052348] imx rpmsg driver is registered.
[    0.062607] imx8mq-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver
[    0.069092] platform 30a70000.mipi_csi1: Fixed dependency cycle(s) with /soc@0/bus@30800000/csi1_bridge@30a90000
[    0.069115] platform 30a70000.mipi_csi1: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a30000/ov5640_mipi@3c
[    0.070408] platform 30b60000.mipi_csi2: Fixed dependency cycle(s) with /soc@0/bus@30800000/csi2_bridge@30b80000
[    0.070430] platform 30b60000.mipi_csi2: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a20000/ov5640_mipi2@3c
[    0.071955] platform 32c00000.hdmi: Fixed dependency cycle(s) with /soc@0/bus@32c00000/display-controller@32e00000
[    0.072717] platform 38100000.usb: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a20000/tcpc@50
[    0.075529] platform ptn36043: Fixed dependency cycle(s) with /soc@0/bus@30800000/i2c@30a20000/tcpc@50/connector
[    0.078185] KASLR disabled due to lack of seed
[    0.099085] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[    0.099093] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[    0.099099] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[    0.099102] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[    0.099108] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[    0.099112] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[    0.099117] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[    0.099122] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[    0.101170] ACPI: Interpreter disabled.
[    0.101864] iommu: Default domain type: Translated
[    0.101869] iommu: DMA domain TLB invalidation policy: strict mode
[    0.102174] SCSI subsystem initialized
[    0.102497] usbcore: registered new interface driver usbfs
[    0.102540] usbcore: registered new interface driver hub
[    0.102572] usbcore: registered new device driver usb
[    0.103694] mc: Linux media interface: v0.10
[    0.103732] videodev: Linux video capture interface: v2.00
[    0.103819] pps_core: LinuxPPS API ver. 1 registered
[    0.103823] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.103837] PTP clock support registered
[    0.103989] EDAC MC: Ver: 3.0.0
[    0.105081] FPGA manager framework
[    0.105161] Advanced Linux Sound Architecture Driver Initialized.
[    0.105767] Bluetooth: Core ver 2.22
[    0.105795] NET: Registered PF_BLUETOOTH protocol family
[    0.105799] Bluetooth: HCI device and connection manager initialized
[    0.105808] Bluetooth: HCI socket layer initialized
[    0.105814] Bluetooth: L2CAP socket layer initialized
[    0.105827] Bluetooth: SCO socket layer initialized
[    0.106202] vgaarb: loaded
[    0.106699] clocksource: Switched to clocksource arch_sys_counter
[    0.106891] VFS: Disk quotas dquot_6.6.0
[    0.106933] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.107122] pnp: PnP ACPI: disabled
[    0.114641] NET: Registered PF_INET protocol family
[    0.114902] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.118186] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
[    0.118230] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.118246] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.118504] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes, linear)
[    0.119538] TCP: Hash tables configured (established 32768 bind 32768)
[    0.119643] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    0.119757] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    0.119958] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.120308] RPC: Registered named UNIX socket transport module.
[    0.120313] RPC: Registered udp transport module.
[    0.120316] RPC: Registered tcp transport module.
[    0.120319] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.121180] PCI: CLS 0 bytes, default 64
[    0.121912] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[    0.122797] kvm [1]: IPA Size Limit: 40 bits
[    0.124422] kvm [1]: vgic-v2@31020000
[    0.124437] kvm [1]: GIC system register CPU interface enabled
[    0.124531] kvm [1]: vgic interrupt IRQ9
[    0.124625] kvm [1]: Hyp mode initialized successfully
[    0.125844] Initialise system trusted keyrings
[    0.126018] workingset: timestamp_bits=42 max_order=20 bucket_order=0
[    0.133146] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.133742] NFS: Registering the id_resolver key type
[    0.133800] Key type id_resolver registered
[    0.133804] Key type id_legacy registered
[    0.133884] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.133890] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    0.133914] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.134233] 9p: Installing v9fs 9p2000 file system support
[    0.177343] Key type asymmetric registered
[    0.177349] Asymmetric key parser 'x509' registered
[    0.177401] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
[    0.177407] io scheduler mq-deadline registered
[    0.177413] io scheduler kyber registered
[    0.184348] EINJ: ACPI disabled.
[    0.192978] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.192990] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
[    0.196444] mxs-dma 33000000.dma-apbh: initialized
[    0.201165] SoC: i.MX8MQ revision 2.0
[    0.201263] Config NOC for VPU and CPU
[    0.201999] Bus freq driver module loaded
[    0.207932] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.210235] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 18, base_baud = 1562500) is a IMX
[    1.343959] printk: console [ttymxc0] enabled
[    1.348916] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 19, base_baud = 5000000) is a IMX
[    1.357832] serial serial0: tty port ttymxc2 registered
[    1.377072] loop: module loaded
[    1.381486] of_reserved_mem_lookup() returned NULL
[    1.386468] megasas: 07.719.03.00-rc1
[    1.394997] spi-nor spi3.0: n25q256a (32768 Kbytes)
[    1.404529] tun: Universal TUN/TAP device driver, 1.6
[    1.410448] thunder_xcv, ver 1.0
[    1.413733] thunder_bgx, ver 1.0
[    1.417027] nicpf, ver 1.0
[    1.421895] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version
[    1.429126] hns3: Copyright (c) 2017 Huawei Corporation.
[    1.434493] hclge is initializing
[    1.437830] e1000: Intel(R) PRO/1000 Network Driver
[    1.442720] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    1.448512] e1000e: Intel(R) PRO/1000 Network Driver
[    1.453484] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.459446] igb: Intel(R) Gigabit Ethernet Network Driver
[    1.464854] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.470467] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[    1.476742] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.482848] sky2: driver version 1.30
[    1.487126] usbcore: registered new interface driver r8152
[    1.492886] VFIO - User Level meta-driver version: 0.3
[    1.501366] usbcore: registered new interface driver uas
[    1.506740] usbcore: registered new interface driver usb-storage
[    1.512829] usbcore: registered new interface driver usbserial_generic
[    1.519388] usbserial: USB Serial support registered for generic
[    1.525435] usbcore: registered new interface driver ftdi_sio
[    1.531206] usbserial: USB Serial support registered for FTDI USB Serial Device
[    1.538552] usbcore: registered new interface driver usb_serial_simple
[    1.545104] usbserial: USB Serial support registered for carelink
[    1.551221] usbserial: USB Serial support registered for zio
[    1.556903] usbserial: USB Serial support registered for funsoft
[    1.562934] usbserial: USB Serial support registered for flashloader
[    1.569323] usbserial: USB Serial support registered for google
[    1.575268] usbserial: USB Serial support registered for libtransistor
[    1.581819] usbserial: USB Serial support registered for vivopay
[    1.587850] usbserial: USB Serial support registered for moto_modem
[    1.594140] usbserial: USB Serial support registered for motorola_tetra
[    1.600777] usbserial: USB Serial support registered for nokia
[    1.606634] usbserial: USB Serial support registered for novatel_gps
[    1.613011] usbserial: USB Serial support registered for hp4x
[    1.618783] usbserial: USB Serial support registered for suunto
[    1.624729] usbserial: USB Serial support registered for siemens_mpi
[    1.631126] usbcore: registered new interface driver usb_ehset_test
[    1.640335] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0
[    1.654823] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0
[    1.661033] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock to 1970-01-01T00:22:14 UTC (1334)
[    1.670461] i2c_dev: i2c /dev entries driver
[    1.675976] mxc-mipi-csi2_yav 30a70000.mipi_csi1: mipi_csi2_probe
[    1.682136] mxc-mipi-csi2_yav 30a70000.mipi_csi: Remote device at endpoint@0 XXX found
[    1.690076] mxc-mipi-csi2_yav 30a70000.mipi_csi1: lanes: 2, name: mxc-mipi-csi2.0
[    1.697933] mxc-mipi-csi2_yav 30b60000.mipi_csi2: mipi_csi2_probe
[    1.704086] mxc-mipi-csi2_yav 30b60000.mipi_csi: Remote device at endpoint@0 XXX found
[    1.712027] mxc-mipi-csi2_yav 30b60000.mipi_csi2: lanes: 2, name: mxc-mipi-csi2.1
[    1.719857] mx6s-csi 30a90000.csi1_bridge: initialising
[    1.725326] CSI: Registered sensor subdevice: mxc-mipi-csi2.0
[    1.731257] mx6s-csi 30b80000.csi2_bridge: initialising
[    1.736706] CSI: Registered sensor subdevice: mxc-mipi-csi2.1
[    1.746378] Bluetooth: HCI UART driver ver 2.3
[    1.750845] Bluetooth: HCI UART protocol H4 registered
[    1.755995] Bluetooth: HCI UART protocol BCSP registered
[    1.761343] Bluetooth: HCI UART protocol LL registered
[    1.766491] Bluetooth: HCI UART protocol ATH3K registered
[    1.771919] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    1.778292] Bluetooth: HCI UART protocol Broadcom registered
[    1.783981] Bluetooth: HCI UART protocol QCA registered
[    1.790813] sdhci: Secure Digital Host Controller Interface driver
[    1.797003] sdhci: Copyright(c) Pierre Ossman
[    1.802107] Synopsys Designware Multimedia Card Interface Driver
[    1.808792] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.816462] ledtrig-cpu: registered to indicate activity on CPUs
[    1.823236] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    1.830209] usbcore: registered new interface driver usbhid
[    1.835793] usbhid: USB HID core driver
[    1.844583]  cs_system_cfg: CoreSight Configuration manager initialised
[    1.852538] optee: probing for conduit method.
[    1.857008] optee: revision 3.21 (1962aec9)
[    1.858298] optee: dynamic shared memory is enabled
[    1.867762] optee: initialized driver
[    1.879658] NET: Registered PF_LLC protocol family
[    1.886254] NET: Registered PF_INET6 protocol family
[    1.893438] Segment Routing with IPv6
[    1.897149] In-situ OAM (IOAM) with IPv6
[    1.901136] NET: Registered PF_PACKET protocol family
[    1.906230] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    1.920308] Bluetooth: RFCOMM TTY layer initialized
[    1.925206] Bluetooth: RFCOMM socket layer initialized
[    1.930369] Bluetooth: RFCOMM ver 1.11
[    1.934135] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    1.939458] Bluetooth: BNEP filters: protocol multicast
[    1.944700] Bluetooth: BNEP socket layer initialized
[    1.949674] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    1.955605] Bluetooth: HIDP socket layer initialized
[    1.962255] 8021q: 802.1Q VLAN Support v1.8
[    1.966471] lib80211: common routines for IEEE802.11 drivers
[    1.972249] 9pnet: Installing 9P2000 support
[    1.976663] Key type dns_resolver registered
[    1.982373] registered taskstats version 1
[    1.986510] Loading compiled-in X.509 certificates
[    2.029551] gpio-157 (wl-reg-on-hog): hogged as output/high
[    2.039027] ov5640_mipi 0-003c: No sensor reset pin available
[    2.044822] ov5640_mipi 0-003c: supply DOVDD not found, using dummy regulator
[    2.052065] ov5640_mipi 0-003c: supply DVDD not found, using dummy regulator
[    2.059182] ov5640_mipi 0-003c: supply AVDD not found, using dummy regulator
[    2.079001] ov5640_mipi 0-003c: Read reg error: reg=300a
[    2.084332] ov5640_mipi 0-003c: Camera is not found
[    2.089749] imx-gpcv2 303a0000.gpc: Failed to create device link (0x180) with 0-0008
[    2.097515] imx-gpcv2 303a0000.gpc: Failed to create device link (0x180) with 0-0008
[    2.106686] pfuze100-regulator 0-0008: Full layer: 2, Metal layer: 1
[    2.113697] pfuze100-regulator 0-0008: FAB: 0, FIN: 0
[    2.118777] pfuze100-regulator 0-0008: pfuze100 found.
[    2.142473] imx-gpcv2 303a0000.gpc: Failed to create device link (0x180) with 0-0008
[    2.150238] imx-gpcv2 303a0000.gpc: Failed to create device link (0x180) with 0-0008
[    2.161080] i2c i2c-0: IMX I2C adapter registered
[    2.167805] ov5640_mipi 1-003c: No sensor reset pin available
[    2.173599] ov5640_mipi 1-003c: supply DOVDD not found, using dummy regulator
[    2.180841] ov5640_mipi 1-003c: supply DVDD not found, using dummy regulator
[    2.187941] ov5640_mipi 1-003c: supply AVDD not found, using dummy regulator
[    2.207000] ov5640_mipi 1-003c: Read reg error: reg=300a
[    2.212333] ov5640_mipi 1-003c: Camera is not found
[    2.217456] i2c i2c-1: IMX I2C adapter registered
[    2.224174] i2c i2c-2: IMX I2C adapter registered
[    2.229578] imx8mq-usb-phy 381f0040.usb-phy: supply vbus not found, using dummy regulator
[    2.238189] imx8mq-usb-phy 382f0040.usb-phy: supply vbus not found, using dummy regulator
[    2.248822] imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges:
[    2.251008] imx6q-pcie 33c00000.pcie: host bridge /soc@0/pcie@33c00000 ranges:
[    2.256123] imx6q-pcie 33800000.pcie:       IO 0x001ff80000..0x001ff8ffff -> 0x0000000000
[    2.263310] imx6q-pcie 33c00000.pcie:   No bus range found for /soc@0/pcie@33c00000, using [bus 00-ff]
[    2.271503] imx6q-pcie 33800000.pcie:      MEM 0x0018000000..0x001fefffff -> 0x0018000000
[    2.280815] imx6q-pcie 33c00000.pcie:       IO 0x0027f80000..0x0027f8ffff -> 0x0000000000
[    2.297174] imx6q-pcie 33c00000.pcie:      MEM 0x0020000000..0x0027efffff -> 0x0020000000
[    2.316563] cdns-mhdp-imx 32c00000.hdmi: lane-mapping 0xe4
[    2.322074] [drm] Both HDCP 1.4 and 2.2 are enabled
[    2.333004] imx-dcss 32e00000.display-controller: bound 32c00000.hdmi (ops cdns_mhdp_imx_ops)
[    2.342949] [drm] Initialized imx-dcss 1.0.0 20190917 for 32e00000.display-controller on minor 0
[    2.352842] imx-dcss 32e00000.display-controller: [drm] Cannot find any crtc or sizes
[    2.361786] imx-dcss 32e00000.display-controller: [drm] Cannot find any crtc or sizes
[    2.370675] pps pps0: new PPS source ptp0
[    2.374802] imx-dcss 32e00000.display-controller: [drm] Cannot find any crtc or sizes
[    2.503366] imx6q-pcie 33800000.pcie: iATU: unroll T, 4 ob, 4 ib, align 64K, limit 4G

After I use demo image to flash the SD card or eMMC, it still stop at this mesg.

I don't know what wrong with this.

Can somebody give me advises?

Thanks!

 

Labels (1)
0 Kudos
23 Replies

2,235 Views
bernhardfink
NXP Employee
NXP Employee

Hi Derek,

the description in your link refers to a PCIe based WiFi module with the NXP chipset 88W8997. If you would provide such a PCIe board  to the M.2 connector of the 8M EVK, then I would expect that it works with the BSP demo image.

Just changing the conf file to something for the Murata module may not work if during Linux booting this module has already been "treated" with stuff for the 88W8997.

Anyway, getting the Murata WiFi module back to work with the latest BSP is one thing, your reboot problem is another.

How do you reboot?

  • Reset button?
  • Out of Linux with a reboot command?
  • Board power-off-on?

Can you do this with a write-protected SD-card to exclude the possibility that something on the boot medium changes?

Regards,
Bernhard

0 Kudos

2,218 Views
Derek0902
Contributor II

Hi Bernhard,

I use the reset button to reboot the EVK.

 

Could you provide the correct dmseg ?

 

Regards,

Derek

0 Kudos

2,211 Views
Dhruvit
NXP TechSupport
NXP TechSupport

Hello @Derek0902 

I hope you are doing well.

Please share the Linux BSP version you are using.
I have checked the EVK by flashing the demo image into that and it worked.
Please check the same with the latest image.
LF_v6.1.1_1.0.0_images_IMX8MQEVK

I hope it helps!

Thanks & Regards,

Dhruvit Vasavada

0 Kudos

2,206 Views
Derek0902
Contributor II

Hi Dhruvit Vasavada,

 

It seem like LF_v6.1.22_2.0.0_images_IMX8MQEVK.

 

Regards,

Derek

0 Kudos

1,979 Views
Dhruvit
NXP TechSupport
NXP TechSupport

Hi @Derek0902,

I hope you are doing well

Please verify the DIP switches have been set correctly.
We tried the same modification you have in the 'wifi_mod_para.conf' file. But we were unable to reproduce the issue. Our EVK successfully boots from SD card and EMMC.
Please confirm if you have performed any hardware changes on the EVK or not. 
 
Thanks & Regards,
Dhruvit Vasavada
0 Kudos

1,971 Views
Derek0902
Contributor II

Hi @Dhruvit ,

Thanks for your reply.

 

This makes me more convinced  that the hardware is broken.

However, the Original Dealer has brought the EVK back to confirm the problem.

 

Regards,

Derek

 

0 Kudos

1,949 Views
Dhruvit
NXP TechSupport
NXP TechSupport

Hi @Derek0902,

I hope you are doing well.

So, If there are no further queries from your side, Can I mark this case as close now?
If an issue still appears, Please reopen the thread.

Thanks & Regards,
Dhruvit Vasavada

0 Kudos

1,854 Views
Derek0902
Contributor II

Hi @Dhruvit 

 

Okay!

You can mark this case.

 

Regards,

Derek Lin

0 Kudos

2,196 Views
bernhardfink
NXP Employee
NXP Employee

Hi Derek,

the power structure of the 8M EVK is pretty complicated, can you please do a cross-check using different methods of re-booting and check if the problem appears there as well:

  1. Reset button: This goes on a reset circuit and power cycles VDD_SOC_0V9, but other volatges are not affected. So there is maybe some "history" left over using this method.
  2. EVK power cycle:  this makes a complete power cycle of the EVK, most safe way to re-boot
  3. Linux re-boot command: Linux will instruct the PMIC PF4210 to generate a power cycle, but there are also discrete regulators on the EVK, so also here I wouldn't guarantee that really everything starts from scratch

And please tell me exactly what you've done when you say "after I modify the WiFi config". What did you change?

Regards,
Bernhard

 

0 Kudos

2,215 Views
bernhardfink
NXP Employee
NXP Employee

Hi Derek,

you said that you can boot the board up to the end if you have a freshly programmed image. In this case you get a complete dmesg log. This is what I have as well, it should be identical to yours, because I'm also just booting a freshly programmed image (BSP 6.1.22)

Regards,
Bernhard.

0 Kudos

2,204 Views
Derek0902
Contributor II

Hi Bernhard,

 

I can't boot the board up, after I modify the wifi config.

Then I use freshly programmed image, it also stop at the PCIe which I mentioned earlier about the dmesg.

 

Regards,

Derek

0 Kudos

2,347 Views
Dhruvit
NXP TechSupport
NXP TechSupport

Hi @bernhardfink,

I hope you are doing well.

"Is the flash command correct?"
->Yes, the commands are correct, Moreover one can also use the Sudo command as well, Both will work in a proper manner.

"After that I want to try wifi if can use, then modified some file and use reboot button."
->Which files did you make changes in, One can also use a pre-built image, in which wifi is enabled by default, further one can also flash that image using the same command and then when the device is booted, One can check the driver is loaded or not by giving below command.
dmesg | grep -rin interface (it will let you know if the interface was made or not)
If not made one can load the wifi driver manually as well to bring up the wifi.

"I found the EVK can't boot so I re-flash the eMMC. Then it can boot correctly."
->When the device finally booted successfully, was wifi service in working mode or it wasn't enabled at that time too?

Please share the observation.

Thanks & Regards,
Dhruvit Vasavada

 

0 Kudos

2,281 Views
Derek0902
Contributor II
0 Kudos

2,179 Views
Derek0902
Contributor II

Hi @bernhardfink ,

 

I follow this web page. I just do the commands which is in screenshot, and modified the config file.

Regards,

Derek

 

0 Kudos

2,119 Views
bernhardfink
NXP Employee
NXP Employee

But the WLAN/Bluetooth module on the 8M EVK is not with a 88W8997 chip. So if you load this configuration into the Infinion based WiFi module from Murata, it will not work.

So why do you do this change?

Regards,
Bernhard.

 

0 Kudos

2,106 Views
Derek0902
Contributor II

Hi Bernhard,

 

You are right. This is modified by my colleague. she just wanted to try if it can work. 

Then I found that it can't work so I use fresh image to flash the SD card and eMMC again. After the flashing, the EVK can't boot up from both SD card and eMMC. What is the possible reason? 

 

By the way,

I remember that the WF-Fi + Bluetooth module is QCA6174. If I find the booting solution, I will try the menuconfig to enable ath10k driver. 

 

Regards,

Derek 

0 Kudos

2,071 Views
bernhardfink
NXP Employee
NXP Employee

I can't explain a permanent problem, a freshly programmed SD card should do the job.

I remember one strange effect on the 8M board in the past:  when the eMMc had a valid content from the boot image point of view, it always started from eMMC and not from an inserted SD card. Boot into u-boot prompt and erase some eMMC sectors by using "MMC erase 0 0x800".

On the other hand, also a re-flashing of the eMMC with UUU.exe should completely overwrite any old content in the eMMC, so no history should be left over.

Regards,
Bernhard.

0 Kudos

2,316 Views
Derek0902
Contributor II

Hi Dhruvit Vasavada,

I think that the wifi isn't major problem, because I just modify some file on EVK and not in my BSP. If I re-flash the image, the modified files will be covered. Could it be a hardware problem?

 

Regards,

Derek.

0 Kudos

2,329 Views
bernhardfink
NXP Employee
NXP Employee

Hi Derek,

the i.MX 8M EVK has a WiFi module on board (LBEH5UL1CX from Murata). This contains a chipset from Infineon/CYPRESS and it was supported in earlier BSP versions (I think the last version was 5.4.47). Then we changed the BSP to support our own WiFi solutions which we got when we acquired the wireless business from MARVELL a few years ago. So the WiFi support in our lastest BSPs requires an NXP WiFi (+ Bluetooth) chipset from NXP on either a module card for the SD card or on a board for the M.2 connector.

If you want to work with the latest BSP and if you want to get the on-board  Murata WiFi module working, you most likely need to touch the kernel configuration, just taking our demo image and modify something might not be enough.I need to check.

Details can be found here:  https://www.infineon.com/dgdl/Infineon-AN232689_-_Wi-Fi_software_user_guide-ApplicationNotes-v01_00-...

Or you work with an older demo image (5.4.47) which still supports the Murata module.

Regards,
Bernhard.

0 Kudos

2,435 Views
bernhardfink
NXP Employee
NXP Employee

Hi Derek,

 

my EVK boots correctly to the login prompt on both SD an eMMC. I can send you a complete dmesg maybe tomorrow.

But I don't really understand your procedure. You firstly program the .wic demo BSP image and it works. And then?

How do you program the SD card? On a PC SD card slot  or do you use the EVK in Serial Download Mode together with UUU.EXE?

Regards, Bernhard.

0 Kudos