pixo_replacement
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| pixo_replacement [2023/03/29 15:02] – [chrony tracking] millerjs | pixo_replacement [2024/11/14 02:30] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 27: | Line 27: | ||
| * http:// | * http:// | ||
| + | |||
| + | As far as I can tell, the Pi 2B through 3B+ all use this part, as well as a number of the A models. The Pi 4B uses two AEL crystals, one at 25MHz, the other at 54MHz. I have not yet experimented with replacing these parts. | ||
| ==== New TCXO ==== | ==== New TCXO ==== | ||
| Line 34: | Line 36: | ||
| ====== Quantifying Results ====== | ====== Quantifying Results ====== | ||
| + | There are a number of different methods for quantifying the results of this sort of modification. A few that I am exploring will be detailed below. | ||
| ==== chrony tracking ===== | ==== chrony tracking ===== | ||
| (Graphs coming eventually) | (Graphs coming eventually) | ||
| Line 55: | Line 57: | ||
| GPIO.cleanup() | GPIO.cleanup() | ||
| exit() | exit() | ||
| + | </ | ||
| + | |||
| + | ==== WiringPi GPIO_CLOCK ==== | ||
| + | The WiringPi toolset has a function to use the SoC's PLLs to generate a precise clock using the GPIO_CLOCK function. This can be initiated easily from the linux userspace by first setting the pin mode, then the output frequency. Only WiringPi Pin 7 (GPIO 4) supports this mode. | ||
| + | |||
| + | < | ||
| + | gpio mode 7 clock | ||
| + | gpio clock 7 1000000 # frequency in Hz | ||
| </ | </ | ||
pixo_replacement.1680102177.txt.gz · Last modified: 2024/11/14 02:30 (external edit)