Post Go back to editing

ADRV9002 on ZC706 cannot connect to TES

Category: Hardware
Product Number: ADRV9002

The ADRV9002NP/W1/PCBZ daughter card is plugged into the ZC706 carrier board, But cannot be connected to TES.

The SD boot image file is: ADRV9001 SD Card image for ZC706 FPGA (zip) ( Wideband RF Transceiver Evaluation Software | Analog Devices ) 

boot.txt is the boot log of ZC706;
ip.txt is the network debugging log of ZC706;

My PC network configuration is:
IP assignment:manual
IPv4 address:192.168.1.2
IPv4 mask:255.255.255.0


Question:

When checking ip.txt, eth0 is not listed on the network and cannot be pinged. TES cannot connect to ADRV9002. What is the reason?
Looking forward to your reply, thank you.

ip link show
ifconfig -a
ip addr
ping 192.168.1.10
ping 192.168.1.2
cat /etc/network/interfaces



root@linaro-developer:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
root@linaro-developer:~# ifconfig -a
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:1488 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1488 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:121552 (121.5 KB)  TX bytes:121552 (121.5 KB)

sit0      Link encap:IPv6-in-IPv4  
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@linaro-developer:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
3: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
root@linaro-developer:~# ping 192.168.1.10
connect: Network is unreachable
root@linaro-developer:~# ping 192.168.1.2
connect: Network is unreachable
root@linaro-developer:~# cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

allow-hotplug eth0
iface eth0 inet dhcp

root@linaro-developer:~# ping linaro-developer
PING linaro-developer (127.0.1.1) 56(84) bytes of data.
64 bytes from linaro-developer (127.0.1.1): icmp_seq=1 ttl=64 time=0.096 ms
64 bytes from linaro-developer (127.0.1.1): icmp_seq=2 ttl=64 time=0.061 ms
64 bytes from linaro-developer (127.0.1.1): icmp_seq=3 ttl=64 time=0.058 ms
64 bytes from linaro-developer (127.0.1.1): icmp_seq=4 ttl=64 time=0.052 ms
64 bytes from linaro-developer (127.0.1.1): icmp_seq=5 ttl=64 time=0.052 ms
64 bytes from linaro-developer (127.0.1.1): icmp_seq=6 ttl=64 time=0.088 ms
^C
--- linaro-developer ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5152ms
rtt min/avg/max/mdev = 0.052/0.067/0.096/0.020 ms
root@linaro-developer:~# 
  
L: PM Bus VADJ Read Voltage: [1868064 uV]


U-Boot 2018.01 (Jan 24 2021 - 13:45:35 -0500) 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
*** Warning - bad CRC, using default environment

In:    serial@e0001000
Out:   serial@e0001000
Err:   serial@e0001000
Net:   ZYNQ GEM: e000b000, phyaddr 7, interface rgmii-id
eth0: ethernet@e000b000
reading uEnv.txt
442 bytes read in 9 ms (47.9 KiB/s)
Importing environment from SD ...
Hit any key to stop autoboot:  0 
Device: sdhci@e0100000
Manufacturer ID: 3
OEM: 5344
Name: SD64G 
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 59.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
4388168 bytes read in 249 ms (16.8 MiB/s)
reading devicetree.dtb
14239 bytes read in 13 ms (1 MiB/s)
** Unable to read file uramdisk.image.gz **
## Booting kernel from Legacy Image at 03000000 ...
   Image Name:   Linux-4.14.0-xilinx
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4388104 Bytes = 4.2 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 1fff9000, end 1ffff79e ... OK

Starting kernel ...

