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
As mentioned on #4 we have a way to assess the XTAL accuracy by performing a calibration process, and logging the results.
I have/am writing scripts to automate this process and previously noted that a unit could settle on calibration values which differ by 1 unit - which represents 1/256 fractional division of the CPU clock.
I previously though that this was a set-up issue (ie only at start), but now I have a couple of logs where the calibration value changes during the process to 'jump' between the two values. This suggests that there is something wrong with the way the code monitors/tracks the input (from UltraSync)...
and
Note: Multiple units monitoring the same input signal, so I don't think that this is the UltraSync glitching.
The text was updated successfully, but these errors were encountered:
As mentioned on #4 we have a way to assess the XTAL accuracy by performing a calibration process, and logging the results.
I have/am writing scripts to automate this process and previously noted that a unit could settle on calibration values which differ by 1 unit - which represents 1/256 fractional division of the CPU clock.
I previously though that this was a set-up issue (ie only at start), but now I have a couple of logs where the calibration value changes during the process to 'jump' between the two values. This suggests that there is something wrong with the way the code monitors/tracks the input (from UltraSync)...
and
Note: Multiple units monitoring the same input signal, so I don't think that this is the UltraSync glitching.
The text was updated successfully, but these errors were encountered: