<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hi all,<br>
<br>
I am working on bringing up the Ethernet interface for RTEMS 4.12 with libBSD on a Xilinx zc702 (<a href="https://wiki.trenz-electronic.de/display/TE0720/TE0720+User+Manual">GigaZee</a>) board. I currently have 6 configurations, Zedboard and GigaZee, each running
U-Boot, Yocto and RTEMS. Only in the GigaZee with RTEMS configuration am I having the problem that the Ethernet interface can not be found.<br>
<br>
I have run the netshell, loopback and DHCPD examples on both devices. Loopback works on both, but on the GigaZee, I run into the problem that<br>
<br>
nexus0: <RTEMS Nexus device><br>
info: version 6.2.1 starting<br>
err: no valid interfaces found<br>
warning: no interfaces have a carrier<br>
<br>
Whereas on the Zedboard the output starts with the following for the DHCP01 example:<br>
<br>
nexus0: <RTEMS Nexus device><br>
cgem0: <Cadence CGEM Gigabit Ethernet Interface> on nexus0<br>
miibus0: <MII bus> on cgem0<br>
e1000phy0: <Marvell 88E1512 Gigabit PHY> PHY 0 on miibus0<br>
e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000bo<br>
cgem0: Ethernet address: 00:0a:35:00:01:04<br>
zy7_slcr0: <Zynq-7000 slcr block> on nexus0<br>
notice: cgem0: link state changed to DOWN<br>
info: version 6.2.1 starting<br>
warning: no interfaces have a carrier<br>
info: cgem0: waiting for carrier<br>
notice: cgem0: link state changed to UP<br>
info: cgem0: carrier acquired<br>
info: DUID 00:01:00:01:e9:6d:a1:82:00:0a:35:00:01:04<br>
info: cgem0: IAID 35:00:01:04<br>
info: cgem0: soliciting an IPv6 router<br>
debug: cgem0: delaying Router Solicitation for LL address<br>
debug: cgem0: using hwaddr 00:0a:35:00:01:04<br>
info: cgem0: soliciting a DHCP lease<br>
debug: cgem0: sending DISCOVER (xid 0x158cc5c9), next in %0.1f seconds<br>
...<br>
<br>
I've compared the device tree files for both the Zedboard and the GigaZee and they differ only slightly:<br>
<br>
GigaZee:<br>
<br>
ethernet@e000b000 {<br>
compatible = "cdns,gem";<br>
reg = <0xe000b000 0x1000>;<br>
status = "okay";<br>
interrupts = <0x0 0x16 0x4>;<br>
clocks = <0x1 0x1e 0x1 0x1e 0x1 0xd>;<br>
clock-names = "pclk", "hclk", "tx_clk";<br>
#address-cells = <0x1>;<br>
#size-cells = <0x0>;<br>
phy-mode = "rgmii-id";<br>
xlnx,ptp-enet-clock = <0x69f6bcb>;<br>
local-mac-address = [00 0a 35 00 1e 53];<br>
};<br>
<br>
ethernet@e000c000 {<br>
compatible = "cdns,gem";<br>
reg = <0xe000c000 0x1000>;<br>
status = "disabled";<br>
interrupts = <0x0 0x2d 0x4>;<br>
clocks = <0x1 0x1f 0x1 0x1f 0x1 0xe>;<br>
clock-names = "pclk", "hclk", "tx_clk";<br>
#address-cells = <0x1>;<br>
#size-cells = <0x0>;<br>
};<br>
<br>
ZedBoard:<br>
<br>
ethernet@e000b000 {<br>
compatible = "cdns,zynq-gem", "cdns,gem";<br>
reg = <0xe000b000 0x1000>;<br>
status = "okay";<br>
interrupts = <0x0 0x16 0x4>;<br>
clocks = <0x1 0x1e 0x1 0x1e 0x1 0xd>;<br>
clock-names = "pclk", "hclk", "tx_clk";<br>
#address-cells = <0x1>;<br>
#size-cells = <0x0>;<br>
phy-mode = "rgmii-id";<br>
phy-handle = <0x4>;<br>
<br>
ethernet-phy@0 {<br>
reg = <0x0>;<br>
linux,phandle = <0x4>;<br>
phandle = <0x4>;<br>
};<br>
};<br>
<br>
ethernet@e000c000 {<br>
compatible = "cdns,zynq-gem", "cdns,gem";<br>
reg = <0xe000c000 0x1000>;<br>
status = "disabled";<br>
interrupts = <0x0 0x2d 0x4>;<br>
clocks = <0x1 0x1f 0x1 0x1f 0x1 0xe>;<br>
clock-names = "pclk", "hclk", "tx_clk";<br>
#address-cells = <0x1>;<br>
#size-cells = <0x0>;<br>
};<br>
<br>
This is my first mailing list request, so please excuse any inadvertent missteps.<br>
<br>
Best regards,<br>
Moritz<br>
</div>
</body>
</html>