UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Participant silentlab54
Participant
925 Views
Registered: ‎08-29-2018

No eth0 ethernet connection on Petalinux 2018.2 and 2018.3

Jump to solution

Hi all, 

I need your help to solve a problem on ZC702 EVK GEM0 ethernet; I configured the project to activate the Zynq Ethernet #0 PS adapter in the PS part of the Zynq. I've controlled every pin in the design (ETH, MDIO, RESETn): the configuration matches the EVK pin documentation supplied with the ZC702 board.

Actually I'm developing with Petalinux 2018.3. I've build the bitstream, FSBL, u-boot, kenrnel, rootfs, all coming from Xilinx and with standard setup for &gem.

I've set a custom static IP configuration between my PC and the ZC702 EVK.

Thesetup is:

  • PC ip address 192.168.137.1, netmask 255.255.255.0
  • ZC702 board ip address 192.168.137.10, netmask 255.255.255.0, gateway 192.168.137.1

With this configuration, this is a successfully ping attempt from the ZX702 u-boot:

 

U-Boot 2018.01 (Jan 23 2019 - 15:59:13 +0000) Xilinx Zynq ZC702

Model: Zynq ZC702 Development Board
Board: Xilinx Zynq
Silicon: v3.1
I2C:   ready
DRAM:  ECC disabled 1 GiB
MMC:   mmc@e0100000: 0 (SD)
** No device specified **
Using default environment

In:    serial@e0001000
Out:   serial@e0001000
Err:   serial@e0001000
Model: Zynq ZC702 Development Board
Board: Xilinx Zynq
Silicon: v3.1
Net:   ZYNQ GEM: e000b000, phyaddr 7, interface rgmii-id
eth0: ethernet@e000b000
U-BOOT for test

Hit any key to stop autoboot:  0
Zynq> ping 192.168.137.1
Using ethernet@e000b000 device
host 192.168.137.1 is alive
Zynq>

But the ping from the PC to the board gives this output (failure):

 

C:\Users\user>ping 192.168.137.10

Esecuzione di Ping 192.168.137.10 con 32 byte di dati:
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.

Statistiche Ping per 192.168.137.10:
    Pacchetti: Trasmessi = 4, Ricevuti = 0,
    Persi = 4 (100% persi)

 

Booting Linux, this is the kernel output:

 

Hit any key to stop autoboot:  0
Device: mmc@e0100000
Manufacturer ID: 3
OEM: 5344
Name: SL08G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 7.4 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
reading image.ub
3964572 bytes read in 232 ms (16.3 MiB/s)
## Loading kernel from FIT Image at 10000000 ...
   Using 'conf@system-top.dtb' configuration
   Verifying Hash Integrity ... OK
   Trying 'kernel@1' kernel subimage
     Description:  Linux kernel
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0x10000104
     Data Size:    3940769 Bytes = 3.8 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x00008000
     Entry Point:  0x00008000
     Hash algo:    sha1
     Hash value:   2c51132329b08a3e05be928f25226065ad2eca31
   Verifying Hash Integrity ... sha1+ 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
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x103c23a8
     Data Size:    21890 Bytes = 21.4 KiB
     Architecture: ARM
     Hash algo:    sha1
     Hash value:   0c5222d13a64e3acc9339d5fac44eab9c5d349f9
   Verifying Hash Integrity ... sha1+ OK
   Booting using the fdt blob at 0x103c23a8
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 07ff7000, end 07fff581 ... OK

Starting kernel ...

