peripheral uart unstable

RE: peripheral uart unstable

runved — Tue, 20 Dec 2022 06:58:14 GMT

solved in:https://devzone.nordicsemi.com/f/nordic-q-a/87359/peripheral-uart-rx-timeout-and-notification-size/366255?focus=true

RE: peripheral uart unstable

Edvin — Thu, 17 Nov 2022 12:43:41 GMT

[quote user="runved"]I am able to get data from nrf91 and i can scope the data on SB8. but none from nrf52 SB7.[/quote]

I am not familiar with the Thingy52 on that level. Is Solder Bridge 7 routed to the P0.21 on the nRF52832?

[quote user="Edvin Holmseth"]

Does the UART_RX_RDY case occur when it doesn't trigger on \r or \n? Is "disable_req" for some reason set to true?

[/quote]

Did you try to debug this?

BR,
Edvin

RE: peripheral uart unstable

runved — Tue, 15 Nov 2022 11:58:44 GMT

Hi Edvin,

Yes, my UART_RX_RDY is excactly like yours.

before i build the the application i selected the "Enable UART async adapter" under "nordic UART BLE GATT service sample" in the Kconfig. at that seems to make it moore stabile,

CONFIG_UART_ASYNC_API=y is in the prj.conf so why?

Anyway this is only my first step.

I use this Peripheral_uart eksample on THINGY:52 and Central_uart on a Thingy:91_nrf52 and a uart connection to Thingy:91_nrf91.

my proble is now on the Thingy:91 and the uart connection between nrf52 and nrf91 internaly:

The problem is that the nrf52 does not send anything out on the pin, i got UART_TX_DONE from my debug.

I am able to get data from nrf91 and i can scope the data on SB8. but none from nrf52 SB7.

is there any pin conflict that i am missing?

nrf52840dk_nrf52840.overlay

&uart1 {
	current-speed = <115200>;
	status = "okay";
	/delete-property/ hw-flow-control;
	pinctrl-0 = <&uart1_default>;
	pinctrl-1 = <&uart1_sleep>;
	pinctrl-names = "default", "sleep";
};


&pinctrl {

	uart1_default: uart1_default {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 21)>,
					<NRF_PSEL(UART_RX, 1, 0)>;
					
		};
	};

	uart1_sleep: uart1_sleep {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 21)>,
					<NRF_PSEL(UART_RX, 1, 0)>;
			low-power-enable;
		};
	};

};

Thingy91_nrf9160_ns.overlay

&uart1 {
	current-speed = <115200>;
	status = "okay";
	/delete-property/ hw-flow-control;
	pinctrl-0 = <&uart1_default>;
	pinctrl-1 = <&uart1_sleep>;
	pinctrl-names = "default", "sleep";
};


&pinctrl {

    uart1_default: uart1_default {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 22)>;		
		};
		group2 {
			psels =<NRF_PSEL(UART_RX, 0, 21)>;
			//bias-pull-up;
		};
	};

	uart1_sleep: uart1_sleep {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 22)>,
					<NRF_PSEL(UART_RX, 0, 21)>;
			low-power-enable;
		};
	}; 
};

I have tryed all MCU_IF pins with same result

RE: peripheral uart unstable

Edvin — Mon, 14 Nov 2022 13:07:00 GMT

Does this switch case look like this for UART_RX_RDY in your uart_cb() function?

	case UART_RX_RDY:
		LOG_DBG("UART_RX_RDY");
		buf = CONTAINER_OF(evt->data.rx.buf, struct uart_data_t, data);
		buf->len += evt->data.rx.len;

		if (disable_req) {
			return;
		}

		if ((evt->data.rx.buf[buf->len - 1] == '\n') ||
		    (evt->data.rx.buf[buf->len - 1] == '\r')) {
			disable_req = true;
			uart_rx_disable(uart);
		}

		break;

Does the UART_RX_RDY case occur when it doesn't trigger on \r or \n? Is "disable_req" for some reason set to true?

Does the log on the Thingy say anything?

Best regards,

Edvin

RE: peripheral uart unstable

runved — Fri, 11 Nov 2022 14:37:14 GMT

Sorry, short happiness, this version fails also after a while.

i have tried to debug with no sucsess, I send "Test\r\n" many times and when buffer is full the hole buffer is sendt "Test\r\nTest\r\nTest\r\nTest\r\nTest\r\nTest\r\n"

Rune

RE: peripheral uart unstable

runved — Fri, 11 Nov 2022 12:37:21 GMT

Hi,

reconnect or power toggle.

i have tested it in sdk2.0.2. and It seam to work fine in this version.

RE: peripheral uart unstable

Edvin — Fri, 11 Nov 2022 11:02:05 GMT

Hello,

If I understand you correctly, you are saying that after you disconnect and reconnect the bluetooth connection, the data will no longer be sent on cr,lf, but only when the buffer is full? Have you tried to debug to see why it doesn't trigger when the incoming byte is cr,lf?

Best regards,

Edvin

RE: peripheral uart unstable

runved — Thu, 10 Nov 2022 09:01:25 GMT

Comment after moore testing: after repeated power on it start up in 2 different modes(60/40), one all ok, and one where

UART_RX_RDY: does not trigger when inncomming data from uart.