Regarding support in bringing up the ADRV9002 driver in the petalinux

Hi

In the design, we are using single ended clock source to DEV_CLK_IN+ (40MHz) and the other pin DEV_CLK_IN- is connected to ground. Attached the schematic snapshot. Is there any way to resolve this issue ?

Hi,

That ARM related error looks to be related with HW issues. Either that or, hopefully, it's just a matter of a mismatched profile. Which version of the driver are you using? Can you paste a complete boot log before trying to add any profile? Also important is, which version of TES are you using to generate the profiles?

- Nuno Sá

Hii Nuno Sa,

                     Thanks for reply.

                      Driver Version :- adrv9002 spi1.0: adrv9002-phy Rev 12.0, Firmware 0.20.0.10,Stream 0.7.9.0, API version: 48.49.2 

                     TES version  :-  Navis-0.20.0.  

i am also pasting the log here .

U-Boot 2021.01 (Jun 01 2021 - 11:54:06 +0000)

Board: Xilinx ZynqMP
DRAM: 2 GiB
PMUFW: v1.1
EL Level: EL2
Chip ID: zu9eg
NAND: ERROR:arasan_nand_reset timedout
ERROR:arasan_nand_cmd_function:command:0xff
ERROR:arasan_nand_read_buf timedout:Buff RDY
ERROR:arasan_nand_read_buf timedout:Xfer CMPLT
2048 MiB
MMC:
Loading Environment from SPIFlash... SF: Detected mt25qu02g with page size 256 Bytes, erase size 64 KiB, total 256 MiB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Bootmode: QSPI_MODE
Reset reason: EXTERNAL
Net:
ZYNQ GEM: ff0d0000, mdio bus ff0d0000, phyaddr -1, interface rgmii-id
ZYNQ GEM: requesting PHY reset gpio 70

