UART problem NRF9160(Icarus) to ESP8266

RE: UART problem NRF9160(Icarus) to ESP8266

Simon — Thu, 29 Jul 2021 09:43:15 GMT

I'm sorry for the delay on this. When the status of a case is set to 'verified', it is removed from my queue of cases for good. I stumbled upon your reply just now on accident.

Have you made any progress in the last 6 days? When using the nrf91 nonsecure board, the uart1 peripheral is used by the TF-M, maybe you could test using uart2 instead?

Please tell me if you can't get it to work, and I'll take a look

Best regards,

Simon

RE: UART problem NRF9160(Icarus) to ESP8266

GiulianoFranchetto — Fri, 23 Jul 2021 07:53:04 GMT

Hi,

I'd like to follow up on this subject.

I'm trying to use LPUART on nRF5340_cpuappns and nrf9160ns but I can't get it to work.

As you mentioned, every tx is failing with Tx aborted and of course, no data is received on the other end.

"Normal" UART is working perfectly, even with RTS-CTS flow control, so REQ/RDY should also work.

Something even more strange, setting the GPIOTE priority in the DT makes the GPIO unusable with a lot of pin not changing state when calling gpio_pin_set and none of the interrupt firing.

For example, in our board, we are also using a SPIM line to communicate with a sensor, which also has an IRQ line.

If the ```interrupts = <13 NRF_DEFAULT_IRQ_PRIORITY>``` is added to the DT, the communication with the sensor is failing as we don't receive any IRQ even if the hardware line is correct.

Once removing the line from the DT, the irq starts working again.

I may be 1000% wrong, but I have the same feeling as debugging a race condition between 2 modules wanting to use the same memory region or hardware IP at the same time.

Regards

Giuliano

RE: UART problem NRF9160(Icarus) to ESP8266

Simon — Wed, 14 Jul 2021 16:08:48 GMT

It doesn't seem like it is possible to disable req and rdy, but I modified the sample by disabling lpuart (dropping the lpuart driver and using uart.h->uart async api directly), and then it's possible to disable rts and cts.

Here is the sample. It supports both the nrf9160dk_nrf9160 and the nrf9160dk_nrf9160ns.

https://github.com/simon-iversen/sdk-nrf/tree/lpuart_using_normal_uart/samples/peripheral/lpuart

Here is the changes I applied to the lpuart sample:

Best regards,

Simon

RE: UART problem NRF9160(Icarus) to ESP8266

Lemmiwink — Mon, 12 Jul 2021 08:56:30 GMT

How can I use this sample to connect with a device without the req and rdy pin?

RE: UART problem NRF9160(Icarus) to ESP8266

Simon — Mon, 05 Jul 2021 12:05:43 GMT

Try to use some other pins than 46 (P1.14) and 47 (P1.14). The nRF9160 does not support two ports like the nRF52840.

I tried to get the lpuart board working with the nonsecure nrf9160, but I encountered "TX aborted", please get back to me if you encounter the same with your custom board.

RE: UART problem NRF9160(Icarus) to ESP8266

Lemmiwink — Mon, 28 Jun 2021 12:22:24 GMT

I just tested it with your suggested changes and with nRF Connect SDK v1.6.0-rc2. I am using the icarus Board and created the following two documents within lpuart/Boards to get Board support:

/* actinius_icarus_ns.overlay */

&uart1 {
	status = "okay";

	current-speed = <115200>;
	tx-pin = <24>;
	rx-pin = <23>;
	
	lpuart: nrf-sw-lpuart {
                compatible = "nordic,nrf-sw-lpuart";
                status = "okay";
                label = "LPUART";
                req-pin = <46>;
                rdy-pin = <47>;
        };
};

&gpiote {
	interrupts = <13 NRF_DEFAULT_IRQ_PRIORITY>;
};

## actinius_icarus_ns.conf

CONFIG_UART_1_ASYNC=y
CONFIG_UART_1_INTERRUPT_DRIVEN=n
CONFIG_UART_1_NRF_HW_ASYNC=y
CONFIG_UART_1_NRF_HW_ASYNC_TIMER=2
CONFIG_NRFX_TIMER2=y

Unfortunately I get the following outprint after flashing:

E: Could not get GPIO Device Binding
*** Booting Zephyr OS build v2.6.0-rc1-ncs1-rc1  ***
Flash regions           Domain          Permissions
00 01 0x00000 0x10000   Secure          rwxl
02 31 0x10000 0x100000  Non-Secure      rwxl

Non-secure callable region 0 placed in flash region 1 with size 32.

SRAM region             Domain          Permissions
00 07 0x00000 0x10000   Secure          rwxl
08 31 0x10000 0x40000   Non-Secure      rwxl

