nrf9160 uart Pull-Up and power consumption

RE: nrf9160 uart Pull-Up and power consumption

Håkon Alseth — Thu, 07 Nov 2019 20:45:08 GMT

You cannot disable/enable the DMA. This is done in hardware, and not controllable by the application.

Can you please post your code?

Kind regards,

Håkon

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Thu, 07 Nov 2019 14:57:53 GMT

this didn't work...

do I need the disable the DMA too somehow ?

RE: nrf9160 uart Pull-Up and power consumption

Håkon Alseth — Wed, 06 Nov 2019 08:58:10 GMT

Could you post your enable and disable routine?

[quote user="MosheSmartAmr"]if I disable UART before sending/receiving, i get stuck on while(NRF_UARTE1->EVENTS_RXTO==0); after stopping RX.[/quote]

Try setting the event to 0 before stopping the RX:

NRF_UARTEx->EVENTS_RXTO = 0; 
NRF_UARTEx->TASKS_STOPRX = 1; 
while(NRF_UARTEx->EVENTS_RXTO==0);

Kind regards,

Håkon

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Tue, 05 Nov 2019 17:35:18 GMT

Hi Hakon,

Do I need any special handling if I am using the UART DMA?

it seems to go wrong when I disable and enable it .

i.e.

1. if I disable UART before sending/receiving, i get stuck on while(NRF_UARTE1->EVENTS_RXTO==0); after stopping RX.

2. lf it is disabled after an initial connection, I receive garbage from the uart.

any suggestions?

RE: nrf9160 uart Pull-Up and power consumption

Håkon Alseth — Tue, 05 Nov 2019 12:02:17 GMT

Hi,

[quote user="MosheSmartAmr"]also how do I re-enable uart after the code you suggested above.[/quote]

You store the INTENCLR mask, then set that via INTENSET, and the same goes to all other parameters that are "unset" from the disable function. Note that you strictly do not need to clear the PSEL registers. Then you start the TX and RX via its respective tasks.

There are events that can be generated when entering/exiting sleep, in the POWER peripheral:

https://infocenter.nordicsemi.com/topic/ps_nrf9160/power.html?cp=2_0_0_4_2_0

However; they are not really meant to enable interrupts on, as that would again wake you up, thus it'll defeat the purpose if you hook onto these events to do CPU processing. They are however very useful to see how often the CPU sleeps if you set/clear a GPIO on these events via PPI and GPIOTE, and look at it using a logic analyzer.

Kind regards,

Håkon

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Tue, 05 Nov 2019 10:17:51 GMT

also how do I re-enable uart after the code you suggested above.

(specifically after setting NRF_P0_NS->OUTCLR = (1 << TXD_PIN);)

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Tue, 05 Nov 2019 09:59:21 GMT

Thanks Hakon,

Your last answer seemed to direct me to the answer,

there was an issue with the SW flow,

which leaves the question, is there a way to get an event / interrupt when leaving sleep mode (so I can re-enable uart) ?

Kind Regards ,

Moshe

RE: nrf9160 uart Pull-Up and power consumption

Håkon Alseth — Mon, 04 Nov 2019 14:50:48 GMT

If the current consumption does not come from VDD_IO, then it should not be related to the IO settings at all, but more in the program flow.

Is there any functions running after disabling the uart which tries to use it again? So that the firmware goes into a bad state, causing the high current consumption?

If you're unsure if this comes from VDD_IO, could you try setting it to a input instead of output?

// Input, connected, with pull-down
NRF_P0_NS->PIN_CNF[pin_used] = 0x4;

Kind regards,

Håkon

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Mon, 04 Nov 2019 13:05:06 GMT

unfortunately that did not work.

still getting the same consumption

RE: nrf9160 uart Pull-Up and power consumption

Håkon Alseth — Mon, 04 Nov 2019 11:34:31 GMT