Warning: ethernet@ff0d0000 (eth0) using random MAC address - 12:be:0b:e5:34:15
eth0: ethernet@ff0d0000
Hit any key to stop autoboot: 0
SF: Detected mt25qu02g with page size 256 Bytes, erase size 64 KiB, total 256 MiB
device 0 offset 0x3e80000, size 0x80000
SF: 524288 bytes @ 0x3e80000 Read: OK
QSPI: Trying to boot script at 20000000
## Executing script at 20000000
Trying to load boot images from qspi0
SF: Detected mt25qu02g with page size 256 Bytes, erase size 64 KiB, total 256 MiB
device 0 offset 0x3f00000, size 0x3700000
SF: 57671680 bytes @ 0x3f00000 Read: OK
## Loading kernel from FIT Image at 10000000 ...
Using 'conf-system-top.dtb' configuration
Trying 'kernel-1' kernel subimage
Description: Linux kernel
Created: 2022-04-01 15:02:14 UTC
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x10000100
Data Size: 11092900 Bytes = 10.6 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x00080000
Entry Point: 0x00080000
Hash algo: sha256
Hash value: 3c5686689f1b48f7c775985ec21ab71289c87f1146c75352f513fff2204b942e
Verifying Hash Integrity ... sha256+ OK
## Loading ramdisk from FIT Image at 10000000 ...
Using 'conf-system-top.dtb' configuration
Trying 'ramdisk-1' ramdisk subimage
Description: petalinux-image-minimal
Created: 2022-04-01 15:02:14 UTC
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x10a9eca0
Data Size: 45092799 Bytes = 43 MiB
Architecture: AArch64
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha256
Hash value: fb2b57e931b4740ec05786a02ee2dd20daa13d1909197f38811048baaf22c2a8
Verifying Hash Integrity ... sha256+ OK
## Loading fdt from FIT Image at 10000000 ...
Using 'conf-system-top.dtb' configuration
Trying 'fdt-system-top.dtb' fdt subimage
Description: Flattened Device Tree blob
Created: 2022-04-01 15:02:14 UTC
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x10a945b4
Data Size: 42524 Bytes = 41.5 KiB
Architecture: AArch64
Hash algo: sha256
Hash value: ef552f9d3b1bf312356cf183eced66087ac6af936ab2f1cc2dd99f4968426b48
Verifying Hash Integrity ... sha256+ OK
Booting using the fdt blob at 0x10a945b4
Uncompressing Kernel Image
Loading Ramdisk to 7b211000, end 7dd11fbf ... OK
Loading Device Tree to 000000007b203000, end 000000007b21061b ... OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.10.0-xilinx-v2021.1 (oe-user@oe-host) (aarch64-xilinx-linux-gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35.1) #1 SMP Fri Apr 1 15:02:14 UTC 2022
[ 0.000000] Machine model: xlnx,zynqmp
[ 0.000000] earlycon: cdns0 at MMIO 0x00000000ff010000 (options '115200n8')
[ 0.000000] printk: bootconsole [cdns0] enabled
[ 0.000000] efi: UEFI not found.
[ 0.000000] [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader!
[ 0.000000] cma: Reserved 256 MiB at 0x000000006b000000
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000000000-0x000000003fffffff]
[ 0.000000] DMA32 [mem 0x0000000040000000-0x000000007fefffff]
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x000000007fefffff]
[ 0.000000] Zeroed struct page in unavailable ranges: 256 pages
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fefffff]
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.1 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
[ 0.000000] psci: SMC Calling Convention v1.2
[ 0.000000] percpu: Embedded 22 pages/cpu s50968 r8192 d30952 u90112
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: detected: ARM erratum 845719
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 515844
[ 0.000000] Kernel command line: earlycon console=ttyPS0,115200 clk_ignore_unused cpuidle.off=1
[ 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] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] software IO TLB: mapped [mem 0x000000003bfff000-0x000000003ffff000] (64MB)
[ 0.000000] Memory: 1650688K/2096128K available (15872K kernel code, 1690K rwdata, 11976K rodata, 2624K init, 516K bss, 183296K reserved, 262144K cma-reserved)
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU event tracing is enabled.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 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] GIC: Adjusting CPU interface base to 0x00000000f902f000
[ 0.000000] GIC: Using split EOI/Deactivate mode
[ 0.000000] random: get_random_bytes called from start_kernel+0x31c/0x524 with crng_init=0
[ 0.000000] arch_timer: cp15 timer(s) running at 100.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x171024e7e0, max_idle_ns: 440795205315 ns
[ 0.000003] sched_clock: 56 bits at 100MHz, resolution 10ns, wraps every 4398046511100ns
[ 0.008424] Console: colour dummy device 80x25
[ 0.012481] Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=400000)
[ 0.022841] pid_max: default: 32768 minimum: 301
[ 0.027588] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.034786] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.043605] rcu: Hierarchical SRCU implementation.
[ 0.047524] EFI services will not be available.
[ 0.051963] smp: Bringing up secondary CPUs ...
[ 0.056693] Detected VIPT I-cache on CPU1
[ 0.056733] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 0.057135] Detected VIPT I-cache on CPU2
[ 0.057159] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 0.057539] Detected VIPT I-cache on CPU3
[ 0.057562] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 0.057610] smp: Brought up 1 node, 4 CPUs
[ 0.091780] SMP: Total of 4 processors activated.
[ 0.096452] CPU features: detected: 32-bit EL0 Support
[ 0.101556] CPU features: detected: CRC32 instructions
[ 0.106694] CPU: All CPU(s) started at EL2
[ 0.110736] alternatives: patching kernel code
[ 0.116230] devtmpfs: initialized
[ 0.122758] Registered cp15_barrier emulation handler
[ 0.123451] Registered setend emulation handler
[ 0.128054] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.137636] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[ 0.150413] pinctrl core: initialized pinctrl subsystem
[ 0.151082] NET: Registered protocol family 16
[ 0.155758] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
[ 0.161482] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.169204] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.177033] audit: initializing netlink subsys (disabled)
[ 0.182437] audit: type=2000 audit(0.116:1): state=initialized audit_enabled=0 res=1
[ 0.182762] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.196854] ASID allocator initialised with 65536 entries
[ 0.220063] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.221121] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[ 0.227794] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.234455] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[ 1.300186] DRBG: Continuing without Jitter RNG
[ 1.377909] raid6: neonx8 gen() 2148 MB/s
[ 1.445966] raid6: neonx8 xor() 1597 MB/s
[ 1.514033] raid6: neonx4 gen() 2191 MB/s
[ 1.582090] raid6: neonx4 xor() 1566 MB/s
[ 1.650166] raid6: neonx2 gen() 2078 MB/s
[ 1.718221] raid6: neonx2 xor() 1436 MB/s
[ 1.786285] raid6: neonx1 gen() 1770 MB/s
[ 1.854344] raid6: neonx1 xor() 1219 MB/s
[ 1.922414] raid6: int64x8 gen() 1438 MB/s
[ 1.990474] raid6: int64x8 xor() 771 MB/s
[ 2.058544] raid6: int64x4 gen() 1602 MB/s
[ 2.126598] raid6: int64x4 xor() 817 MB/s
[ 2.194687] raid6: int64x2 gen() 1398 MB/s
[ 2.262742] raid6: int64x2 xor() 748 MB/s
[ 2.330804] raid6: int64x1 gen() 1033 MB/s
[ 2.398882] raid6: int64x1 xor() 517 MB/s
[ 2.398920] raid6: using algorithm neonx4 gen() 2191 MB/s
[ 2.402878] raid6: .... xor() 1566 MB/s, rmw enabled
[ 2.407809] raid6: using neon recovery algorithm
[ 2.412799] iommu: Default domain type: Translated
[ 2.417456] SCSI subsystem initialized
[ 2.421110] usbcore: registered new interface driver usbfs
[ 2.426433] usbcore: registered new interface driver hub
[ 2.431710] usbcore: registered new device driver usb
[ 2.436828] mc: Linux media interface: v0.10
[ 2.440955] videodev: Linux video capture interface: v2.00
[ 2.446451] EDAC MC: Ver: 3.0.0
[ 2.449896] zynqmp-ipi-mbox mailbox@ff990400: Registered ZynqMP IPI mbox with TX/RX channels.
[ 2.458256] jesd204: found 0 devices and 0 topologies
[ 2.463026] FPGA manager framework
[ 2.466491] Advanced Linux Sound Architecture Driver Initialized.
[ 2.472806] Bluetooth: Core ver 2.22
[ 2.475982] NET: Registered protocol family 31
[ 2.480383] Bluetooth: HCI device and connection manager initialized
[ 2.486700] Bluetooth: HCI socket layer initialized
[ 2.491542] Bluetooth: L2CAP socket layer initialized
[ 2.496566] Bluetooth: SCO socket layer initialized
[ 2.501722] clocksource: Switched to clocksource arch_sys_counter
[ 2.507595] VFS: Disk quotas dquot_6.6.0
[ 2.511397] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 2.522295] NET: Registered protocol family 2
[ 2.522860] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[ 2.531015] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 2.538960] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
[ 2.546320] TCP: Hash tables configured (established 16384 bind 16384)
[ 2.552678] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[ 2.559312] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[ 2.566481] NET: Registered protocol family 1
[ 2.570997] RPC: Registered named UNIX socket transport module.
[ 2.576581] RPC: Registered udp transport module.
[ 2.581244] RPC: Registered tcp transport module.
[ 2.585915] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 2.592903] PCI: CLS 0 bytes, default 64
[ 2.596319] Trying to unpack rootfs image as initramfs...
[ 4.799756] Freeing initrd memory: 44032K
[ 4.800309] hw perfevents: no interrupt-affinity property for /pmu, guessing.
[ 4.805436] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[ 4.813788] Initialise system trusted keyrings
[ 4.817448] workingset: timestamp_bits=46 max_order=19 bucket_order=0
[ 4.824453] NFS: Registering the id_resolver key type
[ 4.828769] Key type id_resolver registered
[ 4.832908] Key type id_legacy registered
[ 4.836903] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 4.843561] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 4.886144] NET: Registered protocol family 38
[ 4.886187] xor: measuring software checksum speed
[ 4.893883] 8regs : 2363 MB/sec
[ 4.897544] 32regs : 2799 MB/sec
[ 4.902497] arm64_neon : 2380 MB/sec
[ 4.902681] xor: using function: 32regs (2799 MB/sec)
[ 4.907708] Key type asymmetric registered
[ 4.911769] Asymmetric key parser 'x509' registered
[ 4.916632] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[ 4.923967] io scheduler mq-deadline registered
[ 4.928463] io scheduler kyber registered
[ 4.959226] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 4.963284] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 4.970531] brd: module loaded
[ 4.975034] loop: module loaded
[ 4.975309] Registered mathworks_ip class
[ 4.978555] libphy: Fixed MDIO Bus: probed
[ 4.981611] tun: Universal TUN/TAP device driver, 1.6
[ 4.985713] CAN device driver interface
[ 4.990092] usbcore: registered new interface driver asix
[ 4.994812] usbcore: registered new interface driver ax88179_178a
[ 5.000853] usbcore: registered new interface driver cdc_ether
[ 5.006645] usbcore: registered new interface driver net1080
[ 5.012266] usbcore: registered new interface driver cdc_subset
[ 5.018148] usbcore: registered new interface driver zaurus
[ 5.023695] usbcore: registered new interface driver cdc_ncm
[ 5.029994] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 5.035776] ehci-pci: EHCI PCI platform driver
[ 5.040548] usbcore: registered new interface driver uas
[ 5.045500] usbcore: registered new interface driver usb-storage
[ 5.051489] usbcore: registered new interface driver usbserial_generic
[ 5.057935] usbserial: USB Serial support registered for generic
[ 5.063907] usbcore: registered new interface driver ftdi_sio
[ 5.069608] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 5.076881] usbcore: registered new interface driver upd78f0730
[ 5.082757] usbserial: USB Serial support registered for upd78f0730
[ 5.090319] rtc_zynqmp ffa60000.rtc: registered as rtc0
[ 5.094181] rtc_zynqmp ffa60000.rtc: setting system clock to 2035-10-16T11:33:10 UTC (2076147190)
[ 5.103030] i2c /dev entries driver
[ 5.108126] usbcore: registered new interface driver uvcvideo
[ 5.112157] USB Video Class driver (1.1.1)
[ 5.117142] Bluetooth: HCI UART driver ver 2.3
[ 5.120636] Bluetooth: HCI UART protocol H4 registered
[ 5.125737] Bluetooth: HCI UART protocol BCSP registered
[ 5.131029] Bluetooth: HCI UART protocol LL registered
[ 5.136116] Bluetooth: HCI UART protocol ATH3K registered
[ 5.141490] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 5.147742] Bluetooth: HCI UART protocol Intel registered
[ 5.153083] Bluetooth: HCI UART protocol QCA registered
[ 5.158284] usbcore: registered new interface driver bcm203x
[ 5.163906] usbcore: registered new interface driver bpa10x
[ 5.169443] usbcore: registered new interface driver bfusb
[ 5.174893] usbcore: registered new interface driver btusb
[ 5.180352] usbcore: registered new interface driver ath3k
[ 5.185847] EDAC MC: ECC not enabled
[ 5.189449] EDAC DEVICE0: Giving out device to module zynqmp-ocm-edac controller zynqmp_ocm: DEV ff960000.memory-controller (INTERRUPT)
[ 5.201754] sdhci: Secure Digital Host Controller Interface driver
[ 5.207566] sdhci: Copyright(c) Pierre Ossman
[ 5.211888] sdhci-pltfm: SDHCI platform and OF driver helper
[ 5.217858] ledtrig-cpu: registered to indicate activity on CPUs
[ 5.223494] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[ 5.229926] zynqmp_firmware_probe Platform Management API v1.1
[ 5.235680] zynqmp_firmware_probe Trustzone version v1.0
[ 5.293548] zynqmp-aes firmware:zynqmp-firmware:zynqmp-aes: will run requests pump with realtime priority
[ 5.313450] alg: No test for xilinx-keccak-384 (zynqmp-keccak-384)
[ 5.314185] alg: No test for xilinx-zynqmp-rsa (zynqmp-rsa)
[ 5.319709] usbcore: registered new interface driver usbhid
[ 5.325070] usbhid: USB HID core driver
[ 5.335397] axi_sysid 85000000.axi-sysid-0: AXI System ID core version (1.01.a) found
[ 5.337740] axi_sysid 85000000.axi-sysid-0: system ID header version mismatch. Expected 2, Reported 0
[ 5.346765] axi_sysid: probe of 85000000.axi-sysid-0 failed with error -14
[ 5.354025] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered
[ 5.360452] usbcore: registered new interface driver snd-usb-audio
[ 5.367759] pktgen: Packet Generator for packet performance testing. Version: 2.75
[ 5.374268] Initializing XFRM netlink socket
[ 5.377957] NET: Registered protocol family 10
[ 5.382714] Segment Routing with IPv6
[ 5.386083] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 5.392160] NET: Registered protocol family 17
[ 5.396235] NET: Registered protocol family 15
[ 5.400714] can: controller area network core
[ 5.404984] NET: Registered protocol family 29
[ 5.409377] can: raw protocol
[ 5.412312] can: broadcast manager protocol
[ 5.416466] can: netlink gateway - max_hops=1
[ 5.420865] Bluetooth: RFCOMM TTY layer initialized
[ 5.425640] Bluetooth: RFCOMM socket layer initialized
[ 5.430746] Bluetooth: RFCOMM ver 1.11
[ 5.434459] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.439729] Bluetooth: BNEP filters: protocol multicast
[ 5.444923] Bluetooth: BNEP socket layer initialized
[ 5.449851] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 5.455734] Bluetooth: HIDP socket layer initialized
[ 5.460793] 9pnet: Installing 9P2000 support
[ 5.464929] NET: Registered protocol family 36
[ 5.469328] Key type dns_resolver registered
[ 5.473744] registered taskstats version 1
[ 5.477612] Loading compiled-in X.509 certificates
[ 5.482776] Btrfs loaded, crc32c=crc32c-generic
[ 5.495520] ff010000.serial: ttyPS0 at MMIO 0xff010000 (irq = 50, base_baud = 6250000) is a xuartps
[ 5.504539] printk: console [ttyPS0] enabled
[ 5.504539] printk: console [ttyPS0] enabled
[ 5.508834] printk: bootconsole [cdns0] disabled
[ 5.508834] printk: bootconsole [cdns0] disabled
[ 5.518146] of-fpga-region fpga-full: FPGA Region probed
[ 5.529146] xilinx-zynqmp-dma fd500000.dma: ZynqMP DMA driver Probe success
[ 5.536330] xilinx-zynqmp-dma fd510000.dma: ZynqMP DMA driver Probe success
[ 5.543507] xilinx-zynqmp-dma fd520000.dma: ZynqMP DMA driver Probe success
[ 5.550689] xilinx-zynqmp-dma fd530000.dma: ZynqMP DMA driver Probe success
[ 5.557871] xilinx-zynqmp-dma fd540000.dma: ZynqMP DMA driver Probe success
[ 5.565044] xilinx-zynqmp-dma fd550000.dma: ZynqMP DMA driver Probe success
[ 5.572218] xilinx-zynqmp-dma fd560000.dma: ZynqMP DMA driver Probe success
[ 5.579398] xilinx-zynqmp-dma fd570000.dma: ZynqMP DMA driver Probe success
[ 5.586639] xilinx-zynqmp-dma ffa80000.dma: ZynqMP DMA driver Probe success
[ 5.593833] xilinx-zynqmp-dma ffa90000.dma: ZynqMP DMA driver Probe success
[ 5.601008] xilinx-zynqmp-dma ffaa0000.dma: ZynqMP DMA driver Probe success
[ 5.608178] xilinx-zynqmp-dma ffab0000.dma: ZynqMP DMA driver Probe success
[ 5.615347] xilinx-zynqmp-dma ffac0000.dma: ZynqMP DMA driver Probe success
[ 5.622526] xilinx-zynqmp-dma ffad0000.dma: ZynqMP DMA driver Probe success
[ 5.629696] xilinx-zynqmp-dma ffae0000.dma: ZynqMP DMA driver Probe success
[ 5.636872] xilinx-zynqmp-dma ffaf0000.dma: ZynqMP DMA driver Probe success
[ 5.644191] zynqmp_pll_disable() clock disable failed for rpll_int, ret = -13
[ 5.655987] ------------[ cut here ]------------
[ 5.660609] /axi/spi@ff050000/spidev@0x00: buggy DT: spidev listed directly in DT
[ 5.668131] WARNING: CPU: 0 PID: 30 at drivers/spi/spidev.c:741 spidev_probe+0x164/0x1e4
[ 5.676206] Modules linked in:
[ 5.679256] CPU: 0 PID: 30 Comm: kworker/0:1 Not tainted 5.10.0-xilinx-v2021.1 #1
[ 5.686726] Hardware name: xlnx,zynqmp (DT)
[ 5.690899] Workqueue: events deferred_probe_work_func
[ 5.696025] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--)
[ 5.702022] pc : spidev_probe+0x164/0x1e4
[ 5.706015] lr : spidev_probe+0x164/0x1e4
[ 5.710006] sp : ffffffc01217b7c0
[ 5.713304] x29: ffffffc01217b7c0 x28: 0000000000000000
[ 5.718608] x27: ffffff80402947c8 x26: 0000000000000000
[ 5.723911] x25: ffffffc011ee23e0 x24: ffffff807cd40000
[ 5.729214] x23: 000000000000001a x22: ffffffc011eeba08
[ 5.734518] x21: ffffffc011eeb9e8 x20: ffffff807cd40000
[ 5.739821] x19: 0000000000000000 x18: 0000000000000030
[ 5.745125] x17: 0000000000000002 x16: 0000ab6e00306d64
[ 5.750428] x15: ffffff8040275598 x14: 3030303530666640
[ 5.755732] x13: ffffffc011e7db70 x12: 0000000000000351
[ 5.761035] x11: 000000000000011b x10: ffffffc011ea9b70
[ 5.766339] x9 : 00000000fffff800 x8 : ffffffc011e7db70
[ 5.771642] x7 : ffffffc011ea9b70 x6 : 0000000000000000
[ 5.776946] x5 : 0000000000005ff4 x4 : 0000000000000000
[ 5.782249] x3 : 0000000000000000 x2 : 00000000ffffffff
[ 5.787553] x1 : a9e33a2f7f802500 x0 : 0000000000000000
[ 5.792856] Call trace:
[ 5.795290] spidev_probe+0x164/0x1e4
[ 5.798943] spi_drv_probe+0x80/0xe0
[ 5.802502] really_probe+0xe8/0x4b4
[ 5.806070] driver_probe_device+0x58/0xc0
[ 5.810158] __device_attach_driver+0xa8/0x10c
[ 5.814584] bus_for_each_drv+0x78/0xd0
[ 5.818403] __device_attach+0xdc/0x17c
[ 5.822223] device_initial_probe+0x14/0x20
[ 5.826389] bus_probe_device+0x9c/0xa4
[ 5.830208] device_add+0x328/0x714
[ 5.833681] spi_add_device+0xbc/0x1b0
[ 5.837413] of_register_spi_device+0x230/0x380
[ 5.841935] spi_register_controller+0x7bc/0x800
[ 5.846536] cdns_spi_probe+0x29c/0x380
[ 5.850365] platform_drv_probe+0x54/0xb0
[ 5.854365] really_probe+0xe8/0x4b4
[ 5.857924] driver_probe_device+0x58/0xc0
[ 5.862003] __device_attach_driver+0xa8/0x10c
[ 5.866430] bus_for_each_drv+0x78/0xd0
[ 5.870250] __device_attach+0xdc/0x17c
[ 5.874069] device_initial_probe+0x14/0x20
[ 5.878235] bus_probe_device+0x9c/0xa4
[ 5.882054] deferred_probe_work_func+0x74/0xb0
[ 5.886569] process_one_work+0x1d4/0x380
[ 5.890569] worker_thread+0x298/0x4e0
[ 5.894303] kthread+0x124/0x130
[ 5.897522] ret_from_fork+0x10/0x3c
[ 5.901088] ---[ end trace 04d6482447f4c774 ]---
[ 5.906666] spi-nor spi0.0: SPI-NOR-UniqueID 1044003eda0b00180f00220058198125d7
[ 5.914562] spi-nor spi0.0: trying to lock already unlocked area
[ 5.920568] spi-nor spi0.0: mt25qu02g (262144 Kbytes)
[ 5.926958] macb ff0d0000.ethernet: Not enabling partial store and forward
[ 5.939436] libphy: MACB_mii_bus: probed
[ 5.943410] macb ff0d0000.ethernet eth0: Cadence GEM rev 0x50070106 at 0xff0d0000 irq 38 (12:be:0b:e5:34:15)
[ 5.953722] xilinx-axipmon ffa00000.perf-monitor: Probed Xilinx APM
[ 5.960311] xilinx-axipmon fd0b0000.perf-monitor: Probed Xilinx APM
[ 5.966847] xilinx-axipmon fd490000.perf-monitor: Probed Xilinx APM
[ 5.973372] xilinx-axipmon ffa10000.perf-monitor: Probed Xilinx APM
[ 5.980197] cdns-i2c ff020000.i2c: 400 kHz mmio ff020000 irq 40
[ 5.986624] i2c i2c-1: of_i2c: modalias failure on /axi/i2c@ff030000/i2c-mux@75
[ 5.993935] i2c i2c-1: Failed to create I2C device for /axi/i2c@ff030000/i2c-mux@75
[ 6.001605] cdns-i2c ff030000.i2c: 400 kHz mmio ff030000 irq 41
[ 6.007973] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for freq 1200000000 (-34)
[ 6.016712] cpufreq: cpufreq_online: CPU0: Running at unlisted initial frequency: 1200000 KHz, changing to: 1199999 KHz
[ 6.027504] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for freq 1200000000 (-34)
[ 6.079565] random: fast init done
[ 7.170834] random: crng init done
[ 14.224196] adrv9002 spi1.0: adrv9002-phy Rev 12.0, Firmware 0.20.0.10, Stream 0.7.9.0, API version: 48.49.2 successfully initialized
[ 14.237533] cf_axi_adc 84a00000.axi-adrv9002-rx-lpc: ADI AIM (10.01.b) at 0x84A00000 mapped to 0x00000000f846fe1e, probed ADC ADRV9002 as MASTER
[ 14.251727] cf_axi_tdd 84a0c800.axi-adrv9002-core-tdd1-lpc: Analog Devices CF_AXI_TDD MASTER (1.00.a)
[ 14.261568] cf_axi_tdd 84a0cc00.axi-adrv9002-core-tdd2-lpc: Analog Devices CF_AXI_TDD MASTER (1.00.a)
[ 14.289993] cf_axi_dds 84a0a000.axi-adrv9002-tx-lpc: Analog Devices CF_AXI_DDS_DDS MASTER (9.01.b) at 0x84A0A000 mapped to 0x00000000cabb78cf, probed DDS ADRV9002
[ 14.321991] cf_axi_dds 84a0c000.axi-adrv9002-tx2-lpc: Analog Devices CF_AXI_DDS_DDS MASTER (9.01.b) at 0x84A0C000 mapped to 0x00000000c62d1bb6, probed DDS ADRV9002
[ 14.339115] of_cfs_init
[ 14.341569] of_cfs_init: OK
[ 14.344501] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 14.482491] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 14.489027] clk: Not disabling unused clocks
[ 14.493506] ALSA device list:
[ 14.496467] No soundcards found.
[ 14.500161] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 14.508775] cfg80211: failed to load regulatory.db
[ 14.509615] Freeing unused kernel memory: 2624K
[ 14.541795] Run /init as init process
INIT: version 2.97 booting
Starting udev
[ 14.672845] udevd[141]: starting version 3.2.9
[ 14.683058] udevd[142]: starting eudev-3.2.9
Starting tcf-agent: OK

