Closed thedjnK closed 3 years ago
If doing it afresh not on an existing module, also do ninja menuconfig
to get the infinite loop
You are using NCS which handles partition management differently from upstream zephyr. Please see https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/scripts/partition_manager/partition_manager.html for details on how to specify the flash partitions you want. In general, only those needed should be included by default. Run ninja partition_manager_report
to see what is currently included.
Although @hakonfam is correct about this belonging in NCS and not upstream Zephyr, then I have tested this out as well, as there should not something causing an infinite CMake loop with Zephyr.
I have tried with the NCS bluetooth sample peripheral_lbs
, but CMake executed as expected on Windows.
No looping.
But I had to adjust the test.overlay
to:
/delete-node/ &slot1_partition;
/delete-node/ &scratch_partition;
because otherwise I would get: Label or path lfs_partition not found
Could you provide some more details on how to reproduce ?
Closing since it is not reproduceable. @thedjnK please reopen this if you have a way of helping us reproduce this.
Describe the bug A project for the nRF5340 was configured with an overlay file and it entered an infinite loop of configuring the CPU core over and over and over and over again. This was tested using nRF connect SDK so it could be an issue in that rather than zephyr, I have done no investigation into the cause of the issue.
To Reproduce Steps to reproduce the behavior:
Expected behavior The configuration to complete
Impact Showstopper
Logs and console output
Environment (please complete the following information):