Text only | Text with Images

Trenz Electronic GmbH Support Forum

Trenz Electronic Products => Trenz Electronic FPGA Modules => Topic started by: Brainiac on April 23, 2018, 03:46:32 PM

Title: TE0782-100 PL eth1 problem
Post by: Brainiac on April 23, 2018, 03:46:32 PM
Hello!

I have an issue with te0782-100 module

I tryed to launch ethernet which connects through PL in delivery state on TEBT0782, but it does not work

dmesg output is^

Code Select

root@te0782_test_board:~# dmesg
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.
PCI: CLS 0 bytes, default 64
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
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)
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
e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 145, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
bootconsole [earlycon0] disabled
xdevcfg f8007000.devcfg: ioremap 0xf8007000 to f086c000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
libphy: MACB_mii_bus: probed
mdio_bus e000b000.etherne: /amba/ethernet@e000b000/mdio has invalid PHY address
mdio_bus e000b000.etherne: scan phy mdio at address 0
mdio_bus e000b000.etherne: scan phy mdio at address 1
mdio_bus e000b000.etherne: scan phy mdio at address 2
mdio_bus e000b000.etherne: scan phy mdio at address 3
mdio_bus e000b000.etherne: scan phy mdio at address 4
mdio_bus e000b000.etherne: scan phy mdio at address 5
mdio_bus e000b000.etherne: scan phy mdio at address 6
mdio_bus e000b000.etherne: scan phy mdio at address 7
mdio_bus e000b000.etherne: scan phy mdio at address 8
mdio_bus e000b000.etherne: scan phy mdio at address 9
mdio_bus e000b000.etherne: scan phy mdio at address 10
mdio_bus e000b000.etherne: scan phy mdio at address 11
mdio_bus e000b000.etherne: scan phy mdio at address 12
mdio_bus e000b000.etherne: scan phy mdio at address 13
mdio_bus e000b000.etherne: scan phy mdio at address 14
mdio_bus e000b000.etherne: scan phy mdio at address 15
mdio_bus e000b000.etherne: scan phy mdio at address 16
mdio_bus e000b000.etherne: scan phy mdio at address 17
mdio_bus e000b000.etherne: scan phy mdio at address 18
mdio_bus e000b000.etherne: scan phy mdio at address 19
mdio_bus e000b000.etherne: scan phy mdio at address 20
mdio_bus e000b000.etherne: scan phy mdio at address 21
mdio_bus e000b000.etherne: scan phy mdio at address 22
mdio_bus e000b000.etherne: scan phy mdio at address 23
mdio_bus e000b000.etherne: scan phy mdio at address 24
mdio_bus e000b000.etherne: scan phy mdio at address 25
mdio_bus e000b000.etherne: scan phy mdio at address 26
mdio_bus e000b000.etherne: scan phy mdio at address 27
mdio_bus e000b000.etherne: scan phy mdio at address 28
mdio_bus e000b000.etherne: scan phy mdio at address 29
mdio_bus e000b000.etherne: scan phy mdio at address 30
mdio_bus e000b000.etherne: scan phy mdio at address 31
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 147 (00:0a:35:00:1e:53)
macb e000b000.ethernet eth0: attached PHY driver [Marvell 88E1510] (mii_bus:phy_addr=e000b000.etherne:01, irq=-1)
macb e000c000.ethernet: invalid hw address, using random
libphy: MACB_mii_bus: probed
mdio_bus e000c000.etherne: /amba/ethernet@e000c000/mdio has invalid PHY address
mdio_bus e000c000.etherne: scan phy mdio at address 0
mdio_bus e000c000.etherne: scan phy mdio at address 1
mdio_bus e000c000.etherne: scan phy mdio at address 2
mdio_bus e000c000.etherne: scan phy mdio at address 3
mdio_bus e000c000.etherne: scan phy mdio at address 4
mdio_bus e000c000.etherne: scan phy mdio at address 5
mdio_bus e000c000.etherne: scan phy mdio at address 6
mdio_bus e000c000.etherne: scan phy mdio at address 7
mdio_bus e000c000.etherne: scan phy mdio at address 8
mdio_bus e000c000.etherne: scan phy mdio at address 9
mdio_bus e000c000.etherne: scan phy mdio at address 10
mdio_bus e000c000.etherne: scan phy mdio at address 11
mdio_bus e000c000.etherne: scan phy mdio at address 12
mdio_bus e000c000.etherne: scan phy mdio at address 13
mdio_bus e000c000.etherne: scan phy mdio at address 14
mdio_bus e000c000.etherne: scan phy mdio at address 15
mdio_bus e000c000.etherne: scan phy mdio at address 16
mdio_bus e000c000.etherne: scan phy mdio at address 17
mdio_bus e000c000.etherne: scan phy mdio at address 18
mdio_bus e000c000.etherne: scan phy mdio at address 19
mdio_bus e000c000.etherne: scan phy mdio at address 20
mdio_bus e000c000.etherne: scan phy mdio at address 21
mdio_bus e000c000.etherne: scan phy mdio at address 22
mdio_bus e000c000.etherne: scan phy mdio at address 23
mdio_bus e000c000.etherne: scan phy mdio at address 24
mdio_bus e000c000.etherne: scan phy mdio at address 25
mdio_bus e000c000.etherne: scan phy mdio at address 26
mdio_bus e000c000.etherne: scan phy mdio at address 27
mdio_bus e000c000.etherne: scan phy mdio at address 28
mdio_bus e000c000.etherne: scan phy mdio at address 29
mdio_bus e000c000.etherne: scan phy mdio at address 30
mdio_bus e000c000.etherne: scan phy mdio at address 31
macb e000c000.ethernet eth1: Cadence GEM rev 0x00020118 at 0xe000c000 irq 148 (da:6a:42:82:d7:4e)
macb e000c000.ethernet eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000c000.etherne:08, irq=-1)
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
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
e0003000.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.1: EHCI Host Controller
ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 2
ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 141
rtc-isl12022 1-006f: rtc core: registered rtc-isl12022 as rtc0
cdns-i2c e0005000.i2c: 400 kHz mmio e0005000 irq 142
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
sdhci-arasan e0101000.sdhci: No vmmc regulator found
sdhci-arasan e0101000.sdhci: No vqmmc regulator found
mmc0: SDHCI controller on e0101000.sdhci [e0101000.sdhci] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
Registering SWP/SWPB emulation handler
rtc-isl12022 1-006f: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
ALSA device list:
  No soundcards found.