PetaLinux 2021.1 xilinx-uetc ttyPS0

root@xilinx-uetc:~# cd ../..
root@xilinx-uetc:/# ls
bin boot dev etc home init lib log_lock.pid media mnt proc root run sbin sys tmp usr var
root@xilinx-uetc:/# cd sys/bus/iio/devices
root@xilinx-uetc:/sys/bus/iio/devices# ls
iio:device0 iio:device1 iio:device2 iio:device3 iio:device4 iio:device5 iio:device6 iio:device7 iio_sysfs_trigger
root@xilinx-uetc:/sys/bus/iio/devices# cd iio:device1
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1# ls
dev in_voltage1_bbdc_rejection_en out_voltage0_atten_control_mode_available
frequency_hopping_hop1_signal_trigger in_voltage1_bbdc_rejection_tracking_en out_voltage0_close_loop_gain_tracking_en
frequency_hopping_hop1_table_a in_voltage1_decimated_power out_voltage0_en
frequency_hopping_hop1_table_b in_voltage1_digital_gain_control_mode out_voltage0_ensm_mode
frequency_hopping_hop1_table_select in_voltage1_digital_gain_control_mode_available out_voltage0_ensm_mode_available
frequency_hopping_hop2_signal_trigger in_voltage1_dynamic_adc_switch_en out_voltage0_hardwaregain
frequency_hopping_hop2_table_a in_voltage1_en out_voltage0_lo_leakage_tracking_en
frequency_hopping_hop2_table_b in_voltage1_ensm_mode out_voltage0_loopback_delay_tracking_en
frequency_hopping_hop2_table_select in_voltage1_ensm_mode_available out_voltage0_nco_frequency
frequency_hopping_hop_table_select_available in_voltage1_gain_control_mode out_voltage0_pa_correction_tracking_en
in_temp0_input in_voltage1_gain_control_mode_available out_voltage0_port_en_mode
in_voltage0_agc_tracking_en in_voltage1_hardwaregain out_voltage0_port_en_mode_available
in_voltage0_bbdc_loop_gain_raw in_voltage1_hd_tracking_en out_voltage0_quadrature_tracking_en
in_voltage0_bbdc_rejection_en in_voltage1_interface_gain out_voltage0_rf_bandwidth
in_voltage0_bbdc_rejection_tracking_en in_voltage1_interface_gain_available out_voltage0_sampling_frequency
in_voltage0_decimated_power in_voltage1_nco_frequency out_voltage1_atten_control_mode
in_voltage0_digital_gain_control_mode in_voltage1_orx_bbdc_rejection_en out_voltage1_atten_control_mode_available
in_voltage0_digital_gain_control_mode_available in_voltage1_orx_en out_voltage1_close_loop_gain_tracking_en
in_voltage0_dynamic_adc_switch_en in_voltage1_orx_hardwaregain out_voltage1_en
in_voltage0_en in_voltage1_orx_quadrature_w_poly_tracking_en out_voltage1_ensm_mode
in_voltage0_ensm_mode in_voltage1_port_en_mode out_voltage1_ensm_mode_available
in_voltage0_ensm_mode_available in_voltage1_port_en_mode_available out_voltage1_hardwaregain
in_voltage0_gain_control_mode in_voltage1_quadrature_fic_tracking_en out_voltage1_lo_leakage_tracking_en
in_voltage0_gain_control_mode_available in_voltage1_quadrature_w_poly_tracking_en out_voltage1_loopback_delay_tracking_en
in_voltage0_hardwaregain in_voltage1_rf_bandwidth out_voltage1_nco_frequency
in_voltage0_hd_tracking_en in_voltage1_rfdc_tracking_en out_voltage1_pa_correction_tracking_en
in_voltage0_interface_gain in_voltage1_rssi out_voltage1_port_en_mode
in_voltage0_interface_gain_available in_voltage1_rssi_tracking_en out_voltage1_port_en_mode_available
in_voltage0_nco_frequency in_voltage1_sampling_frequency out_voltage1_quadrature_tracking_en
in_voltage0_orx_bbdc_rejection_en in_voltage2_en out_voltage1_rf_bandwidth
in_voltage0_orx_en in_voltage2_input out_voltage1_sampling_frequency
in_voltage0_orx_hardwaregain in_voltage3_en out_voltage2_en
in_voltage0_orx_quadrature_w_poly_tracking_en in_voltage3_input out_voltage2_input
in_voltage0_port_en_mode in_voltage4_en out_voltage3_en
in_voltage0_port_en_mode_available in_voltage4_input out_voltage3_input
in_voltage0_quadrature_fic_tracking_en in_voltage5_en out_voltage4_en
in_voltage0_quadrature_w_poly_tracking_en in_voltage5_input out_voltage4_input
in_voltage0_rf_bandwidth name out_voltage5_en
in_voltage0_rfdc_tracking_en of_node out_voltage5_input
in_voltage0_rssi out_altvoltage0_RX1_LO_frequency power
in_voltage0_rssi_tracking_en out_altvoltage1_RX2_LO_frequency profile_config
in_voltage0_sampling_frequency out_altvoltage2_TX1_LO_frequency stream_config
in_voltage1_agc_tracking_en out_altvoltage3_TX2_LO_frequency subsystem
in_voltage1_bbdc_loop_gain_raw out_voltage0_atten_control_mode uevent
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1# cat in_voltage0_ensm_mode_available
calibrated primed rf_enabled

