NFC Tag reader example with ST25R3911B fails

RE: NFC Tag reader example with ST25R3911B fails

runsiv — Fri, 22 Mar 2024 12:21:29 GMT

Thanks.

The 5340 supports up to 5 SPI slave/masters instances. So the different SPI0-4 would reflect different SPI instances.

Regards

Runar

RE: NFC Tag reader example with ST25R3911B fails

kahlenberg — Fri, 22 Mar 2024 09:36:00 GMT

I am using nRF Version 2.4.2.

I already activated SPI with CONFIG_SPI=y, but why are there multiple SPI nodes in device-tree? spi0, spi1, spi3... and even spi4.

RE: NFC Tag reader example with ST25R3911B fails

runsiv — Fri, 22 Mar 2024 09:29:21 GMT

You should only need to use the CONFIG_SPI=y to enable the SPI interface. I can't see anything stands out. Could you build the project with optimized for debug and see if anything more is printed. I'm also curious regarding the E: Oscillator start failed.

Which version of the SDK are you using?

Regards

Runar

RE: NFC Tag reader example with ST25R3911B fails

kahlenberg — Fri, 22 Mar 2024 08:35:31 GMT

One more question about selecting SPI instances.

In device-tree there are a couple of SPI nodes, i.e. spi0, spi1, spi3... and in proj.conf SPI is activated with CONFIG_SPI=y. But which instance is used in particular case? spi0 or spi1 or spi3? How / where is the selection occur?

RE: NFC Tag reader example with ST25R3911B fails

kahlenberg — Thu, 21 Mar 2024 21:58:55 GMT

Edit:
I am using a device tree overlay as in the example code:

&spi1 {
	compatible = "nordic,nrf-spim";
	status = "okay";
	cs-gpios = <&gpio1 12 GPIO_ACTIVE_LOW>;

	pinctrl-0 = <&spi1_default_alt>;
	pinctrl-1 = <&spi1_sleep_alt>;
	pinctrl-names = "default", "sleep";
	st25r3911b@0 {
		compatible = "st,st25r3911b";
		reg = <0>;
		spi-max-frequency = <4000000>;
		irq-gpios = <&gpio0 3 GPIO_ACTIVE_HIGH>;
		led-nfca-gpios = <&gpio0 7 GPIO_ACTIVE_HIGH>;
	};
};

&pinctrl {
	spi1_default_alt: spi1_default_alt {
		group1 {
			psels = <NRF_PSEL(SPIM_SCK, 1, 15)>,
				<NRF_PSEL(SPIM_MOSI, 1, 13)>,
				<NRF_PSEL(SPIM_MISO, 1, 14)>;
		};
	};

	spi1_sleep_alt: spi1_sleep_alt {
		group1 {
			psels = <NRF_PSEL(SPIM_SCK, 1, 15)>,
				<NRF_PSEL(SPIM_MOSI, 1, 13)>,
				<NRF_PSEL(SPIM_MISO, 1, 14)>;
			low-power-enable;
		};
	};

};

The connections from X-NUCLOE-NFC08A1 seem correct.

proj.conf

#
# Copyright (c) 2019 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
CONFIG_NCS_SAMPLES_DEFAULTS=y

CONFIG_SPI=y

CONFIG_ST25R3911B_LIB=y

CONFIG_NFC_NDEF=y
CONFIG_NFC_NDEF_RECORD=y
CONFIG_NFC_NDEF_MSG=y
CONFIG_NFC_NDEF_PARSER=y
CONFIG_NFC_NDEF_LE_OOB_REC_PARSER=y
CONFIG_NFC_T2T_PARSER=y
CONFIG_NFC_T4T_HL_PROCEDURE=y
CONFIG_NFC_NDEF_CH_PARSER=y

CONFIG_POLL=y

CONFIG_MAIN_STACK_SIZE=2048

Still doesn't work.

RE: NFC Tag reader example with ST25R3911B fails

kahlenberg — Thu, 21 Mar 2024 20:21:15 GMT

Hi Runar,

I am using the example code without changing anything:
https://github.com/nrfconnect/sdk-nrf/tree/main/samples/nfc/tag_reader

I am not sure and searching for If the ST25R3911B must be programmed with a firmware before usage.

Regards.

RE: NFC Tag reader example with ST25R3911B fails

runsiv — Thu, 21 Mar 2024 08:41:29 GMT

Hi Mubin

The error indicate that the device is not found. Could you post devicetree and the prj.conf. What interface do you use to communicate with the ST25R3911B? Have you checked if there is any activity on the pins?

Regards

Runar