nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

RE: nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

Kazi Afroza Sultana — Tue, 07 Nov 2023 08:09:02 GMT

I am Sorry for the delayed response. nrfx_spim_xfer() function is from nrfx APIs for SPIM. My colleague has answered also briefly. I hope that helps.

RE: nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

AKV — Tue, 07 Nov 2023 07:06:42 GMT

Thanks for the response.

RE: nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

Hieu — Mon, 06 Nov 2023 14:48:38 GMT

Hi AKV,

[quote userid="73768" url="~/f/nordic-q-a/104169/nrf52840-custom-board-pin-mapping-change-in-nrf-connect-sdk-v2-2-0/452868"]

1. We don't need to write/read by suing SPI API nrfx_spim_xfer(&spim_inst, &spim_xfer_desc_tx_rx, 0)?

If we enable the CONFIG_MPSL_FEM_NRF21540_GPIO_SPI=y Then the function bt_hci_cmd_send_sync() will Internally doing the SPI read/write right?

[/quote]

You are right that you don't need to directly control the FEM via SPI. It might actually be difficult even if you want to, because when you use CONFIG_MPSL_FEM_NRF21540_GPIO_SPI, the Multiprotocol Service Layer (MPSL) controls the SPI communication with the FEM.

Technically, the function bt_hci_cmd_send_sync() does not actually perform the any SPI read/write. The function itself just sends a command to our SoftDevice Controller, of which MPSL is a component.

Since you referred to this case, I think you have read over it. However, I just want to reiterate here that MPSL does not actually give you full range of gain. By default, it uses model, which will control the nRF SoC Radio and the FEM to achieve 0, 10, and 20 dB. Links about the details are available in that post.

I see that this case is originally about pin mapping. I suggest that we keep the discussion here focused on that. If you have further questions about FEM control, please open a new case.

Hieu

RE: nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

AKV — Mon, 06 Nov 2023 12:10:19 GMT

Kazi Afroza Sultana Can you please respond?

RE: nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

AKV — Sat, 28 Oct 2023 11:01:02 GMT

Hi,

I was able to control the gain by using the below code. And also getting the value as per this discussion nRF21540 SPI Gain Dynamic Control

void set_tx_power(uint8_t handle_type, uint16_t handle, int8_t tx_pwr_lvl)
{
	struct bt_hci_cp_vs_write_tx_power_level *cp;
	struct bt_hci_rp_vs_write_tx_power_level *rp;
	struct net_buf *buf, *rsp = NULL;
	int err;

	buf = bt_hci_cmd_create(BT_HCI_OP_VS_WRITE_TX_POWER_LEVEL, sizeof(*cp));
	if(!buf) {
		__ASSERT_NO_MSG(false);
		return;
	}

	cp = net_buf_add(buf, sizeof(*cp));
	cp->handle = sys_cpu_to_le16(handle);
	cp->handle_type = handle_type;
	cp->tx_power_level = tx_pwr_lvl;

	err = bt_hci_cmd_send_sync(BT_HCI_OP_VS_WRITE_TX_POWER_LEVEL, buf, &rsp);
	if(err) {
		uint8_t reason =
			rsp ? ((struct bt_hci_rp_vs_write_tx_power_level *)rsp->data)->status : 0;
		__ASSERT(false, "Set Tx power err: %d reason 0x%02x\n", err, reason);
		return;
	}

	k_sleep(K_MSEC(100));
	int8_t gain = 0;
	mpsl_fem_pa_is_configured(&gain);

	rp = (void *)rsp->data;
	LOG_INF("New Tx Power: %d (Gain: %d)", rp->selected_tx_power, gain);

	net_buf_unref(rsp);
}
void get_tx_power(uint8_t handle_type, uint16_t handle, int8_t *tx_pwr_lvl)
{
	struct bt_hci_cp_vs_read_tx_power_level *cp;
	struct bt_hci_rp_vs_read_tx_power_level *rp;
	struct net_buf *buf, *rsp = NULL;
	int err;

	*tx_pwr_lvl = 0xFF;
	buf = bt_hci_cmd_create(BT_HCI_OP_VS_READ_TX_POWER_LEVEL,
				sizeof(*cp));
	if (!buf) {
		printk("Unable to allocate command buffer\n");
		return;
	}

	cp = net_buf_add(buf, sizeof(*cp));
	cp->handle = sys_cpu_to_le16(handle);
	cp->handle_type = handle_type;

	err = bt_hci_cmd_send_sync(BT_HCI_OP_VS_READ_TX_POWER_LEVEL,
				   buf, &rsp);
	if (err) {
		uint8_t reason = rsp ?
			((struct bt_hci_rp_vs_read_tx_power_level *)
			  rsp->data)->status : 0;
		printk("Read Tx power err: %d reason 0x%02x\n", err, reason);
		return;
	}

	rp = (void *)rsp->data;
	*tx_pwr_lvl = rp->tx_power_level;

	net_buf_unref(rsp);
}

1. We don't need to write/read by suing SPI API nrfx_spim_xfer(&spim_inst, &spim_xfer_desc_tx_rx, 0)?

If we enable the CONFIG_MPSL_FEM_NRF21540_GPIO_SPI=y Then the function bt_hci_cmd_send_sync() will Internally doing the SPI read/write right?

RE: nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

Kazi Afroza Sultana — Fri, 27 Oct 2023 15:41:51 GMT