root@xilinx-uetc:/sys/bus/iio/devices/iio:device1# echo calibrated > in_voltage0_ensm_mode
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1# cat in_voltage0_ensm_mode_available
calibrated primed rf_enabled
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1# cat in_voltage0_ensm_mode
calibrated

root@xilinx-uetc:/sys/bus/iio/devices/iio:device1#
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1# ifconfig 192.168.1.10
ifconfig: 192.168.1.10: error fetching interface information: Device not found
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1# ifconfig eth0 192.168.1.10
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1#
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1# passwd
New password:
Retype new password:
passwd: password updated successfully
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1#
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1# cat /tmp/test.bin > stream_config
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1#
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1# cat /tmp/test.json > profile_config
[ 238.696621] adrv9002 spi1.0: [ERROR]: Error number 1 (0x00000001), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_powermanagement.c, in function adi_adrv9001_powermanagement_Configure_Validate, in line 39, variable name readPattern.Error message ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board.
[ 238.731630] adrv9002 spi1.0: [ERROR]: Error number 1 (0x00000001), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_powermanagement.c, in function adi_adrv9001_powermanagement_Configure, in line 70, variable name NULL.Error message ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board.
[ 238.765248] adrv9002 spi1.0: adrv9002_power_mgmt_config, 2597: failed with "ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board" (1)
[ 240.241544] adrv9002 spi1.0: [ERROR]: Error number 1 (0x00000001), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_powermanagement.c, in function adi_adrv9001_powermanagement_Configure_Validate, in line 39, variable name readPattern.Error message ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board.
[ 240.276558] adrv9002 spi1.0: [ERROR]: Error number 1 (0x00000001), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_powermanagement.c, in function adi_adrv9001_powermanagement_Configure, in line 70, variable name NULL.Error message ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board.
[ 240.310168] adrv9002 spi1.0: adrv9002_power_mgmt_config, 2597: failed with "ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board" (1)
cat: write error: Invalid argument
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1#

