Hi,
I'm using nRF52810 with SDK 17.02.
When I don't download bootloader my application worked normally. After I downloaded bootloader, there logging NRF_ERROR_SVC_HANDLER_MISSING.
Hi,
I'm using nRF52810 with SDK 17.02.
When I don't download bootloader my application worked normally. After I downloaded bootloader, there logging NRF_ERROR_SVC_HANDLER_MISSING.
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?
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.
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?
Taylor 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.
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.