nrf5340DK with nrf21540EK build and config issue.

[Tommy_Li]

Dear Nordic Team,

We have tested that the nrf5340DK borad was ok for the broadcast audio source role.

We want to add the nrf21540EK FEM borad on it to test the max broadcast distance.

Although the nrf21540EK board is still on its way to us, we would like to do some work in advance.

 

The picture above depicts that we should use the command below to compile our code.

west build -b nrf5340dk/nrf5340/cpuapp -- -DSHIELD=nrf21540ek_fwd -Dmultiprotocol_rpmsg_SHIELD=nrf21540ek

And the Note part also said that for the nRF53 devices SPIM0 and UART0 are mutually exclusive on the network core.

So we must disable the UART0 node in the network core's devicetree file.

My question is how to disable the uart0 on the network core by using the overlay file.

I can disable the uart0 on the application core by using nrf5340dk_nrf5340_cpuapp.overlay.

But I can't disable the uart0 on the network core by using nrf5340dk_nrf5340_cpunet.overlay.

From the compile log, It didn't recognize nrf5340dk_nrf5340_cpunet.overlay.

Best Regards.

Tommy.

[Edvin]

Hello Tommy,

The reason the network core is not affected by the nrf5340dk_nrf5340_cpunet.overlay is that the networ core's application is configured via the child_image folder.

Depending on what NCS version that you are using, the child image is called either hci_ipc.conf or hci_rpmsg.conf, found in the child_image folder in your application folder. (hci_ipc.conf for ncs v2.6.0 and later, hci_rpmsg.conf for older).

If you want to add an overlay file, you can add a folder called "boards" in your application folder. In there you can place the file nrf5340dk_nrf5340_cpunet.overlay.

Then you can delete your build folder, and generate a new build configuration, to be sure that the compiler picks up the overlay files and configurations.

Best regards,

Edvin