slave must be booted up no later than 2 minutes after master / master restarts not supported #1
Description
At the moment the only source of information about master's clock slaves have are T1/T4 fields of FTM reports, which are 48 bits picosecond counters. These counter overflows every 2 minutes. During normal operation detect the overflow and track master's clock correctly. But if slave misses the wrap around event, they will have incorrect idea of master's clock.
One solution is for master to broadcast its full clock (64 bits counter, 25ns resolution). In fact broadcasting is already implemented. I have not yet figured out how to digest the broadcasts on slaves side without creating any race conditions.