Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

Kenneth — Tue, 02 Jul 2019 11:52:06 GMT

I expect it may occur more frequently if there is more BLE activity in general. One question though, what is the detailed chip markings on the nRF52832 IC you are using? Do you have products in the market already, or can you order revision 2 of the nRF52832?
https://infocenter.nordicsemi.com/topic/comp_matrix_nrf52832/COMP/nrf52832/ic_revision_overview.html?cp=3_1_2_0

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

bds — Mon, 24 Jun 2019 13:17:52 GMT

Is the issue also related to central behavior, or bluetooth activity in the environment?

We updated our bluetooth central code (running on a Raspberry Pi), and now the issue suddenly appears to happen a lot more frequently, and on a lot more devices. Not sure if there is any relation.

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

Kenneth — Mon, 10 Jun 2019 14:57:26 GMT

[quote user="bds"]Is there a work around, or some way to avoid it?[/quote]

Unfortunately no.

With "allow these asserts" I meant that you allow a soft reset once a ~week due to the assert. It is somewhat hardware related yes, though the only way to avoid the issue altogether is to update softdevice.

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

bds — Fri, 07 Jun 2019 10:17:08 GMT

Hi,

do you have some more information on what exactly causes the assert?

Is there a work around, or some way to avoid it?

It seems hardware related as we have some boards that never have the problem, and some that show it regularly.

What do you mean with "allow these asserts"? Does it mean we can ignore them and just keep running? Or do we need take action and call some softdevice functions?

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

Kenneth — Wed, 05 Jun 2019 12:04:24 GMT

Hi,

It seems you have found a known issue with S132v3.x softdevices, with the your latest error code I can find it's been fixed in S132v4.0.4 and S132v4.0.5, from the release notes in S132v4.0.5:

"Fixed an issue which could cause an assert while running advertiser or scanner (DRGN-9044). (This was also fixed in 4.0.4.)"

So I guess you must either update (see migration document in S132v4.0.0 release on how to) or allow these rare asserts in S132v3.x release.

Best regards,
Kenneth

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

bds — Tue, 04 Jun 2019 08:19:29 GMT

We updated to S132v3.1, and now get:

Fault identifier: 0x1
Program counter: 0x10A62
Fault information: 0x0

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

Kenneth — Wed, 27 Mar 2019 14:14:53 GMT

In general I recommend to use S132v3.1, so please download S132v3.1, update the S132 softdevice header files and program the S132v3.1 binary:

https://www.nordicsemi.com/Software-and-Tools/Software/S132

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

Kenneth — Wed, 27 Mar 2019 13:54:04 GMT

Hi, max time for critical region is intended to be used only for a few us, in other words simply set or clear a flag inside the critical region. At least it is the place I would have started to look for this assert.

Best regards,
Kenneth

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

bds — Wed, 27 Mar 2019 13:01:02 GMT

The critical region enter macro only disables application interrupts, right?

How can it then cause a Softdevice assert?

What time is acceptable to spend in a critical region?

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

Eddie — Wed, 27 Mar 2019 12:38:52 GMT

We are using critical regions, but only copy some data in them at this point. We logged the time inside critical regions and never use more than 1ms. Some of the critical regions are nested though, could that cause a problem?

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

Kenneth — Wed, 27 Mar 2019 11:55:42 GMT

Hi, I suspect you are blocking interrupts (e.g. critical region enter) for a long period of time.

Best regards,
Kenneth

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

bds — Tue, 26 Mar 2019 20:55:03 GMT

It's APP_IRQ_PRIORITY_LOW.

RE: Crash due to softdevice assert (id:0x1 pc:0x1089E info:0x0)

Turbo J — Tue, 26 Mar 2019 17:47:18 GMT

Check TWI IRQ priority.