Error compiling peripheral_uart example in nRF Connect SDK

[Dave_couling]

I've recently put nRF Connect on my new machine, v1.7.0.  I wanted to test the peripheral_uart sample application.  However when I go to compile the peripheral_uart example I get the following error:

‘build’ in configuration ‘Common’
Combining ‘modules/nrf/samples/spm_subimage-prefix/src/spm_subimage-stamp/spm_subimage-build’
opening dependency file modules\nrfxlib\nrfxlib\nrf_security\src\mbedtls\CMakeFiles\mbedcrypto_base_vanilla.dir\C_\Nordic_Development\ncs\mbedtls\library\psa_crypto_slot_management.c.obj.d: No such file or directory
opening dependency file modules\nrfxlib\nrfxlib\nrf_security\src\mbedtls\CMakeFiles\mbedcrypto_base_vanilla.dir\C_\Nordic_Development\ncs\mbedtls\library\psa_crypto_driver_wrappers.c.obj.d: No such file or directory
Build failed

Is there a step that I've missed?

[Sigurd Hellesvik]

Hi

Could you try the steps listed in this blog post?

If I were to take a guess, I would say the error could be due the difference between secure and non-secure, which is mentioned in step 2 in the blog post

Regards,
Sigurd Hellesvik

[Dave_couling]

Unfortunately that blog does not address my issue

[Dave_couling]

HI,

I've tried following the instructions here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.7.1/nrf/ug_nrf5340.html#ug-nrf5340-ses-multi-image

However the file shown in the example at Load File to add the Network core image just doesn't not exist in my SDK.  There is no hci_rpmsg project, not is there a folder called such within the ProjectDir of my current project.  This is very puzzling what these instructions are trying to achieve?  Is my SDK missed a Network Sample project?

I did find a similarily name project in the /zephyr/sampes/bluetooth folder.  However the paths do not match the screen host at the above link.  This also doesn't seem to be solving my underlying issue which is that all nRF53 project simply do not compile.

Thanks,

DC

[Sigurd Hellesvik]

Hi

How committed are you to using Segger Embedded Studio?

It is a lot easier to work with nRF5340 using our Extension for VS Code.

However, we still support Segger Embedded Studio. So if you insist on using this, I will continue to assist you in solving your issue.

Regards,
Sigurd Hellesvik

[Dave_couling]

Hi Sigurd,

Unfortunately, I need to stick with SES until VS Code supports better debugging and disassembly

[Dave_couling]

I've also tried using VSCode in the past, but it refused to recognize the nRF Toolchains.  I always get a "This workspace requires version undefined of the nRF Connect toolchain, but it isnt installed..."   No matter what I've done, this is the case.  All tools are properly installed and added to the PATH.  Perhaps I need to wait for a new version to come out that fixes this?

[Sigurd Hellesvik]

Hi Dave,

Dave_couling said:

Unfortunately, I need to stick with SES

Fair enough, let us continue with Segger Embedded Studio then.

I have some good news, I have found the reason for your error.

Dave_couling said:

Unfortunately that blog does not address my issue

I thought you read through my blog, so I assumed that this was not the issue.

However, I set up and replicated your problem.
The build fail seems to be due to Step 3 from the blog here.

Sigurd Hellesvik said:

Could you try the steps listed in this blog post?

The part where you need to set up Segger Embedded Studio specifically to work with nRF5340 for multi-image builds might still apply though.
If you face problems with that later, please create a new post, to keep DevZone tidy.

Regards,
Sigurd Hellesvik