I have trouble connecting to the board using the evaluation software (TES). Getting GUI pop-up error.
I have trouble connecting to the board using the evaluation software (TES). Getting GUI pop-up error.
First make sure the physical connection with the FPGA board is strong and firm. In addition TES provides a feature to forcibly update the SD card. This button can be found in "File -> Force Update Platform…
Just following up on Connection Issues Questions with some relevant links:
EngineerZone Article Debug Guide:
I have also connection problems. ADRV9002 + ZYNQ702
The directory /home/analog/adrv9001_server/resources/Adi.Adrv9001.Server/
Ping in both directions is ok.
How can I star the server manualy?
You can manually start the server by navigation to that 'Adi.Adrv9001.Server/' folder and then running:
This should manually start the server. While the server is starting it will attempt to connect to the ADRV9002 device. If this connection attempt fails then the server will fail, so make certain the device is connected securely and operational. If the server starts successfully the command prompt indicate that the server is waiting for something to connect to it. At this point go to TES on your host laptop and connect to the platform. If TES connects you should be good to go, it'd be unlikely that you'll need to perform this step again.
If you continue having issues capture a screenshot of the command prompt output and post it here, we'll take a look at it and provide next steps.
If you use that second SD card you'd be using the IIO Scope software to connect to the device. This software is supported by a different team, we'd be happy to direct you to them if you decide to carry on with that software.
For the TES SD Card, I noticed that you're pinging 192.168.1.5. Our server expects the laptop's ethernet connection to be at 192.168.1.2. These requirements are listed in the ADV9001 Evaluation System section of the User Guide. Is there anything stopping you from setting the laptop's IP address? If so we can try to accommodate or adapt to it.
Failing this, what sometimes works is a redownload of the TES software and a reimage of the SD card. If all else fails we'll circle back to this option.
Let me know if any of this helps! If not I'll consult with the team.
IP 192.168.1.2 does not help. I used the IIO SD card only to test the principal hardware function.
I will redownload and reimage the TES SD card.
I have no luck with the TES image.
I put the image (adrv9001-tes-sdcard.zipà 65883SD01.img) on the SD card several times. With this card the ZCU702 Board does not boot: I think the image is for the ZC706.
After copying the three files:
from the other SD card (directory zynqmp-zcu102-rev10-adrv9002) to the root directory of the TES card the system boot. But the server doesn’t start.
It would be very helpful, if you provide an image of the zcu102/adrv9002 TES configuration.
Upon re-reading your issue I noticed that you're using the ZCU702 board, rather than the ZC706. I apologise for not seeing that detail before. The current release does not support the ZCU702, however the next release will. The next software release is not long away, I can't confirm the exact date, but it should be very soon.
Do also take a look at the "Documents" tab of this forum. The next release of software will require an update to the SD card in order to accommodate the changes made. One of our engineers has written a guide on how to update the SD card to the version 12 release (the current release). When the next release is published the new SD card image will be available for download, and a new guide will be published on how to update to the version 13 image.
We also got a trouble.
We used the "adrv9001-tes-sdcard.zip" image on ZC706,
But print Failed to start Load Kernel Modules, and could not find the folder "Adi.Adrv9001.server"
What can we do to solve this situation???
This is a bit of a pernicious issue, it happens pretty rarely but the root cause is very hard to track down. I believe it's caused by some error being saved into a log file. Sadly the only solution I've found to be effective is to wipe TES and the SDK from the host machine (making sure to backup any files you wrote yourself or modified for your application) as well as deleting the .zip file downloaded from analog.com. Use the "Uninstall.exe" found in the TES folder to remove TES properly, before deleting the SDK. Download a new SDK and reinstall TES from scratch. This should give you a completely uncorrupted install.
After that, before connecting TES to the ZC706, use PuTTY to confirm whether or not the Adi.Adrv9001.server folder is there. If it is, try to run the executable Adrv9001Server_B0_29.2.0 file. It may be called something else on your setup. With nothing connected, it should wait for something to try to connect to the server. At this point use TES to connect. If it isn't there, delete the /home/analog/adrv9001_server/resources folder, then try using TES to perform a "Force System Update" in the "File" dropdown menu in the top left corner. This should write a new folder with the server executable in it. Try to connect to TES normally first, then failing that try to connect by running the executable in PuTTY and then connecting through TES.
Failing all of that, your best bet is a clean build of everything. New SDK, new TES and new SD card image. Before trying any of this be certain to have backed up any essential files. I do apologize that this debug guide is convoluted, long and not really certain of itself, however this particular issue is not always an easy one to fix. Sometimes just reinstalling TES will fix everything and there'll be no need for the long and difficult debug process. Other times you'll be deleting and reinstalling things for a long time and then it'll work with no explanation.
The Documents Tab for this forum has a guide for reimaging the SD card, do give it a look also if you run into a lot of issues. Do also let me know if there's more questions I can answer.
Please see the photo below, it's used the "for ADRV9001 TES software R0.1 2020.07" SD Card, from the purchase box.
When run the "Adrv9001Server_B0_29.2.0" file, it's still not connect to the TES.
If Used the Website download "adrv9001-tes-sdcard.zip" image,
"Failed to start load kernel modules " Error message will still appear, try using TES to perform a "Force System Update", the folder and Adrv9001Server_B0_29.2.0 file finally appeared.
But run the "Adrv9001Server_B0_29.2.0" file, show below
I still can not connect to TES.
I've had a chat with the team for more solutions to this issue. The next things to check are the firewall and the server. Make certain there's nothing on your laptop / pc that's interfering with traffic over the ethernet port. If there is you'll need to find a way to disable it and allow ethernet traffic.
Then to check the server, use PuTTY to perform the following commands:
"ps -x | grep server" -> To locate the PID of the Server. It should also confirm if the server is running at all. If it is not running, try to start it again.
"kill -9 <PID of server>" -> If the server is running, use this command to kill it and try running it again.
Do let me know if any of this works.
I think it may not be a problem with ethernet. When I used the ZC706 + AD9375 EVB, the TES connection is OK.
Is there anything that needs to change or set when the ZC706 connect with ADRV9002? (example: Vadj 1.8V?)
Our ADRV9002 EVB red LED is Constantly On..... UG-1828 says it auto adjust VAdj?
ADRV9002 EVB red LED is correct now, when the SW12 switch to close the number(1,2,3,4) position.
But We still can not connect to TES....
ADRV9002 EVB red LED is correct now, when the SW12 switch to close the number(1,2,3,4) position.
But We still can not connect to TES....
Attached file is the putty LOG, please let me know if you have any idea, Thank you!!!
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2020.12.14 17:16:24 =~=~=~=~=~=~=~=~=~=~=~= � U-Boot 2018.01 (Aug 30 2018 - 18:22:43 +0530) Xilinx Zynq ZC706 Model: Zynq ZC706 Development Board Board: Xilinx Zynq Silicon: v3.1 I2C: ready DRAM: ECC disabled 1 GiB MMC: sdhci@e0100000: 0 (SD) SF: Detected s25fl128s_64k with page size 512 Bytes, erase size 128 KiB, total 32 MiB In: serial@e0001000 Out: serial@e0001000 Err: serial@e0001000 Net: ZYNQ GEM: e000b000, phyaddr 7, interface rgmii-id eth0: ethernet@e000b000 Hit any key to stop autoboot: 3 2 1 0 Device: sdhci@e0100000 Manufacturer ID: 2 OEM: 544d Name: SA16G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 14.5 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes reading uEnv.txt 442 bytes read in 9 ms (47.9 KiB/s) Loaded environment from uEnv.txt Importing environment from SD ... Running uenvcmd ... Copying Linux from SD to RAM... reading uImage 3929656 bytes read in 230 ms (16.3 MiB/s) reading devicetree.dtb 19738 bytes read in 15 ms (1.3 MiB/s) ** Unable to read file uramdisk.image.gz ** ## Booting kernel from Legacy Image at 03000000 ... Image Name: Linux-4.14.0-xilinx-00107-g45f98 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3929592 Bytes = 3.7 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02a00000 Booting using the fdt blob at 0x2a00000 Loading Kernel Image ... OK Loading Device Tree to 1fff8000, end 1ffffd19 ... OK Starting kernel ... Booting Linux on physical CPU 0x0 Linux version 4.14.0-xilinx-00107-g45f9852-dirty (email@example.com) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11-rc1)) #4 SMP PREEMPT Tue Oct 2 00:25:12 IST 2018 CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache OF: fdt: Machine model: Zynq ZC706 Development Board Memory policy: Data cache writealloc cma: Reserved 16 MiB at 0x3f000000 random: fast init done percpu: Embedded 16 pages/cpu @ef7c8000 s32844 r8192 d24500 u65536 Built 1 zonelists, mobility grouping on. Total pages: 260608 Kernel command line: console=ttyPS0,115200 root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext4 rootwait uio_pdrv_genirq.of_id="generic-uio" PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1012860K/1048576K available (6144K kernel code, 237K rwdata, 1544K rodata, 1024K init, 152K bss, 19332K reserved, 16384K cma-reserved, 245760K highmem) Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xf0800000 - 0xff800000 ( 240 MB) lowmem : 0xc0000000 - 0xf0000000 ( 768 MB) pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) modules : 0xbf000000 - 0xbfe00000 ( 14 MB) .text : 0xc0008000 - 0xc0700000 (7136 kB) .init : 0xc0900000 - 0xc0a00000 (1024 kB) .data : 0xc0a00000 - 0xc0a3b500 ( 238 kB) .bss : 0xc0a3b500 - 0xc0a6164c ( 153 kB) Preemptible hierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. Tasks RCU enabled. RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 efuse mapped to f0800000 slcr mapped to f0802000 L2C: platform modifies aux control register: 0x72360000 -> 0x72760000 L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000 L2C-310 erratum 769419 enabled L2C-310 enabling early BRESP for Cortex-A9 L2C-310 full line of zeros enabled for Cortex-A9 L2C-310 ID prefetch enabled, offset 1 lines L2C-310 dynamic clock gating enabled, standby mode enabled L2C-310 cache controller enabled, 8 ways, 512 kB L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001 zynq_clock_init: clkc starts at f0802100 Zynq clock init sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns Switching to timer-based delay loop, resolution 3ns clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns timer #0 at f080a000, irq=17 Console: colour dummy device 80x30 Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Setting up static identity map for 0x100000 - 0x100060 Hierarchical SRCU implementation. smp: Bringing up secondary CPUs ... CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 smp: Brought up 1 node, 2 CPUs SMP: Total of 2 processors activated (1333.33 BogoMIPS). CPU: All CPU(s) started in SVC mode. devtmpfs: initialized VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns futex hash table entries: 512 (order: 3, 32768 bytes) pinctrl core: initialized pinctrl subsystem NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations cpuidle: using governor ladder hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. hw-breakpoint: maximum watchpoint size is 4 bytes. zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0880000 zynq-pinctrl 700.pinctrl: zynq pinctrl initialized e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 26, base_baud = 3125000) is a xuartps console [ttyPS0] enabled vgaarb: loaded SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb media: Linux media interface: v0.10 Linux video capture interface: v2.00 pps_core: LinuxPPS API ver. 1 registered pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <firstname.lastname@example.org> PTP clock support registered FPGA manager framework fpga-region fpga-full: FPGA Region probed Advanced Linux Sound Architecture Driver Initialized. clocksource: Switched to clocksource arm_global_timer NET: Registered protocol family 2 TCP established hash table entries: 8192 (order: 3, 32768 bytes) TCP bind hash table entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured (established 8192 bind 8192) UDP hash table entries: 512 (order: 2, 16384 bytes) UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. hw perfevents: no interrupt-affinity property for /pmu@f8891000, guessing. hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available workingset: timestamp_bits=30 max_order=18 bucket_order=0 jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. bounce: pool size: 64 pages io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) io scheduler mq-deadline registered io scheduler kyber registered dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330 dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16 brd: module loaded loop: module loaded libphy: Fixed MDIO Bus: probed CAN device driver interface libphy: MACB_mii_bus: probed macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 28 (00:0a:35:00:01:22) Marvell 88E1116R e000b000.ethernet-ffffffff:07: attached PHY driver [Marvell 88E1116R] (mii_bus:phy_addr=e000b000.ethernet-ffffffff:07, irq=POLL) e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k e1000e: Copyright(c) 1999 - 2015 Intel Corporation. ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-pci: EHCI PCI platform driver usbcore: registered new interface driver usb-storage chipidea-usb2 e0002000.usb: e0002000.usb supply vbus not found, using dummy regulator ULPI transceiver vendor/product ID 0x0424/0x0007 Found SMSC USB3320 ULPI transceiver. ULPI integrity check: passed. ci_hdrc ci_hdrc.0: EHCI Host Controller ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1 ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected i2c /dev entries driver cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 23 si570 1-005d: registered, current frequency 148500000 Hz i2c i2c-0: Added multiplexed i2c bus 1 i2c i2c-0: Added multiplexed i2c bus 2 at24 3-0054: 1024 byte 24c08 EEPROM, writable, 1 bytes/write i2c i2c-0: Added multiplexed i2c bus 3 i2c i2c-0: Added multiplexed i2c bus 4 rtc-pcf8563 5-0051: low voltage detected, date/time is not reliable. rtc-pcf8563 5-0051: rtc core: registered rtc-pcf8563 as rtc0 i2c i2c-0: Added multiplexed i2c bus 5 i2c i2c-0: Added multiplexed i2c bus 6 at24 7-0050: 256 byte 24c02 EEPROM, writable, 1 bytes/write i2c i2c-0: Added multiplexed i2c bus 7 i2c i2c-0: Added multiplexed i2c bus 8 pca954x 0-0074: registered 8 multiplexed busses for I2C switch pca9548 IR NEC protocol handler initialized IR RC5(x/sz) protocol handler initialized IR RC6 protocol handler initialized IR JVC protocol handler initialized IR Sony protocol handler initialized IR SANYO protocol handler initialized IR Sharp protocol handler initialized IR MCE Keyboard/mouse protocol handler initialized IR XMP protocol handler initialized cdns-wdt f8005000.watchdog: Xilinx Watchdog Timer at f0992000 with timeout 10s Xilinx Zynq CpuIdle Driver started sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci-pltfm: SDHCI platform and OF driver helper mmc0: SDHCI controller on e0100000.sdhci [e0100000.sdhci] using ADMA ledtrig-cpu: registered to indicate activity on CPUs usbcore: registered new interface driver usbhid usbhid: USB HID core driver fpga_manager fpga0: Xilinx Zynq FPGA Manager registered NET: Registered protocol family 10 Segment Routing with IPv6 sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver NET: Registered protocol family 17 can: controller area network core (rev 20170425 abi 9) NET: Registered protocol family 29 can: raw protocol (rev 20170425) can: broadcast manager protocol (rev 20170425 t) can: netlink gateway (rev 20170425) max_hops=1 Registering SWP/SWPB emulation handler input: gpio_keys as /devices/soc0/gpio_keys/input/input0 rtc-pcf8563 5-0051: low voltage detected, date/time is not reliable. rtc-pcf8563 5-0051: hctosys: unable to read the hardware clock of_cfs_init of_cfs_init: OK mmc0: new high speed SDHC card at address 1234 mmcblk0: mmc0:1234 SA16G 14.5 GiB ALSA device list: mmcblk0: p1 p2 p3 No soundcards found. �EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) VFS: Mounted root (ext4 filesystem) on device 179:2. devtmpfs: mounted Freeing unused kernel memory: 1024K systemd: Failed to insert module 'autofs4' Welcome to [1mUbuntu 15.04[0m! Cannot add dependency job for unit org.freedesktop.resolve1.busname, ignoring: Unit org.freedesktop.resolve1.busname failed to load: No such file or directory. Cannot add dependency job for unit cups.service, ignoring: Unit cups.service failed to load: No such file or directory. [[32m OK [0m] Created slice Root Slice. [[32m OK [0m] Listening on /dev/initctl Compatibility Named Pipe. [[32m OK [0m] Listening on Journal Socket (/dev/log). [[32m OK [0m] Created slice System Slice. [[32m OK [0m] Created slice User and Session Slice. [[32m OK [0m] Reached target Slices. [[32m OK [0m] Listening on udev Control Socket. [[32m OK [0m] Listening on Delayed Shutdown Socket. [[32m OK [0m] Listening on networkd rtnetlink socket. [[32m OK [0m] Created slice system-serial\x2dgetty.slice. [[32m OK [0m] Listening on udev Kernel Socket. [[32m OK [0m] Listening on Journal Socket. Starting Load Kernel Modules... [[32m OK [0m] Started Boot Process Profiler. Starting Boot Process Profiler... Starting udev Coldplug all Devices... Mounting Temporary Directory... [[32m OK [0m] Started Braille Device Support. Starting Braille Device Support... [[32m OK [0m] Started Read required files in advance. Starting Read required files in advance... Starting Setup Virtual Console... [[32m OK [0m] Reached target Encrypted Volumes. [[32m OK [0m] Reached target Swap. Starting Increase datagram queue length... [[32m OK [0m] Created slice system-getty.slice. Starting Nameserver information manager... Starting Remount Root and Kernel File Systems... [[32m OK [0m] Reached target Remote File Systems (Pre). Starting Create Static Device Nodes in /dev... [[1;31mFAILED[0m] Failed to start Load Kernel Modules. See "systemctl status systemd-modules-load.service" for details. systemd-modules-load.service failed. systemd-bootchart.service failed. Starting Apply Kernel Variables... Mounting Configuration File System... [[32m OK [0m] Started Setup Virtual Console. [[32m OK [0m] Mounted Configuration File System. [[32m OK [0m] Mounted Temporary Directory. [[32m OK [0m] Started Increase datagram queue length. ureadahead.service failed. [[32m OK [0m] Started Remount Root and Kernel File Systems. [[32m OK [0m] Started Create Static Device Nodes in /dev. [[32m OK [0m] Started Apply Kernel Variables. [[32m OK [0m] Started Nameserver information manager. [[32m OK [0m] Started udev Coldplug all Devices. Starting udev Kernel Device Manager... [[32m OK [0m] Reached target Local File Systems (Pre). Starting Load/Save Random Seed... [[32m OK [0m] Listening on Syslog Socket. Starting Journal Service... [[32m OK [0m] Reached target Local File Systems. Starting Wait for all "auto" /etc/n... up for network-online.target... Starting Tell Plymouth To Write Out Runtime Data... Starting Set console keymap... [[32m OK [0m] Reached target Remote File Systems. [[32m OK [0m] Started Load/Save Random Seed. Starting LSB: Raise network interfaces.... [[32m OK [0m] Started Tell Plymouth To Write Out Runtime Data. [[32m OK [0m] Started Journal Service. Starting Flush Journal to Persistent Storage... [[32m OK [0m] Started udev Kernel Device Manager. [[32m OK [0m] Reached target Paths. Starting Copy rules generated while the root was ro... [[32m OK [0m] Started Set console keymap. [[32m OK [0m] Started Flush Journal to Persistent Storage. [[32m OK [0m] Started Copy rules generated while the root was ro. [[32m OK [0m] Found device /dev/ttyPS0. Starting Create Volatile Files and Directories... [[32m OK [0m] Started Create Volatile Files and Directories. Starting Update UTMP about System Boot/Shutdown... Starting Network Time Synchronization... [[32m OK [0m] Started Update UTMP about System Boot/Shutdown. [[32m OK [0m] Started Network Time Synchronization. [[32m OK [0m] Created slice system-ifup.slice. [[32m OK [0m] Started ifup for eth0. Starting ifup for eth0... [[32m OK [0m] Reached target System Time Synchronized. [[32m OK [0m] Started ifup for sit0. Starting ifup for sit0... [[32m OK [0m] Started LSB: Raise network interfaces.. [[32m OK [0m] Started Wait for all "auto" /etc/ne...be up for network-online.target. [[32m OK [0m] Reached target System Initialization. [[32m OK [0m] Listening on OpenBSD Secure Shell server socket. [[32m OK [0m] Listening on Avahi mDNS/DNS-SD Stack Activation Socket. [[32m OK [0m] Reached target Timers. [[32m OK [0m] Listening on D-Bus System Message Bus Socket. [[32m OK [0m] Reached target Sockets. [[32m OK [0m] Reached target Basic System. Starting LSB: Speech Dispatcher... Starting Permit User Sessions... [[32m OK [0m] Reached target Containers. Starting LSB: Platform initscript... [[32m OK [0m] Started Run anacron jobs. Running Platform Init Starting Run anacron jobs... Starting Enable support for additional executable binary formats... Starting Accounts Service... Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"... Starting LSB: Xen daemons... Starting Restore /etc/resolv.conf i...e the ppp link was shut down.... Starting Initialize hardware monitoring sensors... [[32m OK [0m] Started Regular background program processing daemon. Starting Regular background program processing daemon... Starting Network Manager... Starting Provide limited super user privileges to specific users... Starting LSB: Load kernel modules needed to enable cpufreq scaling... Starting LSB: automatic crash report generation... Starting WPA supplicant... Starting Avahi mDNS/DNS-SD Stack... Starting System Logging Service... [[32m OK [0m] Started Cgroup management daemon. Starting Cgroup management daemon... Starting D-Bus System Message Bus... Starting Login Service... [[32m OK [0m] Started LSB: Speech Dispatcher. [[32m OK [0m] Started Permit User Sessions. [[32m OK [0m] Started Enable support for additional executable binary formats. [[32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". [[32m OK [0m] Started LSB: Xen daemons. [[32m OK [0m] Started Restore /etc/resolv.conf if...ore the ppp link was shut down.. [[32m OK [0m] Started Provide limited super user privileges to specific users. [[32m OK [0m] Started LSB: Load kernel modules needed to enable cpufreq scaling. [[32m OK [0m] Started LSB: automatic crash report generation. [[32m OK [0m] Started D-Bus System Message Bus. Switching VADJ from 2.5V to 1.8V [[32m OK [0m] Started WPA supplicant. [[32m OK [0m] Started Avahi mDNS/DNS-SD Stack. [[32m OK [0m] Started Initialize hardware monitoring sensors. [[32m OK [0m] Started System Logging Service. fpga_manager fpga0: Error requesting firmware system_top.bit.bin failed to load fpga image OF: overlay: of_overlay_create: Pre-apply notifier failed (err=-22) create_overlay: Failed to create overlay (err=-22) [[32m OK [0m] Started Login Service. Starting Authenticate and Authorize Users to Run Privileged Tasks... [[32m OK [0m] Started Make remote CUPS printers available locally. Starting Make remote CUPS printers available locally... Starting Network Service... Starting LSB: set CPUFreq kernel parameters... Starting LSB: Start/stop secondary xen domains... Starting Light Display Manager... [[32m OK [0m] Started LSB: set CPUFreq kernel parameters. [[32m OK [0m] Started LSB: Start/stop secondary xen domains. [[32m OK [0m] Started Network Service. Unhandled fault: imprecise external abort (0x406) at 0xb6cab000 pgd = ee48c000 [b6cab000] *pgd=3ed6b831 Internal error: Oops - BUG: 406 [#1] PREEMPT SMP ARM Modules linked in: CPU: 1 PID: 1750 Comm: cat Not tainted 4.14.0-xilinx-00107-g45f9852-dirty #4 Hardware name: Xilinx Zynq Platform task: ef172d80 task.stack: ee4b0000 PC is at xspi_read32+0x8/0xc LR is at xilinx_spi_probe+0x2c8/0x538 pc : [<c03ff5a0>] lr : [<c03ffdbc>] psr: 600c0013 sp : ee4b1ce0 ip : 00000000 fp : 00000000 r10: c08118fd r9 : f0b63000 r8 : eebc4e00 r7 : ee6fd800 r6 : eebc4e10 r5 : 00000000 r4 : ee6fdb38 r3 : c03ff598 r2 : 00000000 r1 : 600c0013 r0 : 00000000 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none Control: 18c5387d Table: 2e48c04a DAC: 00000051 Process cat (pid: 1750, stack limit = 0xee4b0210) Stack: (0xee4b1ce0 to 0xee4b2000) 1ce0: 00000000 eeb1f580 eeb1fdc0 c081bd2a 00000003 00000008 00000000 00000100 1d00: c03ffaf4 eebc4e10 c0a1c574 00000000 c0a1c574 00000000 00000003 c03abbc0 1d20: eebc4e10 c0a55858 c0a5585c c03aa708 00000000 ee4b1d68 c03aa8ac eebc4e44 1d40: c0a55834 00000000 00000000 c03a9000 ef076f6c ee8c1538 eebc4e10 c0a18e68 1d60: 00000001 c03aa490 eebc4e10 00000001 00000031 eebc4e10 c0a18e68 eebc4e10 1d80: ef17a810 c03a9ae0 eebc4e10 eebc4e18 00000000 c03a82fc eebc4e10 400c0013 1da0: 00000000 ffffffff eebc4e00 ef7f6048 00000000 00000000 ef17a810 00000008 1dc0: ee50d108 c04f0948 ee4b1e4c ef17a800 00000005 ee4b1e4c c0a1bfb0 c04f1018 1de0: c0a32e18 00000005 ffffffff 00000000 00000005 c013425c 00000005 c0a32f44 1e00: ee4b1e4c ffffffff ee50d100 c0134620 00000000 00000005 ee4b1e4c eeabdd80 1e20: eeabdd80 ef158294 eead3800 c013464c 00000000 00000005 ee4b1e4c c04f2a90 1e40: eeabdd80 c04f2ad4 00000005 ef7f5ff8 ee50d980 ef7f62ac eeabdd80 c04f2b64 1e60: 800c0013 c022a5b0 00000000 ee50d998 00000001 c04f2ea0 eeabdd80 ef7f62ac 1e80: eeabdd80 00000000 ef158294 c04f3214 eead3a84 eead3800 c082f4c3 eead3800 1ea0: ee50d100 c04ee978 ef158280 00000000 00000001 c04f78ec 00000000 014000c0 1ec0: 00000000 c080f812 eead3800 00000000 ef158284 ef158294 ef7f72bc 00000000 1ee0: 00000014 eead38c8 dfffc57c 00000036 eeef1d70 ee5a7000 00000000 ee5a6000 1f00: 00000000 eeef1d70 eeaa3210 eeef1d70 eead7f08 c04f2150 00000109 ee5a7000 1f20: ee5a6000 c04f21dc ee6381c0 00000001 00000000 eead7f00 eeef1d70 c022ba18 1f40: eead7f00 eeef1d70 00000000 00000008 eedef220 c01d2cac 00000000 00000000 1f60: 00000000 00000000 ef1731f8 ef172d80 eead7f00 c0a3c4d0 ee4b0000 00000000 1f80: 00020000 c0131e94 c01070a4 ffffe000 ee4b1fb0 00000006 c01070a4 c010a344 1fa0: b6f4bd60 b6f85390 00000000 c0106f40 00000000 80100000 fbad2004 b6eae79d 1fc0: b6f4bd60 b6f85390 00000000 00000006 b6f4c0b4 00000000 00000000 00020000 1fe0: b6ea76a9 bef71b64 b6eaf4f5 b6eeb036 400c0030 00000001 00000000 00000000 [<c03ff5a0>] (xspi_read32) from [<c03ffdbc>] (xilinx_spi_probe+0x2c8/0x538) [<c03ffdbc>] (xilinx_spi_probe) from [<c03abbc0>] (platform_drv_probe+0x50/0x9c) [<c03abbc0>] (platform_drv_probe) from [<c03aa708>] (driver_probe_device+0x1ec/0x2b0) [<c03aa708>] (driver_probe_device) from [<c03a9000>] (bus_for_each_drv+0x84/0x8c) [<c03a9000>] (bus_for_each_drv) from [<c03aa490>] (__device_attach+0x98/0x100) [<c03aa490>] (__device_attach) from [<c03a9ae0>] (bus_probe_device+0x28/0x80) [<c03a9ae0>] (bus_probe_device) from [<c03a82fc>] (device_add+0x400/0x500) [<c03a82fc>] (device_add) from [<c04f0948>] (of_platform_device_create_pdata+0x7c/0xa0) [<c04f0948>] (of_platform_device_create_pdata) from [<c04f1018>] (of_platform_notify+0x6c/0xe0) [<c04f1018>] (of_platform_notify) from [<c013425c>] (notifier_call_chain+0x40/0x64) [<c013425c>] (notifier_call_chain) from [<c0134620>] (__blocking_notifier_call_chain+0x40/0x58) [<c0134620>] (__blocking_notifier_call_chain) from [<c013464c>] (blocking_notifier_call_chain+0x14/0x1c) [<c013464c>] (blocking_notifier_call_chain) from [<c04f2a90>] (of_reconfig_notify+0x14/0x2c) [<c04f2a90>] (of_reconfig_notify) from [<c04f2ad4>] (of_property_notify+0x2c/0x34) [<c04f2ad4>] (of_property_notify) from [<c04f2b64>] (__of_changeset_entry_notify+0x88/0xa8) [<c04f2b64>] (__of_changeset_entry_notify) from [<c04f3214>] (__of_changeset_apply+0x9c/0xac) [<c04f3214>] (__of_changeset_apply) from [<c04f78ec>] (of_overlay_create+0x3e0/0x4dc) [<c04f78ec>] (of_overlay_create) from [<c04f2150>] (create_overlay+0x78/0xac) [<c04f2150>] (create_overlay) from [<c04f21dc>] (cfs_overlay_item_dtbo_write+0x58/0x88) [<c04f21dc>] (cfs_overlay_item_dtbo_write) from [<c022ba18>] (configfs_release_bin_file+0x50/0x84) [<c022ba18>] (configfs_release_bin_file) from [<c01d2cac>] (__fput+0xd8/0x1ac) [<c01d2cac>] (__fput) from [<c0131e94>] (task_work_run+0x9c/0xac) [<c0131e94>] (task_work_run) from [<c010a344>] (do_work_pending+0xa8/0xb0) [<c010a344>] (do_work_pending) from [<c0106f40>] (slow_work_pending+0xc/0x20) Code: e28cc004 eafffff1 e5900000 f57ff04f (e12fff1e) ---[ end trace 51947515224cf2e7 ]--- Unhandled fault: external abort on non-linefetch (0x018) at 0xb6f4f080 pgd = ee48c000 [b6f4f080] *pgd=3ece3831 [[32m OK [0m] Started Authenticate and Authorize Users to Run Privileged Tasks. [[32m OK [0m] Started Accounts Service. [[32m OK [0m] Started Network Manager. [[32m OK [0m] Started Light Display Manager. Starting Network Manager Wait Online... [[32m OK [0m] Reached target Network. Starting /etc/rc.local Compatibility... Starting Network Name Resolution... [[32m OK [0m] Started Network Name Resolution. [[32m OK [0m] Started Network Manager Wait Online. [[32m OK [0m] Started /etc/rc.local Compatibility. Starting Wait for Plymouth Boot Screen to Quit... [[32m OK [0m] Reached target Network is Online. Starting LSB: start Samba NetBIOS nameserver (nmbd)... Starting LSB: start Samba daemons for the AD DC... Starting LSB: Tool to automatically...ubmit kernel crash signatures... Starting LSB: simple distributed compiler server... [[32m OK [0m] Started Wait for Plymouth Boot Screen to Quit. [[32m OK [0m] Started Getty on tty1. Starting Getty on tty1... [[32m OK [0m] Started Serial Getty on ttyPS0. Starting Serial Getty on ttyPS0... [[32m OK [0m] Reached target Login Prompts. [[32m OK [0m] Started LSB: simple distributed compiler server. [[32m OK [0m] Started LSB: Tool to automatically ... submit kernel crash signatures. Ubuntu 15.04 analog ttyPS0 analog login: root (automatic login) Last login: Mon Dec 14 02:08:01 UTC 2020 on ttyPS0 root@analog:~#
By the way, the ADP5056 normally have 1V0, 1V3 and 1V8 output?
Can you confirm for me that
a) The FPGA is configured exactly as stated in the User Guide
b) The Red LED remains off when the FPGA is fully configured (If it does not turn off then there's either an FPGA issue or a Linux kernel issue on the SD card)
c) All Green LED's on the board light up. There's one close to the Red LED at the bottom of the board, a dim one in the middle of the board to indicate all power domains are okay, and 2 at the top of the board signifying that the VCTCXO is powered on and is selected using the adjacent switch.
If we can confirm all of these and still the issue hasn't been fixed we'll know it's either a connection issue or a SW issue.
The DS901 does not light, please see the video.
That light is very dim, so do make certain it's definitely not turning on. If it's not turning on that means that the power domains for the ADRV9002 are not being set to the right level, which would explain your difficulties in connecting to it. We've experienced similar issues when setups were damaged by human error.
The next thing we'll check is the inputs and outputs to the ADP5056 power supply chip. First check the three enable lines on R810, R807, R804 and then the power good output from the ADP5056 on R813. If the enable lines are all high and the output is low then there may be damage to this ADP5056 or to one of the surrounding components. These parts can be replaced if we confirm that there is indeed damage to them. One engineer noticed that a capacitor around the ADP5056 was causing a short to ground, go around the device and confirm that there's no damage to any component.
If the 3 enable lines are not high that would indicate that power being delivered to the board, which would suggest an issue with the ZC706. That'd be surprising, but it could have happened.
Let me know how this check goes.
This is really disappointing!!!
Three enable lines on R810, R807, R804 are all high(3.3V), and the Power good output on R813 is 4.8V.
Channel3 (L803, D901) output voltage is 0.79V, Channel2 output voltage is 0.09V, Channel1 is 0V....
And we could not found any capacitor short to ground that around the ADP5056.
Are there any software control or feedback could cause this situation?
Hi again Luke,
If your channel voltages are that far off then there's an issue with you ADP5056. Either the enable pin is being pulled to ground by the FPGA (part of the FMC connection standard is that any daughter card connected to an FMC connection must give control of the enable pin of the daughter card's power management circuitry to the FPGA. We adhere to this standard) or the chip itself has been damaged during your use of the product.
The Enable pin for the ADP5056 is routed to pin D1 on the FMC connecter. See if you can probe the enable pin at the ADP5056 side or at the FPGA side. If it's pulled to GND then the issue is with the FPGA.
If the enable pin is pulled high, then the last remaining solution is to replace the ADP5056. To the best of my knowledge this is not a trivial task, however we have successfully repaired damaged boards by replacing this chip.
As far as software causes for the issues you're experiencing, we've exhausted all of the possible explanations that we've encountered. We've attempted to manually start the TES server on the FPGA. We've redownloaded TES and reimaged the SD card with a TES image successfully. I assume you've confirmed that your Ethernet connection adheres to the requirements we outlined in the user guide, and you've double checked that the FPGA is configured as shown in the user guide.
A possible reason for the damage to the ADP5056 is your earlier work with with ZCU702 board. As this board is not yet supported by our software (it will be in future releases) the interface voltages will have likely been a fair deal higher than the 1.8V the ADRV9002 expects. We do have clamping circuitry in place to keep our card safe, but it was theorized that providing excessively high voltages to the interface pins may cause damage to the board. No-one in Analog Devices has encountered this, but it was believed to be a possibility.
Attempt to confirm the behavior of the Enable pin, failing that my only remaining piece of advice is to replace the ADP5056. Bear in mind that this is a difficult component to replace, we have had to make multiple attempts at some replacements in order to be successful. Let me know how far this takes you.
Really appreciate your effort.
We do not work with ZCU702.
Whatever we work with ZCU102 or ZC706, this trouble still needs to be solved, next step we will contact the agent to help....
Apologies, I meant the ZCU102.
Do contact them, and any further questions or queries you have I'll be happy to answer here or elsewhere on the forum.