mmc0: MAN_BKOPS_EN bit is not set
Freeing unused kernel memory: 4040K (c067a000 - c0a6c000)
mmc0: new high speed MMC card at address 0001
mmcblk0: mmc0:0001 Q2J54A 3.58 GiB
mmcblk0boot0: mmc0:0001 Q2J54A partition 1 16.0 MiB
mmcblk0boot1: mmc0:0001 Q2J54A partition 2 16.0 MiB
mmcblk0rpmb: mmc0:0001 Q2J54A partition 3 512 KiB
mmcblk0: p1 p2
FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
EXT4-fs (mmcblk0rpmb): unable to read superblock
EXT4-fs (mmcblk0rpmb): unable to read superblock
EXT2-fs (mmcblk0rpmb): error: unable to read superblock
FAT-fs (mmcblk0rpmb): unable to read boot sector
EXT4-fs (mmcblk0rpmb): unable to read superblock
EXT4-fs (mmcblk0rpmb): unable to read superblock
EXT2-fs (mmcblk0rpmb): error: unable to read superblock
FAT-fs (mmcblk0rpmb): unable to read boot sector
FAT-fs (mmcblk0rpmb): unable to read boot sector
random: dd urandom read with 5 bits of entropy available
macb e000b000.ethernet eth0: link up (100/Full)
macb e000b000.ethernet eth0: link down
macb e000b000.ethernet eth0: link up (10/Full)
macb e000b000.ethernet eth0: link down
random: nonblocking pool is initialized



Is it ok that on second ethernet kernel found only generic phy, not marvel?

I tryed to lauch PL ethernet, but it does not work too.
Only when I program PL side with bitstream, when linux is launched on ARM I have ONLY RX packets on eth1

Code Select

eth1      Link encap:Ethernet  HWaddr DA:6A:42:82:D7:4E
          inet addr:192.168.80.243  Bcast:192.168.80.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:28235 errors:0 dropped:1 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2221412 (2.1 MiB)  TX bytes:0 (0.0 B)
          Interrupt:148 Base address:0xc000


How to solve this problem? Are any tools for mdio interface to check state of phy?

Title: Re: TE0782-100 PL eth1 problem
Post by: JH on April 24, 2018, 04:51:39 PM
Hi,

we have an 2017.1 reference design available, with both eth:
Currently only with short description on the download webpage. petalinux template project and also prebuilt files are included. For petalinux see also:br
John
Title: Re: TE0782-100 PL eth1 problem
Post by: Brainiac on April 25, 2018, 08:08:47 PM
I have a feeling that eth1 works only for 10Mbit/s. In 100mbit/s and 1000mbit/s I could not get data transmitting or receving. Connection had only link up and that's all. I could ping device by eth1 in point to point connection, but could not get ping for 100mbit/s and higher
Is it true or I did something wrong?
Title: Re: TE0782-100 PL eth1 problem
Post by: JH on April 25, 2018, 08:47:22 PM
Hi,

did you try out the reference design?
br
John
Title: Re: TE0782-100 PL eth1 problem
Post by: Brainiac on April 26, 2018, 12:27:09 PM
I think yes. I try another time

Is it true that reference design from trenz works with 100mbit/s and higher?
Title: Re: TE0782-100 PL eth1 problem
Post by: JH on April 26, 2018, 12:46:24 PM
Hi,

which version did you try out?

ETH console log from 2017.1 reference design is on the attachment.

br
John

Title: Re: TE0782-100 PL eth1 problem
Post by: Brainiac on April 28, 2018, 11:50:58 AM
Thank you for help!
There were some errors and misunderstanding of zynq work in my mind

I repeat this result and all works with trenz bit and petalinux
Text only | Text with Images