nRF52 UART Lock Up in NCS Connect

RE: nRF52 UART Lock Up in NCS Connect

Einarh — Mon, 29 Aug 2022 09:27:47 GMT

Have you tried uart_irq_rx_disable/uart_irq_rx_enable?

You could also look into the Power Management module.

Though I still believe the best way to handle this would be to figure out what is actually going wrong so you can avoid ending up in this crashed state at all.

RE: nRF52 UART Lock Up in NCS Connect

NautDesigner — Sat, 27 Aug 2022 02:12:57 GMT

Using NCS. Is there a way to restart/re-init the UART? Right now when this happens, rebooting the nRF52 is the only option that fixes it.

RE: nRF52 UART Lock Up in NCS Connect

Einarh — Thu, 25 Aug 2022 14:25:52 GMT

I see, then logging is already enabled, strange that you're not getting any warnings.

Have you done any debugging to figure out exactly where in your code something goes wrong?

Also, it looks like you're using the Zephyr UART API, have you considered using the nrfx UARTE driver?

RE: nRF52 UART Lock Up in NCS Connect

NautDesigner — Wed, 24 Aug 2022 16:54:07 GMT

Currently set to LOG_LEVEL_DBG which isn't outputting anything. What level would we need to get more indepth info? We also wouldn't want to show this level of detail until the issue occurs. Is there a way to restart/re-init the UART on the nRF52?

RE: nRF52 UART Lock Up in NCS Connect

Einarh — Thu, 18 Aug 2022 14:28:27 GMT

[quote user="NautDesigner"]Nothing to log. Just send data and nothing returns.[/quote]

What do you mean? If something goes wrong there is likely something getting logged:

http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/services/logging/index.html

RE: nRF52 UART Lock Up in NCS Connect

NautDesigner — Thu, 18 Aug 2022 14:05:26 GMT

Interrupt driven UARTE. Nothing to log. Just send data and nothing returns.

static void uart_irq_handler(const struct device *dev)
{
int read = 0;

	uart_irq_update(dev);

	if (uart_irq_rx_ready(dev)) {
      struct rx_uart_data_t *buf = k_malloc(sizeof(struct rx_uart_data_t));
		read = uart_fifo_read(dev, buf->data, RX_BUF_SIZE);

	   k_fifo_put(&rx_fifo, buf);

	}

	if (uart_irq_tx_ready(dev)) {
		struct tx_uart_data_t *buf = k_fifo_get(&tx_fifo, K_NO_WAIT);
      if (!buf) {
         uart_irq_tx_disable(dev);
         return;
      }

	   uart_fifo_fill(dev, buf->data, buf->len);

      while (!uart_irq_tx_complete(dev)) {
			/* Wait for the last byte to get
			 * shifted out of the module
			 */
		}
      if (k_fifo_is_empty(&tx_fifo)) 
		   uart_irq_tx_disable(dev);
      k_free(buf);

	}
}

static void interrupt_driven(const struct device *dev)
{
	uart_irq_callback_set(dev, uart_irq_handler);
	uart_irq_rx_enable(dev);
}

void initUart() {
   uart = device_get_binding("UART_1");
    //uart = device_get_binding("LPUART");
	__ASSERT(uart, "Failed to get UART device");
	interrupt_driven(uart);
}

void enableUART() {
   pm_device_action_run(uart, PM_DEVICE_ACTION_RESUME);
}

void disableUART() {
   if (!device_is_ready(uart)) {
		return;
	}

   pm_device_action_run(uart, PM_DEVICE_ACTION_SUSPEND);
}

RE: nRF52 UART Lock Up in NCS Connect

Einarh — Thu, 18 Aug 2022 13:54:21 GMT

Sounds like it would be a good idea to activate more logging to investigate what goes wrong.

It would be easier to debug this if you had a specific error message to work with.

Also, what UART driver/API are you using?

-Einar

RE: nRF52 UART Lock Up in NCS Connect

NautDesigner — Thu, 18 Aug 2022 12:45:21 GMT

Ongoing communication with the modem is fine for 30 minutes to several hours of constant communication. And it is just repeating the same sequence over and over.

Based on the lights, we thought it may have been received TX commands, but that may not be the case. It could just be that we are turning if off, turning it back on again to try and get the UART to sync up again.

RE: nRF52 UART Lock Up in NCS Connect

Einarh — Thu, 18 Aug 2022 08:17:10 GMT

Hello!

[quote user=""]Things work great until have an irregular amount of time[/quote]

Can you please expand on what you mean by this?

[quote user="NautDesigner"]From what I can see, it is RX that is the problem, not TX[/quote]

Can you also explain how you came to this conclusion?

Best regards,

Einar

RE: nRF52 UART Lock Up in NCS Connect

NautDesigner — Wed, 17 Aug 2022 22:11:45 GMT

From what I can see, it is RX that is the problem, not TX.