Hello,

It's good to hear that you have increased power.

Maybe you can read this https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.3.0/nrf/app_dev/working_with_fem/index.html#id18 to know about nRF21540 GPIO+SPI built-in power model?

RE: nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

AKV — Fri, 20 Oct 2023 10:27:44 GMT

Hi,

nrf_radio_fem: nrf21540_fem {
		compatible = "nordic,nrf21540-fem";
		tx-en-gpios = <&gpio1 10 GPIO_ACTIVE_HIGH>;
		rx-en-gpios = <&gpio1 13 GPIO_ACTIVE_HIGH>;
		pdn-gpios   = <&gpio1 02 GPIO_ACTIVE_HIGH>;
		mode-gpios  = <&gpio0 29 GPIO_ACTIVE_HIGH>;
		ant-sel-gpios = < &gpio0 02 GPIO_ACTIVE_HIGH >;
		spi-if = <&nrf_radio_fem_spi>;		
	};	
	
	fem_spi: &spi1 {
	status = "okay";
	pinctrl-0 = <&spi1_default>;
	pinctrl-1 = <&spi1_sleep>;
	pinctrl-names = "default", "sleep";
	cs-gpios = <&gpio0 21 GPIO_ACTIVE_LOW>;
 
	nrf_radio_fem_spi: nrf21540_fem_spi@0 {
	   compatible = "nordic,nrf21540-fem-spi";
	   status = "okay";
	   reg = <0>;
	   spi-max-frequency = <8000000>;
	};
 };

I have added the above code portion into my overlay file and updated the custom pins.

CONFIG_MPSL_FEM_NRF21540_TX_GAIN_DB=20

CONFIG_BT_CTLR_TX_PWR_ANTENNA=20

CONFIG_MPSL_FEM_NRF21540_RX_GAIN_DB=0

And added config macros in to the defconfig file.

After that the power is increased. Looks like the 21540 chip is enabled after added the gpio config.

Now I need to control and change the power by using SPI. But by using the above code portion the SPI read and write is not working. I am using SPI1.

How to fix this issue?

RE: nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

Kazi Afroza Sultana — Fri, 20 Oct 2023 09:01:34 GMT

Hello,

GPIO mode implementation of FEM is compatible with the device. So, you can implement 3-pin PA/LAN interface. The functionalities designated as PA and LNA apply to the pin tx-en-gpios and rx-en-gpios.

You have to add the following node in the device tree file.

These pin numbers for tx-en and rx-en can be any available pin.

Here is the link https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/device_guides/working_with_fem.html#spi-gpio-mode you can look at to implement this.

RE: nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

AKV — Tue, 17 Oct 2023 06:36:55 GMT

Thanks for the response.

I was able to configure the SPI and SPIS.

I am using nRF21540 interface with nRF52840.

How to add PA LNA GPIO and SPI configurations into my custom code. Is there any example code?

RE: nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

Kazi Afroza Sultana — Tue, 03 Oct 2023 13:09:39 GMT

Hello,

Did you set the pin correctly according to your custom board design? Do you have overlay file for your custom board that should be looked like below overlay file?

&spi1 {
status = "okay";
compatible = "nordic,nrf-spim";
pinctrl-0 = <&spi1_default>;
...rest of configuration
};

RE: nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

AKV — Sat, 30 Sep 2023 08:06:29 GMT

Hi,

Thanks for the response.

I was able to create the custom board and able to enable the LED, Button and UART and tested.

But getting errors when I am trying to enable the SPIM1 and SPIS2. (SPIM1 and SPIS2 was working in the nRF52840 DK but not able to enable in the custom board config code).

Here I am attaching the config files,

prj.conf

# Configure SPIS
CONFIG_SPI=y
CONFIG_NRFX_SPIM1=y
CONFIG_NRFX_SPIS2=y

Custom_nRF52840.dts

&spi1 {
	compatible = "nordic,nrf-spi";
	status = "okay";
	sck-pin = < 28 >;
	miso-pin = < 4 >;
	mosi-pin = < 3 >;
};

&spi2 {
	compatible = "nordic,nrf-spi";
	status = "disabled";
	sck-pin = < 13 >;
	miso-pin = < 20 >;
	mosi-pin = < 15 >;
};

&uart0 {
	compatible = "nordic,nrf-uarte";
	status = "okay";
	current-speed = <115200>;
	tx-pin = <6>;
	rx-pin = <8>;
	rts-pin = <5>;
	cts-pin = <7>;
};

The errors I am getting are,

nrfx_spim.h:84:35: error: 'NRFX_SPIM1_INST_IDX' undeclared here (not in a function); did you mean 'NRF_SPIM_INST_GET'?

nrfx_spis.h:81:35: error: 'NRFX_SPIS2_INST_IDX' undeclared here (not in a function); did you mean 'NRF_SPIS_INST_GET'?

How to fix these errors?

RE: nRF52840 Custom board Pin mapping change in nRF Connect SDK V2.2.0

Kazi Afroza Sultana — Tue, 26 Sep 2023 13:25:31 GMT

Hello,

You can look at this previous case (+) Build own custom board on nrf Connect SDK(Devicetree) - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com). It may help you.

For the device tree of custom board, you have to follow your schematic design to set the pin numbers of the peripheral. You can read about device tree here https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-2-reading-buttons-and-controlling-leds/.

Thanks.

Kazi