migrating from old sdk to ned sdk, spi.

RE: migrating from old sdk to ned sdk, spi.

shlomots — Mon, 02 Dec 2024 13:48:22 GMT

actually, this problem was allready solved, it was an hardware problem in the end.
thanks anyway.
-Shlomo

RE: migrating from old sdk to ned sdk, spi.

Priyanka — Mon, 02 Dec 2024 13:45:40 GMT

Hi,

From the code, you have
// Configure MISO (pin 11) as input with pull-up
gpio_pin_configure(gpio_dev, MISO_PIN, GPIO_INPUT | GPIO_PULL_UP);

So this will set MISO pin as pull up and not pull down. Also, I don't think CS pin is set as pull down since in order to set them as pull up or down, you need them as a GPIO input, but the CS pin is GPIO output.

Could you share your dts to see if they are set as GPIO pull up or down there?

-Priyanka

RE: migrating from old sdk to ned sdk, spi.

shlomots — Thu, 14 Nov 2024 12:46:43 GMT

[quote userid="107729" url="~/f/nordic-q-a/116283/migrating-from-old-sdk-to-ned-sdk-spi/510458"]Configuration on the pins is handled by the driver. You just need to set the pins you want to use, in the device tree.[/quote]

shouldnt these lines of code set miso for example as pull down?

RE: migrating from old sdk to ned sdk, spi.

Priyanka — Thu, 14 Nov 2024 12:02:50 GMT

Hi,

[quote user="shlomots"]1. how can I control the orc and irq values? [/quote]

.orc Can be set in devicetree. e.g. with a overlay like this:

&spi0 {

overrun-character = < 0xFF >;

};

irq can also be set in devicetree. But the default value is the recommended option.

[quote user="shlomots"]2. how can I control the miso to be pull_up or pin_down.[/quote]

Configuration on the pins is handled by the driver. You just need to set the pins you want to use, in the device tree.

-Priyanka

RE: migrating from old sdk to ned sdk, spi.

shlomots — Tue, 12 Nov 2024 08:58:36 GMT

Thank you for your response!
to be honest, this doesn't answer my question.
I am very much aware of the device tree and overlay files, but my question is about deeper in the process.
I want to see these values when I debug the code, ensure that the pin information for example actually reaches the the spi driver in code.
I think with some pictures I can explain better the process I went through.
this is the bus field returned by the devicetree macro.

the information is inside the config field but as you can see it is not reachable from at this point.
in order to reach it I had to look deeper inside the call stack and see what the proper casting is:
I found it is (const struct spi_nrfx_config *)
so when I cast it, I can look inside it:

if I open spi->p_reg->PSEL:

I can find the actual pin numbers I wrote in my device tree.
when I went further in the call stack into the transcieve function, I found where the freqauncy, bit order, mode and irq find .
I found these lines:

as you can see, in the call stack that starts at the transcieve function we got to these lines of configuration in which the orc, freqauncy an mode numbers go also into the p_reg.
(the mode is not configurable through the device tree but through the operation variable that goes to the devicetree macro).
so for conclusion I pretty much found the answers for my questions but I still have some followup questions:
1. how can I control the orc and irq values?
2. how can I control the miso to be pull_up or pin_down. this is another change I saw in the old code that I didn't see mentioned in the samples based on the new SDK. The way it was don't in the old code is this:

RE: migrating from old sdk to ned sdk, spi.

rbmarcus — Mon, 11 Nov 2024 20:19:05 GMT

What you're looking for are the DeviceTree and DeviceTree overlay files. Nordic has a GUI-based editor to help set this up for you. Generally you will have a base DeviceTree file for your board, and then an overlay to add your project-specific configurations. Here's a (possibly outdated) example of what your overlay would look like:

&spi2 {
        status = "okay";
        cs-gpios = <&gpio0 18 GPIO_ACTIVE_LOW>;
        pinctrl-0 = <&spi2_default>;
        pinctrl-1 = <&spi2_sleep>;
        pinctrl-names = "default", "sleep";
        mcp3201: mcp3201@0 {
                compatible = "vnd,spi-device";
                reg = <0>;
                spi-max-frequency = <1600000>;
                label = "mcp3201";
        };
};
&pinctrl {
        spi2_default: spi2_default {
                group1 {
                        psels = <NRF_PSEL(SPIM_SCK, 0, 19)>,
                                <NRF_PSEL(SPIM_MOSI, 0, 21)>,
                                <NRF_PSEL(SPIM_MISO, 0, 22)>;
                };
        };
        spi2_sleep: spi2_sleep {
                group1 {
                        psels = <NRF_PSEL(SPIM_SCK, 0, 19)>,
                                <NRF_PSEL(SPIM_MOSI, 0, 21)>,
                                <NRF_PSEL(SPIM_MISO, 0, 22)>;
                        low-power-enable;
                };
        };
};

You can see the sensor is defined along with your target parameters (frequency, chip select pin, etc.) and the SPI pins are redefined at the bottom for cases where you may not want to use the default SPI pin configuration associated with your board.

I recommend going through the Nordic Developer Academy beginner course before jumping in and setting up a project yourself. Zephyr is a lot more involved than the nRF5 SDK and you'll likely run into more problems that would have otherwise been answered by quick-start tutorials.