RE: Send AT commands on button press on nRF9160dk

Jagruti — Tue, 12 Nov 2019 12:29:57 GMT

Hello,

Thank you for the reply. I will try what you have suggested.

Yes I realized that app_socket_start() is called twice as ISR is called on both press and release. I observed that.

RE: Send AT commands on button press on nRF9160dk

MJD093 — Tue, 12 Nov 2019 11:41:07 GMT

Try this instead, remove the app_socket_start() function from your callback. This shouldn't be here as an ISR should be returned from as quickly as possible. From my experience with ISRs in Zephyr, trying to run a function from the ISR will hang.

Place a boolean flag in the ISR for button_pressed = true, place a while loop in your main function that can run a k_sleep() delay (reduce idle current by yielding main thread via sleep). In the while loop place a function that can react to the boolean button_pressed. Something like app_socket_start(button_pressed), where inside app_socket_start() is a boolean if-true check. Remember to clear the ISR flag when completing app_socket_start().

Side note:

You do realise you are calling app_socket_start() twice right? I helped you set up that ISR last week but you have continued to use it in rising and falling edge operation. That will call the ISR when you press and release the button, running the code for app_socket_start() and the LED with each press and de-press.