NRF_ERROR_SVC_HANDLER_MISSING PC at 0x00025D3D

Hi,

The error code is actually referring to the UARTE.ERRORSRC bit in this case.  And "1" means you have an OVERRUN error which indicates that your app is not emptying the UART RX buffer fast enough.

When I don't download bootloader

How are you downloading the bootloader? Is it with a programmer, or is that what you are doing over the UART interface when you get the crash?

user4240 said:

How are you downloading the bootloader?

I download soft device and bootloader with J-flash, and update my application with DFU. 

After update my application, this error will happen on UART interface in my application process.

user4240 said:

that your app is not emptying the UART RX buffer fast enough

How could I empty the UART RX buffer? I need to empty the "data_array" when the "data_index" larger than RX_BUFF_SIZE?

The bootloader should not have any affect on how the application runs. Do you always get this error with the bootloader present, and never when it is not?

ColorPen said:

How could I empty the UART RX buffer? I need to empty the "data_array" when the "data_index" larger than RX_BUFF_SIZE?

It's when you are calling app_uart_get() from the callback. So the error basically indicating that the uart callback is not being processed frequently enough. Maybe it is being blocked by some other interrupt.

user4240 said:

The bootloader should not have any affect on how the application runs. Do you always get this error with the bootloader present, and never when it is not?

YES! When I used UART to read AT command of LTE modem with the bootloader present, this error will happen.

Here is the log without log:(my application will repeat AT command)

Here is the log with bootloader:

Hi,

What about the buttonless DFU service, do you initialize it even when the bootloader is not present?

And another thing, could you try to comment the APP_ERROR_HANDLER() call at line ~119 to ignore com. errors,  then check then check if the event gets triggered multiple times or just once.

user4240 said:

And another thing, could you try to comment the APP_ERROR_HANDLER() call at line ~119 to ignore com. errors,  then check then check if the event gets triggered multiple times or just once.

Strangely! Just when I send  "MQTT_QMTOPEN", it will cause this error.

And this only happens when the bootloader is present?

And this only happens when the bootloader is present?

user4240 said:

And this only happens when the bootloader is present?

Yes. If I just download soft device, this application will work normally.

OK, thanks for confirming. I still don't see how the bootloader could be impacting this. Does the MQTT_QMTOPEN command cause the receiver to respond with more data than the other commands?

user4240 said:

MQTT_QMTOPEN command cause the receiver to respond with more data than the other commands?

But I don't edit the application process when I removed bootloader.  

There is not enough information for me to go on here, unfortunately. The bootloader will normally not have any impact on the program execution in the main app.

Please check my video.

Video 1 WITHOUT BOOTLOADER

1.erase chip

2.program SoftDevice

3.download application

Video 2 & 3  WITH BOOTLOADER

1.erase chip

2.program SoftDevice

3.program bootloader

4.DFU by nRFConnect 

5.RTT Viewer log