AM62P: cadence-qspi probe failure

Part Number: AM62P

Tool/software:

Hello,

working on a custom board based on TI AM62P processor, and the cadence-qspi probe fails.

[   18.147644] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22
[   18.155721] platform fc40000.spi: deferred probe pending

root@verdin-am62p-15664920:~# cat /sys/kernel/debug/devices_deferred 
fc40000.spi	cadence-qspi: No Rx DMA available

Complete kernel logs:

class="code-editor"> 43/cfs-filesystemfile/__key/communityserver-discussions-components-files/791/kernel_2D00_logs.txt?_=638773035951548310" class="code-download ui-tip" data-tip="Download kernel-logs.txt">kernel-logs.txt data-mode="text" data-theme="light" style="height:240px;min-width:320px;margin:0px;" data-gutter="true">kern :info : [ 0.000000 < 0.000000>] Booting Linux on physical CPU 0x0000000000 [0x410fd034] 0.000000>] Linux version 6.6.58-7.2.0-devel-g9d7c5d371546 (oe-user@oe-host) (aarch64-tdx-linux-gcc (GCC) 13.3.0, GNU ld (GNU Binutils) 2.42.0.20240723) #1 SMP PREEMPT Fri Feb 28 16:55:00 UTC 2025 0.000000>] KASLR disabled due to lack of seed 0.000000>] Machine model: Toradex Verdin AM62P WB on Verdin Development Board 0.000000>] efi: UEFI not found. 0.000000>] OF: reserved mem: 0x0000000080000000..0x000000008007ffff (512 KiB) nomap non-reusable tfa@80000000 0.000000>] Reserved memory: created DMA memory pool at 0x000000009c900000, size 30 MiB 0.000000>] OF: reserved mem: initialized node r5f-dma-memory@9c900000, compatible id shared-dma-pool 0.000000>] OF: reserved mem: 0x000000009c900000..0x000000009e6fffff (30720 KiB) nomap non-reusable r5f-dma-memory@9c900000 0.000000>] OF: reserved mem: 0x000000009e800000..0x000000009fffffff (24576 KiB) nomap non-reusable optee@9e800000 0.000000>] Zone ranges: 0.000000>] DMA [mem 0x0000000080000000-0x00000000ffffffff] 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 0x0000000080000000-0x000000008007ffff] 0.000000>] node 0: [mem 0x0000000080080000-0x000000009c8fffff] 0.000000>] node 0: [mem 0x000000009c900000-0x000000009e6fffff] 0.000000>] node 0: [mem 0x000000009e700000-0x000000009e7fffff] 0.000000>] node 0: [mem 0x000000009e800000-0x000000009fffffff] 0.000000>] node 0: [mem 0x00000000a0000000-0x00000000ffffffff] 0.000000>] Initmem setup node 0 [mem 0x0000000080000000-0x00000000ffffffff] 0.000000>] cma: Reserved 410 MiB at 0x00000000e3400000 on node -1 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.5 0.000000>] percpu: Embedded 20 pages/cpu s42792 r8192 d30936 u81920 0.000000>] pcpu-alloc: s42792 r8192 d30936 u81920 alloc=20*4096 0.000000>] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 0.000000>] Detected VIPT I-cache on CPU0 0.000000>] CPU features: detected: GIC system register CPU interface 0.000000>] alternatives: applying boot alternatives 0.000000>] Kernel command line: root=PARTUUID=fd47d490-02 ro rootwait console=tty1 console=ttyS2,115200 0.000000>] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) 0.000000>] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear) 0.000000>] Built 1 zonelists, mobility grouping on. Total pages: 516096 0.000000>] mem auto-init: stack:all(zero), heap alloc:off, heap free:off 0.000000>] software IO TLB: area num 4. 0.000000>] software IO TLB: mapped [mem 0x00000000df400000-0x00000000e3400000] (64MB) 0.000000>] Memory: 1495488K/2097152K available (11264K kernel code, 1222K rwdata, 3496K rodata, 2496K init, 458K bss, 181824K reserved, 419840K 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: 256 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:0x0000000001880000 0.000000>] ITS [mem 0x01820000-0x0182ffff] 0.000000>] GIC: enabling workaround for ITS: Socionext Synquacer pre-ITS 0.000000>] ITS@0x0000000001820000: Devices Table too large, reduce ids 20->19 0.000000>] ITS@0x0000000001820000: allocated 524288 Devices @80c00000 (flat, esz 8, psz 64K, shr 0) 0.000000>] ITS: using cache flushing for cmd queue 0.000000>] GICv3: using LPI property table @0x0000000080440000 0.000000>] GIC: using cache flushing for LPI property table 0.000000>] GICv3: CPU0: using allocated LPI pending table @0x0000000080450000 0.000000>] rcu: srcu_init: Setting srcu_struct sizes based on contention. 0.000000>] arch_timer: cp15 timer(s) running at 200.00MHz (phys). 0.000000>] clocksource: arch_sys_counter: mask: 0x3ffffffffffffff max_cycles: 0x2e2049d3e8, max_idle_ns: 440795210634 ns 0.000000>] sched_clock: 58 bits at 200MHz, resolution 5ns, wraps every 4398046511102ns 0.000000>] Console: colour dummy device 80x25 0.000010>] printk: console [tty1] enabled 0.000523>] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000) 0.000023>] pid_max: default: 32768 minimum: 301 0.000163>] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) 0.000023>] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) 0.001659>] RCU Tasks: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1. 0.000084>] RCU Tasks Trace: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1. 0.000182>] rcu: Hierarchical SRCU implementation. 0.000012>] rcu: Max phase no-delay instances is 1000. 0.000676>] Platform MSI: msi-controller@1820000 domain created 0.000333>] PCI/MSI: /bus@f0000/interrupt-controller@1800000/msi-controller@1820000 domain created 0.000111>] EFI services will not be available. 0.000319>] smp: Bringing up secondary CPUs ... 0.000593>] Detected VIPT I-cache on CPU1 0.000068>] GICv3: CPU1: found redistributor 1 region 0:0x00000000018a0000 0.000015>] GICv3: CPU1: using allocated LPI pending table @0x0000000080460000 0.000049>] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] 0.000646>] Detected VIPT I-cache on CPU2 0.000052>] GICv3: CPU2: found redistributor 2 region 0:0x00000000018c0000 0.000013>] GICv3: CPU2: using allocated LPI pending table @0x0000000080470000 0.000032>] CPU2: Booted secondary processor 0x0000000002 [0x410fd034] 0.000573>] Detected VIPT I-cache on CPU3 0.000050>] GICv3: CPU3: found redistributor 3 region 0:0x00000000018e0000 0.000011>] GICv3: CPU3: using allocated LPI pending table @0x0000000080480000 0.000029>] CPU3: Booted secondary processor 0x0000000003 [0x410fd034] 0.000073>] smp: Brought up 1 node, 4 CPUs 0.000107>] SMP: Total of 4 processors activated. 0.000011>] CPU features: detected: 32-bit EL0 Support 0.000010>] CPU features: detected: CRC32 instructions 0.000071>] CPU: All CPU(s) started at EL2 0.000010>] alternatives: applying system-wide alternatives 0.001613>] devtmpfs: initialized 0.008963>] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns 0.000051>] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) 0.010994>] pinctrl core: initialized pinctrl subsystem 0.000660>] DMI not present or invalid. 0.000649>] NET: Registered PF_NETLINK/PF_ROUTE protocol family 0.000829>] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations 0.000115>] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations 0.000127>] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations 0.000492>] thermal_sys: Registered thermal governor 'step_wise' 0.000006>] thermal_sys: Registered thermal governor 'user_space' 0.000013>] thermal_sys: Registered thermal governor 'power_allocator' 0.000043>] cpuidle: using governor menu 0.000125>] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. 0.000096>] ASID allocator initialised with 65536 entries 0.007247>] /bus@f0000/interrupt-controller@1800000: Fixed dependency cycle(s) with /bus@f0000/interrupt-controller@1800000 0.000368>] /bus@f0000/dss@30200000: Fixed dependency cycle(s) with /bus@f0000/dss@30200000/oldi-txes/oldi@0 0.000037>] /bus@f0000/dss@30200000: Fixed dependency cycle(s) with /bus@f0000/dss@30200000/oldi-txes/oldi@1 0.000039>] /bus@f0000/dss@30200000/oldi-txes/oldi@0: Fixed dependency cycle(s) with /bus@f0000/dss@30200000 0.000034>] /bus@f0000/dss@30200000/oldi-txes/oldi@0: Fixed dependency cycle(s) with /panel-lvds-mez 0.000113>] /bus@f0000/dss@30200000/oldi-txes/oldi@1: Fixed dependency cycle(s) with /bus@f0000/dss@30200000 0.000039>] /bus@f0000/dss@30200000/oldi-txes/oldi@1: Fixed dependency cycle(s) with /panel-lvds-mez 0.010705>] /bus@f0000/dss@30200000: Fixed dependency cycle(s) with /bus@f0000/dss@30200000/oldi-txes/oldi@0 0.000061>] /bus@f0000/dss@30200000: Fixed dependency cycle(s) with /bus@f0000/dss@30200000/oldi-txes/oldi@1 0.000046>] /bus@f0000/dss@30200000/oldi-txes/oldi@0: Fixed dependency cycle(s) with /bus@f0000/dss@30200000 0.000040>] /bus@f0000/dss@30200000/oldi-txes/oldi@0: Fixed dependency cycle(s) with /panel-lvds-mez 0.000087>] /bus@f0000/dss@30200000/oldi-txes/oldi@1: Fixed dependency cycle(s) with /bus@f0000/dss@30200000 0.000043>] /bus@f0000/dss@30200000/oldi-txes/oldi@1: Fixed dependency cycle(s) with /panel-lvds-mez 0.000516>] /bus@f0000/usb@f900000/usb@31000000: Fixed dependency cycle(s) with /connector 0.000076>] /connector: Fixed dependency cycle(s) with /bus@f0000/usb@f900000/usb@31000000 0.001645>] Modules: 27984 pages in range for non-PLT usage 0.000010>] Modules: 519504 pages in range for PLT usage 0.000685>] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages 0.000031>] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page 0.000013>] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages 0.000010>] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page 0.000012>] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages 0.000011>] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page 0.000012>] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages 0.000011>] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page 0.001446>] k3-chipinfo 43000014.chipid: Family:AM62PX rev:SR1.0 JTAGID[0x0bb9d02f] Detected 0.000391>] iommu: Default domain type: Translated 0.000019>] iommu: DMA domain TLB invalidation policy: strict mode 0.000315>] SCSI subsystem initialized 0.000149>] usbcore: registered new interface driver usbfs 0.000035>] usbcore: registered new interface driver hub 0.000045>] usbcore: registered new device driver usb 0.000745>] mc: Linux media interface: v0.10 0.000047>] videodev: Linux video capture interface: v2.00 0.000031>] pps_core: LinuxPPS API ver. 1 registered 0.000011>] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> 0.000022>] PTP clock support registered 0.000539>] Advanced Linux Sound Architecture Driver Initialized. 0.001313>] clocksource: Switched to clocksource arch_sys_counter 0.006599>] NET: Registered PF_INET protocol family 0.000186>] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear) 0.001631>] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear) 0.000082>] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) 0.000024>] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear) 0.000120>] TCP bind hash table entries: 16384 (order: 7, 524288 bytes, linear) 0.000428>] TCP: Hash tables configured (established 16384 bind 16384) 0.000133>] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear) 0.000065>] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear) 0.000185>] NET: Registered PF_UNIX/PF_LOCAL protocol family 0.000452>] RPC: Registered named UNIX socket transport module. 0.000022>] RPC: Registered udp transport module. 0.000010>] RPC: Registered tcp transport module. 0.000009>] RPC: Registered tcp-with-tls transport module. 0.000009>] RPC: Registered tcp NFSv4.1 backchannel transport module. 0.000022>] PCI: CLS 0 bytes, default 64 0.001105>] Initialise system trusted keyrings 0.000200>] workingset: timestamp_bits=46 max_order=19 bucket_order=0 0.000526>] NFS: Registering the id_resolver key type 0.000036>] Key type id_resolver registered 0.000011>] Key type id_legacy registered 0.000025>] nfs4filelayout_init: NFSv4 File Layout Driver Registering... 0.000014>] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... 0.000181>] Key type asymmetric registered 0.000013>] Asymmetric key parser 'x509' registered 0.000051>] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245) 0.000019>] io scheduler mq-deadline registered 0.000011>] io scheduler kyber registered 0.000035>] io scheduler bfq registered 0.003519>] pinctrl-single 4084000.pinctrl: 34 pins, size 136 0.001001>] pinctrl-single f4000.pinctrl: 171 pins, size 684 0.044710>] Serial: 8250/16550 driver, 6 ports, IRQ sharing disabled 0.007384>] usbcore: registered new interface driver usb-storage 0.000241>] i2c_dev: i2c /dev entries driver 0.002412>] sdhci: Secure Digital Host Controller Interface driver 0.000026>] sdhci: Copyright(c) Pierre Ossman 0.000236>] sdhci-pltfm: SDHCI platform and OF driver helper 0.000533>] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping .... 0.000427>] usbcore: registered new interface driver usbhid 0.000014>] usbhid: USB HID core driver 0.001355>] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available 0.002374>] NET: Registered PF_PACKET protocol family 0.000102>] Key type dns_resolver registered 0.005975>] Loading compiled-in X.509 certificates 0.012380>] ti-sci 44043000.system-controller: ABI: 4.0 (firmware rev 0x000b '11.0.2-v11.00.02 (Fancy Rat)') 0.051574>] omap_i2c 4900000.i2c: bus 3 rev0.12 at 100 kHz 0.001171>] /bus@f0000/bus@b00000/i2c@2b200000/pmic@30: Fixed dependency cycle(s) with /bus@f0000/bus@b00000/i2c@2b200000/pmic@30/regulators/buck2 0.000052>] /bus@f0000/bus@b00000/i2c@2b200000/pmic@30: Fixed dependency cycle(s) with /bus@f0000/bus@b00000/i2c@2b200000/pmic@30/regulators/buck1 0.028216>] rtc-ds1307 0-0032: oscillator failed, set time! 0.000266>] rtc-ds1307 0-0032: registered as rtc0 0.000299>] rtc-ds1307 0-0032: hctosys: unable to read the hardware clock 0.000506>] at24 0-0050: supply vcc not found, using dummy regulator 0.000434>] at24 0-0050: 256 byte 24c02 EEPROM, writable, 16 bytes/write 0.000054>] omap_i2c 2b200000.i2c: bus 0 rev0.12 at 400 kHz 0.001718>] at24 1-0057: supply vcc not found, using dummy regulator 0.009163>] tps65219 0-0030: Error IRQ trap residual voltage for LDO4 0.012241>] at24 1-0057: 256 byte 24c02 EEPROM, writable, 16 bytes/write 0.000068>] omap_i2c 20000000.i2c: bus 1 rev0.12 at 100 kHz 0.001259>] omap_i2c 20010000.i2c: bus 2 rev0.12 at 100 kHz 0.000960>] omap_i2c 20030000.i2c: bus 4 rev0.12 at 100 kHz 0.000265>] ti-sci-intr 4210000.interrupt-controller: Interrupt Router 5 domain created 0.000165>] ti-sci-intr bus@f0000:interrupt-controller@a00000: Interrupt Router 3 domain created 0.000233>] ti-sci-inta 48000000.interrupt-controller: Interrupt Aggregator domain 28 created 0.000264>] ti-sci-inta 4e400000.interrupt-controller: Interrupt Aggregator domain 200 created 0.001645>] ti-udma 485c0100.dma-controller: Number of rings: 82 0.002508>] ti-udma 485c0100.dma-controller: Channels: 48 (bchan: 18, tchan: 12, rchan: 18) 0.002814>] ti-udma 485c0000.dma-controller: Number of rings: 150 0.004687>] ti-udma 485c0000.dma-controller: Channels: 35 (tchan: 20, rchan: 15) 0.002214>] ti-udma 4e230000.dma-controller: Number of rings: 6 0.000571>] ti-udma 4e230000.dma-controller: Channels: 6 (bchan: 0, tchan: 0, rchan: 6) 0.001785>] 4a00000.serial: ttyS1 at MMIO 0x4a00000 (irq = 302, base_baud = 3000000) is a 8250 0.001564>] 2800000.serial: ttyS2 at MMIO 0x2800000 (irq = 303, base_baud = 3000000) is a 8250 0.000063>] printk: console [ttyS2] enabled 1.461998>] 2810000.serial: ttyS0 at MMIO 0x2810000 (irq = 304, base_baud = 3000000) is a 8250 0.009408>] omap8250 2860000.serial: failed to get alias 0.046968>] davinci_mdio 8000f00.mdio: davinci mdio revision 17.7, bus freq 1000000 0.009113>] am65-cpsw-nuss 8000000.ethernet: initializing am65 cpsw nuss version 0x6BA01903, cpsw version 0x6BA81903 Ports: 3 quirks:00000006 0.012888>] am65-cpsw-nuss 8000000.ethernet: initialized cpsw ale version 1.5 0.007139>] am65-cpsw-nuss 8000000.ethernet: ALE Table size 512 0.006566>] am65-cpsw-nuss 8000000.ethernet: CPTS ver 0x4e8a010d, freq:500000000, add_val:1 pps:0 0.013965>] am65-cpsw-nuss 8000000.ethernet: set new flow-id-base 19 0.013576>] cpufreq: cpufreq_online: CPU0: Running at unlisted initial frequency: 1200000 KHz, changing to: 1250000 KHz 0.012694>] mmc0: CQHCI version 5.10 0.000063>] mmc2: CQHCI version 5.10 0.039983>] mmc0: SDHCI controller on fa10000.mmc [fa10000.mmc] using ADMA 64-bit 0.004533>] mmc2: SDHCI controller on fa20000.mmc [fa20000.mmc] using ADMA 64-bit 0.007463>] davinci_mdio 8000f00.mdio: davinci mdio revision 17.7, bus freq 1000000 0.018279>] davinci_mdio 8000f00.mdio: phy[0]: device 8000f00.mdio:00, driver TI DP83867 0.008121>] davinci_mdio 8000f00.mdio: phy[7]: device 8000f00.mdio:07, driver Microchip KSZ9131 Gigabit PHY 0.011049>] sdhci-am654 fa00000.mmc: Got CD GPIO 0.002703>] clk: Disabling unused clocks 0.006185>] mmc1: CQHCI version 5.10 0.006099>] ALSA device list: 0.002983>] No soundcards found. 0.003506>] mmc2: new ultra high speed SDR104 SDIO card at address 0001 0.045181>] mmc1: SDHCI controller on fa00000.mmc [fa00000.mmc] using ADMA 64-bit 0.007650>] mmc0: Command Queue Engine enabled 0.000260>] Waiting for root device PARTUUID=fd47d490-02... 0.004213>] mmc0: new HS200 MMC card at address 0001 0.011456>] mmcblk0: mmc0:0001 S40016 14.6 GiB 0.006143>] mmcblk0: p1 p2 0.003449>] mmcblk0boot0: mmc0:0001 S40016 4.00 MiB 0.005700>] mmcblk0boot1: mmc0:0001 S40016 4.00 MiB 0.005647>] mmcblk0rpmb: mmc0:0001 S40016 4.00 MiB, chardev (242:0) 0.022576>] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem 0.007364>] EXT4-fs (mmcblk0p2): write access will be enabled during recovery 0.016434>] EXT4-fs (mmcblk0p2): recovery complete 0.006139>] EXT4-fs (mmcblk0p2): mounted filesystem f09729b3-29df-4b34-8b8a-021fdbf270e3 ro with ordered data mode. Quota mode: disabled. 0.012431>] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. 0.008914>] devtmpfs: mounted 0.003831>] Freeing unused kernel memory: 2496K 0.004626>] Run /sbin/init as init process 0.004104>] with arguments: 0.000007>] /sbin/init 0.000006>] with environment: 0.000005>] HOME=/ 0.000005>] TERM=linux 0.131222>] systemd[1]: System time before build time, advancing clock. 0.022346>] systemd[1]: Inserted module 'autofs4' 0.031254>] NET: Registered PF_INET6 protocol family 0.006247>] Segment Routing with IPv6 0.003757>] In-situ OAM (IOAM) with IPv6 0.028033>] systemd[1]: systemd 255.17^ running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA -SMACK +SECCOMP -GCRYPT -GNUTLS -OPENSSL +ACL +BLKID -CURL -ELFUTILS -FIDO2 -IDN2 -IDN -IPTC +KMOD -LIBCRYPTSETUP +LIBFDISK -PCRE2 -PWQUALITY -P11KIT -QRENCODE -TPM2 -BZIP2 -LZ4 -XZ -ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) 0.032108>] systemd[1]: Detected architecture arm64. 0.026593>] systemd[1]: Hostname set to <verdin-am62p-15664920>. 0.381091>] systemd[1]: Queued start job for default target Graphical Interface. 0.042078>] systemd[1]: Created slice Slice /system/getty. 0.022002>] systemd[1]: Created slice Slice /system/modprobe. 0.024053>] systemd[1]: Created slice Slice /system/serial-getty. 0.024032>] systemd[1]: Created slice User and Session Slice. 0.022641>] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. 0.023981>] systemd[1]: Started Forward Password Requests to Wall Directory Watch. 0.023821>] systemd[1]: Expecting device /dev/ttyS2... 0.016103>] systemd[1]: Reached target Host and Network Name Lookups. 0.023955>] systemd[1]: Reached target Path Units. 0.015904>] systemd[1]: Reached target Remote File Systems. 0.020066>] systemd[1]: Reached target Slice Units. 0.016074>] systemd[1]: Reached target Swaps. 0.061764>] systemd[1]: Listening on RPCbind Server Activation Socket. 0.026368>] systemd[1]: Reached target RPC Port Mapper. 0.027895>] systemd[1]: Listening on Syslog Socket. 0.016774>] systemd[1]: Listening on initctl Compatibility Named Pipe. 0.036572>] systemd[1]: Journal Audit Socket was skipped because of an unmet condition check (ConditionSecurity=audit). 0.012445>] systemd[1]: Listening on Journal Socket (/dev/log). 0.023583>] systemd[1]: Listening on Journal Socket. 0.016485>] systemd[1]: Listening on Network Service Netlink Socket. 0.025627>] systemd[1]: Listening on udev Control Socket. 0.021584>] systemd[1]: Listening on udev Kernel Socket. 0.025492>] systemd[1]: Listening on User Database Manager Socket. 0.053431>] systemd[1]: Mounting Huge Pages File System... 0.020440>] systemd[1]: Mounting POSIX Message Queue File System... 0.026991>] systemd[1]: Mounting Kernel Debug File System... 0.016859>] systemd[1]: Kernel Trace File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/tracing). 0.018432>] systemd[1]: Mounting Temporary Directory /tmp... 0.021764>] systemd[1]: Starting Create List of Static Device Nodes... 0.028314>] systemd[1]: Starting Load Kernel Module configfs... 0.019569>] systemd[1]: Starting Load Kernel Module drm... 0.019791>] systemd[1]: Starting Load Kernel Module fuse... 0.021267>] systemd[1]: Starting RPC Bind... 0.010818>] fuse: init (API version 7.39) 0.008381>] systemd[1]: Starting File System Check on Root Device... 0.030732>] systemd[1]: Starting Journal Service... 0.018065>] systemd[1]: Load Kernel Modules was skipped because no trigger condition checks were met. 0.013994>] systemd[1]: Starting Generate network units from Kernel command line... 0.013942>] systemd[1]: Starting Apply Kernel Variables... 0.013878>] systemd[1]: Starting Coldplug All udev Devices... 0.023126>] systemd[1]: Started RPC Bind. 0.010571>] systemd[1]: Mounted Huge Pages File System. 0.015831>] systemd-journald[121]: Collecting audit messages is disabled. 0.011974>] systemd[1]: Mounted POSIX Message Queue File System. 0.023901>] systemd[1]: Mounted Kernel Debug File System. 0.023608>] systemd[1]: Started Journal Service. 0.308908>] EXT4-fs (mmcblk0p2): re-mounted f09729b3-29df-4b34-8b8a-021fdbf270e3 r/w. Quota mode: disabled. 0.110222>] systemd-journald[121]: Received client request to flush runtime journal. 1.104246>] random: crng init done 0.081407>] lm75 0-0048: supply vs not found, using dummy regulator 0.012075>] ina2xx 1-0040: supply vs not found, using dummy regulator 0.002345>] hwmon hwmon0: temp1_input not attached to any thermal zone 0.014861>] lm75 0-0048: hwmon0: sensor 'tmp1075' 0.008124>] ina2xx 1-0040: power monitor ina219 (Rshunt = 10000 uOhm) 0.000580>] omap8250 2b300000.serial: failed to get alias 0.014547>] lm75 1-004f: supply vs not found, using dummy regulator 0.013431>] CAN device driver interface 0.009041>] atmel_mxt_ts 2-004a: supply vdda not found, using dummy regulator 0.001463>] hwmon hwmon2: temp1_input not attached to any thermal zone 0.000765>] pca953x 0-0021: supply vcc not found, using dummy regulator 0.000227>] pca953x 0-0021: using no AI 0.002459>] pca953x 1-0021: supply vcc not found, using dummy regulator 0.000178>] pca953x 1-0021: using no AI 0.006564>] omap-mailbox 29000000.mailbox: omap mailbox rev 0x66fca100 0.002109>] lm75 1-004f: hwmon2: sensor 'tmp75c' 0.019066>] atmel_mxt_ts 2-004a: supply vdd not found, using dummy regulator 0.015173>] omap-mailbox 29010000.mailbox: omap mailbox rev 0x66fca100 0.020870>] omap-mailbox 29020000.mailbox: no available mbox devices found 0.000329>] m_can_platform 4e08000.can: m_can device registered (irq=504, version=32) 0.017018>] omap-mailbox 29030000.mailbox: no available mbox devices found 0.013056>] tidss 30200000.dss: failed to init OLDI: -517 0.001166>] m_can_platform 20701000.can: m_can device registered (irq=508, version=32) 0.004534>] vdec 30210000.video-codec: OPP table not found in device tree 0.047645>] vdec 30210000.video-codec: Added wave5 driver with caps: 'ENCODE' 'DECODE' 0.009314>] vdec 30210000.video-codec: Product Code: 0x521c 0.006347>] vdec 30210000.video-codec: Firmware Revision: 344874 0.030301>] tidss 30200000.dss: failed to init OLDI: -517 0.101043>] tidss 30200000.dss: failed to init OLDI: -517 0.021034>] /connector: Fixed dependency cycle(s) with /bus@f0000/usb@f900000/usb@31000000 0.009180>] atmel_mxt_ts 2-004a: Family: 164 Variant: 11 Firmware V1.2.AA Objects: 41 0.010128>] atmel_mxt_ts 2-004a: Enabling RETRIGEN workaround 0.019058>] /bus@f0000/usb@f900000/usb@31000000: Fixed dependency cycle(s) with /connector 0.030850>] input: tps65219-pwrbutton as /devices/platform/bus@f0000/bus@f0000:bus@b00000/2b200000.i2c/i2c-0/0-0030/tps65219-pwrbutton.2.auto/input/input0 0.002220>] tidss 30200000.dss: failed to init OLDI: -517 0.000174>] rtc-ti-k3 2b1f0000.rtc: registered as rtc1 0.034424>] input: gpio-keys as /devices/platform/gpio-keys/input/input1 0.009565>] optee: probing for conduit method. 0.004762>] atmel_mxt_ts 2-004a: Direct firmware load for maxtouch.cfg failed with error -2 0.001640>] optee: revision 4.5 (ef1ebdc23034a804) 0.004897>] pvrsrvkm: loading out-of-tree module taints kernel. 0.014232>] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 0.006658>] optee: dynamic shared memory is enabled 0.000330>] [drm] Initialized tidss 1.0.0 20180215 for 30200000.dss on minor 0 0.005833>] PVR_K: 177: Device: fd80000.gpu 0.004140>] optee: initialized driver 0.012861>] atmel_mxt_ts 2-004a: Touchscreen size X1279Y799 0.006645>] input: Atmel maXTouch Touchscreen as /devices/platform/bus@f0000/20010000.i2c/i2c-2/2-004a/input/input2 0.015511>] PVR_K: 177: Read BVNC 36.53.104.796 from HW device registers 0.000132>] PVR_K: 177: RGX Device registered BVNC 36.53.104.796 with 1 core in the system 0.001578>] [drm] Initialized pvr 24.2.6643903 20170530 for fd80000.gpu on minor 1 0.027659>] Console: switching to colour frame buffer device 160x50 0.090442>] tidss 30200000.dss: [drm] fb0: tidssdrmfb frame buffer device 0.050418>] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 0.108852>] xhci-hcd xhci-hcd.4.auto: xHCI Host Controller 0.001048>] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 0.005214>] xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 1 0.014538>] xhci-hcd xhci-hcd.4.auto: USB3 root hub has no ports 0.004654>] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 0.001481>] xhci-hcd xhci-hcd.4.auto: hcc params 0x0258fe6d hci version 0x110 quirks 0x0000008020000010 0.000081>] xhci-hcd xhci-hcd.4.auto: irq 522, io mem 0x31100000 0.022264>] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06 0.008509>] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 0.007489>] usb usb1: Product: xHCI Host Controller 0.005007>] usb usb1: Manufacturer: Linux 6.6.58-7.2.0-devel-g9d7c5d371546 xhci-hcd 0.007791>] usb usb1: SerialNumber: xhci-hcd.4.auto 0.005550>] hub 1-0:1.0: USB hub found 0.003968>] hub 1-0:1.0: 1 port detected 0.005320>] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 0.253795>] usb 1-1: new high-speed USB device number 2 using xhci-hcd 0.156699>] usb 1-1: New USB device found, idVendor=0424, idProduct=2744, bcdDevice= 2.21 0.010383>] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 0.007836>] usb 1-1: Product: USB2744 0.000011>] usb 1-1: Manufacturer: Microchip Tech 0.039884>] hub 1-1:1.0: USB hub found 0.006995>] hub 1-1:1.0: 4 ports detected 0.068195>] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 0.012359>] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 0.066403>] usbcore: registered new device driver onboard-usb-hub 0.231929>] hub 1-1:1.0: USB hub found 0.006485>] hub 1-1:1.0: 4 ports detected 0.059691>] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 0.093857>] hub 1-1:1.0: USB hub found 0.012646>] hub 1-1:1.0: 4 ports detected 0.054643>] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 0.288004>] usb 1-1.4: new high-speed USB device number 3 using xhci-hcd 0.091093>] Bluetooth: Core ver 2.22 0.006337>] NET: Registered PF_BLUETOOTH protocol family 0.007906>] Bluetooth: HCI device and connection manager initialized 0.008989>] Bluetooth: HCI socket layer initialized 0.000016>] Bluetooth: L2CAP socket layer initialized 0.000033>] Bluetooth: SCO socket layer initialized 0.024551>] usb 1-1.4: New USB device found, idVendor=0424, idProduct=2740, bcdDevice= 2.00 0.011423>] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 0.018297>] usb 1-1.4: Product: Hub Controller 0.011866>] configfs-gadget.g1 gadget.0: HOST MAC 6e:57:ac:54:7e:d4 0.010180>] configfs-gadget.g1 gadget.0: MAC 62:b0:6e:54:34:43 0.001748>] usb 1-1.4: Manufacturer: Microchip Tech 0.020317>] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 0.016622>] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 0.376172>] am65-cpsw-nuss 8000000.ethernet eth0: PHY [8000f00.mdio:00] driver [TI DP83867] (irq=386) 0.013339>] am65-cpsw-nuss 8000000.ethernet eth0: configuring for phy/rgmii-rxid link mode 0.095647>] am65-cpsw-nuss 8000000.ethernet eth1: PHY [8000f00.mdio:07] driver [Microchip KSZ9131 Gigabit PHY] (irq=392) 0.014571>] am65-cpsw-nuss 8000000.ethernet eth1: configuring for phy/rgmii-rxid link mode 0.019321>] cfg80211: Loading compiled-in X.509 certificates for regulatory database 0.024604>] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' 0.008901>] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600' 2.928831>] PVR_K: 448: RGX Firmware image 'rgx.fw.36.53.104.796' loaded 0.013552>] PVR_K: 448: Shader binary image 'rgx.sh.36.53.104.796' loaded 0.036143>] weston[448]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set 0.284782>] am65-cpsw-nuss 8000000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx 0.032705>] 8021q: 802.1Q VLAN Support v1.8 0.004437>] 8021q: adding VLAN 0 to HW filter on device eth0 0.005786>] 8021q: adding VLAN 0 to HW filter on device eth1 6.264679>] ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 0.008077>] platform fc40000.spi: deferred probe pending