Peripheral              Domain          Status
00 NRF_P0               Non-Secure      OK
01 NRF_CLOCK            Non-Secure      OK
02 NRF_RTC0             Non-Secure      OK
03 NRF_RTC1             Non-Secure      OK
04 NRF_NVMC             Non-Secure      OK
05 NRF_UARTE1           Non-Secure      OK
06 NRF_UARTE2           Secure          SKIP
07 NRF_TWIM2            Non-Secure      OK
08 NRF_SPIM3            Non-Secure      OK
09 NRF_TIMER0           Non-Secure      OK
10 NRF_TIMER1           Non-Secure      OK
11 NRF_TIMER2           Non-Secure      OK
12 NRF_SAADC            Non-Secure      OK
13 NRF_PWM0             Non-Secure      OK
14 NRF_PWM1             Non-Secure      OK
15 NRF_PWM2             Non-Secure      OK
16 NRF_PWM3             Non-Secure      OK
17 NRF_WDT              Non-Secure      OK
18 NRF_IPC              Non-Secure      OK
19 NRF_VMC              Non-Secure      OK
20 NRF_FPU              Non-Secure      OK
21 NRF_EGU1             Non-Secure      OK
22 NRF_EGU2             Non-Secure      OK
23 NRF_DPPIC            Non-Secure      OK
24 NRF_REGULATORS       Non-Secure      OK
25 NRF_PDM              Non-Secure      OK
26 NRF_I2S              Non-Secure      OK
27 NRF_GPIOTE1          Non-Secure      OK

SPM: NS image at 0x10000
SPM: NS MSP at 0x20011838
SPM: NS reset vector at 0x16111
SPM: prepare to jump to Non-Secure image.
ASSERTION FAIL [i < 8] @ WEST_TOPDIR/nrf/drivers/serial/uart_nrf_sw_lpuart.c:412
        Used channel not found
[00:00:00.000,244] <err> board_control: Could not get GPIO Device Binding
[00:00:00.012,176] <err> os: r0/a1:  0x00000004  r1/a2:  0x0000019c  r2/a3:  0x0                                                                                                             0000001
[00:00:00.012,207] <err> os: r3/a4:  0x00000018 r12/ip:  0x00004000 r14/lr:  0x0                                                                                                             001a4e7
[00:00:00.012,207] <err> os:  xpsr:  0x41000000
[00:00:00.012,237] <err> os: Faulting instruction address (r15/pc): 0x000210b8
[00:00:00.012,268] <err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
[00:00:00.012,268] <err> os: Current thread: 0x20010460 (unknown)
▒E: Could not get GPIO Device Binding Resetting system

Best regards,

Tim

RE: UART problem NRF9160(Icarus) to ESP8266

Simon — Fri, 25 Jun 2021 14:29:18 GMT

I just tested it with NCS v1.6.0 and it worked fine. I did the following changes to enable logging:

https://github.com/nrfconnect/sdk-nrf/compare/nrfconnect:7a076c2...simon-iversen:060b624

I connected P0.10 to P0.11 and P0.12 to P0.13, programmed it and got the following otuput:

*** Booting Zephyr OS build v2.6.0-rc1-ncs1  ***
[00:00:01.349,731] <inf> app: Tx sent 5 bytes
[00:00:01.350,433] <inf> app: Received data 5 bytes
[00:00:01.850,372] <inf> app: Received data 1 bytes
[00:00:01.950,439] <inf> app: Tx sent 5 bytes
[00:00:01.951,141] <inf> app: Received data 5 bytes
[00:00:02.451,049] <inf> app: Received data 1 bytes
[00:00:02.551,147] <inf> app: Tx sent 5 bytes
[00:00:02.551,818] <inf> app: Received data 5 bytes
[00:00:03.051,788] <inf> app: Received data 1 bytes
[00:00:03.151,855] <inf> app: Tx sent 5 bytes
[00:00:03.152,557] <inf> app: Received data 5 bytes
[00:00:03.652,465] <inf> app: Received data 1 bytes
[00:00:03.752,593] <inf> app: Tx sent 5 bytes
[00:00:03.753,265] <inf> app: Received data 5 bytes
[00:00:04.253,204] <inf> app: Received data 1 bytes
[00:00:04.353,302] <inf> app: Tx sent 5 bytes

Try the same and see if you're able to get it to work. By the way, the sample does not support the board nrf9160dk_nrf9160ns, so you have to add it yourself here https://github.com/nrfconnect/sdk-nrf/tree/v1.6.0/samples/peripheral/lpuart/boards.

Best regards,

Simon

RE: UART problem NRF9160(Icarus) to ESP8266

Lemmiwink — Wed, 23 Jun 2021 11:51:40 GMT

This sample just print out: "E: could not get GPIO Device Binding" and then it ends. if I set CONFIG_NRF_SW_LPUART_INT_DRIVEN=y, then it reboots everytime after the same error message. How can I send anything with that sample?

Best regards,

Tim

RE: UART problem NRF9160(Icarus) to ESP8266

Simon — Tue, 22 Jun 2021 15:25:03 GMT

Check out the LPUART sample and see if you're able to communicate with the ESP8266 board.

Best regards,

Simon