root@xilinx-uetc:/sys/bus/iio/devices/iio:device1# iio_info | grep iio:device
iio:device0: ams
iio:device1: adrv9002-phy
[ 297.731929] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -101.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_arm.c, in function adi_adrv9001_arm_CmdStatus_Wait, in line 679, variable name device.Error message ArmCmdStatusWait() failed due to thrown ARM error. ARM time out .
[ 297.760859] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -101.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001.c, in function adi_adrv9001_Temperature_Get, in line 556, variable name NULL.Error message ArmCmdStatusWait() failed due to thrown ARM error. ARM time out .
[ 297.789000] adrv9002 spi1.0: adrv9002_phy_read_raw_no_rf_chan, 1809: failed with "ArmCmdStatusWait() failed due to thrown ARM error. ARM time out " (3)
[ 297.802802] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_fh.c, in function adi_adrv9001_fh_HopTable_Get, in line 963, variable name devStateInfo->frequencyHoppingEnabled.Error message Frequency hopping not enabled in device profile.
[ 297.832417] adrv9002 spi1.0: adrv9002_attr_show, 571: failed with "Frequency hopping not enabled in device profile" (3)
[ 297.843338] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_fh.c, in function adi_adrv9001_fh_HopTable_Get, in line 963, variable name devStateInfo->frequencyHoppingEnabled.Error message Frequency hopping not enabled in device profile.
[ 297.872950] adrv9002 spi1.0: adrv9002_attr_show, 571: failed with "Frequency hopping not enabled in device profile" (3)
[ 299.968781] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -101.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_arm.c, in function adi_adrv9001_arm_Cmd_Write, in line 774, variable name device.Error message ARM Mailbox Busy. Command not executed in ArmCmdWrite().
[ 299.996502] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -101.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_fh.c, in function adi_adrv9001_fh_Configuration_Inspect, in line 623, variable name NULL.Error message ARM Mailbox Busy. Command not executed in ArmCmdWrite().
[ 300.024906] adrv9002 spi1.0: adrv9002_fh_config_dump_show, 936: failed with "ARM Mailbox Busy. Command not executed in ArmCmdWrite()" (3)
[ 300.037456] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_fh.c, in function adi_adrv9001_fh_HopTable_Inspect_Validate, in line 413, variable name devStateInfo->frequencyHoppingEnabled.Error message Frequency hopping not enabled in device profile.
[ 300.068208] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_fh.c, in function adi_adrv9001_fh_HopTable_Inspect, in line 863, variable name NULL.Error message Frequency hopping not enabled in device profile.
[ 300.095320] adrv9002 spi1.0: adrv9002_hop_table_dump_show, 993: failed with "Frequency hopping not enabled in device profile" (3)
[ 300.107000] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_fh.c, in function adi_adrv9001_fh_HopTable_Inspect_Validate, in line 413, variable name devStateInfo->frequencyHoppingEnabled.Error message Frequency hopping not enabled in device profile.
[ 300.137756] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_fh.c, in function adi_adrv9001_fh_HopTable_Inspect, in line 863, variable name NULL.Error message Frequency hopping not enabled in device profile.
[ 300.164849] adrv9002 spi1.0: adrv9002_hop_table_dump_show, 993: failed with "Frequency hopping not enabled in device profile" (3)
[ 300.176611] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_fh.c, in function adi_adrv9001_fh_HopTable_Inspect_Validate, in line 413, variable name devStateInfo->frequencyHoppingEnabled.Error message Frequency hopping not enabled in device profile.
[ 300.207367] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_fh.c, in function adi_adrv9001_fh_HopTable_Inspect, in line 863, variable name NULL.Error message Frequency hopping not enabled in device profile.
[ 300.234478] adrv9002 spi1.0: adrv9002_hop_table_dump_show, 993: failed with "Frequency hopping not enabled in device profile" (3)
[ 300.246173] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_fh.c, in function adi_adrv9001_fh_HopTable_Inspect_Validate, in line 413, variable name devStateInfo->frequencyHoppingEnabled.Error message Frequency hopping not enabled in device profile.
[ 300.276927] adrv9002 spi1.0: [ERROR]: Error number 3 (0x00000003), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_fh.c, in function adi_adrv9001_fh_HopTable_Inspect, in line 863, variable name NULL.Error message Frequency hopping not enabled in device profile.
[ 300.304036] adrv9002 spi1.0: adrv9002_hop_table_dump_show, 993: failed with "Frequency hopping not enabled in device profile" (3)
iio:device2: axi-adrv9002-rx-lpc (buffer capable)
iio:device3: axi-adrv9002-rx2-lpc (buffer capable)
iio:device4: axi-core-tdd (label: axi-core-tdd-1)
iio:device5: axi-core-tdd (label: axi-core-tdd-2)
iio:device6: axi-adrv9002-tx-lpc (buffer capable)
iio:device7: axi-adrv9002-tx2-lpc (buffer capable)
root@xilinx-uetc:/sys/bus/iio/devices/iio:device1#

