Skip to content

STM32: RESET GPIO during init is configurable #14032

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

Merged
merged 1 commit into from
Jan 15, 2021

Conversation

jeromecoutant
Copy link
Collaborator

Summary of changes

Since #13777, GPIO are all reset during init before application starts.

Now this reset is done only if, in order to optimize power, application is configured it in mbed_app.json

    "overrides": {
        "target.gpio_reset_at_init": 1
    },

@facchinm
@LMESTM

Impact of changes

Migration actions required

Documentation


Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

Reviewers


@ciarmcom ciarmcom added the release-type: patch Indentifies a PR as containing just a patch label Dec 11, 2020
@ciarmcom
Copy link
Member

@jeromecoutant, thank you for your changes.
@ARMmbed/team-st-mcd @ARMmbed/mbed-os-maintainers please review.

@ciarmcom ciarmcom requested review from a team December 11, 2020 16:30
@@ -3200,6 +3204,9 @@
"macro_name": "CLOCK_SOURCE"
}
},
"overrides": {
"gpio_reset_at_init": 1
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
"gpio_reset_at_init": 1
"gpio_reset_at_init": true

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

},
"gpio_reset_at_init": {
"help": "if value set, all GPIO are reset during init",
"value": 0
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
"value": 0
"value": false

@0xc0170
Copy link
Contributor

0xc0170 commented Jan 5, 2021

@jeromecoutant please rebase to resolve Travis error (latest master).

This type of config would make sense to be for all targets (not part of this PR), just thinking we shall upstream it one day.

To recap, it was fixed to reset all gpio pins during startup. This however has implications so it should be configurable (13826 PR was affected unfortunately). Correct?

@jeromecoutant
Copy link
Collaborator Author

please rebase to resolve Travis error (latest master).

Done

To recap, it was fixed to reset all gpio pins during startup. This however has implications so it should be configurable (13826 PR was affected unfortunately). Correct?

Yes

@0xc0170
Copy link
Contributor

0xc0170 commented Jan 5, 2021

CI started

@mbed-ci
Copy link

mbed-ci commented Jan 5, 2021

Jenkins CI Test : ❌ FAILED

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs Status
jenkins-ci/mbed-os-ci_cmake-example-GCC_ARM ✔️
jenkins-ci/mbed-os-ci_cmake-example-ARM ✔️
jenkins-ci/mbed-os-ci_unittests ✔️
jenkins-ci/mbed-os-ci_build-greentea-ARM ✔️
jenkins-ci/mbed-os-ci_build-greentea-GCC_ARM ✔️
jenkins-ci/mbed-os-ci_build-example-ARM ✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM ✔️
jenkins-ci/mbed-os-ci_build-cloud-example-ARM ✔️
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM ✔️
jenkins-ci/mbed-os-ci_cmake-example-test ✔️
jenkins-ci/mbed-os-ci_greentea-test

@mergify mergify bot added needs: work and removed needs: CI labels Jan 5, 2021
@0xc0170
Copy link
Contributor

0xc0170 commented Jan 5, 2021

@jeromecoutant can you check ethernet failures if they are related to this PR?

@jeromecoutant
Copy link
Collaborator Author

@jeromecoutant can you check ethernet failures if they are related to this PR?

I don't see any failed tests in the log...

NB: see https://forums.mbed.com/t/cant-debug-with-nucleo-stm32f411re-stlink-error-22/11550/10
This PR seems important

@0xc0170
Copy link
Contributor

0xc0170 commented Jan 11, 2021

I restarted tests to confirm if its related, if fail again, I'll check the failures in detail.

@mbed-ci
Copy link

mbed-ci commented Jan 11, 2021

Jenkins CI Test : ✔️ SUCCESS

Build Number: 2 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs Status
jenkins-ci/mbed-os-ci_cmake-example-ARM ✔️
jenkins-ci/mbed-os-ci_cmake-example-GCC_ARM ✔️
jenkins-ci/mbed-os-ci_unittests ✔️
jenkins-ci/mbed-os-ci_build-greentea-ARM ✔️
jenkins-ci/mbed-os-ci_build-greentea-GCC_ARM ✔️
jenkins-ci/mbed-os-ci_build-cloud-example-ARM ✔️
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM ✔️
jenkins-ci/mbed-os-ci_build-example-ARM ✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM ✔️
jenkins-ci/mbed-os-ci_cmake-example-test ✔️
jenkins-ci/mbed-os-ci_greentea-test ✔️

@jeromecoutant
Copy link
Collaborator Author

Let's merge ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants