Fix KL05Z GCC_ARM linker script #814
Merged
Conversation
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
Issue originally reported on mbed site here: https://developer.mbed.org/questions/5695/FRDM-KL05z-hardfault-when-compiled-with-/ The RAM base address was incorrectly set to the beginning of RAM instead of at a 0xC0 byte offset to reserve room for the interrupt vectors. Without this fix, the global variables and the interrupt vectors were occupying the same space in RAM once the user enabled the timer interrupt. The user who originally reported the issue on the mbed site has tested this fix and verified that it corrected the hard fault issue that they were encountering.
|
Thanks, this was probably changed when targets were moved around. |
0xc0170
added a commit
that referenced
this pull request
Dec 24, 2014
Targets: Fix KL05Z GCC_ARM linker script
|
Thanks for merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue originally reported on mbed site here:
https://developer.mbed.org/questions/5695/FRDM-KL05z-hardfault-when-compiled-with-/
The RAM base address was incorrectly set to the beginning of RAM
instead of at a 0xC0 byte offset to reserve room for the interrupt
vectors. Without this fix, the global variables and the interrupt
vectors were occupying the same space in RAM once the user enabled the
timer interrupt.
The user who originally reported the issue on the mbed site has tested
this fix and verified that it corrected the hard fault issue that they
were encountering.