Using nRF5340-PDK with zephyr adxl372 sensor sample project

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

DBT — Wed, 10 Jun 2020 18:41:34 GMT

Thanks!

With this last piece of information, I was able to get non-secure builds working with SPI pins on port 1.

Now I'm able to get SPI working based on the adxl372 example code and the rallare example code, both secure and non-secure builds, using SPI pins on port 1.

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

Simon — Wed, 10 Jun 2020 13:25:26 GMT

I am really sorry for the late reply. I managed to make it work by modifying the files subsys/spm/spm.c and subsys/spm/Kconfig.

Could you try to apply the patch below to NCS v1.2.0 (nrf repo) and see if you can make it work. I was able to make it work with the P1 pins with these changes.

devzone.nordicsemi.com/.../mypatch.diff

Regarding referencing the P1 pins by using the index plus 32, you are correct, it seems like this function will find the correct port. I have not used this approach before, so I apologize for the confusion. I am learning every day 🙂

Best regards,

Simon

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

DBT — Tue, 02 Jun 2020 20:03:17 GMT

Are you saying that the rallare example only supports P0 (Port 0) pins - not P1 pins?

Or that the pin numbering for both P0 and P1 fit within 32 values?

Per my prior post, these are the pins I want to use:

CS: P1.05

SCK: P1.06

MISO: P1.07

MOSI: P1.08

I would expect (based on prior experience with the nRF52840 and with the SPI example programs that are working for me - the ones that use a secure build) for P1 pins, you use the index plus 32.

So P1.00 = 32, P1.01=33, P1.06 = 38 = 0x26, P1.07 = 39 = 0x27, P1.08 = 40 = 0x28

What numbers should I use for the pins I want to use?

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

Simon — Tue, 02 Jun 2020 17:31:12 GMT

The reason it isn't working with the SPI pins you're using is that there are only 32 valid pin select option, specifically between 0 and 31.

You've chosen the values 0x28, 0x27 and 0x26 which converts to the decimal values 40, 39, and 38. Check out the file ncs\nrf\samples\other\rallare_spi\build\zephyr\include\generated\devicetree.conf after building the sample with those pins:

# SCK pin
DT_NORDIC_NRF_SPIM_40009000_SCK_PIN=38
DT_ALIAS_SPI_1_SCK_PIN=38
DT_NORDIC_NRF_SPIM_SPI_1_SCK_PIN=38
DT_INST_0_NORDIC_NRF_SPIM_SCK_PIN=38
# MOSI pin
DT_NORDIC_NRF_SPIM_40009000_MOSI_PIN=40
DT_ALIAS_SPI_1_MOSI_PIN=40
DT_NORDIC_NRF_SPIM_SPI_1_MOSI_PIN=40
DT_INST_0_NORDIC_NRF_SPIM_MOSI_PIN=40
# MISO pin
DT_NORDIC_NRF_SPIM_40009000_MISO_PIN=39
DT_ALIAS_SPI_1_MISO_PIN=39
DT_NORDIC_NRF_SPIM_SPI_1_MISO_PIN=39
DT_INST_0_NORDIC_NRF_SPIM_MISO_PIN=39

I was too quick to answer the question you asked earlier: "I don't understand why it was necessary to change the pins. I had planned to use:". The reply provided above answers this question.

Best regards,

Simon

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

DBT — Fri, 29 May 2020 20:14:42 GMT

OK if I download the rallare_spi.zip file from the link you provided, it seems to work as-is with a non-secure build.

If I try to change the SPI pins to the ones I want to use, it stops working. Do you have any insight?

nrf5340_dk_nrf5340_cpuappns.overlay


BEFORE 

&spi1 {
	compatible = "nordic,nrf-spim";
	status = "ok";
	mosi-pin = <4>;
	miso-pin = <5>;
	sck-pin = <6>;
};


&spi2 {
	status = "disabled";
};

&i2c1 {
    status = "disabled";
};


AFTER

&spi1 {
	compatible = "nordic,nrf-spim";
	status = "ok";
	mosi-pin = <0x28>;
	miso-pin = <0x27>;
	sck-pin = <0x26>;
};


&spi2 {
	status = "disabled";
};

&i2c1 {
    status = "disabled";
};

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

Simon — Wed, 27 May 2020 22:28:44 GMT

[quote user="DTurnbow"]I don't understand why it was necessary to change the pins. I had planned to use:[/quote]

No, that shouldn't be necessary. Just forget my comment about that.

Have you seen this ticket, where a colleague has provided a working modified version of rallare SPI using SPI_1 and the non-secure version of the board (nrf5340_dk_nrf5340_cpuappns).

