Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

replaces lost reset logic from 'feature/reset-network-flag' (fixes #1045) #1050

Merged
merged 2 commits into from
Jul 20, 2016

Conversation

technobly
Copy link
Member

@technobly technobly commented Jun 29, 2016

  • replaces lost reset logic from 'feature/reset-network-flag' (fixes #1045)
  • also adds CLR_WLAN_WD() when SYSTEM_FLAG_RESET_NETWORK_ON_CLOUD_ERRORS is disabled
  • handle_cloud_errors() was not displaying orange blinks due to HAL_Delay_Milliseconds() not blocking
  • handle_cloud_errors() was moved to the end of establish_cloud_connection() to ensure errors are shown
  • added debugging info for all of the places ARM_WLAN_WD/CLR_WLAN_WD is called
  • added new logic for notify_connected() to ensure ARM_WLAN_WD is not called after DHCP resolves successfully
  • handle_cloud_errors() was fixed by making its process atomic, so that background system LED signaling did not interfere.
  • Because this fix causes a slight 1 to 1.5 second delay in system code execution, even when multi-threading is enabled. Not desirable, so for now we will disable this routine completely and defer enabling it again until the new LED handling routine is in place (0.6.x or 0.7.x). Also these particular blinks were never seen in the past, so existing behavior is preserved.

Doneness:

  • Contributor has signed CLA
  • Problem and Solution clearly stated
  • Code peer reviewed
  • API tests compiled
  • Run unit/integration/application tests on device
  • Add documentation (N/A)
  • Add to CHANGELOG.md after merging (add links to docs and issues)

- also adds CLR_WLAN_WD() when SYSTEM_FLAG_RESET_NETWORK_ON_CLOUD_ERRORS is disabled
- handle_cloud_errors() was not displaying orange blinks due to HAL_Delay_Milliseconds() not blocking
- handle_cloud_errors() was moved to the end of establish_cloud_connection() to ensure errors are shown
- added debugging info for all of the places ARM_WLAN_WD/CLR_WLAN_WD is called
- added new logic for notify_connected() to ensure ARM_WLAN_WD is not called after DHCP resolves successfully
@technobly technobly added this to the 0.6.x milestone Jun 29, 2016
@pomplesiegel
Copy link

just tested - issue still persists and is easily reproducible w/ this PR combined w/ #1047

@technobly
Copy link
Member Author

@pomplesiegel hmm, did you try without merging with #1047? I wonder if a merge issue negated something. Testing these separately, they both appear to work 100% for me. I'll attempt to merge #1047 with this and test.

- handle_cloud_errors() was fixed by making its process atomic, so that background system LED signaling did not interfere.
- Because this fix causes a slight 1 to 1.5 second delay in system code execution, even when multi-threading is enabled.  Not desireable, so for now we will disable this routine completely and defer enabling it again until the new LED handling routine is in place (0.6.x or 0.7.x).  Also these particular blinks were never seen in the past, so existing behavior is preserved.
@technobly
Copy link
Member Author

@pomplesiegel please give this one another test when you get a chance. I've tested it now with normal Tinker and multi-threaded Tinker with a blinking D7 LED and they both behave well for me. Thanks!

@technobly
Copy link
Member Author

@pomplesiegel just a friendly reminder, are issues with this PR are resolved for you now?

@technobly technobly merged commit b406724 into develop Jul 20, 2016
@technobly technobly deleted the feature/reset-network-flag-fixes branch October 27, 2016 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Flashing blue or green following wifi disconnect
3 participants