Usage of signal_state_change

[ilhamikivrak]

Thank you for such a good project.
I did not understand how to use of signal_state_change.
Without this, I can not set debounce time. But I am confused about when to trigger.

[dretay]

Hi @ilhamikivrak and thank you for the kind words! signal_state_change is usually called in your interrupt handler like here:

https://github.com/dretay/stm32l051c8t_pulsar_p2/blob/7fbe5d781fc84222f2337cef8077cb43ba45c166/Core/Src/Application.c#L151-L163

Basically you setup your GPIO pins to trigger an external interrupt, and in the interrupt handler call signal_state_change.

Hope the above helps, let me know if you're still seeing issues and good luck!

[ilhamikivrak]

Thank. you for the answer. Looking at your code, i could not see how you implement the interrupt state. Only for rising edge or for the both?

[ilhamikivrak]

Thank. you for the answer. Looking at your code, i could not see how you implement the interrupt state. Only for rising edge or for the both?

GPIO_InitStruct.Mode = GPIO_MODE_IT_RISING;
Ok. Thank you.

[dretay]

You should be able to open up the pin configuration in stm32cube to see exactly how it's configured:

https://github.com/dretay/stm32l051c8t_pulsar_p2/blob/master/stm32l051c8t_pulsar_p2.ioc

I just checked for you and I have mine setup as rising edge trigger... this is because if you want something like a "long press" to work then falling wouldn't ever work... and BOTH tends to just create noise if you're trying to debounce.

[ilhamikivrak]

With pulled up design, RISINGFALLING works best with me.