It seems like you have to disable i2c1 in the overlay file.

Best regards,

Simon

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

DBT — Tue, 26 May 2020 18:41:31 GMT

With the changes you suggested, I was able to get the SPI sample from Rallare SPI sample to work as you described.

It seems like your step "Removed CONFIG_TRUSTED_EXECUTION_NONSECURE=y from prj.conf" was necessary to get the secure build to build successfully.

I don't understand why it was necessary to change the pins. I had planned to use:

CS: P1.05

SCK: P1.06

MISO: P1.07

MOSI: P1.08

Which you changed to:

CS: P1.05

SCK: P0.26

MISO: P0.27

MOSI: P0.30

But why was this change necessary?

The modified adxl372 example (secure build) I mentioned above uses the original pins successfully.

By the way, the CS pin did not go low during transmissions even after implementing your changes, so is there some problem with the sample code that makes port 1 pins not work? (You have to use port 0?)

I also don't understand why the non-secure builds for the SPI sample or the adxl372 sample don't produce any SPI activity on the SPI port.

Can you provide any insight?

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

Simon — Sun, 24 May 2020 15:09:01 GMT

I managed to get your modified SPI sample from Rallare SPI sample to work. I did the following to make it work:

Started with the SPI sample you uploaded in your latest reply
Removed CONFIG_TRUSTED_EXECUTION_NONSECURE=y from prj.conf
Changed the pin values in nrf5340_dk_nrf5340_cpuapp.overlay from hexadecimal format into decimal format:

&spi1 {
	status = "okay";
	compatible = "nordic,nrf-spim";
	sck-pin = <26>; //sck-pin = <0x26>;
	//Had to use pin 30 since pin 28 was not accessible on my nRF53DK for some reason
	mosi-pin = <30>; //mosi-pin = <0x28>;
	miso-pin = <27>; //miso-pin = <0x27>;
	cs-gpios = <&gpio1 5 0>;
	clock-frequency = <4000000>;
};
&spi2 {
	status = "disabled";
};

Then I connected P0.27 with P0.30 on the nRF53 DK
Built the sample, turned on the nRF53 DK, and flashed it.

If it works, you should see the following log:

*** Booting Zephyr OS build v2.1.99-ncs1  ***
SPIM Example
TX sent: 0
RX recv: 0
TX sent: 1
RX recv: 1
TX sent: 2
RX recv: 2
TX sent: 3
RX recv: 3
TX sent: 4
RX recv: 4
TX sent: 5
RX recv: 5
TX sent: 6
RX recv: 6
TX sent: 7
RX recv: 7
TX sent: 8
RX recv: 8
TX sent: 9
RX recv: 9
TX sent: a
RX recv: a

Best regards,

Simon

Here is the working sample: devzone.nordicsemi.com/.../spi.zip

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

DBT — Tue, 19 May 2020 22:06:55 GMT

According to the errata, SPI_3 does not work on nRF5340, so I tried the other option.

I added these lines to nrf/subsys/spm/Kconfig

config SPM_NRF_P1_NS
bool "GPIO is Non-Secure"
default y

config SPM_NRF_SPIM1_NS
bool "SPIM1 is Non-Secure"
default y

I added these lines to nrf/subsys/spm/spm.c

#ifdef NRF_P1
PERIPH("NRF_P1", NRF_P1, CONFIG_SPM_NRF_P1_NS),
#endif

#ifdef NRF_SPIM1
PERIPH("NRF_SPIM1", NRF_SPIM1, CONFIG_SPM_NRF_SPIM1_NS),
#endif

But I still don't get any SPI activity on the non-secure build.

Did I miss something?

I also tried the other SPI example you provided, but it looks like the formatting of the nRF Connect SDK has changed a lot since that example was written. I tried fixing each issue as I got warning messages, but I wasn't able to get the secure build to build successfully, and the non-secure build does not produce any SPI activity.

Here is the current state of that sample project (with my edits)

devzone.nordicsemi.com/.../spi_2D00_20200519.zip

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

Martin Lesund — Tue, 19 May 2020 13:01:25 GMT

Hi,
If you are trying out just the SPI, I would rather recommend you checking out a simple SPI sample --> https://github.com/Rallare/fw-nrfconnect-nrf/tree/nrf9160_samples/samples/nrf9160/spi that shows how you can implement and use it.

Just change the .overlay file to suit your nrf5340 and your chosen pins.

The reason it's working when building the application in the Secure area, is because then you have the SPI 1 available to be used. If you look at the "Secure Partition Manager" when building the application for the non-secure area you see that you only have enabled SPI 3 to be used in the non-secure area:

