nrf_clock_lf_cfg_t for SYNTH operation

[RK]

I don't have a 32KHz crystal on my board (using the stock Rigado module) and power isn't an issue as the board is mains powered in operation, so I was intending on using the HF SYNTH for the LF clock.

I've just moved to the latest S130/S132 V2 which uses the nrf_clock_lf_cfg_t structure for configuring ble, for SYNTH operation do I have to provide a xtal_accuracy field and if so should it be

1. the accuracy of the actual 16MHz crystal (which I'll have to ask Rigado but I assume is better than 50ppm)

or

2. The default (0) 250ppm which matches the old SDK's NRF_CLOCK_LFCLKSRC_SYNTH_250_PPM, which was the only SYNTH source available?

or is SYNTH not really recommended and I should use the RC source with frequent calibration? I don't really mind, I'll take whatever gives the most stable BLE performance.

[Luis]

A few weeks ago we were told at the Nordic MyPage support to use the SYNTH option instead of the internal RC one, because at our application the HF clock is always ON, then they said there were no drawbacks about using SYNTH option, and we would get a better accuracy than using the RC option. Now the answer above says SYNTH is not recommended... I am confused.

Would the correct statement be: "NRF_CLOCK_LF_SRC_SYNTH is not recommended unless your application is using the HF clock non stop or you don't care about power consumption"?