Linux kernel is based on the latest 6.6 from TI, GIT sources here, https://git.toradex.com/cgit/linux-toradex.git/log/?h=toradex_ti-linux-6.6.y, based on TI SDK 10.01.10.04.

Board device tree file: https://git.toradex.com/cgit/linux-toradex.git/tree/arch/arm64/boot/dts/ti/k3-am62p5-verdin-wifi-dev.dts?h=toradex_ti-linux-6.6.y

Can you help?

1 month ago

0 Andreas Dannenberg 1 month ago

TI__Guru 65867 points

> kern :info : [ 0.153619 < 0.012380>] ti-sci 44043000.system-controller: ABI: 4.0 (firmware rev 0x000b '11.0.2-v11.00.02 (Fancy Rat)')

That could be where your issue is. That TIFS/DM FW version is associated with our upcoming SDK v11.0 (e/o March) that uses Kernel 6.12, whereas you are using Kernel 6.6. Can you instead use "firmware rev 0x000a '10.1.8--v10.01.08 (Fiery Fox)' with your Kernel? For both TIFS and DM. Also make sure you have the right board config associated with that SDK/Kernel Version (in U-Boot) so that resources can get allocated. Best would be to model after the current SDK v10.1 more closely.

Regards, Andreas

0 fd 1 month ago in reply to Andreas Dannenberg

