Hello!
I am using mbed based boot loader and application. Boot loader uses internal clock and application uses external crystal (custom_targets.json => “clock_source”: “USE_PLL_HSE_XTAL”). When boot loader boots the application certain gpio’s and other interfaces don’t work as they should.
If i configure my custom board to use internal clock then these things work (custom_targets.json => “clock_source”: “USE_PLL_HSI”) . External 8MHz crystal is connected PH0 and PH1 (OSC_IN, OSC_OUT).
If I use debugger (and thus skip the boot loader) to start application these things work.
My question is should i take something into account when boot loader switches over to my application and they have different clock sources?
Hi
I don’t know which clock setting do you use, but you can have a deep look into this issue:
ARMmbed:master ← pilotak:master
opened 09:52AM - 19 May 20 UTC
<!--
For more information on the requirements for pull requests, please see [th… e contributing guidelines](https://os.mbed.com/docs/mbed-os/latest/contributing/workflow.html).
NOTE: Do not remove any of the template headings (even for optional sections) as this
template is automatically parsed.
-->
### Summary of changes
fixes STM32F412 SetSysClock failed #12993
<!--
Please provide the following information:
Description of the the change (what is this fixing / adding / removing?).
Why the change is needed (if this is fixing a reported issue please summarize what
the issue is and add the reference. E.g. Fixes #17119).
NOTE: This section is automatically written to release notes for Feature and
Major releases and should contain enough details for a user.
-->
#### Impact of changes
<!--
If there are any implications for users taking this change then they must be
provided here. For Major PR types this field is MANDATORY.
NOTE: This section is automatically written to release notes for Feature and
Major releases and should contain enough details for a user.
-->
#### Migration actions required
<!--
This should only be applicable in Major PR types for which this field is MANDATORY.
NOTE: This section is automatically written to release notes for Feature and
Major releases and should contain enough details for a user.
-->
### Documentation
<!--
Please provide details of any document updates required, including links to any
related PRs against the docs repository.
If no document updates are required please specify 'None', this at least tells us
that this has been considered.
-->
----------------------------------------------------------------------------------------------------------------
### Pull request type
<!--
Please add only one X to one of the following types. Do not fill multiple types (split the pull request otherwise).
Please note this is not a GitHub task list, indenting the boxes or changing the format to add a '.' or '*' in front of them would change the meaning incorrectly.
-->
[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
<!--
Provide all the information required, listing all the testing performed. For new targets please attach full test results for all supported compilers.
-->
[] 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
<!--
Request additional reviewers with @username or @team
-->
@jeromecoutant
----------------------------------------------------------------------------------------------------------------
Jerome
Hello,
Thank you i will take a look at this! Might have something to do with my issue.
