- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In our central device, running SDK 2.0.1, does anyone know why
blecen_cen_cfg.filter_duplicates = HCIULP_SCAN_DUPLICATE_FILTER_OFF;
causes a large tracedump leading to a watchdog reset?
Of course, we could enable filtration, but then we would be missing some advertisements.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
seems like we had a timing problem with an NVRAM write that was exposed when we turned filtration off.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?