Struggling for several days to get SPI working w/ Zephyr

RE: Struggling for several days to get SPI working w/ Zephyr

bmalchow — Mon, 27 Feb 2023 16:04:48 GMT

I did, it works well and reliably. All code is pasted in this thread. Used git post that was recommended as well. Changed these lines as well:

#define MY_SPI_MASTER DT_NODELABEL(canspi)
#define MY_SPI_DEVICE DT_NODELABEL(mcp2517fd)

spi_dev = DEVICE_DT_GET(MY_SPI_MASTER);

RE: Struggling for several days to get SPI working w/ Zephyr

ril3y — Sat, 25 Feb 2023 20:33:30 GMT

Did you end up getting this code working? I am going to use the same chip and was curious if you had posted your code anywhere? I would love to take a look at it.

RE: Struggling for several days to get SPI working w/ Zephyr

Øyvind — Thu, 02 Feb 2023 09:58:42 GMT

Thanks for sharing, bmalchow ! Happy to hear that you found the solution.

RE: Struggling for several days to get SPI working w/ Zephyr

bmalchow — Mon, 30 Jan 2023 14:37:20 GMT

After realizing I made some dumb mistakes, I have it linking. Figured I'd post in case someone else wants some snippets. Thanks again!

can_spi: &arduino_spi {
{
    mcp2517fd: spi-dev-a@0{
        compatible = "spi-device";
        spi-max-frequency = < 500000 >;
        reg = < 0 >;
    };
};
#define CAN_SPI DT_NODELABEL(can_spi)
#define CAN_SPI_CS DT_NODELABEL(mcp2517fd)

LOG_MODULE_REGISTER(spi_interface, LOG_LEVEL_ERR);

static const struct device * spi_dev;

static struct spi_buf tx_spi_buffer[1];
static struct spi_buf rx_spi_buffer[1];

struct spi_cs_control spim_cs = {
    .gpio = DEVICE_DT_GET_ANY(CAN_SPI_CS),
    .delay = 0,
};

static struct spi_config spi_cfg = {
    .frequency = 500000,
    .operation = SPI_OP_MODE_MASTER | SPI_TRANSFER_MSB | SPI_WORD_SET(8) | SPI_LINES_SINGLE | SPI_MODE_CPOL | SPI_MODE_CPHA,
    .cs = &spim_cs
};

RE: Struggling for several days to get SPI working w/ Zephyr

bmalchow — Fri, 27 Jan 2023 20:40:20 GMT

It looks like I missed some steps in West. I think this can be closed and I have to go back and familiarize myself with the initial env. setup. Thanks for the SPI example though! It was useful.

RE: Struggling for several days to get SPI working w/ Zephyr

bmalchow — Fri, 27 Jan 2023 16:06:47 GMT

Forgot to add this as it shows where the error is being generated:

struct spi_cs_control spim_cs = {
    .gpio = SPI_CS_GPIOS_DT_SPEC_GET(DT_NODELABEL(mcp2517fd)),
    .delay = 0,
};

RE: Struggling for several days to get SPI working w/ Zephyr

bmalchow — Fri, 27 Jan 2023 16:05:50 GMT

Hi Øyvind,

The sample project has been helpful! I think I may have found an issue though. I choose nrf52833dk_nrf52833 as my board as that is my dev board. When making my overlay, all the references, such as &spi2, are referencing nrf52dk_nrf52832.dts. Thi pins specified do not match the dev board I have so could this be a bug with nRF Connect? I figured I'd ask.

Aside from that, I cannot get the example to compile I am getting this now:

zephyr\include\zephyr\device.h:83:41: error: '__device_dts_ord_DT_N_NODELABEL_mcp2517fd_BUS_P_cs_gpios_IDX_DT_N_NODELABEL_mcp2517fd_REG_IDX_0_VAL_ADDRESS_PH_ORD' undeclared here (not in a function)
   83 | #define DEVICE_NAME_GET(dev_id) _CONCAT(__device_, dev_id)
      |                                         ^~~~~~~~~
C:\Users\Bmalch01\ncs\v2.2.0\zephyr\include\zephyr\device.h:209:37: note: in expansion of macro 'DEVICE_NAME_GET'
209 | #define DEVICE_DT_NAME_GET(node_id) DEVICE_NAME_GET(Z_DEVICE_DT_DEV_ID(node_id))
      |                                     ^~~~~~~~~~~~~~~
C:\Users\Bmalch01\ncs\v2.2.0\zephyr\include\zephyr\device.h:226:34: note: in expansion of macro 'DEVICE_DT_NAME_GET'
226 | #define DEVICE_DT_GET(node_id) (&DEVICE_DT_NAME_GET(node_id))

It cannot get a reference to the CS pin. I had to add some tweaks to get the overlay to not have errors. I'll highlight those:

&pinctrl {
    spi0_default: spi0_default {
        group1 {
            psels = <NRF_PSEL(SPIM_SCK, 0, 31)>,
                    <NRF_PSEL(SPIM_MOSI, 0, 30)>,
                    <NRF_PSEL(SPIM_MISO, 0, 29)>;
        };
    };

    spi0_sleep: spi0_sleep {
        group1 {
            psels = <NRF_PSEL(SPIM_SCK, 0, 31)>,
                    <NRF_PSEL(SPIM_MOSI, 0, 30)>,
                    <NRF_PSEL(SPIM_MISO, 0, 29)>;
            low-power-enable;
        };
    };
};

can_spi: &spi0 {
    compatible = "nordic,nrf-spi";
    status = "okay";
    pinctrl-0 = <&spi1_default>;
    pinctrl-1 = <&spi1_sleep>;
    cs-gpios = <&gpio0 28 GPIO_ACTIVE_LOW>;
    mcp2517fd: spi-dev-a@0 {
        //added this
 compatible = "spi-device";
        reg = <0>;
 //added this
        spi-max-frequency = < 500000 >;
    };
};

RE: Struggling for several days to get SPI working w/ Zephyr

bmalchow — Wed, 25 Jan 2023 21:35:57 GMT

Oh, I missunderstood. Yes, it is outputting a '0', which is success. I am printing over UART to NRF console. I'll have a look and get back. Thanks!

RE: Struggling for several days to get SPI working w/ Zephyr

Øyvind — Wed, 25 Jan 2023 15:31:31 GMT

Ben,

[quote user="bmalchow"]-Are you referring to the .ninja_log? Will provide when certain.[/quote]

No, I am referring to the logger module that you are using in your code:

    if (ret < 0)
    {
        LOG_ERR("err code %d", ret);
    }

Please see the documentation on Logging API. This will allow you to print issues into a UART terminal through the nRF52833DK.

Have you tried going through our nRF Connect SDK Fundamentals course in DevAcademy?

You could also look at this SPI master slave sample which my colleague Torbjørn has made.

Kind regards,
Øyvind

RE: Struggling for several days to get SPI working w/ Zephyr

bmalchow — Wed, 25 Jan 2023 13:38:28 GMT

Hi Øyvind,

-Are you referring to the .ninja_log? Will provide when certain.

-SDK version is 2.2.0

--Yes, started with 'hello world' for nRF52833. Have 802.15.4, GPIO output, GPIO inputs w/ interrupts, and GPIOTE working

Thank you!

-Ben

RE: Struggling for several days to get SPI working w/ Zephyr

Øyvind — Wed, 25 Jan 2023 13:25:47 GMT

Hello,

Do you get anything in the log output?
- Can you please provide it here?
What version of nRF Connect SDK are you working on?
- Have you based you application on a specific sample?

Kind regards,
Øyvind