Booting Linux on physical CPU 0x0
Linux version 4.14.0-xilinx (rkutty@rkutty-lx01.adsdesign.analog.com) (gcc version 8.2.0 (GCC)) #1 SMP PREEMPT Sun Jan 24 14:19:48 EST 2021
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 17 pages/cpu @ef7c8000 s37324 r8192 d24116 u69632
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: 1012632K/1048576K available (6144K kernel code, 435K rwdata, 1736K rodata, 1024K init, 160K bss, 19560K 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 - 0xc0a6ce38   ( 436 kB)
       .bss : 0xc0a72d48 - 0xc0a9b094   ( 161 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 <giometti@linux.it>
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
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
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
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
ucd9000 8-0065: Device ID UCD90120A|2.3.4.0000|110603
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
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
mmc0: new high speed SDXC card at address aaaa
of_cfs_init: OK
ALSA device list:
  No soundcards found.
Waiting for root device /dev/mmcblk0p2...
mmcblk0: mmc0:aaaa SD64G 59.5 GiB 
 mmcblk0: p1 p2
EXT4-fs (mmcblk0p2): recovery complete
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[1]: Failed to insert module 'autofs4'

Welcome to Ubuntu 15.04!

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 display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Reached target Swap.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Paths.
[  OK  ] Created slice Root Slice.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Created slice System Slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Listening on networkd rtnetlink socket.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on Journal Socket.
         Starting udev Coldplug all Devices...
         Mounting Debug File System...
         Starting Load Kernel Modules...
         Starting Remount Root and Kernel File Systems...
         Starting Nameserver information manager...
         Mounting Temporary Directory...
[  OK  ] Started Boot Process Profiler.
         Starting Boot Process Profiler...
[  OK  ] Started Read required files in advance.
         Starting Read required files in advance...
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Created slice User and Session Slice.
         Starting Increase datagram queue length...
[  OK  ] Reached target Slices.
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Remount Root and Kernel File Systems.
systemd-bootchart.service failed.
[  OK  ] Mounted Debug File System.
[  OK  ] Mounted Temporary Directory.
ureadahead.service failed.
[  OK  ] Started Increase datagram queue length.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started Nameserver information manager.
[  OK  ] Started udev Coldplug all Devices.
         Starting udev Kernel Device Manager...
[  OK  ] Listening on Syslog Socket.
         Starting Journal Service...
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Reached target Local File Systems.
         Starting Wait for all "auto" /etc/n... up for network-online.target...
[  OK  ] Reached target Remote File Systems.
         Starting Load/Save Random Seed...
         Starting Apply Kernel Variables...
         Mounting Configuration File System...
[  OK  ] Started Load/Save Random Seed.
         Starting LSB: Raise network interfaces....
[  OK  ] Started Wait for all "auto" /etc/ne...be up for network-online.target.
[  OK  ] Mounted Configuration File System.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Journal Service.
         Starting Flush Journal to Persistent Storage...
         Starting Copy rules generated while the root was ro...
[  OK  ] Started Copy rules generated while the root was ro.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Found device /dev/ttyPS0.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Create Volatile Files and Directories.
         Starting Network Time Synchronization...
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Created slice system-ifup.slice.
[  OK  ] Started ifup for sit0.
         Starting ifup for sit0...
[  OK  ] Started LSB: Raise network interfaces..
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on OpenBSD Secure Shell server socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Login Service...
         Starting Permit User Sessions...
         Starting Initialize hardware monitoring sensors...
[  OK  ] Started Regular background program processing daemon.
         Starting Regular background program processing daemon...
         Starting Provide limited super user privileges to specific users...
         Starting LSB: Platform initscript...
         Starting LSB: Load kernel modules needed to enable cpufreq scaling...
         Starting System Logging Service...
         Starting Network Manager...
         Starting LSB: Xen daemons...
         Starting WPA supplicant...
[  OK  ] Reached target Containers.
         Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"...
         Starting D-Bus System Message Bus...
[  OK  ] Reached target Timers.
[  OK  ] Started System Logging Service.
[  OK  ] Started Permit User Sessions.
Running Platform Init
[  OK  ] Started Provide limited super user privileges to specific users.
[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
[  OK  ] Started LSB: Xen daemons.
[  OK  ] Started LSB: Set the CPU Frequency Scaling governor to "ondemand".
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started WPA supplicant.
[  OK  ] Started Initialize hardware monitoring sensors.
[  OK  ] Started Login Service.
         Starting Authenticate and Authorize Users to Run Privileged Tasks...
         Starting Network Service...
         Starting LSB: Start/stop secondary xen domains...
         Starting LSB: set CPUFreq kernel parameters...
[  OK  ] Started Network Service.
[  OK  ] Started LSB: set CPUFreq kernel parameters.
[  OK  ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[  OK  ] Started LSB: Start/stop secondary xen domains.
         Starting Network Name Resolution...
[  OK  ] Started Network Manager.
[  OK  ] Reached target Network.
         Starting /etc/rc.local Compatibility...
         Starting Network Manager Wait Online...
[  OK  ] Started Network Name Resolution.
[  OK  ] Started Network Manager Wait Online.
[  OK  ] Reached target Network is Online.
         Starting LSB: start Samba daemons for the AD DC...
         Starting LSB: start Samba NetBIOS nameserver (nmbd)...
[  OK  ] Stopped OpenBSD Secure Shell server.
[  OK  ] Started OpenBSD Secure Shell server.
         Starting OpenBSD Secure Shell server...
[  OK  ] Stopped LSB: start Samba SMB/CIFS daemon (smbd).
         Starting LSB: start Samba SMB/CIFS daemon (smbd)...
[  OK  ] Closed OpenBSD Secure Shell server socket.
[  OK  ] Stopped OpenBSD Secure Shell server.
[  OK  ] Started OpenBSD Secure Shell server.
         Starting OpenBSD Secure Shell server...
[  OK  ] Started LSB: start Samba daemons for the AD DC.
[  OK  ] Started LSB: start Samba SMB/CIFS daemon (smbd).
[  OK  ] Started LSB: start Samba NetBIOS nameserver (nmbd).
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started Serial Getty on ttyPS0.
         Starting Serial Getty on ttyPS0...
[  OK  ] Started Getty on tty1.
         Starting Getty on tty1...
[  OK  ] Reached target Login Prompts.
[  OK  ] Started LSB: Platform initscript.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Chang
Ubuntu 15.04 linaro-developer ttyPS0

linaro-developer login: root (automatic login)

Last login: Mon Feb 16 20:55:15 UTC 2015 on ttyPS0
root@linaro-developer:~# 
   



Modify error text
[编辑人: TimmyZhang 编辑时间: 18 Dec 2023 3:24 PM (GMT -5)]
  • Hi TimmyZhang,

    Can you verify that your ZC706 is not showing any red LEDs? From your boot log, it appears that there shouldn't be any, but I want to make sure.

    Is your ZC706 plugged directly into the computer that's running TES, or is it plugged in somewhere else on the network?

    If you are connected directly, verify that your adapter settings are configured as you have shown, but only for the ethernet adapter that's connected directly to the FPGA.

    If you connected your FPGA to a network, you'll need to find the IP address of your FPGA, and use that when connecting to the TES.

    Kind Regards,
    Michał

  • Thank you for your reply.
    Yes, ZC706 does not display red LED.

    My ZC706 is directly connected to the computer running TES and configured according to the content of the log.
    I also tried connecting through the switch and modified the corresponding configuration, but eth0 could not be discovered and TES could not be connected.

    Let's check the logs:
    When I try to run
    "ip link show"
    "ifconfig -a"
    "ip addr"

    There is no eth0 in the log. What is the reason?
    Is the TES I'm using incorrect?
    Is my ZC706 having a hardware failure?
    (I have run the Xilinx network port test program, and the PC and ZC706 can loop back normally)

  • Hi TimmyZhang,

    The way that it *should* work, is that when the FPGA boots, it searches for the PC at the specified address, and then configures its own IP based on that. Once that's done, you can log into it remotely via SSH (through the ethernet connection). The TES relies on this - it logs into the FPGA over SSH and starts up the ADRV9001 server, which facilitates communication between the TES and the FPGA, and then between the FPGA and the ADRV9001. If you cannot connect to the FPGA via SSH, the TES will not be able to do it either. So first, let's make sure that you can connect to the FPGA over SSH, before we worry about the TES.

    I don't know what could be causing eth0 to be missing. My first suggestion is that you try download a fresh image from the website and try to image the SD card again.

    From the above image, it also looks like your FPGA fan is not spinning - this was an issue with some of the earlier SD card images that has since been resolved, so it may just be the case that your SD card image is old or corrupted.

    Kind Regards,
    Michał

  • Dear Michał
    Thank you very much for your reply!

    The reason why there is no eth0 is that the ZC706 hardware is faulty. There should be a problem with the connection between the Ethernet chip and the peripherals. After I replaced a ZC706, the ADRV9002 can connect to the PC.

    1. ADRV9001 TES img (www.analog.com/.../navassa_zc706.zip), the FPGA fan does not work. Where can I download the img that supports the FPGA fan to work?

    2. I tried to use Kuiper Linux. After configuring ADRV9002, the Vadj of ZC706=2.5V. ADRV9002 cannot work at Vadj1.8V. How to use Kuiper Linux to adjust Vadj=1.8V?

    3. There is another question. The ADRV9001 TES img does not have an IIO module. How to get the img file: it supports IIO and FPGA fan operation, and can also adjust the Vadj=1.8V of the ZC706?

    Again looking forward to your reply.

    BR

    Timmy

  • Hi Timmy,

    I'm glad that you resolved your ethernet issue.

    1. I was told that this has since been resolved - have you downloaded this image recently? If it still doesn't work using the latest image, the ADRV9001 EVB has the same 3-pin fan header beside its FMC connector. You can plug the fan cable into this pin header instead.

    2 & 3. Here, you are conflating two separate software flows. The TES and its associated SDK is part of the software package that's supported by the product line team on the ADRV9001-ADRV9007 forums. The IIO software is a completely separate package, and this is supported on the Linux Software Drivers forum. I suggest you read through the ADRV9001 Software and Hardware Selection Guide to get a better understanding of this.

    Kind Regards,
    Michał

  • Dear Michael,

    1. Yes, I have downloaded the latest ADRV9001 TES img, the fan still does not work, but it is not important, as you said, the fan can be connected to the fan socket on the side of the FMC.

    2.TES uses a software method to set the Vadj voltage of ZC706. No other settings are required. It is very simple, but there is no release documentation.
    I used a TI USB Interface Adapte to set up the TI power chip on the ZC706 board to modify Vadj.

    Anyway, the circuit has started working normally, thank you very much for your reply, thank you!

    BR

    Timmy

  • Hi Timmy,

    I'm glad that you got your setup working.

    However, I have to say that we do not recommend modifications like this - Vadj being at the incorrect voltage is an indication of an issue with the FPGA image, and issues like this should be resolved in the software - we do not recommend (nor do we support) any modifications like the ones described in your answer.

    Kind Regards,
    Michał