Intellectual 665 points

Andreas Dannenberg

I can confirm that using the previous firmware it works as expected, so your suggestion was correct.

Whit that said the current solution is not really working for us, the expectation is that we have compatibility on the interface between the firmware and the OS driver.

We need this because

- the firmware/bootloader update workflow and the kernel/OS update workflow are not the same.

- meta-ti currently support both 6.6 and 6.12 kernel with this `TI_PREFERRED_BSP` variable (ti-6_6, ti-6_12, ...), and we need to be able to use the latest meta-ti scarthgap branch even when using the previous TI 6_6 kernel.

Any suggestion?

Just for reference, please find attached here the logs: AM62P_Latest_TISCI_Compatibility_Issue_With_TI_Linux_6_6.txt

0 Andreas Dannenberg 1 month ago in reply to fd

TI__Guru 65867 points

fd said:
I can confirm that using the previous firmware it works as expected, so your suggestion was correct.

Thanks for the confirmation.

fd said:
Whit that said the current solution is not really working for us, the expectation is that we have compatibility on the interface between the firmware and the OS driver.

Firmwares and Kernel should fundamentally work together when they use the same ABI level. For firmwares for SDK v10.x and SDKv11.x this is "ABI: 4.0" (see your boot log), so I'd expect things to work but I haven't analyzed this in detail. Was the firmware version the only difference between your NG and OG scenarios, or did you change anything else related to U-Boot?

