Reading ADXL355 via SPI with the nrf52840

RE: Reading ADXL355 via SPI with the nrf52840

Adrian1504 — Thu, 04 Apr 2024 11:42:06 GMT

Thank you so much! I tried it, and it is still not compiling. I guess I have to modify the _core and _spi files from the ADXL355 driver. I am getting an error with the #include<linux> files.

RE: Reading ADXL355 via SPI with the nrf52840

mk102 — Mon, 01 Apr 2024 17:00:23 GMT

Hi Adrian,

It does look like all the necessary files are present.
- You can add the .h and .c files under the src folder, and add them to CMakeLists.txt. (link)
- .yaml file goes under "dts/bindings" folder. (link)
- As per overlay.dts, I usually do it in a slightly different way and am not sure if his above implementation made for Raspberry Pi & Linux combination works or not. You can do it in a simpler way, just go through some .overlay files for nrf platform link1, link2 etc.,

RE: Reading ADXL355 via SPI with the nrf52840

Adrian1504 — Mon, 01 Apr 2024 09:18:01 GMT

Hi!

Thank you so much for the information. I read what you included. I think it will be super helpful.

I found this repository: https://github.com/puranjaymohan/GSoC-2021-DOC/tree/master/src
I think here are all the files that I need right? So i would just need to include this files into my project to have the drivers, and the binding?

Otherwise, how can I copy the binding from the 345 for example and work it? Is there a folder which I can enter to copy the file?

Again, thank you for the information!
Best regards, Adrian Lopez

RE: Reading ADXL355 via SPI with the nrf52840

mk102 — Tue, 26 Mar 2024 00:57:50 GMT

Hi Adrian,

ADXL355 isn't in the list of devices already included in Zephyr's device tree bindings.
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/build/dts/api/bindings.html#dt-vendor-adi

Therefore, I am afraid that you have to create the bindings yourselves.
https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-2-debugging/topic/troubleshooting-the-devicetree/

If ADXL355 interface is similar to 345, 362, 367 etc., maybe you can use them as reference.

As for samples that read data from accelerometer without using SPI, I assume the "device drivers" are already implemented and are hidden away. https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-7-device-driver-model/topic/device-driver-model-2/