lib_tsn: gPTP: MDSyncReceiveSM doesn't block PortSyncSyncReceive

If you have a simple question and just want an answer.
User avatar
MikeCole
Junior Member
Posts: 4
Joined: Tue Jul 09, 2019 8:26 pm

lib_tsn: gPTP: MDSyncReceiveSM doesn't block PortSyncSyncReceive

Postby MikeCole » Thu Aug 01, 2019 4:02 pm

https://github.com/xmos/lib_tsn/issues/36 has anyone found a solution to this issue?
User avatar
akp
Respected Member
Posts: 314
Joined: Thu Nov 26, 2015 11:47 pm

Postby akp » Fri Aug 02, 2019 3:42 pm

Did you get a patch for this issue? I have to admit I can't follow the logic, when the AGED event breaks what's the fallout?
User avatar
MikeCole
Junior Member
Posts: 4
Joined: Tue Jul 09, 2019 8:26 pm

Postby MikeCole » Fri Aug 02, 2019 8:33 pm

akp wrote:
Fri Aug 02, 2019 3:42 pm
Did you get a patch for this issue? I have to admit I can't follow the logic, when the AGED event breaks what's the fallout?
ahogan had replied with a patch and then it was mysteriously removed. by whom I do not know! We are testing using the AVNU violett test suite and we are getting some gPTP errors.

The PortAnnounceInformation State Machine does not seem to check currentTime=syncReceiptTimeoutTime and enter the AGED state.

The test specification for gPTP.com.c.3.1b can be found in the following Avnu document:
https://groups.avnu.org/wg/Avnu_Members/document/3133

The issue can be found where the TS is sending Sync/FollowUp every 500ms which is definitely a timeout situation. However the device does not start sending Announce and Sync/FollowUp as it should.

Who is online

Users browsing this forum: No registered users and 1 guest