Re: MicroZed PHY timeout
Hey Kinsey, Thanks for the response. Yes, I am using the 6-freebsd-12 branch of rtems-libbsd. This doesn’t make any sense to me, but i get the error when I build everything (rsb, rtems, libbsd) on Redhat Enterprise Linux 8. If I build everything on Ubuntu 22.04, everything works fine. -Rick > On Mar 13, 2024, at 10:00 AM, Kinsey Moore wrote: > > As far as I know, the Zynq LibBSD CGEM support hasn't changed much beyond > the updates to support ZynqMP variants of the peripheral. Are you building > LibBSD master or 6-freebsd-12? > > Kinsey > > -Original Message- > From: users On Behalf Of Richard VanderWal > Sent: Tuesday, March 12, 2024 11:34 AM > To: RTEMS Users > Subject: MicroZed PHY timeout > > Good Morning, > > We are moving our RTEMS 5.1 application on ARM 32 MicroZed hardware (BSP > arm/xilinx_zynq_zedboard) to the latest RTEMS master. We have found that the > cgem0 interface no longer is initialized and we’re seeing a “phy read > timeout: 1” message during boot. This appears to be happening in a call to > cgem_miibus_readreg called from cgem_probe. > > We’re running on actual Avnet MicroZed board not anything custom. > > Has anyone else encountered this? Any help is appreciated. > > Thanks in advance! > Rick VanderWal > > > ___ > users mailing list > users@rtems.org > http://lists.rtems.org/mailman/listinfo/users ___ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
Re: MicroZed PHY timeout
On 14/3/2024 2:00 am, Kinsey Moore wrote: > As far as I know, the Zynq LibBSD CGEM support hasn't changed much beyond the > updates to support ZynqMP variants of the peripheral. Are you building LibBSD > master or 6-freebsd-12? > > Kinsey > > -Original Message- > From: users On Behalf Of Richard VanderWal > Sent: Tuesday, March 12, 2024 11:34 AM > To: RTEMS Users > Subject: MicroZed PHY timeout > > Good Morning, > > We are moving our RTEMS 5.1 application on ARM 32 MicroZed hardware (BSP > arm/xilinx_zynq_zedboard) to the latest RTEMS master. We have found that the > cgem0 interface no longer is initialized and we’re seeing a “phy read > timeout: 1” message during boot. This appears to be happening in a call to > cgem_miibus_readreg called from cgem_probe. > > We’re running on actual Avnet MicroZed board not anything custom. > > Has anyone else encountered this? Any help is appreciated. > As a starting point and a guess I would check the clock to the PHY. If something in the path to defining the PHY clock changed it could result in the PHY appearing to no work. The cgem driver is being used on Zynq, ZynqMP and Versal boards now and something may have touched the clock set up. Chris ___ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
RE: MicroZed PHY timeout
As far as I know, the Zynq LibBSD CGEM support hasn't changed much beyond the updates to support ZynqMP variants of the peripheral. Are you building LibBSD master or 6-freebsd-12? Kinsey -Original Message- From: users On Behalf Of Richard VanderWal Sent: Tuesday, March 12, 2024 11:34 AM To: RTEMS Users Subject: MicroZed PHY timeout Good Morning, We are moving our RTEMS 5.1 application on ARM 32 MicroZed hardware (BSP arm/xilinx_zynq_zedboard) to the latest RTEMS master. We have found that the cgem0 interface no longer is initialized and we’re seeing a “phy read timeout: 1” message during boot. This appears to be happening in a call to cgem_miibus_readreg called from cgem_probe. We’re running on actual Avnet MicroZed board not anything custom. Has anyone else encountered this? Any help is appreciated. Thanks in advance! Rick VanderWal ___ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users ___ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
MicroZed PHY timeout
Good Morning, We are moving our RTEMS 5.1 application on ARM 32 MicroZed hardware (BSP arm/xilinx_zynq_zedboard) to the latest RTEMS master. We have found that the cgem0 interface no longer is initialized and we’re seeing a “phy read timeout: 1” message during boot. This appears to be happening in a call to cgem_miibus_readreg called from cgem_probe. We’re running on actual Avnet MicroZed board not anything custom. Has anyone else encountered this? Any help is appreciated. Thanks in advance! Rick VanderWal ___ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users