INT2 working but INT1 is not

RE: INT2 working but INT1 is not

AHaug — Fri, 28 Jun 2024 13:09:24 GMT

Hi,

Apologies for the long response time.

Could you please check if you're able to reproduce this on a nRF5340DK?

I've not been able to reproduce the behavior.

Kind regards,
Andreas

RE: INT2 working but INT1 is not

IvanR — Thu, 20 Jun 2024 07:00:12 GMT

This is an excerpt from zephyr.dts where P0.11 is referenced. I can't see what's colliding.

	buttons {
		compatible = "gpio-keys";
		button0: button_0 {
			gpios = < &gpio0 0x17 0x11 >;
			label = "Push button 1";
			zephyr,code = < 0xb >;
		};
		button1: button_1 {
			gpios = < &gpio1 0xd 0x11 >;
			label = "Push button 2";
			zephyr,code = < 0x2 >;
		};
		button2: button_2 {
			gpios = < &gpio0 0x8 0x11 >;
			label = "Push button 3";
			zephyr,code = < 0x3 >;
		};
		button3: button_3 {
			gpios = < &gpio0 0x9 0x11 >;
			label = "Push button 4";
			zephyr,code = < 0x4 >;
			status = "disabled";
		};
		int1: int_1 {
			status = "okay";
			gpios = < &gpio0 0xb 0x0 >;
			label = "interrupt 1";
		};
		int2: int_2 {
			status = "okay";
			gpios = < &gpio0 0x9 0x0 >;
			label = "interrupt 2";
		};
	};
	arduino_header: connector {
		compatible = "arduino-header-r3";
		#gpio-cells = < 0x2 >;
		gpio-map-mask = < 0xffffffff 0xffffffc0 >;
		gpio-map-pass-thru = < 0x0 0x3f >;
		gpio-map = < 0x0 0x0 &gpio0 0x4 0x0 >, < 0x1 0x0 &gpio0 0x5 0x0 >, < 0x2 0x0 &gpio0 0x6 0x0 >, < 0x3 0x0 &gpio0 0x7 0x0 >, < 0x4 0x0 &gpio0 0x19 0x0 >, < 0x5 0x0 &gpio0 0x1a 0x0 >, < 0x6 0x0 &gpio1 0x0 0x0 >, < 0x7 0x0 &gpio1 0x1 0x0 >, < 0x8 0x0 &gpio1 0x4 0x0 >, < 0x9 0x0 &gpio1 0x5 0x0 >, < 0xa 0x0 &gpio1 0x6 0x0 >, < 0xb 0x0 &gpio1 0x7 0x0 >, < 0xc 0x0 &gpio1 0x8 0x0 >, < 0xd 0x0 &gpio1 0x9 0x0 >, < 0xe 0x0 &gpio1 0xa 0x0 >, < 0xf 0x0 &gpio1 0xb 0x0 >, < 0x10 0x0 &gpio1 0xc 0x0 >, < 0x11 0x0 &gpio1 0xd 0x0 >, < 0x12 0x0 &gpio1 0xe 0x0 >, < 0x13 0x0 &gpio1 0xf 0x0 >, < 0x14 0x0 &gpio1 0x2 0x0 >, < 0x15 0x0 &gpio1 0x3 0x0 >;
		phandle = < 0x8 >;
	};
	arduino_adc: analog-connector {
		compatible = "arduino,uno-adc";
		#io-channel-cells = < 0x1 >;
		io-channel-map = < 0x0 &adc 0x0 >, < 0x1 &adc 0x1 >, < 0x2 &adc 0x2 >, < 0x3 &adc 0x3 >, < 0x4 &adc 0x4 >, < 0x5 &adc 0x5 >;
	};
	gpio_fwd: nrf-gpio-forwarder {
		compatible = "nordic,nrf-gpio-forwarder";
		status = "okay";
		uart {
			status = "disabled";
			gpios = < &gpio0 0xb 0x0 >, < &gpio0 0xa 0x0 >;
		};
	};
				i2c2: i2c@b000 {
				compatible = "nordic,nrf-twim";
				#address-cells = < 0x1 >;
				#size-cells = < 0x0 >;
				reg = < 0xb000 0x1000 >;
				clock-frequency = < 0x186a0 >;
				interrupts = < 0xb 0x1 >;
				easydma-maxcnt-bits = < 0x10 >;
				status = "disabled";
			};
			spi2: spi@b000 {
				compatible = "nordic,nrf-spim";
				#address-cells = < 0x1 >;
				#size-cells = < 0x0 >;
				reg = < 0xb000 0x1000 >;
				interrupts = < 0xb 0x1 >;
				max-frequency = < 0x7a1200 >;
				easydma-maxcnt-bits = < 0x10 >;
				status = "disabled";
			};
			uart2: uart@b000 {
				compatible = "nordic,nrf-uarte";
				reg = < 0xb000 0x1000 >;
				interrupts = < 0xb 0x1 >;
				status = "disabled";
			};

		pwm0_default: pwm0_default {
			phandle = < 0xb >;
		};

RE: INT2 working but INT1 is not

AHaug — Wed, 19 Jun 2024 13:15:20 GMT

Could you check in zephyr.dts if the pins are used for anything else? You can find the file in the build folder

Kind regards,
Andreas

RE: INT2 working but INT1 is not

IvanR — Wed, 19 Jun 2024 11:11:07 GMT

I did it in dts, in code, and by reconfiguring the INT output of the sensor itself. I checked all permutations. could not get any response from INT1.

Sensor is properly configured as when I only switch its config to use p0.9 instead of p0.11 it works. If I switch it in dts it works. ... confused

RE: INT2 working but INT1 is not

AHaug — Wed, 19 Jun 2024 11:04:02 GMT

Ah, my bad. I had somehow picked up that you were using a DK, where some of the GPIOs has other predefined default settings: https://docs.nordicsemi.com/bundle/ug_nrf5340_dk/page/UG/dk/connector_if.html

Anyways. I assume that you've consulted with the pin assignment for the 5340SoC when selecting which pins to use https://docs.nordicsemi.com/bundle/ps_nrf5340/page/chapters/pin.html?

Moving back to the issue you're observing.

[quote user=""]I also tried switching the outputs of the sensor and when I did so I got a response on INT2 (that should have been triggered on INT1) and vice versa. [/quote]

By this do you mean that you reconfigured this in the dts, in the code or physically? Could you specify to avoid any misunderstandings?

Kind regards,
Andreas

RE: INT2 working but INT1 is not

IvanR — Wed, 19 Jun 2024 08:46:46 GMT

Its custom board so I cant just rewire P0.11. P0.9 works fine

P0.11 is not free use ?

RE: INT2 working but INT1 is not

AHaug — Tue, 18 Jun 2024 11:52:47 GMT

Hi,

Have you tried any other GPIOs than P0.11? If you inspect the backside of the nrf5340DK you will see that some GPIOs are already in use, while other are free purpose GPIOs (such as P0.09). Do you see the same thing if you use pin 9 and 10 instead of 9 and 11?

Kind regards,
Andreas