I performed early software development on an nRF52840-DK. I'm using Zephyr on the nRF52840.
Now I have a custom board and started doing development on it by creating a .overlay file to change pin assignments, etc.
I then decided to create a custom board folder under my Project_folder/boards/arm to eliminate the dependence on the nRF52840-DK. I copied the contents of the nRF52840-DK board entries and renamed them to refer to the custom board, then edited the references to also refer to the custom board. Unused peripherals in the .dts have been marked as "disabled".
The project compiles and loads using the custom board specification, but BLE doesn't advertise. printk statements show that BLE gets initialized and the advertising is enabled, but the advertisements don't show up on LightBlue. Everything else seems to work the same as with the original nRF52840-DK .dts with .overlay file (and BLE advertises with them). Is there any peripheral specified by the .dts/.overlay that could affect the operation of the BLE radio? Is there something else in the board definition scheme that could affect BLE (or radio)?
Thanks!