Skip to content

[NUCLEO_F302R8] Fix issue with SystemCoreClock variable update. #233

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
Mar 25, 2014
Merged

[NUCLEO_F302R8] Fix issue with SystemCoreClock variable update. #233

merged 1 commit into from
Mar 25, 2014

Conversation

bcostm
Copy link
Contributor

@bcostm bcostm commented Mar 25, 2014

This variable must be placed outside the RAM initialization section.

This variable must be placed outside the RAM initialization section.
bogdanm added a commit that referenced this pull request Mar 25, 2014
[NUCLEO_F302R8] Fix issue with SystemCoreClock variable update.
@bogdanm bogdanm merged commit 8b4f078 into ARMmbed:master Mar 25, 2014
@0xc0170
Copy link
Contributor

0xc0170 commented Mar 25, 2014

Hello bcostm,

why that variable must be placed outside of the RAM initialization section?
There should be an easier way to get desired result. First which comes to my mind, to set variable System core clock by preprocessor based on the selected clocks (it is known before run-time) ? This is how it's done in another platforms.

Regards,
0xc0170

@bcostm
Copy link
Contributor Author

bcostm commented Mar 25, 2014

Hi,

Thanks to Bogdan, yes there is another way. I must use the mbed_sdk_init function which is called after the RAM initialization and before the main. I will do my clock setting stuff inside it. I will remove the change in the scatter file too (not needed) and send a new pull request.

Regards

bridadan pushed a commit that referenced this pull request Jun 21, 2016
Automatically define uVisor labels
pan- pushed a commit to pan-/mbed that referenced this pull request May 29, 2020
Adds a trigger, invokes the library in tests repo
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.

3 participants