Building sample "nrf/sample/zigbee/light_bulb" gives compiler error!

[Elevation]

Hello,

I have been using NRF Connect SDK 1.6.1 with Microbit V2 to run some zigbee projects! Now when I should build some new firmwares I upgraded to SDK 1.7.1 and after that the sample gives the error below! 

CMake Error at C:\Dev\Nrf\sdk\v1.7.1\nrf\drivers\mpsl\temp_nrf5\CMakeLists.txt:12 (message):
CONFIG_TEMP_NRF5 and CONFIG_TEMP_NRF5_MPSL have both been enabled, but must
not be used together.

I have driled it down to that it seems to be the clock control needed for Microbit that gives the error! 

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_250PPM=y

Any suggestions on how to proceed? An easy way to reproduce this error is to add the above compiler directive to ..\v1.7.1\zephyr\boards\arm\nrf52833dk_nrf52833\nrf52833dk_nrf52833_defconfig and build for that board.

[Simonr]

Hi

Thank you for reporting this issue, we're currently looking into it. We've made an internal ticket on this and I'll keep you updated on any progress. Don't hesitate to provide any more information you might think is useful.

Best regards,

Simon

[Axel Schlueter]

+1 on this, I ran into exactly the same problem today with a custom BT840 board using OpenThread without an external 32kHz crystal. My temporary solution is to configure CONFIG_CLOCK_CONTROL_NRF_CALIBRATION_MAX_SKIP=0, which seems to work for now (though admittedly I don't fully understand the potential impact yet).

[Simonr]

Hi

Our first thought was that using CONFIG_TEMP_NRF5_MPSL would solve this, but CONFIG_TEMP_NRF5 is selected by other symbols. There is a fix for this in upstream Zephyr: https://github.com/zephyrproject-rtos/zephyr/pull/39313/files. It will likely find its way into a future release of the nRF Connect SDK.

Best regards,

Simon

PS: Great timing Axel Schlueter!