Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

RE: Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

Kriki — Sun, 17 Jul 2022 08:26:17 GMT

Hello,
Sorry for the long wait.

I have found out what i have to do to get the UARTE Driver to work with the "normal" (Zephyr based) Async Api.

You dont have to implement the UARTE Driver directly you just have to enable

CONIFG_UARTE
CONFIG_UARTE_x ( where x is youre instance etc)

As for the Questions you had:
1. Yes im very sure i build it for the NS Target it might hat something to do with the Fact that i just used a normal char buffer.

2.It was identical to the other nrf91 implementation.

In General the rewrite just made sure that it wasnt a weird Logic Fault or something,
otherwise the new Code was very similar to the Codes and KConfigs i posted here earlier.

This Driver also solved the Problem i had in this Ticket.https://devzone.nordicsemi.com/f/nordic-q-a/88947/isr-error-in-asynchronous-uart-rx-tx-crashing-zephyr-when-using-bluetooth-ncs-v1-9-1

I have my implementation here for anyone maybe having the same problem.
devzone.nordicsemi.com/.../uart_5F00_drv.rar

Still thank you for your help

Regards,
Nick

RE: Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

Jared — Thu, 07 Jul 2022 13:20:50 GMT

Hi,

For the nRF9160 case:

Are you still building the project in non secure mode? Can you share the code and prj.config for this, it seems that you're using the incorrect instance.

For the nRF52840:

A bit unsure what happens with the nRF52840. Could you also share the code and prj.config file for this one?

regards

Jared

RE: Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

Kriki — Fri, 01 Jul 2022 13:41:02 GMT

Hello,

Sorry for this mess of a Help Request.

The build from the last Error Message was the nrf52840 Build.
That Error Message occurs when i use the KCONFIG Option

CONFIG_UART_ASYNC_API=y
CONFIG_UART_1_NRF_HW_ASYNC=y
CONFIG_UART_1_NRF_HW_ASYNC_TIMER=1

and

CONFIG_NRFX_UARTE=y

together. I do not know why

I have rewritten the Applications.

For the nrf52840 i use

build target is nrf52840dk_nrf52840

IRQ_DIRECT_CONNECT(UARTE1_IRQn, 0, uart_event_handler, 0);

For the nrf9160 i use

build target is nrf9160dk_nrf9160_ns

IRQ_DIRECT_CONNECT(UARTE1_SPIM1_SPIS1_TWIM1_TWIS1_IRQn, 0, uart_event_handler, 0);

I tried tx and rx with both devices neither complete either task.
For the nrf52:

It "completes" the tx but repeatedly calls the uart_event_handler with a unknown event code

00> [00:00:00.378,448] <inf> main: All Initialized
00> [00:00:00.378,753] <inf> app_uart: app_uart_send, length:10
00> [00:00:00.379,089] <inf> app_uart: Trying to TX
00> [00:00:00.380,249] <err> app_uart: Unknown Case 8669
00> [00:00:00.380,584] <err> app_uart: Unknown Case 8669

For the nrf92:

It does not complete the Tx and hard crashes with following LOG

00> [00:00:00.493,865] <inf> main: All Initialized
00> [00:00:00.494,171] <inf> app_uart: app_uart_send, length:10
00> [00:00:00.494,537] <inf> app_uart: Trying to TX
00> [00:00:00.495,727] <err> os: Exception occurred in Secure State
00> [00:00:00.496,093] <err> os: ***** HARD FAULT *****
00> [00:00:00.496,398] <err> os:   Fault escalation (see below)
00> [00:00:00.496,765] <err> os: ***** BUS FAULT *****
00> [00:00:00.497,070] <err> os:   Precise data bus error
00> [00:00:00.497,375] <err> os:   BFAR Address: 0x50008158
00> [00:00:00.497,741] <err> os: r0/a1: 0x00000000 r1/a2: 0x00000000 r2/a3: 0x00000000
00> [00:00:00.498,199] <err> os: r3/a4: 0x00000000 r12/ip: 0x00000000 r14/lr: 0xffffffbc
00> [00:00:00.498,657] <err> os: xpsr: 0x01000000
00> [00:00:00.498,992] <err> os: Faulting instruction address (r15/pc): 0x00010676
00> [00:00:00.499,420] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
00> [00:00:00.499,847] <err> os: Current thread: 0x2000c6b8 (unknown)