You can clear the events that are set (EVENTS_*), disable the interrupts (Write 0xFFFFFFFF to NRF_UARTEx->INTENCLR), and see if this has any effect.

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Mon, 04 Nov 2019 10:30:46 GMT

I don't see any reason that the NRF91 will be awaken once I disable uart.

could the uart module do that internally? is there a way to disable the uart's module ability to interrupt the NRF91 from sleep ?

RE: nrf9160 uart Pull-Up and power consumption

Håkon Alseth — Mon, 04 Nov 2019 10:25:42 GMT

Hi,

This should not affect the PSM mode, but it might affect the application in terms of sleep routines.

Is there anything specific that happens when you have disabled the UART? Are you able to see if the nRF9160 is awoken from sleep by anything unpredictable?

Kind regards,

Håkon

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Mon, 04 Nov 2019 09:40:55 GMT

Hi,

just to be clearer:

1. the pin is actually pulled down right now.

2. working in power optimmization mode (PSM), Nordic now consumes 2.5ma (not on Vio).

3. before applying what suggested here, nordic consumed 70ua on power optimization mode.

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Sun, 03 Nov 2019 14:11:22 GMT

Hi,

Could this be in any way interfering with low power (PSM) mode ?

although the pin is now down, the current draw is 2.5ma.

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Wed, 23 Oct 2019 09:34:37 GMT

Thanks !! it worked !!

RE: nrf9160 uart Pull-Up and power consumption

Håkon Alseth — Tue, 22 Oct 2019 09:17:41 GMT

Hi,

When the UART is disabled, the RXD is left as an input, and TXD is left as an output (with high level).

This is the routine that I have tested your scenario with:

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

#define TXD_PIN 19

static u8_t uart_buf[1024];

void uart_cb(struct device *x)
{
	uart_irq_update(x);
	int data_length = 0;

	if (uart_irq_rx_ready(x)) {
		data_length = uart_fifo_read(x, uart_buf, sizeof(uart_buf));
		uart_buf[data_length] = 0;
	}
	printk("%s", uart_buf);
}

void main(void)
{
	struct device *uart = device_get_binding("UART_1");

	uart_irq_callback_set(uart, uart_cb);
	uart_irq_rx_enable(uart);
	printk("UART loopback start!\n");
	while (1) {
		static u32_t wakeup_cnt;		
		k_cpu_idle();
		wakeup_cnt++;
		if (wakeup_cnt > 40) {
			wakeup_cnt = 0;
			NRF_UARTE1->TASKS_STOPRX=1;
			while(NRF_UARTE1->EVENTS_RXTO == 0);
			NRF_UARTE1->EVENTS_RXTO = 0;

			NRF_UARTE1->TASKS_STOPTX = 1;
			while(NRF_UARTE1->EVENTS_TXSTOPPED == 0);
			NRF_UARTE1->EVENTS_TXSTOPPED = 0;
			
			NRF_UARTE1->ENABLE = 0;
			NRF_UARTE1->PSEL.TXD = 0xFFFFFFFF;
			NRF_P0_NS->OUTCLR = (1 << TXD_PIN);
		}
	}
}

This code assumes that I loopback UART0:TXD to UART1:RXD, and when it has gotten 40 chars, it disconnects the UART1 interface completely.

If I do not clear the GPIO, it is held high. When I run NRF_P0_NS->OUTCLR = 1<<19;, the pin goes low again after disconnecting it from the UARTE1 peripheral.

Could you try this and see if that works at your end?

Kind regards,

Håkon

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Tue, 22 Oct 2019 08:19:55 GMT

Hi,

Sorry for the delay ,

1.about CONFIG_SERIAL=n, this is exactly wht i did .

2. attaching again .

3. just tried what you suggested (waiting for the event before disabling) , thath did not work too ...

overlay file:

/* SPDX-License-Identifier: Apache-2.0 */

&uart1 {
        current-speed = <115200>;
        compatible = "nordic,nrf-uarte";
        status = "okay";
        tx-pin = <19>;
        rx-pin = <18>;
};

dts file :

/*
 * Copyright (c) 2018 Nordic Semiconductor ASA
 *
 * SPDX-License-Identifier: Apache-2.0
 */

/ {
	model = "Nordic PCA10090 Dev Kit";
	compatible = "nordic,pca10090-dk", "nordic,nrf9160-sica",
		     "nordic,nrf9160";

	chosen {
		zephyr,console = &uart0;
		zephyr,shell-uart = &uart0;
		zephyr,uart-mcumgr = &uart0;
	};

	leds {
		compatible = "gpio-leds";
		led0: led_0 {
			gpios = <&gpio0 2 GPIO_INT_ACTIVE_HIGH>;
			label = "Green LED 0";
		};
		led1: led_1 {
			gpios = <&gpio0 3 GPIO_INT_ACTIVE_HIGH>;
			label = "Green LED 1";
		};
		led2: led_2 {
			gpios = <&gpio0 4 GPIO_INT_ACTIVE_HIGH>;
			label = "Green LED 2";
		};
		led3: led_3 {
			gpios = <&gpio0 5 GPIO_INT_ACTIVE_HIGH>;
			label = "Green LED 3";
		};
	};

	buttons {
		compatible = "gpio-keys";
		button0: button_0 {
			gpios = <&gpio0 8 GPIO_PUD_PULL_UP>;
			label = "Switch 1";
		};
		button1: button_1 {
			gpios = <&gpio0 9 GPIO_PUD_PULL_UP>;
			label = "Switch 2";
		};
		button2: button_2 {
			gpios = <&gpio0 6 GPIO_PUD_PULL_UP>;
			label = "Push button 1";
		};
		button3: button_3 {
			gpios = <&gpio0 7 GPIO_PUD_PULL_UP>;
			label = "Push button 2";
		};
	};

	/* These aliases are provided for compatibility with samples */
	aliases {
		led0 = &led0;
		led1 = &led1;
		led2 = &led2;
		led3 = &led3;
		sw0 = &button2;
		sw1 = &button3;
		sw2 = &button0;
		sw3 = &button1;
	};
};

&adc {
	status ="ok";
};

&gpiote {
	status = "ok";
};

&gpio0 {
	status = "ok";
};


&uart0 {
	status = "ok";
	current-speed = <115200>;
	tx-pin = <26>;
	rx-pin = <30>;
};

/*
&uart0 {
	status = "okay";
	current-speed = <115200>;
	tx-pin = <29>;
	rx-pin = <28>;
	rts-pin = <27>;
	cts-pin = <26>;
};
*/
&uart1 {
	status = "ok";
	current-speed = <115200>;
	tx-pin = <1>;
	rx-pin = <0>;
	rts-pin = <14>;
	cts-pin = <15>;
};

&i2c2 {
	status = "ok";
	sda-pin = <12>;
	scl-pin = <31>;
};

&pwm0 {
	status = "ok";
	ch0-pin = <2>;
};

&spi3 {
	status = "ok";
};

&timer0 {
	status = "ok";
};

&timer1 {
	status = "ok";
};

&timer2 {
	status = "ok";
};

&flash0 {
	/*
	 * For more information, see:
	 * http://docs.zephyrproject.org/latest/guides/dts/index.html#flash-partitions
	 */
	partitions {
		compatible = "fixed-partitions";
		#address-cells = <1>;
		#size-cells = <1>;

		boot_partition: partition@0 {
			label = "mcuboot";
			reg = <0x00000000 0x10000>;
		};
		slot0_partition: partition@10000 {
			label = "image-0";
		};
		slot0_ns_partition: partition@40000 {
			label = "image-0-nonsecure";
		};
		slot1_partition: partition@80000 {
			label = "image-1";
		};
		slot1_ns_partition: partition@b0000 {
			label = "image-1-nonsecure";
		};
		scratch_partition: partition@f0000 {
			label = "image-scratch";
			reg = <0x000f0000 0xa000>;
		};
		storage_partition: partition@fa000 {
			label = "storage";
			reg = <0x000fa000 0x00006000>;
		};
	};
};