Hi,

Well, the versions are ok. Can you share the profiles you're trying to load?

- Nuno Sá

Hii ,
       I have uploaded the profile files on the git-hub , Please find the link below . there is all profile files which we had tried.

https://github.com/sagarvvdn/Query/blob/main/adrv%20test.zip

Hi,

You said you have the device clock set as 40MHz... In profiles 1 and 2 I see it as 38.4MHz which probably won't work. Anyways, I will be able to only test the profiles with 38.4MHz. I'll try to test it on my side tomorrow morning....

- Nuno Sá

Hii ,
      We have tested the  both frequency 38.4 MHz and 40 MHz on the board.
      In the folder both type of profile files are available set-3,5,6  has 40 Mhz and set-1,2,4 has  38.4 MHz files.

Hi,

I just tested your 38.4MHz profiles on ZCU102 with the evaluation board.

https://wiki.analog.com/resources/eval/user-guides/adrv9002/quickstart/zynqmp

The profiles load without errors.

Do you think it's useful to you if I would provide the ZCU102 boot files I used for testing?

-Michael 

Hii michael ,
                     We have already tested these files  with ZCU102 evaluation board , its working in eval board, but our main concern is that we are  facing issue while uploading in our  customised board , We are not able to identify the reason why this error is coming during the profile file upload.  Also i wanna  share with you  we are using single-ended clock  in our customised ADRV RF board . i have  already attached the  schematic in this thread, in which single ended  connection mentioned .i am attaching  the log error again.