Regards, Andreas

0 fd 1 month ago in reply to Andreas Dannenberg

Intellectual 665 points

Andreas Dannenberg said:
did you change anything else related to U-Boot?

Nothing else was changed

0 Andreas Dannenberg 1 month ago in reply to fd

TI__Guru 65867 points

Andreas Dannenberg said:
For firmwares for SDK v10.x and SDKv11.x this is "ABI: 4.0" (see your boot log), so I'd expect things to work but I haven't analyzed this in detail

I've reached out to our FW expert on this; will let you know what I can find out about the background here and if there's something we can do about this or better manage this.

fd said:
We need this because

- the firmware/bootloader update workflow and the kernel/OS update workflow are not the same.

- meta-ti currently support both 6.6 and 6.12 kernel with this `TI_PREFERRED_BSP` variable (ti-6_6, ti-6_12, ...), and we need to be able to use the latest meta-ti scarthgap branch even when using the previous TI 6_6 kernel.

Ideally you'd want to update those together but you do have a valid scenario there as well.

This may not be ideal, but you could have an additional small temporary initramfs-based Kernel/Filesystem (e.g., you could even bake the filesystem into a Kernel directly like shown here https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1259528/faq-sk-am62-how-to-build-initramfs-into-kernel-image resulting in a single-file solution), and update this one always together with the bootloader, and boot into that. And from this image is how you trigger/perform the update of your main filesystem/Kernel image.

