UARTE

[Elbert]

In UART async mode (CONFIG_UART_ASYNC_API=y) the UART transmit data and receive callback works fine. I've been able to set up the callback and enable the rx.

After switching to UARTE (CONFIG_NRFX_UARTE0=y), the UART transmit once, but the event handler is never called.

UARTE is set up like example from: "C:\ncs\v2.0.0\zephyr\samples\boards\nrf\nrfx_prs\src\main.c", the baudrate is set to 9600. nrfx_uarte_init() and nrfx_uarte_tx() show NRFX_SUCCESS. When nrfx_uarte_tx_in_progress() call is added, just after nrfx_uarte_tx(),  nrfx_uarte_tx_in_progress() hangs without any further (log) message.

Is it possible to implement UARTE like this on nRF9160 development board?

Do you need to enable rx on UARTE?

Is there any working sample for nRF9160?

[Hakon]

Can you show the overlay file?

[Elbert]

This is the used overlay file:

/*
 * Copyright (c) 2021 Nordic Semiconductor ASA
 *
 * SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
 */

/* Disable uart1 in nonsecure since it is used by the TFM secure app. */
&uart1 {
	status = "disabled";
};

/* Console uart0 baudrate 9600 */
&uart0 {
    current-speed = < 9600 >;
};

/ {
    aliases {
        console-uart = &uart0;
    };
};

[Hakon]

Try setting "compatible = nordic,nrf-uarte" for uart0.

[Elbert]

Hi,

This setting was already present. From compiled devicetree output:

uart0: uart@8000 {
                                compatible = "nordic,nrf-uarte";
                                reg = <0x8000 0x1000>;
                                interrupts = <8 NRF_DEFAULT_IRQ_PRIORITY>;
                                status = "okay";
                                current-speed = <9600>;
                                pinctrl-0 = <&uart0_default>;
                                pinctrl-1 = <&uart0_sleep>;
                                pinctrl-names = "default", "sleep";
                        };

prj.conf contains CONFIG_UART_ASYNC_API=y and output file .config show:

CONFIG_UART_ASYNC_API=y

CONFIG_UART_0_NRF_UARTE=y

CONFIG_NRF_UARTE_PERIPHERAL=y

• Does this mean uart0 is running in UARTE mode?
• Can I use standard uart functions (like uart_callback_set, uart_rx_enable, etc.) and run in UARTE mode or do I have to use the uarte functions (like nrfx_uarte_init, nrfx_uarte_tx, etc.) to run in UARTE mode?

Best regard, Elbert

[Elbert]

Is there any update on this item?

[Hakon]

Can you just show me the full main.c file? It's difficult to tell what's going on with the short bits of the code you have shown me.

[Elbert]

Hi Hakon,

The code shown at 26 Sep 2022 is exactly what I'm doing. There is not much more to show you.

Perhaps you can take a look at my questions of 26 Oct 2022. If these questions are answer it might not be necessary to use specific nrfx functions?

I have been told that there is a nRF9160-dk UARTE sample. Is it possible to provide this sample to me?

Best regards, Elbert

[Hakon]

Elbert said:

I have been told that there is a nRF9160-dk UARTE sample. Is it possible to provide this sample to me?

Where have you been told this? As far as I know there is one internal example that is outdated and deprecated, and there is an official LP-UART sample. I don't think there is a specific UARTE sample, but I could be wrong.

Elbert said:

Can I use standard uart functions (like uart_callback_set, uart_rx_enable, etc.) and run in UARTE mode or do I have to use the uarte functions (like nrfx_uarte_init, nrfx_uarte_tx, etc.) to run in UARTE mode?

Yes it should be possible. I'm pretty sure you can use the same API for both UART and UARTE.