Defining IO pin in zephyr

RE: Defining IO pin in zephyr

AHaug — Thu, 23 Jan 2025 13:47:29 GMT

Hi,

Apologies for the response time.

[quote user="cmag"]I have found direct pin control samples in Internet, [/quote]

Could you share a link to this sample? You might be missing some configurations if there's a mismatch between the sample and the SDK version you're using

Kind regards,
Andreas

RE: Defining IO pin in zephyr

cmag — Wed, 15 Jan 2025 13:20:02 GMT

For the red LEDs I have:
hwledred linked to ledred and referenced in C as:

#define LED_RED_NODE DT_ALIAS(ledred)
static const struct gpio_dt_spec ledRed = GPIO_DT_SPEC_GET(LED_RED_NODE, gpios);

I expected that the analogous for WP should be:
hwmemwp linked to memwp and referenced in C as:

#define WP DT_ALIAS(memwp)
const struct gpio_dt_spec memWP = GPIO_DT_SPEC_GET_OR(WP, gpios, {0});

Should work in the same way.
But I am obviously missing something.
I have found direct pin control samples in Internet, but when I try them I get a long chain of errors concerning macros calling more macros.
For this I am asking of a simple example of a DTS defining a pin and the C file referencing it.

RE: Defining IO pin in zephyr

AHaug — Wed, 15 Jan 2025 13:01:56 GMT

Hi,

In the zephyr,user node you've written "mew_wp". Shouldn't this also be mem_wp or memwp depending on the alias you decided to use??

Have you defined this device binding somewhere? I can't see the device binding for any memwp within the SDK

Kind regards,
Andreas