- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
From the trace window provided in WICED-Smart-SDK IDE, I got following message:
Is this something related to the back-trace of previous crash? How do I enable the source code interpretation to the IDE?
16:40:51 Trace Decoding Error - Could not find line number 314
16:40:51 Len, Max Len : 0014, 0014
16:40:51 UUID : 0000
16:40:51 Attribute bytes
16:40:51 Handle: FF06
16:40:51 Perm : 0002
16:40:51 Trace Decoding Error - Could not find line number 372
16:40:51 Trace Decoding Error - Could not find line number 15361
16:40:51 Trace Decoding Error - Could not find line number 269
16:40:51 Trace Decoding Error - Could not find line number 0
16:40:51 Trace Decoding Error - Could not find line number 13884
16:40:51 Trace Decoding Error - Could not find line number 524
16:40:51 Trace Decoding Error - Could not find line number 512
16:40:51 Trace Decoding Error - Could not find line number 512
16:40:51 Trace Decoding Error - Could not find line number 512
16:40:51 Trace Decoding Error - Could not find line number 512
16:40:51 Trace Decoding Error - Could not find line number 528
16:40:51 Trace Decoding Error - Could not find line number 512
16:40:51 Trace Decoding Error - Could not find line number 512
16:40:51 Trace Decoding Error - Could not find line number 0
Solved! Go to Solution.
- Labels:
-
SDK 2.X
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We spoke to the developers on this one and they believe that the problem is that your GATT DB may not be formed correctly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is this a sample application or your own? Is the GATT DB well-formed (no errors if the structure, especially if you hand-coded it)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is my own application.
Such message was popping up after crash when I tried to use OOB pairing with encryption in my application.
My application can work well when OOB pairing is not enabled, but it crashed every time when the OOB is enabled. That's why I am trying to check if any possibility to have deep analysis from the log message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We spoke to the developers on this one and they believe that the problem is that your GATT DB may not be formed correctly.