Fatal error with uart_config(void) on nRF52840 SDK15.0 S140

RE: Fatal error with uart_config(void) on nRF52840 SDK15.0 S140

Jørgen Holmefjord — Thu, 06 Sep 2018 13:16:16 GMT

Since nRF52840 have two UART instances, you can try to change the UART instance used by app_uart to 1:

#define APP_UART_DRIVER_INSTANCE 1

Note that you will have to enable UARTE1 in the config as well. You have to set the configuration to use EasyDMA, as nRF52840 does not support legacy UART on instance 1.

Another alternative is to use the UART driver directly for the second UART instance, or use NRF_serial library.

You can also change the logger backend to use RTT to output the logs. This will free up UART0 for use for other purposes:

#define NRF_LOG_BACKEND_RTT_ENABLED 1
#define NRF_LOG_BACKEND_UART_ENABLED 0

The RTT logs can be viewed using J-Link RTT Viewer, or in the terminal window of Segger Embedded Studio while debugging.

RE: Fatal error with uart_config(void) on nRF52840 SDK15.0 S140

lmouelo — Thu, 06 Sep 2018 09:58:01 GMT

Yes but if i disable the NRF_LOG i will can't see the values of my component

RE: Fatal error with uart_config(void) on nRF52840 SDK15.0 S140

Jørgen Holmefjord — Thu, 06 Sep 2018 09:04:43 GMT

You need to disable NRF_LOG module if you want to use the UART. You have the logger module enabled and configured to use the UART as the logger backend. The UART driver have already been initialized for the UART instance when you initialized NRF_LOG and it cannot be initialized again for use with app_uart.

You can disable logging by setting '#define NRF_LOG_ENABLED 0' in sdk_config.h, or you can disable the UART backend by setting '#define NRF_LOG_BACKEND_UART_ENABLED 0'

RE: Fatal error with uart_config(void) on nRF52840 SDK15.0 S140

lmouelo — Thu, 06 Sep 2018 07:38:33 GMT

I joined the complete project.

RE: Fatal error with uart_config(void) on nRF52840 SDK15.0 S140

lmouelo — Thu, 06 Sep 2018 07:38:04 GMT

devzone.nordicsemi.com/.../twi_5F00_sensor.zip