/ {
	/* SRAM allocated and used by the BSD library */
	sram0_bsd: memory@20010000 {
		device_type = "memory";
		compatible = "mmio-sram";
	};

	/* SRAM allocated to the Non-Secure image */
	sram0_ns: memory@20020000 {
		device_type = "memory";
		compatible = "mmio-sram";
	};
};

/* Include partition configuration file */
#include "nrf9160_pca10090_partition_conf.dts"

RE: nrf9160 uart Pull-Up and power consumption

Håkon Alseth — Fri, 11 Oct 2019 08:29:54 GMT

Hi Moshe,

[quote user="MosheSmartAmr"]2. if I disable UART completely, I see the line on LOW.[/quote]

Never initialize it? ie: CONFIG_SERIAL=n?

[quote user="MosheSmartAmr"]4. attached. [/quote]

Looks like they weren't attached. Could you try .zip'ing it and then attach it?

Did you try disabling per the recommendation in the datasheet, ie: wait for the events on RX and TX before completely disabling the peripheral to see if this has a difference on the behavior?

Kind regards,

Håkon

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Thu, 10 Oct 2019 07:52:12 GMT

Hi Hakon,

1. I'm pretty sure it is the NRF since the device on the other size is powered off.

2. if I disable UART completely, I see the line on LOW.

3. it is measured on a costum board.

4. attached.

Thanks !!!

RE: nrf9160 uart Pull-Up and power consumption

Håkon Alseth — Mon, 07 Oct 2019 07:48:08 GMT

Hi Moshe,

Are you 100 % certain that its the nRF that is keeping this line high?

If you power off only the nrf91, does the voltage drop to gnd?

Is this measured on a nRF91-DK or a custom board?

If it still is set high, can you please post any changed overlay/dts files?

PS: your stop/disable routines will not work as you intend them to, because when you issue TASKS_STOPRX=1, you have to wait for the EVENTS_RXTO to occur before you disable the UART instance (same goes for the TX, although its less of a change for that the occurring while you disable the peripheral), as stated here in the PS:

https://infocenter.nordicsemi.com/topic/ps_nrf9160/uarte.html?cp=2_0_0_5_18_6#concept_twi_low_power

Kind regards,

Håkon

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Sun, 06 Oct 2019 12:39:39 GMT

what I did was to disable UART completely (from the code) and measure.

however, the issue is that i still measure 1.8v on the uart pin.

somehow nothing I do seems to disable the uart pull-up.

RE: nrf9160 uart Pull-Up and power consumption

Vidar Berg — Sun, 06 Oct 2019 10:28:07 GMT

Hi,

To get a baseline measurement, is it possible to add a long sleep at the beginning of your code before you enable the UART instances, then try to measure the idle current? Or did you do that already?

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Sun, 06 Oct 2019 10:04:18 GMT

Hi,

1. current consumption is around 1ma.

2. Verified the GPIO's from the register and they look ok, the pins that contols the external device I measured the voltage and it looks corrct.

3. checked the ENABLE , they look ok .

RE: nrf9160 uart Pull-Up and power consumption

Vidar Berg — Thu, 26 Sep 2019 07:34:20 GMT

Could you let me know the current consumption you see is? Here are some things you can try:

- Verify GPIO pin configuration RX and TX by reading out the configuration registers with your debugger. Also, the pin that controls the power to the external device if you use an output pin for it.

- If possible, get a baseline measurement by measuring the current consumption before enabling UARTE and power to external circuitries.

- Check the enable registers for all UART instances.

RE: nrf9160 uart Pull-Up and power consumption

MosheSmartAmr — Thu, 26 Sep 2019 07:19:33 GMT

Hi Vidar ,

>> Did you determine that based on the total current consumption?

yes, I did.

How can I further debug this issue?