P1.00 GPIO on 4x3 keypad not detecting Col

RE: P1.00 GPIO on 4x3 keypad not detecting Col

melt — Fri, 15 Nov 2024 06:41:36 GMT

Hi Kenneth

I ran the blink and push button samples on P1.00 with success. I then loaded the original NRF_desktop keyboard.conf example. Change button0 to P1.00 and that also worked.

I made a copy of my project from a year ago sdk 2.4 and tool chain 2.4 changed the pins and it worked first time.

I will now complete the project then port it to SDK 2.6 and revert back. for now, I'm just glad I can move on.

Thanks for you guys' assistance as always.

RE: P1.00 GPIO on 4x3 keypad not detecting Col

Kenneth — Tue, 12 Nov 2024 15:58:47 GMT

Sorry to ask a bit obvious question, but running for instance blinky or button example, you are able to control the P1.00 pin then yes?

Kenneth

RE: P1.00 GPIO on 4x3 keypad not detecting Col

melt — Mon, 11 Nov 2024 12:54:26 GMT

No It is still the same. Looking at the below from the data sheet

im wondering if it may have something to do with this

&qspi {
	status = "okay";
	pinctrl-0 = <&qspi_default>;
	pinctrl-1 = <&qspi_sleep>;
	pinctrl-names = "default", "sleep";
	mx25r64: mx25r6435f@0 {
		compatible = "nordic,qspi-nor";
		reg = <0>;
		/* MX25R64 supports only pp and pp4io */
		writeoc = "pp4io";
		/* MX25R64 supports all readoc options */
		readoc = "read4io";
		sck-frequency = <8000000>;
		jedec-id = [c2 28 17];
		sfdp-bfp = [
			e5 20 f1 ff  ff ff ff 03  44 eb 08 6b  08 3b 04 bb
			ee ff ff ff  ff ff 00 ff  ff ff 00 ff  0c 20 0f 52
			10 d8 00 ff  23 72 f5 00  82 ed 04 cc  44 83 68 44
			30 b0 30 b0  f7 c4 d5 5c  00 be 29 ff  f0 d0 ff ff
		];
		size = <67108864>;
		has-dpd;
		t-enter-dpd = <10000>;
		t-exit-dpd = <35000>;
	};
};

I tried CONFIG_FLASH=n in the prj_keyboard.conf. But then it does not compile as configuration is incomplete.

I also tried disabling it in the overlay but it has no effect.

&qspi {
    status = "disabled";
};

RE: P1.00 GPIO on 4x3 keypad not detecting Col

Kenneth — Sat, 09 Nov 2024 16:27:19 GMT

Sorry, I was not clear. If you for instance set gpio-reserved-ranges = <15>;, is the problem then moved to P1.15?

Kenneth

RE: P1.00 GPIO on 4x3 keypad not detecting Col

melt — Fri, 08 Nov 2024 06:49:04 GMT

I have tried P1.15, P1,13, P1.11 they all work and the program runs normally

RE: P1.00 GPIO on 4x3 keypad not detecting Col

Kenneth — Thu, 07 Nov 2024 22:58:18 GMT

Okey, can I ask for one more test. Can you set it to something else than 0? Is there any pins on P1 not used for anything?

Kenneth

RE: P1.00 GPIO on 4x3 keypad not detecting Col

melt — Thu, 07 Nov 2024 06:20:39 GMT

Hi Kenneth, Apologies I have been trying to find where the P1.00 is being used.

if I remove gpio-reserved-ranges = <0>;? in the overlay it defaults to the .dts file which I don't want to edit. (original GPIO1 below)

&gpio1 {
	status = "okay";
	gpio-line-names = "", "D0", "D1", "D2", "D3", "D4", "D5", "D6",
		"D7", "", "D8", "D9", "D10", "D11", "D12", "D13";
};

As soon as I setup col2 P1.00. My entire program stops working. The keyboard is not detected via USB or BLE. I can use any other pin and it will work.

col2: col_2 {
		gpios = <&gpio1 0 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)>;//0.17//remember to change buttons_def
		label = "keypadcol2";
	};

Somewhere in the nrf_Dekstop keyboard configuration example P1.00 must be reserved and I cant seem to find it

RE: P1.00 GPIO on 4x3 keypad not detecting Col

Kenneth — Thu, 24 Oct 2024 11:19:19 GMT

Have you tried removing gpio-reserved-ranges = <0>;?

It's not a required property, and using it will likely, as you write, prevent it to be useable?

Kenneth

RE: P1.00 GPIO on 4x3 keypad not detecting Col

melt — Wed, 23 Oct 2024 11:50:25 GMT

HI Kenneth, I have tried another board. same thing. I suspect it has something to do with the reserved pins.

I initially had this problem with gpio0 . I then unreserved as below but not sure I did it correctly with gpio1

&gpio0 {
	status = "okay";
	gpio-reserved-ranges = <0 2>;
	gpio-line-names = "XL1", "XL2";
};

&gpio1{
	status = "okay";
	gpio-reserved-ranges = <0>;
	gpio-line-names = "";
};

The original device tree looked as follow

&gpio0 {
	status = "okay";
	gpio-reserved-ranges = <0 2>, <6 1>, <8 3>, <17 7>;
	gpio-line-names = "XL1", "XL2", "AREF", "A0", "A1", "RTS", "TXD",
		"CTS", "RXD", "NFC1", "NFC2", "BUTTON1", "BUTTON2", "LED1",
		"LED2", "LED3", "LED4", "QSPI CS", "RESET", "QSPI CLK",
		"QSPI DIO0", "QSPI DIO1", "QSPI DIO2", "QSPI DIO3","BUTTON3",
		"BUTTON4", "SDA", "SCL", "A2", "A3", "A4", "A5";
};

&gpio1 {
	status = "okay";
	gpio-line-names = "", "D0", "D1", "D2", "D3", "D4", "D5", "D6",
		"D7", "", "D8", "D9", "D10", "D11", "D12", "D13";
};

Although nothing reserved in GPIO1 it does not allow me to toggle or read P1.00

RE: P1.00 GPIO on 4x3 keypad not detecting Col

Kenneth — Wed, 23 Oct 2024 11:31:22 GMT

Hello,

You can download the schematic and layout from here if you haven't already:
https://www.nordicsemi.com/Products/Development-hardware/nRF52840-Dongle/Download?lang=en#infotabs

I don't see any reason why P1.00 should not be possible to use for any purpose no. If you just make a simple application toggling the IO, does that work? Maybe the pin have been damaged in some way?

Kenneth