Hello Kinsey, thanks for the answer. I am now using the REPHY driver and everything is working fine:
diff --git a/rtemsbsd/include/bsp/nexus-devices.h b/rtemsbsd/include/bsp/nexus-devices.h index ac4a52a1..6908ca46 100644 --- a/rtemsbsd/include/bsp/nexus-devices.h +++ b/rtemsbsd/include/bsp/nexus-devices.h @@ -100,7 +100,8 @@ RTEMS_BSD_DRIVER_XILINX_ZYNQ_SLCR; RTEMS_BSD_DRIVER_XILINX_ZYNQ_SDHCI0; RTEMS_BSD_DRIVER_XILINX_ZYNQ_SDHCI1; RTEMS_BSD_DRIVER_XILINX_ZYNQ_CGEM0(ZYNQ_IRQ_ETHERNET_0); -RTEMS_BSD_DRIVER_E1000PHY; +/* RTEMS_BSD_DRIVER_E1000PHY; */ +RTEMS_BSD_DRIVER_REPHY; RTEMS_BSD_DRIVER_MMC; Heinz > On 14. Aug 2024, at 19:41, Kinsey Moore <kinsey.mo...@oarcorp.com> wrote: > > Even if that one isn't already used, the generic PHY driver (UKPHY) will work > most of the time as long as it's enabled (it isn't by default for the Zynq > BSPs). I haven't done much with the Zynq boards, so I won't be of much help. > The link you posted mentioned a board frequency change. Have you verified > that the default clock hasn't changed for your RevD board? > > Kinsey > > On Wed, Aug 14, 2024 at 5:14 AM Heinz Junkes <jun...@fhi-berlin.mpg.de> wrote: > I have a Rev.D board and it has a different Realtek PHY with different > connections to MIO Bank. > RTL8211F instead of RTL8211E > I have to find out where this is defined/used in the rtems-libbsd. > Heinz > > > > On 13. Aug 2024, at 17:16, Heinz Junkes <jun...@fhi-berlin.mpg.de> wrote: > > > > This is the output of NFS01 Test: > > > > *** BEGIN OF TEST LIBBSD NFS 1 *** > > *** TEST VERSION: 6.0.0.e5b6fa026ac1c07d252233624054785b2b29f54e > > *** TEST STATE: USER_INPUT > > *** TEST BUILD: RTEMS_POSIX_API > > *** TEST TOOLS: 13.3.0 20240521 (RTEMS 6, RSB > > 4c6dfb7aef9811258457971aa9213d5aebb9ce8d, Newlib 1ed1516) > > nexus0: <RTEMS Nexus device> > > cgem0: <Cadence CGEM Gigabit Ethernet Interface> on nexus0 > > miibus0: <MII bus> on cgem0 > > info: cgem0: Ethernet address: 92:c2:88:7d:f4:79 > > arasan_sdhci1: <Arasan SDIO> on nexus0 > > arasan_sdhci1-slot0: Hardware doesn't specify base clock frequency, using > > 50MHz as default. > > arasan_sdhci1-slot0: Hardware doesn't specify timeout clock frequency, > > setting BROKEN_TIMEOUT quirk. > > arasan_sdhci1-slot0: Hardware doesn't report any support voltages. > > arasan_sdhci1: Card Detect failed to stabilize, setting to not present. > > arasan_sdhci0: <Arasan SDIO> on nexus0 > > arasan_sdhci0-slot0: Hardware doesn't specify base clock frequency, using > > 50MHz as default. > > arasan_sdhci0-slot0: Hardware doesn't specify timeout clock frequency, > > setting BROKEN_TIMEOUT quirk. > > mmc0: <MMC/SD bus> on arasan_sdhci0 > > zy7_slcr0: <Zynq-7000 slcr block> on nexus0 > > mmcsd0: 16GB <SDHC SC16G 8.0 SN E237916D MFG 01/2021 by 3 SD> (read-only) > > at mmc0 50.0MHz/4bit/65535-block > > info: lo0: link state changed to UP > > add host 141.14.128.128: gateway cgem0 > > add net default: gateway 141.14.128.128 > > error: cgem0: no active link > > assertion "seconds < 10" failed: file > > "../../testsuite/include/rtems/bsd/test/default-network-init.h", line 193, > > function: default_wait_for_link_up > > > > *** FATAL *** > > fatal source: 7 (RTEMS_FATAL_SOURCE_ASSERT) > > fatal code: 3443784 (0x00348c48) > > RTEMS version: 6.0.0.e5b6fa026ac1c07d252233624054785b2b29f54e > > RTEMS tools: 13.3.0 20240521 (RTEMS 6, RSB > > 4c6dfb7aef9811258457971aa9213d5aebb9ce8d, Newlib 1ed1516) > > executing thread ID: 0x0a010001 > > executing thread name: UI1 > > > > Heinz > > > >> On 13. Aug 2024, at 16:40, Heinz Junkes <jun...@fhi-berlin.mpg.de> wrote: > >> > >> Hi, > >> unfortunately I cannot activate the cgem0 network interface with RTEMS 6 > >> (libbsd 6-freebsd-12) > >> on a xilinx_zynq_zybo_z7 board : > >> > >> cgem0: flags�43<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > >> d options�008<VLAN_MTU,LINKSTATE> > >> e ether 92:c2:88:7d:f4:79 > >> inet6 fe80::90c2:88ff:fe7d:f479%cgem0 prefixlen 64 scopeid 0x1 > >> b inet 141.14.128.72 netmask 0xfffff000 broadcast 141.14.143.255 > >> u nd6 options!<PERFORMNUD,AUTO_LINKLOCAL> > >> ifconfig: cgem0: ngo media types?: cgem0: sending ARP announce (1 of 2), > >> next in 2.0 seconds > >> > >> > >> These messages appear during startup : > >> > >> ***** Initializing network (libbsd, dhcpcd) ***** > >> nexus0: <RTEMS Nexus device> > >> cgem0: <Cadence CGEM Gigabit Ethernet Interface> on nexus0 > >> miibus0: <MII bus> on cgem0 > >> info: cgem0: Ethernet address: 92:c2:88:7d:f4:79 > >> arasan_sdhci1: <Arasan SDIO> on nexus0 > >> arasan_sdhci1-slot0: Hardware doesn't specify base clock frequency, using > >> 50MHz as default. > >> arasan_sdhci1-slot0: Hardware doesn't specify timeout clock frequency, > >> setting BROKEN_TIMEOUT quirk. > >> arasan_sdhci1-slot0: Hardware doesn't report any support voltages. > >> arasan_sdhci1: Card Detect failed to stabilize, setting to not present. > >> arasan_sdhci0: <Arasan SDIO> on nexus0 > >> arasan_sdhci0-slot0: Hardware doesn't specify base clock frequency, using > >> 50MHz as default. > >> arasan_sdhci0-slot0: Hardware doesn't specify timeout clock frequency, > >> setting BROKEN_TIMEOUT quirk. > >> mmc0: <MMC/SD bus> on arasan_sdhci0 > >> zy7_slcr0: <Zynq-7000 slcr block> on nexus0 > >> mmcsd0: 16GB <SDHC SC16G 8.0 SN E237916D MFG 01/2021 by 3 SD> (read-only) > >> at mmc0 50.0MHz/4bit/65535-block > >> > >> I have already found a suitable entry here, but unfortunately I don't know > >> how it 'fits' my problem: > >> https://lists.rtems.org/pipermail/users/2023-July/068855.html > >> > >> > >> Danke Heinz_______________________________________________ > >> devel mailing list > >> devel@rtems.org > >> http://lists.rtems.org/mailman/listinfo/devel > > > > > > _______________________________________________ > > devel mailing list > > devel@rtems.org > > http://lists.rtems.org/mailman/listinfo/devel > > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
