Output pins configured in the Overlay, not showing in Devicetree view

I have the following setup in my overlay file:

relay {
compatible = "gpio-relay";
relay1: relay_1 {
gpios = <&gpio0 9 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>;
label = "DC Mtr Tension UP";
};
relay2: relay_2 {
gpios = <&gpio0 10 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>;
label = "DC Mtr Tension DN";
};
};

I have created the gpio-relay.yaml and placed it in the gpio binding directory.

The project builds with no issue, and the pins appear in the DTS output, but these new pins do not show up in the devicetree overlay view.

Why is that?

Thanks,

Stephen

Parents
  • Hi Stephen,

    Please clarify if the board build and work as it should ? And it's only the Devicetree view GUI interface having trouble displaying ? 

    You mentioned overlay file. Did you create an .overlay file or it's the .yaml you were writing about ? 

  • Good Morning,

    The board builds with no issue.  I am just configuring the Inputs and Outputs right now, so not sure on functionality. (No code for that yet)

    I did create the .overlay file and the above code is in it.  I'm asking why the changes in the overlay show up in the DTS, but not the Devicetree view GUI.

    So yes, just the Devicetree view GUI interface is having trouble displaying.

    Stephen

  • Hi Stephen, 
    Sorry for the late response. I tried to reproduce the issue but couldn't . 
    Could you please make a minimal project or modify a sample and include the overlay file to show the problem ? 
    If I can reproduce the issue in-house I can report it to the team. 

  • Good day,

    We resolved another issue on one of my other threads that explained this.  I'm using a Ezurio DVK and we found that it has to use it's own SDK that is no longer in sync with NRF SDK.  Because of this, the Kconfig/Device tree is not compatible with Python versions of the older SDK.

    Stephen

Reply
  • Good day,

    We resolved another issue on one of my other threads that explained this.  I'm using a Ezurio DVK and we found that it has to use it's own SDK that is no longer in sync with NRF SDK.  Because of this, the Kconfig/Device tree is not compatible with Python versions of the older SDK.

    Stephen

Children