mtharp / laureline-firmware Goto Github PK

Add an option to use GPS and/or TAI timescales instead of UTC.

One or more log entries get sent that say time-of-day is valid, yet have the default starting time of 1900-01-01. The ToD flag should stay clear until the clock has actually been set.

This may be affected by changes made in #1

Prevent replies being delayed by an ARP or NDP lookup. Just use the layer 2 source address from the query packet.

Implement NTPv4 support which would offer IPv6

The current logging implementation just sends raw data once per second, which isn't very useful. Send "cooked" statistics less frequently, perhaps something similar to what ntpd would send.

If responding to a query triggers an ARP request, then some time will elapse between when the reply was generated and when it is finally sent. Postpone writing that field until immediately before transmission.

Receive leap second data from GPS and advertise it to NTP clients.

After flashing the bootloader v4.2 and ll.hex (also 4.2) I have the status LED solid yellow and the PPS blinking red for hours. Console output says:
1900-01-01T00:15:43.702180Z vtimer NOTE step(PPS) -197400 us
1900-01-01T00:15:01.899901Z loopstats INFO off:-108570111ns freq:-11844012ppb jit:129443958ns fjit:0ppt looptc:4s state:1 flags:PPS,!ToD,!PLL,!QUANT

DHCP leases renew many times later than they should due to a timer issue. This also potentially affects any other part of the network stack that uses timers.