RF Test on custom board (nrf5340 + nrf21540)

RE: RF Test on custom board (nrf5340 + nrf21540)

benoit.gorostidi — Thu, 21 Sep 2023 08:55:38 GMT

Device tree of my board provides 3 ACM ports. But in fact, 4 ports appears on host.

So, I removed all the ACM ports on my device tree and lets the conf/remote_shell/usb.dts enable 1 port.

  zephyr_udc0: &usbd {
 	 compatible = "nordic,nrf-usbd";
 	 status = "okay";
 
// 	 cdc_acm_uart0: cdc_acm_uart0 {
// 		 compatible = "zephyr,cdc-acm-uart";
// 	 };
 
// 	 cdc_acm_uart1: cdc_acm_uart1 {
// 		 compatible = "zephyr,cdc-acm-uart";
// 	 };

// 	 cdc_acm_uart2: cdc_acm_uart2 {
// 		compatible = "zephyr,cdc-acm-uart";
// 	 };
  };

After this change, only 1 port appears on host and "Direct Test Mode" desktop app can drive the cpunet.

Many thanks for your help.

RE: RF Test on custom board (nrf5340 + nrf21540)

Vidar Berg — Wed, 20 Sep 2023 12:03:25 GMT

Thanks for confirming, but then I don't understand how the nRF USB exposes multiple ACM ports. Have you tried to program the FW built for the 'nrf5340dk_nrf5340_cpunet' target to your custom board to see if that works? You can edit the board overlays if it is necessary to change the pinout.

VS Code settings for building the nRF5340 DK with FEM enabled and USB activated in the remote shell app:

[quote user="benoit.gorostidi"]I thought that Remote shell app was builded/flashed in the same time due to the CONFIG_NCS_SAMPLE_REMOTE_SHELL_CHILD_IMAGE[/quote]

Yes, it should. But the remote shell app should only expose one COM port on the nRF USB interface.

RE: RF Test on custom board (nrf5340 + nrf21540)

benoit.gorostidi — Tue, 19 Sep 2023 14:46:11 GMT

1. I use the native nRF USB interface.

2. Just flashing the Direct Test Mode app with VScode. I thought that Remote shell app was builded/flashed in the same time due to the CONFIG_NCS_SAMPLE_REMOTE_SHELL_CHILD_IMAGE option.Same process for nrF5340DK board work fine.

RE: RF Test on custom board (nrf5340 + nrf21540)

Vidar Berg — Tue, 19 Sep 2023 14:01:35 GMT

To help me better understand your setup, could you please answer the questions below?

1. Are you using the native nRF USB interface for USB ACM, or are you using an external UART-to-USB bridge?

2. Do you have the remote shell application programmed on the appcore?

RE: RF Test on custom board (nrf5340 + nrf21540)

benoit.gorostidi — Tue, 19 Sep 2023 12:32:18 GMT

DTM commands sended manualy doesn't have any effects on each of 4 ports.

RE: RF Test on custom board (nrf5340 + nrf21540)

Vidar Berg — Fri, 15 Sep 2023 12:44:31 GMT

Please try with a serial terminal such as Putty or similar, and see if you can send the DTM commands manually as explained in the sample documentation.

RE: RF Test on custom board (nrf5340 + nrf21540)

benoit.gorostidi — Fri, 15 Sep 2023 08:19:22 GMT

Thanks for the modified version of the project. I'm now able to build and flash the project.

In our app, custom board provides 3 virtual serial ports through USB ACM, but with "Direct test mode" app, 4 serial ports are available. Direct Test Mode desktop app detect "Nordic Remote Shell sample" device but cannot communicate with none of the 4 ports.

RE: RF Test on custom board (nrf5340 + nrf21540)

Vidar Berg — Wed, 13 Sep 2023 09:46:27 GMT

Sorry, I did not notice your attachment earlier. Please try the modified version of your project included below and see if that works for you.

devzone.nordicsemi.com/.../8524.direct_5F00_test_5F00_mode.zip

diff --git a/boards/arm/erl_nrf5340/Kconfig.board b/boards/arm/erl_nrf5340/Kconfig.board
index acca550..0566ae9 100644
--- a/boards/arm/erl_nrf5340/Kconfig.board
+++ b/boards/arm/erl_nrf5340/Kconfig.board
@@ -13,6 +13,6 @@ config BOARD_ERL_NRF5340_CPUAPP_NS
 
 endif # SOC_NRF5340_CPUAPP_QKAA
 
-config BOARD_ERL_NRF5340_CPUAPP_CPUNET
+config BOARD_ERL_NRF5340_CPUNET
 	bool "ERL NRF5340 Network MCU"
 	depends on SOC_NRF5340_CPUNET_QKAA
