Attachments (5) Download All
Nordic Case Info
  • Case ID: 340633
Options

SPI for nrf5340dk in ncsv2.8

KTH

nrfConnectSDK V2.8

Toolchain

Board: nrf5340dk

Hi, while compiling ncs-spi-master-slave-example , I am getting below errors

In function 'spi_init':
C:/Users/hello/spi/src/main.c:34:8: error: macro "GPIO_DT_SPEC_GET_BY_IDX_OR" requires 4 arguments, but only 3 given
34 | struct gpio_dt_spec spim_cs_gpio = MY_SPI_MASTER_CS_DT_SPEC;


In file included from C:/Users/hello/spi/src/main.c:11:
C:/ncs/v2.8.0/zephyr/include/zephyr/drivers/spi.h:213:9: error: 'GPIO_DT_SPEC_GET_BY_IDX_OR' undeclared (first use in this function)
213 | GPIO_DT_SPEC_GET_BY_IDX_OR(DT_BUS(spi_dev), cs_gpios, \

C:/Users/hello/spi/src/main.c:44:8: error: macro "GPIO_DT_SPEC_GET_BY_IDX_OR" requires 4 arguments, but only 3 given
44 | .cs = {.gpio = MY_SPI_MASTER_CS_DT_SPEC, .delay = 0},

C:/ncs/v2.8.0/zephyr/include/zephyr/drivers/spi.h:213:9: error: 'GPIO_DT_SPEC_GET_BY_IDX_OR' undeclared here (not in a function)
213 | GPIO_DT_SPEC_GET_BY_IDX_OR(DT_BUS(spi_dev), cs_gpios, \

Is it related to sdk version? Can anyone help to resolve ?

Parents
  • 0

    Hi,

    I recommend you go through the SPI lesson on our academy pages https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-5-serial-peripheral-interface-spi/ as well as the sysbuild exercise https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/topic/sysbuild-explained/.

    The unofficial sample that you're using will unfortunately not be maintained and upgraded to support any newer release and the latest version this sample was supported for is NCS older than v2.7.0 as far as I can see.

    The only resolution for you is to go through the two supplied links, understand the topics and apply the required changes to the sample you've based the application on.

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    Hi, We want a design where we want use 2 spi buses for 4 slaves.

    Fullscreen nrf.txt Download
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    &pinctrl {
    spi_master1_default: spi_master1_default {
    group1 {
    psels = <NRF_PSEL(SPIM_SCK, 1, 15)>,
    <NRF_PSEL(SPIM_MOSI, 1, 13)>,
    <NRF_PSEL(SPIM_MISO, 1, 14)>;
    };
    };
    spi_master1_sleep: spi_master1_sleep {
    group1 {
    psels = <NRF_PSEL(SPIM_SCK, 1, 15)>,
    <NRF_PSEL(SPIM_MOSI, 1, 13)>,
    <NRF_PSEL(SPIM_MISO, 1, 14)>;
    low-power-enable;
    };
    };
    spi_master0_default: spi_master0_default {
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Can you once check above attached file??

    Is there any zephyr spi sample example for nrf5340 for multiple slaves?

    Thankyou

  • 0 in reply to KTH

    Hi,

    KTH said:
    1. Can you explain how to get "custom netcore firmware with custom board changes"?

    I can't quite see why this is relevant, since you can always set the SPI up on the appcore (which is recommended) and simply send the data using BLE, for instance NUS over BLE.

    If I  understand you're issue correct, you're now struggling with adding BLE to the SPI applicaiton. In NCS v2.9.0 we're using "sysbuild" and "companion images" instead og child/parent-images which was previously used.

    What you need to do to get BLE is the same as is done in the BLE samples for nrf5340, where you build the hci_ipc companion component for the netcore through sysbuild. https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/ should explain it, but in case it does not you can see the sysbuild images here:https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/config_and_build/sysbuild/sysbuild_images.html 

    Enabling SB_CONFIG_NETCORE_HCI_IPC in sysbuild.conf adds the netcore image to the application.

    I strongly recommend you go through https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/topic/sysbuild-explained/ 

    KTH said:
    2. For our requirement do we need to add overlay for cpunet also?

    I believe the answer to this is within my answer to 1 as well.

    Apologies for not supplying you with a simple sample, but I would recommend you to go through any BLE sample in the SDK that is built for the nrf5340 and copy the settings and setup to your application.

    This will be a multi-image build, and you don't have to build for the netcore itself. By enabling the correct components (such as SB_CONFIG_NETCORE_HCI_IPC), the build system will drag in the required images to generate the hex that will flash both the appcore and netcore.

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    Hi Andreas,

    Thank you for your guidance in resolving bt issue, flashed hci_ipc sample to network core and our application to application core. Able to transfer data.

    Now we have our custom board where AD5940 is connected to nrf5340 through spi. Not able to read chip id of ad5940. Tried with the example above.

    Taken reference from Exercise 1 – Interfacing with a sensor over SPI and sample from github mentioned in the exercise, spi_example. Modified spi pins in overlay.

    Using ad5940library.

    Fullscreen 0523.main.c Download
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    /*
    * Copyright (c) 2024 Nordic Semiconductor ASA
    *
    * SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
    */
    #include <zephyr/kernel.h>
    #include <zephyr/logging/log.h>
    /* STEP 1.2 - Include the header files for SPI, GPIO and devicetree */
    #include <zephyr/device.h>
    #include <zephyr/devicetree.h>
    #include <zephyr/drivers/gpio.h>
    #include <zephyr/drivers/spi.h>
    #include "ad5940.h"
    LOG_MODULE_REGISTER(Lesson5_Exercise1, LOG_LEVEL_INF);
    #define DELAY_VALUES 1000
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    When we are tyring to read chipid, getting output as below

    *** Booting nRF Connect SDK v2.9.0-7787b2649840 ***
    *** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
    SPI : spi@9000
    00000000

  • 0 in reply to KTH

    Hi,

    Glad to hear you've managed to get past the BLE issues.

    I see you've commented out the error check to see if the device is ready (line 49). Do you check at any point if your device is set up? Could you add a check to see if you've enabled and initialized the device properly and that it is working? There are some lessons in the fundamentals course that should cover how to do this as well

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    Hi, 

    if (spi_dev == NULL)
    {
    LOG_ERR("Error: SPI device is not ready, err: %d", err);
    return 0;
    }

    This will check for whether the device is ready or not right?

  • 0 in reply to KTH

    Hi,

    DEVICE_DT_GET returns a pointer to the device object created for the instance, i.e a pointer to spi1 based on the DT_NODELABEL property of the device. See https://github.com/nrfconnect/sdk-zephyr/blob/bd1cf27b22f1003d58ecf4af81961722e1eb9949/include/zephyr/device.h#L254 or look the API up by going to definition within VS Code.

    The following

    Fullscreen
    1
    2
    3
    4
    5
    6
    spi_dev = DEVICE_DT_GET(DT_NODELABEL(spi1));
    if (spi_dev == NULL)
    {
    LOG_ERR("Error: SPI device is not ready, err: %d", err);
    return 0;
    }
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    returns a pointer. And the ONLY time you enter the If-check is if said pointer is NULL. This means that you never check if the device is ready.

    See https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-5-serial-peripheral-interface-spi/ for more information about setting up and checking a SPI peripheral.

    Kind regards,
    Andreas

Reply Children
  • 0 in reply to AHaug

    Hi,

    Now able to read AD5940 chip id.

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    struct spi_cs_control spi_cs = {
    .gpio = SPI_CS_GPIOS_DT_SPEC_GET(DT_NODELABEL(reg_my_spi_master)),
    .delay = 0,
    };
    static void spi_init(void)
    {
    /*get device address*/
    spi_dev = DEVICE_DT_GET(DT_NODELABEL(spi1_master));
    if (!device_is_ready(spi_dev))
    {
    printk("SPI master device not ready!\n");
    }
    if (!device_is_ready(spi_cs->gpio.port))
    {
    printk("SPI master chip select device not ready!");
    }
    printk("SPI : %s CS_GPIO: %s CS_PIN: %d\n", spi_dev->name, spi_cs->gpio.port->name, spi_cs->gpio.pin);
    printk("SPI device ready\n");
    }
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Thank you

      
  • 0 in reply to KTH

    Glad to hear that! :) 

    Kind regards,
    Andreas

Terms of service