UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

RE: UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

Einarh — Mon, 07 Mar 2022 10:06:11 GMT

Hi again.

This means the compiler doesn't find your overlay file.

Please make sure you've included it correctly according to the Zephyr devicetree guide.

Best regards,

Einar

RE: UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

Deepak Aagri — Fri, 04 Mar 2022 16:34:21 GMT

Q1- As I asked earlier, do you see the "Found devicetree overlay" message when building?

Ans- NO

Q2- tell me what this function returns:

DT_NODE_HAS_STATUS(UART2_NODE, okay)

Ans- Zero

RE: UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

Einarh — Fri, 04 Mar 2022 10:02:06 GMT

As I asked earlier, do you see the "Found devicetree overlay" message when building?

And if you do, could you put this in your code:

#define UART2_NODE DT_NODELABEL(uart2)

and then tell me what this function returns:

DT_NODE_HAS_STATUS(UART2_NODE, okay)

-Einar

RE: UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

Deepak Aagri — Fri, 04 Mar 2022 07:09:29 GMT

if we use this CONFIG_NRFX_UARTE2... cmake and build compilation not generating error. but still UART2 not working...

RE: UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

Einarh — Thu, 03 Mar 2022 12:56:56 GMT

So from your error log it's clear you're not using CONFIG_UART_2_NRF_UARTE correctly.

Have you looked up what this option does before including it in your project?

You can see a list of all config options here.

You can also use the nRF Kconfig browser in NCS for VS Code to browse available config options and their dependencies.

Just from a quick look at the full list, I believe CONFIG_HAS_HW_NRF_UARTE2 or CONFIG_NRFX_UARTE2 could be more relevant.

-Einar

RE: UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

Deepak Aagri — Thu, 03 Mar 2022 12:45:44 GMT

build tree::

uart0: uart@8000 {

compatible = "nordic,nrf-uarte";

reg = <0x8000 0x1000>;

interrupts = <8 NRF_DEFAULT_IRQ_PRIORITY>;

status = "disabled";

label = "UART_0";

};

uart1: uart@9000 {

compatible = "nordic,nrf-uarte";

reg = <0x9000 0x1000>;

interrupts = <9 NRF_DEFAULT_IRQ_PRIORITY>;

status = "disabled";

label = "UART_1";

};

uart2: uart@a000 {

compatible = "nordic,nrf-uarte";

reg = <0xa000 0x1000>;

interrupts = <10 NRF_DEFAULT_IRQ_PRIORITY>;

status = "disabled";

label = "UART_2";

};

RE: UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

Einarh — Thu, 03 Mar 2022 12:43:27 GMT

I'm not sure those #include lines need to be in your overlay file, any specific reason you put them there?

Otherwise it looks as I'd expect.

When you add all this to your project, does it work?

If not, what errors do you get while building?

Do you see "Found devicetree overlay" when the project builds?

-Einar

RE: UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

Deepak Aagri — Thu, 03 Mar 2022 12:02:53 GMT

if i include this CONFIG_UART_2_NRF_UARTE=y

I am this error....

------------------------------------------------------------------------------------------------------------

Merged configuration 'c:/Users/kumarde/ncs/v1.9.0/nrf/samples/nrf9160/lwm2m_client/prj.conf'
Merged configuration 'c:/Users/kumarde/ncs/v1.9.0/nrf/samples/nrf9160/lwm2m_client/boards/nrf9160dk_nrf9160_ns.conf'
Merged configuration 'C:/Users/kumarde/ncs/v1.9.0/nrf/samples/nrf9160/lwm2m_client/build/zephyr/misc/generated/extra_kconfig_options.conf'

error: UART_2_NRF_UARTE (defined at c:\Users\kumarde\ncs\v1.9.0\nrf\samples\nrf9160\lwm2m_client\build\drivers\serial\Kconfig.nrfx:198) is assigned in a configuration
file, but is not directly user-configurable (has no prompt). It gets its value indirectly from other
symbols. See docs.zephyrproject.org/.../CONFIG_UART_2_NRF_UARTE.html
and/or look up UART_2_NRF_UARTE in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

CMake Error at C:\Users\kumarde\ncs\v1.9.0\zephyr\cmake\kconfig.cmake:272 (message):
command failed with return code: 1
Call Stack (most recent call first):
C:\Users\kumarde\ncs\v1.9.0\zephyr\cmake\app\boilerplate.cmake:544 (include)
C:\Users\kumarde\ncs\v1.9.0\zephyr\share\zephyr-package\cmake\ZephyrConfig.cmake:24 (include)
C:\Users\kumarde\ncs\v1.9.0\zephyr\share\zephyr-package\cmake\ZephyrConfig.cmake:35 (include_boilerplate)
c:\Users\kumarde\ncs\v1.9.0\nrf\samples\nrf9160\lwm2m_client\build\CMakeLists.txt:9 (find_package)

