Topic

stm32mp1

A collection of 7 issues

TCXO RTC Raspberry Pi Hat, part 2

The motivation for this project is NTP servers in datacenters - it can be expensive to get a GPS antenna on top of other people's buildings with a wire running down into your rack. The question is, how do you maximize the accuracy of a stratum 2 NTP

Embedded NTP client/NTP interleaved mode, part 5

I'll test what happens when I plug my embedded NTP client directly into my NTP servers, bypassing the Ethernet switch. This ends my long running embedded NTP client series. The systems involved Embedded NTP client (Archmax): Part 4 [https://blog.dan.drown.org/embedded-ntp-client-ntp-interleaved-mode-part-4/], Part 3 [https://blog.

STM32MP1 NTP server, part 3

Previous posts: part 1 [https://blog.dan.drown.org/stm32mp1-ntp-server/], part 2 [https://blog.dan.drown.org/stm32mp1-ntp-server-part-2/], NTP client [https://blog.dan.drown.org/embedded-ntp-client-ntp-interleaved-mode-part-3/] The NTP client confirmed that there was a 943ns difference between my two NTP servers. Now, to investigate where it is coming from. Changes

Embedded NTP client/NTP interleaved mode, part 3

Previous posts: part 1 [https://blog.dan.drown.org/archmax-ntp-client/], part 2 [https://blog.dan.drown.org/embedded-ntp-client-ntp-interleaved-mode-part-2/] In this post, I wrap up my embedded NTP client and use it to measure the difference between my other two NTP servers with hardware timestamps. Goal 1: synchronize the local clock

STM32MP1 NTP server, part 2

Previous post: https://blog.dan.drown.org/stm32mp1-ntp-server/ [https://blog.dan.drown.org/stm32mp1-ntp-server/] I figured out my offset problem, which was not a PLL problem like I thought. Connman has a NTP client enabled by default :(The distro I'm using uses connman by default to manage the

STM32MP1 NTP server

Previous post: Debian for STM32MP1 [https://blog.dan.drown.org/debian-for-stm32mp1/] NIC Hardware Timestamps First step: enable hardware timestamps in chrony.conf: chrony configuration for hardware timestampsNext, enable chrony's measurements log, and verify it's using hardware timestamps (H) not kernel timestamps (K): it's using

Debian for STM32MP1

I bought a STM32MP1 dev board [https://www.st.com/en/evaluation-tools/stm32mp157a-dk1.html] because it has a gigabit NIC with 1588 PTP timestamps as well as hardware timers that can timestamp PPS events without interrupt latency and jitter. I am hoping that it will both be better than the