SPI for nrf5340dk in ncsv2.8

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Tue, 25 Mar 2025 08:48:43 GMT

Glad to hear that! :)

Kind regards,
Andreas

RE: SPI for nrf5340dk in ncsv2.8

KTH — Tue, 25 Mar 2025 04:08:17 GMT

Hi,

Now able to read AD5940 chip id.

struct spi_cs_control spi_cs = {
	.gpio = SPI_CS_GPIOS_DT_SPEC_GET(DT_NODELABEL(reg_my_spi_master)),
	.delay = 0,
};

static void spi_init(void)
{
	/*get device address*/
	spi_dev = DEVICE_DT_GET(DT_NODELABEL(spi1_master));

	if (!device_is_ready(spi_dev))
	{
		printk("SPI master device not ready!\n");
	}
	if (!device_is_ready(spi_cs->gpio.port))
	{
		printk("SPI master chip select device not ready!");
	}
	printk("SPI : %s	CS_GPIO: %s		CS_PIN: %d\n", spi_dev->name, spi_cs->gpio.port->name, spi_cs->gpio.pin);
	printk("SPI device ready\n");
}

Thank you

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Mon, 24 Mar 2025 13:16:05 GMT

Hi,

DEVICE_DT_GET returns a pointer to the device object created for the instance, i.e a pointer to spi1 based on the DT_NODELABEL property of the device. See https://github.com/nrfconnect/sdk-zephyr/blob/bd1cf27b22f1003d58ecf4af81961722e1eb9949/include/zephyr/device.h#L254 or look the API up by going to definition within VS Code.

The following

	spi_dev = DEVICE_DT_GET(DT_NODELABEL(spi1));
	if (spi_dev == NULL)
	{
		LOG_ERR("Error: SPI device is not ready, err: %d", err);
		return 0;
	}

returns a pointer. And the ONLY time you enter the If-check is if said pointer is NULL. This means that you never check if the device is ready.

See https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-5-serial-peripheral-interface-spi/ for more information about setting up and checking a SPI peripheral.

Kind regards,
Andreas

RE: SPI for nrf5340dk in ncsv2.8

KTH — Mon, 24 Mar 2025 03:39:03 GMT

Hi,

if (spi_dev == NULL)
{
LOG_ERR("Error: SPI device is not ready, err: %d", err);
return 0;
}

This will check for whether the device is ready or not right?

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Fri, 21 Mar 2025 13:45:53 GMT

Hi,

Glad to hear you've managed to get past the BLE issues.

I see you've commented out the error check to see if the device is ready (line 49). Do you check at any point if your device is set up? Could you add a check to see if you've enabled and initialized the device properly and that it is working? There are some lessons in the fundamentals course that should cover how to do this as well

Kind regards,
Andreas

RE: SPI for nrf5340dk in ncsv2.8

KTH — Wed, 19 Mar 2025 06:13:11 GMT

Hi Andreas,

Thank you for your guidance in resolving bt issue, flashed hci_ipc sample to network core and our application to application core. Able to transfer data.

Now we have our custom board where AD5940 is connected to nrf5340 through spi. Not able to read chip id of ad5940. Tried with the example above.

Taken reference from Exercise 1 – Interfacing with a sensor over SPI and sample from github mentioned in the exercise, spi_example. Modified spi pins in overlay.

Using ad5940library.

devzone.nordicsemi.com/.../0523.main.c

When we are tyring to read chipid, getting output as below

*** Booting nRF Connect SDK v2.9.0-7787b2649840 ***
*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
SPI : spi@9000
00000000

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Wed, 05 Mar 2025 14:13:07 GMT

Hi,

[quote user="KTH"]1. Can you explain how to get "custom netcore firmware with custom board changes"?[/quote]

I can't quite see why this is relevant, since you can always set the SPI up on the appcore (which is recommended) and simply send the data using BLE, for instance NUS over BLE.

If I understand you're issue correct, you're now struggling with adding BLE to the SPI applicaiton. In NCS v2.9.0 we're using "sysbuild" and "companion images" instead og child/parent-images which was previously used.

What you need to do to get BLE is the same as is done in the BLE samples for nrf5340, where you build the hci_ipc companion component for the netcore through sysbuild. https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/ should explain it, but in case it does not you can see the sysbuild images here:https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/config_and_build/sysbuild/sysbuild_images.html

Enabling SB_CONFIG_NETCORE_HCI_IPC in sysbuild.conf adds the netcore image to the application.

I strongly recommend you go through https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/topic/sysbuild-explained/

[quote user="KTH"]2. For our requirement do we need to add overlay for cpunet also?[/quote]

I believe the answer to this is within my answer to 1 as well.

Apologies for not supplying you with a simple sample, but I would recommend you to go through any BLE sample in the SDK that is built for the nrf5340 and copy the settings and setup to your application.