xilinx-uetc:/sys/bus/iio/devices/iio:device1# cat /tmp/test1.bin > stream_config
xilinx-uetc:/sys/bus/iio/devices/iio:device1# cat /tmp/test1.json > profile_config
[ 3698.162265] adrv9002 spi1.0: [ERROR]: Error number 1 (0x00000001), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_powermanagement.c, in function adi_adrv9001_powermanagement_Configure_Validate, in line 39, variable name readPattern.Error message ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board.
[ 3698.197278] adrv9002 spi1.0: [ERROR]: Error number 1 (0x00000001), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_powermanagement.c, in function adi_adrv9001_powermanagement_Configure, in line 70, variable name NULL.Error message ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board.
[ 3698.230896] adrv9002 spi1.0: adrv9002_power_mgmt_config, 2597: failed with "ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board" (1)
[ 3699.598724] adrv9002 spi1.0: [ERROR]: Error number 1 (0x00000001), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_powermanagement.c, in function adi_adrv9001_powermanagement_Configure_Validate, in line 39, variable name readPattern.Error message ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board.
[ 3699.633727] adrv9002 spi1.0: [ERROR]: Error number 1 (0x00000001), Recovery action -2.In file drivers/iio/adc/navassa/devices/adrv9001/public/src/adi_adrv9001_powermanagement.c, in function adi_adrv9001_powermanagement_Configure, in line 70, variable name NULL.Error message ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board.
[ 3699.667339] adrv9002 spi1.0: adrv9002_power_mgmt_config, 2597: failed with "ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board" (1)

Also i have checked the  clock and power , both are okay .

Hi,

I think you're right and this is most likely an HW issue.

I moved this thread over to the ADRV9001-ADRV9004 Design Support Community.

Since there are the product experts which can guide you with your HW issues.

-Michael