How in-accuracy of SYSCLK affects the HAL_GetTick?
I have observed, using a frequency counter, that the HSE clock on Nucleo board (after using the calibration value in the OTP memory) is off by around 20ppm. I have configured the SYSCLK to HSE_SYS. Now, HAL_GetTick counts the tick from the derived clock. So, it will go (in ms) off after certain time. right?. Could we correct such error.
My application requires precise timekeeping. I see similar issue in the RTC source clock. it's deviated from the actual frequency of 32768Hz. Is there any procedure to correct the deviation.If someone could point to any literature on how to do precise timekeeping in embedded systems considering different latencies and physical errors.