Bluetooth (SoftDevice) + high speed UART (libuarte)

RE: Bluetooth (SoftDevice) + high speed UART (libuarte)

Paolo D — Thu, 02 Apr 2020 15:50:45 GMT

I'm able to reproduce this exact same SoftDevice assert, using SoftDevice S132 v7.0.1 with nRF52832. In my app I was intentionally trying to cause an assert to test my error logging function. Disabling interrupts for too long while the SoftDevice is active causes the 0x000156e0 error consistently. I used the following code:

            __disable_irq();
            nrf_delay_ms(1000);
            __enable_irq();

RE: Bluetooth (SoftDevice) + high speed UART (libuarte)

Simonr — Mon, 27 Jan 2020 09:06:15 GMT

Hi Kilian

Please check out this post, which elaborates on a few common problems when using libuarte. This should cover most of the things to look out for when merging it together with other examples. Also, what is your priority interrupt in nrf_libuarte_async.c set to? You can try setting this to 5 in case it is causing conflicts with the SoftDevice.

Best regards,

Simon

RE: Bluetooth (SoftDevice) + high speed UART (libuarte)

VGKilian — Fri, 24 Jan 2020 12:53:02 GMT

Sorry i was wrong. The pc point at 0x00014cbc or 0x000156e0. As far as i know, this should be a part of the SoftDevice.

Is there any other resource, which is used in both examples?

RE: Bluetooth (SoftDevice) + high speed UART (libuarte)

VGKilian — Fri, 24 Jan 2020 09:49:53 GMT

Hi Simon,

i have tried Timer2 & RTC2 (NRF_LIBUARTE_ASYNC_DEFINE(libuarte, 0, 2, 2, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 255, 3)) and Timer2 & Timer3 (NRF_LIBUARTE_ASYNC_DEFINE(libuarte, 0, 2, NRF_LIBUARTE_PERIPHERAL_NOT_USED,3, 255, 3);).

Both with the same result.

I start the program with BLE running, everything works fine. If the UART communication starts the error accrues.

The pc point at nrfx_timer or nrtx_rtc.

Best regards,

Kilian

RE: Bluetooth (SoftDevice) + high speed UART (libuarte)

Simonr — Fri, 24 Jan 2020 08:14:08 GMT

Hi Kilian

The ble_app_uart example uses Timer1 and runs the SoftDevice which uses RTC0 and Timer0, so you're probably having trouble because the ble_app_uart and libuarte are now both trying to use Timer1.

Best regards,

Simon

RE: Bluetooth (SoftDevice) + high speed UART (libuarte)

VGKilian — Thu, 23 Jan 2020 13:53:57 GMT

Hi Dmitry and Simonr,

thanks a lot for your help.

I tried both of our suggested solutions and it takes me a step further.

But now the "app_error_fault_handler" function gets called. The address of the pc is located in nrfx_timer.c.

Could you tell me which timers are used in “ble_app_uart” and “libuarte” examples?

I use Timer1 and Timer2 for the libuarte.

Best Regards,

Kilian

RE: Bluetooth (SoftDevice) + high speed UART (libuarte)

Simonr — Thu, 23 Jan 2020 13:27:02 GMT

Hi Kilian and Dmitry

The nRF52840 has 3 RTCs so you should be able to use RTC2 as well if you don't want to follow Dmitry's advice.

Best regards,

Simon

RE: Bluetooth (SoftDevice) + high speed UART (libuarte)

Dmitry — Thu, 23 Jan 2020 10:25:09 GMT

Hi,

libuarte can use either RTC or TIMER instance:

_rtc1_idx	RTC instance used for timeout. If set to NRF_LIBUARTE_PERIPHERAL_NOT_USED then TIMER instance is used or app_timer instance if _timer1_idx is also set to NRF_LIBUARTE_PERIPHERAL_NOT_USED.
_timer1_idx	TIMER instance used for timeout. If set to NRF_LIBUARTE_PERIPHERAL_NOT_USED then RTC instance is used or app_timer instance if _rtc1_idx is also set to NRF_LIBUARTE_PERIPHERAL_NOT_USED.