Closed M1cha closed 5 years ago
@cvinayak can you take a look at this one?
@M1cha if using synthesized LF clock, then HF clock needs to be persistent, i.e. an explicit clock_clock_on for HF clock needs to be called.
@cvinayak thanks for the tip, that seems to work. What's the proper way to do this though? enabling the HF clock from my main function and never disabling it doesn't sound very power-efficient.
@M1cha i just looked at schematic, you "shall" use LF RC, not synth. Its not very useful to use synth unless there are other requirements to keep HF clock always on.
you're totally right, using RC works just fine.
Describe the bug I bought an nrf52832 on aliexpress and am trying to run zephyr on it using the "nrf52_pca10040" config. schematics: https://ae01.alicdn.com/kf/HTB1kysEdhrI8KJjy0Fpq6z5hVXav.jpg?size=85239&height=783&width=1000&hash=374338387ec77f380a36ef738c15d7d8
A key difference is that the clock is connected to XC1/XC2 which is called
Synth
in the nrf52 sdk. That's why I have to changeNRFX_CLOCK_CONFIG_LF_SRC
to2
to successfully run the nordic examples.For zephyr I've done something similar by adding support for the synth clock(this diff also includes my config changes so you can see exactly what I did):
This way I can at least run zephyr and discover the device. The problem is that I can't start a pairing because zepyhr disconnects after a few seconds:
Expected behavior The device should successfully pair.
Environment (please complete the following information):