30ms Active Low Pulse not recognized in GPIO Interrupt Falling Edge

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable

I am using AIR_GPIO_RegisterInterrupt(13, myCallBackFunc13, AIR_GPIO_TRIGGER_FALLING_EDGE );

and

void myCallBackFunc13() {

        iWasInturrupted = 13;

        AIR_BLE_SetDiscoverable(true);   

}

now my interrupt pulse is  active low  but only for about 20-30 ms.  I am unable to reconnect the BLE in time to send the event trigger data.

Does anyone know how long the AIR_BLE_SetDiscoverable(true) should be true for it to be sufficient to sent this info. 

I was hoping the easiest solution would be to add a delay in the myCallBackFunc13 to ensure there is enough time to do this.

Anyone experience anything like this? Any other software workaround to ensure this works smoothly? I guess because i designed the BLE device to be off always but for the interrupt times to save battery is the issue.

0 Likes
1 Solution
5 Replies
Anonymous
Not applicable

Hello Kava,

What example are you using from the SDK?

Thanks,

JT

0 Likes
Anonymous
Not applicable

This is from Anaren Air Atmosphere.based of the Broadcom SIP.

0 Likes
Anonymous
Not applicable

Thanks mwf_mmfae

0 Likes
Anonymous
Not applicable

I replied to your post on the Anaren Atmosphere forum.

Mininmum time GPIO intterupt needed to reconnect BLE | Anaren Atmosphere

0 Likes