about 5340 gpiote issue

RE: about 5340 gpiote issue

hbenchoi — Mon, 28 Nov 2022 00:22:04 GMT

I remove that, not changed.

thank you reply.

if any have not issue about 46pin, it might be hw level problem. now I will closed ticket.

later, If i find cause problem,I will reply comment.

RE: about 5340 gpiote issue

Einar Thorsrud — Fri, 25 Nov 2022 13:42:17 GMT

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.

RE: about 5340 gpiote issue

hbenchoi — Fri, 25 Nov 2022 08:23:17 GMT

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

RE: about 5340 gpiote issue

Einar Thorsrud — Wed, 23 Nov 2022 14:57:27 GMT

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

RE: about 5340 gpiote issue

hbenchoi — Wed, 23 Nov 2022 00:08:22 GMT

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.

RE: about 5340 gpiote issue

Einar Thorsrud — Tue, 22 Nov 2022 12:55:12 GMT

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.