Output driver not working for P1.13 on nRF5340 DK

RE: Output driver not working for P1.13 on nRF5340 DK

AHaug — Tue, 23 Jan 2024 14:59:39 GMT

Ah, I see. Yes, this is as you've concluded in your discussion, i.e that the GPIO has been assigned to other nodes that is not "free to use" since it is predefined to be used to something else on the board. Another example is of course the GPIO's that are connected to NFC, buttons and LEDS. A build error is triggered if the configuration has faulty syntax, but it does not trigger a build error in this case since it is "valid" to overlay a GPIO pin select

The best way to see the predefined assignments (in combination with examining the PS) is to see the board files. Board files are found under \zephyr\boards\arm, or in the extension

Kind regards,
Andreas

RE: Output driver not working for P1.13 on nRF5340 DK

Aaron F — Tue, 23 Jan 2024 14:21:56 GMT

I am talking about this, with the squiggle under the pin number 13.

RE: Output driver not working for P1.13 on nRF5340 DK

AHaug — Tue, 23 Jan 2024 14:13:47 GMT

I will just add here that I second Anthony's remarks and tips. Everything is correct and answers your questions, so thank you for your input Anthony

For now I will mark this case as verified, and please feel free to open new cases if new topics comes up

Kind regards,
Andreas

RE: Output driver not working for P1.13 on nRF5340 DK

AHaug — Tue, 23 Jan 2024 14:11:22 GMT

[quote user="Aaron F"]

On further investigation, I see that the overlay view in VS Code does have a squiggle underline for the conflict and does provide a pop-up saying there is a conflict when hovering over the underlined value.

I am going to change this ticket to a feature request. Would it be possible to have this conflict cause a build failure, or is it considered valid to do this?

[/quote]

Are you referring to yellow squiggly lines as shown in this image?

Regarding the feature request we would prefer you raise the request in another ticket dedicated with that topic.

Kind regards,
Andreas

RE: Output driver not working for P1.13 on nRF5340 DK

Aaron F — Mon, 22 Jan 2024 17:02:23 GMT

Ah, thank you for that help. The devicetree view gives a view similar to the pin configurator that other vendors provide. It is much easier to see all the pin assignments and conflicts there. That is what I've been looking for.

The files in the build dir (both the .dts and .h) seem to contain all the information, but they don't seem easy to parse in a meaningful way.

I don't know anyone currently looking for Nordic/Zephyr work.

RE: Output driver not working for P1.13 on nRF5340 DK

Anthony Ambuehl — Mon, 22 Jan 2024 16:53:06 GMT

Two tips, not sure if either is exactly what you want:

* In Visual Studio Code in the nRF Connect extension there is an Action called "Devicetree" which allows exploring the device tree files.

* All the devicetree configuration ends up in

build_dir/zephyr/include/generated/device_tree_generated.h

or for cpunet in

build_dir/hci_rpmsg/zephyr/include/generated/device_tree_generated.h

these files are big and not exactly pretty but I believe they have everything determined from devicetree in it.

BTW, if you know anyone looking for a developer experienced with zephyr and Nordic's SDK, I'm currently looking for new clients:

www.linkedin.com/.../

RE: Output driver not working for P1.13 on nRF5340 DK

Aaron F — Mon, 22 Jan 2024 16:41:31 GMT

In the final build/zephyr/zephyr.dts I see that spi4 also has a claim on 0x2D (i.e. P1.13). However, spi4 is disabled in this configuration. That spi4 configuration must be coming from .dtsi files. I wish there was an easier way to view all the pin assignments.

RE: Output driver not working for P1.13 on nRF5340 DK

Aaron F — Mon, 22 Jan 2024 16:36:53 GMT

I am going to change this ticket to a feature request. Would it be possible to have this conflict cause a build failure, or is it considered valid to do this?

RE: Output driver not working for P1.13 on nRF5340 DK

Anthony Ambuehl — Mon, 22 Jan 2024 16:36:23 GMT

Assuming your board is based on nrf5340dk, I noticed in boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet-pinctrl.dtsi

spi0_default: spi0_default {
group1 {
psels = <NRF_PSEL(SPIM_SCK, 1, 15)>,
<NRF_PSEL(SPIM_MISO, 1, 14)>,
<NRF_PSEL(SPIM_MOSI, 1, 13)>;
};

This means the pins are assigned to cpunet and settings from the application process wlll not be used.

RE: Output driver not working for P1.13 on nRF5340 DK

Aaron F — Mon, 22 Jan 2024 16:31:29 GMT

Ah, never mind. I have found the source of the problem:

    uart3_default: uart3_default {
        group1 {
            psels = <NRF_PSEL(UART_TX, 1, 12)>,
                <NRF_PSEL(UART_RTS, 1, 10)>;
        };
        group2 {
            psels = <NRF_PSEL(UART_RX, 1, 11)>,
                <NRF_PSEL(UART_CTS, 1, 13)>;
            bias-pull-up;
        };
    };

It seems that this must be affecting OUT_OVERRIDE, DIR_OVERRIDE or both. That is my problem.