nrf5340 - netcore and cpuapp build and upload issue

RE: nrf5340 - netcore and cpuapp build and upload issue

Simonr — Thu, 06 May 2021 08:40:39 GMT

[quote user="Sunil vignesh"]and i have a question that is it possible to update the netcore in DFU OTA without affecting the application core[/quote]

This is no longer the same subject as your initial ticket, so I would appreciate it if you could create a new ticket for this question, as it will help others to keep each ticket on subject.

If you're happy flashing the network core using nRFConnect for Desktop that should be fine as well, but it should be possible flashing it using SES as well, but it's important to follow the guide step-by-step.

Best regards,

Simon

RE: nrf5340 - netcore and cpuapp build and upload issue

Sunil vignesh — Wed, 05 May 2021 06:26:51 GMT

Hi Simonr, Yes before flash the netcore. I am able to build the application core successful.. but i can't able to flash the netcore hex file from the segger studio. Instead of doing that i am able to flash the netcore hex file from nrf connect desktop. and after that i am able to flash the application core from the segger studio.

and i have a question that is it possible to update the netcore in DFU OTA without affecting the application core

RE: nrf5340 - netcore and cpuapp build and upload issue

Simonr — Wed, 05 May 2021 06:14:44 GMT

Hi Sunil

According to the "Programming the network sample from SES guide, you should first build an application onto the app core before trying to flash the hci_rpmsg_nrf5340_netcore application onto the network core. Are you able to do that successfully first? It seems like you're mixing these two processes together.

Best regards,

Simon

RE: nrf5340 - netcore and cpuapp build and upload issue

Sunil vignesh — Thu, 29 Apr 2021 15:54:19 GMT

Hi Simonr, Still i am getting the same error on uploading hci_rpmsg_nrf5340_netcore

I added the line CONFIG_BT_RPMSG_NRF53=y in prj.conf of peripheral_lbs

#
# Copyright (c) 2018 Nordic Semiconductor
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
CONFIG_NCS_SAMPLES_DEFAULTS=y

CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME="Nordic_Blinky"

CONFIG_BT_RPMSG_NRF53=y

# Enable the LBS service
CONFIG_BT_LBS=y
CONFIG_BT_LBS_POLL_BUTTON=y
CONFIG_DK_LIBRARY=y

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

Step I have followed

1. I have selected peripheral_lbs project and board nrf5340dk_nrf5340_cpuapp

2. Build the project. (without doing dfu setup - the build hex is creating merged.hex) why its creating merged.hex only for peripheral_lbs

3. I found merged_CPUNET.hex in

D:\nRF5xx\NCS\v1.5.0\nrf\samples\bluetooth\peripheral_lbs\build_nrf5340dk_nrf5340_cpuapp\hci_rpmsg\zephyr

4. I have created hci_rpmsg_nrf5340_netcore project file inside the current peripheral_lbs solution from this link https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf5340.html

5. loaded the path $(ProjectDir)/hci_rpmsg/zephyr/merged_CPUNET.hex as like same link

6. merged_CPUNET.hex file is uploading only by doing with nrfconnect desktop

after that i upload the zephyr/merged.hex from the segger and the project working in the nrf5340 board

My questions are.

1.why its creating merged.hex only for peripheral_lbs project?

2. Is merged_CPUNET.hex is different for different projects ?

3. nrf5340 DK creating 3 comports what are they?

RE: nrf5340 - netcore and cpuapp build and upload issue

Simonr — Thu, 29 Apr 2021 10:19:35 GMT

Hi Sunil

Yes, nrfjprog and west are command line tools.

There are examples for Flash storage and TWI in the Zephyr project, please check them out here.

Best regards,

Simon

RE: nrf5340 - netcore and cpuapp build and upload issue

Sunil vignesh — Wed, 28 Apr 2021 18:54:01 GMT

Hi Simonr,

Yeah i am new to nRF53 and NCS SDK

this nrfjprog or west are the CMD is it right?

and

[quote userid="75734" url="~/f/nordic-q-a/74511/nrf5340---netcore-and-cpuapp-build-and-upload-issue/307259#307259"]CONFIG_BT_RPMSG_NRF53 [/quote]

where we need to find These kind of configuration lines

Is there example code for writing

1. Data in flash storage for nRF53

2. TWI data sensing

RE: nrf5340 - netcore and cpuapp build and upload issue

Simonr — Wed, 28 Apr 2021 12:45:40 GMT

Hi Sunil

The Secure and nonsecure environments in the ARM Cortex-M33 processor of the nRF5340 is explained in detail in Part 2 | section 1.6 of our nRFConnect SDK tutorial.

In short, the nRF53 has two cores. The application core(appcore) and network core (netcore). Then, in the appcore you can choose whether to use a secure or non-secure environment for your application. In order to flash a BLE example onto the nRF5340 with SES, follow the Building and programming a sample, and make sure you set CONFIG_BT_RPMSG_NRF53 to y before programming the network sample from SES.

If you're new to the nRF53 and NCS environment, I think it's easier to use nrfjprog or west to flash this example onto the nRF53DK.

Best regards,

Simon