Regards, Andreas

+1 Andreas Dannenberg 1 month ago in reply to Andreas Dannenberg

TI__Guru 65867 points

Hi fd,

Andreas Dannenberg said:
I've reached out to our FW expert on this; will let you know what I can find out about the background here and if there's something we can do about this or better manage this.

Discussing about this internally it sounded like there might have been an offline/IRC discussion about this with you as well. Just in case, here is what I found out about this scenario:

For TIFS/DM FW v11.x we added High Capacity BCDMA feature support, which requires and updated Resource Management (RM) board config to consume new firmware.

I haven't tried your specific scenario but first thing you need to do is to make sure your relevant config files are up-to-date in the state as they are used for SDK v11.x (see here https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62px?h=ti-u-boot-2025.01) and use this together with the v11.x TIFS/DM firmwares all as part of the U-Boot SW stack. Then you might be able to to use the different Kernels you are referring to without any issue, if this is where your disconnect is. For example, this commit here will be critical: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/board/ti/am62px/rm-cfg.yaml?h=ti-u-boot-2025.01&id=6905ef58d3e256e02c15fa995f5934eaa49b640d

Please let me know if that's not the case, which would mean you'd need corresponding Kernel changes as well.

Regards, Andreas

PS: I'll be on PTO until e/o March so further responses will be a bit delayed.