diff --git a/boards/arm/erl_nrf5340/Kconfig.defconfig b/boards/arm/erl_nrf5340/Kconfig.defconfig
index 974e5e0..f87f923 100644
--- a/boards/arm/erl_nrf5340/Kconfig.defconfig
+++ b/boards/arm/erl_nrf5340/Kconfig.defconfig
@@ -74,7 +74,7 @@ endif # BOARD_ERL_NRF5340_CPUAPP_NS
 endif # BOARD_ERL_NRF5340_CPUAPP || BOARD_ERL_NRF5340_CPUAPP_NS
 
 config BOARD
-	default "erl_nrf5340_cpunet" if BOARD_ERL_NRF5340_CPUAPP_CPUNET
+	default "erl_nrf5340_cpunet" if BOARD_ERL_NRF5340_CPUNET
 
 config MBOX_NRFX_IPC
 	default MBOX
@@ -90,9 +90,9 @@ config HEAP_MEM_POOL_SIZE
 
 endif #  BOARD_ERL_NRF5340_CPUAPP || BOARD_ERL_NRF5340_CPUAPP_NS
 
-if BOARD_ERL_NRF5340_CPUAPP_CPUNET
+if BOARD_ERL_NRF5340_CPUNET
 
 config BT_CTLR
 	default y if BT
 
-endif # BOARD_ERL_NRF5340_CPUAPP_CPUNET
+endif # BOARD_ERL_NRF5340_CPUNET
diff --git a/boards/arm/erl_nrf5340/erl_nrf5340_cpunet_defconfig b/boards/arm/erl_nrf5340/erl_nrf5340_cpunet_defconfig
index 6228a45..a2dae95 100644
--- a/boards/arm/erl_nrf5340/erl_nrf5340_cpunet_defconfig
+++ b/boards/arm/erl_nrf5340/erl_nrf5340_cpunet_defconfig
@@ -2,7 +2,7 @@
 
 CONFIG_SOC_SERIES_NRF53X=y
 CONFIG_SOC_NRF5340_CPUNET_QKAA=y
-CONFIG_BOARD_ERL_NRF5340_CPUAPP_CPUNET=y
+CONFIG_BOARD_ERL_NRF5340_CPUNET=y
 
 # Enable MPU
 CONFIG_ARM_MPU=y
diff --git a/boards/erl_nrf5340_cpunet.overlay b/boards/erl_nrf5340_cpunet.overlay
index e218494..c289448 100644
--- a/boards/erl_nrf5340_cpunet.overlay
+++ b/boards/erl_nrf5340_cpunet.overlay
@@ -10,4 +10,8 @@
 	ipc = <&ipc0>;
 	ept-name = "remote shell";
 	current-speed = <19200>;
-};
\ No newline at end of file
+};
+
+&radio {
+	/delete-property/ dfe-supported;
+};

RE: RF Test on custom board (nrf5340 + nrf21540)

benoit.gorostidi — Wed, 13 Sep 2023 07:36:56 GMT

You can found it in the zip file uploaded in my first message. Let me know if you cannot access to the file.

RE: RF Test on custom board (nrf5340 + nrf21540)

Vidar Berg — Wed, 13 Sep 2023 07:28:13 GMT

Can you upload your .config file here?

RE: RF Test on custom board (nrf5340 + nrf21540)

benoit.gorostidi — Wed, 13 Sep 2023 07:13:48 GMT

Actualy, DOMAIN_CPUAPP_BOARD symbol is not taken into account in the .config file.

Kconfig content:

# ERL board configuration

if BOARD_ERL_NRF5340_CPUAPP || BOARD_ERL_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 "erl_nrf5340_cpunet"
	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_ERL_NRF5340_CPUAPP || BOARD_ERL_NRF5340_CPUAPP_NS

config DOMAIN_CPUAPP_BOARD
	string
	default "erl_nrf5340_cpuapp"
	depends on BOARD_ERL_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.

RE: RF Test on custom board (nrf5340 + nrf21540)

Vidar Berg — Tue, 12 Sep 2023 08:31:20 GMT

Hi,

Please check what the DOMAIN_CPUAPP_BOARD symbol is set to in your .config output file.

RE: RF Test on custom board (nrf5340 + nrf21540)

benoit.gorostidi — Tue, 12 Sep 2023 07:37:38 GMT

Hi,

I've double checked the Kconfig and the DOMAIN_CPUAPP_BOARD is well defined with the board name.

RE: RF Test on custom board (nrf5340 + nrf21540)

Vidar Berg — Thu, 07 Sep 2023 11:11:04 GMT

Hi,

It looks like your custom board does not define the DOMAIN_CPUAPP_BOARD symbol. Please try adding it to the Kconfig file in your board directory like how we've done it for the nRF5340DK here: https://github.com/nrfconnect/sdk-zephyr/blob/c7094146b5b47fd4da05ed773e0128e2e6a634e1/boards/arm/nrf5340dk_nrf5340/Kconfig#L51. Note that the string should reflect the name of your board.

Best regards,

Vidar