You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+19-2
Original file line number
Diff line number
Diff line change
@@ -18,10 +18,11 @@ Stratum-1 NTP time server with Raspberry Pi, GPS and Chrony:
18
18
While you can use any model of Raspberry Pi to implement a Stratum-1 NTP server with GPS, the best choice
19
19
is Raspberry Pi 4, due to 1Gbit network interface and fast hardware for lowest possible latencies.
20
20
21
-
- Using a Raspberry Pi 5 gives two additional advantages:
21
+
- Using a Raspberry Pi 5 gives two additional advantages, but has changed the configuration of the serial port.
22
22
23
23
- Support for the inbuilt hardware real time clock (RTC) that comes with the Raspberry Pi 5
24
24
- Support for the PTP protocol, which allows to transmit precision time information via ethernet hardware
25
+
- When connecting the GPS receiver via serial port, the new default is not to use the RX, TX pins on the 40pin connector, but the new three-pin UART connector. To use the 40-pin connector a special configuration is needed.
25
26
26
27
Both options are of limited advantage for most settings: the hardware clock is only useful for providing time during the first few seconds after boot (and if both GPS _and_ network are inaccessible), and PTP is a time standard requiring IEEE1588-enabled hardware everywhere and provides no advantages over NTP/chrony in most settings. Both however are documented below (See `chrony` configuration, PTP-chapter).
27
28
@@ -30,7 +31,7 @@ Both options are of limited advantage for most settings: the hardware clock is o
* Raspberry Pi 5 changed the default serial connection to the 3-pin UART connector by default.
76
78
77
79
### Recommended setup
78
80
@@ -90,6 +92,20 @@ _Typical wiring between GPS module and Raspberry Pi connector._
90
92
91
93
> **Note:** If your GPS module is connected via USB, you only need to connect the PPS connector on the GPS module to GPIO 4 on the Raspberry. Power (Vin), Gnd and Tx/Rx are handled via USB.
92
94
95
+
> **Note:** The Raspberry Pi 5 has a new connector for the serial port that is used by default instead of the Pins RX, TX on the diagram:
96
+
97
+
#### Raspberry PI 5 serial connection changes
98
+
99
+
- Either use _new the three-pin UART connector_, which is used by default for serial communication,
100
+
- or reconfigure the serial ports by editing `/boot/firmware/config.txt` and adding the lines:
101
+
102
+
```
103
+
dtparam=uart0
104
+
dtparam=uart0_console
105
+
```
106
+
107
+
Documentation for those options is currently in a disarray for Raspberry Pi 5, so some research might be required. See discussion in [#6](https://github.com/domschl/RaspberryNtpServer/issues/6). Also this [video on Raspberry Pi 5 Serial Port](https://www.youtube.com/watch?v=27p4XHE3iyw) usage might be helpful.
108
+
93
109
### Test
94
110
95
111
**Before you continue with software:** At this point, the GPS module should be connected to the Raspberry Pi and the active antenna. Power up the Raspberry Pi, and check that the GPS module receives the GPS signal (the antenna must have unhindered access to the open sky, it does *not* work indoors!).
@@ -602,6 +618,7 @@ Optionally, you can use [this sub-project to a status display to the Raspberry P
602
618
603
619
## History
604
620
621
+
- 2024-04-30: Changes to Raspberry Pi 5 serial Port configuration, see [6](https://github.com/domschl/RaspberryNtpServer/issues/6), thanks @aGGreSSiv for figuring out the issue!
605
622
- 2024-03-06: Update: location of `/boot/config.txt` has changed to `/boot/firmware/config.txt`. Thanks to @Nebulosa-Cat for the information!
606
623
- 2023-12-21: Cleanup for the display software, display current stratum level (thanks @Lefuneste83, see [#7](https://github.com/domschl/RaspberryNtpServer/issues/7)), implemented logging.
607
624
- 2023-12-20: Raspberry 5 and suport for RTC and PTP precision time protocol how-tos.
0 commit comments