2 pin connections to control the key
There are a few nRF52 anomalies that I regularly encounter which are decrease radio performance with high current or leaving floating P0.25 an P0.26, and Compile flags needed that make P0.09 and P0.10 useless because they are the NFC coil ones. So can't find any other reason.

If P0.13 is pulled low, presumably that's what your interrupting from, but why then configure P0.15 an output-high? P0.15 could be pulled low and you just set the interrupt to occur to only on one of them?

(Nrf5 SDK pin_change_int example)

    err_code = nrf_drv_gpiote_init();

    nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(true);
    in_config.pull = NRF_GPIO_PIN_PULLUP;

    err_code = nrf_drv_gpiote_in_init(PIN_IN, &in_config, in_pin_handler);

    nrf_drv_gpiote_in_event_enable(PIN_IN, true);

I normally use the App_button to do my debounce, and usually do a few other things to detect short / long / double / triple presses.

Messages In This Thread
RE: 2 pin connections to control the key - by Independent_Contact - 01-10-2020, 11:48 AM

Forum Jump:

Users browsing this thread: 1 Guest(s)