SPI Communication SDK 2.4.0 nRF5340 DK

RE: SPI Communication SDK 2.4.0 nRF5340 DK

Sigurd — Mon, 19 Aug 2024 19:36:46 GMT

Hi!

Could you elaborate a bit more on this. How many bytes are you sending/receiving, how are you meausering the delay, could you show the code that you are using for the write and read functions, etc

RE: SPI Communication SDK 2.4.0 nRF5340 DK

Paul M. — Mon, 19 Aug 2024 14:36:55 GMT

Hi Sigurd,

we were able to get the spi communication to run. We redid everything following the Zephyr SPI API step by step.

However, our sensor which we want to use requires a minimum delay time between write and read functions of 1 ms. Is there a way to do that using the spi_transceive_dt function? We were able to do it using the seperate write and read functions, but I'd rather use the spi_transceive_dt function.

Best regards,

Paul

RE: SPI Communication SDK 2.4.0 nRF5340 DK

Sigurd — Mon, 12 Aug 2024 12:31:56 GMT

Hi!

[quote user="Paul M."]it keeps shooting our errors if I do that.[/quote]

What errors are you getting? With spi4 you don't get any errors?

did you set spi1_default and spi1_sleep to use P1.13 for MOSI, P1.14 for MISO and P1.15 for SCK ?

RE: SPI Communication SDK 2.4.0 nRF5340 DK

Paul M. — Fri, 09 Aug 2024 16:14:49 GMT

I may need to add that I did not create the overlay file with the following as it was told in the tutorial:

&spi1 {
        compatible = "nordic,nrf-spi";
        status = "okay";
        cs-gpios = <&gpio0 18 GPIO_ACTIVE_LOW>;
        pinctrl-0 = <&spi1_default>;
        pinctrl-1 = <&spi1_sleep>;
        pinctrl-names = "default", "sleep";
        gendev: gendev@0 {
                compatible = "vnd,spi-device";
                reg = <0>;
                spi-max-frequency = <1600000>;
                label = "GenDev";
        };
};

I tried doing that, but (I did change spi1 to spi4) it keeps shooting our errors if I do that.

Instead, I used spi4 directly.