Enable SOC_NRF54H20_CPURAD_ENABLE and SOC_NRF53_CPUNET_ENABLE by defa… #3027
Conversation
…ult for BLE samples At the moment these configs should be selected explicitly for each sample. Apply them by default as these configs enable the clock for radio (network) core during application boot time and requests power for radio (network) core. Once powered, radio (network) core begins executing instructions. Signed-off-by: Mirlenko, Aleksandr <[email protected]>
| config SOC_NRF53_CPUNET_ENABLE | ||
| bool "NRF53 Network MCU is enabled at boot time" | ||
| default y if NRF_802154_SER_HOST | ||
| default y if NRF_802154_SER_HOST || BT |
There was a problem hiding this comment.
rather than no-up here, put these in nrf/soc/nordic/nrf5* folders (can just make a Kconfig.defconfig and put e.g.
config SOC_NRF53_CPUNET_ENABLE
default y if BT
)
| config SOC_NRF53_CPUNET_ENABLE | ||
| bool "NRF53 Network MCU is enabled at boot time" | ||
| default y if NRF_802154_SER_HOST | ||
| default y if NRF_802154_SER_HOST || BT |
There was a problem hiding this comment.
I would assume this change is not needed? We previously didn't need to set SOC_NRF53_CPUNET_ENABLE for Bluetooth applications
There was a problem hiding this comment.
I had a talk with @SebastianBoe , and he suggested to keep SOC_NRF53_CPUNET_ENABLE and SOC_NRF54H20_CPURAD_ENABLE consistent.
There was a problem hiding this comment.
If we are observing that 54H needs to set this for BT applications, but 53 for some reason does not, then
I would also support having 54H copy whatever 53 is doing at the moment.
As long as there is no unnecessary divergence between 53 and 54 I am happy :)
4 participants
…ult for BLE samples
At the moment these configs should be selected explicitly for each sample. Apply them by default as these configs enable the clock for radio (network) core during application boot time and requests power for radio (network) core. Once powered, radio (network) core begins executing instructions.