- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I use scan result to pass to the "wwd_wifi_join_specific" call, but this call fails with reasons like:
"1024: Failed to find network",
"1006: Failed to authenticate",
1023, 1025 etc.
I have enabled WWD prints to log the status and attached it in this post.
What could be the reason this join specific call fails so many times before succeeding? Is there a way to reduce this failure rate?
The errors like failed to find network and failed to authenticate don't seem right since the network is clearly available as it is being passed the result of scan call and the passkey is correct as it eventually succeeds[but takes many many tries].
This is in contrast to wiced_network_up call that usually succeeds pretty quickly on the same network. But that is usually called on first boot up
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Okay I was able to get around this by explicitly using the semaphore input in the join_specific call and waiting for the join to complete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello:
Do you have an antenna in your evb before the test ? yes, sometimes I will encounter the join fails, but not very often.
I think you can have a AP with open and place it near to your evb , let us remove the antenna and authentication factors firstly .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, The AP is right next to the EVB. Surprising is the fact that if I join this same network on boot up with wiced_network_up() it connects in one or two tries. So it is surprising why join_specific would take so many tries? Is it got to do with the parameters passed to the call? For example, I scan for a particular network and pass the result of the scan to join_specific
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Okay I was able to get around this by explicitly using the semaphore input in the join_specific call and waiting for the join to complete