Got NRF_FAULT_ID_SD_ASSERT on S130 while doing sd_ble_gatts_hvx

[codezork]

When I repeatedly (>290 times) send the same notification to the connected host via sd_ble_gatts_hvx, I get a sd_assertion:

Fault identifier:  0x1
Program counter:   0x104FA
Fault information: 0x0
Fault identifier:  0x1
Program counter:   0x14D98
Fault information: 0x0

The payload is 10 bytes long, using S130 with SDK 12.1 on the PCA10028. sd_ble_tx_packet_count_get always returns 7 and the event BLE_EVT_TX_COMPLETE comes after every notification. I am trying to notify repeatedly a sensor reading to a connected host. The assertion sometimes comes after less readings or more. Can anybody give me a hint on that?

Here is the EmBlitz project: notifytest.zip

Here the Android host project: bluenodes.apk

The oscillogram showing disable_irq/enable_irq activities:

[codezork]

No, unfortunatly this error doesn't occur. The function itself works perfect. The SD 130 fails somehow internally. Every time at the same address. Somebody at Nordic could say what is done at the location 0x104FA.

[Petter Myhre]

You could get an assert at 0x104FA if you are not ending a timeslot in time. Could that be the case?

[codezork]

This could be the case. But, as there are no peripherals envolved in this test, it must be a problem in the timeslot processing of the mesh stuff. There is a rtc timer job counting up and sending the value to the host device - that's all. Maybe trond-snekvik has a clue to that.

[Petter Myhre]

Could you share your complete project? Or a project that exhibits the behavior?

[codezork]

Can I upload something here?