nrf52832 Uart SDK14

RE: nrf52832 Uart SDK14

T_chapelle — Wed, 17 Jan 2018 13:42:47 GMT

Sorry I didn't took the time to explain all the steps but i though it would take too long to do it. At the same time I did restart from scratch the migration and managed to find the problem.

As i said, i disabled the easyDma ( #define UART_EASY_DMA_SUPPORT 0 #define UART0_CONFIG_USE_EASY_DMA 0) but what did the trick was commenting the line #define UARTE_PRESENT in nrf52832_peripherals.h. Since then, the uart with HW flow control is working fine at 115200. If anyone have an explanation, i would be glad to hear it. I will set this comment as an answer if no tech tell me i'm wrong.

Thanks for the support Sigurd !

RE: nrf52832 Uart SDK14

Sigurd — Mon, 08 Jan 2018 08:45:21 GMT

Since it worked fine before migrating to SDK 14, there is probably something you missed when you migrated. Could you explain the steps you did when you migrated to SDK 14 ?

RE: nrf52832 Uart SDK14

T_chapelle — Wed, 03 Jan 2018 15:55:05 GMT

I'm still struggling with this problem and could really use some guidance on the topic :-(

RE: nrf52832 Uart SDK14

T_chapelle — Mon, 18 Dec 2017 07:30:59 GMT

What pins are you using for UART?

#define RX_PIN_NUMBER  6
#define TX_PIN_NUMBER  5
#define CTS_PIN_NUMBER 7
#define RTS_PIN_NUMBER 8
#define HWFC           true

Does it make any difference if you set the priority to APP_IRQ_PRIORITY_HIGH ? No difference

Do you have UART0_CONFIG_USE_EASY_DMA set to 1 in sdk_config.h ? No, it's set to 0

Did you have this issue when you used "SDK12/s132 version 3.0" ? No i didn't have the problem. The main change i've done for the migration from the sdk 12 of the program concern BLE functions.

Does it make any difference if you turn off the nrf_log module ? I.e. set NRF_LOG_ENABLED to 0 in sdk_config.h ? NRF_LOG_ENABLED is already set to 0

Have you done the migration for the nrf_log ? No i didn't (i will look to it)

RE: nrf52832 Uart SDK14

Sigurd — Sun, 17 Dec 2017 23:19:16 GMT

What pins are you using for UART?

Does it make any difference if you set the priority to APP_IRQ_PRIORITY_HIGH ?

Do you have UART0_CONFIG_USE_EASY_DMA set to 1 in sdk_config.h ?

Did you have this issue when you used "SDK12/s132 version 3.0" ?

Does it make any difference if you turn off the nrf_log module ? I.e. set NRF_LOG_ENABLED to 0 in sdk_config.h ?

Have you done the migration for the nrf_log ? See here.

RE: nrf52832 Uart SDK14

T_chapelle — Wed, 13 Dec 2017 09:44:45 GMT

Yes, i do call app_uart_get in the uart_event_handle fonction that i initialized in :

const app_uart_comm_params_t comm_params =
{
    RX_PIN_NUMBER,
    TX_PIN_NUMBER,
    RTS_PIN_NUMBER,
    CTS_PIN_NUMBER,
APP_UART_FLOW_CONTROL_ENABLED, 
    false,
UART_BAUDRATE_BAUDRATE_Baud115200
};

APP_UART_FIFO_INIT( &comm_params,
                   UART_RX_BUF_SIZE,
                   UART_TX_BUF_SIZE,
                   uart_event_handle,
		APP_IRQ_PRIORITY_LOW,
                   err_code);

and in the uart_event_handle :

void uart_event_handle(app_uart_evt_t * p_event)
{
	uint8_t serial_char;
	uint16_t i;

    switch (p_event->evt_type)
    {
    case APP_UART_DATA_READY:

			if(app_uart_get(&serial_char) == NRF_SUCCESS)
			{
...

RE: nrf52832 Uart SDK14

Sigurd — Tue, 12 Dec 2017 22:45:45 GMT

The nRF5x RTS pin is set high when the nRF5x is unable to receive more bytes, i.e. when buffers are full, and want to stop the sending device sending until you've read the data which already came in so you don't lose it. Are you reading the data which comes in?

Since you are basing your code on ble_app_uart(BLE NUS example), are you calling app_uart_get()when you get the APP_UART_DATA_READY event ?

RE: nrf52832 Uart SDK14

T_chapelle — Fri, 08 Dec 2017 14:37:37 GMT

Further investigations : i added a app_timer and when it expire, called the following functions : app_uart_flush(); app_uart_close(); uart_init(); // as in ble_app_uart example

After that the uart communication is back for a while, but when i do some ble transfer, it fail again and I can see the RTS line held high before the timer expire.

RE: nrf52832 Uart SDK14

T_chapelle — Thu, 07 Dec 2017 07:23:08 GMT

My mistake, it's the RTS pin that stay high (sorry for that)

RE: nrf52832 Uart SDK14

Sigurd — Wed, 06 Dec 2017 15:19:48 GMT

The CTS pin is a input pin for the nRF52, and if the pin is high, then the STM32 is the one setting this pin high. Indicating to the nRF52 that the STM32 is not ready to receive any data.

RE: nrf52832 Uart SDK14

T_chapelle — Mon, 04 Dec 2017 07:58:04 GMT

Yes i tried debugging and everything else is working fine (BLE, leds, buttons), the app is not running into the error-handler.

RE: nrf52832 Uart SDK14

Sigurd — Sun, 03 Dec 2017 15:51:37 GMT

Hi,

Have you tried debugging, and seeing if you are running into the error-handler ? See this post on debugging.