question about 52832 system reset

RE: question about 52832 system reset

Vidar Berg — Fri, 26 Jan 2024 07:39:59 GMT

[quote user="Victor A"]1.How can I find the documentation about interrupt priorities reserved to the Softdevice[/quote]

Interrupt model and processor availability

[quote user="Victor A"]2.What are the Softdevice timeslot API？Where can I found？[/quote]

[quote user="Victor A"]

We used the example project:ble_app_uart, which based on sdk14.2.0 and softdevice s112 for testing，only changed the broadcast timeout to zero, This problem will still occur on 52832.

Why the SDK example project also have this problem

[/quote]

This is interesting. Approximately how long does it take to reproduce the assert using this example, and is it the exact same assert as earlier? (i.e., SOFTDEVICE: ASSERTION FAILED PC =0x0000EAC2)

RE: question about 52832 system reset

Victor A — Fri, 26 Jan 2024 02:01:42 GMT

We used the example project:ble_app_uart, which based on sdk14.2.0 and softdevice s112 for testing，only changed the broadcast timeout to zero, This problem will still occur on 52832.

Why the SDK example project also have this problem

RE: question about 52832 system reset

Victor A — Fri, 26 Jan 2024 01:53:31 GMT

1.How can I find the documentation about interrupt priorities reserved to the Softdevice

2.What are the Softdevice timeslot API？Where can I found？

RE: question about 52832 system reset

Vidar Berg — Thu, 25 Jan 2024 12:07:45 GMT

Thank you. The assertion is raised by the SoftDevice scheduler because an allocated timeslot was overstayed. Typical reasons for these kind of asserts are:

1. The application uses interrupt priorities reserved to the Softdevice

2. The application uses the Softdevice timeslot API

3. Interrupts are disabled by the application

4. Continuing execution after having halted the CPU with the debugger.

Does anything of what I have listed above apply to your application?

RE: question about 52832 system reset

Victor A — Thu, 25 Jan 2024 11:54:16 GMT

s112_nrf52810_5.1.0_softdevice.hex

RE: question about 52832 system reset

Vidar Berg — Thu, 25 Jan 2024 11:49:05 GMT

What version of the s112 Softdevice are you using? I need the exact version number to look up the assert.

RE: question about 52832 system reset

Victor A — Thu, 25 Jan 2024 07:52:53 GMT

We get the error code: SOFTDEVICE: ASSERTION FAILED PC =0x0000EAC2

What does this mean?

RE: question about 52832 system reset

Vidar Berg — Tue, 23 Jan 2024 12:15:40 GMT

Hello,

Since resets are typically caused by firmware crashes, I recommend that you debug the devices that have crashed to determine what led to the crash.

Things you can try:

1. Build the FW with the DEBUG flag set to ensure the device is not reset on SDK/SD errors, but rather enter an endless loop in the error handler (Error module). You can then use "nrfjprog --readregs" to connect to one of the devices that have crashed to confirm if program is in the error handler.

2. Read the RESETREAS to determine the reset source.

Best regards,

Vidar