nRF5340 DK: application on both application-core and network-core

RE: nRF5340 DK: application on both application-core and network-core

Yanpengwu — Tue, 14 Nov 2023 09:26:16 GMT

Hi Hung,

Thank you very much for your reply and guidance. You are right, the sample 'multicore hello_world sample' is the right starting point for multi-core application. In the sample, use 'sysbuild' to build images for two cores.
I tried it and it works. Thank you very much!

RE: nRF5340 DK: application on both application-core and network-core

Hung Bui — Mon, 13 Nov 2023 15:32:01 GMT

Please take a look at the multicore hello_world sample, I think it's more relevant.

I don't think developing on the empty_app_core would be a good idea. The main job of the empty app core is to turn off everything and let the netcore handles the GPIO.

RE: nRF5340 DK: application on both application-core and network-core

Yanpengwu — Mon, 13 Nov 2023 15:17:09 GMT

Hi,

Thanks for the reply. I checked these two options and found CONFIG_SERIAL=y was set in the board default conf(C:\ncs\v2.5.0\zephyr\boards\arm\nrf5340dk_nrf5340\nrf5340dk_nrf5340_cpuapp_defconfig), and CONFIG_PRINTK=y was set in prj.conf already. But it did not work.

Could you help run the sample 'empty_app_core' on a nRF5340 DK and add some log info in the application-core main()? I tried many ways today, with printk,printf, zephyr logging on RTT and COM consoles, but not find the right way.

Thank you very much.

RE: nRF5340 DK: application on both application-core and network-core

Hung Bui — Mon, 13 Nov 2023 15:06:03 GMT

Hi,
You may want to enable
CONFIG_PRINTK=y

CONFIG_SERIAL=y

to be able to print serial log.
I would suggest to take a look at the \nrf\samples\multicore\hello_world sample to see how you can build an application for multi cores.

Or if you simply want the empty_app_core , you can include

CONFIG_NCS_SAMPLE_EMPTY_APP_CORE_CHILD_IMAGE=y
in the netcore application to have it as the child image.

RE: nRF5340 DK: application on both application-core and network-core

Yanpengwu — Mon, 13 Nov 2023 12:53:10 GMT

Hi again,

In the sample 'empty_app_core', I doubt the log of printk in the main() can't be printed because of the setting in the prj.conf.

Below is the setting of prj.conf in 'empty_app_core':

#-------------------------------------------------------------------------------------
# Copyright (c) 2020 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
CONFIG_MULTITHREADING=n
CONFIG_KERNEL_MEM_POOL=n
CONFIG_NUM_PREEMPT_PRIORITIES=0
CONFIG_SYS_CLOCK_EXISTS=n
CONFIG_ARM_MPU=n
CONFIG_SIZE_OPTIMIZATIONS=y
CONFIG_I2C=n
CONFIG_WATCHDOG=n
CONFIG_GPIO=n
CONFIG_SPI=n
CONFIG_SERIAL=n
CONFIG_FLASH=n
CONFIG_DYNAMIC_INTERRUPTS=n
CONFIG_IRQ_OFFLOAD=n
CONFIG_THREAD_STACK_INFO=n
CONFIG_THREAD_CUSTOM_DATA=n
CONFIG_BOOT_BANNER=n
CONFIG_BOOT_DELAY=0
CONFIG_CONSOLE=n
CONFIG_UART_CONSOLE=n
CONFIG_STDOUT_CONSOLE=n
CONFIG_PRINTK=n
CONFIG_EARLY_CONSOLE=n
CONFIG_BOARD_ENABLE_CPUNET=y

#-------------------------------------------------------------------------------------

But after I changed the settings of console to 'y' as below, the log still can't be seen.

CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y
CONFIG_STDOUT_CONSOLE=y
CONFIG_PRINTK=y
CONFIG_EARLY_CONSOLE=y

RE: nRF5340 DK: application on both application-core and network-core

Yanpengwu — Mon, 13 Nov 2023 11:10:02 GMT

Hi again,

In the sample 'system_off', I can see the log from the application core with printk in the main function.

But in the sample 'empty_app_core', after I added some printk in the main function, there was no log from the application core. Could you tell me what's the reason for this difference? In this sample, I programmed Zephyr’s Blinky sample to the network core and the led blink works.

Thank you very much.