NRF52832 MESH with UART

RE: NRF52832 MESH with UART

Edvin — Mon, 09 Mar 2020 08:00:12 GMT

Hello,

Actually I never had this issue. Have you tried the suggestions that were mentioned?

What HW do you use? And what baudrate (on both the nRF and the other end)? Are the RX and TX lines always connected?

RE: NRF52832 MESH with UART

BattleDroid — Mon, 09 Mar 2020 03:57:05 GMT

Hello Edvin,

Were you able to overcome this problem? If so, how? I believe I am seeing the same issue with UARTE0 on nRF52840

RE: NRF52832 MESH with UART

Edvin — Mon, 12 Aug 2019 11:55:04 GMT

Hello,

Do you use baudrate = 9600 in the nRF Project as well?

Can you try to use an analyzer to check that the values on the lines look OK?

Is the UART device connected at all times?

What is your LFCLK configurations in sdk_config.h? Are you using an nRF52832 DK? If not, do you have an external LFXTAL (32kHz), or do you use the RC Oscillator?

RE: NRF52832 MESH with UART

Prasad — Mon, 12 Aug 2019 09:58:10 GMT

Hi Edvin,

As you said my APP_COMMUNICATION_ERROR error code is 4. So according to "nRF52832 Objective Product Specification" ERRORSRC register value is 0b0100. It mean It should be framing error.

In my case RX pin isn't in floating and it's baud rate is 9600 and other MCU also send data in that baud rate.

I tried different methods to overcome this issue, increased buffer size, enable internal pullups but nothing work for me.

So do you have any suggestion for this issue ?

RE: NRF52832 MESH with UART

Edvin — Mon, 29 Jul 2019 13:10:09 GMT

[quote user="Prasad Anuruddhike"]NRF_MESH_IRQ_PRIORITY_LOWEST in APP_UART_FIFO_INIT instead of APP_IRQ_PRIORITY_LOWEST but that won't work for me.[/quote]

why is that?

What do you do in main after Communication ERROR? Do you pass this err_code into the error handler? What is the error value?

RE: NRF52832 MESH with UART

Prasad — Mon, 29 Jul 2019 07:37:51 GMT

Hi Edvin,

Thanks for your advice. I manage to overcome that error. As you said it occurs due to incorrect data receive from other side. When opening the port from other side there is a junk data packet.

Now I'm able to read data through serial. But when data receive continuously I got APP_UART_COMMUNICATION_ERROR again. But this time it has random pattern.

<t:     678274>, main.c,  242, Receive 55 
<t:     678276>, main.c,  242, Receive AA 
<t:     678278>, main.c,  242, Receive 1 
<t:     678280>, main.c,  242, Receive 7 
<t:     678282>, main.c,  242, Receive 0 
<t:     678284>, main.c,  242, Receive 5 
<t:     678286>, main.c,  242, Receive 1 
<t:     678288>, main.c,  242, Receive 1 
<t:     678289>, main.c,  242, Receive 0 
<t:     678291>, main.c,  242, Receive 1 
<t:     678293>, main.c,  242, Receive 0 
<t:     678295>, main.c,  242, Receive F 
<t:     696344>, main.c,  242, Receive 55 
<t:     696346>, main.c,  242, Receive AA 
<t:     696348>, main.c,  242, Receive 1 
<t:     696350>, main.c,  242, Receive 7 
<t:     696352>, main.c,  242, Receive 0 
<t:     696354>, main.c,  242, Receive 5 
<t:     696356>, main.c,  242, Receive 1 
<t:     696358>, main.c,  242, Receive 1 
<t:     696360>, main.c,  242, Receive 0 
<t:     696362>, main.c,  242, Receive 1 
<t:     696364>, main.c,  242, Receive 1 
<t:     696366>, main.c,  242, Receive 10 
<t:     714118>, main.c,  242, Receive 55 
<t:     714120>, main.c,  242, Receive AA 
<t:     714122>, main.c,  242, Receive 1 
<t:     714124>, main.c,  242, Receive 7 
<t:     714126>, main.c,  242, Receive 0 
<t:     714128>, main.c,  242, Receive 5 
<t:     714130>, main.c,  242, Receive 1 
<t:     714132>, main.c,  242, Receive 1 
<t:     714134>, main.c,  242, Receive 0 
<t:     714136>, main.c,  242, Receive 1 
<t:     714137>, main.c,  242, Receive 0 
<t:     714139>, main.c,  242, Receive F 
<t:     732787>, main.c,  242, Receive 55 
<t:     732789>, main.c,  242, Receive AA 
<t:     732791>, main.c,  242, Receive 1 
<t:     732793>, main.c,  242, Receive 7 
<t:     732795>, main.c,  242, Receive 0 
<t:     732797>, main.c,  242, Receive 5 
<t:     732799>, main.c,  242, Receive 1 
<t:     732800>, main.c,  242, Receive 1 
<t:     732802>, main.c,  242, Receive 0 
<t:     732804>, main.c,  242, Receive 1 
<t:     732806>, main.c,  242, Receive 1 
<t:     732808>, main.c,  242, Receive 10 
<t:     752258>, main.c,  361, Communication ERROR
<t:     752261>, app_error_weak.c,  119, Mesh error 1 at 0x00000000 (:0)

One of my friends suggested to set NRF_MESH_IRQ_PRIORITY_LOWEST in APP_UART_FIFO_INIT instead of APP_IRQ_PRIORITY_LOWEST but that won't work for me. Is there any suggestions for overcome this issue ?

APP_UART_FIFO_INIT(&comm_params,
                       UART_RX_BUF_SIZE,
                       UART_TX_BUF_SIZE,
                       uart_event_handle,
                       NRF_MESH_IRQ_PRIORITY_LOWEST,    //APP_IRQ_PRIORITY_LOWEST,     
                       err_code);
    APP_ERROR_CHECK(err_code);

RE: NRF52832 MESH with UART

Edvin — Fri, 26 Jul 2019 08:25:08 GMT

Hello,

The APP_COMMUNICATION_ERROR event tells you that there is something weird happening on the UART. If this event has the value 4, it means that the ERRORSRC register in the UART has the value 0b0100.

If you look in the link it means "Framing error". This is an error you typically get if you either haven't connected the RX pin to anything (It is floating), or that you use the incorrect baud rate. It basically tells you that it has detected movement on the pin, but it doesn't make up an entire byte with the given baudrate.

So is your RX pin connected or floating? And do you use the same baudrate as the device you are connected to?

Best regards,

Edvin