seems like we had a timing problem with an NVRAM write that was exposed when we turned filtration off.
Compound problem. In addition to NVRAM write latency causing issues, I had to also turn scan off before initiating a peripheral connection. For whatever reason, initiating a connection with scan enabled caused some very explosively undesirable behavior and a huge crash dump.
Is there any way to interpret what is contained in the crash dump?