Custom Board based on nRF9160 + GPIO Pin Mapping problem

RE: Custom Board based on nRF9160 + GPIO Pin Mapping problem

Yury Morgunov — Mon, 10 Aug 2020 09:36:52 GMT

Already created a topic:
https://devzone.nordicsemi.com/f/nordic-q-a/64596/some-uart-registers-don-t-change-after-changing-in-overlay
Now I'm trying to figure out what they answered me

RE: Custom Board based on nRF9160 + GPIO Pin Mapping problem

Martin Lesund — Mon, 10 Aug 2020 09:05:40 GMT

Hi Yury,
This case is over 1 year old. Please make a new ticket and also state which NCS version you are using since there has been updates since 2019.

RE: Custom Board based on nRF9160 + GPIO Pin Mapping problem

Yury Morgunov — Fri, 07 Aug 2020 06:10:50 GMT

Hello!
I faced a similar problem. Tell me, could you solve it?

RE: Custom Board based on nRF9160 + GPIO Pin Mapping problem

Marcin — Wed, 12 Jun 2019 20:35:05 GMT

Thank you for your message, I really appreciate that!

My problem is unfortunately still not solved. I cannot turn the state to on and pin 0.30. I checked with the multimeter and there is no voltage on the output on 0.30.

On 0.28 I can control state (1/0) but not on 0.30

I've noticed that:
- pin 28 (as you mentioned) is a part of Uart0
- pin 30 is a part of i2c

My overlay file:

&uart0 {
tx-pin = <10>;
rx-pin = <11>;
rts-pin = <12>;
cts-pin = <13>;
};

&i2c2 {
sda-pin = <2>;
scl-pin = <0>;
clock-frequency = <I2C_BITRATE_STANDARD>;
};

My code:

#include <gpio.h>
#include <misc/printk.h>
#include <zephyr.h>

int LED_GREEN = 28;
int LED_RED = 30;
void main(void) {

struct device *gpio_dev;
gpio_dev = device_get_binding(DT_GPIO_P0_DEV_NAME);

int initializeDiode1 = gpio_pin_configure(gpio_dev, LED_RED, GPIO_DIR_OUT);
int initializeDiode2 = gpio_pin_configure(gpio_dev, LED_GREEN, GPIO_DIR_OUT);
int redInit = gpio_pin_write(gpio_dev, LED_RED, 1);
int greenInit = gpio_pin_write(gpio_dev, LED_GREEN, 1);

while (1) {

}
}

As mentioned, I'm using a custom PCB board with RF9160-SICA

RE: Custom Board based on nRF9160 + GPIO Pin Mapping problem

DevinCallahan — Wed, 12 Jun 2019 19:52:58 GMT

I think my initial answer was wrong about how to fix this. What you want is to assign different pins to UART0 through the Device Tree. We can do that with an overlay file.

Create a file called exactly "nrf9160_pca10090ns.overlay" in the project source directory (at the same level as CMakeLists.txt). It must be exactly "<board name you configured project with>.overlay" because the zephyr build process uses the board name when searching this for file in your project directory.

I know that is has found my overlay file because the initial west build will dump something like this to the console:

-- Loading ~/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090ns.dts as base
-- Overlaying ~/zephyr/dts/common/common.dts
-- Overlaying ~/nrf/experiment/shell_test/nrf9160_pca10090ns.overlay

In the .overlay file define this. Pick which pins you want to move the UART to (I chose 10-13 because those just happen to be free pins on the dev-kit):

&uart0 {
    tx-pin = <10>;
    rx-pin = <11>;
    rts-pin = <12>;
    cts-pin = <13>;
};

This will modify the pins that get assigned.

You can verify this by looking at the header file the device tree system generates at: "build/zephyr/include/generated/generated_dts_board_unfixed.h"

Before adding the overlay I get these definitions (which match the default config):

#define DT_NORDIC_NRF_UARTE_40008000_CTS_PIN		26
#define DT_NORDIC_NRF_UARTE_40008000_RTS_PIN		27
#define DT_NORDIC_NRF_UARTE_40008000_RX_PIN		28
#define DT_NORDIC_NRF_UARTE_40008000_TX_PIN		29

After adding the overlay I get these definitions:

#define DT_NORDIC_NRF_UARTE_40008000_CTS_PIN		13
#define DT_NORDIC_NRF_UARTE_40008000_RTS_PIN		12
#define DT_NORDIC_NRF_UARTE_40008000_RX_PIN		11
#define DT_NORDIC_NRF_UARTE_40008000_TX_PIN		10

RE: Custom Board based on nRF9160 + GPIO Pin Mapping problem

Marcin — Wed, 12 Jun 2019 19:21:07 GMT

I removed uart0 from chosen {} and even changed the pin definitions in _common.dts but still without any result. Any information about how to change the config properly?

RE: Custom Board based on nRF9160 + GPIO Pin Mapping problem

Marcin — Wed, 12 Jun 2019 19:19:15 GMT

Basically the microchipnRF9160-SICA
BAA-E2.1.8
11YP5

Is connected with the GPS, SIM card on the custom PCB.
I can properly upload the code, but I cannot access previously defined pins (28,29,30,31) and (7 and 8)

Overlay file does not change the availability of pin 28 and 30.

Can I get any assist with that?

RE: Custom Board based on nRF9160 + GPIO Pin Mapping problem

DevinCallahan — Wed, 12 Jun 2019 16:01:47 GMT

Pin 28 is being used as the RX pin for UART0 in the default Device Tree for the devkit. This is configured at: /zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090_common.dts

&uart0 {
	status = "ok";
	current-speed = <115200>;
	tx-pin = <29>;
	rx-pin = <28>;
	rts-pin = <27>;
	cts-pin = <26>;
};

Unless you modify the zephyr,console chosen attribute to not use UART0 for the console, the default configuration will initialize pin 28 for the UART. I don't think the chip handles pin-mux conflicts very well.

Additionally the 52840 on the DK configures P0.28 to go to VCOM0 on the FTDI chip. If you want to use P0.28 on one of the Arduino headers you will need to modify the 52840 config to do so.

RE: Custom Board based on nRF9160 + GPIO Pin Mapping problem

Martin Lesund — Wed, 12 Jun 2019 12:12:55 GMT

Hi Marcin,

How much have you based it on the nRF91DK?

Please try to update the .overlay file for the spm as well for your application.

Also please study the nRF Connect SDK tutorial