I currently have a problem with the gpiote setup. I'm using it to detect an interrupt from mma8652 accelerometer.
here is an annotated version with the key portions of the code.
pin_event_handler()
{
NRF_LOG_INFO("\r\n PIN 26 triggered \r\n");
NRF_LOG_FLUSH();
}
static void accel_intrpt_pin_config()
{
nrf_drv_gpiote_in_config_t config = GPIOTE_CONFIG_IN_SENSE_HITOLO(true);
config.pull = NRF_GPIO_PIN_PULLUP;
err_code = nrf_drv_gpiote_in_init(26, &config, pin_event_handler);
APP_ERROR_CHECK(err_code);
nrf_drv_gpiote_in_event_enable(26, false);
}
main()
{
// basic inits
...
while (1)
{
...
// wait for interrupt from accelerometer to trigger pin 26 -- I never get past this
while(nrf_drv_gpiote_in_is_set(26) == 1)
{
nrf_delay_ms(1000); // check every second just to be sure we didn't freeze early
NRF_LOG_INFO("\r\n PIN 26 value: %u \r\n",nrf_drv_gpiote_in_is_set(26));
NRF_LOG_FLUSH();
}
}
}
this is the ending uart output after which nothing happens
APP:INFO:
PIN 26 value: 1
APP:INFO:
PIN 26 value: 1
APP:INFO:
PIN 26 value: 0
so I see the pin changes but I never get to my trigger comment in the event handler. I'm sure I'm missing something but I haven't really been able to figure out what. When it reached the point in the code where a change was detected, the whole things stops and when I try to flash the code again to restart it, it freezes at the accelerometer register setup and I have to disconnect to remove the power to the MCU and re-connect to get it going again.
I was using the pin_change_int example to structure this. This wasn't a very complicated thing so I figured that was all I needed. then I was looking on other solved question and I saw all these other things on interrupt and priorities. Is that necessary?
