BLE_UART using NRF52810 Chipset

[Lee]

Hi Sir: 

I am using SDK nRF5_SDK_17.0.2,the chip is nRF52810. Using the ble_peripheral\ble_app_uart.

The IO is using P0.6 as the BLE Uart's RX Pin,And P0.7 is used as BLE uart's Tx Pin.

But when i change the Rx Pin as P0.6 ,the system will be crashed .

 I have find ,there is no used the PIN Why?

Best Regards!
James Lee

[Lee]

Hi Edvin:

• What I found was that the system was rebooting all the time.
• We using STM32F745's uart8 to communication withe NRF52810.
• And in mobile phone ,The phenomenon is constantly connected, disconnected, disconnected
• And Finally, it is found that the serial port error processing causes the system to restart
• The data sent by stm32f745 is 0x55, but the data received by nrf52810 is incorrect.

[Lee]

Hi Edvin:

 I have debug and found the system is reset when uart receiving error.

I using the example code.nRF5_SDK_17.0.2_d674dde\examples\ble_peripheral\ble_app_uart\pca10040e

Just only modified the Rx PIN and Tx PIN(Uart).

And remove the button part.

Other not modifed .

[Edvin]

Ok. Where does it reset? Does any of these events occur:

APP_UART_COMMUNICATION_ERROR

APP_UART_FIFO_ERROR

in your uart_event_handle()?

Please check this.

[Lee]

Yes ,in the APP_UART_COMMUNICATION_ERROR will cause the system reset.

And now i configure the Uart's RX PIN is 6,and the tx pin of uart is 7.

And the baudrate is 9600.

There is always the communication error,and the system reset always.

Why did it ?:

I have found the SDK version from 17 to 13.but there is no other verison can support nRF52810.

What's the reason of the Problem ? if there is any can be useful example for ble uart to use ?

[Edvin]

Lee said:

if there is any can be useful example for ble uart to use ?

 The ble_app_uart example can be useful.

Lee said:

Why did it ?:

 This event is caused by communication error. Probably because your RX pin is not connected to anything, or connected to something transmitting on the wrong baudrate. The event is generated when it receives data that doesn't match the baud rate, so possibly a floating non-connected pin that goes high to low without a consistent speed.

Try to comment out the line:

APP_ERROR_HANDLER(p_event->data.error_communication);