Simple GPIO Example - nRF9160 DK

RE: Simple GPIO Example - nRF9160 DK

Captain CK — Wed, 29 Dec 2021 04:28:30 GMT

Try on this program, But I am using SEGGER SDK 1.7.1. Hear I have blinked P0.02 & P0.12. I hope this will help.

#include <stdio.h>
#include <zephyr.h>
#include <device.h>
#include <devicetree.h>
#include <drivers/gpio.h>

//sleep time
#define SLEEP_TIME_MS   100

void main(void)
{
	int cnt = 0;
	const struct device *dev;

	dev = device_get_binding("GPIO_0");
	/* Set led0 pin as output */


	gpio_pin_configure(dev, 2, GPIO_OUTPUT); //GPIO p0.03 == LED2
    gpio_pin_configure(dev,12, GPIO_OUTPUT); //GPIO P0.12

	while (1) {
		/* Set pin to HIGH/LOW every 1 second */
		gpio_pin_set(dev, 2,cnt % 2);	//GPIO p0.03 == LED2
        gpio_pin_set(dev, 12, cnt % 2);

		cnt++;
		k_msleep(SLEEP_TIME_MS);
	}
}

RE: Simple GPIO Example - nRF9160 DK

Captain CK — Wed, 29 Dec 2021 03:57:55 GMT

can you please explain what mean by this "cnt" object that was created the beginning of the program.

RE: Simple GPIO Example - nRF9160 DK

mrwesleycrusher — Fri, 12 Apr 2019 19:40:18 GMT

I have discovered that you can get this stuff to work by reading the datasheet for the SiP to get register addresses and then by using the zephyr build tool, west, to compile your programs without using the additional nordic sdk

RE: Simple GPIO Example - nRF9160 DK

hmolesworth — Mon, 25 Mar 2019 14:41:12 GMT

Nothing special, other than allocating the io pins correctly. If using the nRF52 SDK then add a suitable .h pinout file to .\Components\Boards\. This can be created from a file in the nRF9160 tree here .\ncs\Zephyr\boards\arm\nrf52840_pca10090\board.c

RE: Simple GPIO Example - nRF9160 DK

mrwesleycrusher — Thu, 21 Mar 2019 23:18:35 GMT

For working with the 52840 on the 9160 DK, can code be compiled for it just like on the older 52840 development kits? Is there anything special I need to do to program for it besides switch the PROG/DEBUG fromnrf91 to nrf52?

Thanks,

Wes

RE: Simple GPIO Example - nRF9160 DK

JustWalt — Wed, 27 Feb 2019 20:28:49 GMT

Thanks for your help. I haven't quite solved the problem yet, but your posts have definitely pointed me in the right direction. Much appreciated.

RE: Simple GPIO Example - nRF9160 DK

hmolesworth — Wed, 27 Feb 2019 17:49:22 GMT

No, D7 is a signal label not a pin as such; P0.07 is the pin, which can be connected to D7 or disconnected from D7 by nRF52_P0.26 (I wrote P0.7 above, meaning P0.07 on the nRF9160)

RE: Simple GPIO Example - nRF9160 DK

JustWalt — Wed, 27 Feb 2019 17:46:57 GMT

Thanks, I'll give this a shot.

By D7, I assume you're talking about the physical P0.07 pin on the board itself?

RE: Simple GPIO Example - nRF9160 DK

hmolesworth — Wed, 27 Feb 2019 17:38:28 GMT

I would suggest those pins are indeed available, but they have to be properly directed by the nRF52 to be i/o ports disconnected to buttons and LEDs by setting the appropriate nRF52 pin high to select the required i/o function.

For example, P0.7 (nRF9160) can be connected to D7 by driving nRF52_P0.26 high (see U12 FSA2466UMX DPDT FET switch)
D7 is available on P13 and P12, two headers which are marked not assembled but pads are available, and are not otherwise connected as far as I can see. These pins may be listed in the user Manual (I haven't checked), but are traceable on the schematic.

RE: Simple GPIO Example - nRF9160 DK

JustWalt — Wed, 27 Feb 2019 17:10:49 GMT

P0.17 was functional. But I need to use pins 2-7.

"The pins that are available from the nRF91 are pins P0.10 - P0.20 and P0.0 and P0.01."

Well, shoot. Where is this made known? Is there a way that I can use the 9160 to communicate with the 52840 to access these pins? They are pretty important for the task I purchased the board for.

Thanks,
Justin

RE: Simple GPIO Example - nRF9160 DK

Jared — Wed, 27 Feb 2019 14:16:15 GMT

Hi,

You didn't see any activity on P0.17 after programming the hex file? The pins that are available from the nRF91 are pins P0.10 - P0.20 and P0.0 and P0.01.

Best regards

Jared

RE: Simple GPIO Example - nRF9160 DK

JustWalt — Fri, 22 Feb 2019 19:15:10 GMT

Sorry Jared, I should have been more specific. The included hex file does run, and I'm able to see the output on the board.

However, the pins that I need to use are the physical pins on the board. While the LEDs do light up when I set 3 and 4 to high, the actual pin itself sees no change in voltage.

I need to use pins [P0.0]2, 4, 6, and 7 in order to interact with an Arduino shield. The documentation says that there is an Arduino interface, but nothing about how to activate it. Is that an nRF52840 only feature, or is it available for the nRF9160?

Thanks,
Justin

RE: Simple GPIO Example - nRF9160 DK

Jared — Fri, 22 Feb 2019 13:51:06 GMT

Hi,

That should be correct. I've included a hex that toggles some LEDs and P0.17. Could you flash the hex to the board and see if it run?

If it doesn't, then you are maybe missing secureboot?

Jared

#include <zephyr.h>
#include <device.h>
#include <gpio.h>

/* 1000 msec = 1 sec */
#define SLEEP_TIME 	1000

void main(void)
{
	int cnt = 0;
	struct device *dev;

	dev = device_get_binding("GPIO_0");
	/* Set LED pin as output */
	gpio_pin_configure(dev, 3, GPIO_DIR_OUT); //p0.03 == LED2
	gpio_pin_configure(dev, 4, GPIO_DIR_OUT); //p0.04 == LED3
	gpio_pin_configure(dev, 17, GPIO_DIR_OUT); //p0.17

	while (1) {
		/* Set pin to HIGH/LOW every 1 second */
		gpio_pin_write(dev, 3, cnt % 2);	//p0.03 == LED2
		gpio_pin_write(dev, 4, cnt % 2);	//p0.04 == LED3
		gpio_pin_write(dev, 17, cnt % 2);	//p0.17 Toggling pin 17
		cnt++;
		k_sleep(SLEEP_TIME);
	}
}

devzone.nordicsemi.com/.../Togglepin.hex

RE: Simple GPIO Example - nRF9160 DK

JustWalt — Wed, 20 Feb 2019 19:48:44 GMT

Hi Jared,

Thanks for the response.

I'm not sure how to set those pins. Should I address them as such: gpio_pin_write(gpio_dev, 17, 1);?

Perhaps I'm doing something else wrong, because this has no effect. Is there some .overlay or prj.conf setting that I'll need to have active so I can access the GPIO from nRF9160 code?

Justin

RE: Simple GPIO Example - nRF9160 DK

Jared — Wed, 20 Feb 2019 10:18:21 GMT

Hi,

P0.02 is connected to LED 1 (Note that there is an error in the pin mapping in that it should state that LED 2 should be connected P0.03 etc..) . You can try P0.17, P0.18, or P0.19 instead.

Best regards

Jared