about 5340 gpiote issue

[hbenchoi]

Hi.

i am using 5340 + ncs 2.0.2. and gpiote nrfx drvier.

i used gpiote for count encoder

encoder clock speed is about 2.5k and input pint is 2 gpiote pin.

gpiote polarity is toggle.

gpiote pin number : A is 46, B is 47

pin B (number 47) is working good. but pin A (number 46) is detect slow less a half speed than pin A.

last test, I used pin 22,36 it work.

is there some limit about pin 46?

under below, code and screenshot

nrfx_gpiote_in_config_t config =
        {
            .sense = NRF_GPIOTE_POLARITY_TOGGLE,
            .pull = NRF_GPIO_PIN_NOPULL,
            .is_watcher = false,
            .hi_accuracy = true,
            .skip_gpio_setup = false};
    err_code = nrfx_gpiote_in_init(A_PIN, &config, gpiote_handler);
    if (err_code != NRFX_SUCCESS)
    {
        LOG_INF("gpiote in init failed : %x", err_code);
        return;
    }
    err_code = nrfx_gpiote_in_init(B_PIN, &config, gpiote_handler);
    if (err_code != NRFX_SUCCESS)
    {
        LOG_INF("gpiote in init failed : %x", err_code);
        return;
    }
static void gpiote_handler(nrfx_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{
    if(pin == A_PIN)
    {
       ...
    }
    else
    {
        ...
    }
}

/cfs-file/__key/communityserver-discussions-components-files/4/2275.bmp

[Einar Thorsrud]

Hi,

I do not see any reason why these pins should be different seen from the nRF. Are there some other differences in these pins on your custom HW, or perhaps you do some other code changes while changing the pins?

Also, it might not be a good idea to get interrupts for every pin change here, as that will keep the CPU quite busy. So I would consider if you could use the QDEC peripheral to achieve what you want.

[hbenchoi]

thank reply.

I considered QDEC peripheral but it it not enough speed to detect all encoder.

I tried , but QDEC is missed some encoder counter.

I didn't change code previous used pin 22, 36, in Code, just change pin number.

If doesn't have any limit, I try to find hw level.

now I changed pin number 46 -> 41, it work fine.

[Einar Thorsrud]

I am not able to explain this, then. It would be interesting to know more about the HW you are using.

[hbenchoi]

when test this one, in hw level. input line connect both 46 & 41 line. (short 46 & 41)

I checked same freq clock inputline, 46, 41

so i think it is not hw issue. under below prj.conf

#LOG
CONFIG_LOG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_LOG_BACKEND_RTT=y
#CONFIG_LOG_MODE_DEFERRED=y

#UART
CONFIG_UART_ASYNC_API=y
CONFIG_UART_INTERRUPT_DRIVEN=y

#GPIO
CONFIG_NFCT_PINS_AS_GPIOS=y

[Einar Thorsrud]

I see. One thing sticks out, and that is that for instance 46 (P1.14) is configured as SPI4 MISO in  zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340_cpuapp_common-pinctrl.dtsi. That should not cause problems when it is not used, but you could remove it and see.