0 fd 1 month ago in reply to Andreas Dannenberg

Intellectual 665 points

Andreas Dannenberg said:
Discussing about this internally it sounded like there might have been an offline/IRC discussion about this with you as well.

Correct, on us to confirm the current findings, I am pretty confident this is the root cause and I'll confirm here once this is tested.

0 Parth Pancholi 28 days ago in reply to fd

Intellectual 360 points

Hi Andreas Dannenberg

Sorry to jump in, I’ve been actively testing this issue.

I ran a few tests with ti-linux-firmware 11.0.7--v11.00.07 (Fancy Rat), U-Boot (ti-u-boot-2024.04 based), and Linux (ti-linux-6.6.y based) on both our custom Verdin AM62P hardware and the TI AM62P SK board using the latest recommended config files (https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62px?h=ti-u-boot-2025.01).

Observations:

QSPI DMA Issue: The original ti-udma 485c0100.dma-controller: bchan0 cfg failed -22 error related to QSPI is no longer present.

CPSW Regression: Ethernet ports (CPSW) are not working in Linux.

[    1.851949] am65-cpsw-nuss 8000000.ethernet: initializing am65 cpsw nuss version 0x6BA01903, cpsw version 0x6BA81903 Ports: 3 quirks:00000006
[    1.864839] am65-cpsw-nuss 8000000.ethernet: initialized cpsw ale version 1.5
[    1.871976] am65-cpsw-nuss 8000000.ethernet: ALE Table size 512
[    1.878556] am65-cpsw-nuss 8000000.ethernet: CPTS ver 0x4e8a010d, freq:500000000, add_val:1 pps:0
[    1.889714] am65-cpsw-nuss 8000000.ethernet: Failed to get tx dma irq -6

