The hardware bug #39 on the GPIOTE in EVENT mode which gives a overconsumption of ~1mA even in idle mode on, kills the interest of having a low power chip, because the solution gived by Nordic which is to use the PORT interrupt mode on a pin with SENSE mode enabled, doesn't works when I use multiple interrupts with short transition signals. When I read the NRF_GPIO->IN, the signal may have has already gone down because I have lost some interrupts occurences.
Could you please recommend another way to deal with interrupts, still staying in low power ?
Yes you are correct, using the GPIOTE->IN events is high current. For low power applications, you should use the app_gpiote library to use the GPIOTE->PORT event most efficiently and is very low power. The functionality is as follows:
Thanks Stefan ! It works if interrupt signals are not too recurrent.
Hi, do you have a rough indication when the 3rd hardware revision will be available? 250us would cover my timing requirement, but 2ms during advertising might be tricky to deal with. Another option would have been if the RTC supported input capture, but according to the spec it does not. Thanks.
Latest update says the third revision engineering release hardware will be available in October. The production release is typically 3-4 months later.
Thanks Stefan :)