stm32u5g9 的 GUI 指南 我正在研究带有 MIPI DBI 接口的 320x240 显示器。我正在使用 STM32U5G9 与显示器连接。我可以使用 Gui Guider 来制作 GUI 吗？如果是的话，我需要遵循哪些步骤才能让它与 stm32u5g9 一起工作 回复：stm32u5g9 的 Gui Guider 我明白了。 感谢您的快速支持。

PN7642 jlink error Hi there, I have used the same PN7642 development kits(https://www.nxp.com/products/rfid-nfc/nfc-hf/nfc-readers/development-kit-for-pn7642-secure-compact-nfc-controller-with-programmable-memory-and-crypto-acceleration:OM27642)  and Segger J-link utra+(https://www.segger.com/products/debug-probes/j-link/models/j-link-ultra-plus/)  for a while.   It works pretty well until two days ago.   The detail of the error message is the following. I am wondering if my dev board is bad or something like that.   Any idea what happened and how to fix it?   Thank you very much   --Kenny   ERROR: Could not connect to target.   SEGGER J-Link GDB Server V7.94b Command Line Version   JLinkARM.dll V7.94b (DLL compiled Dec 13 2023 16:59:37)   Command line: -SettingsFile "/source/nfc_pn7642/application/Debug/nfc_pn7642 JLink Debug SettingsFile.jlink" -nosilent -swoport 2337 -select USB=505001876 -jlinkscriptfile /Documents/MCUXpressoIDE_11.9.0_2144/workspace/.mcuxpressoide_packages_support/PN7642_support/Script/pnev7642fama.jlinkscript -telnetport 2338 -singlerun -endian little -noir -speed 4000 -port 2339 -vd -device PN7642 -if SWD -halt -reportuseraction   -----GDB Server start settings-----   GDBInit file:                  none   GDB Server Listening port:     2339   SWO raw output listening port: 2337   Terminal I/O port:             2338   Accept remote connection:      yes   Generate logfile:              off   Verify download:               on   Init regs on start:            off   Silent mode:                   off   Single run mode:               on   Target connection timeout:     0 ms   ------J-Link related settings------   J-Link Host interface:         USB   J-Link script:                 /Documents/MCUXpressoIDE_11.9.0_2144/workspace/.mcuxpressoide_packages_support/PN7642_support/Script/pnev7642fama.jlinkscript   J-Link settings file:          "/source/nfc_pn7642/application/Debug/nfc_pn7642 JLink Debug SettingsFile.jlink"   ------Target related settings------   Target device:                 PN7642   Target device parameters:      none   Target interface:              SWD   Target interface speed:        4000kHz   Target endian:                 little   Connecting to J-Link...   J-Link is connected.   Device "PN7642" selected.   Firmware: J-Link Ultra V5 compiled Dec 13 2023 14:34:48   Hardware: V5.00   S/N: 505001876   Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB   Checking target voltage...   Target voltage: 3.32 V   Listening on TCP/IP port 2339   Connecting to target...   Found SW-DP with ID 0x6BA02477   DPIDR: 0x6BA02477   CoreSight SoC-400 or earlier   Scanning AP map to find all available APs   AP[1]: Stopped AP scan as end of AP map seems to be reached   AP[0]: AHB-AP (IDR: 0x84770001)   Iterating through AP map to find AHB-AP to use   AP[0]: Skipped. Could not read CPUID register   Attach to CPU failed. Executing connect under reset.   DPIDR: 0x6BA02477   CoreSight SoC-400 or earlier   Scanning AP map to find all available APs   AP[1]: Stopped AP scan as end of AP map seems to be reached   AP[0]: AHB-AP (IDR: 0x84770001)   Iterating through AP map to find AHB-AP to use   AP[0]: Skipped. Could not read CPUID register   Could not find core in Coresight setup   Found SW-DP with ID 0x6BA02477   DPIDR: 0x6BA02477   CoreSight SoC-400 or earlier   Scanning AP map to find all available APs   AP[1]: Stopped AP scan as end of AP map seems to be reached   AP[0]: AHB-AP (IDR: 0x84770001)   Iterating through AP map to find AHB-AP to use   AP[0]: Skipped. Could not read CPUID register   Attach to CPU failed. Executing connect under reset.   DPIDR: 0x6BA02477   CoreSight SoC-400 or earlier   Scanning AP map to find all available APs   AP[1]: Stopped AP scan as end of AP map seems to be reached   AP[0]: AHB-AP (IDR: 0x84770001)   Iterating through AP map to find AHB-AP to use   AP[0]: Skipped. Could not read CPUID register   Could not find core in Coresight setup   ERROR: Could not connect to target. Re: PN7642 jlink error OK. Here is what I did to solve the issue. - After board operates in Mass-Storage mode - Delete the CRP_00.BIN(180KB) - Then copy one of the .bin application fw to the drive. - Then my J-link works again. Thanks Kelly for the hints. --Kenny Re: PN7642 jlink error OK. I think I found the documentation for Mass-storage mode to update the firmware. https://www.nxp.com/docs/en/application-note/AN13134.pdf page 54. However, I have no idea which file I should put. [kenny@MBP PN7642_FW_v02.02]$ ls -l total 1840 -rw-r--r--@ 1 kenny staff 207995 Oct 10 2023 NXP_SLDA.pdf -rw-r--r--@ 1 kenny staff 115 Oct 6 2023 PN7642_Default_AESChipKey.txt -rw-r--r--@ 1 kenny staff 5702 Oct 6 2023 PN7642_Default_App_RSAKey.pem -rw-r--r--@ 1 kenny staff 55036 Dec 15 2022 PN7642_SecureFW_SCR.pdf -rw-r--r--@ 1 kenny staff 40114 Oct 9 2023 PN7642_v02.F2.esfwu -rw-r--r--@ 1 kenny staff 1770 Oct 10 2023 ReadMe.txt -rw-r--r--@ 1 kenny staff 306336 Oct 9 2023 phDnldNfc_UpdateSeq_v02.02.c -rw-r--r--@ 1 kenny staff 256876 Oct 9 2023 phDnldNfc_UpdateSeq_v02.F2.c -rw-r--r--@ 1 kenny staff 47842 Oct 9 2023 pn7642_v02.02.esfwu -rw-r--r--@ 1 kenny staff 232 Oct 6 2023 version.txt I assume that should be a bin file format. Here is the screenshot when board operates in Mass-storage mode. --Kenny Re: PN7642 jlink error Hi Kelly, I believe I am using FW02.02. OK. I will try to update the firmware again. Do you have a quick reference for using Mass-storge mode to update the firmware? Thanks. --Kenny Re: PN7642 jlink error Hello @asknxp  What is your FW version? Or can you enter Mass-storage mode and update the firmware to the latest version (FW02.02)and try again. BR kelly

SJA1110 Linux DSA driver Hello,         Can you give me the CLI command to set SJA1110's port mode base on SJA1110's Linux DSA driver?        I can see that it provides support for other features of the switch like VLAN and PTP, but can't see how to config port-mode in the Linux-BSP UM file. Example of network interfaces when the SJA1110 DSA driver is loaded: root@s32g274aevb:~# ip addr show ... 7: pfe2: mtu 1504 qdisc noop state DOWN group default qlen 1000 link/ether 00:01:be:be:ef:33 brd ff:ff:ff:ff:ff:ff 8: enet_p1@pfe2: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:01:be:be:ef:33 brd ff:ff:ff:ff:ff:ff 9: enet_p3@pfe2: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:01:be:be:ef:33 brd ff:ff:ff:ff:ff:ff 10: enet_p4@pfe2: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:01:be:be:ef:33 brd ff:ff:ff:ff:ff:ff GoldVIP Re: SJA1110 Linux DSA driver Hello @xiaoshumiao, Since this post was already solved, I will answer your question in the post you last opened: 2088290. Best regards  Re: SJA1110 Linux DSA driver Hello, I have read the three posts you posted. Can you provide the download address of dsa for sja1110? I would be very grateful if you can provide some other tips on compiling or using dsa Re: SJA1110 Linux DSA driver Hello @yangjinzhuang, Good to read you again.  About your question, there are no specific terminal commands to interact with the SJA1110, there are several software abstraction layers between the SJA1110 driver and the command line utilities. With that said, I recommend you checking the Linux kernel documentation where you can see the following [https://docs.kernel.org/networking/dsa/dsa.html]: In this case the "switch" mentioned in the docs, is the SJA1110. This means that you can interact with it with the generally supported network commands. You can learn more about them by using the "--help" argument, for example: root@s32g399ardb3:~# ip --help Usage: ip [ OPTIONS ] OBJECT { COMMAND | help } ip [ -force ] -batch filename where OBJECT := { link | address | addrlabel | route | rule | neigh | ntable | tunnel | tuntap | maddress | mroute | mrule | monitor | xfrm | netns | l2tp | fou | macsec | tcp_metrics | token | netconf | ila | vrf | sr | nexthop | mptcp } OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] | -h[uman-readable] | -iec | -j[son] | -p[retty] | -f[amily] { inet | inet6 | mpls | bridge | link } | -4 | -6 | -I | -D | -M | -B | -0 | -l[oops] { maximum-addr-flush-attempts } | -br[ief] | -o[neline] | -t[imestamp] | -ts[hort] | -b[atch] [filename] | -rc[vbuf] [size] | -n[etns] name | -N[umeric] | -a[ll] | -c[olor]} root@s32g399ardb3:~# bridge --help Usage: bridge [ OPTIONS ] OBJECT { COMMAND | help } bridge [ -force ] -batch filename where OBJECT := { link | fdb | mdb | vlan | monitor } OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -o[neline] | -t[imestamp] | -n[etns] name | -c[ompressvlans] -color -p[retty] -j[son] } root@s32g399ardb3:~# ifconfig --help Usage: ifconfig [-a] [-v] [-s] [[ ] ] [add [/ ]] [del [/ ]] [[-]broadcast [ ]] [[-]pointopoint [ ]] [netmask ] [dstaddr ] [tunnel ] [outfill ] [keepalive ] [hw ] [mtu ] [[-]trailers] [[-]arp] [[-]allmulti] [multicast] [[-]promisc] [mem_start ] [io_addr ] [irq ] [media ] [txqueuelen ] [[-]dynamic] [up|down] ... =Hardware Type. List of possible hardware types: loop (Local Loopback) slip (Serial Line IP) cslip (VJ Serial Line IP) slip6 (6-bit Serial Line IP) cslip6 (VJ 6-bit Serial Line IP) adaptive (Adaptive Serial Line IP) ether (Ethernet) netrom (AMPR NET/ROM) tunnel (IPIP Tunnel) ppp (Point-to-Point Protocol) arcnet (ARCnet) dlci (Frame Relay DLCI) frad (Frame Relay Access Device) irda (IrLAP) =Address family. Default: inet List of possible address families: unix (UNIX Domain) inet (DARPA Internet) inet6 (IPv6) netrom (AMPR NET/ROM) root@s32g399ardb3:~# Other resources that you might find useful related to this topic: https://wiki.linuxfoundation.org/networking/iproute2  http://www.policyrouting.org/iproute2.doc.html#ss9.1  https://wiki.linuxfoundation.org/networking/bridge  https://man7.org/linux/man-pages/man8/ifconfig.8.html  Let me know if this information answers your question.

No soundcards found in ALSA device list Hi  NXP Here's my environment SoC:imx8qm audio chip:add2010 OS:yocto kirkstone Linux version:5.15.71 It show No soundcards found in ALSA device list But I cat /proc/asound/cards, the add2010 audio is registered successful I try to play audio file, and control audio volume are OK I don't understand why it show No soundcards found in boot log Booting from mmc ... 106496 bytes read in 2 ms (50.8 MiB/s) Loading hdp firmware from 0x000000009c000000 offset 0x0000000000002000 Loading hdp firmware Complete 129532 bytes read in 2 ms (61.8 MiB/s) ## Flattened Device Tree blob at 83000000 Booting using the fdt blob at 0x83000000 ERROR: reserving fdt memory region failed (addr=90400000 size=100000 flags=4) ERROR: reserving fdt memory region failed (addr=901ff000 size=1000 flags=4) Using Device Tree in place at 0000000083000000, end 00000000830229fb Disable pwm@5a190000 rsrc 188 not owned Disable clock-controller@5a590000 rsrc 188 not owned Disable jr@40000 rsrc 502 not owned Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000100 [0x410fd082] [ 0.000000] Linux version 5.15.71+ga753ba3716b0 (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 11.3.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Tue May 7 08:45:30 UTC 2024 [ 0.000000] Machine model: Freescale i.MX8QM CNH Pegasus [ 0.000000] efi: UEFI not found. [ 0.000000] Reserved memory: created CMA memory pool at 0x00000000c0000000, 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 0x0000000090400000, size 1 MiB [ 0.000000] OF: reserved mem: initialized node vdevbuffer, compatible id shared-dma-pool [ 0.000000] earlycon: lpuart32 at MMIO32 0x000000005a060000 (options '') [ 0.000000] printk: bootconsole [lpuart32] enabled [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000080200000-0x00000009ffffffff] [ 0.000000] NUMA: NODE_DATA [mem 0x9feffe800-0x9ff000fff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000080200000-0x00000000ffffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal [mem 0x0000000100000000-0x00000009ffffffff] [ 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 0x0000000084000000-0x00000000863fffff] [ 0.000000] node 0: [mem 0x0000000086400000-0x000000008fffffff] [ 0.000000] node 0: [mem 0x0000000090000000-0x000000009001ffff] [ 0.000000] node 0: [mem 0x0000000090020000-0x00000000900fefff] [ 0.000000] node 0: [mem 0x00000000900ff000-0x000000009011ffff] [ 0.000000] node 0: [mem 0x0000000090120000-0x00000000901fefff] [ 0.000000] node 0: [mem 0x00000000901ff000-0x00000000901fffff] [ 0.000000] node 0: [mem 0x0000000090200000-0x00000000903fffff] [ 0.000000] node 0: [mem 0x0000000090400000-0x00000000904fffff] [ 0.000000] node 0: [mem 0x0000000090500000-0x0000000091ffffff] [ 0.000000] node 0: [mem 0x0000000092000000-0x00000000920fffff] [ 0.000000] node 0: [mem 0x0000000092100000-0x00000000943fffff] [ 0.000000] node 0: [mem 0x0000000094400000-0x00000000951fffff] [ 0.000000] node 0: [mem 0x0000000095200000-0x00000000fdffffff] [ 0.000000] node 0: [mem 0x0000000880000000-0x000000088fffffff] [ 0.000000] node 0: [mem 0x0000000890000000-0x00000009ffffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000080200000-0x00000009ffffffff] [ 0.000000] On node 0, zone DMA: 512 pages in unavailable ranges [ 0.000000] On node 0, zone Normal: 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 s41368 r8192 d32360 u81920 [ 0.000000] Detected PIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: Spectre-v2 [ 0.000000] CPU features: detected: Spectre-v3a [ 0.000000] CPU features: detected: Spectre-BHB [ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 2055688 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: console=ttyLP0,115200 earlycon root=/dev/mmcblk0p2 rootwait rw cpufreq.default_governor=SCHEDUTIL [ 0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [ 0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] software IO TLB: mapped [mem 0x00000000bc000000-0x00000000c0000000] (64MB) [ 0.000000] Memory: 6667276K/8353792K available (17856K kernel code, 1530K rwdata, 7052K rodata, 2944K init, 534K bss, 703476K reserved, 983040K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, 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=6. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=6 [ 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] Root IRQ handler: gic_handle_irq [ 0.000000] GICv3: 16 PPIs implemented [ 0.000000] GICv3: CPU0: found redistributor 100 region 0:0x0000000051b80000 [ 0.000000] ITS: No ITS available, not enabling LPIs [ 0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns [ 0.000000] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns [ 0.008371] Console: colour dummy device 80x25 [ 0.012523] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000) [ 0.022730] pid_max: default: 32768 minimum: 301 [ 0.027361] LSM: Security Framework initializing [ 0.032020] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.039534] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.048501] rcu: Hierarchical SRCU implementation. [ 0.054088] EFI services will not be available. [ 0.058553] smp: Bringing up secondary CPUs ... [ 0.064497] CPU features: detected: ARM erratum 845719 [ 0.064520] Detected VIPT I-cache on CPU1 [ 0.064556] GICv3: CPU1: found redistributor 0 region 0:0x0000000051b00000 [ 0.064615] CPU1: Booted secondary processor 0x0000000000 [0x410fd034] [ 0.065506] Detected VIPT I-cache on CPU2 [ 0.065523] GICv3: CPU2: found redistributor 1 region 0:0x0000000051b20000 [ 0.065546] CPU2: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.066360] Detected VIPT I-cache on CPU3 [ 0.066378] GICv3: CPU3: found redistributor 2 region 0:0x0000000051b40000 [ 0.066401] CPU3: Booted secondary processor 0x0000000002 [0x410fd034] [ 0.067217] Detected VIPT I-cache on CPU4 [ 0.067235] GICv3: CPU4: found redistributor 3 region 0:0x0000000051b60000 [ 0.067258] CPU4: Booted secondary processor 0x0000000003 [0x410fd034] [ 0.068075] Detected PIPT I-cache on CPU5 [ 0.068095] GICv3: CPU5: found redistributor 101 region 0:0x0000000051ba0000 [ 0.068118] CPU5: Booted secondary processor 0x0000000101 [0x410fd082] [ 0.068165] smp: Brought up 1 node, 6 CPUs [ 0.164104] SMP: Total of 6 processors activated. [ 0.168790] CPU features: detected: 32-bit EL0 Support [ 0.173920] CPU features: detected: 32-bit EL1 Support [ 0.179040] CPU features: detected: CRC32 instructions [ 0.200003] CPU: All CPU(s) started at EL2 [ 0.203798] alternatives: patching kernel code [ 0.209125] devtmpfs: initialized [ 0.219973] KASLR disabled due to lack of seed [ 0.224182] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.233816] futex hash table entries: 2048 (order: 5, 131072 bytes, linear) [ 0.250911] pinctrl core: initialized pinctrl subsystem [ 0.256148] DMI not present or invalid. [ 0.259968] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.268601] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations [ 0.275778] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [ 0.283690] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [ 0.291395] audit: initializing netlink subsys (disabled) [ 0.296860] audit: type=2000 audit(0.184:1): state=initialized audit_enabled=0 res=1 [ 0.297154] thermal_sys: Registered thermal governor 'step_wise' [ 0.304475] thermal_sys: Registered thermal governor 'power_allocator' [ 0.310820] cpuidle: using governor menu [ 0.321037] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.327783] ASID allocator initialised with 65536 entries [ 0.333868] Serial: AMBA PL011 UART driver [ 0.337663] imx mu driver is registered. [ 0.341535] imx rpmsg driver is registered. [ 0.377225] platform bus@56240000:ldb@562410e0: Fixing up cyclic dependency with 56180000.dpu [ 0.388074] platform 56228000.dsi_host: Fixing up cyclic dependency with 56180000.dpu [ 0.397864] platform lvds1_panel: Fixing up cyclic dependency with bus@56240000:ldb@562410e0 [ 0.413542] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 0.419911] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages [ 0.426590] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 0.433278] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages [ 0.440922] cryptd: max_cpu_qlen set to 1000 [ 0.448091] ACPI: Interpreter disabled. [ 0.452467] iommu: Default domain type: Translated [ 0.457052] iommu: DMA domain TLB invalidation policy: strict mode [ 0.463418] vgaarb: loaded [ 0.466098] SCSI subsystem initialized [ 0.469903] usbcore: registered new interface driver usbfs [ 0.475182] usbcore: registered new interface driver hub [ 0.480475] usbcore: registered new device driver usb [ 0.486766] mc: Linux media interface: v0.10 [ 0.490718] videodev: Linux video capture interface: v2.00 [ 0.496207] pps_core: LinuxPPS API ver. 1 registered [ 0.501120] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 0.510245] PTP clock support registered [ 0.514169] EDAC MC: Ver: 3.0.0 [ 0.518647] FPGA manager framework [ 0.521747] --> alsa_sound_init [ 0.524835] --> snd_minor_info_init [ 0.528309] --> snd_card_info_init [ 0.531690] [ 0.533168] Advanced Linux Sound Architecture Driver Initialized. [ 0.539516] Bluetooth: Core ver 2.22 [ 0.542823] NET: Registered PF_BLUETOOTH protocol family [ 0.548112] Bluetooth: HCI device and connection manager initialized [ 0.554454] Bluetooth: HCI socket layer initialized [ 0.559318] Bluetooth: L2CAP socket layer initialized [ 0.564364] Bluetooth: SCO socket layer initialized [ 0.570016] imx-scu scu: NXP i.MX SCU Initialized [ 0.590389] imx8qm-pinctrl scu:pinctrl: initialized IMX pinctrl driver [ 0.598277] clocksource: Switched to clocksource arch_sys_counter [ 0.604151] VFS: Disk quotas dquot_6.6.0 [ 0.607980] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.614899] pnp: PnP ACPI: disabled [ 0.644440] NET: Registered PF_INET protocol family [ 0.649370] IP idents hash table entries: 131072 (order: 8, 1048576 bytes, linear) [ 0.658667] tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear) [ 0.666907] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.674594] TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear) [ 0.682758] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear) [ 0.690393] TCP: Hash tables configured (established 65536 bind 65536) [ 0.696691] UDP hash table entries: 4096 (order: 5, 131072 bytes, linear) [ 0.703460] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear) [ 0.710759] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.716549] RPC: Registered named UNIX socket transport module. [ 0.722129] RPC: Registered udp transport module. [ 0.726829] RPC: Registered tcp transport module. [ 0.731504] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.737940] PCI: CLS 0 bytes, default 64 [ 0.742483] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available [ 0.750779] kvm [1]: IPA Size Limit: 40 bits [ 0.755340] kvm [1]: vgic-v2@52020000 [ 0.758684] kvm [1]: GIC system register CPU interface enabled [ 0.764609] kvm [1]: vgic interrupt IRQ9 [ 0.768531] kvm [1]: Hyp mode initialized successfully [ 0.776542] workingset: timestamp_bits=42 max_order=21 bucket_order=0 [ 0.785471] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.791314] NFS: Registering the id_resolver key type [ 0.796042] Key type id_resolver registered [ 0.800190] Key type id_legacy registered [ 0.804222] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.810877] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... [ 0.818272] jffs2: version 2.2. (NAND) c 2001-2006 Red Hat, Inc. [ 0.824534] 9p: Installing v9fs 9p2000 file system support [ 0.854265] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243) [ 0.861333] io scheduler mq-deadline registered [ 0.865848] io scheduler kyber registered [ 0.881394] EINJ: ACPI disabled. [ 1.054147] mxs-dma 5b810000.dma-apbh: initialized [ 1.061687] Bus freq driver module loaded [ 1.070643] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.079220] 5a060000.serial: ttyLP0 at MMIO 0x5a060010 (irq = 58, base_baud = 5000000) is a FSL_LPUAR[ 1.088376] printk: console [ttyLP0] enabled [ 1.088376] printk: console [ttyLP0] enabled [ 1.096801] printk: bootconsole [lpuart32] disabled [ 1.096801] printk: bootconsole [lpuart32] disabled [ 1.107010] 5a080000.serial: ttyLP2 at MMIO 0x5a080010 (irq = 59, base_baud = 5000000) is a FSL_LPUART [ 1.116824] 5a090000.serial: ttyLP3 at MMIO 0x5a090010 (irq = 60, base_baud = 5000000) is a FSL_LPUART [ 1.126772] 5a0a0000.serial: ttyLP4 at MMIO 0x5a0a0010 (irq = 85, base_baud = 5000000) is a FSL_LPUART [ 1.137630] arm-smmu 51400000.iommu: probing hardware configuration... [ 1.144183] arm-smmu 51400000.iommu: SMMUv2 with: [ 1.148891] arm-smmu 51400000.iommu: stage 1 translation [ 1.154293] arm-smmu 51400000.iommu: stage 2 translation [ 1.159697] arm-smmu 51400000.iommu: nested translation [ 1.165014] arm-smmu 51400000.iommu: stream matching with 32 register groups [ 1.172159] arm-smmu 51400000.iommu: 32 context banks (0 stage-2 only) [ 1.178781] arm-smmu 51400000.iommu: Supported page sizes: 0x61311000 [ 1.185308] arm-smmu 51400000.iommu: Stage-1: 48-bit VA -> 48-bit IPA [ 1.191841] arm-smmu 51400000.iommu: Stage-2: 48-bit IPA -> 48-bit PA [ 1.198437] arm-smmu 51400000.iommu: preserved 0 boot mappings [ 1.283399] loop: module loaded [ 1.288345] of_reserved_mem_lookup() returned NULL [ 1.293207] megasas: 07.717.02.00-rc1 [ 1.299118] imx ahci driver is registered. [ 1.311195] tun: Universal TUN/TAP device driver, 1.6 [ 1.316392] CAN device driver interface [ 1.323928] thunder_xcv, ver 1.0 [ 1.327204] thunder_bgx, ver 1.0 [ 1.330457] nicpf, ver 1.0 [ 1.336837] hclge is initializing [ 1.340194] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [ 1.347424] hns3: Copyright (c) 2017 Huawei Corporation. [ 1.352798] e1000: Intel(R) PRO/1000 Network Driver [ 1.357680] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 1.363447] e1000e: Intel(R) PRO/1000 Network Driver [ 1.368471] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 1.374418] igb: Intel(R) Gigabit Ethernet Network Driver [ 1.379822] igb: Copyright (c) 2007-2014 Intel Corporation. [ 1.385442] igbvf: Intel(R) Gigabit Virtual Function Network Driver [ 1.391719] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 1.398039] sky2: driver version 1.30 [ 1.402813] usbcore: registered new interface driver r8152 [ 1.408488] VFIO - User Level meta-driver version: 0.3 [ 1.417102] cdns3-imx 5b110000.usb: Adding to iommu group 0 [ 1.424242] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.430801] ehci-pci: EHCI PCI platform driver [ 1.435304] ehci-platform: EHCI generic platform driver [ 1.441030] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.447229] ohci-pci: OHCI PCI platform driver [ 1.451707] ohci-platform: OHCI generic platform driver [ 1.458013] usbcore: registered new interface driver uas [ 1.463369] usbcore: registered new interface driver usb-storage [ 1.469428] usbcore: registered new interface driver usbserial_generic [ 1.475967] usbserial: USB Serial support registered for generic [ 1.481991] usbcore: registered new interface driver ftdi_sio [ 1.487791] usbserial: USB Serial support registered for FTDI USB Serial Device [ 1.495142] usbcore: registered new interface driver usb_serial_simple [ 1.501682] usbserial: USB Serial support registered for carelink [ 1.507792] usbserial: USB Serial support registered for zio [ 1.513463] usbserial: USB Serial support registered for funsoft [ 1.519483] usbserial: USB Serial support registered for flashloader [ 1.525851] usbserial: USB Serial support registered for google [ 1.531791] usbserial: USB Serial support registered for libtransistor [ 1.538336] usbserial: USB Serial support registered for vivopay [ 1.544356] usbserial: USB Serial support registered for moto_modem [ 1.550637] usbserial: USB Serial support registered for motorola_tetra [ 1.557314] usbserial: USB Serial support registered for nokia [ 1.563247] usbserial: USB Serial support registered for novatel_gps [ 1.569697] usbserial: USB Serial support registered for hp4x [ 1.575526] usbserial: USB Serial support registered for suunto [ 1.581486] usbserial: USB Serial support registered for siemens_mpi [ 1.587920] usbcore: registered new interface driver usb_ehset_test [ 1.601722] input: sc-powerkey as /devices/platform/sc-powerkey/input/input0 [ 1.609432] i2c_dev: i2c /dev entries driver [ 1.621750] amphion-vpu-core 2d080000.vpu-core: [0] = decoder [ 1.629359] amphion-vpu-core 2d090000.vpu-core: [1] = encoder [ 1.637302] amphion-vpu-core 2d0a0000.vpu-core: [2] = encoder [ 1.650649] Bluetooth: HCI UART driver ver 2.3 [ 1.655112] Bluetooth: HCI UART protocol H4 registered [ 1.660253] Bluetooth: HCI UART protocol BCSP registered [ 1.665583] Bluetooth: HCI UART protocol LL registered [ 1.670724] Bluetooth: HCI UART protocol ATH3K registered [ 1.676134] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 1.682638] Bluetooth: HCI UART protocol Broadcom registered [ 1.688308] Bluetooth: HCI UART protocol QCA registered [ 1.697268] sdhci: Secure Digital Host Controller Interface driver [ 1.703488] sdhci: Copyright(c) Pierre Ossman [ 1.709116] Synopsys Designware Multimedia Card Interface Driver [ 1.716387] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.724729] sdhci-esdhc-imx 5b010000.mmc: Adding to iommu group 1 [ 1.731030] ledtrig-cpu: registered to indicate activity on CPUs [ 1.738653] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping .... [ 1.745198] usbcore: registered new interface driver usbhid [ 1.750780] usbhid: USB HID core driver [ 1.756850] mxc-isi 58100000.isi: mxc_isi.0 registered successfully [ 1.763684] mxc-isi 58110000.isi: mxc_isi.1 registered successfully [ 1.764207] mmc0: SDHCI controller on 5b010000.mmc [5b010000.mmc] using ADMA [ 1.770546] mxc-isi 58120000.isi: mxc_isi.2 registered successfully [ 1.783868] mxc-isi 58130000.isi: mxc_isi.3 registered successfully [ 1.798590] cs_system_cfg: CoreSight Configuration manager initialised [ 1.807502] optee: probing for conduit method. [ 1.811975] optee: revision 3.19 (00919403) [ 1.812620] optee: initialized driver [ 1.825278] Galcore version 6.4.3.p4.398061 [ 1.832264] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 1.839290] mmcblk0: mmc0:0001 AAM20F 59.3 GiB [ 1.842541] [drm] Initialized vivante 1.0.0 20170808 for 80000000.imx8_gpu1_ss on minor 0 [ 1.852201] mmcblk0: p1 p2 [ 1.855070] --> snd_register_device [ 1.855549] mmcblk0boot0: mmc0:0001 AAM20F 31.5 MiB [ 1.861427] NET: Registered PF_LLC protocol family [ 1.864797] mmcblk0boot1: mmc0:0001 AAM20F 31.5 MiB [ 1.868670] NET: Registered PF_INET6 protocol family [ 1.874384] mmcblk0rpmb: mmc0:0001 AAM20F 4.00 MiB, chardev (234:0) [ 1.878761] Segment Routing with IPv6 [ 1.888262] In-situ OAM (IOAM) with IPv6 [ 1.892220] NET: Registered PF_PACKET protocol family [ 1.897296] can: controller area network core [ 1.901683] NET: Registered PF_CAN protocol family [ 1.906490] can: raw protocol [ 1.909467] can: broadcast manager protocol [ 1.913659] can: netlink gateway - max_hops=1 [ 1.918139] Bluetooth: RFCOMM TTY layer initialized [ 1.923023] Bluetooth: RFCOMM socket layer initialized [ 1.928192] Bluetooth: RFCOMM ver 1.11 [ 1.931953] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 1.937264] Bluetooth: BNEP filters: protocol multicast [ 1.942510] Bluetooth: BNEP socket layer initialized [ 1.947495] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 1.953419] Bluetooth: HIDP socket layer initialized [ 1.958486] 8021q: 802.1Q VLAN Support v1.8 [ 1.962689] lib80211: common routines for IEEE802.11 drivers [ 1.968411] 9pnet: Installing 9P2000 support [ 1.972705] tsn generic netlink module v1 init... [ 1.977449] Key type dns_resolver registered [ 2.000893] mxs_phy 5b100000.usbphy: supply phy-3p0 not found, using dummy regulator [ 2.022823] imx-lpi2c 58226000.i2c: use pio mode [ 2.027819] i2c 2-0044: Fixing up cyclic dependency with 58227000.csi [ 2.058451] isl7998x 2-0044: isl7998x_write_reg:write reg error:reg=ff,val= 0 [ 2.066060] isl7998x 2-0044: In isl7998x_hardware_init() [ 2.090352] isl7998x 2-0044: isl7998x_data->num_lanes=2 [ 2.131416] isl7998x 2-0044: isl7998x is found, id = 0x87, name isl7998x 2-0044 [ 2.138890] i2c i2c-2: LPI2C adapter registered [ 2.144390] gpio-430 (scl): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 2.153380] imx-lpi2c 5a810000.i2c: using scl,sda for recovery [ 2.159228] imx-lpi2c 5a810000.i2c: use pio mode [ 2.167555] hwmon hwmon6: temp1_input not attached to any thermal zone [ 2.174106] lm75 3-0048: hwmon6: sensor 'tmp75' [ 2.179289] elan_ktf 3-0016: [elan] enter elants_i2c_probe...v.0.0.14-17 [ 2.182139] rtc-ds1307 3-0068: registered as rtc0 [ 2.186283] elan_ktf 3-0016: supply vcc33 not found, using dummy regulator [ 2.191036] rtc-ds1307 3-0068: setting system clock to 2000-01-20T17:52:57 UTC (948390777) [ 2.197916] elan_ktf 3-0016: supply vccio not found, using dummy regulator [ 2.206024] i2c 3-0051: Fixing up cyclic dependency with 5b130000.usb [ 2.213111] elan_ktf 3-0016: [elan] ts->intr_gpio = 310. [ 2.224835] elan_ktf 3-0016: [elan] irq num = 459. [ 2.229653] elan_ktf 3-0016: Power_on [ 2.230183] i2c i2c-3: LPI2C adapter registered [ 2.239058] imx-lpi2c 5a830000.i2c: use pio mode [ 2.244242] msi-mcu 4-0020: ++ mcu_probe ++ << i2c_device_probe [ 2.250212] msi-mcu 4-0020: got channel select gpio. [ 2.255194] msi-mcu 4-0020: create file ok: 0 [ 2.259562] msi-mcu 4-0020: create file ok: 0 [ 2.263932] msi-mcu 4-0020: create file ok: 0 [ 2.268302] msi-mcu 4-0020: create file ok: 0 [ 2.272746] msi-mcu 4-0020: register backlight pwm, 0 [ 2.277855] msi-mcu 4-0020: == init_rgb_pwm == register led: 0 [ 2.283741] msi-mcu 4-0020: == init_rgb_pwm == register led: 0 [ 2.289623] msi-mcu 4-0020: == init_rgb_pwm == register led: 0 [ 2.295465] msi-mcu 4-0020: == init_runtime_cvbs_input == create file ok: 0 [ 2.302439] msi-mcu 4-0020: ++ init_wakeup_source ++ got IRQ 398 [ 2.308749] msi-mcu 4-0020: -- init_wakeup_source -- request irq: 0 [ 2.315111] msi-mcu 4-0020: -- mcu_probe -- [ 2.319722] ms5629-adc 4-0021: ms5629-adc, dev_info [ 2.325029] at24 4-0056: supply vcc not found, using dummy regulator [ 2.332117] at24 4-0056: read 1@0 --> 0 (4294892826) [ 2.337122] at24 4-0056: 1024 byte br24g64 EEPROM, writable, 32 bytes/write [ 2.362888] random: crng init done [ 2.369007] shx goin add2010_probe start [ 2.373110] client->addr = 0x30 [ 2.376346] add2010 4-0030: supply dvdd not found, using dummy regulator [ 2.383124] add2010 4-0030: supply pvdd not found, using dummy regulator [ 2.390309] devm_snd_soc_register_component ret = 0 [ 2.395206] shx goin add2010_probe end [ 2.399602] add2010 chip_id = 0xc8 [ 2.403077] i2c i2c-4: LPI2C adapter registered [ 2.411355] pwm-backlight lvds_backlight@0: supply power not found, using dummy regulator [ 2.421028] pwm-backlight lvds_backlight@1: supply power not found, using dummy regulator [ 2.438492] dpu-core 56180000.dpu: driver probed [ 2.445060] dpu-core 57180000.dpu: driver probed [ 2.546467] [elan] enter elants_i2c_initialize.... [ 2.554179] elan_ktf 3-0016: 43 00 02 01 20 ff ff ff [ 2.559153] elan_ktf 3-0016: ff ff ff ff ff ff ff ff [ 2.564119] elan_ktf 3-0016: ff ff ff ff ff ff ff ff [ 2.569090] elan_ktf 3-0016: ff ff ff ff ff ff ff ff [ 2.574062] elan_ktf 3-0016: ff ff ff ff ff ff ff ff [ 2.579027] elan_ktf 3-0016: [elan] Johnny: Receive 0x20, Gen7, in Normal Mode. [ 2.589105] elan_ktf 3-0016: [elan] elants_i2c_query_hw_version: (Firmware ID) 43 00 02 04 52 f4 33 01 [ 2.601083] elan_ktf 3-0016: [elan] elants_i2c_query_bc_version: (BC version) 43 00 02 04 52 19 c0 81 [ 2.613268] elan_ktf 3-0016: [elan] elants_i2c_query_fw_version: (Firmware version) 43 00 02 04 52 08 30 81 [ 2.625744] elan_ktf 3-0016: [elan] elants_i2c_query_test_version: (test version) 43 00 02 04 52 e0 00 04 [ 2.638006] elan_ktf 3-0016: [elan] elants_i2c_query_ts_info: (get resolution) 43 00 02 11 9b 2c 32 1c [ 2.650002] elan_ktf 3-0016: [elan] elants_i2c_query_ts_info: (get osr) 43 00 02 04 52 d6 00 30 [ 2.661456] elan_ktf 3-0016: [elan] elants_i2c_query_ts_info: (get physical scan) 43 00 02 04 52 d7 01 26 [ 2.673682] elan_ktf 3-0016: [elan] elants_i2c_query_ts_info: ts->cols=28, ts->rows=50, x_max=2352, x_res=8, y_max=1296, y_res=8 [ 2.685268] elan_ktf 3-0016: [elan]init delayed work for elants_auto_update [ 2.692451] input: Elan Touchscreen as /devices/platform/bus@5a000000/5a810000.i2c/i2c-3/3-0016/input/input1 [ 2.702366] elan_ktf 3-0016: set irqflags = IRQF_TRIGGER_LOW [ 2.708229] elan_ktf 3-0016: [elan] misc_register finished!! [ 2.911719] tcan4x5x spi0.0: m_can device registered (irq=405, version=32) [ 2.918610] tcan4x5x spi0.0 can3: TCAN4X5X successfully initialized. [ 2.925739] fec 5b040000.ethernet: Adding to iommu group 2 [ 3.038889] pps pps0: new PPS source ptp0 [ 3.043774] fec 5b040000.ethernet: Invalid MAC address: 00:00:00:00:00:00 [ 3.050820] fec 5b040000.ethernet: Using random MAC address: e2:cb:df:79:36:f1 [ 3.060404] fec 5b040000.ethernet eth0: registered PHC device 0 [ 3.067430] fec 5b050000.ethernet: Adding to iommu group 2 [ 3.178755] pps pps1: new PPS source ptp1 [ 3.183648] fec 5b050000.ethernet: Invalid MAC address: 00:00:00:00:00:00 [ 3.190752] fec 5b050000.ethernet: Using random MAC address: 3a:87:9a:fe:28:7f [ 3.200944] fec 5b050000.ethernet eth1: registered PHC device 1 [ 3.207910] cdns-usb3 5b130000.usb: Adding to iommu group 0 [ 3.215033] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller [ 3.220554] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1 [ 3.229032] xhci-hcd xhci-hcd.1.auto: hcc params 0x200073c8 hci version 0x100 quirks 0x0000002200018010 [ 3.238488] xhci-hcd xhci-hcd.1.auto: irq 237, io mem 0x5b130000 [ 3.244882] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller [ 3.250390] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2 [ 3.258077] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed [ 3.265249] hub 1-0:1.0: USB hub found [ 3.269036] hub 1-0:1.0: 1 port detected [ 3.273163] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.281510] hub 2-0:1.0: USB hub found [ 3.285290] hub 2-0:1.0: 1 port detected [ 3.293450] ci_hdrc ci_hdrc.0: EHCI Host Controller [ 3.298365] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 3 [ 3.318297] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 [ 3.324045] hub 3-0:1.0: USB hub found [ 3.327828] hub 3-0:1.0: 1 port detected [ 3.354289] mxc-mipi-csi2 58227000.csi: lanes: 2, name: mxc-mipi-csi2.0 [ 3.366730] xhci-hcd xhci-hcd.1.auto: remove, state 1 [ 3.371813] usb usb2: USB disconnect, device number 1 [ 3.377292] xhci-hcd xhci-hcd.1.auto: USB bus 2 deregistered [ 3.383032] xhci-hcd xhci-hcd.1.auto: remove, state 84 [ 3.388176] usb usb1: USB disconnect, device number 1 [ 3.399880] xhci-hcd xhci-hcd.1.auto: USB bus 1 deregistered [ 3.409619] imx-lpi2c 56226000.i2c: use pio mode [ 3.414527] i2c 5-0062: Fixing up cyclic dependency with external_panel [ 3.421179] i2c 5-0062: Fixing up cyclic dependency with 56228000.dsi_host [ 3.428338] max96789 5-0062: max96789_probe : max96789_probe start [ 3.434524] max96789_probe : max96789_probe start [ 3.464484] max96789 5-0062: drm_of_find_panel_or_bridge(dev->of_node, 2, 0, &panel, &panel_bridge) fail [ 3.473977] max96789 5-0062: max96789_probe : max96789_parse_dt fail [ 3.480462] i2c i2c-5: LPI2C adapter registered [ 3.485855] panel-simple external_panel: Specify missing connector_type [ 3.486040] imx6q-pcie 5f000000.pcie: supply epdev_on not found, using dummy regulator [ 3.493940] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops) [ 3.500826] imx6q-pcie 5f000000.pcie: No cache used with register defaults set! [ 3.508795] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.5 (ops dpu_bliteng_ops) [ 3.524367] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops) [ 3.531891] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops) [ 3.539437] imx-drm display-subsystem: bound imx-dpu-crtc.3 (ops dpu_crtc_ops) [ 3.542289] imx6q-pcie 5f000000.pcie: PCIe PLL is locked. [ 3.547111] imx-drm display-subsystem: bound imx-dpu-crtc.4 (ops dpu_crtc_ops) [ 3.552229] imx6q-pcie 5f000000.pcie: iATU unroll: disabled [ 3.564922] imx6q-pcie 5f000000.pcie: Detected iATU regions: 6 outbound, 6 inbound [ 3.572514] imx6q-pcie 5f000000.pcie: host bridge /bus@5f000000/pcie@0x5f000000 ranges: [ 3.580576] imx6q-pcie 5f000000.pcie: IO 0x006ff80000..0x006ff8ffff -> 0x0000000000 [ 3.588790] usb 3-1: new high-speed USB device number 2 using ci_hdrc [ 3.595277] imx6q-pcie 5f000000.pcie: MEM 0x0060000000..0x006fefffff -> 0x0060000000 [ 3.596142] imx-drm display-subsystem: bound bus@56240000:ldb@562410e0 (ops imx8qm_ldb_ops) [ 3.603605] imx6q-pcie 5f000000.pcie: iATU unroll: disabled [ 3.612149] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /bus@56220000/dsi_host@56228000 to encoder DSI-149: -517 [ 3.617434] imx6q-pcie 5f000000.pcie: Detected iATU regions: 6 outbound, 6 inbound [ 3.639547] max96789 5-0062: max96789_probe : max96789_probe start [ 3.645770] max96789_probe : max96789_probe start [ 3.674646] max96789 5-0062: max96789_probe : max96789_probe successfully [ 3.683334] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops) [ 3.691761] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.5 (ops dpu_bliteng_ops) [ 3.700383] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops) [ 3.707911] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops) [ 3.715620] imx-drm display-subsystem: bound imx-dpu-crtc.3 (ops dpu_crtc_ops) [ 3.717492] imx6q-pcie 5f000000.pcie: Link up [ 3.723306] imx-drm display-subsystem: bound imx-dpu-crtc.4 (ops dpu_crtc_ops) [ 3.735227] imx-drm display-subsystem: bound bus@56240000:ldb@562410e0 (ops imx8qm_ldb_ops) [ 3.744574] nwl-dsi 56228000.dsi_host: [drm:nwl_dsi_host_attach] lanes=4, format=0x0 flags=0x3 [ 3.753040] hub 3-1:1.0: USB hub found [ 3.753423] imx-drm display-subsystem: bound 56228000.dsi_host (ops nwl_dsi_component_ops) [ 3.757382] hub 3-1:1.0: 2 ports detected [ 3.765767] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1 [ 3.780967] imx-drm display-subsystem: [drm] fb0: imx-drmdrmfb frame buffer device [ 3.792732] debugfs: Directory 'lvds1' with parent 'pm_genpd' already present! [ 3.800074] debugfs: Directory 'mipi1-i2c1' with parent 'pm_genpd' already present! [ 3.808058] debugfs: Directory 'mipi1-i2c0' with parent 'pm_genpd' already present! [ 3.815748] debugfs: Directory 'mipi1-pwm0' with parent 'pm_genpd' already present! [ 3.823417] debugfs: Directory 'mipi1' with parent 'pm_genpd' already present! [ 3.827227] imx6q-pcie 5f000000.pcie: Link up [ 3.835028] imx6q-pcie 5f000000.pcie: Link up, Gen2 [ 3.836912] isi-m2m 58100000.isi:m2m_device: Register m2m success for ISI.0 [ 3.873117] ALSA device list: [ 3.876094] No soundcards found. root@cnh-pegasus:~# cat /proc/asound/cards 0 [add2010 ]: simple-card - add2010                       add2010 root@cnh-pegasus:~# ls /dev/snd/ by-path controlC0 pcmC0D0p timer Thanks Re: No soundcards found in ALSA device list Do not worry about it, I have test on our EVK BOARD, found the No sound cards found the same. Because not sound card are in using, I think it is the reason. The same with you, it is not the error or failed information, you can ignore it. But in your log you can see it is already added success. You can also see that all the sound card support in my side: So it is OK in your side, no problem. Re: No soundcards found in ALSA device list Hi @Rita_Wang  We are using the board designed by ourselves Do you have any suggestion? Thanks Re: No soundcards found in ALSA device list Are you using NXP reference board or the board you designed yourself?

S32K312 cannot enter CAN error callback problem Hello, the environment is DS3.5+RTD3.0.0 In the routine S32K312_CAN_TX_RX_using_MB_Interrupt, when the CAN line is disconnected or CANH and CANL are shorted, error_callback() is not entered. In main_can_task(), FLEXCAN_STATUS_BUSY is read as 2 (busy state). What kind of error can enter error_callback()? Please help analyze it. The demo program is attached. Thanks!

S32K312 不能进入CAN error callback 问题 你好，环境的DS3.5+RTD3.0.0  例程S32K312_CAN_TX_RX_using_MB_Interrupt中，当把CAN线断开，或把CANH与CANL短接，没有进入error_callback()中，在main_can_task()中读取FLEXCAN_STATUS_BUSY为2（busy状态），请问发生什么样错误才能进入error_callback()，请帮忙分析一下，。 demo例程如附件。 Thanks！ Re: S32K312 不能进入CAN error callback 问题 Hi@Bert2023 没有使能相应的错误中断位，你可以使用下面这些API使能相应的错误中断位: FlexCAN_Ip_SetErrorInt_Privileged(INST_FLEXCAN_0,FLEXCAN_IP_INT_RX_WARNING,1); FlexCAN_Ip_SetErrorInt_Privileged(INST_FLEXCAN_0,FLEXCAN_IP_INT_TX_WARNING,1); FlexCAN_Ip_SetErrorInt_Privileged(INST_FLEXCAN_0,FLEXCAN_IP_INT_ERR,1); FlexCAN_Ip_SetErrorInt_Privileged(INST_FLEXCAN_0,FLEXCAN_IP_INT_ERR_FAST,1); FlexCAN_Ip_SetErrorInt_Privileged(INST_FLEXCAN_0,FLEXCAN_IP_INT_BUSOFF,1);

Gui Guider for stm32u5g9 (英語) 私はMIPI DBIインターフェースを備えた320x240ディスプレイに取り組んでいます。ディスプレイとのインターフェースにSTM32U5G9を使用しています。Gui Guiderを使用してGUIを作成できますか?はいの場合、stm32u5g9で動作させるために従う必要がある手順は何ですか 日時:Gui Guider for stm32u5g9 わかりました。 迅速なサポートをありがとうございました。

MCUXpresso for VSCodeとZephyrの関係は何ですか? こんにちは iMXRT10xxシリーズプロセッサで新しいプロジェクトを開始したいです。 私はVSCodeのためにMCUXpressoとMCUXpressoまたはVSCodeを使用できることを理解しています。 それらは同じですが、IDEが異なるだけですか? それとも、ZephyrとMCUXpressorに基づくVSCode用のMCUXpressoはそうではありませんか? Re:MCUXpresso for VSCodeとZephyrの関係は何ですか? では、拡張機能でVSCodeを使用する場合、MCUXpressまたはZephyrのどちらかを選択できますか? 私が正しく理解していれば、MCUXpressはUartsやI2Cなどのチップリソースの設定を処理します。 私の知る限り、Zephyrも同じことをしています(より一般的な方法で? それで、私はそれらの中から選択する必要がありますか?

PT2001 Vboost LS7 G 卡在 由于 dram2.bin 和目标电压较高，我得到恒定电压，因此我降低了电压和电流切换点，并且没有电流。文档不清楚，我假设电压水平始终有效，目标是 20V 关闭 18V 打开以及 1A 关闭 0.5A 打开。注意图 6 显示不存在的 D_LS7，为什么我们会被下划线入侵？比连字符或减号更安全？谁对 DLS7 或 LS7D 有问题？ 电磁阀控制器 回复：PT2001 Vboost LS7 G 卡在 我不知道为什么，但写这些请求确实有帮助。修改为 20Voff 18Von、2Aoff 1Aon，并且......现在可以工作了。 🙂

MCUXpresso for VSCode 和 Zephyr 之间有什么关系？ 你好， 我想用iMXRT10xx系列处理器启动一个新项目。 我知道我可以将 MCUXpresso 或 VSCode 与 MCUXpresso 用于 VSCode。 它们是相同的，只是 IDE 不同吗？ 或者 MCUXpresso for VSCode 是基于 Zephyr 而 MCUXpressor 不是？ 回复：MCUXpresso for VSCode 和 Zephyr 之间有什么关系？ 那么当使用带有扩展的 VSCode 时，我可以在 MCUXpress 或 Zephyr 之间进行选择吗？ 如果我理解正确的话，MCUXpress 将负责配置 Uarts 和 I2C 等芯片资源。 据我所知，Zephyr 也做同样的事情（以更通用的方式？）。 所以我必须在它们之间做出选择吗？

S32K388 RMII Reference Clock Good Morning,  I have an issue with the S32K388 on the RMII interface of a custom board.  The S32K388 is setup as the MAC and is connected to a PHY.  The issue is related with 50MHz reference clock because I want to generate it internally and send it to the PHY using the gmac1_mii_rmii_rgmii_tx_clk pin. All the examples that I have found use an external crystal oscillator (ex. S32K324 MII mode - NXP Community) but I think it is not necessarily required after reading this in the RM: I wasn't able to find in the RM how achieve it.  Any help would be appreciated! Thanks in advance! Re: S32K388 RMII Reference Clock Hi @javivalero , In theory, it is possible to generate the clock reference from the internal PLL and connect it to the gmac1_mii_rmii_rgmii_tx_clk (PTC1) pin. However this was thought for RGMII mode, not RMII. Best regards, Pavel Re: S32K388 RMII Reference Clock Hi @javivalero , what PHY are you using? Could you shared schematic of your board? Best regards, Pavel

PT2001 Vboost LS7 G stuck on With the dram2.bin and target voltage high, I am getting constant on, so I reduced both voltage and current switching points, and no current. Documentation is unclear, I assume the Voltage levels are always effective, and a target 20V off 18V on and for 1A off 0.5A on. Note Figure 6. shows non existant D_LS7, why have we been invaded by the underscore? Safer than hyphen or minus? Who has a problem with DLS7 or LS7D? Solenoid Controller Re: PT2001 Vboost LS7 G stuck on I dont know why but writing these request really help. Revised to 20Voff 18Von, 2Aoff 1Aon, and ...... works now. 🙂

Freemaster : How to access to registry ? I would like to know if Freemaster allows access to ARM and hardware registers during the execution of embedded code. Can we perform a memory dump of an application and thus have access to the registers, and deduce their hardware representation? Re: Freemaster : How to access to registry ? Hello,  no, you cannot sample Core registers from FreeMASTER. Sampling register values over JTAG is not supported. And in case of communication over UART, CAN or another driver, sampling register values would be quite useless as most of the values would be set to values related to the driver execution. Sampling other core registers and special registers could be useful in some cases. You would need to mirror their values to variables first (or periodically) and then sample the variables. Regards, Michal I guess it would make no sense to sample common registers as they But you can modify your application to periodically mirror them to 

What is relation between MCUXpresso for VSCode and Zephyr? Hello, I want to start a new project with the iMXRT10xx series processor. I understand I can use MCUXpresso or VSCode with MCUXpresso for VSCode. Are they the same but just on a different IDE? Or is MCUXpresso for VSCode based on Zephyr and MCUXpressor not? Re: What is relation between MCUXpresso for VSCode and Zephyr? So when using VSCode with the extension, I can select between MCUXpress or Zephyr? If I understand correctly MCUXpress will take care of configuration of the chip resources like Uarts and I2C. To my knowledge Zephyr does the same (in a more generic way?). So I have to choose between them? Re: What is relation between MCUXpresso for VSCode and Zephyr? Hi, MCUXpresso is an ecosystem of software and tools supporting NXP devices with ARM Cortex-M (https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-:MCUXPRESSO) "MCUXpresso for VS Code" is an VS Code extension supporting NXP ARM Cortex-M devices using various software repositories, including Zephyr and MCUXpresso SDK (https://marketplace.visualstudio.com/items?itemName=NXPSemiconductors.mcuxpresso) Documentation about how to use this extension : https://github.com/nxp-mcuxpresso/vscode-for-mcux/wiki A step by step guide for using VS Code + Zephyr + RT10xx device is located here: https://github.com/nxp-mcuxpresso/vscode-for-mcux/wiki/Training-Zephyr-Getting-Started-RT1060  Regards, Cristian

S32K344 Sensing voltage on PTA11 pin using ADC. Hello, I want to sense voltage varying from 0 to 3.3V DC on PTA11 pin of S32K344 MCU using ADC. Can someone provide me any RTD based(non-Autosar) example of that or similar example with different pin also fine. I am using Design Studio 3.5 and RTD3.0.0 Thanks. Re: S32K344 Sensing voltage on PTA11 pin using ADC. Hi @jerryrig, I have sent you a private message regarding the example. Best regards, Julián

PT2001 Vboost LS7 Gが動かなくなる dram2.binと目標電圧が高いと、常にオンになってしまうので、電圧と電流の両方のスイッチングポイントを減らし、電流を流さないようにしました。ドキュメントは不明ですが、電圧レベルは常に有効であり、目標値は20Vオフ18Vオン、1Aオフ0.5Aオンだと思います。図6に注意してください。存在しないD_LS7を示していますが、なぜアンダースコアに侵されているのですか?ハイフンやマイナスよりも安全ですか?DLS7またはLS7Dに問題があるのは誰ですか? ソレノイドコントローラー 日時:PT2001 Vboost LS7 Gが動かなくなる なぜかはわかりませんが、これらのリクエストを書くことは本当に役に立ちます。20Voff 18Von、2Aoff 1Aon、...... に改訂現在動作します。 🙂

u-boot splash screen (no command line messages) hello guys,  I am pretty new to this u-boot environment and customization and using i.mx 8mp board. I need some inputs or help or some steps(actually elaborated) in order to create a minimal u-boot with custom splash screen(image on entire screen) with no command line logs while booting. I have this .bmp image which I have created by following some external links. but no idea how to proceed further from there. Any help or inputs on this is highly appreciated as I know I am asking you guys a bigger chunk of help. Anil Kumar i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: u-boot splash screen (no command line messages) Hello @anilkandikonda  I hope you are doing very well. You can take a look to the AN13709 that is about of Linux Boot Time Optimizations for i.MX8M Family. In chapter 4 is mentioned the possible Bootloader optimizations. I hope this information can helps to you. Best regards, Salas.

Freemaster : レジストリへのアクセス方法 ? Freemasterが組み込みコードの実行中にARMとハードウェアレジスタへのアクセスを許可しているかどうか知りたいです。アプリケーションのメモリダンプを実行してレジスタにアクセスし、そのハードウェア表現を推測することはできますか?

Freemaster：如何访问注册表？ 我想知道 Freemaster 是否允许在执行嵌入式代码期间访问 ARM 和硬件寄存器。我们能否执行应用程序的内存转储，从而访问寄存器并推断其硬件表示？

imx6ull increase cpu frequency to 792MHz Hi, I built a Debian based OS with the current environment: Linux 6.6.58-rt45-0 - Mainline u-boot 2024.07 - Mainline I have a custom HW which has an imx6ull microprocessor.  I based the device tree on imx6ul-14x14-evk.dtsi (uboot and kernel). My custom device tree inherits from "imx6ull.dtsi" I would like to know if I can use 792MHz or 900MHz for CPU freq. I've seen those frequencies are available on Device Tree definition: &cpu0 {        clock-frequency = <900000000>;        operating-points = <                /* kHz  uV */                900000  1275000                792000  1225000                528000  1175000                396000  1025000                198000  950000        >;        fsl,soc-operating-points = <                /* KHz  uV */                900000  1250000                792000  1175000                528000  1175000                396000  1175000                198000  1175000        >; }; However, in my file system I do not have them available: root@imx6ull:~# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq 528000 root@imx6ull:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies   198000 396000 528000 Does it possible? Does it limited by HW, voltage or current input?  I've seen other questions in the forum related to it but I did not find a clear answer: How to set imx6UL CPU to 528MHz in U-boot  About changing the internal LDOs voltage in i.MX6DQ.  How to set CPU frequency on u-boot?  Thanks, Javier Re: imx6ull increase cpu frequency to 792MHz Hi, Thank you both four replies. Now I understand where the limitation comes from. The partnumber is MCIMX6Y2CVM05AB, therefore it is nothing to do here. I've checked the fuses and results match with @lapohab described. Regarding the software changes... I agree with @lapohab . By default all frequencies are available in the Device Tree, therefore, if it is supported by the soc, those frequencies must appear in user space and it would be possible to change the CPU frequency in running time. There is no need to hardcode only one frequency in the Device Tree. Thanks for the support Re: imx6ull increase cpu frequency to 792MHz It has been clearly described in the last post. This cannot be burned by yourself. It is burned during production testing. I attach it again. It says "Burned by tester program, forindicating IC core speed (Hotburn may not be used)." Industrial part and Consumer part have different life times. This is in i.MX 6ULL ​​Product Usage Lifetime Estimates (AN5337). If you force a higher frequency in the software than its grade defined, the life time will inevitably be shortened. According to your idea, everyone should buy a cheaper Consumer part and burn it into an industrial part by themselves. It will save lots of money including my running projects. According to your idea, another case is just burn fuse of industrial part, it can run at 900M without life time impact. Why NXP does not have 900M industrial part? Why are there still different parts of different grades for sale? Remove the other frequencies? Have you ever tried it? Just looking at the code, it doesn't work. You can only modify the following code, but I think it is only for testing purpose. As I said before, If you force a higher frequency in the software, the life time will inevitably be shortened. if (of_machine_is_compatible("fsl,imx6ull")) { #if 0 if (val < OCOTP_CFG3_6ULL_SPEED_792MHZ) imx6x_disable_freq_in_opp(dev, 792000000); if (val != OCOTP_CFG3_6ULL_SPEED_900MHZ) imx6x_disable_freq_in_opp(dev, 900000000); #endif } Re: imx6ull increase cpu frequency to 792MHz Hi, My idea was to remove the other frequencies before blowing the highlighted fuse. You could try to only add the 792MHz node in DTS, if not, you should modify the fuses if your part number matches the 08 code. Regards, Re: imx6ull increase cpu frequency to 792MHz All frequencies are already in the device tree. The code will determine the chip type based on different fuses and then modify the DTB in real-time. https://github.com/nxp-imx/linux-imx/blob/lf-6.6.3-1.0.0/drivers/cpufreq/imx6q-cpufreq.c #define OCOTP_CFG3_6UL_SPEED_696MHZ 0x2 #define OCOTP_CFG3_6ULL_SPEED_792MHZ 0x2 #define OCOTP_CFG3_6ULL_SPEED_900MHZ 0x3 static int imx6ul_opp_check_speed_grading(struct device *dev) { u32 val; int ret = 0; if (of_property_present(dev->of_node, "nvmem-cells")) { ret = nvmem_cell_read_u32(dev, "speed_grade", &val); if (ret) return ret; } else { struct device_node *np; void __iomem *base; np = of_find_compatible_node(NULL, NULL, "fsl,imx6ul-ocotp"); if (!np) np = of_find_compatible_node(NULL, NULL, "fsl,imx6ull-ocotp"); if (!np) return -ENOENT; base = of_iomap(np, 0); of_node_put(np); if (!base) { dev_err(dev, "failed to map ocotp\n"); return -EFAULT; } val = readl_relaxed(base + OCOTP_CFG3); iounmap(base); } /* * Speed GRADING[1:0] defines the max speed of ARM: * 2b'00: Reserved; * 2b'01: 528000000Hz; * 2b'10: 696000000Hz on i.MX6UL, 792000000Hz on i.MX6ULL; * 2b'11: 900000000Hz on i.MX6ULL only; * We need to set the max speed of ARM according to fuse map. */ val >>= OCOTP_CFG3_SPEED_SHIFT; val &= 0x3; if (of_machine_is_compatible("fsl,imx6ul")) if (val != OCOTP_CFG3_6UL_SPEED_696MHZ) imx6x_disable_freq_in_opp(dev, 696000000); if (of_machine_is_compatible("fsl,imx6ull")) { if (val < OCOTP_CFG3_6ULL_SPEED_792MHZ) imx6x_disable_freq_in_opp(dev, 792000000); if (val != OCOTP_CFG3_6ULL_SPEED_900MHZ) imx6x_disable_freq_in_opp(dev, 900000000); } return ret; } Re: imx6ull increase cpu frequency to 792MHz Hi Josheph, I have already available that operating point in my device tree, it is defined in imx6ull.dtsi, and by default is set to 900000000Hz. I decompiled the Device Tree in my running system and I can see the same configuration: cpus { #address-cells = <0x01>; #size-cells = <0x00>; cpu@0 { compatible = "arm,cortex-a7"; clocks = <0x01 0x5d 0x01 0x1a 0x01 0x26 0x01 0xdb 0x01 0x38 0x01 0x39 0x01 0x19>; nvmem-cells = <0x04>; device_type = "cpu"; soc-supply = <0x03>; arm-supply = <0x02>; clock-names = "arm\0pll2_bus\0pll2_pfd2_396m\0secondary_sel\0step\0pll1_sw\0pll1_sys"; fsl,soc-operating-points = <0xdbba0 0x1312d0 0xc15c0 0x11edd8 0x80e80 0x11edd8 0x60ae0 0x11edd8 0x30570 0x11edd8>; phandle = <0x37>; reg = <0x00>; clock-frequency = <0x35a4e900>; // 900000000 Hz operating-points = <0xdbba0 0x137478 0xc15c0 0x12b128 0x80e80 0x11edd8 0x60ae0 0xfa3e8 0x30570 0xe7ef0>; //900000 - 1275000 ... clock-latency = <0xee6c>; #cooling-cells = <0x02>; nvmem-cell-names = "speed_grade"; }; }; However, I do not have available 792MHz nor 900MHz from user space. And the system is running at 528MHz. I have exactly the same configuration in u-boot. What you mean with "modify the dts file" Which dts file? Do you mean leave only 900MHz frequency in DTS? Thanks, Javier Re: imx6ull increase cpu frequency to 792MHz Hi, Thank you for your interest in NXP Semiconductor products, If you want to run the i.MX6ULL at exact 900MHz, then for that you need to modify the dts file. operating-points = <       /* kHz  uV */       900000  1275000 Regards