nRF5340 SPI slave doesnt seem to receive

RE: nRF5340 SPI slave doesnt seem to receive

Kenneth — Tue, 25 Feb 2025 08:52:59 GMT

Can you at least make sure it works without TF-M?

The overlay you refer to , what is the name of that file?

Kenneth

RE: nRF5340 SPI slave doesnt seem to receive

kaushalyasat — Tue, 25 Feb 2025 05:26:06 GMT

Hi Kenneth,

Yes we use NS+TF-M. When I add ' CONFIG_TFM_LOG_LEVEL_SILENCE=y' to my prj.conf, I get

d:/Projects/nrf/zm2hostradiofw/prj.conf:89: warning: ignoring malformed line ' CONFIG_TFM_LOG_LEVEL_SILENCE=y'

It seems I have not built TF-M with my application. So I added CONFIG_BUILD_WITH_TFM=y and then the project got built, but then the app doesnt seem to run. (I have disabled UART1 from my overlay as explained in https://docs.nordicsemi.com/bundle/ncs-2.9.0/page/nrf/security/tfm.html#building)

Apparently TF-M uses UART1. I have tried assigning different pins to the UART1 in my overlay as follows.

uart1_default: uart1_default {

group1 {

psels = <NRF_PSEL(UART_TX, 1, 5)>,

<NRF_PSEL(UART_RTS, 0, 11)>;

};

group2 {

psels = <NRF_PSEL(UART_RX, 1, 0)>,

<NRF_PSEL(UART_CTS, 0, 10)>;

bias-pull-up;

};

uart1_sleep: uart1_sleep {

group1 {

psels = <NRF_PSEL(UART_TX, 1, 5)>,

<NRF_PSEL(UART_RX, 1, 0)>,

<NRF_PSEL(UART_RTS, 0, 11)>,

<NRF_PSEL(UART_CTS, 0, 10)>;

low-power-enable;

};

But still P0.01 doesnt seem to work for SPI slave.

My time limit for this project has almost finished. So any help is much appreciated.

Cheers,

Kaushalya

RE: nRF5340 SPI slave doesnt seem to receive

Kenneth — Thu, 20 Feb 2025 17:10:59 GMT

Hello,

I notice you are mentioning P1_NS, does this mean you are working with non-secure and have TF-M? If yes, try to set CONFIG_TFM_LOG_LEVEL_SILENCE=y, ref:
https://docs.nordicsemi.com/bundle/ncs-2.9.0/page/nrf/security/tfm.html#building

Kenneth

RE: nRF5340 SPI slave doesnt seem to receive

kaushalyasat — Thu, 20 Feb 2025 01:07:35 GMT

Hi Kenneth,

Yes uart1 was using it, but I had disabled uart1 in my overlay file. However I tried to reassign different pins to uart1 as in this overlay file.

devzone.nordicsemi.com/.../8306.zmhostradio.overlay

Also I assigned gpio1, 1 as led3 under leds node and tried to drive it.

I tried like

	ret = dk_leds_init();
	if (ret) {
		LOG_ERR("Could not initialize leds, err code: %d", ret);
		goto end;
	}
	dk_set_led_on(DK_LED4);
	dk_set_led_off(DK_LED4);

and also

#define LED3_NODE DT_ALIAS(led3)
	int ret;
	
	static const struct gpio_dt_spec gpio11 = GPIO_DT_SPEC_GET(LED3_NODE, gpios);

	if (!gpio_is_ready_dt(&gpio11)) {
		return 0;
	}

	ret = gpio_pin_configure_dt(&gpio11, GPIO_OUTPUT_ACTIVE);
	if (ret < 0) {
		return 0;
	}

	ret = gpio_pin_toggle_dt(&gpio11);

No matter what, gpio1, 1 doesn't seem like its configured as an output.

I then tried debugging into it (both nrf connect debugger and ozone debugger) and check DIR register of P1_NS peripheral, and it shoes pin 1 as an input!!

Can this pin be assigned to something in network processor? How to verify it?

I checked the zephyr.dts and it seems my led3 mapping is correct.

I am totally puzzled. What is going on here??

Thanks,

Kaushalya

RE: nRF5340 SPI slave doesnt seem to receive

Kenneth — Wed, 19 Feb 2025 09:36:11 GMT

Hi,

It's a bit hard to decode the files, but looks like uart1 might be using port1 pin1. I would start looking there. Does the pin work as a normal gpio (if you don't use it for spis)?

Kenneth

RE: nRF5340 SPI slave doesnt seem to receive

kaushalyasat — Tue, 18 Feb 2025 23:42:23 GMT

Hi Kenneth,

[quote userid="2111" url="~/f/nordic-q-a/118820/nrf5340-spi-slave-doesnt-seem-to-receive/523223"]If you are using the DK maybe check out:[/quote]

I am not using the DK. I am using UBlox NORA B126 in my board. There is no other connection to P1.1. When I debug into SPI2S init, I can see the MOSI is assigned to P1.1 and is connected to the peripheral. But when I send a byte from the master, all I receive is 0.

This is my zephyr.dts after the build with P1.1 set as MOSI.

devzone.nordicsemi.com/.../06736.zephyr.dts

I couldn't find gpio 1,1 being used in any other place. May be you can correct me if I am wrong.

Can you see any clue as to why the P1.1 is not functioning as SPI2S MOSI?

Cheers,

Kaushalya

RE: nRF5340 SPI slave doesnt seem to receive

Kenneth — Mon, 17 Feb 2025 10:27:32 GMT

[quote user="kaushalyasat"]1. Why wouldn't the devicetree compiler complains when the same pins is assigned to two interfaces?[/quote]

In an ideal world it would, but it doesn't.

[quote user="kaushalyasat"]I verified it in zephyr.dts, but P1.1 doesnt seem to work!! Any ideas?[/quote]

If you are using the DK maybe check out:
https://docs.nordicsemi.com/bundle/ug_nrf5340_dk/page/UG/dk/dyn_hw_flow_control.html#d10e117

[quote user="kaushalyasat"]This means if I map P0.8, P0.9 etc as SPI2S, it doesn't need to be mapped as a peripheral? I[/quote]

Correct.

Kenneth

RE: nRF5340 SPI slave doesnt seem to receive

kaushalyasat — Mon, 17 Feb 2025 04:06:41 GMT

Hi Kenneth,

Thanks again. I have also noticed this but when I check from the GUI devicetree view, the nrf-gpio-forwarder was not visible. But as you point out in the zephyr.dts I can see the relevant pins being used.

1. Why wouldn't the devicetree compiler complains when the same pins is assigned to two interfaces?

2. I have given up using P0.8 - P0.11 and picked up other four GPIOs as SPI2S and I selected them as following.

nCS - P0.13

SCLK - P0.14

MOSI - P1.1

MISO - P0.15

Then I could see the spi handler gets invoked but the received character was always 0x00. Then I changed MOSI to P0.18 and all was good.

Now after seeing your comment, I see P1.1 is also used in nrf-gpio-forwarder and remapped all my spi2 related pins from nrf-gpio-forwarder. I verified it in zephyr.dts, but P1.1 doesnt seem to work!! Any ideas?

[quote userid="2111" url="~/f/nordic-q-a/118820/nrf5340-spi-slave-doesnt-seem-to-receive/523145"]for SPIM4 and 32Mbps you need to configure MCUSEL to "Peripheral"[/quote]

This means if I map P0.8, P0.9 etc as SPI2S, it doesn't need to be mapped as a peripheral? I thought SPI2S is also acts as a peripheral. Even after SPI2S is working fully, the CNF register indicates that each pin belongs to APPCPU, not Peripheral.

Cheers,

Kaushalya

RE: nRF5340 SPI slave doesnt seem to receive

Kenneth — Sun, 16 Feb 2025 20:05:52 GMT

Hi,

Think I found the problem. I compiled hello world for nRF5340 and looked at the zephyr.dts file in the build folder. I can find 4 pins are assigned by default to the network core, like this:

	gpio_fwd: nrf-gpio-forwarder {
		compatible = "nordic,nrf-gpio-forwarder";
		status = "okay";
		uart {
			gpios = < &gpio1 0x1 0x0 >, < &gpio1 0x0 0x0 >, < &gpio0 0xb 0x0 >, < &gpio0 0xa 0x0 >;
		};
	};

Amongst those are for instance P0.10 and P0.11, I assume that is the cause of your problems. To answer your questions:

[quote user="kaushalyasat"]I thing for the SPI to work, they should be connected to 'Peripheral', not 'APPCPU'. Can you please confirm?[/quote]

Looks like you are right, for SPIM4 and 32Mbps you need to configure MCUSEL to "Peripheral" yes.

Kenneth

RE: nRF5340 SPI slave doesnt seem to receive

kaushalyasat — Fri, 14 Feb 2025 00:45:51 GMT

Thanks Kenneth,

I figured out that SPI4 has only master mode, but what I cant figure out is why cant I assign P0.08, P0.09, P0.10 and P0.11 to any other SPI interface like SPI2. I guess if we dont use them as NFC or tracedata, they could be assigned to SPI function. Please confirm.

Even after I assigned NFC as GPIO, my SPI comms were not working. I was running out of options (and time) so wired the SPI to different set of pins (P0.13, P0.14, P0.15 and P1.01) and immediately it was working!! So there is something with P0.8-P0.11 that prevented them from being used as SPI slave.

Also one other observation is when I debugged it and check the MCUSEL bits of corresponding pins, I saw them as assigned to APPCPU. Even my new pin assignment is same. I thing for the SPI to work, they should be connected to 'Peripheral', not 'APPCPU'. Can you please confirm?

Cheers,

Kaushaya

RE: nRF5340 SPI slave doesnt seem to receive

Kenneth — Thu, 13 Feb 2025 14:16:25 GMT

Hello,

The driver should handle everything, so as long as you use the driver in the same way as the test examples that is all you need to do.

The SPIM4 do not share hardware resources with other instances, ref:
https://docs.nordicsemi.com/bundle/ps_nrf5340/page/chapters/memory/appmem.html#ariaid-title3

spim3 share with spis3, twim3, twis3 and uart3:

spim4 don't share with other functionality:

The pin assignment tables show recommended usage:
https://docs.nordicsemi.com/bundle/ps_nrf5340/page/chapters/pin.html

If there is no specific recommended usage for a pin, then it can be used for anything. The spi pins can use those pins that have labeled qspi usage, if qspi is not used.

Edit: I can see that you write P0.9 and P0.10, make sure that these pins are not configured to nfc by using:
CONFIG_NFCT_PINS_AS_GPIOS=y (that might be deprecated, you may need to use in devicetree &uicr { nfct-pins-as-gpios; };.

Kenneth

RE: nRF5340 SPI slave doesnt seem to receive

kaushalyasat — Thu, 13 Feb 2025 06:28:16 GMT

Hi,

We need some help urgently as we are stuck at this point.

After refering bit more on NORA B1 user guide, I come across this.

"SPIM4: For the fastest SPI mode, the special purpose GPIO pins are enabled using the Peripheral setting of the MCUSEL pin of the PIN_CNF register. When activated, the SPIM PSEL settings are ignored, and the dedicated pins are used. The GPIO must use the extra high drive E0E1 configuration in the DRIVE field of the PIN_CNF GPIO register."

I tried setting the MCUSEL to peripheral as follows.

	#define SPIM4_SCK  NRF_GPIO_PIN_MAP(0,8)
	#define SPIM4_MOSI NRF_GPIO_PIN_MAP(0,9)
	#define SPIM4_MISO NRF_GPIO_PIN_MAP(0,10)

	nrf_gpio_cfg(SPIM4_SCK, NRF_GPIO_PIN_DIR_OUTPUT, NRF_GPIO_PIN_INPUT_DISCONNECT, NRF_GPIO_PIN_NOPULL, NRF_GPIO_PIN_H0H1, NRF_GPIO_PIN_NOSENSE);
	nrf_gpio_cfg(SPIM4_MOSI, NRF_GPIO_PIN_DIR_OUTPUT, NRF_GPIO_PIN_INPUT_DISCONNECT, NRF_GPIO_PIN_NOPULL, NRF_GPIO_PIN_H0H1, NRF_GPIO_PIN_NOSENSE);
	nrf_gpio_cfg(SPIM4_MISO, NRF_GPIO_PIN_DIR_OUTPUT, NRF_GPIO_PIN_INPUT_DISCONNECT, NRF_GPIO_PIN_NOPULL, NRF_GPIO_PIN_H0H1, NRF_GPIO_PIN_NOSENSE);

	nrf_gpio_pin_control_select(SPIM4_SCK, NRF_GPIO_PIN_SEL_PERIPHERAL);
	nrf_gpio_pin_control_select(SPIM4_MOSI, NRF_GPIO_PIN_SEL_PERIPHERAL);
	nrf_gpio_pin_control_select(SPIM4_MISO, NRF_GPIO_PIN_SEL_PERIPHERAL);

But when I debug and check register at GPIO0-Pin 8, I see it is still set as APPMCU.

So I have following questions.

1. Can P0.8, P0.9 and P0.10 only be used as SPI4 in master mode, not as a slave?

2. If SPI4 on the above pins can be used as a slave, how to do it?

Cheers,

Kaushalya

RE: nRF5340 SPI slave doesnt seem to receive

kaushalyasat — Wed, 12 Feb 2025 05:29:51 GMT

Also I can see that there is a hardware semaphore that you got to acquire before any spi slave comms can happen. But I havent seen anywhere a sample code on how to do this. Could you also elaborate on how to do that?

RE: nRF5340 SPI slave doesnt seem to receive

kaushalyasat — Wed, 12 Feb 2025 05:14:25 GMT

We are using 4 pins of NORA B126 for SPI, which is a classified as SPIM4. This is bit confusing as we can assign these pins to any SPI function vie PSEL registers. At the moment we have assigned them to SPI2. Is there any issue here?

RE: nRF5340 SPI slave doesnt seem to receive

kaushalyasat — Wed, 12 Feb 2025 03:00:37 GMT

Hi Kenneth, I accidently closed this thread, apologies about that.

I tried importing my nRF5340 overlay, but I am getting the following error, for which I cant work out the reason.

fatal error: opening dependency file secure_fw\partitions\crypto\mbedcrypto\nrf_security_src\CMakeFiles\crypto_service_mbedcrypto.dir\C_\ncs\v2.9.0\modules\crypto\mbedtls\library\memory_buffer_alloc.o.d: No such file or directory

My overlay file is devzone.nordicsemi.com/.../zmhostradio.overlay

Can you help to sort it out?

Thanks,

Kaushalya

RE: nRF5340 SPI slave doesnt seem to receive

Kenneth — Tue, 11 Feb 2025 11:56:24 GMT

Hello,

I suggest to look at the driver test examples for spi, which also include spis:
\zephyr\tests\drivers\spi\spi_controller_peripheral\src\main.c

By default I can see there is no overlay for nRF5340, but I would expect you can rename nrf52840dk_nrf52840.overlay to nrf5340dk_nrf5340_cpuapp.overlay, and update the pins used for spi and spis, and then it should work.

Kenneth

RE: nRF5340 SPI slave doesnt seem to receive

kaushalyasat — Tue, 11 Feb 2025 04:49:25 GMT

We use NORA B120 module and the SPI signals are wired as follows.

The overlay file contents related to the SPI is as follows.

&pinctrl {
.
.
	spi_slave_default: spi_slave_default {
		group1 {
			psels = <NRF_PSEL(SPIS_SCK, 0, 8)>,
					<NRF_PSEL(SPIS_MOSI, 0, 9)>,
					<NRF_PSEL(SPIS_MISO, 0, 10)>,
					<NRF_PSEL(SPIS_CSN, 0, 11)>;
		};
	};
};

my_spi_slave: &spi2 {
	compatible = "nordic,nrf-spis";
	status = "okay";
	pinctrl-0 = <&spi_slave_default>;
	pinctrl-names = "default";
	def-char = <0x00>;
};