Custom board configuration causes runtime error, "E: Device id 00 00 00 does not match config ef 40 14"

[zsvtmml]

Our project was previously functional when we were developing using the nrf52840dk_nrf52840 with an overlay to reconfigure for our custom pcba. We created a custom board config using the "Create a new board" thing in  nRF Connect. After adding a bunch of apparently missing CONFIGs in <custom_pcba_name>_defconfig, and copying all the dts stuff over form zephyr/boads/arm/nrf52840dk_nrf52840 the project builds, but fails in runtime with following output to the console:

Our project was previously functional when we were developing using the nrf52840dk_nrf52840 with an overlay to reconfigure for our custom pcba. We created a custom board config using the "Create a new board" thing in  nRF Connect. After adding a bunch of apparently missing CONFIGs in <custom_pcba_name>_defconfig, and copying all the dts stuff over form zephyr/boads/arm/nrf52840dk_nrf52840 the project builds, but fails in runtime on a call to bt_enable, with following output to the console:

Our project was previously functional when we were developing using the nrf52840dk_nrf52840 with an overlay to reconfigure for our custom pcba. We created a custom board config using the "Create a new board" thing in  nRF Connect. After adding a bunch of apparently missing CONFIGs in <custom_pcba_name>_defconfig, and copying all the dts stuff over form zephyr/boads/arm/nrf52840dk_nrf52840 the project builds, but fails in runtime on a call to bt_enable, with following output to the console:

E: Device id 00 00 00 does not match config ef 40 14

Any help on how to fix this would me much appreciated.

Thank you.

[Susheel Nuguru]

Hi, I see that you have another thread created that says that you have issues initializing BLE. 

Are these two unrelated or you have solved this to move ahead to that issue?

[zsvtmml]

Hi Susheel,

Thank you for getting back.

This and the other case are related in that all of these runtime errors appears after we migrated the project to a custom pcba, rather than using an nrf52840dk_nrf52840 with overlay. So this case is definitely not resolved or superseded by the other (Case ID: 299733). I submitted this as a separate case because it is clear that bt_conn_cb_register and bt_enable are failing in the other instance, but I don't know what is throwing this Device id error.