adxl362 sample not compiling

RE: adxl362 sample not compiling

PeterC — Wed, 29 Apr 2020 13:20:27 GMT

Hi Jon,

So I finally have the adxl362 working. I had downloaded the latest version of the SDK in a new directory for testing but even after loading the adxl362 sample project from the new directory SES was still compiling the project using the older drivers in the old directory...

Even though my "old" version of the SDK was a clean install from February there has been some changes since then which prevented the setup below from working.

So here are the files that work for the DK board using SPI3 (pins 10 through to 12 with pin 13 as the cs). I am not using the interrupt pin at the moment so needed to comment out the trigger code for the sample to output data.

Thanks for your help.

nrf9160_pca10090ns.overlay file :

&spi3 {
compatible = "nordic,nrf-spim";
status = "okay";
sck-pin = <10>;
mosi-pin = <11>;
miso-pin = <12>;
cs-gpios = <&gpio0 13 0>;

adxl362@0 {
compatible = "adi,adxl362";
label = "ADXL362";
spi-max-frequency = <8000000>;
reg = <0>;
int1-gpios = <&gpio0 9 0>;
};
};

config file for DK using SPI 3

CONFIG_SENSOR=y
CONFIG_ADXL362=y
CONFIG_ADXL362_TRIGGER_GLOBAL_THREAD=y
CONFIG_ADXL362_INTERRUPT_MODE=1
CONFIG_ADXL362_ABS_REF_MODE=1

# SPI
CONFIG_SPI=y
CONFIG_SPI_3_NRF_SPIM=y
CONFIG_SPI_3=y 
CONFIG_SPI_NRFX=y

RE: adxl362 sample not compiling

Jon Helge — Wed, 29 Apr 2020 08:23:15 GMT

I tried this now (only compiling) on NCS 1.2.0. I put the following into a file called nrf9160_pca10090ns.overlay in the adxl362 sample folder. The .overlay file name is important it needs to match the board. This now compiles without error on my setup.

&spi3 {
compatible = "nordic,nrf-spim";
status = "okay";
sck-pin = <3>;
mosi-pin = <4>;
miso-pin = <5>;
cs-gpios = <&gpio0 8 0>;

adxl362@0 {
compatible = "adi,adxl362";
label = "ADXL362";
spi-max-frequency = <8000000>;
reg = <0>;
int1-gpios = <&gpio0 9 0>;
};
};

RE: adxl362 sample not compiling

PeterC — Tue, 28 Apr 2020 23:24:21 GMT

I tried the different formatting without success.

Thanks for you input though.

RE: adxl362 sample not compiling

PeterC — Tue, 28 Apr 2020 22:38:55 GMT

But I will try that different formatting,

Cheers

RE: adxl362 sample not compiling

PeterC — Tue, 28 Apr 2020 22:20:01 GMT

Thanks,

I am trying to add a adxl362 to the DK board as I am doing all my development on that, I will be transferring the code to the thingy for field testing though.

RE: adxl362 sample not compiling

Jon Helge — Tue, 28 Apr 2020 22:08:17 GMT

Hi, not sure if it will be of any help but I noticed that the .dts for the Thingy:91 (nrf9160_pca20035) which uses the ADXL362 use a bit different .dts formatitng than your overlay. github.com/.../nrf9160_pca20035_common.dts

RE: adxl362 sample not compiling

PeterC — Tue, 28 Apr 2020 21:35:46 GMT

Thanks for your reply,

That did clear that error, but now I have another error in adxl362.c

"CONFIG_ADXL362_DEV_NAME undeclared":

DEVICE_AND_API_INIT(adxl362, CONFIG_ADXL362_DEV_NAME, adxl362_init,
&adxl362_data, NULL, POST_KERNEL,
CONFIG_SENSOR_INIT_PRIORITY, &adxl362_api_funcs);

If I replace CONFIG_ADXL362_DEV_NAME with "SPI_3" (a guess at this stage!) the error moves to "adxl362_config undeclared"

What am I missing to set this up properly?

RE: adxl362 sample not compiling

Jon Helge — Tue, 28 Apr 2020 21:13:36 GMT

Have you tried the following?

device_get_binding("ADXL362");