This will be a multi-image build, and you don't have to build for the netcore itself. By enabling the correct components (such as SB_CONFIG_NETCORE_HCI_IPC), the build system will drag in the required images to generate the hex that will flash both the appcore and netcore.

Kind regards,
Andreas

RE: SPI for nrf5340dk in ncsv2.8

KTH — Tue, 04 Mar 2025 11:40:05 GMT

Hi, we do have our custom board where we want to read sensor data using spi and send it through bt.

Able to test bt.

prj.conf:

CONFIG_BT=y

CONFIG_BT_PERIPHERAL=y

CONFIG_BT_DEVICE_NAME="nRF5340 DKK BLE"

CONFIG_BT_GATT_CLIENT=y

But when integrating bt in the sample where spi is working, it is building for cpuapp but not for cpunet. It is giving errors like i mentioned before.

1. Can you explain how to get "custom netcore firmware with custom board changes"?

2. For our requirement do we need to add overlay for cpunet also?

Thank you

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Mon, 03 Mar 2025 11:35:46 GMT

[quote user="KTH"]

1. Tried with a different pc where ncs2.6.1 and toolchain 2.7 were installed, it is building.

2.Reinstalled ncs and all tools again.

ncs 2.9

tool chain 2.9. Able to build the sample.

[/quote]

Great! Glad to hear that

[quote user="KTH"]But in both the cases it is giving error related to overlay file[/quote]

To be frank, the Problem-tab is quite misleading in some cases and might through warnings and red-underline some issues that is not there at all. But if I would guess if the error is a real one, I would guess that it is because some naming has changed between v2.5.1 (where the sample was built) and v2.6.1. On second thought, it might actually be due to hardware model changes https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_hwmv2.html

[quote user="KTH"]And also, do we have to add different overlay for application and network core?[/quote]

For the 5340 you only need to have a board file for the cpuapp and the non-secure version of cpuapp, i.e cpuapp/ns unless you have custom netcore firmware with custom board changes. As it is by default: The build system will add the companion components it needs to add for the netcore if you add the relevant configurations to prj.conf or sysbuild.conf and sysbuild/<your_companion_image>.conf and .overlay. See https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-3-elements-of-an-nrf-connect-sdk-application/ for a great explanation of the components in an NCS application and https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/topic/sysbuild-explained/ for the sysbuild expandation

[quote user="KTH"]When building the same sample for configuration nrf5340dk/nrf5340/cpunet, it is giving errors[/quote]

This is roughly the same errors that you got previously, where the build fault log states that it can't find the items in main.c that is specified in <your_build_target>.overlay, since there are no nrf5340dk/nrf5340/cpunet overlay files that states that the various SPIM/S instances should be on the board.

Let me know if this answers your questions!

Kind regards,
Andreas

RE: SPI for nrf5340dk in ncsv2.8

KTH — Mon, 03 Mar 2025 10:43:22 GMT

Hi Andreas,

1. Tried with a different pc where ncs2.6.1 and toolchain 2.7 were installed, it is building.

2.Reinstalled ncs and all tools again.

ncs 2.9

tool chain 2.9. Able to build the sample.

But in both the cases it is giving error related to overlay file

And also, do we have to add different overlay for application and network core?

When building the same sample for configuration nrf5340dk/nrf5340/cpunet, it is giving errors

Thank you

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Fri, 28 Feb 2025 13:25:38 GMT

I must admit I'm baffled. I can't see anything but there being something faulty with the installation or that something has been modified in the SDK

Could you try with a different work station
Could you uninstall NCS and all tools completely and reinstall them per https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/installation/install_ncs.html

I've tried building with multiple different work stations myself, as well as different OS and none give the faults you're seeing. Since you were able to build the adc sample out of tree, I am expecting you to be able to build the zip I sent you with the exact same steps as you successfully built the adc sample with.

Kind regards,
Andreas

RE: SPI for nrf5340dk in ncsv2.8

KTH — Fri, 28 Feb 2025 10:20:05 GMT

Built the sample for given configuration, still it is giving errors

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Fri, 28 Feb 2025 09:37:21 GMT

[quote user="KTH"]adc_sequene sample is building with target nrf52840dk[/quote]

Thats good to hear. This indicates that the SDK is properly set up and that building an in-tree application works.

[quote user="KTH"]nrf connect generate support information is as below[/quote]

Everything here looks fine and your setup is as good as identical to mine.

W.r.t the spi sample.

Here's a new, unmodified version of the same sample from here https://github.com/too1/ncs-spi-master-slave-example/tree/master

devzone.nordicsemi.com/.../spi_5F00_m_5F00_s.zip

I've verified with multiple colleagues that this sample builds out of the box for the following configuration

NCS 2.8.0
nrf5340dk/nrf5340/cpuapp
with and without sysbuild

I see that you've previously built the SPI sample from c:\Users\hello\Music\ncs-spi-master-slave-example-master. Could you shorten the name of the sample and preferably place it closer to C:\? Windows has an issue with path length when building any project.

