From aecc7ccaf90e7cdf86c7a945d50b29eb8016a490 Mon Sep 17 00:00:00 2001 From: Nicolas Munnich <98408764+Nick-Munnich@users.noreply.github.com> Date: Tue, 13 Aug 2024 19:31:20 +0200 Subject: [PATCH] Update docs/docs/troubleshooting/connection-issues.mdx Co-authored-by: Cem Aksoylar <caksoylar@users.noreply.github.com> --- docs/docs/troubleshooting/connection-issues.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/troubleshooting/connection-issues.mdx b/docs/docs/troubleshooting/connection-issues.mdx index c14c3ba0..19d9f441 100644 --- a/docs/docs/troubleshooting/connection-issues.mdx +++ b/docs/docs/troubleshooting/connection-issues.mdx @@ -111,7 +111,7 @@ While you can find [documented workarounds](https://wiki.archlinux.org/title/blu ### Mitigating a Faulty Oscillator -Rarely, due to a manufacturing error, a device may have a faulty oscillator. This prevents it from functioning correctly wirelessly, and can be difficult to diagnose. Some microcontrollers, such as the `nRF52840`, allow for the usage of an internal oscillator instead of an external one. This results in increased power draw, but can be a solution if your device does indeed have a faulty oscillator. +Rarely, due to a manufacturing error, a device may have a faulty oscillator. This prevents it from functioning correctly wirelessly and can be difficult to diagnose. Some microcontrollers such as the `nRF52840` allow for the usage of an internal oscillator instead of an external one. This results in increased power draw but can be a solution if your device does indeed have a faulty oscillator. For the `nRF52840`, the flag to set to use the internal oscillator is: