RE: Custom Board Network Core Firmware Issue

Hakon — Fri, 04 Aug 2023 11:23:54 GMT

This seems like a separate issue. Do you mind creating a new ticket for this?

RE: Custom Board Network Core Firmware Issue

hugzy123 — Wed, 02 Aug 2023 09:48:15 GMT

We have managed to fix most of the issues with the nrf53 custom board now and can now successfully run the ipc service. However, we are still having an issue running our custom board type on our pcb.

Our PCB does not have an external LFCLK so we need to set the application to use the internal LFCLK. Setting just CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y on its own does not work, the sensor fails to boot, so we need to use the workaround suggested here. However, when we set CONFIG_CLOCK_CONTROL_NRF_K32SRC_SYNTH=y, the build gets the value CONFIG_CLOCK_CONTROL_NRF_K32SRC_SYNTH=n and we don't know why.

What can we do to see why we're getting CONFIG_CLOCK_CONTROL_NRF_K32SRC_SYNTH=n in our build files? All dependencies are being met. We're using the network core image "multiprotocol_rpmsg_subimage".

Thanks

RE: Custom Board Network Core Firmware Issue

hugzy123 — Mon, 31 Jul 2023 10:16:02 GMT

I tried to build the ipc_service sample but the compilation failed for my custom boards with the following error;

It compiled ok for the nrf53 DK.

It's looking for a .conf file which is created successfully when using the dk but not when I use my custom board. The error mentions a possible issue with the kconfig file for my custom board, so I have included the contents below in case you can spot something;

# nRF5340 DK board configuration

# Copyright (c) 2019 - 2021 Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0

if BOARD_S_COMBO_BOARDS || BOARD_NRF5340DK_NRF5340_CPUAPP_NS

config BOARD_ENABLE_DCDC_APP
	bool "Application MCU DCDC converter"
	select SOC_DCDC_NRF53X_APP
	default y

config BOARD_ENABLE_DCDC_NET
	bool "Network MCU DCDC converter"
	select SOC_DCDC_NRF53X_NET
	default y

config BOARD_ENABLE_DCDC_HV
	bool "High Voltage DCDC converter"
	select SOC_DCDC_NRF53X_HV
	default y

config BOARD_ENABLE_CPUNET
	bool "NRF53 Network MCU"
	select SOC_NRF_GPIO_FORWARDER_FOR_NRF5340 if \
		$(dt_compat_enabled,$(DT_COMPAT_NORDIC_NRF_GPIO_FORWARDER))
	help
	  This option enables releasing the Network 'force off' signal, which
	  as a consequence will power up the Network MCU during system boot.
	  Additionally, the option allocates GPIO pins that will be used by UARTE
	  of the Network MCU.
	  Note: GPIO pin allocation can only be configured by the secure Application
	  MCU firmware, so when this option is used with the non-secure version of
	  the board, the application needs to take into consideration, that the
	  secure firmware image must already have configured GPIO allocation for the
	  Network MCU.
	default y if (BT || NRF_802154_SER_HOST)

config DOMAIN_CPUNET_BOARD
	string
	default "s_combo_boards_net"
	depends on BOARD_ENABLE_CPUNET
	help
	  The board which will be used for CPUNET domain when creating a multi
	  image application where one or more images should be located on
	  another board. For example hci_rpmsg on the nRF5340_cpunet for
	  Bluetooth applications.

endif #  BOARD_S_COMBO_BOARDS || BOARD_NRF5340DK_NRF5340_CPUAPP_NS

config DOMAIN_CPUAPP_BOARD
	string
	default "s_combo_boards"
	depends on BOARD_NRF5340DK_NRF5340_CPUNET
	help
	  The board which will be used for CPUAPP domain when creating a multi
	  image application where one or more images should be located on
	  another board.

Are there any simple custom board examples which use the nRF53 chipset?

RE: Custom Board Network Core Firmware Issue

Hakon — Fri, 28 Jul 2023 11:58:09 GMT

Hello,

you can check this sample, see if you are able to run this.