I double-checked and confirmed that all relevant changes, including this commit ( https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2025.01&id=cc48dd0802c53a7876bdf720344225c034ad1ce5 ), are in my board config.
The same CPSW regression is also present on the TI AM62P SK board when using the latest config files with mentioned software configuration.

Could you help identify what might be missing here?

Logs:

AM62P SK board CPSW regression: /cfs-file/__key/communityserver-discussions-components-files/791/AM62P_5F00_SK_5F00_Board_5F00_CPSW_5F00_Not_5F00_Working_5F00_logs.txt
Custom AM62P Hardware (Verdin AM62P) board CPSW regression: /cfs-file/__key/communityserver-discussions-components-files/791/Verdin_5F00_AM62P_5F00_Board_5F00_CPSW_5F00_Not_5F00_Working_5F00_logs.txt

Our goal is to get QSPI working without DMA errors while ensuring there is no regression in critical functionality like CPSW/Ethernet ports on AM62P with:

ti-linux-firmware 11.0.7--v11.00.07 (Fancy Rat)
U-Boot (ti-u-boot-2024.04 based)
Linux (ti-linux-6.6.y based)

Thank you.

Regards,
Parth P

0 Andreas Dannenberg 28 days ago in reply to Parth Pancholi

TI__Guru 65867 points

