Short version: Can someone from NordicSemi give me some pointers as to what the assertion at PC 0x134A2 in S132 v6.0.0 is testing? Thanks!
Long version: Since the Friend feature is not available in the Mesh SDK yet, I'm doing a proof-of-concept experiment of implementing a low-power Mesh node using GATT proxy. Basically, the low-power nRF52832 would connect to a mains-powered nRF52832 through the GATT proxy, and then "inject" the packets it receives into its own mesh stack. In order to reduce the average power consumption to < 50 uA, I disabled the scanner and advertiser portion of the Mesh SDK, and replaced the TIMER0-based timer to a RTC2-based timer instead. I understand that this would be less precise, but I think it's potentially doable for a proof-of-concept, since with scanner and advertiser disabled, the mesh stack doesn't handle radio timing anymore. However I'm now running into the 0x134A2 assertion in the SoftDevice. Due to the decreased timer precision, I've increased the timeslot end safety margin and checked that the time slots are closed in time. Pointers about what that assertion is testing would be much appreciated.