Not all peripherals have been set to new available by default in the non-secure area.

However, there is a Pull request to fix that:https://github.com/NordicPlayground/fw-nrfconnect-nrf/pull/1896

So either change the device tree file (.overlay file) + prj.conf (configuration file) file to use SPI 3 or

change the nrf/subsys/spm files "Kconfig" and "spm.c" with these additional lines so you get access to the SPI_1 in the non-secure area.

Kconfig

spm.c

Br,

Martin L.

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

DBT — Mon, 18 May 2020 16:09:04 GMT

Q1:

I understand that if I want to fully use the adxl372 example program (get accelerometer readings, etc.) I would need to connect an adxl372.

But I'm just trying to get the SPI port operating.

Once I get the SPI port operating, I'm going to change the example code to not use the adxl372 but to accomodate what we're doing on our board.

I'm looking at the SPI signals (cs, sck, mosi, miso) with an oscilloscope and looking for data to be sent over the SPI bus.

I understand that without an adxl372 connected, device_get_binding() will fail, but it should attempt to read a few registers over the SPI bus before concluding that the adxl372 is not connected. I should see those register reads on the oscilloscope.

When I build and run a non-secure application

This is what I see on the console:

devzone.nordicsemi.com/.../adxl_2D00_nonsecure.txt

Using the debugger in SES, I can see that the code execution is getting to adxl372_init() and running adxl372_probe() and adxl372_reg_read(). It appears to get stuck in z_impl_spi_transceive().

On the oscilloscope, I've tried triggering on CS going low, SCK going low, and MOSI going low. None of these signals are changing state while running the non-secure app.

HOWEVER, if I build and run the app as secure:

This is what I see on the console:

devzone.nordicsemi.com/.../adxl372_2D00_secure.txt

and the oscilloscope triggers. I see the nRF5340 send 0x01 0xFF 0x05 0xFF over the SPI bus (on MOSI).

So I'm trying to understand why the secure app is actually sending SPI bytes but the non-secure app is not.

It's not preventing me from moving on, but since I'm new to the nRF Connect SDK and zephyr and the nRF5340 I'm trying to better understand the issues with using them.

By the way, I've changed the overlay files to separate the CS and interrupt pins. This doesn't seem to affect the behavior described above.

Here's my updated project

devzone.nordicsemi.com/.../adxl372_2D00_20200518.zip

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

Martin Lesund — Mon, 18 May 2020 13:52:06 GMT

Hi Douglas,

Q1:

Looking at the pins you have selected, 26,27 and 28 should be OK, but you have selected the same pin (p1.05) for both CS and int1. ( They are not the same )

One other thing you should notice is that to use the adxl372 driver you need to connect to a adxl372. Since it is a init function that runs in the beginning and check if the device is connected. (if not the "device_get_binding()" will fail)

Q2:

When you build a regular application, you build it for the non-secure area as described in the document "working with nrf9160".
But you also build "Secure Partition Manager" at the same time, which is why both the "menuconfig" for your application and "spm_menuconfig" shows when you try to configure something building an application in the "non-secure" area.

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

DBT — Tue, 12 May 2020 12:56:43 GMT

Here's my project zipped up

devzone.nordicsemi.com/.../adxl372.zip

RE: Using nRF5340-PDK with zephyr adxl372 sensor sample project

DBT — Mon, 11 May 2020 20:53:18 GMT

Since SPIM2 does not work on nRF5340 yet I updated prj.conf as follows:

CONFIG_STDOUT_CONSOLE=y
CONFIG_LOG=y
CONFIG_SPI=y
CONFIG_SPI_2=n
CONFIG_SPI_1=y
CONFIG_SPI_1_OP_MODES=1
CONFIG_SPI_1_NRF_SPIM=y
CONFIG_SPI_1_NRF_ORC=0xff
CONFIG_SENSOR=y
CONFIG_ADXL372=y
CONFIG_ADXL372_SPI=y
CONFIG_SENSOR_LOG_LEVEL_WRN=y

And I added nrf5340_dk_nrf5340_cpuapp.overlay and nrf5340_dk_nrf5340_cpuappns.overlay both as follows:

&spi1 {
	status = "okay";
	compatible = "nordic,nrf-spim";
	sck-pin = < 0x26 >;
	mosi-pin = < 0x28 >;
	miso-pin = < 0x27 >;
	cs-gpios = <&gpio1 5 0>;

	adxl372@0 {
		compatible = "adi,adxl372";
		reg = <0>;
		spi-max-frequency = <1000000>;
		label = "ADXL372";
		int1-gpios = <&gpio1 5 0>;
	};
};
&spi2 {
	status = "disabled";
};