kb01/zmk
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

prettier

Browse source
This commit is contained in:
Nicolas Munnich 2024-08-11 15:45:19 +02:00
parent 5db97a0d30
commit d274aab26c
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/docs/troubleshooting/connection-issues.mdx
View file

@ -114,9 +114,11 @@ While you can find [documented workarounds](https://wiki.archlinux.org/title/blu
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:
```
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
```
Other microcontrollers may have similar configuration options [found in the Zephyr documentation](https://docs.zephyrproject.org/3.5.0/search.html?q=CONFIG_CLOCK_CONTROL&check_keywords=yes&area=default). Do note that not all microcontrollers allow for the use of an internal oscillator, though.
## Issues While Connected
@ -162,4 +164,4 @@ If this doesn't help, try following the procedure above but replace step 3 with
- Restart the Windows device
- Open "Device Manager," turn on "Show hidden devices" from the "View" menu, then find and delete the keyboard under the "Bluetooth" item
Some Windows devices may also require passkey entry, described under ["Unable to Connect to Device"](#unable-to-connect-to-device).
Some Windows devices may also require passkey entry, described under ["Unable to Connect to Device"](#unable-to-connect-to-device).