Porting source code from nRF52832 single core to nRF5340 dual core

RE: Porting source code from nRF52832 single core to nRF5340 dual core

Hieu — Mon, 10 Jul 2023 06:38:17 GMT

No problem. If you don't have any other questions on this topic, please feel free to close this case at your convenience.

RE: Porting source code from nRF52832 single core to nRF5340 dual core

snowuyl — Sat, 08 Jul 2023 01:18:25 GMT

Thanks for your reply!

RE: Porting source code from nRF52832 single core to nRF5340 dual core

Hieu — Fri, 07 Jul 2023 16:15:10 GMT

In BLE sample, most often the application for the Network Core is built from the HCI RPMsg sample as a child image. As mentioned before, please try to go over the Working with the nRF53 Series guides. It will explain most concepts that are important for beginner and save you much effort.

RE: Porting source code from nRF52832 single core to nRF5340 dual core

snowuyl — Fri, 07 Jul 2023 07:47:27 GMT

devzone.nordicsemi.com/.../3731.minimal_5F00_log_5F00_nus.zip

RE: Porting source code from nRF52832 single core to nRF5340 dual core

snowuyl — Fri, 07 Jul 2023 07:47:11 GMT

Thanks for your reply! minimal_log_nus.zip is sample for NUS sending data to iOS Nordic toolbox APP. And I follow below procedure to build and flash image. But I didn't write any code for Network Core. Did I miss something for nRF5340 development?

1. Unzipping minimal_log_nus.zip
2. cd minimal_log_nus
3. west build -b nrf5340dk_nrf5340_cpuapp
4. west flash

RE: Porting source code from nRF52832 single core to nRF5340 dual core

Hieu — Thu, 06 Jul 2023 22:35:31 GMT

I have a feeling you might be expecting to use have one application running on both cores of the nRF5340 to improve performance. Please be informed that it is not the intended purpose of the dual core design on the nRF5340.

On the nRF5340, the cores are named Application Core and Network Core. As the names suggested, they are designed to handle jobs specific to the application and networking, respectively.

For example, for most if not all of our BLE samples, only the BLE Controller runs on the Network Core. The BLE Host and the application runs on the Application Core.

Thus, for the most part, you don't need API changes. In detail though, it is hard to say whether there is any change in API necessary or not without in-depth knowledge of your application. I am afraid this will have to be an exploring process for you.

For an example of no change needed, the BLE Beacon sample.

For an example of changes needed, the nrfx HAL API for the RESETREAS register changed (nRF52 vs nRF53), because the location of the register changed.

I recommend you go over our Working with the nRF53 Series guides and then run a few basic BLE samples to get a feeling of things.

RE: Porting source code from nRF52832 single core to nRF5340 dual core

snowuyl — Thu, 06 Jul 2023 01:39:16 GMT

Thanks for your reply! I am using Ncs v2.3.0 for nRF52832 and nRF5340. Do I need to do api change for nRF5340? Besides, which sample code do you suggest for new comer of nRF5340?

RE: Porting source code from nRF52832 single core to nRF5340 dual core

Susheel Nuguru — Wed, 05 Jul 2023 18:04:22 GMT

That depends on many things.

If you are using nRF Connect SDK (NCS) on nRF52832 aswell, and assuming that you want to port application to NCS of the same version you were using, then most of the source code remains similar on the code for nRF5340 but you need to change some settings for splitting the controller and host on two different cores.
If your application on nRF52832 was made on older version of NCS and you want to port to a newer version of NCS for nRF5340, then there might be API changes.
If you were using nRF5SDK on nRF52840, then you need to move to NCS for nRF5340 and that is a whole different beast of porting effort that needs considerable architectural changes along with a lot of changes in your application to adapt to new API.