-
Notifications
You must be signed in to change notification settings - Fork 3k
STM32: add setting for LSE drive load level #13797
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
0xc0170
merged 7 commits into
ARMmbed:master
from
JojoS62:PR_fix_LSE-drive-load-setting
Nov 18, 2020
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
8145b69
add setting for LSE drive load level
JojoS62 a209d44
simplify checking for F4_g2 exception
JojoS62 e7f1430
remove duplicate LSEDRIVE_CONFIG
JojoS62 80847e9
simplify default setting
JojoS62 64072a9
fix for targets with non-modifiable
JojoS62 622a452
fix macro usage error
JojoS62 6264e0a
add defaults values
JojoS62 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not entirely sure if something changed since [1] was documented, but I think the build system will interpret the "macro_name" from target.json without adding the "MBED_CONF_" prefix, which will lead to the setting never being applied. I noticed this while I was backporting this to mbedos 5 so I might be wrong.
[1] https://os.mbed.com/docs/mbed-os/v6.11/program-setup/advanced-configuration.html
Edited: added the comment here, as adding it to all the target.json lines would have been a pain.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi
I am sorry, I didn't understand well the question.
I don't think there is something different between mbedos 5 and 6 about json configuration.
And no need to add this line for each target as it can be defined at the family level.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I didn't made my point in an understandable way:
The implementation requires
MBED_CONF_TARGET_LSE_DRIVE_LOAD_LEVELto be defined to set LSEDRV from the config. However, intarget.jsonthe actual parameter is set to"macro_name": "TARGET_LSE_DRIVE_LOAD_LEVEL"which will result in the target not being generated asMBED_CONF_TARGET_LSE_DRIVE_LOAD_LEVEL, but without the prefixMBED_CONF_. (See [1] above comment)This results in the value from
target.json(or anywhere else, where the setting is overridden from) never being used in the first place, as far as I understand.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sorry, was resolved here #13939
Never mind. My fault.