- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
I want to enable logs at stack and HCI levels for debugging an issue with paring for simple secure pairing method. I didnt found any documentation also for the same. I went through the header files but I didnt found any useful information
Solved! Go to Solution.
- Labels:
-
Debug
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The bug has been identified and should be corrected in the next SDK release
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try enabling your HCI tracing capabilities in your application_init(). For example, the hello sensor app is enabled for tracing by default, and it has to be disabled otherwise. I think a search on "tracing" will reveal quite a number of threads on this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Take a look at the WICED Smart Quick Start Guide (SDK 2.x and TAG3 Board)
"Viewing Traces from the WICED Smart Tag"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am using wiced Avnet IOT starter kit. I want to debug some issues with pairing. So is there any APIs that I should enable so as go get all the logs enabled at stack and HCI level.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Moving to the WICED Wi-Fi forum (this is where combo chips are supported), adding the WICED WiFi AE team: aky vik86 and peter_fenn (AWS specific)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any updates
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The bug has been identified and should be corrected in the next SDK release
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
aky wrote:
The bug has been identified and should be corrected in the next SDK release
Which SDK version fixes this issue?