I am using SDK 15.3, SES 4.30 and softdevice 132 with the ble_app_uart_c as the core functionality for my system.
I've read many dev support threads about this issue and most seem to point to using high accuracy with GPIOTE. I have high accuracy enabled. Attached is my code:
// GPIOTE is used for D_TEMP_IRQ input to know when a temperature conversion is completed
void in_pin_handler(nrf_drv_gpiote_pin_t pin, nrf_gpiote_polarity_t action) {
nrf_gpio_pin_toggle(LED_1); // Flash the led so we know something's happening
get_water_temp();
}
/**
* @brief Function for configuring: PIN_IN pin for input,
* and configures GPIOTE to give an interrupt on pin change. */
#define PIN_IN D_TEMP_IRQ
void gpio_init(void) {
ret_code_t err_code;
err_code = nrf_drv_gpiote_init();
APP_ERROR_CHECK(err_code);
nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(true); // true = high accuracy
in_config.pull = NRF_GPIO_PIN_NOPULL;
err_code = nrf_drv_gpiote_in_init(PIN_IN, &in_config, in_pin_handler);
APP_ERROR_CHECK(err_code);
d_temp_irq_enable();
}
// Functions to enable and disable interrupts on d_temp_irq
int d_temp_irq_enable(void) {
nrf_drv_gpiote_in_event_enable(PIN_IN, true);
// nrf_gpio_pin_toggle(LED_2); // Flash the led so we know something's happening
temp_probe_irq = true;
}
uint32_t d_temp_irq_disable(void) {
nrf_drv_gpiote_in_event_disable(PIN_IN);
// nrf_gpio_pin_toggle(LED_1); // Flash the led so we know something's happening
temp_probe_irq = false;
}
I have an external pullup on the d_temp_irq line that is triggering the GPIOTE. The system is consistently shutting down the GPIOTE interrupts within the approximately 400ms time period. This is the only GPIOTE interrupt I use.
The GPIOTE is setup early in the startup sequence via gpio_init() in main(void) code were I immediately configure the Dallas DS18B20 temperature sensor. The sensor is working up until the 400ms time wherein the interrupt stops working. I'm thinking that there is other code starting afterwards that is disabling the interrupt function.
Does the soft device, timers, or other BLE functions affect the GPIOTE operation? Here's my main(void) code:
int main(void) {
// Initialize.
log_init();
app_timers_init();
uart_init();
pins_buttons_leds_init();
gpio_init();
// pwm_init();
// saadc_init();
// saadc_sampling_event_init();
perfect_shower_init();
db_discovery_init();
power_management_init();
ble_stack_init();
gatt_init();
nus_c_init();
scan_init();
// Start execution.
printf("BLE UART central example started.\r\n");
NRF_LOG_INFO("BLE UART central example started.");
scan_start();
// Enter main loop.
for (;;) {
idle_state_handle();
}
}
/
I've disabled the pwm and saadc code to see if they're causing the problem... They aren't.
