-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Using two SAMA5D3 EDS with plug-in card EVB-KSZ8563, my objective is to have a functional PTP master and slave.
Started with buildroot-mchp branch 2024.02-mchp and buildroot-external-microchip branch linux4microchip-2025.04 build a sdcard image, it boots and connects to a network.
The issue is when launching ptp4l it throws driver rejected error and enter failed state despite ethtool confirming hw timestamp support.
Another issue is that there is no pps output (no pps device on /dev), pps support is enabled on kernel (CONFIG_PPS=y, CONFIG_NETWORK_PHY_TIMESTAMPING=y, CONFIG_PTP_1588_CLOCK=y)
Does mentioned branch of buildroot-mchp fully supports PTP? I'm avoiding EVB-KSZ9477 repository since it fails to build (there is a pull request pending for years) and uses very old kernel version.
Build was made as instructed by readme using sama5d3_eds_headless_defconfig and u-boot _chip variable was set to ksz8563.
Output of $ ethtool -T lan1
Time stamping parameters for lan1:
Capabilities:
hardware-transmit
hardware-receive
software-receive
software-system-clock
hardware-raw-clock
PTP Hardware Clock: 0
Hardware Transmit Timestamp Modes:
off
onestep-p2p
Hardware Receive Filter Modes:
none
ptpv2-l4-event
ptpv2-l2-event
ptpv2-event
Output of $ ptp4l -m -l6 -i lan1
ptp4l[136.462]: selected /dev/ptp0 as PTP clock
ptp4l[136.474]: driver rejected most general HWTSTAMP filter
ptp4l[136.476]: ioctl SIOCSHWTSTAMP failed: Numerical result out of range
ptp4l[136.477]: port 1 (lan1): INITIALIZING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[136.479]: port 0 (/var/run/ptp4l): INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[136.484]: port 0 (/var/run/ptp4lro): INITIALIZING to LISTENING on INIT_COMPLETE