Place the sample for instance within ncs/my_projects

and build for the configuration I mentioned.

Kind regards,
Andreas

RE: SPI for nrf5340dk in ncsv2.8

KTH — Fri, 28 Feb 2025 08:56:58 GMT

Hi,

adc_sequene sample is building with target nrf52840dk

nrf connect generate support information is as below

devzone.nordicsemi.com/.../1682.nrf.txt

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Fri, 28 Feb 2025 08:14:49 GMT

Lets start with the ADC sample first. This sample work for at least the supported boards. Lets focus on the adc_sequence sample within zephyr/samples/drivers/adc.

[quote user="KTH"]Not able to build zephyr ADC examples also[/quote]

There are also no nRF5340 board support in the board folder of this sample. It works with any of the boards found within adc_sequence/boards, for instance with nrf52840dk/nrf52840 (below is a result with build from terminal and list of the boards found in the boards folder of this sample. The same can be stated for the VS Code extension).

If you remove and build for the nrf52840dk, do you see the error as you previously did? If you do, then I believe there is something wrong with your installation. Could you 1: generate support information from vs code by opening command pallette in VS Code, i.e

Open VS Code
Open command pallet by pressing ctrl+***+p
search for "generate support information"
Select it and press enter and upload the information here

If we get this working, then we can go back to the spi master sample from too1's git repo

Kind regards,
Andreas

RE: SPI for nrf5340dk in ncsv2.8

KTH — Fri, 28 Feb 2025 04:23:17 GMT

Hi, tried building with target nrf5340dk/nrf5340/cpuapp selected, still giving errors.

Not able to build zephyr ADC examples also

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Thu, 27 Feb 2025 13:16:07 GMT

Ah, thank you for providing this. You're building for the /ns target of the nRF5340DK. Currently there are no board files for this within the board folder meaning that the SPI configuration is not set up for the build target you're trying to target

Please try again with this target and let me know if this compiles

Kind regards,
Andreas

RE: SPI for nrf5340dk in ncsv2.8

KTH — Thu, 27 Feb 2025 04:53:54 GMT

Hi,Here are the images of the building the sample

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Tue, 25 Feb 2025 15:02:52 GMT

Strange.. And the errors you're getting is the same as the initial comment in this post?

Please describe in detail every step you do to build the sample. Images are also welcome.

Kind regards,
Andreas

RE: SPI for nrf5340dk in ncsv2.8

KTH — Mon, 24 Feb 2025 10:32:15 GMT

Tried to build again like you mentioned by deleting the build folder before building again, still same.

Previously also, downloaded the example again and tried to build it.

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Mon, 24 Feb 2025 09:13:33 GMT

[quote user="KTH"]I tried again to build the same example by selecting nrf5340dk/nrf5340/cpuapp in Board target when adding build configuration. still getting the below errors.[/quote]

You're referring to an unmodified version this sample, right? https://github.com/too1/ncs-spi-master-slave-example/tree/master/src

If so, please try again but first delete the build folder before building again. I'm not getting any faulty builds for any versions of NCS from NCS 2.5.0 to NCS 2.9.0

Kind regards,
Andreas

RE: SPI for nrf5340dk in ncsv2.8

KTH — Mon, 24 Feb 2025 05:11:42 GMT

Hi,

I tried again to build the same example by selecting nrf5340dk/nrf5340/cpuapp in Board target when adding build configuration. still getting the below errors.

devzone.nordicsemi.com/.../2388.nrf.txt

Didn't make any changes to the example.

Also can you once check the configurations in my before post ?

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Thu, 20 Feb 2025 09:37:16 GMT

Hi,

Apologies for the delay.

I reviewed the sample you originally supplied and there is nothing in it that suggests that it is not compatible with sysbuild (which is used in NCS v2.8.0). I build the sample using

west build -b nrf5340dk/nrf5340/cpuapp and flashed it with west flash --recover on my nRF5340DK and got the expected output:

Kind regards,
Andreas

RE: SPI for nrf5340dk in ncsv2.8

KTH — Fri, 14 Feb 2025 11:49:22 GMT

Hi, We want a design where we want use 2 spi buses for 4 slaves.

devzone.nordicsemi.com/.../nrf.txt

Can you once check above attached file??

Is there any zephyr spi sample example for nrf5340 for multiple slaves?

Thankyou

RE: SPI for nrf5340dk in ncsv2.8

AHaug — Thu, 13 Feb 2025 14:40:31 GMT

Hi,

I recommend you go through the SPI lesson on our academy pages https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-5-serial-peripheral-interface-spi/ as well as the sysbuild exercise https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/topic/sysbuild-explained/.

The unofficial sample that you're using will unfortunately not be maintained and upgraded to support any newer release and the latest version this sample was supported for is NCS older than v2.7.0 as far as I can see.

The only resolution for you is to go through the two supplied links, understand the topics and apply the required changes to the sample you've based the application on.

Kind regards,
Andreas