Booting Linux on physical CPU 0x0
Linux version 4.14.0-xilinx-v2018.3 (oe-user@oe-host) (gcc version 7.3.0 (GCC)) #1 SMP PREEMPT Wed Jan 23 09:35:28 UTC 2019
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
OF: fdt: Machine model: Zynq ZC702 Development Board
bootconsole [earlycon0] enabled
Memory policy: Data cache writealloc
cma: Reserved 16 MiB at 0x3f000000
random: fast init done
percpu: Embedded 16 pages/cpu @ef7c7000 s34764 r8192 d22580 u65536
Built 1 zonelists, mobility grouping on.  Total pages: 260608
Kernel command line: console=ttyPS0,115200 earlyprintk root=/dev/mmcblk0p2 rw rootwait
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: 1012856K/1048576K available (6144K kernel code, 238K rwdata, 1564K rodata, 1024K init, 152K bss, 19336K 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 - 0xc0a3b8c0   ( 239 kB)
       .bss : 0xc0a3b8c0 - 0xc0a61c04   ( 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 f0802000
slcr mapped to f0804000
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 f0804100
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 f080c000, 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 menu
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 = 27, base_baud = 3125000) is a xuartps
`▒▒k▒▒▒▒[ttyPS0] enabled
console [ttyPS0] enabled
bootconsole [earlycon0] disabled
bootconsole [earlycon0] disabled
XGpio: /amba_pl/gpio@41200000: registered, base is 1020
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
EDAC MC: Ver: 3.0.0
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
xilinx-vdma 43000000.dma: Xilinx AXI VDMA Engine Driver Probed!!
brd: module loaded
loop: module loaded
m25p80 spi0.0: found n25q128a11, expected n25q512a
m25p80 spi0.0: n25q128a11 (16384 Kbytes)
4 ofpart partitions found on MTD device spi0.0
Creating 4 MTD partitions on "spi0.0":
0x000000000000-0x000000500000 : "boot"
0x000000500000-0x000000520000 : "bootenv"
0x000000520000-0x000000fa0000 : "kernel"
0x000000fa0000-0x000001000000 : "spare"
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 31 (3c:39:e7:e0:2c:e7)
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 24
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 rtc0: invalid alarm value: 2019-1-30 35:73:0
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
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
ucd9200 8-0034: Device ID UCD9248-80|5.8.0.11400|091112
ucd9200 8-0034: 4 rails configured
ucd9200 8-0035: Device ID UCD9248-80|5.8.0.11400|091112
ucd9200 8-0035: 4 rails configured
ucd9200 8-0036: Device ID UCD9248-80|5.8.0.11400|091112
ucd9200 8-0036: 2 rails configured
cdns-wdt f8005000.watchdog: Xilinx Watchdog Timer at f09bc000 with timeout 10s
EDAC MC: ECC not enabled
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.mmc [e0100000.mmc] 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: setting system clock to 2019-01-24 13:13:29 UTC (1548335609)
of_cfs_init
of_cfs_init: OK
ALSA device list:
  No soundcards found.
Waiting for root device /dev/mmcblk0p2...
mmc0: new high speed SDHC card at address aaaa
mmcblk0: mmc0:aaaa SL08G 7.40 GiB
 mmcblk0: p1 p2
EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature incompatibilities
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
INIT: version 2.88 booting
Starting udev
udevd[803]: starting version 3.2.2
udevd[804]: starting eudev-3.2.2
FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered
Starting internet superserver: inetd.
INIT: Entering runlevel: 5
Configuring network interfaces... IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
done.
Starting Dropbear SSH server: dropbear.
Starting rpcbind daemon...done.
starting DNS forwarder and DHCP server: dnsmasq... done.
Starting syslogd/klogd: done
Starting tcf-agent: OK

root@test:~# macb e000b000.ethernet eth0: link up (1000/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

This is the output of ifconfig eth0:

 

 

root@test:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 3c:39:e7:e0:2c:e7
          inet addr:192.168.137.10  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::3e39:e7ff:fee0:2ce7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:49 dropped:0 overruns:0 frame:49
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:4056 (3.9 KiB)
          Interrupt:31 Base address:0xb000

root@test:~#

this is the output of ethtool eth0:

 

 

root@test:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 7
        Transceiver: internal
        Auto-negotiation: on
        Link detected: yes

this is the output of mii-tool:

 

 

root@test:~# mii-tool
eth0: negotiated 1000baseT-FD flow-control, link ok

All the configurations and the output of the commands seems to be ok, but, when I am unable to ping my PC.

From the EVK the ping command output is stuck (i have to press CTRL-C to exit):

root@test:~# ping 192.168.137.1
PING 192.168.137.1 (192.168.137.1): 56 data bytes
^C
--- 192.168.137.1 ping statistics ---
151 packets transmitted, 0 packets received, 100% packet loss

From the pc the ping command fails:

C:\Users\user>ping 192.168.137.10

Esecuzione di Ping 192.168.137.10 con 32 byte di dati:
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.

Statistiche Ping per 192.168.137.10:
    Pacchetti: Trasmessi = 4, Ricevuti = 0,
    Persi = 4 (100% persi)

Note: the device-tree configuration is the standard supplied by Petalinux for the eth0 (&gem0) and for the Marvell PHY.

 

Honestly, I don't understand why eth0 is not working: I suspect there's something faulty in the MACB driver, but it's strange because it isn't a new driver..

 

To be exhaustive: the hardware is working because I've tried the Zynq System SD Card Image which is supplied with the ZC702 EVK and, with that petalinux system, the ethernet adapter works like a charm. In that configuration the linux driver for &gem0 is the deprecated EMACPS.

 

What am I doing wrong? Thanks in advance for your help and support!

 

 

0 Kudos
1 Solution

Accepted Solutions
Participant silentlab54
Participant
708 Views
Registered: ‎08-29-2018

Re: No eth0 ethernet connection on Petalinux 2018.2 and 2018.3

Jump to solution

Hi all,

I've finally solved my problem. It is directly related to the voltage levels of the RGMII tx/rx signals.. I've made a typo changing the I/O type to LVCMOS 1.8V.

The correct I/O typer standard for RGMII signals is HSTL 1.8V .

 

Changing my Enet0 signals to HSTL 1.8V solved the problem.

 

Thanks in advance for your support.

 

0 Kudos
4 Replies
Explorer
Explorer
899 Views
Registered: ‎06-03-2015

Re: No eth0 ethernet connection on Petalinux 2018.2 and 2018.3

Jump to solution

Hi

Thesetup is:

  • PC ip address 192.168.137.1, netmask 255.255.255.0
  • ZC702 board ip address 192.168.137.10, netmask 255.255.255.0, gateway 192.168.137.1
  • Satish: From Macb driver, it looks fine because it is probing successfully and mii-tool is also fine,change the PC Ip address to 192.168.137.10 because PC ip & gateway ip are both same.
  • Keep gateway IP as it is & change the PC IP , it will work

Give kudos if reply is helpful

Thanks & Regards

Satish G

G Satish Kumar
0 Kudos
Participant silentlab54
Participant
878 Views
Registered: ‎08-29-2018

Re: No eth0 ethernet connection on Petalinux 2018.2 and 2018.3

Jump to solution

Hi gsatish10,

 

thanks for your answer but I don't think the problem is so straightforward.

However, I have tried to do what you have suggested, with no luck.

 

Here's the configuration adopted:

root@test:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 3c:39:e7:e0:2c:e7
          inet addr:192.168.137.10  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::3e39:e7ff:fee0:2ce7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:28 dropped:0 overruns:0 frame:28
          TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:5974 (5.8 KiB)
          Interrupt:31 Base address:0xb000
root@test:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.137.254 0.0.0.0         UG    0      0        0 eth0
192.168.137.0   0.0.0.0         255.255.255.0   U     0      0        0 eth0
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback
#
auto eth0
iface eth0 inet static
        address 192.168.137.10
        netmask 255.255.255.0
        gateway 192.168.137.254

ping fails both from PC side and ZC702 side.

 

Another point: if I set the configuration to DHCP mode, I have the same behaviour mentioned in  the topic's first post: in u-boot I'm able to receive an IP address from the DHCP server quickly and without any problem, but in Linux the udhcpc client tries to receive an IP address, it fails and forks to the background. ZC702 never receives an IP address.

 

Other useful informations: I post the output of some /sys/ data: I think those data could be useful to understand the problem:

 

root@test:~# ls -l /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx*
-r--r--r--    1 root     root          4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_bytes
-r--r--r--    1 root     root          4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_compressed
-r--r--r--    1 root     root          4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_crc_errors
-r--r--r--    1 root     root          4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_dropped
-r--r--r--    1 root     root          4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_errors
-r--r--r--    1 root     root          4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_fifo_errors
-r--r--r--    1 root     root          4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_frame_errors
-r--r--r--    1 root     root          4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_length_errors
-r--r--r--    1 root     root          4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_missed_errors
-r--r--r--    1 root     root          4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_nohandler
-r--r--r--    1 root     root          4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_over_errors
-r--r--r--    1 root     root          4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_packets
root@test:~# cat /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/rx_* 0 0 209 0 358 0 149 0 0 0 0 0
root@test:~# ls -l /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/tx* -r--r--r-- 1 root root 4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/tx_aborted_errors -r--r--r-- 1 root root 4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/tx_bytes -r--r--r-- 1 root root 4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/tx_carrier_errors -r--r--r-- 1 root root 4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/tx_compressed -r--r--r-- 1 root root 4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/tx_dropped -r--r--r-- 1 root root 4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/tx_errors -r--r--r-- 1 root root 4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/tx_fifo_errors -r--r--r-- 1 root root 4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/tx_heartbeat_errors -r--r--r-- 1 root root 4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/tx_packets -r--r--r-- 1 root root 4096 Jan 25 13:30 /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/tx_window_errors
root@test:~# cat /sys/devices/soc0/amba/e000b000.ethernet/net/eth0/statistics/tx* 0 26332 0 0 0 0 0 0 122 0

 

As you can see, the Tx packets are sent correctly to the Marvell phy, but there's something strange with the incoming packets.

Could be something related to a wrong timing programmed to the rx of the PHY? Cold be an issue related to a wrong device-tree phy-mode parameter?

I've tried different phy-mode settings into the device-tree (I've followed this link), with no luck.

I've also tried to lower the transmit speed of the connection, using  the command mii-tool -F 10baseT-FD. I've tested all the supported modes, 10/100/1000, Half/Full duplex. I never saw good results.

Thanks in advance for your answers!

0 Kudos
Moderator
Moderator
856 Views
Registered: ‎12-04-2016

Re: No eth0 ethernet connection on Petalinux 2018.2 and 2018.3

Jump to solution

Hi

Can you please share your HDF with us if the issue is reproducible in zc702 Eval board?

Best Regards

Shabbir

 

0 Kudos
Participant silentlab54
Participant
709 Views
Registered: ‎08-29-2018

Re: No eth0 ethernet connection on Petalinux 2018.2 and 2018.3

Jump to solution

Hi all,

I've finally solved my problem. It is directly related to the voltage levels of the RGMII tx/rx signals.. I've made a typo changing the I/O type to LVCMOS 1.8V.

The correct I/O typer standard for RGMII signals is HSTL 1.8V .

 

Changing my Enet0 signals to HSTL 1.8V solved the problem.

 

Thanks in advance for your support.

 

0 Kudos