nrf52-mesh-light-switch-client-server-proxy-master add uart module

RE: nrf52-mesh-light-switch-client-server-proxy-master add uart module

Kamo — Fri, 26 Jul 2019 12:45:27 GMT

Hi Enzo.

Am strugle with the same issue.

Looking at the one, you are quite succes.

Could you attache project file (am guess in SES)?

Thanks forward,

Kamo.

RE: nrf52-mesh-light-switch-client-server-proxy-master add uart module

haakonsh — Mon, 03 Dec 2018 16:15:07 GMT

What is the value of data field of the app_uart event? From app_uart.h :

/**@brief Struct containing events from the UART module.
 *
 * @details The app_uart_evt_t is used to notify the application of asynchronous events when data
 * are received on the UART peripheral or in case an error occured during data reception.
 */
typedef struct
{
    app_uart_evt_type_t evt_type; /**< Type of event. */
    union
    {
        uint32_t error_communication; /**< Field used if evt_type is: APP_UART_COMMUNICATION_ERROR. This field contains the value in the ERRORSRC register for the UART peripheral. The UART_ERRORSRC_x defines from nrf5x_bitfields.h can be used to parse the error code. See also the \nRFXX Series Reference Manual for specification. */
        uint32_t error_code;          /**< Field used if evt_type is: NRF_ERROR_x. Additional status/error code if the error event type is APP_UART_FIFO_ERROR. This error code refer to errors defined in nrf_error.h. */
        uint8_t  value;               /**< Field used if evt_type is: NRF_ERROR_x. Additional status/error code if the error event type is APP_UART_FIFO_ERROR. This error code refer to errors defined in nrf_error.h. */
    } data;
} app_uart_evt_t;

Non-blocking means that you continue executing code when you wait for a state change instead of blocking execution:

change_state();

while(!state_changed); // Blocking function 

do_stuff();

do_other_stuff(); // Blocked function

-------------------------- VS ----------------------------

change_state();
do_other_stuff(); // Not blocked


void some_event_handler(bool state_changed) 
{
    if(state_changed)
    {
        do_stuff();
    }
}

RE: nrf52-mesh-light-switch-client-server-proxy-master add uart module

Enzo — Mon, 03 Dec 2018 02:14:44 GMT

sorry for the later reply.

"a mistake" means the error APP_UART_COMMUNICATION_ERROR as same as this question.

my example used the uart with easyDMA but I don't know much about non-blocking

RE: nrf52-mesh-light-switch-client-server-proxy-master add uart module

haakonsh — Thu, 29 Nov 2018 10:08:55 GMT

I need you to define "a mistake", I can not help you if I do not know the nature of your problem.

One thing that might solve your problems is using the UARTE — Universal asynchronous receiver/transmitter with EasyDMA peripheral with the UARTE driver in non-blocking mode with DMA. That way your UART communication is almost completely independent from the CPU.

RE: nrf52-mesh-light-switch-client-server-proxy-master add uart module

Enzo — Wed, 28 Nov 2018 06:05:16 GMT

I got something new.

I tried to modify FIFO BUFFER SIZE RX and TX to a maximum of 2048. I found that if sent and received 5 bytes per 200 ms. There will be no mistakes. But more than 5 bytes will make a mistake.
In addition, I tried to modify the priority parameter in the function uart_init() to be high priority. There was no error every 200 ms when the test received and sent 20 bytes. The question now is whether changing priorities will have any other impact.

APP_IRQ_PRIORITY_LOWEST-->APP_IRQ_PRIORITY_HIGH

RE: nrf52-mesh-light-switch-client-server-proxy-master add uart module

Enzo — Wed, 28 Nov 2018 02:57:13 GMT

Hi haakonsh.

thanks for your reply.

I found these defines,

/* Bit 3 : Break condition */
#define UART_ERRORSRC_BREAK_Pos (3UL) /*!< Position of BREAK field. */
#define UART_ERRORSRC_BREAK_Msk (0x1UL << UART_ERRORSRC_BREAK_Pos) /*!< Bit mask of BREAK field. */
#define UART_ERRORSRC_BREAK_NotPresent (0UL) /*!< Read: error not present */
#define UART_ERRORSRC_BREAK_Present (1UL) /*!< Read: error present */

/* Bit 2 : Framing error occurred */
#define UART_ERRORSRC_FRAMING_Pos (2UL) /*!< Position of FRAMING field. */
#define UART_ERRORSRC_FRAMING_Msk (0x1UL << UART_ERRORSRC_FRAMING_Pos) /*!< Bit mask of FRAMING field. */
#define UART_ERRORSRC_FRAMING_NotPresent (0UL) /*!< Read: error not present */
#define UART_ERRORSRC_FRAMING_Present (1UL) /*!< Read: error present */

/* Bit 1 : Parity error */
#define UART_ERRORSRC_PARITY_Pos (1UL) /*!< Position of PARITY field. */
#define UART_ERRORSRC_PARITY_Msk (0x1UL << UART_ERRORSRC_PARITY_Pos) /*!< Bit mask of PARITY field. */
#define UART_ERRORSRC_PARITY_NotPresent (0UL) /*!< Read: error not present */
#define UART_ERRORSRC_PARITY_Present (1UL) /*!< Read: error present */

/* Bit 0 : Overrun error */
#define UART_ERRORSRC_OVERRUN_Pos (0UL) /*!< Position of OVERRUN field. */
#define UART_ERRORSRC_OVERRUN_Msk (0x1UL << UART_ERRORSRC_OVERRUN_Pos) /*!< Bit mask of OVERRUN field. */
#define UART_ERRORSRC_OVERRUN_NotPresent (0UL) /*!< Read: error not present */
#define UART_ERRORSRC_OVERRUN_Present (1UL) /*!< Read: error present */

thanks for your suggestion, I will try.

RE: nrf52-mesh-light-switch-client-server-proxy-master add uart module

haakonsh — Tue, 27 Nov 2018 11:58:58 GMT

APP_UART_COMMUNICATION_ERROR

From app_uart_evt_t :

uint32_t app_uart_evt_t::error_communication

Field used if evt_type is: APP_UART_COMMUNICATION_ERROR. This field contains the value in the ERRORSRC register for the UART peripheral. The UART_ERRORSRC_x defines from nrf5x_bitfields.h can be used to parse the error code. See also the nRF5 Series Reference Manual for specification.

I need you to share the value of the UARTs ERRORSRC register.

I suggest using HW Flow Control, or the UARTE — Universal asynchronous receiver/transmitter with EasyDMA peripheral with UARTE driver.