-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'c:\Users\kumarde\ncs\v1.9.0\toolchain\opt\bin\cmake.EXE' '-DWEST_PYTHON=c:\Users\kumarde\ncs\v1.9.0\toolchain\opt\bin\python.exe' '-Bc:\Users\kumarde\ncs\v1.9.0\nrf\samples\nrf9160\lwm2m_client\build' '-Sc:\Users\kumarde\ncs\v1.9.0\nrf\samples\nrf9160\lwm2m_client' -GNinja -DBOARD=nrf9160dk_nrf9160_ns -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=On -DNCS_TOOLCHAIN_VERSION:STRING=NONE -DBOARD_ROOT:STRING=c:/Users/kumarde/ncs/v1.9.0/nrf/samples/nrf9160/lwm2m_client -DCONFIG_DEBUG_OPTIMIZATIONS:STRING=y -DCONFIG_DEBUG_THREAD_INFO:STRING=y -DDTC_OVERLAY_FILE:STRING=c:/Users/kumarde/ncs/v1.9.0/nrf/samples/nrf9160/lwm2m_client/boards/nrf9160dk_nrf9160_ns.overlay '-DCONF_FILE:STRING=c:/Users/kumarde/ncs/v1.9.0/nrf/samples/nrf9160/lwm2m_client/prj.conf;c:/Users/kumarde/ncs/v1.9.0/nrf/samples/nrf9160/lwm2m_client/boards/nrf9160dk_nrf9160_ns.conf'
The terminal process terminated with exit code

Best Regards

Deepak Aagri

RE: UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

Deepak Aagri — Thu, 03 Mar 2022 11:29:46 GMT

Is this my "nrf9160dk_uart2_nrf9160_ns.overlay" file correct?

-------------------------------------------------------------------------------------------------------------------------

#include <nordic/nrf9160ns_sica.dtsi>
#include "nrf9160dk_nrf9160_common.dts"

/ {
chosen {
zephyr,uart=&uart2;
};
};

&uart2 {
compatible = "nordic,nrf-uarte";
current-speed = <115200>;
status = "okay";
label = "UART_2";
tx-pin = <24>;
rx-pin = <23>;
/* Set to FFFFFFFF to disconnect/disable */
rts-pin = <0xFFFFFFFF>;
cts-pin = <0xFFFFFFFF>;

};

------------------------------------------------------------------------------------

I am planning to add this file in Board folder of project

and

In prj.conf file includes >>

CONFIG_SERIAL=y
CONFIG_TRUSTED_EXECUTION_NONSECURE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_UART_2_NRF_UARTE=y

---------------------------------------------------------------------------------

Is this correct way? Could you please help me ...

Best Regards

Deepak Aagri

RE: UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

Einarh — Thu, 03 Mar 2022 09:10:04 GMT

Yes you can enable it manually, and that's what you're supposed to do.

But you don't edit the devicetree file itself, you add a devicetree overlay file to your project.

You would know this if you read through what I sent you.

Please read the devicetree documentation, and about how to use devicetree overlays here.

-Einar

RE: UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

Deepak Aagri — Wed, 02 Mar 2022 16:29:57 GMT

I didn't understand shared documents. but i found uart1 can't use for _ns board project :

so i am trying to configure uart2:

In prj.conf

CONFIG_UART_2_NRF_UARTE=y

but it shows this :: CONFIG_UART_2_NRF_UARTE cannot be set (has no prompt) and getting error in compilation.

Compiled Deice tree output showing this:

art2: uart@a000 {

compatible = "nordic,nrf-uarte";

reg = <0xa000 0x1000>;

interrupts = <10 NRF_DEFAULT_IRQ_PRIORITY>;

status = "disabled";

label = "UART_2";

tx-pin = <24>;

rx-pin = <23>;

==========================================================================

can we enable in device tree: manually?

uart2: uart@a000 {

compatible = "nordic,nrf-uarte";

reg = <0xa000 0x1000>;

interrupts = <10 NRF_DEFAULT_IRQ_PRIORITY>;

status = "disabled";

label = "UART_2";

};

and

&uart2 {

status = "okay";

current-speed = <115200>;

tx-pin = <24>;

rx-pin = <23>;

rx-pull-up;

};

Best Regards

Deepak

RE: UART0 RX interrupt stuck in while loop doesn't allow lwm2m function to run?

Einarh — Wed, 02 Mar 2022 15:18:24 GMT

Hello!

In terminal it's waiting for next RX value. which doesn't allow to run other function.

I think it's a bad idea to place your uart read code in an ISR, for exactly the reason you mention that other functions get starved while the high priority ISR is waiting for the uart device.

Instead I would make a lower priority thread that takes care of your uart reading, that you can signal to with a semaphore from your ISR.

How we can switch UART0 to UART1?

When you call device_get_binding("UART_0"), you are using Zephyr's Devicetree API to access your device.

You can find the devicetree file in your application folder as build/zephyr/zephyr.dts

If you look up the uart nodes in this file you'll find that uart_1 is disabled by default in the lwm2m_client project (status = "disabled").

One way to change this is by adding a devicetree overlay file to your project. Please refer to Zephyr's introduction to devicetree to learn how to do this.

Best regards,

Einar