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

Fixed ESP32 GPIO Uninitialize #1854

Merged
merged 3 commits into from
Mar 11, 2021
Merged

Fixed ESP32 GPIO Uninitialize #1854

merged 3 commits into from
Mar 11, 2021

Conversation

hbraasch
Copy link
Contributor

Description

The way CPU_GPIO_Uninitialize was implemented, a linked list itteration fails after the current item in the linked list gets removed during the itteration.
A better coding pattern, macro NANOCLR_FOREACH_NODE is now used which allows removal of the item while itterating.

Motivation and Context

As part of solving issue #705 it was noticed that, if any INPUT pins are defined, the application raises an unhandled exception when entering deep sleep state.

How Has This Been Tested?

Tested on a cloned build using the same test app using for Issue #705

Screenshots

Types of changes

  • Improvement (non-breaking change that improves a feature, code or algorithm)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Config and build (change in the configuration and build system, has no impact on code or features)
  • Dependencies (update dependencies and changes associated, has no impact on code or features)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

As part of solving issue #705 it was noticed that, if any INPUT pins are defined, the application raises an unhandled exception when entering deep sleep state.
This change is to fix this problem.
It was found that the way <<CPU_GPIO_Uninitialize>> is implemented, a linked list itteration fails after the current item in the linked list gets removed during the itteration. 
A better coding pattern is now used which allows removal of the item while itterating.
Automated fixes for code style.
@nfbot
Copy link
Member

nfbot commented Mar 11, 2021

@hbraasch there are issues with the code style on the source files.
A PR was submitted with the code style fixes. Please review and merge the changes. See https://github.com/hbraasch/nf-interpreter/pull/1.

Make sure you are using the project code style. Check the details here.

Copy link
Contributor Author

@hbraasch hbraasch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks OK

…7de-7b23-4abf-a9e7-7276b2c31254

Code style fixes for nanoframework/nf-interpreter PR#1854
@josesimoes josesimoes added the Series: ESP32 Everything related specifically with ESP32 series targets label Mar 11, 2021
Copy link
Member

@josesimoes josesimoes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well done! Thanks for taking care of this one too. 👍🏻

@josesimoes josesimoes changed the title Fixed ESP32 deep sleep start exception by correcting linked list iterration Fixed ESP32 GPIO Uninitialize Mar 11, 2021
@josesimoes josesimoes merged commit 2679545 into nanoframework:develop Mar 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Series: ESP32 Everything related specifically with ESP32 series targets Type: bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants