uart_tx api crashing issue

RE: uart_tx api crashing issue

AHaug — Thu, 21 Apr 2022 13:41:18 GMT

Hi,

I am not able to reproduce the error using a nRF52833DK in NCS v1.9.1 in VS Code and changing only

    struct uart_data_t *buf = k_fifo_get(&fifo_uart_rx_data, K_FOREVER);
    
    if (uart_tx(uart, buf->data, buf->len, SYS_FOREVER_MS)) {
		LOG_WRN("Failed to send data over UART");
	}

    struct uart_data_t *buf = k_fifo_get(&fifo_uart_rx_data, K_FOREVER);
    
    if (uart_tx(uart, "UartDataRxed\n", 13, SYS_FOREVER_MS)) {
		LOG_WRN("Failed to send data over UART");
	}

I was able to force a bus fault by adding " uart_tx(uart, "UartDataRxed\n", 13, SYS_FOREVER_MS);" in the case UART_TX_DONE: before any checks are done, which results in a thread interruption fault with the same zephyr error you got caused by. This error and crash is triggered by ,C:/Nordic/SDKs/ncs/v1.9.1/zephyr/kernel/thread.c:819(r15/pc) and C:/Nordic/SDKs/ncs/v1.9.1/zephyr/include/spinlock.h:129 (r14/lr), but I can't guarantee that this interruption error is what caused the issue for you.

If you can add the central_uart project with the modifications and add it here, I can take a closer look if I either have misunderstood where you've done the change or if any other changes has happened by a mistake.

Kind regards,
Andreas

RE: uart_tx api crashing issue

PingISTL — Thu, 21 Apr 2022 07:14:35 GMT

Hi, Andreas

I didn't change anything except that line. I use nrf Connect SDK v1.9.1, and VS Code.

Regards!

Ping

RE: uart_tx api crashing issue

AHaug — Wed, 20 Apr 2022 10:38:18 GMT

Hi,

[quote user="PingISTL"]here is what I did, and cannot go any further - did I misunderstand you?[/quote]

You did it correct. This just means that gnuarmemb is not added to the your system variables, which we need to run the two other lines. If we need to/or you want to try this yourself while we look on the next possible solution, you could perform this step in the manual installation guide. It should allow you to run the two missing lines lines in the prior suggestion.

[quote user="PingISTL"]Thanks for your reply, I changed the length to 14, and it still crashes. don't think it is the length issue.[/quote]

Before we started the command line investigation, you said that your code still crashes. Have you changed anything else in central_uart than than line 162 illustrated as seen below? I am not able to recreate any error by simply editing that line. If your project does not contain any sensitive information, you could add the .c file you're working in by inserting it in a code-snippet in a reply, and I'll take a look.

Also, I should have asked this question earlier: What version of nRF Connect SDK are you working with?

...

// if (uart_tx(uart, buf->data, buf->len, SYS_FOREVER_MS)) {
if (uart_tx(uart, "UartDataRxed\n", 14, SYS_FOREVER_MS)){
	LOG_WRN("Failed to send data over UART");
}

break;

Kind regards,
Andreas

RE: uart_tx api crashing issue

PingISTL — Wed, 20 Apr 2022 08:27:17 GMT

Thanks for reply, Andreas

here is what I did, and cannot go any further - did I misunderstand you?

Ping

RE: uart_tx api crashing issue

AHaug — Tue, 19 Apr 2022 10:46:49 GMT

Hi Ping,

Apologies for the delay in response. The office has been closed due to the recent holidays. Have you figure out the issue since your last reply?

If not, lets check out if the error you've pasted may help us. Could you open a command line window and write the following

1) "where arm-none-eabi-addr2line"

This should return something like

C:\Program Files (x86)\GNU Tools ARM Embedded\4.9 2015q3\bin\arm-none-eabi-addr2line.exe

If it does not return something like this, then we can't do the next steps.

2) We now want to know what causes the error you've pasted. Write now:

arm-none-eabi-addr2line -e <path to _build\zephyr\zephyr.elf> <0xaddr>

where you replace "<path to build>" with your path and <0xaddr> with the R15/pc and R14/lr adress

"arm-none-eabi-addr2line -e <path to _build\zephyr\zephyr.elf> <0x0001e533>" for r15/pc

and

"arm-none-eabi-addr2line -e <path to _build\zephyr\zephyr.elf> <0x0001e820>" for r14/lr

This should (hopefully) return a function or variable that could point to why the cpu has crashed.

Let me know about the progress.

Kind regards,
Andreas

RE: uart_tx api crashing issue

PingISTL — Wed, 13 Apr 2022 15:06:21 GMT

Hi, Andreas

Thanks for your reply, I changed the length to 14, and it still crashes. don't think it is the length issue.

I tried the ehco_bot sample, it is based on interrupt, and it works fine, thank you for sending it. The other sample uses uart_tx function too - not based on interrupt, so for me it has same issue.

Ping

RE: uart_tx api crashing issue

AHaug — Wed, 13 Apr 2022 12:33:37 GMT

Hi Ping,

The string you're trying to pass is not of length 13, but rather it is length 14. Try to change it to 14 and see if it works!

If it does not work, I would recommend you take a look at this NCS Course topic concerning UART to both read up on the essentials as well as examine if the sample in exercise 1 could explain what you're missing. Additionally, this uart echo sample might be of help

Let me know if any of this helps!

Kind regards,
Andreas