Parth,

I'm out of the office until end of March. Will look into this after my return.

Regards, Andreas

0 Vishal Mahaveer 27 days ago in reply to Parth Pancholi

TI__Mastermind 33090 points

Hi Parth,

Can you check if this commit from 2025 u-boot is there in your code base?
https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2025.01&id=cc48dd0802c53a7876bdf720344225c034ad1ce5

Regards,
Vishal

0 Parth Pancholi 27 days ago in reply to Vishal Mahaveer

Intellectual 360 points

Hi Vishal Mahaveer,

As I mentioned, yes, this commit is part of my u-boot code base where I am testing.

Parth Pancholi said:
I double-checked and confirmed that all relevant changes, including this commit ( https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2025.01&id=cc48dd0802c53a7876bdf720344225c034ad1ce5 ), are in my board config.

Thank you.

Regards,
Parth P

+1 Vishal Mahaveer 27 days ago in reply to Parth Pancholi

TI__Mastermind 33090 points

Hi Parth,

Could you try picking up this Kernel change and test?
https://git.ti.com/gitweb?p=ti-linux-kernel/ti-linux-kernel.git;a=commit;h=2a22ced08c021e976c7c01b9d113ae16a77b03f2

Regards,
Vishal

0 Parth Pancholi 26 days ago in reply to Vishal Mahaveer

Intellectual 360 points

Hi Vishal Mahaveer,

With the kernel commit https://git.ti.com/gitweb?p=ti-linux-kernel/ti-linux-kernel.git;a=commit;h=2a22ced08c021e976c7c01b9d113ae16a77b03f2 and the latest U-Boot board configuration updates ( https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2025.01&id=cc48dd0802c53a7876bdf720344225c034ad1ce5 and https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/board/ti/am62px/rm-cfg.yaml?h=ti-u-boot-2025.01&id=6905ef58d3e256e02c15fa995f5934eaa49b640d ), I no longer observe the QSPI DMA errors, and both Ethernet (CPSW) ports appear to be functioning correctly.

However, I am now encountering a new regression in the suspend-resume use case, which previously worked fine. After resuming from suspend, not all CPU cores come back online failing the subsequent suspend-resume and other functionalities.

Full logs:
/cfs-file/__key/communityserver-discussions-components-files/791/Verdin_5F00_AM62P_5F00_DMA_5F00_CPSW_5F00_Working_5F00_Suspend_5F00_Resume_5F00_Broken_5F00_26032025.txt

I can confirm that this issue arises specifically after updating the U-Boot configuration files, as suspend-resume works fine with the mentioned Linux changes alone.

Could you help identify any missing changes in my U-Boot/Linux kernel setup that might be causing suspend-resume failures after syncing the latest tifs-rm-cfg and rm-cfg files?

Thank you.

Regards,
Parth P

0 Vishal Mahaveer 25 days ago in reply to Parth Pancholi

TI__Mastermind 33090 points

Hi Parth,

Parth Pancholi said:
I can confirm that this issue arises specifically after updating the U-Boot configuration files, as suspend-resume works fine with the mentioned Linux changes alone.

I don't think the behavior is related to the RM boardcfg update.

Can you share the build commands you used for building OPTEE?

Regards,
Vishal

0 Parth Pancholi 25 days ago in reply to Vishal Mahaveer

Intellectual 360 points

Hi Vishal Mahaveer,

I am using the following commands with suspend support enabled for TFA (K3_PM_SYSTEM_SUSPEND=1), as outlined in the SDK documentation.

https://software-dl.ti.com/processor-sdk-linux/esd/AM62PX/10_01_10_04/exports/docs/linux/Foundational_Components_OPTEE.html
https://software-dl.ti.com/processor-sdk-linux/esd/AM62PX/10_01_10_04/exports/docs/linux/Foundational_Components_ATF.html

As mentioned earlier, with the same setup, suspend-resume works fine without the RM boardcfg update, using the same OP-TEE and TFA builds.

TFA:
make ARCH=aarch64 CROSS_COMPILE="$CROSS_COMPILE_64" PLAT=k3 K3_PM_SYSTEM_SUSPEND=1 TARGET_BOARD=lite SPD=opteed

OPTEE:
make CROSS_COMPILE="$CROSS_COMPILE_32" CROSS_COMPILE64="$CROSS_COMPILE_64" PLATFORM=k3-am62px CFG_ARM64_core=y

Just to reiterate,

Our goal is to get QSPI working without DMA errors while ensuring there is no regression in critical functionality Suspend-Resume/Low-power modes, Ethernet, etc. on AM62P with:

ti-linux-firmware 11.0.7--v11.00.07 (Fancy Rat)
U-Boot (ti-u-boot-2024.04 based)
Linux (ti-linux-6.6.y based)

Regards,
Parth P

0 Vishal Mahaveer 25 days ago in reply to Parth Pancholi

TI__Mastermind 33090 points

Hi Parth,

I asked about OPTEE build command because we have a known issue of DeepSleep not functional if the logging is enabled in OPTEE.

Regards,
Vishal

0 Vishal Mahaveer 7 days ago in reply to Vishal Mahaveer

TI__Mastermind 33090 points

Hi Parth,

The logs you shared showed OPTEE debug flags.
Could you try by disabling the OPTEE debug flags?

We were not able to reproduce the issue with same combination of software components as you mentioned.

Regards,
Vishal

0 Parth Pancholi 7 days ago in reply to Vishal Mahaveer

Intellectual 360 points

Hello Vishal Mahaveer,

The previously mentioned suspend-resume regression is now resolved on my end, and the original Cadence QSPI probe failure due to the DMA issue is also resolved.

The root cause for the suspend-resume issue was the unsigned OP-TEE image, which prevented optee-rng from functioning correctly in Linux.

Thank you for your support.

Regards,
Parth P

Processors

Processors forum

AM62P: cadence-qspi probe failure