topic Re: Hardware timestamping for IEEE 1588 (PTP) via UDP not working with default values in Ethernet Products

Hardware timestamping for IEEE 1588 (PTP) via UDP not working with default values

MehTheHedgehog — Wed, 05 Feb 2020 20:17:01 GMT

Hi,

We are currently working on PTP implementation using DPDK with Intel X520-DA2 (82599 Controller). We encountered an issue with default configuration of 82599 controller for UDP port number filter.

As stated in datasheets(8.2.3.26.6), register RXMTRL(31:16 bit) is default initialized to value 0x319 (dec: 793), but it should be 0x13F (dec: 319).

8.2.3.26.6 Rx Message Type Register Low — RXMTRL (0x05120; RW)

UDPT | 31:16 | 0x319 | UDP port number to time stamp.

This post is just informational for anyone looking for this problem.

Also we think this should be stated somewhere in datasheets (or errata) that this value is misconfigured and will not be working with default ptp implementations.

Regards,

Artur

Re: Hardware timestamping for IEEE 1588 (PTP) via UDP not working with default values

Mike_Intel — Thu, 06 Feb 2020 09:25:34 GMT

Hello MehTheHedgehog,

Thank you for posting in Intel Ethernet Communities.

Regarding your inquiry, kindly open the link below on how you can access DPDK support.

Click the "Login and Access" to contact the DPDK support.

https://www.intel.com/content/www/us/en/design/support/ips/training/welcome.html

If you still have questions, please let us know. If there is no reply, is it okay if make a follow up after 3 business days?

Best regards,

Michael L.

Intel Customer Support Technicians

A Contingent Worker at Intel

Re: Hardware timestamping for IEEE 1588 (PTP) via UDP not working with default values

AlfredoS_Intel — Fri, 21 Feb 2020 12:49:25 GMT

Hi MehTheHedgehog,

Thank you for posting on our Intel® Ethernet Communities page.

We have not received your response on this forum, and we are reaching out to check if you need more time.

Should we not hear from you, we will check back with you again after 3 business days.

Best Regards,

Alfred S

Intel Customer Support

Re: Hardware timestamping for IEEE 1588 (PTP) via UDP not working with default values

Mike_Intel — Wed, 26 Feb 2020 07:57:39 GMT

Hello MehTheHedgehog,

I am sending another follow up on the information that I requested.

Since we have not heard back from you, I need to close this inquiry.

If you need further assistance, please post a new question.

Best regards,

Michael L.

Intel Customer Support Technicians

Re: Hardware timestamping for IEEE 1588 (PTP) via UDP not working with default values

lexa — Mon, 14 Feb 2022 17:00:55 GMT

Hi,

I'm trying to get hardware timestamping working with Intel NICs, but it's not working as advertised.

I use an Intel I210 adapter (Intel I210 server adapter) under Windows 11 (I'm not sure hardware timestamping is supposed to work on Windows 10, because to my knowledge Windows 10 is not supporting hardware timestamping, who has more information regarding Windows 10, please explain).

I use the latest Intel Ethernet complete driver pack 27.0 which lets me choose the I210 driver version 13.0.13.0 from January 31st 2022.

I have set "PTP Hardware Timestamp" to "Enabled". No matter if I choose "Disabled" or any other setting" for "Software Timestamp" calling Windows API function "GetInterfaceActiveTimestampCapabilities" fails with error "ERROR_BAD_DRIVER".

I think this is a bug in the I210 driver.

Could someone please comment on this?

Thank you.

Re: Hardware timestamping for IEEE 1588 (PTP) via UDP not working with default values

lexa — Mon, 14 Feb 2022 17:17:05 GMT

Sorry, I think I posted to the wrong thread.

Re: Hardware timestamping for IEEE 1588 (PTP) via UDP not working with default values

Ossama-MOUSTAFA — Tue, 29 Nov 2022 19:53:50 GMT

Hi @lexa.

I have the same problem here, for GetInterfaceActiveTimestampCapabilities() ("ERROR_BAD_DRIVER").

Did you find any solution, please ?

Re: Hardware timestamping for IEEE 1588 (PTP) via UDP not working with default values

lexa — Tue, 29 Nov 2022 22:52:21 GMT

No, still the same, ERROR_BAD_DRIVER.