If you need any other Details. Please let me know

Also i dont know why but i cant reply to some of your replies.

Regards

Nick

RE: Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

Jared — Wed, 29 Jun 2022 08:19:00 GMT

You're building it in non secure mode. The error log specified register 0x50008158 which points to the UARTE0 Secure peripheral not the non secure peripheral which lies at 0x40008000. Can you double check that you're using the correct instance?

RE: Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

Kriki — Mon, 27 Jun 2022 15:43:27 GMT

I build using the nrf9160dk_nrfn9160_ns build target.
Also i accidentally misclicked and verified your last reply

RE: Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

Jared — Mon, 27 Jun 2022 13:20:09 GMT

Hi,

Are you building it from non-secure for the nRF9160?

regards

Jared

RE: Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

Kriki — Tue, 21 Jun 2022 16:18:38 GMT

I accidentally built it for the nrF9160 which explains why it didnt Compile.

I since changed it to use "UARTE1_SPIM1_SPIS1_TWIM1_TWIS1_IRQn" as it seemed to be the only UARTE related Interrupt but using this crashes the 9160 with this Errorlog

00> [00:01:08.228,729] <err> os: Exception occurred in Secure State
00> [00:01:08.229,095] <err> os: ***** HARD FAULT *****
00> [00:01:08.229,431] <err> os:   Fault escalation (see below)
00> [00:01:08.229,797] <err> os: ***** BUS FAULT *****
00> [00:01:08.230,133] <err> os:   Precise data bus error
00> [00:01:08.230,468] <err> os:   BFAR Address: 0x50008158
00> [00:01:08.230,834] <err> os: r0/a1:  0x00000000  r1/a2:  0x2000d7f4  r2/a3:  0x00000000
00> [00:01:08.231,323] <err> os: r3/a4:  0x2000c8fc r12/ip:  0x0000000a r14/lr:  0x000106cf
00> [00:01:08.231,842] <err> os:  xpsr:  0x61000000
00> [00:01:08.232,177] <err> os: Faulting instruction address (r15/pc): 0x000106ce
00> [00:01:08.232,635] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
00> [00:01:08.233,093] <err> os: Current thread: 0x2000c7a0 (unknown)

I then tried using the Zephyr Uart Driver on the nRF9160 an the UARTE Driver on the nRF52840.

The Tx from 52->91 works but the Tx from 91->52 doesnt.

Also when Tx from 52->91 the Uarte Eventhandler gets called repedeatly with the Eventtype 31.

RE: Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

Jared — Tue, 21 Jun 2022 13:27:09 GMT

Is this when you build for the nRF52840 or the nRF9160? Could you share the entire error log?

RE: Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

Kriki — Mon, 20 Jun 2022 10:43:38 GMT

Hello,
Do you by chance know which Header to include ?
VS Code tells me that it cant find "UARTE1_IRQn" and the file you linked to isnt in the 1.9.1 version of the ncs

Regards,

Nick

RE: Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

Jared — Mon, 20 Jun 2022 09:28:44 GMT

Hi,

Good, but you also need to connect the IRQ to the handler, as in this case for the PWM peripheral. You can use the UARTE1_IRQn.

regards

Jared

RE: Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

Kriki — Mon, 20 Jun 2022 09:21:18 GMT

Hello,

Yes i did.

Here is the relevant Codedevzone.nordicsemi.com/.../7585.app_5F00_uart.rar

Regards

Nick

RE: Implementing UARTE on a Bluetooth Enabled DK (ncs v1.9.1)

Jared — Mon, 20 Jun 2022 09:17:04 GMT

Hi,

Have you added a callback handler for the UARTE driver?

regards

Jared