Hi team,
The customer encountered an issue. They implemented the gPTP protocol themselves and found that when receiving frames, the gPTP frame’s host reason is 0. When the host reason is 0, the timestamp of this frame is not saved by RTD drivers. In NXP’s gPTP software, the received frame’s host reason is 8 (NETC_ETH_IP_HOSTREASON_SW_PTP). I’d like to ask: how can we make the host reason of the received frame be 8?
Best Regards,
Bridget
Could you please answer this question? Thank you.
Hi @Bridget ,
there is necessary to enable timestamping on each port of the NETC switch where you want to receive timestamp information. We do not have other details from you of what tools/versions customer use - so we can provide you just with this general information. In our case where we use Tresos and RTD it is directly done in each port configuration of switch plugin.
best regards,
Tomas
Hi Bridget,
please follow UM for EthSwt from RTD - the parameter should be
For more details please consult with RTD. I would also suggest to check our gPTP example for N5 - but in your first message you wrote, that customer implemented own the gPTP - so probably you do not have our example.
best regards,
Tomas
Hi Tomas,
The customer use the SW32N_RTD_R21-11_1.8.0_CD05.
They want to receive the gPTP frames in RTU and get the receive timestamps. They can receive the frames after enabling broadcast frame reception. Timestamp functionality is also enabled. But they find that to obtain the reception timestamp, the frame's host reason needs to be NETC_ETH_IP_HOSTREASON_SW_PTP (this macro equals 8), as shown in the code in the screenshot below.
However, their Rx BD has a host reason of 0. Could you please advise how to configure it so that the host reason becomes 8?
Best Regards,
Bridget
I already answered the two questions which you have - please check.